Main Page

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

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

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.

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. 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

Artifacts

• Subversion repository
  • Read-write access can be requested by emailing Steven Lawrance
• Shared documents
  • Read-write access can be requested by emailing Steven Lawrance
• Releases (coming later)

People

• Project Lead: Steven Lawrance
• Architects
  • Steven Lawrance
• Developers
  • Steven Lawrance
• Quality Assurance
  • Steven Lawrance
• Development Support
  • Steven Lawrance
• Graphics
  • New logo being designed by a fabulous friend from CMU
• Language Translators
• End-User Documentation
• End-User Testing
• Please let me know which role(s) you want to help out with. With your help, Thunderforce can ship sooner rather than later :-)

Useful Development Links

• Salesforce.com API 9.0 (entity-relationship diagrams (ERDs))
• Mozilla platform documentation
• SQLite documentation

Disambiguation

Thunderforce is not to be confused with the following:

• Thunder Force video game
• ThunderForce heavy metal band (requires JavaScript)