Main Page: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
==Process==
==Process==
Thunderforce is presently in its requirements elicitation stage. At this time, the following process is planned, though this can easily change as needed. This process is loosely based on [http://www.sei.cmu.edu/architecture/saturn/2006/Lattanze.pdf Anthony Lattanze's Architecture-Centric Development Methodology (ACDM)].
Thunderforce is presently in its requirements elicitation stage. At this time, the following process is planned, though this can easily change as needed. This process is loosely based on [http://www.sei.cmu.edu/architecture/saturn/2006/Lattanze.pdf Anthony Lattanze's Architecture-Centric Development Methodology (ACDM)].
#[[Picture of success]]
#[[Requirements elicitation]]
#[[Requirements elicitation]]
#[[Quality attributes]]
#[[Quality attributes]]
Line 21: Line 22:
**Read-write access can be requested by emailing [mailto:thunderforce@moonlightdesign.org Steven Lawrance]
**Read-write access can be requested by emailing [mailto:thunderforce@moonlightdesign.org Steven Lawrance]
*Releases (coming later)
*Releases (coming later)
==People==
*Project Lead: [https://www.moonlightdesign.org/steve/ Steven Lawrance]
*Architects
**[https://www.moonlightdesign.org/steve/ Steven Lawrance]
*Developers
**[https://www.moonlightdesign.org/steve/ Steven Lawrance]
*Quality Assurance
**[https://www.moonlightdesign.org/steve/ Steven Lawrance]
*Development Support
**[https://www.moonlightdesign.org/steve/ Steven Lawrance]
*End-User Documentation
*End-User Testing
*'''Please [mailto:thunderforce@moonlightdesign.org let me know] which role(s) you want to help out with'''

Revision as of 03:27, 27 April 2007

Welcome to Thunderforce -- a Mozilla Thunderbird extension for Salesforce.com

Process

Thunderforce is presently in its requirements elicitation stage. At this time, the following process is planned, though this can easily change as needed. This process is loosely based on Anthony Lattanze's Architecture-Centric Development Methodology (ACDM).

  1. Picture of success
  2. Requirements elicitation
  3. Quality attributes
  4. Requirements prioritization and project scope
  5. Notional architecture
  6. Experiments
  7. Architectural review and refinement
  8. Module planning
  9. Module test creation
  10. Module authoring and unit testing
  11. Module integration testing
  12. Releases

Artifacts

People