ITM 430 Chapter Notes - Chapter 8: Storyboard, Software Architecture

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 430
• Professor: Aziz Guergachi

Document Summary

This is not the requirements phase of the project. The artifacts are brief, incomplete, quick and light investigation. Most actors, goals, and uses cases named. Technical proof-of-concept prototypes and other investigations to explore the technical feasibility of special requirements. The core, risky software architecture is programmed and tested. The majority of requirements are discovered and stabilized. It is not the design phase or a phase when the models are fully developed in preparation for implementation. In one sentence: build the core architecture, resolve the high-risk elements, define most requirements, and estimate the overall schedule and resources. Domain model (a static information model of the domain entities) Design model (set of diagrams that describe the logical design, which includes software class diagrams, object interaction diagrams, package diagrams, and so forth) Software architecture document (key issues, resolution in the design, and a summary of the outstanding design ideas and their motivation in the system)