Process: Difference between revisions
Jump to navigation
Jump to search
(New page: Thunderforce's development process is loosely based on [http://reports-archive.adm.cs.cmu.edu/anon/isri2005/CMU-ISRI-05-103.pdf Anthony Lattanze's Architecture-Centric Development Methodol...) |
No edit summary |
||
| Line 8: | Line 8: | ||
#[[Experiments]] | #[[Experiments]] | ||
#[[Architectural review and refinement]] | #[[Architectural review and refinement]] | ||
#Module identification and assignment | #[[Module identification and assignment]] | ||
#Integration test creation | #Integration test creation | ||
#Detailed module designs | #Detailed module designs | ||
Revision as of 07:21, 21 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