EBAZAAR

A Project Report

Submitted in partial fulfillment of the requirement

For the award of the Degree of
Master of Computer Application
(M.C.A)
2007-2010

Submitted By Under the Guidance of

Deepmala Raghuvanshi Mr Mukesh Nigam

Roll no Cube InfoNexus Pvt. Ltd (Noida)
 CERTIFICATE

This is to certify that Deepmala Raghuvanshi is a benefited student of

MCA of batch 2007-2010 has completed the Project titled “Ebazar.” being
submitted for the partial fulfillment of degree of MCA.

This is to further certify that the student has attended the United
Institute of Management, Allahabad and CUBE INFONEXUS PVT.
LTD. for the 6 months after the fifth semester theory exams. Her work has
been satisfactory and commendable.

Date: College
name:-
Mr. Awaneesh Gupta United Institute
of Management
HOD( MCA) Department Naini,
Allahabad
Place: Allahabad
 ACKNOWLEDGEMENT

I take this opportunity to express my sincere thanks and deep gratitude to all
those people who extended their wholeh co-operation and helping me in
completing this project

First of all, I would like to thank Mr. Mukesh Nigam , Director (Cube InfoNexus
Pvt. Ltd.) for creating opportunity to undertake me in the esteemed
organization.

Special thanks to Mr. Mukesh Nigam Project Manager for all the help and
guidance extended to me by him.

I would also thanks to Mr Awaneesh Gupta (H.O.D MCA Dept.) and my

internal project guide Mr. Anand Maurya who is guiding me a lot to make
complete this project.

In all I find a congenial work environment in Cube InfoNexus Pvt. Ltd. And this
project will mark a new beginning for me in the coming days.

Praise to God, the beneficial it is he no one else who has given us all the
boundaries, which we see, in the world and given courage to complete this
project.
 DECLARATION

I am Deepmala Raghuvanshi hereby declare that the report of the project

entitled “Ebazaar” has not presented as a part of any other academic work
to get my degree or certificate except United Institute of Management
for the fulfillment of the requirements for the degree of Master of Computer
Application.

Name:
Roll No:
 CERTIFICATE OF ORIGINALITY

This is to certify that the project entitled Ebazaar being submitted for the
partial fulfillment of degree of MCA, session 2009-2010, is a record of work carried
out by Ms Deepmala Raghuvanshi under my guidance and supervision.

This is to further certify that the student has attended the CUBE
INFONEXUS PVT.LTD, NOIDA for the 6 months after the fifth semester theory
exams. Her work has been satisfactory and commendable.

We wish her success in her life.

Date:03/06/2010

Place: Noida

CONTENTS

1. Introduction
Company Profile
2. Project Detail
a. Introduction
b. Overall project description
3. System Development methodologies
4. Initial Investigation and System Requirements
a. System Study and Problem Formulation
b. Project Category
c. Platform(Technologies/Tools)
d. Front-end and Back-end Tools
e. Software and Hardware Used
5. Feasibility Study
6. System Design
a. Data Flow Diagrams
b. E-R Diagrams
c. Data Base Design
7. Module Description
8. Web Pages(Input/Output Screens)
9. Testing and System Security
10. Quality Assurance
11. Implementation and maintenance
12. Evaluation
13. Conclusion
14. Bibliography

COMPANY PROFILE

A company where innovation and technical integrity of our professionals,

work to your advantage. We at CUBE INFONEXUS have decided to embark
upon a need based approach challenging the “Me too” approach used
conventionally, tailor-making IT solutions hence bridging the gap between
you and IT. We at UM InfoNexus offer you all the services under one roof,
providing you total IT solutions with a complete team of professionals
(Microsoft Certified and Sun Microsystems Certified Professionals) to handle
various projects. The difference our company creates is the level of
analytical services provided. Our professionals analyze the acceptability
level of users of solutions beforehand designing a solution for them. We are
more inclined to implement solutions rather than selling solutions. This not
only increases the dependability on computer but also makes the users
more confident. Our organization has computer professionals experienced in
a varied area of activities.
 Overview

CUBE INFONEXUS is a subsidiary of U S Tech India Inc. which was

established in April 1999 with view to provide single point solutions to the
entire computer related needs to not only big organizations but to
individuals as well. The sole aim of the company is to increase the
awareness of computers and their versatile use by eliminating the common
and recurring problems. In addition to providing hardware and software
solutions we are also engaged in activities such as handling turnkey projects
to implement complete solutions at the user’s place. We offer you an
amazing diversity with everything you could ever want, to be it software
designing, bulk data handling and research, customer relationship
management solutions (CRM), web based applications, ERP solutions, E-
Commerce solutions, Corporate & Institutional Training and many more
options besides your hardware related needs and networking solutions into
a fresh perspective. We are staffed with a team of bright, creative,
dedicated people who work in pursuit of professional objectives. Our team
works on a disciplined plan, agreed upon and followed through. We work
together efficiently, economically, and constantly. We respect, admire and
love the talents of our co-workers, and draw on them in our pursuits. We
challenge one another in efforts to serve our clients, always seeking and
encouraging the next great idea.

segment having about 75% departments of Delhi Government, Government

of India and many more of other states on our client list.
Another very renowned software product of our company dedicated to the
corporate

and SME (small and mid sized companies) is USTECH CRM. This software
solution takes care of Sales, Support, Client Management, Lead Management,
Sales process flow, Campaigns management and office process
automation for a company. But this is just a start, which is a part of the
targeted comprehensive ERP package.

We also have to our credits, the experience to serve Intelligence agencies in

developing software tools to fight the technical threats in secret and secure
manner. The solutions include Mobile Tracking System developed for Anti
terrorist cell, Delhi Police and same for Daman police also. We had also
designed and developed solutions to monitor the registration and
movement of the Pak Nationals coming to India and many more.

On the pretext of Corporate and Institutional Training, we are equipped with

the work force having skill set on the latest and ongoing technologies in the
current IT scenario. We can name out those technologies as below:

• DotNet 2008 with framework 3.5

• J2SE/J2EE with Struts
• Software Quality Testing (SQT)
• Embedded Systems
• Biztalk Server
• Sharepoint Server
 • Silver Light.

Varied areas of activities of Digital Creations include the following:

• US TECH CRM
• Pay Bill Reporter Software Package
• Web applications development.
• Software Training and Consultancy.
• Web Designing
• Product lifecycle management
• Relational database management and research
• Customized Software Development
• Software Sales
• CAD-CAM
• Character Modeling
• 3D Animations & Walkthroughs

Our Services

Relational Database management and Research

We have completed a prestigious work to be specially mentioned here is to
design, develop and maintain a relational database solution for the
intelligence agencies which is capable to handle the information getting
stored in hundred millions. To be more precise the system, which was kept
secret few years ago, but now it’s open to the world is called Mobile
Tracking System. The system was responsible to track the position of a user,
his incoming and outgoing calls and number of other queries based on the
combinations and permutations as per the requirements of the investigating
officers. In this system data was coming from all the mobile companies and
local bodies relating to all the users, which was numbering in hundred
millions. That data was transformed and stored in a pre-designed relational
database. A front-end solution was prepared for the
investigators/researchers to get their required queries from such a bulky
database. Accuracy and speed of the result of queries was the major factor
to be taken care-off. The success of our efforts has resulted in solving many
of highlighted cases and has also become a service to the nation from our
company.
Web Development

Interactive media redefined the way organizations communicate, taking

advantage of the advancement in the information technology to supplement
and to add value to existing marketing activities thereby giving companies
with more traditional creative tendencies a new lease on life. In this age of
highly selective audience with shorter attention span, let us help you utilize
these new media to establish your presence where in counts, when it
counts. In addition to creating Web sites for our own clients, we specialize in
creating spot illustration and graphics for developers of major database-
driven sites. Seeing your organization on a website can help you make
better decisions. Having your website of your organization that shows your
activities to date. Create and analyze work areas and organization’s profiles.
And more!

Whether you are launching a new website, upgrading on existing site or

