Garment Industries: Khushi Kunjay Chokshi

GARMENT INDUSTRIES
A PROJECT REPORT
Submitted by
KHUSHI KUNJAY CHOKSHI

180320116006
In partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
in
Information Technology Department
L. J. Institute of Engineering & Technology

Ahmedabad
Gujarat Technological University, Ahmedabad

[May - 2022]
Ahmedabad
CERTIFICATE
This is to certify that the project report submitted along with the project entitled
Garment Industries has been carried out by Chokshi Khushi Kunjay under
my guidance in partial fulfillment for the degree of Bachelor of Engineering in
Information Technology, 8th Semester of Gujarat Technological University,
Ahmadabad during the academic year 2021-22.
Prof. Prayag Patel Prof. Mitesh Thakkar
Internal Guide Head of the Department

Ahmedabad
DECLARATION
We hereby declare that the Internship report submitted along with the
Internship entitled Garment Industries submitted in partial fulfillment for the
degree of Bachelor of Engineering in Information Technology to Gujarat
Technological University, Ahmedabad, is a bonafide record of original project
work carried out by me at SKP Software under the supervision of Mr. Kalpesh
Trivedi and that no part of this report has been directly copied from any
students’ reports or taken from any other source, without providing due
reference.
Name of the Student Sign of Student
Khushi Kunjay Chokshi

199859 Acknowledgement
ACKNOWLEDGEMENT
It is great pleasure for me to undertake this Internship as software engineer intern and a project
at SKP Software. I feel highly doing the project entitled “Garment Industries”. I offer my
sincere appreciation for the learning opportunities provided by SKP Software.
I am very grateful and would like to thank my supervisor and external guide Mr. Kalpesh
Trivedi who has been mentoring me through the whole journey of this project and internship. I
would also like to thank Prof. Mitesh Thakkar, Head of Department and Prof. Prayag Patel,
my Internal guide for their continued support.
This Internship and project would not have completed without their enormous help and worthy
experience. Whenever I was in need, they were there behind me. Although, this report has been
prepared with utmost care and deep routed interest. Even then I accept respondent and
imperfection. This opportunity has proved to be very useful to me in a way of taking
responsibilities and enhancing my coding skills and becoming more code friendly. And for that
I am very glad.
Khushi Chokshi
(180320116006) DATE:30th April,2022.
Gujarat Technological University i LJIET

199859 Abstract
ABSTRACT
In growing country, India, employers go through many difficulties especially those who
are a scarce of employees and find it hard to manage the company records. They often
get perplexed with the amount of data they have to manage and record in different files.
The project I worked on during this internship at SKP Software was to solve the above
faced issue. The company works of creating software for its clients.
The company is currently working on a stock management desktop application for

various companies. Furthermore, I was assigned to work alongside to make a web
application for the same. We learnt Asp.Net and C# during the period of internship and
eventually implemented the acquired knowledge in creating a web application. We will
be taught how to host the application on web server later on.
The Web Application is used for storing all the data of stocks exchanged for a garment
industry. Additionally, the data about the transaction of payment and reception is all a
feature included in the web application. Various components learnt during the internship
are also implemented in the project like TreeView, GridView, etc.
Gujarat Technological University ii LJIET

199859 List Of Figures
LIST OF FIGURES
Fig 3.1 System Introduction 10
Fig 3.2 Project Scope 12
Fig 3.3 Iterative Model 15
Fig 3.4 Gantt Chart 21
Fig 4.1 Features Of Current System 28
Fig 4.2 List of Main Modules 30
Fig 5.1 System snap(Account Master) 32
Fig 5.2 System snap(Sales Tax Setup) 33

Fig 5.3 System snap(Master Menu) 34
Fig 5.4 System snap(Pop up div box) 34
Fig 5.5 System snap(Pop up div box with live search) 35
Fig 5.6 System snap(Tree View) 35
Fig 5.7 System snap(GridView) 36
Fig 5.8 System flow diagram 37
Fig 5.9 List od tables in database 38
Fig 5.10 Design of AccountMaster Table 39
Fig 5.11 Records of the Account Master table 39
Fig 5.12 Records of the Program Sheet table 39
Fig 5.13 Title,Menu and Tool Bar 40
Fig 5.14 Learnt how to create a pop up div box 40
Fig 5.15 Decided the layout of the form 41
Fig 6.1 Code snippet from Company Master 44
Fig 6.2 CSS on Dept Master 44

Fig 6.3 CSS on buttons in the side panel 44
Fig 6.4 JavaScript for required fields 45
Gujarat Technological University iv LJIET

199859 List Of Figures
Fig 6.5 JavaScript for displaying div on checked box 45
Fig 6.6 jQuery code to copy field values 46

Fig 6.7 Code snippet from Narration Master 46
Fig 6.8 Code snippet from Company Master 47
Fig 6.9 Code snippet for Grid View 47
Fig 6.10 Code snippet for Tree View 48
Fig 6.11 Item Master 48
Fig 6.12 Pop Up Div Box 49
Fig 6.13 Required Validation 49
Fig 6.14 Live Search 49
Fig 6.15 Tree View 49
Fig 6.16 Grid View 49
Fig 6.17 Company Setup 50
Gujarat Technological University iv LJIET

199859 List Of Tables
LIST OF TABLES
List of Figures iii
List of Tables v
List of Abbreviation vi
Table of Content vii
Table 3.1 Project Plan 16
Table 3.2 Estimated Code of Line 19
Table 4.1Hardware Requirement 23
Table 7.1 Test Results 52
Gujarat Technological University v LJIET

199859 List Of Abbreviation
LIST OF ABBREVIATION
Following is the list of abbreviations used in the report:
Abbreviation Full Form
HTML Hyper Text Markup Language
ASP Active Server Pages
CSS Cascading Style Sheet
JS Java Script
M SQL Microsoft Structured Query Language
.NET Network Enabled Technologies
ERP Enterprise Resourse Planning
SDLC System Development Life Cycle
SRS Software Requirement Specification
Gujarat Technological University vi LJIET

