1

Week 2 Project: Requirements Gathering and Use-Case Specification

Student’s Name

Institution’s Name

Course Name and Number

Instructor’s Name

Date
 2

Mechanisms for Soliciting Stakeholder Input

This is a crucial process of gathering effective stakeholder input in building a system that

actually meets the needs of users and falls in line with business objectives. The stakeholder

interview allowed the development team to gain deep insight into those people involved directly

in the customer service, information technology, and freight management processes of a business

(Rodriguez-Calero et al., 2020). In-depth interviews across departments allow the team to refrain

from collecting quantitative data about pain points or operational challenges. For instance,

customer service representatives mentioned that when handling an inquiry, time is of the

essence.

Surveys and questionnaires allowed for a controlled method of capturing data with regard

to a larger population of stakeholders, including frontline employees and customers. Surveys

could be used to quantify information in regard to preferences related to system features such as

preference for notification or shipment tracking options (Kadam, 2023). The resultant data

helped validate system requirements against the preference needs of stakeholders and rank them.

This class of stakeholders proposed requirements that would be nice to have, such as having

mobile access to handle on-the-go customers.

Also, stakeholder workshops were conducted; it allowed group discussions and

interdepartmental collaborations to be facilitated. These workshops have allowed the

stakeholders to talk with each other across multiple departments about the needs of the system

that were common (Klauer et al., 2022). This was helpful in finding workflows that might affect

multiple departments and also selecting those features that would advance overall productivity.

Testing the prototype during the development of a low-fidelity prototype of the DCMS

with which the stakeholders will interact. It allows early presentation of the system with an
 3

immediate ability to gauge its usability and functionality for features such as freight tracking

and, for example, customer inquiries about those (Rodriguez-Calero et al., 2020). This allowed

the developer team to afford refinement of such features before committing fully to a design that

would eventually render intuitive and efficient to the user.

Nonfunctional requirements and declarative requirements

The three critical categories that were found for the non-functional requirements of

DCMS include performance, security, and usability. Performance requirements ensure that a

system can handle expected workloads and respond promptly to user actions, especially during

peak operational times (Khurshid et al., 2021). Security plays an important role in ensuring that

sensitive customer information is protected and access by unauthorized users to much-sensitive

functions or data is restricted within the system. Usability refers to the navigational and

functional ease for its users, maintaining attributes that design intuitiveness and accessibility of a

system for varied techno-functional stakeholders.

Performance Needs

The system should support up to 500 concurrent users without any decline in response

times. It should be able to respond to page load requests in less than two seconds under normal

conditions (Khurshid et al., 2021). During high traffic, the response time of the system under

stress should not exceed three seconds. In addition, real-time data related to freight tracking

should be made available within a five-second delay.

Security Requirements

All data transferred between the user and the server must be encrypted using Transport

Layer Security (TLS) protocols (Khurshid et al., 2021). This sensitive data should be accessed

with a role-based access control mechanism in such a way that only specific personnel have
 4

access to it. In particular, users must automatically log out after 15 minutes of inactivity as a way

of preventing unauthorized access. The sensitive customer data, personal details, and shipment

history must be encrypted for storage.

Usability Requirements

Intuitive system users can complete major tasks in three clicks or less. The system shall

be available on desktop, tablet, and mobile with similar functionality. There shall be a help

section or tooltip feature for each feature that can facilitate users without external documentation.

The customer service representative shall be proficient with up to two hours of training.

Defining Subjects for Use Case Models

The first subject is the management of customer inquiries, which was identified through

the customer service representative's input. This will provide the facility to handle inquiries at a

faster pace, and the process of responding to every query of every customer will help improve

service quality (Dong, 2023). By knowing the inquiries within the Digital Customer

Management System (DCMS), Swift Transport Solutions will manage to increase the response

times and track the customers' issues more effectively. The use-case models will outline the

process of recording, tracking, and resolving inquiries.

The second will be that freight tracking is very much based on customer and operations

teams' feedback. The customers need up-to-date information on shipments, while the operations

team urgently seeks accurate tracking data to handle delivery management (Dong, 2023). Freight

tracking shall enable the viewing of shipment location, receipt of updated estimated delivery

times, and tracking of the current status. The models of use-cases shall be done by focusing on

how freight information is updated and retrieved by internal and external stakeholders.
 5

The third subject is about User Access Control (UAC), through which security-related

issues have been raised by the IT department. The Digital Customer Management System

(DCMS) should provide different levels of access to the data based on user roles in order to

ensure the protection of sensitive information and system integrity (Dong, 2023). User Access

Control shall include user authentication-based, role-based permissions, and session management

capabilities. The use-case model for this topic will disclose how the system handles user access,

from the very moment of authentication to the different levels of access.

References

Dong, D. G. (2023). Design and development of Intelligent Logistics Tracking System based on

computer algorithm. International Journal for Applied Information Management, 3(2),

58-69. https://doi.org/10.47738/ijaim.v3i2.56

Kadam, D. (2023). The Essentials of Survey Study and Reporting. Indian Journal of Plastic

Surgery, 56(03), 195-196. doi: 10.1055/s-0043-1770695

Khurshid, I., Imtiaz, S., Boulila, W., Khan, Z., Abbasi, A., Javed, A. R., & Jalil, Z. (2022).

Classification of non-functional requirements from IOT oriented healthcare requirement

document. Frontiers in Public Health, 10, 860536. doi: 10.3389/fpubh.2022.860536

Klauer, B., Küblböck, K., Omann, I., Karutz, R., Klassert, C., Zhu, Y., ... & Gorelick, S. (2022).

Stakeholder Workshops Informing System Modeling—Analyzing the Urban Food–

Water–Energy Nexus in Amman, Jordan. Sustainability, 14(19), 11984.

https://doi.org/10.3390/su141911984

Rodriguez-Calero, I. B., Coulentianos, M. J., Daly, S. R., Burridge, J., & Sienko, K. H. (2020).

Prototyping strategies for stakeholder engagement during front-end design: Design

practitioners’ approaches in the medical device industry. Design Studies, 71, 100977.

https://doi.org/10.1016/j.destud.2020.100977