merely need a logo or banner ad, CUBE INFONEXUS has the expertise to
make your projects a success.
Owner-updateable sites - CUBE INFONEXUS custom built Content
Management Systems mean that your website stays as current as you want
at absolute minimum costs.
Database design - CUBE INFONEXUS’s competency in Information
Architecture makes for highly efficient information archival and retrieval.
E-commerce ennoblement - CUBE INFONEXUS’s decades of small-
business experience can minimize risks in your entry into marketing.

Technologies

Following are the tools and technologies that we use as building blocks in
Application Development:

Web Technologies
· VB.Net, C#.Net, ASP.Net, XML.net
· J2EE, Cold Fusion, ASP, Java (JSP, Servelet, EJB & Applet), JavaScript, PHP,
XML, VoiceXML, WAP.

Web Servers
· All popular web servers.

Database
· Oracle, MS SQL & Access, Cache.

Platforms
· NT, Linux, UNIX.

Tools
· Cold Fusion Studio, Visual Interdev, Jbuilder, Visual Age for Java.
Web Application Server
· Cold Fusion Application Server, Jrun. · HTML, Editors
· Macromedia Dreamweaver, 'Microsoft FrontPage. Multimedia / Animation
· Flash, Director, 3DX Player, 3D Studio Max, Illustrator, Sound Forge, Adobe
Premier, ULead Media Studio & More.
E-Commerce

To set-up and undertake e-commerce through Internet using

computer telecommunications.

To establish develop and maintain online databases and services and e-

mailing, e-communications, e-shopping and other similar databases and
service.

This is the fastest moving development on the Internet, which makes selling
your products over the web easy.

We can set up a database of your products and allow the customers to

purchase your products online quickly, easily and above securely.

Multimedia Presentation

A multimedia production combines different media types into a cohesive

presentation. These media types include the latest packages in animation
and graphics alone each of these types is a factor but when combined it
dramatically improves the effectiveness of the presentation. A multimedia
presentation can be utilized for any application viz. company profile,
product demos, sales, training, medical presentation to name a few.

Corp Presentation

Breathe new life into your corporate presentations!

CUBE INFONEXUS can create introduction, animations and special effects
for your corporate presentations that will clearly communicate your
message and is sure to keep your audience's eyes open. We can add value
to your presentations with animations of your corporate logo, 3D animated
charts and graphs and by making your idea or concept a reality through 3D
simulation. CUBE INFONEXUS’s team of animators is skilled in developing
productions for presentations, commercials, and other corporate
promotional purposes that will impress and dazzle your audience. Utilizing
the latest animation tools and special in-house technologies, we can bring
broadcast quality animation and special effects to the corporate market at a
fraction
of broadcast prices.

CD Authoring

CUBE INFONEXUS is able to offer your business or organization fun

production of CD-ROMs. For use in advertising campaigns, employee
education programs and public relations efforts.
Employee Education - Training manuals, company policies and explanations
of benefit programs can be published on CD at a fraction of the cost of
printing.
 Business card-sized CDs - CUBE INFONEXUS can assist you in making
an unforgettable first impression with a unique and informative custom
production.

How can our CD-ROMs give your company a competitive edge in the
marketplace? Let's take an example of a software company. CUBE
INFONEXUS can create CD-ROMs for software companies who are looking
for a way to actually demonstrate their software.

Once again, paper based marketing materials by themselves often fail to

convey the excitement of high tech products and services, in this case a
software product. In paper based material, a software company describes
their software and shows the customer a couple of screenshots to give them
a vague sense of the functionality and the interface.

But with a CD-ROM, CUBE INFONEXUS can show your clients live
demonstrations of your programs and can package those demonstrations
with sleek, elegant graphics and interactivity. It really is important to show,
not tell. We look forward to creating a CDROM for your organization. We can
also web enable the complete CD-ROM presentation and incorporate it
within your corporate web site.

“Dedication of our core team of professionals to deliver our services before

the set deadline of our esteemed clients." This is the thrust to satisfy the
client with the quality, punctuality and accuracy. CUBE INFONEXUS is
entering the field of Back Processing operations with the motto. Data Entry
Services, Call Center Services are the key places to work on.

PRODUCTS

PBR
Preparation of Pay bill Inner Sheet
Preparation of Pay bill Outer Sheet
Preparation of All Schedules:
Acquaintance Rolls
Pay Slips
Last pay Certificate
History Vision (Privilege to see and to take printouts of the past records).

ITAX
Preparation of Tax Calculation Sheets Preparation of Form 16.
Preparation of Form 24.
Penal interest calculation
Tax planning

ARREAR
Long term Arrears of Pay and Allowances IV Pay Commission (i.e. 1986)
Onwards.
Reports available are: -
Due drawn statement month wise Inner Sheet
Outer Sheet
Dearness Allowance Arrear
Reports available are: -
Due drawn statement individually Inner Sheet
Outer Sheet
Acquaintance roll

PENSION
Preparation of Death Pension
Preparation of Family Pension
Calculation of last ten months working service.
Commutation

GPF
Preparation of GPF Ledger
Preparation of GPF Broad Sheet
Preparation of GPF Annual Card
Preparation of GPF statement
GPF Interest calculation

BUDGET
Preparation of Budget statements, which includes all 11 statements
Budgetary Control
Preparation of Bill register

FORMS
G.A.R. Forms
Pension Forms
G.F.R Forms
G.P.F. Forms
HBA Forms
Advances Forms
Inventory
Vendor Masters
Item Masters
Receipt &. Issue
Department Masters
Reports

PIS (Personnel Information system)

Unique ID to all employees
Detailed Personal/Official Information of all employees Records of Service
and Breaks.
All employee transactions
Reports

Some of our Prestigious Clients (Government Segment)

are: -

Delhi: -
- Director General of Security, Cabinet Secretariat
- General Administration Department
- Sales Tax Department
- Office of Labor Commissioner
- Office of Divisional Commissioner (New Delhi Distt.)
- Department of Social Welfare
- Directorate of Information and Publicity
- Registrar of Cooperative Societies
- Land and Building Dep't.
- Transport Department
- Directorate of Agricultural Marketing
- Legislative Assembly

Directorate of Health Services: -

- Lok Nayak Hospital
- Aruna Asaf Ali Govt. Hospital
- G.B. Pant Hospital
- Institute of Human Behavior and Allied Sciences
- Guru Teg Bahadur Hospital
- Geeta Colony Super Specialty Children Hospital
- Maulana Azad Medkal College
- Guru Nanak Eye Center

Directorate of Training and Technical Education

- Delhi College of Engineering
Hindi Academy
Delhi Police (All 34 units)

Goa: -
- Office of Resident Commissioner

Chandigarh: -
- I. G. Of Police
INTRODUCTION
OBJECTIVE

DESCRIPTION

INTRODUCTION
The Application is a working demonstration of how to use blueprints principles
in a real application design. This document is an online guide to the design
and the implementation of the application with web technology.

Each release of the application maintains consistent design features such as

separating logic and presentation, using web component for control and web
pages for presentation, using business components, and so on. High-level
design features, this document goes deeper into the implementation details of
the current application release.

This document is provided as an online resource so that it may be continually

extended and updated. This document begins with a description of the
separate applications that the sample application comprises, describes the
modular structure of the ebazaar application, and provides an in-depth
description of several pieces of the modules.

Objective

The ebazaar website is an application that provides customers with online

shopping. Through a Web browser, a customer can browse the product
catalogs, purchase items by placing them into a virtual shopping cart, create
and sign in to a user account, and complete the sales process by placing an
order with a credit card.
GENERAL DESCRIPTION

SYSTEM CONCEPTUALISATION

Ebazaar is a web-based application to enable customer for online shopping

with credit card, written using ASP.NET, C#, and Microsoft SQL Server2005
(or its free cousin, SQL Server Express). It is in daily use by thousands of
customers and admin teams around the world. It facilitates the transaction
through credit cards or online payments.

SYSTEM OPERATION AND SECURITY REQUIREMENT

The software will be hosted on web to cater to User anywhere they may be.
They will be able to access the desired information to which he/she has been
given access to. The user of the application will login remotely and hence
remains always in touch with the latest critical information. Keep track of
how many hours it will be in use may be on daily basis. It is secured as only
team members will be able to access this application based on UserID and
Password issued to particular team member by Administration.

COMMUNICATION AND LOCATION

The application can be hosted anywhere depending on organizational

