The Federal University of Technology Department of Software Engineering SEN20 - Software requirements Time Allowed: One Hour Instructions: ATTEMPT ALL 1. Draw a UML class diagram to capture the following situation: "Every student is enrolled in a course. Each student may be enrolled in a set of units. Some units are core units for one or more courses and some units are elective units for one or more courses." 2. Identify the actors and the objects in the following scenario to register a patient in a hospital management system: The administrator enters the patient's name, address, date of birth and emergency contact details into the system. If the patient has only public health insurance, the administrator enters the patient's medicare number, and the system verifies this with government health database. If the patient also has private health insurance, then the administrator enters also the patient's private health insurance details, and the system verifies these details with the private health insurance system. When these details are verified as correct, the system saves the patient's details and confirms the registration. Sketch a UML sequence diagram for the scenario where the administrator registers a patient who only has public health insurance. 3. A security light system has a switch and a motion sensor attached. It can be either armed or unarmed. If the switch is in the off position, the light is off and the system is unarmed. When the switch is turned on, the light stays off but the system is armed. If the system is armed and the motion sensor detects movement, the light comes on. If no movement is detected for 5 seconds, the light goes off. Draw a UML state-chart diagram to describe the states of the security light system. 4a. Draw a use case diagram to show all the functionality of the system, (b} Đescribe in detait four nen-functionat requirements for the system. Discuss metrics for specifying non-functional requirements; and b Discuss the general activities common to requirements engineering processes 5a. Briefly describe what should be stored in a traceability table; (b) Give three reasons why requirements negotiation is needed in software engineering; and (c) Summarise the standard XYZCO-SP-STAN-95