ER 2 C SDMLC: e nterprise r elease r isk- c entric s ystems d evelopment and m aintenance l ife c ycle

  • PDF / 948,019 Bytes
  • 33 Pages / 439.37 x 666.142 pts Page_size
  • 62 Downloads / 170 Views

DOWNLOAD

REPORT


ER2C SDMLC: enterprise release risk-centric systems development and maintenance life cycle Hamish Sadler 1 # Springer Science+Business Media, LLC, part of Springer Nature 2019

Abstract Traditional systems development life cycle models can be viewed as technical life cycle models in systems development projects. These life cycle models mostly focus on the initial delivery of systems as part of projects. However, many systems end up in a perpetual development mode and can be viewed as a continuum of releases rather than the deliverables of temporary projects. Newer versions of such systems are usually released as part of support/ maintenance processes rather than through rigorous projects. In environments with quick-fix maintenance or loose release management regimes, lack of rigor may result in the compromise of quality, especially quality-in-use. This may cause end users’ exposure to risks as a result of using potentially faulty releases and products. Minimizing product risks should be an inherent inclusion in product life cycle, regardless of whether the product is released as part of a project or as part of support/maintenance work. A novel systems development and maintenance life cycle model is proposed that models the life of a system as a sequence of releases. It covers non-project maintenance-related releases as well as major projectized releases under a unified consistent governance model. It proposes applying different levels of rigor depending on analyzed release risks via the enforcement of different thresholds to a set of metrics that are extracted from release artifacts. The proposed life cycle model supports iterative development and is conformant to ISO 15288:2015. Evaluations performed by a community of practice in a large government agency in Queensland, Australia, has demonstrated the success of the proposed model in a number of areas, especially in how risk is managed when changes are introduced to systems after their initial release. Keywords Release risk . Systems development life cycle . Quality-in-use . Freedom from risk . Software quality management . Metric-centric development

* Hamish Sadler [email protected]

1

Queensland University of Technology (QUT), Brisbane, Australia

Software Quality Journal

1 Introduction SO 15288: 2015 defines a life cycle model as “the framework of processes and activities concerned with a life cycle which may be organized into stages and can also act as a common reference for communication and understanding” (ISO/IEC 2015). Systems development life cycle models could also be considered as technical life cycle models in systems development projects (Dalcher 2002). The International Standard ISO 21500: 2012-Guidance on Project Management defines a project as “a unique set of processes consisting of coordinated and controlled activities with start and finish dates, undertaken to achieve an objective” (ISO/IEC 2012) which implies the temporary nature of projects. There are a number of software and systems development life cycle models used in dif