Describes the Structure Shared by a list of Instances. It contains Attributes, Functions (or Methods) and
User Interfaces. The definition of the Attributes and Methods serves as the Interface to the Class.
Example: for Class “Person”, Attributes are: "Name", "First Name", "Birth Date" and Methods are
"search Person by name", "compute age".
Values for Instance 1: "Smith", "John", "03 10 1976"
Values for Instance 2: "Murray", "Paul", "06 03 2002"
A Class "benefits" from the Attributes and Methods of the Classes from which it inherits.
Example: Life Insurance Policy inherits from Insurance Policy which is a basic Model for all Insurance
Policies (damage, life, health... )
The same Business Entity can be implemented in one or several Classes. Example:
The Business Entity "Address" could be described by one Class "Address".
The Business Entity "Bill" could be described by a Class "Bill Header" and a Class "Bill Line".

Actor who benefits from the Process Value: he can be a Business Actor (Customer, prospect, partner,
provider, government Entity), or an Organization Actor such as an employee.

A Group is broken down into Companies. The breakdown criteria can be: Product Line or Processes (like
Distribution/Production) or Customer segment or Geography.

Actions that a Worker is able to execute.

CEISAR reserves the word “Component” for software Model elements: Solution software, Process software, Activity software or Function software. A Component can be reusable or not.

Work station (for Assisted Worker) or Server (for Automate) which executes Actions.

Agreement signed when a Legal Entity sells a Product to a Subscriber.
Generally the Subscriber is a Customer.
For Distribution Agreement (including commissioning), the Subscriber is the Distributor.
For provider Agreement, the Subscriber is the Procurement department.

Person or Legal Entity who benefits from Enterprise Value. For many Enterprises he or she can be a Subscriber of a Contract (for Legal purposes) and/or a Decider (for Sales purposes)