ADM Guidelines and Techniques Flashcards
ADM + ADM Guidelines and Techniques
- G+T is resources, guidelines, templates, techniques- G+T directly support the use of the ADM- Separated from the ADM to reduce clutter- E.g., Iteration, security, gap analysis, principles list
ADM + Enterprise Continuum + Architecture Repository
- Continuum categorizes entities created using the ADM
- Repository stores work created using the ADM
- Repository has reference architectures, models, patterns
- ADM phase dictates the types of assets used
ADM + Foundation Architecture
- ADM populates Foundation Architecture with- Reusable common models, policy, governance
Briefly describe guidelines vs techniques
- Guidelines document how to adapt the ADM- Techniques are used when applying the ADM
Characteristics of a good business scenario (5)
- S: Specific: Defines what needs to be done- M: Measurable: Clear metrics for success- A: Actionable: Provides the solution- R: Realistic: Within time and cost constraints- T: Time bound: When the opportunity expires
Characteristics of Architecture Principles
- A set of rules and guidelines for architecture
- Seldom amended
- Guides the way mission is accomplished
- Guides values, actions, results
- Initial output of Preliminary phase
Define Business Architecture
- Description of structure and interaction between- strategy, organization, functions, processes, needs
Define Business Governance
- Ensuring business processes deliver outcomes- And adhere to regulations
Define Capability
- Ability of organization, system, person- Requires org, people, processes, technology- E.g., telemarketing dept
Define Concerns
- Interests important to stakeholders- Determine acceptability of a solution- E.g., performance, reliability, security
Define Constraint
- External factor that prevents an approach or goal- E.g., Customer data is not consistent
Define Data Architecture
- Logical and physical data assets- Structure and interaction- Data management resources.
Define Deliverable
- Work contractually specified- Reviewed, agreed, signed off by stakeholders- Archived or stored in an Architecture Repository- Can be: Reference model, standard, or snapshot
Define Enterprise
- Collection of organizations with common goals- Highest organizational level- Covers all missions and functions- Can extend to partners, suppliers, customers
Define Gap
- Difference between two states- E.g., Baseline vs Target Architecture
Define Governance
- Monitoring, managing, steering a business- Enforces delivery of required business outcome
Define IT (4 definitions)
- Lifecycle management of info + technology2. Umbrella including computer industry areas3. Department assigned to provision IT areas4. Information Services; Information Management
Define Logical Architecture
- Implementation-independent definition- Logical grouping of related physical entities
Define Reference Model (RM)
- Abstract framework of entities and relations- Based on small number of unifying concepts- Common semantics across implementations
Define Repository
- System that manages data in an enterprise- Includes data, processes, other information
Define Segment Architecture
- Formal description of areas within enterprise- E.g., program or portfolio level
Define Solution Architecture
- Descr of a discrete and focused business operation- Applies to a single project, release, solution
Define Solution Building Block (SBB)
- A concrete, physical Building block- Conforms to an Architectural building block
Define Solutions Continuum
- Part of the Enterprise Continuum- Implementations of Architecture Continuum- Reusable solutions for future implementations
Define Stakeholder
- Individual, team, or organization- Interests in or concerns about an architecture
Define Strategic Architecture
- Formal summary of an entire enterprise- Framework for operational activity- Executive level, long term view
Describe Business Transformation Readiness Assessment
- Technique to understand readiness to accept change- Identifies issues and solutions in Migration Plan- Based on Canadian Government BTEP E=Enablement
Describe Capability Based Planning
- Business driven: Focuses on business outcomes- Combines efforts of business lines to achieve- Useful when a latent capability needed (DR)
Describe IT interoperability in the 4 domains:
- Business: Common look/feel, portal
- Data: Identity, common ontology, shared services
- Application: Common components, reuse
- Technical: Shared methods, systems, services
Describe the 2 domains of principles
- Enterprise principles
- Guides and harmonizes decision making
- Includes principles for business units (HR)
- Architecture principles
- Reflect enterprise architecture consensus
- Govern architecture process and its use
Dimensions for limiting architecture scope:
- Breadth: Enterprise, segment, capability
- Depth: Level of detail (simple = shallow)
- Time period: Resources vs time, transitions
- Domains: (Business, data, app, tech) vs subset
Guidelines vs techniques
- Guidelines: How to adapt ADM, e.g., iteration - Techniques: Support specific tasks, e.g. gap analysis
How does TOGAF work with other architectures
- TOGAF can include the use of other frameworks- ADM is framework agnostic
How is Capability based planning related to the ADM
- A: Corporate strategic plan
- B-D: Define corporate projects and ABBs
- E,F: Define transition architectures (increments)
In what ADM phases is Bus Transformation Readiness Assessment used
- A: Initial assessment readiness/CMM- E,F: Selection and implementation
In what ADM phases is interoperability considered
- A: Nature and security of information exchange
- B-D: Defined for each domain
- E: Actual solutions are selected - (Make/Buy)
- F: Logical interoperability
In what phases is Gap Analysis used
- B, C, D, and E
Key ADM points
- ADM is iterative
- Decisions are made at each iteration
- Reuse from: Previous ADM iterations or other models
List 3 categories of interoperability
- Operational/business: Shared processes
- Information: Shared information
- Technical: Sharing or connection of services
List 4 items included in the guidelines (adapt ADM)
- Ways to apply iteration to the ADM
- Applying ADM at different levels in enterprise
- Security considerations
- Using TOGAF to define SOAs
List 7 steps used to create business scenarios
- Problem: Identify, document, and rank
- Environment: Business and technical
- Objectives: Successful outcomes
- Human actors: Positions and roles
- Computer actors: Elements and roles
- Roles and responsibilities: For each actor
- Refine: If neces
List ADM iteration levels (3)
- Around: Cycle through the phases in order- Between: E.g., return to B Business from D Tech- Within: Repeated execution of a phase activities
List ADM Phase B-D steps needed per each domain (BDAT) (9)
- Select reference models, viewpoints, tools- 2. Develop baseline __ Architecture Description- 3. Develop target __ Architecture Description- 4. Perform gap analysis (target vs baseline)- 5. Define candidate roadmap components- 6. Resolve imp
List some business domain gaps
- People: cross training
- Process: inefficiencies
- Tools: duplicate or missing
- Information
- Measurement
- Financial
- Facilities: buildings, office space
List some business modeling tools-techniques
- Business process models (activity models)- Use case models- Class models- Node connectivity diagrams- Information exchange matrices
List some data domain gaps
- Not current
- Not located where needed
- Wrong data
- Not created
- Not consumed
- Relationship gaps
List the TOGAF principles template elements (4)
- Name: Descriptively names the principle- Statement: Communicates the fundamental rule- Rationale: Business benefits, precedence- Implications: Resources, activities, tasks, impact
Process for managing risk (5 steps)
- Risk classification- Risk identification- Initial risk assessment- Mitigation and residual risk assessment- Risk monitoring