Executive Summary/Abstract: Tech Drive

Tech Drive 1
1. EXECUTIVE SUMMARY/ABSTRACT
Online shopping is a form of electronic commerce which, allows consumers to directly

buy goods or services from a seller over the internet using a browser. “Tech Drive” is an
online shopping site for selling computers, laptops and mobile phones. It provides the user
with a list of different types of products available for purchase in the store. This site will let
customers to view and order products online from any part of the world.
Using the system, management can expose their products by giving attractive offers
and discounts. So they can easily catch the attention of customers. Customers can purchase
products and services easily from the centre with less expense at the time of the offers. The
system has three categories of users. Admin, registered customer, and guest. Guest can view
all the product details and can request for an enquiry. Registered customers only get the
benefits from the system properly. They can purchase products at lower rates by viewing its
images and request for service. Notifications inform them the arrival of new offers or
products in the system. The admin is the person who controls the system. He can
add/edit/remove products, verify the orders and service requests and manage offers, stock and
payments.
The purpose of this system is to build software to reduce manual works. It is designed
from a user point of view. The user friendly design helps the users in accomplishing their
tasks with ease.
Department of Computer Science Nirmala College,Muvattupuzha

Tech Drive 2
2.1. EXISTING SYSTEM
Computer sales and service centre is a centre whose main products are the latest
models computers, laptops, and all the accessories related to them. This centre also deals all
the branded desktop computers and laptops.
The existing system of computer sales and service centre is a manual system in which
all process are done manually. All data and information are kept as files and records. The
Seller directly collects the data from the customers and store as a record.
2.2. DEFINITION OF PROBLEM
The existing system has many limitations like lack of accuracy, redundancy, expense,
low speed, inefficiency and unformatted outputs. In the existing system all tasks are done
manually. So there are a lot of issues related with retrieval and storage of the information.
Keeping track of data is a tedious task in this system.
2.3. PROPOSED SYSTEM
In the proposed system, a new Website called “Tech Drive” is developed for computer
sales and service centre. By implementing a computerized system, the limitation in the
existing system can be reduced. Manpower can be reduced to a great extent, and more
efficiently with accuracy which manifolds. More over consumption of time can be reduced to
a great extend and can increase the speed of information extraction, processing speed, data
security and hence it gives accurate reports. Advantages of the proposed system:
 It provides online shopping facility.

 It saves time.
 Information retrieval is faster.
 Flexibility.
 Easy transaction.
 The system should provide better security and control over data.
 Reduce costs.
 It removes the overhead of management.

Tech Drive 3
3.1. OBJECTIVE OF THE PROJECT
The main objective of this project is to provide a better platform for the customers
who need to buy computer, phone, and accessories. A customer can buy a new product from
home itself. This website facilitates the service also. So the customer can easily buy and
service their products. Customers get notification about their product’s status while
purchasing and servicing. The unseen quality of this project is, it provides a mechanism of
getting notification about new offers of products to the registered customers. This helps the
customer to buy things at lower price during the time of offers. Computer sales and service
will keep one or two pieces of each item initially and will provide the item in bulk on order.
3.2. STAKEHOLDERS
A person, group, organization that has interest or concern in an organization is called

as a stakeholder. Stakeholders can affect or be affected by the organization's actions,
objectives and policies. Stakeholders of this project are
The customers are the main stakeholder of this application. They get most of the
benefits of the application. Customers get a platform to purchase the branded products
directly from a shop without going there. They can buy products without any other
intermediaries and also can service their products by requesting online.
The next stakeholder is the owner. He is the admin of the system. He will get profit
from selling the products based on the customer needs. The pictures with description
displayed on the site will attract the customers. The site will also show offers for the
products. So customer will get interest to buy products through online.
3.3. SCOPE OF THE PROJECT
The Tech Drive is a web based application intended for online retailers. The main
objective of this application is to make it interactive and ease of use. It will make Searching,
viewing and selection of a product easier.
By converting the sales and service centre to a website, the customer can easily use
the services. They can buy computer, mobile phones or accessories from the online site. Also
the customer can book for services through online.

Tech Drive 4
3.4. FEASIBILITY ANALYSIS
After the problem is clearly understood and solutions are proposed, the next step is to
conduct the feasibility study, which is the part of system analysis. The main objective of
this study is to determine whether the proposed system is feasible or not. There are various
types of feasibility to be determined. They are,
 Technical Feasibility
 Operational Feasibility
 Schedule Feasibility
 Economic Feasibility
3.4.1 Technical feasibility

 Usage of minimum hardware. A System and an 8GB RAM are the main hardware
requirements
 Hardware and software requirement for implementation is minimum
3.4.2. Operational feasibility
• User friendly and attractive website.
• Can buy and service products easily through online.
• Offer notifications help to buy products at low rate.
3.4.3. Schedule feasibility
The schedule feasibility means that whether the project can be completed within a
specified time period or not. Each process will take a specific time to complete it. As per the
schedule for this project a time table is created as follows:
05/06/2018 to 13/06/2018 : Study the existing system

14/06/2018 to 20/06/2018 : Analysis
21/06/2018 to 25/06/2018 : Table Design
26/06/2018 to 12/07/2018 : Form design
15/07/2018 to 26/08/2018 : Development

Tech Drive 5
07/12/2018 : Submission of document .
So it satisfies schedule feasibility.
3.4.4. Economic feasibility- Cost - Benefit analysis
• Cost effective and saves time
• Can work on any desktops or laptops.
It can be developed under optimal expenses with the available hardware and software.
The computerized system provides easy and fast information retrieval and saves lot of time
and manpower.

Tech Drive 6
4.1 DEVELOPMENT ENVIRONMENT
The project is planned to develop on the following environment:

 IDE : Brackets
 Back End : MySQL
 Front End : PHP
4.2. CONSTRAINT
There are some constraints related to this project. They are:
 Time Constraints
 Project should complete, test and implement within 6 months.
 Hardware Constraints
 Needs 8GB RAM to implement.
 Laptop or desktop computer needed.
4.3. DELIVERABLES
Every project should contain a set of deliverables. This project also has a set of
deliverables as follows:
 The Application software.
 The user manual
 Installation manual (hosting)
4.4. RISKS
Every project should meet some risks.
 The software works only when there is proper internet connection.
 Customers need a bank account.
4.5. PROCESS MODEL
Unified process (UP) is a popular iterative and incremental software development

process framework. It is extensible framework which can be customized for specific

Tech Drive 7
organization or project. The UP when used in the software development the project lifecycle
can be divided in to four phases.
 Inception
 Elaboration
 Construction
 Transition
General idea is to develop a system through iteration (repeated cycles) and

incrementally (in small portion of time). Through them team members or stakeholders can
learn from their mistakes and apply that knowledge on the next iteration.
Working through iteration means that the development of application is split into
smaller chunks. In iteration features are defined, designed, developed and tested. Iteration
cycles are repeated until fully functional software is ready to deliver. The process doesn’t try
to start with the full set of requirements and design. Instead, team tries to prepare just what is
needed for the successful delivery of next iteration.
4.6. TEST STRATEGY
Testing is a process of executing a program with the interest of finding an error. A good
test is one that has a high probability of finding the yet undiscovered errors. Testing begins at
the level and works outward towards the interaction of the entire software. A series of testing
are performed for this project before the system is ready for acceptance. Each web page,
functionality validation scripts and other executable components were tested independently.
The integrity of entire system is checked. Some of testing strategies applied for the system
are listed here.
A test plan should contain the following:
 Test unit specification
 Features to be tested
 Approach for testing
 Test deliverables
 Schedule.

