KEMBAR78
Project Report | PDF | Software Testing | Feasibility Study
0% found this document useful (0 votes)
8 views88 pages

Project Report

The document is a project report for a Master's or Bachelor's degree in Computer Applications, detailing the development of an Inventory Management System for the textile industry in Panipat. It outlines the need for modernizing inventory management practices among local handloom companies, which currently rely on outdated methods. The report includes acknowledgments, declarations, company profiles, project descriptions, and various chapters covering feasibility studies, system design, and implementation details.

Uploaded by

callmeluffy7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views88 pages

Project Report

The document is a project report for a Master's or Bachelor's degree in Computer Applications, detailing the development of an Inventory Management System for the textile industry in Panipat. It outlines the need for modernizing inventory management practices among local handloom companies, which currently rely on outdated methods. The report includes acknowledgments, declarations, company profiles, project descriptions, and various chapters covering feasibility studies, system design, and implementation details.

Uploaded by

callmeluffy7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 88

“PROJECT NAME”

A Project Report submitted in partial fulfillment of the requirement


For the award of degree of

Master of Computer Applications /

Bachelor of Computer Applications

(CTIS/DS)

Batch

Supervised By Submitted By
Internal Mentor Name Student Name
Designation MCA III Sem
Department of Computer Applications University/Autonomous Roll no

Department of Computer Applications


PANIPAT INSTITUTE OF ENGINEERING & TECHNOLOGY

KUKRUKSHETRA UNIVERSITY, KURUKSHETRA

Batch

1
Acknowledgement

A successful completion of this project is attributed to the great and indispensable help
received from different people.

I will always be grateful and thankful to Head of Department Dr. Dinesh Verma and
Project Mentor Internal Mentor Name for giving me the opportunity to learn the
different aspects of designing and implementing this system. It would never be possible
for me to design this system without your continuous assistance and guidance.

I want to thanks to my project lead External Mentor Name for providing me platform,
necessary facilities, guidance and support for completing this project.

I would like to thanks to all faculty members of Computer Applications Department


who are always encourage me during progress of this project.

Student Name

2
Declaration

I, Student Name, a student of Master of Computer Applications, in the Department of


Computer Application, Panipat Institute of Engineering and Technology, Panipat, under
class Roll No. _______ and University Roll No. ____________for the Session batch,
hereby, declare that the project report Project Code as per scheme entitled “Project
Name” has been completed by me in ______semester during the two-month project
training. I hereby declare that the matter embodied in this project is my original work and
has not been submitted earlier for award of any degree or diploma in any college or
university.

Date: Student Name

3
Department of Computer Applications Panipat Institute of
Engineering and Technology, Samalkha Certificate
It is certified that Student Name, a student of Master of Computer Applications, under
class Roll No. ________and University Roll No. _________ for the Session _______
(batch), has completed the project entitled “Project Title” under my supervision.

The project report is the authenticate work of the candidate as per her declaration and is
found to be fit for the award of degree of Master of Computer Applications in
accordance with the rules and regulations of Kurukshetra University, Kurukshetra as per
my opinion.

I wish her all the success in her all endeavors.

Internal Mentor Name

Designation

Department of Computer Applications, PIET

Counter-signed by

HOD-Computer Applications

4
Certificate from Company

List of figures

Fig Number. Caption Page No.

5
List of Tables

Table Number Caption Page No.

6
Table of Contents
Acknowledgement 2
Certificate from the Student 3
Certificate from the Department 4
Certificate from Company 5
List of Figures 6-8
List of Tables 9

Chapter 1 Company Profile 15


1.1 About Company 16
1.2 Products & Services 16
1.2.1 Website Services 16
1.2.2 Software Development 17
1.2.3 Mobile App Development 17
1.2.4 SEO Services 17
1.2.5 Digital Marketing Services 18
1.2.6 Ecommerce Development 19
1.3 Culture and Environment 19

Chapter 2 Project Description 20


2.1 Project Title 21
2.2 Overview 21
2.3 Need and Purpose 21
2.3.1 Need 21
2.3.2 Purpose 22
2.3.3 Benefits 23
2.4 Hardware Requirements 23
2.5 Software Requirements 23
2.6 Application Architecture 24

7
2.7 Features 25

Chapter 3 Feasibility Study 26

3.1 Overview 27
3.2 Technical Feasibility 28
3.3 Economic Feasibility 28
3.4 Legal Feasibility 29
3.5 Operational Feasibility 29
3.6 Scheduling Feasibility 30

Chapter 4 Requirement Analysis 31


4.1 Overview 32
4.2 System Analysis 32
4.3 Requirement study/analysis 33
4.3.1 Present System & Identification of Needs 33
4.4 Software Requirement Analysis 34

Chapter 5 System Design 35


5.1 Overview 36
5.2 Entity-Relationship Diagram 36
5.2.1 Components of ER Diagram 37
5.3 Data Flow Diagrams 38
5.3.1 0-Level DFD 39
5.3.2 1-Level DFD 39
5.4 Class Diagram (Not for BCA Students) 40
5.4.1 Class Diagram for Attendance System 38
5.5 Activity Diagram 41

Chapter 6 Testing 42
6.1 Introduction 43

8
6.1.1 Objective 43
6.2 Formal Technical Review 43
6.3 Types of Testing 44
6.4 Testing Strategy 45
]6.5 Test Cases 46

Chapter 7 Implementation 49
7.1 Software Used 50
7.2 Hardware Specification 50
7.3 Platform 50
7.4 Languages Used 50
7.4.1 DJANGO 50
7.4.2 MYSQL 53
7.4.3 JavaScript 53
7.4.4 HTML 54
7.4.5 CSS 54
7.4.6 JQUERY 55
7.4.7 AJAX 55
7.4.8 BOOTSTRAP 55
7.4.9 VPS 56

Chapter 8 Snapshots/ Forms 57


8.1 Home Page 58
8.2 Filters 59

8.2.1 Bale Filter Screen 59

8.2.2 Bale Quality Report 59

8.2.3 Bale Size Report 60

8.2.4 Roll Filter Data 61

9
8.2.5 Roll Quality Report 62

8.2.6 Role Design Report 62


8.2.7 Master Table Bale Quality 63

8.2.8 Master Table Bale Pieces 63


8.2.9 Master Table Roll Quality 64
8.2.10 Master Table Print 65

8.2.11 Create User 66

8.11.12 User List 66


Chapter 9 Maintenance and Evaluation (Not Mandatory) 83
9.1 Introduction 84
9.2 Types of Maintenance 85
9.3 Cost of Maintenance 86
9.4 Maintenance Activities 87

Chapter 10 Future Scope and Conclusion 89


