Home

Document status	DRAFT
Document owner	Nanii Gheorghe
Stakeholders
Designers	Nanii Gheorghe

Table of contents

• Functional Requirements
• Non Functional Requirements
• REST API
• Viewpoint Catalog
  • Functional View point
    • Functional system components
  • Information Viewpoint
    • Class diagram
    • Entity relationship diagram
  • Development view point
    • Layers
  • Deployment Viewpoint
    • Deployment Viewpoint Diagram
• Quality Attributes
  • Performance
  • Availability
  • Usability
  • Modifiability
  • Interoperability
• References https://github.com/NaniiGheorghe/AccessControlSystem/wiki/REST-API

Functional Requirements

Given following functional requirements:

Epic Link	Description
ACSFR1	The ability of the user/administrator to open a door lock(if has access to it) using an electronic key or fingerprint.
ACSFR2	The ability of the user/administrator to login in the system to access his personal data(web/mobile).
ACSFR3	The ability of the user to see all his accessible/inaccessible door locks(web/mobile).
ACSFR4	The ability of the user to request access to a specific office room(web/mobile).
ACSFR5	The ability of the administrator to give access to a user to a specific office room
ACSFR6	The ability of the administrator to create a new office room.
ACSFR7	The ability of the administrator to create a new door lock.
ACSFR8	The ability of the administrator to link a room with a door lock.
ACSFR9	The ability of the administrator to see all entries and exits for in a room.
ACSFR10	The ability of the administrator to see all entries and exits for a user.
ACSFR11	The ability of the administrator to see how much time stayed a person in the office in a specific day.
ACSFR12	The ability of the administrator to export a statistic about how much time stayed a person in the office during a period of time.
ACSFR13	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:

Epic Link	Description
ACSNFR1	The ability of the system to respond to a key event in max 2 sec.
ACSNFR2	The ability of the system to load each web page in max 2 sec.
ACSNFR3	The ability of the system to handle more key events at ones.
ACSNFR4	The ability of the system to recover itself if the process stopped.
ACSNFR5	The ability of the system to notify(via email) the developer if the system stopped.
ACSNFR6	The ability of the system to load each mobile page in max 2 sec.
ACSNFR7	The ability of the system to unlock all the door locks if the system stopped.
ACSNFR8	The ability of the system to export a statistic in less than 4 sec.
ACSNFR9	They ability of the system to store user password hashed.
ACSNFR10	They ability of the system to handle 70 requests per second (web).

Viewpoint Catalog

Functional View point

Functional system components

Information Viewpoint

Class diagram

Entity relationship diagram

Development view point

Layers

Deployment view point

Deployment view point diagram

Quality Attributes

Performance

The below Non Functional Requirements will determine the quality attribute - performance.

Non Functional Requirement	Architectural Tactics Rational
ACSNFR1	The ability of the system to respond to a key event in max 2 sec.
ACSNFR2	The ability of the system to load each web page in max 2 sec.
ACSNFR6	The ability of the system to load each mobile page in max 2 sec.
ACSNFR8	The ability of the system to export a statistic in less than 4 sec.
ACSNFR10	They ability of the system to handle 70 requests per second (web).

Availability

Usability

Modifiability

Interoperability

References