University Institute of Information Technology,

PMAS-Arid Agriculture University,

Rawalpindi Pakistan

INVENTORY MANAGEMENT SYSTEM

By

Syed Wasi Haider Rizvi 18-Arid-2706

Javed Jabbar 18-Arid-2629

Supervisor
Ms. Saba-un-Nisa
Bachelor of Science in Computer Science (2018-2022)
 The candidate confirms that the work submitted is their own and appropriate
credit has been given where reference has been made to the work of others.

DECLARATION
We hereby declare that this software, neither whole nor as a part has been copied out from
any source. It is further declared that we have developed this software documentation and
accompanied report entirely on the basis of our personal efforts. If any part of this project is
proved to be copied out from any source or found to be reproduction of some other. We will
stand by the consequences. No Portion of the work presented has been submitted of any
application for any other degree or qualification of this or any other university or institute of
learning.

Syed Wasi Haider Rizvi Javed Jabbar

--------------------------------------- ---------------------------------------
 CERTIFICATE OF APPROVAL
It is to certify that the final year project of BS (CS) “Inventory Management System” was
developed by “Syed Wasi Haider Rizvi, 18-arid-2706”, “Javed Jabbar, 18-arid-2629”

under the supervision of “Ms. Saba-un-Nisa” and that in their opinion; it is fully
adequate, in scope and quality for the degree of Bachelors of Science in Computer
Science/Information Technology/Software Engineering.

---------------------------------------
Ms. Saba-un-Nisa
---------------------------------------

External Examiner

---------------------------------------
Administrator UIIT
 Executive Summary
The project Inventory Management System is a complete web based application
designed on asp.NET technology using Visual Studio Software. The main aim of the
project is to develop an Inventory Management System for National Institute of
Electronics (NIE) in which all the information regarding the stock of the institute will be
presented. This web based application will allow to manage institute assets inventories
i.e. all consumable and non-consumable products.

This application is based on the management of stock of that institute. It contains general
institute profile, sales details, Purchase details and the remaining stock that are presented
in the institute. There is a provision of updating the inventory also.
This application also provides the remaining balance of the stock. Each new stock is
created and entitled with the named and the entry date of that stock. Here the login page
is created in order to protect the management of the stock of organization in order to
prevent it from the threats and misuse of the inventory.

4
 Acknowledgement
All praise is to Almighty Allah who bestowed upon us a minute portion of His boundless
knowledge by virtue of which we were able to accomplish this challenging task.
We are greatly indebted to our project supervisor “Ms.Saba-un-Nisa” for personal
supervision, advice, valuable guidance and completion of this project. We are deeply
indebted to him/her/them for encouragement and continual help during this work.

And we are also thankful to our parents and family who have been a constant source of
encouragement for us and brought us the values of honesty & hard work.

Sayed Wasi Haider Rizvi Javed Jabbar

--------------------------- ---------------------

5
 Abbreviations
IMS Inventory Management System

DML Data Manipulation Language

DFD Data Flow Diagram

CLR Common Language Runtime

Table of Contents
6
Introduction....................................................................................................................................
1.1 Brief.................................................................................................................................
1.2 Relevance to Course Modules..........................................................................................
1.3 Project Background..........................................................................................................
1.4 Literature Review.............................................................................................................
1.5 Methodology and Software Life Cycle...........................................................................
Problem Definition.........................................................................................................................
2.1 Purpose.............................................................................................................................
2.2 Product Functions............................................................................................................
2.3 Proposed Architecture......................................................................................................
2.4 Project Deliverables.........................................................................................................
2.5 Operating Environment....................................................................................................
2.6 Assumptions and Dependencies.......................................................................................
Requirement Analysis..................................................................................................................
3.1 Functional Requirments.................................................................................................
3.2 Non – Functional Requirments......................................................................................
3.3 Use case Model..............................................................................................................
3.3.1 Use Case Diagarm......................................................................................................
3.3.2 Actors Discription......................................................................................................
3.3.3 Use Case Discription..................................................................................................
The Design....................................................................................................................................
4.1 System Architecture.......................................................................................................
4.2 System Design................................................................................................................
4.2.1 UML Structural Diagrams..........................................................................................
4.2.1.1 Component Diagram......................................................................................
4.2.1.2 Package Diagram...........................................................................................
4.2.1.3 Deployment Diagram.......................................................................................
4.2.2 UML Behavioral Diagrams............................................................................................
4.2.2.1 Activity Diagram..........................................................................................
4.2.2.2 State Machine Diagram.................................................................................
4.2.3 UML Interaction Diagrams.............................................................................................

