System use case specification access project location on the map - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
Identification |
UC05 |
Use case |
Access project location on the map |
Actors |
Administrator, Technician |
Stakeholders and interests |
Consulting company: Ability to access the map location of each client's projects. |
Pre-conditions |
User is logged into the system as an administrator or technician; Has at least one registered client; Has at least one registered project. |
Minimum guarantees |
System informs service unavailability. |
Success guarantees |
User accesses a map with the project location marked. |
Main Success Scenario
User Action |
System Response |
1. This use case begins when the user selects the option to access the information of a client's project |
2. The system redirects to the project's information |
3. The user then accesses the option to locate the project on the map |
4. The system redirects to a map with a marker of the project location |
Alternative Flows
2a Map service unavailable
User Action |
System Response |
|
1. The system detects that the map service is unavailable |
|
2. The system displays an error message |
3. The user acknowledges the error |
4. The system returns to the project information view |
3a User cancels the action
User Action |
System Response |
1. The user cancels the action |
2. The system returns to the project information view without displaying the map |
Special Requirements
- Map Integration: The system must integrate with a reliable mapping service (e.g., Google Maps, OpenStreetMap).
- Location Data: Project locations must be stored with precise coordinates (latitude and longitude).
- Performance: Map loading should be optimized for quick response times.
- Offline Support: The system should handle cases when the map service is unavailable.
- Access Control: Only authorized users can access project locations based on their role.