Term Name |
Acronym |
Definition | Related Modeling Terms |
|---|---|---|---|
Acceptance Criteria | AC | Tests associated with requirements that must be met in order for the implemented requirement to be approved by stakeholders.. |
|
Activity |
| The specification of a series of actions that achieve a goal, or may result in a change in the state of the system. |
|
Action |
| The specification of a function that is performed by a system, an actor or a worker, that forms part of an activity. |
|
Actor |
| Someone or something that gains benefit from use case activity, or interacts with the system under consideration. |
|
Aggregation |
| A type of relationship, where one component contains another, yet both may exist independently of each other. |
|
Analysis/Analyze |
| The art of breaking down a problem space into smaller related components. | Synthesis/Synthesize |
Analysis Model |
| A complete description of the requirements for a system (or application), in terms of the operations it performs, the data that it manipulates and the relationships between that data. |
|
Application |
| The software part of the system under discussion. |
|
Application Use Case | AUC | Activity that is performed by the software that resides within a system, in terms of the actors of the use case and their interface to the system. | System Use Case, Use Case |
Architecture |
| The high-level design showing the system components and the interfaces and relationships between those components. |
|
Architecturally Significant |
| A requirement that has an impact o the architectural design of a system. |
|
Artifact |
| Something that is created during the process. | Object, Class |
Association |
| Shows communication between an actor and a use case, 2 use cases or 2 classes. |
|
Assumption |
| A potential constraint on the requirements that has not been confirmed. | Risk |
Attribute |
| A component of a class that partially defines of the scope of the class in terms of the data that it manipulates. |
|
Business Actor |
| Someone who gets benefit from a business use case. | Actor |
Business Process Management | BPM | A method for determining how business processes are automated, managed and governed. | BPMN |
Business Process Model and Notation | BPMN | The rules, guidelines and notation used to model business processes using BPM. | BPM |
Business Use Case | BUC | An activity that gives benefit to a business actor. The BUC is documented in terms of its actors, preconditions, activity steps and postconditions. |
|
Business Rule |
| A business constraint on the implementation of 1 or more requirements. |
|
Class |
| A collection of objects sharing the same relationships, attributes and operations. | Object, Artifact |
Component |
| Anything that is captured by the model and can be viewed on a model diagram. |
|
Composition |
| A type of relationship where one component contains another, and the contained component is wholly dependent upon the container component. (I.e. it may not exist without its container.) |
|
Consumable |
| An artifact that is delivered to a consumer | Object, Class |
Consumer |
| A person that takes delivery of an artifact | Actor |
Current State |
| An analysis, (including models and descriptions) of the as-is business processes and systems within the scope of the project. |
|
Customer |
| A stakeholder who uses products or services that are impacted by the analysis activity. | Actor, Stakeholder |
Decision |
| A question whose answer will decide which 1 of 2 or more paths is taken through an activity. |
|
Diagram |
| A graphical depiction of all or part of a model. |
|
Element |
| A component of a task | Attribute |
Elicitation Result |
| Information from an elicitation activity that can be used to derive or constrain system requirements. |
|
End User |
| A stakeholder who interacts with the system. | Stakeholder, Actor |
Enterprise Architect |
| A stakeholder responsible for the interfaces and distributed functionality between systems in the enterprise. |
|
Extend Relationship |
| Concerning use cases; an extending use case adds activity to the body of other use cases. |
|
Fork |
| A method for splitting a single activity path into 2 or more parallel paths. |
|
Future State |
| An analysis, (including models and descriptions) of the to-be business processes and systems within the scope of the project. |
|
Hardware |
| Any part of a system that may be physically touched by a person |
|
Guideline and Tool |
| A set of instructions or a piece of software that assists with completing a task | Object |
Include Relationship |
| Concerning use cases; an included use case is fully contained within the body of other use cases. |
|
Instance |
| A member of a class that has been instantiated. | Object |
Join |
| A method for reconnecting 2 or more parallel activity paths into a single path. |
|
Knowledge Area |
| A packaged grouping of artifacts | Package |
Logical Data Model | LDM | Represents the information managed by a system in terms of classes and their relationships. |
|
Merge |
| A notation used to bring together 2 alternate activity paths, that resulted from a decision, into a single path |
|
Model |
| A complete description of a system from all perspectives or Points Of View. |
|
Object |
| An entity with a well-defined boundary and identity that encapsulates state and behavior. | Class, Instance |
Operation |
| A description of a function that is performed by a class. |
|
Operations Support Engineer |
| A stakeholder who is responsible for the day-to-day management and | Stakeholder, Actor |
Package |
| A container used to group artifacts. |
|
Postcondition |
| The state of the system after an activity has taken place. |
|
Precondition |
| The state of the system prior to an activity taking place. |
|
Priority |
| An attribute of a use case or scenario that describes its impact on the architecture, or its importance for a release. |
|
Project Manager |
| A stakeholder who is responsible for managing the work to deliver a system and for ensuring that the project's objectives are met while balancing the project constraints, including scope, budget, schedule, resources, quality, and risk. | Stakeholder, Actor |
Proposed Change |
| A request that impacts project requirements . |
|
Rational Unified Process | RUP | An iterative adaptable software development process framework created by the Rational Software Corporation (a division of IBM), intended to be tailored by organizations that select the elements of the process that are appropriate for their needs. | RUP |
Recommended Action |
| A description of what could be done to improve the value of a solution. |
|
Relationship |
| Shows a connection between any 2 components of a model. |
|
Regulator |
| A stakeholder from outside the organization who is responsible for the definition and enforcement of standards. | Stakeholder, Actor |
Requirement |
| Describes a condition or capability to which a system must conform. |
|
Risk (Analysis Result) |
| Description of an adverse effect on the project, it causes, probability of it occurring and mitigation strategies for minimizing the impact to the project. |
|
Scaled Agile Framework | SAFE | A process framework for implementing agile practices across an enterprise with multiple development teams. |
|
Software |
| Any part of the system that no physical presence. I.e. it cannot be physically touched by a person. |
|
Sponsor |
| A stakeholder who authorizes the work to be performed and controls the budget and scope of the project. | Stakeholder, Actor |
State |
| A condition or situation during the life of an object during which it satisfies some condition, performs some activity, or waits for some event. |
|
Stakeholder |
| Any person with an interest in realizing the benefits of the process | Actor |
Stakeholder Engagement |
| A description of stakeholder engagement activities and their willingness to participate in business analysis activities. |
|
Subject Matter Expert | SME | A stakeholder with in-depth knowledge of business needs, solution scope or specialized knowledge about the implementation of one or more solution components. | SME |
Supplier |
| A stakeholder outside the organization who provides products or services to the organization. | Stakeholder, Actor |
Synthesis/Synthesize |
| The art of combining small components into a larger picture of a solution. | Analysis/Analyze |
System |
| The combination hardware and software under discussion. |
|
System Actor |
| Someone or something, outside the system that interacts with the system. | Actor |
Task |
| A function of the BABOK process that produces one or more consumables. |
|
Technique |
| A method that may be used by a task. |
|
Tester |
| A stakeholder who is responsible for determining that the delivered system meets the to-be requirements for that system. | Stakeholder, Actor |
Transition |
| A description of an event and subsequent actions that occur as a result of that event occurring. A change in state of the system being described, is caused by a transition. |
|
Unified Modeling Language |
| An object modeling and specification language used in software engineering. | UML |
Use Case |
| A set of actions a that yields an observable result of value to a particular actor. |
|
Use Case Fragment |
| A partial use case activity description, that is either included or extends other use cases. | Use Case |
Use Case Model |
| A model of the system under discussion in terms of actors, and use cases and the relationships between the use cases. |
|
Vision |
| An overview description of the objectives for a project or system. |
|
Worker |
| Any role that assists the BA with producing an artifact. | Actor |