Quality attributes

Quality attributes and their drivers appear on this page. These are also known as "non-functional requirements" in some circles.

Portability

• Should Thunderforce support Thunderbird 1.5 and 2.0 or just 2.0?
• If possible, Thunderforce should use only JavaScript code for maximum portability between the platforms that Thunderbird supports
  • If needed, Java code can be used, but that may decrease the portability to only those platforms that support Java
  • C++ should not be used unless if deemed as absolutely necessary. Using native code greatly increases the cost of portability and maintaining releases

Security

• Should authentication information be stored in the Thunderbird configuration if the user requests, or only when a master password is being used to encrypt the Thunderbird password database?

Usability

• Should Salesforce authentication information be stored in the Thunderbird configuration? That can increase ease of use at the expense of security, though it should be possible to cache this information when a master password is being used to encrypt the database
• User interface screens should be vetted by the community and, if possible, usability experts to get feedback on ease-of-use

Performance

• Any specific performance attributes? These may include performance characteristics against very large organizations (VLOs)

Any others?

• Please feel free to add more :-)!