Online Shopping System

A Project Proposal

Presented to

The Faculty of STI College

In Partial Fulfillment

Of the Requirements for the Degree of

Information Technology

by:

Cruz, Nheil Cymon F.

Limjoco, Lalaine S.

Mendiola, Miguel C.

Pronuevo, Ivan Job S.

Reyes, Plot Arman M.

Sir Kar-el Paulino

Project Adviser

October 2017
CHAPTER 1
1.0 Introduction

Technology has a major role in our lives. It has been recognized as a major driver of modernization

of different aspects in life. In the field of IT, there are lot of programmers who create different systems to

facilitate faster transactions for various companies. The time that technologies has arrived, the whole

world changed in the way we live, work and spends leisure time. That’s why we created online shopping

system that is user friendly in able to help our client/clients. Online shopping is the process whereby

consumers directly buy goods or services from a seller in real-time, without an intermediary service, over

the Internet.

1.1 Background of the Study

Evangeline Home Furniture starts back in way back 1978 as small furniture shop. As

time goes by, Evangeline Home Furniture grew bigger as they have many branches

across the province of Bulacan. We ask Mr. Ronnel Galdacan some question about their

company. Mr. Ronnel Galdacan is the owner of the Evangeline Home Furniture in

Bustos. He stated that he is hired here because the system they process in their

inventory. His background was he work for financial institute company for 15 years. He

has similar background from his previous company. Evangeline only market their

business by using advertising referral of the customers. They entertain the customers by

good customer service. If the customer feedback is good they can refer to other people.

They also have streamer if they have a sale in their company. Their goal is to have many

branches not in Bulacan, but also in other provinces. Their mission is to serve the people

with good customer service and serve the items in good condition and on time deliveries.

They want an online system because of their inventory. To have a high reachability for

people to look their items even they are not visiting their shop. Also they can advertise
 and deliver their products easily to the customer. They can deliver everywhere in the

country and to promote the items in the net.

Online Shopping is the process consumer go through to purchase products or services

over the Internet. An online shop or virtual store cause the physical analogy of buying

products or services a bricks-and-mortar retailer in a shopping mall.

Customer make purchase in order to satisfy needs. The wealth of products and services

produced in a country make our economy strong. Online shopping is a type of electronic

commerce used for business to business and business to consumer transactions.

1.2 Statement of Objective

1.2.1 General Objective

To create and develop Online Shopping System for Evangeline Home Furnishing Inc. that makes

our client more convenient in their daily objectives. Our main objective is to entertain our customer with

our website and to improve their sales.

1.2.2 Specific Objective

 To create a module to promote a service or product online.

 To create a module to have high reachability to people.

 To create a module to convert the number of people that buys the product from web.

 To create a module to have a 24/7 customer support through online.

1.3 Significance of the Study

Owner. To improve their marketing strategies using the privilege of the web technologies targeting their

entire prospect customer through online in faster, easier, hustle free without worrying the legitimacy of the

product.

Staff/Employee. This will help to minimize their task and speed up the processing of information. Data will

be more secure and relations between the Evangeline Home Furnishing Inc. and its client or customer will

be greatly improved.

Customer. This will help for easier and faster shopping. The customers or client will be able to order

goods online from wherever they are.

Future Developer. The knowledge that will gain in this study would help them in developing other system

in the future.

1.4 Scope and Limitation

Scope

Front End

 Registration Module.

This module lets the customer create an account for them can have an access to buy and reserve

products.

 Products Module.

This module is where you can select items you want to buy.

 About Us Module.

This module shows the history and background of the company.

 Customer Care Module.

This module lets the customer post their comments and feedback for the company.
  Add Cart Module

This module can add products to the cart.

BACK END

 File Maintenance Module.

This module lets the admin to add, edit, and delete products that are posted in the products

module.

 Report Module.

This module can create reports like by category and sales report.

 User Feedback Module.

This module lets the admin to read, delete, and post the comments from the customers.

 Sales Module.

This module lets the admin to check the sales of the company.

Limitation

 Exclusive only for the company

 Delivery process takes lots of time.

CHAPTER 2
 Spiral Model

The spiral model is a risk-driven process model generator for software projects. Based on the unique risk

patterns of a given project, the spiral model guides a team to adopt elements of one or more process

models, such as incremental, waterfall, or evolutionary prototyping.

• Planning Phase: Requirements are gathered during the planning phase. I will gather all of the

information about the system error form the customer to figure out what’s happening.

• Risk Analysis: a process is undertaken to identify risk and alternate solutions. I will identify

the known problems in the system and start planning how I will work on it.
• Engineering Phase: In this phase software is developed, along with testing at the end of the

phase. Once the problem has been found, I will start working on it by trial and error until they

fixed the system.

• Evaluation phase: This phase allows the customer to evaluate the output of the project to

date before the project continues to the next spiral. I will give it to the customer to test it,

when the customer satisfied working on system, the job is done, once a customer found an

issue, I will fix it asap

CHAPTER 3
Research Methodologies

This chapter presents the method of research used, bases of information respondents of the study and

construction of instruments, methods used in developing system and statistical behavior of the study.

Methods of Research

Descriptive research is used to describe characteristics of a population or phenomenon being studied. It

does not answer questions about how/when/why the characteristics occurred. The purpose of the study is

to describe systematically a situation or area of interest factually and accurately.

Library research involves the step-by-step process used to gather information in order to write a paper,

create a presentation, or complete a project. ... They describe, analyze, and/or evaluate information found

in primary sources.

Survey research is a commonly used method of collecting information about a population of interest.

There are many different types of surveys, several ways to administer them, and many methods of

sampling.
Sources of Data

Software Evaluation. Criteria-based assessment is a quantitative assessment of the software in terms of

sustainability, maintainability, and usability. This can inform high-level decisions on specific areas

for software improvement.

Feasibility Checklist. It is a software assessment that is answerable by yes or no determining how

technically, operationally, and economically feasible tangible or not in the development of the proposed

system.

Unconstructed Interview. It is a method of interview in which questions are not prearranged. These non-

directive interviews are considered to be the opposite of a structured interview which offers a set amount

of standardized questions. The form of the unstructured interview varies widely, with some questions

being prepared in advance in relation to a topic that the researcher or interviewer wishes to cover. They

tend to be more informal and free flowing than a structured interview, much like an everyday

conversation. Probing is seen to be the part of the research process that differentiates the in-depth,

unstructured interview from an everyday conversation. This nature of conversation allows for spontaneity

and for questions to develop during the course of the interview, which are based on the interviewees'

responses. The chief feature of the unstructured interview is the idea of probe questions that are

designed to be as open as possible.

Methods Used in Developing a Software

The company and its customer will help them to easily transact order. The developer used certain

software like Dreamwave, Xamp, Wamp and PHPMyAdmin SQL as database of our system
CHAPTER 4
Documentation of the Current System

Ever since the Evangeline Home Furnishing Inc. has not been using the proposed
system, their business is not capable at all time, there are basing on their costumer’s manual
evaluation. They say that their costumer is their advertisement to other costumer.

Nowadays, the online shopping system is the most popular way of shopping. Through
using the proposed system “Online Shopping for Evangeline Home Furnishing Inc.” it will make
the current business process secure, fast and more organized.
CHAPTER 5
SOFTWARE / PROJECT ESTIMATION

Effective software project estimation is one of the most challenging and important activities in software
development. Proper project planning and control is not possible

Without a sound and reliable estimate. As a whole, the software industry doesn’t estimate projects well
and doesn’t use estimates appropriately. We suffer far more than we should as result and we need to
focus some effort on improving the situation.

Under-estimating a project leads to under-staffing it (resulting in staff burnout)

Under-scoping the quality assurance effort (running the risk of low quality deliverables),

And setting too short a schedule (resulting in loss of credibility as deadlines are missed).

For those who figure on avoiding this situation by generously padding the estimate, over estimating a
project can be just about as bad for the organization! If you give a project more resources than it really
needs without sufficient scope controls it will use them. The project is then likely to cost more than it
should (a negative impact on the bottom line), take longer to deliver than necessary (resulting in lost
opportunities), and delay the use of your resources on the next

5.1 Schedule of Activities

This will deal about the schedule of activities that the proponents have undergone in developing
the proposed system. The proponent shall create a tracking record which will serve the as guidelines in
their development
2017

Activities June July August September October

Data Gathering

Analysis

Design

Coding

Testing

Evaluation

Implementation
5.2 Cost Estimation

Software cost comprises a small percentage of overall computer based system cost. There are a number
of factors which are considered, that can affect the ultimate cost of the software as-human, technical,
Hardware and Software availability.

The main point that was considered during the cost estimation of project was its sizing. In spite of
complete software sizing, function point and approximate lines of code were also used to “size” each
element if the Software and their costing.

The cost estimation done by the proponents for the project also depend upon the baseline metrics
collected from past projects and these were used in conjunction with estimation variables to develop cost
and effort projections.