10.1 Conclusion 90
10.2 Future Scope 90

Bibliography 91

10
Chapter 1
Company Profile

11
Chapter 1 Company Profile

1.1 About Company

Geoms Digital House Private Limited is a leading service provider of software


development service for Web Designing, Mobile Application Development Services.
Geoms Digital House Private Limited specializes in offering Software development
service for web designing, mobile application development services etc. The Geoms
Digital House Private Limited family is committed to do work within a time frame
which is set by our valued clients.

1.2 Products & Services


Information about the products/services of the company

1.2.1 Website Services

At Geoms Digital House Private Limited, you will meet the experts and talented web
developers and designers who can handle your website in no time. They have the ability
to understand the concept of each kind of websites. Our experts have experience in

12
building all kinds of website designs. They will create designs which have perfect
design Interface, search engine friendly, and overall consistent designs. Our company is
a trusted digital service provider and website designing company in the Haryana, India.

1.2.2 Software Development

Geoms Digital House Private Limited is the best destination for those who are looking
for best Software development provider in Haryana. 5 years of experience makes us
excellent and feasible Software Development Company. We offer all kind of Software
Development technologies and methods including Application Development, Web
Technology etc. We are specialized in developing multiple applications to improve the
client’s productivity, market value and earn more profit. Our main concern is to provide
excellent software solutions to our respective clients. Browse our website and search the
services we are offering for the convenience of our clients.

1.2.3 Mobile App Development

Whether you are taking an existing iPhone app and developing a counterpart for
Android or devising an entirely new app from scratch, it’s essential to align yourself
with the right development professionals. Simply put, you want a company you can
trust, with plenty of experience and design excellence that can provide you with what
you need for a dollar amount you can afford. Sounds simple enough, right?

At Geoms Digital House Private Limited, we try to make Android mobile application
development in Haryana as simple as it can be. We know that businesses and
entrepreneurs often compare multiple app developers before hiring someone to do the
work. This comparison process often includes price shopping, work sample review and
‘pro and con’ lists. Our goal is to be the app development company in Haryana with all
pros and no cons.

1.2.4 SEO Services

Search engine optimization is the most crucial requirement for inbound marketing
success. Being found online in search engines is not just a luxury, its a necessity in

13
today’s competitive marketplace. In fact, in our experience, consistent high visibility in
search results is the most cost-effective long term marketing strategy most companies
should be pursuing for sustained growth.

• It has been a long term goal of ours to be the best SEO agency in Haryana. Not
just the best at delivering rankings. Not just the best at delivering organic search
traffic. The best at delivering qualified traffic that helps grow inquiries and sales.

• Why do we want to be the best SEO agency in Haryana? Because Search Engine
Optimization (SEO) is the best way we know for you to attract new, motivated
customers and grow your business.

• The problem is that most SEO agencies have it wrong because they focus on
rankings, not revenue. At Geoms Digital House Private Limited, all we care about
is how many new customers we can drive to your business. We have been helping
clients around Haryana with search engine optimization since 2010. Our team has
some of the leading SEO experts in Haryana.

1.2.5 Digital Marketing Services

Geoms Digital House Private Limited provides a wide range of top-notch digital
marketing services to clients around Haryana. We are a premier digital marketing
agency offering unique methodologies to ensure outstanding solutions for clients from
any sector. Your business can be assured of online success with our customized digital
marketing strategy.

Our Process

1 Each step we practice is and backed by analysis and information. This enables us
to formulate efficient plans over each system.

2 We develop practical experiences that can amaze and entertain customers over all
platforms. We also help you to create the best relationships between the product
and the consumer.

3 We build the right content that is useful and apt for your brand. So that the user
can get the necessary information about your brand.

14
4 We constantly optimize your website for better results.

1.2.6 Ecommerce Development

A leading ecommerce development company in Haryana, Geoms Digital House Private


Limited helps businesses to build successful ecommerce websites. code to be executed
if condition is false; Ecommerce development team at our offshore ecommerce
development center in Haryana draws from their expertise in marketing, analytics, and
technology to offer end-to-end ecommerce solutions that drive your customers to buy.

A store that is disorganized and unappealing doesn’t sell, and that is why we never cut
corners on the design of an ecommerce website. You care for your customer, and offer
the best products — and we translate that to online language by means of a clean,
attractive and comfortable ecommerce solution. Every pixel, every picture and every
word is planned to give a good impression to your customer. We ensure that the site is
easily navigated and delivers a great shopping experience.

1.3 Culture and Environment


The company’s culture is a non-hierarchical that means all employees are working
together without any divisions. All employees are worked as a team according to their
work.

15
Chapter 2 Project
Description

16
Chapter 2 Project Description
2.1 Project Title
Inventory Management System in Textile

2.2 Overview
There is hardly any country, where handloom products manufactured in Panipat are not
supplied. The city is globally known as the ‘Textile City’. There in Panipat we have all
type of handloom companies like small , medium , big they all export their
products all around world. Panipat is a center of handloom products where carpets,
cushions, velvet cushions, sofa fabrics, bed sheets, curtains and towels among other
things are manufactured.

• Small and big industries 30,000 (approx)

• Total turnover Rs35-36 crore (approx)

• Domestic market Rs27,000-Rs28,000 crore (approx)

• Export turnover Rs8,000 crore (approx)

In Panipat even a small company can produce approx. 500 products


daily. Most of these does not have any Inventory system where
they can maintain their stock details, patched details and
dispatched details or mostly use outdated unsecured software.
I discussed about this with some companies and find that they all have
some issue in their inventory software also some of them don’t have
any special software for that.
This software would feature them two account one master account for
admin where they can manage everything add , update , delete , dispatch
any product data and an another account for their workers where they can
only add product and dispatch product.

2.3 Need and Purpose


2.3.1 Need

17
▪ To overcome the traditional process of maintaining Inventory record.
▪ As we know till today many handloom companies are using the old
methodology of keeping inventory record which is difficult as well as time
consuming. So, to reduce teacher’s load to maintain inventory registers we
need the proposed system.
▪ Traditional methodology include paper work which is difficult at last of the
session when accontant,managers have to give complete session’s inventory
status of all products or a particular company that they supplied their
products. So to reduce paper work we need this proposed system.
▪ Traditional approach is weary task for employes to take records. To make it
an easy task we can adopt the proposed system.
▪ As inventory is maintained in registers in today’s approach it is difficult to
maintain for long time or we can say for future. Using the proposed system it
is easy to maintain large amount of data easily or can be accessed in future
anytime.

2.3.2 Purpose

Purpose to develop “Inventory Management System in Textile”

▪ To reduce manual efforts.


