ADM Guidelines and Techniques Flashcards
ADM Guidelines
The guidelines document how to adapt the ADM process. Include
- Ways to apply iteration to the ADM
- Applying the ADM at different levels of the enterprise
- How to use the TOGAF framework with different architectural styles
ADM Techniques
The techniques are used when applying the ADM process
In Phase B, Phase C, and Phase D the practitioner is expected
To select the relevant architecture resources, including models, viewpoints, and tools, to properly describe the architecture domain and demonstrate that stakeholder concerns are addressed.
Architecture Principles
A set of general rules and guidelines for the architecture being developed.
Architecture Principles
An initial output of the Preliminary Phase and are used throughout the ADM to provide a framework for guiding decision-making within the enterprise
Key domains to establish Architecture Principles
- Enterprise Principles. Provide a basis for decision-making throughout an enterprise and dictate how the organization fulfills its mission
- Architecture Principles. A set of principles that relate to architecture work and govern the architecture process, affecting the development, maintenance, and use of the Enterprise Architecture.
TOGAF Template for Defining Principles
- Name
- Statement
- Rationale
- Implications
TOGAF Recommended Criteria for Quality Principles
- Understandability
- Robustness. Should enable good quality decisions about architectures and plans to be made, and enforceable policies and standards to be created
- Completeness
- Consistency
- Stability
Business Scenario describes
- A business process, application, or set of applications
- The business and technology environment
- The people and computing components (“actors”) who execute the scenario
- The desired outcome of proper execution
The Business Scenario Process
Problem->Environment->Objectives->Human Actors->Computer Actors->Roles & Responsibilities->Refine
Business scenarios figure most prominently in
The initial phase of an ADM cycle, Architecture Vision, when they are used to define relevant business requirements, and to build consensus with business management and other stakeholders.
Gap Analysis
Highlight a shortfall between the Baseline Architecture and the Target Architecture; that is, items that have been deliberately omitted, accidentally left out, or not yet defined
Sources of Gaps - Business domain gaps
- People gaps (e.g., cross-training requirements)
- Process gaps (e.g., process inefficiencies)
- Tools gaps (e.g., duplicate or missing tool functionality)
- Information gaps
- Measurement gaps
- Financial gaps
- Facilities gaps (buildings, office space, etc.)
Sources of Gaps - Data domain gaps
- Data not of sufficient currency
- Data not located where it is needed
- Not the data that is needed
- Data not available when needed
- Data not created
- Data not consumed
- Data relationship gaps
Sources of Gaps - Applications impacted, eliminated, or created
self
Sources of Gaps - Technologies impacted, eliminated, or created
…anything under “Eliminated Services” or “New Services” is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function
Interoperability
the ability to share information and services
Interoperability categorization
- Operational or Business Interoperability defines how business processes are to be shared
- Information Interoperability defines how information is to be shared
- Technical Interoperability defines how technical services are to be shared or at least connect to one another
From an IT perspective, it is also useful to consider interoperability in a similar vein to Enterprise Application Integration (EAI); specifically
- Presentation Integration/Interoperability is where a common look-and-feel approach through a common portal-like solution guides the user to the underlying functionality of the set of systems
- Information Integration/Interoperability is where the corporate information is seamlessly shared between the various corporate applications to achieve, for example, a common set of client information. Normally this is based upon a commonly accepted corporate ontology and shared services for the structure, quality, access, and security/privacy for the information.
- Application Integration/Interoperability is where the corporate functionality is integrated and shareable so that the applications are not duplicated (e.g., one change of address service/component; not one for every application) and are seamlessly linked together through functionality such as workflow. This impacts the business and infrastructure applications and is very closely linked to corporate business process unification/interoperability.
- Technical Integration/Interoperability includes common methods and shared services for the communication, storage, processing, and access to data primarily in the application platform and communications infrastructure domains
Business Transformation Readiness Assessment
Provides a technique for understanding the readiness of an organization to accept change, identifying the issues, and dealing with them in the Implementation and Migration Plan.
An initial assessment of business transformation readiness is carried out in Phase A.
Phase A
Two levels of risk that should be considered
- Initial Level of Risk. Risk categorization prior to determining and implementing mitigating actions.
- Residual Level of Risk. Risk categorization after implementation of mitigating actions.
The recommended process for managing risk consists of the following activities
- Risk classification
- Risk identification
- Initial risk assessment
- Risk mitigation and residual risk assessment
- Risk monitoring
Risk is pervasive in any Enterprise Architecture activity and present in all phases within the ADM.
self
Capability-Based Planning
A business planning technique that focuses on business outcomes. It is business-driven and business-led and combines the requisite efforts of all lines of business to achieve the desired capability.