Tech Drive 8
 Unit Testing
 Modules are tested separately.
 Testing is carried out during programming stage itself.
 Individual modules such as admin, customer are tested.
 Got expected output against given input in the software.
 Integration Testing
 All the individual modules were combined and tested.
 System Testing
 The behaviour of whole system is tested.
 All modules are completely tested, there is no error.
 User Acceptance Testing
 Done by users or stakeholders.
 Checked whether the purchase, sale, stock updating are executed error
free.
 All user needs are satisfied.
4.7. TESTING ENVIRONMENT AND TOOL
 Testing on developers site

 To check whether the web site working properly.
 Check whether the site produce correct output for each test case.
 Testing on users site
 Test to get feedback from users.
 To check whether the web site running perfectly at users site.

Tech Drive 9
5.1. SCHEDULE
Schedule for this project is:
System Analysis : 14/06/2018 to 20/06/2018
Requirements Gathering : 21/06/2018 to 30/06/2018
Analyse the modules of the project : 2/07/2018 to 5/07/2018
Designing (Table) : 6/07/2018 to 13/07/2018
Development of web site : 14/07/2018 to 14/08/2018
Documentation : 9/10/2018 to 06/12/2018
Final Product Implementation : 12/12/2018
Document Submission : 10/12/2018
5.2. RISKS
 Delay from the scheduled date affects the whole project development.

Tech Drive 10
6.1. USER CHARACTERISTICS
The main Users are:
 Administrator
 Customer
 Guest
Admin
Web site reduces the work of admin by automating the processes. Admin can monitor the
sales and purchase operations effectively. The admin uses this system to fulfil the order and
requests from the customers. The admin may not be aware of how to use the new system. He
may not be fluent to the systematic execution of proposed system. So he/she need training to
the proposed system.
Customer
Customer can be an individual who has already an account. Customers use their account
to place their order, service request and payment. Proposed application is user friendly and
provides respective guidelines to use or navigate the system processes. So no training is
needed for customers.
Guest
Guest can be one who wishes to buy products. He can purchase products by creating
account. He can also get respective guidelines to use or navigate the system process.
6.2. FUNCTIONAL REQUIREMENTS
Features of the web application are:
• Web application is user friendly and easy to operate
• The customer can register, buy, book service and make payments through the
website.
• The admin can view and manage products and other details.
• Customers receive notifications about offers.

Tech Drive 11
• Customers are the main users.
• Customers can give feedback.
This section gives a functional requirement that applicable to the Computer sales and service
system.
There are two modules
 Admin module.
 Customer module.
The function of each module is as follows
Admin module: Admin manages the system. He can add a new product into the system
by providing its details and images. When a sale takes place the admin need to verify the
products, customer and payment details. After that he will assign a person for the delivery of
the product and set the product status according to the process. Even if the quantity of
product is less, the charges applied if it exceeds 2km.
For a service request, the admin need to verify the request. He finalizes a person to pick
up the product and deliver. Also change the product status. The admin can also add or remove
offers for a product and he can inform the customers by sending notifications.
The features that are available to the Administrator are:
• Can add/edit/view or remove products in to the site.
• Can add/remove offers to the products.
• Products stock management.
• Order conformation and management.
• Can send notifications.
• Can view complaints and service management.
• Can view the feedback.
Customer module: Mainly two type of customers, registered customers and guest.
Customers can view products and to buy, can add to cart. From the cart they can order the

Tech Drive 12
products by paying bill. He can also request for service and give feedbacks for previous
services from their account.
The features that are available to the Customers are:
• Can view the products.
• Can view about us, contact details and enquiry.
• Can cart items.
• Can place new orders for buying products or accessories.
• Can request for the service.
• Can register complaints and feedback.
• Get the notification.
• Can change password and address.
6.3. NON-FUNCTIONAL REQUIREMENTS

There are some non-functional requirements for this project. The main non-functional
requirements are:
Security
 Only the registered customers will get the service of the agency
 The username and password used for the system security.
 For secure payment, the customer needs a bank account.
Performance
Some Performance requirements identified is listed below:
 The database shall be able to accommodate a minimum of 10,000 records
 The software shall support use of multiple users at a time.
6.5. BUSINESS RULES
 Only registered customers can place order.

 There is no instalment payment.
 Delivery charge is assigned for each delivery.

Tech Drive 13
 Seasonal offers have a time period.
6.6. USE CASES
UC1 : sale.
Primary actor : admin
Stakeholders : customer
Main success scenario :
 After login customer can view products.

 He can cart the products.
 From cart he can purchase by making payments.
 Stock of product gets updated.
 Admin need to verify.
UC2 : service.
Stakeholders : customer
 After login customer can select the name of purchased product.

 Then describe the problem of product.
 Request for service.
 Admin need to verify.
UC3 : product
Stakeholders : admin
 Login into the system.

 Admin can add/edit/update product details.
 Update stock details.

Tech Drive 14
UC4 : Registration
Primary actor : customer
Stakeholders : admin
 Customers provide necessary details.

 Request for registration.
UC5 : Enquiry
Primary Actor : Guest
Stakeholders : Admin
 Provide necessary details.

 Make an enquiry
UC6 : Notification.
Primary Actor : Admin
Stakeholders : Customer
 Admin Login into the system.

 Send notification to the users about the newly arrived items.
UC7 : Payment
Primary Actor : Customer
Stakeholders : Admin
 Login into the system.

 Cash pay either through credit card or by net banking.

Tech Drive 15
7.1 USE CASE DIAGRAM
The most important aspect is to capture the dynamic behaviour when modelling a
system. Dynamic behaviour means the behaviour of the system when it is operating. Use case
diagram is one of the diagrams that describe the dynamic behaviour of the system. Use case
diagrams are used to gather the requirements of a system including internal and external
influences. These requirements are mostly design requirements. Hence, when a system is
analysed to gather its functionalities, use cases are prepared and actors are identified. When
the initial task is complete, use case diagrams are modelled to present the outside view.
The purpose of use case diagrams are:
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements is actors.
Use case diagrams specify the events of a system and their flows. But use case
diagram never describes how they are implemented. Use case diagram can be imagined as a
black box where only the input, output and the function of the black box is known. These
diagrams are used at a very high level of design. This high level design is refined again and
again to get a complete and practical picture of a system. A well structured use case also
describes the pre-condition, post condition and exceptions. These elements are used to make
test cases when performing the testing.
Basic use case Symbols

Tech Drive 16
An actor represents a coherent set of roles that users of a system play when interacting with
the use cases of the system. Actors can be anything-humans, devices, other systems. One
physical object can play several roles and so can be modelled by several actors.
Use cases describe what a system does, not how it does it. A use case contains
multiple scenarios, each of which describes a specific flow of events through the use case.
Use case behavior is specified by describing the scenarios clearly enough for outsiders to
understand.
Association symbol represent the connection between actor and use cases.
Include symbol include the relationship between use cases. One use case (base)
includes the functionality of another (inclusion case).
Extend symbol shows the relationship between use cases. Use case (extension)
extends the behavior of another (base).

Tech Drive 17
Use case Diagram
Tech Drive
Product management
Offer management
admin
Stock management
Payment management
Sale
Service
customer Notification
Account Creation
View products
Enquiry
Order placing
Feedback
guest

Tech Drive 18
fig 7.1.1 usecase diagram
7.2 SYSTEM SEQUENCE DIAGRAM
A sequence diagram is an interaction diagram that shows how objects operate with
one another and in what order. It is a constant 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.
Symbols in Sequence Diagram
 Life lines & life line boxes: - Active objects can be an object which is an instance of a
class and can be drawn with rectangular box called the life line box with its name is
specified within the box. The long dashed line tailing the object is called life lines.
Active object name
 Message: -It is used to illustrate the communication between different active objects.
Each message between object is represented with a message expressions and filled arrow
solid lines from the calling active objects life line to the recipient life lines.
 Synchronous: - This type of message is used when it is important that a message is
received & completed before execution of control flow begins.
 Return: -Return message shows that the control flow has return into the calling active
objects and the synchronous messages are completed its operations.
 Asynchronous: - This type of message is send from an active object and waits for a
responds. This type of message is used when control flow doesn’t lead to interrupted
before complete the operation.

Tech Drive 19
 Flat: -This type of message is used when there is no distinction between asynchronous
and synchronous messages.
SYSTEM SEQUENCE DIAGRAM
: guest : customer : Admin : Tech Drive
Login (username, pass)

Login successful
Manage item(pro_id)
Items added
Login (username, password)

Login successful
Order (pro_id, cust_id)
Order confirmation req
Confirmed
Notification of Order
service (pro_id, cust_id, sev_id)

Service confirmation
Confirmed
Service Notification
enquiry (enq_id,name)
details provided.
Account creation
Customer registered View details
Offer notification s

Tech Drive 20
Notification received
Fig 7.2.1 sequence diagram
7.3. OPERATION CONTRACT
Op1 Registration
Operation : Registration (cust_id : integer, name : string, ph : integer )
Cross reference : Use case Registration
Post condition : The instance R is created, data saved and response received.
R associated i.e. New customer get registered (association formed).
Op2 Sale
Operation : Sale(order_id : integer, cust_id : integer, product_id : integer)
Cross reference : Use case sale
Precondition : need to be a registered customer.
R associated i.e. product is sold (association formed).
Op3 Service Request
Operation : Service (service_id : integer, cust_id : integer, product_id : integer)
Cross reference : Use case service
Precondition : need to be a registered customer.
R associated i.e. request for service registered (association formed).
Op4 Enquiry
Operation : Enquiry (name : string, email : string )
Cross reference : Use case Enquiry
R associated i.e. An enquiry request is send (association formed).

Tech Drive 21
Op5 Stock
Operation : stock (pro_id: integer)
Cross reference : usecase product management.
Precondition : Arrival of new product/sale
R associated i.e. An item is added/updated.(association formed).
Op6 Payment
Operation : payment (pro_id: integer, cust_id: integer)
Cross reference : usecase payment management.
Precondition : new sale
R associated i.e. Payment is done.(association formed).
Op7 Notification
Operation : notification (not_id: integer)
Cross reference : usecase notification
Precondition : New products/Offer.
R associated i.e. Notification sent(association formed).
Op8 Feedback
Operation : Feedback (f_id: integer, cust_id: integer)
Cross reference : usecase feedback
Precondition :need to be a reg.customer.

Tech Drive 22
R associated i.e. Feedback sent(association formed).
8.1. CLASS DIAGRAMS
Class diagram is an important UML diagram used in the Designing phase. Class
Diagrams are the blueprints of the system or subsystem. Class diagrams can be used to model
the objects that make up the system, to display the relationship between the objects and to
describe what those objects do and the services they provide. Class diagrams are useful in
many stages of system design. Class diagram is a static diagram. It describes the attributes
and operations of a class and also the constraints imposed on the system. Class diagram
shows a collection of classes, interfaces, associations, collaborations and constraints. It is also
known as a structural diagram. UML diagrams like activity diagram and sequence diagram
can only give the sequence flow of applications.
Class diagram is created to perform the following functions:
 Capture and define the structure of classes and other classifiers.
 Define relationship between classes and classifiers.
 Illustrate the structure of a model by using attributes, operations and signals.
 Show the common classifier roles and responsibilities that define the behaviour of
the system.
 Show the structure and behaviour of one or more classes.
A class notation consists of 3 parts:

1. Class Name
The name of the class appears in the first partition.
2. Class Attributes
Attributes are shown in the second partition. Attributes map on to member
variables.
3. Class Operations
Operations are shown in the third partition. They are services the class
provides.

Tech Drive 23
CLASS DIAGRAM
Guest
Admin
Products Viewproducts ()
Id : integer
Id : integer Registration ()
View details()
Manage Name : string View
Addproducts()
1 * Category : string * 1
View/edit/remove()
Company : string
Offermanagement()
Des : string
Notification()
Customer
Buy
Id : integer
Cart
Name : string
can Id : integer
Address : string
1 Qty : integer
Viewproducts()
has Productid : integer
Buyproducts()
1 1 Name : string
Requestservice()
Price : string
Addtocart ()
Service
1 Id : integer
Productid :
integer
Request *
Name : string
Custid : integer

Tech Drive 24
Fig 8.1.1 class diagram
8.2. ACTIVITY DIAGRAMS
Activity diagrams are graphical representation of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the UML, activity diagrams
are intended to model both computational and organizational processes. It shows the overall
flow of control.
Symbols in Activity Diagram
Action State: - It is an automatic state once it started execution. It will come to completion
without any interruption at the middle of execution.
Transition: - When the action or activity state completes the flow of control passes
immediately to the next action or activity state. This is represented by using the solid lines.
Branching: - It specifies the alternative paths that are taken based on some Boolean
expressions.
Initial node: - The initial node is a control node from where the activity is invoked. An
activity may have more than one initial node.

Tech Drive 25
Final node: - The final node shows the end of the activity. An activity can have more than
one final node but the first one reached will stop the activity.
Join:-A join represents multiple incoming transitions and provide only one outgoing
transitions.
Fork:-A Fork represents only one incoming transitions and provide multiple outgoing
transitions.

Tech Drive 26
ACTIVITY DIAGRAM
ADMIN Start
Login
No
Check
Yes
Add/edit/Remove Manage Manage Manage Send Manage
Product Order Stock Service Notification Sale
Logout
Fig 8.2.1 admin activity diagram

Tech Drive 27
CUSTOMER
Start
Login
No
Check
Yes
make send receive request place make make
Registration Feedback Notification Service Order payment Enquiry
Logout
Fig 8.2.2 customer activity diagram.

Tech Drive 28
8.3. USER INTERFACE DESIGN
Interface design deals with the process of developing a method for two (or more)
modules in a system to connect and communicate. These modules can apply to hardware,
software or the interface between a user and a machine. An example of a user interface
could include a GUI, a control panel for a nuclear power plant, or even the cockpit of an
aircraft and systems engineering, all the inputs and outputs of a system, subsystem, and its
components are listed in an interface control document often as part of the requirements of
the engineering project. The development of a user interface is a unique field.
Input Design
The user interface design is very important for any application. The interface design
describes how the software communicates within itself, to system that interpreted with it and
with humans who use it. The input design is the process of converting the user-oriented
inputs into the computer based format. The data is fed into the system using simple inactive
forms.
The forms have been supplied with messages so that the user can enter data without
facing any difficulty. They data is validated wherever it requires in the project. This ensures
that only the correct data have been incorporated into system. The goal of designing input
data is to make the automation as easy and free from errors as possible. For providing a
good input design for the application easy data input and selection features are adopted. The
input design requirements such as user friendliness, consistent format and interactive
dialogue for giving the right messages and help for the user at right are also considered for
development for this project.
Input Design is a part of the overall design. The input methods can be broadly
classified into batch and online. Internal controls must be established for monitoring the
number of inputs and for ensuring that the data are valid. The basic steps involved in input
design are:
• Review input requirements.