▪ To generate Inventory records in an organized format.
▪ To check inventory records of a particular product type at any time at
anywhere.
▪ It helps to maintain accurate results.
▪ When we have to deal with large amount of data then this will be weary task
for employes to give outcome on the spot. So to handle such type of
situations the proposed system should be adopted.
▪ By utilizing this system into daily inventory records it will helpful to
maintain and organize data.
▪ If we want to make a list of products either available or not within given
dates i.e. Starting date to required date it is difficult in traditional approach to

18
do this. So, to overcome this typical task we can use this system. By enter the
product name and selecting the dates on the dashboard the complete status of
the product can be fetched .

2.3.3 Benefits
▪ Minimal paper work.
▪ Less time consuming.
▪ User-friendly Interface.
▪ Cost Effective.
▪ Fast report generation.
▪ Access anytime.
▪ Easy remote access.
▪ Easy to handle data of large number of inventory records.
▪ Can store large amount of data and kept secure for future.
▪ Easily manageable.
▪ Show accurate timings of attendance.

2.4 Hardware Requirements


□ Processor type : x64 or x86 compatible processors
□ RAM : 1GB minimum
□ Processor Speed : 1.4GHz; recommended 2GHz or faster

2.5 Software Requirements

□ Compatible Browsers : Chrome, Firefox, Opera ,Edge


□ Languages : HTML, CSS, ,python, JavaScript, JQuery,
JSON, AJAX, SQL
□ Database : MySQL
□ IDE : Pycharm
□ Application Stack : Apache Server
□ Backend Framework : Django

19
2.6 Application Architecture
While using the traditional approach it is difficult to handle and maintain records
and also time consuming to find data when we required inventory data. So,
Inventory Management System can resolve such type of issues. The Online
Inventory system is a Three-Tier Architecture.

The three-tier Architecture for the proposed system is defined as:


▪ Presentation: Presentation tier is at the top level which shows the services of the
system to users of the system i.e. Admin, Employee. The presentation tier is can
be introduced as Front-End of the system which is designed using web
development frameworks such as: CSS, JavaScript, JQuery, Bootstrap and
communicate with other levels of system. It is the interface with which users of
the system will interact with the proposed system, it gathers the information from
the user, perform some investigations and provide the connection with the server.

▪ Application:
Application tier is used for many purposes. This is responsible for running
the application, includes all functionalities such as perform functionality of
database, get requests from user/client perform on requests and gives the
appropriate result. This is also known as middle-tier or logic-tier which gets
request of user from the presentation tier. It is designed using Django
Python Framework.

• Handle requests

• Request evaluation

• Controls core functionality

Data:
Data tier deals with database servers. To store and retrieve data against any
query request data tire is responsible for this task. It is accessed and

20
managed through a program. For this application I have used MySQL for
database.

2.7 Features
The features of this application (Inventory Management System in Textile ) are:
Features Description

Auto Barcode
This software have a special feature that create of every
Generator
product unique barcode .

Product patched Details It show is your product is packed or not.

Product dispatch
details It shows product Dispatch details when the product is
dipatched , who buy the product and other info.

Responsive Design Capable for every device smartphones,tablets,


Laptop,Desktop

Daily Monthly yearly


weekly report It have special filters that can generate report of your
products daily monthly weekly yearly

Master table for


admins Admins have some master table where he can control all
the users data

User authentication
Secure login with authentication

Trash option
Here you have a trash option where you can remove from
inventory damaged products.

Table 2.1 Features of proposed system

21
Chapter 3
Feasibility Study

22
Chapter 3 Feasibility Study

3.1 Overview
A feasibility analysis is essential to determine the practicability of an idea to meet the
performance requirement of any proposed system. It is done to reveal whether the
project is feasible or not. This study ensures that the proposed idea is possible or not. It
is the initial design stage of any project. This type of study can determine if the project
will be implemented or not. It is the key resource to examine the scope of any project.
As the analysis implies that we have to cover some aspects to check the feasibility of the
project. The main goals of feasibility study are as follows:

▪ To understand all aspects of project


▪ Concept development
▪ Determining the scope
▪ Determining the market values
▪ To measure cost Benefit analysis
▪ To check compatibility with existing system
It is a formal documentation of any project which provides the summarized information
about “What is going to be done”.

The feasibility study includes:

▪ Scope of the project


▪ Analyse current market trends and scenarios
▪ Detailed Risk Analysis
▪ Evaluating Cost Analysis
▪ Make Assessment
▪ Recommendations and conclusions

23
Preliminary investigation of any project is its Feasibility Study. This report provides
overview of all relevant data. There are five major dimensions of feasibility study
acronym as TELOS: Technical, Economic, Legal, Operational and Scheduling. If these
five dimensions are successfully tested for adding new modules and debugging existing
running system.

The types of feasibility study that are covered during preliminary investigation:

▪ Technical Feasibility
▪ Economic Feasibility
▪ Legal Feasibility
▪ Operational Feasibility
▪ Scheduling Feasibility

3.2 Technical Feasibility


Technical feasibility revolved around the existing system and the requirements of
proposed system.

Basically this is the assessment which provides the information about the resources
required to develop the proposed system and how much the system is capable to carry
out the implementation of proposed system.

Let’s take an example according to this system which is currently run on local server.
So, to run this system on local machine we need some software which helps to run this
system’s functionality. So, that software is technically required for this system. If the
required softwares and hardwares will be easily available it means the system is
technical feasible.

Since required software i.e. Apache and django application and necessary hardware to
run this system (Inventory Management System) are easily available. Hence, the system
is technically feasible. The essential questions which should be covered during technical
feasibility study are as following:

• Is the proposed system is practicable?


• Is the system is available in inadequacy of resources?

24
• Does the necessary technology exist?
• Does the system capable for up gradation if required in future?
• Does the system capable to handle the queries and solutions?
• Are the existing technologies enough to develop new proposed system?

If the answer of the above questions are Yes then it is technical feasible.

3.3 Economic Feasibility


It is the study which refers to cost analysis. It is the assessment of checking cost benefit
analysis. It is also a method which helps the organizations to determine the investment
on the system and the future benefits. Economic feasibility is also used to evaluate the
effectiveness of the proposed system.

As cost is the important factor, so it must be checked that the system will be economical
feasible or not so that it can be determined that proposed system should be continued or not.

The questions which should be covered during the economic feasibility study/analysis
are as following:

• Estimated cost of required software and hardware.


• Estimated cost of system development
• Determine cost with its total expected benefits
• Determine the savings which will be result from the proposed system Does the
system cost effective or not?
These are some key points which should be kept in mind during the phase of economic
feasibility. If these questions will be answered yes then the system can be implemented
otherwise there may be chances of rejection or enhancements according to requirements.

3.4 Legal Feasibility


It is the assessment which provides the information about that the proposed system
doesn’t violate any law. It is the study to determine whether the proposed system
conform the legal and ethical requirements. This study includes ethical issues and social
issues. Main objective to perform legal feasibility is:

• To check that the proposed system is legally feasible

25
• To facilitate risk mitigation
3.5 Operational Feasibility
Any project/system will be beneficial only if they can be turned out into an information
system. If the proposed system meets the organization’s requirements then it means that
the proposed system is operationally feasible. It is an important part of project
implementation. As it is dependent on human resources for the system involves in either
development or maintenance or implementation. It is the study/analysis that tells us how
well proposed system solves the user quires.

Some questions are raised during the operational feasibility are as follows:

• Is the system solving problem properly


• Does management supports the system
• Does the system satisfies the required requirements listed in technical feasibility
phase

3.6 Scheduling Feasibility


This is the study to determine whether the proposed system will complete on scheduled
time period. It means how long project will run.

Feasibility study is not only about collecting information and determining the
requirements but scheduling feasibility study is also an important factor which provides
the report of deadlines for the system. According to deadlines mentioned in report
generating during scheduling feasibility it can be determined easily whether the
proposed system will complete on prescribed time or not. If the system will done on the
prescribed time then the system is acceptable.

26
Chapter 4 Requirement
Analysis

27
Chapter 4 Requirement Analysis

4.1 Overview
In this chapter we can study about the analysis which developers will do during
development of system/project. It contains the requirement observations which are
performed by developers so that project should be developed and delivered on time.
There are various requirements which are important and all these are mentioned in this
chapter. Before starting any project or system there are some factors which must be
analyzed as it is an important phase of project development. The requirement analysis
and specification phase starts when feasibility study is done and it will start when the
project is economically and technically sound feasible. The main goal of this phase is to
understand requirements of customer so that project/system should meet the customer’s
requirements. It is important because after analyzing the requirements of customer all
collected data is formatted and arranged in a document. This document is also known as
RAD (Requirement Analysis Documentation), which is important for any developer to
go through this RAD to understand what outcome customer wants from the proposed
system. SRS plays an important role in project/system development. As RAD is a report
which describes about the system output and for those corresponding input
requirements. In short RAD is a report which contains all functional and non-functional
requirements.

4.2 System Analysis


System analysis is the process that involves gathering of factual data, system
functioning or we can say what should be the output of proposed system. It is the study
from that developer team can understand the process involved and identifying the
problem. This involves the study of business process, gathering the functional as well as
functional data of the system, understand the flow of system. It is an important factor

28
that system meets the customer requirement. So, system requirement is the phase which
makes a bridge between customer requirement and developers team.

The main goal/objective of system analysis phase is as follows:


• What are the customer’s requirements?
• What are the customer’s expectations?
• Flow of data .What is being done?
• How it is being done?
• Who can do this?

4.3 Requirement Analysis/Study


Requirement analysis is the process of understanding user’s or customer’s expectations. It
is important to understand the user’s expectations because if the system meets the user’s
satisfaction then the system is considered useful and acceptable otherwise system is not
considered. It is important to gather information for a new and modified system
according to user’s expectations. This feature is called requirements must be perceptible,
relevant and detailed.

This is also an important factor of project management. Frequent meetings with


customer/user are important to know the requirements time to time as customer’s
requirements may be changed as previously documented. There may be chances of
ambiguity or conflict in requirements as demanded previously by the users.

It is not only the task of one person but it is a team effort that is combination of hardware,
software and public dealing expertise.

There are many fact finding techniques which can be used by developer to gather the
information about system requirements.

4.3.1 Present System & Identification of Needs

Present system requires lot of manual work to maintain inventory record. Present system
is time consuming to search any dispatched product or packed product record. To
maintain and track product record is very important for any textile industry or

29
organization. It is difficult to access current system anytime means in case of emergency
it is difficult to access and give report.

Why we need this application?

So to overcome these problems we can use the proposed system which will able to do all
these tasks at anytime without time consuming.

4.4 Software Requirement Analysis


Software Requirement Specification (SRS) is the starting point of the software
development activity. It is a complete description of the behavior of a system which is to
be developed. The SRS document includes all necessary requirements for project
development. To determine the requirements we need to have clear and thorough
understanding of the system which is to be developed. This is prepared after detailed
communication with project team and the customer/user.

An SRS minimizes the time and effort required by developers to achieve desired goals
and also minimizes the development cost. A good SRS defines how an application will
interact with system hardware, other programs and human users in a wide variety of
realworld situations.

The goal is to design a recommender system on domain. The system will be composed of
server side components and client side components. The server-side component will
manage the database operations and algorithms that produce recommendation results.
The client-side components will be graphical interfaces that are integrated into
corresponding larger systems.

30
Chapter 5
System Design

31
Chapter 5 System Design

5.1 Overview
This chapter includes the designs which are related to our project that describes about
the aspects of the system. This chapter includes Data Flow Diagrams (DFD’s),
EntityRelationship Diagram, Structure of database, Class Diagram, Activity Diagram.
Design is the first step which is required to understand the flow of data, input interface
and output screen looks like.

There are some key points why we system design is important. These are as follows:

• To understand the flow of data


• To visualize the customer’s expectation
• For better productivity
• To understand the activities performed on system
• To determine the relationship between entities of the system
• To determine the relationship between system modules
• It helps in understanding results comes from previous phases
• To create a better view of system
• Reveal design issues and flaws
• To visualize the interaction between objects of system
• Designs are helpful to implement code

5.2 Entity-Relationship Diagram


ER Diagrams was first developed by PETER CHEN in 1976. When we are using
database it must be understand the relationship between data. It is used to describe the
structure of database with the help of diagram. Entity-Relationship diagrams act as a
tool to build the logical database design of the system.

There are some factors which tell us why we need Entity-Relationship Diagrams. These
are as follows:

32
• To determine the logical structure of database
• To define about the entities and their attributes
• To show relationship between entities
• To visualize the entities within the system scope
5.2.1 Components of ER Diagram

ERD is basically consists of five main components:


Features Description

Entity
Entity is anything real or concept or abstract about which we can
store data. Those have some information are entities. It is
represented as a rectangular box. Entities of the proposed system
are: admin,employee,roll,bale,etc.

Relationship
Relationship is an action which defines how entities will share the
data. It is represented by diamond shape. It acts as an association
between entities. e.g. Create roll

Cardinality
Defines how instances of entities are related to other entities. It also
defines the number of instances of entity relate to instance of another
entity. It basically specifies the occurrences of entities. e.g. Create
roll, print it and dispatch