199859 Table Of Content
TABLE OF CONTENTS
Acknowledgement i
Abstract ii
List of Figures iii
List of Tables iv
List of Abbreviations v
Table of Contents vi
Chapter 1 Overview of the Company 1
1.1 History 1
1.2 Different scope/ Product of work 1
1.3 Organization Chart 3
Chapter 2 Overview of different process being carried out in company 4
2.1 Work being carried out in each department 4
2.2 Technical specifications of major equipment in each department 5
2.3 Sequence of operation for end product 5
2.4 Details about each stage of production 7
Chapter 3 Introduction to Internship and Project 8
3.1 Introduction to internship and project 8
3.2 Purpose 8
3.3 Objective 9
3.4 Scope 10

3.5 Technology and Literature Review 10
3.6 Project/ Internship Planning 12
3.6.1 Project/Internship Development Approach and Justification 12
3.6.2 Project/Internship Effort and Time, Cost Estimation 14
3.6.3 Roles and Responsibilities 18
3.6.4 Group Dependencies 18
3.7 Project/ Internship Scheduling (Gantt Chart) 19
Chapter 4 System Analysis 20
4.1 Study Of Current System 20
4.2 Problem and Weakness of Current System 20
4.3 Requirements of New System 20
4.4 System Feasibility 22
4.4.1 System’s contribution to the overall objectives of the organization 24
4.4.2System’s implementation using the current system 24
4.4.3 System’s integration with other systems 24
4.5 Features of Main System 25
4.6 List Main Modules 26
4.7 Selection approaches and Justification 27
Chapter 5 System Design 28
5.1 System Design and Methodology 28
5.2 Database Design 32
5.3 Input/ Output and Interface Design 35

5.3.1 Samples of Forms, Reports and Interface 35
5.3.2 Access/ Control Security 36
Chapter 6 Implementation 37
6.1 Implementation Platform/ Environment 37
6.2Technology and Modules, Specifications 37
6.3 Outcomes 43
6.4 Result Analysis 45
Chapter 7 Testing 46
7.1 Testing Plan/ Strategy 46
7.2 Test Results and Analysis 47
7.2.1 Test Cases 47
Chapter 8 Conclusions and Discussion 49
8.1 Overall Analysis of Internship/ Project Viabilities 49
8.2 Dates Of Continuous Evaluation (CE-I and CE-II) 49
8.3 Problem Encountered and Possible Solutions 49
8.4 Summary of Internship/ Project Work 50
8.5 Limitation and Future Enhancement 51
References 52

199859 Overview Of Company
1.0 OVERVIEW OF THE COMPANY
1.1 HISTORY
Where and when did it all began?

The company named “SKP Software” was founded originally in the year 1993 by Mr. Kalpesh
Trivedi. The founder and owner Mr. Trivedi has been in the IT industries since over three decades
now. He started his journey by working at a company named NOVELL network Tech. After gaining
years of experience and working on many high- profile projects Mr. Trivedi decided to start his own
company to generate software for clients.
The company has always been a small scale company but never failed in gaining the trust consistency
of many well-known company as their clients. Some of their prominent clients include:
 Adani Industries
 Jivraj Hospital
 Ganesh Housing
Over the years, the company has been standing strong through all the ups and downs and have
completed around 400 projects. They proudly claim to be a provider of over 100 satisfied and
recurring customers.
The company now works on .NET framework and is product base company.
1.2 DIFFERENT PRODUCT/SCOPE OF WORK
As I mentioned earlier, the company is product based organization, it makes large scale software for
its clients. It only works with big data. The main feature of the products this company creates is the
management of huge database. It has a highly skilled team for organization and maintenance.
It creates Application Software only or can also be defined as business software.
Some types of products it has created in the past are as follows:
 Health care software
 Manufacturing software
Gujarat Technological University 1 LJIET

 Engineering Software
 ERP Software
 Glass Industry
 Garment Industry
I was assigned to work on the already existing desktop application of a garment industry for its
conversion into a web application version. The system I was given was for a garment industry called
AARYA CLOTHING CULTURE. The detailed explanation is given in the later chapters in the
report.

1.3 Organization Chart
Figure 1.1 Organization Chart
https://devoxsoftware.com/blog/agile-software-development-team

199859 Overview of different processes
2.0 OVERVIEW OF DIFFERENT PROCESS BEING CARRIED
OUT IN COMPANY
2.1 DETAILS ABOUT THE WORK BEING CARRIED OUT IN EACH
DEPARTMENT
 Client:[Not necessarily a department of the company]:
A client is someone who request for a software either of personal or professional use. The client is
the person who specifies the requirements in the product and is responsible for the user stories.
 Project Manager:
Project managers are accountable forplanning, organizing, and cheerleading the employees. These
gate keepers ensure customer satisfaction, push documentation, and efficiently optimize the
workflow.
 Business Analyst:
Although the responsibilities of business analysts can differ on the waterfall and agile projects,
strive to help guide businesses. They do this by gathering, analyzing, developing, and documenting
business requirements. In a broader sense, they bridge the gap between the business and IT to
improve efficiency.
 Quality Assurance engineers:
They are more than just testing a feature or a product. These specialists advocate for the quality of a
product by monitoring each stage of software development, debugging, and defining corrective
measures.
 Designer:
UI/UX designer creates user-friendly and intuitive interactions by building a route that logically
flows from one stage to the next. A user interface designer focuses on the user’s visual experience
that goes with that route.

 Developer:
Software developers are the creative, brainstorming eminence grise that power computer programs
of all kinds. Among their daily duties are software development and testing, upgrading, quality
monitoring, and documenting all processes for future reference.
2.2 LIST THE TECHNICAL SPECIFICATIONS OF MAJOR EQUIPMENT
USED IN EACH DEPARTMENT
List of major equipment used in each department individually is not provided to us by the company.
Hence, I have specified the equipment I used as a software developer intern:
Back end and Frontend coding: Visual Studio 2019
Framework and library: .NET framework from Visual Studio Libraries
Database: Microsoft SQL Server 2008 R2
2.3 SCHEMATIC LAYOUT OF SEQUENCE OF OPERATION FOR

MANUFACTURING OF END PRODUCT
The process of developing a software is done via following the basic SDLC rule which is proved to
be most efficient while developing a software. Hence, the company uses the same SDLC technique
for developing a software.

Figure 2.1 SDLC
Schematic or sequence of operation to produce a software:
Requirements Operations
UI/UXDesign Coding QA Stage
Collection Stage
Figure 2.2 Layout of Process
The above given process is a schematic representation of the sequence of stages that the software
development team undertakes to produce a software. It is basically a SDLC with a use of differently
chosen words.
https://www.uptech.team/blog/product-development-life-cycle

2.4 DETAILS ABOUT EACH STAGE OF PRODUCTION
1. Gather the information about Requirements:
While starting any software development project this is the most essential part of the whole
process and therefore the company first get a clear idea about the functional and non-functional
requirements. This is the responsibility of the project manager to communicate the requirements
distinctly to the development and designer team.
2. Start with the Front-end design:
It is the role of UI/UX designers of the company. Once the requirements about the design and user
interface is understood theteam starts with developing the visual solution of the product. This part
of the process is known as user interface design, and it stands for how users perceive the app.
3. Focus on Coding:
In the third step, we finally get down to coding the concepts listed above. Here, the development
team implements all models, business logic, and service integrations specified in the prior
stages. The coding stage is usually the longest, as it is the cornerstone of the whole process. The
development team follows the software requirements to build a product that lives up to the
stakeholder’s expectations.
4. Review of the product by QA team:
At the QA stage, the testing specialists discover and inform about the problems that arise while
using the system. The testing frameworks may vary depending on the project, including
automation and/or manual testing.
5. Operation Stage/ Deployment Stage:
Finally, the application goes on to be deployed in a live environment. This stage involves
deployment, support, and maintenance necessary to keep the system functional and up-to-date.

199859 Introduction
3.0 INTRODUCTION
3.1 INTRODUCTION TO INTERNSHIP AND PROJECT
Currently, as world is going through a long terming wave of pandemic. Struggles are not limiting
for any category of crowd in almost past two years. Hence, the company I was an intern in, makes
software for its client who fails to have appropriate staff to makes software and have scarce
employees due to pandemic layoffs. Online option is both easy and safe and a very good pick. The
company make customized and personalized software for its clients. SKP Software is an IT
company that works on ASP.NET Framework
I was assigned to work on a web application that was to be duplicated from an ongoing live project
of a desktop application that manages stocks for garment industries. This project used languages
like JAVASCRIPT, JQUERY, C#, HTML, CSS along with asp components. It is an inventory
management application for various garment industries. It stored the records of the transaction
details as well as the stock update is done within the project. Details of all the employees and
departments are also kept track of in the application. While the desktop application has a wide
range of features, web application fails to achieve those at this state.
During the whole term of internship, I firstly learnt about the new language and framework I was
going to work with. Later on I was provided with the system they wanted me to work on. After
getting familiar with the language and system I started working on the coding part of the project.
Gradually understanding the requirements and applying the gathered knowledge to the project for
output, my knowledge became clearer with time. And again the daily reporting to the supervisor
really helped me a lot throughout the project
3.2 PURPOSE
The purpose of choosing to work at SKP Software under Mr. Kalpesh Trivedi was his over three
decades of experience in the field and his excellence in manages over 50 clients currently. The
purpose of working on this project was to implement the acquired knowledge during the period of
internship to practical use. I tried to pull the client towards the ease of getting the help to manage

199859 Introduction
the inventory and company records through a user friendly system. In today’s situation and the hit
of pandemic, we generally seek out online option for almost everything. While it was very hard to
go around to get skilled employees to manage the whole working of the organization, it is even
harder now. So this website gives an effective way not just by saving time but also by giving them
multiple options to make the work easier.
1. Saves time
2. Wide range of choices
3. Easy to store data and verify later
4. Can store large data
5. Make is easily understandable by non-skilled employees to work on.
Figure 3.1 System Introduction
3.3 OBJECTIVES
There are various goals we have in mind coming up with this project. We look forward to create a
helpful system for the company’s clients and they are personalized according to the requirements of
the client that can help them saving time and ease work load. The main objectives that we aim to
achieve with this platform are as follow:

199859 Introduction
 To provide immediate help with ease to the Clients

 To save with easy to understand system.
 To provide user with various choice features like saving data, updating data, saving details of
all employees etc.
 To let user know, the current balance while recording transaction details.
 To store delivery and reception of stocks.
 To allow only the admin to log in.
3.4 PROJECT SCOPE
• This system is found tested and examined for its successful processing. Future change in the
environment or processing can be easily adopted by having simple change in coding. It is very
user friendly, cost effective, feature rich and it provides very high level of security.
• It protects the unauthorized users. Moreover, the system coding is so well designed that new
operations can be easily incorporated without much modification.
MASTER/TRANSACTION
ADMIN
LOG IN REPORT/VIEW RECORDS
STORE/WINDOW
Figure 3.2 Project Scope
3.5 TECHNOLOGY AND LITERATURE REVIEW
 The front end used in my project is HTML, JavaScript, ASP components, JQUERY,
CSS, and the back end used is C# and Microsoft SQL. Furthermore, the framework

199859 Introduction
used is ASP.Net Framework.
 I followed the Spiral Model for developing this Project and whole Project will be
developed using the SDLC scenario.
I. HTML and CSS

HTML is the foundation of all web pages. Without HTML, you wouldn’t be able to organize text
or add images or videos to your web pages. HTML is the beginning of everything you need to
know to create engaging web pages! You will learn all the common HTML tags used to structure
HTML pages, the skeleton of all websites. You will also be able to create HTML tables to
present tabular data efficiently. However, CSS is used for the styling of the HTML pages. Hence,
I have used HTML along with ASP Components and CSS to create the structure of Web
Application.
II. JAVASCRIPT and JQUERY
JavaScript is a lightweight, cross-platform, and interpretedscripting language. JavaScript can be

used for Client-side developments as well as Server-side developments. Whereas, jQuery is an
open source JavaScript library that simplifies the interactions between an HTML/CSS
document, or more precisely the Document Object Model (DOM), and JavaScr ipt. I have used
JavaScript and jQuery (on few components) for the client-side scripting in the project.
III. ASP.NET and C#
ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled codes,
written using the extensible and reusable components or objects present in .Net framework.
These codes can use the entire hierarchy of classes in .Net framework. The ASP.NET
application codes can be written in any of the following languages:
 C#
 Visual Basic.Net
 Jscript
 J#

199859 Introduction
Hence, I have used C# for the backend coding, which was learnt during the internship.
IV. Microsoft SQL (Microsoft SQL Server 2008 R2)
Microsoft SQL Server is a Relational Database Management System (RDBMS) developed by

Microsoft. It is a highly scalable product that can be run on anything from a single laptop, to a
network of high-powered cloud servers, and anything in between. The company I interned in
used Microsoft SQL server 2008 R2 for its database management and I worked on the same.
3.6 PROJECT/INTERNSHIP PLANNING
The systems development life cycle (SDLC) is a conceptual model used in Project Management that
describes the stages involved in an information system development project, from an initial
feasibility study through maintenance of the completed application. SDLC can apply to technical
and non-technical systems. In most use cases, a system is an IT technology such as hardware and
software. Project and program managers typically take part in SDLC, along with system and
software engineers, development teams and end-users.
 We have used Software development model called Iterative model during creating this project.
3.6.1 Project / Internship Development Approach and Justification
We undertook the Iterative Model for the development of our project. The Iterative Model relies on
specifying and implementing individual parts of the software, rather than attempting to start with
full specification requirements. Once a rough product is created within an iteration, it is then
reviewed and improved in the next iteration and so on. The Iterative Model relies on the whole
product being developed step-by-step (Design/Develop, Test, Implement).
Advantages and Disadvantages of Iterative Model

Advantages: Since the product is developed gradually, it’s easy to identify problems early when
using this software development model.

199859 Introduction
Disadvantages: Because each iteration phase is rigid with no overlaps, the Iterative Model can take
longer and be costly.
Mr. Kalpesh Trivedi, supervisor for the internship/Project used to have a routine reporting after
every 3 days. Where we were assigned various different components(module) and had to work on
the component in the next three days.
Evaluation and verification was done by the supervisor on the next routine reporting.
Planning>understanding the requirements>analysis and
design>Implementation>Testing>Evaluation
Figure 3.3 Iterative model

199859 Introduction
Table3.1 Project Plan
TASK Start Date End Date

Introduction to the system and asp.net 2/7/2022 2/12/2022
Introduction to C# and database server 2/14/2022 2/19/2022
Structural designing of 50% of the system 2/21/2022 2/26/2022
Structural designing of remaining system and CSS application 2/28/2022 3/5/2022
Understanding the infrastructure of database and connectivity 3/7/2022 3/12/2022
Understanding components like pop up divs,GridView, Treeview 3/14/2022 3/19/2022

etc.
Starting off with Backend programming for Masters menu 3/21/2022 3/26/2022
Learnt how to debug and application of debugging 3/28/2022 4/2/2022
Insert and Update operation on SQL with Masters Menu 4/4/2022 4/9/2022
Understanding Requirements and programming for Transaction 4/11/2022 4/16/2022

Menu
Connecting one page to another with Testing 4/18/2022 4/23/2022
Continuation with Transaction Menu 4/25/2022 4/29/2022
3.6.2 Project / Internship Effort and Time, Cost Estimation
COCOMO Model
 Like all estimation models for software, the COCOMO models require sizing information.
 Three different sizing options are available as part of the model hierarchy : object points, function
points ,and lines of source code.
 Like function points ,the object point is in direct software that is computed using counts of the
number of
1. Screens(at the user interface),
2. Reports, Components likely to be required to build the application.
3. There are three types of software project:

199859 Introduction
 Organic project
 Semi-detached project
 Embedded project
Cost required to develop project= effort*RS/month
 Effort Estimation(E):
In Organic=2.4 (KLOC)1.05PM
In semidetached=3.0(KLOC)1.12PM
In Embedded=3.6(KLOC)1.20PM
 Duration Estimation(D):
