IPRO 329 Pipeline Model Below is the pipeline showing how IPRO 329 team operates throughout the semester. By using time efficiently, more work can be done on a parallel basis. The team divides process of work into three phases: Phase I: Create, analyze, research, and select game ideas. Phase II: Design and Development. Phase III: Deployment.

Iterative Prototyping Model (Software)
The final product of our collaborative efforts is a software product. There are a number of approaches to software development, each of which has a set of advantages and disadvantages associated with it. For our project, we have chosen an approach that we call the Iterative Prototyping Process Model. This model is based on the general Prototyping Process Model.

When using the Prototyping Model, the developers build a simplified version of the proposed system, and present it to potential users for consideration as part of the development process. The users in turn provide feedback to the designers and developers, who go back and refine the system to incorporate the additional information.

The process consists of the following looping steps:

• Analysis. The information collected is usually limited to a subset of the complete system requirements.
• Design. Once the initial layer of requirements information is collected, or new information is gathered, it is rapidly integrated into a new or existing design so that it may be folded into the prototype.
• Prototyping. The information from the design is rapidly rolled into a prototype. This may mean the creation/modification of paper information, new coding, or modifications to existing coding.
• User Testing. The prototype is presented to possible users for review. Comments and suggestions are collected from the users and reported back to the team.
• Refinement. Information collected from the customer is digested and the prototype is refined. The developer revises the prototype to make it more effective and efficient.
• Implementation. The results of the tests are used to guide the changes to the system. As some parts or phases of the software are implemented, other parts and prototyped and tested.

The main advantage of this model is that the iterative nature of development allows for parallel progress of several tasks - different system features are being designed, tested and implemented at the same time.