Prev | Next |
ACM Core
Elements from the ACM page of the Architecture Content Model Toolbox.
ACM Core Toolbox
Item |
Description |
---|---|
Actor |
Identifies a person, organization or system with a role that initiates or interacts with activities. Actors can be internal or external to an organization. Tagged Values – ID, Category, Source, Owner, #FTEs, ActorGoal, ActorTasks |
Assumption |
Defines a statement of probable fact that has not been fully validated at this stage, due to external constraints. Tagged Values – ID, Rationale, Statement, Type |
Business Constraint |
Identifies an external factor that prevents an organization from pursuing particular approaches to meet its goals. Tagged Value – ID |
Business Function |
Identifies a factor that delivers business capabilities closely aligned to an organization, but not necessarily explicitly governed by the organization. Tagged Value – ID |
Business Requirement |
Defines a quantitative statement of business need that must be met by a particular architecture or work Package. Tagged Value – ID |
Business Service |
Identifies a service that supports business capabilities through an explicitly defined interface and is explicitly governed by an organization. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate |
Capability |
Defines a business-focused outcome that is delivered by the completion of one or more work Packages. Using a capability-based planning approach, change activities can be sequenced and grouped in order to provide continuous and incremental business value. Tagged Values – ID, Category, Source, Owner, Increments, BusinessValue |
Data Entity |
Defines an encapsulation of data that is recognized by a business domain expert as an entity. Logical data entities can be tied to applications, repositories and services, and can be structured according to implementation considerations. Tagged Values – ID, Category, Source, Owner, PrivacyClassification, RetentionClassification |
Gap |
Provides a statement of difference between two states. Used in the context of gap analysis, where the difference between the Baseline and Target Architecture is identified. Tagged Values – ID, Category, Source, Owner |
Organization Unit |
Defines a self-contained unit of resources with line management responsibility, goals, objectives, and measures. Organizations can include external parties and business partner organizations. Tagged Values – ID, PersonIncharge |
Principle |
Provides a qualitative statement of intent that should be met by the architecture. This has at least a supporting rationale and a measure of importance. Tagged Values – ID, Type, Statement, Rationale, Implications |
Process |
Represents the flow of control between or within functions and/or services (depending on the granularity of definition). Processes represent a sequence of activities that together achieve a specified outcome, can be decomposed into sub-processes, and can show operation of a function or service (at the next level of detail). Processes can also be used to link or compose organizations, functions, services, and processes. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate, ProcessCriticality, ProcessVolumetrics, ProcessType |
Platform Service |
Defines a technical capability required to provide enabling infrastructure that supports the delivery of applications. Tagged Values – ID, Category, Source, Owner, StandardClass |
Role |
Defines the usual or expected function of an Actor, or the part somebody or something plays in a particular action or event. An Actor can have a number of roles. Tagged Values – ID, Category, Source, Owner, Responsibilities |
Work Package |
Identifies a set of actions to achieve one or more objectives for the business. A work Package can be a part of a project, a complete project or a program. Tagged Values – ID, Category, Source, Owner, CapabilityDelivered |
Application Component |
Provides an encapsulation of application functionality aligned to implementation structure. See also: 'Logical Application Component' and 'Physical Technology Component'. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate |
Logical Application Component |
Provides an encapsulation of application functionality that is independent of a particular implementation. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate |
Technology Component |
Provides an encapsulation of technology infrastructure that represents a class of technology product or specific technology product. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate |
Physical Technology Component |
Defines an instance of a specific technology infrastructure product or technology infrastructure product. Tagged Values – ID, Category, Source, Owner, StandardsClass, StandardCreationDate, LastStandardReviewDate, NextStandardReviewDate, RetireDate, ModuleName, ProductName, Vendor, Version |