Chapter 1: Introduction

1.1. Background

E-Clothing system in PHP analysis is an e-commerce service to provide online services to the users. The
benefit of this research is to help users to choose the preferred products from different product categories
on online clothing communities. This system will discover the ones key phases in dashboard posted by
price for the products as a result. The purpose of this system defines feature visitors
can see the publicly available features such as browse products (clothing for men, women and children),
view details of products (size, color and price) and also able to look other content. Registered users also
able to view all publicly obtainable features and in addition to do this they able to purchase the products
by adding them into shopping carts.

1.2. Literature Review

You will find number of products online. Some might be correctly posted some may not. Sometimes the
products what you read will not be the same what we find after order. Online shopping indicates electronic
commerce to buy products or services directly from the seller through the internet. People have multiple
choices to choose their products while they are shopping through an online platform. In online shopping,
it is expected that shoppers are more likely to associate price attractiveness and time saving with their
intention to shop.

1.3. Problem Statements

There is no cumulative system for shopping online trustfully. The system database must be well structured
and all the entities must be related accordingly if the system will be more complicated then no technicians
and uneducated users will face any problems, so the system must be simple and easy for viewing and
buying products from the site. Therefore, users can easily find the newly added products with their labels
and can add to cart for shopping.

1
 1.4. Objectives

The objectives for the developments of this e-commerce system are as follows:-
➢ To get correct products for the users online.
➢ To become a member through registration process.
➢ To add to cart by browsing different products from the site.
➢ To guide the user to the products based on the user’s choice and needs.

1.5. Scope

➢This application can be used by many users who look for clothes online.
➢ This application can be used mostly in garments, textiles company and fancy shops.
➢ This application can be used by different users to analyze the trending products

1.6. Limitation

● Efficient inventory control methods can reduce but cannot eliminate business risk.

● Since only one person can access an account, it may not be suitable for situations where multiple
people handle accounts of a company.

2
 Chapter 2: System Analysis

2.1. Requirement Analysis

Requirement analysis is the process of precisely identifying, defining, and documenting the
various requirements that are related to a particular business objective. Requirements gathering
helps in clearly understanding the needs of the customer, defining the scope of the project, and
assessing the timescales and resources required to complete it. There are two types of
requirement which are as follows:

2.1.1. Functional Requirements

In order to make the application functional, we require the following:

a) User Registration
User registration is a process of registering users in our application by saving their credentials
in the database. So, in this article, we are going to learn how to implement user registration
actions in our project. Additionally, we are going to learn about different identity options that
could help us in a process.

b) User login
A login is a security principal, or an entity that can be authenticated by a secure system. Users need
a login to connect to SQL Server. You can create a login based on a Windows principal (such as a
domain user or a Windows domain group) or you can create a login that is not based on a Windows
principal (such as an SQL Server login).

3
c) User Profile

Unsourced material may be challenged and removed. A user profile is a visual display of personal
data associated with a specific user, or a customized desktop environment. A profile refers
therefore to the explicit digital representation of a person's identity. A user profile can also be
considered as the computer representation of a user model.

d) Owner profile

Managed profile works as separate persona, all the apps under profile are distinct it is similar to
new user. Profile owner is owner app of managed profile hence it doesn't have much power and
functionality compare to device owner thus it cannot control the entire user profile.

e) Logout

The user should be able to signing off of the system.

2.1.2 Non-functional Requirements

The non-functional requirements of this web application are as follows:

a) User-friendly

User-friendly is a term we use to describe anything that is easy to learn how to use. It is also
easy to use. In other words, even if it sophisticated, using it is simple and straightforward. We use
the term for computer interfaces, devices, equipment, facilities, and systems. This non-functionality
increases the involvement of users to use the application.

b) Maintainability

Maintainability is the ease with which a product can be maintained in order to: correct defects or
their cause, repair or replace faulty or worn-out components without replace still working parts,

4
 prevent unexpected working conditions, maximize a product's useful life, maximize efficiency,
reliability, and safety.

c) Performance

A performance is an act of staging or presenting a play, concert, or other form of entertainment.

It is also defined as the action or process of carrying out or accomplishing an action, task, or
function.

d) Ease of use

Ease of use is the usability of a product, service, tool, process or environment. It can be
accessed anytime from anywhere with an Internet Connection.

2.2. Feasibility Analysis

Feasibility study is a test of system proposed according to its work ability, impact on the organization,
ability to meet user needs, and effective use of resources. The feasibility study of this application had
been carried out which are as follows:

2.2.1. Technical
The main Technology and tools associated with this project are:
• Visual Studio2010
• HTML, CSS, Bootstrap, JavaScript, jQuery, SQL, PHP.
• Diagramming draw tool like Photoshop
Each of the technologies are freely available and technical skills required are
manageable.
It is clear that this project is technically feasible

2.2.2. Operational
Being a web-based application, this system needs computer or mobile device with browser. The system
will be user friendly so, the user will be comfortable with this system. From there, it is clear that the
project is operationally feasible.

5
2.2.3. Economic
Being a web-based application, this system will have an associated, hosting cost. Economic
feasibility is the analysis of a project's costs and revenues in an effort to determine
whether or not it is logical and possible to complete. This application is economically
feasible because this web application. This system will follow the freeware software
standard no cost will be charged from the potential user. The bandwidth required for the
operation will be low. Therefore, it is clear that the project is economically

6
 Chapter 3: System Design
System design is the process of defining the architecture, components, modules, interfaces and data for
a system to satisfy specified requirements. Design of the system brings down the knowledge of
requirements and analysis to design the software product. Generally, this chapter deals with the module,
database design, user interface design and the program design. For the designing of the application,
various diagrams like use case diagram, schema diagram, ER diagram, DFD etc. have been used.

3.1. Database design

Database design is the process of producing a detailed data model of database. This data model contains
all the needed logical and physical design choices and physical storage parameters needed to generate a
design in a data definition language, which can then be used to create a database. For the database design
of the application, ER diagram, Relational schema diagram which are as follows:

3.1.1. ER Diagram

An entity relationship model is a graphical representation of entities and their relationships to each other,
typically used in computing in regard to the organization of data within databases or information systems.
An entity is a piece of data- an object or concept about which data is stored and a relationship is how
the data is shared between entities.

7
 Fig 3.1.1 - ER diagram of database for Inventory manager

The above ER diagram shows the relationship between the user, accounts, sales, purchase and items of
the system. Entities have been represented by the rectangle, attributes of an entity have been represented
by the oval and the relationships between those entities have been represented by the diamond shape.

3.1.2. Database Relational Schema

A database relational schema is the skeleton structure that represents the logical view of the entire
database and defines how the data is organized and how the relations among them are associated. It
formulates all the constraints that are to be applied on the data and defines its entities and the
relationship among them. It contains a descriptive detail of the database which can be depicted by
means of relational schema diagrams. The relational schema of the application is as follows:

8
 Fig 3.1.2 - Database schema

3.2. Process Modeling

9
Process modeling is used to describe how things must/should/could be done in contrast to the process
itself which is really what happens. A process model is roughly an anticipation of what the process will
look like. The process modeling of the application is done through Flowchart and Use case diagram.

3.2.1. Flowchart
A flowchart is a type of diagram that represents the workflow or process, showing the steps as
boxes of various kinds, and their order by connecting them with arrows. The flowchart has used
simple geometric symbols and arrows to define relationships. The beginning or end of a
program is represented by an oval. A process is represented by a rectangle, a decision is
represented by a diamond and an I/O process is represented by a parallelogram which is shown
below:

10
Fig 3.2.1 - Flowchart

11
3.2.2 Use Case Diagram
A use case diagram is used to specify the functionality of the system from the point of view of
a user. Each use case describes a logical task that may be performed by a user. It mainly shows
the interaction between the system and the outside world. The use case of Inventory
Management System is given below:

Fig 3.2.2 - Use case diagram

12
 Chapter 4: Implementation

The implementation phase of the software development refers to the final process of moving
the solution from development status to production status. In this phase, Project developers
begin building and coding the software. This phase is followed by the software development
life cycle model used, tools used and the description of major classes/methods.

4.1. Software development life cycle model

Software development life cycle is a process followed for a software project, within a software
organization. It consists of a detailed plan describing how to develop, maintain, replace and enhance
specific software. The life cycle defines a methodology for improving the quality of software and the
overall development process. The model of SDLC used in this project is the waterfall model. The waterfall
model is comprised of series of very definite phases each one intended to be started sequentially only
after the last has been completed, with one or more tangible deliverables produced at the end of each
phase of the waterfall model of SDLC. Essentially, is starts with the heavy, documented, requirement
planning phase that outlines all the requirements for the project, followed by sequential phase of design,
coding, test-casing, optional documentation, verification, validation and finally deployment/release.

Figure 4.1: Waterfall model

13
4.1.1 Requirement and analysis
Before developing the system, it is crucial for requirement collection and analysis. This phase was used
to determine the requirements such as: who are target group for the system? How will they use the system?
These were the type of questions that were answered during the requirements gathering phase. We
performed field visit to gather information and searching on internet.

4.1.2 Design

In this phase, the actual design of the system takes place. The output of the design phase is the design
document that acts as an input for all subsequent SDLC phases. The design of the software is simple and
user friendly containing major activities, namely:

a) Register

b) Login

c) Dashboard

d) Add stock items

e) New sale details

f) View items

4.1.3. Coding/Implementation

Coding phase is carried out after the design phase. It includes the translation of the requirements specified
in requirement phase into a logical structure that can be implemented in a programming language. The
output of the design phase is a design document that acts as an input for all subsequent SDLC phases. The
project is done using android studio using android SDK.

4.1.4. Testing
After the code was developed in the coding phase, the codes were tested to check whether or
not it complied with the requirements and that the code actually solved the needs that were

14
 addressed in the requirements phase. Testing has been done for the individual activities of the
project. Errors that occurred were corrected and further debugging was performed.

4.1.5. Maintenance and Documentation

Maintenance phase includes the implementation of changes that application might undergo over a certain
period of time, or implementation of the new requirements and handling the residual errors that may exist
in the software even after the testing phase. Maintenance of the project will be followed according to the
changing requirements and trends. Similarly, documentation is the crucial part in the development of any
project which has been done hand in hand with the development process wherever possible.

4.2. Tools

4.2.1 Visual Studio

Visual studio is a free tool provided by Google which is used by developers to develop and debug code.
It offers more features that enhance the productivity.

4.2.2 XAMPP
It is a free and open-source cross-platform web server solution stack package developed
by Apache Friends, consisting mainly of the Apache HTTP Server, SQL database, and interpreters for
scripts written in the PHP.

15
 4.3. Programming language used such as

4.3.1. HTML

HTML is an acronym which stands for Hyper Text Markup Language which is used for creating web pages
and web applications. Let's see what is meant by Hypertext Markup Language, and Web page. Hyper Text:
Hypertext simply means "Text within Text." A text has a link within it, is a hypertext.

4.3.2. CSS

CSS stands for Cascading Style Sheets CSS describes how HTML elements are to be displayed on screen,
paper, or in other media CSS saves a lot of work. It can control the layout of multiple web pages all at once

4.3.3. Bootstrap

Bootstrap is an open-source JavaScript framework . It is a combination of HTML, CSS, and JavaScript code
designed to help build user interface components. Bootstrap was also programmed to support both HTMLand
CSS. Also, it is called Front-end-framework.

4.3.4. JavaScript

JavaScript is the Programming Language for the Web. JavaScript can update and change both HTML and
CSS. JavaScript can calculate, manipulate and validate data.

4.3.5. jQuery

Query is a fast and concise JavaScript Library. Write less, do more. jQuery simplifies HTML document
traversing, event handling, animating, and Ajax interactions for rapid web development.

16
4.3.6. SQL

Structured Query Language (SQL) is the standard and most widely used programming language for relational
databases. It is used to manage and organize data in all sorts of systems in which various data relationships
exist. SQL is a valuable programming language with strong career prospects.

4.3.7. PHP

PHP is a widely-used open-source general-purpose scripting language that is especially suited for web
development and can be embedded into HTML.

17
 Chapter 5: Testing

Software testing is the process of evaluation a software item to detect differences between given
input and expected output. It also assesses the feature of a software item.

5.1. Unit Testing

Unit testing is a software testing method by which individual units of source code sets of one or
more computer program modules. Each activity like registration, sign in, reset password,
dashboard, deal details, organization details, contact details, account etc. has been tested
individually.

5.2. Integration Testing

Integration testing is a software development process in which program units are combined and
tested as groups in multiple ways. The integration testing of the application has been done by
dividing the project in to modules.

5.3. System Testing

System Testing is a level of the software testing where complete and integrated software is tested.
The system testing has been performed by testing the whole application in an android phone.
 Chapter 6: Conclusion

6.1. Conclusion
E-clothing system is an web application that helps to manage and keep track of cloth and keep all
process related to garment. The system has been developed using a PHP framework, JavaScript as
main programming language. SQL store has been use to handle database. CSS language is used
for template and layout. All the requirements and the objectives of the project that have been
fulfilled by the android application. The admin can access all the information of the current
inventory and the activity that he/she had added in the application through the application from
anywhere around the world.

6.2. Future scope

Currently the application has the features of adding, editing the purchases, sales and items and
displaying them for a single user. In future, our Website will also include the features of analytics
with graphs and will also allow multiple staffs of the same business to login and manage.
 References
➢ Denise J., Deveau (14 January 2010). "Keeping It Real for Cross-Border Online Shoppers".
ecommercetimes.com. ECT News Network. Retrieved 19 March 2014.
➢ Nielsen, "Online Shopping Trends", (USA: The Nielsen Company, 2010)
 APPENDICES

Screenshot of the application