7
 4.2.3.1 Sequence Diagrams.......................................................................................
4.3 Class Diagram.................................................................................................................
Implementation............................................................................................................................
5.1 Communication Protocol Implementation.....................................................................
5.2 Component Diagram......................................................................................................
5.3 User Interface.................................................................................................................
Testing and Evaluation................................................................................................................
6.1 Verification.....................................................................................................................
6.1.1 Functional Testing......................................................................................................
6.1.2 Static Testing..............................................................................................................
6.2 Validation.......................................................................................................................
6.3 Usability Testing............................................................................................................
6.4 Unit Testing....................................................................................................................
6.5 Integration Testing.........................................................................................................
6.6 System Testing...............................................................................................................
6.7 Acceptance testing.........................................................................................................
6.8 Stress Testing.................................................................................................................
6.9 Hardware Configuration Testing...................................................................................
6.10 Evaluation....................................................................................................................
6.11 Deployment................................................................................................................
6.12 Maintenance.................................................................................................................

Future Work.................................................................................................................................
References.....................................................................................................................................

List of Figures
8
4.1 System Architecture 1...........................................................................................................26

4.2.1.1 Component Diagram 1......................................................................................................28

4.2.1.2. Package Diagram 1..........................................................................................................29

4.2.1.3 Deployment Diagram 1.....................................................................................................30

4.3.1. Activity Diagram 1.............................................................................................................32

4.4 Sequence Diagram 1..............................................................................................................33

4.5 State Machine Diagram 1.......................................................................................................35

4.6 Communication Protocol Implementation 1.............................................................................35

4.8 Admin Page 1......................................................................................................................37

4.10 GRN Page 1.......................................................................................................................39

4.12 ERD 1..............................................................................................................................41

5.5 Admin Page 2......................................................................................................................47

5.8 Inventory Front 1.................................................................................................................50

List of Tables
9
Chapter 1: Introduction

10
In this chapter we will discuss over view of our whole project, its brief introduction, and how it
is relevant to the courses which we have studied during our degree. We will also discuss project
literature review and its analysis and methodology that we will use in project.

1.1. Brief
The project Inventory Management System is a complete web based application designed on
.Net Core technology using Visual Studio Software. The main aim of the project is to
develop an Inventory System for Government Organization the National Institute of
Electronics (NIE) an autonomous organization under the Administrative control of
Ministry of Science & Technology in which all the information regarding the stock of the
Institute will be presented. This web based application will allow to manage institute assets
inventories i.e. all Consumable and non-Consumable products. This application is based on
the management of stock of that institute. It contains general institute profile, sales details,
Purchase details and the remaining stock that are presented in the institute. There is a
provision of updating the inventory also. This application also provides the remaining
balance of the stock. Each new stock is created and entitled with the named and the entry
date of that stock. Here the login page is created in order to protect the management of the
stock of organization in order to prevent it from the threats and misuse of the inventory.

1.2 Relevance to Course Modules

Almost everything which we are using in our project “Inventory Management System” is
totally relevant to our course materials.
 The Web Application which we are developing in our project is relevant to the subject
“Visual Programming".
 The data of the users which will be stored in Database and status will be shown on
screen, is relevant to the subject Database Management System.

1.3Project Background
The proposed solution of the problem is to develop an Inventory System for the National
Institute of Electronics (NIE) that can provide a complete solution for their store. In present

11
all records related to the institute is being done manually. The Managers have to keep
separate files for new information so managing them is very complex and has become an
impossible task to be performed manually systematic way.

1.4. Literature Review

Products are considered as the business resources for the organization. This includes
managing the product with appropriate way to review any time as per the requirement.
Therefore, it is important to have a computer based IMS which has the ability to generate
reports, maintain the balance of the stock, details about the purchase and sales in the
organization. Before developing this application, we came up with two Inventory
Management System existing in the market, which helps to give the knowledge for the
development of our project. By reviewing existing inventory systems, we got information
that would be helpful in our project mainly higher Productivity, better Profitability, easy
Inventory Processing, accurate expense Tracking.
 Inventory system of Shopify
Shopify is great for drop shippers and resellers, but if you actually make your product and
require maintaining an inventory of raw materials to make said product, you’ll probably find
the platform a bit lacking. Unfortunately, no. Shopify has no option to track raw materials,
but our system will cover it. Our system will be able to cover these aspects to get reports of
raw materials.
 Food Inventory Management
Inventory tracking means knowing exactly: what supplies come into your restaurant, what
goes out of your kitchen, and what's leftover in the back of the house. The tracking system in
inventory much beneficial for the stock and productivity for the Institute. This system faced
problems like. No Stock Forecasting, No Reporting. In our case the software we are
designing will generate reports and a proper stock system

 QuickBooks inventory management

Store cost of goods sold (COGS) and inventory accounting information and keep it aligned
with final QuickBooks accounts and balance sheets. Run inventory reports to see best

12
sellers, total value and taxes paid, Track inventory levels and costs across online sales
channels. This inventory system has Inability to Track Unshipped Orders. Lack of Industry-
Specific Features. Our System can cover these problems easily without interruption.

1.5Analysis from Literature Review

The goal is to make cleaner and less complex project for the Institute. As per idea we have
developed this application on Asp.Net Core which is an open source and cloud-optimized
web framework for developing modern web applications that can be developed and run on
Windows, Linux and the Mac. Here the Application is designed in a way that the Admin
have access to all the departments.

1.6 Methodology and Software Lifecycle for this Project

For this website, Waterfall Methodology will be used. Actually, implementing a waterfall
model within our project is rather straightforward process. Waterfall methodology is a
stepped software development approach that has a prescribed set of activities and
dependencies. It incorporates the steps of Analysis, Planning, Content, Design,
Programming, Testing, Marketing and Advertising.

1.6.1 Rationale behind Selected Methodology

 It’s a well-defined methodology that has been used in all business verticals.
 Requirements are clear and fixed that may not change.
 There are no ambiguous requirements (no confusion).
 It is good to use this model when the technology is well understood.
 The project is short and cast is low.
 Risk is zero or minimum.

1.6.1.1 Rationale behind Selected Methodology

 It is simple and easy to understand and use.
 It is easy to manage.

13
  It works well for smaller and low budget projects where requirements are very well
understood.
 Clearly defined stages.
 It is easy to arrange tasks.
 Process and results are well documented.

Chapter 2: Problem Definition

This chapter discusses the precise problem to be solved. It should extend to include the
outcome.

14
2.1. Problem Statement
The main aim of the project is to develop an Inventory Management System for National
Institute of Electronics (NIE) in which all the information regarding the stock of the institute
is presented. National institute of Technology has no inventory system, majorly their work
depends upon the manual system that is time consuming and difficult to manage their
records because it has no backup. We are shifting their manual system to software system
where they can hold and manage their record easily which is time saving and efficient.

2.2. Product Functions

The product functions of inventory management system are:

2.2.1 Register:
In registration the user can add their personal information and the information can be
verified and store in to the database and the user account created.

2.2.2 Login:
The user provides their account credential after that they can use the application features.

2.2.3 Manage Database:

The admin can manage database i.e., add user, view user, search users etc.

2.2.4 Manage user info: The admin can manage user info the admin can delete, add, and
update user name, details and its other information.

2.2.5 Supply Order:

Management do order for the employers.

2.2.6 Inventory:
Products which are added in the stock.
• Register
• Login

15
 • Manage Database
• Manage User Info
• Supply Order
• Inventory

2.3. Purpose Architecture

This desktop based application is based on 3-tier architecture of .Net Framework. The 3-tier
includes the three hierarchy of the flow of programming logic from user interface to
database and again database to user interface with the desired information requested by the
clients. In between there involves the logic layer for effectively and correctly manipulating
the request. The 3-tier includes the following:

