Software Requirement Engineering – Exercise Week 09

Individual Work

Name: Nguyễn Thanh Phương

Student ID: 22205366

Fingerprint Access System (FAS) Use Case Analysis

1. Context Diagram - System Boundaries

The context diagram outlines the overall system and shows how the Fingerprint Access System
(FAS) interacts with external entities (actors). In this case, the system is designed to control
access to secure facilities through fingerprint recognition, and the context diagram depicts how it
communicates with external actors such as Commuters, Security Managers, Fire Marshals, and
other stakeholders.

+---------------------------+
| Fingerprint Access |
| System (FAS) |
+---------------------------+
^ ^ ^ ^
| | | |
| | | |
+------------+ | +--------------+ +------------+
| Commuter |--|>| Security |>| Fire Marshal|
+------------+ | | Manager | +------------+
| +--------------+
+------------+ | ^
| Developer |--| |
+------------+ | +------------+
| | Company |
+------------+ | | Management |
| Sales & | | +------------+
| Marketing | |
+------------+ |
|
+--------------+
| Product |
| Support |
+--------------+

Actors:

 Commuter: Individuals attempting to access the facility (e.g., employees or visitors).

 Security Manager: Responsible for managing security-related tasks like monitoring
logs, adjusting settings, and checking access.
  Fire Marshal: Ensures that access control is maintained during emergencies (e.g., in the
case of a fire).
 Developer: Responsible for maintaining and improving the system.
 Sales and Marketing: Responsible for promoting and selling the system.
 Product Support: Provides help and troubleshooting support for the system.
 Company Management: Oversees the general performance and use of the system.

2. Actors and Their Goals

 Commuter:
o Goal: To gain access to or exit the secure facility quickly and efficiently.
 Security Manager:
o Goal: To ensure that only authorized individuals are allowed to enter or exit the
facility. This includes monitoring and maintaining logs, adjusting security settings
(like error rates), and ensuring that reports are generated correctly.
 Fire Marshal:
o Goal: To ensure that in the event of an emergency, the system allows for rapid,
unimpeded exit of all individuals from the facility and allows for emergency
personnel to enter without delay.
 Developer:
o Goal: To ensure the system is functioning correctly, troubleshoot any issues, and
implement any necessary updates.
 Sales and Marketing:
o Goal: To promote the system to potential clients, demonstrate its features, and
ensure it meets market demands.
 Product Support:
o Goal: To provide technical support, resolve user issues, and handle system-related
queries.
 Company Management:
o Goal: To oversee the effective deployment, operation, and maintenance of the
system to ensure it serves its intended purpose.

3. Use Cases

Use cases are the specific tasks or processes that each actor must perform to meet their goals.
Below is a list of primary use cases for the Fingerprint Access System:

1. Commuter Use Cases:

o Scan fingerprint for access.
o Exit facility (via fingerprint scan).
o Receive notification of access denied.
2. Security Manager Use Cases:
o Adjust fingerprint recognition error rate.
o View entry and exit logs.
o Generate reports of current facility occupants.
o Verify if a specific individual is in the facility.
 3. Fire Marshal Use Cases:
o Override security settings to allow emergency personnel access.
o Ensure smooth exit of all personnel during an emergency.
4. Developer Use Cases:
o Perform system maintenance and updates.
o Troubleshoot and fix system issues.
5. Sales and Marketing Use Cases:
o Demonstrate the system to potential clients.
o Gather customer feedback for improvement.
6. Product Support Use Cases:
o Provide technical support for fingerprint scanning issues.
o Assist in troubleshooting system problems.
7. Company Management Use Cases:
o Monitor system performance.
o Review system activity reports.

4. Use Case Descriptions

Use Case 1: Scan Fingerprint for Access

 Actor(s): Commuter
 Goal: Gain access to the secure facility by scanning their fingerprint.
 Preconditions: The commuter’s fingerprint has been previously registered in the system.
 Postconditions: The commuter is granted access if the fingerprint matches.
 Main Flow:
1. The commuter places their finger on the fingerprint scanner.
2. The system scans the fingerprint.
3. The system matches the fingerprint with the database.
4. If the fingerprint matches, the gate unlocks, allowing the commuter to enter.
5. The system logs the entry.
 Alternative Flow: If the fingerprint doesn’t match:
1. The system displays a “denied access” message.
2. The system logs the failed attempt.
 Error Flow:
1. If the system encounters an error (e.g., scanner failure), it alerts the commuter and
logs the error.

Use Case 2: View Entry and Exit Logs

 Actor(s): Security Manager

 Goal: View logs of all entries, exits, and failed attempts.
 Preconditions: The security manager has appropriate access rights.
 Postconditions: The security manager views detailed logs.
 Main Flow:
1. The security manager accesses the FAS software interface.
2. The system displays a list of all entries and exits.
 3. The manager can filter logs by time, date, or commuter ID.
4. The system shows failed or aborted access attempts.
 Alternative Flow: If the security manager cannot find the required log:
1. The system alerts the security manager that no logs exist for that time period.
 Error Flow:
1. If the system encounters an issue retrieving the logs, it alerts the security manager
and logs the error.

5. Use Case Diagram

The use case diagram visually organizes all the use cases and how the actors interact with them.
Here is a simplified representation:

+----------------------------------+
| Fingerprint Access System |
| (FAS) |
+------------------+ | |
| | Scan Fingerprint for Access |
| Commuter |<-----------------------------+ |
| | View Entry and Exit Logs | |
+------------------+ | |
+------------------+
+-----|------------------+
| | View Entry Logs |
| |--------------------|
+------------------+ | | Security Manager |
| Fire Marshal |<------>+-----|------------------+ |
+------------------+ | | Provide Emergency|
| | Personnel Access |
| |------------------+ |
+------------------+ | |
| Developer |<------>+-----|------------------+ |
+------------------+ | | Troubleshoot |
| | System Issues |
+------------------+ | |
| Product Support |<------>+-------------------------+
+------------------+ | Maintain System |
+-------------------------+

In this diagram, the actors (e.g., Commuter, Security Manager) interact with the use cases (e.g.,
Scan Fingerprint, View Entry and Exit Logs) within the system.

Conclusion

The Fingerprint Access System is designed to provide fast, secure access control to facilities
using fingerprint recognition. By defining the actors, use cases, and system boundaries, we can
understand how the system operates, meets the needs of the stakeholders, and addresses various
security, emergency, and performance requirements. Through the use of use cases and a context
diagram, the system's functionality and its interaction with users are clearly represented, ensuring
that all needs are effectively met.