KAINAT BOUTIQUE AND LEHANGA HOUSE

Project Proposal

Supervisor
Dr. Asif Kabir

Submitted by

Zainab Shoukat

Roll No (53)

Session: 2019-2023

DEPARTMENT OF CS & IT

FACULTY OF COMPUTING & ENGINEERING

UNIVERSITY OF KOTLI AZAD JAMMU AND KASHMIR

Submission Date

(03-02-2022)
Contents

1 Introduction ............................................................................................................................. 3

2 Problem Definition .................................................................................................................. 3

3 How will it work? .................................................................................................................... 3

4 Feasibility Study ...................................................................................................................... 3

5 Gant Chart................................................................................................................................ 4

6 Software Requirement Analysis .............................................................................................. 4

Design ...................................................................................................................................... 4

Code Generation ...................................................................................................................... 4

Testing ..................................................................................................................................... 5

7 System Requirements .............................................................................................................. 5

8 Functional Requirements ......................................................................................................... 6

9 Non Functional Requirements ................................................................................................. 7

Use Case Diagram ................................................................................................................... 8

10 Sequence Diagram ............................................................................................................... 9

11 Activity Diagram ............................................................................................................... 10

1 Introduction
Today the internet and its boom have created a new economic scenario that not only
stresses on the classical concept of the “product” but also on the modern concept of “service”. It
is this level of service that dictates whether a commercial venture will succeed or not in the
market. To provide a high accessibility of service I will design the online shopping website, so
that potential customers need not go to a physical shop to buy products or services. They just
need to online to complete their purchases. Unlike the prevailing “brick and mortar” shops which
have physical existence, we will operate solely from cyberspace Kainat boutique and lehanga
house is aimed towards the vendors who want to reach out to the maximum cross-section of
customer and common people who can be potential customer. This project envisages bridging
the gap between the seller, the retailer and the customer.
2 Problem Definition
Most current systems have a physical foundation that is the root cause to quite a number
of problems. By maintaining multiple store fronts, itself being an expensive proposition, store
prices are forced to rise. Thus, by using my product, customer‟ competitors are at a disadvantage
because their costs are significantly higher than our costs, allowing clients to sell the same goods
at a lower price. As people become more accustomed to using the internet, they view ordering
products and services online as a time-saving and cost-saving experience, which is the very
essence of my online Kainat boutique

3 How will it work?

We will adopt three-tier architecture to separate the user interface from programming
logic, and programming logic from database. In reality, the architecture is n-tier, because there
can be any number of intermediate programming levels communicating with each other.

4 Feasibility Study
Feasibility study is the formal study to decide what type of system can be developed
which meet the needs of the organization and it is the comparison between the old system and
new system. A system request must need several tests to see whether it is worthwhile to proceed
further. This series of test is called feasibility study and it is virtual part of every system project.
Feasibility study will also detail the cost, time and project plan.
5 Gant Chart
This chart shows the whole projects phases in diagram which demonstrate that which
aspect of the system will take how much time and how process will be further accomplish.

6 Software Requirement Analysis

The requirement gathering process is focused specially on software. Requirements for
both the system and the software are viewed with the customers.

Design
The design process translates requirements into a representation of the software that can
be accessed for quality before coding begins.

Code Generation
The design must be translated into a machine-readable form. The code generation step
performs this task.
Testing
Once code has generated, program testing has begins. The testing process focuses on the
logical internals of the software, ensuring that all statements have been tested. Tests are
conducted to uncover errors and ensure that defined input will produce actual results that agree
with required results.

7 System Requirements
Tools Used:

Database Tool: MySQL

Development Tools: Php (Laravel)
Editor: Visual Studio code
Server: XAMPServer
Programming Language: HTML, Css, PhP, JavaScript
Documentation: Microsoft Office 2010
Graphic Designing Tool: Adobe illustrator Cs
System Used:
Intel Core i5 4 GB RAM 2.40GHz Hard disk
Operating System:
Microsoft Windows 10
8 Functional Requirements
The framework should bolster association of gatherings and decide, for each meeting
demand, a meeting date and area so that the greater part of the expected recipient will adequately
take an interest.

 The framework should screen products, particularly when they are held in an
appropriated way or intermittently.
 The framework should arrange Products under the imperatives communicated by
recipient.
Cart
A cart is a software application that typically runs on the computer where your Web site
is located (the Web server), and allows your customers to do things such as searching for a
product in your store catalog, adding a selected product to a basket, and placing an order for it.
Creating a cart so that customers can shop „n‟ no. of items and checkout finally with the entire
carts. The cart details can be viewed and items can be removed from the cart. Also, the customer
can modify personal profile information (such as phone number and shipping address) stored by
the Website .The customer can also view the status of any previous orders, and cancel any order
that has not been shipped yet. Also there will be secure mechanism for checking out from the
Shop.

Browse:
A user can browse the categories and view products manually. But Sometime user is
much interested in searching a specific product that best match with his requirements. User needs
to give his requirements by few mouse clicks and system will give the best matched products.

Registration:
user is prompted to login. There will be secure registration and profile management
facilities for Users and Customers. Customers should be able to mail the Shop about the items
they would like to see in the Shop. A customer can perform the actions like login, Browse
catalogue.
9 Non Functional Requirements
Before designing a web-based system, it is essential and helpful to identify Objectives
along with the relative importance of each objective. Keeping in mind the Drawbacks of the
existing system, following objectives of the proposed system are set.

Efficiency
Efficiency is defined as the economic utilization of available resources for achieving a
desired objective, so that proposed system must be more efficient than the existing one. It utilizes
minimal human and financial resources and still its output is far better in terms of time and
appearance and error free.

Time Factor
The new system will have the great advantage of time because the customer just has to
click and buy the products from great selection.

Productivity
Significant reduction of clerical task will lead to much improved system productivity.

Reliability
The new system will be more reliable than the manual system, due to its accurate, secure
environment.
9.1.1 Use Case Diagram
A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. In this context, the term "system" refers to something being developed or
operated. Use case diagrams are employed in UML (Unified Modeling Language), a standard
notation for the modeling of real-world objects and systems.

A use case diagram contains four components.

 The boundary, which defines the system of interest in relation to the world around it
 The actors, usually individuals involved with the system defined according to their roles.
 The use cases, which the specific roles are played by the actors within and around the
system.
 The relationships between and among the actors and the use cases.

Use Case diagram for Kainat boutique and lehanga house

 Use Case: Manage categories

Summary: To manage the different categories of available items.

Actor: Admin

Preconditions: Authorized user must be logged in.

Description: The admin manages categories by giving the required information.

Exception:

Canceled: If the admin presses the cancel button before manage categories has been selected,
then the control is resets to state.

Postcondition: Categories updated successfully.

10 Sequence Diagram
A sequence diagram is a interaction diagram that shows how processes 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 time sequence. It depicts the objects and classes involved
in the scenario and the sequence of messages exchanged between the objects needed to carry out
the functionality of the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence diagrams are
sometimes called event diagrams, event scenarios.

Sequence diagram for login

11 Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling Language,
activity diagrams are intended to model both computational and organizational processes (i.e.
workflows).Activity diagrams show the overall flow of control. Arrows run from the start
towards the end and represent the order in which activities happen. Activity diagrams may be
regarded as a form of flowchart.

Figure: Activity diagram for login