PREFACE

The Project ONLINE FLIPKRT is designed as the project work of BCA 5 th semester.
Problems have been solved by manually which required lot of time. Here is a system designed to
simplify the task and make it so easily to do. The project starts with system analysis. This part
focuses on the requirements analysis &specification. It first describes the present working
system. Then the problems are identified. After the complete analysis of present system and
problem related to old system has been specified new system is proposed, which gives the user a
better and efficient way of managing transaction and updating his knowledge regarding the latest
development.
Then we have covered topics of algorithms, mathematical foundation and flowchart to be easily
understandable by any one.
The Online Service Center provide has the different type of Modules-

A.
B.
C.
D.
E.

Employee Modules
Customer Modules
Booking Module
Payment Section
Feedback

INTRODUCTION

INTRODUCTION

The task of developing this project has been carried out in project BCA. This gives us the
advantages of knowing flipkart environment. The project entitled ONLINE FLIPKART has
been developed as per the requirements of a customers .

ABOUT THE CLIENT:Online flipkart is designed and developed for ABC flipkart. In this project there will be
more than customers (Clients)Some workers & a one particular manager. This is the one of the
best and popular flipkart in whole Ghazipur it will be earn per year 1CR rupees. The project
entitled ONLINE FLIPKART has been developed as per the requirements of address .

ABOUT THE PROJECT:The online flipkart will be provide very smooth an error free solution for every client who
will be join to website of this online flipkart. It give every client free facility to registered
his requirements and provide different services. In this project a online flipkart provide every
customer to registered her whole requirements for the different types of dresses. And then
manager check his registered form day by day and complete the requirements of customers by
the help of home

delivery. There will be one special choices for the customers that when the

delivery will not completed at write time than the manager provide his whole rupees and provide
the all demands that will be give n by him free facility.

The online flipkart provide has the different type of Modules1.

Employee Modules:-It is used to maintain the structure facility and whole envouirment

of the flipkart.
2. Customer Module :- This module keeps details of the customers, their personal
information, about their shopping etc.
3. Booking Modules :- This modules is used for the booking system by the customers.
4. Delivery Modules:- This modules is used for delivered the requirements of customers
at home.

5. Payment Section:- This modules is used for generating the payroll for regular
customers & non-regular customers.

6.

Feedback:- This module is used for give the satisfaction by customers by his delivery
system.

INITIAL REQUIRMENT

Initial Requirements:-

The following are the list of initial requirements used in this document and the project as
well:

Administrator: A login id representing a user with user administration privileges to

the software
User: A general login id assigned to most users.
MS ACCESS: Structured Query Language; used to retrieve information from a
database.

Users requirement:Hardware requirement:Hardware which supports Win XP/ Win 7, VB-6.0 and M.S. Access.

Visual Basic:Visual basic is the method which enable user to create graphical user
interface application. it is developed by Microsoft Corporation of U.S.A. It is a
package or language to create graphical user interface application.

M.S. Access:A database is a collection of information thats related. Access allows you to
manage your information in one database file. Within access there are four major
areas: Tables, Queries, Forms and Reports.

Table store your data in your database.

Queries ask questions about information stored in

your table.
Reports allow you to print data based on queries /
tables that you have created.

System Analysis

System Analysis
System analysis is the process of gathering and interpreting facts, diagnosing problems and using
the information to recommend improvements on the system. System analysis is a problem
solving activity that requires intensive communication between the system users and system
developers. System analysis or study is an important phase of any system development process.
The system is studied to the minutest detail and analyzed. The system analyst plays the role of an
interrogator and dwells deep into the working of the present system. The system is viewed as a
whole and the inputs to the system are identified. The outputs from the organization are traced
through the various processing that the inputs phase through in the organization.
A detailed study of these processes must be made by various techniques like Interviews,
Questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now, the existing system is subjected to close study and the problem
areas are identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as a proposal. The proposal is then
weighed with the existing system analytically and the best one is selected. The proposal is
presented to the user for an endorsement by the user. The proposal is reviewed on user request
and suitable changes are made. This loop ends as soon as the user is satisfied with the proposal.

Business Need

In the world we are growing for globalization day by day with the development in IT
resources and advancement, by using latest technologies every organization wants to beat its
competitors and want to grow. Enterprise Resourceful Planning is the need of todays
organization. Survival on manual system is difficult so, thats why organization of the corporate
world wants to computerize their departments. The modules should be complete database driven
and interactive that should provide the proper information about the Placement and Training
Organization. Success of any system depends up to a large extent on how accurately a problem is
defined, thoroughly investigated and properly carried out to the choice of solution. Analysis is
the only phase in which the requirements for the new system are identified. System analysis is a
detail study of the various operations performed by a system and their relationship within and
outside of the system. The question is: what must be done to solve the problem? One aspect of
analysis is defining the boundaries of the system and determining whether or not a candidate
system should consider other related system. During analysis data are collected on the available
files, decision points and transactions handled by the parent system. Data flow diagram,
interviews, onsite observations, questionnaires are used as a logical system model and tools to
perform the analysis.

Objective of Project
This software helps customer to find different all shopping, their features, and new updates
easily. It is designed such a way that one can view all the updates of the Shopping from any
place through online. The software will help in easy maintaining and updating products in the
website for the administrator.
The project brings forth current method and techniques used in the Requirement. Specification of
information system. The highlight here has been the use of various modal to define system scope,
domain analysis, functional behavior, system timing, and object definition & design.

The problem in shopping information system is dealing with the Flipkart Shopping between
database design and process design. Designing/ mobile the database and designing/ Online
Shopping the software are often treated as separate processes.

The main objectives of this project of the new system are mentioned below1. Fast and efficient.
2. Reliable and accurate.
3. Centralized Data.
4. Non Redundant Information.
5. Easy to Access.

LIMITATIONS OF EXISTING SYSTEM

The existing system had several limitations and drawbacks, which led the SHOPPING to switch
to a better and effective system

Low functionality

Erroneous input/output

Security problem

Data redundancy

Processing speed

Manual errors

Complexity problem

It also include the following limitations

1. The use of man power in this so high.

2. Quick report on the current status will be very time consuming and the chances of error
3.

will be high.
Need a lot of paper work.

Proposed System
Proposed system is an automated Online Flipkart Shopping. Through our software user can
Shopping. Website admin to update information, edit information .Our proposed system has the
following advantage.
User friendly interface.
Fast access to database.
Less error.
More Storage Capacity.
Quick response.

Benefits:
Online shopping makes all the difference when it comes for the mobile products .It not
only allows buying best products within your parches for the new Product of all shopping .The
best thing about online shopping, is not just only offers the widest selection but also the
everything in your budget.

Cost Benefits Analysis:Cost Benefits analysis is performed to ascertain whether the costs in the system match
with the benefits they will provide. The various end of costs incurred in the development and
implementation of the system include:

Hardware costs incurred in purchase of hardware, i.e., computer and its

peripherals.
Personnel cost include the salaries of the EDP staff as well as the perks of
personnel involved in the development of the system.
Facility costs are expenses incurred in the preparation of the physical site
like flooring, wiring, lighting etc.
Operation costs include all costs associated with the day-to-day operation of
the system.
Supply costs are variable costs that increased use of paper, ribbon, disks etc.
The system is expected to provide benefits. The first is to identify each benefit
and then assign a monetary value to it for cost/benefit analysis. Both tangible
and intangible benefits are considered as discussed earlier.

Procedure for Cost-Benefit Analysis:

The determination of cost and benefit can be enumerated as under:

Identify the various costs and benefit pertaining to give project.

Categorize the various costs and benefits for analysis.

Select and method for evaluation.

Interpret the results of evaluation.

Take action.

Advantage:1. All the procedure in this project is automatic accept the of data from the user.
2. The project given the user-friendly environment, which gives the way of working in
more efficient manner.

Feasibility Study
When a project is started an initial investigation is carried out. During this
phase of study users need has recognized and other requirements are determined.

Once the problem has been defined a study is carried out to select the best
system i.e. a feasible system that means performance requirements. So Feasibility is the
determination of whether or not a project is worth doing and the process followed
in making this determination is called a Feasibility Study. In order to conduct the
feasibility study we have seven distinct, but inter-related types of feasibility, These
are Technical feasibility, Operational feasibility, Economical feasibility, Social feasibility,
Management feasibility, Legal feasibility and Time feasibility. Out of these seven three
are key feasibilities to consider, these are:

Technical Feasibility
Economical Feasibility
Operational Feasibility

Technical feasibility:This is concerned with specifying equipment (hardware) and software that will successful
satisfy the user requirement. It considers the following facts:

The facility to produce outputs in a given time

Response time under certain conditions
Ability to process a certain volume of transaction at a particular speed
Facility to communicate data to distant location

While examining technical feasibility, huge importance is given to the configuration of the
proposed system. The configuration should give the complete picture about the systems
requirement such that what kind of hardware is required and how these units are
interconnected .The proposed system can be run on currently existing software and hardware.

Economical feasibility:Since cost plays quite an important role in deciding the new system, it must be identified
and estimated properly. So economic analysis is the most frequently used technique for
evaluating the effectiveness (economical feasibility) of a proposed system. To determine the
economical feasibility of the system a cost/benefit analysis is to make. This procedure is

to determine the benefits and savings that are expected from a proposed system and
compare them with costs. Four facts that plays an important role in deciding economical
feasibility of the proposed system are as follows: Cost-saving benefits, Cost-avoidance
benefits, Improved-performance benefits, Improved-information benefits, Hence the proposed
system is economically feasible.

Operational feasibility:It is mainly related to human organizational aspects. The points to be considered are:

What changes will be brought with the system?

What organizational structures are disturbed?
What new skills will be required?

Do the existing staff members have these skills if not, can they be trained. The project would be
beneficial because it satisfies the objectives when developed & installed. All operational aspects
are considered carefully & conclude that the project is operationally feasible.

Software requirement
specification

Software requirement specification

A requirements specification for a software system is complete description of the behavior of a
system to be developed. It includes a set of used cases that describe all the interactions the users
will have with the software. In addition to use cases, the SRS also contains non-functional (or
supplementary) requirements. Non-functional requirements are requirements which impose
constraints on the design or implementation (such as performance engineering requirements,
quality standards, or design constraints).Requirement

documentation is very important

activity after the requirements elicitation and analysis. This is the way to represent the
requirements in a consistent format. Requirement document is called Software Requirement
Specification (SRS).
The

software

requirement

specification is produced at the culmination after analysis task.

This is the way to represent requirements in a consistent format. It is a specification for

a particular software product , program or a set of programs that performs certain
functions in a specific environment .The function and allocated to software as part of
system engineering are

refined by establishing a complete information description, a

detailed functional and behavioral description, an indication of performance requirements

and design constraints,

appropriate

validation

criteria,

and

other

data pertinent to

requirements.
Software product, program or set of programs that perform certain functions in a specific
environment. There are two important cases regarding SRS: First one, SRS is used to
define the needs and expectations of the users. The second one, SRS is written for different
purpose and serve as a contract document between customer and developer. This
produces the probability of the customer being disappointment with the final product.
IEEE defines a requirement as:
A condition of capability needed by a user to solve a problem or achieve an
objective.

A condition or capability that must be met or processed by a system to satisfy

a contract, standard, specification, or other formally imposed document.
Generally, the SRS is a document that completely describes what the proposed software
should do without describing how the
requirements

software will do it.

The

basic goal of the

phase is to produce the SRS, which describe the complete external

behavior of the proposed software.

Organization of an SRS
The most general organization of an SRS is as follow:

Introduction:This site will provide the mobile product process online.

Purpose:
Easy access and reduce limitation of existing system.

Scope:
It will give the great help for the keep us update with product.

