ACKNOWLWDGEMENT

We take opportunity to express our sincere gratitude to all those who helped us in various
capabilities in undertaking this project and devising the report.

We are privileged to express our sense of gratitude to our respected teacher whose unparalleled
knowledge, moral fiber and judgment along with his know-how was an immense support in
completing the project.

We take also grateful to the Head of Department, Information Technology, for the Brainwave
and encouragement given.

Sagar Mhasu Kambhire

 Index
1. Abstract.
2. Introduction.
a. Project Background
b. Project Statement
c. Objective
d. Scope
3. Literature Review And Project Methodology.
a. Introduction
b. Facts And Finding
4. System Implementation.
a. Hardware And Software Requirement.
5. System Analysis And Design.
a. Analysis
b. UML Diagrams.
DFD Diagram
Activity Diagram
Sequence Diagram
Use Case Diagram
Class Diagram
ER- Diagram
Deployment Diagram
Component Diagram

6. Form Designing
7. Testing
a. Manual Testing
b. Automation Testing
8. Test Cases
a. Future Scope
b. Conclusion
c. References
 Abstract

This system is desktop application software designed to handle time and billing tracking as well

as invoicing customers for services and products. Billing software can track the daily sale as

well as expenses associated with cloth shop.

This system provides the facility of adding discount and barcode at the time of billing. Barcode

based billing improves the speed of billing and tally the bill quickly.
 INTRODUCTION

1.1 Project Background

Smart Cloth Mall Application is the system for manage the mall business. The main point of
developing this system is to help mall administrator manage the mall business and help customer
for calculating product wise billing.

The project is developing because; many mall have a lot difficult to manage the business such as
customer ordering and product wise billing. By using manual customer ordering is difficult to
employee keep the correct customer information and maybe loss the customer information.

So, smart store system will develop to help the mall administrator to manage mall management
and for customer make their ordering and billing. Other than that, this project is to upgrade the
manual system and make the business easily to access and systematic.

1.2 Problem Statement

Nowadays, many shopping mall manage their business by manual especially take customer
ordering and write bill manually. Today, mall employee takes the customer ordering by manual
system with using paper. This is problem for mall employee the probability lost and duplicates
customer information. Additionally, it would affect to reputation mall in operate management of
ordering.

Furthermore, mall side needs management in the section product. This is the important to mall
employee to manage the product. Besides this section is for customer viewer the product that
mall prepared and make their ordering.

As a result, the current system (manual system) is not effective and efficient to use
anymore because the current system cannot save, manage and monitor the mall employee
information, product information , customer ordering information and generate report and bill
well.

1.3 Objective

Based on the problems stated above, the objectives of the project are:

i) To develop ordering and product wise billing system in mall.

ii) To develop use interface for digital mall management system
iii) To provide product information for customer

1.4 Scope

This system will be going to help customer and administrator in mall especially part of ordering
and product wise billing. Most of mall has a problem of the ordering and making daily sale
reports. The result of ordering and billing will give cashier easy to make ordering and
maintaining product wise billing and hopefully can smoothen up the job of administrator and
employee. This system also produces a computerized system in defining the best solution in each
ordering and daily expenses by cashier and administrator.

LITERATURE REVIEW AND PROJECT

METHODOLOGY
2.1 Introduction

The second phase in delivering a system is Literature Review and Methodology. The purpose of
Literature Review is to help in explaining how far the question needs to be investigated to maps
out the requirement needed. A Literature Review is a summary of previous research on a topic.
Literature Review can be either a part of a larger report of a research project. This chapter
explains about facts or statement which known as Literature Review that will be used as
guidance in developing the system.

Other that, methodology will elaborate Prototyping model approach. To develop this system,
methodology should be choose for one important part of the Literature Review.

2.2 Facts and Finding

Facts and findings establishes what the existing system does and what the problems are, and
leads to a definition of a set of options from which users may choose their required system
(Yeates and Wakefield, 2004).

This section will maps out different perspective which related to the project that will be
developed. It focused on the how customer order category wise product and maintain bill product
wise is important to customers and administrators. In the other situation, it will describe any
element or method which is useful to be used for the purpose of searching and gathered useful
information in developing this system.

System Implementation
We propose to build a software project that can efficiently handle and manage various activities
of a mall and all these activities will be happening under the supervision of the administrator.
The businesses in mall are now growing constantly. At the same time, the need for managing its
operations and tasks arises. The best way to optimize these activities is growing the business
online as well. Today’s generation encourages high-tech services especially over the Internet.
Hence the project is developed proficiently to help cloth shop owners automate their business
operations. This project serves the best way of maintaining customer’s information and caters
their needs.

