From Proprietary to Open Source Transition - PowerPoint PPT Presentation

1 / 9
About This Presentation
Title:

From Proprietary to Open Source Transition

Description:

Open source contributions RedHat's usage of packages. Software Development ... Open source is usually built around new instead of stable. Requirements for Transition ... – PowerPoint PPT presentation

Number of Views:226
Avg rating:3.0/5.0
Slides: 10
Provided by: l266140
Category:

less

Transcript and Presenter's Notes

Title: From Proprietary to Open Source Transition


1
From Proprietary to Open Source Transition
  • By Benjamin Arai
  • barai_at_cs.ucr.edu
  • University of California, Riverside
  • Computer Science CS245, Software Evolution

2
Abstract
  • Status quo of software development
  • Software development
  • TCO total cost of ownership
  • Shift of development
  • Requirements for transition
  • Phases of transition
  • Transition feasibility

3
Status Quo of Software Development
  • Proprietary software
  • Consumer driven
  • Clear commercial model
  • Open source software (Movement)
  • Consumer developer driven
  • Unclear goals
  • Stability of the status quo
  • Long-term profits
  • Short-term profits
  • Dependencies
  • Commercial funding of open source MS Perl IBM
    100 million
  • Open source contributions RedHats usage of
    packages

4
Software Development
  • Open source development
  • Cathedral and the Bazaar
  • Open community encourages new ideas
  • Lack of reliable labor and resources
  • Commercial development
  • Slower to innovate
  • Consumer driven development
  • Meeting world expectations
  • Roles of software development
  • Niche software development Open source
  • Profit driven Proprietary
  • Consumer education (TCO)

5
TCO Total Cost of Ownership
  • Direct cost of ownership
  • Usability (Easy of use)
  • Initial product cost
  • Indirect cost of ownership
  • Maintenance
  • Support
  • Balancing direct and indirect costs
  • Lowering cost of total ownership

6
Shift of Development Model
  • Retraining
  • Re-introduction of new software
  • Bugs
  • Reliability
  • Stability
  • Integration with other Software Suites
  • Software Scalability
  • Meet requirements of previous software
  • Open source development doesnt always scale
  • Open source is usually built around new instead
    of stable

7
Requirements for Transition
  • Compatibility
  • Software compatibility
  • Hardware compatibility
  • Consumer acceptance
  • Interface
  • Workflow
  • Bugs
  • Open source community acceptance
  • Continual support for open development

8
Transitioning from a Closed to Open Source Model
  • Pre-Transition
  • Requirements gathering
  • Consumers
  • Developers
  • Transition
  • Development compatibility
  • Consumer compatibility
  • Post-Transition
  • Long-term integration

9
Is transition possible?
Write a Comment
User Comments (0)
About PowerShow.com