Rapid application development: in typical prototyping projects, which toolset or language class is commonly used to build quick, interactive mockups?
-
AThird-generation languages only (for example, COBOL) with full production scaffolding
-
BFourth-generation languages (4GLs), RAD tools, or visual builders to iterate quickly with users
-
CHandwritten assembly to maximize performance from the start
-
DOnly documentation templates without executable artifacts
-
ENone of the above
Answer
Correct Answer: Fourth-generation languages (4GLs), RAD tools, or visual builders to iterate quickly with users
Explanation
Introduction / Context:Prototyping emphasizes speed and user feedback to reduce requirements risk. Tools that accelerate UI building, data binding, and logic stubs enable rapid iterations.
Given Data / Assumptions:
- Goal: quickly demonstrate behavior to users for validation.
- High productivity and flexibility matter more than early optimization.
- Artifacts may later be hardened or rewritten for production.
Concept / Approach:Fourth-generation languages (4GLs) and RAD tools provide declarative forms, report writers, visual designers, and high-level data access. They shorten the path from idea to interactive model, which is why they are favored in prototyping.
Step-by-Step Solution:
Select tools with rapid UI/data features (forms, wizards, scaffolding).Create a minimum viable prototype, gather feedback, and refine.Plan transition to production quality after requirements stabilize.Verification / Alternative check:Case studies show reduced rework when user feedback is captured early via working prototypes.
Why Other Options Are Wrong:COBOL or assembly are inefficient for fast iteration; documentation alone cannot validate usability.
Common Pitfalls:Mistaking a prototype for production without refactoring; always assess non-functional requirements before go-live.
Final Answer:Fourth-generation languages (4GLs), RAD tools, or visual builders to iterate quickly with users