Modules:

Cloth Entry: Here, we can add cloth by unique 8 digit id.

Update Cloth: If any change in cloth price or in the quantity then we can update it.

Employee Entry: We can add the employee with supporting staff details in this module. We can
also update and delete employee as per required.

Billing: Here, with the help of cloth id which is scan by the barcode reader, cloth price and total
are calculated. Further we can generate the bill.

Reports: In reports, we can view daily sale reports, items reports etc.

Hardware And Software Requirements:

Hardware Specification (Minimum):

Disc Space: 40 GB
PC Used: IBM Compatible
Processor: Pentium 3
Memory: 512 MB RAM
File System: 32 Bit

Software Specification:

Operating System : Windows XP.

Front End: C#
Back End: Sql Server 2008

System Analysis and Design

In this phase the software’s overall structure and its nuances are defined. In terms of client server
technology the no of tiers needed for the package architecture, database design, data structure
design etc are defined in this phase. Analysis and Design are very crucial in entire development
cycle. Any glitch in this phase could be expensive to solve in the later stage of software
development. Hence following is the essential approach taken during application designing:

3.1 UML Diagrams

a) DFD Diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. A DFD is often used as a preliminary step to
create an overview of the system without going into great detail, which can later be elaborated.

Fig. DFD Diagram

b) Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system. So the control flow
is drawn from one operation to another.

Fig. Activity Diagram

c) Sequence Diagram
A sequence diagram is an interaction diagram that shows how objects operate with one another
and in what order. It is a construct of a message sequence chart. A sequence diagram shows
object interactions arranged in timesequence.

Fig. Sequence Diagram

d) Use Case Diagram

UML Use Case Diagrams. Use case diagrams are usually referred to as behavior diagrams used
to describe a set of actions (use cases) that some system or systems (subject) should or can
perform in collaboration with one or more external users of the system (actors).

Fig. Use Case Diagram

e) Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among objects.

Fig. Class Diagram

f) ER- Diagram
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate the
logical structure of databases.

Fig. ER-Diagram

g) Deployment Diagram
Deployment diagram is a structure diagram which shows architecture of the system
as deployment(distribution) of software artifacts to deployment targets. Artifacts represent
concrete elements in the physical world that are the result of a development process

Fig. Deployment Diagram

h) Component Diagram
Component diagram is a special kind of diagram in UML. The purpose is also different from all
otherdiagrams discussed so far. It does not describe the functionality of the system but it
describes thecomponents used to make those functionalities.

Fig. Component Diagram

3.2 Database Designing

Table: Cloth
Attributes Data types Size Constraints Description
ClothID Int 11 Primary Key Unique ID for Cloth
ClothName Varchar 100 Not Null Cloth Name
Category Varchar 100 Not Null Cloth Category
Quantity Int 11 Not Null Cloth Quantity
PurchasePrice Decimal (11,2) Not Null Cloth Purchase Price
SalePrice Decimal (11,2) Not Null Cloth Sale Price

Table: Login
Attributes Data types Size Constraints Description
UserName Varchar 50 Not Null User Name

Password Varchar 50 Not Null User Password

Table: sale1
Attributes Data types Size Constraints Description
SaleID Int 11 Primary Key Temporary Sale ID
ClothID Int 11 Not Null Menu Item ID
ClothName Varchar 45 Not Null Menu Item Name
Price Decimal (11,2) Not Null Menu Item Price
Quantity Int 11 Not Null Menu Item Quantity
Total Decimal (11,2) Not Null Total Bill Per Order
CustomerName Varchar 100 Not Null Customer Name
OrderID Bigint 11 Not Null Customer Bill ID
Table: order2
Attributes Data types Size Constraints Description
OrderID Int 11 Primary Key Customer Order ID
Date of Customer
OrderDate Varchar 50 Not Null Order
Total Decimal (11,2) Not Null Total Customer Bill
EmployeeName Varchar 90 Not Null Name of Employee

Table: Employee
Attributes Data types Size Constraints Description
EmployeeID Int 11 Primary Key Waiter ID
EmployeeName Varchar 100 Not Null Name of Waiter
Address Varchar 100 Not Null Waiter’s Address
ContactNumber Int 11 Not Null Waiters Mobile No

3.3 Form Designing