Definitions:
Not applicable.

System Overview:
This system will be used by users buy the product.

Overall Description:
It will provide the online facility for buying for product.

Product Functions:
It provide online mobile shopping for buying mobile product.

User Characteristics:
Administration, users.

Constraints Assumptions and Dependencies:

Fast excess and responsive.

Dependency on window platform and web

browser.

External interfaces:

Hardware requirement
Software requirement

User can search baby product.

User cans also his/her view about the site.
User /Admin can view the feedback.
Admin can view/post/edit/update/the product and add baby product.

Functions:-

Performance requirements:
Easy and Fast access.

Logical database requirements:

MS access.

Design constraints:
User friendly and easy access to users and viewer. Suitable page
management for product.

Features:An SRS must consist of following features:

Consistent
Complete
Unambiguous
Modifiable
Verifiable
Traceable
Ranked

Platform:
Windows is very powerful scalable Operating System that Provide basic file and prints
services as well as robust for server application.

Main features are follows: More extensive network management features.

Improved network Performance.
Enhanced communication features.

Need for SRS:The SRS is needed for the following reasons:

An SRS establishes the basis for agreement between client and developer.

An SRS provides a reference for validation of the final product.

A high- quality SRS

A high- quality SRS reduces the development cost.

is a prerequisite to highquality software.

Objective:A software requirement specification is literally the conversation of a specific point. It's
difficult in this instance to avoid the circular reference. A project's specifications consist of the
body of information that should guide the project developers, engineers, and designers through
the work of creating the software.
A software requirement specification document describes how something is supposed to
be done. A specifications document may list out all of the possible error states for a
certain form, along with all of the error messages that should be displayed. The
specifications may also describe the steps of any functional interaction, and the order in
which they should be followed by the user.
A requirements document, on the other hand, would state that the software must handle
error states reasonably and effectively, and provide explicit feedback to the users. The
specifications show how to meet this requirement.
Specifications may take several forms. They can be a straightforward listing of functional
attributes, they can be diagrams or schematics of functional relationships or flow logic, or
they can occupy some middle ground. Software Requirement Specifications can also be
in the form of prototypes, mockups, and models. Project specifications are much more

important for determining the quality of the product. Every rule and functional
relationship provides a test point.
A disparity between the program and its specification is an error in the program if and only if the
software requirement specification exists and is correct. A program that follows a terrible
specification perfectly is terrible, not perfect.

Scope:Boundaries of software products are defined by a set of Requirements. The software

development team designs, implements, tests, and delivers these Requirements to you. A
Requirement is an atomic unit of a software product from the viewpoint of the user. As a rule,
Requirements are always correct, unambiguous, verifiable, and traceable. Requirements are
numbered and prioritized. High-level user Requirements is called Features. Up to 10 Features
can be defined in any software project, regardless of the project size. Features are defined in the
Vision document. The Vision is created before the project commences, and is the basis for the
ROM Estimate. The Vision is developed right after you submit an Informal request.
Up to 5 hours are spent for developing the Vision by a system analyst, regardless of the project
size. When a ROM Estimate is approved, an Alpha-Specification is created. Upon your approval,
the Alpha-Specification becomes a Beta-Specification. When the project begins and the Budget
is approved (following a LCO Milestone), the Beta-Specification becomes an effective
Specification.
A fully-dressed Specification is called a SRS (Software Requirements Specification) and is
compliant with IEEE 830-1998 'Recommended Practices for Software Requirements
Specifications'. The SRS includes a Glossary, Use Cases, Functional Requirements, and NonFunctional Requirements
All Functional Requirements are then listed in a requirements attributes spreadsheet, where all
necessary attributes for each Requirement are maintained. Changes to the project scope can be
made only by issuing new Specifications through a process called Change Requests. Each
Change Request implies that changes will be made to the Budget, Schedule, and Risks.

Requirement:The software requirements specification is produced at the culmination of the analysis

task. This is the way to represent requirements in a consistent format. It is a
specification for a particular software product , program or a set of programs that
performs certain functions in a specific environment .The function and allocated to
software as part of system engineering are

refined by establishing a complete

information description.
A detailed functional and behavioral description, an indication of performance
requirements and design constraints, appropriate validation criteria, and other data pertinent to
requirements.

Functional Requirement:Functional requirements define the internal workings of the software: that
is, the calculations, technical details, data manipulation and processing, and other
specific functionality that shows how the use cases are to be satisfied. It also
contains nonfunctional requirements, which impose constraints on the design or
implementation (such as performance requirements, quality standards, or design
constraints).
The name, summary and rationale of each functional requirement are used in the same way as
those of the use cases. The behavior that is to be implemented should be described in plain
English in the Requirements section most requirements are only relevant to a small number of
use cases-these should be listed by name and number in the References section. (Some
requirements are not associated with use cases.)The core of the requirement is the description of
the required behavior. It is very important to make this clear and readable. This behavior may
come from organizational or business rules, or it may be discovered through elicitation sessions
with users, stakeholders, and other experts within the organization. Many requirements will be
uncovered during the use case development. When this happens, the requirements analyst should
create a placeholder requirement with a name and summary, and research the details later, to be
filled in when they are better known.

It deals with the functionalities required from the system which are as follows:

The website will help the people to conduct their online buying product.

Only authorized person can access related detail.

Administrator will be responsible for updating the site.

Security Requirement:Security requirements are the particularly significant in defense system and many
database systems. Security requirement place restrictions on the use of certain
commands, control access to data, provide different kind of access requirement for
different people, require the use of passwords and cryptography techniques, and maintain
a log of activities in system. Given the current security needs even of common systems,
they may also require proper assessment of security threats, proper programming
techniques, and use of tools to detect flaws like buffer overflow.
For the purpose of security process I have added the login feature into my project so as to keep it
safe from the external problem. One can only interact with my project by giving it the suitable
i.e. the accurate ID and password.

Output Requirement:The output requirements of the project are:

Admin should have and id for Login.

There must be a output device for taking the
hard copy of any information.

Software Requirement:Software requirement plays a very important role in the making the
development of a project, as it provide a suitable language as well as the perfect medium to
implement our program or project on the system .Software requirement is very necessary for the
implementation of a program. The software requirements specification is produced at the

culmination after analysis task. This is the way to represent requirements in a consistence format.
It is a specification for a particular software product. Program or a set of program that perform
certain function in a specific environment. The function and allocation to software as part of
system engineering are refined by establishing a complete information description, a detailed
functional and behavioral description, an indication of performance requirements and design
constraints, appropriate validation criteria, and other data pertinent to requirements.
Software product, program or set of program that perform certain function in a specific
environment. There are two important cases regarding SRS. First one, SRS is used to define the
needs and expectations of the users. The second one, SRS is written for different purpose and
serve as a contract document between customers and developer. This produces the probability of
the customer being disappointment with the final product.

Hardware Requirement:The hardware requirement specification at the culmination of the analysis task.
This is the way to represent requirements in a consistent format. It is a specification for a
particular hardware product, program or asset of programs that perform certain functions in a
specific manner.
In the designation of my project hardware requirement is also very necessary as it
provide various tools for the making of my project. Which supports development tools and web
browsers?

Module Description:Client in supported Residential Services (SRS) have the same rights as anyone
else in the community-to be treated as an individual and to have his/ her rights and values
respected. This module will give you an opportunity to explore these issues, as well your own
practices in relation to your clients autonomy, dignity, rights and value.

Module Aims:

On successful completion of this session you should be able.

Recognize how you developed your own values and how they can impact on

others.
Understand the nature of self, self-esteem, self-worth, dignity, respect and

personhood.
Recognize the practices can increase or reduce a clients autonomy describe ways
in which you can support clients autonomy, dignity, rights and values.

Form Modules:Form module (form file name extension) can contain textual description of the
forms and its controls including their property setting. They can also contain form level
declaration of constants, variables and external procedure and events and general procedure.

Class module:Class modules (.cls file name extension) are similar to form modules, except that
They have no visible user interface. You can use also modules to create your own object
including code for method and properties.

Standard modules:Standard modules (.bas file name extension) can contain public modules level
declaration of type, constants, variables, external procedures and public procedures.

SYSTEM DESIGN

SYSTEM DESIGN
System design provides the understandings and procedural details necessary for implementing
the system recommended in the system Emphasis is on the translating the performance
requirements into design specifications. The design phase is a transition from a user oriented
document (system proposal) to a document oriented to the programmers or database personnel.
System design goes through two phases of the development:

Logical Design

Physical Design

A data flow diagram shows the logical flow of the system. For a system it describes
the input (source), output (destination), database (data stores), and procedures (data flows) all in
a format that meets the user requirements. When analysis prepares the logical system design,
they specify the user needs at a level of detail that virtually determines the information flow into
and out of the system and the required data resources.

SOFTWARE PROCESS MODEL

Waterfall Model:The waterfall model is a popular version of the systems development life cycle
model for software engineering. Often considered the classic approach to the systems
development life cycle, the waterfall model describes a development method that is linear and
sequential.
Waterfall development has distinct goals for each phase of development.
Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of
the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the

same with waterfall development. Once a phase of development is completed, the development
proceeds to the next phase and there is no turning back.
The advantage of waterfall development is that it allows for
departmentalization and managerial control. A schedule can be set with deadlines for each stage
of development and a product can proceed through the development process. Theoretically, be
delivered on time. Development moves from concept, through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order, without any overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought out in the concept stage. Alternatives to the waterfall model
include joint application development (JAD), rapid application development (RAD), synchronize
and stabilize, build and fix problems.
The waterfall model is a sequential design process, often used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the
phases

of conception, initiation, analysis, design, construction, testing, production,

implementation &maintenance.

Waterfall Model

Feasibility Study

Requirements analysis Delivery

and Specification

Design and
specification
Coding and Module
Testing
Integration and
module testing

Maintenance

DESIGNING APPROACH
Top down design:The TOP DOWN approach starts from the highest level component of the
hierarchy and proceed through to lower levels. A TOP DOWN design approach start by
the major component of the system. Decomposing them into their lower level component
and iterative until the desired label of detail is achieved. Top down design method is in
some form of step wise refinement. Starting from a abstract design in each step the design
is refine to more concrete level, until we reach a level were no more refinement is
needed.
A system consists of components, which have components of their own; indeed a system is a
hierarchy of components. The highest level components correspond to the total system. The top
down approach from the highest level components of hierarchy and proceeds through to lower
levels. By contrast a bottom up approach starts with the lowest level component of the hierarchy
and proceeds through progressively higher levels to the top level components.
The TOP DOWN approach has been promulgated by many researches and has been found to be
extremely useful for design. Most design methodologies are based on the top down approach.
A TOP DOWN approach suitable only if the specifications of the systems are clearly known and
the system development is from scratch. However, if a system is to be built from an existing
system, a bottom approach is more suitable, as it starts from some existing components.

HIGH LEVEL
DESIGN

TABLE SCHEMA
Table Name: - Admin Login
Field Name

Attribute

Data Type

Or Attribute

Description

Size

Cross Reference
Or Primary Key

Admin Id

ID of admin

Text

10

Primary Key

Password

Name of Retailer

Text

10

Not Null

Table Description: -Login of admin.

Table Name:-User
Table Description:-Details of users.

Firstname

First Name of user

VarChar

25

Cross Reference
OR Primary Key
Null

Middlename
Lastname

Middle Name of user

Last Name of user

VarChar
VarChar

25
25

Null
Null

Address of user

VarChar

300

Null

Email
Moblie

Email of user
Mobile number of user

VarChar
VarChar

50
16

Null
Null

Password

User Password

VarChar

25

Null

Field Name OR Attribute

Address

Attribute Description

Data Type

Size

