Taxonomy/2. Methodology/Focus (architecture)
Uit Werkplaats
< Taxonomy | 2. Methodology
Versie door Hanno Wupper (overleg | bijdragen) op 2 okt 2011 om 18:02
Problem statement form architecture
Please stay at one level and don't climb up and down! It can be helpful, however, also to fill in a problem statement form for the surrounding artefact.
Problem (a short name for identification) | ||
---|---|---|
Question | Answer | Explanation |
→FOCUS | ||
Goal |
|
|
Fragment of reality | ||
→RATIONALITY SQUARE | ||
→properties | ||
How are the desired →properties (not its design or structure) of the artefact under discussion defined? |
|
|
Can the customer be consulted? Who? | ||
What is the problem domain? | ||
Can a Domain expert for the problem domain be consulted? Who? | ||
→principles and →requirements | ||
Are the →principles of the (organisation of the) →customer known? |
|
|
Are the →reqirements (on a lower level than principles)? |
|
|
If principles and requirements are not fixed: how can it be Validated? | ||
→blueprint | ||
Which blueprint language is (to be) used? Why? | ||
How complete is the blueprint? |
|
|
Do the providers of parts or their Domain experts understand the respective →specification languages from the →blueprint? | ||
How should it be established that the blueprint satisfies the principles and requerements? | ||
How should it be established that the artefact is a correct realisation of the blueprint? | ||
→artefact | ||
How much of the artefact exists? Where? |
|
|
If it does not (fully) exist, how and by whom will it be realised? | ||
What are the solution domains for the missing parts? | ||
Who are the Domain experts for the missing parts and their interfaces? | ||
How can the artefact be Validated w.r.t. a specification? | ||
PLAN | ||
Step | To do | Comment |
1 | ||
2 |