Glossary of Terms


 * 1) Action - An uninteruptable serial function that is performed as part of an activity.
 * 2) Activity - A description of the functionality that is performed in order to satisfy a use case or similar operation. An activity comprises actions, decisions forks, states and flows between those elements.
 * 3) Association - A relationship between two entities, which implies some sort of communication (or sharing of information) between the entities.
 * 4) Business Use Case - A Business Use Case(BUC) represents a discrete unit of functionality performed by the business in order to satisfy a customer of the business. The BUC is initiated by an external event indicating that the customer has a need to be satisfied and ends when that need is satisfied, or is unable to be satisfied.
 * 5) Class - A logical entity encapsulating data and behavior. A class is a classifier template for an object.
 * 6) Deployment Model - A model of the proposed hardware that will make up the new system, together with the physical components that will execute on that hardware. Includes specifications for machine, operating system, network links, backup units &etc.
 * 7) Entity - An encapsulation of data and related functions, such as a class, object or actor.
 * 8) Extends - A relationship between two use cases in which one use case adds to the behavior of another. Typically this represents optional behavior in a use case scenario.
 * 9) Includes - A relationship between two use cases in which the included use case contains the details of the behavior of the parent. Used when the use case details in the included use case are referenced by many other use cases.
 * 10) Model - A description of the problem at a certain level of abstraction. A model has its own unique set of rules for modeling elements..
 * 11) Object - An instance of a class.
 * 12) Project - Set of models and supporting information making up complete specification of the project vision.
 * 13) Relationship - A connection between to entities which demonstrates a type how they are related. An association demonstrates data sharing, a generalization demonstrates sharing of data, functionality and behavior and dependency demonstrates an existance relationship.
 * 14) Repository - Area of storage for elements contained within 1 or more modelsi n a project.
 * 15) State Transition Diagram (STD).
 * 16) System Use Case - A System Use Case(SUC) represents a discrete unit of interaction between an actor (human or machine) and the system. A SUC is a single unit of meaningful work that initiates with the actor sending a message to the system and terminates when the objective of the use case is complete or is unable to continue to completion.
 * 17) View - Display of a subset of the contents of one or more models that satisfy the criteria being requested.