"Requirement Specification" can be Satisfied By what kind of requirement type(Artifact Types), and can Satisfy what kind of requirement type(Artifact Types)?
This is for CLM 4.0.3 and default "Use Case Requirements Template" is used for the project.
The following artifact types are included in this template:
Actor
Feature
Heading
Information
Personal Collection
Process Diagram
Release Collection
Requirement Specification
Sketch
Stakeholder Request
Storyboard
Supplementary
Term
Use Case
Use Case Diagram
We have "Link Types" giving an example of "Satisfaction" type as:
A stakeholder request can be satisfied by features. A feature can be satisfied by use cases and supplemental requirements.
Client wants to know the same for "Requirement Specification": "Requirement Specification" can be Satisfied By what kind of requirement type(Artifact Types), and can Satisfy what kind of requirement type(Artifact Types)?
Or, What level does "Requirement Specification" should be in the requirement hierarchy?
The following artifact types are included in this template:
Actor
Feature
Heading
Information
Personal Collection
Process Diagram
Release Collection
Requirement Specification
Sketch
Stakeholder Request
Storyboard
Supplementary
Term
Use Case
Use Case Diagram
We have "Link Types" giving an example of "Satisfaction" type as:
A stakeholder request can be satisfied by features. A feature can be satisfied by use cases and supplemental requirements.
Client wants to know the same for "Requirement Specification": "Requirement Specification" can be Satisfied By what kind of requirement type(Artifact Types), and can Satisfy what kind of requirement type(Artifact Types)?
Or, What level does "Requirement Specification" should be in the requirement hierarchy?
One answer
The short answer is "it depends on your requirements process".
It's important to be able to do gap analysis and traceability-based reporting involving the individual requirements in the requirements specification; many teams find that it is not as valuable to do this at the specification level (which is a module in RRC / DOORS NG consisting of many individual requirements). Those whodo module linking most commonly use "satisfaction" between requirements specifications as well: for example, a subsystem specification satisfies a higher-level specification (and if you only have one, then that specification satisfies the vision document, stakeholder needs document, etc).
Comments
Thank you very much Daniel for prompt reply.
I actually asked this question for my client David. I'll ask him if he needs further clarification. Cheers!
What is the relationship between requirement specification and use case?
Is a requirement specification higher or lower than a use case?
Thanks you very much.
There is no "one" answer to this: it depends how an organization chooses to organize their information, which depends on how complicated the thing is that the project team is building, conventions in particular industries etc.. For example some organizations have a vision document and/or a customer needs document. These are kinds of "specifications". At the next level of detail could be system-level requirements, use cases and a supplementary (non-functional) requirements. These could be in one specification document or multiple -- it depends what makes the most sense in your context.
It would be interesting to hear from other participants in this forum: what are YOUR main requirements artifacts/documents, and how are they related?