Table Name: - Baby Product

Table Description: -Baby Shopping Details.
Field Name

Attribute

Or Attribute

Description

Retailer Id

ID of Retailer

Name

Data
Type

Cross Reference Or
Size

Primary Key

VarChar

10

Primary Key

Name of Retailer

VarChar

10

Not Null

Address

Address of Retailer

VarChar

10

Not Null

Phone no.

Phone no. of Retailer

Number

15

Not Null

E-mail id

E-mail id of Retailer

VarChar

15

Not Null

Table Name:- Shop

Table Description: -Shop Details.
Field Name

Attribute Description

Data Type

Size

Cross Reference
Or Primary Key

Attribute
Shop_id

Shop_id

VarChar

10

Primary Key

Name

Shop Name

VarChar

20

Not Null

Address

Address of Shop

VarChar

30

Not Null

Phone no.

Phone no. of Shop

Number

15

Not Null

Table Name: - Marketing Representative

Table Description: -Marketing Representative Details.
Field Name

Attribute Description Data Type

Size

Cross Reference
Or Primary Key

Attribute
MR id

ID of the M R

VarChar

10

Primary Key

Name of the M R

VarChar

20

Not Null

Address

Address of M R

VarChar

10

Not Null

Mobile no.

Mobile no of M R

Number

10

Not Null

E-mail id

E-mail id of M R

VarChar

15

Not Null

Name

Table Name:-Company
Table Description: -Company Details.
Field Name

Data Type

Size

Cross Reference Or
Primary Key

ID of Company

VarChar

10

Primary Key

Name

Name of the Stockiest

VarChar

10

Not Null

Address

Add of Ph. Company

VarChar

15

Not Null

E-mail id

Email id of Company

VarChar

10

Not Null

No.

15

Not Null

Attribute
Company id

Phone no.

Attribute
Description

Phone no. of company

Table Name:-Feedback
Table Description: -Feedback Details.

Field Name

Attribute

Data Type Cross Reference Or

Primary Key

Attribute

Description

Name

Name of the user

VarChar

Not Null

E-mail id

Email id of user

VarChar

Not Null

Suggestion

Suggestion of user

Text

View

View of user

Text

Not Null
Not Null

Entity-Relationship Diagram
The entity relationship model is a generalization of primitive commercial systems, which are
based on hierarchical and network approaches. The E-R relationship, which is also known as
Entity Relationship is based on the theory of real world which consists of a set of basic objects,

which are called entities and relationships among these object. An entity exists as an object and
is distinguishable from other objects.
Entity Relationship Diagram is popular data modeling tool. An ER-Diagram can express the
overall logical structure of a database graphically. An ER-Diagram illustrates data at rest. It gives
more detailed picture of the data stores, independent of the processing. The ER-Diagram shows
the pictorial representation of the system database. It describes the Distinguishable Entity sets,
their attributes and relation established between the different entities. It is detailed logical
representation of the data for an online Mobile shopping and user three main constructs-Data
entities, relationships and attributes. ER Diagrammatic representation of the database design, ER
Diagram is like blue print of database.
For example: account number 1002 at the ICICI bank is an entity that uniquely identifies one
particular account.

Guideline for Drawing E-R Diagram:When gathering information I have to:A. Identify the entities in the system.
B. Identify the attributes of each entity.
C. Identify the relationship between the entities.

Entity:
Any distinguishable person, place, thing, event or concept about which information is kept or an
object which can be distinctly identified and distinguished and represented in a database or
anything about which we store information is called an Entity.

Relationship:A relationship is an association among entities relation is the link between objects through
which a entity is related with other entity.

Attribute:-

Attributes describe the entity to which they are associated. A particular instance of an
attribute is a value. In other words attributes are the characteristics of an entity type. Attributes
can be classified as descriptors or identifiers. A descriptor describes a non-uniquely identify an
instance of an entity.

Notification for E-R Diagram:There is no standard for representing data objects in E-R diagram. Each modeling
methodology uses its own notation. All notational style represents entities as rectangular
boxes and relationship as lines connecting boxes. Each style uses a special set of symbols
to represent the cardinality of a connection. An entity is represented in E-R diagram as a
rectangular box enclosing the entity type name.

Attribute names are enclosed in ellipses and attached to their entity type by straight lines.

The symbols used for the basic E-R constructs are

Notation

Use

Lines

Linking

Symbols

attributes

to

entity

to

sets

relationship sets

Ellipse

Representing
attributes

Rectangle

Representing
entity set

Keys:A key is a value which can always be used to uniquely identify an object instance. It
becomes important to invent a method to distinguish entity and relationship. The differences
between entities must be expressed in terms of attributes.

Super Key:A Super Key is a set of one or more attributes which, taken collectively, allows us
to identify uniquely an entity in the entity set.

Candidate Key:An attribute that uniquely identify a row is called Candidate Key. Candidate key
is also referred to as Surrogate keys.

Primary Key:A candidate key to choose to identify rows uniquely is called a Primary key.

Alternate Key:If there are multiple candidate keys in a table, then the keys which are not chosen
as primary key will be called as alternate key.

Composite Keys:When the key that uniquely identifies the rows of the table is made up of more
than one attribute it is called a composite key.
Entity digram
DATA FLOW DIGRAM:A Data Flow Diagram (DFD) is a graphical representation of the information flow and
transformation that are applied, as data moves from the input to the output. It is also known as
data flow graph or a bubble chart. The DFD may be used to represent increasing information
flow and functions details. A level 0 DFD, also called a fundamental system model, represent an
entire software element as a single bubble with the input and the output data directed by the
incoming and outgoing arrows. Data flow diagrams are commonly used during problem analysis.
Data flow diagram is quite general and nit limited to problem analysis for software
requirement specification. DFDs are very useful if understanding a system and can be
effectively used during analysis.
A DFD shows the flow of data through the system. It views the system as a function that
transforms the input into desired output. The DFD aims to capture the transformations that
take place within a system to the input data so that eventually the output data is
produced. The agent that performs transformation of data from one state to another is
called a process. So a DFD shows the movement of data through the different processes.
Named and circle shows the processes and data flows are shows by arrows entering or
leaving the circles. A rectangle represent a source or sinks and is a net originator or

consumer of the data. A source or sink is typically outside the main system of study. The
DFD should be carefully scrutinized to make sure that all the process in the physical
environment are shown in DFD.

It should also ensure that none of data flow is actually carrying control information.
Features of DFD:

The exceptional simplicity of the DFD zymology is one reason why data oriented
analysis techniques is the most widely used.

The data flow diagram is a graphical tool that can be very valuable during the system
analysis.

The DFD depicts information flow without explicit notation of control.(e.g. conditions of
loops).

The level 0 data flow diagram should depict the software as a single bubble.

Primary input/output files should be maintained.

One bubble at a time should be refined.

There is a natural tendency to over complicate the DFD. This happens when we try to show too
many details early.

LOW LEVEL
DESIGN

Low level design

The low level design documents for a project should provide a complete and detailed
specification of the design for the software that will be development in the project, including the

classes, member and non-member function, and associations between classes that are involved.
By the end of the low level design stage, the code should be all but written.
The low level design document should contain a listing of the declarations of all the classes, nonmember-functions, and class member function that will be defined during the 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 plan defined in the projects requirement document. More importantly, each
projects low level design document should provide a narrative describing (and comments in
your declaration and definition files should point out) how the high level design is mapped into
its detailed low-level design, which is just a step away from implementation itself. This should
be an English description of how you converted the technical diagram (and text description
found in your high level design into appropriate class and function declarations in your low level
design. Your should be especially careful to explain how the class roles and their methods were
combined in your low level design. And any change that you decided to make in combining and
refining them.

Modula ration:

A system is considered modular if a consist of discreet component show that each

component can be implemented separately, and a change to one component has minimal
impact on other components.

Each function in each abstraction has a single, well defined purpose.

Each function manipulates no more than one major data structure.
Function share global data selectively .it easy to identify all routines that share a

major data structure.

Function that manipulates instances of abstract data types are encapsulated with
the data structure be in manipulated.

Structure chart:
The structure chart is one the most commonly used methods for system design. Structures
chats are used during architectural design to document hierarchical structure, parameters
and inter connection in a system.

CODING

Coding

The goal of the coding or programming phase is to translate the design of the system
produced during the design phase into code in a given programming language which can
be executed by a computer, and which performs the computation specified by the design.
For a given design, the aim is to implement the design in the best possible manner.
The coding phase affects both testing and maintenance profoundly. As we saw earlier, the
time spent in coding is a small percentage of the total software cost, while testing and
maintenance consume the major percentage. Thus it should be clear that the goal during
coding should not be to reduce the implementation cost, but the goal should be to
reduce the cost of later phases, even if it means that the cost of this phase has to be
increase. In other words, the goal during this phase is not simplify the job of the
programmer. Rather the goal should be to simplify the job of the tester and the
maintainer.
This distinction is important, as most programmers are individualistic, and are mostly
concerned about how to finish their job quickly, without keeping the later phases in
mind. During implementation it should be kept in mind that the programs should not be
constructed so that they are easy to write but, that they are easy to read and understand.
There are many different criteria for judging a program, including readability, size of the
program, execution time, and required memory.

Different programmers were required to implement a program, and were given different
goals. It was found that the programs written by different programmers were very
different, and each tended to satisfy its goal. for our purposes ease of understanding and
modification should be the basic goals of the programming activity. This means that
simplicity and clarity are desirable, while cleverness and complexity are undesirable.

Programming Practice

The primary goal of the coding phase is to translate the given detailed design into source
code in a given programming language, such that code is simple, easy to test, and easy
to understand and modify. Simplicity and clarity are the properties a programmer should
strive for in the programs.

Top-Down and Bottom-Up:The design of a software system consist of a hierarchy of modules.

The main program invokes its subordinate modules, which in turn invoke
their subordinate modules and so on.
In a top down implementation, the implementation starts from the top of the hierarchy,
and then proceeds to the lower levels. First the main module is implemented and then its
subordinates are implemented and then their subordinates and so on. In a bottom up
implementation, the process is the reverse. The development starts with implementing the
modules that are at the bottom of the hierarchy.
The implementation proceeds through the higher levels, until it reaches the top. Top down
and bottom up implementation should not be confused with top down and bottom up design. It is
most reasonable to have implementation proceed in a top-down manner if testing is being done
in a top-down manner. On the other hand, if bottom-up testing is planned then bottom-up
implementation should be preferred.

Structured Programming:
Structured programming is often regarded as go to-less programming. A program has a static
structure as well as a dynamic structure. The static structure is the structure of the text
of the program which is usually just a linear organization of statements of the program.
The dynamic structure of the program is the sequence in which the statements are
executed during the program execution.
The goal of structured programming is to write a program such that its dynamic
structure is the same as its static structure. In other words, the program should be
written in a manner such that during execution its control flow is liberalized and follows

the linear organization of the program text. For structured programming, a statement is
not a simple assignment statement, but could be a structured statement. The key property
is that the statement should have a single entry and single exit. That is during execution,
the execution of the statement should start from one defined point and the execution
should terminate at a single defined point.

Information Hiding:To reduce coupling between modules of a system it is best that different modules be
allowed to access and modify only those data items that are needed by them. The other
data items should be hidden from such modules and the modules should not be allowed
to access these data items. Language and operating system mechanisms should preferably
enforce this restriction. Thus modules are given access to data items on a need to know
basis.
One form of information hiding that is supported by many modern programming
language is data abstraction. The advantage of this form of data abstraction is that the
data is entirely in the control of the module in which the data is encapsulated.

Programming Style:It is impossible to provide an exhaustive list of what to do and what not to do in order
to produce a simple and readable code. Being able to do this will amount to providing
an algorithm for writing good code. Here we will list some general rules which are
usually applicable1) Names:Most variables in a program reflect some entity in the problem domain,
and the modules reflect some process. Variable names should be closely related to

