PROJECT REPORT

On

PROJECT_NAME_HERE
Submitted in partial fulfillment of their requirements for the
award of the diploma in

DIPLOMA IN COMPUTER SCIENCE & ENGINEERING

Under the supervision of

Er. Himanshu Kashyap
(Sr. Project Manager-IT)

DigiCoders Technologies Pvt. Ltd.

Lucknow (UP)

Submitted By
Student_Name_Here

Submitted to
College_Name_Here

1
 TABLE OF CONTENT

1. Introduction…………………………………………………………………………..…........7-12
1.1 Overview of Organization

1.2 Objectives
1.3 Existing System Description
1.4 Proposed System
1.5 Tools Used
2. System Analysis…………………………………………………………………...............13-24
2.1 Identification of need
2.2 SDLC Phases
2.2.1 Feasibility Study
2.2.2 Report Approval
2.2.3 System Analysis
2.2.4 System Design
2.2.5 Coding
2.2.6 Testing
2.2.7 Implementation
2.2.8 Maintenance
2.3 Process Description
2.4 Project Model Used
2.5 Data Flow Diagram
3. Software Requirement Specification………….
…………………………………………………………….………..25-26
3.1 Hardware Requirement
3.2 Software Requirement
3.3 Support Maintenance
4. System Design Approach…………………………………………………………………27-28
4.1 Top-Down Designing
4.2 Bottom–Up Designing
4.3 Following Approach

5. Low Level Design………………………………………………………………………………………29

5.1 Description of Classes and Methods

6. Data Modeling………………………………………………………………………..25-27
6.1 List of Tables

2
 6.2 Structure of Tables
7. Testing…………………………………………………………………………… 28-31
8. Input-Output Forms………………………………………………………………………….…32-54
8.1 Modularization Details
8.2 User Screenshots
8.3 Admin Screenshots
9. Future Scope……………………………………………………………………………….…55
10.Conclusion……………………………………………..……………………………..60

PROBLEM DEFINITION

In this section we shall discuss the limitation and drawback of the existing system that
forced us to take up this project. Really that work was very typical to manage the daily
errors free records and adding or removing any node from server. This problem produces a
need to change the existing system. Some of these shortcomings are being discussed below:

● Low Functionality

With the existing system, the biggest problem was the low functionality. The
problem faced hampered the work. For small task like adding any new node to
server or deleting a node or keeping daily record we have to appoint minimum two
or three employee.

● Erroneous Input and Output

In the existing system, humans performed all the tasks. As in the human tendency,
error is also a possibility. Therefore, the inputs entered by the person who is
working in the Company, in the registers may not be absolutely foolproof and may

3
 be erroneous. As a result of wrong input, the output reports etc. Will also be wrong
which would in turn affect the performance.

● Portability Problem

System that existed previously was manual. As a result, the system was less
portable. One has to carry the loads of many registers to take the data from one
place to another. A big problem was that the system was less flexible and if we
wanted to calculate yearly or monthly maintenance report or efficiency report, then
it was a big headache

● Security-

Security concerns were also one of the motives of the Company for the need of
software. In the registers, the data is not secure as anybody can tamper with the
data written in the registers. While in this software, just a password makes it
absolutely secure from the reach of unauthorized persons.

● Data Redundancy

In the case of manual system, the registers are maintained in which, a lot of data is
written.

● Processing Speed

In manual system maintaining a register and performing the necessary calculation

has proved to be a troublesome job, which takes a lot of time and may affect the
performance of the Company. But with this software we can have all the tasks
performed in a fraction of second by a single click thus making the troublesome job
much easier.

● Manual Errors

When a number of tough tasks are prepared by the humans like preparation of
reports, performing long calculation then some human error are obvious due to a
number of factors like mental strain, tiredness etc. But as we all know that computer
never get tired irrespective of the amount of work it has to do. So this software can
nullify the probability of manual error that improve the performance.

⮚ Complexity in Work
4
 In manual system whenever a record is to be updated or to be deleted a lot of
cutting and overwriting needs to be done on the registers that are concerned that
are deleted or updated record, which makes the work very complex.

PROPOSED SYSTEM

The development of this new system contains the following activities, which try to develop
on-line application by keeping the entire process in the view of database integration
approach.
● Secure registration and profile management facilities for Customers.

● Browsing through the e-Mall to see the items that are there in each category of
products like Apparel, Kitchen accessories, Bath accessories, Food items etc.

● Creating a Shopping cart so that customer can Shoppe ‘n’ no. of items and checkout
finally with the entire shopping cart

● Customers should be able to mail the Shop about the items they would like to see in
the Shop

● Secured mechanism for checking out from the Shop (Credit card verification
mechanism)

● Updates to customers about the Recent Items in the Shop.

● Uploading ‘Most Purchased’ Items in each category of products in the Shop like
Apparel, Kitchen accessories, Bath accessories, Food items etc.

SYSTEM ANALYSIS

Identification of needs

Social and economic factor: a wave of social and economic changes often follows in the
wake of the new technology. New opportunities may arise to improve on a production
process or to do something that was not previously possible. Changes in the ways
individuals are organized into groups may then be necessary, and the new groups may
complete for economic resources with established units.

5
Technological factor: people have never before in a time when the scope of scientific
inquiry was so broad, so when the speed of applying the new technology accounts for many
changes in the organization.
High level decisions and operating processes: in response to technological, socio-economic
factors, top level managers may decide to recognize operations and introduce new
products. To deal with these needs, people commonly seek new modified information to
support the decision. When that happens, then they obtain turn to a computer system for
help the information users and data processing specialist then work together to complete a
series of steps in a system study to produce output results to satisfy information needs.

Feasibility Study

Feasibility study is these Cond step of the system development life cycle .Things are always
easy at the beginning in any software process. In fact nothing is infeasible with unlimited
time and resources. But it is not the fact. So, practically we have to do in limited resources
in a restricted time margin. So for the system to be feasible, following points we have to
consider.
The feasibility study is conducted to check whether the candidate system is feasible. The
system which is selected to be the best against the criteria is thereafter designed and
developed. The feasibility study takes in to consideration, the risks involved in the project
development beforehand. Therefore in this phase we have to do feasibility study which is
the test of the website according to its workability, impact on the organization, ability to
meet user need and effective use of resources. We do the feasibility study for website to
analyze the risks, costs and benefits relating to economics, technology and user
organization. There are several types of feasibility depending on the aspect they cover.
Import of these includes:

1. Problem Statement:

To develop a study material which is a web based application which handles inquiry
regarding the different product available on the website .This enhances the working
ability and reduces the required resources and manpower; also give new and
refreshing look to the interface.

6
 2. Technical Feasibility:
● The current system is built on user interface environment using MYSQL and PHP which
will provide a good and enhanced working environment.
● Provides a user friendly environment.
● Windows OS and PHP software are easily available and easy to Interact.

3. Behavioral Feasibility:
During the onsite review of the current system the client showed a positive approach
towards the changeover. Any further change in the current system will be accepted
smoothly, as this new developing system is based on GUI interface.

4. Alternate Solution:
Right now we are implementing this system using MY-SQL as backend. It can be structured.

5. Risk Analysis:

Risk identification:
Technical risk: - In this project, the only risk can arise if some change occurs in the
technical requirements of the management. As per the requirement, we have taken
PHP as technology for system development.

Software Tools:-

Technology used in:

● Server Side : Server Side Language
● Client Side : JavaScript
● Layout : HTML, CSS
● Database : MYSQL

Platform:-

● Server : WAMP
● Database : MYSQL

Software Requirement:-

● Operating system : Windows XP/7/8/8.1/10

7
 ● Language used : JSP, Java
● Database : MYSQL
● Browser : Google Chrome
● For Documentation : Microsoft Word 2007/10/13

Hardware Tools:-

● System : Dell compatible PC’s

● Processor : Core 3 Duo Processor

● RAM : 4 GB RAM

● HDD : 256 GB

● Output device: : Monitor, Laser Printer

● Input device : Keyboard, Mouse

● LAN connection (Wired)

Request Approval:-
Request approval is the third phase of system development lifecycle. Request approval is
the phase in which all the requirements which would be provide in the system are stated.
The request approval is a sort of agreement between the client and the company which is
building this software. Both the parties should be mutually agreed on the stated
requirements.

