| Line 1: | Line 1: | 
|  |  |  |  | 
| − | ==== Application Data   ====
 |  | 
| − | * Should, where possible, be linked to a business object.
 |  | 
| − | 
 |  | 
| − | ==== Business Actor: ====
 |  | 
| − | * Represents an actual person, org structure section, committee or working group within or external to the organization.  e.g.:  Senior Advisor, Director Operations, Senior Vice President, ESSARB, Senior Management Board, Treasury Board, NRCan, John Smith, Dr. Henry Jones.  Not:  process modeler, designer, client, solution architect, manager
 |  | 
| − | * Linking:  Actors are usually linked to Roles.
 |  | 
| − | 
 |  | 
| − | ==== Business Event ====
 |  | 
| − | * Naming:  Should be a verb in the perfect tense, e.g: "claim received".
 |  | 
| − | 
 |  | 
| − | ==== Business Function  ====
 |  | 
| − | A logical grouping of related business activity (processes, sub-functions, roles, business information, etc...)  No flow or sequence is necessary.
 |  | 
| − | * Linking:  Must (directly or indirectly) support and link to an established Business Capability
 |  | 
| − | * Linking:  Should be associated with an enterprise requirement, strategic outcome, goal, and/or driver.
 |  | 
| − | * Naming convention:  Should NOT use verb-noun naming, in order to not be confused with business processes.
 |  | 
| − | 
 |  | 
| − | ==== Business Object ====
 |  | 
| − | * Naming:  Business object names should be nouns.
 |  | 
| − | 
 |  | 
| − | ==== Business Process  ====
 |  | 
| − | Something that is done/performed, that has a flow or sequence.  
 |  | 
| − | * Linking:  Should be related to a particular (superior) business function (e.g.  an SSC Service)
 |  | 
| − | * Naming:  Should name processes with verb-noun notation.  "Do something to something".  i.e.:  Place Order
 |  | 
| − | 
 |  | 
| − | ==== Business Role ====
 |  | 
| − | * Represents an abstract role, not a personal name or defined organizational position, committee, title, rank or hierarchy within the organization.  e.g.:  process modeler, designer, client, solution architect.  Not:  Senior Advisor, Director Operations, Senior Vice President, ESSARB, Senior Management Board, Treasury Board, NRCan, John Smith, Dr. Henry Jones.
 |  | 
| − | * Roles are usually linked to actors and business functions and processes.
 |  | 
| − | 
 |  | 
| − | ==== Business Service ====
 |  | 
| − | Something that is provided to an entity external to the business function.
 |  | 
| − | * Must link directly (or indirectly through another business service, interface or product) to a client of the related function for the service.
 |  | 
| − | * Naming:  Should use verb-noun.  May use an "ing" ending.
 |  | 
| − | 
 |  | 
| − | ==== SSC Services ====
 |  | 
| − | SSC Services are usually business <u>functions</u>, and should not be represented as ArchiMate business <u>services</u>.
 |  | 
| − | * Representation:  Must be represented as a business function, with category of "client-facing service" or "supporting service"
 |  |