A PROJECT REPORT

ON

ONLINE MARKET

A PROJECT
Submitted in partial fulfillment of the requirements for the award of the degree

OF

BACHELOR OF COMPUTER APPLICATION

Submitted By

Vikramjeet Singh
(07890202015)

UNDER THE SUPERVISION OF:

Mr.Amandeep Singh Arora
(Asst.Professor SGTBIMIT)

SRI GURU TEGH BHAHADUR INSTITUTE OF MANAGEMENT AND

INFORMATION TECHNOLOGY
GURUDWARA NANAK PIAO CAMPUS G.T. KARNAL ROAD,DELHI-110033
(Approved By AICTE Ministry of HRD, Govt. of India)
AFFILIATED TO GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY,DELHI

2017-2020
 CANDIDATES’S DECLARATION

I hereby certify that the work which is being presented in the project is
the project report entitled SARKARI EXAM in partial fulfilment of the
requirement for the awards of the degree of“BACHELOR OF
COMPUTER APPLICATION “ , submitted in theSri Guru Tegh
Bahadur of Management and Information Technology,GuruGobind
Singh IndraprasthaUniversity is an authentic record of my work carried
out under the supervision of Mrs.

The matter embodied in this project report has not been submitted by us
for the award of my other degree or diploma.

Date:

Roop Singh Soni

 CERTIFICATE

This is to certify that the project entitled: “ SARKARI EXAM ” done by

Mr. Roop Singh Soni & Shoab Khan University Enrolment Number
40490202017 is an authentic work carried out by them at Sri Guru Tegh
Bahadur Institute Of Management & Information Technology.The
matter embodied in this project work has not been submitted earlier for
the award of any degree or diplomas to the best of my knowledge and
belief .The suggestion as approved by the faculty was duly incorporated.

DATE:

HOD:

Guide: Mrs.
 ACKNOWLEDGEMENT

I sincerely thank Mrs. Assistant Professor Sri Guru

Tegh Bahadur Institute of Management & Information Technology
for giving me the opportunities to work under their able guidance.

As a write through these pages my mind recollects their invaluable

suggestions, their encouragement at every step which was my guiding
light.

Last but not the least my sincere thanks to my family and my friends for
their valuable suggestions at every time.

Place: New Delhi Roop Singh Soni

BCA – 5th SEM.
 TABLE OF CONTENT

Chapter Topic Page

No. No.

1. INTRODUCTION
1.1 Introduction to the Project 11

2. REQUIREMENT & ANALYSIS

2.1 Software Requirement Specification 13

2.2 Software Development Life Cycle 13

2.3 Project Category 17

2.4 Software Requirements 18

2.5 Technologies Used 18

2.6 Use Case Diagram 19

3 SOFTWARE DESIGN

3.1 Introduction 21

3.2 High Level/Detailed Design (HLD/DD) 21

3.3 Context Diagram(Level 0) 22

4 DATABASE DESIGN

4.1 Introduction 29
4.2 Database Field Specifications 29

4.3 Entity-Relationship Diagram 31

5 TESTING

5.1 Introduction 33

5.2 Methods adopted for testing 33

5.3 Test cases 34

6 ROLES AND RESPONSIBILITIES

6.1 Project roles and responsibilities 37

7 CONCLUSION & ACHIEVMENTS 39

APPENDICES Coding & Snapshots 40

BIBLOGRAPHY 55
 LIST OF FIGURES

Figure Page
Numbe
r
Figure 1: The Waterfall Model 15
Figure 2:Requirement Analysis 18
Figure 3:Use Case 20
Figure 4: Context Flow Diagram 23
Figure 9: E-R Diagram 24
 LIST OF TABLES

Table Page
Number
Admin 29
Register 29
Card 30
 LIST OF SCREENSHOTS

Table Page
Number
Screenshot 1: Home Page 46
Screenshot 2: Login Page 46
Screenshot 3:Register Page 47
Screenshot 4:Mens Collection Page 47
Screenshot 5:Womens Collection Page 48
Screenshot 6:Electronics Collection Page 48
Screenshot 7:Add to Cart Page 49
Screenshot 8:Product View Page 49
Screenshot 9:Mode of Payment Page 50
Screenshot 10:Cash on Delivery Page 50
Screenshot 11: Credit Card Page 51
Screenshot 12:Debit Card Page 51
Screenshot 13:Internet Banking Page 52
Screenshot 14:Thanking you Page 52
 CHAPTER-1
INTRODUCTION

11
1.1Introduction to the Project

The youth of today is facing many challenges and a high level of competition,
all to get a government job. Preparation for an exam, when your whole career
depends upon it, was never an easy task. There are a number of issues in it
including proper study plans, material collections, practice, and many other
things.

India is still a developing country and hence lacking in offering as many

opportunities as the increasing demands, making the competition process quite
tough. In order to solve the problem on its own level, Sarkari Exams , came up
with a solution by going in depth to provide the best content, material, study
plans, test series and notifications to the readers.

 Our aim is to focus on the career-growth of the youth to add our

contribution to the development of our country
 We wish to serve the fresher students in every possible way so that they
can get a decent job in the leading government and public organizations.

1.1.1 Objective and Scope of the Project

The sole objective of helping out aspiring students by providing them time-to-
time guidance and appropriate study material for competitive examinations in
order to secure a respectable position in various Government Organizations,
Institutes, Ministries, and Departments.

12
 CHAPTER-2
REQUIREMENT ANALYSIS

13
 2.1 SOFTWARE REQUIREMENT SPECIFICATION
If a document that completely describes what the proposed software should do
without describing how the software will do it, The basic goal of requirements
specific to produce the requirements, which describes the complete external
behavior of the proposed software. However, producing the report is said to be
done.
2.1.1 INTRODUCTION
The introduction states the goals and objectives of the software describing it in the
context of the computer -based system. Actually the introduction may be nothing
more than the software people of the planning document.

2.1.2 FUNCTIONAL DESCRIPTION

The project also provides the facility to contact the registered user easily without
any admin interaction. If you find an existing entry meeting your requirement, then
you can contact the concerned party directly. If there is no entry, which meets your
requirement, you can register your details on the site, so that others can find you.
The project improves the efficiency and effectiveness of the whole system.

2.1.3 BEHAVIORAL DESCRIPTION

It examine the operations of the software as a consequence of external events and
internally generated control characteristics. Here the Admin checks the classified
entered by the registered users. Admin is the only person who can activate or
deactivate the classified entered by the registered users.
2.1.4 PROJECT PLANNING
I was assigned the duty for developing a website known as “Online Market”.
Working in team reinstates the team for some common guidelines and standard to
be followed by all the team members across all team. For the optimum use of
practical time it is necessary that every session is planned. Planning of this project
will include the following things:
 Topic Understanding.
14
 Module Break –Up Of The System.
 Processor Logic For Each Module.
 Database Requirements.

2.2. SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

The software development life cycle (SDLC) is the process based

standard practice to develop any kind of software product. These processes are
categories as phases in SDLC and related to different activities. Different
models are described in software engineering text books, but none is fully
satisfied all the need of a software companies. Some SDLC models are Water
Fall Model, Spiral Model, and Prototype Model etc.

Our Project is based on Waterfall Model.

15
 Figure 1: The Waterfall Model

Phases in waterfall model:

1.Requirement Analysis & Specification

The goal of this phase is to understand the exact requirements of the customer
and
to document them properly. The output of this phase is a documented in natural
language known as Software Requirement Specification (SRS) document.
We have gathered the following requirements after interacting with the
Financial officials:

16
NO. REQUIREMENTS ESSENTIAL DESCRIPTION REMARKS
OR OF THE
DESIRABLE REQUIREMENTS
RS 1 The system should Essential A admin page The id are’s
have a admin Sign should appear assigned by
In when the admin the
clicks on main- admin
admin sign in

RS 2 The system should Essential A sign in box Anyone can

have a User sign in. should appear create a sign
when the user clicks in id by
on sign in. reistering

RS 3 The system should Essential It will allow the

have register form user to book their
for new users tickets
RS 4 If the Registration Essential After the Registration
of Registration of a are
user is successfully user assigned by
done. The system name or user ID it the
must redirect to must redirect to user
homepage homepage to sign
his/her id.

RS 5 Registration form Essential Registration form of When new

should be stored in a user user
database. should be stored in registered
database. himself/herself
So admin must see all information
them stored in
database
RS 6 If the admin is Essential All the rights of This page is
login, admin are only
the system should Shown access by the
show the rights of Admin not by
the Others
administrator

17
RS 7 The administrator Essential The administrator The
have the right of have the administrator
adding, deleting and right of adding, have the
modifying the deleting and right of
details modifying the adding,
details deleting and
modifying the
details
RS 8 The system should Essential After sign in the User must
have a logout page user must logout logout
from the system the page after
booking
tickets

2. Design

In this phase the SRS in transformed into a structure that is suitable for
implementation in some programming language. Here overall system
architecture is defined and high level design work is performed.

3. Implementation and Unit Testing

During this phase, design is implemented. During testing small modules are
tested in isolation from the rest of the software.

4. Integration & System testing

Integration deals with testing of the interface between modules. System Testing
involves the testing of entire system, whereas the software is a part of this
system.

5. Operation & Maintenance

The purpose of this phase is to preserve the value of the software over
time.
Software maintenance includes error correction, enhancement of capabilities,
deletion of obsolete capabilities and optimization.

18
STEPS IN REQUIREMENT ANALYSIS

Draw the
context
diagram

Develop
prototype
(optional)

Model
the
requirements

Finalize
the
Requirements

FIGURE 2. REQUIREMENT ANALYSIS STEPS

2.3 PROJECT CATEGORY

Functional Requirements
There are registered people in the system. Some are approvers. An approver can
also be a requestor. In an organization, the hierarchy could be
engineers/Managers/Business Managers/Managing Director etc. In a college, it
could be Lecturer/Professor/Head of the Department/Dean/Principal etc.
The system should be able to:-
 Login a user.
 Login an admin
 Allow a user to enter his/her details.
 Admin can add/delete/modify the things.

19
DESIGN CONSTRAINTS

In our design phase we have come across following constraints:

 Technology-We have used PHP for our project. Regarding it we have to be
careful about following things:-
o Fonts-We have to use fonts that are properly visible.
o Forms-Number of forms used in our project are need to be less to
avoid complexity
o GUI-User interface should be easy to operate.
 Requirements-While designing we need to change design of project
accordingly.
 Policies- new policies can be added as and when required.

2.4. SOFTWARE REQUIREMENTS

 For Server:-

Component Minimum Recommended

OS Windows 7 or above Windows Server 2003 SP 1 or above

Software PHPmyadmin PHPmyadmin

 For Clients:-

Component Minimum Recommended

OS Windows XP SP 2 Windows 8.1 or above

2.5. TECHNOLOGIES USED

Following is a tabular representation of the technology to be used for the

development of the proposed solution:

20
 Operating System Windows 10

Technologies PHP
Tools Xampp
Data Base Microsoft MYSQL

2.6. USE CASE DIAGRAMS

A use case diagram at its simplest is a representation of a user's interaction

with the system and depicting the specifications of a use case. A use case
diagram can portray the different types of users of a system and the various
ways that they interact with the system. This type of diagram is typically used in
conjunction with the textual use case and will often be accompanied by other
types of diagrams.

FIGURE 3: USE CASE DIAGRAM

21
 CHAPTER – 3
SOFTWARE DESIGN

22
3.1. INTRODUCTION

This chapter will focus on the design of the system using diagrams to illustrate
graphically certain sections of the software system.

3.2 High Level/Detailed Design (HLD/DD)

3.2.1 Data flow Diagrams (DFDs)

As information moves through software, it is modified by a series of

transformations. A data flow diagram is a graphical representation that
depicts information flow and the transforms that are applied as data move
from input to output.
The data flow diagram may be used to represent a system or software at any
level of abstraction. In fact, DFDs may be partitioned into levels that
represent increasing information flow and functional detail. Therefore, the
DFD provides a mechanism for functional modeling as well as information
flow modeling.

LIST OF SYMBOLS
SYMBOL NAME FUNCTION

Data Flow Connect process

Perform some transformation of

Process its input data to yield output
data.

A source of system inputs or

Source or sink sink of system outputs
A repository of data, the
arrowhead indicate net
Data Store input and net outputs
to store

23
 3.3 Context Diagram

A level 0 DFD is called fundamental system model or context model represents

entire software element as a single bubble with input and output data indicating
by incoming and outgoing arrows.

Registration Add &Remove Questions

Sarkari Exam:
Gives Tests A Competitive Change Databse
USER Exam Preparation ADMIN
Application
Result Suggested Questions

FIGURE 4: CONTEXT DIAGRAM

24
 CHAPTER – 4
DATABASE DESIGN

25
4.1 INTRODUCTION
This article/tutorial will teach the basis of relational database design and
explains how to make a good database design. It is a rather long text, but we
advise to read all of it. Designing a database is in fact fairly easy, but there are a
few rules to stick to. It is important to know what these rules are, but more
importantly is to know why these rules exist, otherwise you will tend to make
mistakes!

4.2 Database Fields Specification

A small write-up on the database, giving the fields, explaining each field etc
should be written. This write-up can be evaluated on the following points.

1. Clarity and conciseness of the database design. Like, whether key is

defined, whether any redundant fields are there etc.
2. Whether data-storage calculations are made, and if so, whether they are
done properly etc.
3. Whether any data-backup/recovery mechanism is discussed or being
thought of.

Employee Number/Registration Number is the Key of the database. The range

of valid values entered below as examples need not be taken as such. They can
be modified by the team.

TABLE NAME DESCRIPTION

WORLD CONTAINS ALL THE REGISTRATION
DETAIL OF THE USERS.
CONTAINS QUESTIONS ,ANSWERS
QUIZDATABASE AND OTHER INFORMATION

A) Register

Field Name Data Type Size Constraint

Name Varchar 20 Not Null
Email Varchar 20 Not Null
Username Varchar 20 Primary key
Password Varchar 30 Not Null
Gender Varchar 8 Not Null
Phone Int 10 Not Null

26
 B) USER

Field Name Data Type Size Constraint

Id Varchar 10 Primary Key
Username Varchar 30 Not Null
Name Text 30 Not Null
Description Varchar 50 Not Null
Price Double Not Null

4.3 Entity-Relationship Diagram

It is a detailed logical representation of data for an organization and uses

three main constructs.
Entities
It is a fundamental thing about which data may be maintained. Each
entity has its own identity.
Entity Type is the description of all entities to which a common definition
and common relationships and attributes apply.

Attributes

Attributes are properties of entities. Attributes are represented by means

of eclipses. Every eclipse represents one attribute and is directly
connected to its entity (rectangle).

Relationship

Relationships are represented by diamond shaped box. Name of the

relationship is written in the diamond-box. All entities (rectangles),
participating in relationship, are connected to it by a line.

27
FIGURE 9: ER DIAGRAM

28
CHAPTER-5
TESTING

29
5.1 INTRODUCTION

Executing a program with the intent of finding errors is called testing. Testing is
vital to the success of any system. Testing is done at different stages within the
development phase. System testing makes a logical assumption that if all parts
of the system are correct, the goals will be achieved successfully. Inadequate
testing or no testing at all leads to errors that may come up after a long time
when correction would be extremely implementation. The testing of the system
was done on both artificial and live data. In order to test data test cases are
developed. Following are the various methods that are employed for testing:

5.2 Methods employed for Testing

5.2.1 Unit Testing

In unit testing the module is tested independently. It is done to test that

the module does satisfy the functional specification. This is done to
check syntax and logical errors in programs. At the time of preparation
of technical specifications, unit test data was also prepared. The coding
for that program was considered after verifying its output against this
test data.
Following are the unit testing methods:
 In Conditional Testing, the logical conditions that are given in the
module were checked to see whether they satisfy the functionality of
the module. This is done by using the test data was prepared.
 In Loop Testing, different loops in the module like nested loops
were tested using the data. Attempts to execute the loops to their
maximum range are done.

5.2.2 Integration Testing

In Integration testing whole system was checked when all the

individual modules were integrated together in order to test whether the
system is performing as according to the requirements specified.
Interface errors if any were corrected.
Test data was prepared was fed into the system to check whether the
system fails to detects an error.

30
 5.2.3 Functional Testing

This is done for each module/sub module of the system. Functional

testing serve as a means of validating wheater the functionality of the
system confers the original user requirement i.e. does the module do
what it was supposed to do? Separate schedules were made for
functional testing. It involves preparation of test data, writing test cases,
testing for conformance to test cases and preparation of bug’s listing for
non-conformities.

5.2.4 System Testing

System testing is done when the entire system has been fully integrated.
The purpose of the system testing is to test how the different modules
interact with each other and whether the entire system provides the
functionality that was expected.
System testing consists of the following steps:
 Program Testing
 System Testing
 System Documentation
 User Acceptance Testing

5.3 Test-Cases (TC)

The test-cases is basically a list of test cases that need to be run on the system.
Some of the test cases can be run independently for some components (report
generation from the database, for example, can be tested independently) and
some of the test cases require the whole system to be ready for their execution.
It is better to test each component as and when it is ready before integrating the
components.

31
No Test cases Title Description Expected Result
. Outcome
1 Successful User The login to the Login should be Passed
Verification system should successful and the
be tried with the user should be
login name and connected to
the correct server.
password.
2 Unsuccessful Login to the Login should fail Passed
User Verification system with a with an error
due to wrong wrong password ‘Invalid password’.
password
3 Unsuccessful Login to the Login should fail Passed
User Verification server with a with an error
due invalid ‘Invalid username’.
to invalid Username
Username

4 The system A form for Form for register Passed

should provide creating new users is shown
sign up form for users login id of
creating new user the system
Login id
5 Unsuccessful Filling the Field can’t be Passed
User Verification registration empty
if they does not form without

32
enter his whole entering the
detail. whole details

CHAPTER-6

ROLES AND RESPONSIBILITIES

33
6.1.Project Roles and Responsibilities

6.1.1 ROLE

 Work as a developer, designer, tester of the application.

6.1.2 RESPONSIBILITIES

 Work on definition of development requirements and priorities.

 Data migration.
 Interfaces with other systems.
 Reporting configuration and deployment.
 Set up and maintain of security rights and access permission.
 Contributing to technical strategy ,policy and procedure.
 Development and operation of technical testing programmer.
 Production of technical documentation to agreed quality standards.
 Reporting on progress/issues to management and users.

34
 CHAPTER-7
CONCLUSION
AND
ACHIEVEMENTS

35
CONCLUSION
Sarkari Exam is an Educational application having the sole objective of helping
out aspiring students by providing them time-to-time guidance and appropriate
study material for competitive examinations in order to secure a respectable
position in various Government Organizations, Institutes, Ministries, and
Departments. The primary thought behind developing such an educational
application was to provide a study-platform for all those students who are
unable to afford the expenses of coaching classes. Our aim is to reach aspirants
in as many numbers as possible so that they can get a decent job in their field of
choice. Sarkari Exam is getting positive response from the users .

FUTURE SCOPE
The scope of this project is to provide the users with the bundle of information.
As till now if the client wanted to know one detail he use to go through many
process to get any information. It keeps the promise to deliver the quality
content from different most reliable official sources.

36
Screenshots

BIBLOGRAPHY

 http://www.google.co.in
 http://www.youtube.co.in
 http://www.wikipedia.com
 http://www.w3schools.com

PHP for the Web: Visual QuickStart Guide

Book by Larry Ullman

PHP and MySQL Web Development

Book by Luke Welling

37
38