2. Outline
● Basis of Maturity Model
● Types of Open Source Maturity Models
● OSPI
● Shortcomings of existing models
● Proposed Model
● Inputs/comments
3. Basis of Maturity Model
Product Maturity
A product will be said to be mature if it has a full feature set, high quality,
longevity in market, has good support, exhibits robust behavior in error
situations.
Using a mature product means :
● Lesser downtime/failures
● Predictable results
● Low Maintenance Costs
● Higher Productivity
● Acts as a solid basis for more stable products
4. Types of Open Source Maturity
Models
There are four existing Open Source Product Maturity
Models:
● Open Source Maturity Model from Navica
● Qualification and Selection of Open Source Software
(QSOS) by Atos Origin
● OSMM Capgemini Model
● Open BRR by Spikesource
● Woods&Guliani(2005) Software Maturity Model
5. OPEN SOURCE SOFTWARE POTENTIAL INDEX (OSPI)
Red Hat and Georgia Tech published the results of a collaborative research project which
attempted to measure relative open source software adoption by countries and regions.
The statistics were used as the basis for formulating a global open source activity index.
Countries are ranked by overall activity and scores are also provided to indicate the level
of open source adoption in government and industry.
France (1.35)
Spain (1.07)
Germany (1.05)
Australia (1.04)
Finland (1.03)
United Kingdom (1.00)
Norway (0.95)
Estonia (0.89)
United States of America (0.89)
Denmark (0.79)
India ranked 23rd among a total of 75 countries.
6. Shortcomings of existing model
From enterprise point of view
● None of the model looks at enterprise capability
● Enterprise maturity in using open source software is not
considered
● Competencies in one open source project only serve a
small basis for usage of the next project
● All models consider if a OSS is mature then it serves as a
solid ground for using that OSS
● The existing models a good to make choice between
competing OSS products and not crafting the IT policy wrt
FOSS