2.3.1 Client tier

The visual part is implemented using all kinds of swing components, which does not make
database calls. The main function of this tier is to display information to the user upon user’s
request generated by user’s inputs such as firing button events. For example, inventory list
will display when user click “display” button if he or she wants to know the list of stock
remaining in the organization

2.3.2 Business tier

The middle tier, business logic, is called by the client to make database queries. It provides
core function of the system as well as connectivity to the data tier, which simplify tasks that
were done by the client tier.

2.3.3 Data tier

Data layer is also the class which gets the data from the business tier and sends it to the
database or gets the data from the database and sends it to business tier. This is the actual
DBMS access layer or object layer also called the business object. The database backend
stores information which can be retrieved by using the MySQL database Connectivity.

16
2.4 Project Deliverables
Following are the deliverables and development requirements:

2.4.1 Projects Deliverables:

In this project the deliverables will consist of the input as equipment (i.e. Software
components) then there will be a process (i.e., development phases in which development
will be completed) applied on the input and then as a result there will be an output (Project
being completed “Inventory System”). In this case product deliverables are the completed
parts or modules of the project. Input will be software-based components. The project is
divided into different modules.

2.4.2 Development Requirements:

Development requirements are the requirements needed for the development purposes
without which the development is not possible. It can be software or any kind of
requirements. These include the software equipment’s, time and date constraints, budget,
planning, following the waterfall etc. development requirements are met accordingly to
make sure that the end result does not differ from what is expected and that it can perform
its functionality accurately and perfectly without any glitches.

2.5 Operating Environment

 Operating environment for the Inventory System is as listed below:
 Operating System: Window 10.
 Database: SQL database
 Platform: Asp.NET Core for the development, similarly C#, HTML, CSS will be
used.

2.6 Assumptions and Dependencies

Assumptions:
The application developed from this technique is more efficient than others. The Manager
will have access to all the departments under them. The data will be protected with
passwords.

17
Dependencies:
This software is dependent on internet connectivity

18
 Chapter 3: Requirement Analysis
In this chapter we will define all the requirements of proposed system that include functional
and non-functional requirements. We will also discuss about use cases of the system and see
how our system will respond to various use cases.

3.1Functional Requirements
The main purpose of functional requirements within the requirement specification document
is to define all the activities or operations that take place in the system. These are derived
through interactions with the users of the system. Since the Requirements Specification is a
comprehensive document & contains a lot of data, it has been broken down into different
Chapters in this report. The depiction of the Design of the System in UML is presented in a
separate chapter. The Data Dictionary is presented in the Appendix of the system. But the
general Functional Requirements arrived at the end of the interaction with the Users are
listed below. A more detailed discussion is presented in the Chapters, which talk about the
Analysis & Design of the system.
 The System holds all the details of the all the employees who are working in the
organization.
 It allows admin to manage two types of users, hold their details, authenticate
these users at the time of login and accordingly provide different options
 It holds the details of all the employees which are part of our organization.
 It holds the details of all Product Stocks held in the ware-house of the company.
 The system allows the manager to log into the system and enter their inwards
entries related to their go down.
 It also allows them to view the list of inward entries.
 It also allows them to view the list of Outward entries.
 Whenever an inwards entry is entered then accordingly the stock number will be
automatically updated.
 Whenever an outward entry is entered then accordingly the stock number will be
automatically updated.

19
  The system allows the go down manager to log into the system and enter stock
return entries and the reason for return.
 Whenever a return entry is entered then accordingly the stock number will be
automatically updated if the reason is order cancelled otherwise It need not
update the stock.
 It allows the users to change their password for future security.
 It allows the authorized users to a new employee at the time of creating a go
down if the employee is a newly appointed for this go down.
 It allows the admin to view the list of users and take the print.
 It allows admin to generate go down details report.
 It allows admin to generate inwards details report.
 It allows admin to generate outwards details report.
 It allows admin to generate returns details report.
 It allows admin to generate stock statement report.
 It allows any user to logout when he wants to come out from the system.

