251
edits
Changes
Introduction to Modeling - Archimate in Qualiware (view source)
Revision as of 13:20, 19 September 2019
, 13:20, 19 September 2019Major fixes and updates to content.
{{Under construction}}
{{Under construction}}
This guide is intended for SSC architects modeling using ArchiMate in Qualiware. Currently, it focuses on very high-level business modeling, specifically about SSC Catalog Services.
This guide is intended for SSC architects modeling using ArchiMate in Qualiware. Currently, it focuses on very high-level business modeling, specifically about SSC Services.
== Login to QualiWare ==
== Login to QualiWare ==
* Select Configuration "Base Configuration" (the default - in future this may change).
* Select Configuration "Base Configuration" (the default - in future this may change).
== Starting a New Model: SSC Catalog Service ==
== Starting a New Model: SSC (Client-facing or Supporting) Service ==
* Click on the “ArchiMate” folder at the bottom left of the screen.
* Click on the “ArchiMate” folder at the bottom left of the screen.
* Select “LayeredViewpoint:ArchiMate”.
* Select “BusinessProcessCoopViewpoint:ArchiMate”.
* Don’t forget to follow the metamodel:
* Don’t forget to follow the metamodel:
** Guidance: Content Metamodel
** Guidance: Content Metamodel
** Guidance: Content Guidelines
** Guidance: Content Guidelines
*Create a new “LayeredViewpoint: ArchiMate”[[File:ArchiMate Icon.png]]
*Create a new “BusinessProcessCoopViewpoint: ArchiMate”[[File:ArchiMate Icon.png]]
*Give it a name: “Catalog Service: YOURFULLSERVICENAMEHERE”. E.G.: "Catalog Service: Mobile Devices"
*Give it a name: “Client-facing Service: YOURFULLSERVICENAMEHERE”, e.g.: "Client-facing Service: Mobile Devices".
== Modeling the Service ==
== Modeling the Service ==
Note: At SSC, we represent SSC Services with ArchiMate Business Functions.
Note: At SSC, we represent SSC Services with ArchiMate Business Functions.
* The first object you’ll want to place on your diagram is the function that represents your SSC Catalog Service. This object should already exist in the tool. It will be of type “BusinessFunction:ArchiMate”.
* The first object you’ll want to place on your diagram is the function that represents your SSC Catalog Service. '''This object should already exist in the tool'''. It will be of type “BusinessFunction:ArchiMate”.
* Find the appropriate object by:
* Find the appropriate object by:
**Create a BusinessFunction:ArchiMate object on the diagram, and right-click on the default name of the object. [It’s important to right-click directly on the highlighted “New BusinesFunction:Archimate” text.[[File:New Bus Function Archimate.png]]
**Create a BusinessFunction:ArchiMate object on the diagram, and right-click on the default name of the object. [It’s important to right-click directly on the highlighted “New BusinesFunction:Archimate” text.[[File:New Bus Function Archimate.png]]
== Things to consider/cover in your Model ==
== Things to consider/cover in your Model ==
* Who are the clients for this SSC service? Any Partner, a specific type of partner? Represent with BusinessActor:Archimate
* Who are the clients for this SSC service? Any Partner, a specific type of partner? Represent with '''BusinessActor:Archimate'''
* What things does this service do specifically for those clients? These "exposed business behaviours" are modeled (somewhat confusingly) using '''BusinessService:Archimate''' objects.
** These services are what, exactly, a client can expect to receive from this service. It’s unlikely to be the name of the SSC service like “Video Conferencing”, but more like “Request a videoconference account”, or “Ordering a new desktop computer”. What’s the request a client is making?
* Does this service use the SSC Enterprise Service Desk?
* Does this service use the SSC Enterprise Service Desk?
** If so, you may wish to drop that Business Function on your diagram as a starting point – it already exists in the system.
** If so, you may wish to drop that Business Function on your diagram as a starting point – it already exists in the system.
* What roles/actors are responsible for this SSC service? These should be assigned to the service and represented as BusinessRole:Archimate objects:
* What roles/actors are responsible for this SSC service? These should be assigned to the service and represented as '''BusinessRole:Archimate''' objects:
** Service Executive Sponsor
** Service Executive Sponsor
** Service Lead
** Service Lead
** Service Subject Matter Expert
** Service Subject Matter Expert
** Service Architect
** Service Architect
* What are the main (sub) functions for this SSC service? Represent as BusinessFunction:Archimate. You’re breaking down this “SSC Service” into logical portions. Remember, functions are just groups – they don’t have flow or sequence.
* What are the main (sub) functions for this SSC service? Represent as BusinessFunction:Archimate. You’re breaking down this “SSC Service” into logical portions. Remember, functions are just groups – they don’t have flow or sequence.
* Are there any other SSC Services (catalog/technical/supporting) that are used to realize this SSC Service?
* Are there any other SSC Services (catalog/technical/supporting) that are used to realize this SSC Service?
* 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
* Processes generally imply data. What data is used or 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 (e.g. "Order/Request" not "Word Order Form" or "Database field 26".
** NOTE: Business objects should be common (or business) term for the item, not representing particular format or technology, e.g. "Order/Request" not "Word Order Form" or "Oracle Order Table".
* 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? These should be associated with the appropriate business services via a '''BusinesInterface:ArchiMate''' object.
* 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? You should link to any relevant business capabilities using the '''Capability:ArchiMate''' objects.
** You should not create a new business capability. Instead, these capabilities should already be pre-populated in the system for you.
== Connecting and Associating Objects ==
== Connecting and Associating Objects ==
Full descriptions of how to make relationships between objects can be found in the ArchiMate 3.0.1 Specification. Some key relationships to consider however are:
* Between processes there is usually a '''flow''' relationship.
* ''[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]''
* Functions and processes '''access''' business objects (data/information).
* Once you've made your associations in the background, <u>generating a Context View</u> on an object can help you quickly get a visual of the associationsR:
* Roles are '''assigned''' to processes/functions.
*# Right-click your object and select Properties
* Services '''realize''' functions or processes.
*# Expand Associate --> select RelationContext
* Processes comprise ('''composition''') functions.
*# Near bottom-right, select Create Context View
* If you do not know what the most appropriate relationship is between an object, then simply '''associate''' them. Associations will always work.
Note: 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… These are accomplished in Qualiware by using the properties menu, and inserting objects as "Implements" or "Breaks down to" or other associations within the tool.
Hint: Once you've made your associations in the background, <u>generating a Context View</u> on an object can help you quickly get a visual of the associations:
# Right-click your object and select Properties
# Expand Associate --> select RelationContext
# Near bottom-right, select Create Context View
== Governance ==
== Governance ==
* Governance roles determine what Governance Actions can be taken based on the user and the state of the diagram
* Governance roles determine what Governance Actions can be taken based on the user and the state of the diagram