Rapid Prototyping Model
• Emphasis is on creating a prototype that looks and acts like the desired product in order to test its usefulness
• Develop a system with reduced capability
• Present to client for approval
• Once the prototype is approved, it is discarded and the “real” software is written.
• Develops specification with better understanding
• Exactly like the Spiral Model, where a prototype or only “shadow” of the real software is made, where the system (during implementation stage) is not that graphically perfect but features are functioning well for testing purposes
• Only difference is, in Rapid Prototyping, it requires client approval prior to the building of the “real” software
• Develop a system with reduced capability
• Present to client for approval
• Once the prototype is approved, it is discarded and the “real” software is written.
• Develops specification with better understanding
• Exactly like the Spiral Model, where a prototype or only “shadow” of the real software is made, where the system (during implementation stage) is not that graphically perfect but features are functioning well for testing purposes
• Only difference is, in Rapid Prototyping, it requires client approval prior to the building of the “real” software
Comments