3.2 Non-Functional Requirements

The non-functional requirements consist of 1. Analysis, Design & Data requirements
(Use-case diagrams, textual analysis, sequence diagrams, data dictionary etc.) 2.
Constraints. 3. Guidelines.

3.3 Use Case Model

In the Unified Modeling Language (UML), a use case diagram can summarize the
details of your system's users (also known as actors) and their interactions with the
system. Following are the use cases of the Inventory Management system.

20
3.3.1 Use Case Diagram

Fig 3.1.1: Use Case diagram 1

21
3.3.2 Actors Description:
Actor

An actor is a person, organization or external system that plays a role in one or more
interactions with the system. We have these actors.

 Admin

Admin registers and authenticates himself. He manages the database which contains
information regarding to the institute and employees.

 User

Employees who are working in the institute can registers themselves and requests their
desired products through store men.

22
3.4 Use Case Description:
Table 3.4.1: Request products
Use Case ID: U_ID_1
Use Case Name: Authentication
Actors: Admin, Customer/User,
Description: User will provide its credentials and authenticated by the system
through database.

Trigger: When user click on login button

Preconditions: Username and password must be provided by the users.
Post conditions: User will login successfully.
Normal Flow: Credentials will be entered by users
Credentials will be authenticated from database of the system
User will be successfully login

Alternative Flows: If user is not already registered, then user will first sign up
User will then provide credentials
User will again be authenticated through database

Exceptions: If user will be not authenticated, error message will be appeared.

Special Requirements: None

Assumptions: None
Notes and Issues: User will have only 3 attempts for login. After 3 attempts user will have
to wait for 30 seconds to retry.

23
Use Case ID: U_ID_02

ID:
Use Case Name: U_ID_03
Inventory Register

Actors: User/Customer
Use Case Name: Supply Order
Description:
Actors: System will
Suppliers/ show a form in which information regarding to the
Company
stores register is given which include supply order, GRN, issue
Description: The company
voucher, will sent
receive the product
voucher, to of
quantity theproduct,
destination.
and reports.
Trigger: When delivery is done, the product received by the store men.
Preconditions: Product have been delivered.
Trigger:
Post conditions: Whencompletes
System employee the
want to place
order an order.
and deliver the product.
Normal Flow: None
Preconditions: User should be authenticating.
Alternative Flows: Product is not received...
User should have internet connection.
Exceptions: None
Special None
Post conditions: The System will view the order request.
Requirements:
Assumptions:
Normal Flow: None
User will first login then request for product requiring himself
and this request will be sent to the inventory store. System will
send confirmation message to the user.

Alternative Flows: None

Exceptions: None

Special None
Requirements:

Assumptions: Web Application will be connected to the system.

Notes and Issues: If user want to buy any product, then user must be placing an
order.
Table 3.4.2: Request products

Table 3.4.3: Supply Order

24
 Chapter 4: Design and Architecture
The process of designing a solution for the creation and the definition of a new system is
known as System Design. It deals with designing and developing elements of a system like
architecture, modules, components along with their interfaces, and data for a system that
satisfies the specific needs and requirements of a business or organization. System design
has two phases of development.
As system design varies from system to system, therefore user need to have the architecture
view of the whole system.

4.1 System Architecture

Presentation tier

Interface
Business logic tier

25
Application server
 Data management tier

Database server
4.1 System Architecture 1
2

4.2 System Design

Systems design is the process of defining elements of a system like components, modules,
architecture and their interfaces and data for a system based on the specified requirements.
The purpose of the System Design process is to provide sufficient detailed data and
information about the system. Following is the system design of the Inventory Management
System.
4.2.1 UML Structural Diagrams
Following are the UML structural diagrams of our

4.2.1.1 Component Diagram

26
4.2.1.1 Component Diagram 1

27
4.2.1.2. Package Diagram

4.2.1.2. Package Diagram 1

28
 4.2.1.3 Deployment Diagram

4.2.1.3 Deployment Diagram 1

4.3 UML Behavioral Diagram

