Muutke küpsiste eelistusi

E-raamat: Architecture Principles: The Cornerstones of Enterprise Architecture

3.67/5 (48 hinnangut Goodreads-ist)
,
  • Formaat: PDF+DRM
  • Sari: The Enterprise Engineering Series
  • Ilmumisaeg: 29-Apr-2011
  • Kirjastus: Springer-Verlag Berlin and Heidelberg GmbH & Co. K
  • Keel: eng
  • ISBN-13: 9783642202797
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 159,93 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Architecture Principles: The Cornerstones of Enterprise ArchitectureSuurem pilt
  • Formaat: PDF+DRM
  • Sari: The Enterprise Engineering Series
  • Ilmumisaeg: 29-Apr-2011
  • Kirjastus: Springer-Verlag Berlin and Heidelberg GmbH & Co. K
  • Keel: eng
  • ISBN-13: 9783642202797
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Enterprises, from small to large, evolve continuously. As a result, their structures are transformed and extended continuously. Without some means of control, such changes are bound to lead to an overly complex, uncoordinated and heterogeneous environment that is hard to manage and hard to adapt to future changes. Enterprise architecture principles provide a means to direct transformations of enterprises. As a consequence, architecture principles should be seen as the cornerstones of any architecture.

In this book, Greefhorst and Proper focus on the role of architecture principles. They provide both a theoretical and a practical perspective on architecture principles. The theoretical perspective involves a brief survey of the general concept of principle as well as an analysis of different flavors of principles. Architecture principles are regarded as a specific class of normative principles that direct the design of an enterprise, from the definition of its business to its supporting IT. The practical perspective on architecture principles is concerned with an approach to the formulation of architecture principles, as well as their actual use in organizations. To illustrate their use in practice, several real-life cases are discussed, an application of architecture principles in TOGAF is included, and a catalogue of example architecture principles is provided.

