Requirements Revision for Cmpe451 ‐v2 ‐‐ Req Version 0.3.1 - bounswe/bounswe2023group1 GitHub Wiki

**Project Requirement Inconsistencies Resolution Report - 2

Prepared on 01.11.2023

Report Overview:

The identified discrepancies between the project requirements, mockup designs, and the web application (APK) have been effectively addressed and resolved.

Resolved Inconsistencies:

1. User Registration:

The initial requirement for user registration specified that account creation is not mandatory in emergency situations. Additionally, unregistered users were assigned the "victim" role by default for immediate access to essential features. The requirement was revised to clarify the user experience as follows:

Previous:

Users shall be able to create an account on the system. Considering emergency situations, account creation is not mandatory situation.

Revised Requirement:

1.1.1 User Registration

1.1.1.1 User Account Creation

Users shall be able to create an account on the system. In emergency situations, account creation is not mandatory, and unregistered users are, by default, assigned the "victim" role for immediate access to essential features without mandatory account creation. 1.1.1.2 Registration Confirmation and Login

After successful registration, users shall receive a notification confirming the approval of their registration, indicating that the registration process is successful. Users will be automatically redirected to the login page after registration. 1.1.1.3 Convenient Sign-In

At the login page, users have the option to save their login information for a convenient sign-in process in subsequent visits, eliminating the need to re-enter their credentials. 1.1.1.4 Role Selection

Upon logging in, users must choose their role to proceed. Initially, users will only see the "victim" role. After submitting a successful role request, users will have access to view and select from their approved roles on the user role selection page after signing in. Justification for Revision: The revised requirement provides more clarity and a smoother user experience, especially for unregistered users, and ensures a convenient and efficient sign-in process.

2. Resource Information for Responders:

The initial requirement for responders lacked specific details regarding the information they should provide about the resources they can offer. The requirement was revised as follows:

**Previous: **

1.1.2.4.1 Responders must provide information about the resources they can offer and add them to their profiles.

Revised Requirement:

1.1.2.4.1 Responders must provide information (location, quantity, type, status, priority, and additional description) about the resources they can offer and add them to their profiles.

Justification for Revision: The revised requirement provides comprehensive guidance to responders on the information they should provide, enhancing the system's effectiveness in managing resources during emergencies.

  1. Identification for Responders:

The original requirement stated that any user can become a responder after providing sufficient information to the system. The requirement was updated to include the necessity of uploading a valid identification document for role transition:

Previous:

1.1.2.4.2 Any user can become a responder after providing sufficient information to the system.

Revised Requirement:

1.1.2.4.2 Any user wishing to become a responder must upload a valid identification document as a necessity for their role transition in the system.

Justification for Revision: The inclusion of an identification document as a necessity for role transition enhances security and accountability within the system.

  1. Task Status Terminology:

The requirement for responders to update the status of their tasks lacked clarity regarding the task status terminology. It was revised to clarify the terminology:

Revised Requirement:

**Previous: **

1.1.2.4.5 Responders can update the status of their tasks as: not started, in progress, completed.

**Revised: **

1.1.2.4.5 Responders can update the status of their tasks as: "to do," "in progress," "completed."

Justification for Revision: The revised requirement provides a clear and consistent terminology for task status updates.

  1. Victim Access to Resources and Requests:

The initial requirement for victims to access critical locations was expanded to include access to resources provided by responders and information about other requests shared by fellow victims:

Previous:

1.1.2.1.3 Victims should be able to access critical locations (Help centers, soup kitchens etc.).

Revised Requirement:

1.1.2.1.3 Victims should be able to access critical locations (Help centers, soup kitchens, etc.). Additionally, they should have the capability to view resources provided by responders, including the status of these resources (such as "to be delivered," "in progress," "completed"), and access information about other requests shared by fellow victims.

Justification for Revision: The revised requirement offers victims more comprehensive access to resources and information during emergency situations.

  1. Unregistered User Role/Status:

There was an inconsistency related to unregistered user role/status, specifically if the system could be used without registration. The resolution to this problem was under discussion, and it should be finalized with a decision regarding unregistered user role/status.

Justification for Resolution: The resolution is still under discussion and will be finalized based on the project's needs and goals.

  1. Convenient Sign-In (Additional Point):

Upon customer request for a quick and easy sign-in process, an additional requirement was added:

Added Requirement:

1.1.1.3 Convenient Sign-In: At the login page, users have the option to save their login information for a convenient sign-in process in subsequent visits, eliminating the need to re-enter their credentials.

Justification for Addition: The additional requirement addresses customer needs and enhances the sign-in process for users.

Conclusion:

The identified inconsistencies between the project requirements, mockup designs, and the web application (APK) have been successfully resolved. These revisions and additions provide clear guidance and enhance the overall functionality of the system, ensuring it aligns with the project's objectives and user requirements.

Report Prepared By: Kübra Aksu 01.11.2023