Business Architecture Development and Process and Project Maturity

  • Igor V. IlinEmail author
  • Anastasia I. Lyovina
  • Anton R. Antipin
Part of the Progress in IS book series (PROIS)



Business architecture is the basis for the development and implementation of information systems. In turn the basis for business architecture are business processes and project portfolio. The article is aimed at the development of theoretical foundation of business architecture design on the basis of such business technologies as business process management and the corporate standard of project management.


The article analyses the place and role of business processes and projects within the enterprise architecture as well as the interdependence between maturity levels of process and project management in order to develop the approach to the design of the balanced business architecture of a process and project oriented company.


Maturity of project management depends on the maturity of process management. In turn, the maturity of process management is determined by the capabilities of the company to implement projects for the re-engineering of business processes. Development of project and process activity of the company is a mutually conditioned process.

Research limitations/implications

In their research of the mutual conditionality of maturity of the project and process management, the authors have to rely largely on their research experience, because the process and project management maturity in the literature are reviewed separately.


The paper’s findings extend current knowledge. Its results provide guidance for scholars and practitioners involved in the design and implementation of enterprise architecture.

Paper type

Research paper


Enterprise architecture Business architecture Process Project Maturity 


  1. 1.
    Lankhorst, M. (2013). Enterprise architecture at work. Modelling, communication, analysis. Berlin: Springer.CrossRefGoogle Scholar
  2. 2.
    CIO Council. (2014, January 25). Federal enterprise architecture framework version 1.1 September 1999. Retrieved from Institute for Enterprise Architecture Development:
  3. 3.
    Kalyanov, G. (2014 January 25). Enterprise architecture and instruments of its modeling. Retrieved from National Institute Higher School of Management :
  4. 4.
    Group, T. O. (2009). TOGAF version 9. The open group architecture framework (TOGAF). London: TSO.Google Scholar
  5. 5.
    Becker, J., Kugeler, M., & Rosenmann, M. (2011). Process management. Berlin: Springer.CrossRefGoogle Scholar
  6. 6.
    Repin, V. (2013). Business-processes. Modeling, implementation, management. Moscow: Mann, Ivanov and Ferber.Google Scholar
  7. 7.
    OGC. (2009). Managing successful projects with PRINCE2. London: TSO.Google Scholar
  8. 8.
    Ilin, I. V., Antipin, A. R., & Lyovina, A. I. (2013). Business architecture modeling for process- and project-oriented companies. Economics and Management, 95, 32–38.Google Scholar
  9. 9.
    Röglinger, M., Pöppelbuß, J., & Becker, J. (2012). Maturity models in business process management. Business Process Management Journal, 18, 328–346.CrossRefGoogle Scholar
  10. 10.
    Scott, D., Pultz, J. E., Holub, E., Bittman, T. J., & McGuckin, P. (2007). Introducing the Gartner IT infrastructure and operations. Stamford: Gartner.Google Scholar
  11. 11.
    Object Management Group. (2008). Business process maturity model (BPMM). Version 1.0. OMG.Google Scholar
  12. 12.
    De Bruin, T., & Rosemann, M. (2005). Towards a business process management maturity model (Proceedings of ECIS 2005). Germany: Regensburg.Google Scholar
  13. 13.
    Hammer, M. (2007, April). The process audit. Harvard Business Review, 111–123.Google Scholar
  14. 14.
    Software Engineering Institute. (2010). CMMI ® for development, version 1.3. Carnegie Mellon University.Google Scholar
  15. 15.
    Chrissis, M. B., Konrad, M., & Shrum, S. (2003). CMMI: Guidelines for process integration and product development. Reading, MA: Addison-Wesley.Google Scholar
  16. 16.
    Kwak, Y. H., & Ibbs, W. C. (2002, July). Project management process maturity (PM2) model. Journal of Management in Engineering, 150–155.Google Scholar
  17. 17.
    AXELOS. (2014, January 25). Portfolio, programme and project management (P3M3). Introduction and guide to P3M3. Retrieved from P3M3 Official Site:
  18. 18.
    Giachetti, R. E. (2010). Design of enterprise systems: Theory, architecture, and methods. Boca Raton, FL: CRC Press.Google Scholar
  19. 19.
    Jonkers, H., Proper, E., & Turner, M. (2009). TOGAF™ and ArchiMate®: A future together. A vision for convergence & co-existence. The Open Group.Google Scholar
  20. 20.
    The Open Group. (2012). A pocket guide to ArchiMate 2.0. The Open Group.Google Scholar
  21. 21.
    CMMI Product Team. (2010). CMMI® for development, version 1.3. Carnegie Mellon University.Google Scholar
  22. 22.
    Trinity Management Consultants Limited. (2014, February 01). Overview of maturity levels. Retrieved from Trinity Management Consultants Limited:
  23. 23.
    CIO Council. (2001). A practical guide to federal enterprise architecture. Chief Information Officer Council.Google Scholar
  24. 24.
    PMI. (2013). A guide to the project management body of knowledge: PMBOK guide. 5th ed. Project Management Institute.Google Scholar
  25. 25.
    Turner, M. (2006). Microsoft® solutions framework essentials: Building successful technology solutions. Microsoft Press.Google Scholar
  26. 26.
    Giachetti, R. E. (2012). A flexible approach to realize an enterprise architecture. Procedia Computer Science, 8, 147–152.CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  • Igor V. Ilin
    • 1
    Email author
  • Anastasia I. Lyovina
    • 1
  • Anton R. Antipin
    • 2
  1. 1.Saint Petersburg State Polytechnic UniversitySaint PetersburgRussia
  2. 2.Business Set CorpSaint PetersburgRussia

Personalised recommendations