Patients are taken to the hospital and discharged from a hospital. A patient can be in the regular ward, in the ICU or in the monitored aftercare unit. New parameters have to be added to the monitoring function when the equipment of the medical practice is changed.
Patients are taken to the hospital and discharged from a hospital. A patient can be in the regular ward, in the ICU or in the monitored aftercare unit. New parameters have to be added to the monitoring function when the equipment of the medical practice is changed.
Patients are taken to the hospital and discharged from a hospital. A patient can be in the regular ward, in the ICU or in the monitored aftercare unit. New parameters have to be added to the monitoring function when the equipment of the medical practice is changed.
Requirements Specification of a Patient Monitoring System
1. Patients are taken to the hospital and discharged from a hospital. The patients can be in the regular ward, in the intensive care unit (ICU) or in the monitored aftercare unit (MACU). 2. A patient can be in several wards during her or his stay in hospital and within the same ward different beds can be allocated to him or her. 3. When staying in a ward, it may happen that the patient is outside the bed from time to time (e.g. when an operation is performed). In that case the monitoring function has to be interrupted. It has to be resumed as soon as the patient returns into the bed. 4. For each patient the system monitors a set of parameters. Depending on the patient some patient-specific parameters have to be taken into account, too. 5. New parameters have to be added to the monitoring function when the equipment of the medical practice is changed. 6. The system has to analyze images recorded by the video camera system in order to check the patients emotional condition. 7. All ICU- and MACU-patients are to be monitored. In case of MACU-patients usually less parameters are monitored as for ICU-patients. In all other aspects they are treated the same way. 8. Patients in normal wards are not monitored. 9. ICU-patients are more important than MACU-patients. 10. Patient parameters are monitored by means of analog or digital devices being controlled by software. All devices are equipped with a standard hardware interface providing a digital data output. The data format used in the messages passed at the devices output depends on the function of the device. 11. The devices are connected to the computer by means of data cables. They are provided by the connector panel every bed is equipped with. The devices are able to identify themselves, this is the software can determine which device is connected to which data cable by a simple query. 12. Two limits are assigned to every parameter and every device: standard limits, device limits and patient limits. 13. An Excel database application on a PC stores both the parameters of all patients as well as the messages that came up (alarms and display journal look-up requests). 14. In the nurses room a master display panel is installed. In the ICU room other display panels are used. The MACU rooms are equipped with portable display panels. 15. Three different kinds of messages can be displayed: alarms, status messages and journal look-ups. 16. When requested, the status message of a specific patient can be shown on every display panel. 17. A journal look-up returns all journal entries available for a specific patient and can be requested from any display panel. 18. The system has to be made easy to use and reliable.
Software Engineering for Real-Time Systems Exercise 4: Requirements Engineering WS 04/05 2 1 Dec. 2004, Gt Question 6.1 Analysis of an Informal Requirements Specification Teamwork (20 minutes): The class will be divided into five teams. Each team has to analyze the requirements specification of the patient monitoring system with respect to a specific characteristic. The results are to be collected in the solution table provided in the appendix of this exercise. There is one line for each requirement section and one column for each team. During the teamwork only the column concerned needs to be considered, afterwards the results of all teams will be collected and discussed in common.
Team 1: Assign each requirement section to one or more of the following categories:
F Functional Requirement Q Quality Requirement I Implementation Requirement H Hardware Requirement N No Requirement
Team 2: Check if the information given by each requirement section is unambiguous.
Team 3: Check if the information given by each requirement section is consistent. In the solution table either Yes has to be entered or the number of the requirement section being in contradiction to the current one.
Team 4: Check if it is possible to meet the requirement in question.
Team 5: Check if the implementation of the requirement in question can be verified in the system when the development has been finished. Software Engineering for Real-Time Systems Exercise 4: Requirements Engineering WS 04/05 3 1 Dec. 2004, Gt Appendix Solution table for question 6.1 Section Team 1 Classification Team 2 Unambiguous? Team 3 Consistent? Team 4 Realizable? Team 5 Verifiable? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18