Main Page: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
Line 44: Line 44:
Thunderforce is not to be confused with the following:
Thunderforce is not to be confused with the following:
*[http://en.wikipedia.org/wiki/Thunder_Force Thunder Force video game]
*[http://en.wikipedia.org/wiki/Thunder_Force Thunder Force video game]
*[http://www.thunderforce.org/ ThunderForce heavy metal band]
*[http://www.thunderforce.org/ ThunderForce heavy metal band] (requires JavaScript)

Revision as of 06:32, 27 April 2007

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

Surveys

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. Requirements elicitation
  2. Quality attributes
  3. Requirements prioritization and project scope
  4. Notional architecture
  5. Experiments
  6. Architectural review and refinement
  7. Module planning
  8. Module test creation
  9. Module authoring and unit testing
  10. Module integration testing
  11. Releases

Artifacts

People

Disambiguation

Thunderforce is not to be confused with the following: