Professional Documents
Culture Documents
Acknowledgement………..……..…..…………………………………………………….…..i
Abstract………………………..……………………………………………………………...ii
List of Figure………………......……………………………………………………………...v
List of Table…...…………..…………………………………………………………………vi
1.0 INTRODUCTION ........................................................................................................ 1
1.1 PROJECT SUMMARY ................................................................................................. 1
1.2 PURPOSE ...................................................................................................................... 1
1.3 OBJECTIVE .................................................................................................................. 1
1.4 TECHNOLOGY AND LITERATURE REVIEW ........................................................ 1
2.0 PROJECT MANAGEMENT ...................................................................................... 2
2.1 PROJECT PLANNING ................................................................................................. 2
2.1.1 Project Development Approach and Justification ............................................... 2
2.1.2 Roles and Responsibilities ................................................................................... 3
2.2 PROJECT SCHEDULING ............................................................................................ 4
3.0 SYSTEM REQUIREMENTS STUDY ....................................................................... 5
3.1 USER CHARACTERISTICS ........................................................................................ 5
3.2 HARDWARE AND SOFTWARE REQUIREMENTS ................................................ 6
4.0 SYSTEM ANALYSIS .................................................................................................. 7
4.1 STUDY OF CURRENT SYSTEM ................................................................................ 7
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM ..................................... 7
4.3 REQUIREMENTS OF NEW SYSTEM ........................................................................ 7
4.3.1 Functional Requirements ..................................................................................... 8
4.3.2 Non-Functional Requirements ............................................................................. 8
Performance Requirements: ................................................................................................. 8
Safety Requirements: ........................................................................................................... 8
Security Requirements ......................................................................................................... 8
4.4 FEASIBILITY STUDY ................................................................................................. 9
4.4.1 Does the System Contribute to The Overall Objectives of The Organization? ... 9
4.4.2 Can the System Be Implemented Using the Current Technology and Within the
Given Cost and Schedule Constraints?............................................................................. 9
4.4.3 Technical Feasibility ............................................................................................ 9
5.0 SYSTEM DESIGN ..................................................................................................... 10
5.1 SYSTEM FLOWCHART ............................................................................................ 10
5.2 INPUT/OUTPUT AND INTERFACE DESIGN ......................................................... 11
5.2.1 Samples of Forms, Reports and Interface .......................................................... 11
6.0 IMPLEMENTATION PLANNING ......................................................................... 14
6.1 IMPLEMENTATION ENVIRONMENT .................................................................... 14
6.2 PROGRAM/MODULES SPECIFICATION ............................................................... 15
6.3 SECURITY FEATURES ............................................................................................. 15
7.0 TESTING .................................................................................................................... 16
7.1 TESTING PLAN .......................................................................................................... 16
7.2 TESTING STRATEGY ............................................................................................... 16
7.3 TEST SUITES DESIGN .............................................................................................. 17
7.3.1 Test Cases .............................................................................................................. 17
8.0 CONCLUSION AND DISCUSSION ........................................................................ 18
8.1 PROBLEM ENCOUNTERED .................................................................................... 18
8.2 SUMMARY OF PROJECT WORK ............................................................................ 18
9.0 FUTURE ENHANCEMENT .................................................................................... 19
Bibliography: .......................................................................................................................... 19
Book Reference : ................................................................................................................ 19
Web References: ................................................................................................................ 19
List of Figure
v
List of Table
vi
17CE007 INTRODUCTION
1.0 INTRODUCTION
1.2 PURPOSE
1.3 OBJECTIVE
The core coding is done in HTML, CSS and PHP. We have used the bootstrap
for making the dashboard attractive. We have used MYSQL as database.
We have divided the project into individual modules which have unique
constraint limited functionalities which will be further explained. The
estimated project development period has been 1 month. The project team
consists of 2 key members.
For the project development the approach we have made was using Iterative
waterfall model. In iterative development, first of all feature code is designed,
developed and then tested in repeated cycles. With each iteration additional
features can be designed, developed and tested until there is a fully functional
product which is ready to use.
model to be the best to follow for our project. We divided each individual
unique main functionality into a module. And each module was developed in
sequence in accordance with the functionality and working of that respective
module.
The project development and designing are equally divided among the team
members by even taking care of the documentation part. As the project was
divided into modular constructions and developments, each member has his
own key respective role into development of individual model and into the
final making of the project.
The Project Scheduling will be initially explained by the help of WBS (Work
Breakdown Structure). The Work Breakdown Structure is a hierarchical
reflection of all the work in the project in terms of deliverables. In order to
produce these deliverables work must be done. A typical approach in
developing a WBS is to start at the highest level, with the product of the
project. For example, you are assigned as the project manager of a New
Product Development project. The new product you are developing is a new
toy for children age's five through nine. The objective of this product
development project is to increase the revenue of the organization by ten
percent.
Our project will benefit more to specific organizations which are sell
product.
Normally,in this type of project handal by non-tech. person.so hear no need to any
technical person but some functionality like, data entry of product In database done buy
user.so,user knowledge about how to enter data in database.
Web- Browser
Windows- The oldest version of Windows supported is Windows XP
with Service Pack 2 installed.
MacOS- 64-bit x86.
Linux- 64-bit x86, 32-bit x86, 64-bit Power8/Power9.
The current system was studied before the development began of this
system. Firstly, the current system’s functionalities were observed and
thoughts were given to their respective extensions. Ms Excel was being used
before our system is developed.Our project’s all functionalities can be seen
in individually working standalone applications which are currently in the
market.
Customer can browse through the product catalog and the items to shopping
cart.he can proceed to check out as long as his shopping cart is not empty.
customer will require to login to the system when he proceed to check out,or
he can create an account if he not yet have one. The order will change to the
credit card registered in customer’s account
This project provides the software for online shopping. Thepurpose of this project is
To provide an easy shopping facility online and easy selling facility to the merchants
of all categories
Requirement 1: Registration
Requirement 2: Login
Performance Requirements:
The proposed system that we are going to develop will be used as the Chief
performance system for providing help to the organization in managing the
whole database of the student studying in the organisation. Therefore, it is
expected that the database would perform functionally all the requirements
that are specified..
Safety Requirements:
Security Requirements
This web application required the authentication of users before they use it
and it should never display any personal information to any other users. We
are going to develop a secured database. There are different categories
of users namely who will be viewing either all or some specific
information form the database. Depending upon the category of user the
access rights are decided. It means if the user is an administrator then he can
be able to modify the data, append etc.
C.S.P.I.T 8 U & P U. Patel Department of
Computer Engineering
PRJ2019CE008 SYSTEM DESIGN
4.4.1 Does the System Contribute to The Overall Objectives of The Organization?
Yes, our project contributes to the overall objectives of the organization. Our
organization microcreative website design & development agency solely
deals with manipulation of Geo-spatial data, and thus our system is of much
use to the organization. Our project can even be integrated with the already
existing software.
Yes, the system we have developed can be implemented using the current
technology and within the given cost and schedule constraints.
This project is complete web based application. The main technologies and
tools that are associated with this project are:
1. Subline
2. Xampp 7.3.0
3. MYSQL database
Figure 3 Flowchart
Hardware:
Software:
GUI Non-GUI
GUI introduces additional objects such as In Non-GUIs, the fields on the form have
logout buttons, id and other graphics that a redefined and unchangeable, the user
may be displayed or directly can just enter data in fields and use the
manipulated. functionality
We have used VS code (Version 1.34) for the development of the project and
MYSQL database. For the graphics and styling GUI we have used CSS and
its features.
Module 1: Sign Up
New intern has to provide appropriate details to get registered and use the web
application.
Data of user will be stored in table in database.
After registration display massage sign up successfully
Module 2: Login
Admin has to enter correct credentials to get access of managing
and manipulating interns’ information.
Admin will be redirected to the main page.
Entering wrong username and password system display massage.
There are no security features as of now and the website is easily accessible from a
computer having Xampp server installed along with proper data.
7.0 TESTING
This testing plan describes the test environment and the platform for
testing the project “Online Shopping System Using PHP-MYQL”.
The sole objective of the testing is to see if the project meets the
“Software Requirements”.
This plan will provide the guidelines for the testing team to test the
functionalities embedded into the project in every possible case.
Testing begins “in the small” and progresses “to the large”.
Initially individual components are tested using white box and black
box techniques.
After the individual components are tested and added to the system,
integration testing takes place. Once the full software product is
developed, system testing is performed.
Bibliography:
Book Reference :
1. Beginning PHP6,Apache,MySQL Web Development By Timothy
Boronczyk
2. Learning PHP, MySQL, CSS & HTML5 By Robin Nixon
Web References:
1. Fundamentals of database and front end:
2. http://www.javaknowledge.info/login-and- registration-example-in-jsp-with-
session/
4. PHP-mysql: https://www.eduonix.com/courses/Web-Development/Learn-PHP-and-
MySQL-Developm
5. https://www.javatpoint.com/php-tutorial
6. https://www.geeksforgeeks.org/php/