Welcome!

Linux Containers Authors: AppDynamics Blog, Liz McMillan, PagerDuty Blog, Tim Hinds, Kareen Kircher

Related Topics: Linux Containers

Linux Containers: Article

The OSS Development Life Cycle

Part 4 of 4

This is an excerpt from Chapter 6 of Understanding Open Source Software Development by Joseph Feller and Brian Fitzgerald, published by Addison-Wesley. ISBN 0201734966. No part of this excerpt may be reproduced, in any form or by any means without the prior written permission of the publisher. (c) 2002 Addison-Wesley

The traditional software development life cycle (SDLC) is premised on a set of stages, which, in their most generic form, include:

  • Planning
  • Analysis
  • Design
  • Implementation
However, the OSS development life cycle is quite different. First, the planning, analysis, and design phases are largely conducted by the initial project founder, and are not part of the general OSS development life cycle. Getting design issues right is perhaps even more critical in OSS than in conventional development. Certain criteria in relation to modularity of the code are critical. For example, modules must be loosely coupled, thereby allowing distributed development in the first place. Less important, but still highly desirable for achieving an efficient development model, is that modules be highly cohesive and address a single well-defined purpose. However, design decisions are generally made in advance, before the larger pool of developers start to contribute, and are generally based on well-established design patterns. This allows developers to collaborate without having to undergo the detailed requirements analysis or design phases of the traditional life cycle. In the absence of conventional project management, the importance of "having a tail-light to follow" (Bezroukov, 1999b) is a very useful coordinating principle, as it allows a multitude of developers to contribute. This also helps to explain why many OSS products are horizontal infrastructure-type products, as these are ones in which the requirements are pretty well understood. In vertical domains, developer knowledge of the application domain has been found to be critical, but it is unlikely that the pool of potential developers would be as high in such domains.

Thus, the OSS development life cycle is located primarily within the implementation phase of the traditional SDLC. Several researchers have investigated the life cycle underpinning OSS. Bollinger et al. (1999) suggest that it follows a very intensive spiral model (Boehm, 1988), albeit without any real risk assessment. Mockus et al. (2000) have derived a life cycle for OSS from their study of the Apache Project, and Jorgensen (2001) has investigated the life cycle in the FreeBSD Project. Both have come up with models that are largely compatible, but Jorgensen's is more detailed. He identifies the following main phases in the OSS development life cycle:

