Software Requirement Engineering – Exercise Week 06
Group Work
Name: Nguyễn Thanh Phương
Name: Lê Minh Trí
Fingerprint Access System (FAS) Use Case Exercise
1. Context Diagram
A Context Diagram is a high-level view of the system, showing its boundaries, the actors interacting with the system,
and the relationships between the system and these actors. It highlights how external entities interact with the Fingerprint
Access System (FAS).
Context Diagram Components:
System (Fingerprint Access System): The central system that controls access through fingerprint recognition.
Actors:
o Commuters (users seeking entry or exit)
o Security Managers (overseeing system functionality, logging, and reports)
o Fire Marshal (ensures emergency personnel entry and exit)
o Developers (responsible for the development and maintenance of the system)
o Sales and Marketing (promoting the system)
o Product Support (provides help to end-users)
o Company Management (overall system oversight)
In this context diagram, the Fingerprint Access System interacts with each of the external actors through the following
flows:
Commuters: Interact with the system by scanning their fingerprints for entry and exit.
Security Managers: Interact with the system for monitoring, adjusting recognition accuracy, viewing logs, and
generating reports.
Fire Marshal: Interacts with the system to ensure that in emergencies, personnel can enter or leave freely.
Developers: Responsible for maintaining and upgrading the system.
Sales and Marketing: Engage with the system to understand its features and capabilities for promotional
purposes.
Product Support: Interact with the system to resolve technical issues or answer customer queries.
Company Management: Oversee the overall functionality and performance of the system.
2. Identify Actors and Their Goals
Actors:
1. Commuters
Goal: Quickly and accurately gain entry or exit from the facility.
2. Security Managers
Goal: Ensure system security by adjusting error rates, viewing logs, generating reports, and verifying whether
individuals are inside the facility.
3. Fire Marshal
Goal: Ensure that the system does not block emergency exit or entry during an emergency.
4. Developers
Goal: Ensure the system operates smoothly by maintaining and updating software and hardware as necessary.
5. Sales and Marketing
Goal: Promote the system by understanding its features and capabilities.
6. Product Support
Goal: Provide customer service to resolve any technical issues with the system.
7. Company Management
Goal: Oversee the implementation and functionality of the system.
3. Identify All Use Cases
Based on the goals of the actors, the following use cases can be identified:
1. Commuters:
o Use Case 1: Scan Fingerprint for Entry/Exit
o Use Case 2: Report Entry/Exit Status (optional, for support cases)
2. Security Managers:
o Use Case 3: Adjust Fingerprint Recognition Error Rate
o Use Case 4: View Logs of Entries/Exits
o Use Case 5: Generate Reports on Current Occupants
o Use Case 6: Check Individual’s Presence in Facility
3. Fire Marshal:
o Use Case 7: Override Access for Emergency Personnel
o Use Case 8: Allow Unimpeded Exit for Commuters in an Emergency
4. Developers:
o Use Case 9: Maintain and Update Software and Hardware
5. Sales and Marketing:
o Use Case 10: Provide System Demonstrations
6. Product Support:
o Use Case 11: Troubleshoot System Errors
7. Company Management:
o Use Case 12: Oversee System Performance
4. Write Use Case Descriptions
Use Case 1: Scan Fingerprint for Entry/Exit
Primary Actor: Commuter
Goal: The commuter scans their fingerprint for entry or exit to the facility.
Preconditions: The commuter is registered in the system, and the fingerprint scanner is active.
Main Success Scenario:
1. The commuter approaches the gate.
2. The system prompts the commuter to place their finger on the scanner.
3. The commuter scans their fingerprint.
4. The system checks the fingerprint against the stored records.
5. If the fingerprint matches, the gate unlocks, and the commuter gains access or exits.
6. The system logs the entry/exit time.
Alternative Scenario (Fingerprint Match Failure):
1. If the fingerprint does not match any stored record, the system displays an error message.
2. The commuter may attempt to scan the fingerprint again or request assistance.
Exception Scenario (System Failure):
1. If the fingerprint scanner malfunctions, the system displays an error message.
2. The commuter is instructed to contact security personnel for further assistance.
Use Case 3: Adjust Fingerprint Recognition Error Rate
Primary Actor: Security Manager
Goal: The security manager adjusts the error rate of the fingerprint recognition system to improve accuracy.
Preconditions: The security manager is logged in with appropriate privileges.
Main Success Scenario:
1. The security manager accesses the settings page for the fingerprint recognition system.
2. The security manager navigates to the error rate settings section.
3. The security manager adjusts the recognition error rate to the desired level.
4. The system applies the new settings, and the change is confirmed to the manager.
Alternative Scenario (Invalid Setting):
1. If the error rate is set too high or low, the system displays a warning about potential issues.
2. The security manager can decide whether to proceed or adjust the settings again.
Exception Scenario (System Error):
1. If the settings cannot be applied due to system issues, the system displays an error message.
2. The security manager is prompted to contact technical support for assistance.
5. Organize Use Cases in a Use Case Diagram
A Use Case Diagram visually represents the interactions between actors and the use cases in the system.
The actors (Commuters, Security Managers, Fire Marshal, Developers, Sales & Marketing, Product Support, and
Company Management) are represented as stick figures.
The use cases (e.g., Scan Fingerprint for Entry/Exit, Adjust Fingerprint Recognition Error Rate, etc.) are
represented as ovals.
The relationships between actors and use cases are shown with lines, demonstrating which actors interact with
each use case.
Example:
+---------------------------+
| Fingerprint Access |
| System |
+---------------------------+
| | |
+-----------+---+---+---+---+---------+
| Commuter | Security Manager | Fire Marshal |
+-----------+---+---+---+-----------+
| Scan Fingerprint | Adjust Fingerprint |
| for Entry/Exit | Recognition Error Rate |
| | Check Individual's Presence |
| | View Logs |
+---------------------+-------------------+
This diagram visually encapsulates the system’s main use cases and their relationship with actors.