In Organic=2.5(effort)0.38months
In semidetached=2.5(effort)0.35months
In Embedded=2.5((effort)0.32months
 Person Estimation:
1. P=E/D KLOC=Kilo Line of Code

199859 Introduction
Table 3.2 Estimated Lines of code
Modules Page Estimated lineofcode

Master - 5600
Account Master 600
Item Master 700
Department Master 150
Color Master And HSN CODE 300
TDS Master 200
Lot Master 200
Lot type Master 150
Employee Master 550
Sales Tax Setup 650
Unit Master 150

Purchase Tax Setup 650
Group Master 450
Narration Master 150
Category Master 450
Company Master 250
Transaction 4950
Receipt Entry/Payment Entry 1400
Program sheet/Cutting Entry 1500
Work Allocation/Lot Costing 100

199859 Introduction
Final Lot Costing/Lot Rate 100
Purchase Expense/Challan 200

Challan return/Purchase Invoice 300
Sales Entry 500
Contra Entry 550
Journal Voucher/Dr cr Entry 150
Generate salary 150
Item Opening Entry -
Store - 200
-
Inward Entry ___________________________________
_
100
Report Issue Entry 100
- 2050
Account Payable 50
Account Receivable 50
Balance Sheet 100
Bank Book 150
Cash Book 150
Inventory/Journal Register 300
Ledger/Monthly Attendance 250
Party Floor/Periodic Work 100
PL Account/Trading ACC/Trial bal 400
Purchase Register/Purchase return 250

_____________
Sales Register/Sales return 250
_
Admin/Feature All admin and features pages 900
s

199859 Introduction
 Total line of code=13,700 (actual value is more than calculated figure)

 KLOC=13.70
Effort Estimation(E):
=2.4(KLOC)1.05PM
=37.48PM
Duration Estimation(D):
=2.5(effort)0.38month
=2.5(37.48)0.38months
~10 months
Project Cost:
=effort*RS/month
=37.48*RS/month
3.6.3 Roles and Responsibilities
My roles and Responsibilities throughout the internship were:

1. Communication
2. Reporting
3. Requirement Analysis
4. Database Connectivity
5. Coding
6. Testing
3.6.4 Group Dependencies
We were a group of two people during the internship and we both worked on the project

199859 Introduction
together. My teammate Vanshika and I worked together on the project. System connectivity
was provided on her desktop so she handled the communication, we worked together on the
designing, coding and testing phases.
3.7 PROJECT / INTERNSHIP SCHEDULING (GANTT CHART)
The weekly work done is shown in the GANTT chat shown below:
Figure 3.4 Gantt Chart

199859 System Analysis
4.0 SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM
 When I started my internship, I was assigned to work on a system that is currently a desktop
application for inventory management. There are various generally available inventory
management systems socially available on online platform to make any organizations job easier
to keep track of the stock available to them.
 General systems I have come across for inventory management have some common features like
view stock available history of stock exchange management etc. but most of those systems are
just limited to that.
 The system I was assigned to work on was a web application version of the same desktop
application the company made for inventory management.
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM
 The currently available systems for inventory management systems have limited
features like stocks exchanged and transaction details with different customers.
 Though it saves time and lessen the man power required in the on-paper
management system. It lacks user-friendliness and requires highly skilled
employees to operate the system.
 Employee and department details has to be stored on different systems.
 Daily attendance is not managed in the same system.
 Database management is not strong enough to store large data.
4.3 REQUIREMENTS OF NEW SYSTEM
 A common system to store transaction details, employee details, department details, stock
exchange details, Monthly attendance etc.

 More of a user-friendly system so that no highly skilled employee are required to employ for
operation.
User Requirement:
 It describes the type of user which deals with the applications. Basically, this application has one
type of user as given below:
1. Administrator
1. Administrator:
 Responsibility of administrator is to manage the application database and update the data in
database regularly .For e.g. manage the data of booked tours and manage cancellation.
 User who uses this portal should know how to operate the windows. Because the software has the
same look and features like whole software is menu driven.
 Just click navigation bar and corresponding page will open up.
Hardware and Software Characteristics:

Hardware Requirements:
Component Minimum Recommended
Processor 1.9 gigahertz (GHz) x86- or x64-bit 3.3 gigahertz (GHz) or faster
dual core processor with SSE2 64-bit dual core processor with
instruction set SSE2 instruction set
Memory 2-GB RAM 4-GB RAM or more
Display Super VGA with a resolution of Super VGA with a resolution

1024 x 768 of 1024 x 768
Table 4.1 Hardware requirement

Software Requirements:
Editor Required: Visual Studio 2019
Database Server: Microsoft SQL server 2008 R2

Install .NET Framework in the system through visual studio installer
Install Web Application library from visual studio installer
Functional and Non-Functional Requirements:

Functional requirements are product features or functions that developers must implement to enable
users to accomplish their tasks.
Non-Functional Requirements, not related to the system functionality, rather define how the system
should perform
Functional Requirement
It uses search bar in choice box divs. As the user types in the search bar it implements live search
and filter the options to choose from for the user.
As the user chooses an option from choice box it shows its hierarchy from the database through
treeView.
User can enter as many rows (dynamic gridview) he/she wants in the grid view for a single entry.
The values in gridview should summed and output a total value on the same page for a clear idea
about the entries.
Non-Functional Requirement
User do not have to enter fields input in some fields they are auto incremented and are saved in
database.
Some fields only allow number of a specific length like phone numbers allow 10 digits.
Some Text fields allow only numbers.
Some fields convert text to upper case.
4.4 SYSTEM FEASIBILITY
As name suggests feasibility study is the feasibility analysis or it is a measure of the
software product in terms of how much beneficial product development will be for
the organization in a practical point of view. Feasibility study is carried out based on

many purposes to analyze whether software product will be right in terms of
development, implantation, contribution of project to the organization etc.
Types of Feasibility Analysis:
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
 Scheduling Feasibility
Technical Feasibility:
In Technical Feasibility current resources both hardware software along with required technology
are analyzed/assessed to develop project. This technical feasibility study gives report whether
there exists correct required resources and technologies which will be used for project
development. Along with this, feasibility study also analyzes technical skills and capabilities of
technical team, existing technology can be used or not, maintenance and up-gradation is easy or
not for chosen technology etc. Hence, the system should be maintained from time to time.
Operational Feasibility:
The System is to be developed for any user who wants to use it. We want our system
user friendly and easy to use.
The administrator also may be non-technical, so the user interface will be designed in such a way
that it gets comfortable for non-technical person to operate easily.
Economic Feasibility:
In Economic Feasibility study cost and benefit of the project is analyzed. Means
under this feasibility study a detail analysis is carried out what will be cost of the
project for development which includes all required cost for final development like
hardware and software resource required, design and development cost and

operational cost and so on. After that it is analyzed whether project will be beneficial
in terms of finance for organization or not. For the system to be economically feasible, the
profits from the project must be greater than or equal the cost of development.
Scheduling Feasibility:
The project was quite feasible when it comes to scheduling. Routine reporting as done for the
progress of the project.
4.4.1 System’s contribution to the overall objectives of the organization
As discussed before the company I work for makes personalized software for its clients. Hence,
the company had created a desktop application for its client called AARYA CLOTHING
CULTURE for it inventory management. When I joined the internship I was assigned to work
on a web application for the same system that was already made as a desktop application
version. Hence, the system was requirement of the company itself and it fulfils all of the
objectives of the organization i.e, making personalized systems for clients.
4.4.2 System’s implementation using the current system
System was implemented using the current system as a reference. Although the system is built
from scratch, the initiation of the system was understood by analyzing the current system. The
database was provided by the company itself but the flow of data from what page to what table
was studied personally.
The current system was very useful while creating the new system as to where it is facing some
shortcomings, for some requirements and improvements etc.
4.4.3 System’s integration with other systems
System’s integration with other system can be explained as the integration of provided desktop
application. Future integration can be done, for example it can be used for multiple
departmental inventory management at once. User can choose from options of different
companies. For example, a client manages for data of more than one companies at a time and
want to get access to one of its companies. He would get an option to choose from and log in to

access that companies details specifically. The infrastructure of the system for those companies
would be same just the id in the database will be different for different company so that it can
be fetch and save data accordingly.
4.5 FEATURES OF NEW SYSTEM
Employee
details
Transaction
Stock details
details
System
Department
Live search
details
User-Friendly
Figure 4.1 Features of new system

4.6 LIST MAIN MODULES
System
Master Transaction
Store
Menu Menu
Account receipt
Issue Entry
Master entry
Item payment
Master entry
Sales Tax program

SetUp sheet
Purchase Contra
Tax Setup Entry
Group
Master
Category
Master
Figure 4.2 List of Main Modules

4.7 SELECTION APPROACHES AND JUSTIFICATION
ASP.Net is an open-source, server-side web-application framework designed for web development

to produce dynamic web pages application(back end)for small and large enterprise with portable
implementation.
C# (C-Sharp) is a programming language developed by Microsoft that runs on the .NET
Framework. C# is used to develop web apps, desktop apps.
Microsoft SQL Server is a relational database management system developed by Microsoft.
Combination of both will give great web application as output.

199859 System Design
5.0 SYSTEM DESIGN
5.1 SYSTEM DESIGN AND METHODOLOGY
System design plays a very crucial role in an application. It is the process of defining the
components, modules, interfaces, and data for a system to satisfy the specified requirements
The desktop application (current system) provided by the company had a very distinctive as well as a
user friendly design. It consists of tool bars, menu bars with n number of menus and submenus
present. Some of the snapshots of the current system are as follow:
Figure 5.1 System snap(Account Master)
As it can be seen in the above image the system consists of a title bar, Menu bar with different menus
like Master, Transaction, Report, etc.
Next is the title of the web page with the respective form underneath, that consists of different HTML
elements like labels, input, text boxes, checkboxes, drop down lists, etc.
On the right side, are the navigation buttons that provide an immediate link to the respective web
pages , for direct access.

Some other snapshots of the desktop application are as follow:
Figure 5.2 System Snap(Sales Tax Setup)
Figure 5.3 System Snap(Masters Menu) Figure 5.4 System Snap(Pop Up div box)

There were various features present in the desktop application that were to be incorporated in the web
application. These functionalities included —pop up div boxes, live search, grid view, tree view etc.
Some examples are as follow:
Figure 5.5 System Snap(Pop up div box with live search)
Figure 5.6 System Snap (Dynamic Grid View)

Figure 5.7 System Snap(Tree View)
The design approach used for the web application was almost similar; we tried to create an interface
for the users that was attractive, engaging as well as very easy to access. The system was designed to
provide a pleasant experience to the user to navigate and browse through different web pages with
ease. Also it was designed in such a way that the performance of the system was not compromised.
The flow of the new system is as follow:

Figure 5.8 System flow diagram
5.2 DATABASE DESIGN / DATA STRUCTURE DESIGN
A database is typically designed so that it is easy to store and access information. Database Systems
or DBMS is software that caters to the collection of electronic and digital records to extract useful
information and store that information.
The current system has a vast database of 50-60 data tables consisting of multiple records in each.
The database is hosted on Microsoft SQL Server 2008 R2.
The data inserted, deleted and updated are stored in the database in an organized manner which can
be easily accessed by the user. The database designing is done keeping in mind the future scalability
and modifiability of the system as needed.

Some of the snapshots of the system database are as follow:
Figure 5.9 List of tables in database
Figure 5.10 Design of the Account Master table

Figure 5.11 Records of the Account Master table
Figure 5.12 Records of the Program Sheet table

5.3 INPUT/ OUTPUT AND INTERFACE DESIGN
5.3.1 Samples Of Forms Reports And Interface

Based on the system design and flow, we started to create different elements that were a part of the
current system. The basic idea was to understand the design of the system, learn to create the
elements that were new for us and to decide from the multiple options available, to choose the one
that works best for the smooth functioning of the system.
In this process, we selected the layout that looked the best, the color scheme that engages the most
with the user and the features that provide an easy and smooth navigation throughout the system.
Some of the examples of the elements that were finalized are as follow:
Figure 5.13 Title, Menu and Tool Bar
Figure 5.14 Learnt how to create a pop up div box

Figure 5.15 Decided the layout of forms
5.3.2 Access Control/ Security

As we know that there’s always a fear of data leaks and breaches when working on the network of
networks, the internet. And in times when anything can be accessed with a click of button it gets
imperative to take necessary steps for the data security and users privacy.
With the same purpose we have included user identification and authentication in order to access any
data on the web application. It is compulsory for the user to provide the correct username and
password to access, insert or modify data on the system

199859 Implementation
6.0 IMPLEMENTATION
6.1 IMPLEMENTATION PLATFORM/ ENVIRONMENT
The next step after the completion of system design was to start implementing the ideas, layout,
features, and functionalities of the system based on the requirements.
The two main software that were used by us for the development of the system were:
Microsoft Visual Studio 2019 – It is an integrated development environment (IDE) that is
used to develop computer programs, websites, web applications and more. It includes a code
editor that supports code completion as well as code refactoring.
Microsoft SQL Server 2008 R2 – It is a comprehensive data management and business
intelligence platform. It is a software product with the primary function of storing and
retrieving data as requested by other software applications.
Thus, Visual Studio was used for coding and SQL serves for managing the database of the
system.
6.2 PROCESS/ PROGRAM/ TECHNOLOGY/ MODULE SPECIFICATIONS
TECHNOLOGY SPECIFICATIONS
There were certain different technologies/ languages that were used in the development of the web
application. We worked with languages like HTML, CSS, JAVASCRIPT, JQUERY, C# and
ASP.NET.
The designing, framework and styling of elements of the system was done using HTML
and CSS .
Certain validations like numeric fields, required fields, etc were implied with the help of
languages like JavaScript and jQuery.
Functions like database connectivity, inserting, storing, updating of the data and many
more were performed using the C# language.
Also certain functionalities of the system like GridView, TreeView, etc were all applied
using the ASP.Net elements
Process Specifications
The entire process of the system development was carried out in following steps:
Deciding the system design and features as per the requirements
Implementing the layout designed in the previous step and creating a framework of the web
application
Adding necessary styling elements to the forms
Applying validation to the required fields
Finally connecting the database to the system and respective forms of the application
In the initial days of our internship we were made familiar with the languages like C# and ASP.NET,
their framework, working, etc. Also we were familiarized with the softwares that were to be used in
the development process.
After receiving the basic training we moved on to start implementing the knowledge gained to
practical application. As the design, features and functionalities etc were discussed and finalized in
the earlier stages of the SDLC, we first started establishing a basic layout and framework for the web
application. We first incorporated the menu bar, tool bar and different menus of the system.
Next ,we moved on create all the webpages and forms present in different menus of the system using
HTML.
We began with the Masters menu, and then moved on to the other respective menus like
Transactions, Report, Store, Features, etc.
Figure 6.1 Code snippet from Company Master
Once the structure and layout of the pages was done, we further added CSS properties to different
elements like margins, width, background and text colour and many more.

Figure 6.2 CSS on DeptMaster Figure 6.3 CSS on the buttons in side panel
After the designing and styling of the system, we moved on to apply necessary validation to fields as
required per the requirement of the system. Certain validations like required fields, error messages
for the same, restricted input length or data type, etc were applied to the system where needed.
Languages like JavaScript and JQuery were used for the same.
Some code snippets for JavaScript and jQuery are as follow:

Figure 6.4 JavaScript for required fields
Figure 6.5 JavaScript for displaying div on checked box

Figure 6.6 jQuery code to copy field values
After adding the needed validations to the fields, we next moved on to understand and implement
database connectivity of the system. We learnt what tables were connected to which forms/web
pages, from which table was data displayed or inserted into. Once we had a good understanding of
the database in Microsoft SQL Server 2008 R2, we started implementing the database connection to
insert, display and update data in respective fields. Some code snippets for the same are as follow:
Figure 6.7 Code snippet from Narration Master

Figure 6.8 Code snippet from Company Master
Along with the database connectivity using C#, there were certain ASP.NET elements like GridView,
TreeView, etc were added to the system as per requirement. Some code snippets for the same are as
follow:
Figure 6.9 Code snippet for GridView
Figure 6.10 Code snippet for TreeView

6.3 FINDINGS / RESULTS / OUTCOMES
Finally, after the front end and backend programming we were able to create a system that matches
the design and requirements of the desktop application.
Some of the snapshots of the web application created are as follow:
Figure 6.11 Account Master
Figure 6.12 Pop-Up div box Figure 6.13 Required Validation

Figure 6.14 Live Search Figure 6.15 Tree View
Figure 6.16 GridView
Figure 6.17 Company Setup

6.4 RESULT ANALYSIS/ COMPARISONS/DELIBERATIONS
After putting in ample efforts and time in designing and programming of the software, we have
achieved a smooth functioning system as envisioned. Thus on comparison with the current desktop
application, following features can be inferred about the web application created:
An attractive and smooth user interface
User-friendly and easy to browse through
The functioning and features are same as the desktop application
All the elements like GridView, TreeView, etc work as needed
User can easily insert and access data from database
The buttons on the side panel provide easy access to related pages
The user identification and authentication maintains the privacy of the user
User working on desktop application was easily able to work on web application

199859 Testing
7 .0 TESTING
7.1 TESTING PLAN / STRATEGY
System testing is testing conducted on a complete integrated system to evaluate the system’s
compliance with its specified requirements. 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).
The company’s testing strategy was quite distinctive and aggressive. It consisted of several
different testing strategies to make sure that the system created is efficient and stands true to all the
expectations of the user.
Different testing strategies used are as follow:
1. Functionality Testing: It is a type of testing that seeks to establish whether each application
feature works as per the software requirements. Each function is compared to the
corresponding requirement to ascertain whether its output is consistent with the end user's
expectations.
2. Usability Testing: It is a type of testing method for measuring how easy and User-friendly a
software is, carried out by a small focus group similar to the users of the system. Its also
known as User Experience (UX) Testing. It tests how easily can a user navigate through the
system.
3. Interface Testing: Three areas are tested here: Application, Database and Web Browser.
 Application: Test requests are sent correctly to the Database and output at the client
