 |
| This artifact contains the definition of the stakeholders' view of the product to be developed, specified in terms of the stakeholders' key needs and features. It contains an outline of the envisioned core requirements for the system. |
Domain: Requirements
Work Product Kinds: Concept |
|
Purpose
This artifact provides a high-level, sometimes contractual, basis for
the more detailed technical requirements that are visible to the Stakeholders.
It captures the essence of the system by describing high-level
requirements and design constraints that give the reader an overview of the
system from a behavioral requirements perspective. It serves
as input for the project-approval process,
communicates the fundamental "what and why" for the project, and provides
a plan against which all future decisions should be validated. |
Relationships
| Roles | Responsible:
| Modified By:
|
| Tasks | Input To:
| Output From:
|
Description
| Brief Outline | This artifact is written from the customers' perspective, focusing on the essential features of the system and
acceptable levels of quality. The artifact should include a description of what features will be included, as well as those considered but not included. It should
also specify operational capacities (volumes, response times, accuracies), user profiles (who will be using the system),
and interoperational interfaces with entities beyond the system boundary, where applicable. |
| Main Description | This artifact provides a complete vision for the software system under development
and supports the contract between the customer and
the development organization. Every project
needs a source for capturing all Stakeholders' expectations. |
Illustrations
Tailoring
| Impact of not having | If this artifact is not used, there is a high risk that Stakeholders and the development
team will have different expectations. This could lead to cancellation of
the project. |
| Representation Options | Tailor this artifact as necessary for your project's needs. It is generally good
practice to keep this artifact brief so you can release
it to Stakeholders as soon as possible, and to make it easy for Stakeholders to
read and understand. You can
accomplish this by including only the most important Stakeholder requests
and features and avoiding details of requirements.
You can describe details in the other requirement
artifacts. |
More Information
|