preference on various accounts. Preferably from Organization's perspective it
should be hosted at a place where they are able to keep track in case of any
undesired functional problems (i.e. close to Company’s Headquarters).

PLATFORM AND OPERATIONAL REQUIREMENT

The application is platform independent as designed using ASP.NET. Based

on Thin Client Architecture, as no process is taking place at client side, all
the processing that is taking place is at the Server side. The Client is just
accessing the application using a browser and actual things are done at
Server side.

TRAINING REQUIREMENT

The users of this application must be made proficient in accessing the web
application via Web Browsers. The application is descriptive to an extent to
take care of proper Navigation throughout the use of entire application. The
labels/buttons are very descriptive of the task they are going to perform. All
the Client side validations are done using JavaScript to stop any wrong data
being feed into the Database, it specifies on the data types/Range within
which values that are expected from the user.

Functional Requirements

INPUT/OUTPUT

The input being given to the application varies at various levels. The input is
given inform of various values i.e.

PROCESSING

The request made by the user varies according to different options that
he/she has to choose from, based on which user gives data values which are
being processed.

VALIDATION

All the valid users will have a UserID and a Password; the user will be
given access to the application only after matching these values. Login
will be denied if the user is not validated after matching UserID and
Password from the Database. Appropriate message will be given to the
user. It will ensure the application is secure as only Registered
Employees will be given Access, to protect application, from being
accessed by any Invalid user and hence ensuring important data from
being accessed or even tampered.

EXCEPTION CONDITION

In various transactions user unwillingly may raise an exception

condition, these expected mistakes are being caught in the Application
and user will be prompted of the mistake, and will be given correct
navigation point via which transaction is to be performed from there
on.

SECURITY

The kind of data that is being handled, it is of utmost importance that

data is kept secure at all levels. The data at various Levels is not
accessible to other Levels. Hence different team members are not able
to view data of other team members. This is being accomplished by
getting desired data about the user, who has logged in, from the
Database and from thereon maintaining his/her required data for the
entire Session for which he/she has logged in.

SEQUENCE OF OUTPUTS

The output that is being generated at various levels is done keeping in

mind the information that the user has login .Different pages will b
shown no user can see other or administrators’ resources. So different
type of user can see different type of views according to his roles.
• S
 System Development Methodology
System Development Life Cycle

PHASES:

Initiation Phase

The initiation of a system (or project) begins when a business need or

opportunity is identified. A Project Manager should be appointed to
manage the project. This business need is documented in a Concept
Proposal. After the Concept Proposal is approved, the System Concept
Development Phase begins.

System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the

concept are reviewed for feasibility and appropriateness. The Systems
Boundary Document identifies the scope of the system and requires
Senior Official approval and funding before beginning the Planning Phase.

Planning Phase

The concept is further developed to describe how the business will

operate once the approved system is implemented, and to assess how the
system will impact employee and customer privacy. To ensure the
products and /or services provide the required capability on-time and
within budget, project resources, activities, schedules, tools, and reviews
are defined. Additionally, security certification and accreditation activities
begin with the identification of system security requirements and the
completion of a high level vulnerability assessment.
Requirements Analysis Phase

Functional user requirements are formally defined and delineate the

requirements in terms of data, system performance, security, and
maintainability requirements for the system. All requirements are defined
to a level of detail sufficient for systems design to proceed. All
requirements need to be measurable and testable and relate to the
business need or opportunity identified in the Initiation Phase.

Design Phase

The physical characteristics of the system are designed during this phase.
The operating environment is established, major subsystems and their
inputs and outputs are defined, and processes are allocated to resources.
Everything requiring user input or approval must be documented and
reviewed by the user. The physical characteristics of the system are
specified and a detailed design is prepared. Subsystems identified during
design are used to create a detailed structure of the system. Each
subsystem is partitioned into one or more design units or modules.
Detailed logic specifications are prepared for each software module.

Development Phase

The detailed specifications produced during the design phase are

translated into hardware, communications, and executable software.
Software shall be unit tested, integrated, and retested in a systematic
manner. Hardware is assembled and tested.

Integration and Test Phase

The various components of the system are integrated and systematically

tested. The user tests the system to ensure that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. Prior to installing and
operating the system in a production environment, the system must
undergo certification and accreditation activities.

Implementation Phase

The system or system modifications are installed and made operational in

a production environment. The phase is initiated after the system has
been tested and accepted by the user. This phase continues until the
system is operating in production in accordance with the defined user
requirements.

Operations and Maintenance Phase

The system operation is ongoing. The system is monitored for continued

performance in accordance with user requirements, and needed system
modifications are incorporated. The operational system is periodically
assessed through In-Process Reviews to determine how the system can be
made more efficient and effective. Operations continue as long as the
system can be effectively adapted to respond to an organization’s needs.
When modifications or changes are identified as necessary, the system
may reenter the planning phase.

Disposition Phase

The disposition activities ensure the orderly termination of the system

and preserve the vital information about the system so that some or all of
the information may be reactivated in the future if necessary. Particular
emphasis is given to proper preservation of the data processed by the
system, so that the data is effectively migrated to another system or
archived in accordance with applicable records management regulations
and policies, for potential future access.

SDLC Objectives

This guide was developed to disseminate proven practices to system

developers, project managers, program/account analysts and system
owners/users throughout the DOJ. The specific objectives expected
include the following:

• To reduce the risk of project failure

• To consider system and data requirements throughout the entire life
of the system
• To identify technical and management issues early
• To disclose all life cycle costs to guide business decisions
• To foster realistic expectations of what the systems will and will not
provide
• To provide information to better balance programmatic, technical,
management, and cost aspects of proposed system development or
modification
• To encourage periodic evaluations to identify systems that are no
longer effective
• To measure progress and status for effective corrective action
• To support effective resource management and budget planning
• To consider meeting current and future business requirements

Key Principles
This guidance document refines traditional information system life cycle
management approaches to reflect the principles outlined in the following
subsections. These are the foundations for life cycle management.

Life Cycle Management Should be used to Ensure a Structured

Approach to Information Systems Development, Maintenance,
and Operation

This SDLC describes an overall structured approach to information

management. Primary emphasis is placed on the information and systems
decisions to be made and the proper timing of decisions. The manual
provides a flexible framework for approaching a variety of systems
projects. The framework enables system developers, project managers,
program/account analysts, and system owners/users to combine
activities, processes, and products, as appropriate, and to select the tools
and methodologies best suited to the unique needs of each project.

Support the use of an Integrated Product Team

The establishment of an Integrated Product Team (IPT) can aid in the success of
a project. An IPT is a multidisciplinary group of people who support the Project
Manager in the planning, execution, delivery and implementation of life cycle
decisions for the project. The IPT is composed of qualified empowered individuals
from all appropriate functional disciplines that have a stake in the success of the
project. Working together in a proactive, open communication, team oriented
environment can aid in building a successful project and providing decision
makers with the necessary information to make the right decisions at the right
time.

Each System Project must have a Program Sponsor

To help ensure effective planning, management, and commitment to

information systems, each project must have a clearly identified program
sponsor. The program sponsor serves in a leadership role, providing
guidance to the project team and securing, from senior management, the
required reviews and approvals at specific points in the life cycle. An
approval from senior management is required after the completion of the
first seven of the SDLC phases, annually during Operations and
Maintenance Phase and six-months after the Disposition Phase. Senior
management approval authority may be varied based on dollar value,
visibility level, congressional interests or a combination of these.

The program sponsor is responsible for identifying who will be

responsible for formally accepting the delivered system at the end of the
Implementation Phase.

A Single Project Manager must be Selected for Each System

Project

The Project Manager has responsibility for the success of the project and
works through a project team and other supporting organization
structures, such as working groups or user groups, to accomplish the
objectives of the project. Regardless of organizational affiliation, the
Project Manager is accountable and responsible for ensuring that project
activities and decisions consider the needs of all organizations that will be
affected by the system. The Project Manager develops a project charter to
define and clearly identify the lines of authority between and within the
agency’s executive management, program sponsor, (user/customer), and
developer for purposes of management and oversight.

A Comprehensive Project Management Plan is Required for Each

System Project
 The project management plan is a pivotal element in the successful
