SOFTWARE REQUIREMENTS
SPECIFICATION
for
CONVENIENCE STORE
RESTOCKING SYSTEM
Version 1.0
Prepared by : Nguyen Thuy Quynh
Submitted to: TrueConnect
Technology JSC
July 3, 2025
1
Contents
1 Introduction 3
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Intended Audience and Reading Suggestions . . . . . . . . . . . . . . . . . 3
1.3 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Definitions, Acronyms, and Abbreviations . . . . . . . . . . . . . . . . . . 3
1.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Overall Description 5
2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Product Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 System Features 9
3.1 Description and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 Other Nonfunctional Requirements 10
4.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Software Quality Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4 Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Other Requirements 11
2
1 Introduction
1.1 Purpose
This Software Requirements Specification (SRS) document outlines the functional and
non-functional requirements for the Create Order Use case within the Convenience
Store Restocking System. This system is being created for Universal Logistics Ser-
vices (ULS) with the goal of making restocking easier for retailers (convenience stores),
suppliers, and third-party logistics (3PL) providers.
1.2 Intended Audience and Reading Suggestions
This SRS is for developers, project managers, users and testers. Further the discussion
will provide the Use Case (UC) Diagram, Use Case Description with an accompanying
Activity Diagram and Mockups.
1.3 Project Scope
This Software Requirements Specification rigorously defines the Create Order use case for
the Convenience Store Restocking System. The scope includes the entire order creation
process where Store Staff and Store Managers use an iPad interface to start restocking
orders, with explicit validation against important business requirements. The following
topics are specifically covered: preventing multiple daily orders per store by requiring
order updates for same-day restocking; enforcing store-specific Minimum Order Value
(MOV) thresholds that prevent orders below configured limits; and automated approval
logic that allows orders created by Managers are immediately approved (if they exceed
MOV), while Staff-created orders below the approval threshold automatically approve
and those above are routed for Manager review.
1.4 Definitions, Acronyms, and Abbreviations
Term Definition
SRS Software Requirements Specifications: A document describing functional/
non-functional requirements for a system
UC Use Case: A specific interaction scenario between users and a system to
achieve a goal
ULS Universal Logistics Services (client)
3PL Third-Party Logistics (delivery service providers)
3
MOV Minimum Order Value: The lowest acceptable order value for cost efficiency
1.5 References
IEEE Recommended Practice for Software Requirements Specifications,” in IEEE Std
830-1998, vol., no., pp.1-40, 20 Oct. 1998.
IEEE Guide for Developing System Requirements Specifications,” in IEEE Std 1233-
1996, vol., no., pp.1-30, 22 Dec. 1996.
4
2 Overall Description
2.1 Product Perspective
”IICT WEBSITE” is the replacement of the manual hard copy result process. The data
have been stored in the hard file or papers, this website will store all of those in the
website. Main goal of this project is to minimize the work and maximize the result of
this result processing system.
2.2 User Classes and Characteristics
”IICT WEBSITE” has basically 4 types of users.
• Teachers
– Director
– Course Teacher
• Students
• Official Staff
Teacher has 2 types - Director defines the course teachers who will take the courses.
Student fulfill all the requirements like- fees, informations can take advantages of the
website.
Figure 2.1: type of users
5
2.3 Product Functions
”IICT WEBSITE” store all the results of the students of program PGD, MIT. Also
others programs can be included if necessary. Before using the main function of the
Figure 2.2: Data Flow Diagram
software result process, users have to be registered.
All users have - login parameter, user name, first name, last name, user id, role, post,
email, phone number, present address, parmanent address, blood group, password hash
and timeStamp.
Students have some extra informations after complete his/her registration , such as -
user id(foreign key), registration id, year, semester, course array and drop course array.
These are the information that contains his/her result of his taken courses and program.
Each programs has some data - program name, program id, course id, nunmber of -
semester, total credit and course length. There will be onew or many course id in each
programs.
Courses table contains - course name, course id, course code, credit, semester and teacher -
id.
Every course has its own Credit Values. Those have been 2 types - lab, theory.
Result is the main feature of all. It contains the values of all the exams of a particu-
lar student. It has data field - student id, course id, term test, attendance, marks(A),
marks(B), teacher id(A), teacher id(B), entry date(A), entry date(B), publish date, semester
and result state.
6
2.4 Operating Environment
The website will be operate in any Operating Environment - Mac, Windows, Linux etc.
2.5 Design
Student activities have 3 steps -
• From Fill Up Process
• Courses Payment
• Student Profile
Top selected Student first fill his/her form, bank payment. After verification, student
pays for their selected courses. Then he can enter his profile.
Every student profile contains his/her personal information, results, taken courses, dropped
courses and notice.
Notice will contain all the news of IICT.
Figure 2.3: Student Activities
7
Teacher activities have 2 steps -
• Director
• Course Teacher
Director can re-view the result, publish result, give notice and also create teacher. He
can also perform course teacher activities.
Teacher creates results, view students and create notice.
Figure 2.4: Teacher Activities
Staff has only one activity -
• Notice
Figure 2.5: Staff Activities
8
3 System Features
”IICT WEBSITE” is a result processing web software. So the main art of this product
is to enter data of results and publish.
3.1 Description and Priority
”IICT WEBSITE” has features that are main and also some are sub. But all the feature
is necessary for this software.
The features with priority up to down -
1. Result Creation : This is the goal feature of this software. It is been operated by
teachers. They input the results of the students.
2. Result Re-view : This is done by director.
3. Result Publish : It is basically notice. This is mainly done by director or sometimes
by staffs commanded by director.
4. Teacher : Teacher takes the courses and create the results.
5. Student : Student takes the courses of a program.
6. Staff : Their only work is to post notice.
3.2 Functional Requirements
The ”IICT WEBSITE” website is being build on .NET framework, C# language, React,
React Redux, JavaScript and MongoDB.
Back-End - .NET framework, C# language.
Font-End - React, React Redux, JavaScript.
Database - MongoDB.
9
4 Other Nonfunctional Requirements
4.1 Performance Requirements
”IICT WEBSITE” will be used for result system of IICT programs, like - PGD, MIT.
So for more interaction .NET, React and MongoDB is used.
4.2 Security Requirements
No one without registered users can inter to the website. One particular user of a section
only can perform his/her particular actions.
4.3 Software Quality Attributes
In the development phase also testing and conferences of users is been continued. So
that the quality of the software is been maintained and all the requirements are been
fulfilled.
Database, logical and also UI test is required.
4.4 Business Rules
”IICT WEBSITE” is for storing students results and publish those results of particular
programs.
Basically save working time and pressure.
10
5 Other Requirements
”IICT WEBSITE” needs maintenance as it is a long process software. It will need re-
factoring and further the requirements can be changed as the field is changing frequently.
11
