- Created by Robert Reiner, last modified on 14. Nov 2018
projectdoc Toolbox
Quality Scenarios document required qualities.
- ID
quality-scenario- Suite
- Parent
- Documentation Type
- Categories
- Tags
Quality scenarios document required qualities. They help to describe qualities of a product in a precise manner, including information about the environment, stimulus and response. This allows to evaluate and discus project qualities.
Properties
The document type quality scenario provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
Type
Define the type of the quality scenario for grouping and selecting.
- general
- The quality scenario is not bound to a particular system.
- example
- The quality scenario is an example for general scenario, but is not bound to a particular system
- concrete
- The quality scenario is system-specific.
You may also remove the macro value and replace it with a Name List Macro and its own type.
Qualities
A scenario is typically bound to one Quality, but you may specify more than one here.
Requirements
A scenario is typically bound to one Requirement, but you may specify more than one here.
Business Importance
Specify the importance of this requirement according to business goals.
You may also remove the macro value and replace it with a Name List Macro and its own type. You may also use the Priority Macro, if you require more categories.
Technical Difficulty
Specify the difficulty to implement this requirement from a technical view.
You may also remove the macro value and replace it with a Name List Macro and its own type. You may also use the Priority Macro, if you require more categories.
Sections
Description
Introduce the reader to the the scenario.
Business Goals
List the business goals reached, if this scenario passes its test.
Details
Provide information about the scenario.
Keep in mind that it is not necessary to add information for each section.
Source of Stimulus
Describe the entity that is responsible for the stimulus. May be more than one entity.
Stimulus
Describe the condition to be considered by the system on arrival.
Environment
Describe the conditions that influence the system on arrival of stimulus.
Artifact
Describe the artifact within its environment that is affected by the stimulus and produces a response.
Response
Describe the activity of the artifact in response to the stimulus.
Response Measure
Describe the measurements of the response. To test the quality, these figures show how to determine failure or success.
Test
Provide additional information about tests that proof the correct implementation of the required quality. This may include references to real test results.
Related Scenarios
Scenarios of this Family
List quality scenarios that are children of this scenario.
Scenarios from other Areas
List any quality scenarios that are related to this scenario and are not children of this scenario.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
The text of notes sections is also indexed.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
For further information please refer to References and Resources.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
For further information please refer to References and Resources.
Related Doctypes
- Quality
- Qualities describe desired aspects of the product.
- Quality Scenario Type
- Quality scenario types categorize quality scenarios.
- Test Case
- Document a test case of your project.
- Test Case Type
- Test case types categorize test cases.
- Test Charter
- Defines a charter to run an exploratory test session.
- Test Charter Type
- Test charter types categorize test charters.
- Test Data
- Document data used for test cases.
- Test Data Type
- Test data types categorize test data.
- Test Report
- Documents the results of a test session for the sponsoring stakeholders.
- Test Report Type
- Test report types categorize test reports.
- Test Session
- Defines a document to collect information during a test session.
- Test Session Type
- Test session types categorize test sessions.