• Decide how the input data flow will be implemented.
• Decide the source document.
• Prototype on line input screens.

Tech Drive 29
• Design the input screens.

The quality of the system input determines the quality of the system output. Input
specifications describe the manner in which data enter the system for processing. Input
design features can ensure the reliability of the system and produce results from accurate
data. The input design also determines whether the user can interact efficiently with the
system.
In this system several forms are used as input screen for collecting data form
the users. Forms contains text box drop down radio button multi line text box check box list
box etc. For entering values text box and multiline text boxes are used. For single selection
drop down, radio button are used. For multiple selection of values check box list is used.
Validation checking is done for all mandatory field. If the value format is incorrect wrong
message is displayed.
Main Inputs forms are:
Fig 8.3.1 Add product

Tech Drive 30
Fig 8.3.2 Registration
Fig 8.3.3 stock/offer updation.

Tech Drive 31
Fig 8.3.4 Cart
Fig 8.3.5 Service request.
Output Design
A quality output is one, which meets the requirements of end user and presents the
information clearly. In any system result of processing are communicated to the user and to

Tech Drive 32
the other system through outputs. In the output design it is determined how the information
is to be displayed for immediate need.
It is the most important and direct source information is to the user. Efficient and
intelligent output design improves the system’s relationships with the user and helps in
decision making. The objective of the output design is to convey the information of all the
past activities, current status and to emphasis important events.
The output generally refers to the results and information that is generated from the
system. Outputs from computers are required primarily to communicate the results of
processing to the users.
Output also provides a means of storage by copying the results for later reference in
consultation. There is a chance that some of the end users will not actually operate the input
data or information through workstations, but will see the output from the system.
Two phases of the output design are:
1.Output Definition
2.Output Specification
Output Definition takes into account the type of output contents, its frequency and its
volume, the appropriate output media is determined for output. Once the media is chosen,
the detail specification of output documents are carried out. The nature of output required
from the proposed system is determined during logical design stage. It takes the outline of
the output from the logical design and produces output as specified during the logical design
phase.
In a project, when designing the output, the system analyst must accomplish the following:
• Determine the information to present.
• Decide whether to display, print, speak the information and select the output
medium.
• Arrange the information in acceptable format.
• Decide how to distribute the output to the intended receipt.
Thus by following the above specifications, a high quality output can be generated.

Tech Drive 33
In this system an output or response is given to the user after submission of

each forms. Output screens are well defined. In most of the forms tables are used to display
the output information to the user. Report values are table formatted. User can print the
details.
Main output forms are:
Fig 8.3.6 front page

Tech Drive 34
Fig 8.3.7 Product Page
Fig 8.3.8 Account details

Tech Drive 35
Fig 8.3.9. Order details
Fig 8.3.10 service details

Tech Drive 36
Fig 8.3.11 notification.

Tech Drive 37
8.4. THEORETICAL BACKGROUND
 PHP
PHP Hypertext Pre-processor, commonly known as PHP is one of the
revolutionary scripting language which has enabled us to have a much better web
presentation today. This has fast become one of the widely used scripting languages which are
used for web development. One of the key features of this language is it’s an open
source which will enable anybody to use the platform it provides. PHP is used to
design dynamic web pages. Here you can find the starting origination of PHP and few basics
of the scripting language.
PHP is a server side scripting language which is used for generating dynamic
page which can be used for transferring on the web. The main plus point of PHP is that it is
an open source product and it can be freely downloaded from the web. The various
advantages of PHP include speed of execution by using only a little system resources. This
will increase the stability of the system, its simplicity which allows anyone to learn it very
easily. PHP is also extensible that it allows interfacing different libraries such as encryption,
XML etc. the PHP parser engine is identical irrespective of the operating system, so PHP
page need not be changed to run on different platform.
MySql
MySQL is an open-sourcer elational database management system (RDBMS) in

July 2013, it was the world's second most widely used RDBMS, and the most widely used
open-source client–server model RDBMS. It is named after co-founder Michael Widenius's. The
SQL acronym stands for Structured Query Language. The MySQL development project has
made its source code available under the terms of the GNU General Public License, as well as
under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-
profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation For proprietary
use, several paid editions are available, and offer additional functionality.The IDE used for
MySql is HeidiSql

Tech Drive 38
8.5. DATABASE DESIGN
A database is a collection of interrelated data stored with minimum redundancy to

serve many users quickly and effectively. The general objective is to make information
access easy, quick, inexpensive and flexible for the users. The general theme behind a
database is to integrate all information. Database design is recognized as a standard of
management information system and is available virtually for every computer system. In
database design several specific objectives are considered.
 Ease of learning and use

 Controlled redundancy
 Data independency
 More information at low cost
 Accuracy and integrity
 Recovery and failure
 Privacy and security
A database is an integrated collection of data and provides centralized access to the

data. Usually the centralized data managing the software is called RDBMS. The main
significant difference between RDBMS and other DBMS is the separation of data as seen by
the program and data has in direct access to store device . This is the difference between
logical and physical data.
Table Structure
A database is a collection of related data. The organization of data in a database has to

represent the underlying meaning or semantics of the data correctly and effectively. During
table design the nature and content of the record type, data items that are to be included in the
record and the characteristics of each data items that are to be included in the record and the
characteristics of each data item such as its name, type and width have to be considered.
Various factors are considered during the table design phase of system analysis. Some of
them are listed below.
 Purpose of the table

 Availability of the hardware
 Method of access

Tech Drive 39
 File activity
 File size
 Output requirements
 Input requirements
 File organization
Table design also deals with the design of physical database. A key field determines
how the access is to be implemented. Suitable key fields are identified various tables and are
coded appropriately. The type, width and size of the fields are identified. Techniques of file
organization are studied so that the most appropriate storage device can be selected and an
efficient database design can be achieved. Specifying the data between them identifies the
interface between system databases and other databases.
The designing of the tables in the database is done according to the rules specified for
database as described above. In the proposed project 22 tables are used and some of them
connected using foreign keys. Insertion and retrieval of values is easy by designing the
database in this way.
Table Design
Table design is a collection of complete details about a particular subject. These data
are saved in rows and columns. The data of each row are different units. Hence, rows are
called records and columns of each row are called fields. Data is stored in tables, which is
available in the backend. The items and data, which are entered in the input, form id directly
stored in this table using linking of database. We can link more than one table to input forms.

Tech Drive 40
8.7. DATABASE DESIGN
Table Name : tbl_customer.

Description : Details of Customer.
Primary Key : Cust_id.
Fieldname Length Data Type Description
Cust_id 6 Integer(PK) Customer Id.
Name 25 Varchar Customer name.
Address 40 Varchar Customer address.
Pin 5 varchar PIN Number.
Mobile 10 Varchar Customer contact number.
E_mail 20 Varchar Customer email address.
Username 15 Varchar Username for login.
Password 15 Varchar Password.
Table 8.7.1 registration
Table Name : tbl_product.

Description : Details of product.
Primary Key : Product_id.

Product_id 6 Integer(PK) Product Id.
Product_name 25 Varchar Product name.
MRP 10 Varchar Product MRP.
Price 10 Varchar Product actual
price.
Company 20 Varchar Product company
name.
Category 20 Varchar Product category.

Tech Drive 41
Sub_category 20 Varchar Product sub

category.
Offer 5 Integer Product offers.
Img1 50 varchar Product image
Stock 20 Varchar Product stock.
Description 50 Varchar Description of
product.
Highlight_1 50 Varchar Product highlights.
Table 8.7.2 product.
Table Name : tbl_service.

Description : Details of service.
Primary Key : Service_id.
Foreign key : Cust_id,Product_id.
Service_id 5 Integer(PK) Service Id.
Cust_id 6 Integer(FK) Customer id.
Product_id 6 Integer(FK) Product id.
Complaints 50 Varchar Compliant of

customer about
product.
Feedback 30 Varchar Feedback of the

Tech Drive 42
customer.
Date 10 date Date of compliant
registration.
Product_name 20 Varchar Product Name
Img1 50 Varchar Product image.
Status 25 Varchar Compliant status.
Table 8.7.3 service
Table Name : tbl_order.

Description : Details of order.
Primary Key : Order_id.
Foreign key : Cust_id,Product_id.
Order_id 5 integer Order id.
Cust_id 6 integer Customer id.
Product_id 6 integer Product id.
Qty 5 integer No. of products

purchased.
Date_time 15 date Order date and time.
Status 20 Varchar Order status.
Date 10 date Order date.
Img 50 Varchar Product image

Tech Drive 43
Mrp 10 Varchar Product price.
Table 8.7.4 order
Table Name : tbl_cart_head.

Description : Details of Cart.
Primary Key : Cart_head_id.
Foreign key : Cust_id,.
Fieldname Field Data Type Description
Cart_head_id 5 integer Cart head id
Cust_id 6 integer Customer id.
Table 8.7.5 carthead

Table Name : tbl_cart_sub.
Description : Details of Cart.
Primary Key : Cart_sub_id.
Foreign key : Cust_id,.
Fieldname Field Data Type Description
cartsub_id 5 Integer(PK) Cart sub id
carthead_id 6 Integer(FK) Cart head id.
product_id 5 Integer(FK) Product id
Qty 5 Integer(FK) Quantity
Table 8.7.6 cartsub

Table Name : tbl_enquiry.
Description : Details of Enquiry.

Tech Drive 44
Primary Key : Enquiry_id.
Enquiry_id 5 integer Enquiry id
Name 20 Varchar Name of enquirer.
Mobile_no 10 integer Mobile no. of

enquirer.
Email_id 25 Varchar Email id.
Message 60 Varchar Message.
date 10 date date
Table 8.7.7 enquiry

Table Name : notification_tbl.
Description : Details of notification.

Primary Key : Enquiry_id.
not_id 5 integer Notification id
cust_id 20 Varchar Customer id
Message 60 Varchar Message.
Date 10 date date
Table 8.7.8 notification

Tech Drive 45
9.1. TEST CASES
TEST CASE FOR CUSTOMER REGISTRATION
TC No. Test Steps Expected Actual Result Status(Pass/fail/not

Result executed)
TC1 Test by Value not Value saved. Fail
giving empty submit, a
fields without required
required message is
valuator displayed
Test by Value not Value not Pass
giving values submit, a submit, a
with required required required
field valuator message is message is
displayed displayed
Table 8.1 test case for required valuator

Result executed)
TC2 Test by Value not Value saved Fail
giving invalid saved and a
email format message
without email notification
validation should display
Test by Value not A message has Pass
giving invalid saved and a been displayed

Tech Drive 46
email format message like enter in

with email notification correct format
validation should display
Table 8.2 test case for email validator
Fig 9.1.1 registration with validation.

Result executed)
TC3 Test by It should limit Value saved. Fail
giving the entering of
lengthy the data to the
values to the field by the
fields without max length

Tech Drive 47
phone property
number
validation
Test by It should limit A message has Pass
giving the entering of been displayed
lengthy the data to the
values to the field by the
fields with max length
phone property
number
validation
Table 8.3 test case for phone number validation
TEST CASE FOR STOCK UPDATION

Result executed)
TC4 Test by It needs to Same quantity. Fail
purchasing reduce the
product quantity of
without stock product.
updation.
Test by It needs to Quantity Pass
purchasing reduce the changed.
product with quantity of
stock product.
updation
Table 8.3 test case for stock.
TEST CASE FOR PURCHASE

Result executed)
TC5 Test by Can’t Product can’t pass
purchasing purchase purchase.
product without
without user account.
account.

Tech Drive 48
Test by Can’t Product Pass

purchasing purchase purchased.
product with without
user account. account.
Table 8.3 test case for stock.
9.2. TEST REPORT
Test Report provides a summary of the results of test performed. A Test report
must contain the following details: -
 Test Summary
This must include basic information about what was tested and what
happened.
 Test Type
This must include basic information about what type of testing (unit testing,
integration testing, validation testing etc.) was done and what happened.
 Test Assessment
It should contain a comprehensive assessment of your interpretation of how

adequate the test was in light of how thorough the test plan said it should be? It must
also specify what wasn’t tested well enough.
 Test Result
Summarize the test result. Include a detailed description of any deviations

from the original test plan, design, test case, or expected results.
Include any issues or bugs discovered during the test.
 Variances
Describe any variances between the testing that was planned and the testing
that actually occurred. Also, provide an assessment of the manner in which the test
environment may be different from the operational environment and the effect of this
difference on the test results.

Tech Drive 49
CUSTOMER REGISTRATION-TEST CASE REPORT
Function Description % test case %test passed

executed
Customer Register with some 100% 98%
Registrations fields empty
Table 8.2.1 test case report for customer registration
CUSTOMERREGISTRATION-TEST CASE REPORT
Function Description % registration

test case %test passed
Table 8.2.2 Test case report for customer
executed
Customer Register with 100% 98%
Registrations incorrect format for
email field
CUSTOMERREGISTRATION-TEST CASE REPORT
Function Description % test case %test passed

executed
Customer Registe rwith 100% 98%
Registrations lengthy values for
phone number field.
Table 8.2.3 Test case report for customer registration

Tech Drive 50
10.1. SYSTEM IMPLEMENTATION
Implementation is the process of converting a new or a revised system design into an

operational one. Conversion means changing from one system to another. The objective is to
put the system into operation while holding costs, risks and personnel irritation to minimum.
It involves:
• Creating computer compatible files.
• Training the operating staff.
• Installing terminals and hardware.
Implementation includes all those activities that take place to convert from the
old system to new system. The new system may be totally new, replacing an existing manual
or automated system or it may be a major modification to an existing system. Proper
implementation is essential to provide a reliable system to meet the organization
requirements.
Successful implementation may not guarantee improvement in the organization
using the new system, but improper installation will prevent it. The method of
implementation and the time scale to be adopted are found out initially. Next the system is
tested properly and the same time users are trained in the new procedures.

Tech Drive 51
IMPLEMENTATION PROCEDURES:
Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system. In the
initial stage they doubt about the software but we have to ensure that the resistance does not
built up as one has to make sure that
 The active user must be aware of using the system.
 Their confidence in the software is built up.
 Proper guidance is imparted to the user so that he is comfortable in using the
application.
Before going ahead and viewing the system, the user must know that for viewing the
result, the server program should be running in the server. If the server object is not up
running on the server, the actual processes won’t take place.
POST IMPLEMENTATION:
The final step of the systems approach recognizes that implemented solution can fail
to solve the problem for which it was developed. The results of implementing a solution
should be monitored and evaluated .This is called post implementation review process, since
the success of a solution is reviewed after it is implemented.
“Computer Sales and Service centre” software is hosted on the internet. The owner and
customers can access the website anywhere using separate username and password.
10.2. SYSTEM MAINTENANCE
This phase occurs as a result of deploying the whole system at the end users
organization. They will perform the beta testing at the end user and inform to the developers
about any needed modification to the application. The customer records all the problems that
are encountered during the beta testing and reports these to the developer at regular intervals.
Maintenance has not yet been performed and is a part of future plans.
 Corrective Maintenance
Even with the best quality assurance activities, it is likely that the customer will
uncover defects in the software. Corrective maintenance changes the software to correct the
defects.
 Adaptive Maintenance

Tech Drive 52
Over time, the original environment (CPU, operating system, business rules, external
product characteristics) for which the software was developed is likely to change. Adaptive
maintenance results in modification to the software to accommodate changes to its external
environment.
 Enhancement Maintenance
As software is used, the customer/user will recognize additional functions that will
provide the benefit. Perfect maintenance extends the software beyond its original functional
requirements.
 Preventive Maintenance
Computer software deteriorates due to change, and because of this preventive
maintenance often called software engineering, must be conducted to enable the software to
serve the needs of its end users. Preventive maintenance makes changes to computer
programs so that they can be more easily corrected, adapted and enhanced.
11.1. ORGANIZATION PROFILE
Bright Future Education working under Aptech LEARNING is a major international

force in IT consulting and services across in 1300countries.Utilizing our broad range of Web-
based solutions, we address and resolve the integration & solutions needs of today's IT users
for both hardware and software. Our integrated quality information system helps us manage
all aspects of high quality software production in our organization. Internal quality
assessments are done twice a year with the intention of identifying quality issues and areas of
improvement. The assessment focuses on customer feedback on product quality, our service
levels as well as the effectiveness of the quality system. We also get approval from KERALA
STATE RUTRONIX.
WEB APPLICATION DEVELOPMENT
Professional web site design is critical for success in the modern Internet Business
World. Offering an attractive, intuitive interface with a logical and easy to use navigation
layout will make the difference between a happy visitor (and potential client) and a frustrated
web surfer at your website. A successful site begins by carefully planning a rewarding user
experience.

Tech Drive 53
Bright Future expert creative services team delivers the following services:
 User Interface Design
 Site Layout Design
 Site Re-Design
 Site Flow And Navigation
 HTML Integration With Backend Technologies
 Logo Designing
 Computer Education(c,c++,java,c#,VB,.NET,SQL&mysql,PL/SQL,Oracle
DBA,Red Hat,DCA Microsoft Office…)
 HARDWARE & NETWORK ACADEMY(Windows Server,COMPTIA

A+,CCNA,CCNP,MCSA,MCSE,Ethical Hacking,Linux,Red Hat)
 ENGLISH LEARNING ACADEMY(Beginners,Intermediate&advanced

English learning,Spoken English,Bussiness Communication TOEFL & IELTS
Preparatory Course.)
CUSTOM APPLICATION DEVELOPMENT
E-business Applications develops custom applications that are built to meet specific
needs within your business. Our solutions are business focused to help improve your bottom
line by increasing productivity, increasing information and business process transparency and
improving business systems efficiency. Not only are our solutions business driven, but they
are focused on leading edge and industry standard technologies that will be able to evolve
with your needs over the long term.
CUSTOMER FOCUS
At Bright Future, we view our customer relationships as partnerships and are

committed to being accountable to ensure that the development, integration and
implementation of solutions are performed in a professional and timely manner. We unite this
accountability with our dedication to applying the most appropriate methodologies &
technologies, and we dispatch our 'best-of-breed' technology professionals to make it all
happen. The result is satisfied customers who consistently give us high marks for our
expansive offerings of precise engineering.

Tech Drive 54
Capabilities
Our combination of business knowledge and IT services provide our customers with
high-quality, end-to-end solutions. Our success is based on a clear vision of the business and
technology solutions for your needs and the ability to deliver results that help you establish
an edge over your competitors. We focus on establishing long-term partnerships with our
customers. We have the talent, knowledge and experience to understand your industries,
business processes and IT requirements, and to identify solutions that meet your specific
needs. Business process outsourcing to maximize business efficiency, all processes that are
not competitive edge to the enterprise should be outsourced. As an integrated tech and ops
company with global services delivery, Bright Future is driving this emerging business
model.
Through a combination of intelligent process management, proprietary outsourcing

management technology, and a dedicated, shared service or transaction-based model.
BUSINESS PROCESS OUTSOURCING: Here we operate the process on behalf of the

client on the client's process and technology. Business Services Provisioning (BSP): here we
take end-to-end responsibility for the process and run it on the gold-standard process and
technology, and provide the output in the required format to the clients on a pay-per-drink
basis. This enables clients to variables their costs, maximize efficiency and manage for spikes
in business.
CONTACT DETAILS
Bright Future Education

ll nd Floor,Matha Business Square
OppPvt Stand,Thodupuzha
Kerala, India.
Phone Contact
+91 9495259988/7025492988
Email Contact
sinsejose1@gmail.com

Tech Drive 55
Website:
www.AptechThodupuzha.com
www.TallyLearnings.com
www.BrightFuture-Education.com
11.2. DOCUMENT GLOSSARY, FIGURES, TABLES
Abbreviations
IDE -- Integrated Development Environment
SQL -- Structured Query Language
UI -- User Interface
PK -- Primary Key
FK -- Foreign Key
UML -- Unified Modelling Language
List of Figures
Fig7.1.1.use case diagram............................................................................................17

Fig 7.2.1.sequence diagram..........................................................................................19
Fig 8.1.1. class diagram................................................................................................23
Fig 8.2.1.Activity diagram...........................................................................................26
Fig 8.3.1.user interface design.....................................................................................28
Fig 9.1.1.Test cases......................................................................................................45

Tech Drive 56
List of Tables
Table 8.7.1 tbl_registration..........................................................................................40

Table 8.7.2 tbl_product................................................................................................40
Table 8.7.3 tbl_service.................................................................................................41
Table 8.7.4 tbl_order....................................................................................................42
Table 8.7.5 tbl_carthead...............................................................................................43
Table 8.7.6 tbl_cartsub.................................................................................................43
Table 8.7.7 tbl_enquiry................................................................................................44
Table 8.7.8 notification................................................................................................44
11.3. References
1. Database Management Systems – Raghu Ramakrishnan and Johannes Gehrke, Third

Edition, McGraw Hill, 2003
2. Applying UML and Patterns, an Introduction to Object Oriented Analysis –Larman Craig,
Third Edition, Pearson Education,2004
3. Software Engineering- K.K. Aggarwal, revised, New Age International, 2005
4. Mysql: The Complete Reference- Vikram Vaswani, revised, McGraw-Hill/Osborne, 2004
http://download.cnet.com>WampServer
http://www.w3schools.com>sql
www.w3schools.com/PHP /Tutorial points 20-08-2018
11.4. SAMPLE PROJECT CODE
index
<?php
session_start();
include('connection.php');
include "alert.php";

Tech Drive 57
if(isset($_SESSION['cid']))
$cid=$_SESSION['cid'];
else
$cid="";
$sql="select * from order_tbl where cust_id='$cid' and status='Item

Delivered'";
$res=mysqli_query($con,$sql);
?>
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1.0">
<title>computer sales and service</title>
<link rel="stylesheet" href="css/service.css">
<script src="js/jquery-3.3.1.min.js"></script>
</head>
<body>
<div class="menubar">
<img src="images/backarrow.png" class="arrow"