Attribute
Attributes are the characteristics of any entity. It may be common to
all or most instances of a particular entity. Attribute can be said as
field, data entry. e.g. username, barcode, rolllid, baleid, etc.

Table 5.1: Features Table

33
Figure 5.1: ER Diagram

5.3 Data Flow Diagram


Data Flow Diagram was developed by LARRY CONSTANTINE. These were
popularized in late 1970s. This is the method to show the system requirements
graphically.

It is a traditional visual representation of the flaw of information. It can be designed


manually, automated or combination of both. They can be used to analyze an existing
system or model new one.

34
DFD is can be divided into Logical and Physical. Logical DFD represents the flow of
data into the system whereas Physical DFD represents how the flow of information will
be implemented. DFD is used or designed for:

• To determine the logical flow of the information


• To determine the implementation of logical flow
• To determine the physical construction of the system
• To arrange the system requirements in a format so that system will easily be
determined

These are some reasons why do we need a DFD in system/project development or


software engineering. A clear and neat DFD is helpful to develop an efficient and
quantifiable system.

Data Flow Diagram is categorized mainly into these levels:

• 0-Level DFD
• 1-Level DFD
5.3.1 0-Level DFD

0-level DFD is also known as Context design and fundamental design of a system. It is
used to represent whole system/software into a single bubble with input and output data
indicated by arrows.

Figure 5.2: 0-Level DFD

5.3.2 1-LEVEL DFD

In this we process the process of level 0 DFD and expand it. Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the

35
system is divided into sub-systems (processes), each of which deals with one or more of
the data flows to or from an external agent, and which together provide all of the
functionality of the system as a whole. It also identifies internal data stores that must be
present in order for the system to do its job, and shows the flow of data between the
various parts of the system.

▪ This level DFD states the inner process of each module.


▪ How these processes take place with the help of entities include in it.

Fig 5.3 1-level DFD

5.4 Class Diagram


The class diagram is the main building block in object oriented modeling. They are
being used both for general conceptual modeling of the systematic of the application,
and for detailed modeling translating the models into programming code. The classes in
a class diagram represent both the main objects and or interactions in the application
and the objects to be programmed.

36
In the conceptual design of a system, a number of classes are identified and grouped
together in a class diagram which helps to determine the statically relations between
those objects. With detailed modeling, the classes of the conceptual design are often
split in a number of subclasses.

In order to further describe the behavior of systems, these class diagrams can be
complemented by state diagram or UML state machine. Also instead of class diagrams
Object role modeling can be used if you just want to model the classes and their
relationships.

5.5 Activity Diagram


Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by- step workflows of components in a system. An activity diagram
shows the overall flow of control.

37
Chapter 6
Testing

38
Chapter 6 Testing

6.1 Introduction
Testing accomplishes a variety of things, but most importantly it measures the quality of
application that is developed. This view presupposes that there are defects in application
waiting to be discovered.

Testing plays a vital role in the success of the system. System testing makes the logical
assumptions that if all the parts of the system are correct, the goal will be successfully
achieved. Once program code has been developed, testing begins. The testing proves
focuses on the logical internals of the application, ensuring that all statements have been
tested, and on the functional externals, that is conducting tests to uncover error and
ensure that define input will produce actual results that agrees with required results .

6.1.1 Objective

▪ Testing is a process of executing a program with intent of finding an error.


▪ A good test case is one that has a high probability of finding an as–yet
undiscovered error.

▪ A successful test is one that uncovers an as–yet undiscovered error.

6.2 Formal Technical Review


In each Formal Technical Reviews, the steps were as follows:

▪ The meeting was planned in advance and all the team members were intimated.

▪ The project modules to be reviewed were decided.


▪ The module was discussed in detail, as regarding its design and
implementations. The working of the module was checked and conformity to
requirements was tested.

▪ The team took one of the three decisions regarding the modules, based on
review:

39
1 Accept the module as it is, without change or modification
2 Accept the module, with few changes or modifications

3 Reject the module entirely and re-implement it.

▪ The reviews, suggestions and decisions were documented.

▪ In each Technical Review, the point put up in previous session was followed up.

6.3 Types of Testing


• Unit Testing

• Integration Testing

• Validation testing

• System Testing

Unit Testing:

In computer programming, unit testing is a verification and validation method in


which a programmer tests if individual units of source code are fit for use. A unit is the
smallest testable part of an application. In procedural programming a unit may be an
individual function or procedure.

Integration Testing:

Integration testing is the phase in software testing in which individual software


modules are combined and tested as a group. It occurs after unit testing and before
system testing. Integration testing takes as its input modules that have been unit tested,
groups them in larger aggregates, applies tests defined in an integration test plan to
those aggregates, and delivers as its output the integrated system ready for system
testing.

Validation Testing:

Validation is the process of checking that a product, service, or system meets


specification and that it fulfills its intended purpose Validation is Quality assurance
process of establishing evidence that provides a high degree of assurance that a product,

40
service, or system accomplishes its intended requirements. This often involves
acceptance of fitness for purpose with end users.

System Testing

• System testing of software or hardware is testing conducted on a complete,


integrated system to evaluate the system's compliance with its specified
requirement. System testing falls within the scope of black box testing, and
as such, should require no knowledge of the inner design of the code or
logic.

• As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the
software system itself integrated with any applicable hardware system. The
purpose of integration testing is to detect any inconsistencies between the
software units that are integrated together or between any of the assemblages
and the hardware

6.4 Testing Strategy


To be truly robust, application require more than simple functional testing before release
into production. At least one and preferably all of the following types of testing before
releasing application to customers should be performed.

▪ Performance Testing
▪ Load Testing
▪ Stress Testing
Performance Testing:

Performance Testing covers a broad range of engineering or functional evaluations


where a material, product, system, or person is not specified by detailed material or
component specifications rather, emphasis is on the final measurable performance
characteristics. In the computer industry, software performance testing is used to
determine the speed or effectiveness of a computer, network, software program or

41
device. Qualitative attributes such as reliability, scalability and interoperability may also
be evaluated. Performance testing is often done in conjunction with stress testing.

Load Testing:

Load testing is the process of putting demand on a system or device and measuring its
response Load testing generally refers to the practice of modeling the expected usage of
a software program by simulating multiple users accessing the program concurrently.

As such, this testing is most relevant for multi-user systems; often one built using a
client/server model, such as web servers.

Stress Testing:

In software testing, "System stress test" refers to tests that put a greater emphasis on
robustness, availability, and error handling under a heavy load, rather than on what
would be considered correct behavior under normal circumstances. In particular, the
goals of such tests may be to ensure the software does not crash in conditions of
insufficient computational resources (such as memory or disk space), unusually high
concurrency, or denial of service attacks.

