Template:REQ - Revision history

Anw: Minor formatting change

2026-02-27T13:27:34Z

Minor formatting change

← Older revision		Revision as of 15:27, 27 February 2026
Line 21:		Line 21:

	<!-- TOC -->		<!-- TOC -->
	~~<div class="noprint">~~
	= Introduction =		= Introduction =
	<!-- The introduction will detail the initial requirements supplied by the client -->		<!-- The introduction will detail the initial requirements supplied by the client -->
Line 123:		Line 122:
	\|Rev1=Rev1		\|Rev1=Rev1
	\|Rev1Title=Rev1 Title		\|Rev1Title=Rev1 Title
	}}~~</div>~~		}}
	[[Category:{{#var:Client}} REQ]]		[[Category:{{#var:Client}} REQ]]
	[[Category:{{#var:SystemCode}}]]		[[Category:{{#var:SystemCode}}]]

Anw: Categorisation of document pages

2019-11-29T09:48:42Z

Categorisation of document pages

← Older revision		Revision as of 11:48, 29 November 2019
Line 3:		Line 3:
	{{#vardefine:ClientName\|The Client Name}}		{{#vardefine:ClientName\|The Client Name}}
	{{#vardefine:System\|''CALIDUS'' Mobile/WMS/TMS/ePOD}}		{{#vardefine:System\|''CALIDUS'' Mobile/WMS/TMS/ePOD}}
			{{#vardefine:SystemCode\|WCS/WMS/TMS/EPOD/MCS/Portal}}
	{{#vardefine:Doc_Title\|Description}}		{{#vardefine:Doc_Title\|Description}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.1}}
Line 124:		Line 125:
	}}</div>		}}</div>
	[[Category:{{#var:Client}} REQ]]		[[Category:{{#var:Client}} REQ]]
			[[Category:{{#var:SystemCode}}]]

Anw: Fixed copyright date

2018-11-28T09:31:36Z

Fixed copyright date

← Older revision		Revision as of 11:31, 28 November 2018
Line 16:		Line 16:
	\|Version={{#var:Version}}		\|Version={{#var:Version}}
	\|Date={{#var:Date}}		\|Date={{#var:Date}}
	\|~~Date~~={{#var:Year}}		\|Year={{#var:Year}}
	}}		}}

Anw at 14:21, 15 January 2013

2013-01-15T14:21:54Z

← Older revision		Revision as of 16:21, 15 January 2013
Line 42:		Line 42:

	= Client Requirements =		= Client Requirements =
	Listed below are the proposed processes that will be followed by the ~~warehouse~~ operatives using ~~Calidus 3pl-Mobile~~. Also shown are the SCRs required for this to be achieved.		Listed below are the proposed processes that will be followed by the operatives using {{#var:System}}. Also shown are the SCRs required for this to be achieved.

	<The current operational process flow has been described in documents produced by X of Y.>		<The current operational process flow has been described in documents produced by X of Y.>

Anw: Updated for latest template versions; added SCR template

2013-01-14T09:03:05Z

Updated for latest template versions; added SCR template

← Older revision		Revision as of 11:03, 14 January 2013
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=FS {{#var: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 ~~3.4~~ of the ~~Calidus 3pl~~-~~Mobile system, and version 4~~.~~14 of the Calidus 3pl system~~.		*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, ~~put~~ the ~~text ‘SCR~~ :~~’ in bold in front~~ of ~~it.~~ Then, add the line in the table in appendix A.		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. -->

Anw at 14:12, 19 August 2011

2011-08-19T14:12:11Z

← Older revision		Revision as of 16:12, 19 August 2011
Line 1:		Line 1:
	<div class="noprint">		<div class="noprint">
	{{#vardefine:Client\|The Supimix Client Code}}		{{#vardefine:Client\|The Supimix Client Code}}
	{{#vardefine:~~Client~~\|The Client Name}}		{{#vardefine:ClientName\|The Client Name}}
	{{#vardefine:System\|''CALIDUS'' Mobile/WMS/TMS}}		{{#vardefine:System\|''CALIDUS'' Mobile/WMS/TMS}}
	{{#vardefine:Doc_Title\|Description}}		{{#vardefine:Doc_Title\|Description}}
Line 107:		Line 107:
	\|Rev1Title=Rev1 Title		\|Rev1Title=Rev1 Title
	}}</div>		}}</div>
	[[Category:{{#var:Client}} FS]]		[[Category:{{#var:Client}} REQ]]

Anw at 14:10, 19 August 2011

2011-08-19T14:10:24Z

← Older revision		Revision as of 16:10, 19 August 2011
Line 107:		Line 107:
	\|Rev1Title=Rev1 Title		\|Rev1Title=Rev1 Title
	}}</div>		}}</div>
	[[Category:~~Test~~]]		[[Category:{{#var:Client}} FS]]

Anw at 08:29, 18 August 2011

2011-08-18T08:29:27Z

← Older revision		Revision as of 10:29, 18 August 2011
Line 1:		Line 1:
	<div class="noprint">		<div class="noprint">
	{{#vardefine:Client\|The Client}}		{{#vardefine:Client\|The Supimix Client Code}}
	{{#vardefine:System\|~~Calidus~~ Mobile/WMS/TMS}}		{{#vardefine:Client\|The Client Name}}
			{{#vardefine:System\|''CALIDUS'' Mobile/WMS/TMS}}
	{{#vardefine:Doc_Title\|Description}}		{{#vardefine:Doc_Title\|Description}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.1}}
Line 8:		Line 9:
	</div>		</div>
	{{Doc_Title		{{Doc_Title
	\|Client={{#var:~~Client~~}}		\|Client={{#var:ClientName}}
	\|System={{#var:System}}		\|System={{#var:System}}
	\|Title={{#var:Doc_Title}}		\|Title={{#var:Doc_Title}}
Line 23:		Line 24:

	== Objective ==		== Objective ==
	The primary purpose of this document is to document the requirements gathered from {{#var:~~Client~~}}, at X, Y, Z		The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at X, Y, Z

	<!-- List all amendments to the requirements here, and reference in final section, e.g. The document also encompasses the follow-up meeting held at X, with Y and Z attending, where the requirements were modified. See the minutes of the meeting referenced as item X in appendix B -->		<!-- List all amendments to the requirements here, and reference in final section, e.g. The document also encompasses the follow-up meeting held at X, with Y and Z attending, where the requirements were modified. See the minutes of the meeting referenced as item X in appendix B -->

	This document has been written in a manner such that it can be approved by non-technical representatives of {{#var:~~Client~~}} whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.		This document has been written in a manner such that it can be approved by non-technical representatives of {{#var:ClientName}} whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.

	== Scope and Limitations ==		== Scope and Limitations ==
	This document is based on the documentation provided by {{#var:~~Client~~}}, as referred to in the appendices, as well as information gleaned from site visits and workshops with {{#var:~~Client~~}}.		This document is based on the documentation provided by {{#var:ClientName}}, as referred to in the appendices, as well as information gleaned from site visits and workshops with {{#var:ClientName}}.

	<!-- ANY scope or limitations, bulleted. -->		<!-- ANY scope or limitations, bulleted. -->

Anw at 14:01, 8 July 2011

2011-07-08T14:01:18Z

← Older revision		Revision as of 16:01, 8 July 2011
Line 64:		Line 64:

	= Appendix A: Table of SCRs and Ballpark Estimates =		= Appendix A: Table of SCRs and Ballpark Estimates =
	<-- If there’s only one system being discussed here, the system column can be removed.		<!-- If there’s only one system being discussed here, the system column can be removed.
	Ballpark estimates may not be required to be included in this document. If they are, include the column, and note 1. Estimates should be rounded up, and should be produced using the standard mechanism of estimates (i.e. any standard spreadsheet designed to automate the production of estimates). The total line need only be added if the estimates are being produced at this point		Ballpark estimates may not be required to be included in this document. If they are, include the column, and note 1. Estimates should be rounded up, and should be produced using the standard mechanism of estimates (i.e. any standard spreadsheet designed to automate the production of estimates). The total line need only be added if the estimates are being produced at this point
	The description should be the description from the text in the main sections.		The description should be the description from the text in the main sections.
	The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. -->		The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. -->

	{{~~TestPlan_Header~~		{{ #vardefine: SCR \| 0 }}
	\|~~Title~~={{#~~var~~:~~Doc_Title}}~~		{{REQ_SCR_Header}}
	\|~~Log=~~{{#var:~~Reference~~}}		{{REQ_SCR_Line
	\|~~Description~~=~~description of what is to be achieved~~		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|~~MenuAccess~~=~~Where on the menus the item can be found~~		\|System=System Affected
	\|~~Prerequisites~~=~~The prerequisites~~ of ~~the test~~		\|Area=Area Affected
	\|~~Objective~~=~~The details of what each group of tests is to achieve~~		\|Description=Description of change
			\|Estimate=Cost
			\|Notes=Any notes, numerically listed
	}}		}}
			{{REQ_SCR_Footer}}

			Notes:
			#Any high level ballpark estimates for development are based on the basic information provided and are subject to detailed design and creation of an SCR.
			#<Further notes, referenced in the notes column of the grid above>

	<!-- MEDIA LANDSCAPE NO -->		<!-- MEDIA LANDSCAPE NO -->

Anw: Created page with "
{{#vardefine:Client|The Client}} {{#vardefine:System|Calidus Mobile/WMS/TMS}} {{#vardefine:Doc_Title|Description}} {{#vardefine:Version|0.1}} {{#vardefine:D..."

2011-07-08T12:18:37Z

Created page with "<div class="noprint"> {{#vardefine:Client|The Client}} {{#vardefine:System|Calidus Mobile/WMS/TMS}} {{#vardefine:Doc_Title|Description}} {{#vardefine:Version|0.1}} {{#vardefine:D..."

New page

<div class="noprint">
{{#vardefine:Client|The Client}}
{{#vardefine:System|Calidus Mobile/WMS/TMS}}
{{#vardefine:Doc_Title|Description}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|16th June 2011}}
{{#vardefine:Reference|Supimix References}}
</div>
{{Doc_Title
|Client={{#var:Client}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Introduction =

This document is the {{#var:Doc_Title}}.

== Objective ==
The primary purpose of this document is to document the requirements gathered from {{#var:Client}}, at X, Y, Z



This document has been written in a manner such that it can be approved by non-technical representatives of {{#var:Client}} whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.

== Scope and Limitations ==
This document is based on the documentation provided by {{#var:Client}}, as referred to in the appendices, as well as information gleaned from site visits and workshops with {{#var:Client}}.


*The changes will be made in the latest version 3.4 of the Calidus 3pl-Mobile system, and version 4.14 of the Calidus 3pl system.



= Client Requirements =
Listed below are the proposed processes that will be followed by the warehouse operatives using Calidus 3pl-Mobile. Also shown are the SCRs required for this to be achieved.

<The current operational process flow has been described in documents produced by X of Y.>



== Operational Information ==


== Standard Processing ==
=== Process 1 ===


== Functional Area 1 ==


== Functional Area 2 ==



= Appendix A: Table of SCRs and Ballpark Estimates =
<-- If there’s only one system being discussed here, the system column can be removed.
Ballpark estimates may not be required to be included in this document. If they are, include the column, and note 1. Estimates should be rounded up, and should be produced using the standard mechanism of estimates (i.e. any standard spreadsheet designed to automate the production of estimates). The total line need only be added if the estimates are being produced at this point
The description should be the description from the text in the main sections.
The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. -->

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=description of what is to be achieved
|MenuAccess=Where on the menus the item can be found
|Prerequisites=The prerequisites of the test
|Objective=The details of what each group of tests is to achieve
}}


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=WCS
|Ref1=Reference1
|RefV1=0.1
|RefDate1=01/01/2011
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|Client=
|Year=
|FSEST=Y
|Rev1=Rev1
|Rev1Title=Rev1 Title
}}</div>
[[Category:Test]]