Code

  • Review
  • Pre-commit test
  • Development release
  • Parallel debugging
  • Production release

    Code
    This is the sine qua non activity. However, many potential OSS contributors may fear taking the initial step of submitting their code for review by the supremely talented OSS "code-gods" (Asklund and Bendix, 2001; Bergquist and Ljungberg, 2001), a fear that is quite warranted when you consider the views of a FreeBSD developer reported by Jorgensen (2001):

    The way you get commit privileges is by first making enough code contributions&This implies the code you've been submitting is of sufficiently impressive quality that no one objects and says, "Yuck, no, don't give him commit privileges. He writes ugly code."

    Thus, the knowledge that talented and respected peers will be reviewing the code is a real incentive to improve the quality of the code being submitted in the first place.

    Review
    As already mentioned, truly independent peer review is one of the central strengths of the OSS process. However, Jorgensen found that eliciting feedback was not always easy. "Heavyweights" with a proven reputation will get a lot of feedback, but it can be quite difficult to get attention as a newbie - another classic "Catch-22" situation. Also, somewhat paradoxically, the simpler the code, the more feedback you gets. However, complex code would invariably benefit more from feedback. Also, it's more difficult to get feedback on design issues.

    Precommit Test
    Given the vulnerability of the OSS development model, it's critical that committers test each contribution carefully to avoid breaking the build, another common norm in the OSS community. Since there is no convenient help-line or telephone support for those installing the eventual product, it can be an adventure completing an actual OSS product installation. Sanders (1998) quotes the "tech-savvy" Ellen Ullman's description of her installation of Linux as "an exhilarating succession of problem-solving challenges." Given this problematic installation context, it is imperative that installation proceeds as smoothly as possible without unnecessary noise, and thus rogue modules that could jeopardize this must be prevented.

    Interestingly, testing is very much a personal process. There is no requirement that test scenarios be rigorously planned and written down in advance. However, the negative implications of allowing a faulty contribution through are such that the testing process is taken very seriously indeed. As mentioned earlier, the delegation of testing to the user community - or partial delegation, as is the case with Mozilla and GNOME - is one of the strengths of OSS (Schmidt and Porter, 2001).

    Development Release
    If the committer deems the module ready, it can be incorporated in the development release. This is the key payoff for many developers as they get the reward of seeing their code implemented quickly in the product. Jorgensen (2001) cites a developer who captures it quite graphically:

    There is a tremendous satisfaction to the "see bug, fix bug, see bug fix get incorporated so that the fix helps others" cycle.

    Parallel Debugging
    The advantages of global parallel debugging were discussed above. Again, as in testing, there is typically no formal plan for debugging. Rather the numbers of potential debuggers is where the power of the debugging arises - Linus's Law. If bugs are found, they can be fixed and resubmitted as per the life cycle described above, or problem reports may be created and submitted. This can also be a way of initiating your contributions to OSS. For example, the database of outstanding problem reports could be examined, and if there are some outstanding that catch your interest or are within your capability, then these can be worked on. Thus, can you begin a career in OSS.

    Production Release
    Contributions eventually become part of the production release. They are merged into the stable production branch. This is accomplished in different ways in different projects. FreeBSD maintains stable production and current development branches, and contributions that are eventually found suitable are merged into the latest stable production branch, and, in the case of a bug fix, to any previous production branches to which it might be relevant. Linux maintains its stable production and development versions in different directories, and uses release numbers to identify production (even numbers) and development (odd numbers) versions.

    Conclusion
    We have argued that the generic OSS development process is characterized by the practice of parallel, rather than linear, collaboration among developers, which leads to increases in both speed and quality; by the participation of large, globally distributed communities of developers who participate in a truly independent peer review process; by prompt feedback (e.g., bug reports) and prompt recognition (e.g., integration of bug fixes); by the participation of talented and motivated developers and extremely active users; and by rapid, incremental release schedules. We also examined the well-stocked toolkit of OSS, including configuration management tools like CVS, as well as editors, build tools, documentation extractors, and the like. Finally, we argued that the OSS process is governed by an elaborate system of taboos and social mores that take the place of formal project management, and that the OSS process follows a distinctly different development life cycle to traditional proprietary software.

  • More Stories By Joseph Feller

    Joseph Feller is a lecturer with the Business Information Systems Group,
    University College Cork, Ireland. His research on Open Source Software is
    published in several prominent conference proceedings and he is the author
    of Customer Friendly: Design Guidelines for eCommerce. He also edits the
    monthly professional journal, Inside XML Solutions.

    More Stories By Brian Fitzgerald

    Brian Fitzgerald is the Frederick A Krehbiel II Professor of Innovation in Global Business and Technology at the University of Limerick, Ireland. He is Associate Editor for two leading international journals in the IS field, The Information Systems Journal, and Data Base. His publications include five books and more than 50 papers, published in leading international conferences and journals. Having worked in the industry prior to taking up an academic position, he has more than 20 years of experience in the IS field.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    @ThingsExpo Stories
    We’ve worked with dozens of early adopters across numerous industries and will debunk common misperceptions, which starts with understanding that many of the connected products we’ll use over the next 5 years are already products, they’re just not yet connected. With an IoT product, time-in-market provides much more essential feedback than ever before. Innovation comes from what you do with the data that the connected product provides in order to enhance the customer experience and optimize busi...
    Manufacturers are embracing the Industrial Internet the same way consumers are leveraging Fitbits – to improve overall health and wellness. Both can provide consistent measurement, visibility, and suggest performance improvements customized to help reach goals. Fitbit users can view real-time data and make adjustments to increase their activity. In his session at @ThingsExpo, Mark Bernardo Professional Services Leader, Americas, at GE Digital, will discuss how leveraging the Industrial Interne...
    The increasing popularity of the Internet of Things necessitates that our physical and cognitive relationship with wearable technology will change rapidly in the near future. This advent means logging has become a thing of the past. Before, it was on us to track our own data, but now that data is automatically available. What does this mean for mHealth and the "connected" body? In her session at @ThingsExpo, Lisa Calkins, CEO and co-founder of Amadeus Consulting, will discuss the impact of wea...
    Increasing IoT connectivity is forcing enterprises to find elegant solutions to organize and visualize all incoming data from these connected devices with re-configurable dashboard widgets to effectively allow rapid decision-making for everything from immediate actions in tactical situations to strategic analysis and reporting. In his session at 18th Cloud Expo, Shikhir Singh, Senior Developer Relations Manager at Sencha, will discuss how to create HTML5 dashboards that interact with IoT devic...
    Whether your IoT service is connecting cars, homes, appliances, wearable, cameras or other devices, one question hangs in the balance – how do you actually make money from this service? The ability to turn your IoT service into profit requires the ability to create a monetization strategy that is flexible, scalable and working for you in real-time. It must be a transparent, smoothly implemented strategy that all stakeholders – from customers to the board – will be able to understand and comprehe...
    Artificial Intelligence has the potential to massively disrupt IoT. In his session at 18th Cloud Expo, AJ Abdallat, CEO of Beyond AI, will discuss what the five main drivers are in Artificial Intelligence that could shape the future of the Internet of Things. AJ Abdallat is CEO of Beyond AI. He has over 20 years of management experience in the fields of artificial intelligence, sensors, instruments, devices and software for telecommunications, life sciences, environmental monitoring, process...
    The IoTs will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, will demonstrate how to move beyond today's coding paradigm and share the must-have mindsets for removing complexity from the development proc...
    A critical component of any IoT project is the back-end systems that capture data from remote IoT devices and structure it in a way to answer useful questions. Traditional data warehouse and analytical systems are mature technologies that can be used to handle large data sets, but they are not well suited to many IoT-scale products and the need for real-time insights. At Fuze, we have developed a backend platform as part of our mobility-oriented cloud service that uses Big Data-based approache...
    trust and privacy in their ecosystem. Assurance and protection of device identity, secure data encryption and authentication are the key security challenges organizations are trying to address when integrating IoT devices. This holds true for IoT applications in a wide range of industries, for example, healthcare, consumer devices, and manufacturing. In his session at @ThingsExpo, Lancen LaChance, vice president of product management, IoT solutions at GlobalSign, will teach IoT developers how t...
    Digital payments using wearable devices such as smart watches, fitness trackers, and payment wristbands are an increasing area of focus for industry participants, and consumer acceptance from early trials and deployments has encouraged some of the biggest names in technology and banking to continue their push to drive growth in this nascent market. Wearable payment systems may utilize near field communication (NFC), radio frequency identification (RFID), or quick response (QR) codes and barcodes...
    SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
    We're entering the post-smartphone era, where wearable gadgets from watches and fitness bands to glasses and health aids will power the next technological revolution. With mass adoption of wearable devices comes a new data ecosystem that must be protected. Wearables open new pathways that facilitate the tracking, sharing and storing of consumers’ personal health, location and daily activity data. Consumers have some idea of the data these devices capture, but most don’t realize how revealing and...
    The demand for organizations to expand their infrastructure to multiple IT environments like the cloud, on-premise, mobile, bring your own device (BYOD) and the Internet of Things (IoT) continues to grow. As this hybrid infrastructure increases, the challenge to monitor the security of these systems increases in volume and complexity. In his session at 18th Cloud Expo, Stephen Coty, Chief Security Evangelist at Alert Logic, will show how properly configured and managed security architecture can...
    There is an ever-growing explosion of new devices that are connected to the Internet using “cloud” solutions. This rapid growth is creating a massive new demand for efficient access to data. And it’s not just about connecting to that data anymore. This new demand is bringing new issues and challenges and it is important for companies to scale for the coming growth. And with that scaling comes the need for greater security, gathering and data analysis, storage, connectivity and, of course, the...
    The IETF draft standard for M2M certificates is a security solution specifically designed for the demanding needs of IoT/M2M applications. In his session at @ThingsExpo, Brian Romansky, VP of Strategic Technology at TrustPoint Innovation, will explain how M2M certificates can efficiently enable confidentiality, integrity, and authenticity on highly constrained devices.
    So, you bought into the current machine learning craze and went on to collect millions/billions of records from this promising new data source. Now, what do you do with them? Too often, the abundance of data quickly turns into an abundance of problems. How do you extract that "magic essence" from your data without falling into the common pitfalls? In her session at @ThingsExpo, Natalia Ponomareva, Software Engineer at Google, will provide tips on how to be successful in large scale machine lear...
    You think you know what’s in your data. But do you? Most organizations are now aware of the business intelligence represented by their data. Data science stands to take this to a level you never thought of – literally. The techniques of data science, when used with the capabilities of Big Data technologies, can make connections you had not yet imagined, helping you discover new insights and ask new questions of your data. In his session at @ThingsExpo, Sarbjit Sarkaria, data science team lead ...
    SYS-CON Events announced today that Ericsson has been named “Gold Sponsor” of SYS-CON's @ThingsExpo, which will take place on June 7-9, 2016, at the Javits Center in New York, New York. Ericsson is a world leader in the rapidly changing environment of communications technology – providing equipment, software and services to enable transformation through mobility. Some 40 percent of global mobile traffic runs through networks we have supplied. More than 1 billion subscribers around the world re...
    In his session at @ThingsExpo, Chris Klein, CEO and Co-founder of Rachio, will discuss next generation communities that are using IoT to create more sustainable, intelligent communities. One example is Sterling Ranch, a 10,000 home development that – with the help of Siemens – will integrate IoT technology into the community to provide residents with energy and water savings as well as intelligent security. Everything from stop lights to sprinkler systems to building infrastructures will run ef...
    You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.