Main Page: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
Line 20: Line 20:


==Process==
==Process==
This process is loosely based on [http://www.sei.cmu.edu/architecture/saturn/2006/Lattanze.pdf Anthony Lattanze's Architecture-Centric Development Methodology (ACDM)], which is popular in the Master of Software Engineering (MSE) program at Carnegie Mellon University.
This process is loosely based on [http://www.sei.cmu.edu/architecture/saturn/2006/Lattanze.pdf 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, with an adaptation of [http://en.wikipedia.org/wiki/Scrum_%28development%29 scrum] as the development process.
#[[Requirements elicitation]]
#[[Requirements elicitation]]
#[[Quality attributes]]
#[[Quality attributes]]
#[[Requirements prioritization and project scope]]
#[[Requirements prioritization and project scope]]
#[[Project planning]]
#Notional architecture
#Notional architecture
#Experiments
#Experiments
#Architectural review and refinement
#Architectural review and refinement
#Module planning
#Module identification and assignment
#Module test creation
#Sprint 1: Initial integration tests and development of base functionality
#Module authoring and unit testing
#Sprint 2: Feature development and integration test refinement
#Module integration testing
#Sprint 3: Release finalization and packaging
#Releases
#Releases



Revision as of 07:03, 3 May 2007

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

Please feel free to look at and comment on the feature list. This extension has not been written yet, so if you contribute now, you can help steer the direction of Thunderforce. Contrary to a recent posting on ZDnet, Thunderforce will not be available in the upcoming days or weeks. Instead, partial functionality is presently planned for a pre-alpha version in mid-August.

Current stage: High-level schedule planning

Please feel free to discuss features through the "discussion" tab at the top of each page

Surveys

  • Requirements survey 1
    • Which Thunderbird versions should Thunderforce support? (note that requiring 2.0 or later is almost a foregone conclusion with the current feature set)
    • Which operating systems do you run Thunderbird on? So far, Linux and Windows are both tied with the highest number of votes. Fortunately, promoting the portability quality attribute will lead to compatibility for all platforms that Thunderbird runs on, assuming technical feasibility
    • What should the license be?
    • Which features are most popular? (note that the feature list has expanded somewhat since the survey was created)
    • Take the survey to quickly and anonymously let us know!
  • Feature Survey 1 coming soon!
  • Survey administration (email me for access)

Process

This 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, with an adaptation of scrum as the development process.

  1. Requirements elicitation
  2. Quality attributes
  3. Requirements prioritization and project scope
  4. Project planning
  5. Notional architecture
  6. Experiments
  7. Architectural review and refinement
  8. Module identification and assignment
  9. Sprint 1: Initial integration tests and development of base functionality
  10. Sprint 2: Feature development and integration test refinement
  11. Sprint 3: Release finalization and packaging
  12. Releases

Artifacts

People

Useful Development Links

Disambiguation

Thunderforce is not to be confused with the following: