19
Testing Requirements • Make the Requirement Measurable • Quantifiable and non- Quantifiable – Requirements test 1 • Keeping track • Coherence and Consistency – Requirements test 2 – Requirements test 3

Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Embed Size (px)

Citation preview

Page 1: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Make the Requirement Measurable

• Quantifiable and non-Quantifiable– Requirements test 1

• Keeping track

• Coherence and Consistency– Requirements test 2– Requirements test 3

Page 2: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

Page 3: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Make the Requirement Measurable

• Quantifiable and non-Quantifiable– Requirements test 1

• Keeping track

• Coherence and Consistency– Requirements test 2– Requirements test 3

Page 4: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

Page 5: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

Page 6: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Completeness– Requirements test 4– Requirements test 5

• Relevance– Requirements test 6

• Requirement or Solution– Requirements test 7

• Stakeholder Value– Requirements test 8

Page 7: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

Page 8: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

Page 9: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Completeness– Requirements test 4– Requirements test 5

• Relevance– Requirements test 6

• Requirement or Solution?– Requirements test 7

• Stakeholder Value– Requirements test 8

Page 10: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

6. Is every requirement in the specification relevant to this system?

Page 11: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Completeness– Requirements test 4– Requirements test 5

• Relevance– Requirements test 6

• Requirement or Solution?– Requirements test 7

• Stakeholder Value– Requirements test 8

Page 12: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

6. Is every requirement in the specification relevant to this system?

7. Does the specification contain solutions posturing as requirements?

Page 13: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Completeness– Requirements test 4– Requirements test 5

• Relevance– Requirements test 6

• Requirement or Solution?– Requirements test 7

• Stakeholder Value– Requirements test 8

Page 14: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

6. Is every requirement in the specification relevant to this system?

7. Does the specification contain solutions posturing as requirements?

8. Is the stakeholder value defined for each requirement?

Page 15: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Traceability– Requirements test 9

• Order in a Disorderly World– Requirements test 10

• Conclusion

Page 16: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

6. Is every requirement in the specification relevant to this system?

7. Does the specification contain solutions posturing as requirements?

8. Is the stakeholder value defined for each requirement?

9. Is each requirement uniquely identifiable?

Page 17: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Testing Requirements

• Traceability– Requirements test 9

• Order in a Disorderly World– Requirements test 10

• Conclusion

Page 18: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Requirement Test Questions

1. Does each Requirement have a quality measure that can be used to test whether any solution meets the requirement?

2. Does the Specification contain a definition of the meaning of every essential subject matter term within the specification

3. Is every reference to a defined term consistent with its definition?

4. Is the context of the requirements wide enough to cover everything we need to understand?

5. Have we asked the stakeholders about conscious, unconscious, and dreamed of requirements?

6. Is every requirement in the specification relevant to this system?

7. Does the specification contain solutions posturing as requirements?

8. Is the stakeholder value defined for each requirement?

9. Is each requirement uniquely identifiable?

10. Is each requirement tagged to all parts of the system where it is used? For any change to requirements, can you identify all parts of the system where this change has an effect?

Page 19: Testing Requirements Make the Requirement Measurable Quantifiable and non-Quantifiable –Requirements test 1 Keeping track Coherence and Consistency –Requirements

Source

• Title:Testing Requirements

• Author: Paul Gerrard Systeme Evolutif Ltd.

• Presented: EuroSTAR '94, 10-13 October 1994, Conrad International Hotel, Brussels, Belgium

http://www.evolutif.co.uk/TestReqs/TESTREQS.html