The following table contains a list of requirements for the system. They have been labelled according to the MoSCoW system, of requirements that the system Must have, Should have, Could have and Would have.
Must Have
Must be implemented during this project in order for the system to be demonstrable. These requirements are in the scope of this project.
Should Have
Requirements that need to be implemented to make the system designed in this project a worthwhile investment of time. These requirements are in the scope of this project.
Could have
Features that could be added to the system, if and only if all “must” and “should” requirements are implemented with time to spare. In addition, features that may one day be added to the system with future development. These requirements may be in the scope of this project dependant on the “must” and “should” requirements.
Would have
Features that the system would have if it were being created for commercial purposes, and not as a prototype. These requirements are not in the scope of this project.
| No. | Detail | Type | Priority | Actors |
|---|---|---|---|---|
| R1 | The System shall monitor surgical tool movements within the body. | Functional | Would Have | System |
| R2 | The image received from the camera of the System shall be displayed on a Heads-Up Display (HUD). | Functional | Must Have | System |
| R3 | The System shall be able to tell how close surgical instruments are to the tissue in the patient’s body. | Functional | Would Have | System |
| R4 | The System shall be able to tell how close an item is to another item for the purpose of demonstrating the system’s functionality. | Functional | Must Have | System |
| R5 | The System shall provide visual feedback related to the proximity of items to the User. | Non-Functional | Should Have | System, User |
| R6 | The System shall provide audio feedback related to the proximity of items to the User. | Non-Functional | Should Have | System, User |
| R7 | The System shall provide haptic feedback related to the proximity of items to the User. | Non-Functional | Could Have | System, User |
| R8 | The System shall be controlled by voice control. | Non-Functional | Must Have | System |
| R9 | The System shall have a secondary method of control at the endoscope terminal. | Non-Functional | Would Have | System |
| R10 | The item used to control the System shall be a small earpiece that provides haptic and audio feedback and contains a microphone to receive voice commands. | Non-Functional | Could Have | System |
| R11 | The System shall be able to be controlled by voice commands received by the Kinect 2.0 sensor. | Non-Functional | Must Have | System |
| R12 | The System shall provide a virtual 3D view of the camera feed that can be rotated and viewed from different angles. | Non-Functional | Could Have | System |
| R13 | The System shall be controllable from a handheld device such as an iPad or other tablet. | Non-Functional | Could Have | System |
| No. | Detail | Type | Priority | Actors |
|---|---|---|---|---|
| R14 | The System shall run on the Windows 8 operating system. | Functional | Must Have | System |
| R15 | The software for the System shall be written in C# using Microsoft Visual Studio. | Functional | Must Have | System |
| R16 | R16 The System shall be created using a Kinect 2.0 sensor which shall be a larger-than-scale prototype of the target surgical endoscope to be built. | Functional | Must Have | System |
| No. | Detail | Type | Priority | Actors |
|---|---|---|---|---|
| R17 | The System shall inform the user when it is listening for voice commands, that is it is in the “listening” state. | Non-functional | Should Have | System, User |
| R18 | The System shall inform the user what visual augmentations are currently being applied to the camera feed. | Non-functional | Should Have | System, User |
| R19 | The System shall inform the user whether audio feedback is switched on. | Non-functional | Should Have | System, User |
| R20 | The System shall inform the user whether haptic feedback is switched on. | Non-functional | Would Have | System, User |
| R21 | The System shall provide a form of help menu that explains the meanings of the various buttons on the screen and how the system is controlled. | Non-functional | Should Have | System |
| No. | Detail | Type | Priority | Actors |
|---|---|---|---|---|
| R22 | The System shall provide a high-definition video feed from its camera. | Non-Functional | Should Have | System |
| R23 | The System shall provide video feedback in real time without any delay due to augmentation algorithms. | Functional | Must Have | System |
| R24 | The System shall have fail-safe mechanisms so that if the augmentation algorithms crash a basic camera feed will always be provided. | Functional | Must Have | System |
| R25 | The earpiece control shall have a long battery life and shall warn the surgeon when this is getting low. | Non-Functional | Would Have | System |
| R26 | The haptic feedback provided by the System shall not distract the surgeon from the task at hand by being to strong or vigorous. | Non-Functional | Would Have | System |
| R27 | The System shall be able to support multiple screens showing different visual augmentations of the same camera feed without any loss of speed. | Non-Functional | Could Have | System |
| No. | Detail | Type | Priority | Actors |
|---|---|---|---|---|
| R28 | An actual size depth sensing endoscopic camera shall be created. | Non-Functional | Could Have | System |
| R29 | A robotic endoscope prototype shall be created. | Non-Functional | Could Have | System |
| R30 | The endoscope prototype shall have some method of illuminating the area into which it is inserted. | Functional | Would Have | System |
| R31 | The endoscope prototype shall be small enough to fit into the body. | Non-Functional | Would Have | System |
| R32 | The endoscope prototype shall be controlled either by a User or by automated software. | Non-Functional | Could Have | System |