Archi Forum

Archi => Share your Models, Templates and Reports => Topic started by: JacquesTessier on April 18, 2019, 14:50:31 PM

Title: Modelling an Architecture Decision
Post by: JacquesTessier on April 18, 2019, 14:50:31 PM
Hi, I am trying to model architecture decisions. I am struggling with which elements I should be using.
so far I am planning on this
     Architecture decision = outcome
     Assumption = constraint
     Justification = requirement
     subject area = driver
     explaining the issue = assessment
     motivation = goal
    derived requirements = requirement
I need to document the alternatives being considered, the implications of this decision, related decision.. Any suggestions on what I should use?
Title: Re: Modelling an Architecture Decision
Post by: Jean-Baptiste Sarrodie on April 18, 2019, 19:15:04 PM
Hi,

I would map it a bit differently and would suggest the following:

I'm not sure what you mean by "Motivation".

See attached image for suggested relationships.

Regards,

JB
Title: Re: Modelling an Architecture Decision
Post by: JacquesTessier on April 26, 2019, 11:08:54 AM
thank you
any suggestion on what I could use for options. I will need to document each option considered.
Jacques
Title: Re: Modelling an Architecture Decision
Post by: Jean-Baptiste Sarrodie on April 26, 2019, 18:43:04 PM
Hi,

Quote from: JacquesTessier on April 26, 2019, 11:08:54 AM
any suggestion on what I could use for options. I will need to document each option considered.

I'd suggest to keep it simple and simply describe options in the Documentation field of the Architecture Decision.

Regards,

JB
Title: Re: Modelling an Architecture Decision
Post by: jrg1166 on May 08, 2019, 07:23:11 AM
Quote from: JacquesTessier on April 18, 2019, 14:50:31 PM
Hi, I am trying to model architecture decisions. I am struggling with which elements I should be using.
so far I am planning on this
     Architecture decision = outcome
     Assumption = constraint
     Justification = requirement
     subject area = driver
     explaining the issue = assessment
     motivation = goal
    derived requirements = requirement
I need to document the alternatives being considered, the implications of this decision, related decision.. Any suggestions on what I should use?
There was an Architecture Decision Canvas published on this site at one stage,  I have attached a copy that I downloaded that could be useful
Title: Re: Modelling an Architecture Decision
Post by: Jose-Carlos on June 04, 2019, 15:54:53 PM
In my organization, I started to modelize in detail an architecture decision. My problem was that on some models, I could have more than 10 AD which increased the complexity of models.
Finally, I used assessment element with properties describing expected topics. This is more a pragmatic approach than a formal Archimate approach. I have a dedicated model with popular ADs that can be reused on many models in a simple way.
In attachment a copy screen of an AD example.
Title: Re: Modelling an Architecture Decision
Post by: secarch on May 08, 2020, 20:45:26 PM
I would suggest adding the options:
Option 1: xxx
Pros Option 1: aaa
Cons Option 1: bbb
Option 2: yyy
Pros Option 2: ccc
Cons Option 2: ddd
Architecture Decision: (Option 1 or 2)
Rationale of AD: eee   
----
It is good practice to expose the potential options before making AD.