We have basically estimated this project mainly on two bases –

1.) Effort Estimation – This refers to the total man-hours required for the development of the project.
It even includes the time required for doing documentation and user manual.
2.) Hardware and Required Estimation – This includes the cost of the PC’s and the hardware cost
required for the development of this project.
CHAPTER 6
REQUIREMENT ANALYSIS SPECIFICATION

In this chapter the proponents will discuss the requirement analysis specification of the
proposed system, Included here is the list of hardware and software specification to show the
requirement of the proposed system, the entity relationship diagram that shows the relationship
of the attributes. Data flow diagram gives the logical information about the data and how they
were flowing through the system.

6.1 Process Specification/Modeling

This is a vital part of developing a system. It is partially divided into parts including the ff.
Hardware and Software.

6.1.1 Hardware Requirement

The most common set of requirements defined by any operating system or software application
is the physical computer resources, also known as hardware, A hardware requirements list is
often accompanied by a hardware compatibility list (HCL), especially in case of operating
systems. An HCL lists tested, compatible, and sometimes incompatible hardware devices for a
particular operating system or application.

6.1.2 Software Requirement

Deals with defining software resource requirements and prerequisites that need to be installed
on a computer to provide optimal functioning of an application. These requirements of
prerequisites are generally not included in the software installation package and need to be
installed separately before the software installed.

.
6.2 Data Specification/Modeling

6.2.1 Context Diagram

A system context diagram (SCD) in software engineering and systems engineering is a diagram
that defines the boundary between the system, or part of a system and its environment, showing
the entities that interact with it. This diagram is a high level view of a system.
6.2.2 Data Flow Diagram

A graphical representation of the “flow” of data through an information system, modeling its
process aspects. A DFD is often used as a preliminary step to create an overview of the system,
which can lated be elaborated.

Diagram Zero
Child Diagram
6.2.3 Hierarchical Input Process Output

Is a systems analysis design aid and documentation technique form the 1970s, used for
representing the modules of a system as a hierarchy and for documenting each module.

Online Shopping for

Evangeline’s Home
Furnishing Inc.

1.0 Login 2.0 Search 3.0 Add 4.0 Order 5.0

Items to cart Purchase

1.1 Sign
Up

3.1 3.2 Delete 4.1 Item 4.2 Total 5.1

Update Item Details Price of Delivery
Item the Item
6.2.4 Entity Relationship Diagram

Shows the relations 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.
CHAPTER 7
Software Design Specification

In this chapter in the context of software, Design Specification is usually a design document that

describes all data, architectural, interface and component-level design for the software. A design

specification provides explicit information about the requirements for a product and how the product is to

be put together. Its use is called for where a product has to be specially made to meet a unique need.

7.1 Process Specification

This is a vital part of developing a system. It is partially divided into parts including the ff. Hardware and

Software.

Hardware Requirements

Keyboard Standard 102/105 key Keyboard

Mouse Optical Mouse or Wheel Mouse

System Unit Minimum Requirements: 900 MHz, Pentium 3

Monitor LCD Monitor

Drive Flash Drive

Hard Drive 2GB Hard Drive

Software Requirements

Operating System Windows XP to Windows 10

Browser Internet Explorer, Firefox, Google Chrome

Programming Language HTML, PHP, Javascript

Database MySQL

7.2 Data Specification/Modeling

7.2.1 Context Diagram

A system context diagram (SCD) in software engineering and systems engineering is a diagram
that defines the boundary between the system, or part of a system and its environment, showing
the entities that interact with it. This diagram is a high level view of a system.
7.2.2 Data Flow Diagram

A graphical representation of the “flow” of data through an information system, modeling its
process aspects. A DFD is often used as a preliminary step to create an overview of the system,
which can lated be elaborated.

Diagram Zero
Child Diagram
7.2.3 Hierarchical Input Process Output

Is a systems analysis design aid and documentation technique form the 1970s, used for
representing the modules of a system as a hierarchy and for documenting each module.

Online Shopping for

Evangeline’s Home
Furnishing Inc.

1.0 Login 2.0 Search 3.0 Add 4.0 Order 5.0

Items to cart Purchase

1.1 Sign
Up

3.1 3.2 Delete 4.1 Item 4.2 Total 5.1

Update Item Details Price of Delivery
Item the Item
7.2.4 Entity Relationship Diagram

Shows the relations 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.
7.4 Program/Module Specification

7.4.1 Registration Module