System Analysis:-
System analysis is the phase following the phase of the request approval .In this phase we
tend to analyze the overall system which we have to build .System analysis is the crucial
part in SDLC.

System Design:-
System design means the designing of the system. The System can be done in either of the
following two ways:-

● Logical System Design

● Physical System Design
8
 Coding:-

Coding is the phase in which a developer code suing any programming

languages .Coding constitutes only20 %of the whole project and which is easier to
write. The coding work is also done in the teams; development of the system is usually
done under the modular programming style, which can be either top-down approach
or bottom-up approach.

Testing:-

Testing is the phase in which the system that has been developed is tested. Testing
comprises of the 60%ofthe overall development of the system. Testing of the system is
important because testing aims to uncover the different errors in the system. There are
various different testing techniques that can be used forth testing of the system.

Implementation:-

Implementation process involved the installation of software on user’s side.

Process actually depends on type of a system & various. Opting for suitable conversion
approach is a step implementation. The conversion processes are as follows:-

● Parallel Conversion
● Direct Conversion Approach
● Pilot Conversion Approach
● Phase In Conversion Approach

Maintenance: -
Merelydevelopingthesystemisnotimportantbutalsomaintenanceisimportant.Thecompanyth
at has builtthesystemprovidesforsometimefreeofcostmaintenancetotheclient and after that
period it is usually paid service.

9
Process Description:-

Gantt charts mainly used to allocate resources to activities. The resources allocated to
activities include staff, hardware, and software. Gantt charts (named after its developer
Henry Gantt) are useful for resource planning. A Gantt chart is special type of bar chart
where each bar represents an activity. The bars are drawn along a timeline. The length of
each bar is proportional to the duration of the time planned for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt
chart, by coloring each milestone when completed. The project will start in the month of
January and end after 4 months at the beginning of April.

10
PROJECT MODEL USED
Iterative Enhancement Model:-

⮚ This model has the same phases as the waterfall model, but with fewer restrictions.
Generally the phases occur in the same order as in the waterfall model, but they may be
conducted in several cycles.
⮚ Useable product is released at the end of the each cycle, with each release providing
additional functionality. Customers and developers specify as many requirements as
possible and prepare a SRS document. Developers and customers then prioritize these
requirements. Developers implement the specified requirements in one or more cycles
of design, implementation and test based on the defined priorities.

The procedure itself consists of the initialization step, the iteration step, and the
Project Control List. The initialization step creates a base version of the system. The
goal for this initial implementation is to create a product to which the user can react. It
should offer a sampling of the key aspects of the problem and provide a solution that is
simple enough to understand and implement easily. To guide the iteration process, a
project control list is created that contains a record of all tasks that need to be
11
 performed. It includes such items as new features to be implemented and areas of
redesign of the existing solution. The control list is constantly being revised as a result
of the analysis phase.
The iteration involves the redesign and implementation of iteration is to be simple,
straightforward, and modular, supporting redesign at that stage or as a task added to
the project control list. The level of design detail is not dictated by the iterative
approach. In a light-weight iterative project the code may represent the major source
of documentation of the system; however, in a critical iterative project a
formal Software Design Document may be used. The analysis of iteration is based upon
user feedback, and the program analysis facilities available.

PHASES:-

Incremental development slices the system functionality into increments (portions).

In each increment, a slice of functionality is delivered through cross-discipline work, from
the requirements to the deployment. The unified process groups increments/iterations
into phases: inception, elaboration, construction, and transition.
● Inception identifies project scope, requirements (functional and non-functional) and
risks at a high level but in enough detail that work can be estimated.
● Elaboration delivers a working architecture that mitigates the top risks and fulfills the
non-functional requirements.
● Construction incrementally fills-in the architecture with production-ready code
produced from analysis, design, implementation, and testing of the functional
requirements.
● Transition delivers the system into the production operating environment.

12
Data Flow Diagram

Introduction:-
DFD is an acronym for the word Data Flow Diagram. DFD is pictorial representation of the
system. DFD is a graphical representation of the―flow ‖of data through the information
system. DFD are also used for the visualization of data processing (structured design).
ADFD provides no information about the timings of the process, or about when the r
process will operate in parallel or sequence. DFD is an important technique for modeling
system’s high-level detail by showing how input data is transformed to output results
through has sequence off unction transformations. DFD reveal relationships among
between the various components in a program or system. The strength of DFD lies in the
fact that using few seem bolster are able to express program design in an easier manner.
ADFD can be used store present the following:-