side is displayed correctly.
 Web Server : Test Web server is handling all application requests without any service
denial.
 Database Server: Make sure queries sent to the database give expected results.
4. Database Testing: is a type of software testing that checks the schema, tables, triggers, etc.
of the Database under test. It also checks data integrity and consistency. It checks whether the
data entered in the web application is stored correctly in the database and vice versa.
5. Compatibility Testing: Compatibility testing is a part of non-functional testing conducted on
application software to ensure the application's compatibility with different computing

199859 Testing
environment. Different web browsers like Google Chrome, Opera, etc were used to test the
system
7.2 TEST RESULTS AND ANALYSIS
Based on the above testing strategies several test cases were deduced in order to ensure the efficient
and smooth functioning of the system. A brief detail about different test cases and their results are as
follow:
7.2.1 Test Cases
TEST ID TEST CONDITION EXPECTED ACTUAL REMARKS
OUTPUT OUTPUT
T001 Launch application Account Master Account Master Success
T002 Open pop up div box Category box Category box Success
on clicking the with results with results
respective field
T003 Live search in pop up Display only the Display only the Success
div box related options related options
T004 Add new row in New row inserted New row Success
GridView inserted
T005 Display TreeView TreeView TreeView Success
for selected option displayed displayed
T006 Required field Show alert on Show alert on Success
Validation empty field empty field
T007 Numeric field Accept only Accept only Success
validation numeric values numeric values
T008 Store inserted data in Inserted data Inserted data Success
database stored correctly stored correctly
T009 Display data from Required data Required data Success
database displayed displayed
T010 Launch application Application Application Success

