Skip to content
Snippets Groups Projects
Commit a9d7453e authored by Marko Rintamäki's avatar Marko Rintamäki
Browse files

Update semat-essence.md

parent db478b36
No related branches found
No related tags found
No related merge requests found
Pipeline #442104 passed with warnings
...@@ -51,10 +51,15 @@ Any underlying problems and their root causes have been identified. ...@@ -51,10 +51,15 @@ Any underlying problems and their root causes have been identified.
## REQUIREMENT ## REQUIREMENT
**Conceived**
- [ ] The initial set of stakeholders agrees that a system is to be produced. - [ ] The initial set of stakeholders agrees that a system is to be produced.
- [ ] The stakeholders that will use the new system are identified. - [ ] The stakeholders that will use the new system are identified.
- [ ] The stakeholders that will fund the initial work on the new system are identified. - [ ] The stakeholders that will fund the initial work on the new system are identified.
- [ ] There is a clear opportunity for the new system to address. - [ ] There is a clear opportunity for the new system to address.
**Bounded**
- [ ] The stakeholders involved in developing the new system are identified. - [ ] The stakeholders involved in developing the new system are identified.
- [ ] The stakeholders agree on the purpose of the new system. - [ ] The stakeholders agree on the purpose of the new system.
- [ ] It is clear what success is for the new system. - [ ] It is clear what success is for the new system.
...@@ -64,6 +69,9 @@ Any underlying problems and their root causes have been identified. ...@@ -64,6 +69,9 @@ Any underlying problems and their root causes have been identified.
- [ ] The prioritization scheme is clear. - [ ] The prioritization scheme is clear.
- [ ] Constraints are identified and considered. - [ ] Constraints are identified and considered.
- [ ] Assumptions are clearly stated. - [ ] Assumptions are clearly stated.
**Coherent**
- [ ] The requirements are captured and shared with the team and the stakeholders. - [ ] The requirements are captured and shared with the team and the stakeholders.
- [ ] The origin of the requirements is clear. - [ ] The origin of the requirements is clear.
- [ ] The rationale behind the requirements is clear. - [ ] The rationale behind the requirements is clear.
...@@ -73,15 +81,24 @@ Any underlying problems and their root causes have been identified. ...@@ -73,15 +81,24 @@ Any underlying problems and their root causes have been identified.
- [ ] The priority of the requirements is clear. - [ ] The priority of the requirements is clear.
- [ ] The impact of implementing the requirements is understood. - [ ] The impact of implementing the requirements is understood.
- [ ] The team understands what has to be delivered and agrees to deliver it. - [ ] The team understands what has to be delivered and agrees to deliver it.
**Acceptable**
- [ ] The stakeholders accept that the requirements describe an acceptable solution. - [ ] The stakeholders accept that the requirements describe an acceptable solution.
- [ ] The rate of change to the agreed requirements is relatively low and under control. - [ ] The rate of change to the agreed requirements is relatively low and under control.
- [ ] The value provided by implementing the requirements is clear. - [ ] The value provided by implementing the requirements is clear.
- [ ] The parts of the opportunity satisfied by the requirements are clear. - [ ] The parts of the opportunity satisfied by the requirements are clear.
- [ ] The requirements are testable. - [ ] The requirements are testable.
**Addressed**
- [ ] Enough of the requirements are addressed for the resulting system to be acceptable to the stakeholders. - [ ] Enough of the requirements are addressed for the resulting system to be acceptable to the stakeholders.
- [ ] The stakeholders accept the requirements as accurately reflecting what the system does and does not do. - [ ] The stakeholders accept the requirements as accurately reflecting what the system does and does not do.
- [ ] The set of requirement items implemented provide clear value to the stakeholders. - [ ] The set of requirement items implemented provide clear value to the stakeholders.
- [ ] The system implementing the requirements is accepted by the stakeholders as worth making operational. - [ ] The system implementing the requirements is accepted by the stakeholders as worth making operational.
**Fulfilled**
- [ ] The stakeholders accept the requirements as accurately capturing what they require to fully satisfy the need for a new system. - [ ] The stakeholders accept the requirements as accurately capturing what they require to fully satisfy the need for a new system.
- [ ] There are no outstanding requirement items preventing the system from being accepted as fully satisfying the requirements. - [ ] There are no outstanding requirement items preventing the system from being accepted as fully satisfying the requirements.
- [ ] The system is accepted by the stakeholders as fully satisfying the requirements. - [ ] The system is accepted by the stakeholders as fully satisfying the requirements.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment