| Description |
1 online resource (xv, 197 pages) |
| Series |
The Enterprise engineering series |
|
Enterprise engineering series.
|
| Contents |
Machine generated contents note: 1. Introduction -- 1.1. Challenges to Enterprises -- 1.2. Enterprise Architecture and Architecture Principles -- 1.3. Motivations and Target Audience -- 1.4. Outline of the Book -- 2. Role of Enterprise Architecture -- 2.1. Introduction -- 2.2. Enterprise Transformations and Enterprise Engineering -- 2.3. Streams of Activities in Enterprise Engineering -- 2.4. Architecture-Based Governance of Enterprise Transformations -- 2.4.1. Need for Architecture -- 2.4.2. Architecture as a Bridge from Strategy to Design -- 2.4.3. Steering with Architecture -- 2.4.4. Three Roles of Enterprise Architecture -- 2.5. Defining Enterprise Architecture -- 2.5.1. Purpose of an Enterprise Architecture -- 2.5.2. Meaning of an Enterprise Architecture -- 2.5.3. Elements of an Enterprise Architecture -- 2.5.4. Definition of Enterprise Architecture -- 2.6. Other Forms of Architecture -- 2.7. Standards for Enterprise Architecture -- 2.8. Role of Architecture Principles -- 2.9. Key Messages -- 3. Conceptual Framework for Principles -- 3.1. Introduction -- 3.2. Background of Architecture Principles -- 3.3. Key Classes of Principles -- 3.3.1. Scientific Principles -- 3.3.2. Design Principles as Normative Principles -- 3.3.3. From Credos to Norms -- 3.3.4. Conceptual Framework -- 3.4. Architecture Principles as Pillars from Strategy to Design -- 3.4.1. Architecture Principles -- 3.4.2. Business and IT Principles -- 3.4.3. Bridging from Strategy to Design -- 3.4.4. Extended Conceptual Framework -- 3.5. Motivating Architecture Principles -- 3.5.1. Sources for Finding Motivation -- 3.5.2. Drivers as Motivation for Architecture Principles -- 3.5.3. Extended Conceptual Framework -- 3.6. Formal Specification of Normative Principles -- 3.7. Key Messages -- 4. Architecture Principle Specifications -- 4.1. Introduction -- 4.2. Dimensions in Architecture Principles -- 4.2.1. Type of Information Dimension -- 4.2.2. Scope Dimension -- 4.2.3. Genericity Dimension -- 4.2.4. Level of Detail Dimension(s) -- 4.2.5. Stakeholder Dimension -- 4.2.6. Transformation Dimension -- 4.2.7. Quality Attribute Dimension -- 4.2.8. Meta-level Dimension -- 4.2.9. Representation Dimension -- 4.3. Attributes -- 4.3.1. Basic Structure -- 4.3.2. Advised Attributes -- 4.3.3. Attributes for Classification -- 4.3.4. Potential Attributes -- 4.3.5. Generic Meta-data Attributes -- 4.3.6. Relationships -- 4.4. Architecture Principle Sets -- 4.5. Quality Criteria -- 4.6. Key Messages -- 5. Practical Approach -- 5.1. Introduction -- 5.2. Generic Process -- 5.2.1. Determine Drivers -- 5.2.2. Determine Principles -- 5.2.3. Specify Principles -- 5.2.4. Classify Principles -- 5.2.5. Validate and Accept Principles -- 5.2.6. Apply Principles -- 5.2.7. Manage Compliance -- 5.2.8. Handle Changes -- 5.3. Key Messages -- 6. Case Studies -- 6.1. Introduction -- 6.2. ICTU -- 6.2.1. Introduction -- 6.2.2. Architecture Principles -- 6.2.3. Approach -- 6.3. CVZ -- 6.3.1. Introduction -- 6.3.2. Architecture Principles -- 6.3.3. Approach -- 6.4. Enexis -- 6.4.1. Introduction -- 6.4.2. Architecture Principles -- 6.4.3. Approach -- 6.5. TKP Pensioen -- 6.5.1. Introduction -- 6.5.2. Architecture Principles -- 6.5.3. Approach -- 6.6. Schiphol -- 6.6.1. Introduction -- 6.6.2. Architecture Principles -- 6.6.3. Approach -- 6.7. Key Messages -- 7. Architecture Principles in Context -- 7.1. Introduction -- 7.2. Types of Architectures -- 7.2.1. Enterprise Architecture Development -- 7.2.2. Reference Architecture Development -- 7.2.3. Solution Architecture Development -- 7.3. Architecture Maturity -- 7.3.1. Department of Commerce Maturity Model -- 7.3.2. Architecture Maturity and Architecture Principles -- 7.4. Culture -- 7.5. Key Messages -- 8. Summary, Conclusions and Future Work -- 8.1. Summary and Conclusions -- 8.2. Future Work -- Appendix A Principles Catalogue -- A.1. Business Units Are Autonomous -- A.2. Customers Have a Single Point of Contact -- A.3. Stock Is Kept to a Minimum -- A.4. Processes Are Straight Through -- A.5. Processes Are Standardized -- A.6. Management Layers Are Minimized -- A.7. Tasks Are Designed Around Outcome -- A.8. Routine Tasks Are Automated -- A.9. Primary Business Processes Are not Disturbed by Implementation of Changes -- A.10. Components Are Centralized -- A.11. Front-Office Processes Are Separated from Back-Office Processes -- A.12. Channel-Specific Is Separated from Channel-Independent -- A.13. Status of Customer Requests Is Readily Available Inside and Outside the Organization -- A.14. Data Are Provided by the Source -- A.15. Data Are Maintained in The Source Application -- A.16. Data Are Captured Once -- A.17. Data Are Consistent Through All Channels -- A.18. Content and Presentation Are Separated -- A.19. Data Are Stored and Exchanged Electronically -- A.20. Data That Are Exchanged Adhere to a Canonical Data Model -- A.21. Data Are Exchanged in Real-Time -- A.22. Bulk Data Exchanges Rely on ETL Tools -- A.23. Documents Are Stored in the Document Management System -- A.24. Reporting and Analytical Applications Do Not Use the Operational Environment -- A.25. Applications Have a Common Look-and-Feel -- A.26. Applications Do Not Cross Business Function Boundaries -- A.27. Applications Respect Logical Units of Work -- A.28. Applications Are Modular -- A.29. Application Functionality is Available Through an Enterprise Portal -- A.30. Applications Rely on One Technology Stack -- A.31. Application Interfaces Are Explicitly Defined -- A.32. Proven Solutions Are Preferred -- A.33. IT Systems Are Scaleable -- A.34. Only in Response to Business Needs Are Changes to IT Systems Made -- A.35. Components Have a Clear Owner -- A.36. IT Systems Are Standardized and Reused Throughout the Organization -- A.37. IT Systems Adhere to Open Standards -- A.38. IT Systems Are Preferably Open Source -- A.39. IT Systems Are Available at Any Time on Any Location -- A.40. IT Systems Are Sustainable -- A.41. Processes Are Supported by a Business Process Management System -- A.42. Presentation Logic, Process Logic and Business Logic Are Separated -- A.43. IT Systems Communicate Through Services -- A.44. Reuse Is Preferable to Buy, Which is Preferable to Make -- A.45. IT Systems Support 24*7 Availability -- A.46. IT Systems Are Selected Based on a Best-of-Suite Approach -- A.47. Sensitive Data Are Exchanged Securely -- A.48. IT Systems May Under no Circumstances Revert to Insecure Mode -- A.49. Management of IT Systems is Automated as Much as Possible -- A.50. End-to-End Security Must Be Provided Using Multiple Defensive Strategies -- A.51. Access Rights Must Be Granted at the Lowest Level Necessary for Performing the Required Operation -- A.52. Authorizations Are Role-Based -- A.53. Identity Management Environment Is Leading for All Authentications and Authorizations -- A.54. Security Is Defined Declaratively -- A.55. Access to IT Systems Is Authenticated and Authorized -- A.56. Integration with External IT Systems Is Localized in Dedicated IT Components -- A.57. Application Development Is Standardized -- A.58. All Messages Are Exchanged Through the Enterprise Service Bus -- A.59. Rules That Are Complex or Apt to Change Are Managed in a Business Rules Engine -- Appendix B Architecture Principles in TOGAF -- B.1. Architecture Principles in TOGAF -- B.2. Architecture Principles in TOGAF ADM -- B.3. Mapping the Generic Process to TOGAF's ADM |
| Summary |
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 |
| Analysis |
economie |
|
economics |
|
bedrijfswetenschap |
|
management science |
|
informatiesystemen |
|
information systems |
|
internet |
|
modellen |
|
models |
|
gegevensverwerking |
|
data processing |
|
computertechnieken |
|
computer techniques |
|
bedrijfsinformatiesystemen |
|
management information systems |
|
software engineering |
|
Management studies, Business Administration, Organizational Science (General) |
|
Management, bedrijfskunde, organisatiekunde (algemeen) |
| Bibliography |
Includes bibliographical references |
| Notes |
Print version record |
| In |
Springer eBooks |
| Subject |
Management information systems.
|
|
System design.
|
|
Management Information Systems
|
|
BUSINESS & ECONOMICS -- Information Management.
|
|
BUSINESS & ECONOMICS -- Knowledge Capital.
|
|
Affaires.
|
|
Science économique.
|
|
Management information systems
|
|
System design
|
| Form |
Electronic book
|
| Author |
Proper, Erik.
|
| LC no. |
2011927926 |
| ISBN |
9783642202797 |
|
3642202799 |
|