This module processes the personal information of the customer and stores it into the database. It verifies

the information entered by user whether if the user is legitimate for the purpose of the company security

that the customer is not troll or hoax.

7.4.2 Transaction Module

Transaction Module allows user to enable the end-user to define the business process with the usage of

transaction processing commands.

7.4.3 Add Cart Module

Is a module based system which allows the customer to easily extend the functionality for their needs. A

shopping cart is a piece of e-commerce software on a web server that allows visitors of the site to select

their desire items they choose to purchase. This allows online shopping customers to accumulate a list of

items for purchase. Upon checkout, the software typically calculates total for the order, including, shipping

and handling charges and the associated taxes.

 CHAPTER 8

Software Implementation

In this chapter, a software implementation method is a systematically structured approach to effectively

integrate a software based service or component into the workflow of an organizational structure or an

individual end-user.

8.1 Programming Consideration, Issues

8.2 System Requirement Specification

Hardware Requirements

Keyboard Standard 102/105 key Keyboard

Mouse Optical Mouse or Wheel Mouse

System Unit Minimum Requirements: 900 MHz, Pentium 3

Monitor LCD Monitor

Drive Flash Drive

Hard Drive 2GB Hard Drive

Software Requirements

Operating System Windows XP to Windows 10

Browser Internet Explorer, Firefox, Google Chrome

Programming Language HTML, PHP, Javascript

Database MySQL

8.2.3 Human Resource Requirements

This determines what criteria a system or modified system must meet. Requirements analysis and

definition is the first stage in the system engineering and software development process.
8.3 Software Testing

Software testing is a process of executing a program or application with the intent of finding the software

bugs. It can also be stated as the process of validating and verifying that a software program or

application or product: Meets the business and technical requirements that guided it's design and

development.

Software Testing depending on the testing method employed, can be implemented at any time in the

development process, however the most test effort is employed after the requirements have been denied

and coding process has been completed.

8.3.1 System Integration and Testing

As we develop the codes for our modules, it will be integrated and then the resultant main module was

tested to detect any malfunction or error of our system

8.3.2 Unit Testing

Unit testing is a software development process in which the smallest testable parts of an application,

called units, are individually and independently scrutinized for proper operation. Unit testing can be done

manually but is often automated.

We will make sure that the system is functioning well and see to it that the connections are the same with

the flow of our shopping system.

8.3.2 Validation Testing

In software project management, software testing, and software engineering, verification and validation

(V&V) is the process of checking that a software system meets specifications and that it fulfills its

intended purpose. It may also be referred to as software quality control.

The system was tested using prepared test causes to ascertain that the right system was built. It was also

done to test if the system satisfied all the problem requirement of the project.

8.3.3 Security Testing

Security testing is a process intended to reveal flaws in the security mechanisms of an information system

that protect data and maintain functionality as intended.

8.4 Installation Process

8.4.1 Attended Installation

On windows systems, this is the most common form of installation. An installation process usually needs

a user who attends it to make choices, such as accepting or declining an EULA, specifying preferences

such as the installations location, supplying passwords or assisting in product activation

8.4.2 Silent Installation

It is an installation of a software program that requires no user interaction. It is a convenient way to

streamline the installation process of a desktop application. Silent installs are performed by many

legitimate software programs, but they are also used by malware and PUPs to hide the installation

process from the user. Silent installs are useful for simple programs that have limited installation options.

They are also helpful for installing software on several machines at once.

8.4.3 Unattended Installation

Installation that is performed without user interaction during in progress or with no user present at all. An

unattended installation either does not require the user to supply anything or has received all necessary

input prior to the start of installation.

8.4.4 Headless Installation

Installation performed without using a computer monitor connected. To attended forms of headless

installation, another machine connects to the target machine and takes over the display output. Since

headless installation does not need a user at the location of the store, unattended headless installers may

be used to install a program on multiple machines at the same time

8.4.5 Scheduled Installation

8.4.6 Clean Installation

A clean installation of an operating system formats the drive and erases all existing data -- the user has to

back up all data beforehand. Applications will have to be reinstalled, as well. An upgrade, sometimes

referred to as an "in-place install," retains user data and settings.

 CHAPTER 9

9.0 System Maintenance Plan

Our maintenance plan should always be monitored when there’s a problem in the system, we will

maintain process of the system. If there is an error, we will visit Evangelines Home Furnitures and we will

monitor the system if it is still meet the system requirements. They can contact us through our facebook

and Gmail account by sending the file of system and make sure their system works fine