Klaus Marquardt
ABSTRACT
Software developers rightfully focus on the activities needed to polish the software for its first release. The management of future releases, version identification, compatibility checks, and update strategies are typically treated as an afterthought, but insufficiencies or inconsistencies here have all the potential to make your life miserable once the software has hit the market.
These patterns cover practices to identify a particular version, policies to determine version compatibility, and release update strategies. They aim to make the versioning issues explicit, prepare the project for the foreseeable, and help decide what amount of thought to spend. They target the project participants responsible for releases: release manager, project leader, software architect, and product manager.
- Bercuk, S. 2002. Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Addison-Wesley, Reading, MA, 2002 Google Scholar
Digital Library
- Hohmann, L. 2003. Beyond Software Arcitecture: Creating and Sustaining Winning Solutions. Addison-Wesley, Reading, MA, 2003 Google ScholarDigital Library
- Kelly, A. 2012. Business Patterns for Software Developers. John Wiley & Sons, 2012 (under review)Google Scholar
- Marquardt, K. 2006. Patterns for Software Release Versioning. In Zdun, U. and Hvatum, L. (eds.) Proceedings of the 11th European Conference on Pattern Languages of Programs (EuroPLoP 2006). UVK, Konstanz, Germany 2007Google Scholar
- Rüping, A. 2010. From Old to New -- Patterns for Data Migration. In Proceedings of the 15th European Conference on Pattern Languages of Programs (EuroPLoP 2010), ACM, New York, NY, 978-1-4503-0259-3Google Scholar
- Salecker, J. and Schütz, D. 2004. Bill of Material. In Marquardt, K. and Schütz, D. (eds.) Proceedings of the 9th European Conference on Pattern Languages of Programs (EuroPLoP 2004). UVK, Konstanz, Germany 2005Google Scholar
Index Terms
- Patterns for software release versioning
Recommendations
Versions, releases, and distribution
OOPSLA '07: Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companionDuring the core development phases, managers and software developers rightfully focus on the activities needed to complete the software's first release. They strive to minimize the project risk and to keep the schedule.
The management of future releases,...
Versioning in cyber-physical production system engineering: best-practice and research agenda
SEsCPS '15: Proceedings of the First International Workshop on Software Engineering for Smart Cyber-Physical SystemsThe parallel engineering of cyber-physical production systems (CPPSs), an important type of sCPS, needs the collaboration of several engineering disciplines, which use a wide range of heterogeneous tools and data sources. Systems engineers and process ...
Software release management for component-based software
Software release management is the process through which software is made available to and obtained by its users. Until now, this process has been relatively straightforward. However, the emergence of component-based software is complicating software ...
Comments