solution of an information management requirement. The project
management plan must describe how each life cycle phase will be
accomplished to suit the specific characteristics of the project. The project
management plan is a vehicle for documenting the project scope, tasks,
schedule, allocated resources, and interrelationships with other projects.
The plan is used to provide direction to the many activities of the life
cycle and must be refined and expanded throughout the life cycle.

Specific Individuals Must be Assigned to Perform Key Roles

throughout the Life Cycle

Certain roles are considered vital to a successful system project and at

least one individual must be designated as responsible for each key role.
Assignments may be made on a full- or part-time basis as appropriate.
Key roles include program/functional management, quality assurance,
security, telecommunications management, data administration,
database administration, logistics, financial, systems engineering, test
and evaluation, contracts management, and configuration management.
For most projects, more than one individual should represent the actual or
potential users of the system (that is, program staff) and should be
designated by the Program Manager of the program and organization

SDLC Steps
 System Requirements

Review & Validation

User Requirement Specifications

Software Requirements
Software Requirements
Review & Validation

Preliminary Design
Review & Validation
Detailed Functional Specifications

Detailed Design Global Implementation Specifications &

Review & Validation Detailed Implementation Specifications

Code and Debugging

Review & Validation Coding & Debugging

Testing
Testing
Review & Validation

Maintenance

Review & Validation Maintenance

• PROBLEM
• PROJECT
• PLATEFOR
• SOFTWAR
HARDWAR
 REQUIRMENTS ANALYSYS

SYSTEM STUDY AND PROBLEM FORMULATION

THE EXISTING SYSTEM

In old system every task was done manually which takes lot of time and
lack accuracy too. In the old system there was need to recruit more
employees to maintain all facilities. But through computerized system this
need is reduced, as computerized system is fast one. System can check
duplicity, can enter self- generated Customer identification numbers and
telephone no. So there are less chances of mistake in generation of Ids.

From the description of the present system and problems with the
existing system one can gauge the manpower wasted in these activities
even then it is difficult to gain access to different information. Addition,
updating, viewing, searching is very easy in the computerized system.
Just on the click of fingers different data can be accessed. So, here lies
the need for a change from the old system.

General Telecom system has following objectives:

1. Contains all the forms for the new connection and generates
customer identification no by the system itself.

2. Checks all the details and existing connections for some facilities
for the telephone like safe custody, transfer and shifting cases.

3. Provides all searching criteria to search any details of customer.

4. Provides Edition and deletion facilities to modify customer details

and connection details.

5. Provides security to use different options of the system.

6. Provides reports for all connection and telephone facilities.

Summary reports and daily reports as per chosen by authority to
view connection details.
THE PROPOSED SYSTEM

The proposed system is a computerized one. This has greater accuracy

and efficiency. This takes only limited time for calculation.
The proposed system can be used to maintain efficiently the Export
Department. In larger organizations Items are large. At that time also the
proposed system is useful and helpful. Export System is not only a desire
of the company but it becomes the need of the company.

Advantages of the proposed system are

1) Easy access to the data

2) The new system is more users friendly, reliable and flexible.
3) Pop-up menus to carry out transactions for a new user, and
for other alert messages.
4) Timely Report generation

Requirement Analysis

At the heart of system analysis is a detailed understanding of all

important facts of business area under investigation. (For this reason, the
process of acquiring this is often termed the detailed investigation)
Analyst, working closely with the employees and managers, must study
the business process to answer
These key questions:

 What is being done?

 How is it being done?
 How frequent does it occur?
 How great is the volume of transaction or decisions?
 How well is the task being performed?
 Does a problem exist?
 If a problem exists, how serious is it?
 If a problem exists, what is the underlying cause?

Requirement analysis relies on fact-finding techniques. These include:

 Interview
 Questionnaires
 Record inspection
 On-site observation

IDENTIFICATION OF 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 today’s organization.
Survival on manual system is difficult so, that’s 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 detailed 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.

An analyst is responsible for performing following tasks:

 Gathered all facts about the present system from the employees.

 Studied strength and weakness of the current system.

 Determined “what” must be done to solve the problem.

 Prepared a functional specifications document.

In order to reduce the time, there is a need for computerized system that cans
retrieve data, insert data, update existing data or delete existing data. These
modules are developed wit the aim of reducing time, reducing manpower,
reducing cost so that the records can be easily maintained. The volume of work
and complexity are increasing year by year. This system reduces complexity and
workload.

PRELIMINARY INVESTIGATION

A request to take assistance from information system can be made for many
reasons, but in each case some one in the organization initiate the request.
When the request is made, the first system activity the preliminary investigation
begins. This activity has three parts:

 Request clarification
 Feasible Study
 Request approval
 Many requests from employees and users in the organization are not clearly
defined. Therefore, it becomes necessary that project request must be examined
and clarified properly before considering systems investigation.

The feasibility study is carried out by a small group of people who are
familiar with information system techniques, understand the parts of the business
or organization that will be involved or affected by the project, and are skilled in the
system analysis and design process.

• Request Approval:

It is not necessary that all request projects are desirable or feasible. Some
organizations receive so many projects request from employees that only a few
of them can be purchased. However, those projects that are feasible and
desirable should be put into a schedule.

In some cases, development can start immediately, although usually

system staff members are busy on other ongoing projects. When such situation
arises, management decides which projects are more urgent and schedule them
accordingly. After a project request is approved, its cost, priority, completion
time and personal requirements are estimated and used to determine where to
add it to any existing project list. Later on, when the other projects have been
completed, the proposed application development can be initiated.
Analysis is a process of studying a problem and to find the best
solution to that problem. System analysis gives us the target for the design and
the implementation. Analysis is one phase, which is important phase for system
development lie cycle. System development is a problem solving techniques.
Analysis involves interviewing the client and the user. Three people and the
existing documents about the current mode of operation are the basic source of
information for the analyst.

SOFTWARE ENGINEERING PARADIGM

 Computer Aided Software Engineering can be as simple as a single tool
that support a specific software engineering activity or as complex as a
complete “environment “ that encompasses tools, a database, people,
hardware, a network, operating system, standards, and myriad other
components.

Each building block forms a foundation for the next, with tools sitting as
the top of the heap. It is interesting to note that the foundation for
effective CASE environment has relatively little to do for software
engineering tools themselves. Rather, successful environments
appropriate hardware and systems software. In addition, the environment
architecture must consider the human work patterns that are applied
during the software engineering process.

Although this approach is quite effective, the closed architecture of most

single source environments precludes easy addition from other vendors.

System analysis is a detailed 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.

An analyst is responsible for performing following tasks:

 Gathered all facts about the present system from the employees.
 Studied strength and weakness of the current system.

 Determined “what” must be done to solve the problem.

 Prepared a functional specifications document.

In order to reduce the time, there is a need for computerized system that
cans retrieve data, insert data, update existing data or delete existing
data. These modules are developed wit the aim of reducing time,
reducing manpower, reducing cost so that the records can be easily
maintained. The volume of work and complexity are increasing year by
year. This system reduces complexity and workload.

PRELIMINARY INVESTIGATION

A request to take assistance from information system can be made for many
reasons, but in each case some one in the organization initiate the request.
When the request is made, the first system activity the preliminary investigation
begins. This activity has three parts:

 Request clarification
 Feasible Study
 Request approval
 Many requests from employees and users in the organization are not clearly
defined. Therefore, it becomes necessary that project request must be examined
and clarified properly before considering systems investigation.

The feasibility study is carried out by a small group of people who are
familiar with information system techniques, understand the parts of the business
or organization that will be involved or affected by the project, and are skilled in the
system analysis and design process.

• Request Approval:

It is not necessary that all request projects are desirable or feasible. Some
organizations receive so many projects request from employees that only a few
of them can be purchased. However, those projects that are feasible and
desirable should be put into a schedule.

In some cases, development can start immediately, although usually

system staff members are busy on other ongoing projects. When such
situation arises, management decides which projects are more urgent and
schedule them accordingly. After a project request is approved, its cost,
priority, completion time and personal requirements are estimated and
used to determine where to add it to any existing project list. Later on,
when the other projects have been completed, the proposed application
development can be initiated.

Analysis is a process of studying a problem and to find the best solution

