Prototype and Waterfall Model
Terms in this set (20)
A prototype is an early sample or model built to test a concept or process or to act as a thing to be replicated or learned from
Software prototyping, refers to the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed.
Stage One Prototype Model
Purpose: To get the system requirements from the user
Prototype Stage One Process
Process: Interviews, questionnaire, feedback reports, work process flowcharts
Prototype Stage One Documents
Documents Generated: Draft Requirements, Feasibility Report, Cost Benefit Analysis
Prototype Stage Two
Stage 2: Build/Change Prototype
Purpose: To build a system prototype as per user requirements to give an idea of system to be developed
Prototype Stage Two Process
Process: Develop/Change prototype as per draft requirements
Prototype Stage Two Documents
Documents: Prototype Functionality Report, Version Control Document
Prototype Stage Three
Stage 3: User Feedback
Purpose: To seek feedback on prototype so as to capture specific requirements and refine the prototype.
Prototype Stage Three Process
Process: Present prototype, Generate Feedback report
Prototype Stage Three Documents
Documents: Feedback report
Prototype Stage Four
Stage 4: Finalise Requirements
Purpose: To get sign-off on final system requirements from user/client
Prototype Stage Four Process
Process: Prepare final requirements specifications, Project scope and planning
Prototype Stage Four Documents
Documents: Project Proposal, Requirements Specifications
Used for well defined projects with less degree of uncertainty
Project progresses sequentially through each stage of the waterfall model
Each stage involves a test (validation or verification) to prevent problem accumulation over stages.
Waterfall Model Advantages
1. Clear project objectives. 2. Stable project requirements. 3. Progress of system is measurable. 4. Strict sign-off requirements.
Waterfall Model Disadvantages
1. Time consuming 2. Never backward (Traditional) 3. Little room for iteration 4. Difficulty responding to changes
Process of developing a small working model of a program component or system with the intent of seeing what it can do.
Learn and build approach.
Users evaluate prototype
New prototype built on user feedback
Allows user to see benefits from the system
Develops requirements when uncertain what the system needs to do
Lower development cost and time
Users directly involved in system design
Less efficient performance
Large-scale projects difficult to prototype