the entity they represent and module names should reflect their activity. It is bad
to choose cryptic names or totally unrelated names.

2) Control constructs:As discussed above it is desirable that as much as possible single entry,
single exit constructs should be used. It is also desirable to use a few
standard control constructs rather than using a wide variety of constructs, just
because they are available in the language.
3) Go to s: - Go to s should be used sparingly and in a disciplined manner. Only when
the alternative to using go to s is more complex should the go to s be used. In any
case alternatives must be thought of before finally using a go to. If a go to must be
used forward transfers is more acceptable that a backward jump.
4) Information Hiding:- Information hiding should be supported where possible. Only
the access functions for the data structure should be made visible while hiding the
data structure behind these functions.
5) User Defined Types:- Modern languages allow the users to define types like the
enumerated type. When such facilities are available, they should be exploited where
applicable.
6) Nesting:The different control constructs, particularly the if-then-else, can be nested. If the
nesting becomes too deep, the programs become harder to understand. In case of
deeply nested if-then-else, it is often difficult to determine the if statement to
which a particular else clause is associated. Where possible, deep nesting should
be avoided even if it means a little inefficiency.

7) Module Size:-

A programmer should carefully examine any routine with very few statements or
with too many statements. Large modules often will not be functionally cohesive and
too small modules might be incurring unnecessary overhead. There can be no hard
and fast rule about module size and the guiding principle should be cohesion and
coupling.

8) Module Interface:A module having a complex interface should be carefully examined.

Such

modules

might

not

be

functionally

cohesive

and

might

be

implementing multiple functions. As a rule of thumb any module whose

interface has more than five parameters should be carefully examined and
broken into multiple modules with a simpler interface if possible.

9) Program Layout:How the program is organized and presented can have great effect on the
readability of programs. Proper indentation, blank spaces, and parenthesis should
be employed to enhance the readability of programs. Automated tools are
available to pretty print a program, but it is good practice to have a
clear layout of program.
10) Side effort:When a module is invoked, it sometimes has side effects of modifying the
program state beyond the modification of parameters listed in the module interface
definition, for example, modifying global variables. Such side effects should be
avoided where possible, and if a module has side effects, they should be properly
documented.

Robustness:Program is robust if it does something planned even for exceptional

condition. A program might encounter exceptional conditions in such forms

as incorrect input, the incorrect value of some variable and overflow. A

program should try to handle such situations. In general a program should
check for validity of inputs, where possible, and should check for possible
overflow of the data structures. If such situations do arise, the program
should not just crash or core jump , but should produce some
meaningful message and exit gracefully.

SCREEN
SHOT

TESTING

Testing:The code is tested at various levels in software testing. Unit, system and user acceptance testing
are often performed. This is a grey area as many different opinions exist as to what the stages of
testing are and how much, if any iteration occurs. Iteration is not generally part of the waterfall
model, but usually some occur at this stage. In the testing the whole system is test one by one
Following are the types of testing:

Defect testing the failed scenarios, including defect tracking

Path testing

Data set testing

Unit testing

System testing

Integration testing

Black-box testing

White-box testing

Regression testing

Automation testing

User acceptance testing

Software performance testing

System Testing:It involves two kinds of activities: integration testing and acceptance testing developing
strategy for integration the components of a software system in to a complete system

requires functioning of the whole system and careful planning so that modules are
available for integration when needed.
Acceptance testing involves planning and execution of various types of tests in order to
demonstrate that implemented software system satisfies the requirement document.

Integration testing:It is a systematic technique for testing the programmed structure while at
the same time conducting test to uncover errors associated with interfacing. The
objective is to play unit tested modules and build a programmed structure that has
been dedicated by design. Bottom-up integration was used in developing.

Testing mechanism:Software testing is the most important phase of any software development
life cycle. It is the testing part, which validates the software and check whether
the software is working as desired or not. The major purpose of testing is to
retrieval bugs in the software. In testing software design is executed with various
test inputs for which the test programmer knows result in advance. The departure
of the programmed output from the known results confirms that the software
contains error.

Testing is divided into following phases:

The module interface was tested to assume that information properly float into
and out of the program unit test.

The local data structure was examined to assume that data stored temporally
maintain their integrity during all steps in an algorithm execution.

Boundary condition were tested to assume that module operated properly at

boundaries establish to limit or restrict processing.

All independent parts through this control structure were exercised to assume that
all statement in a module have been executed at least once.

All error handling path were tested.

Acceptance testing:Acceptance testing is performed with realistic data of the client to

demonstrate that the software is working satisfactory. Testing here is focused on
external behavior of the system; the internal logic of program is not emphasized.
White box testing:This is a unit testing method, where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.
Black box testing:This testing method considers a module as a single unit and checks the unit at interface
and communication with other modules rather getting into details at statement level. Here
the module will be treated as a block that will take some input and generate output.
Output for a given set of input combinations are forwarded to other modules.
Desirable features are frequently dropped because there is no time to implement them.
Code rewrites are also set aside, even if they are needed to bring a fragile first working
version to a level a programmer considers professional. A conscientious programmer
might take the initiative and do the job anyway, on the sly. Late in the project, he
may drop a significant change into the package without warning. These efforts go
beyond the call of duty and the 40- hour week. They may improve the product
tremendously or destabilize it badly, probably both for a time. Whatever the result,
people take personal initiative to improve the product.
-

By incorrect or missing function.

Applying block box testing in my project ONLINE SHOPPING SYSTEM
Interface error.
Error in external database access behavior (or) performance error.
Initialization and termination error its mainly used for uncover error in software
function.