6.5 Test Cases:


Step Test Test Case Prerequisite Step Expected Actual
No CaseID Name Description Result Result

1 TO_01 Generate all the fields Please Roll /Bale Roll/


Roll/Bale must be check your Not created Bale
details cretaed.
filled

42
2 TO_02 Generate all the fields All fields Roll/Bale Roll/Bale
Roll/Bale must be are filled Created Created
correctly. successfuly successfu
filled ly

3 TO_03 Generate All the fields One field is This filler is Please
Roll/Bale must be not filled. missing check
your
filled details

4 TO_04 User create by No Plese insert Please insert


admin No
Information record record
result
filled
Should
Display

All
Display Display
Information Display
Filled User List User
User List
accurately
List

43
5 TO_05 Report Report Report
Generation generatio generat
n fsucces
Filter used ed
according to accepte
Use filter
need d.

6 TO_06 Dispatch Submission List


roll/bale not allowed dispatc
Show error
h give
Add roll/bale already
error
that already dispatched
dispatched

7 TO_07 Trash If item Unable to Dont show No


dispatched trash Trash Button Result

If item is Able to Trash Show Trash Add the


packed only Button item to
Trash

Table 6.1 Test Cases

44
Chapter 7
Implementation

45
7.1 Software Used

□ Compatible Browsers : Firefox, Safari, Opera, Chrome, Edge

□ Database : MySQL

□ IDE Tools : Pycharm

□ Languages : HTML, CSS, PHP, SQL, JavaScript,


JSON, JQuery ,Python

□ Backend Framework : Django

□ Application Stack : Apache Server , Django Enviroment

7.2 Hardware Specification


□ Microprocessor - 1.4 GHz; recommended 2 GHz or faster.
□ RAM - 1 GB

7.3 Platform
□ Operating System - Ubuntu

7.4 Languages Used


Following technologies that are used by Inventory Management System is -

7.4.1 Python Django Framework


Django is a high-level Python web framework that enables rapid development
of secure and maintainable websites. Built by experienced developers, Django
takes care of much of the hassle of web development, so you can focus on

46
writing your app without needing to reinvent the wheel. It is free and open
source, has a thriving and active community, great documentation, and
many options for free and paid-for support.

Django helps you write software that is:

Complete
Django follows the "Batteries included" philosophy and provides almost
everything developers might want to do "out of the box". Because everything
you need is part of the one "product", it all works seamlessly together, follows
consistent design principles, and has extensive and up-to-date documentation.

Versatile
Django can be (and has been) used to build almost any type of website — from
content management systems and wikis, through to social networks and news
sites. It can work with any client-side framework, and can deliver content in
almost any format (including HTML, RSS feeds, JSON, XML, etc). The site you
are currently reading is built with Django!

Internally, while it provides choices for almost any functionality you might
want (e.g. several popular databases, templating engines, etc.), it can also be
extended to use other components if needed.

Secure
Django helps developers avoid many common security mistakes by providing a
framework that has been engineered to "do the right things" to protect the
website automatically. For example, Django provides a secure way to manage
user accounts and passwords, avoiding common mistakes like putting session
information in cookies where it is vulnerable (instead cookies just contain a
key, and the actual data is stored in the database) or directly storing passwords
rather than a password hash.

A password hash is a fixed-length value created by sending the password


through a cryptographic hash function. Django can check if an
entered password is correct by running it through the hash function and
comparing the output to the stored hash value. However due to the "one-way"
nature of the function, even if a stored hash value is compromised it is hard for
an attacker to work out the original password.

Django enables protection against many vulnerabilities by default,


including SQL injection, cross-site scripting, cross-site request forgery.

47
Scalable
Django uses a component-based “shared-nothing” architecture (each part of
the architecture is independent of the others, and can hence be replaced or
changed if needed). Having a clear separation between the different parts
means that it can scale for increased traffic by adding hardware at any level:
caching servers, database servers, or application servers. Some of the busiest
sites have successfully scaled Django to meet their demands (e.g. Instagram
and Disqus, to name just two).

Maintainable
Django code is written using design principles and patterns that encourage the
creation of maintainable and reusable code. In particular, it makes use of the
Don't Repeat Yourself (DRY) principle so there is no unnecessary duplication,
reducing the amount of code. Django also promotes the grouping of related
functionality into reusable "applications" and, at a lower level, groups related
code into modules (along the lines of the Model View Controller
(MVC) pattern).

Portable
Django is written in Python, which runs on many platforms. That means that
you are not tied to any particular server platform, and can run your applications
on many flavours of Linux, Windows, and Mac OS X. Furthermore, Django is
well-supported by many web hosting providers, who often provide specific
infrastructure and documentation for hosting Django sites.

Django was initially developed between 2003 and 2005 by a web team who were
responsible for creating and maintaining newspaper websites. After creating a number of
sites, the team began to factor out and reuse lots of common code and design patterns.
This common code evolved into a generic web development framework, which was open-
sourced as the "Django" project in July 2005.

Django has continued to grow and improve, from its first milestone release (1.0) in
September 2008 through to the recently-released version 3.1 (2020). Each release has
added new functionality and bug fixes, ranging from support for new types of
databases, template engines, and caching, through to the addition of "generic" view
functions and classes (which reduce the amount of code that developers have to write for a
number of programming tasks).

Django is now a thriving, collaborative open source project, with many thousands of users
and contributors. While it does still have some features that reflect its origin, Django has
evolved into a versatile framework that is capable of developing any type of website.

48
7.4.2 MYSQL

MySQL is an open-source relational database management system (RDBMS). Its name


is a combination of "My", the name of co-founder Michael Widenius's daughter, and
"SQL", the abbreviation for Structured Query Language.

MySQL is a component of the LAMP web application software stack (and others),
which is an acronym for Linux, Apache, MySQL, Perl/PHP/Python. MySQL is used by
many database-driven web applications, including Drupal, Joomla, phpBB, and
WordPress. MySQL is also used by many popular websites, including Facebook,
Twitter, Flickr, and YouTube.

MySQL is the most popular open source database software. It is the most downloaded
and distributed software. Because of speed, ease of use and reliability, it has become the
best choice for Web, Web 2.0 and all IT Companies.

7.4.3 JAVASCRIPT
JavaScript often abbreviated as JS, is a high-level, interpreted programming language
that conforms to the ECMAScript specification. JavaScript has curly-bracket syntax,
dynamic typing, prototype-based object-orientation, and first-class functions.

JavaScript is an object scripting language which nowadays it is used in a lot of web