to that problem. System analysis gives us the target for the design and
the implementation. Analysis is one phase, which is important phase for
system development lie cycle. System development is a problem solving
techniques. Analysis involves interviewing the client and the user. Three
people and the existing documents about the current mode of operation
are the basic source of information for the analyst

PROJECT CATEGORY
 PROJECT CATEGORY
Project category:
2-tier application software using c#.net as front end and MS-SQL Server
2005 as RDBMS .
Category of this project is RDBMS based, n-tier architecture, Distributed
environment project with server-side components.

Project can be categorized in two ways:-

• Local Area Network projects.

• Distributed Projects.

Local Area Network projects are those projects where application has to be
incorporated in the Local area network of the client i.e within its premises
only. In case of LAN, server is not remotely located and client accesses the
application through the network. Here the question of platform
independence does not arise and we can use the technologies like: Visual
Basic, Fox pro, D2k or C, C++, etc.

Distributed projects are those projects where application is remotely

situated. In these kinds of projects, application is remotely situated on to
the remote server from where client machine accesses the application. WAN
and Internet is a kind of distributed application where client machine
connects to the remote server and application is downloaded on to the client
machine. Here the question of platform independence arises and we use
technologies like Java Servlet, Java Server Pages, Java Beans, RMI, etc.
 SOFTWARE &
HARDWARE
REQUIRMENT
SPECIFICATION
 SOFTWARE AND HARDWARE REQUIREMENT
SPECIFICATION

Hardware Specification:-
It is recommended that the minimum configuration for clients is as
appended below:-
Suggested Configuration of Windows clients:-
Microprocessor: - Pentium-2 class processor,450 megahertz (MHz)
Ram: - 128 MB of RAM
Hard Disk: - 2.5 gigabytes (GB) on installation drive, which
Includes 500 MB on system drive.
CD ROM Drive: - 52 X CD ROM Drive

Software Specifications:-
Operating System: Windows 2000XP/Windows 2000 NT
RDBMS: SQL Server 2005
Microsoft Visual Studio.NET

This system was developed under window 2000XP/Windows 2000 NT. It is

complete with all 32-bit versions of windows operating system. Windows is a
popular and largest used operating system in the world because it is easy to
understand and provides an easy interface to users.

Windows 2000XP/Windows 2000 NT Operating System

The main responsibility of an operating system is to manage computer’s

resources. All activities in the system scheduling application programs,
waiting files to disk, sending data across a network and so on should function
as seamlessly and transparently as possible. Windows 98 makes your
computer easier to use, with new and enhanced feature.

Improved Reliability

Window 98 improves computer reliability by introducing new wizards, utilities

and resources that keep your system running smoothly.
Faster Operating System

Windows 98 includes tools that help your computer run faster than Windows
95 with out adding new hardware. Window 98 includes a suite of programs
designed to optimized you’re web.

Integration

Windows 98 Explorer and Internet Explorer integrate local and Web-based resources

in a singleviewer computer’s efficiency, especially when used together. Window 98

makes your computer more entertaining by new hardware. These enhancements

provide you with hours of fun.

DESIGN

The most creative and challenging phase of the system life cycle is system
design. The term design describes a final system and the process by which it
is developed. It refers to the technical specifications that will be applied in
implementing the candidate system.The first step is to determine how the
output is to be produced and in what format. Samples for the output (and
input) are also presented.
The second step is input data and master files (data base) have to be
designed to meet the requirements of the proposed output. The operational
(processing) phases are handled through program construction and testing
including a list of the programs needed to meet the system’s objective and
complete documentation. Finally, details related to justification of the system
on the user and the organization are documented and evaluated by
management as a step toward implementation. To design the system we
must note the following points:
 To identify the Software Components which satisfy the System Design?
 To design and document the Software Components and their linkage.

In this component the software components and relevant interfaces such as,
interactions with existing internal and external systems, network connections, and
standard input an output formats are to be identified.

Identify Relevant Interfaces

  Interaction with existing internal systems.
 Interaction with external systems.
 Network Connections.
 Standard Input Formats
 Standard Output Formats.

Program Specification

Elements of Specifications required are

 How it is being accessed.

 Function called.
 Program Security.
 Field Details.
 Program Functions.

From Analysis

Detailed Cost
System Justification
Output Documentation and
Design Candidate
design

Input Design
Design submitted to
management
for approval
 File
Design

Design
accepted Abandon project
Processing
Design No
Yes

Test
Programs

S T E P S I N S YS T E M D E S I G N

STEPS IN SYSTEM DESIGN

Databases and database technology are having a major impact on the

growing use of computers. It is fair to say that databases will play critical
role: in almost all areas where computers are used. Including business,
engineering, medicine, law, education and library, science to name a few. A
database is a collection of related data. By data we mean known facts that
can be recorded and that have implicit meaning for example, consider, the
names, telephone numbers and addresses of the people you know. You may
have recorded this data in an indexed address, book, or you may have
stored it on a diskette. Using a personal computer and software such as
DBASE IV or V, PARADOX, MS EXCEL OR MS ACCESS. This is a collection of
related data with an implicit meaning and hence is a database.

A database is a logically coherent of with some inherent meaning.

A database represents some aspects of the real world. Sometimes called the
mini-world or the universe of discourse (UOD). Changes to the mini-world are
reflected in the database.
A database is designed, built and populated with data for the specific people.
It has an intended group of users and some preconceived applications in
which the users are interested.

A database can be of any size and of varying complexity. For example, the
list of names and addresses referred to earlier may consist of only a few
hundred records, each with simple structure. On the other hand the card
catalog of a large library may contain half a million cards stored under
different categories by primary author’s last name, by subject, by book title
with each category organized in alphabetic order.

A database may be generated and maintained or by machine. The library

card catalog is an example of a database that may be created and
maintained either by a group of application programs written specially for
that task or by a database management system.

A database management system (DBMS) is a collection of programs that

enables users to create and maintained a database. The DBMS is hence a
general-purpose software system that facilities tile processed of defining,
constructing and manipulating database for various applications. Defining a
database involves specifying the data types, structures and constraints for
the data to be stored in the database. Constructing the database is the
process of storing the data itself on some storage medium that is controlled
by the DBMS. Manipulating a database includes such functions as querying
the database to reflect changes in the mini-world, and generating reports
form the data.

With the advent of the graphical operating system like windows, the world of
imputing went through a dramatic change. It opened up a whole new world
of graphics. Interfaces that use graphics came to known so graphical user
interface (GUI). These became very popular because the users could identify
with images than words. Mention tile word print to a person and it invokes
the image of a printer. The primary requirements for an interface are that it
is easy to use. We must be able react intuitively to an interface presented to
us. This is possible if the interface presented is such that is it emulates real
life.
 Feasibility Study

A feasibility study is conducted to select the best system that meets

performance requirement. This entails an identification description, an
evaluation of candidate system and the selection of best system for he job. The
system required performance is defined by a statement of constraints, the

identification of specific system objective and a description of outputs.

The key consideration in feasibility analysis are:

1. Economic Feasibility:

2. Technical Feasibility:
3. Operational Feasibility:

Economical feasibility:-

Economic analysis is the most frequently used technique for evaluating the
effectiveness of a proposed system. More commonly known as cost/benefit
analysis; the procedure is to determine the benefits and savings that
expected from a proposed system and compare them with costs. If benefits
outweigh costs, a decision is taken to design and implement the system.
Otherwise, further justification or alternative in the proposed system will
have to be made if it is to have a chance of being approved. This is an
ongoing effort that improves in accuracy at each phase of the system life
cycle.

This feasibility also depends upon quality of staff hired and the proposed
duration of time taken in this project sometimes it might be possible due to
extension of time duration may fall the project under loss. The study of
feasibility changes from phase to phase of the project development.

In this project although this feasibility study doesn’t matter much in the case
new setup of project because we start according to client specification but on
the other hand if we have to modify over existing system we must take care
of our existing resources and must analyze specially the working condition of
hardware like server quality etc.

• Software Cost :

IIS Server : 20030/-

Sql 2000 : 15000/-

.Net frame work : 25000

• Manpower Cost :

Team cost : 25000/-

System Cost : 40,000/-

Total Cost : 125000/-

Technical Feasibility :

During technical analysis, system analyst evaluates the technical merits of