Text Script:The development team has vision of what they want, they want to create, a
commitment to getting as close to the dream as they can, and recognition to that theyll
have to flash out details by trial and error. By the time they have worked out the final
detail of one aspect of the product, they have working version that one or two key people
understand fully. That version is the specification. It is not engraved in stone: it will be
reviewed and polished later, to achieve consistency with other parts of the system. Much
of polished may be at a suggestion of a tester.
Desirable features are frequently dropped because there is no time to implement then code
rewrites are also set aside, even if they are needed to bring a fragile first working version to a
level a programmer considers professional. A conscientious programmer might take the initiative
and do the job anyway, on the sly late in the project; he may drop a significant change into the
package without warning. These efforts go beyond the call of duty and the 40-hour week. They
may improve the product tremendously or destabilize it badly, probably both for a time.
Whatever the result, people take personal initiative to improve the product. These are always late
changes, the goal is to with then-they are needed as painlessly as possible. The goal is not to
create administrative system to inhibit them. If we cant keep up with then as tester, we have a
problem. But the solution wont come from complaining about or in trying to stop them.

Phase in Testing:Testing was done in following phases:

First the live database was portable form previous database version to visual studio 6.0

for testing but later real implementation has to be done.

And on client machine setup for particular module was installed.
And also MS Access was installed and Net service name was created for connecting the
database on NT server.

Then the module which consists of data entry form, process form, reports enquiries were
tested by entering the real data which was taken from the respective department.

TEST INFORMATION FLOW:A strategy for software testing may also be viewed in the context of the
spiral. Unit testing begins at the vortex of the spiral and, concentrates on each
unit, component of the software as implemented in source code. Testing
progresses moving outward along the spiral to integration testing, where the focus
is on designed the construction of the software architecture. Taking another turn
outward on spiral, we encounter validation testing, where requirements
established as part of software requirements analysis are validated against the
software that has been constructed. Finally, we arrive at system testing, where the
software and other system elements are tested as a whole. To test computer
software, we spiral out along stream lines that broaden the scope of testing with
each turn.
Considering the process from a procedural point of view, testing within the context of software
engineering is actually a series of four steps that are implemented sequentially. The steps are
shown in Figure. Initially, tests focus on each component individually, ensuring that it functions
properly as unit. Hence, the name unit testing. Unit testing makes heavy use of white-box testing
techniques, exercising specific paths in modules control structure to ensure complete coverage
and maximum error detection.

IMPLEMENTATION
&MAINTENANCE

Implementation
Implementation is the carrying out, execution, or practice of a plan, a method, or any design for
doing something. As such, implementation is the action that must follow any preliminary
thinking in order for something to actually happen. In an information technology context,
implementation encompasses all the processes involved in getting new software or hardware
operating properly in its environment, including installation, configuration, running, testing, and
making necessary changes. The word deployment is sometimes used to mean the same thing.
The Implementation Phase is the final phase of the SDLC and it involves the actual construction
and installation of a system. This phase also includes the maintenance of the system and any
future updates or expansion of the system. With the database project example, the following
activities would be common:
There are several activities involved which implementing a new project they are:

End user training.

End user education.
Training on the application software.
System design.
Parallel run and to new system.
Post implementation review.

End user training:

The successful implementation of the new system will purely upon the involvement of
the officers working in that department. The officers will be imparted the necessary training on
the new technology.

End user education: -

The education of the end user start after the implementation and testing is over.
When the system is found to be more difficult to understand and complex more
effort is put to education the end used to make them aware of the system, giving
then lectures about the new system and providing them necessary documents and
materials about how the system can do this.

Training of application software: After providing the necessary basic training on the computer awareness.
The users will have to be training upon the new system such as the screen flow
and screen design type of help on the screen, type of error while entering the data,
the corresponding validation check at each entry and the way to correct the data
entered. It should then cover information needed by the specific user or group to
use the system.

Post implementation view: The department is planning a method to know the states of the past
implementation process. For that regular meeting will be arranged by the concerned
officers about the implementation problem and success.

Maintenance

Software maintenance is the last phase in the software engineering process that eliminates
error in the working system during its work span and to tune the system to any variation
in its working environment. The system require maintenance as there may be changes and
requirements in the organizational needs, government policies, hardware and software
environment etc. often small system deficiencies are found as a system is brought into
operation and changes are made to remove then. System requirements may be revised as
a result of system usage or changing operational needs. Perhaps oversight that occurred
during the development process needed to be corrected. Often the maintenance need
arises to capture additional data for storage in a database or in transaction, files or
perhaps it may be necessary to add error detection features to prevent system users from
in adversely taking an unwanted action.
Maintenance of the system after it is installed is concerned with an additional factor in hardware.
Once the system is delivered and installed there is a brief warranty period during which time the
vector is responsible for maintenance. This is typically a 90-day period after that time the
purchaser has the option of acquiring maintenance from various sources. Maintenance source
excepting vendor is also available from companies specializing in providing the service called
third party maintenance companies. Following table summarized the broad classes of
maintenance found in development of information systems:-

Category

1.Corrective debugging

Activity

Emergency fixer, routing.

2. Adaptive Data and to hardware and

software, change in the external
environment.

Accommodation of changes.

3. Preference documentation
recording of computational

User enhancement, improved.

efficiency, user recommendations for

new capabilities.
4. Preventive and adjusting the
equipment to prevent breakdowns,

Routine service of cleaning.

future maintainability reliability

enhancement, recovering design
information improves the overall
quantity.

BIBLIOGRAPHY &
REFRENCE

BIBLIOGRAPHY & REFERENCE

With tremendous advances in software technology, it is very essential for software to be up to
date and user interactive keeping this fact in view, I have tried my best to keep it to such level as
of todays. So, to make it to this level, I had to consult many books and media. These are the list
of books and media, I have consulted:-

BOOKS:

Office 2000 by SANJAY SAXENA.

Software Engineering by PANKAJ JALOTE (NAROSA Publication).

Database Management System by Leon & Leon (VIKASH Publishing House).

WEBSITES:

www.google.co.in

www.wikipedia.com

www.w3school.com