Login Screen
Home Page
Masters: Customer Entry
Update Customer
Employee: Add Employee
Delete Employee
Employee Payment
Update Employee
Expense Entry
Delete Expense
Stock: Add Cloth
Stock: Add Category
Stock: Delete Cloth
Stock: Update Cloth
Billing: Add Purchased Cloth
Bill
Reports: Daily Sale
Report: Employee
 Chapter 4
Testing

Testing is the process of evaluating a system or its component(s) with the intent to find whether
it satisfies the specified requirements or not. Testing is executing a system in order to identify
any gaps, errors, or missing requirements in contrary to the actual requirements. This tutorial
will give you a basic understanding on software testing, its types, methods, levels, and other
related terminologies.

Types of Testing
Manual Testing
Manual testing includes testing a software manually, i.e., without using any automated tool or
any script. In this type, the tester takes over the role of an end-user and tests the software to
identify any unexpected behavior or bug. There are different stages for manual testing such as
unit testing, integration testing, system testing, and user acceptance testing.
Testers use test plans, test cases, or test scenarios to test a software to ensure the completeness of
testing. Manual testing also includes exploratory testing, as testers explore the software to
identify errors in it.
Automation Testing
Automation testing, which is also known as Test Automation, is when the tester writes scripts
and uses another software to test the product. This process involves automation of a manual
process. Automation Testing is used to re-run the test scenarios that were performed manually,
quickly, and repeatedly.
Apart from regression testing, automation testing is also used to test the application from load,
performance, and stress point of view. It increases the test coverage, improves accuracy, and
saves time and money in comparison to manual testing.
What is Automate?
It is not possible to automate everything in a software. The areas at which a user can make
transactions such as the login form or registration forms, any area where large number of users
can access the software simultaneously should be automated.
Furthermore, all GUI items, connections with databases, field validations, etc. can be efficiently
tested by automating the manual process.
When to Automate?
Test Automation should be used by considering the following aspects of a software:
 Large and critical projects
 Projects that require testing the same areas frequently
 Requirements not changing frequently
 Accessing the application for load and performance with many virtual users
 Stable software with respect to manual testing
 Availability of time
How to Automate?
Automation is done by using a supportive computer language like VB scripting and an
automated software application. There are many tools available that can be used to write
automation scripts. Before mentioning the tools, let us identify the process that can be used to
automate the testing process:
  Identifying areas within a software for automation
 Selection of appropriate tool for test automation
 Writing test scripts
 Development of test suits
 Execution of scripts
 Create result reports
 Identify any potential bug or performance issues
 Software Testing Tools
The following tools can be used for automation testing:
 HP Quick Test Professional
 Selenium
 IBM Rational Functional Tester
 SilkTest
 TestComplete
 Testing Anywhere
 WinRunner
 LoadRunner
 Visual Studio Test Professional
 WATIR
 Test Cases

Sr.No Test Data Expected Result Actual Result Status

(Pass/
Fail)

1 User Login: Without Error message should Display Message: Pass

providing id and name display as “Invalid User” “Invalid User”

2 User Login: Providing Error message should Display Message: Pass

Valid username with display: “Enter valid ID” “Enter valid ID
invalid ID

3 Cloth Entry: Entering Error message: “ Cloth ID Display Message: “ Pass

cloth duplicate cloth id should be unique ” Cloth ID should be
unique ”

4 Item Entry: Without Error message: “Invalid Display message: Pass

giving tab at the end of Entry” “Invalid Entry”
cloth id click on view
button

5 Daily Sale Report: Error message: “Please Display Message: Pass

Without entering date Enter date ” “Please Enter date”
in Date textbox and
click on view button

6 Daily Sale Report: Error Message: “Please Display Message: Pass

Enter date format other enter date in correct “Please enter date in
than the system date format” correct format”
format

7 Product Entry: Without Error Message: “Invalid Display Message: Pass

giving tab in item Entry” “Invalid Entry”
number field click on
update button
 Future Scope

We can give online home delivery of product in future for home delivery. Using home delivery
concept we can convert our application as a smart online shopping mall application. We can
implement this through the networking between home delivery website to mall administrator
system.
 Conclusion

Smart Cloth Mall Application are developed as a system-based desktop application. We tried to
solve each problem occurred by using the manual system. Project objective and project scope
identified the solution for each of the problem. This system hopefully can overcome the problem
in the current system.
 Refrences

1) www.w3schools.com
2) http://www.c-sharpcorner.com
3) https://www.lightspeedhq.com/pos/mall
1.