Software Engineering Paradigms Quiz

Course Information

• Course Code: SWEG5109
• Target Group: 5th Year Software Engineering
• Instructor: Biniam Behailu
• Date: Oct, 2024

Chapter 1: Introduction to Open Source Software Engineering

• Outline:
  • Open source paradigm
  • Open Source Software in Practice
  • Benefits of Open Source
  • Economics of Open Source
  • Open Source Business Models
  • Open-Source Software Criteria

Introduction

• Software engineering is a systematic approach for designing, developing, testing, and maintaining software products.
• Its aim is to create high-quality software applications, achieving optimal quality, budget, and time efficiency.
• Software follows consistent, correct requirements within the budget and time constraints.

Introduction (Continued)

• Software engineering paradigms establish fundamental principles, methodologies, and practices for developing high-quality software systems.
• These paradigms shape how programmers approach problems, structure their solutions, and organize code.
• Examples of paradigms (Procedural, OOP, Functional, Agile, DevOps, SaaS) have impacted the development of software engineering (SWEng).

Introduction (Continued)

• Selecting the right paradigm is crucial and influences how developers design, write, and maintain software.
• Key factors for selecting a paradigm include problem domain, complexity, performance, and developer familiarity
• Code readability, maintainability, and program structure are impacted by the chosen paradigm.

What is Open Source Software?

• Open source software (OSS) is software released with a license allowing anyone to view, modify, and distribute the source code.
• This model fosters collaboration and transparency, permitting global developer participation in projects.
• The open-source movement radically improved software development innovations while reducing costs.

What is Open Source Software? (Continued)

• Open source represents a novel approach to intellectual property management.
• Code transparency allows anyone to inspect the code.
• Collaboration enables community-driven development
• Open-source licenses govern the software (eg. MIT, GPL)
• Open source is centered around access, customization, finding and fixing bugs, and sharing modifications.

What is Open Source Software? (Continued)

• Open-source software is not just a concept; it fundamentally empowers the Internet.
• A significant percentage of websites (60%) rely on popular open-source web servers like Apache and Nginx.
• Even large Fortune 500 companies frequently integrate open-source software, particularly Nginx.

History of Open Source

• Early Days of Computing (1950s-1970s): The Free Software Movement emerged, advocating for software freedom, allowing users to modify and redistribute software.
• The Birth of Free Software (1983): Richard Stallman's GNU Project aimed to build a free Unix-like operating system.
• The concept of copyleft was introduced, ensuring free use and modification while maintaining the open nature of derivative works.
• The Free Software Foundation (FSF) promoted the development and use of free software, including the GNU operating system and the GNU General Public License (GPL).

History of Open Source (Continued)

• The Open Source Initiative (1998): The term "Open Source" was popularized to attract businesses and mainstream developers.
• The Open Source Initiative (OSI) was established to promote and certify open-source software licenses.
• Netscape Navigator's source code release in 1998 was pivotal, influencing the formation of the Mozilla project.
• The Cathedral and Bazaar model (1998) defines centralized planning and rapid releases respectively.

History of Open Source (Continued)

• Growth and Adoption (2000s): Linux, developed by Linus Torvalds in 1991, achieved widespread adoption in servers and desktops.
• The Apache HTTP Server became a widely adopted and prominent web server, highlighting open source's viability across different sectors.
• Corporate Involvement (2000s-Present): Major technology companies began incorporating open-source software into their initiatives.
• The rise of cloud computing fostered increased interest in open source solutions like OpenStack and Kubernetes.

Community and Collaboration

• Git and GitHub (2000s): Introduced version control, facilitating easier collaboration on open-source projects.
• Projects diverse and transcend operating systems, encompassing applications, libraries, and frameworks (eg Python, Ruby on Rails).

Current Trends and Future (2020s)

• Continued Growth: Open-source software thrives due to a strong, community-driven model.
• Focus on Security: Concerns surrounding open-source security and sustainability have spurred significant efforts towards ensuring open-source project security and upkeep.

Open Source Software Advancements

• Linux released to the public, including the source code (1991).
• Publication of the Python interpreter source code (1991).
• Introduction of the Apache HTTP Server (1995) and the term "open source" (1998)
• Netscape source code release (1998) and creation of the Open Office software, a free counterpart to Microsoft Office (2000).
• The 20th century laid a strong foundation for open-source software (OSS).

Characteristics of Open Source

• Accessibility of Source Code: Open access and modification for anyone and redistribution.
• Freedom of modification: Modification according to needs.
• Community Collaboration.
• Transparency: Enhanced scrutiny because of its open nature.
• Licensing; Complying with open-source licenses (GPL, MIT).
• Vendor lock-in-avoidance: Increased flexibility in use and support choices.
• Continuous improvement: Active community engagement fosters further enhancements.
• Flexibility in use and support.

Criteria to Choose Open Source Software

• Does the software offer the needed functions (Features)?
• Will the software accommodate project growth (Scalability)?
• How secure is the software (Security)?
• Is the software actively maintained by a community, regular updates, and bug fixes are essential.
• Is there an active user community where assistance and answers are provided (Community Support)?
• Does the software have straightforward, extensive documentation (Documentation)?
• Does your team have the necessary skills to use and maintain the software (Skills)?
• Review software licenses to understand rules and conditions (License).
• Popular open-source software typically has a larger community and resources (Popularity).

Open Source Contributions Types

• Code contributions (Bug Fixes, Feature Development, Refactoring).
• Documentation (User Manuals, API Documentation, Contribution Guidelines).
• Testing (Unit Testing, Bug Reporting, Quality assurance)
• Design (User Interface, Graphic Design).
• Translation and Localization.
• Community Engagement (Support, Mentorship).
• Project Management (Maintaining Issues, Release Management).
• Advocacy and Promotion (Blogging and writing, Speaking Engagements).

Open Source Programs and Projects

• Provide various links for open-source projects in areas such as web development, cloud computing, and machine learning.

Economics of Open Source Software

• Cost Structure: Free to use, reduce cost and barriers to entry (e.g., for startups).
• Support Costs: Organizations often need support, maintenance, and training, even if the original software is free.
• Business Models: Freemium model, dual licensing, consulting, subscription, support maintenance, crowdfunding, and sponsorship.
• Value Creation: Community contributions, network effects.
• Market Dynamics: OSS competes with proprietary software, driving quality and innovation.
• Vendor lock-in avoidance; increased flexibility and cost benefits for businesses.
• Investment and Funding: Crowdfunding, donations, sponsorship.
• Economic Impact: Job creation and boosting innovation.
• Challenges and Risks: Sustainability concerns, quality assurance, and potential issues in long-term viability.

Business Models of Open Source Software

• Freemium Model
• Dual Licensing
• Subscription Model
• Consulting and Services
• Support and Maintenance
• Crowdfunding and Donations
• Sponsorship and Grants
• Open Core Model
• Marketplace Model

Open Source Criteria summary

• Open source license
• Availability of source code - Publicly accessible
• Freedom to Modify
• Sharing/ Redistribution
• Comprehensive documentation
• Code quality,
• Regular updates
• Security audits
• Compatibility and Interoperability
• Support channels

Why use Open Source?

• User Perspective: Cost reduction, enhanced security and flexibility, broader choices and innovations, and community support.
• Developer Perspective: Increased user community, collaboration, accelerated feedback loops, skill development, improved software, improved transparency.