251
edits
Changes
Introduction to Modeling - Archimate in Qualiware (view source)
Revision as of 12:38, 16 April 2019
, 12:38, 16 April 2019no edit summary
** Find the Catalog service you want in the dialog box that appears, and select the service.
** Find the Catalog service you want in the dialog box that appears, and select the service.
** Click OK – to reuse that object in your diagram.
** Click OK – to reuse that object in your diagram.
== Object Reuse ==
* Cardinal Rule 1: '''DON’T RECREATE any EXISTING OBJECT.'''
** ALWAYS search for the object you want before creating a new one. Reuse existing objects, where appropriate, ALWAYS.
*** For example, you want to show that a process in your function uses another SSC Service. Place a BusinessFunction on your diagram, and right-click on it before giving it a name. Scroll through the list of existing functions to find that SSC Service.
** That said, it’s OK to create functions of the same name as existing functions if they are indeed unique/different than those existing functions. E.g.: 2 different SSC catalog services may have 2 different functions called “Request Fulfilment”… if indeed they are 2 different request fulfillment processes.
*** This reuse of objects is what creates the rich, connected model that we need to produce appropriate reporting and deliverables in future.
*** If you accidentally create a duplicate object, be sure to delete it to prevent others from also using that duplicate object in other models.
== Catalog Service from Blueprint ==
* So, you’ve started your new diagram, and placed the SSC Catalog Service business function on it.
* Now, you’ll need to find your reference material – in this case, an SSC Service Blueprint document for your SSC Catalog Service.
* Many service blueprints can be found here https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objId=3595626&objAction=browse
* Description: The Service blueprints cover the main business functions, processes, clients, and high-level service team roles for a service. These are the things you will place on 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
* 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.
* 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 Lead
** Service Subject Matter Expert
** Service Architect
* What (Archimate) Services does this SSC Service provide? To what clients? Represent using BusinessService:Archimate and respectively.
** 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 “Order a new desktop computer”. What’s the request a client is making?
* 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?
* 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
** NOTE: Business Objects should be common terms for the item, not representing format or technology.
* 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 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?