1. Security System Elion Sõber Vahur Kaar Kristof Mikael Rosenberg

2. Goal model

3. Role nameSecurity Manager DescriptionThe role of a security manager Responsibilities Monitor the situation. Assess raised incidents. Classify the incident and act accordingly. Notify the police and/or security providers if necessary. ConstraintsRelies on data given by sensors to monitor the environment.

4. Role namePersonnel DescriptionThe role of a person who is protected by the system. Responsibilities Register their presence on the premises. Not allow any visitors in without them being registered. Contact security officials if necessary. ConstraintsFollow the guidelines provided by security authorities.

5. Role nameVisitor DescriptionThe role of a person visiting the protected site. Responsibilities Register their presence on the premises. ConstraintsFollow the guidelines and instructions given by the personnel or security officials. Must not intervene the handling of an incident without an explicit order to do so.

6. Role nameSensor Description The role of a unit that provides data about the surroundings/environment. Responsibilities Present the system with data. Data must be valid. ConstraintsData from sensors can be faulty.

7. Role namePolice DescriptionThe role of a police authority. Responsibilities To intervene if something illegal and/or dangerous is taking place. Guarantee the safety of personnel and visitors. ConstraintsTakes time to arrive. Shouldn’t be called for unnecessarily.

8. Role nameSecurity contractor DescriptionThe role of a security contractor providing a security service. Responsibilities To solve a security incident. Guarantee the safety of personnel and visitors. Contact police if necessary. ConstraintsDoes not have full authority (separate from the police). Requires to be called for.

9. Domain model

10. Organization model