Date: 8th October 2002
Documentation based on the DTD.
Elements which are not described below may be found in Common XML for Requirements and Solutions.
See also XML for Structured Requirements.
Contents: (title, author+, introduction?, solution*)
|date||required||text||Date of release.|
|version||required||text||Version number for identification.|
|requirements||required||text||The URL of the corresponding requirements document (with .html extension).|
Contents: (summary, details?, (solution | impact)*)
|tag||required||text||Brief tag to identify the element in the hierarchy.|
|status||optional||(pending | adopted | rejected)||An indication of whether or not the solution element has been adopted by the project.|
|risk||optional||(high | medium | low)||The risk associated with the solution idea, that is, the probability that the solution will not succeed given that it is adopted. The risk could be a technical risk inherent in the solution or could be a wider risk affecting the ability of the project team to deliver the solution.|
Contents: (figure, justify?)
In the case of a function element, the impact of a solution is that it either achieves or does not achieve the function specified. In the case of a quality element, the solution may contribute to some extent towards the planned level.
|refersto||required||text||The full path-name of the requirement being impacted.|
|type||required||(achieves | absolute | relative)||If the impact refers to a function then it is of type achieves. If it refers to a quality or resource element then there are two possibilities. If the effect of adopting the solution is determined by adding quantity to the current level of the quality or resource element then the type is relative. If the effect of adopting the solution is to set the level at quantity then the type is absolute.|
© University of Leicester 2002. Please send any comments and bug reports to S.Ambler@mcs.le.ac.uk.