CEA-C01 flashcards
CEA-C01 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Enterprise architecture definition
- The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of a company's operating model.
- Architecture building block
- A technology-neutral, reusable description of a capability or function required by the business, specified well enough to guide the selection of solution building blocks.
- Solution building block
- A concrete, technology-specific component or product that realizes one or more architecture building blocks within a delivered solution.
- Architecture principle
- An enduring statement of belief about how the enterprise should use architecture to achieve its mission, expressed with a rationale and implications.
- Stakeholder and concern
- A stakeholder is an individual or group with an interest in the architecture; a concern is that interest as it relates to one or more system elements.
- View versus viewpoint
- A view is a representation of a set of concerns held by a stakeholder; a viewpoint is the template, convention, or pattern used to construct that view.
- Zachman Framework structure
- A six-by-six ontology crossing six interrogatives (what, how, where, who, when, why) with six perspectives from planner through functioning enterprise.
- Zachman is not a methodology
- The Zachman Framework classifies architecture artifacts into cells but prescribes no sequence, process, or set of steps for producing them.
- TOGAF ADM phases
- Preliminary then A through H: Vision, Business, Information Systems, Technology, Opportunities and Solutions, Migration Planning, Implementation Governance, Change Management.
- TOGAF Requirements Management
- A continuous activity at the center of the ADM that captures, stores, and feeds requirements into every phase rather than a one-time phase.
- TOGAF Enterprise Continuum
- A progression from Foundation to Common Systems to Industry to Organization-Specific architectures, used to classify reusable architecture assets.
- FEAF reference models
- Performance, Business, Data, Application, and Infrastructure/Security reference models used to describe and compare federal enterprise architectures.
- Framework versus methodology
- A framework supplies structure for describing an architecture; a methodology supplies the process and steps for producing it.
- Viewpoint selection rule
- Select viewpoints based on documented stakeholder concerns, ensuring every view answers a stated question rather than filling out a framework.
- Cross-view consistency rule
- The same element appearing in multiple views must carry identical name, definition, and relationships so views can be reconciled.
- Baseline and target architecture
- The baseline describes the architecture as it currently exists; the target describes the desired future state against which gaps are assessed.
- Transition architecture
- A formally defined intermediate state of the enterprise architecture between baseline and target, delivered at a planned point in time.
- Work package
- A set of logically grouped change activities identified from gap analysis that together deliver a defined portion of the target architecture.
- Architecture contract
- A formal agreement between the architecture function and an implementation team defining conformance obligations, deliverables, and governance checkpoints.
- Architecture dispensation
- A time-bound waiver granted when a project cannot conform to a standard, recorded with justification and a remediation commitment.
- Preliminary phase outputs
- Architecture principles, the defined architecture capability, a tailored ADM, and the architecture governance framework established before formal ADM cycles begin.
- Architecture scope dimensions
- Breadth (organizational units covered), depth (level of detail modeled), and time horizon (how far into the future) must be agreed before work starts.
- Request for architecture work
- The document that authorizes an architecture engagement, stating objectives, scope, constraints, budget, and acceptance criteria.
- Architecture maturity assessment
- A CMMI-style rating from level 0 to 5 of the architecture practice's processes, used to plan capability improvements.
- Architecture communication plan
- A mapping of each stakeholder group to the views, channels, and cadence used to deliver architecture information to them.
- ArchiMate layers
- Strategy, Business, Application, Technology, Physical, and Implementation & Migration layers, plus cross-cutting Motivation and Composite elements.
- ArchiMate core relationships
- Composition, aggregation, realization, serving, access, and association, with specialization and triggering, define legal connections between elements.
- Metamodel validity
- A metamodel defines permitted element types and relationships; a model violating it is structurally invalid even if the diagram looks correct.
- Model traceability
- The linking of requirements to architecture elements and of architecture elements to designs and tests, enabling impact analysis.
- Gap analysis classification
- Comparing baseline and target elements and labeling each difference as eliminated, added, changed, or unchanged to derive work packages.
- Impact analysis
- Tracing a proposed change through dependency relationships to identify which processes, applications, data, and interfaces are affected.
- Architecture trade-off analysis
- Making explicit that improving one quality attribute, such as security, typically degrades another, such as usability or performance.