199859 Testing
on Opera browser launched launched

T011 Navigate through Browse through Browse through Success
menu and tool bar website easily website easily

199859 Conclusion/ Discussion
8.0 CONCLUSIONS AND DISCUSSIONS
8.1 OVERALL ANALYSIS OF INTERNSHIP/ PROJECT
On taking a final look at our 12-week internship at SKP Software and the Garment Industries project
we can evaluate the following:
We were introduced to the industry culture and its methods
We were made aware about all the efforts that go into making a successful software
We were introduced to new languages like C# and ASP.Net, and had a practical experience
with them
Continuous feedback and guidance during the development process helped us a lot to make an
efficient system
Coming to the project, we were able to duplicate the desktop system into a web application
efficiently
The system created provides an easy and engaging experience to the user
The web application can capably store, display and update data in the database.
The user can successfully maintain a record of all the stocks, transactions, employees and
many more using just one web application
Users working with the desktop application were able to work with the web application
efficiently
8.2 DATES OF CONTINUOUS EVALUATION (CE-I AND CE-II)
Date of First Continuous Evaluation (CE-I) – 09/04/2022

Date of Second Continuous Evaluation (CE-II) – 02/05/2022
8.3 PROBLEMS ENCOUNTERED AND POSSIBLE SOLUTIONS
Various difficulties were faced by us during the course of our internship and the development
process, but the guidance of our mentors made it easier for us. Some of those were as follow:

The very first problem faced by us was the technical language barrier, the languages C# and
ASP.NET were completely new for us but the step by step training provided by the company
helped us overcome this challenge
There were certain aspects of the desktop application that were hard to understand, but the
team helped us to get a better understanding of the system
During the coding phase, there were certain errors that were hard for us to understand but the
team helped us rectify them and make it better
During the testing, certain flaws of the system were pointed out and we were unaware of the
solution, our mentor guided us to resolve the issues and make system more efficient
8.4 SUMMARY OF INTERNSHIP / PROJECT WORK
As a result of all the time and efforts put into the development of the web application, we were
finally able to create a system that was a one stop solution for all the manufacturers in the Garment
Industry to keep a record of their stocks, materials, transactions, employees and many more. We were
able to create a user friendly and easy to access interface that also protected the user’s privacy and
data security.
The 12-week internship programme with SKP Software was a great opportunity of learning and
getting a first hand experience with the industry’s method and working techniques. The internship
made us aware of the vast number of options the industry has to offer. Furthermore, being trained
under such an experienced mentor like Mr Kalpesh Trivedi was a blessing in itself. Physically,
working on a project made us aware about every minute detail and effort that goes into the
development process. It was a great opportunity to practically implement everything that we have
learnt till date. Also learning and working with new languages like C# and ASP.Net was a thrilling
experience. We are sure the training and the experience we have had at SKP Software will help us
greatly in our future endeavors.

8.5 LIMITATION AND FUTURE ENHANCEMENT
Talking about the drawbacks of the system we could say that overall we were able to create a web
application that was an efficient duplication of the desktop application. Although on getting the
feedback from the users we realized that there were certain limitations to the system such as lack of
homepage, the insertion process takes a little time to process completely, some flaws in the
designing, etc. We look forward to work more on the system and resolve all the above listed issues.
For the future of the system we envision the following:
To provide more security to the system.
To create a mobile application to provide better access
To incorporate multiple companies or agencies in one centralized system
Increase the database capacity of the system and make it more efficient

199859 References
REFERENCES
During the course of project we took help from certain external sources. Some of them are as follow:
https://docs.microsoft.com/en-us/aspnet/overview
https://docs.microsoft.com/en-us/dotnet/csharp/
https://www.geeksforgeeks.org/
https://stackoverflow.com/
https://www.w3schools.com/
https://www.youtube.com/kudvenkat
https://www.youtube.com/c/CodAffection
https://www.youtube.com/c/SwiftLearn

Garment Industries: Khushi Kunjay Chokshi

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Garment Industries: Khushi Kunjay Chokshi

Uploaded by

Copyright:

Available Formats

GARMENT INDUSTRIES

KHUSHI KUNJAY CHOKSHI

In partial fulfillment for the award of the degree of

L. J. Institute of Engineering & Technology

Gujarat Technological University, Ahmedabad

my guidance in partial fulfillment for the degree of Bachelor of Engineering in

Information Technology, 8th Semester of Gujarat Technological University,

Ahmadabad during the academic year 2021-22.

Prof. Prayag Patel Prof. Mitesh Thakkar

Internal Guide Head of the Department

Internship entitled Garment Industries submitted in partial fulfillment for the

degree of Bachelor of Engineering in Information Technology to Gujarat

Technological University, Ahmedabad, is a bonafide record of original project

Name of the Student Sign of Student

Khushi Kunjay Chokshi

sincere appreciation for the learning opportunities provided by SKP Software.

my Internal guide for their continued support.

imperfection. This opportunity has proved to be very useful to me in a way of taking

(180320116006) DATE:30th April,2022.

Gujarat Technological University i LJIET

The company is currently working on a stock management desktop application for

Gujarat Technological University ii LJIET

Fig 3.2 Project Scope 12

Fig 3.3 Iterative Model 15

Fig 3.4 Gantt Chart 21

Fig 4.1 Features Of Current System 28

Fig 4.2 List of Main Modules 30

Fig 5.1 System snap(Account Master) 32

Fig 5.2 System snap(Sales Tax Setup) 33

Fig 6.2 CSS on Dept Master 44

Gujarat Technological University iv LJIET

Fig 6.5 JavaScript for displaying div on checked box 45

Fig 6.6 jQuery code to copy field values 46

Gujarat Technological University iv LJIET

Table of Content vii

Table 3.1 Project Plan 16

Table 3.2 Estimated Code of Line 19

Table 4.1Hardware Requirement 23

Table 7.1 Test Results 52

Gujarat Technological University v LJIET

Abbreviation Full Form

HTML Hyper Text Markup Language

ASP Active Server Pages

CSS Cascading Style Sheet

M SQL Microsoft Structured Query Language

.NET Network Enabled Technologies

ERP Enterprise Resourse Planning

SDLC System Development Life Cycle

SRS Software Requirement Specification

Gujarat Technological University vi LJIET

List of Figures iii

Chapter 1 Overview of the Company 1

1.2 Different scope/ Product of work 1

1.3 Organization Chart 3

Chapter 2 Overview of different process being carried out in company 4

2.1 Work being carried out in each department 4

2.2 Technical specifications of major equipment in each department 5

2.3 Sequence of operation for end product 5

2.4 Details about each stage of production 7

Chapter 3 Introduction to Internship and Project 8

3.1 Introduction to internship and project 8

Gujarat Technological University vi LJIET

3.5 Technology and Literature Review 10