Home

Document status	DRAFT
Document owner	Nanii Gheorghe
Stakeholders
Designers	Nanii Gheorghe

Table of contents

• Functional Requirements
• Viewpoint Catalog
  • Functional View point
    • Functional system components
  • Development view point
    • Layers
• Perspective Catalog
  • Performance
  • Availability
    • Socket communication
    • Error/Faults mitigation
      • TCP errocodes
    • Interoperability
      • System actions on specific messages
  • Usability
    • General Settings
      • Common Settings
      • TCP Settings
      • IP Settings
• Examples
  • How to change IP
  • How to change TCP socket ports
  • How to change a setting
• References

Functional Requirements

Given following functional requirements:

Epic Link	Description
ACS1	The ability of the user/administrator to open a door lock(if has access to it) using an electronic key or fingerprint.
ACS2	The ability of the user/administrator to login in the system to access his personal data(web/mobile).
ACS3	The ability of the user to see all his accessible/inaccessible door locks(web/mobile).
ACS4	The ability of the user to request access to a specific office room(web/mobile).
ACS5	The ability of the administrator to give access to a user to a specific office room
ACS6	The ability of the administrator to create a new office room.
ACS7	The ability of the administrator to create a new door lock.
ACS8	The ability of the administrator to link a room with a door lock.
ACS9	The ability of the administrator to see all entries and exits for in a room.
ACS10	The ability of the administrator to see all entries and exits for a user.
ACS11	The ability of the administrator to see how much time stayed a person in the office in a specific day.
ACS12	The ability of the administrator to export a statistic about how much time stayed a person in the office during a period of time.
ACS13	The ability of the administrator to link a physical door look with a entity in the system.

Non Functional Requirements

Given following non functional requirements: