Use a spiral development model with periodic prototype deliveries for assessment software¶

Strategy · All strategies
Evidence · no claims cited

Description¶

Because the assessment software will have evolving requirements, the report adopts a spiral development model: "The spiral model minimizes risks through incremental development of software." Periodic prototype deliveries are planned, with each cycle implementing only the highest priority features and successive cycles adding more. Technical and functional problems are identified early, informing cancel-or-continue decisions, and a working prototype is always available for demonstration.

Design Implications¶

Context¶

Requirements¶

• Software development with evolving requirements

Constraints¶

• Assumes the team will be developing software rather than only specifying it

Target Learners¶

• developers and funders of educational assessment software

Target Learning Goals¶

• risk-managed development of computer-based assessment tools

Related Strategies¶

Examples¶

-

Key Sources¶

• Chung, G. K. W. K., Herl, H. E., Klein, D. C. D., O'Neil, H. F., Jr., & Schacter, J. (1997). Estimate of the Potential Costs and Effectiveness of Scaling Up CRESST Assessment Software. https://eric.ed.gov/?id=ED418102