Skip to main content

A Conceptual Framework for Principles

  • Chapter
Architecture Principles

Part of the book series: The Enterprise Engineering Series ((TEES,volume 4))

Abstract

This chapter provides the theoretical core of this book. It is concerned with a conceptual framework for architecture principles and related concepts. It starts by providing some historical background to the concept of principle. We will distinguish between scientific principles that describe laws or facts of nature, and normative principles that start as fundamental beliefs and which are translated to more specific and measurable statements. Based on the distinction between architecture and design, as made in the previous chapter, we will be able to define architecture principles as a subset of design principles. We also include a discussion on the motivation for the use of architecture principles in specific situations. In doing so, we provide a set of typical drivers for their formulation and enforcement. The chapter ends with the discussion of a general strategy to more precisely specify architecture principles and their underlying domain concepts.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 169.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    See http://en.wikipedia.org/wiki/SMART_criteria.

  2. 2.

    Which does not only have to refer to money. We refer here to the exchange of scarce goods and/or services, which may include money, but also societal esteem, happiness, physical wellbeing, et cetera.

  3. 3.

    The capital letters in MoSCoW stand for:

    M :

    Must have this.

    S :

    Should have this if at all possible.

    C :

    Could have this if it does not affect anything else.

    W :

    Won’t have this time but would like in the future.