system concepts, while at the same time collecting additional information
about performance, reliability, maintainability and predictability.

1. Technical study begins with an assessment of technical viability of

proposed

1. What technologies are required to accomplish system function and

performance?

3.What new material, methods, algorithms or process are required and

what is their development risk is studied?

4.How will this technology issues affect costs.

The results obtained from technical analysis from the basis for another
go/on-go decision on the test system. If technical risks are severe, if the
models indicate that the desired function cannot be achieved, if the
pieces just won’t fit together smoothly- it’s back to the drawing board.

Duration of Project:-

Time Duration

For study 30 days

Designing &
Documentation 40 days
For development 60 days
Testing 15 days

Total time 165 days

Operational Feasibility

• The system will be used if it is developed well then be resistance for

users that undetermined
• No major training and new skills are required as it is based on DBMS
model.
• It will help in the time saving and fast processing and dispersal of user
request and applications.
• New product will provide all the benefits of present system with better
performance.
• User support.
• User involvement in the building of present system is sought to keep in
mind the user specific requirement and needs.
• User will have control over there own information. Important
information such as pay-slip can be generated at the click of a button.
• Faster and systematic processing of user application approval,
allocation of IDs, payments, etc. used had greater chances of error due
to wrong information entered by mistake.

Behavioral Feasibility

People are inherent to change. In this type of feasibility

check, we come to know if the newly developed system will be
taken and accepted by the working force i.e. the people who will use
it.
• INTR
• DFD
• E-R
• DATA
 SYSTEM DESIGN

Introduction
System design provides the understandings and procedural details
necessary for implementing the system recommended in the system
study. 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 development:

1) Logical Design

2) 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’s
requirement. When analysis prepares the logical system design, they
specify the user needs at a level of detail that virtually determines the
information flow into an out of the system and the required data
resources. The logical design also specifies input forms and screen
layouts.

The activities following logical design are the procedure followed in the
physical design e.g., producing programs, software, file and a working
system. Design specifications instruct the user about what the system
should do.
Logical and Output Design:

The logical design of an information system is analogous to an

engineering blue print of an automobile. It shows the major features and
how they are related to one another. The detailed specification for the
new system was drawn on the bases of user’s requirement data. The
outputs inputs and databases are designed in this phase.

Output design is one of the most important features of the

information system. When the outputs are not of good quality the users
will be averse to use the newly designed system and may not use the
system. There are many types of output, all of which can be either highly
useful or can be critical to the users, depending on the manner and
degree to which they are used.

Outputs from computer system are required primarily to

communicate the results of processing to users; they are also used to
provide a permanent hard copy of these results for later consultation.
Various types of outputs required can be listed as below:

• External Outputs, whose destination is outside the organization

• Internal outputs, whose destination is with the organization

• Operational outputs, whose use is purely with in the computer

department e.g., program-listing etc.

• Interactive outputs, which involve the user is communicating

directly with the computer, it is particularly important to consider human
factor when designing computer outputs. End user must find outputs easy
to use and useful to their jobs, without quality output, user may find the
entire system unnecessary and avoid using it. The term “Output” in any
information system may apply to either printer or displayed information.
 During the designing the output for this system, it was taken into
consideration, whether the information to be presented in the form of
query of report or to create documents etc.

Other important factors that were taken into consideration are:

The End user, who will use the output.

• The actual usage of the planned information

• The information that is necessary for presentation

• When and how often output and their format is needed. While designing
output for project based Attendance Compilation System, the following
aspects of outputs designing were taken into consideration.

• The outputs (i.e., well formatted table outputs in the screen itself)
designed are simple to read and interpret.

• Format of each output was another important point taken into

consideration. Output media, for each output appropriate media is
decided whether it will be displayed on screen or will be taken to printer
or both.

• Other output design related specifications, i.e., how frequently the

outputs will be generated, how many pages or sheets approximately it will
keep up, what is its planned use and output distribution to users are also
taken into account.

These were a few major designing issues, which were taken into
consideration, while deciding the output specifications for the system. As
direct beneficiary of reports is the user community, they were consulted
constantly at every level. Formats and screen design for various reports
were identified, taking into account the user requirements. Before
finalizing these were given to users for any improvement and
suggestions. End users issues taken into consideration were Readability,
Relevance and Acceptability.
Once all the output reports to be generated by ACS system were
identified, they were given to users for their acceptance. For prototyping
various outputs, final outputs models were created with dummy data,
before they were finalized.

Output Sources:

Output contents originate from these sources:

• Retrieval from a data source.

• Transmission from a process or system activity.

• Directly from an input source.

The information produced in an output can be presented as

• Tabular contents

• Graphic format

• Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs

• Content-headings, numeric, alphanumeric, etc.,

• Format-hardcopy, screen, microfilm, etc.,

• Location-local, remote, transmitted, etc.,

• Frequency-daily, weekly, hourly, etc.,

• Response-immediate with in a period, etc.,

Data items

The name given to each data item should be recorded and its
characteristics described clearly in a standard form:

• Whether alphanumeric or numeric

• Legitimate and specific range of characteristics

• Number of characters

• Positions of decimal point, arithmetic design, etc.,

Input Design:

The input design is the link that ties the information system into the
user’s world. Input specifications describe the manner in which data
enters the system for processing. Input design features can ensure the
reliability of the system and produce results from accurate data, or they
can result in the production of erroneous information.

Input Design consists of

developing specifications and procedures for data preparation

• Steps necessary to put data into a usable form for processing.

• Data entry, the activity of putting data into the computer

processing.

Objectives of Input design

Five objectives of design input focus on

• Controlling the amount of input required

• Avoid delay

• Avoiding errors in data

• Avoiding extra steps.

• Keeping the process simple.

Input stages several activities have to be carried out as part of the overall
input process. They include some or all of the following.

Data recording (i.e., collection of data)

Data encapsulation (i.e., transfer of data)

Data conversion (i.e. controlling the flow of data)

Data transmission (i.e. transporting data)

Data validation (i.e., checking the input data)

Data correction (i.e., correcting the errors)

Input Performa were designed, after a careful discussion with users.

It was attempted to cover all user requirements. Designed Performa were
given to user for any suggestion and final approval.Various data items
were identified and wherever necessary were recorded.

Input designs are aimed at reducing the chances of mistakes of

errors. As the human beings are prone to errors there is always a
possibility of occurrence of chance of errors. Adequate validation checks
are incorporated to ensure error free data storage. Some of the data
validation checks applied are as following:

• Redundancy of data is checked. It means the records of primary

key do not occur twice.

• Primary key field of any table must not be left blank.

• Wherever items are coded, input code is checked for it’s validly
with respect to several checks.

• Utmost care has been taken to incorporate the validation at each

stage of the system. E.g. when entering records into employee
information table for employee, it is checked that whether the
corresponding employee exists in the employee information table etc.,

Enough messages and dialogue boxes are provided while design

screen, which does guide user at the time of any errors, or at time of
entry. This feature provides a user-friendly interface to native users. It can
be emphasized that input deigns of BUG TRACKING is so designed that it
ensures easy and error free data entry mechanism. Once one is sure of
input data the output formatting becomes an routine work.

The purpose of this phase is to plan a solution for the problem specified
by the requirement document. This is first step in moving from the
problem domain to solution domain.

Designing activity is divided into two parts.

a) System Design
It aims to identify the modules that should be in the system, the
specification of these modules and how they interact with each other to
produce the desired result.

b) Detailed Design
The internal goal of each of the modules specified in the system design is
decided
DATABASE DESIGN

A database is a collection of inter-related data stored with a minimum of

redundancy to serve many applications. It minimizes the artificiality
embedded in using separate files. The primary objectives are fast
response time to enquires, more information at low cost, control of
redundancy, clarity and ease of use, accuracy and fast recovery. The
organization of data in a database aims to achieve three major objectives,
they are data integration, data integrity and data independence. During
the design of the database at most care has been taken to keep up the
objectives of the database design.

CODE DESIGN

The process of code is to facilitate the identification and retrieve of items

of information. The code should be simple and easy to understandable.
The codes were designed in such a way that the features such as
optimum human – oriented use and machine efficiency are unaffected.

For the code to be designed effectively, the following characteristics

