Role
|
Task
|
Procedure
|
||
Analyst
|
Perform impact analysis on a requirement
An impact analysis is commonly performed to analyze a proposed change to a requirement, or to review the implementation of a requirement to make sure it conforms to the requirement.
|
1) Open the requirement and view the traces in the source link field.
2) Select a source trace and select
> > .3) In the Source Trace Viewer, analyze the impact of changing the member by viewing everywhere it is used (
> ).4) Select any other requirement that is implemented by the same member revision and select
> .
5) Review the details of the other requirement to determine if the planned changes to the current requirement will affect it.
|
||
Engineer
|
Implement a requirement (or a change to a requirement)
|
1) Open the requirement and view the content in order to understand the change.
2) View the traces in the source link field in order to see what source files currently satisfy the requirement.
3) Select a source trace to a member that will be changed and select
> > .4) In the Source Trace Viewer, analyze the changes required to the traced member by viewing the revision contents (
> ).5) Select any other requirement that is implemented by the same source file and select
> .
6) Review the details of the other requirement to determine if the planned changes to the current requirement will affect it.
7) Update the source file to be consistent with all requirements.
|
||
Software Engineer
|
Review requirements for a file being changed
|
1) Select the member or revision that needs to be changed and select
> > .2) In the Source Trace Viewer, select any requirement that is implemented by the source file and select
> .
3) Review the details of the other requirement to make sure the planned source file changes will not affect it.
|