pages, tablets, smart phones and server applications worldwide. It’s basic syntax is
similar to Java and C++. Language constructs such as: if statements, while and for
loops, switch and try catch blocks functions nearly same as in these two languages.
JavaScript can function as a procedural and an object oriented language.

As a multi-paradigm language, JavaScript supports event-driven, functional, and


imperative (including object-oriented and prototype-based) programming styles. It has
APIs for working with text, arrays, dates, regular expressions, and the DOM, but the
language itself does not include any I/O, such as networking, storage, or graphics
facilities. It relies upon the host environment in which it is embedded to provide these
features.

49
7.4.4 HTML
The documents on the Web are written in the Hypertext Markup Language. HTML
documents contain content to be displayed, formatting instructions that tell the browser
how to display the contents of the document, and links to other documents. HTML has
evolved along with browsers to achieve better visual presentations and standardization.
Web browsers read the HTML files and show or compose them into web pages. Tags
are not displayed; however they are just used to interpret the content of the page.

HTML provides the facility to HTML users to describe the structure of pages. Html
describes the structure of web pages. We can use HTML to:

• Publish online documents with headings, text, tables, lists, photos, etc.
• Retrieve online information via hypertext links, at the click of a button.
• Design forms for conducting transactions with remote services, for use in
searching for information, making reservations, ordering products, etc.
• Include spread-sheets, video clips, sound clips, and other applications directly.

7.4.5 CSS
CSS is a style sheet language which is used to describe the presentation of a file written
in a markup language. Its function is mostly styling web pages which are written in
HTML. CSS is designed for enabling separation of file content, which is written in
HTML or any other markup language. It improves content accessibility; it provides
more flexibility in the specification of presentation characteristics and reduces repetition
in the structural content. It is also used to allow web pages to be displayed differently
depending on the size of the screen in which is being viewed. CSS specifies also a
priority scheme where it determines which style rules should be applied if more than
one rule matches against a particular element. So, according to that, priorities are
calculated and assigned to the rules.

The name cascading comes from the specified priority scheme to determine which style
rule applies if more than one rule matches a particular element. This cascading priority
scheme is predictable.

50
The CSS specifications are maintained by the World Wide Web Consortium (W3C).
Internet media type (MIME type) text/CSS is registered for use with CSS by RFC 2318
(March 1998). The W3C operates a free CSS validation service for CSS documents.

7.4.6 JQUERY
JQUERY is a JavaScript library which works on multiple browsers and it is designed to
simplify the Client Side Scripting of Hypertext Markup Language. It is open source
software. Nowadays most of the websites has implemented this library to make
powerful dynamic pages. Saying this means that this is also one of the most used
JavaScript libraries. It is designed to create animations with advanced effects, make file
handling easy, handle events, etc.

7.4.7 AJAX
AJAX stands for "Asynchronous JavaScript and XML". AJAX is not a programming
language. AJAX just uses a combination of:-

i. A browser built-in XMLHttpRequest object (to request data from a web server) ii.

JavaScript and HTML DOM (to display or use the data)

How AJAX Works:-

• An event occurs in a web page (the page is loaded, a button is clicked)

• An XMLHttpRequest object is created by JavaScript


• The XMLHttpRequest object sends a request to a web server

• The server processes the request

• The server sends a response back to the web page

• The response is read by JavaScript

• Proper action (like page update) is performed by JavaScript

7.4.8 BOOTSTRAP
Bootstrap is a free front-end framework for faster and easier web development.
Bootstrap includes HTML and CSS based design templates for typography, forms,

51
buttons, tables, navigation, modals, image carousels and many other, as well as optional
JavaScript plugins. Bootstrap also gives you the ability to easily create responsive
designs. Responsive designs means web design is about creating web sites which
automatically adjust themselves to look good on all devices, from small phones to large
desktops.

7.4.9 VPS
Virtual private server (vps) is hosting that virtually mimics dedicated server environments within a
shared server. Vps hosting has become a popular choice because it is generally lower in cost than
dedicated hosting but provides better reliability, security, and performance than shared hosting.
Moreover, users get root access to the server, giving them the freedom to install applications and
make environment changes without having to go through the hosting provider, as they would with
shared hosting.

Vps is often a great option for saas providers, game makers, programmers, companies that have
outgrown their shared hosting, and any company who needs a secure and affordable backup
environment. But knowing what vps is by definition and whether it’s right for you are two different
matters. In this guide, we’ll give you the information you need to make the vps hosting decision an
easy one.

52
Chapter 8 Snapshots

53
Chapter 8 Snapshots

8.1 Home Page

Fig 8.1 Main Index Page

54
8.2 Filters

8.2.1 Bale Filter Screen

Fig 8.2 Bale filter Screen

8.2.2 Bale Quality Report

Fig 8.3 Bale Quality Report

55
8.2.3 Bale Size Report

Fig 8.4 Bale Size Report

56
8.2.4 Roll Filter Data

Fig 8.5 Roll Filter Data

57
8.2.5 Roll Quality Report

Fig 8.6 Roll Quality Report

8.2.6 Role Design Report

Fig 8.7 Role Design Report

58
8.2.7 Master Table Bale Quality

Fig 8.8 Master Table Bale Quality

8.2.8 Master Table Bale Pieces

Fig 8.9 Master Table Bale Pieces

59
8.2.9 Master Table Roll Quality

Fig 8.10 Master Table Roll Quality

60
8.2.10 Master Table Print

Fig 8.11 Master Table Print

61
8.2.11 Create User

Fig 8.12 Create User

8.2.12 User List

Fig 8.13 User List

62
8.3 Add Roll

8.3.1 Create Roll

Fig 8.3.1 Create Roll

8.3.2 Print roll

Fig 8.3.2 Print roll

63
8.3.3 Dispatch Roll

Fig 8.3.3 Dispatch Roll

8.3.4 Roll Inventory

Fig 8.3.4 Roll Inventory

64
8.3.5 Dispatch roll Inventory Error List

Fig.8.3.5 Dispatch roll Inventory Error List

65
8.3.6 Roll Trash list

Fig 8.3.6 Roll Trash list

66
8.4 Add Bale

8.4.1 Create Bale

Fig 8.4.1 Create Bale

67
8.4.2 Print bale

Fig 8.4.2 Print bale

68
8.4.3 Dispatch Bale

Fig 8.4.3 Dispatch Bale

69
8.4.4 Bale Inventory

Fig 8.4.4 Bale Inventory

70
8.4.5 Dispatch Bale Inventory Error List

Fig.8.4.5 Dispatch Bale Inventory Error List

71
8.4.6 Bale Trash list

Fig 8.4.6 Bale Trash list

72
8.5 Client Details

8.5.1 Client List

Fig 8.5.1 Client List

73
8.5.2 Client Records

