Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Medspiration</strong> MED-SOC-RS-001_1<br />
<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong> Issue F<br />
APPENDIX A TRACE BETWEEN USER REQUIREMENTS AND SYSTEM REQUIREMENTS<br />
This appendix contains two large tables which facilitate cross-referencing between the three reference documents [RD-1, RD-2 and RD-3] and the<br />
system requirements presented in the main body of this document. Table A1 segments the text in the reference documents (except for sections that are<br />
clearly out of the scope of <strong>Medspiration</strong>) and assigns unique identifiers to each statement, alongside the document page number and any relevant table,<br />
rule or figure numbers. The right hand column of this large table shows the SRs which can be traced back to the statement. Alternatively the statement<br />
is judged to be one which is intended to provide background information, or (in the case of [RD-3]) is out of the scope of <strong>Medspiration</strong>. In this case the<br />
entry is not a software requirement (NASR).<br />
Table A2 provides the reverse reference, from a systematic list of SRs back to the IDs of the reference document statements (as defined in Table A1)<br />
from which they are derived or which have influenced their definition. This arrangement using two tables should facilitate the following:<br />
• Checks to ensure that the system functionality required by the reference documents is fully reflected in the <strong>System</strong> requirements.<br />
• A means of rapidly cross-referencing those parts of the reference documents which relate to each of the system requirements.<br />
Not all SRs have a trace back to the reference documents. For these, their origin should be apparent from their context in this document. In many<br />
cases they relate to internal requirements such as internal interfaces or system controllers which are essential for the specification of a consistent<br />
overall system. Where there are discrepancies between the SR and the reference to which it is traced, this should be explained in the comments<br />
following the SR in the main body of this document, or will be discussed in the Design Justification File (DJF).<br />
© 2004 SOC Page 88 of 193
Change language