If you see value in writing quality attribute scenarios to help you create or select software architecture, then you're likely a disciplined software architect (or apprentice) who takes the role seriously. The six-part approach for writing quality attributes is difficult to get used to; it requires practice. It's much easier to get started from working examples. You're invited to buy a comprehensive set of well written quality attribute scenarios. The catalog of 50 scenarios was gathered from dozens of actual software architecture design documents and some of the scenarios were written from scratch just for this catalog.
About this catalog:
1. You will be able to pick, copy and paste, and customize scenarios to apply immediately on your project.
2. You will learn by observing the structure of the existing well written scenarios.
3. Microsoft word format will make it easy for you to copy and paste.
Sample scenario:
Thirty One
|
Scenario Name:
|
|
Scenario(s):
|
The system provides failover on the Servlet Container
|
|
Business Goal(s):
|
Eloquently handle general failures
|
|
Relevant Quality
Attributes:
|
Availability
|
|
Scenario Components
|
Stimulus:
|
Servlet container failure
|
|
Stimulus Source:
|
Internal (unspecified)
|
|
Environment:
|
Normal operating environment (runtime)
|
|
Artifact (If Known):
|
A Servlet container failure
|
|
Response:
|
Detect a fault, perform provide failover, and recover fully
|
|
Response Measure:
|
Detect a fault within 1 second, provide failover within 15 seconds, and fully recover from failure within 2 minutes
|
|
Questions / Risks / Issues:
|
|