were also considered while designing the code.

• Uniqueness
• Versatility
• Stability
• Simplicity
• Consciousness
 The code should be adequate for present and anticipated data processing
for machine and human use. Care was taken to minimize the clerical
effort and computer time required to continue operation
.

PROCESS DESIGN
The process can be conceptualized in such a way to keep the methodology of
main module process along with some auxiliary task, which will run concurrently
with the main program.

The top-down approach is maintained so as to keep track of the process, which

satisfies the maintenance
reliability testing requirements. The concurrency of the data is checked during
data entry, by means of validation check for data in each field.

DATAFLOW DIAGRAM

Data Flow Diagramming is a means of representing a system at any level of

detail with a graphic network of symbols showing data flows, data stores,
data processes, and data sources/destination.

The data flow diagram is analogous to a road map. It is a network model of

all possibilities with different detail shown on different hierarchical levels.
This processes of representing different details level is called “leveling” or
“partitioning” by some data flow diagram advocates. Like a road map, there
is no start point or stop point, no time or timing, or steps to get somewhere.
We just know that the data path must exist because at some point it will be
DATA FLOW DIAGRAMS
needed. A road map shows all existing or planned roads because the road is
needed.

Details that is not shown on the different levels of the data flow diagram
such as volumes, timing, frequency, etc. is shown on supplementary
diagrams or in the data dictionary. For example, data store contents may be
shown in the data dictionary.

Data Flow Diagram (DFD) uses a number of symbols to represent the

systems.

Data Flow Diagram also known as ‘Bubble Chart’ is used to clarify system
requirements and identifying the major transformations that will become
programs in system design. So it is the starting point of the design phase
that functionally decomposes the requirements specifications down to the
level of details.

The various symbols used for DFD are:

 Square

A square defines a source (originator) or destination of system data.

 Arrow

An arrow identifies data flow-data in motion. It is a pipeline through which

information flows.
 Circle

A circle or a bubble represents is a process that transforms incoming data flow into

outgoing data flow. Circle basically represents a process.

 Open Rectangle

An open Rectangle is data store-data at rest, or temporary repository of data. Open

rectangle basically denotes data storage.

User

ebazaar
 Admin

DFD Level 0

User LOGIN

ORDER
GENERATE PURCHASE

CREDIT
CARD
VERIFICATI
ON
DFD Level 1

E R DIAGRAM
 Personal
Details/Contact Update Product
Details ADMIN
Customers
Updating item
Get Product
Prices
Details
Get Item
Pricing
Get Offers &
Scheme Details Customers order
ebazaar wish list,
Select Item to Buy registration &
details
 ER Diagram

Passwor
d
First_Nam Last_Nam
e e
User_Typ
e
User_Id
Address
User_Id

User User Details

Emai
l
Mobile_N
o
Contact_No

User to
Purchase
MODULE DESCRIPTION
Product_I Product_Type_
Name Id
d

Price

Product_Master Categor
y Product_type_Master

Product_Typ
Quantit e
y
Name Desc

Product_Desc
 MODULE DESCRIPTION

Each ebazaar module has different requirements from the others. This section describes the
requirements, design, and implementation of each module.

Control module

The control module dispatches requests to business logic, controls screen flow, coordinates
component interactions, and activates user sign on and registration. The control module is
implemented by the WAF and application-specific WAF extensions.

Shopping Cart module

The shopping cart tracks the items a user has selected for purchase.

Sign on module

The Sign on module requires a user to sign on before accessing certain screens, and manages the
sign on process.

Messaging module

The messaging module asynchronously transmits purchase orders from the pet store to the OPC.

Catalog module

The catalog module provides a page-based view of the catalog based on user search criteria.

Customer module

The customer module represents customer information: addresses, credit cards, contact
information, and so on.
Control Module Requirements

The control module forms the framework underlying the application, so it

naturally has the most high-level requirements. Extensibility and
maintainability are prime considerations in this module. The control module
must be extensible because all real-world enterprise applications change
constantly. Because the control module plays a role in virtually every
interaction, its code must be well-structured to avoid complexity-related
maintenance problems. The requirements of the control module are:

• The module must handle all HTTP requests for the application. This
module controls a Web application, and interacts with a user who
sends HTTP service requests. The control module is responsible for
classifying and dispatching each of these requests to the other
modules.
• HTTP responses may be of any content type. Web application
developers do not want to be limited to just textual content types. The
control module must also be able to produce binary responses.
• Business logic must be easily extensible. Enterprise applications are
always changing and growing as business rules and conditions change.
A developer familiar with the control module should be able easily to
add new functionality with minimal impact on existing functions.
• New views must be easy to add. Most business logic changes imply
new user

control module must be structured so that such requirements can be easily

met

• views, so developers must be able to create new views easily.

• Module must provide application-wide control of look and feel.
Manually editing hundreds or dozens of user views is not a practical
way to manage application look and feel. The control module must
provide a way for application screen layout and style to be controlled
globally.
• Application must be maintainable even as it grows. The control module
must be structured so that new functions added over time do not result
in a thicket of not maintainable “spaghetti” code. It should be possible
to easily understand the control of even an application with several
hundred business classes.
• Application-wide functionality must be easy to add. New application
requirements occasionally apply to every operation or view in an
application. The

SCREEN SHOT:-

HOME PAGE
LOGIN PAGE
PRODUCTS
• TESTING

• SYSTEM
 TESTING
Testing plays a critical role in quality assurance of the software. Testing is a
dynamic method for verification and validation. With the help of testing we
observe the failure of the system in terms of logical and runtime errors. The
testing process can deduce the presence of fault in the system; however,
separate activities have to be performed to identify the faults.

As the goal of testing is to detect any errors in the programs, different flavor
of testing are often used. Unit testing are used to test module or a small
collection of modules and the focus is on detecting coding errors in modules.
During integration testing modules are combined into sub-system, which are
then tested. The goal here is to test the system design. In system testing and
acceptance testing, the entire system is tested. The goal here is to test the
fulfillment of the requirement. Structural testing can be used for unit testing
while at higher level mostly functional testing is used.

The objective for test case design is to derive asset of test that has the
highest likelihood for uncovering errors in the software. To accomplish this
objective, two different categories of test case design techniques are used.
White-box testing and black-box testing.

White-box test focuses on the program control structure. Test cases are
derived to ensure that all statement in the program control structure. Test
cases are derived to ensure that all statement in the program control
structure. Test cases are derived to ensure that all statement in the program
has been executed at least once during testing and that all logical conditions
have been exercised. Basis path testing, a white box technique, makes use
of program graphs (or graph matrices) to derive the set of linearly
independent test that will ensure coverage. Condition and data flow testing
further exercising degrees of complexity.

Black-box test are designed to uncover errors functional requirement

without regard to the internal workings of a program. Black-box testing
techniques focus on the information domain of the software, deriving test
cases by partitioning the input and output domain of a program in manner
that provides through test coverage. The black-box test is used to
demonstrate that software functions are operational, that input is properly
produced, and that the integrity of external information are maintained. A
 black-box test examines some fundamental aspect of a system with little or
no regard for the integral logical structure of the software.
Graph based testing methods explore the relationship between and behavior
of program objects. Equivalence partitioning divides the input classes of data
are likely to exercise specific software function. Boundary values analysis
probes the program’s ability to handle data at the limits of acceptability.
Specialized testing methods encompass broad arrays of software capabilities
and application areas. Graphical user interface, client/server architectures
documentation and help facilities, and real-time systems each require
specialized guidelines and techniques for software testing.

Test Information Flow

Evaluatio
n
Software Test Results
Configuration

Error
Rate Data
Expected Results
Testing
Reliability
Model Debug

Test Configuration

Predicated Reliability
Correction
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 module’s control
structure to ensure complete coverage and maximum error detection.

System Testing

Validation Testing

System Engineering
 Integration Testing
Unit Testing
Code

Design

Requirements

Nest, components must be assembled or integrated to form the complete

software package. Integration testing addresses the issues associated with
the dual problems of verification and program construction. Black-box case
design techniques are the most prevalent during integration, although a
limited amount of white-box testing may be used to ensure coverage of
major control paths. After the software has been integrated (constructed), a
set of high-order tests conducted. Validation criteria (established during
requirements analysis) must be tested. Validation testing provides final
assurance that software meets all functional, behavioral, and performance
requirements. Black-box testing techniques are used exclusively during
validation.
IMPLEMENTATION
 IMPLEMENTATION

