Version: 1.0
Date: 8th November 2002
See associated requirements.
Loosely based on a question from the 2002 examination paper for MC106 Software Engineering and Professional Practice.
Holding all records in a central repository is likely to reduce the number of overall number of errors.
Status: adopted
Pocket PCs are relatively low cost and put the computing power of a PC in a handheld device.
Requirement | Impact | Type | Justification |
CareWorker | - | achieves | - |
Data entry on a pocket PC is fiddly. In particular, handwriting recognition software is difficult to use quickly. The GUI should minimize the amount of input which is done through text boxes, by using menus, icons, checkboxes, etc. wherever possible.
Requirement | Impact | Type | Justification |
CareWorker.Records.Ease | 5 | absolute | A well designed GUI should provide a quick and easy inteface to the system. However, it will require considerable usuability testing to ensure that this is so. |
Only records which have actually been modified since last synchronization should be transfered.
Requirement | Impact | Type | Justification |
HQ.Records.Accuracy | 0.5 ± 0.5 | relative | Pure guess!! Need to know the common sources of errors in the records. |
Requirement | Impact | Type | Justification |
Clinic.Synchronization | - | achieves | - |
HQ.Records.Update | 1 | absolute | Do not expect careworkers to go into the clinic every day but once per week is reasonable. |
Requirement | Impact | Type | Justification |
Clinic.Synchronization.Speed | 110kb/s | absolute | - |
Requirement | Impact | Type | Justification |
Clinic.Synchronization.Speed | ??kb/s | absolute | - |
Requirement | Impact | Type | Justification |
HQ.Records.Update | 5 | absolute | Careworkers will be able to upload changes from anywhere. To synchronize once per day is reasonable. If the process is easy it might be more often. |
Such devices are coming on to the market. It may be possible to delay the implementation until a suitable model becomes available. This is a medium risk strategy since waiting may significantly delay the development.
Requirement | Impact | Type | Justification |
Development.Time | 3months | relative | The software running locally on the mobile device cannot be finalized until the exact model is known. |
Risk: medium
Requirement | Impact | Type | Justification |
HQ.HealthSurveys | - | achieves | - |
Requirement | Impact | Type | Justification |
HQ.HealthSurvey.Responsive | -3weeks | relative | No printing time. |
Requirement | Impact | Type | Justification |
HQ.HealthSurveys.Responsive | -4weeks | relative | No data entry stage at HQ (as there is with paper forms). |
This document was prepared using XML for Structured Solutions © University of Leicester 2002. Please send any comments and bug reports to S.Ambler@mcs.le.ac.uk.