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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Bass, L., Kazman, R.: Architecture based development. Technical Report CMU/SEI-2000-TR-007, SEI (April 1999)
Hofmeister, C., Kruchten, P., Nord, R., Obbink, H., Ran, A., America, P.: Generalizing a model of software architecture design from five industrial approaches. In: WICSA 2005. 5th Working IEEE/IFIP Conference on Software Architecture, Pittsburgh, Pennsylvania, pp. 77–86 (2005)
Bosch, J.: Software architecture: The next step. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds.) EWSA 2004. LNCS, vol. 3047, pp. 194–199. Springer, Heidelberg (2004)
Tyree, J., Akerman, A.: Architecture decisions: Demystifying architecture. IEEE Software 22(2), 19–27 (2005)
van der Ven, J.S., Jansen, A., Avgeriou, P., Hammer, D.K.: Using architectural decisions. In: Hofmeister, C., Crnkovic, I., Reussner, R. (eds.) QoSA 2006. LNCS, vol. 4214, Springer, Heidelberg (2006)
Abowd, G., Bass, L., Clements, P., Kazman, R., Northrop, L., Zaremski, A.: Recommended best industrial practice for software architecture evaluation. Technical Report CMU/SEI-96-TR-025, SEI (1997)
Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures. Addison-Wesley, Reading (2002)
Gilb, T.: Principles of Software Engineering Management. Addison-Wesley, Reading (1988)
CMMI Product Team: Capability maturity model integration (cmmi(sm). Technical report, SEI (2002) staged representation, version 1.1, CMU/SEI-2002-TR-012, ESC-TR-2002-012
Chrissis, M.B., Konrad, M., Shrum, S.: CMMI: Guidelines for Process Integration and Product Improvement. Addison-Wesley, Reading (2003)
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison-Wesley, Reading (2003)
Booch, G.: Observations from the road (May 2006), http://www-03.ibm.com/developerworks/blogs/page/gradybooch?entry=observation_from_the_road
US Department of Commerce: It architecture maturity model http://www.osec.doc.gov/cio/arch_cmm.htm
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2007 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Poort, E.R., Postema, H., Key, A., de With, P.H.N. (2007). The Influence of CMMI on Establishing an Architecting Process. In: Overhage, S., Szyperski, C.A., Reussner, R., Stafford, J.A. (eds) Software Architectures, Components, and Applications. QoSA 2007. Lecture Notes in Computer Science, vol 4880. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-77619-2_13
Download citation
DOI: https://doi.org/10.1007/978-3-540-77619-2_13
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-77617-8
Online ISBN: 978-3-540-77619-2
eBook Packages: Computer ScienceComputer Science (R0)