29
Behavioral diagrams is another important diagram in UML to describe dynamic aspects of
the system. Behavioral diagrams is basically another activity. The activity can be described
as an operation of the system.
4.3.1. Activity Diagram
Admin Side

4.3.1. Activity Diagram 1

Activity Diagram User Side

30
4.3.2 Activity Diagram for User 1

31
4.4 Sequence Diagrams

A sequence diagram is a type of interaction diagram because it describes how and in what

order a group of objects works together

4.4 Sequence Diagram 1

32
4.5 State Machine Diagram

4.5 State Machine Diagram 1

33
4.6 Communication Protocol Implementation

4.6 Communication Protocol Implementation 1

34
4.7 Login Page

35
4.8 Admin

36
4.9 Admin Page 2

37
4.10 GRN

4.11 Class Diagram

Class diagrams are the main building block in object-oriented modeling. They are used to
show the different objects in a system, their attributes, their operations and the relationships
among them.

38
4.11 Class Diagram 1

39
4.12 ERD

4.12.1 ERD Diagram

40
 Chapter 5: Implementation
This chapter will discuss implementation details supported by UML diagrams (if
applicable).

5.1 Communication Protocol Implementation

5.1Communication Protocol Implementation 1

Explanation:
41
This project Inventory Management System is concerned with different technologies. We
developed a Web base system with front end in xml and backend in C#. The User registers
himself and can Order Through the institute management. The User have to ensure for Order
confirmation. We also have an admin panel which is managed through our application.
When a User Reaches Order of Product and make an order. Its Product number and other
details will be display on Admin Dashboard. Admin will be issue a voucher and make a
confirmation message for the user and orders through tenders.

42
5.2 Component Diagram

5.2 Component Diagram 1

43
Explanation:
In component diagram it has been shown that the User registers himself and make an order
of Product confirm it through payment module. The admin login himself and manage the
dashboard.

5.3 System Component Diagram

5.3 System Component Diagram 1

Explanation:

44
We have Website for which we use Inventory Management System. For Website we have
used SQL Management Studio database.
5.4 Login Page

5.4 Login 1

The user will enter the data for account creation. The validations applied on Signup page are
given below:
1. Email should be valid.
2. Username should contain number and alphabets.
3. Name should only contain alphabets.
4. CNIC should be valid.
5. Password must be more than 5 digits.

45
After checking the given validations and when user press “Signup” button, the user account
will be created successfully.
At login page the user will enter his valid email and password. If the email or password is
invalid/empty the user will not be able to Log in to his/her account, and if the user does not
have any account, then user should first create his/her account on clicking “Sign up” button.
5.5 Admin page 1

5.5 Admin Page 1

5.6 Admin Page 2

46
 5.6 Admin Page 1B

At this interface the Admin will be able to see details of User, Product & Order.

47
5.7 GRN Page 1

5.7 GRN Page 1

48
5.8 Inventory Front

5.8 Inventory Front 1

49
 Chapter 6: Testing and Evaluation
Testing the software application is an important activity in the software development life
cycle (SDLC). It helps in maintaining the quality of the system.
6.1 Introduction

System testing is an essential step for the development of a reliable and error free system.
Testing is the process of executing a program with explicit intension of finding errors. A test
case is a set of data items that the system process as normal input. A successful test is the
one that does find the errors.
Software testing is a process of Verifying and Validating that a software application or
program. Software testing. Software testing also identifies important defects, flaws, or errors
in the application code that must be fixed. Software testing has three main Purposes:
verification, validation, and defect finding.

 The verification process confirms that the software meets its technical Specifications. A
“specification” is a description of a function in terms of Measurable output value given a
specific input value under specific preconditions.
 The validation process confirms that the software meets the business requirements.
 A defect is a variance between the expected and actual result. The defect’s ultimate
source may be traced to a fault introduced in the specification, design, or development
(coding) phases.

6.1.1 Verification

Verification is the process of checking that a software achieves its goal without any bugs. It
is the process to ensure whether the product that is developed is right or not. It verifies
whether the developed product fulfills the requirements that we have.

6.1.2 Functional Testing

Functional Testing is a type of black box testing whereby each part of the system is tested
against functional specification/requirements.