Fig 8.5.2 Create Records

74
8.5.3 Dispatch List

Fig 8.5.3 Dispatch List

75
8.6 Different User View

8.6.1 Admin

Fig 8.6.1 Admin View

76
8.6.2 Packing User

Fig 8.6.2 Packing User View

77
8.6.3 Dispatch User View

Fig 8.6.3 Dispatch User View

78
Chapter 9
Maintenance
and Evaluation

79
Chapter 9

Maintenance and Evaluation

9.1 Introduction
Maintenance is an important phase of software or any system. It is the major and also crucial
part of any system. It is basically done after delivery of system or software. It includes
updation and modification after delivery to user or customer. It’s main motive is to correct
faults. There are various reasons why modifications required in a system, these are:

• Client Requirements: After some time client’s requirement can be fluctuated, user
may ask for some updation, adding new features or re-implement some existing ones into
a new format.

• Market Trends: There may be some policies which may be changed over time.
So, in this situation system must be meets the market trends. This I also the reason for
maintenance.

• Host Modifications: There may be chances where we need to update hardware or


platform for system. Chances to update software so the system meets should be
adaptable.

• Organization: If there is any business level change at client end, such as reduction of
organization strength, acquiring another company, organization venturing into new
business, need to modify in the original software may arise.

80
9.2 Types of Maintenance
In a software lifetime, type of maintenance may vary based on its nature. It may be just a
routine maintenance tasks as some bug discovered by some user or it may be a large event in
itself based on maintenance size or nature. Following are some types of maintenance based
on their characteristics:

• Corrective Maintenance: This includes modifications and updates done in order to


correct or fix problems, which are either discovered by user or concluded by user error
reports.

• Adaptive Maintenance: This includes modifications and updates applied to keep


the Application product up-to date and tuned to the ever changing world of technology
and business environment.

• Perfective Maintenance - This includes modifications and updates done in order to


keep the application usable over long period of time. It includes new features, new user
requirements for refining the application and improve its reliability and performance.

• Preventive Maintenance - This includes modifications and updations to prevent


future problems of the application. It aims to attend problems, which are not significant
at this moment but may cause serious issues in future.

9.3 Cost of Maintenance


Reports suggest that the cost of maintenance is high. A study on estimating software
maintenance found that the cost of maintenance is as high as 67% of the cost of entire
software process cycle.

81
Fig 9.1 Maintenance cost distribution
On an average, the cost of software maintenance is more than 50% of all SDLC phases.
There are various factors, which trigger maintenance cost goes high, such as:

Real-world factors affecting Maintenance Cost

• The standard age of any application is considered up to 10 to 15 years.

• Older application’s, which were meant to work on slow machines with less memory
and storage capacity cannot keep they are challenging against newly coming
enhanced softwares on modern hardware.

• As technology advances, it becomes costly to maintain old application.

• Most maintenance engineers are newbie and use trial and error method to rectify
problem.

• Often, changes made can easily hurt the original structure of the application, making
it hard for any subsequent changes.

• Changes are often left undocumented which may cause more conflicts in future.

Application-end factors affecting Maintenance Cost

82
• Structure of Software Program

• Programming Language

• Dependence on external environment

• Staff reliability and availability

9.4 Maintenance Activities


IEEE provides a framework for sequential maintenance process activities. It can be used in
iterative manner and can be extended so that customized items and processes can be
included.

These activities go hand-in-hand with each of the following phase:

• Identification & Tracing - It involves activities pertaining to identification of


requirement of modification or maintenance. It is generated by user or system may itself
report via logs or error messages. Here, the maintenance type is classified also.

• Analysis - The modification is analyzed for its impact on the system including safety
and security implications. If probable impact is severe, alternative solution is looked for.
A set of required modifications is then materialized into requirement specifications. The
cost of modification/maintenance is analyzed and estimation is concluded.

• Design - New modules, which need to be replaced or modified, are designed against
requirement specifications set in the previous stage. Test cases are created for validation
and verification.

• Implementation - The new modules are coded with the help of structured design
created in the design step. Every programmer is expected to do unit testing in parallel.

• System Testing - Integration testing is done among newly created modules.


Integration testing is also carried out between new modules and the
system. Finally the system is tested as a whole, following regressive testing
procedures.

83
• Acceptance Testing - After testing the system internally, it is tested for acceptance
with the help of users. If at this state, user complaints some issues they are addressed or
noted to address in next iteration.

• Delivery - After acceptance test, the system is deployed all over the organization either
by small update package or fresh installation of the system. The final testing takes place
at client end after the software is delivered. Training facility is provided if required, in
addition to the hard copy of user manual.

• Maintenance management - Configuration management is an essential part of


system maintenance. It is aided with version control tools to control versions,
semiversion or patch management.

84
Chapter 10
Future Scope and
Conclusion

85
Chapter 10 Future Scope and Conclusion

10.1 Conclusion
In the era of digitization when almost in every area digitization is implemented now
days. Our Industry system is also used digital platform to manage Products. So, in this
era where everything is going on digital platform this proposed system “ Inventory
Management System” is very much helpful to maintain records easily and efficiently.

In traditional method of Inventory Management there are some aspects why need this
proposed system. The proposed system not only helpful to reduce paper work but also
capable to do operation like filtration while generating records, which is easy to handle.

In the current scenario our lives are so busy so in that case there is difficult for
Employees to maintain large records in leader. So to maintain and handle large amount
of data we can use this system.

It is easy to use because it provides user friendly environment to users. There is no hard
and tough system of managing records.

10.2 Future Scope


Today, almost every field converts their traditional systems into digital. So this is the
way to move traditional Inventory management system on digital platform which is not
only beneficial but also capable to perform tasks at anytime and anywhere the basic
requirement is that system must be connected with internet when it will be moved from
local server to live server. In case of local server we mean as it is developed using
python Enviroment To run the proposed system on local machine we need some server.

Now there are some benefits which shows what is the future scope of the proposed
system, these are:

• In the upcoming years textile industry is trying to move towards the digitization so
this system should be the part of that system.
• As we have less time, we don’t want to spend time on maintaining records Leader.
So, this system can help in this.
• This is not possible to take Inventory leader with you every time, so this also can
be solved by this proposed system because it is portable you can access it from
your home pc or laptop.
• It is less time consuming for report generation.
• It reduces man power also.
• It overcomes traditional problems of current system.
Bibliography

• https://getbootstrap.com/docs/3.3/
• https://docs.djangoproject.com/en/3.2/
• https://docs.djangoproject.com/en/3.2/ref/templates/
builtins/
• https://jqueryui.com/demos/
• https://www.tutorialspoint.com/json/
json_ajax_example.htm

You might also like