Process: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Protected "Process" [edit=sysop:move=sysop]) |
Latest revision as of 21:40, 22 November 2008
Note: This page is obsolete. Please go to the home page.
Thunderforce's development process is loosely based on Anthony Lattanze's Architecture-Centric Development Methodology (ACDM), which is popular process framework in the Master of Software Engineering (MSE) program at Carnegie Mellon University and elsewhere. For the development phase, a design-oriented process that refines the architectural modules into detailed design and then code will be used.
- Requirements elicitation
- Quality attributes
- Requirements prioritization and project scope
- High-level project planning
- Use cases
- Notional architecture
- Experiments
- Architectural review and refinement
- Module identification and assignment
- Integration test creation
- Detailed module designs
- Module unit tests
- Module code
- Integration tests passing
- Releases