Implementation is the process of having systems personnel check out and put new

equipment into use, train users, install the new application and construct any files

of data needed to use it. This phase is less creative than system design. Depending

on the size of the organization that will be involved in using the application and the

risk involved in its use, systems developers may choose to test the operation in only

one area of the firm with only one or two persons. Sometimes, they will run both old

and new system in parallel way to com-pare the results. In still other situations,

system developers stop using the old system one day and start using the new one

the next.
Evaluation
 EVALUATION

The evaluation phase ranks vendor proposals and determines the one best
suited, Evaluation of the system is performed to identify its strengths and
weaknesses. The actual evaluation can occur along any of the following
dimensions:
 Operational Evaluation: Assessment of the manner in which the
system functions, including case of use, response time, overall
reliability and level of utilization.
 Organizational Impact: Identification and measurement of benefits
to the organization in such areas as financial concerns, operational
efficiency and competitive impact.
 User Manager Assessment Evaluation of the attitudes of senior and
user manager within the organization, as well as end-users.
 Development Performance: Evaluation of the development process
in accordance with such yardsticks as overall development time and
effort, conformance to budgets and standards and other project
management criteria.
Maintenance
 MAINTENANCE

The maintenance of existing software can account for over 30 percent of all
effort Expended by a development organization, and the percentage
continues to rise as more software is produced. Uninitiated readers may ask
why so much maintenance is required and why so much effort is expended.
Much of the software we depend on today is on average 10 to 15 years old.
Even when these programs were created using the best design and coding
techniques known at the time and most were not, they were created when
program size and storage space were principle concerns. They were then
migrated to new platforms, adjusted for changes in machine and operating
system technology and enhanced to meet new user needs-all without
enough regard to overall architecture.
The result is the poorly designed structures, poor coding, poor logic, and
poor documentation of the software systems we are now called on to keep
running. The ubiquitous nature of change underlies all software work.
Change is inevitable when computer-based systems are built; therefore, we
must develop mechanisms for evaluating, controlling, and making
modifications.
Software maintenance is, of course, far more than “fixing mistakes.” We may
define maintenance by describing four activities that are undertaken after a
program is released for use. There are four different maintenance activities:
collective maintenance, adaptive maintenance, perfectly maintenance or
enhancement, and preventive maintenance or reengineering. Only about 20
percent of all maintenance work is spent “fixing mistakes”. The remaining 80
percent is spent adapting existing systems to changes in their external
environment, making enhancements requested by users, and re engineering
an application for future use. When maintenance is considered to encompass
all of these activities, it is relatively easy to see why it absorbs so much
effort.
SCOPE AND L
 FUTURE SCOPE

Since using Object Oriented programming has generated this system, there
are every chances of reusability of the codes in other environment even in
different platforms. Also its present features can be enhanced by some
simple modification in the codes so as to reuse it in the changing scenario.

LIMITATIONS

Though it was planned, that the system developed will absolutely error free
but there certain limitations in the system. Following may be the drawback of
this system.

 Since every time interaction is with the database so the load is more.
So the system tends to be bit slow.

 Though the system is developed as a multi-user

 Online transaction can be done with credit cards but the

for which we have to implement pay pal or take the subscription third party
tools.

CONCLUSIONS
Analysis Breaking a problem into successively manageable

parts for individual study.

Attribute A data item that characterizes an object.

Cost/Benefit Analysis The purpose of the comparing projected savings

and benefits to projected costs to decide whether a

system changed is justified.

Database A store of integrated data capable of being

directly addressed for multiple users; it is organized

so that various files can be accessed through a single

reference Based on the relationship among records

in the file rather then the physical location.

DBMS The software that determines how data must be

structured to produce the user’s view; and maintain

and update the system.

Data flow Movement of data in a system from a point of origin

to a Specific destinations- indicated by a line and

arrow.

Data security Protection of data from loss, disclosure, modification

or destruction.
Data structure A logically related set of data that can be

decomposed into lower level data elements; a group

of data elements handled as a unit.

Design Process of developing the technical and operational

specifications of a candidate system for

implementation.

Feasibility Study A procedure that identifies, describes and evaluate

candidate systems and select the best system for

implementation.

File Collection of related records organized for a particular purpose also

called a dataset.

Flow Chart A graphic picture of the logical steps and sequence

involved in a procedure or a program.

Form A physical carrier of data of information.

Gantt Chart A static system model used for scheduling; portrays

output performance against time.

Implementation In system development – a phase that focuses on

user training, site preparation and file conversion for

installing a candidate system.

Maintenance Restoring to its original condition.

Normalization A process of replacing a given file with its logical

equivalent; the object is to derive simple files with no

redundant elements.
Operating System In database – machine based software that facilitates

the availability of information or reports through the

DBMS.

Password Identity authenticator a key that allow access to a

program system or procedure.

PERT (Project Evaluation & Review Technique) A flow system model used to

manipulate various values as a basis for determining

the critical path to interpret these relationship and to

relate them back to the real world as a control

technique.

Record A collection of aggregates or related items of data

treated as a unit.

Source Code A Procedure or format that allow enhancements on a

software package.

System A regular or orderly arrangements of components or

parts in a connected and interrelated series or whole;

a group of components necessary to some operation.

System Design Detailed concentration on the technical and other

specifications that will make the new system

operational.

SDLC(System Development Life Cycle) A structured sequence of phases for

implementing an information system

System Testing. Testing the whole system by the user after major

programs and subsystems have been tested.

Unit Testing Testing changes made in an existing or new

programs.

Validation Checking the quality of software in both simulated

and live environments.
 APPENDIX

Backend remains on server side and has two components i.e.

1. Server side program
2. Data Base.

Data base is the most important thing in this universe as data base gives
identity to a thing without data base existence of a thing is impossible
while working on a project first step is to design a database.

What is data base ?

Data Base is a collection of tables and table is a collection of records in a

tabular form i.e. in row and columns.

Data Base can be divided into two parts :-

1. RDBMS.

2. DBMS.

We will be using RDBMS (Relational Database Management System) in our

project i.e. Sql Server 2005 Enterprise edition.

Why we are using (RDBMS)?

 Some of the merits of using Oracle (RDBMS) is as under
:-

• Centralization of database.
• Client Server Technology.
• Security.

• Normalization of Data Base.

• Relationship.
• Transaction Processor.
• It gives some internet related features.

Hence because of these features we are using Oracle as a

back end technology.

ABOUT Sql Server 2005

Sql Server 2005 contains all the features of previous version. It also
supports some new features & enhancement to some existing features.
Oracle servers provide deficient & effective solution for the major
features.
Large Database & Space Management Control
Many Concurrent Database Performances
High Transaction Processing Performance
High Availability
Controlled Availability
Industry Accepted Standards
Manageable Security
Database Enforced Integrity
Distributed Database System
Portability
Compatibility
Connectivity

NEW FEATURES OF Sql Server 2005

Improved Scalability
Improved Security
Improved Performance via Partition
Enhanced Support for Database Replication
Capability to Handle a Much Larger Number of
Concurrent Users
New & Improved Data Types
 REFERENCES REFRENC
BIBILIOG
FUTURE SCOPE

Since using Object Oriented programming has generated this system,

there are every chances of reusability of the codes in other environment
even in different platforms. Also its present features can be enhanced by
some simple modification in the codes so as to reuse it in the changing
scenario.

BIBLIOGRAPHY

This is not client/server application. This application is easily extensible

and upgradeable according to organization need with little or no changes.
Besides all these things, the system is very useful to management as it
provides them with the latest information about their organization. With
the few enhancement in the system it can be made more interactive

REFERENCES

1. Analysis and design of information system by V.Rajaraman

2. Software Engineering by Pankaj Jalote
3. Software Engineering by Roger S., Pressman
4. Microsoft c#.NET (Unleashed)
5. Microsoft asp.NET And c#.NET (Wrox)
6. après .net
7. pro après .net

Websites visited:

 www.codeguru.com
 www.microsoft.com
 www.3gschool.com