Process: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
#[[Module identification and assignment]] | #[[Module identification and assignment]] | ||
#[[Integration test creation]] | #[[Integration test creation]] | ||
#Detailed module designs | #[[Detailed module designs]] | ||
#Module unit tests | #[[Module unit tests]] | ||
#Module code | #[[Module code]] | ||
#Integration tests passing | #Integration tests passing | ||
#Releases | #Releases | ||
Revision as of 04:49, 30 August 2007
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