onclick="window.locatin.href='index.php'"/>
<h5 class="phead">MY SERVICES</h5> </div>
<div style="width:100%; height:90px; "></div>
<div class="select1">

Tech Drive 58
<form action="service.php" method="post">
<select class="prodts" name="selpro">
<option >Select...</option>
<?php
while($row=mysqli_fetch_array($res))
echo '<option value="'.$row["product_id"].'">'.

$row["product_name"].'</option>';
?>
</select>
<input type="submit" class="sb1" value="SELECT" name="search">
</form>
</div>
<?php
if(isset($_POST['search']))
$pid=$_POST['selpro'];
$sql1="select * from order_tbl where cust_id='$cid' and product_id='$pid' and

status='Item Delivered' ";
$result1=mysqli_query($con,$sql1);
?>
<div class="productd">

Tech Drive 59
<h5 class="pcomp"> ENTER THE COMPLIANT : </h5>
<textarea class="com" placeholder=" Compliants Here...." name="comp"></textarea>
</div>
<div class="compl">
<?php
while($row=mysqli_fetch_array($result1))
$mrp=$row['mrp']*$row['qty'];
$offer=$mrp*$row['offer']/100;
$price=$mrp-$offer
?>
<div class="item">
<div class="itimg">
<img src="<?php echo "admin/".$row['img1']; ?>" class="itimg1">
</div>
<div class="itemdet">
<h5 class="name"><?php echo $row['product_name'] ;?></h5>
<h5 class="price">MRP <?php echo $price ;?>/-</h5><strike>MRP <?php

echo $mrp ;?>/-</strike>
<h5 style="float:left; color:green;font-size:18px;padding-top:10px;padding-

left:17px;font-weight:100;"><?php echo $row['offer'] ;?>% off</h5><br/>
<h5 style="float:left; color:red;font-size:18px;padding-top:10px;padding-

left:17px;font-weight:100;">Order Date : <?php echo $row['order_date'] ;?></h5><br/>
<input type="hidden" name="prdtid" value="<?php echo $row['product_id'];?

>"/>
<input type="hidden" name="prdtname" value="<?php echo

$row['product_name'];?>"/>
<input type="hidden" name="img1" value="<?php echo $row['img1']; ?>"/>
<h5 class="des">Description :</h5><br/>

Tech Drive 60
<?php
$qry="select * from product_tbl where product_id='$pid'";
$res2=mysqli_query($con,$qry);
while($row=mysqli_fetch_array($res2))
?>
<p class="highlight"><?php echo $row['pro_highlight1'] ;?><br>
<?php echo $row['pro_highlight2'] ;?><br>
<?php echo $row['pro_highlight3'] ;?><br>
</p>
<?php
?>
</div>
</div>
<?php
?>
</div>
<div class="sub">
<input type="submit" class="sb2" value="SUBMIT" name="rqst"/>
</div>
</form>
<?php
?>

Tech Drive 61
<?php
$sql3="select * from sevice_tbl where cust_id='$cid'";
$res3=mysqli_query($con,$sql3);
$count=mysqli_num_rows($res3);
if($count>0)
?>
<div class="hist">
<h5 class="hed">PREVIOUS DETAILS</h5>
<?php
$x=1;
while($row1=mysqli_fetch_array($res3))
?>
<div class="hdetails">
<div class="psubd">
<div class="pimage">
<img src="<?php echo "admin/".$row1['img1']; ?>" class="itimg1">
</div>
<h5 class="pname"><?php echo $row1['product_name'] ;?></h5>
</div>
<div class="compt1">
<h5 class="pname12">COMPLAINTS</h5>
<div class="cdet">
<p><?php echo $row1['complaints'] ;?></p>
</div>
<?php

Tech Drive 62
if($row1['s_status']=="Completed")
?>
<input type="submit" class="sb4" value="FEEDBACK"

onclick="show();" />
<?php
?>
<h5 class="stats">STATUS : <?php echo $row1['s_status'] ;?> </h5>
</div>
<div id="fdbck" id="<?php echo $x; ?>">
<h5 class="efk"> FEEDBACK </h5>
<h5 id="close" onclick="hide()">✖</h5>
<input type="hidden" name="feedback" value="<?php echo $row1['service_id'];?

>"/>
<textarea class="feedback" placeholder=" Feedback Here...."

name="feed"></textarea>
<input type="submit" class="sb3" value="SEND" name="send">
</form>
</div>
</div>
<script>
function show()
document.getElementById('fdbck').style.display="block";
window.scrollTo(0,document.body.scrollHeight+77);

Tech Drive 63
function hide()
document.getElementById('fdbck').style.display="none";
</script>
<?php
$x++;
?>
</div>
<?php
?>
</body>
</html>
<?php if(isset($_POST['rqst']))
$id=$_POST['prdtid'];
$name=$_POST['prdtname'];
$img=$_POST['img1'];
$complaint=$_POST['comp'];
date_default_timezone_set('Asia/Kolkata');
$date=date('d/m/Y');
$sql5="inserintosevice_tbl
(cust_id,product_id,product_name,complaints,s_status,s_date,img1)
values('$cid','$id','$name','$complaint','Requested','$date','$img')";
if(mysqli_query($con,$sql5))

Tech Drive 64
alt("Service Requested.","service.php");
if(isset($_POST['send']))
$sid=$_POST['feedback'];
$feed=$_POST['feed'];
$sql6="update sevice_tbl set s_feedback='$feed' where service_id='$sid'";
if(mysqli_query($con,$sql6))
alt("Feedback Sended.","service.php");
?>
Cart
<?php session_start();
include('connection.php');
if(isset($_SESSION['cid']))
$cid=$_SESSION['cid'];
else

Tech Drive 65
$cid="";
$sql="select c.cartsub_id,c.qty,p.* from cart_sub_tbl c inner join cart_head_tbl h on

c.carthead_id=h.carthead_id inner join product_tbl p on c.product_id=p.product_id where
h.cust_id='$cid'";
$res=mysqli_query($con,$sql);?>
<!DOCTYPE HTML>
<html lang="en"><head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1.0">
<title>computer sales and service</title>
<link rel="stylesheet" href="css/cart.css">
<script src="js/jquery-3.3.1.min.js"></script>
<script>
$(document).ready(function(){
});
</script>
</head>
<body>
<div class="menubar">
<imgsrc="images/backarrow.png"class="arrow"
onclick="window.location.href='index.php'"/>
<h5 class="phead">CART</h5>
</div>
<div style="width:100%; height:90px; ">
</div>
<form action="cart.php" method="post">
<div class="container">

Tech Drive 66
<?php
$total=0;
$ship=0;
$x=1;
$count=mysqli_num_rows($res);
while($row=mysqli_fetch_array($res))
?>
<div class="item">
<input type="hidden" value="<?php echo $row['product_id'];?>" name="pid[]"/>
<div class="itimg"><img src="<?php echo 'admin/'.$row['img1'];?>"

class="itimg1"/></div>
<div class="qty">
<select class="qt" name="qty[]" id="<?php echo $x;?>"

