DEPARTMENT OF MANAGEMENT (LSM)TERM PAPER

OFDATABASE MANAGEMENT SYSYTEM (DBMS)

0N

FINANCIAL ACCOUNTING SYSTEM FOR A MEDIUM SIZE

ORGANISZATION

SUBMITTED TO : SUBMITTED BY :

MR. NANDAN SHUJA QAMMERREG NO: 10904442ROLL NO: 03SECTION: S1906MBA (I.T)

ACKNOWLEDGEMENT

The most precious moments are those when we get an opportunity to remember

and thank everyone who has in some way or the other motivated and facilitated

us to achieve our goals.

First of all I thank to GOD ALMIGHTY ALLAH for giving me power to pen

down the term paper in its present shape. I thank the entire teaching staff

especially Mr. NANDAN for sharing his valuable knowledge with us & for

providing his able guidance and support. I also thank to my classmate who

every time helped me out and encouraged me for carrying out the task.

I fall short of words to thank my family, who stood beside me while completion

of my task.

SHUJA QAMMER

FINANCIAL ACCOUNTING SYSTEM

INTRODUCTION->

The Financial Accounting System is an integrated financial accounting system that records,

monitors and maintains all accounting and financial transactions of the students of our

University using tables. This system would access the fiscal information of the university.

This system would maintain a record of the students who have submitted their fees and

whose fees is pending. It would be a boon to the university officials.

Our university is also a medium size organization that’s why to clear things quickly i have

chosen my university as the organization for whom i would be developing this financial

system .

ABSTRACT

The main aim of the this “financial accounting system” is to develop a Software package for

managing and keeping track of the fees collected in a our College i.e LPU in various departments.

The user can get the following details.

Can maintain the students’ individual fees details.

Can calculate the fees collected per department in LPU.

This project has been implemented using SQL.

REQUIREMENT ANALYSIS:

Description:

It gives detailed description about students details, fee structure for students joining under

various streams.

Criticality:

It allows modification of a student’s detail by specifying his admission number and calculates

the fees collected per department separately.

Flexibility:

The system can operate on all kind of systems.

SYSTEM DESIGN

This section contains the detailed description of the system design. Most components

described in the system architecture section will require a more detailed discussion.

The specific purpose and semantic meaning of the component describe this. This may need to refer

back to the requirement specification.

Constraints:

Any relevant assumption, limitation, or constraints for this component are essential. This should

include constraints on timing ,storage ,or component state..

The design of a software can be effectively analyzed through

1. ER diagram

OR

2. Data flow diagram

ER diagram:

The entity relationship diagram for the design of relational database systems which is used to

represent the data objects and their relationships.

Data Flow diagram:

It explains all the essential things like how the data flow into, through and out of the system. To

Exhibit the requirements for the flow of data, we use dataflow diagrams. The system may be a

software system or hardware system , a combination of both and a set of procedures.

OUR EXISTING SYSTEM:

The existing system uses ‘db concept’ in SQL to perform the manipulation on a students’ detail.

It request for name, department, current year, fees for the current year and hostel fees and finally the

total fees collected is displayed. These details are stored in separate columns and they provide the

necessary detail by making use of the unique column name for each detail.

PROPOSED SYSTEM:

The proposed system is built using the same concept of the existing system but the breakup for

fees in various criteria is elaborated.. The new system would be less complex and would be easy to

use, user friendly.

DESIGNING OF SYSTEM

ENTITY RELATIONSHIP(E-R) DIAGRAM:

Joining

Date

STUDENT

College

Courses

Fees

Departments

IdNam

e

Phone

Address

Location

Head

IT

Id

Name

Tution

Fee

Transport

Hostel

Other

MECHCSE

ECE

Joins

Offers

Collects

In

OPTS

TABLES USED IN FINANCIAL ACCOUNTING SYSTEM IN LPU

RELATIONAL TABLES

DATA FLOW DIAGRAM:

LEVEL 0:

LEVEL 1:

DESCRIPTION:

1. NEW RECORD- It creates a new cell in table and writes the various details (that are

entered by the user) of a student to that specified row.

2. OPEN PARTICULAR RECORD- This option opens the already saved details in the

table and it gives the detail about a particular student based on his admission number.

3. DISPLAY RECORD- This option displays the fees collected in a particular

department.

4. ADD RECORD- This option opens already saved table and adds a particular detail of

a student onto the same department.

5. MODIFY RECORD- This option opens the saved table in and allows the user to

modify a student’s detail.

6. REMOVE RECORD- This option removes the detail by deleting the whole specified

row of a student according to the admission number of the student.

EXAMPLE OF HOW RECORD WOULD BE STORED:

STUDENT_ID

(admission no)

FEES_TYPE FEES DEPT_ID

10904442 HOSTEL 500000 LSM

10901234

TUTION

HOSTEL

49,000.00

40,000.00 LIT

10902311

TUTION

HOSTEL

OTHERS

53000.00

40,000.00

20,000.00

ECE

107007080

TRANSPORT

HOSTEL

30000.00

50,000.00 MEC

Testing Techniques

->Introduction

The software Test Plan (STP) is designed to prescribe the scope, approach,

resources, and schedule of all testing activities. The plan must identify the

items to be tested, the features to be tested.

->Testing Strategy

Testing is the process of analyzing a software item to detect the differences

Between existing and required conditions and to evaluate the features of the

Software item.

Specific test plan components include:

Purpose for this level of test,

Items to be tested,

Features to be tested,

Features not to be tested,

Management and technical approach,

Pass/fail criteria,

Individual roles and responsibilities,

Milestones,

Schedules, and

Risk assumptions and constraints.

->TESTING

->Conversion Testing

Testing to ensure that all data elements and historical data is converted from an old system format

to the new system format.

->Performance Testing

Testing done to ensure that the application performs to custom expectations.

CONCLUSION:

Thus an effective code is developed for the Financial accounting system by using

the sql tables of database. The efficiency in tracking the details of a student

whether it is based on admission number or department had been a big end during

the development phase. It was overcome by using separate columns for the

department and the admission number. Still the program could be developed by

placing a banking option in the coding and allotting special concessions in fees

based on the performance of the student and providing scholarships for them. The

development in collection sector can be improved as well by placing an option to

pay the fees in installments which may be flexible according to the needs of the

student. But tracing those details would be a problem. These are the developments

that could be made in the existing system. On the whole,This provides a basic

structure for the collection and manipulation of fess in a college for which it had

been designed for.

REFERENCES

http://ezinearticles.com/?id=16128

http://www.hitmill.com/computers/intro.html

http://ezinearticles.com/?id=16128

http://www.computerdepot-online.com/acatalog/AP23-B5KLW-BK.jpg

http://inventors.about.com/library/blcoindex.htm

http://www.crews.org/curriculum/ex/compsci/articles/generations.htm

http:// www.finance .emory.edu/intro.html.

Principles and systems of Database by Stefano Ceri