Return to HomePage

---

Summary

Scenarios and Solutions provide fast before and after skeletal views of end to end application scenarios. They are a modular content type that organizes and links end-to-end application scenarios (scenario/backdrop/context) to solution assets (patterns, how tos, reference architectures, blocks.)

---

Schema

* Scenario
* Key Characteristics
* Solution
* How To
* Pitfalls
* Analysis
* Questions and Answers
* Additional Resources
* Related Items

---

Test Cases

Title
* Does the title distinguish by product or version where possible?
* Are important nouns a user might scan for towards the left of the title?

Scenario
* Does it describe the architectural representation of the scenario using diagrams?
* Are the diagrams skeletal view of the scenario?

Key Characteristics
* Does it list all the key characterstics which might impact the solution?

Solution
* Does it describe the architectural representation of the solution using diagrams?
* Are the diagrams skeletal view of the solution?
How To
* Does the how to list all the steps required to implement the solution?
* Are the steps precise and concise?
* Does it help successfully implement the solution?
* Are there relevant links available for more detailsed information on the how to steps?
Pitfalls
* Are all the pitfalls listed in context to the solution?
Analysis
* Are all the design decisions made for arriving at the solution analyzed?

Additional Resources
* Are the links from trusted sites?
* Are the links correct in context of the Senarios and Solutions?

Related Items
* Are the correct items linked in context of the Scenarios and Solutions?

---

Examples

* Scenarios and Solution Example

---

Template

* Scenarios and Solution Template

---

Criteria

Scenarios and Solutions are designed with the following criteria:
* Scenarios and Solutions are modular (5 to 10 pages)
* Problem/Solution is quickly consumable (Key points within 5 minutes or less)
* Scenarios and Solutions point to depth implementation solutions as appropriate (How tos, Blocks, Patterns, articles, documentation ... etc.)
* Scenarios and Solutions can be easily cataloged with multiple viewpoints (operational requirements, functional requirements, deployment scenarios ... etc.)
* Scenario sets the backdrop for Solution Assetts (Blocks, Patterns, Reference Architectures, How Tos)
* Scenarios are end-to-end application problems, both functional and non-functional requirements
* Scenarios are prioritized around key challenges

---

Links

* Archived Scenario and Solution Schema
* Scenarios and Solution Example
* Scenarios and Solution Template

---

Return to HomePage