External Entity sending and receiving data.

Process that change the data.
Flow of data within the system.
Data Storage locations.

Uses of DFD:-

The main uses of data flow diagrams are as follows:-

DFD is amen thud of choice for representation of showing of information through a system
13
because of the following reasons:-
● DFDs are easier to understand by technical and non-technical audiences.

● DFDs can provide a high level system overview, complete with boundaries and
connections to other system.
● DFDs can provide a detailed representation of system components.

SOFTWAREREQUIREMENT SPECIFICATION

A requirements specification for a software system is a complete description of the

behavior of a system to be developed and it includes a set of use cases that describe all the
interactions the users will have with the software. In addition to use cases, the SRS also
contains non-functional requirements.

Non-functional requirements are requirements which impose constraints on the design or

implementation (such as performance engineering requirements, quality standards, or
design constraints).Requirements are a sub-field of software engineering that deals with
the elicitation, analysis, specification, and validation of requirements for software.

The software requirement specification document enlists all necessary requirements for
project development. To derive the requirements we need to have clear and thorough
understanding of the products to be developed. This is prepared after detailed
communications with project team and the customer.

SUPPORTANDMAINTENANCE:-

One year free support for rectifying system bugs including front end and beck end will be
provided. During warranty period Software Engineers will be responsible for removing
bugs and improving it. After one year support can be extended @ 20% of the total product
deployment cost.

SYSTEM DESIGN APPROACH

Top – Down designing:

14
The top - down designing approach started with major components of the system. It is a
stepwise refinement which starts from an abstract design, in each steps the design is
refined two or more concrete levels until we reach a level where no – more refinement is
possible or not needed.

Bot
tom – Up designing:

In bottom – up designing the most basic and primitive components are designed first, and
we proceed to higher level components. We work with layers of abstractions and
abstraction are implemented until the stage is reached where the operations supported by
the layer is complete.

Approach we are following:

In this project we are following Mixed Approach i.e. A combination of top – down and
bottom – up. We are developing some of the components using top – down designing

15
approach (e.g. the Web Pages) and the some components in bottom – up designing
approach (e.g. the middle tier classes).

Low Level Design

Description: Low Level Design creation is one of the most important activities in the
development of any software product. The low level design document gives the design of
the actual software application. Low level design document is based on High Level Design
document. It defines internal logic of every sub module. A good low level design document
will make the application very easy to develop by the developer. An effective design
document results in very low efforts in developing a Software product.

Each project's low level design document should provide a complete and
detailed specification of the design for the software that will be developed in the project,
including the classes, member and non-member functions, and associations between
classes that are involved.

The low level design document should contain a listing of the declarations of all the classes,
non-member-functions, and class member functions that will be defined during the
subsequent implementation stage, along with the associations between those classes and
any other details of those classes (such as member variables) that are firmly determined by
the low level design stage. The low level design document should also describe the classes,
function signatures, associations, and any other appropriate details, which will be involved
in testing and evaluating the project according to the evaluation plan defined in the
project's requirements document.

TESTING
Testing is the integral part of any System Development Life Cycle insufficient and
interested application tends to crash and result in loss of economic and manpower
investment besides user’s dissatisfaction and downfall of reputation.

“Software Testing can be looked upon as one among much process, an organization
performs, and that provides the last opportunity to correct any flaws in the developed
system. Software Testing includes selecting test data that have more probability of giving

16
errors.” The first step in System testing is to develop the plan that all aspect of
system .Complements, Correctness, Reliability and Maintainability.

Software is to be tested for the best quality assurance, an assurance that system meets the
specification and requirement for its intended use and performance.
System Testing is the most useful practical process of executing the program with the
implicit intention of finding errors that makes the program fail.

Types of Testing:

Black Box (Functional) Testing:

