This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
RmHome
>
RmScenarios
>
RmTraceabilityScenarios
>
RmRequirementElaborated
(22 Feb 2010,
IanGreen
)
(raw view)
---++ Scenario T1 - A requirement is elaborated ---++++ Motivation This scenario addresses the progressive development of requirements and design artefacts, and can be considered to represent the ‘left leg of the V'. This process is seldom completed in one iteration, so there is a need to support the process of development as well as representing the end state. ---++++ Pre-conditions A requirement exists that is to be elaborated. This requirement is referred to as the 'root requirement'. ---++++ Scenario 1 Alternative elaboration strategies are considered and (optionally) recorded. If recorded, this may be: 1 as a separate argument artefact that is linked to the root requirement, or 1 as a property of the root requirement. 1 Existing lower level requirements are reviewed to identify candidates that could potentially satisfy the root requirement. 1 Any issues (missing information, risks, etc) are identified, recorded, and linked to the root requirement (or argument artefact, if it exists). 1 Any supporting evidence for the elaboration strategy (reference documents, models, etc) is identified, recorded, and linked to the root requirement (or argument artefact, if it exists). 1 A final elaboration strategy is chosen and (optionally) recorded in the argument. 1 Existing lower level requirements that support the chosen elaboration strategy are linked to the root requirement. 1 New requirements needed to support the chosen elaboration strategy are created and linked to the root requirement. 1 Outstanding issues are 'worked' until they are closed. 1 Closure of issues may require changes to any artefact (requirements, arguments, supporting evidence), creation or deletion of artefacts, or changes to traceability. 1 Issue artefacts should include a status property. ---++++ Post-conditions The root requirement is supported by a collection of linked lower-level requirements. Rationale for the elaboration is (optionally) recorded, and supported by relevant evidence. Issues affecting completion of the elaboration are closed. ---++++ Notes This scenario describes a variety of artefacts (requirements, arguments, supporting evidence, issues) that are linked in some way. The nature of these links differs depending upon the artefacts that are linked together (e.g. requirements are linked to other requirements via 'satisifies' relationships, issues are linked to requirements via 'impacts' relationships). This scenario would therefore benefit from explicit [[RmDiscussionLinkTypes][typing of links]]. -- Main.SimonWills - 05 Feb 2010
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 22 Feb 2010 - 17:17:17 -
IanGreen
Main.RmRequirementElaborated moved from Main.RequirementElaborated on 22 Feb 2010 - 17:17 by
IanGreen
-
put it back
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback