v1.11.4
First, watch the lecture video and read the lecture material, then reply the questions below:
Scenario-based analysis methods, choose the correct statements
SAAM (Software Architecture Analysis Method) concentrates especially on adaptability, portability and maintenance.
ATAM (Architecture Trade-off Analysis Method) considers all quality properties.
MPM (Maintenance Prediction Method) concentrates on maintainability and finding a cost estimate for it.
Which of the following concerns for scenario based methods (ATAM and similar) are true?
Are the scenarios sensible or useful?
Are we able to find the risks or could there be hidden ones yet undiscovered?
Is the prioritization of scenarios correct?
Although beneficial, it might be challenging to get all relevant stakeholders into extensive evalutions (such as in ATAM).
DCAR (Decision-centric architecture review method) tries to be
Light and possible to perform with only 1-2 participants.
Incremental and focus only on quality aspects.
Agile and iterative, consider quality but also other aspects, and be estimable in its evaluation.
More detailed than ATAM.
Mythical "force" concept manifests itself as
Different kinds of things affecting architectural decisions.
Design is directed by quality requirements.
Architects opinions or previous knowledge.
Limiting conditions such as costs or time.
Analysis tools in architecture evaluation, choose the correct statements
Can be useful especially when analysing maintainability and adaptability.
Typically operate on the code level and thus only give static analysis unable of capturing all architectural concern at run-time.
Different tools (metrics, visualisation, ...) can be used together to give get better picture to support evaluation.