50
  After giving right credentials we are able to login in our system.
 Our system gives error message when user enter incorrect card number.
 Our system successfully shows the record in database of registered users.


6.1.3 Static testing

Static test techniques provide a great way to improve the quality and productivity of
software development. It includes the reviews and provides the overview of how they are
conducted.

6.2 Test Cases

Table 6.2.1 Test Case Admin Login

Test Engineer: Syed Wasif Haider Rizvi

TEST Case ID: TC1

Related UC UC1-Login
Date: 14-02-2022

Purpose: Application user authentication

Test Data: Email & password

Steps: 1. Run the application

2. Enter Email
3. Enter password
4. Click login Status:

Status: Pass

51
Table 6.2.2 Test Case for Register

Test Engineer: Javed Jabbar

TEST Case ID: TC2

Related UC UC2-Register
Date: 14-02-2022

Purpose: Registration for customer information

Test Data: Required data:

First name, last name, user ID, password, confirm password, Email

Steps: 1. Run the application

2. Enter Name
3. Enter Email
4. Enter password
5. Click register

Status: Pass

52
Table 6.2.3 Test Case for Add Product

Test Engineer: Syed Wasi Haider Rizvi

TEST Case ID: TC3

Related UC: UC3-Manage Product

Date: 15-02-2022

Purpose: Add Product

Test Data: Product category,

product title,
Product image,
Product price,
Product description,
Product keyword

Steps: 1. Enter new product

2. Enter product category
3. Enter product title
4. Choose product image
5. Enter product price
6. Enter product description
7. Enter product keyword
8. Click insert product

Status: Pass

53
Table 6.2.4 Test Case for View Product

Test Engineer: Javed Jabbar

TEST Case ID: TC4

Related UC UC4-Manage Product

Date: 16-02-2022

Purpose: View Product

Test Data: Product Title,

Product Image,
product price,
total sold,
status,
edit, delete

Steps: 1. Select view all products

2. View all products detail

Status: Pass

54
Table 6.2.5 Test Case for View Order

Test Engineer: Javed Jabbar

TEST Case ID: TC5

Related UC UC5-Order

Date: 16-02-2022

Purpose: View Order

Test Data: Order No,

Customer ID, Product ID,
Quantity, Status, Delete

Steps: 1. Select view orders from the admin dashboard

2. View all the orders of the customers, as well as status of
orders

Status: Pass

55
Table 6.2.6 Test Case for View Payment

Test Javed Jabbar

Engineer:

TEST Case TC6

ID:

Related UC UC6-Payment

Date: 16-02-2022

Purpose: View Payment

Test Data: Total Amount,

Contact number,
ID card number,
Payment date

Steps: 1. View payment message on given number from admin

2. Compare payment with product price

Status: Pass

56
Table 6.2.7 Test Case for Log Out

Test Javed Jabbar

Engineer:

TEST Case TC7

ID:

Related UC UC7-7

Date: 19-02-2022

Purpose: Logout

Test Data: Logout.

Steps: 1. System Login

2. Click on Logout button.

Status: Pass

57
Table 6.2.8 Test Case for Delete User

Test Engineer: Javed Jabbar

TEST Case ID: TC8

Related UC UC8-8

Date: 19-02-2022

Purpose: Delete an existing user

Test Data: Serial No, Name, Delete

Steps: 1. Select a user by clicking a row in the data grid.

2. Click on the delete button. The user will be deleted from the
appropriate fields.

Status: Pass

58
6.3 Validation
Validation is the process of checking whether the software product is up to the mark or in
other words product has high level requirements. It is the process of checking the
validation of product i.e., it checks what we are developing is the right product. It is
validation of actual and expected product. Validation involves white box testing  is
software testing technique in which internal structure, design and coding of software are
tested to verify flow of input-output and to improve design, usability and security. E.g.;
Payment and Booking module.

6.4 Usability Testing

Usability testing also known as User Experience (UX) testing, is a testing method for
measuring how easy and user-friendly a software application is. A small set of target end-
users, use software application to expose usability defects. Usability testing mainly focuses
on user's ease of using application, flexibility of application to handle controls and ability of
application to meet its objectives. In our project some users test our system and they all are
successfully registered. One user finds the defect in our payment module that you should
add some other ways to enter amount.

6.5 Module/Unit Testing

Unit testing is a confusing part of the software development process. Unit testing involves
individually testing unit of code separately to make sure that it works on its own,
independent of the other units.  Unit testing is essentially a set of paths, test performed to
examine the several different paths through the modules. Unit testing is remarkably done by
programmers with the help of Unit framework. Unit testing is usually an automated process
and performed within the programmers IDE. Unit testing is an action used to validate that
separate units of source code remains working properly. In our project we test the object
detection, payment and booking modules individually for better results.

6.6 Integration Testing

Integration Testing is defined as a type of testing where software modules are integrated
logically and tested as a group. A typical software project consists of multiple software
modules, coded by different programmers. The purpose of this level of testing is to expose
defects in the interaction between these software modules when they are integrated. In our
project, we integrate Payment and Booking modules and they show results successfully.

6.7 System Testing

System Testing is carried out on the whole system in the context of either system
requirement specifications or functional requirement specifications or in the context of
both. System testing tests the design and behavior of the system and also the expectations
of the customer. It is performed to test the system beyond the bounds mentioned in
the software requirements specification (SRS) . In our project we give different inputs as
user required from our system initially and get ninety percent accuracy in it.

59
6.8 Acceptance testing
Acceptance Testing is a method of software testing where a system is tested for
acceptability. The major aim of this test is to evaluate the compliance of the system with
the business requirements and assess whether it is acceptable for delivery or not.
Acceptance Testing is the last phase of software testing performed after System Testing
and before making the system available for actual use. In our system user check all details,
initially face some defects but after negotiating and resolving some defects they accept our
system.

6.9 Stress Testing

Stress Testing is a type of software testing that verifies stability & reliability of software
application. The goal of Stress testing is measuring software on its robustness and error
handling capabilities under extremely heavy load conditions and ensuring that software
doesn't crash under crunch situations. It even tests beyond normal operating points and
evaluates how software works under extreme conditions.

6.10 Hardware Configuration Testing

Configuration Testing is a testing technique in which the software application is tested with
multiple combinations of hardware in order to evaluate the functional requirements and find
out optimal configurations under which the software application works without any defects
or flaws. We connect Camera with our system and run it successfully.
6.11 Evaluation
Evaluation was done as we completed our project by correctly evaluated things and
completed them on time.

6.12 Deployment
Our project deploys in real time environment and it works accurate. There is proper
exchange of information between system and application, hence deployment was also done.

6.13 Maintenance
Maintenance was done as we fulfilled all the objectives of the project and maintained all the
detection and correction of errors in the system.

60
 Chapter 7: Conclusion and Future Work
This chapter concludes the project and highlights future work.

7.1. Conclusion
This project Inventory Management system is an automated system which has two main
users. User and Admin, Web Application has registration, order payment and dashboard
management module.
This application is based on the management of stock of that institute. It contains general
institute profile, sales details, Purchase details and the remaining stock that are presented in
the institute. There is a provision of updating the inventory also. This application also
provides the remaining balance of the stock. Each new stock is created and entitled with the
named and the entry date of that stock. Here the login page is created in order to protect the
management of the stock of organization in order to prevent it from the threats and misuse
of the inventory.

7.2. Future Work

 We are planning to do following advancements in our project in future.
 Addition of order time more reliable module
 Facilitating the user by providing order cancellation option after payment as well and
refunding of payment.
 Extension of the dedicated Inventory system to the orders of all the product of all over
the country.
 Improvements in the designing and performance of software.

61
 References
1. http://ijcsit.com/docs/Volume%205/vol5issue03/ijcsit2014050370.pdf
2. http://users.csc.calpoly.edu/~jdalbey/205/Lectures/HOWTO-ERD.html
3. https://ieeexplore.ieee.org/document/8743906
4. Technology Function Software House
5. http://www.cse.msu.edu/~cse870/IEEEXplore-SRS-template.pdf
6. https://www.scaledagileframework.com/nonfunctional-requirements/

62