MCQ On Prototype Model
Q1. The Prototype Model is mainly used when:.
- Requirements are very clear
- Requirements are unclear or evolving
- Project is very small
- No user involvement is needed
Answer: b, Requirements are unclear or evolving
Solution: Prototype Model is ideal when requirements are unclear.
Q2. A prototype is:.
- The final working system
- A rough working model to gather requirements
- A testing tool
- A deployment version
Answer: b, A rough working model to gather requirements
Solution: Prototype helps users visualize early.
Q3. Which step comes first in the Prototype Model?.
- Final testing
- Quick design
- Build prototype
- Requirement gathering
Answer: d, Requirement gathering
Solution: Requirements are gathered first.
Q4. The main purpose of building a prototype is to:.
- Finish the project faster
- Clarify user requirements
- Replace the final product
- Enhance system performance
Answer: b, Clarify user requirements
Solution: Prototype clarifies requirements.
Q5. Prototype Model is best suited for:.
- Projects with stable requirements
- UI-heavy or interactive systems
- Projects with no user involvement
- Very large and stable systems
Answer: b, UI-heavy or interactive systems
Solution: Prototypes help visualize UI early.
Q6. Which of the following is NOT part of the Prototype Model?.
- Customer evaluation
- Quick design
- Risk analysis
- Refining requirements
Answer: c, Risk analysis
Solution: Risk analysis is part of Spiral Model.
Q7. After building the prototype, the next step is:.
- Final development
- Customer review
- Deployment
- Validation
Answer: b, Customer review
Solution: User reviews the prototype.
Q8. A disadvantage of the Prototype Model is:.
- Users get early working model
- Requirements can be clarified
- High development cost
- Early detection of errors
Answer: c, High development cost
Solution: Building multiple prototypes is costly.
Q9. The prototype is usually:.
- Fully functional
- Partially functional with limited features
- The final product
- A deployment tool
Answer: b, Partially functional with limited features
Solution: Prototype shows limited functionality.
Q10. The Prototype Model helps reduce:.
- Customer involvement
- Misunderstanding in requirements
- Testing time
- Deployment effort
Answer: b, Misunderstanding in requirements
Solution: Prototype reduces requirement confusion.
Q11. One major problem of Prototype Model is:.
- Slow delivery
- Users may think the prototype is the final system
- No user involvement
- No testing required
Answer: b, Users may think the prototype is the final system
Solution: Users may confuse prototype with final system.
Q12. Prototype Model is NOT suitable for:.
- Complex user-interactive systems
- Systems with unclear requirements
- Stable and well-defined projects
- Research-based projects
Answer: c, Stable and well-defined projects
Solution: Prototype is unnecessary for stable requirements.
Q13. Which is the correct sequence in Prototype Model?.
- Build prototype -> Quick design -> Requirement
- Requirement -> Quick design -> Build prototype -> Review
- Requirement -> Build prototype -> Review -> Quick design
- Deployment -> Prototype -> Review
Answer: b, Requirement -> Quick design -> Build prototype -> Review
Solution: This is the correct order.
Q14. Prototype is mainly used for:.
- Improving documentation
- User interface validation
- Coding optimization
- System maintenance
Answer: b, User interface validation
Solution: Prototype helps validate UI early.
Q15. Which model allows customer feedback very early?.
- Waterfall
- V-Model
- Prototype Model
- Spiral Model
Answer: c, Prototype Model
Solution: Prototype includes early review.
Q16. Which type of prototype is thrown away after use?.
- Evolutionary
- Incremental
- Throwaway prototype
- Spiral prototype
Answer: c, Throwaway prototype
Solution: Throwaway prototype is discarded.
Q17. The final system is developed:.
- Immediately after requirement gathering
- After refining requirements using the prototype
- Without customer involvement
- Before creating a prototype
Answer: b, After refining requirements using the prototype
Solution: Requirements are refined first.
Q18. Prototype Model reduces:.
- Deployment cost
- Communication gap between users and developers
- Testing time
- Documentation effort
Answer: b, Communication gap between users and developers
Solution: Prototype improves communication.
Q19. Prototype Model helps identify:.
- Exact coding errors
- Performance issues
- Misunderstood or missing requirements
- Database errors
Answer: c, Misunderstood or missing requirements
Solution: Prototype clarifies missing requirements.
Q20. The biggest advantage of Prototype Model is:.
- No rework
- Improves requirement clarity
- Saves time always
- No customer involvement
Answer: b, Improves requirement clarity
Solution: Better requirement understanding is the main advantage.