|
|
|
|
| Intrinsic durability |
|
20 / 33 |
| Industrial solutions |
|
|
4 / 15 |
| Strategy |
|
|
5 / 9 |
|
|
|
|
|
|
|
|
|
|
Sheet: Possible label: Silver
Stats:
Mandatory 9 / 9,
Recommended 0 / 17,
Free 4 / 48
|
|
Assenssment: Possible label: Gold
Stats:
Durability: 20 / 33,
Industrial: 4 / 15,
Strategy: 5 / 9
|
|
|
|
|
|
Age
|
|
More than 3 years
|
|
Stability
|
|
Stabilized software. Releases provide mainly new functionalities, even if bug fixes are also provided
|
|
History, known problems
|
|
No known major problem or crisis
|
|
Popularity (at its scale)
|
|
Numerous users, numerous references
|
|
References
|
|
Often implemented for critical applications
|
|
Contributing community
|
|
Strong community: big activity on forums, numerous contributors and advocates
|
|
Books
|
|
Less than 3 books about the software are available
|
|
Developers identification and turnover
|
|
>7 developers, clearly identified, very stable team
|
|
Activity on bugs
|
|
Strong reactivity based on roles and tasks management
|
|
Activity on releases
|
|
Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forecast
|
|
Independence of developments
|
|
20% maximum
|
|
|
|
|
|
|
|
|
|
|
Training
|
|
No offer of training identified
|
|
Support
|
|
No offer of support except via public forums and mailing lists
|
|
Consulting
|
|
No offer of consulting service
|
|
Documentation
|
|
Documentation always up to date, translated and possibly adapted to different target readers (end user, sysadmin, manager, ?)
|
|
Tools
|
|
Very active use of tools for roles/tasks allocation and progress monitoring
|
|
|
|
|
|
|
|
|
|
|
Roadmap
|
|
Existing roadmap without planning
|
|
Sponsorship
|
|
|
|
Strategic independence
|
|
Strong independence of the core team, legal entity holding rights, strong involvement in the standardization process
|
|
|
|
|
|
|