References

  • Achterbergh J, Vriens D (2009) Organisations: Social systems conducting experiments. Springer, Berlin. ISBN-13: 9783642001093

    Book  Google Scholar 

  • Ashby WR (1956) An introduction to cybernetics. Chapman & Hall, London. ISBN-10: 0412056704

    Google Scholar 

  • Beer S (1985) Diagnosing the system for organizations. Wiley, New York

    Google Scholar 

  • Beijer P, De Klerk T (2010) IT architecture: Essential practice for IT business solutions. Lulu, Raleigh

    Google Scholar 

  • BIS (2004) Basel II: International convergence of capital measurement and capital standards: A revised framework. Technical report, Bank for International Settlements, Basel, Switzerland

    Google Scholar 

  • Bloesch AC, Halpin TA (1996) ConQuer: A conceptual query language. In: Thalheim B (ed) Proceedings of the 15th international conference on conceptual modeling (ER‘96), Cottbus, Germany. Lecture notes in computer science, vol 1157. Springer, Berlin, pp 121–133

    Google Scholar 

  • BMM (2006) Business Motivation Model (BMM) specification. Technical Report dtc/06–08–03, Object Management Group, Needham, Massachusetts

    Google Scholar 

  • Bouwens S (2008) DYA architectuurprincipes—Deel 1: Basics (DYA architecture principles—Part 1: Basics). White paper, Sogeti, The Netherlands. In Dutch

    Google Scholar 

  • BPMN (2008) Business process modeling notation, v1.1. OMG Available Specification OMG Document Number: formal/2008-01-17, Object Management Group

    Google Scholar 

  • Campbell LJ, Halpin TA, Proper HA (1996) Conceptual schemas with abstractions—making flat conceptual schemas more comprehensible. Data & Knowledge Engineering 20(1):39–85

    Article  Google Scholar 

  • Chorus GJNM, Janse YHC, Nellen CJP, Hoppenbrouwers SJBA, Proper HA (2007) Formalizing architecture principles using object-role modelling. Via Nova Architectura. http://www.via-nova-architectura.org

  • Chung L, Gross D, Yu E (1999) Architectural design to meet stakeholder requirements. In: Donohue P (ed) First working IFIP conference on software architecture (WICSA1), San Antonio, Texas. Software architecture. Kluwer, Deventer, pp 545–564

    Google Scholar 

  • CIAO (2010) Enterprise engineering—the manifesto. Technical report, The CIAO! Network. http://ciaonetwork.org/publications/EEManifesto.pdf

  • Creasy PN, Proper HA (1996) A generic model for 3-dimensional conceptual modelling. Data & Knowledge Engineering 20(2):119–162

    Article  Google Scholar 

  • Davenport TH, Hammer M, Metsisto TJ (1989) How executives can shape their company’s information systems. Harvard Business Review 67(2):130–134. doi:10.1225/89206

    Google Scholar 

  • Dietz JLG (2006) Enterprise ontology—theory and methodology. Springer, Berlin. ISBN-10: 9783540291695

    Book  Google Scholar 

  • Dietz JLG (2008) Architecture—building strategy into design. Netherlands Architecture Forum, Academic Service—SDU, The Hague. ISBN-13: 9789012580861. http://www.naf.nl

    Google Scholar 

  • ECPD (1941) The Engineers’ council for professional development. Science 94(2446):456

    Google Scholar 

  • Engelsman W, Jonkers H, Quartel D (2010) ArchiMate extension for modeling and managing motivation, principles and requirements in TOGAF. White paper, The Open Group

    Google Scholar 

  • Graves T (2009) Doing enterprise architecture—process and practice in the real enterprise. Tetradian Books, Colchester. ISBN-13: 9781906681180. http://tetradianbooks.com

    Google Scholar 

  • Greefhorst D (2007) Ervaringen met het opstellen van architectuurprincipes bij een verzekeraar (Experiences with the formulation of architecture principles at an insurance company). ICT bibliotheek, vol 35. Academic Service—SDU, The Hague, pp 53–62. Chap 2. In Dutch. ISBN-13: 9789012119511

    Google Scholar 

  • Greefhorst D, Proper HA, Van den Ham F (2007) Principes: de hoeksteen voor architectuur—Verslag van een workshop op het Landelijk Architectuur Congres 2007 (Principles: the cornerstone of architecture—a report of a workshop held at the Dutch National Architecture Congres 2007). Via Nova Architectura. In Dutch. http://www.via-nova-architectura.org

  • Halpin TA, Morgan T (2008) Information modeling and relational databases, 2nd edn. Data management systems. Morgan Kaufman, San Mateo. ISBN-13: 9780123735683

    Google Scholar 

  • Hevner AR, March ST, Park J, Ram S (2004) Design science in information systems research. Management Information Systems Quarterly 28:75–106

    Google Scholar 

  • Hoogervorst JAP (2009) Enterprise governance and enterprise engineering. Springer, Diemen

    Book  Google Scholar 

  • Hoppenbrouwers SJBA, Proper HA, Van der Weide TP (2005) Fact calculus: using ORM and Lisa-D to reason about domains. In: Meersman R, Tari Z, Herrero P (eds) On the move to meaningful Internet systems 2005: OTM workshops—OTM confederated international workshops and posters, AWeSOMe, CAMS, GADA, MIOS+INTEROP, ORM, PhDS, SeBGIS, SWWS, and WOSE 2005, Agia Napa, Cyprus. Lecture notes in computer science, vol 3762. Springer, Berlin, pp 720–729. ISBN-10: 3540297391. doi:10.1007/11575863_91

    Google Scholar 

  • Iacob MqE, Jonkers H, Lankhorst MM, Proper HA (2009) ArchiMate 1.0 specification. The Open Group, Reading. ISBN-13: 9789087535025

    Google Scholar 

  • IEEE (2000) Recommended practice for architectural description of software intensive systems. Technical Report IEEE P1471:2000, ISO/IEC 42010:2007, The Architecture Working Group of the Software Engineering Committee, Standards Department, IEEE, Piscataway, New Jersey. ISBN-10: 0738125180

    Google Scholar 

  • ISO (2001) Software engineering—Product quality—Part 1: Quality model. ISO/IEC 9126–1:2001

    Google Scholar 

  • Lankhorst MM, et al. (2005a) Enterprise architecture at work: modelling, communication and analysis. Springer, Berlin. ISBN-10: 3540243712

    Google Scholar 

  • Lee C (2006) Aerospace Logistics architecture program: action research at Air France Cargo—KLM Cargo. Master’s thesis, Delft Technical University, Delft, The Netherlands

    Google Scholar 

  • Lidwell W, Holden K, Butler J (2003) Universal principles of design. Rockport, Minneapolis

    Google Scholar 

  • Lindström A (2006a) An approach for developing enterprise-specific ICT management methods—from architectural principles to measures. In: IAMOT 2006—15th international conference on management of technology, Beijing, China

    Google Scholar 

  • Lindström A (2006b) On the syntax and semantics of architectural principles. In: Proceedings of the 39th Hawaii international conference on system sciences

    Google Scholar 

  • Meersman R (1982) The RIDL conceptual language. Technical Report, International Centre for Information Analysis Services, Control Data Belgium, Inc, Brussels, Belgium

    Google Scholar 

  • Meriam-Webster (2003) Meriam-Webster Online, Collegiate Dictionary

    Google Scholar 

  • Op ’t Land M, Proper HA (2007) Impact of principles on enterprise engineering. In: Österle H, Schelp J, Winter R (eds) Proceedings of the 15th European conference on information systems. University of St Gallen, St Gallen, Switzerland, pp 1965–1976

    Google Scholar 

  • Op ’t Land M, Proper HA, Waage M, Cloo J, Steghuis C (2008) Enterprise architecture—creating value by informed governance. Springer, Berlin. ISBN-13: 9783540852315

    Google Scholar 

  • Osterwalder A, Pigneur Y (2009) Business model generation: a handbook for visionaries, game changers, and challengers. Self Published, Amsterdam. ISBN-13: 9782839905800

    Google Scholar 

  • Paauwe M (2010) The history of architecture principles. White paper, Paauwe Research

    Google Scholar 

  • PRISM (1986) PRISM: Dispersion and interconnection: approaches to distributed systems architecture, Final Report. Technical Report, CSC Index, Inc and Hammer & Company, Inc, Cambridge MA

    Google Scholar 

  • Regev G, Wegmann A (2005) Where do goals come from: the underlying principles of goal-oriented requirements engineering. In: Proc of the 13th IEEE international conference on requirements engineering (RE05), Paris, France, August 2005

    Google Scholar 

  • Richardson GL, Jackson BM, Dickson GW (1990) A principles-based enterprise architecture: lessons from Texaco and Star Enterprise. Management Information Systems Quarterly 14(4):385–403. http://www.jstor.org/stable/249787

    Google Scholar 

  • Rifaut A, Dubois E (2008) Using goal-oriented requirements engineering for improving the quality of ISO/IEC 15504 based compliance assessment frameworks. In: Proceedings of the IEEE international conference on requirements engineering (RE’08), Barcelona, Spain. IEEE Press, New York

    Google Scholar 

  • Rivera R (2007) Am i doing architecture or design work? IT Professional 9(6):46–48

    Article  Google Scholar 

  • SBVR (2006) Semantics of business vocabulary and rules (SBVR). Technical Report dtc/06–03–02, Object Management Group, Needham, Massachusetts

    Google Scholar 

  • Schekkerman J (2008) Enterprise architecture good practices guide: how to manage the enterprise architecture practice. Trafford, Victoria. ISBN-13: 9781425156879

    Google Scholar 

  • Software & Systems Engineering Standards Committee (1998) IEEE Std 1061-1998—IEEE standard for a software quality metrics methodology. Technical report, IEEE Computer Society

    Google Scholar 

  • Stapleton J (1997) DSDM, dynamic systems development method: the method in practice. Addison Wesley, Reading. ISBN-10: 0201178893

    Google Scholar 

  • Taylor FW (1911) Principles of scientific management. Harper & Row, New York

    Google Scholar 

  • Taylor JR, Van Every EJ (2010) The situated organization: case studies in the pragmatics of communication research. Routledge, London ISBN-13: 9780415881685

    Google Scholar 

  • Ter Hofstede AHM, Proper HA, Van der Weide TP (1993) Formal definition of a conceptual language for the description and manipulation of information models. Information Systems 18(7):489–523

    Article  Google Scholar 

  • TOGAF (2009) The Open Group—TOGAF version 9. Van Haren, Zaltbommel. ISBN-13: 9789087532307

    Google Scholar 

  • Trog D, Vereecken J, Christiaens S, Leenheer PD, Meersman R (2006) T-Lex: a role-based ontology engineering tool. In: Meersman R, Tari Z, Herrero P (eds) On the move to meaningful Internet systems 2006: OTM 2006 workshops. OTM confederated international workshops and posters, AWESOMe, CAMS, COMINF, IS, KSinBIT, MIOS-CIAO, MONET, OnToContent, ORM, PerSys, OTM Acadamy Doctoral Consortium, RDDS, SWWS, and SebGIS, Proceedings, Part II, Montpellier, France. Lecture notes in computer science, vol 4278. Springer, Berlin, pp 1191–1200

    Chapter  Google Scholar 

  • UML2 (2003) UML 2.0 Superstructure specification—final adopted specification. Technical Report ptc/03–08–02, OMG

    Google Scholar 

  • Van Bommel P, Hoppenbrouwers SJBA, Proper HA, Van der Weide TP (2006) Giving meaning to enterprise architectures—architecture principles with orm and orc. In: Meersman R, Tari Z, Herrero P (eds) On the move to meaningful Internet systems 2006: OTM workshops—OTM confederated international workshops and posters, AWeSOMe, CAMS, GADA, MIOS+INTEROP, ORM, PhDS, SeBGIS, SWWS, and WOSE 2006, Montpellier, France. Lecture notes in computer science. Springer, Berlin, pp 1138–1147. doi:10.1007/11915072_17

    Google Scholar 

  • Van Bommel P, Buitenhuis PG, Hoppenbrouwers SJBA, Proper HA (2007) Architecture principles—a regulative perspective on enterprise architecture. In: Reichert M, Strecker S, Turowski K (eds) Enterprise modelling and information systems architectures (EMISA2007). Lecture notes in informatics, vol 119. Gesellschaft fur Informatik, Bonn, pp 47–60

    Google Scholar 

  • Van Lamsweerde A (2001) Goal-oriented requirements engineering: A guided tour. In: Proc RE’01: 5th intl symp req eng

    Google Scholar 

  • Vermeulen E (2009) De principegenerator—principes in de 5e versnelling. Via Nova Architectura. In Dutch. http://www.via-nova-architectura.org

  • Yu E, Mylopoulos J (1994) Understanding ‘why’ in software process modelling, analysis, and design. In: Proceedings of the 16th international conference on software engineering, Sorrento, Italy. IEEE, Los Alamitos, pp 159–168. ISBN-10: 081865855X

    Chapter  Google Scholar 

  • Yu E, Mylopoulos J (1996) Using goals, rules, and methods to support reasoning in business process reengineering. International Journal of Intelligent Systems in Accounting, Finance & Management 5(1):1–13. Special issue on Artificial Intelligence in Business Process Reengineering

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Danny Greefhorst .

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Greefhorst, D., Proper, E. (2011). A Conceptual Framework for Principles. In: Architecture Principles. The Enterprise Engineering Series, vol 4. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-20279-7_3

Download citation

Publish with us

Policies and ethics