Scenario Documentation
The following are templates filled out for scenarios for illustration not completeness.
(H,H) Scenario | Port new to Operating System | |||
Attributes | Portability | |||
Environment | Operating system | |||
Stimulus | New Device | |||
Response | The developers deliver a production quality PAMD Image that supports new device within two months. | |||
Architectural Decisions | Sensitivity | Tradeoff | Risk | Nonrisk |
(H,H) Scenario | Port new hardware to existing infrastructure and operating system(s)>\. | |||
Attributes | Portability | |||
Environment | N/A for now | |||
Stimulus | A new device is selected to inclusion into the ecosystem. | |||
Response | PAMD developers deliver a production quality PAMD images is developed for the new device within 2 months (business) or 1 year (IT Arch). [Negotiated to 6 months between Business Owner and IT Architect] | |||
Architectural Decisions | Sensitivity | Tradeoff | Risk | Nonrisk |
(H,H) Scenario | Data type incompatibility | |||
Attributes | Reliability | |||
Environment | Run-time | |||
Stimulus | The data type understood by the application changes, without an updated plug-in | |||
Response | The system raises an error, informing the user that the data type is incompatible. | |||
Architectural Decisions | Sensitivity | Tradeoff | Risk | Nonrisk |
(H,H) Scenario | Loading PAMD plug-ins and applications | |||
Attributes | Reliability | |||
Environment | ||||
Stimulus | User loads 1 additional plug-in or applications that exceeds the system capacity limits. | |||
Response | The system responds by loading the new plug-in or application without crashing. | |||
Architectural Decisions | Sensitivity | Tradeoff | Risk | Nonrisk |
Here is the clearest definitions I could come up with:
Risk – a clear risk to the architectural design relative to a single quality attribute.
Nonrisk – a good decision.
Tradeoff – two quality attributes are being balanced here.
Sensitivity Point – a single quality attribute is impacted by