This talk presents OW2's efforts, experience, vision and methodology to assess the market readiness of open source software. If ''open source software has won'' it remains that many conventional managers are not comfortable with it : rating open source market readiness can be a powerful tool to help decision makers.
This presentation will cover:
- the value chain of open source software;
- the OW2 Open-source Sofware Capability Assessment Radar (OSCAR) platform;
- the first version of OW2 OSS Market Readiness Level (MRL, derived from NASA's TRL or Technology Readiness Levels).
12. Mar 16, 2017 122017, Cedric Thomas
Agenda OSS Projects and the Value Chain
Evaluating Readiness and Maturity
Evaluating Open Source Projects
OW2 OSCAR Approach
13. Mar 16, 2017 132017, Cedric Thomas
Project categories
Code to product
Supporting market readiness
OSS projects and
the value chain
14. Mar 16, 2017 142017, Cedric Thomas
Community projects
15. Mar 16, 2017 152017, Cedric Thomas
Enterprise projects
16. Mar 16, 2017 162017, Cedric Thomas
Collaborative projects
17. Mar 16, 2017 172017, Cedric Thomas
Software is Code
18. Mar 16, 2017 182017, Cedric Thomas
What is a Software Product?
Developer Customer
19. Mar 16, 2017 192017, Cedric Thomas
What makes a Software Product?
Developer Customer
Documentation
Testing
Upgrades Training Etc.
Pricing Contracts Support Expertise
Packaging
20. 202017, Cedric Thomas
Research &
Development
Code
POCs
Use-cases
Demonstrators
Documentation
Testing
Upgrades
Bug-fixing
Training
Support
Packaging
Casestudies
Collateral
Pricing
Contracts
Earlyadopters
Etc.
Predictability
Quality
Trust
Without the code, the rest does not exist,but it's the rest that gives market value to the code
Delivery
Challenge
What creates value?
Market Value
OSS
21. 212017, Cedric Thomas
Research &
Development
Code
POCs
Use-cases
Demonstrators
Documentation
Roadmap
Upgrades
Bug-fixing
Training
Support
Packaging
Casestudies
Collateral
Pricing
Contracts
Earlyadopters
Etc.
Predictability
Quality
Trust
Delivery
Challenge
Market Value
Who creates value?
The ecosystem
Contributors
Distrib. Vendors
Open Source Orgs.
Fiduciary Services Users
Systems Integrators
22. 222017, Cedric Thomas
Research &
Development
Code
POCs
Use-cases
Demonstrators
Documentation
Roadmap
Upgrades
Bug-fixing
Training
Support
Packaging
Casestudies
Collateral
Pricing
Contracts
Earlyadopters
Etc.
Predictability
Quality
Trust
OW2 is an ecosystem platform that helps create value in open source projects
Delivery
ChallengeCollaborative Development Technical Resources
Governance, Projects, Initiatives, Quality Program
Communication, Outreach, Marketplace
OSCAR
Market Value
Supporting market readiness
and value creation
24. 242017, Cedric Thomas
Origin: Technology
Readiness Level (TRL)
A type of measurement system
used to estimate the maturity level of
a particular technology
In technology, there are usually
nine readiness levels. TRL 1 is the
lowest and TRL 9 is the highest.
A TRL number is obtained once the
description has been achieved.
For example, successfully
achieving TRL 4 does not move the
technology to TRL 5.
Pioneered by NASA in the 80’s.
Adopted by the DOE and DOD for
procurement and management of
complex systems.
Idea
(useless)
Operational
(useful)
29. 292017, Cedric Thomas
OSS Analysis LandscapeEUCollab.ProjectsIndustryStandardization
bodies
IPanalysisStaticanalysisQualitative
analysis
OW2 OMM forms
Engineering
metrics
CI/
Testing
Crowd testing
30. 302017, Cedric Thomas
2007: QualiPSo European project
48 months (2007-2010)
22 organisations from 9 countries
(3 continents)
It is all about TRUST
Trust cannot be claimed without
being proved!!!
QualiPSo aimed at standardising
the way OSS systems are built,
offered and consumed.
32. 322017, Cedric Thomas
2010: OW2 Software
Quality Assurance and
Trustworthiness
(SQuAT)
IP verification: FOSSology
Applied on all OW2 mature
projects
Code verification: Antelink
Provides traceability of external
libraries
Static analysis: Sonar
Set of OW2 Sonar rules
Maturity analysis: Qualipso
OMM applied to OW2 projects
34. 342017, Cedric Thomas
2012: RISCOSS
Commercial
Products/Services
???
Antepedia
Business Users Integrators
Open source as a public
resource freely accessible
But OSS come from very
different backgrounds
Exploring and mapping the
open source landscape
Need to identify, measure,
evaluate existing software
Many tools and online
services available
35. 352017, Cedric Thomas
2015: Linux Foundation
CII Badge Program
Core Infrastructure Initiative (CII)
Launched after the Heartbleed
failure
Organized by The Linux Foundation
Supported by Amazon Web
Services, Adobe, Bloomberg, Cisco,
Dell, Facebook, Fujitsu, Google,
Hitachi, HP, Huawei, IBM, Intel,
Microsoft, NetApp, NEC, Qualcomm,
RackSpace, salesforce.com, and
VMware
https://www.coreinfrastructure.org/
David A. Wheeler at OW2con'16
36. 362017, Cedric Thomas
CII BADGE PROGRAM Checklist:
Basics Project website
Project website content
FLOSS License
Documentation
Other
Change control Public version-controlled source repository
Version numbering
Release notes (ChangeLog)
Reporting Bug reporting process
Vulnerability reporting process
Quality Working build system
Automated test suite
New functionality testing
Warning flags
Security Secure development knowledge
Good cryptographic practices
Secured delivery mechanism
Publicly-known vulnerabilities fixed
Analysis Static code analysis
Dynamic analysis
45. Mar 16, 2017 452017, Cedric Thomas
OSCAR
Market Readiness
Scorecard
46. 462017, Cedric Thomas
From Data to Market
Readiness Levels
A type of measurement system
used to estimate the market maturity
and readiness of a particular project
Rough Code
(useless)
Fully Supported Product
(useful)
47. 472017, Cedric Thomas
A Market Readiness Template
for Open Source Software
“flight proven”
“flight qualified”
“prototype in space”
“proven demo”
“relevant envt validation”
“Lab validation”
“proof of concept”
“application formulation”
“Basic principles”
Established product with properly financed and organized Business
support Customer base, Repeat sales and Market recognition
Early customer base, appropriate financing or active community
support, recognized software
Early customer base and fledgeling financing or active community
support
Proven product recent, market opening, untested governance
Some customers recent, market opening, un-proven governance
Several users, project leadership well established
One declared user (can be internal) with declared project leader
Basic R&D code developed with one demonstrated use case, some
documentation
Basic R&D code developed
48. 48
www.ow2.org
For more details please contact Cedric Thomas, OW2 CEO, cedric.thomas@ow2.org
And now let's talk
Q&A
Disagreements
Complements
Feedback
etc.
Thank You