SOFT7007 Requirements Engineering: Parcel Express Online Delivery SRS

Verified

Added on  2023/06/16

|19
|2810
|122
Report
AI Summary
This document outlines the software requirements specification for 'Parcel Express,' a parcel delivery enterprise aiming to enhance its services through a bespoke software solution. The current delivery system faces challenges such as high costs, limited delivery areas, and a lack of real-time tracking and communication. The proposed system introduces a mobile application providing customers with package tracking, delivery status updates, and direct communication with delivery personnel. The document details user roles (guest users, consumers, employees, managers, administrators, and editors), functional and non-functional requirements, business rules, sprint documentation, wireframes, and version control methodologies. Interview documentation is included to gather insights from executive personnel regarding the existing system and desired improvements. The goal is to create a user-friendly system that improves customer experience and streamlines delivery operations. This document includes information about the system's vision, goals, use case descriptions and diagrams.
Document Page
ONLINE DELIVERY SERVICES FOR THE DELIVERY OF PACKAGES
Name: Francesco Sparviero
Student ID: R00169214
Course Name: SOFT7007 - Requirements Engineering
Instructor’s Name: Please Fill
Date: Please Fill
1
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Table of Contents
Context.............................................................................................................................................4
Current Delivery System.................................................................................................................4
Proposed System..............................................................................................................................4
Vision Statement..............................................................................................................................5
Persona For 1 Role...........................................................................................................................6
Functional Requirements for Each User Roles................................................................................5
General Requirements (Use Case Description)...........................................................................5
Non-Functional Requirements.........................................................................................................8
Business Rules.................................................................................................................................9
Sprint Documentation......................................................................................................................9
Wireframe......................................................................................................................................10
Version Control Methodology.......................................................................................................10
Interview Documentation..............................................................................................................12
Aim of the interview..................................................................................................................12
Expected Outcome.....................................................................................................................12
Risks mitigation while Conducting Interview...........................................................................13
Relevant Interview questions.....................................................................................................13
Bibliography..................................................................................................................................15
2
Document Page
3
Document Page
Context
This paper discusses about the software requirement specification for the ‘Parcel
Express’ a parcel delivery enterprise. This paper is a reference for the system in manner to
eliminate the problems that these enterprise is facing while delivering the services. It presents a
simple system that can track the activities and details related to the delivery of the products.
Current Delivery System
The Packages are categorized into three categories as per the dimension of the parcel, and
deliveries and customers are facing problems related to the services and cost of the packages are
raising or are not able to deliver to the republic of the Ireland. There is not any notification
system for the exact location of the parcel nor it can deliver any contact between the deliveryman
and customer who is about to receive parcel.
Proposed System
The proposed system is capable of eliminating the problems stated above a mobile
application that can provide details necessary for the customers related to the delivery and
location of the package. This will also be capable of delivery and pick-up details for the package.
This will also provide information about Length of journey, Vehicle used for delivery, Courier,
Number of stops including the number of parcels collected and no of parcels delivered. This
system will allow the users to collect, return and send their parcels wherever and whenever they
want to, early ‘til late, seven days a week’ in better and efficient manner.
4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Vision Statement
Establishment of an user-interface system that enables a better customer experience
between the services and the user through providing exact location, and notifying them about the
delivery-status of the package.
Problems with the current system
Current system is unable to deliver information about the package location, delivery status,
number of total deliveries and numbers of packages collected are not being calculated. There is
not any platform for availing these services at the single platform.
Goals for the Proposed System
Implement Google Maps for checking the location of the package, length of the journey,
speed of the delivery van, and expected time for the delivery.
Present a better user-interface system that can enable user to get all the information related to
the delivery of the packages.
User roles
Role privilege Actions allowed
Guest Users Access to the services being offered by the package delivery enterprise
Access details of loyal staffs
Create an account with unique Id and password
Consumers Additional services along with the guest users
Allows to connect with the system through credentials
Stores the data related to the previous transactions and services availed
Use the map locator to detect the live location of the package
Change the delivery address
Cancel the delivery
5
Document Page
Make payment for the services
Employees Special user access
Manager Access to the administrator and manage the services
Administrator Manage everything including
Change user roles,
Approve creation and removal of accounts
Update the application
Editor Review the functioning of the system
Customise the services and user-interface
Persona For 1 Role
6
Document Page
Persona Type System Administration
User/Customer Name Job Title/Functional Role Customer/User segment
Shen Walker System Administrator Administrator level user
Photo Key Demographic Details Personality & Behavioural Characteristics
Age: 35 years
Gender: Female
Family: Single
Education: Master’s in Systems Control and
Administration
Location: Cork
Income: €60,000
Organizational details: Systech, 16 employees,
Systems control
Employment: 12 years, 3 in current occupation
Shen is a professional employee with administrative and techn
experience and fulfil her duties with full responsibilities. Her start up was
a contract administrator and with the contribution of full time employm
she gained her appraisal and reach to this level. In addition to this, shen w
to customers personally and share her experience with them at the techn
and managerial level of authentication
Representative Quote Pain Points Drivers & Influencers
“Success is not only qualification rather
achievements measures the success”
Man power is turning weak or less
Only advanced level employees will be appointed
for the task
Desire to be a lifeline for the organization and provide personal experie
for the enhancement of the performance of the organization
Motivate everyone to stay with the organization
Purchase/User Experience Goals Motivations Perceived Obstacles
Monitor the database and could find out
concerning objectives related to the performance
of the system and the organization.
Provides technical supports for the users
Try to keep the whole team motivated and
enthusiastic with jolly mood
She should find the problems those are undetectable by other representati
and could eliminate them for better user-interface
Contributes in enhancing the performance and output of the organization
Relationship to Brand/Product Technology Expertise Preferred Channels / Devices / Platforms
Voice of the system configuration and innovator in
systems control and administration
Expert proficiency in diagnostics, monitoring tools
and operating systems
programming languages, systems engineering and
scripting
Experienced with most office practice, collaboration
and productivity tools
Does not bring own device
Uses desktop computers while in office, connected to various shared dri
and company intranet
Participate in conference call
Uses mobile phone at the need only
7
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Functional Requirements for Each User Roles
The functional requirement for this system is that the objectives should be well working
and outputs of the project should be according to the desired expectations. Customers should be
able to track the location efficiently through the map. Administrator should be able to handle all
the actions of the system. Manager should be able to manage the delivery and eliminate the bugs
if any problem is reported. System should be flexible in manner that the editor could edit the
system as per the need and add additional systems.
General Requirements (Use Case Description)
Requirement Description
G1 A server should be hosting the application for the users and the service providers
including the data processing and data storage
G2 The display of the application should not be complex and easy to understand for the
users
G3 All the employees, delivery boy and other users should have access control and easy
system functionality
G4 A common display will help in connecting the GPS and the Google Maps
G5 Options will be selected and working at just one click
Standard user Description
S1 Ask for credentials to enter the network
S2 Popup will be appeared for the consumers to register
S3 Personal information related to the user should be saved in the database
S4 Login page will be appeared after registering with the network
5
Document Page
S5 Terms and condition statement will appear and without checking user cannot
proceed
Customer Description
C1 User will be asked to login using unique credentials
C2 Compare it with the existing database and confirms the credentials
C3 System will jump to C1 command
C4 Login page will be appeared again and user will be asked to enter credentials
C5 Main page will be appeared with all the service options with all menu options
C6 Dates with the booking and delivery will be appeared on the screen
C7 User can go to option to track the location
C8 System will ask for the new order
C9 Order will be confirmed
C9 Notification will be received after dispatch of the package
C10 An option will pop-up to change the delivery address
C11 User will be asked if he or she wants quick delivery
C12 Additional amount will be asked
C13 Payment will be made
Delivery boy Description
W1 Delivery boy should Have access to the network
W2 Application will be forced to logout if the user is inactive for five minutes
W3 The system shall alert deliver boy assigned to specific Smartphone
The Smartphone requests assistance from delivery boy
6
Document Page
An order is placed from that Smartphone
A package ordered by the table is ready for serving
An order is rejected by the customer
W4 Package delivery enterprise will be able to accept or reject the order
W5 Payment will be processed
Manager Description
M1 The system shall provide the manager with real-time information channelled
through the system concerning bookings, orders and others.
M2 Communication will be enabled between the delivery boy and user
Editor Description
E1 Bugs and glitches will be audited
E2 Editor will be able to modify
Administrator Description
A1 The administrator shall be able to manage everything in the system while
liaising with the manager.
Use Case Diagram
7
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Figure 1: Use Case Diagram
(Created by Author)
Non-Functional Requirements
Requirements ID Specifications
NFR_01 All the cases should exchange the information smoothly
NFR_02 Customers and delivery boy should be able to communicate with each other
NFR_03 There should be multiple payment option
NFR_04 Encryption should be used for the transactions
NFR_05 Server should be highly secured
NFR_06 Password and user Id should be unique
8
Document Page
Business Rules
Name Administrator might monitor the order placed by users
Identifier BR123
Description Only administrator will be allowed to monitor these activities
Example John placed the order and only Shen and John are the individuals who can monitor
the order and alter the address
Source Package Delivery procedures and policies
DOC ID: U1701
Related users Credentials for the administrator and individuals related to the system
Active processes
Modify the delivery and payment.
Sprint Documentation
Story Estimation Priority
User will be able to reset the password 1 1
Delivery address should be editable 3 2
Data should be exportable 2 3
Administrator should be able to define KPI’s for the sales team 4 4
Administrator should be able to send notifications 5 5
Data should be collected and reported for later use and record 2 6
Administrator should be able to set reminder 5 7
Filtering should be another facility implemented within the system 3 8
User should also be able to filter 4 9
View of the application should be modified as per the administrator 5 10
9
chevron_up_icon
1 out of 19
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]