Main Page: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
Line 9: Line 9:
|style="vertical-align:top; width: 70%; padding-right: .6em;"|
|style="vertical-align:top; width: 70%; padding-right: .6em;"|
==Surveys==
==Surveys==
*[https://www.moonlightdesign.org/thunderforce/phpesp/public/survey.php?name=RequirementsSurvey1 Requirements survey 1]
*[[Results of Requirements Survey 1]]
**Which Thunderbird versions should Thunderforce support? (note that requiring 2.0 or later is almost a foregone conclusion with the [[Features|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 [[Quality_attributes#Portability|portability quality attribute]] will lead to compatibility for all platforms that Thunderbird runs on, assuming technical feasibility
**What should the license be?
**Which [[Features|features]] are most popular? (note that the [[Features|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!
*Feature Survey 1 coming soon!
*[https://www.moonlightdesign.org/thunderforce/phpesp/ Survey administration] ([mailto:thunderforce@moonlightdesign.org email me] for access)
*[https://www.moonlightdesign.org/thunderforce/phpesp/ Survey administration] ([mailto:thunderforce@moonlightdesign.org email me] for access)

Revision as of 15:58, 5 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. Partial functionality is presently planned for a pre-alpha version in mid-August.

Current stage: Notional architecture

Surveys

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. 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. Notional architecture
  6. Experiments
  7. Architectural review and refinement
  8. Module identification and assignment
  9. Integration test creation
  10. Detailed module designs
  11. Module unit tests
  12. Module code
  13. Integration tests passing
  14. Releases

Tips

Get emailed when pages of interest change: After creating a Thunderforce account, enter your email address and check "e-mail me when a page I'm watching is changed" into your preferences and click save, click on the email confirmation link in the message that the system sent to your inbox, and click on the "watch" tab on any page that you want to receive notifications from when the content changes.

Disambiguation

Thunderforce is not to be confused with the following:

Artifacts

Useful Development Links

People

Retrieved from "https://www.moonlightdesign.org/thunderforce/wiki/index.php?title=Main_Page&oldid=137"