wiki

Changes

SSC Architecture Modeling Conventions (view source)

Revision as of 20:02, 19 September 2019

1,427 bytes added ,  20:02, 19 September 2019
m
no edit summary
Line 1: Line 1: −
Business Functions:   
+
 
 +
==== 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.
 
A logical grouping of related business activity (processes, sub-functions, roles, business information, etc...)  No flow or sequence is necessary.
−
- Must always (directly or indirectly) support an established Business Capability, and should be associated with an enterprise requirement, strategic outcome, goal, and/or driver.
+
* Linking:  Must (directly or indirectly) support and link to an established Business Capability
−
- Naming convention:  Should NOT use verb-noun naming, in order to not be confused with business processes.
+
* 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 Process: 
+
==== Business Object ====
 +
* Naming:  Business object names should be nouns.
 +
 
 +
==== Business Process ====
 
Something that is done/performed, that has a flow or sequence.   
 
Something that is done/performed, that has a flow or sequence.   
−
- Should be related to a particular (superior) business function.
+
* 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
+
* 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: 
+
==== Business Service ====
 
Something that is provided to an entity external to the business function.
 
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.
+
* Must link directly (or indirectly through another business service, interface or product) to a client of the related function for the service.
−
- Naming convention:   May use an ing ending?
+
* Naming: Should use verb-noun.  May use an "ing" ending.
   −
Application Data: 
+
==== SSC Services ====
−
- Should, where possible, be linked to a business object.
+
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"
Retrieved from "https://wiki.gccollab.ca/Special:MobileDiff/12433"