onchange="window.location.href='cart.php?crt=<?php echo $row['cartsub_id'];?
>&qty='+this.value">
<option value="1">QTY : 1</option>
</select>
<script>
$('select[id="<?php echo $x;?>"] option[value="<?php echo $row['qty'];?

>"]').attr('selected',true);
</script>
</div>
<h5 class="name"><?php echo $row['product_name'] ;?></h5>

Tech Drive 67
<h5 class="price">Price : <?php echo $row['price']*$row['qty'] ;?>/-

</h5><strike>MRP <?php echo $row['pro_mrp'] *$row['qty'];?>/-</strike>

left:5px;font-weight:100;"><?php echo $row['pro_offer'] ;?> % off</h5>

left:23px;font-weight:100;">Cash On Delivery Available</h5>
<h5 style="float:left;color:gray;font-size:15px;padding-top:7px;padding-
left:23px;font-weight:100;">Usually Delivered in 3-4 Days</h5>
<h5 class="addb" onclick="window.location.href='cart.php?cid=<?php echo

$row['cartsub_id'] ;?>&action=remove'">Remove</h5>
</div>
<?php
$ship+=200;
$x++;
$total+=($row['price']*$row['qty'] );
?>
</div>
<?php
if($cid!="")
if($count>0)
?>
<div class="pricedt">
<div class="priced">
<h5 class="prhead">Price Details</h5>

Tech Drive 68
<hr>
<h5 class="productprl">Product Price (<?php echo $count; ?>) :</h5>
<h5 class="productpr"><?php echo $total; ?>/-</h5>
<h5 class="deli">Delivery Charges :</h5>
<h5 class="delich"><?php echo $ship;?>/-</h5>
<hr class="hr2">
<h5 class="totalab">Total Amount :</h5>
<h5 class="totalp"><?php echo $total+$ship; ?>/-</h5>
</div>
<div class="payment">
<h5 class="prhead">Payment / Address</h5>
<hr>
<div class="pmsub">
<input type="radio" value="" name="group1" class="rdb" checked>
<h5 class="cod">Cash on Delivery</h5>
<input type="radio" value="" name="group1" class="rdb">
<h5 class="cp">Card Payment</h5>
<input type="radio" value="" name="group1" class="rdb">
<h5 class="nb">Net Banking</h5>
</div>
<?php
$sql3="select * from customer_tbl where cust_id='$cid'";
$res1=mysqli_query($con,$sql3);
while($row1=mysqli_fetch_array($res1))
?>
<div class="address">

Tech Drive 69
<h5 class="adh">Delivery Address</h5>
<hr class="hr4">
<p> <?php echo $row1['address'] ;?>,
pin: <?php echo $row1['pin'] ;?>.<br>
Mobile:<?php echo $row1['mobile'] ;?><br>
Email Id:<?php echo $row1['email'] ;?>
</p>
<h5 class="btchange" onclick="window.location.href='changedetails.php?

cid=<?php echo $cid; ?>'">Change / Add</h5>
</div>
<?php
?>
</div>
<input type="submit" name="plorder" class="plord" value="Place Order"/>
</div>
</form>
<?php
?> </body>
</html><?php
if(isset($_GET['action']))
if($_GET['action']=="remove")
$cd=$_GET['cid'];

Tech Drive 70
$sql="delete from cart_sub_tbl where cartsub_id='$cd'";
if(mysqli_query($con,$sql))
echo "<script> alert('Item Is Removed.');

window.location.href='cart.php'</script>";
if(isset($_GET["crt"]))
$id=$_GET["crt"];
$qty=$_GET["qty"];
$sql="update cart_sub_tbl set qty='$qty' where cartsub_id='$id'";
if(mysqli_query($con,$sql))
echo"<script> window.location.href='cart.php' </script>";
}?>
<?php
if(isset($_POST['plorder']))
$pid=$_POST['pid'];
$qty=$_POST['qty'];
date_default_timezone_set('Asia/Kolkata');
$odate=date('d/m/Y');
foreach($pid as $key => $value)
$qt=$qty[$key];

Tech Drive 71
$qry="select pro_mrp,pro_offer,product_name,img1 from product_tbl where

product_id='$value'";
$res=mysqli_query($con,$qry
while($row=mysqli_fetch_array ($res))
$mrp=$row['pro_mrp'];
$offer=$row['pro_offer'];
$name=$row['product_name'];
$img=$row['img1'];
$sql="insertintoorder_tbl
(cust_id,product_id,product_name,mrp,offer,status,img1,qty,order_date)
values('$cid','$value','$name','$mrp','$offer','Order Placed','$img','$qt','$odate')";
if(mysqli_query($con,$sql)) {
$sql="delete cr.* from cart_sub_tbl cr inner join cart_head_tbl ch on

cr.carthead_id=ch.carthead_id where ch.cust_id='$cid' ";
mysqli_query($con,$sql);
} echo "<script> alert('Order Placed'); window.location.href='order.php'</script>";
?>

Executive Summary/Abstract: Tech Drive

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Executive Summary/Abstract: Tech Drive

Caricato da

Copyright:

Formati disponibili

Tech Drive 1

Online shopping is a form of electronic commerce which, allows consumers to directly

Department of Computer Science Nirmala College,Muvattupuzha

2.1. EXISTING SYSTEM

 It provides online shopping facility.

Department of Computer Science Nirmala College,Muvattupuzha

3.1. OBJECTIVE OF THE PROJECT

A person, group, organization that has interest or concern in an organization is called

3.3. SCOPE OF THE PROJECT

Department of Computer Science Nirmala College,Muvattupuzha

3.4. FEASIBILITY ANALYSIS

3.4.1 Technical feasibility

3.4.2. Operational feasibility

• User friendly and attractive website.

• Can buy and service products easily through online.

• Offer notifications help to buy products at low rate.

3.4.3. Schedule feasibility

05/06/2018 to 13/06/2018 : Study the existing system

Department of Computer Science Nirmala College,Muvattupuzha

07/12/2018 : Submission of document .

So it satisfies schedule feasibility.

3.4.4. Economic feasibility- Cost - Benefit analysis

• Cost effective and saves time

• Can work on any desktops or laptops.

Department of Computer Science Nirmala College,Muvattupuzha

4.1 DEVELOPMENT ENVIRONMENT

The project is planned to develop on the following environment:

 Project should complete, test and implement within 6 months.

 The software works only when there is proper internet connection.

 Customers need a bank account.

4.5. PROCESS MODEL

Unified process (UP) is a popular iterative and incremental software development

Department of Computer Science Nirmala College,Muvattupuzha

General idea is to develop a system through iteration (repeated cycles) and

4.6. TEST STRATEGY

 Approach for testing

Department of Computer Science Nirmala College,Muvattupuzha

 Testing on developers site

Department of Computer Science Nirmala College,Muvattupuzha

Schedule for this project is:

System Analysis : 14/06/2018 to 20/06/2018

Requirements Gathering : 21/06/2018 to 30/06/2018

Analyse the modules of the project : 2/07/2018 to 5/07/2018

Designing (Table) : 6/07/2018 to 13/07/2018

Development of web site : 14/07/2018 to 14/08/2018

Documentation : 9/10/2018 to 06/12/2018

Final Product Implementation : 12/12/2018

Document Submission : 10/12/2018

Department of Computer Science Nirmala College,Muvattupuzha

6.1. USER CHARACTERISTICS

The main Users are:

6.2. FUNCTIONAL REQUIREMENTS

Features of the web application are:

• Web application is user friendly and easy to operate

• Customers receive notifications about offers.

Department of Computer Science Nirmala College,Muvattupuzha

• Customers are the main users.

• Customers can give feedback.

The function of each module is as follows

The features that are available to the Administrator are:

• Can add/edit/view or remove products in to the site.

• Can add/remove offers to the products.

• Products stock management.