With this broad coverage, the authors target students and researchers specializing in enterprise architecture or business information systems, as well as practitioners who want to understand the foundations underlying their practical daily work.
1 Introduction
1(6)
1.1 Challenges to Enterprises
1(2)
1.2 Enterprise Architecture and Architecture Principles
3(1)
1.3 Motivations and Target Audience
4(1)
1.4 Outline of the Book
5(2)
2 The Role of Enterprise Architecture
7(24)
2.1 Introduction
7(2)
2.2 Enterprise Transformations and Enterprise Engineering
9(2)
2.3 Streams of Activities in Enterprise Engineering
11(3)
2.4 Architecture-Based Governance of Enterprise Transformations
14(6)
2.4.1 The Need for Architecture
14(2)
2.4.2 Architecture as a Bridge from Strategy to Design
16(2)
2.4.3 Steering with Architecture
18(1)
2.4.4 The Three Roles of Enterprise Architecture
19(1)
2.5 Defining Enterprise Architecture
20(4)
2.5.1 The Purpose of an Enterprise Architecture
21(1)
2.5.2 The Meaning of an Enterprise Architecture
22(1)
2.5.3 The Elements of an Enterprise Architecture
22(2)
2.5.4 Definition of Enterprise Architecture
24(1)
2.6 Other Forms of Architecture
24(2)
2.7 Standards for Enterprise Architecture
26(2)
2.8 The Role of Architecture Principles
28(1)
2.9 Key Messages
29(2)
3 A Conceptual Framework for Principles
31(28)
3.1 Introduction
31(1)
3.2 Background of Architecture Principles
32(2)
3.3 Key Classes of Principles
34(10)
3.3.1 Scientific Principles
34(1)
3.3.2 Design Principles as Normative Principles
35(3)
3.3.3 From Credos to Norms
38(2)
3.3.4 Conceptual Framework
40(4)
3.4 Architecture Principles as Pillars from Strategy to Design
44(5)
3.4.1 Architecture Principles
44(1)
3.4.2 Business and IT Principles
44(2)
3.4.3 Bridging from Strategy to Design
46(2)
3.4.4 Extended Conceptual Framework
48(1)
3.5 Motivating Architecture Principles
49(7)
3.5.1 Sources for Finding Motivation
50(2)
3.5.2 Drivers as Motivation for Architecture Principles
52(2)
3.5.3 Extended Conceptual Framework
54(2)
3.6 Formal Specification of Normative Principles
56(2)
3.7 Key Messages
58(1)
4 Architecture Principle Specifications
59(26)
4.1 Introduction
59(3)
4.2 Dimensions in Architecture Principles
62(8)
4.2.1 Type of Information Dimension
63(1)
4.2.2 Scope Dimension
63(1)
4.2.3 Genericity Dimension
64(1)
4.2.4 Level of Detail Dimension(s)
65(1)
4.2.5 Stakeholder Dimension
66(1)
4.2.6 Transformation Dimension
66(1)
4.2.7 Quality Attribute Dimension
67(2)
4.2.8 Meta-level Dimension
69(1)
4.2.9 Representation Dimension
69(1)
4.3 Attributes
70(9)
4.3.1 Basic Structure
71(2)
4.3.2 Advised Attributes
73(2)
4.3.3 Attributes for Classification
75(1)
4.3.4 Potential Attributes
75(1)
4.3.5 Generic Meta-data Attributes
76(1)
4.3.6 Relationships
77(2)
4.4 Architecture Principle Sets
79(2)
4.5 Quality Criteria
81(2)
4.6 Key Messages
83(2)
5 A Practical Approach
85(26)
5.1 Introduction
85(3)
5.2 Generic Process
88(21)
5.2.1 Determine Drivers
88(3)
5.2.2 Determine Principles
91(7)
5.2.3 Specify Principles
98(2)
5.2.4 Classify Principles
100(1)
5.2.5 Validate and Accept Principles
100(1)
5.2.6 Apply Principles
101(4)
5.2.7 Manage Compliance
105(3)
5.2.8 Handle Changes
108(1)
5.3 Key Messages
109(2)
6 Case Studies
111(22)
6.1 Introduction
111(1)
6.2 ICTU
112(3)
6.2.1 Introduction
112(1)
6.2.2 Architecture Principles
113(2)
6.2.3 Approach
115(1)
6.3 CVZ
115(5)
6.3.1 Introduction
115(2)
6.3.2 Architecture Principles
117(1)
6.3.3 Approach
118(2)
6.4 Enexis
120(4)
6.4.1 Introduction
120(1)
6.4.2 Architecture Principles
121(1)
6.4.3 Approach
121(3)
6.5 TKP Pensioen
124(3)
6.5.1 Introduction
124(1)
6.5.2 Architecture Principles
125(2)
6.5.3 Approach
127(1)
6.6 Schiphol
127(5)
6.6.1 Introduction
128(1)
6.6.2 Architecture Principles
129(1)
6.6.3 Approach
130(2)
6.7 Key Messages
132(1)
7 Architecture Principles in Context
133(14)
7.1 Introduction
133(1)
7.2 Types of Architectures
134(3)
7.2.1 Enterprise Architecture Development
134(1)
7.2.2 Reference Architecture Development
135(1)
7.2.3 Solution Architecture Development
136(1)
7.3 Architecture Maturity
137(5)
7.3.1 Department of Commerce Maturity Model
137(2)
7.3.2 Architecture Maturity and Architecture Principles
139(3)
7.4 Culture
142(3)
7.5 Key Messages
145(2)
8 Summary, Conclusions and Future Work
147(6)
8.1 Summary and Conclusions
147(2)
8.2 Future Work
149(4)
Appendix A Principles Catalogue
153(28)
A.1 Business Units Are Autonomous
153(1)
A.2 Customers Have a Single Point of Contact
154(1)
A.3 Stock Is Kept to a Minimum
154(1)
A.4 Processes Are Straight Through
155(1)
A.5 Processes Are Standardized
155(1)
A.6 Management Layers Are Minimized
156(1)
A.7 Tasks Are Designed Around Outcome
156(1)
A.8 Routine Tasks Are Automated
156(1)
A.9 Primary Business Processes Are not Disturbed by Implementation of Changes
157(1)
A.10 Components Are Centralized
157(1)
A.11 Front-Office Processes Are Separated from Back-Office Processes
158(1)
A.12 Channel-Specific Is Separated from Channel-Independent
158(1)
A.13 The Status of Customer Requests Is Readily Available Inside and Outside the Organization
159(1)
A.14 Data Are Provided by the Source
159(1)
A.15 Data Are Maintained in The Source Application
159(1)
A.16 Data Are Captured Once
160(1)
A.17 Data Are Consistent Through All Channels
160(1)
A.18 Content and Presentation Are Separated
161(1)
A.19 Data Are Stored and Exchanged Electronically
161(1)
A.20 Data That Are Exchanged Adhere to a Canonical Data Model
162(1)
A.21 Data Are Exchanged in Real-Time
162(1)
A.22 Bulk Data Exchanges Rely on ETL Tools
163(1)
A.23 Documents Are Stored in the Document Management System
163(1)
A.24 Reporting and Analytical Applications Do Not Use the Operational Environment
164(1)
A.25 Applications Have a Common Look-and-Feel
164(1)
A.26 Applications Do Not Cross Business Function Boundaries
164(1)
A.27 Applications Respect Logical Units of Work
165(1)
A.28 Applications Are Modular
165(1)
A.29 Application Functionality is Available Through an Enterprise Portal
166(1)
A.30 Applications Rely on One Technology Stack
166(1)
A.31 Application Interfaces Are Explicitly Defined
167(1)
A.32 Proven Solutions Are Preferred
167(1)
A.33 IT Systems Are Scaleable
168(1)
A.34 Only in Response to Business Needs Are Changes to IT Systems Made
168(1)
A.35 Components Have a Clear Owner
169(1)
A.36 IT Systems Are Standardized and Reused Throughout the Organization
169(1)
A.37 IT Systems Adhere to Open Standards
170(1)
A.38 IT Systems Are Preferably Open Source
170(1)
A.39 IT Systems Are Available at Any Time on Any Location
171(1)
A.40 IT Systems Are Sustainable
171(1)
A.41 Processes Are Supported by a Business Process Management System
171(1)
A.42 Presentation Logic, Process Logic and Business Logic Are Separated
172(1)
A.43 IT Systems Communicate Through Services
172(1)
A.44 Reuse Is Preferable to Buy, Which is Preferable to Make
173(1)
A.45 IT Systems Support 24*7 Availability
173(1)
A.46 IT Systems Are Selected Based on a Best-of-Suite Approach
174(1)
A.47 Sensitive Data Are Exchanged Securely
174(1)
A.48 IT Systems May Under no Circumstances Revert to Insecure Mode
175(1)
A.49 Management of IT Systems is Automated as Much as Possible
175(1)
A.50 End-to-End Security Must Be Provided Using Multiple Defensive Strategies
176(1)
A.51 Access Rights Must Be Granted at the Lowest Level Necessary for Performing the Required Operation
176(1)
A.52 Authorizations Are Role-Based
177(1)
A.53 The Identity Management Environment Is Leading for All Authentications and Authorizations
177(1)
A.54 Security Is Defined Declaratively
177(1)
A.55 Access to IT Systems Is Authenticated and Authorized
178(1)
A.56 Integration with External IT Systems Is Localized in Dedicated IT Components
178(1)
A.57 Application Development Is Standardized
179(1)
A.58 All Messages Are Exchanged Through the Enterprise Service Bus
179(1)
A.59 Rules That Are Complex or Apt to Change Are Managed in a Business Rules Engine
180(1)
Appendix B Architecture Principles in TOGAF
181(6)
B.1 Architecture Principles in TOGAF
181(1)
B.2 Architecture Principles in TOGAF ADM
182(2)
B.3 Mapping the Generic Process to TOGAF's ADM
184(3)
Glossary 187(2)
References 189(8)
About the Authors 197
Danny Greefhorst is a principal consultant and owner of ArchiXL, and works for clients in the financial and public sector. Danny acts as an IT architect and IT consultant, and is TOGAF 9 certified. He has extensive experience with the definition and implementation of enterprise architectures, application architectures and technical architectures. In addition, he coaches organizations in setting up and executing their architecture function, and is active as an instructor for several classes on architecture. Before starting ArchiXL he worked as a principal consultant at Yellowtail, as a senior IT architect at IBM Business Consulting Services and as a researcher at the Software Engineering Research Centre. Danny is active in the architecture community and regularly publishes on IT and architecture related topics. He is the chairman of the governing board of Via Nova Architectura, a portal and electronic magazine on enterprise architecture. He is also a member of the governing board of the architecture department of the Dutch Computer Science Association (Ngi).

Erik (H.A.) Proper is a senior research manager at the Public Research Centre -- Henri Tudor in Luxembourg, where he leads Services-oriented Enterprise Engineering programme. He also holds a chair in Information Systems at the Radboud University Nijmegen in the Netherlands. Erik has a mixed industrial and academic background. In the past, Erik worked for companies such as Asymetrix, InfoModeller, Origin, ID Research, Ordina and Capgemini, while interleaving this with his work at research institutions such as the Radboud University of Nijmegen, Queensland University of Technology, the Distributed Systems Technology Centre, and the University of Queensland. His general research drive is the modeling of systems. He applies this drive mainly in the fields of service science, enterprise modeling, enterprise engineering and enterprise architecting. He was co-initiator of the ArchiMate project, and currently also serves on the board of the ArchiMate forum of The Open Group. Erik is also one of the editors in chief of Springer's series on enterprise engineering.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97836422027972e.html
Märksõnad: