TABLES OF CONTENT

1.0 INTRODUCTION..
2.0 SYSTEM PLANNING
3.0 SYSTEM DEFINITION.
4.0 REQUIREMENT COLLECTION & ANALYSIS..

1.0 INTRODUCTION

The Qaila_Shira Fashion is a company selling a variety of cloth to all the communities such as Tshirt, skirt, Muslimah, and pyjamas. Instead, walk-in to the store we also provide online services
for customer that love online shopping. Besides that, it is easier for customers to order the
products just through calls and email. Basically, any orders we will record in the log-book
manually. All its operations like checking stock, confirming orders and process of payment is
done by manually. We think this is too hard and waste time because it takes a long time to
manage the operations. One of the problems with the manual system is each new product Id that
we receive has to be checked to ensure that there is no conflict and misinformation of product Id,
order and receipt. We will be studying and discuss about several issues for these problems which
will help us to understand the system's purpose and limitation. Based on our discussing, we will
find out a best implementable solution to fulfill our mission and vision for our company. So,
from our project we are required to design a database system to achieve our findings, planning
and acting.
2.0 SYSTEM PLANNING
In business online purpose, all information was developed depends on the requirements and
goals that must to achieve. As a business online in the Qaila_Shira Fashion has several goals to
make their customers feel comfort as much as possible when they use our product. Beside this
purpose, some objectives are being focused regarding on our mission and vision.
Objective of our project:

Allow customers to save time by ordering a variety of products just sitting in the house

rather than walk into the store.

Making a database system with all the possible features and creating the opportunity to

expand its operations and heap in the future.

Let the customer know about all information updates about the company such as the
arrival of new product and promotion.

3.0 SYSTEM DEFINITION

After identifying all the requirements, develop operations and objectives of the system, the
design was starting with along the system database. Failure to proper the requirements,
operations and objectives may lead the system design into the unsuitable state. To define system
database scope and boundaries, we have gone through a checklist that is included by following:
3.1 Database Size
When we are starting to build our new system we have to come up with a fixed size database
initially. Regarding on the estimation, we will define how many modules in the database to
be added that will need to be enhanced. The database will be operated and maintained by
database management, which is will store all the information of the system such as customer
details, product details and company details.
The database has boundaries or limitation that is enforced by existing software and hardware.
It may not work properly in times of pressure overloading on it. If our design will be poor, it
may cause much more limitations.
3.2 Operational Areas
We have divided the operational areas into 4 major areas which is customer information,
publicity, staff department and supplier department. Each area will be involved in specific
jobs according to their own tasks generated by the system. We cant expect any task outside
of the specific system to be performed and cannot expect anything that outside of the whole
system such as in shipping product, we cant manage the operations those are being done by
their area. We only can connect to shipping management area and inform the tracking
number to the customer.
3.3 Design and Implementation strategy
For our system designing, we will organize the specific modules inside every operational
area to build up the system. We create our module using Software Development Life Cycle
(SDLC) method inside every component and lead the whole lifecycle in a structured way.
Choosing a good module for our database can ensure the systems design will be efficiency.
3.4 System Modules

For our system modules, we will classify the systems with four modules. Each of the module is
composed of names processes based on the Table 3.4.1
Qaila_Shira Fashion System Modules
Module
Operational Area
Process Name
Staff Department
Staff Form
Staff
Customer Information
Customer Form
Customer
Publicity
Product Form
Product
Business Card
Card
Catalogue
Catalogue
Supplier Department
Vendor Form
Vendor
Shipping Product
Shipping

Table 3.4.1

4.0 REQUIREMENT COLLECTION AND ANALYSIS

Method
The overall information that we collect through the interviewing and select some respondent that
are interested and key in the information into our database.
Based on the analysis that we are record, many of respondent interested and love to shopping
online than walk into the store.
The information that been used was collected through interviewing respondent and all the
information was key in into database.
Based on the analysis that have been recorded, many of respondent prefer to shop through rather
than walk into the store itself.