ABSTRACT

[About the Project xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]

For Example: Our system is developed for supporting entire general
Wire Industry Billing System Process. It is based on current need
provided by the offices to their employees. It is developed on two tier
architecture by which presentation layer is separated by database logic.
This system is designed for secure transactions and can with stand in
heavy loads.

 This project facilitates central control in distributed environment.

 It is having the facility of user registration so that only intended user
can access this system based on their roles.
 This s/w provides the quick way for analyzing and reporting the
transaction based on duration, item and generation of bill.
 Different type of client side validations are implemented for
ensuring data integrity.
 This system will definitely reduce the time required for item reg.,
issuing and bill generation of item and managing database.
 ACKNOWLEDGEMENT

I sincerely wish to thank Honorable chairman Dr. Ram Kishore Agrawal

and respected Director Dr. Amar Kumar Saxena, Rajiv Academy for
Technology and Management, Mathura.
It is a matter of great privilege to express our sincere thanks, to our
programme-coordinator Mr. Chandresh Kumar Dubey for his valuable
guidance and supervision throughout the development of the project.
We are obliged to the advice, encouragement tips and timely suggestion
provided by [xxxxxxxxxx Internal Guide Name xxxxxxxxxxx]. His
guidance and impassionate support all around is really thankful. The time
spent with him for the development of the project was full of potential as
well as knowledge. His prospects of motivation, discipline, timely
discussions and tips along with the moral support as well as confidence
extended us certainly to make a great deal of learning.
We want to express our special thanks to our entire batch mates for
fruitful discussions. We are also great full to all others who helped us
directly or indirectly in our work.
We dedicate our project work to our parents who have influenced us in
more ways then they know. Finally we bow down before the Divine
Majesty who made every thing possible.
(PROJECT TEAM)
 CERTIFICATE OF GUIDANCE

To whom it may Concern

Department Of Computer Science

This is certified that the project entitles “xxxxxProject Namexxxxxx” has

been developed under the guidance and supervision during session 2014-
2015 by following student of B.C.A fifth semester.
[xxxxxxxxName of Studentxxxxxxxxxx]

It is further certified that these student have submitted the present volume
as a project report to the department of computer science this is for partial
fulfillment of award of degree of bachelor of computer application from
Dr. B.R, Ambedkar University, Agra

[Project Guide Name]

(Project Guidance)
 TABLE OF CONTENTS

ABSTRACT

ACKNOWLEDGEMENT
DECLARATION
CERTIFICATE
CETRTIFICATE OF
GUIDANCE

PAGE
CHAPTER No. AND TITLE No.
1. Introduction
1.1 About the Project
1.2 Features Of Project
1.3 Scope
1.4 Limitation
1.5 Process Framework
1.6 Software Development Life Cycle(SDLC)

2. Feasibility & Requirement

2.1 Feasibility Study
2.2 Three Phases Of Feasibility Study
2.3 Steps Involved In Feasibility Study
2.4 Feasibility Analysis Report

3. Software Requirement Specification

3.1 Introduction
3.2 SRS of the Project
3.3 Detailed Description Of Project
3.3.1 Introduction
3.3.2 Overall Description
3.4 Software Requirement
3.5 Hardware Requirement
3.6 Introduction To Visual Basic /C++ [if other tool is
used introduction of that tool and data base]
4. System Design
4.1 Design
4.2 Various Approaches For Design Documentation
4.3 Abstraction
4.4 Modularity
4.5 Module Level Concept
4.6 Module-Based Design
4.7 ER Diagram
4.8 Flow Chart

5. Code And User Interface

6. Testing
6.1 Test Cases
6.2 Type Of Testing

7. Conclusion

8. Bibliography
 Chapter-1

INTRODUCTION
1.1 About Your Project
1.2 Features Of Project
1.3 Scope
1.4 Limitations:
1.5 Process Framework
A process framework establishes the foundation for a complete software
process by identifying a small number of framework activities that are
applicable to all software projects, regardless of their size and complexity.
In addition, the process framework encompasses a set of umbrella
activities that are applicable across the entire software process.

The following generic process framework is applicable to the vast

majority of software projects.

Communication: The framework activity involves heavy communication

and collaboration with the customer and encompasses requirements
gathering and other related activities.
Planning: This activity establishes a plan for the software engineering
work that follows. It describes the technical tasks to be conducted, the
risks that are likely, the resources that will be required, the work products
to be produced, and a work schedule.
Modeling: This activity encompasses the creation of models that allow
the developer and the customer to better understand software
requirements and the design that will achieve those requirements.
Construction: this activity combines code generation and the testing that
is required uncovering errors in the code.
Deployment: The software is delivered to the customer who evaluates the
delivered product and provides feedback based on the evaluation.

The modeling activity is composed of two software engineering actions-

analysis and design. Analysis encompasses a set of work
tasks(requirements gathering, elaboration, negotiation, specification and
validation) that leads to the creation of the analysis model. Design
encompasses work tasks(data design, architectural design, interface
design, and component-level design) that create a design model.
The framework described is complemented by a number of umbrella
activities-
 Software project tracking control
 Risk Management
 Software Quality Assurance
 Formal Technical Reviews
 Measurement
 Software Configuration Management
 Reusability Management
 Work Product Preparation and Production
1.6 SOFTWARE DEVELOPMENT LIFE
CYCLE(SDLC)
 Chapter-2

Feasibility Study
2.1 Feasibility Study
2.2 Three Phases Of Feasibility Study
2.3 Steps Involved In Feasibility Analysis
2.4 FEASIBILITY ANALYSIS REPORT
 CHAPTER-3

SOFTWARE

REQUIREMENT
 SPECIFICATION

3.1 INTRODUCTION
3.2 SRS OF THE PROJECT
 3.3 DETAIL DESCRIPTION OF THE

PROJECT

3.3.1 INTRODUCTION
3.3.2 OVERALL DESCRIPTION
3.4 SOFTWARE REQUIREMENTS-

1. Platform -

2. Back End -

3. Front End -

3.5 HARDWARE REQUIREMENTS-

Hardware Reqirement For Client’s:

1. Minimum RAM -

2. Processor -

3. LAN Card -

4. Free Space -

Hardware Reqirement For Server:

1. Minimum RAM -
 2. Processor -

3. LAN Card -

4. Minimum Free Space -

3.6 INTRODUCTION TO VISUAL

BASIC/C++ (other tool used as data base
write about it)
CHAPTER 4

DESIGN
4.1 DESIGN-

4.2 VARIOUS APPROCHES FOR DESIGN

DOCUMENT

4.3 ABSTRACTION

4.4 MODULARITY-

4.5MODULE LEVEL CONCEPTS

4.6 MODULE BASED DESIGN

4.7 ER DIAGRAM

4.8 FLOWCHART
 CHAPTER 5

EXPLORING THE

CODE AND USER

INTERFACE
 PROJECT MENUS

[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxScreen shot of Design windows and database windows and full
coding of each
modulexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxx]
CHAPTER 6

TESTING
TESTING

6.1 TEST CASE

6.2 TYPES OF TESTING

 CHAPTER 7

CONCLUSION

CONCLUSION
 CHAPTER 8

BIBLIOGRAPHY
 BIBLIOGRAPHY

[xxxxxxxxxxxxxxxxxxxxFor

examplexxxxxxxxxxxxx]

 Search Engine Google.com

 Complete Reference VB 6.0

 VB BLACK BOOK

 BPB publication “Mastering Database Programming In

Visual Basic 6.0”

 Roger s Pressman “Software Engineering”

 Bipin Singh Desai “Relation Data Base Management System”