Karteikarten
Core Concepts, Phase B & C Level 2
Karten in diesem Stapel (98)
- 1Phase B Business Architecture Objectives (1/2)1. Develop the Target Business Architecture describing how the enterprise needs to operate to achieve the business goals, responds to the strategic drivers set out in the Architecture Vision, and addresses the Request for Architecture Work and stakeholder concerns
- 2Phase B Business Architecture Objectives (2/2)2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures
- 3Phase B Business Architecture Approach (1/4)1. Knowledge of the Business Architecture is a prerequisite for architecture work in the other domains (Data, Applications, Technology)
- and so is the first activity that needs to be undertaken - 4Phase B Business Architecture Approach (2/4)2. Buss Strategy defines WHAT to achieve
3. Buss Arch. describes HOW to achieve it
4. This Phase is often required to demonstrate business value of subsequent work to key stakeholders - 5Phase B Business Architecture Approach (3/4)5.Scope depends on existing strategy and planning: - Update and verify
- Bridge between high-level business drivers, strategy and
-Goals on the one hand, and specific business requirements
- Existing architecture discovery must include all relevant detail - 6Phase B Business Architecture Approach (4/4)If there is no existing strategy or planning:
- Identify any existing Arch definitions, then verify and update
- New process definitions may require detailed work
Use business scenarios to identify key business objectives and processes - 7Phase B - Business Architecture Developing the Baseline Description (1/2)1.If an enterprise has existing arch. descriptions, they should be reused as the basis for the Baseline Description
2. The usual approach to analyze the current state is bottomup - 8Phase B - Business Architecture Developing the Baseline Description (2/2)3.Business processes that are not to be carried forward have no value
4.The goal should be to re-use existing material where possible - 9Phase B - Business Architecture Catalogs Business Service / FunctionA functional decomposition in a form that can be filtered, reported on, and queried, as a supplement to graphical.
It contains the following entities:
•Organization Unit,Business Function, Business Service, Information System Service (may optionally be included here) - 10Phase B - Business Architecture Catalogs Location CatalogA listing of all locations where an enterprise carries out business operations or houses architecturally relevant assets, such as data centers or end-user computing equipment.
It contains the following entities:
•Location - 11Phase B - Business Architecture Catalogs Process/ Event/ Control/ Product CatalogProvides a hierarchy of processes, events that trigger processes, outputs from processes, and controls applied to the execution of processes.
It contains the following entities:
•Process, Event, Control, Product - 12Phase B - Business Architecture Catalogs Contract/ Measure CatalogA listing of all agreed service contracts and (opt.) the measures attached to those contracts. It forms the master list of service levels agreed, entities:
•Business Service
•Information System Service (optionally)
•Contract, •Measure - 13Phase B - Business Architecture Matrix1. Business Interaction matrix
2. Actor/Role matrix - 14Phase B - Business Architecture Business Interaction MatrixThe purpose of this matrix is to depict the relationship interactions between organizations and business functions
across the enterprise. - 15Phase B - Business Architecture Business Interaction Matrix Example
- 16Phase B - Business Architecture Actor/Role matrixThis matrix show which actors perform which roles, supporting definition of security and skills requirements.
- 17Phase B - Business Architecture Actor/Role Matrix Example
- 18Phase B - Business Architecture Diagrams (1/2)1.Business Footprint diagram
2.Business Service/Information diagram
3.Functional Decomposition diagram
4.Product Lifecycle diagram
5.Goal/Objective/Service diagram - 19Phase B - Business Architecture Diagrams (1/2)6.Use-Case diagram
7.Organization Decomposition diagram
8.Process Flow diagram
9.Event diagram - 20Phase B - Business Architecture Business Footprint diagram (1/2)Describes the links between business goals, organizational units, business functions, and services, and maps these
functions to the technical components delivering the required capability. - 21Phase B - Business Architecture Business Footprint diagram (2/2)Demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders
- 22Phase B - Business Architecture Business Footprint diagram Example
- 23Phase B - Business Architecture Business Service/Information Diagram (1/2)1.Shows the information needed to support one or more business services.
2.Shows what data is consumed by or produced by a business service and may also show the source of information. - 24Phase B - Business Architecture Business Service/Information Diagram (2/2)3. Shows an initial representation of the information present within the architecture and therefore forms a basis for elaboration and refinement within Phase C (Data
Architecture). - 25Phase B - Business Architecture Business Service/Information Diagram Example
- 26Phase B - Business Architecture Functional Decomposition Diagram (1/2)1.It shows on a single page the capabilities of an organization that are relevant to the consideration of an architecture.
- 27Phase B - Business Architecture Functional Decomposition Diagram (2/2)2.By examining the capabilities of an organization from a functional perspective, it is possible to quickiy develop models of what the organization does without being dragged into extended debate on how the organization does it.
- 28Phase B - Business Architecture Product Lifecycle Diagram (1/3)1. This assists in understanding the lifecycles of key entities within the enterprise.
- 29Phase B - Business Architecture Product Lifecycle Diagram (2/3)2. Understanding product lifecycles is becoming increasingly important with respectto environmental concerns, legislation, and regulation where products must be tracked from manufacture to disposal.
- 30Phase B - Business Architecture Product Lifecycle Diagram (2/3)3. Equally, organizations that create products that involve personal or sensitive information must have a detailed understanding of the product lifecycle during the development of Buss Arch. in order to ensure rigor in design of controls, processes, and procedures.
- 31Phase B - Business Architecture Goal/Objective/Service Diagram (1/3)1. This defines the ways in which a service contributes to the achievement of a business vision or strategy.
- 32Phase B - Business Architecture Goal/Objective/Service Diagram (2/3)2. Services are associated with the drivers, goals, objectives, and measures that they support, allowing the enterprise to
understand which services contribute to similar aspects of business performance - 33Phase B - Business Architecture Goal/Objective/Service Diagram (3/3)3. This also provides qualitative input on what constitutes high performance for a particular service
- 34Phase B - Business Architecture Use-Case diagram (1/3)1. This displays the relationships between consumers and providers of business services.
2. They help to describe and valídate the interaction between actors and their roles to processes and functions. - 35Phase B - Business Architecture Use-Case diagram (2/3)3. Business services are consumed by actors or other business services and the Business Use-Case diagram provides added richness in describing business capability by illustrating how and when that capability is used.
- 36Phase B - Business Architecture Use-Case diagram (3/3)4. As the architecture progresses, the use-case can evolve from the business level to include data, application, and technology details. Architecturai business use-cases can also be re-used in systems design work.
- 37Phase B - Business Architecture Organization Decomposition diagram1. This describes the links between actor, roles & location within an organz. tree.
2.An organization map should provide a chain of command of owners and
decision-makers in the organization. - 38Phase B - Business Architecture Process Flow diagram (1/2)1. This depiets all models and mappings related to the process metamodel entity.
2. It shows sequential flow of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. - 39Phase B - Business Architecture Process Flow diagram (2/2)3. In addition to showing a sequence of activity, process flows can also be used to detail the controls that apply to a process, the events that trigger or result from completion of a process, and also the products that are generated from
process execution. - 40Phase B - Business Architecture Event Diagrams1. This depicts the relationship between events and process.
2.Certain events - such as arrival of information or a point in time cause work and actions to be undertaken within the business. - 41Phase B - Business Architecture Using the Architecture Repository (1/2)As part of Phase B the architecture team need to consider what relevant resources are available from the Architecture
Repository - 42Phase B - Business Architecture Using the Architecture Repository (1/2)1. Generic business models relevant to the organization's industry sector
2. Business models relevant to common high-level business domains -
such as ecommerce, supply chain management etc - 43Phase B - Business Architecture Using the Architecture Repository (2/2)3. Enterprise-specific building blocks (process components, business rules, job descriptions etc)
4. Applicable standards - 44Phase C - Information Systems Architectures1.Fundamental organization of an IT system
2. Shows how the IT systems meets the business goals of the enterprise - 45Phase C - Information Systems Architectures Data or App first?1.It is usually necessary to address both
2. May be developed in either order, or in parallel
3. There will need to be some iteration to ensure consistency - 46Phase C - Information Systems Architectures Objectives (1/2)1. Develop the Target Info. Sys. (Data and Application) Arch., describing how the enterprise's Information Systems
Arch. will enable the Business Arch. and the Arch. Vision, in a way that addresses the Request for Arch. Work and stakeholder concerns - 47Phase C - Information Systems Architectures Objectives (2/2)2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems
(Data and Application) Architectures - 48Phase C - Information Systems Architectures Approach (3/3)1. Phase C involves Data and Applications Architecture, in either order.
2. Advocates exist for both sequences, buttom-up & top-down - 49Phase C - Information Systems Architectures Top-Down DesignDESIGN:
1. Business Architecture
2. Data (or Applications) Architecture
3. Applications (or Data) Architecture
4. Technology Architecture - 50Phase C - Information Systems Architectures Bottom-up ImplementationIMPLEMENTATION:
1. Technology Architecture
2. Applications (or Data) Architecture
3. Data (or Applications) Architecture
4. Business Architecture - 51Phase C - Information Systems Architectures Data driven Implementation1. First implement application systems that CREATE data
2. Then applications that PROCESS the data
3. Finally, applications that ARCHIVE data - 52Phase C - Information Systems Architectures Architecture RepositoryConsider generic models relevant to an organization's industry vertical
1. Data Architecture Resources
2. Application Architecture Resources - 53Phase C - Infor. Sys. Arch. Considerations for Data Architecture1. Data Management
2. Data Migration
3. Data Governance - 54Phase C - Infor. Sys. Arch. Catalog Data Entity/Data ComponentMaintain a list of all the data use across the enterprise, including data entities and data components where are stored. Entities:
1. Data Entity
2. Logical Data component
3.Physical Data component - 55Phase C - Infor. Sys. Arch. Matrices1. Data Entity/Business Function matrix
2. Application/Data matrix - 56Phase C - Infor. Sys. Arch. Data Entity/Business Function Matrix (1/4)1. The purpose ofthe Data Entity/Business Function matrix is to depict the relationship between data entities and business functions within the enterprise.
- 57Phase C - Infor. Sys. Arch. Data Entity/Business Function Matrix (2/4)2. The mapping of the Data Entity-Business Function relationship enables the following to take place:
2.1 Assignment of ownership of data entities to organizations
2.2 Understand the data and information exchange requirements buss. services - 58Phase C - Infor. Sys. Arch. Data Entity/Business Function Matrix (3/4)2.3 Support the gap analysis and determine whether any data entities are missing and need to be created
2.4 Define system of origin, system of record, and system of reference for data entities - 59Phase C - Infor. Sys. Arch. Data Entity/Business Function Matrix (4/4)2.5 Enable development of data governance programs across the enterprise (establish data steward, develop data standards pertinentto the business
function, etc.) - 60Phase C - Infor. Sys. Arch. Application/Data Matrix (1/2)1. The purpose of the Application/Data matrix is to depict the relationship between applications and the data entities that are accessed and updated by them.
- 61Phase C - Infor. Sys. Arch. Application/Data Matrix (2/2)2. Applications will create, read, update, and delete specific data entities that are associated with them.
- 62Phase C - Infor. Sys. Arch. Diagrams1. Conceptual Data diagram
2. Logical Data diagram
3. Data Dissemination diagram
4. Data Security diagram
5. Data Migration diagram
6. Data Lifecycle diagram - 63Phase C - Infor. Sys. Arch. Conceptual Data diagramThe purpose is to depict the relationships among the critical data entities (or classes) within the enterprise
- 64Phase C - Infor. Sys. Arch. Logical Data DiagramThe purpose is to depict logical views relationships among the critical data entities (or classes) within the enterprise.
The audience is:
- Application developers
- Database designers - 65Phase C - Infor. Sys. Arch. Data Dissemination Diagram (1/2)1. The purpose of the Data Dissemination diagram is to show the relationship between
- data entity
- business service
- application components - 66Phase C - Infor. Sys. Arch. Data Dissemination Diagram (2/2)2. The diagram should show how the logical entities are to be physically realized by application components.
3. Additionally, the diagram may show data replication and system ownership of the master reference for data. - 67Phase C - Infor. Sys. Arch. Data Lifecycle diagramIs an essential part of managing business data throughout its lifecycle from conception until disposal within the constraints of the business process.
- 68Phase C - Infor. Sys. Arch. Data Security Diagram (1/2)1. The purpose of the Data Security diagram is to depict which actor (person, organization, or system) can access which
enterprise data. - 69Phase C - Infor. Sys. Arch. Data Security Diagram (2/2)2. This relationship can also be shown in a matrix form between two objects or can be shown as a mapping.
- 70Phase C - Infor. Sys. Arch. Data Migration diagram1.The purpose is to show the flow of data from the source to the target apps.
2. The diagram will provide a visual representation of the spread of sources/targets and serve as a tool for data auditing and traceability - 71Phase C - Infor. Sys. Arch. Data Architecture Objectives (1/2)1. Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision, while addressing the Request for Architecture Work and stakeholder concerns
- 72Phase C - Infor. Sys. Arch. Data Architecture Objectives (2/2)2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Data Architectures
- 73Phase C - Infor. Sys. Arch. Data Architecture Steps (1/2)1. Select reference models, viewpoints, & tools
2. Develop baseline Data Arch. Description
3. Develop target Data Arch. Description
4. Perform gap analysis - 74Phase C - Infor. Sys. Arch. Data Architecture Steps (2/2)5. Define candidate roadmap components
6. Resolve impacts across the Arch. Landscape
7. Conduct formal stakeholder review
8. Finalize the Data Architecture
9.Create Arch. Deinition Document - 75Phase C - Infor. Sys. Arch. Data Architecture Application Portfolio Catalog CatalogTo identify and maintain a list of all the applications in the enterprise. This list helps to define the horizontal scope of change initiatives of applications.
1. Information system Service
2.Logical Application Component
3. Physical Application Component - 76Phase C - Infor. Sys. Arch. Data Architecture Interface Catalog CatalogThe purpose is to scope and document the interfaces between apps to enable the overall dependencies between apps.
1. Logical Application Component
2. Physical Application Component
3. App communicates with app relatinships - 77Phase C - Infor. Sys. Arch. Data Architecture Matrices1. Application/Organization matrix
2. Role/Application matrix
3. Application/Function matrix
4. Application Interaction matrix - 78Phase C - Infor. Sys. Arch. Data Architecture Application/Organization matrix (1/3)1. The purpose ofthis matrix is to depict the relationship between apps & organizational units within the enterprise
2. The mapping of the App Component-Organization Unit relationship is an important step as it enables: - 79Phase C - Infor. Sys. Arch. Data Architecture Application/Organization matrix (2/3)2.1. Assign usage of applications to the org. units that perform business functions
2.2. Understand the app support requirements of the bussiness services and processes carried out by an organization unit - 80Phase C - Infor. Sys. Arch. Data Architecture Application/Organization matrix (3/3)2.3. Support the gap analysis and determine whether any of the app are missing and as a result need to be created
2.4. Define the application set used by a particular organization unit - 81Phase C - Infor. Sys. Arch. Data Architecture Role/Application matrix (1/3)1. The purpose is to show the relationship between apps and the business roles that use them in the enterprise.
2. The mapping of the App Component-Role relationship is an important step as it enables the following to take place: - 82Phase C - Infor. Sys. Arch. Data Architecture Role/Application matrix (2/3)2.1 Assign usage of applications to the specific roles in the organization
2.2 Understand the app security requirements of the business services & processes supporting the function, and check these are in line with current policy - 83Phase C - Infor. Sys. Arch. Data Architecture Role/Application matrix (3/3)2.3 Support the gap analysis & determine whether any of the apps are missing and as a result need to be created
2.4 Define the application set used by a particular business role, essential in any move to role-based computing - 84Phase C - Infor. Sys. Arch. Data Architecture Application/Function matrix (1/3)1. The purpose is to show the relationship between apps & business functions within the enterprise.
2. The mapping of the App Component-Function relationship is an important step as it enables the following to take place: - 85Phase C - Infor. Sys. Arch. Data Architecture Application/Function matrix (2/3)2.1 Assign usage of apps to the business functions that are supported by them
2.2 Understand the app support requirements of the buss services & processes carried out - 86Phase C - Infor. Sys. Arch. Data Architecture Application/Function matrix (3/3)2.3 Support the gap analysis & determine whether any of the apps are missing and as a result need to be created
2.4 Define the application set used by a particular business function - 87Phase C - Infor. Sys. Arch. Data Architecture Diagrams (1/2)1. Application Communication diagram
2. N2 model or Node Connectivity diagram
3. Application and User Location diagram
4. Application Use-Case diagram
5. Enterprise Manageability diagram - 88Phase C - Infor. Sys. Arch. Data Architecture Diagrams (2/2)6. Process/Application Realization diagram
7. Software Engineering diagram
8. Application Migration diagram
9. Software Distribution diagram - 89Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Application Communication diagram1. Shows all models and mappings related to communication between apps in the metamodel entity.
2. Shows application components and interfaces between components.
3. Communication should be logical & only show intermediary tech as archy. relevant - 90Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Application and User Location diagram (1/3)1. Shows the business locations from which business users typically interact with
the apps, but also the hosting location of the application infrastructure.
2. The diagram enables: - 91Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Application and User Location diagram (2/3)2.1 Identification of the number of package instances needed
2.2 Estimation of the number and the type of user licenses
2.3 Estimation of the level of support needed - 92Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Application and User Location diagram (3/3)2.4 Selection ofsystem management tools, structure, and managmt system
2.5 Appropriate Planning for the technological components of the business
2.6 Performance considerations while implementing solutions - 93Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Enterprise Manageability diagram1. Shows how one or more apps interact with app and technology components that support operational managmt. of solution.
2. Analysis can reveal duplication and gaps, and opportunities in the IT service managmt. operation of an organizatn. - 94Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Process/Application Realization diagram1. Shows the sequence of events when múltiple applications are involved in executing a business process.
2. Enhances the app Commn diagram by augmenting it with any sequencing constraints, and handoff points between batch and real-time processing. - 95Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Software Engineering diagram1. Breaks apps into packages, modules, services, and operations from a
development perspective
2. Enables more detailed impact analysis when planning migration stages, and analyzing opportunities and solutions.
3. Ideal for complex dev. environments - 96Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Application Migration diagram1. Identifies app migration from baseline to target app components.
2. Enables a more accurate estimation of migration costs
3. Should be used to identify temporary apps, staging areas, and the infrastructure required to support migrations - 97Phase C - Infor. Sys. Arch. Data Architecture - Diagrams Software Distribution Diagram1. This diagram is a combination of the Software Engineering diagram and the Application-User Location diagram.
2. Depending on the circumstances, this diagram alone may be sufficient, or may not be needed. - 98Phase C - Infor. Sys. Arch. Data Architecture Recommendations1. Simplify complicated applications by decomposing them into two or more apps
2. Remove duplicate functionlity as possibl and combine similar apps into one
3.Develop matrices and app arch views by examing how the app will function
Informationen
- Beschreibung
- Core Concepts Level 2 Phase B Level 2 Phase C Level 2
- Erstellt von
- Juda Osejo · Jul 2017
- Aktualisiert
- 12 Jul 2017
- Aufrufe
- 10
- Bewertung