STUDENT MANAGEMENT SYSTEM

1
PROJECT REPORT
ABSTRACT
Student Management System deals with all kind of student details, academic related reports, college details,
course details, curriculum, batch details and other resource related details too. It tracks all the details of a student from
the day one to the end of his course which can be used for all reporting purpose, tracking of attendance, progress in the
course, completed semesters years, coming semester year curriculum details, exam details, project or any other
assignment details, final exam result; and all these will be aailable for future references too.
!ur program will hae the databases of "ourses offered by the college under all leels of graduation or main
streams, teacher or faculty#s details, batch execution details, students# details in all aspects.
$his program can facilitate us explore all the actiities happening in the college, een we can get to know
which teacher % faculty is assigned to which batch, the current status of a batch, attendance percentage of a batch and
upcoming re&uirements of a batch.
'ifferent reports and (ueries can be generated based of ast options related to students, batch, course, teacher %
faculty, exams, semesters, certification and een for the entire college.
CHAPTER 1
INTRODUCTION
About the project
$he student management system is an automated ersion of manual Student Management System. It can handle
all details about a student. $he details include college details, subject details, student personnel details, academic details,
exam details etc...
In case of manual system they need a lot of time, manpower etc.)ere almost all work is computeri*ed. So the
accuracy is maintained. Maintaining backup is ery easy. It can do with in a few minutes. !ur system has two type of
accessing modes, administrator and user. Student management system is managed by an administrator. It is the job of the
administrator to insert update and monitor the whole process. +hen a user log in to the system. )e would only iew
details of the student. )e can#t perform any changes .$he system has four modules. $hey are
"ollege and 'epartment details
,ogin and subject
Student 'etails
-xam 'etails
CHAPTER 2
MODUES
Student Management System is expected to maintain a number of details. $he needed modules are gien below.
$his table is used to store the details of different department and its category. "ategory specifies the course is
bachelor or master degree. 'epartment gies the arious departments. 'uration specifies the number of semesters.
,ogin and subject
$his module based with the login process and subject details. $he login process specifies the user mode
such as administrator or user. $his module consist of two tables, .dmin ,ogin. It contains the details of login process
and subject details. ,ogin process includes sign in sign up, sign out, change password.
$./,-0 .dmin ,ogin
!"e#$ Co%&tr'"%t&
1ser23ame archar4567 3ot 3ull
8assword archar4567 3ot 3ull
$he table stores the alues like category, department, username, password and priilege. $he priilege specifies
the user mode is administrator or user.
Student 'etails
$his module deals with the student academic details and personnel details. $his module
consists of the tables Student
$./,-0 Student
!"e#$ Co%&tr'"%t&
3ame 9archar:4567 3ot 3ull
8hone2no. number:4;67 3ot 3ull
/ranch 9archar:4;667 3ot 3ull
<ather=s23ame 9archar:4567 3ot 3ull
Mother=s23ame 9archar:4567 3ot 3ull
->Mail 9archar:4567 3ot 3ull
$his table is used to store the details of college like college name, address, phone numbers, fax, email id,
website. $his table is filled at first.
CHAPTER (
SYSTEM STUDY
System study aims at establishing re&uests for the system to be ac&uired, deeloped and installed. It inoles
studying and analy*ing the ways of an organi*ation currently processing the data to produce information. .naly*ing the
problem thoroughly forms the ital part of the system study. In system analysis, preailing situation of problem carefully
examined by breaking them into sub problems. 8roblematic areas are identified and information is collected. 'ata
gathering is essential to any analysis of re&uests. It is necessary that this analysis familiari*es the designer with
objecties, actiities and the function of the organi*ation in which the system is to be implemented.
;.1 S$1'? !< -@IS$I3A S?S$-M
$oday in colleges student details are entered manually. $he student details in separate records are tedious task.
Beferring to all these records and updating is needed. $here is a chance for more manual errors.
;.: 8B!8!S-' S?S$-M
/y deeloping the system we can attain the following facilities.
C -asy to handle and feasible.
C "ost reduction.
C <ast and conenient.
;.; I3$B!'1"$I!3 $! S(, S-B9-B :665
Microsoft S(, Serer :665 is comprehensie, integrated data management and analysis software that enables
organi*ations to reliably manage mission>critical information and confidently run today#s increasingly complex business
applications. S(, Serer :665 allows companies to gain greater insight from their business information and achiee
faster results for a competitie adantage. S(, Serer :665 is the 'ata 8latform leader0
DS(, Serer is the fastest growing 'atabase and /usiness Intelligence endor.
DS(, Serer ships more units than !racle and I/M combined.
DS(, Serer is the E1 !,.8 Serer on the market.
DS(, Serer is more secure than !racle. Since Fuly :66; more than 166 critical !racle database security
ulnerabilities hae been identified, compared to G-B! for S(, Serer for that period.
DS(, Serer is a benchmark leader, with the best price%performance for $8">) 1$/ H ;$/ 4non>clustered7 as
well as best performance for $8">) 1$/.
DAartner :66I worldwide B'/MS market share reports highest growth rate in market share for Microsoft S(,
Serer. +ith :JK growth in market share, growth is almost twice the nearest competitor at 1L.JK growth.
CHAPTER )
SYSTEM ANAYSIS
$he primary goal of the system analyst is to improe the efficiency of the existing system. <or that the study of
specification of the re&uirements is ery essential. <or the deelopment of the new system, a preliminary surey of the
existing system will be conducted. Inestigation done whether the upgradation of the system into an application program
could sole the problems and eradicate the inefficiency of the existing system.
L.1 <-.SI/I,I$? S$1'?
$he initial inestigation points to the &uestion whether the project is feasible. . feasibility is conducted to
identify the best system that meets the all the re&uirements. $his includes an identification description, an aluation of
the proposed systems and selection of the best system for the job. $he re&uirements of the system are specified with a set
of constraints such as system objecties and the description of the out puts. It is then duty of the analyst to ealuate the
feasibility of the proposed system to generate the aboe results. $hree key factors are to be considered during the
feasibility study.
L.1.1 !peration <easibility
.n estimate should be made to determine how much effort and care will go into the deeloping of the system
including the training to be gien to the user. 1sually, people are reluctant to changes that come in their progression. $he
computer initiali*ation will certainly affected the turn oer, transfer and employee job status. )ence an additional effort
is to be made to train and educate the users on the new way of the system.
L.1.: $echnical <easibility
$he main consideration is to be gien to the study of aailable resources of the organi*ation where the software
is to be implemented. )ere the system analyst ealuates the technical merits of the system giing emphasis on the
performance, Beliability, maintainability and productiity.
/y taking the consideration before deeloping the proposed system, the resources aailability of the organi*ation
was studied. $he organi*ation was immense computer facilities e&uipped with sophisticated machines and the software
hence this technically feasible.
L.1.; -conomic <easibility
-conomic feasibility is the most important and fre&uently used method for ealuating the effectieness of the
proposed system. It is ery essential because the main goal of the proposed system is to hae economically better result
along with increased efficiency. "ost benefit analysis is usually performed for this purpose.
CHAPTER *
SYSTEM SPECI!ICATION
5.1 ).B'+.B- B-(1IB-M-3$S
8rocessor 0 8entium I9
Bam
0 51: M/ B.M
)ard 'isk 0 J6 A/ )ard disk
5.: S!<$+.B- B-(1IB-M-3$S
!perating System 0+indowsM%+indowsJ%Microsoft
@8%9IS$.%:66; serer
8latform 0 9isual Studio :665
'atabase 0 Microsoft S(, Serer :665%
!racle16g
.pplication Software 0 Microsoft !ffice :66;
5.; S!<$+.B- <-.$1-BS
5.;.1 ,.3A1.A-S 1S-'0 "E
9isual "E .3et is designed to be a fast and easy way to create .3-$ applications, including +eb serices and
.S8.3-$ +eb applications. .pplications written in 9isual "E are built on the serices of the common language
runtime and take full adantage of the .3-$ <ramework.
It is a simple, elegant, type>safe, object>oriented language recently deeloped by Microsoft for building a wide
range of applications. .nyone familiar with " and similar languages will find few problems in adapting to "E. "E is
designed to bring rapid deelopment to the "NN programmer without sacrificing the power and control that are a
hallmark of " and "NN. /ecause of this heritage, "E has a high degree of fidelity with " and "NN, and deelopers
familiar with these languages can &uickly become productie in "E. "E proides intrinsic code trust mechanisms for a
high leel of security, garbage collection, and type safety. "E supports single inheritance and creates Microsoft
intermediate language 4MSI,7 as input to natie code compilers.
It is fully integrated with the .3-$ <ramework and the common language runtime, which together proide
language interoperability, garbage collection, enhanced security, and improed ersioning support. "E simplifies and
moderni*es some of the more complex aspects of " and "NN, notably namespaces, classes,
enumerations, oerloading, and structured exception handling. "E also eliminates " and "NN features such as macros,
multiple inheritance, and irtual base classes. <or current "NN deelopers, "E proides a powerful, high>productiity
language alternatie.
9isual "E proides prototypes of some common project types, including0
D +indows .pplication.
D "lass ,ibrary.
D +indows "ontrol ,ibrary.
D .S8.3-$ +eb .pplication.
D .S8.3-$ +eb Serice.
D +eb "ontrol ,ibrary.
D "onsole .pplication.
D +indows Serice.
CHAPTER +
SYSTEM DESIGN
System design is the solution to the creation of a new system. $his phase is composed of seeral systems. $his
phase focuses on the detailed implementation of the feasible system. It emphasis on translating design specifications to
performance specification. System design has two phases of deelopment logical and physical design.
'uring logical design phase the analyst describes inputs 4sources7, out puts 4destinations7, databases 4data
sores7 and procedures 4data flows7 all in a format that meats the uses re&uirements. $he analyst also specifies the user
needs and at a leel that irtually determines the information flow into and out of the system and the data resources.
)ere the logical design is done through data flow diagrams and database design.
$he physical design is followed by physical design or coding. 8hysical design produces the working system by
defining the design specifications, which tell the programmers exactly what the candidate system must do. $he
programmers write the necessary programs that accept input from the user, perform necessary processing on accepted
data through call and produce the re&uired report on a hard copy or display it on the screen.
I.1 ,!AI"., '-SIA3
,ogical design of an information system shows the major features and also how they are related to one another.
$he first step of the system design is to design logical design elements. $his is the most creatie and challenging phase
and important too. 'esign of proposed system produces the details of the state how the system will meet the
re&uirements identified during the system analysis that is, in the design phase we hae to find how to sole the
difficulties faced by the existing system. $he logical design of the proposed system should include the details that
contain how the solutions can be implemented. It also specifies how the database is to be built for storing and retrieing
data, what kind of reports are to be created and what are the inputs to be gien to the system. $he logical design
includes input design, output design, and database design and physical design
I.: I381$ '-SIA3
$he input design is the link between the information system and the user. It comprises the deeloping
specification and procedures for data preparation and those steps are necessary to put transaction data into a usable form
for processing data entry. $he actiity of putting data into the computer for processing can be achieed by inspecting
the computer to read data from a written or printed document or it can occur by haing people keying the data directly
into the system. $he design of input focuses on controlling the amount of input re&uired, controlling errors, aoiding
delay, aoiding extra steps and keeping the process simple.
$he system needs the data regarding the asset items, depreciation rates, asset transfer, physical erification for
arious alidation, checking, calculation and report generation.. $he error raising method is also included in the
software, which helps to raise error message while wrong entry of input is done. So in input design the following things
are considered.
+hat data should be gien as inputO
D )ow the data should be arranged or codedO
D $he dialogue to guide the operating personnel in proiding input.
D Methods for preparing input alidations and steps to follow when error occur
D $he samples of screen layout are gien in the appendix.
I.; !1$81$ '-SIA3
"omputer output is the most important and direct information source to the user. !utput design is a process
that inoles designing necessary outputs in the form of reports that should be gien to the users according to the
re&uirements. -fficient, intelligible output design should improe the system#s relationship with the user and help in
decision making. Since the reports are directing referred by the management for taking decisions and to draw
conclusions they must be designed with almost care and the details in the reports must be simple, descriptie and clear
to the user. So while designing output the following things are to be considered.
D 'etermine what information to present
D .rrange the presentation of information in an acceptable format
D 'ecide how to distribute the output to intended receipts
'epending on the nature and future use of output re&uired, they can be displayed on the monitor for
immediate need and for obtaining the hardcopy. $he options for the output reports are gien in the appendix.
I.L 8)?SI"., '-SIA3
$he process of deeloping the program software is referred to as physical design. +e hae to design the process
by identifying reports and the other outputs the system will produce. "oding the program for each module with its logic
is performed in this step. 8roper software specification is also done in this step.
I.5 M!'1,.B '-SIA3
. software system is always diided into seeral sub systems that makes it easier for the deelopment. .
software system that is structured into seeral subsystems makes it easy for the deelopment and testing. $he different
subsystems are known as the modules and the process of diiding an entire system into subsystems is known as
modulari*ation or decomposition.
. system cannot be decomposed into seeral subsystems in any way. $here must some logical barrier, which facilitates
the separation of each module. $he separation must be simple but yet must be effectie so that the deelopment is not
affected.
$he system under consideration has been diided into seeral modules taking in consideration the aboe>mentioned
criteria. $he different modules are
1."ollege and 'epartment details
:. ,ogin and subject
;. Student 'etails
L. -xam 'etails
I.I '.$./.S- '-SIA3
$he oerall objectie in the deelopment of database technology has been to treat data as an organi*ational
resource and as an integrated whole. '/MS allow data to be protected and organi*ed separately from other resources.
'atabase is an integrated collection of data. $he most significant form of data as seen by the programmers is data as
stored on the direct access storage deices. $his is the difference between logical and physical data.
'atabase files are the key source of information into the system. It is the process of designing database files,
which are the key source of information to the system. $he files should be properly designed and planned for collection,
accumulation, editing and retrieing the re&uired information.
$he organi*ation of data in database aims to achiee three major objecties0 >
D 'ata integration.
D 'ata integrity.
D 'ata independence.
$he proposed system stores the information releant for processing in the MS S(, S-B9-B database. $his
database contains tables, where each table corresponds to one particular type of information. -ach piece of information
in table is called a field or column. . table also contains records, which is a set of fields. .ll records in a table hae the
same set of fields with different information. $here are primary key fields that uni&uely identify a record in a table.
$here are also fields that contain primary key from another table called foreign keys.
I.I.1 3!BM.,IG.$I!3
3ormali*ation is a techni&ue of separating redundant fields and braking up a large table in to a smaller one. It is
also used to aoid insertion, deletion and updating anomalies. .ll the tables hae been normali*ed up to the third
normal form. In short the rules for each of the three normal forms are as below.
D <irst normal form
. relation is said to be in 13< if all the under lying domain of attributes contain simple indiidual
alues.
D Second normal form
$he :3< is based on the concept of full functional dependency. . relation said to be in :3< if and only if it is in
13< and eery non>key attribute is fully functionally dependent on candidate key of the table.
D $hird normal form
$he ;3< is based on the concept of transitie dependency. . relation in :3< is said to be in ;3< if eery non>
key attribute is non>transitiely.
CHAPTER ,
"!'I3A
$he goal of the coding phase is to translate the design. $he aim in this phase is to implement the design in the
best possible manner. +ell known code can reduce the testing and maintenance effort. 'uring coding, the focus should
on deeloping programs that are easy to read and understand and not simply on deeloping the programs that are easy
to write. Simplicity and clarity should be stried for during the code phase. .n important concept that help the
understandability of the programs is structured programming. $he program that should be organi*ed as a se&uence of
statements and during execution of the statements is executed in the se&uence gien in the program. $here are many
different criteria for judging of the program, execution time and re&uired memory.
CHAPTER - SYSTEM TESTING AND
IMPEMENTATION
J.1 S?S$-M $-S$I3A
System testing is a critical aspect of Software (uality .ssurance and represents the ultimate reiew of
specification, design and coding. $esting is a process of executing a program with the intent of finding an error. . good
test is one that has a probability of finding an as yet undiscoered error. $he purpose of testing is to identify and correct
bugs in the deeloped system. 3othing is complete without testing. $esting is the ital to the success of the system.
In the code testing the logic of the deeloped system is tested. <or this eery module of the program is
executed to find an error. $o perform specification test, the examination of the specifications stating what the program
should do and how it should perform under arious conditions.
1nit testing focuses first on the modules in the proposed system to locate errors. $his enables to detect errors
in the coding and logic that are contained within that module alone. $hose resulting from the interaction between
modules are initially aoided. In unit testing step each module has to be checked separately.
System testing does not test the software as a whole, but rather than integration of each module in the system.
$he primary concern is the compatibility of indiidual modules. !ne has to find areas where modules hae been
designed with different specifications of data lengths, type and data element name.
$esting and alidation are the most important steps after the implementation of the deeloped system. $he
system testing is performed to ensure that there are no errors in the implemented system. $he software must be executed
seeral times in order to find out the errors in the different modules of the system.
9alidation refers to the process of using the new software for the deeloped system in a lie enironment i.e.,
new software inside the organi*ation, in order to find out the errors. $he alidation phase reeals the failures and the
bugs in the deeloped system. It will be come to know about the practical difficulties the system faces when operated in
the true enironment. /y testing the code of the implemented software, the logic of the program can be examined. .
specification test is conducted to check whether the specifications stating the program are performing under arious
conditions. .part from these tests, there are some special tests conducted which are gien below0
8eak ,oad $ests0 $his determines whether the new system will handle the olume of actiities when the system
is at the peak of its processing demand. $he test has reealed that the new software for the agency is capable of
handling the demands at the peak time.
Storage $esting0 $his determines the capacity of the new system to store transaction data on a disk or on other
files. $he proposed software has the re&uired storage space aailable, because of the use of a number of hard disks.
8erformance $ime $esting0 $his test determines the length of the time used by the system to process transaction
data.
In this phase the software deeloped $esting is exercising the software to uncoer errors and ensure the system
meets defined re&uirements. $esting may be done at L leels
D 1nit ,eel
D Module ,eel
D Integration H System
D Begression
J.1.1 13I$ $-S$I3A
. 1nit corresponds to a screen %form in the package. 1nit testing focuses on erification of the corresponding
class or Screen. $his testing includes testing of control paths, interfaces, local data structures, logical decisions,
boundary conditions, and error handling. 1nit testing may use $est 'riers, which are control programs to co>ordinate
test case inputs and outputs, and $est stubs, which replace low>leel modules. . stub is a dummy subprogram.
J.1.: M!'1,- ,-9-, $-S$I3A
Module $esting is done using the test cases prepared earlier. Module is defined during the time of
design.
J.1.; I3$-AB.$I!3 H S?S$-M $-S$I3A
Integration testing is used to erify the combining of the software modules. Integration testing addresses the
issues associated with the dual problems of erification and program construction. System testing is used to erify,
whether the deeloped system meets the re&uirements. J.1.L B-AB-SSI!3 $-S$I3A
-ach modification in software impacts unmodified areas, which results serious injuries to that software. So the
process of re>testing for rectification of errors due to modification is known as regression testing.
Installation and 'eliery0
Installation and 'eliery is the process of deliering the deeloped and tested software to the customer. Befer
the support procedures. .cceptance and 8roject "losure0
.cceptance is the part of the project by which the customer accepts the product. $his will be done as per the
8roject "losure, once the customer accepts the product, closure of the project is started. $his includes metrics
collection, 8"', etc.
J.: S?S$-M IM8,-M-3$.$I!3
Implementation includes all those actiities that take place to conert from the old system to the new. $he old
system consists of manual operations, which is operated in a ery different manner from the proposed new system. .
proper implementation is essential to proide a reliable system to meet the re&uirements of the organi*ations. .n
improper installation may affect the success of the computeri*ed
system.
J.:.1 IM8,-M-3$.$I!3 M-$)!'S0
$here are seeral methods for handling the implementation and the conse&uent conersion from the old to the
new computeri*ed system.
$he most secure method for conersion from the old system to the new system is to run the old and new system
in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the
new computeri*ed system. $his method offers high security, because een if there is a flaw in the computeri*ed system,
we can depend upon the manual system. )oweer, the cost for maintaining two systems in parallel is ery high. $his
outweighs its benefits.
.nother commonly method is a direct cut oer from the existing manual system to the computeri*ed system.
$he change may be with in a week or with in a day. $here are no parallel actiities. )oweer, there is no remedy in case
of a problem. $his strategy re&uires careful planning.
. working ersion of the system can also be implemented in one part of the organi*ation and the personnel will
be piloting the system and changes can be made as and when re&uired. /ut this method is less preferable due to the loss
of entirety of the system.
J.:.: IM8,-M-3$.$I!3 8,.30
$he implementation plan includes a description of all the actiities that must occur to implement the new
system and to put it into operation. It identifies the personnel responsible for the actiities and prepares a time chart for
implementing the system. $he implementation plan consists of the following steps.
o ,ist all files re&uired for implementation.
o Identify all data re&uired to build new files during the implementation.
o ,ist all new documents and procedures that go into the new system.
$he implementation plan should anticipate possible problems and must be able to deal with them. $he usual
problems may be missing documents; mixed data formats between current and files, errors in data translation, missing
data etc.
CHAPTER .
<IA1B-S
$he different modules, forms and tables in our system are displayed here. P.1
'.$. <,!+ 'I.AB.M
$he following dataflow diagrams show the control flow in our system.
1ser
Serice
<igP.1 ,-9-, 1
'<'
1S-B
SIA3 18
>)
,!AI3
'.$. /.S-
.""-S
9I-+
'.$./.S-
!"/1(02 E1E 2 D!D
P.: S"B--3 S)!$S
P.:.1 Student details
B-AIS$-B-'
M-M/-B
I
1S-B
.'MI3IS$B.$!B
SIA3
!1$
It deals with the details of college and department.
!"/ 12 Stu$e%t $et'"#&
$his form is used to enter the details of the Student.
P.1.: ,ogin and subject
It contains the details of login process and subject details. ,ogin process include sign in sign up ,sign out,
change password.
!"/22 A$3"%"&tr'tor o/"%
$his form is used for sign up process.
!"/(2,ogin
CHAPTER 14
CONCUSION
$he system has been deeloped with much care that it is free of errors and at the same time it is efficient and
less time consuming. $he important thing is that the system is robust. .oid malfunction from outsiders .It goes
through all phases of software deelopment cycle. So product is accurate. .lso proision is proided for future
deelopments in the system.
RESUME
$he current application deeloped is in accordance with the re&uest that has been proided by the organi*ation.
!n regarding the future enhancement, the application can further expanded in accordance with changing scenario.
Since the change in testing and user needs arises fre&uently in certain short interals of time, the application can be
further upgraded to meet the re&uirements that may arise in the far or near future. +ith regarding to the needs that
arises, more and more features can be included by adding it as separate modules and integrate it with the existing
system.
$he html today is a concept, whose main adantage is modularity, which helps us in adding the future needs as
add>on modules to work with the main system which can be done effortlessly instead of rewriting or modifying the
entire application. So the scope of future enhancement is absolutely clear with the concept that is incorporated in the
today that was made used to build the application.
B-<-B-3"-S
www.google.com
www.youtube.com
www.filehippo.com