# IT:AD:ArchiMate #



<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See also:
    * [[IT/AD/OMG/]]
    * [[IT/AD/Enterprise Architect/]]
    * [[Business/Concepts/]]
    * [[IT/AD/Requirements/]]
	* [[IT/AD/Supplemental Specifications/]]
	* [[IT/AD/Design/Blueprints/]]
    * [[IT/AD/


</callout>


<panel title="Summary">



Restrained Vocabulary to elicit the Value of Motivations and Critical Success factors.


</panel>


## ACiD Summary ##

* Advantages:
    * Similar to UML, making it easy to pick up.
    * Version 2 aligned with TOGAF
    * adds value to capturing business stakeholders, motivations, goals, principles, drivers.
    * Includes means to capturing Migration planning, Operation and Decommissioning (see [[IT/AD/ADM/]]
* Considerations:
    * Requires a bit of investment to learn the symbols and approach -- it's not a Natural Language approach.
* Disadvantages:
    * ?


## Notes ##

### Business View ###

* Business View:
  * an `Actor` can be assigned to 1-* `Role`s, 
  * A `Business Product` is a coherent set of `Business Service`s.
  * A `Business Service` is realized by one or `Business Functions` initiated by `Business Events`.
  * `Business Functions` group a flow of `Business Proccesses` offered by a `Business Organisation`:
    * Business Processes are performed by Roles
    * Business Processes can be Business Interaction (ie a Process involving two Roles).
    * Either may involve Business Objects
      * That are manifested as `Representations`
      * And may be constrained by `Business Contracts`


<uml>
!includeurl http://skysigal.com/_media/resources/configuration/plantuml/archimate.txt

class Product <<$businessProduct>>
class Service <<$businessService>>
class Function <<$businessFunction>>
class Process <<$businessProcess>>
class Interaction <<$businessInteraction>>
class Object <<$businessObject>>
class Contract <<$businessContract>>

Product *- "0-*" Service : comprised of 
Service *- "0-*" Function  : ...
Function *- Process 
Event -- Function
Role -- Process 

</uml>



## Examples ##

{{ :it:ad:archimate:archimate_concepts.gif?nolink&600 |}}


## PlantUML ##

With plantuml, you can get close enough for many cases:

<uml>

!includeurl http://skysigal.com/_media/resources/configuration/plantuml/archimate.txt

class "Handle claim" as HC <<business>> <<$businessProcess>> 
class "Capture Information" as CI <<$businessProcess>> <<business>> 
class "Notify\nAdditional Stakeholders" as NAS <<$businessProcess>> <<business>> 
class "Validate" as V <<$businessProcess>> <<business>> 
class "Investigate" as I <<$businessProcess>> <<business>> 
class "Pay" as P <<$businessProcess>> <<business>> 

HC *-down- CI
HC *-down- NAS
HC *-down- V
HC *-down- I
HC *-down- P

CI -right-> NAS
NAS -right-> V
V -right-> I
I -right-> P

class "Scanning" as scanning <<$applicationService>> #A9DCDF
class "Customer admnistration" as customerAdministration <<$applicationService>> #A9DCDF
class "Claims admnistration" as claimsAdministration <<$applicationService>> #A9DCDF
class Printing  <<$applicationService>> #A9DCDF
class Payment  <<$applicationService>> #A9DCDF

scanning -up-> CI
customerAdministration  -up-> CI
claimsAdministration -up-> NAS
claimsAdministration -up-> V
claimsAdministration -up-> I
Printing -up-> V
Printing -up-> P
Payment -up-> P

</uml>







## Resources ##
* https://pubs.opengroup.org/architecture/archimate3-doc/chap08.html#_Toc489946052
* http://blog.bizzdesign.com/archimate-core-concepts
* http://bizshifts-trends.com/2013/11/06/key-business-driver-major-impact-business-performance-managing-value-innovation-growth-sustainability/
* http://www.slideshare.net/LouwLabuschagne1/enterprise-communication-using-archimate (Specifically slide 28 onwards).