04-01-2011, 02:41 PM
SUBMITTED BY:
Aditya Kumar
SUBMITTED TO
Department of Computer Science and Engineering
Lovely Professional University
Phagwara
PUNJAB
[attachment=7938]
TABLE OF CONTENTS
1. Introduction
2. Proposed system
a) Description
b) System requirements
3. Requirement Analysis
4. System Design
5. Flow Chart
6. Source Code
7. Future Scope of the Project
8. Conclusion
INTRODUCTION
In the existing system, most of the records are maintained on paper. It becomes very inconvenient to modify the data. In the existing system, here is a possibility that the same data in different registers may have different values which means the entries of the same data do not match. This inconsistent state does not supply the concrete information which poses a problem in the case information related to particular search record.
Our project is very useful. User is no longer required to check his register in search of records, as now it can be searched over the software by choosing some options. The user need not to type in most of the information. He/she is just required to enter the desired options. On the whole it liberates the user from keeping lengthy manual records. In a nutshell, it abates the work load of an organization.
In today’s world, no one likes to perform calculations on calculator or manually when computer is there. Every one wants his/her work to be done by computer automatically and displaying the result for further manipulations. So this project is about providing convenience regarding fee management system.
PROPOSED SYSTEM
The following documentation is a project the “FEE MANAGEMENT SYSTEM”. It is a detailed summary of all the drawbacks of the old system and how the new proposed system overcomes these shortcomings. The new system takes into account the various factors while designing a new system. It keeps into the account the Economical bandwidth available for the new system. The foremost thing that is taken care of is the need and requirements of the user.
DESCRIPTION
Before developing software we keep following things in mind that we can develop powerful and quality software.
PROBLEM STATEMENT
Problem statement was to design a module:
o Which is user friendly
o Which will restrict the user from accessing other user’s data.
o Which will help user in viewing his data and privileges.
o Which will help the administrator to handle all the changes.
FUNCTIONS TO BE PROVIDED:
The system will be user friendly and completely menu driven so that the users shall have no problem in using all options.
o The system will be efficient and fast in response.
o The system will be customized according to needs.
FOR FEE MANAGEMENT SYSTEM
o (View
o Add
o Delete)
SYSTEM REQUIRMENTS
Operating system: MS Windows XP or Windows Vista
Language: C Language
Processor: Pentium IV Processor
RAM: 512 MB
Hard disk: 5 GB
REQUIREMENT ANALYSIS
This process is adopted when management of the system development, Personnel decide that the particular system needs improvement. The system development life cycle is the set of activities, carried out by the analyst, designers and users to develop and implement a system. The systems that are present in the nature follow common life cycle pattern. For example consider the raining system. Initially the rain falls into the river, river flows into sea, the sea water evaporates to form vapors, the vapors form clouds which again bring rain. Similarly consider a man made system initially a system is analyzed, designed and made operational by the efforts of system analysis.
After successful operation or a number of users, the system becomes less and less effective by change in the environment. So these changes have to be incorporated in to the system by minor modifications. So the general activities from the life cycle of the system are given below:
• Select ion and identification of the system to be studied
• Preliminary study
• Defining the system
• Design and development of the system
• Implementation of the system
SYSTEM DESIGN
Then we began with the design phase of the system. System design is a solution, a “HOW TO” approach to the creation of a new system. It translates system requirements into ways by which they can be made operational. It is a translational from a user oriented document to a document oriented programmers. For that, it provides the understanding and procedural details necessary for the implementation. Here we use Flowchart to supplement the working of the new system. The system thus made should be reliable, durable and above all should have least possible maintenance costs. It should overcome all the drawbacks of the Old existing system and most important of all meet the user requirements.
