| |
| |
| Introduction | |
| |
| |
| How to derive the architecture and its governance | |
| |
| |
| What is the problem? | |
| |
| |
| Ready, Set, Go overview | |
| |
| |
| Conventions used in this book | |
| |
| |
| About the authors | |
| |
| |
| |
| Ready | |
| |
| |
| City plan basic elements | |
| |
| |
| |
| Initiating the assignment | |
| |
| |
| Purpose of EA and EA awareness | |
| |
| |
| Executive sponsor and management commitment | |
| |
| |
| Participants | |
| |
| |
| Risks | |
| |
| |
| Gathering knowledge and getting started | |
| |
| |
| Checklist: Results of the initiation | |
| |
| |
| |
| Modeling the business processes and information | |
| |
| |
| Modeling business processes | |
| |
| |
| Modeling the business information structure | |
| |
| |
| Oh no, not data modeling! | |
| |
| |
| Business information modeling basics | |
| |
| |
| How to produce a business information model | |
| |
| |
| Documenting a business information model | |
| |
| |
| Expressing business expectations | |
| |
| |
| Expressing business expectations using Osterwalder's Business Model Canvas | |
| |
| |
| Expressing business expectations using Ross's Operating Model | |
| |
| |
| Linking business processes to objectives and values | |
| |
| |
| |
| Analyzing consequences and opportunities | |
| |
| |
| Identifying entity groups | |
| |
| |
| Determining information life cycle type | |
| |
| |
| Category information | |
| |
| |
| Resource information | |
| |
| |
| Business event information | |
| |
| |
| Detail operational transaction information ("big data") | |
| |
| |
| Distinguishing between resource and event entity groups | |
| |
| |
| Describing the processes' need of information | |
| |
| |
| Describing existing systems | |
| |
| |
| Analyzing opportunities and assessing benefit | |
| |
| |
| |
| Designing the optimum architecture | |
| |
| |
| Using business capabilities | |
| |
| |
| Understanding the process and system matrices | |
| |
| |
| Forming ideal blocks in the architecture matrix | |
| |
| |
| Forming a realistic architecture | |
| |
| |
| |
| Planning the enterprise architecture deliverables | |
| |
| |
| Short-term EA planning | |
| |
| |
| Long-term EA planning | |
| |
| |
| Establishing a roadmap | |
| |
| |
| Compiling a city plan | |
| |
| |
| |
| Summary of the Ready step | |
| |
| |
| |
| SET | |
| |
| |
| Getting set | |
| |
| |
| |
| Identifying stakeholders and target groups | |
| |
| |
| Conducting a SWOT analysis: analyzing strengths, weaknesses, opportunities, and threats | |
| |
| |
| Formulating targets for EA | |
| |
| |
| Securing support from management | |
| |
| |
| |
| Forming an EA-oriented development environment | |
| |
| |
| EA activities in business development | |
| |
| |
| EA activities when forming an IT vision and IT strategy | |
| |
| |
| EA activities to perform when forming EA and IT plans | |
| |
| |
| EA activities when executing development projects | |
| |
| |
| |
| Forming the EA ownership | |
| |
| |
| Entity owner and entity manager | |
| |
| |
| Who decides, who influences? | |
| |
| |
| Form a decision process | |
| |
| |
| |
| Organizing the enterprise architects | |
| |
| |
| Describing roles, mandates, and responsibilities | |
| |
| |
| Describing competence needs and recruiting | |
| |
| |
| Establishing prioritization rules for projects | |
| |
| |
| Identifying triggers and warnings | |
| |
| |
| |
| Identifying requirements for EA tools | |
| |
| |
| Forming meta-models | |
| |
| |
| Identifying rules for models | |
| |
| |
| |
| Communicating and planning | |
| |
| |
| Key success factors | |
| |
| |
| |
| GO | |
| |
| |
| |
| Conducting enterprise architecture work in practice | |
| |
| |
| Participating in projects | |
| |
| |
| Working with information models and conceptual models | |
| |
| |
| Working with information models for the architecture and for requirements specification | |
| |
| |
| Supporting projects relating to requirements specifications | |
| |
| |
| Providing support for systems acquisitions | |
| |
| |
| Developing triggers and actions | |
| |
| |
| Trigger: a start date for a project is reached | |
| |
| |
| Trigger: a project runs out of control | |
| |
| |
| Trigger: a new business model, strategy, or plan is published | |
| |
| |
| Trigger: a new ERP system is acquired | |
| |
| |
| Trigger: a new or updated business plan is published | |
| |
| |
| Trigger: a new person is appointed to a key decision-making role | |
| |
| |
| Trigger: a company is acquired | |
| |
| |
| Trigger: a new product or way of doing business is introduced | |
| |
| |
| Trigger: a new (unplanned) project is initiated | |
| |
| |
| Trigger: a new systems development method is selected | |
| |
| |
| Trigger: a new key partner needs to be chosen by management | |
| |
| |
| Managing models | |
| |
| |
| Communicating target achievements | |
| |
| |
| Developing standard/generic models | |
| |
| |
| |
| improving the EA work | |
| |
| |
| Monitoring the external environment | |
| |
| |
| Fine-tuning entities and processes | |
| |
| |
| Improving regulations | |
| |
| |
| Appendix: The Zachman Framework and Our Ea Process | |
| |
| |
| Further Reading | |
| |
| |
| Index | |