ARC-001 Software Architecture Methodology

Project: ___________________________
Account: ___________________________

General information
Subject

< system, application, solution, etc that is subject of the workshop>

Date

Workshop duration

Workshop lead
(facilitator)
< The lead facilitates discussions, and ensures that the method is carried out
in a timely fashion and that the required QAW artifacts are produced>
Workshop scribe

< The scribe captures the raw scenarios, their prioritization, the refined
scenarios, and any relevant issues that emerge during the workshop
meeting, and responsible for finalizing this document after the meeting >
Business/Mission
presentation by
< A business authority stakeholder, who presents business context/missions
context and high-level requirements >
Architectural plan
presentation by
< A technical authority stakeholder, who presents strategies for satisfying
business requirements, mandated technical constraints, existing system’s
design >
Other Attendees

< The rest of respresentative stackeholders community >

<Filled in by QAW lead before start>

Input materials
Material item Location

< Any relevant materials mentioned during the workshop: documents, presentations, etc.. This section
may be partially filled before meeting by workshop facilitator lead, completed after the meeting by
workshop scribe, or may be skipped. >

1
 ARC-001 Software Architecture Methodology
A. Problem Background
<Information of this section should to be known before the workshop. The workshop can fill some gaps,
like missed stakeholder groups >

1. System Context
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
<Business model of organization(s) intended to use the system, business-processes. Existing IT landscape.
Development organization’s circumstances >

2. Mission and Scope

___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
< What is system’s mission – how introduction of this system will help to make someone’s life easier.
Scope: what are key capabilities (features) system should provide to fulfill its mission >

3. Stakeholders
Stakeholder Concerns

< List stakeholder (keep in mind different groups of stakeholders) >

4. Business Goals / Objectives

N Description
1
2
3
4
5
6
< Any business goals (market position, operational efficiency, IT TCO reduction, improvement of system’s
capability or end-user confidence and perception), captured by attendees during Business/Mission
Presentation, that are significant for identification of quality-attribute architectural drivers. This section
may be partially filled before meeting by business stakeholder, completed after the meeting by QAW
scribe, or may be skipped. >

2
 ARC-001 Software Architecture Methodology
B. Workshop Output

1. Architectural Drivers (Architecturally Significant Requirements - ASRs)

N Description Derived from
goals

< Architectural drivers of paying attention to particular quality attributes, captured by attendees during
Architectural Plan Presentation and Architectural Drivers Identification phases that are originated from
the business context. All drivers in the list should be considered during scenarios brainstorming. This
section may be partially filled before meeting by technical stakeholder, completed after the meeting by
QAW scribe, or may be skipped. >

2. Consolidated and Prioritized Scenarios

N Description ASRs Votes

< Final list of scenarios answer the architectural drivers and business concerns: after brainstorming,
reformulating into testable form (stimulus, environment, and response), consolidation of similar
scenarios, and prioritization by attendees voting. >

3
 ARC-001 Software Architecture Methodology
3. Refined Scenarios
Example:
Scenario Refinement for Scenario <scenario number>
< scenario description.
e.g. “When a garage door opener senses an object in the door’s path, it stops
Scenarios(s):
the door in less than one millisecond.” >

< business goal, that affected the scenario.

Business Goals: e.g. “Safest system; feature-rich product.”>

< Relevant quality attributes, associated with the scenario

Relevant Quality
e.g. “safety, performance” >
Attributes:

< Relevant quality attributes, associated with the scenario

Stimulus: e.g. “An object is in the path of a garage door” >

< Relevant quality attributes, associated with the scenario

Stimulus
e.g. “Object external to the system such as bicycle” >
source:
Scenario Components

< Relevant quality attributes, associated with the scenario

Environment: e.g. “The garage door is in process of closing” >

< Relevant quality attributes, associated with the scenario

Artifact
e.g. “system’s motion sensor, motion-control software component” >
(if known):
<activity that must result from stimulus,
Response: e.g. “The garage door stops moving” >

<measure by which system’s response may be evaluated, e.g. dialog window

Response
displayed to the user with all data filled in less than 2 seconds after user click>
Measure:
< any unresolved questions to the scenario, may result in follow-up
refinement
Questions: e.g. “How large must an object be before it is detected by the system’s
sensor?” >

< Issues raised regarding scenario, to be handled separately

e.g. “May need to train installers to prevent malfunctions and avoid
Issues:
potential legal issues.”>

< Refined description of all scenarios that threshold some defined prioritization limit. >

4
 ARC-001 Software Architecture Methodology
Scenario Refinement for Scenario N
Scenarios(s):

Business Goals:
Relevant Quality
Attributes:

Stimulus:

Stimulus
Scenario Components

source:
Environment:
Artifact
(if known):
Response:
Response
Measure:
Questions:

Issues:

Scenario Refinement for Scenario N

Scenarios(s):

Business Goals:
Relevant Quality
Attributes:

Stimulus:

Stimulus
Scenario Components

source:
Environment:
Artifact
(if known):
Response:
Response
Measure:
Questions:

Issues: