Académique Documents
Professionnel Documents
Culture Documents
com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
INTRODUCTION AND OBJECTIVES OF THE
PROJECT
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.
PROJECT DESCRIPTION:
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.
SCOPE:
(i) DFDs:
Flow of Data
Store of Data
Level 0 DFD
Level 1 DFD
Level 2 DFD
Student or
Fee Applicant
Depos
it
Admi Book
ssion Fee Reque
Form Depos st
it Issue/
Retur
Valid/
n
Invali
Repor
d
t
School
Managemen
t System
Reports
ADMINISTRATOR
DFD level 0 (Context Level)
DFD Level 1
. 0 2
L i b r a r y
S t u d e n t R e c oM r d a n a g e m e n t
P r o c e s s
1 . 0
S t u d e nS t t u d e n t M aF s e t ee r D F a i tl ae b
A d m i s s i o n a
P r o c e s s
F e e S t r u c t u r e
M a r k s D a t a b a s e
M o n t h l y F
4 . 0 R e c o r d
E x a m i n a t i o n
3 . 0
T C D a t a b a s e M o n t h l y F e e
5 . 0 C o l l e c t i o n
T C R e c o r d
U p d a t i o n
S t u d e n t R e c o r d D
S t u d e n t R e c o r d
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 f i r m
R e g i s t r a t i o nA d m i s s i o n
M ark s
E n t r y R e j e c tC i o o n n f i r m
T C G iv e n b y S c h o o l
F e e D a t a b a s e
A d m i s s i o n D e t a i l
F e e B i l l D e t a i l
F e e S t r u c t u r e
S tu d e n t D e ta il
M a r k s D a t a b a s e
. 31
F e e B i l l
G e n e r a t i o n
1 . 5
S t u d e n t D e t a i l B ill D e ta ils
E x a m i n a t i o n S t u d e n t M a s t e r F i l e
M o n t h l y F e e R
T C D a t a 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 r d M o n t h l y F e e
U p d a t i o n C o l l e c t i o n
Data Flow Diagram Level 2 for School Management Process
N e w B o o k E n t r y
B B o o k D e ta ils
o o k D a t a 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 t a b a s e
B o o k D e ta ils
S t u d e n t D a t a b F in e D e ta ils
a s e
S t u d e nS t t u d e n t
. 1 2 2
D e t a i l D e t a i l
. 2
I s s u e R e t u r n
I s s u e B o Ro ke t u r n B o o k
D e t a i l D e t a i l
I s s u e D a t a b a s e
E-R Diagram:
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
B o o k _ I Sd R _ N o . B o o k _ T i t l e
B o o k _ I d A u t h o r
H a s S t u _ L i b _ R K e ec eo pr d s L i b _ I n f o
P u b l i c a t i o n
N a m e T u i t i o n T _ o F t ea e l _ F e e
S R _ N o . C l a s s C l a s s E x a m _ F e e
S t u d e n t _ R S e e c a o r cr dh F e e _ S t r u S c R t u_ Nr e o .
A p p e a r sF e e S R _ N o . D a t e
P a i d
S t u d e n t _ F e e
S R _ N o .
S u b j e c t B a l a n c e
E x a m
T C _ S t a t u s
0.
1 Student_Address Varchar 30 Not Null
1.
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
1 Student_Phone_No. Numeric 10 Null
2.
1 Date_of_Admission Numeric 08 Not Null
3.
1 Student_Class_No. (Ref. Key) Numeric 02 Not Null
4.
1 Student_Status Varchar 07 Not Null
5.
0.
1 ConveyanceFee_DepDate Numeric 08 Not Null
2.
1 ConveyanceFee_Balance Numeric 04 Not Null
3.
1 Total_Amount_Paid Numeric 04 Not Null
4.
1 Total_Amount_Balance Numeric 04 Not Null
5.
TOOLS:
Environment
Mouse
CD-ROM Drive
Printer
SECURITY MECHANISMS:
Password is categorized as :
Administrator - Complete
- Faculty Display
LIMITATIONS:
PROCESS LOGIC
PROJECT
REPORT
ON
SCHOOL
MANAGEMENT
SYSTEM
1. Approval of Synopsis
2. Certificate of Originality
3. Acknowledgement
4. Introduction
5. Objective
6. System Analysis
7. Identification of Need
8. Preliminary Investigation
9. Feasibility Study
16. Maintenance
22. Database
23. Forms
24. Coding
25. Bibliography
The matter embodied in this project is a genuine work done by the student
and has not been submitted whether to this University or to any other
First and foremost, I would like to thank Mr. Rahul Kumar Mishra (my
for his prodigious, persuasions, painstaking, and attitude, reformative and prudential
Also my thanks to IGNOU study centre In charge, Dr. V.K. Vatsa, who gave
me the idea for this project. I would also thank to Mr. Jitendra Kumar Jindal, Mr.
Deepak Kumar Sharma, lecturers in IFTM and Mr. Ashwani Kumar, Mr. Sunil
Arora, lecturers in study centre IGNOU, for helping me in this project. They helped me
Q. A. Jafri
MCA VI SEM.
042944248
INTRODUCTION
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
PROJECT DESCRIPTION:
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.
We can easily find out the description about the teacher posted
in school .
SYSTEM
ANALYSIS
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
be analyzed. We need to study how it functions currently, what are the problems, and
what are the requirements that the proposed system should meet.
System analysis is an activity that encompasses most of the tasks that are
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 elements
• Create a system definition that forms the foundation for all the
System Analysis is consisting of two main works i.e. Identify the need and
Preliminary Investigation.
defined output. The phases are performed in an order specified by the process model
being followed. The main reason for having a phased process is that it breaks the
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
In general, we can say that any problem solving in software must consist of these
activities:
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 NEED
REQUIREMENT ANALYSIS
Refines project goals into defined functions and operation of the intended
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,
analysis. Training, experience, and common sense are required for collection of the
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 between client and
developer. The goal of the requirement specification phase is to produce the software
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
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
based system. The analyst assists the customer on defining the goals of the system:
“wants”. That is what the main aim behind the system is. Defining aim is very vital in
system work. If we do not know where we want to go, we will not know when we have
reached their. Once we know our aim, we can try to achieve it in the best possible way.
The user department has to define these objectives in terms of their needs. These
Once we know the output, we can easily determine what the input should be.
The essential elements of inputs are timeliness, accuracy, proper format and economy.
Concept Document. The customer before meetings sometimes prepares the original
PRELIMINARY
INVESTIGATION
PRELIMINARY INVESTIGATION
advances relating to the particular are involved in particular systems which competitors
are developing.
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
states.
project is worthwhile. Problems with the current automated or manual system are
identified, as well as the benefits and costs of an alternative system. If the benefits seem
to outweigh 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
The proposed solution to the user’s problem may involve something between
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
way or inserting subtotals or adding new columns to a report. The objectives of this
phase are:
of operation.
3. To establish a good working relationship between the user department and the
systems development.
5. To estimate the resources required for system development, live running and
maintenance.
6. To identify the likely benefits, which should accrue from the introduction
of the system.
FEASIBILITY
STUDY
FEASIBILITY STUDY
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.
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,
figure out how to handle difficult problems. Such systems, even if they exist, are not
The technical issues raised during the feasibility stage of the investigation are:
suggested?
2. Does the proposed equipment have the technical capacity to hold the 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
other hand, if a user is requesting audio input to write, read, and change stored data, the
These benefits and costs may be tangible or intangible. Because of confusion between
the types of costs, it is sometimes very difficult to decide if the benefits outweigh 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
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
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
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
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
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
2. The cost of hardware and software for the class of application being
considered.
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.
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
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 well liked and used to the extent that persons will not see
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
4. Will the proposed system cause harm? The following questions are related to
this issue:
Operational feasibility is a measure of how people are able to work with the
system. For example, a system may require managers to write BASIC, COBOL, or
FORTRAN programs to access data. However, managers probably receive the greatest
help from a system when they can concentrate on the problems to solve rather than on
SOFTWARE
ENGINEERING
PARADIGM
APPLIED
SOFTWARE AND
HARDWARE
REQUIREMENT
SPECIFICATIONS
Environment
Monitor
Mouse
CD-ROM Drive
Printer
SYSTEM DESIGN
SYSTEM DESIGN
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
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
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.
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
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
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
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
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
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
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
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
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 answer questions, clarify fuzzy areas, and handle problems
that can front the programmers when using the design specifications.
accompanying flow charts, procedure charts, and data flow diagrams or data models.
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)
watch program in the system is expected to do and by backing this up with individual
-related procedures.
list all of the tasks to be done, including individual programs, showing the
interrelationship between each task and the planned start and completion date for each
task.
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
8. A back -up plan. This should describe be procedures to be developed for
taking security dumps of files, for ensuring system resilience (e.g., duplexing) and for
running the system at an alternative site in the event of the computer not being available.
It is at this stage that the first reliable estimate of the amount of computer
programming effort required can be produced. Up to this point the estimates are to a
large extent informed guesses and what comes out at the end of this exercise may be
quite frightening compared with the previously available estimates. This is a valid
reason for ensuring that senior management continues to have an approval role at the
CODE
EFFICIENCY
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
specification), and traceable (all design elements can be traced to some requirements).
However, 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
OPTIMIZATION
OF CODE
OPTIMIZATION OF CODE
an attempt to produce a better object language program than the most obvious for a
The primary questions are how beneficial a given optimization is and how much
Typical of this situation is a “student job” which will be run a few times and than
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, however, a program will not run indefinitely without being
compiler which make well 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 we 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
the user can decide how much time he wishes to spend optimizing his program.
Code optimization techniques are generally applied after syntax analysis, usually
cases, you will be optimizing small, tight sections of code that are executed frequently
combination of experience, and eye for detail, and a basic understanding of the
VALIDATION
CHECKS
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
Validation involves checking that the program implemented meets the expectations of
this respect. However, flaws and deficiency in the requirements can sometimes only be
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
inspections, analysis and formal verification. Some purists have suggested that these
validation process and that testing is unnecessary. This is nonsense. Static techniques
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
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.
IMPLEMENTATION
AND
MAINTENANCE
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
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
speech, it means fixing things that break or wear out. In software nothing wears out; it is
either wring from beginning, or we decode later that we want to do something different.
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
misunderstand. Logic errors result from invalid tests and conclusions, incorrect
Coding errors are caused by data processing errors and system performances errors.
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
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
In comparison with all the three maintenance, perfective takes more time and
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, however, software
labor-intensive nature.
SYSTEM
TESTING
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, lower maintenance costs, more accurate,
and reliable results. However, 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
process of executing program (or a part of a program) with the intention of finding the
errors, however, 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
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
are discovered and removed, the lower is the cost of their removal. The most damaging
errors are those, which are not discovered during the testing process and therefore
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.
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
Integration Testing: The modules are gradually integrated into subsystems, which are
then integrated to eventually from the entire system. Integration testing is performed to
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
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.
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
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 well 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
system.
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 were
put to tackle the problem under consideration. A plan was decided to be followed for
testing the system. The complete testing procedure was divided into several steps, to be
Testing Criteria
In this phase each and every condition within a unit program were tested. As and
when a loop or condition statement was incorporated into a unit the loops were 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
were 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 were
properly tested.
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.
After module and string testing, the systems were tested as a whole system Tests
were 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 followed
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 were used while
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.
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.
Testing Procedure
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
• Consistent
• Compatible
• Easy to use
The following conventions are used while designing of the various screens to
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, we 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.
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
firmware functions.
policies to provide protection, external to the database, operating systems, and computer
regularly.
The operating system must ensure that files belonging to the database are not
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 allowed access to the system. Users must be required to
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 allowed. 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. However, 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. However,
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
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
There are three parameters involved in computing the total cost of a software
development project:
For most projects, the dominant cost is the effort cost. Computers that are
powerful 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
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:
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. However, the relationship between the project cost and the
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
product by defining domain architecture and than populating it with structure point.
These structure points are either individual reusable components or packages of reusable
components.
integration, and maintenance cost are nontrivial. Before proceeding with reuse, the
project manager must understand the costs associated with the use of structure points.
Since all structure points have a past history, cost data can be collected for each.
associated with each component in a reuse library is maintained for each instance of
usage. These data can then be analyzed to develop projected costs for the next instance
of reuse.
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 were, 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. We could also compute the
earliest finish dates or latest start dates or latest finish dates, depending on the kind of
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. We will clearly want to monitor the activities on the
SCHOOL MANAGEMENT
Back end coding
SYSTEM
Prepared by: A. G. Finish
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
GANTT CHART
GANTT CHARTS
A bar chart is perhaps the simplest form of formal project management. The bar
chart (also known as Gantt chart) is used almost exclusively for scheduling purposes
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 we 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,
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 we did for the complier example. During the scheduling activity, and also
during implementation of the project, new activities may be identified that were 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.
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, we 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, we can see that the one task design has no slack. It is this task then
DATABASE
6.
1 Student_Father’s_Name Varchar 16 Not Null
7.
1 Student_Mother’s_Name Varchar 16 Not Null
8.
1 Father’s_Occupation Varchar 16 Null
9.
2 Mother’s_Occupation Varchar 16 Null
0.
2 Student_S.R._Number (Primary) Varchar 05 Not Null
1.
2 Student_DOB Numeric 08 Not Null
2.
2 Student_Sex Text 02 Not Null
3.
2 Student_Caste Text 08 Not Null
4.
2 Student_Photo Blob 20 Not Null
5.
2 Student_Address Varchar 30 Not Null
6.
2 Student_Phone_No. Numeric 10 Null
7.
2 Date_of_Admission Numeric 08 Not Null
8.
2 Student_Class_No. (Ref. Key) Numeric 02 Not Null
9.
3 Student_Status Varchar 07 Not Null
0.
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
0.
1 Conveyance_Fee_Amount Numeric 03 Null
1.
1 Total_Fee_Amount Numeric 04 Not Null
2.
6.
1 AnnualFee_Dep_Date Numeric 08 Not Null
7.
1 Fee_Amount_Paid Numeric 04 Not Null
8.
1 Balance_Fee Numeric 04 Not Null
9.
2 TutionFee_DepDate Numeric 08 Not Null
0.
2 TutionFee_AmountPaid Numeric 04 Not Null
1.
2 TutionFee_Balance Numeric 04 Not Null
2.
2 ExamFee_DepositeDate Numeric 08 Not Null
3.
2 ExamFee_AmountPaid Numeric 04 Not Null
5.
2 ConveyanceFee_DepDate Numeric 08 Not Null
6.
2 ConveyanceFee_AmtPaid Numeric 04 Not Null
7.
2 ConveyanceFee_Balance Numeric 04 Not Null
8.
2 Total_Amount_Paid Numeric 04 Not Null
9.
3 Total_Amount_Balance Numeric 04 Not Null
0.
0.
1 Stud_Father’s_Name Char 15 Null
1.
1 Result_Status Char 4 Not Null
2.
1 Result_Year Numeric 4 Not Null
3.
1 TC_Status Boollean 1 Not Null
4.
0.
1 Book_Title Char 15 Not Null
1.
1 Book_Author Char 15 Not Null
2.
1 Publication Char 15 Null
4.
1 Book_Return Numeric 08 Null
5.
1 Book_subject Vanchar 15 Not Null
6.
1 Book_Cost Numeric 04 Null
7.
1 Book_Status Char 10 Null
8.
FORMS
mdiform
frmresult
frmfaculty
frmfee
frmfacultysearch
frmstudent
frmstudentsearch
SUBJECT
TITLES
BOOKS
MEMBERS
EMPLOYEES
OPTIONS
ISSUE
RETURN
RESERVE BOOK
MISSING BOOK
CODING
frmExamResultAdd - 1
Dim r1 As New ADODB.Recordset
Private Sub cmdAdd_Click()
'''''''''''CODE TO INSERT RECORD IN TO DATABASE
Dim rs As New ADODB.Recordset
rs.Open "ExamResult", con, adOpenDynamic, adLockOptimistic
With rs
.AddNew
.Fields("SRNo") = Trim(ComSSRNo.Text)
.Fields("StudNAME") = Trim(txtName.Text)
.Fields("FatherNAME") = Trim(txtFName)
.Fields("CLASSno") = Trim(txtClassNo)
.Fields("ResultStatus") = Trim(txtResultStatus)
.Fields("ResultYear") = Trim(txtResultYear)
.Fields("TCStatus") = Trim(txtTcStatus)
.Update
.Close
End With
MsgBox "SUCESSFULLY ADDED"
''''''''''''''''''''''''''''''''END OF CODE TO INSERT'''''''''''''''''''''''''
Call clearTxtBox(frmExamResultAdd)
Call LCV(ComSSRNo)
End Sub
Private Sub ComSSRNo_Click()
Set r1 = con.Execute("select * from StudentRecord where SSR_Number = '" +
Trim(ComSSRNo.Text) + "'")
txtName.Text = r1.Fields("S_NAME")
txtFName = r1.Fields("F_NAME")
txtClassNo = r1.Fields("CLASS")
Image1.Picture = LoadPicture(r1.Fields("PHOTO"))
r1.Close
End Sub
Private Sub Form_Load()
Call connect
Call LCV(ComSSRNo)
txtResultYear.Text = Format(Date, "yyyy")
End Sub
SCHOOL MANAGEMENT SYSTEM
Prepared by: A. G.
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
www.final-yearprojects.co.cc | www.troubleshoot4free.com/fyp/
Final Year Project's is One place for all Engineering Projects, Presentation, seminar,
summer training report and lot more.
NOTE:-This work is copyright to its Authors. This is only for Educational Purpose.
Private Sub LCV(Combo1 As ComboBox)
Combo1.Clear
Set r1 = con.Execute("select * from StudentRecord order by SSR_Number")
If r1.EOF = True Then
MsgBox "Student List Empty "
Exit Sub
End If
r1.MoveFirst
While Not r1.EOF
Combo1.AddItem r1.Fields("SSR_Number")
r1.MoveNext
Wend
r1.Close
End Sub
frmExamResultDelete - 1
Dim r1 As New ADODB.Recordset
Private Sub cmdAdd_Click()
'''''''''''CODE TO INSERT RECORD IN TO DATABASE
con.Execute ("delete from ExamResult where SRNO = '" +
Trim(ComSSRNo.Text) + "'")
MsgBox "SUCESSFULLY DELETED"
''''''''''''''''''''''''''''''''END OF CODE TO INSERT'''''''''''''''''''''''''
Call clearTxtBox(frmExamResultDelete)
Call LCV(ComSSRNo)
End Sub
Private Sub ComSSRNo_Click()
Set r1 = con.Execute("select * from ExamResult where SRNO = '" +
Trim(ComSSRNo.Text) + "'")
txtName.Text = r1.Fields("StudNAME")
txtFName = r1.Fields("FatherNAME")
txtClassNo = r1.Fields("CLASSno")
txtResultStatus = r1.Fields("ResultStatus")
txtResultYear = r1.Fields("ResultYear")
txtTcStatus = r1.Fields("tcstatus")
r1.Close
End Sub
Private Sub Form_Load()
Call connect
Call LCV(ComSSRNo)
frmAbout - 1
Private Sub cmdOK_Click()
Unload Me
End Sub
Private Sub Form_Load()
'Shape1.BorderColor = vbBlack
End Sub
Private Sub Label2_Click()
End Sub
Private Sub Timer1_Timer()
'If Shape1.BorderColor = vbBlack Then
'Shape1.BorderColor = vbRed
'Else
'Shape1.BorderColor = vbBlack
'End If
End Sub
frmBooks - 1
Dim WithEvents adoPrimaryRS As Recordset
Dim WithEvents adoprimaryrs2 As Recordset
Dim mbChangedByCode As Boolean
Dim mvBookMark As Variant
Dim mbEditFlag As Boolean
Dim mbAddNewFlag As Boolean
Dim mbDataChanged As Boolean
Private Sub DComTitleId_Change()
Dim qunt As Integer
'Set adoPrimaryRS2 = New Recordset
adoprimaryrs2.MoveFirst
adoprimaryrs2.Find ("TitleId" & "='" & DComTitleId & "'")
qunt = adoprimaryrs2.Fields(1)
Combo2.Clear
For i = 1 To qunt
Combo2.AddItem (DComTitleId & "/" & i)
Next i
Combo2.ListIndex = 0
BIBLIOGRAPHY