Template:REQ: Difference between revisions
From Calidus HUB
No edit summary |
(Updated for latest template versions; added SCR template) |
||
Line 2: | Line 2: | ||
{{#vardefine:Client|The Supimix Client Code}} | {{#vardefine:Client|The Supimix Client Code}} | ||
{{#vardefine:ClientName|The Client Name}} | {{#vardefine:ClientName|The Client Name}} | ||
{{#vardefine:System|''CALIDUS'' Mobile/WMS/TMS}} | {{#vardefine:System|''CALIDUS'' Mobile/WMS/TMS/ePOD}} | ||
{{#vardefine:Doc_Title|Description}} | {{#vardefine:Doc_Title|Description}} | ||
{{#vardefine:Version|0.1}} | {{#vardefine:Version|0.1}} | ||
{{#vardefine:Date|16th June 2011}} | {{#vardefine:Date|16th June 2011}} | ||
{{#vardefine:Reference|Supimix References}} | {{#vardefine:Reference|Supimix References}} | ||
{{#vardefine:Year|Year}} | |||
</div> | </div> | ||
{{Doc_Title | {{Doc_Title | ||
Line 12: | Line 13: | ||
|System={{#var:System}} | |System={{#var:System}} | ||
|Title={{#var:Doc_Title}} | |Title={{#var:Doc_Title}} | ||
|Reference= | |Reference=REQ {{#var:Reference}} | ||
|Version={{#var:Version}} | |Version={{#var:Version}} | ||
|Date={{#var:Date}} | |Date={{#var:Date}} | ||
|Date={{#var:Year}} | |||
}} | }} | ||
Line 34: | Line 36: | ||
<!-- ANY scope or limitations, bulleted. --> | <!-- ANY scope or limitations, bulleted. --> | ||
*The changes will be made in the latest version | *The changes will be made in the latest version of the {{#var:System}} system. | ||
<!-- ANY other systems? e.g. does this link to TTM, WMS, 414, 770, etc? --> | |||
{{ #vardefine: SCR | 0 }} | |||
<!-- NEW PAGE --> | <!-- NEW PAGE --> | ||
Line 55: | Line 58: | ||
<!-- A description of the operational flow for this functional area, as it will be. Reference any operational flow documents produced for the way it is now. | <!-- A description of the operational flow for this functional area, as it will be. Reference any operational flow documents produced for the way it is now. | ||
A functional area isn’t ‘Warehousing’, it’s a sub-section of warehousing. For example, Receipt, Picking, Packing, etc. | A functional area isn’t ‘Warehousing’, it’s a sub-section of warehousing. For example, Receipt, Picking, Packing, etc. | ||
It is important to keep the flow of the text, so that it can be easily understood. So, if an SCR has been identified, reference the SCR here, in bold. Keep the description snappy. Also, include a cross-reference to the SCR numbers in the table at the end of the document, and include the supimix number from the Reference Docproperty. When you identify a gap, | It is important to keep the flow of the text, so that it can be easily understood. So, if an SCR has been identified, reference the SCR here, in bold. Keep the description snappy. Also, include a cross-reference to the SCR numbers in the table at the end of the document, and include the supimix number from the Reference Docproperty. When you identify a gap, use the template 'SCR' as follows: | ||
{{SCR | |||
|Reference={{#var:Reference}} | |||
|SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }} | |||
|Definition=The description of the change required | |||
}} | |||
Then, add the line in the table in appendix A with: | |||
{{REQ_SCR_Line | |||
|SCR={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }} | |||
|System=System Affected | |||
|Area=Area Affected | |||
|Description=Description of change | |||
|Estimate=Cost | |||
|Notes=Any notes, numerically listed | |||
}} | |||
There may be many SCRs for each section. Keep numbering and referencing them. Keep the table in Appendix A updated as you go along. If you re-order the SCR’s in the table, or insert new ones, don’t forget to update the document references. --> | There may be many SCRs for each section. Keep numbering and referencing them. Keep the table in Appendix A updated as you go along. If you re-order the SCR’s in the table, or insert new ones, don’t forget to update the document references. --> | ||