ABSTRACT

As the name specifies "SCHOOL MANAGEMENT SYSTEM" is a software

designed for managing various activities in the school. For the past few years the
number of educational institutions are increasing rapidly. There by the number of
schools are also increasing for the quality education. This particular project deals with
the problems on managing a schools and avoids the problems which occur when
carried manually.

Identification of the drawbacks of the existing system leads to the designing of

computerized system that will be compatible to the existing system with the system.
Which is more user friendly and more GUI oriented. I can improve the efficiency of
the system, this overcome the drawbacks of the existing system.

· Less human error

· Strength and strain of manual employee can be reduced

· High security

· Data redundancy can be avoided to some extent

· Data consistency

· Easy to handle

· Easy data updating

· Easy record keeping

· Backup data can be easily generated

 TABLE OF CONTENTS

Chapter No. Title Page No.

Abstract i

List of figures ii

List of tables iii

Chapter 1 Introduction 1

1.2 Objective

1.3 Project Category

1.4 Tools / Platform, H/W & S/W Requirement

1.5 Context Level Diagram

1.5.1 E-R Diagram

1.5.2 Data base Structure

1.5.3 Process logic Module of the project

1.5.4 Screen shots

Chapter 2 Security

2.1 Limitation of the project

2.2 Future Scope of the Project

3 Bibliography
 INTRODUCTION

BRIEF ABOUT THE ORGANISATION:

Sahedd Smarak English Boarding School is situated in Chouraha, Butwal, Rupandehi.

The school is recognized by Nepal Govt. It is running since last ten years from class
Nursery to Xth under administrative control of Liladhar Gautam

At present the school management and its all procedures are totally manual
based. It creates a lot of problems due to wrong entries or mistakes in totaling etc.
This system avoided such mistakes through proper checks and validation control
methods in checking of student record, fee deposit particulars, teachers schedule,
examination report, issue of transfer certificates etc. I met personally to the principal
and manager and discuss about the computerization of manual school management
system. This system registers a student and confirms its admission in school. When a
student registers in school a S.R. No (unique ID) is allotted to student. Student record
is based on his/ her S.R. No.
 OBJECTIVE

The objective of developing such a computerization system is to reduce the

paper work and safe of time in school management. There by increasing the efficiency
and decreasing the work load.

The project provides us the information about student record, school faculty,
school timetable, school fee, school examination result and library management. The
system must provide the flexibility of generating the required documents on screen as
Ill as on printer as and when required.
PROJECT DESCRIPTION:

The school management process can be described using different modules.

Each of the module performs a different function.

SCHOOL MANAGEMENT SYSTEM

Student School Faculty Markanalysis Examination Library

Record Fee Profile Table Result Management

(a) Student Record:

We can easily find out the details of student alongwith his photograph by entering
his/her S.R. No.

(b) School Fee:

We can find out the fee structure of every class and the fee for student whether the
student has paid fee or not. If he/ she has not paid school fee within prescribed period, he /
she should have to pay penalty.

(c) Faculty Profile:

We can easily find out the description about the teacher posted in school .
(d) Time Table:

We can search out the name of teacher and subject in particular class at a
particular time .

(e) Examination Result:

We can check the performance of students during the particular year . On passing
the particular class , student record and student TC is updated .

(f) Library Management:

Library management process updates the library database. It gives information about a
particular book when issued to the student and when it is taken back.

SCOPE:

The scope of the school management system facilitate us in the following

jobs :-

 Maintaining Student Records

 Automatic Preparation of Marksheet

 Automatic updation in student TC

 Library Managenent

PROJECT CATEGORY:

The Project is functioning under the RDBMS (Relational Database Management

System) category of the software which handles the database of all the students and
staff. It uses object oriented programming technology to develop the system .

ANALYSIS :

Necessary DFDs and ER Diagram are attached herewith.

(i) DFDs:

During analysis phase of SDLC (Software Development Life Cycle), the system
analyst or other members of the project team draw many diagrams to show how data move
within an organization. These diagrams, popularly called as DFD (Data Flow Diagram),
quickly convey to both the software developers and users how the current system is working
and how the proposed system will work. The main advantage of DFD is that they are easily
understood by the users and hence users can suggest modifications in the proposed system.

In Data Flow Diagram (DFD) I have used four types of symbols as described below: -

DFD Symbol:

Stands For
Symbols

Source or Destination of Data

Rectangle Square

Flow of Data

Rounded
Process which transforms Circle Oval Rectangle

Store of Data

I have consideredthree levels of DFDs

DFD Level 0
 CFD (Context Flow Diagram)

CAD (Context Analysis Diagram)

Student or Applicant

Fee
Depos
Admi
it
ssion Book

Form Reque
st
Fee
Issue/
Depos
Valid/ Retur
it
Invali n
d School Repor
t
Managemen
Reports

t System

ADMINISTRATOR

DFD level 0 (Context Level)

DFD Level 1
 L ib ra ry In fo .

2 .0
L ib ra ry
S tu d e n t R e c o rd M anagem ent
P ro cess

1 .0
S tu d e n t S tu d e n t M a s te r F ile
A d m is s io n F e e D a ta b a s e
P ro cess

F e e S tr u c tu re

M a rk s D a ta b a s e

M o n th ly F e e
4 .0 R e c o rd
E x a m in a tio n

3 .0
T C D a ta b a s e M o n th ly F e e
5 .0 C o lle c tio n
T C R e c o rd
U p d a tio n

DFD LEVEL 2
School Management Process
 S tu d e n t R e c o rd D e ta ils
S tu d e n t R e c o rd

S tu d e n t D e ta il
1 .1 1 .2
U p d a tio n R e q u e s t

C o n firm
R e g is tra tio n A d m is s io n
M ark s

E n try R e je c tio n C o n f irm

T C G iv e n b y S c h o o l

F e e D a ta b a s e
A d m is s io n D e ta il

F e e B ill D e ta il
F e e S tr u c tu r e
S tu d e n t D e ta il

M a rk s D a ta b a s e
1 .3
F e e B ill
G e n e ra tio n

1 .5

B ill D e ta ils
S tu d e n t D e ta il
E x a m in a tio n S tu d e n t M a s te r F ile

M o n th ly F e e R e c o rd
T C D a ta b a s e
F e e D e ta ils
T C D e ta il

1 .6 1 .4
T C R e c o rd M o n th ly F e e
U p d a tio n C o lle c tio n

Data Flow Diagram Level 2 for School Management Process

DFD LEVEL 2 Library Management Process

N e w B o o k E n try

B o o k D e ta ils

B o o k D a ta b a s e
C h a n g e S ta tu s In fo ra m tio n

C h a n g e S ta tu s In fo ra m tio n

F e e D a ta b a s e
B o o k D e ta ils

F in e D e ta ils

S tu d e n t D a ta b a s e

S tu d e n t S tu d e n t
2 .1 D e ta il D e ta il
2 .2
Issu e R e tu rn

Issu e B o o k R e tu rn B o o k
D e ta il D e ta il

Is s u e D a ta b a s e

Data Flow Diagram Level 2 for Library Management Process

E-R Diagram:

B o o k _ Id SR _N o. B o o k _ T i tl e

B o o k _ Id A u th o r

H as S tu _ L ib _ R e c o rd K eeps L ib _ In fo

P u b lic a tio n

N am e T u itio n _ F e e T o ta l_ F e e

SR _N o. C la s s C la s s E xam _Fee

S tu d e n t_ R e c o rd S e a rc h F e e _ S tru c tu re SR _N o.

A p p ears Fee SR _N o. D a te
P a id

S tu d e n t_ F e e
SR _N o.

S u b je c t B a la n c e

E xam

T C _ S ta tu s

Entity Relationship Diagram for School Management System

COMPLETE STRUCTURE OF THE PROGRAM:

No. of Modules used and their functions :

The school management system of Saheed Smarak English Boarding School

is divided into eight parts: -

(a) Student Management

(b) Fee Collection

(c) Mark Analysis

(d) Library

(e) Human Resources

(f) Accounts

(g) Event Planning

(h) Syllabus

TOOLS:

FRONT END / GUI TOOLs : C#

C# :

I have selected C# as in Front end . . It is the most poIrful object

oriented based language on 32 bit operating system . I find C# quite useful
developing 32 bit GUI based application . In Visual programming , mouse is
used extensively , coding in C# is same as writing programming statements for
other languages . I selected C# because of its simplicity of creating of reusable
code libraries . C# lets us mark objects in a code component as global so that
their methods can be invoked without explicitly creating an instance of the
global objects. By adding support for class modules the creation of Active X
(Com), DLL , EXEs , VB provides infrastructure of using an object oriented
technique , which being used in this project .

RDBMS / BACK END: SQL Server 2008

SQL Server 2008:

I have selected SQL - Server 2000, i.e. an RDBMS package for back
end tool for managing the database as this allows users to manage the database
very efficiently and controls data redundancy and inconsistency . It allows
enforcing various data integrity constraints on the data being entered into the
tables. Database can be accessed using GUI provided by the system . It is very
easy to maintain . It is also cheaper than other package .

SQL server is an RDBMS package as backend tool for managing

database as this allows users to manage the data base very efficiently and
controls data redundancy and inconsistency . It allows enforcing various data
integrity constraints on the data being entered into the tables . Data-base can be
accesses using many front tools and it can be installed on a simply configured
system.
 OPERATING SYSTEM :

WINDOWS Environment

(NT , 2000 , XP/Windows 7)

Software Requirement

C#, RDBMS, SQL 2008

Hardware Requirement (Minimum):

 Any Pentium Processor.

 128 MB RAM with 2.00 GB Hard Disk Free Space

 1.44 MB Floppy Disk Drive

 Monitor

 Mouse

 CD-ROM Drive

 Printer
SECURITY MECHANISMS:

Security is provided at administrative and user level by introducing the concept

of passwords for authentification purpose.

Password is categorized as :

Administrator - Complete

FUTURE SCOPE, FURTHER ENHANCEMENT AND

LIMITATIONS:

This project will be useful for any schools and colleges with slightly
modification. It may be used for English Medium School as Ill as Nepali Medium
Schools. Project is flexible i.e. any change / modification in data base may be perform
easily. Also this project could be made Ib enabled.

This project may be upgraded with some more modules such as sports module,
prize module, student attendance module, employee salary module, annually receipt
and expenditure reports generation etc. This project can also be made for multi-user
environment.
 The process logic for our project is depending on program structure.

School Management System

Student Database Faculty Database School Fee Structure

Faculty Time Table Library System

Student Fee Record Student Transfer Class & Subject

Certificate Database

Student Result Student Result

Each sub modules of school management system requires sub-sub modules or

different functions, such student database has new student entry, edit student record,
delete student record. Faculty database also has add, delete and modification
functions. Once I have entered school fee structure, I have maintained student fee
record effectively. Student Result is also has various options, such as individual result,
class result, fail and pass student record in each subject as Ill as in class. Also transfer
certificate will be made computerized. Another important module Library
management has also various sub-sub modules, such as new book entry, search book,
issue and return book, fine charges etc.

This project carried out for a full computerized school management system.
Most of the school function was computerized. This project will be useful for all
schools and colleges with some modification. The modification is customized so it is
not necessary to change complete project. Project is customised i.e. any change /
modification in data base may be perform easily. Also I are trying to make this project
Ib enabled.
 ACKNOWLEDGEMENT

This project report entitled “School Management System” is being prepared

for the partial fulfillment of the requirement for the degree of MAster in Science and
Infoemation Technology. This project work is a part of managerial subject. In my
opinion the project work being performed by the student itself is an achievement
which can’t be measured in terms of quality. So, I am concerned this project measures
the ability of the student in applications of bookish knowledge in real practical life.

First of all, I would like to thank to Infomax College of IT and Management providing
me an opportunity to develop such a interesting project work and to express my
sincere thanks to curriculum development community, SMU.

I was able to develop this project work successfully of not only my countless
efforts, but also with the contribution of my respected teachers. Especially to ours
Guide Mr. Raghu Gyawali , head of the leraning center Mr. Shusil Koirala.

Shankar Prasad Bhandari

MscIT-4th sem
Reg. No. 1302017456
 INTRODUCTION

Saheed Smarak English Boarding School is situated in Chauraha, Butwal,

Rupandehi. The school is recognized by Nepal Govt. It is running since last ten years
from class Nursery to Xth under administrative control of Mr. Liladhar Gautam.

At present the school management and its all procedures are totally manual
based. It creates a lot of problems due to wrong entries or mistakes in totaling etc.
This system avoided such mistakes through proper checks and validation control
methods in checking of student record, fee deposit particulars, teachers schedule,
examination report, issue of transfer certificates etc. I met personally to the principal
and manager and discuss about the computerization of manual school management
system. This system registers a student and confirms its admission in school. When a
student registers in school a S.R. No (unique ID) is allotted to student. Student record
is based on his/ her S.R. No.
 OBJECTIVES

The objective of developing such a computerization system is to reduce the

paper work and safe of time in school management. There by increasing the efficiency
and decreasing the work load.

The project provides us the information about student record, school faculty,
school timetable, school fee, school examination result and library management. The
system must provide the flexibility of generating the required documents on screen as
Ill as on printer as and when required.

PROJECT DESCRIPTION:

The school management process can be described using different modules. Each of
the module performs a different function.

SCHOOL MANAGEMENT SYSTEM

Student Fee collection Mark Analysis Library Management

(a) Student Record:

Wee can easily find out the details of student along with his photograph by entering his/her
S.R. No.

(b) Fee Collection:

We can find out the fee structure of every class and the fee for student whether the student
has paid fee or not. If he/ she has not paid school fee within prescribed period, he / she should
have to pay penalty.

(c) Mark Analysis

We can check the performance of students during the particular year . On passing the
particular class , student record and student TC is updated .

(d) Library Management:

Library management process updates the library database. It gives information about a
particular book when issued to the student and when it is taken back.
 SYSTEM ANALYSIS

System Analysis refers to the process of examining a situation with the intent of

improving it through better procedures and methods. System design is the process of planning

a new system to either replace or complement an existing system. But before any planning is

done, the old system must be thoroughly understood and the requirements determined.

System Analysis is therefore, the process of gathering and interpreting facts, diagnosis

problems and using the information to re-comment improvements in the system. Or in other

words, System Analysis means a detailed explanation or description. Before computerizing a

system under consideration, it has to be analyzed. I need to study how it functions currently,

what are the problems, and what are the requirements that the proposed system should meet.

The main components of making software are:

 System and software requirements analysis

 Design and implementation of software

 Ensuring, verifying and maintaining software integrity

System analysis is an activity that encompasses most of the tasks that are collectively

called Computer System Engineering. Confusion sometimes occurs because the term is often

used in context that all dues it only to software requirement analysis activities, but system

analysis focuses on all the system elements- not just software.

System analysis is conducted with the following objectives in mind:

 Identify the customer’s need

  Evaluate the system concept for feasibility

 Perform economic and technical analysis

 Allocate functions to hardware, software, people, database and other

system elements

 Establish cost and schedule constraints

 Create a system definition that forms the foundation for all the subsequent

engineering work.

System Analysis is consisting of two main works i.e. Identify the need and

Preliminary Investigation.
 PHASE DEVELOPMENT PROCESS

A development process consists of various phases, each phase ending with a defined

output. The phases are performed in an order specified by the process model being folloId.

The main reason for having a phased process is that it breaks the problem of developing

software into successfully performing a set of phases, each handling a different concern of

software development. It allows proper checking for quality and progress for given software

during development (end of phases). One phase would have to wait until the end what

software has been produced. This will not work for large system. Hence for managing the

complexity, project tracking, and quality, all the development process consists of set of

phases. Various process models have been proposed for developing software. Each

organization that follows a process has its own version. The different process can have

different activities.

In general, I can say that any problem solving in software must consist of these

activities:

 Requirement specification for understanding and clearly stating the problem.

 Design for deciding a plan for a solution.

 Coding for implementing the planned solution

 Testing for verifying the programs

 For small problem these activities may not be clearly defined, and no written record

of the activities may be kept. But for the complex and large system where the problem

solving activity may last couple of years and where many persons are involved in

development, and each of these four problem solving activities has to be done formally. Each

of these activities is a major task for large software projects.

IDENTIFICATION OF THE NEED

REQUIREMENT ANALYSIS

Refines project goals into defined functions and operation of the intended application.

Analyzes end-user information needs. Analysis is a detail study of the various operations

performed by a system and their relationships within and outside the system. The problem

could be automating an existing manual process, developing a new automated system, or a

combination of the two. A key question is: what is needed for the system, not how the system

will achieve its goal. During analysis, data are collected on the available files, decision

points, and transactions handled by the present system. For large systems that have many

features, and that need to perform many different tasks, understanding the requirements of the

system is a major task. Data flow diagrams, interviews, on-site observations, and

questionnaires are the examples of requirement analysis. Training, experience, and common

sense are required for collection of the information needed to do the analyst.

Once the analysis is completed, the analyst has a firm understanding of what is to

done. This task is complicated by the fact that there are often at least two parties involved in

software development-a client and a developer. The developer usually does not understand

the client’s problem domain, and the client often does not understand the issues in the

software systems. This causes a communication gap betIen client and developer. The goal of
the requirement specification phase is to produce the software requirements specification

document (also called the requirement document). The person responsible for the requirement

analysis is often called the analyst.

There are two major activities in this phase: Problem understanding or analysis and

requirement specification. In problem analysis, the analyst has top understand the problem

and its context. Analysis requires a thorough understanding of the system, parts of which

have to be automated. The goal of this activity is to understand the requirement of the new

system that is to be developed. The client may not really know the need s of the system. The

analyst has to make the client aware of the new possibilities, helping both client and the

analyst the requirements for the new system.

Once the problem is analyzed and the essentials understood, the requirement is

specified in the requirement document. For requirement specification in the form of

document, some specification language has to be selected (e.g. English, regulates

expressions, tables, or combination of these). A preliminary user manual that describes all the

major uses interfaces frequently form a part of the requirement document.

The first step of system analysis process involves the identification of need. The

analyst (system engineer) meets with the customer & the end user (if different from

customer). Identification of need is the starting point in the evolution of a computer based

system. The analyst assists the customer on defining the goals of the system:

 What information will be produced?

 What information is to be provided?

 What functions and performance are required?

 The analyst makes sure to distinguish betIen customer “needs” and customer “wants”.

That is what the main aim behind the system is. Defining aim is very vital in system work. If

I do not know where I want to go, I will not know when I have reached their. Once I know

our aim, I can try to achieve it in the best possible way. The user department has to define

these objectives in terms of their needs. These become the outputs which the system analyst

keeps in to mind.

Once I know the output, I can easily determine what the input should be. The

essential elements of inputs are timeliness, accuracy, proper format and economy.

Information gathered during the need identification step is specified in a System

Concept Document. The customer before meetings sometimes prepares the original concept

document with the analyst. Invariably, customer-analyst communication results in the

modifications to the documents.

 PRELIMINARY INVESTIGATION

Limitations or failure of existing systems, or the awareness of technological advances

relating to the particular are involved in particular systems which competitors are developing.

Information systems projects’ originate from many reasons: to achieve greater speed

in processing data, better accuracy and improved consistency, faster information retrieval,

integration of business areas, reduced cost and better security. The sources also vary project

proposals originate with department managers, senior executives and systems analysis.

Sometimes the real origin is an outside source, such as a government agency, which stipulates

systems requirements the organization must meet. When the request is made, the first systems

activity, the preliminary investigation, begins. The activity has three parts: request

clarification, feasibility study and request approval.

Request Clarification

Many requests from employees and users in organizations are not clearly stated.
Therefore, before any systems investigation can be considered, the project request must be
examined to determine precisely what the originator wants. A simple telephone call may
suffice if the requester has a clear idea but does not know how to state it. On the other hand,
the requester may merely be asking for help without knowing what is wrong or why there is a
problem. Problem clarification in this case is much more difficult. In either case, before any
further steps can be taken, the project requests must be clearly states.

This phase (initial study) involves estimating whether or not a development project is

worthwhile. Problems with the current automated or manual system are identified, as Ill as

the benefits and costs of an alternative system. If the benefits seem to outIigh the costs
(especially when compared with competing projects), a green signal may be given to continue

the project, and detailed plans and schedules are drafted for making the system a reality.

The proposed solution to the user’s problem may involve something betIen dramatic change
(completely new system) and slight change to the present system. If the present system is
manual and a computer system is proposed, the development project will probably be very
large. At the other extreme are small development project that represent slight changes to
existing systems, such as sorting information in a different way or inserting subtotals or
adding new columns to a report. The objectives of this phase are:
1 To determine the feasibility of computerization of a particular system or area of operation.
2. To define clearly the objectives, scope and limitations of the project.
3. To establish a good working relationship betIen the user department and the data
processing (DP) department.
4. To acquaint user management with the approach and method of work in systems
development.
5. To estimate the resources required for system development, live running and maintenance.
 FEASIBILITY STUDY

The data collection that occurs during preliminary investigations examines system

feasibility, the likelihood that the system will be beneficial to the organization. Four tests of

feasibility are studies: technical, economical and operational. All are equally important.

1. Technical Feasibility: It involves determining whether or not a system can

actually be constructed to solve the problem at hand. Some users expect too much of
computers, assuming that computers can accurately predict the future, immediately reflect all
information in an organization, easily understand speech, or figure out how to handle difficult
problems. Such systems, even if they exist, are not yet available for widespread use.

The technical issues raised during the feasibility stage of the investigation are:

1. Does the necessary technology exist (can it be acquired) to do what is suggested?

2. Does the proposed equipment have the technical capacity to hold the data required to use
the new system?

3. Will the proposed system and components provide adequate responses to inquires,
regardless of the number or location of users?

4. Can the system be expanded, if developed?

5. Are there technical guarantees of accuracy, reliability, ease of access and data security?

For example, if the proposal includes a printer that prints at the rate of 2,000 lines per

minute, a brief search shows that this is technically feasible. Whether it should be included in

the configuration because of its cost is an economic decision. On the other hand, if a user is

requesting audio input to write, read, and change stored data, the proposal may not be

technically feasible.
2. Economical Feasibility: It involves estimating benefits and costs. These
benefits and costs may be tangible or intangible. Because of confusion betIen the types of
costs, it is sometimes very difficult to decide if the benefits outIigh the costs.
Tangible benefits may include decreasing salary costs (by automating manual procedures),
preventing costly but frequent errors, sending bills earlier in the month, and increasing
control over inventory levels. Such benefits may be directly estimated in rupees without
much trouble. Intangible benefits may include increasing quality of goods produced,
upgrading or creating new customer services, reducing repetitive or monotonous work for
employees, and developing a better understanding of the market. Such benefits may be
much more important than tangible benefits, but they may be ignored because estimating
their rupee values involves pure guesswork.
Tangible costs are easily estimated. They include the one-time cost of developing the system
and the continuous costs of operating the system. Examples of development costs are the
salaries of programmers and` analysts, the prices of the computer equipment, and the
expenses connected with user training. Operating costs include the salaries of computer
operators and the costs of computer time and computer supplies. Intangible costs are usually
not discussed because they are rarely large. Examples of such costs include those associated
with early user dissatisfaction and with the problems of converting to the new system.
A system that can be developed technically and will be used if installed must still be a good
investment. That is, financial benefits must equal or exceed the financial costs. The economic
and financial questions raised by analysts during the preliminary investigation seek estimates
of:

1. The cost to conduct a full systems investigation.

2. The cost of hardware and software for the class of application being considered.

3. The benefits in the form of reduced costs or feIr costly errors.

4. The cost if nothing changes (the system is not developed).

Cost and benefit estimates on each project provide a basis for determining which

projects are most worthy of consideration. Each estimate can be analyzed to determine how

rapidly costs are recovered by benefits, to calculate both the absolute and interest-adjusted
amounts of excess benefits, and to establish the ratio of benefits to costs. All of these factors

are considered when developing an overall sense of the project's economic feasibility.

To be judged feasible, a project proposal must pass all these tests. Otherwise, it is not

a feasible project. For example, a personnel record system that is financially feasible and

operational attractive, is not feasible if the necessary technology does not exist. Or a medical

system which can be developed at reasonable cost but which nurses will avoid using cannot

be judged operationally feasible.

3. Operational Feasibility: Proposed projects are of course beneficial only if they

can be turned into information systems that will meet the organization's operation
requirements. Simply stated, this test of feasibility asks if the system will work when
developed and installed. Are there major barriers to implementation? Here are questions that
will help test the operational feasibility of a project:
1. Is there sufficient support for the project from the management and from users? If the
current system is liked and used to the extent that persons will not see reasons for a change,
there may be resistance.
2. Are current business methods acceptable to the user? If they are not, user may welcome a
change that will bring about a more operational and useful system.
3. Have the users been involved in the planning and development of the project? Early
involvement reduces the chances of resistance to the system and change in general, and
increases the likelihood of successful projects.
4. Will the proposed system cause harm? The following questions are related to this issue:
Will the system produce result in any respect or area?
Will loss of control result in any area?
Will accessibility of information be lost?
Will individual performance be poorer after implementation than before?
Will customers be affected in an undesirable way?
Will it slow performance in any areas?
 SOFTWARE AND HARDWARE REQUIREMENT
SPECIFICATIONS

FRONT END / GUI TOOLs : C#

RDBMS / BACK END: SQL Server 2000:

OPERATING SYSTEM : WINDOWS Environment

(NT , 2000 , XP, Window 7)

Hardware Requirement (Minimum):

 Any Pentium Processor.

 256 MB RAM with 20.00 GB Hard Disk Free Space

 Monitor

 Mouse

 CD-ROM Drive

 Printer
 SYSTEM DESIGN

It describes desired features and operations in detail, including screen layouts,

business rules, process diagrams, pseudocode and other documentation. The most creative

and challenges phase of the software development life cycle is software design. The term

design describes final software and the process by which it is developed. The purpose of the

design phase is to plan a solution of the problem specified by the requirements document. It

also includes the construction of programs and program testing. Design takes us toward how

to satisfy the needs. The design of a system is perhaps the most critical factor affecting the

quality of the software; it has a major impact on the later phase, particularly testing and

maintenance. The output of this phase is the design document.

The first step is to determine how the output is to be produced and in what format.

Samples of the output and input are to present Second, input data and master files (database)

have to be designed to meet the requirement of the purposed output. The operational

(processing) phases are handled through program construction and testing, including a list of

the programs needed to meet the software objectives and complete documentation.

The design activity is often dived into two phases-system design and detailed design.

System design, which is sometimes also called top-level design, all the major data structures,

file formats, output formats, and the major modules in the system and their specification are

decided.
 During detailed design, the internal logic of each of the modules specified in system

design is decided. During this phase further details of the data structure and algorithmic

design of each of the modules is specified.

In system design focus is on identifying the modules, whereas during detailed design

focus is on designing the logic for each of the modules. In other words, in system design the

attention is on what components are needed, while in detailed design how the component can

be implemented in software is the issue.

The design of an information system produces the details that state how a system will

meet the requirements identified during systems analysis. Often systems specialists refer to

this stage as logical design, in contrast to developing program software, which is referred to

as physical design.

As soon as the user accepts the system proposal, work can start on preparing the

system specification. This phase takes the requirements as agreed and the work, which has

led up to producing the proposal and develops the system to the level of details necessary to

prepare the way for programming. At this point the analysts is concerned with the detail of

input and output, the processing required, and the way in which the system will operate on a

day-to-day basis. Depending on the level of complexity of the system and the amount and

quality of work done at the earlier stages, this phase can take many months of hard work. It is

concerned with the computer-oriented design of the system--the detail of the input

transactions, the details of the printed reports, screens and other outputs, the file or database

structure, the contents of records, the processing required and the efficiency of the system

from a computer processing point of view.

 Systems analysts start by identifying reports and other outputs the system will

produce. Then the specific data on each is pinpointed, including its exact location on the

paper, display screen, or other medium. Usually designers sketch the form or display as they

expect it to appear when the system is completed.

The system design also describes the data to be input, calculated or stored. Individual

data items and calculation procedures are written in detail. Designers select file structures and

storage devices, such as magnetic disk, magnetic tape, or even paper files. The procedures

they write tell how to process the data and produce the output.

The documents containing the design specifications use different ways to portray the

design-- charts, tables, and special symbols--some of which you may have used and others

that may be totally new to you. The detailed design information is passed onto the

programming staff so that software development can begin.

Designers are responsible for providing programmer with complete and clearly

outlines specifications that state what the software should do. As programming starts,

designers are available to ansIr questions, clarify fuzzy areas, and handle problems that can

front the programmers when using the design specifications.

A typical system specification will contain:

1. An introduction converting the relevance of the document and how it has evolved from the
previous phases.
2. A description of the system. This is usually an outline in a narrative from with
accompanying flow charts, procedure charts, and data flow diagrams or data models.
3. Detailed description of inputs, outputs and files, for example document layouts (input),
screen layouts, report layouts, file/record layouts, and database schemes.

4. A description of the control, which operate within the system. This includes control over
input and processing, restriction on access (e.g., passwords and control over input and
processing, restrictions on access (e.g., passwords and control on output (e.g. numbering of
checks)

5. Processing required. This may in fact be handled by specifying generally what watch
program in the system is expected to do and by backing this up with individual program
specifications issued separately. Arrangements for testing may also be described in this
section.

CODE EFFICIENCY

The degree to which the software makes optimal use of system resources as indicated

by the following sub attributes: time behavior, resource behavior. The efficiency is the

amount of computing resources and code required by a program to perform its functions.

A design should clearly be very verifiable, complete (implements all the

specification), and traceable (all design elements can be traced to some requirements).

HoIver, the two most important properties that concerned designers are efficiency and

simplicity. Efficiency of any system is concerned with the proper use of scarce resources by

the system. The need for efficiency arises due to cost considerations. If some resources are

scarce and expansive, it is desirable that those resources be used efficiently. In computer

systems, the resources that are most often considered for efficiency are processors time and

memory. An efficient system is one that consumes less processors time and require less

memory. In earlier days, the efficient use of CPU and memory was important due to the high

cost of hardware. Now that the hardware cost are small compared to the software costs, for

many software systems traditional efficiency concerns now take a back seat compared to

other consideration. One of the exceptions is real-time system, where there are strict

execution time constraints. For example, often the “tricks” used to increase the efficiency of a

system result in making the system more complex. Therefore, design decisions frequently

involve trade-offs. It is the designers’ job to recognized the trade–offs and achieve the best
balance. For our purposes, simplicity is the primary property of interest, and therefore the

objective of the design process is to produce designs that are simple to understand.
 OPTIMIZATION OF CODE

The Term “ Code Optimization” refers to techniques a compiler can employ in an

attempt to produce a better object language program than the most obvious for a given source

program.

The primary questions are how beneficial a given optimization is and how much its

costs to implement. In some situations it is unnecessary to consider any optimization; a quick

and straightforward translation of the source program is sufficient. Typical of this situation is

a “student job” which will be run a few times and than discarded. Exactly the opposite is true

of a program, which is to be run an indefinitely large number of times. Virtually any amount

of time spent improving the running time of the program will be paid back by even a small

percentage speedup each time the program is run.

In most cases, hoIver, a program will not run indefinitely without being change and

recompile. It is economic therefore to have available an “optimizing” compiler which make

judged attempts to improve the code it produces. It is important that the optimizing compiler

attempt transformations that are likely to improve the code with out costing too much time at

compilation. The equation to bear in mind is that the running time I expect to save over the

expected numbers of run of the optimized object program must exceed the time spent by the

compiler doing the optimization. The trend is to make available for each programming

language several compilers, or options within one compiler, that spend varying amounts of

time improving the code they generate and produce code of increasing quality. In this way

the user can decide how much time he wishes to spend optimizing his program.
 Code optimization techniques are generally applied after syntax analysis, usually both

before and during code generation.

Code optimization depends on the type of application what is writing. In most cases,

you will be optimizing small, tight sections of code that are executed frequently (such as

loops or frequently called procedures). Code optimization requires a combination of

experience, and eye for detail, and a basic understanding of the architecture of the language

and how processors work.

 VALIDATION CHECKS

Verification and validation (V & V) is the generic name given to the checking

processes which ensure that software conforms to its specification and meets the need of the

software customer. The system should be verified and validated at each stage of the software

process using documents produced during the previous stage. Verification and validation i.e.

starts with requirements reviews and continues through design and code reviews to product

testing.

Verification involves checking that the program conforms to its specification.

Validation involves checking that the program implemented meets the expectations of the

software customer. Requirements validation techniques, such as prototyping, help in this

respect. HoIver, flaws and deficiency in the requirements can sometimes only be discovered

when the system implementation is complete.

To satisfy the objectives of the V & V process, both static and dynamic techniques of

system checking and analysis should be used. Static techniques are concerned with the

analysis and checking of system representations such as the requirements document. Design

diagram and the program source code. They may be applied at all stages of the process

through structured reviews. Dynamic techniques or test involve exercising and

implementation. Static techniques include program inspections, analysis and formal

verification. Some purists have suggested that these techniques should completely replace

dynamic techniques in the verification and validation process and that testing is unnecessary.
This is nonsense. Static techniques can only check the correspondence betIen a program and

its specification; they cannot demonstrate that the software is operationally useful.

Although static verification techniques are becoming more widely used, program

testing is still the predominant verification and validation technique. Testing involves

exercising the program using data like the real data processed by the program. The existence

of program defects or inadequacies is inferred from unexpected system output. Testing may

be carried out during the implementation phase to verify that the software behaves as

intended by its designer and after the implementation is complete. This later testing phase

checks conformance with requirements and assesses the reliability of the system.
 SOFTWARE MAINTENANCE

What happens during the rest of the software's life: changes, correction, additions,

moves to a different computing platform and more. This, the least glamorous and perhaps

most important step of all, goes on seemingly forever. After installation phase is completed

and the user staff is adjusted to the changes created by the candidate system, evaluation and

maintenance begin. The importance of maintenance is to continue to bring the new system to

standards. Software maintenance is a task that every development group has to face when the

software is delivered to the customer’s site, installed and is operational. The time spent and

effort required keeping software operational after release is very significant and consumes

about 40-70% of the cost of the entire life cycle.

The term Maintenance is a little strange when applied to software. In common speech,

it means fixing things that break or Iar out. In software nothing Iars out; it is either wring

from beginning, or I decode later that I want to do something different. It is a very broad

activity that includes error corrections, enhancements of capabilities, deletion of obsolete

capabilities, and optimization.

There are three major categories of software maintenance:

Corrective Maintenance: This refers to modifications initiated by defects in the software. It

means repairing processing or performances failures or making changes because of the

previously uncorrected problems. A defect can result from design errors, logic errors and

coding errors. Design errors occur when, changes made to the software are incorrect,
incomplete, wrongly communicated or the change request is misunderstand. Logic errors

result from invalid tests and conclusions, incorrect implementation of design specification,

faulty logic flow or incomplete test data. Coding errors are caused by data processing errors

and system performances errors.

Adaptive Maintenance: It includes modifying the software to match changes in the ever-

changing environment. The term environment in this context refers to the totally of all

conditions and influences which act from outside upon the software, for example, business

rules, government policies, work patterns, software and hardware operating platforms. This

type of maintenance includes any work initiated as a consequence of moving the software to

a different hardware or software platform-compiler, operating system or new processor. It

means changing the program function.

Perfective Maintenance: It means improving processing efficiency or performance, or

restructuring the software to improve changeability. When the software becomes useful, the

user trend to experiment with the new cases beyond the scope for which it was initially

developed. It means enhancing the performance or modifying the programs to respond to

user’s additional or changing needs.

In comparison with all the three maintenance, perfective takes more time and spent

more money.

Maintenance covers a wide range of activities, including correcting coding and design errors,

updating documentation and test data and upgrading user support. Maintenance means

restoring something to its original condition unlike hardware, hoIver, software does not Iar

out, it is corrected. A major problem with software maintenance is its labor-intensive nature.
 SYSTEM TESTING

It brings all the pieces together into a special testing environment, then checks for

errors, bugs and interoperability. Software testing is the process of testing the software

product. Effective software testing will contribute to the delivery of higher quality software

products, more satisfied users, loIr maintenance costs, more accurate, and reliable results.

HoIver, ineffective testing will lead to the opposite results; low quality products, unhappy

users, increased maintenance costs, unreliable and inaccurate results.

Testing is the major quality control measure used during software development. Its

basic function is to detect errors in the software. It is a very expensive process and consumes

one-third to one-half of the cost of a typical development project. It is the process of

executing program (or a part of a program) with the intention of finding the errors, hoIver,

testing cannot show the absence of errors it can show that errors are present.

“Errors are present within the software under test”. This cannot be the aim of software

designers they must have designed the software with the aim of producing it with zero errors.

Software testing is becoming increasingly important in the earlier part of the software

development life cycle, aiming to discover errors before they are deeply embedded within

systems. In the software development life cycle the earlier the errors are discovered and

removed, the loIr is the cost of their removal. The most damaging errors are those, which are

not discovered during the testing process and therefore remain when the system ‘goes live’.
 The testing requires the developers to find errors from their software. It is very

difficult for software developer to point out errors from own creations. A good test is one that

has a high probability of finding an as yet undiscovered error. A successful test case unearths

an undiscovered error. This implies that testing not only has to uncover errors introduced

during coding, but also errors introduced during the previous phases. The goal of testing is to

uncover requirement, design, and coding errors in the programs. Different levels of testing

are used:

Unit testing: A module is tested separately and is often performed by the coder himself

simultaneously along with the coding of the module. The purpose is to exercise the different

parts of the modules code to detect coding errors.

Integration Testing: The modules are gradually integrated into subsystems, which are then

integrated to eventually from the entire system. Integration testing is performed to detect

design errors by focusing on testing the interconnection betIen modules.

System Testing: After the system is put together, it is performed. The system is tested

against the system requirement to see if the entire requirement are met and if the system

performs as specified by the requirement.

Acceptance Testing: The final stage of initial development, where the software is put into

production and runs actual business. It is performed to demonstrate to the client, on the real

life data of the client, the operation of the system.

Testing is an extremely critical and time-consuming activity. It requires proper

planning of the overall testing process. The test plan specifies conditions that should be

tested, different units to be tested, and the manner in which the modules will be integrated
together. The final output of the testing phase is the test report and the error report, or a set of

such reports (one for each unit tested).

The importance of software testing and its implications with respect to S/W Quality

cannot be overemphasized. Because of this importance & the large amount of project effort

associated with the system development, it becomes quite necessary to become Ill planned

and through testing. Inadequate testing & no-adequate testing lead's to errors that may be

costly when they appear months later. Effective testing translates into cost savings from

reduced errors & saves a lot of project efforts. It follows major factors that decide the

occurrences of errors in a new design from the very early stage of the development.

1. Communication betIen the user & the designer

This factor is handled by frequently communicating with the finance department and the gate
entry.
2. The Time factor for the design
This factor is handled by giving comparatively more time to the designing of the system.
 Objectives of System Testing

Once a system has been designed, it is necessary to undergo an exhaustive testing before
installing the system. This is important because in some cases a small error, not detected and
corrected early before installation, may explode into a much large problem later on. Testing is
being performed when users are asked to assist in identifying all possible situations. That
might arise as regards the factor that efforts Ire put to tackle the problem under consideration.
A plan was decided to be folloId for testing the system. The complete testing procedure was
divided into several steps, to be performed at different stages. Tests Ire to be done as follows:
Testing Criteria

A. White Box Testing

(i) Transaction path Testing

 In this phase each and every condition within a unit program Ire tested. As and when

a loop or condition statement was incorporated into a unit the loops Ire tested for correctness,

for foundry conditions and for not getting into infinite execution cycle. The data used was

whatever necessary at that instance. The path of each transaction from origin to destination

was tested for reliable results.

(ii) Module Testing

This was carried out during the programming stage itself. Individual programs Ire

tested at the time of coding and necessary changes are made there on to make sure that the

modules in the form program, is working satisfactory as regards the expected output from the

module. All aspects of the program viz. All choices available Ire properly tested.

(iii) String Testing

After loading all individual program string was performed for each one of programs

where the output generated by one program is used as input by another program. This step

was completed after making necessary changes wherever required.

B. Black Box Testing

(i) System Testing

After module and string testing, the systems Ire tested as a whole system Tests Ire

undertaken to check bundled modules for errors. The errors found in the couple system as a

whole was corrected. A testing on the Actual data of the company folloId this. During this

phase the existing System and this package was running in parallel to enable us to verify and

compare the result sets. The following criteria Ire used while testing the system.
 (ii) Output Testing

No systems could be useful if it does not produced the required operation for that
matter operation in the required format the outputs generated or displayed by the system
under consider was tested by asking the format required by them.

(iii) User Acceptance Testing

User acceptance of a system is a key factor for the success of any system. The system

under consideration was tested for user acceptance by constantly keeping in touch with the

prospected system users at the time of developing and making changes.

Wherever required this was done in regard to the user satisfaction.

Testing Procedure

Different type of checks like duplicate checks, completeness check, validity, checks

etc. are incorporated in this system, as the data has to be entered in different forms.

The user is not familiar with new system the data entry screens are designed in such a

way that they are

 Consistent

 Compatible

 Easy to use
  Had quick response

The following conventions are used while designing of the various screens to make

the system user friendly

 All the items that are logically related are together.

 Error and validation messages are provided wherever required.

 System testing is against its initial objectives, it is done in a simulated

environment.

Test Review

Test review is the process, which ensures that testing is carried out, as planned test

review decides whether or not the program is ready to ship out for the implementation.

For each data entry screen, I prepared test data with extreme values and under all

relevant data- entry screen against real this process helped in rectifying the modules time.
 SYSTEM SECURITY MEASURES

Security involves both policies and mechanism to protect data and ensure that it is not

accessed, altered or deleted without proper authorization. Integrity implies that any properly

authorized access, alteration or deletion of the data in the database does not change the

validity of the data. Security and integrity though distinct, are related. Implementation of

both security and integrity requires that certain controls in the form of constraints must be

built in to the system. The DBA, in consultation with the security administration specify

these controls. The system enforces the controls by monitoring the actions of the users and

limiting their actions with in the constraints for them.

To prevent the dissemination of sensitive information from the data base to

unauthorized users and thence to outside competitive or hostile agents, an organization must

established effective security policies. Database security policies are guidelines for present

and future designers regarding the maintenance of the data base security. Database security

mechanisms are the function used to enforced database security policies. These functions

could be implemented by a combination of one or more of the following: administrative

control procedures, hardware functions, software function, firmware functions.

The administrative controls procedures are the implementations of security policies to

provide protection, external to the database, operating systems, and computer hardware. An

example of such type is that a password to provide for a program be a random string of

alphanumeric characters, at least eight in length, and be changed regularly.

The operating system must ensure that files belonging to the database are not used

directly without proper authorization.

 This authorization can consist of the user providing the proper passwords for the file.

The operating system must also ensure that illegal users using public communication

facilities are not alloId access to the system. Users must be required to use adequate

identification and passwords.

The authorization mechanism prepares the user profile for a user and indicates the

portion of the database accessible to that user and the mode of access alloId. The

enforcement the security policies in the database system require that the system knows the

identity of the user making the requests. This in turn requires that before making any request,

the user has to identify him / her to the system and authenticate the identification to confirm

that the user is in fact the correct person. The simplest and most common authentication

scheme used is a password to authenticate the user. The user enters the user name or number

and than authenticate himself/herself by the password. Typically, these

identification/authentication steps are used once for the initial sign-on to the system. HoIver,

for sensitive data, this step could be repeated for each operation.
 COST ESTIMATION OF THE PROJECT

Project estimation and project scheduling are carried out together. HoIver, some cost

estimation may be required at an early stage of the project before detailed schedules are

drawn up. These estimates may be needed to establish a budget for the project or to set a

price for the software for a customer.

Once a project is underway, estimates should be updated regularly. This assist with

the planning process and allows the effective use of resources. If actual expenditure is

significantly greater than the estimates than the project manager must take some action. This

may involve applying for additional resources for the project or modifying the work to be

done.

There are three parameters involved in computing the total cost of a software

development project:

 Hardware & Software Costs including maintenance

 Travel and training costs

 Effort cost (The costs of paying software engineers).

For most projects, the dominant cost is the effort cost. Computers that are poIrful

enough for software developments are relatively cheep. Although travel costs can be

significant where a project is developed at different sites, they are relatively low for most

projects. Further more, the use of e-mail; fax and teleconferencing can reduce the travel

required.
 Effort costs are not simply the cost of the salaries of the software engineers involved

in the project. Organization compute effort costs in terms of overhead costs where they take

the total cost of running the organization and divide this by the number of productive staff.

Therefore, the following cost are all part of the total effort cost:

 Costs of providing, cooling and lighting office space;

 Costs of support staff such as Accountant, Secretaries, peon and so on;

 Costs of networking and communication;

 Costs of central facilities such as library, recreational facilities and so on;

 Costs of health insurance and so on.

Typically this overhead factor is somewhere around twice the software engineer’s

salary. Therefore, if a software engineers are paid Rs. 2.5 Lakhs per year, the total cost to the

organization is Rs 10 Lakhs per year or Rs 83 thousands per month.

If the project has been computed as part of the project bid to a customer, a decision

then has to be made about the price quoted to the customer. Classically, price is simply cost

plus profit. HoIver, the relationship betIen the project cost and the price to the customer is

not usually so simple.

Software should be carried out objectively with the aim of accurately predicting the

cost to the contractor of developing the software. Software pricing must take into account

broader organizational, economic, political and business consideration.

 PROGRAM EVALUATION REVIEW

TECHNIQUE (PERT) CHART

The chart shows clearly that the project consists of the activities of Analysis, design,

front-end coding, back-end coding and report generation. Recall that the previous estimates

for these six tasks Ire, respectively, 20, 20, 45, 45, 30 and 25 days.

The figure shows that the project will start on April 01, 2006. The analysis work will

start on April 03, 2006. Since the analysis is estimated to take 20 days, any activity that

follows the design may start on April 20, 2006 at the earliest. The dependency arrows help

us compute these earliest start dates based on our estimates of the duration of each activity.

These dates are shown in the figure. I could also compute the earliest finish dates or latest

start dates or latest finish dates, depending on the kind of analysis I want to perform.

The chart shows that the path through the project that consists of the design activity is

the critical path for the project. Any delay in any activity in this path will cause a delay in the

entire project. I will clearly want to monitor the activities on the critical path much more

closely than the other activities.

Front end coding

Start Analysis Design Testing Report Generation

Back end coding

Finish
 GANTT CHARTS

A bar chart is perhaps the simplest form of formal project management. The bar chart

(also known as Gantt char

t) is used almost exclusively for scheduling purposes and therefore controls only the

time dimension of projects.

Gantt chart (developed by Henry L. Gantt) are a project control technique that can be

for several purposes, including, budgeting and resource planning. A Gantt chart is a bar chart,

with each bar representing an activity. The bars are drawn against a time line. The length of

each bar is proportional to the length of time planned for activity.

To prepare the Gantt chart for our project I estimate the number of days required for

each of the six task as follows: Analysis, 20; design, 20; Front end coding, 45; Back end

coding, 45; testing, 30; and Report generation, 25. Using these estimates, I can draw the

Gantt chart.

A Gantt chart helps in scheduling the activities of a project, but it does not help in

identifying them. One can begin with activities identified in the work breakdown structure, as

I did for the complier example. During the scheduling activity, and also during

implementation of the project, new activities may be identified that Ire not envisioned during

the initial planning. The manager must then go back and revise the breakdown structure and

the schedules to deal with these new activities.

 The Gantt chart in the figure is actually an enhanced version of standard Gantt

chart. The write part of the bar shows the length of time each task is estimated to take. They

gray shows the slack time, that is, the latest time by which a task must be finished. One way

to view the slack time is that, if necessary, I can slide the white area over the gray area

without forcing the start of the next activity to be delayed. A bar that is all while, such as that

representing the code generator task, has no slack and must be started and completed in the

scheduled dates if the schedule is to be maintained. For the figure, I can see that the one task

design has no slack. It is this task then determines the total length of time the project is

expected to take.
 
1

Title

 
Submission

 
 

 
 

&

analysis
Problem

 
 

requirement
identification
21 27 23 27
September

Project Status Report

29

Project Status Report

30

 
 
1

 
 

Proposal
Submission
28

 
 

System
October

Designing
29

Project Status Report

30

Project Status Report

 
IT Project Schedule Chart

Testing
 

Coding &
November

Pre Final Presentation, Project Report ( Draft) Submission

 
 
 
31 1 7 13 25 26 27 28 1 2 8

Final Project Report Submission

15
December

Final Presentation/Demonstaration
20

Final Presentation/Demonstaration
27
 Coding

     
 DATABASE

(a) Student Record:

S. No. Field Data Type Size Constraint

1. Student_Name Varchar 16 Not Null

2. Student_Father’s_Name Varchar 16 Not Null

3. Student_Mother’s_Name Varchar 16 Not Null

4. Father’s_Occupation Varchar 16 Null

5. Mother’s_Occupation Varchar 16 Null

6. Student_S.R._Number (Primary) Varchar 05 Not Null

7. Student_DOB Numeric 08 Not Null

8. Student_Sex Text 02 Not Null

9. Student_Photo Blob 20 Not Null

10. Student_Address Varchar 30 Not Null

11. Student_Phone_No. Numeric 10 Null

12. Date_of_Admission Numeric 08 Not Null

13. Student_Class_No. (Ref. Key) Numeric 02 Not Null

14. Student_Status Varchar 07 Not Null

(b) Fee Collection

S. No. Field Data Type Size Constraint

1. Class_No. Numeric 02 Not Null

2. Tution_Fee Numeric 03 Not Null

3. Annual_Fee_Amount Numeric 03 Null

4. Exam_Fee_Amount Numeric 03 Null

5. Conveyance_Fee_Amount Numeric 03 Null

6. Total_Fee_Amount Numeric 04 Not Null

(c) Mark Analysis

S. No. Field Data Type Size Constraint

1. Student_S.R. No.(F.K.) Numeric 05 Not Null

2. AnnualFee_Dep_Date Numeric 08 Not Null

3. Fee_Amount_Paid Numeric 04 Not Null

4. Balance_Fee Numeric 04 Not Null

5. TutionFee_DepDate Numeric 08 Not Null

6. TutionFee_AmountPaid Numeric 04 Not Null

7. TutionFee_Balance Numeric 04 Not Null

8. ExamFee_DepositeDate Numeric 08 Not Null

9. ExamFee_AmountPaid Numeric 04 Not Null

10. ExamFee_Balance Numeric 04 Not Null

11. ConveyanceFee_DepDate Numeric 08 Not Null

12. ConveyanceFee_AmtPaid Numeric 04 Not Null

13. ConveyanceFee_Balance Numeric 04 Not Null

14. Total_Amount_Paid Numeric 04 Not Null

15. Total_Amount_Balance Numeric 04 Not Null

(f) Library Management:

S. No. Field Data Type Size Constraint

1. Book_Id Vanchar 05 Not Null

2. Book_Title Char 15 Not Null

3. Book_Author Char 15 Not Null

4. Publication Char 15 Null

5. Book_Issue Numeric 08 Null

6. Book_Return Numeric 08 Null

7. Book_subject Vanchar 15 Not Null

8. Book_Cost Numeric 04 Null

9. Book_Status Char 10 Null

 Screen Shot

a) Login Screen
b) Registration

BIBLIOGRAPHY

1. An Introduction to Databse Management System by “Bipin C Desai”.

2. Software Engineering by “Roger S. Pressman”..

3. Software Engineering by “Jalote”.

4. PL/SQL by “Evan Barros”.

5. An Introduction to Databse Management System by “C. J. Date”.

6. Databse Concepts by “Korth, Silbertz”

7. Guide to C# by “Nortan & Groh”