|
|
| Line 22: |
Line 22: |
| <div class="noprint"> | | <div class="noprint"> |
| = Functional Overview = | | = Functional Overview = |
| | == Client Requirement == |
|
| |
|
| == Client Requirement ==
| |
|
| |
|
| == Solution Overview == | | == Solution Overview == |
| | |
|
| |
|
| == Scope == | | == Scope == |
| | |
|
| |
|
| <!-- NEW PAGE --> | | <!-- NEW PAGE --> |
|
| |
| = Set-up = | | = Set-up = |
| | == Pre-requisites == |
|
| |
|
| == Pre-requisites ==
| |
|
| |
|
| == Menu Structure == | | == Menu Structure == |
| | |
|
| |
|
| == Data == | | == Data == |
| | |
|
| |
|
| <!-- NEW PAGE --> | | <!-- NEW PAGE --> |
|
| |
|
| = Functional Description = | | = Functional Description = |
| | == Functional Area 1 == |
|
| |
|
| == Functional Area 1 ==
| |
|
| |
|
| <!-- MEDIA LANDSCAPE YES --> | | <!-- MEDIA LANDSCAPE YES --> |
|
| |
|
| = Appendix A: TEST PLAN = | | = Appendix A: TEST PLAN = |
|
| |
| {{TestPlan_Header | | {{TestPlan_Header |
| |Title={{#var:Doc_Title}} | | |Title={{#var:Doc_Title}} |
| Line 86: |
Line 88: |
| |Appendix=B | | |Appendix=B |
| |Estimate=Y | | |Estimate=Y |
| |Glossary=WCS | | |Glossary=EPOD |
| |Ref1=Reference1 | | |Ref1=Reference1 |
| |RefV1=0.1 | | |RefV1=0.1 |
| Line 97: |
Line 99: |
| |ST=0 | | |ST=0 |
| |IMP=0 | | |IMP=0 |
| | |PM=0 |
| |Client={{#var:Client}} | | |Client={{#var:Client}} |
| |Year={{#var:Year}} | | |Year={{#var:Year}} |
Revision as of 11:45, 19 December 2016
The Client Name
Document Title
CALIDUS Mobile/TTM/Vision/EPOD, etc
16th June 2011 - 0.1
Reference: FS Supimix Ref and Client Ref
Functional Overview
Client Requirement
Solution Overview
Scope
Set-up
Pre-requisites
Data
Functional Description
Functional Area 1
Appendix A: TEST PLAN
| Test Script / Scenario Reference | Document Title | Call Number(s): Supimix Ref and Client Ref |
| Test Script / Scenario Description | description of what is to be achieved | PASS / ISSUES / FAIL |
| Menu Access | Where on the menus the item can be found | |
| Pre-requisites | The prerequisites of the test | Tested By:
|
| Test Objective | The details of what each group of tests is to achieve | Date:
|
| Step |
Action |
Result |
Remarks |
P/F |
| 1 |
Area being tested in this cycle |
|
|
|
| |
Any notes or prerequisites for the tests following. |
|
|
|
| 1.01 |
The actions to follow |
The expected result |
|
|
| 1.02 |
The actions to follow |
The expected result |
|
|
| 1.03 |
The actions to follow |
The expected result |
|
|
Appendix B: Quote & Document References
| Cost Details |
| Activity |
Estimate
No. of Days |
No. of Days |
Rate per Day (£) |
Cost (£ Exc. VAT) |
| Requirements |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Change Request Evaluation |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Functional Specification |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Technical Specification |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Development |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Testing and Release |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Implementation |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Project Management |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| |
| TOTAL |
0.00 |
0.00 |
|
£First argument to "number_format" must be a number. |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | Reference1 | 0.1 | 01/01/2011 |
B.2 Glossary
| Term |
Definition
|
| EPOD |
Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
|
| CALIDUS eSERV |
The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
|
| PDA |
The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
|
| DAL |
Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
|
| GPS |
Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
|
| GPRS, 3G, HSDPA, Data Service |
All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.
|
B.3 Authorised By
Rev1 |
Rev1 Title | _____________________________ |
