Open Source Software For Successful Systems

Open Source Software
1.0x

Open Source Software For Successful Systems

Created 2 years ago

Duration 0:21:01
lesson view count 6
Select the file type you wish to download
Slide Content
  1. Open Source Software For Successful Systems

    Slide 1 - Open Source Software For Successful Systems

    • YALAVARTHI ANUSHA
  2. CONTENTS:

    Slide 2 - CONTENTS:

    • INTRODUCTION
    • TRADITIONAL APPROACH
    • CLOSED SOURCE
    • FREE/ LIBRE OPEN SOURCE SOFTWARE
    • OSS FOR SUCCESSFUL SYSTEMS
    • BENEFITS
    • OPPORTUNITIES
    • CONCLUSION
  3. INTRODUCTION:

    Slide 3 - INTRODUCTION:

    • Open source has recently attracted significant interest from the IT community.
    • Open-source software development is the process by which open-source software whose source code is publicly available and is developed.
    • These are software products made available with its source code under an open-source license to study, change, and improve its design.
    • Open source remains highly suited, both as a software product and as a development methodology. However, no standard development lifecycle exists.
    • There has subsequently been a lot of enthusiasm for utilizing Open Source Software with reasons given as expense cutting and expertise improvement, amongst others
    • It has been recognized that the open collaborative development among software developers from all over the world is a significant factor to the success of OSS projects.
    • One key advantage of open source software is its assumed high quality due partly to the intensive peer review.
  4. TRADITIONAL APPROACH:

    Slide 4 - TRADITIONAL APPROACH:

    • Traditional approach is the oldest type of software development.
    • In traditional approach, the main objective was based on software development towards limited number of users.
    • The projects were inclined towards long term life expectancy which are built in cost and time limit environment.
    • In this approach, the programming steps inclined towards working with past time organizational methodologies like pyramid or church flow developmental organization.
    • Such software's developed are small volume or low end user focused which manually analyzes and coding, debugging on the small loops will be extremely expensive and time consuming.
    • A program developed need to be tested in all means at unit level and user level and an extra part focus to be applied to coupe up with expected efficiency.
  5. CLOSED SOFTWARE:

    Slide 5 - CLOSED SOFTWARE:

    • Another type of software is Closed software.
    • In closed software, the source code is not shared with the public for anyone to look at or make changes to closed source.
    • It is the inverse of open source.
    • When purchasing the software, you will get more than the needed. You will get the warranty and the document stating that the product will work correctly.
    • If there is some problem with it, then one can take legal action against the provider. Any software provider will provide some degree of support/ assistance.
    • As the closed source organizations are the main associations with the rights to manufacture and add to their items, there are a little number of adaptations of normally utilized programming, particularly in light of the quantity of PCs being used today.
    • This implies that the twisted authors of infections can abuse PCs by the thousands, harming whole systems.
  6. FREE/ LIBRE OPEN SOURCE SOFTWARE(FLOSS):

    Slide 6 - FREE/ LIBRE OPEN SOURCE SOFTWARE(FLOSS):

    • Free/ Libre Open source software came in to existence to overcome the issues faced in distributed employment in which diving the work among a group of people takes place.
    • Free/ Libre Open source software is a software developed and released under an open source license.
    • Open Source Software users do pay nothing as there are no copyrights and anyone can use it.
    • code is available for remote access, open to study and modification, and available for redistribution to other with few constraints
    • FLOSS developers are typically also end-users of the FLOSS they develop, and other end-users often participate in and contribute to FLOSS development efforts.
    • FLOSS allows modification, inspection and redistribution.
  7. OPEN SOURCE SOFTWARE FOR SUCCESSFUL SYSTEMS:

    Slide 7 - OPEN SOURCE SOFTWARE FOR SUCCESSFUL SYSTEMS:

    • OSS for successful system should have the following:
    • Individual Participation
    • Resources and capabilities supporting OSS
    • Cooperation, coordination and control
  8. INDIVIDUAL PARTICIPATION IN OSS:

    Slide 8 - INDIVIDUAL PARTICIPATION IN OSS:

    • One of the most common questions about OSSD projects to date is why the software developers join and participate in such efforts, often without pay for sustained periods of time?
    • Many FLOSS developers participate in and contribute to multiple FLOSS development projects, possibly in different roles.
    • , participants in FLOSS projects engage in online discussion forums or threaded email messages as a central way to observe, participate in, and contribute to public discussions of topics of interest to ongoing project participants.
  9. RESOURCES AND CAPABILITIES:

    Slide 9 - RESOURCES AND CAPABILITIES:

    • What kinds of resources or development capabilities are needed to help make OSS efforts more likely to succeed?
    • Software development resources
    • Beliefs supporting OSS
    • OSS development informalisms
    • Skilled, Managing and self organizing OSS developers
    • Time and efforts of developer
    • Trust and social accountability
  10. COOPERATION, CO-ORDINATION AND CONTROL IN OPEN-SOURCE SOFTWARE:

    Slide 10 - COOPERATION, CO-ORDINATION AND CONTROL IN OPEN-SOURCE SOFTWARE:

    • Software version control, as part of a software configuration management activity, is a recurring situation that requires coordination but enables stabilization and synchronization of dispersed and somewhat invisible development work.
    • Tools like CVS, Subversion, Git, and others are being used in FOSS projects as both
    • A centralized mechanism for coordinating and synchronizing FOSS development, as well as
    • An online venue for mediating control over what software enhancements, extensions, or architectural revisions will be checked-in and made available for check-out throughout the decentralized project as part of the publicly released version.
  11. In a FOSSD projects, software development work appears to be logically centralized, while being physically distributed in an autonomous and decentralized manner.

    Slide 11 - In a FOSSD projects, software development work appears to be logically centralized, while being physically distributed in an autonomous and decentralized manner.

    • FOSSD efforts rely on mechanisms and conditions for gentle but sufficient social control that helps constrain the overall complexity of the project.
  12. BENEFITS OF OPEN SOURCE SOFTWARE:

    Slide 12 - BENEFITS OF OPEN SOURCE SOFTWARE:

    • As the software is free to use, it has many benefits.
    • Reliability
    • Stability
    • Auditability
    • Cost
    • Flexibility and Freedom
    • Support and Accountability
  13. Reliability:

    Slide 13 - Reliability:

    • The software is reliable. If bugs are found, they can be altered by the trusted power and then reported. This system lives up to expectations.
    • Stability:
    • The trade configurations are especially stable in Open source software which cannot be changed when needed.
    • Auditability:
    • By distributing the source code, creators make it workable for clients of the product to have.
    • Cost:
    • Open Source tasks are accessible free of charges, prompting the perplexity around the usually utilized term ‘free programming’
  14. Flexibility and Freedom:

    Slide 14 - Flexibility and Freedom:

    • Freedom is provided in open source through flexibility.
    • It is freedom from a vendor and freedom to modify the software.
    • Support and Accountability:
    • Open-source licenses normally disclaim all liabilities and guarantees, including such essential guarantees as merchantability and wellness for reason.
    • Open-source specialists will give preparing and/or backing for programming they suggest.
    • Since the source code is unreservedly accessible, associations are not restricted to getting backing from the developers.
  15. OPPORTUNITIES OF OSS:

    Slide 15 - OPPORTUNITIES OF OSS:

    • OSS poses the opportunity to favorably alter the costs and constraints of accessing, analyzing, and sharing software process and product data, metrics, and data collection instruments.
    • Motivation, participation, role migration, and turnover of individual OSS developers would benefit the SE community.
    • In social networking, community development, and multi-project software ecosystems, it appears that OSSD projects are leading.
    • The cost estimation or accounting techniques are limited to analyzing resources or capabilities that are easily quantified.
  16. CONCLUSION:

    Slide 16 - CONCLUSION:

    • OSSD combines features found in traditional software processes with other features in a unique way that can potentially produce high-quality software, faster and cheaper within the rapidly changing Internet environment.
    • Although OSSD is not a faultless solution, it provides potential benefits and opportunities to the system development process
    • Free and open source software development is emerging as an alternative approach for how to develop large software systems.
    • OSSD projects and project artifact repositories contain process data and product artifacts that can be collected, analyzed, shared, and be re-analyzed in a free and open source manner.
  17. Slide 17

    • Thank You !!