Testing against specification of system or component. Study it by examining its inputs and
related outputs. Key is to devise inputs that have a higher likelihood of causing outputs that
reveal the presence of defects. Use experience and knowledge of domain to identify such
test cases. Failing this a systematic approach may be necessary. Equivalence partitioning is
where the input to a program falls into a number of classes, e.g. positive numbers vs.
negative numbers. Programs normally behave the same way for each member of a class.
Partitions exist for both input and output. Partitions may be discrete or overlap. Invalid
data (i.e. outside the normal partitions) is one or more partitions that should be tested.
Internal System design is not considered in this type of testing. Tests are based on
requirements and functionality.
This type of test case design method focuses on the functional requirements of the
software, ignoring the control structure of the program. Black box testing attempts to find
errors in the following categories:

⮚ Incorrect or missing functions.

⮚ Interface errors.

⮚ Errors in data structures or external database access.

⮚ Performance errors.

⮚ Initialization and termination errors.

17
White Box (Structural) Testing:

Testing based on knowledge of structure of component (e.g. by looking at source code).

Advantage is that structure of code can be used to find out how many test case need to be
performed. Knowledge of the algorithm (examination of the code) can be used to identify
the equivalence partitions. Path testing is where the tester aims to exercise every
independent execution path through the component. All conditional statements tested for
both true and false cases. If a unit has n control statements, there will be up to 2n possible
paths through it. This demonstrates that it is much easier to test small program units than
large ones. Flow graphs are a pictorial representation of the paths of control through a
program (ignoring assignments, procedure calls and I/O statements). Use flow graph to
design test cases that execute each path. Static tools may be used to make this easier in
programs that have a complex branching structure. Tools support. Dynamic program
analyzers instrument a program with additional code. Typically this will count how many
times each statement is executed. At end print out report showing which statements have
and have not been executed. Problems with flow graph derived testing:
❖ Data complexity could not take into account.
❖ We cannot test all paths in combination.
❖ In really only possible at unit and module testing stages because beyond that
complexity is too high.
This testing is based on knowledge of the internal logic of an application’s code. Also
known as a Glass Box Testing .Internal software and code working should be known for
this type of testing. Tests are based on coverage of code statements, branches, paths,
conditions.

Unit Testing:
Unit testing concentrates on each unit of the software as implemented in the code. This is
done to check syntax and logical errors in programs. At this stage, the test focuses on each
module individually, assuring that it functions properly as a unit. In our case, we used
extensive white-box testing at the unit testing stage.
A developer and his team typically do the unit testing do the unit testing is done in parallel
with coding; it includes testing each function and procedure.
Incremental Integration Testing:

18
 Bottom up approach for testing i.e. continuous testing of an application as new
functionality is added; Application functionality and modules should be independent
enough to test separately done by programmers or by testers.
Integration Testing:
Testing of integration modules to verify combined functionality after integration .Modules
are typically code modules, individual applications, client and server and distributed
systems.
Functional Testing:
This type of testing ignores the internal parts and focus on the output is as per
requirement or not .Black box type testing geared to functionality requirements of an
application.
System Testing:
Entire system is tested as per the requirements. Black box type test that is based on overall
requirement specifications covers all combined parts of a system.
End-to-End Testing:
Similar to system testing ,involves testing of a complete application environment in a
situation that mimics real-world use, such as interacting with a database ,using network
communications, or interacting with hardware, applications, or system if appropriate.
Regression Testing:
Testing the application as a whole for the modification in any module or functionality.
Difficult to cover all the system in regression testing so typically automation tools are used
for these testing types.

Acceptance Testing:
Normally this type of testing is done to verify if system meets the customer specified
requirements. User or customers do this testing to determine whether to accept
application.

Performance Testing:
Term often used interchangeably with “stress” and “load” testing, To check whether system
meets performance requirements, Used different performance and load tools to do this.

Alpha Testing:

19
In house virtual user environment can be created for this type of testing. Testing is done at
the end of development .Still minor design changes may be made as a result of such testing.
Beta Testing:
Testing typically done by end-users or others. This is final testing before releasing
application for commercial purpose.

20
 -: Project Screenshots :-

Login Page:

Dashboard:

21
 -: CODING :-
Login Page :-
<%--
Document : login
Created on : 16 Sep, 2022, 8:36:48 PM
Author : ravis
--%>

<%@page contentType="text/html" pageEncoding="UTF-8"%>

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>CRM</title>
<script src="https://kit.fontawesome.com/29d06a1337.js" crossorigin="anonymous"></script>
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.0.0/dist/css/bootstrap.min.css"
integrity="sha384-
Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm"
crossorigin="anonymous">
<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js"
integrity="sha384-KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/
GpGFF93hXpG5KkN"
crossorigin="anonymous"></script>
<script src="https://cdn.jsdelivr.net/npm/popper.js@1.12.9/dist/umd/popper.min.js"

integrity="sha384-ApNbgh9B+Y1QKtv3Rn7W3mgPxhU9K/ScQsAP7hUibX39j7fakFPskvXus
vfa0b4Q"
crossorigin="anonymous"></script>
<script src="https://cdn.jsdelivr.net/npm/bootstrap@4.0.0/dist/js/bootstrap.min.js"
22
integrity="sha384-JZR6Spejh4U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76P
VCmYl"
crossorigin="anonymous"></script>
<style>
body,
html {
margin: 0;
padding: 0;
height: 100%;
background: #d4e6ec !important;
}

.user_card {
height: 400px;
width: 350px;
margin-top: auto;
margin-bottom: auto;
background: #f39c12;
position: relative;
display: flex;
justify-content: center;
flex-direction: column;
padding: 10px;
box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);
-webkit-box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);
-moz-box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);
border-radius: 5px;

.brand_logo_container {
position: absolute;
height: 170px;

23
 width: 170px;
top: -75px;
border-radius: 50%;
background: #d4e6ec;
padding: 10px;
text-align: center;
}

.brand_logo {
height: 150px;
width: 150px;
border-radius: 50%;
/* border: 2px solid white; */
}

.form_container {
margin-top: 65px;
}

.login_btn {
width: 100%;
background: #c0392b !important;
color: white !important;
}

.login_btn:focus {
box-shadow: none !important;
outline: 0px !important;
}

.login_container {
padding: 0 2rem;
}

24
 .input-group-text {
background: #c0392b !important;
color: white !important;
border: 0 !important;
border-radius: 0.25rem 0 0 0.25rem !important;
}

.input_user,
.input_pass:focus {
box-shadow: none !important;
outline: 0px !important;
}

.custom-checkbox .custom-control-input:checked~.custom-control-label::before {
background-color: #c0392b !important;
}
</style>
</head>
<body>
<div class="container h-100">
<div class="d-flex justify-content-center h-100">
<div class="user_card">
<div class="d-flex justify-content-center">
<div class="brand_logo_container">
<img src="image/rslogo.png" class="brand_logo" alt="Logo">
</div>
</div>
<div class="d-flex justify-content-center form_container">
<form>
<div class="input-group mb-3">
<div class="input-group-append">
<span class="input-group-text"><i class="fa fa-user"></i></span>
</div>

25
 <input type="text" name="" class="form-control input_user"
placeholder="UserName">
</div>
<div class="input-group mb-2">
<div class="input-group-append">
<span class="input-group-text"><i class="fas fa-key"></i></span>
</div>
<input type="password" name="" class="form-control input_pass"
placeholder="Password">
</div>
<div class="d-flex justify-content-center mt-3 login_container">
<button type="button" name="button" class="btn login_btn">Login</button>
</div>
</form>
</div>
</div>
</div>
</div>
</body>
</html>

26
Dashboard :-
<%--
Document : index
Created on : 16 Sep, 2022, 8:35:20 PM
Author : ravis
--%>

<%@page contentType="text/html" pageEncoding="UTF-8"%>

<!DOCTYPE html>
<html lang="en">
<head>

<title>Admin</title>

<%@include file="headerlink.jsp" %>

</head>
<body class="sb-nav-fixed">

<%@include file="topbar.jsp" %>

<div id="layoutSidenav">

<%@include file="sidebar.jsp" %>

<div id="layoutSidenav_content">
<main>
<div class="container-fluid px-4">
<div class="row">
<div class="col-sm-10">
<h1 class="mt-4">CRM</h1>
</div>
<div class="col-sm-2" style="margin-top:30px ;">
</div>
27
 <div class="row">
<div class="col-xl-3 col-md-6">
<div class="card bg-warning text-white mb-4">
<div class="card-body">Manage Lead</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="manageleads.jsp">View
Details</a>
<div class="small text-white"><i class="fa-sharp fa-solid
fa-list"></i></div>
</div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-success text-white mb-4">
<div class="card-body">Manage Follow Up's</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="managefollowups.jsp">View Details</a>
<div class="small text-white"><i class="fas fa-chart-area"></i></div>
</div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-dark text-white mb-4">
<div class="card-body">Manage Reminder</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="managereminder.jsp">View Details</a>
<div class="small text-white"><i class="fa-solid
fa-note-sticky"></i></div>

28
 </div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-danger text-white mb-4">
<div class="card-body">Manage Bills</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="managebills.jsp">View Details</a>
<div class="small text-white"><i class="fa-solid
fa-money-bill-1"></i></div>
</div>
</div>
</div>
</div>
<div class="row">
<div class="col-xl-3 col-md-6">
<div class="card bg-info text-white mb-4">
<div class="card-body">Manage Invoice</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="manageinvoice.jsp">View Details</a>
<div class="small text-white"><i class="fa-solid
fa-bars-progress"></i></div>
</div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-secondary text-white mb-4">
<div class="card-body">Manage Complaint</div>
<div class="card-footer d-flex align-items-center justify-content-
between">

29
 <a class="small text-white stretched-link"
href="managecomplaint.jsp">View Details</a>
<div class="small text-white"><i class="fa-solid fa-book"></i></div>
</div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-primary text-white mb-4">
<div class="card-body">Manage Coustomers</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link"
href="managecoustomer.jsp">View Details</a>
<div class="small text-white"><i class="fa-brands
fa-intercom"></i></div>
</div>
</div>
</div>
<div class="col-xl-3 col-md-6">
<div class="card bg-success text-white mb-4">
<div class="card-body">Complaints Tracking</div>
<div class="card-footer d-flex align-items-center justify-content-
between">
<a class="small text-white stretched-link" href="complaints.jsp">View
Details</a>
<div class="small text-white"><i class="fa fa-chart-simple"></i></div>
</div>
</div>
</div>
</div>
</div>
</div>
</main>
<%@include file="footer.jsp" %>

30
 </div>
</div>

<%@include file="footerlink.jsp" %>

</body>
</html>

31
FUTURE SCOPE
Improvements in design can be made using:
❖ Flash
❖ Photoshop
❖ New features can be added, like:
❖ Improved validation
❖ Provision of discounts and offers
❖ Generation of reports
❖ Provision of print-out(s) to buyer
❖ Refund of the money if the order is cancelled within a specific time period
❖ Larger collection of products

CONCLUSION

The program achieved the main requirement which was to develop a website meant for
Online Chatting. Given the amount of time on hand, and given the basic knowledge of the
front end & back end used, the site satisfies most of the basic requirements that it was
supposed and planned to fulfill, like, providing facilities for authentication, registration,
searching for products, using a shopping cart, placing orders, cancellation of orders,
calculation of total payable amount, providing options for means of payment, addition of
new products to the site, managing the delivery of products, a very basic view of account
details, and extraction of  information from the database using queries, where the database
is created in MYSQL & is connected to the design of site using Data Source, and the web site
has been designed using PHP with all the coding done in WAMP.
 
During the development of the project, not only did we learn the basic concept behind
Online Chatting, but we also learnt many basic features and concepts of PHP&MYSQL and
how the PHP technology can enable one to develop web sites and applications with very
little hassle. The development period did give me some confidence to put together some
sites in my spare time!
 
The entire project was like a challenge to me. The concept itself was interesting, and it was
aggravated by the fact that it was my first-ever experience with Practical Training. Most of
the time was consumed by the development of logic and its application in the correct
32
manner. There were matters of concerns, and numerous new ideas coming up, time and
again, but at the end of it all, the problems, their solutions & the new ideas played a major
role in helping me develop a broad outlook towards how things work in the real world, and
everything I gained in the 30-day period, will certainly help me with the projects in the real
software world in the time to come.

APPENDICS

Introduction to WAMP
Wamp Server, Wamp Server refers to a software stack for the Microsoft Windows
operating system, created by Roma in Bourdon and consisting of the Apache web server,
Open SSL for SSL support, MySQL database and PHP programming language.

Managed code
PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management systems, and web frameworks.
PHP code is usually processed by a PHP interpreter implemented as a module in the web
server or as a Common Gateway Interface (CGI) executable. The web server combines the
results of the interpreted and executed PHP code, which may be any type of data, including
images, with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement standalone graphical applications

The PHP Framework

But first, let’s take a look at the top reasons why many developers like to use PHP
frameworks and how these frameworks can level up your development process. Here’s
what PHP frameworks do:

❖ Make speed development possible

❖ Provide well-organized, reusable and maintainable code
❖ Let you grow over time as web apps running on frameworks are scalable
❖ Spare you from the worries about low-level security of a site
❖ Follow the MVC (Model-View-Controller) pattern that ensures the separation of
presentation and logic

33
 ❖ Promote modern web development practices such as object-oriented programming
tools
❖ Access to metadata, which is enhanced type information.
❖ Managing memory for managed objects.
❖ Enforcement of code access security.
❖ Exception handling, including cross-language exceptions.
❖ Interoperation between managed code, com objects, and pre-existing dlls
(unmanaged code and data).
❖ Automation of object layout.
MYSQL

MySQL (officially pronounced as "My S-Q-L",[6]) is an open-source relational database

management system(RDBMS).[7] Its name is a combination of "My", the name of co-
founder Wideness’s daughter[8] and "SQL", the abbreviation 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.[9] For proprietary use, several paid editions are
available, and offer additional functionality.

MySQL is a central component of the LAMP open-source web application software stack

(and other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl
/PHP/Python".

Server Database Systems

Server-based systems are constructed so that a database on a central computer, known as a
server, is shared among multiple users. Users access the server through an application:
In a multi-tier system, such as Windows® DNA, the client application logic is run in two or
more locations. A thin client is run on the user's local computer and is focused on
displaying results to the user.
The business logic is located in server applications running on a server. Thin clients
request functions from the server application, which is itself a multithreaded application
capable of working with many concurrent users. The server application is the one that
opens connections to the database server.

34
 This is a typical scenario for an Internet application. For example, a multithreaded server
application can run on a Microsoft® Internet Information Services (IIS) server and service
thousands of thin clients running on the Internet or an intranet. The server application uses
a pool of connections to communicate with one or more instances of MYSQLSQL. The
instances of MYSQL can be on the same computer as APACHE, or they can be on separate
servers in the network.
In a two-tier client/server system, users run an application on their local computer, known
as a client application,that connects over a network to an instance of MYSQL running on a
server computer. The client application runs both business logic and the code to display
output to the user, so this is sometimes referred to as a thick client.
Advantages of Server Database System
● Having data stored and managed in a central location offers several advantages:
● Each data item is stored in a central location where all users can work with it.
● Business and security rules can be defined one time on the server and enforced equally
among all users.
● A relational database server optimizes network traffic by returning only the data an
application needs.
● Hardware costs can be minimized.
● Maintenance tasks such as backing up and restoring data are simplified because they can
focus on the central server.
Advantages of MYSQL as a Database Server
MYSQL is capable of supplying the database services needed by extremely large systems.
Large servers may have thousands of users connected to an instance of MYSQL at the same
time. MYSQL has full protection for these environments, with safeguards that prevent
problems, such as having multiple users trying to update the same piece of data at the same
time. MYSQL also allocates the available resources effectively, such as memory, network
bandwidth, and disk I/O, among the multiple users. Extremely large Internet sites can
partition their data across multiple servers, spreading the processing load across many
computers, and allowing the site to serve thousands of concurrent users.
Multiple instances of MYSQL can be run on a single computer. For example, an organization
that provides database services to many other organizations can run a separate
Instance.
Advantages of Server Database System
● Having data stored and managed in a central location offers several advantages:
35
 ● Each data item is stored in a central location where all users can work with it.
● Business and security rules can be defined one time on the server and enforced
equally among all users.
● A relational database server optimizes network traffic by returning only the data an
application needs.
● Hardware costs can be minimized.
● Maintenance tasks such as backing up and restoring data are simplified because
they can focus on the central server.

BIBLIOGRAPHY

1) PHP with WAMP by Zend Technologies.

2) Web application development with HTML, CSS, and JAVA SCRIPT.
3) www.w3schools.com: - tutorial for PHP.
4) www.dev.mysql.com: - tutorial for MYSQL.

36