Process

From Thunderforce
Revision as of 21:40, 22 November 2008 by Stevenlawrance (talk | contribs) (Protected "Process" [edit=sysop:move=sysop])
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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.

  1. Requirements elicitation
  2. Quality attributes
  3. Requirements prioritization and project scope
  4. High-level project planning
  5. Use cases
  6. Notional architecture
  7. Experiments
  8. Architectural review and refinement
  9. Module identification and assignment
  10. Integration test creation
  11. Detailed module designs
  12. Module unit tests
  13. Module code
  14. Integration tests passing
  15. Releases