The influence of CMMI on establishing an architecting process

  • Authors:
  • Eltjo R. Poort;Herman Postema;Andrew Key;Peter H. N. de With

  • Affiliations:
  • LogicaCMG, Amstelveen, The Netherlands;LogicaCMG, Amstelveen, The Netherlands;LogicaCMG, London, United Kingdom;Eindhoven Univ. of Technol., Eindhoven, The Netherlands

  • Venue:
  • QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

A large IT company is creating a generic architecting process. Since the company has set an objective to achieve Maturity Level 3 of the Capability Maturity Model Integration (CMMI), the process needs to comply with the relevant requirements set by the CMMI. This paper presents the elicitation of such requirements, and the resulting set of requirements. It analyzes their potential impact on generic architecting processes found in literature. It turns out that many key architectural concepts are at best loosely defined in the CMMI. CMMI is strong in support of the development-related architecting activities, but gives only indirect support for other architecting activities, particularly in a product development context.