Changes

m
no edit summary
Line 67: Line 67:  
* What are the main business processes for the SSC Service?  Remember, processes imply FLOW and/or Sequence.  They also usually involve data flow, use, creation.  Represent as BusinessProcess:Archimate
 
* What are the main business processes for the SSC Service?  Remember, processes imply FLOW and/or Sequence.  They also usually involve data flow, use, creation.  Represent as BusinessProcess:Archimate
 
* What data is used, created for each function/process?  Where does it come from?  Where does it go?  Represent as BusinessObject:Archimate
 
* What data is used, created for each function/process?  Where does it come from?  Where does it go?  Represent as BusinessObject:Archimate
** NOTE:  Business Objects should be common terms for the item, not representing format or technology.
+
** NOTE:  Business Objects should be common terms for the item, not representing format or technology (e.g.  "Order/Request" not "Word Order Form" or "Database field 26".
 
* Who is creating, using, processing this data?  BusinessRole:Archimate
 
* Who is creating, using, processing this data?  BusinessRole:Archimate
 
* What applications do the functions/processes in this SSC service use? (Use Application Layer, ApplicationComponent:ArchiMate to represent these).
 
* What applications do the functions/processes in this SSC service use? (Use Application Layer, ApplicationComponent:ArchiMate to represent these).
 
* What interfaces (phone, fax, email, web, physical kiosk…) are being used for the SSC Service or any sub-functions?
 
* What interfaces (phone, fax, email, web, physical kiosk…) are being used for the SSC Service or any sub-functions?
 
* What business capabilities are realized/enabled with this SSC Service or any of its sub-functions?
 
* What business capabilities are realized/enabled with this SSC Service or any of its sub-functions?
 +
 +
== Connecting and Associating Objects ==
 +
* ''Coming Soon.''
 +
* Graphical associations may not always make the “hard” connections required for all types of reporting.  In some cases, we will need to make explicit associations in the tool to ensure that sub-functions are connected to parent functions, etc…
 +
* ''[Discussion here about how to ensure that objects are connected for reporting purposes.  What associations are required in particular circumstances, and how to implement them]''
 +
 +
== Governance ==
 +
* Governance roles determine what Governance Actions can be taken based on the user and the state of the diagram
 +
* In the present context, the Governance Roles will be determined by the content captured in the diagram being governed:
 +
*# On the main dialog for the object
 +
*# On the Governance -> Circulation dialog for the object
 +
*