This document defines future state and provides context for developing a business architecture model. It discusses why defining a future state is important for providing direction, alignment, and allowing progress. It recommends undergoing a process to map the current and future states of the business and key elements to define the future state task. The document then outlines components of a business architecture model including strategic context, business context, business capabilities, value streams, data context, and IT context. It provides examples of sub-elements under each component to gain a holistic perspective of an enterprise. Finally, it discusses the value of the business architecture model in providing a high-level view of integral business components, elements, and entities.
This document defines future state and provides context for developing a business architecture model. It discusses why defining a future state is important for providing direction, alignment, and allowing progress. It recommends undergoing a process to map the current and future states of the business and key elements to define the future state task. The document then outlines components of a business architecture model including strategic context, business context, business capabilities, value streams, data context, and IT context. It provides examples of sub-elements under each component to gain a holistic perspective of an enterprise. Finally, it discusses the value of the business architecture model in providing a high-level view of integral business components, elements, and entities.
This document defines future state and provides context for developing a business architecture model. It discusses why defining a future state is important for providing direction, alignment, and allowing progress. It recommends undergoing a process to map the current and future states of the business and key elements to define the future state task. The document then outlines components of a business architecture model including strategic context, business context, business capabilities, value streams, data context, and IT context. It provides examples of sub-elements under each component to gain a holistic perspective of an enterprise. Finally, it discusses the value of the business architecture model in providing a high-level view of integral business components, elements, and entities.
This document defines future state and provides context for developing a business architecture model. It discusses why defining a future state is important for providing direction, alignment, and allowing progress. It recommends undergoing a process to map the current and future states of the business and key elements to define the future state task. The document then outlines components of a business architecture model including strategic context, business context, business capabilities, value streams, data context, and IT context. It provides examples of sub-elements under each component to gain a holistic perspective of an enterprise. Finally, it discusses the value of the business architecture model in providing a high-level view of integral business components, elements, and entities.
BY: Group 6 Cadorna, Marrionne Faith Gimena, Jean Shadey Pascual, Kriz Anne D. Roma, Pauline Angela M. Rupa, Edrilyn Faith S. FUTURE STATE definition: the greater vision for the business
where the business
wants to be
Ca d pr an pa oc bi es li se ti s es Why is it important? Without it: a company will often hard to make pivotal find itself lacking decisions direction
misalignment amongst hinders progressions
executives and growth of a company’s mission How? undergo a series of process mapping exercises of both their: current state of business and what it will look like in the future Future State Task Define Future used to determine the conditions State Task: necessary to meet the business needs
In order to successfully implement
the solution, the future state has to be well defined. Future State Description On a detailed 1. Achieves the future state to be assessed and
level identified 4. Assesses the value
created by the future 2. Provides a clear definition state of outcomes that satisfies the business needs 5. Allows consensus among the key stakeholders 3. Is within the scope of the solution DEFINING FUTURE STATE TASK
Pot
goa ness obj s and s ive ent val
i Bus
ect l ial ue as Ide of su nt pe on mp if co ti ti y S lu ce
11 on so spa s
Internal Constraints assets ELEMENTS Org ness e a str nizat si ur uct i Bu ct ure onal ite cul h tur and arc e
Ca d pr an es
pa oc Technology and infrastructure ci
bi es li
li se ti s Po
es external opportunities
strength of new partners
new technologies or knowledge
mandatory adoption of a change
potential loss of a competitor BUSINESS ARCHITECTURE MODEL definition:simple and effective way to gain a holistic perspective
goal: to help chart courses and determine components and elements important to the enterprise
primary business architects
consumers: enterprise architects data architects business business model VS. architecture model deals with "HOW" a concerned with providing company thrives and a conceptual model of "HOW" survives business arki components come together
Important and complementary but
not the same. Highest-Level View of Business Architecture Model Strategic Business Business Context Context Capabilities
Value Data IT Streams Context Context Sub-elements of the Top-level Business Architecture Model Components Strategic Context
Cloud (Public and Private) ICEBREAKER Value of a Business Architecture Model Provides a bird’s eye view
Provides what components,
elements, and entities are an integral part of the business architecture journey SOLUTION SCOPE definition: It is the characteristics and features of the product or service that will be provided. It is: functional; or non-functional
"what" is included in the solution?
"how" will it look like?
Why is the Solution Scope? Why is the Solution Scope? Main Purpose: to make things under control to avoid scope creep to stay focused and easily define the expected capabilities
Non-existence of the solution scope
will lead to the failure of project. Process Mapping definition: a graphical representation with illustrative descriptions of how things get done
helps the participants to
visualize the details of the process closely and guides decision making Process Mapping Symbols major components inputs outputs steps in the process
It contains proper detail
with respect to multiple paths, decisions and rework loops Why do businesses need process maps? gui de il it ate visual Pictur es ma ps fac glimps wo rds Proces s i n the e ter th an ov em ent s bet impr s proces
maki ng e than any
Decision Improvements more effectiv made in the much t oral tools becomes fas process can ea sily be tracke d
guides t the he effect tl oo k of ive detailed ou managem ent of rent pr ocess su re me nt cur change v es as a mea Ser c es s a pr o tool for Types of Process Maps 1. Process flowchart Provides a visual representation of the sequence of activities along with their point of decisions Types of Process Maps 2. Deployment Flowchart provides the interaction between different departments and the roles of different people in the organization Why bother?
Helps Helps uncover deliver to waste expectations How to Start?
Remember: Before beginning the process mapping, you must have clearly established boundaries to make sure the scope of the flowchart that will be created will be manageable. ICEBREAKER for listening!
