STUDENT INFORMATION MANAGEMENT SYSTEM

TABLE OF CONTENTS 1.

INTRODUCTION..........................................................................................................................3

1.1 Purpose:..........................................................................................................................................3 1.2 Scope :............................................................................................................................................4 2.

3.

4.

5.

6.

SYSTEM ANALYSIS .....................................................................................................................5

2.1

Existing System: Student Information Management System:- ..................................................5

2.2

Proposed System - Student Information Management System ..................................................5

2.3

Feasibiity !naysis - Stud ent Information Management System ..............................................6

2.3.1

"ec#nica Feasibiity: ........................................................................................................6

2.3.2

Economica Fe asibiity ......................................................................................................6

SYSTEM ARCHITECTURE .........................................................................................................8

3.1

!dmin Modue:- .......................................................................................................................8

3.2

Facuty Modue:- .......................................................................................................................8

3.3

Student Modue:- ......................................................................................................................8

3.$

Ser%ices &iagram of Modues. ..................................................................................................9

3.'

&ata Fo( &iagram:- ..............................................................................................................11

3.)

E*-&I!+*!M.......................................................................................................................14

OVERALL DESCRIPTION ........................................................................................................17

$.1

Product Perspecti%e : ...............................................................................................................17

$.2

Product Functions : .................................................................................................................17

$.3

,ser asses and #aracteristics : ...........................................................................................18

$.$

perating En%ironment : .........................................................................................................18

$.'

onstraints : ............................................................................................................................18

$.)

,se ase Mode : ....................................................................................................................19

TECHNOLOGY OVERVIEW ....................................................................................................27

'.1

P/P.........................................................................................................................................27

'.2

MyS0...................................................................................................................................27

'.3

!pac#e....................................................................................................................................28

'.$

!MPP..................................................................................................................................28

'.$.1

btaining and Instaing !MPP ...................................................................................28

'.$.2

reating a &atabase and Inserting &ata ..........................................................................29

PROJECT DESCRIPTION .........................................................................................................31

).1

Introduction............................................................................................................................31

1

).2

&escription f *oot &irectory ontents .................................................................................32

).3

&escription of &atabase tabes: ...............................................................................................34

7.

SCREENSHOTS...........................................................................................................................39

8.

CODING........................................................................................................................................45

9.

ILIOGRAPHY.........................................................................................................................85

2

1. INTRODUCTION Student Management System is soft(are (#ic# is #epfu for students as (e as t#e sc#oo aut#orities. In t#e current system a t#e acti%ities are done manuay. It is %ery time consuming and costy. ur Student Management System deas (it# t#e %arious acti%ities reated to t#e students. "#ere are mainy 3 modues in t#is soft(are 

!dministrator Modue



Facuty Modue



Student Modue.

In t#e Soft(are (e can register as a facuty as (e as a student for e%ery student t#e aut#entication code and t#e ro no is pro%ided by t#e #ead of t#e department facuty and for t#e registration of a facuty t#e *egistration I& and t#e aut#entication code is pro%ided by t#e administrator t#e institute. In t#is proect an admin can manage t#e facuty and ta4e decision about t#e students i4e deetion of any student admin is aut#ori5ed to create t#e to4en for t#e registration of t#e facuty as same as a facuty is aut#ori5ed for creating to4en for t#e registration of a student. 1.1 P!"#$%&'

"#e obecti%e of S(!)&*( +*,$"-(+$* S/%(&- is to ao( t#e administrator of any organi5ation to edit and find out t#e persona detais of a student and ao(s t#e student to 4eep up to date #is profie .It6 aso faciitate 4eeping a t#e records of students7 suc# as t#eir id7 name7 maiing address7 p#one number7 &8 etc. So a t#e information about an student (i be a%aiabe in a fe( seconds. %era7 it6 ma4e Student Information Management an easier ob for t#e administrator and t#e student of any organi5ation. "#e main purpose of t#is S*S document is to iustrate t#e re9uirements of t#e proect 3

S(!)&*( +*,$"-(+$* S/%(&- and is intended to #ep any organi5ation to maintain and

manage its student6s persona data.

1.2 S0$#& '

it#out a S(!)&*( +*,$"-(+$* S/%(&- 7 managing and maintaining t#e detais of t#e student is a tedious ob for any organi5ation. Student Information system (i store a t#e detais of t#e students incuding t#eir bac4ground information7 educationa 9uaifications7 persona detais and a t#e information reated to t#eir resume .

4

2. SYSTEM ANALYSIS 2.1 E+%(+* S/%(&-' S(!)&*( I*,$"-(+$* M*&-&*( S/%(&-'

System !naysis is a detaied study of t#e %arious operations performed by a system and t#eir reations#ips (it#in and outside of t#e system. /ere t#e 4ey 9uestion is- (#at a probems exist in t#e present system; #at must be done to so%e t#e probem; !na ysis begins (#en a user or manager begins a study of t#e program using existing system. &uring anaysis7 data coected on t#e %arious fies7 decision points and transactions #anded by t#e present system. "#e commony used toos in t#e system are &ata Fo( &iagram7 inter%ie(s7 etc. "raining 7 experience and common sense are re9uired for coection of ree%ant information needed to de%eop t#e system. "#e success of t#e system depends argey on #o( ceary t#e probem is defined7 t#oroug#y in%estigated and propery carried out t#roug# t#e c#oice of soution. ! goo d anaysis mode s#oud pro%ide not ony t#e mec#anisms of probem understanding but aso t#e frame (or4 of t#e soution. "#us it s#oud be studied t#oroug# y by coecting data about t#e system. "#en t#e proposed system s#oud be anay5ed t#oroug#y in accordance (it# t#e needs. System anaysis can be categori5ed into four parts.     

System panning and initia in%estigation Information +at#ering !ppying anaysis toos for structured anaysis Feasibiity study ost< 8enefit anaysis.

In t#e current system (e need to 4eep a number of records reated to t#e student and (ant to enter t#e detais of t#e student and t#e mar4s manuay. In t#is system ony t#e teac#er or t#e sc#oo aut#ority %ie(s t#e mar4 of t#e student and t#ey (ant to enter t#e detais of t#e student. "#is is time consuming and #as muc# cost. 2.2 P"$#$%&) S/%(&-  S(!)&*( I*,$"-(+$* M*&-&*( S/%(&In our proposed system (e #a%e t#e pro%ision for adding t#e detais of t#e students

by t#emse%es. So t#e o%er#ead of t#e sc#oo aut#orities and t#e teac#ers is become ess. !not#er ad%antage of t#e system is t#at it is %ery easy to edit t#e detais of t#e student and

5

deete a student (#en it found unnecessary. "#e mar4s of t#e student are added in t#e database and so students can aso %ie( t#e mar4s (#ene%er t#ey (ant. ur proposed system #as se%era ad%antages       

,ser friendy interface Fast access to database ess error More Storage apacity Searc# faciity oo4 and Fee En%ironment 0uic4 transaction

! t#e manua difficuties in managing t#e student detais in a sc#oo or coege #a%e been rectified by impementing computeri5ation. 2.3 &%+++(/ A*/%+%  S(!)&*( I*,$"-(+$* M*&-&*( S/%(&#ate%er (e t#in4 need not be feasibe .It is (ise to t#in4 about t#e feasibiity of any

probem (e underta4e. Feasibiity is t#e study of impact7 (#ic# #appens in t#e organi5ation by t#e de%eopment of a system. "#e impact can be eit#er positi%e or negati%e. #en t#e positi%es nominate t#e negati%es7 t#en t#e system is considered feasibe. /ere t#e feasibiity study can be performed in t(o (ays suc# as tec#nica feasibiity and Economica Feasibiity. 2.3.1 T&0*+0 &%+++(/' e can strongy says t#at it is tec#nicay feasibe7 since t#ere (i not be muc#

difficuty in getting re9uired resources for t#e de%eopment and maintaining t#e system as (e. ! t#e resources needed for t#e de%eopment of t#e soft(are as (e as t#e maintenance of t#e same is a%aiabe in t#e organi5ation #ere (e are utii5ing t#e resources (#ic# are a%aiabe aready. 2.3.2 E0$*$-+0 &%+++(/ &e%eopment of t#is appication is #ig#y economicay feasibe ."#e

organi5ation needed not spend muc# money for t#e de%eopment of t#e system aready a%aiabe. "#e ony t#ing is to be done is ma4ing an en%ironment for t#e de%eopment (it# an effecti%e super%ision. If (e are doing so7 (e can attain t#e maximum usabiity of t#e corresponding resources .E%en after t#e de%eopment7 t#e

6

organi5ation (i not be in condition to in%est more in t#e organi5ation ."#erefore7 t#e system is economicay feasibe

7

3. SYSTEM ARCHITECTURE In t#is c#apter7 modues of t#e (ebsite are described. It incudes soft(are interfaces7 #ard(are interfaces7 soft(are re9uirements7 #ard(are re9uirements etc. "#is proect is made under an onine proect (#ic# is (or4s as a (ebsite aso it aso use for t#e ad%ertisement of t#e institute it aso incude t#e information pages of t#e institute i4e %ision7 about us7 #istory7 student information page7 syabus for t#e students7 admission information and a notice board for t#e student of institute and as (e as a guest user. 3.1 A)-+* M$)!&'

"#is is t#e first and t#e base modue of t#e proect by t#is modue a admin is pro%ided to t#e proect to manage t#e facuty and student modue. !n admin #a%e t#e aut#ority to add and remo%e t#e facuty7 !dd and deete t#e =otification7 %ie( progress and attendance status of t#e students7 update academic caendar etc. 3.2 0!(/ M$)!&' "#is modue is for t#e facuty members of t#e institute a facuty are get a uni9ue to4en no and a pin for registration by t#e administrator of t#e institute by using t#e registration id and pin t#e facuty (i get registration page after fiing t#at form t#e facuty (i get registered in t#e institute database and t#ey c#oose a pass(ord for ogin to t#eir profie. !fter ogin t#e facuty #a%e aut#ori5ed to ser%ices for t#e student i4e submit attendance of students7 submit mar4s of t#eir subects7 ma4e resut7 add notification for a particuar department7 send mai to indi%idua or a group of student7 aot assignments and proect to t#e students. 3.3 S(!)&*( M$)!&'

!s i4e facuty registration same t#e student (i get a ro no and a pin to registered t#emse%es. !fter enter t#e ro no and pin students are redirect to t#e registration page after submitting t#eir genera detais student (i get a ro no and a pass(ord to ogin t#eir profie. !fter ogin t#e student is abe to %ie( and update t#eir updatabe information i4e mobie no7 emai7 address and profie pictures but students are restricted to update t#eir 4ey detais i4e =ame7 Fat#er =ame7 &ate of birt# in suc# a case in student is abe to (rite a onine appication to t#eir #ead of department for appro%ing to update t#ese detais. Students are abe to %ie( ot#er 8

information reated to t#eir cass i4e notification of t#eir departments7 o(n attendance in indi%idua subects7 pre%ious test mar4s7 and send message to ot#er students. 3.4 S&"+0&% D+"- $, M$)!&%.

ADMIN MODULE

A))U#)(& N$(+,+0(+$*

A))D&&(& 0!(/

D&&(& S(!)&*(

V+&: S(!)&*(% D(

A$( S!;&0(% ($ 0!(/

Figure 1 ( Admin module services)

ACULTY MODULE

A)) D&#(. N$(+,+0(+$*

A)) S(!)&*(%

S!-+( A((&*)*0&

Figure 2 (Faculty odule Services)

9

S!-+( R&%!( D(

A$( A%%+*-&*(%

STUDENT MODULE

V+&: A((&*)*0&

U#)(& C$*(0( D&(+%

V+&: M"<%&&(

Figure ! (Student odule Services)

10

M&%%& ($ C%%-(&%

V+&:S!-+( A%%+-&*(%

3.5 D( $: D+"-'

Registraon Form

Student

Student_registraon_ system Conrmed !e"er

Figure " ( O Level #F#)

11

%dministrator

Re(uest to !ogin #ata$ase

Re(uest to )ie* Re(uest to edit

%dmin &odu'e

Student modu'e ,ro+ess Re(uest to edit Fa+u'ty modu'e

Re(uest to )ie* Re(uest to !ogin

Re(uest to edit

!ogin granted

Fa+u'ty Fa+u'ty Re(uest to )ie*

Figure $ % (1 Level #F#)

12

Re(uest to !ogin

Student

Reg_orm

1.0

-eriy _a)ai'a$i'ty

2.0 Course_ino Course

Student_registraon_ system Conrmed_'e"er

Course_enro''ed

St u

3.0

Student_registraon_ system

Figure &% (2 Level #F#)

13

o n. _i e at ,d /

de nt _i n. o

Stud_data$ase

3.6 ERDIAGRAM 3.6.1

INTRODUCTION'

!n entity>reations#ip mode ?E* mode@ describes inter-reated t#ings of interest in a specific domain of 4no(edge. !n E* mode is composed of entity types ?(#ic# cassify t#e t#ings of interest@ and specifies reations#ips t#at can exist bet(een instances of t#ose entity types. In soft(are engineering an E* mode is commony formed to represent t#ings t#at a business needs to remember in order to perform business processes. onse9uenty7 t#e E* mode becomes an abstract data mode t#at defines a data or information structure t#at can be impemented in a database7 typicay a reationa database. Entity>reations#ip modeing (as de%eoped for database design by Peter #en and pubis#ed in a 1AB) paper. /o(e%er7 %ariants of t#e idea existed pre%iousy7 some E* modeers s#o( super and subtype entities connected by generai5ation-speciai5ation reations#ips7 and an E* mode can be used aso in t#e specification of domain-specific ontoogy. !n E* mode is typicay impemented as a database. In a simpe reationa database impementation7 eac# ro( of a tabe represents one instance of an entity type7 and eac# fied in a tabe represents an attribute type. In a reationa database a reations#ip bet(een entities is impemented by storing t#e primary 4ey of one entity as a pointer or Cforeign 4eyC in t#e tabe of anot#er entity "#ere is a tradition for E*
14

3.6.2

C$*0&#(! )( -$)&'

"#is is t#e #ig#est e%e E* mode in t#at it contains t#e east granuar detai but estabis#es t#e o%era scope of (#at is to be incuded (it#in t#e mode set. "#e conceptua E* mode normay defines master reference data entities t#at are commony used by t#e organi5ation. &e%eoping an enterprise-(ide conceptua E* mode is usefu to support documenting t#e data arc#itecture for an organi5ation. 3.6.3

L$+0 )( -$)&'

! ogica E* mode does not re9uire a conceptua E* mode7 especiay if t#e scope of t#e ogica E* mode incudes ony t#e de%eopment of a distinct information system. "#e ogica E* mode contains more detai t#an t#e conceptua E* mode. In addition to master data entities7 operationa and transactiona data entities are no( defined. "#e detais of eac# data entity are de%eoped and t#e reations#ips bet(een t#ese data entities are estabis#ed. "#e ogica E* mode is #o(e%er de%eoped independent of tec#noogy into (#ic# it can be impemented. 3.6.4

P/%+0 )( -$)&'

ne or more p#ysica E* modes may be de%eoped from eac# ogica E* mode. "#e p#ysica E* mode is normay de%eoped to be instantiated as a database. "#erefore7 eac# p#ysica E* mode must contain enoug# detai to produce a database and eac# p#ysica E* mode is tec#noogy dependent since eac# database management system is some(#at different.

15

/ser_id

%dmin_name

ass*ord %dmin

&anage s 0!(/=*-&

>!+,+0(+$*

Fa+u'ty 0!(/=ID

C$*(0(=N$

E-+

P"$,+&=#+0

&anage s

&anage s

S(!)=*-&

R$=N$

Su$mit %"endan+e

P"$,+&=#+0 P%%:$")

Student D(&=$,=+"(

C$!"%&=ID

a)e C$!"%&=ID

S!;&0(=*-&

S(!)="$ C$!"%&=*-&

T&-#="$=*$

A((&*)0&=)(&

Course

Su$e+t

D!"(+$*

a)e A((&*)0&=S((!%

16

4. OVERALL DESCRIPTION 4.1 P"$)!0( P&"%#&0(+& '

"#e (ebsite S(!)&*( I*,$"-(+$* M*&-&*( S/%(&- is aimed to(ards record ing a considerabe number of student records and needs onine assistance for managing records of students. ebsite s#oud be user-friendy7 D9uic4 to earn6 and reiabe (ebsite for t#e abo%e purpose.

S(!)&*( I*,$"-(+$* S/%(&- is intended to be a stand-aone product and s#oud

not depend on t#e a%aiabiity of ot#er (ebsite. "#e system (i aso #a%e an administrator (#o #as fu-fedged rig#ts (it# regards to performing a actions reated to contro and management of t#e (ebsite.

4.2 P"$)!0( !*0(+$*% '

"#ere are t#ree different users (#o (i be using t#is product: 

!dministrator (#o can %ie( and edit t#e detais of any students  facuty.



Facuty (#o can %ie( and edit t#e detais of students.



Students (#o can %ie( t#eir detais as (e as t#ey can edit t#eir detais.

T& ,&(!"&% (( "& +& ($ (& A)-+*+%("($" "&'



!n !dministrator can ogin into t#e system and perform any of t#e a%aiabe operations.



an enabe


an add  remo%e front page notifications.



an add  remo%e t#e facuty as (e as student.



an edit student information to t#e database. an ma4e searc# for a specific student.



!dd  ,pdate !cademic caendar.



!ocate t#e subects to t#e facuty. 17



an access a t#e detais of t#e student.

"#e features t#at are a%aiabe to t#e facuty are:

an submit attendance of t#e students.

 

an upoad #is<#er image. an Submit students exam or "est mar4s.



an !ppro%e t#eir ea%e appication



an !dd  *emo%e &epartmenta =otifications.



,pdate sef Profie &etais

"#e features t#at are a%aiabe to t#e Students are:

an %ie( t#eir profie.



ie( t#eir attendance in indi%idua subects.



ie( t#eir test or exam mar4s.



,pdate t#eir basic contact detais.



Send or %ie( t#e message to t#e cassmates.



ie( t#e departmenta notification (#ic# t#ey are beongs to.



Submit ea%e appication or ot#er appication.

4.3 U%&" C%%&% *) C"0(&"+%(+0% '

"#ere are mainy t#ree 4inds of users for t#e product. "#e users incude:  !dministrator  

Facuty Student

4.4 O#&"(+* E*+"$*-&*( '

"#e product can run on any bro(ser ?preferabe to use #rome bro(ser@.

4.5 C$*%("+*(% '

E%ery user must be comfortabe using computer.

18

! operations are in Engis# so user must #a%e basic 4no(edge of Engis#.

4.6 U%& 0%& -$)& '

19

U%& C%& M$)& A)-+*+%("($"' *esponsibe for managing facuty records.

1. 

ogin into t#e (ebsite



!dd < *emo%e =otification



!dd < *emo%e facuty

 

!ocate Subects to facuty. ,pdate !cademic aendar



ie( progress of t#e students.



Searc# student detais o

&ispay student detais

o

Enabe<&isabe student



0!(/ : *esponsibe for managing Students records. Submit attendance of t#e students.



Submit Mar4s of t#e students.



!dd<*emo%e departmenta notifications.



!ppro%e ea%e appications of t#e students.



%ie(  update profie of sef.

2.

G S(!)&*(' /as t#e access rig#ts to %ie( and edit t#eir persona detais.

3. 

ogin into t#e (ebsite .



&ispay student detais



Edit t#eir detais .



ie( t#eir attendance .



ie( t#eir resuts .



Message to cassmates.



ie( departmenta notifications.



,poad t#eir images.



,poad t#eir resumes.

20



A%%!-#(+$*% ? )&#&*)&*0+&%

·

!dministrator is created in t#e system aready.

·

*oes and tas4s are predefined.



S#&0+,+0 R&@!+"&-&*(% '

U%& C%& R&#$"(%

1A)-+*+%("($"' *esponsibe for managing student detais. U%&0%&' ogin into t#e (ebsite G$ +* 0$*(&(' +ain access to t#e (ebsite "+&, D&%0"+#(+$*' "#is use case is used (#en t#e administrator (ants to access t#e

(ebsite to enabe
use case to begin. %+0 $:'

"#e ebsite prompts t#e administrator for t#e user name and pass(ord. "#e !dministrator enters t#e user name and pass(ord. "#e ebsite %erifies t#e pass(ord and sets t#e user6s aut#ori5ation. "#e !dministrator is gi%en access to t#e ebsite to perform #is tas4s. A(&"*(+& $:'

"#e administrator enters in%aid username and pass(ord t#en #e (i not be ao(ed to enter t#e (ebsite. P$%( 0$*)+(+$*%' "#e (ebsite state is unc#anged by t#is use case.

21

U%& C%& R&#$"( L$+* +*($ (& :&%+(&

U%& C%& ' &ispay student detais G$ +* 0$*(&(' ie( t#e detais of a student "+&, D&%0"+#(+$*' "#is use case is used (#en t#e administrator (ants to %ie(

t#e faciitate t#e ser%ices to t#e facuty and %ie( t#e status of t#e students. P"&0$*)+(+$*%' "#e !dministrator must be ogged into t#e system in order for

t#is use case to begin "#e detais of t#e student must pre-exist in t#e database "#e student id must be entered correcty. %+0 $:'

"#e !dministrator ogs onto t#e System. 

=otification Ser%ice :o

!dmin can add t#e notification by t#e #ep of notification add page in t#is page t#e admin ust add t#e tite of t#e notification and t#e upoad t#e reated pdf or document fie of t#at notification.

o

"#is notification is %isibe on t#e #omepage.

o

"#ese notifications are accessibe by a t#e user (#o %isited on t#e (ebsite.

o



!dmin can easiy deete t#e notification.

Facuty management :o

In t#is section an admin can manages t#e facuty .

22

o

!fter ogin admin can generate to4en for t#e facuty. In tis to4en t#e admin aot a registration id and t#e pin reated (it# t#e facuty name.

o



!fter generation of t#e to4en page is redirect to t#e admin page.

,pdate !cademic aendar:o

In t#is section admin can update t#e academic caendar #e can add any #oiday and t#e ot#er e%ents to t#e caendar (#ic# is accessibe by t#e students and t#e facuty of t#e institute.

P$%( 0$*)+(+$*%' "#e to4en is generated for t#e facuty signup and t#e updated caneder is %isibe to t#e students as (e as t#e facuty members. C%& D+"-%.

!ogin ai's

!ogin to *e$site

%ddremo)e o+aon

#ata$se u,dated

23

. 0!(/ ' *esponsibe for managing student detais. U%&0%&' ogin into t#e (ebsite G$ +* 0$*(&(' +ain access to t#e (ebsite "+&, D&%0"+#(+$*' "#is use case is used (#en t#e facuty (ants to access t#e (ebsite

to enabe
to begin. %+0 $:'

"#e ebsite prompts t#e facuty for t#e user name and pass(ord. "#e facuty enters t#e user name and pass(ord. "#e ebsite %erifies t#e pass(ord and sets t#e user6s aut#ori5ation. "#e facuty is gi%en access to t#e ebsite to perform #is tas4s. A(&"*(+& $:'

"#e facuty enters in%aid username and pass(ord t#en #e (i not be ao(ed to enter t#e (ebsite. P$%( 0$*)+(+$*%' "#e (ebsite state is unc#anged by t#is use case.

24

U%& C%& R&#$"( L$+* +*($ (& :&%+(&

U%& C%& ' &ispay Facuty ser%ices page G$ +* 0$*(&(' ie( t#e detais of a student "+&, D&%0"+#(+$*' "#is use case is used (#en t#e facuty (ants to %ie( t#e faciitate

t#e ser%ices to t#e facuty and %ie( t#e status of t#e students. P"&0$*)+(+$*%' "#e facuty must be ogged into t#e system in order for t#is use case

to begin "#e detais of t#e student must pre-exist in t#e database "#e student id must be entered correcty. %+0 $:'

"#e facuty ogs onto t#e System. 

Submit !ttendance :o

Facuty can submit t#e attendance for e%ery student in subect (#o is aotted by t#e administrator.

o

For submit attendance facty #as to na%igate t#e submit attendance page.

o

o

"#ere is t(o (ay a%aiabe to submit t#e attendance. 

Submit attendance in ist %ie(.



0uic4 attendance submit mode.

"o submit attendance in ist %ie( facuty #a%e to seect t#e cass and t#en t#e subect.

25

o

"#en page is na%igated to submit attendance page in t#is page t#e ist of t#e student is %isibe (#ic# are beongings to seected subect.

o

"o sa%e a student as a present ust tic4 t#e c#ec4box and to absent t#e student ust unc#ec4 t#e c#ec4box.



Submit mar4s: o

o



"o submit t#e mar4s for student facuty #as to na%igate t#e page by c#oosing submit mar4s option of menu from t#e facuty page. "#ere are t(o (ay to submit mar4s of students. 

Submit mar4s to eac# student in ist mode.



Submit mar4s by upoading t#e exce fie.

!dd<*emo%e =otification. o

Facuty can add t#e notification by t#e #ep of notification add page in t#is page t#e facuty ust add t#e tite of t#e notification and t#e upoad t#e reated pdf or document fie of t#at notification.

o

"#is notification is %isibe on t#e #omepage.

o

"#ese notifications are accessibe by a t#e user (#o %isited on t#e (ebsite.

o



Facuty can easiy deete t#e notification.

Student management :o

In t#is section an admin can manages t#e Student.

o

!fter ogin admin can generate to4en for t#e student. In tis to4en t#e facuty aot a *o =o and t#e pin reated (it# t#e student name.

o

!fter generation of t#e to4en page is redirect to t#e facuty page.

P$%( 0$*)+(+$*%' "#e to4en is generated by t#e facuty is used by students to signup t#e students. !nd t#e databse of t#e mar4s tabe and attendance tabe is updated.

26

5. TECHNOLOGY OVERVIEW

"#e tec#noogy seected for impementing Student Information Management System is P/P
P/P is a genera-purpose scripting anguage t#at is especiay suited to ser%er-side (eb de%eopment (#ere P/P generay runs on a (eb ser%er.P/P code is embedded into t#e /"M source document.!ny P/P code in a re9uested fie is executed by t#e P/P runtime7 usuay to create dynamic (eb page content.It can aso be used for command-ine scripting and cient-side +,I appications. P/P can be depoyed on many (eb ser%ers and operating systems7 and can be used (it# many reationa database management systems ?*&8MS@. It is a%aiabe free of c#arge7 and t#e P/P +roup pro%ides t#e compete source code for users to buid7 customi5e and extend for t#eir o(n use.

5.2 M/S>L

MyS0 is a reationa database management system ?*&8MS@

1J

t#at runs as a ser%er

pro%iding muti-user access to a number of databases. MyS0 is a popuar c#oice of database for use in (eb appications and is an open source product. "#e process of setting up a MyS0 database %aries from #ost to #ost7 #o(e%er (e (i end up (it# a database name7 a user name and a pass(ord. 8efore using our

27

database7 (e must create a tabe. ! tabe is a section of t#e database for storing reated information. In a tabe (e (i set up t#e different fieds (#ic# (i be used in t#at tabe. reating a tabe in p#pMy!dmin is simpe7 (e ust type t#e name7 seect t#e number of fieds and cic4 t#e Dgo6 button. (e (i t#en be ta4en to a setup screen (#ere you must create t#e fieds for t#e database.!not#er (ay of creating databases and tabes in p#pMy!dmin is by executing simpe S0 statements.e #a%e used t#is met#od in order to create our database and tabes.

5.3 A#0&

"#e !pac#e /""P Ser%er is a (eb ser%er soft(are notabe for paying a 4ey roe in t#e initia gro(t# of t#e ord ide eb. In 2GGA it became t#e first (eb ser%er soft(are to surpass t#e 1GG miion (eb site miestone. ! pac#e is de%eoped and maintained by an open community of de%eopers under t#e auspices of t#e !pac#e Soft(are Foundation. Since !pri 1AA) !pac#e #as been t#e most popuar /""P ser%er soft(are in use. !s of =o%ember 2G1G !pac#e ser%ed o%er 'A.3)K of a (ebsites and o%er )).')K of t#e first one miion busiest (ebsites.

5.4 AMPP

!MPP is a sma and ig#t !pa c#e distribution containing t#e most common (eb de%eopment tec#noogies in a singe pac4age. Its contents7 sma si5e7 and portabiity ma4e it t#e idea too for students de%eopi ng and testing appicati ons in P/P and MyS0. !MP P is a%aiabe as a free do(noad in t(o specific pac4ages: fu and ite. #ie t#e fu pac4age do(noad pro%ides a (ide array of de%eopment toos7 !MPP ite contains t#e necessary tec#noogies t#at meet t#e ntario S4is ompetition standards."#e ig#t %ersion is a sma pac4age containing !pac#e /""P Ser%er7 P/P7 MyS07 p#pMy!dmin7 penss7 and S0ite.

5.4.1

O(+*+* * ) I* %(+*  AMPP

!s pre%iousy mentioned7 !MPP is a free pac4age a%aiabe for do(noad and use for %arious (eb de%eopment tas4s. ! !MPP pac4ages and add-ons are

28

distributed t#roug# t#e !pac#e Friends (ebsite at t#e address: #ttp:<<(((.apac#efriends.org<. nce on t#e (ebsite7 na%igate and find t#e indo(s %ersion of !MPP and do(noad t#e sefextracting LIP arc#i%e. !fter do(noading t#e arc#i%e7 run and extract its contents into t#e root pat# of a #ard dis4 or ,S8 dri%e. For exampe7 t#e extract pat# for a oca indo(s instaation (oud simpy be :. If extracted propery (e (i notice a ne( xampp directory in t#e root of your instaation dis4. In order to test t#at e%eryt#ing #as been instaed correcty7 first start t#e !pac#e /""P Ser%er by na%igating to t#e xampp directory and cic4ing on t#e apac#eNstart.bat batc# fie. =ext (e (i test if t#e ser%er is running correcty by opening an internet bro(ser and typing #ttp:<<oca#ost< into t#e address bar. If configured correcty7 (e (i be presented (it# a screen simiar to t#at of t#e one beo(.

Figure 2 ('A Slas* Screens*ot)

In order to stop a !pac#e processes (e do not cose t#e running termina appication7 but instead run anot#er batc# fie in t#e xamppite directory caed apac#eNstop.bat.

5.4.2

C"&(+*  D( %& *) I*%&"(+* D(

=o( t#at (e #a%e run and tested !pac#e and P/P7 t#e next step is running MyS0 and creating a database and tabe (#ic# (i #od information to be used by our (ebsite. In order to start MyS07 na%igate to t#e xampp directory and run t#e mys9Nstart.bat batc# fie."#e !MPP pac4age contains an appication caed p#pMy!dmin (#ic# ao(s de%eopers to administer and maintain MyS0 databases .e (i be using p#pMy!dmin to create a database and tabe7 and enter test data. 8efore testing p#pMy!dmin7 ma4e sure t#at bot# !pac#e and MyS0 are running by opening t#eir respecti%e batc# fies: apac#eNstart.bat and mys9Nstart.bat. !ong (it# !pac#e and MyS0 running in t#e bac4ground7 (e type #ttp:<<oca#ost
Figure ! (*yAdmin Start age)

"#e first step (it# p#pMy!dmin running is creating a ne( database.e create a ne( database by directy executing S0 statements as s#o(n beo(."#e successfu execution of t#e s9 9uerry creates a database Dsims6 (it# tabes in it."#e tabes are adminNogin and studentNinfo. e aso inserted %aues in t#e admin tabe."#e screens#ot beo( s#o(s t#e successfu execution of t#e 9uery t#us creation of a database named student.

6. PROJECT DESCRIPTION

6.1 I*("$)!0(+$*

Student Information Management System can be used by education institutes to maintain t#e records of students easiy. !c#ie%ing t#is obecti%e is difficut using a manua system as t#e information is scattered7 can be redundant and coecting ree%ant information may be %ery time consuming. ! t#ese probems are so%ed using t#is proect "#e directory structure of t#e proect is as foo(s:

6.2 D&%0"+#(+$* O, R$$( D+"&0($"/ C$*(&*(%

0%%'it contains t#e a css code for t#e pages of t#e (ebsite. D(1' it contains t#e data fies (#ic# #eps to side s#o( of #ome page. D$0%' it contains a t#e documents (#ic# are reated to t#e notification upoaded by t#e admin

or facuty. E*+*&1' it contains t#e css and Oa%aScript code (#ic# #eps to running t#e sides#o( of #omepage. I-&%' it contains a t#e images i4e ogo7 menuNicon7 and t#e profie picture upoaded by t#e students or facuty. A))=,0!(/.##' t#is page contains t#e code (#ic# #eps (#ic# na%igate t#e to4en generation page. A))=*$(&%.## ' it t#is page code containing t#e information (#ic# is used to upoad t#e notification for #ome page. A))=%(!)&*(=&0&.##' t#is page contains t#e code for t#e upoading to4en exce fie for t#e student registration. A))=%(!).## ' in t#is page t#e code is a%aiabe (#ic# s#o( t#e option for c#oosing t#e option for (#ic# mode is seected for to4en generation. A((&*=+*)+.## ' In t#is page code contain t#e to4en generation for any singe student. C$**&0(+$*.## : t#is p#p fie contain t#e connection page (#ic# contains t#e caonnection code for connecting t#e database. 0!(/=$-&.##' t#is page s#o(s t#e ser%ices (#ic# is a%aiabe for t#e facuty. L$+*=*)&".## ' t#is page is used to aut#enticate t#e user id and pass(ord for admin7 student and facuty it redirect t#e page according to t#e user type. L$$!(.##' t#is fie contains t#e code for cosing t#e session and disconnect t#e database. M+*.##' t#is is t#e main #ome page of (ebsite t#is page contains tite bar7 menu bar7 notification area7 picture gaery7 ogin area. N$(&%=)&&(&' t#is fie is used to deete t#e notification (#ic# is upoaded by t#e admin.

N$(+,/.##' t#is page s#o(s a t#e notification (#ic# is acces by t#e admin to %ie( and update t#e notification. S+*!#=*)&"' t#is fie used to sa%e t#e registration data on &atabse. S(!)=#&' t#is page s#o( a t#e ser%ices a%aiabe for t#e students. S(!)=%+*!#.## ' t#is page contains t#e registration form for t#e students. S(!)=%+*!#=*)&"' t#is fie is used to sa%e t#e student information to studNinfo tabe. S(!)=($<&*=&*.##' t#is fie contains t#e code for generation t#e to4en for students. T$<&*=*)&".## 't#is page contains t#e code for sa%e t#e to4ens data on databse.

6.3 D&%0"+#(+$* $, D(%& (&%' T&1' A)-+* (&

A)-+*' N-&' name of t#e admin U%&"=+)' user id for ogin t#e admin page. P%%:$")' pass(ord for aut#enticate and redirect t#e admin page. T&2' ,0!(/=)&(+%

0!(/=)&(+%' R&=+)' id for ogin t#e facuty. *-&: first name of facuty L*-&' ast =ame of facuty. S&' Specify t#e gender of facuty. M$+&' mobie no of t#e facuty. E-+' emai id of t#e facuty.

A))"&%%' address of t#e facuty. C+(/' city of t#e facuty. >!+,+0(+$*' #ig#est 9uaification of t#e facuty. (&"=*-&' fat#er name of t#e facuty. P%%:$")' pass(ord contains t#e pass(ord for t#e ogin to facuty. S&0=@!&%' it contains t#e 9uestion (#ic# is seected by t#e facuty (#ie signup. S&0=*%' in caontains t#e ans(er of security 9uestion (#ic# again #ep to reco%er t#e pass(ord

T&3',0!(/=($<&*

0!(/=($<&*' 0!(/*-&' *-& $, (& ,0!(/ *) !($-(+0/ ,&(0&) +*($ %+*!# #&. P+*' 4 )++( #+* ($ !(&*(+0(& ($<&*. =+)' "&+%("(+$* +) ,$" (&* ,0!(/.

T&4' +-&%'

I-&%' R&=+)' reg-id is t#e id of student or facuty (#ic# is reated to t#e student6s images.

P%%#$"(' name of profie pic. S+*' fie name of student6s signature. D$01' fie name of student6s doc. D$02' fie name of student6s doc.

T&5' -011B%!;&0( (&

S!;&0( (&'

"#is tabe automaticay inserted into databse by t#e name of subect (#ene%er t#e admin aocate a ne( subect.and after it is used to sa%e t#e attendance of t#e student. R&=+)' regNid of t#e student referenced to studNinfo tabe6s primary 4ey. S"=*$' temporary ro no od students. D(&' date of attendance. S((!%' status of student6s attendace sa%es HQ for present =Q for absent.

T&6' %(!)=+*,$

S(!)=+*,$ ' R&=+)' primary 4ey and t#e regid is aso used by t#e student to ogin into (ebsite. *-&: first name of student. L*-&: ast name of t#e student. D$' date of birt# of t#e student M$+&' mobie no of t#e student E-+' emai of t#e student. A))"&%% address of t#e student. C$!"%&' course of t#e student . Y&"' year of course. (&"=*-&' fat#er6s name of t#e student. C+(/' city of t#e student. S&' specify t#e gender of student. P%%:$")' pass(ord for ogin into (ebsite. S&0=@!&%' 9uestion c#oosed by t#e student (#ie signup.

S&0=*%' ans(er of security 9uestion. T&8' S(!)=($<&*

S(!)=($<&*' S(!)=*-&' name of t#e student (#ic# is automaticay into signup page. P+*: $ digit pin code to aut#enticate t#e to4en. S=+)' ro no of t#e student. T&9' !#$)&)=,+&%

U#$)&)=,+&%' +&=*-&' name of t#e fie upoaded for t#e notification. U%&"=+)' userNid of t#e user (#o upoad t#e notification. T+(&' tite of t#e notification.

7. SCREENSHOTS

Figure " (+ome age)

Figure $ (Admin age)

Figure & (No,-ca,on uload age)

Figure . (No,-ca,on #elete age)

Figure / (To0en enera,on age)

Figure  (3aculty Services age)

Figure 16 (a4endance su5mission age)

Figure 11 (a4endance su5mit)

Figure 12 (si ngle To0en enera,on 3or student)

Figure 1! (7load To0ens via e8cel age)

8.

CODING

HOMEPAGE M+*.##

R;p#p incude connection.p#pT sessionNstart?@T ;U

R#tmU RtiteU

/omepage R
Rin4 reWCstyes#eetC typeWCtext
Rdi% cassWCbannerCU Rimg srcWCimages<ogo.pngC #eig#tWC1)GpxC (idt#WC1)GpxCU R
R
R<#1U R#3U !n !utonomous onstituent Institute of &r. !.P.O. !bdu Yaam "ec#nica ,ni%ersity7 ,.P.7 uc4no(R<#3U

R
Ru idWCmbmcpebuNtabeC cassWCmbmcpebuNmenuist cssNmenuCU RiURdi% cassWCbuttonbg gradientNbutton gradient$XC styeWC(idt#: B1pxTCURa #refWCmain.p#pCcassWCbuttonN1CU/omeR
RiURa titeWCCUPubicationR
Ri cassWCfirstNitemCURa titeWCCUM."ec#.R
R
Rdi% cassWCnotifyNpaneCU R;p#p Zs9Wmys9N9uery ?Cseect [ from upoadedNfies (#ere userNidWadminGG1C@or die?mys9Nerror?@@TT (#ie?ZresWmys9Nfetc#Narray?Zs9@@\ Zpat#WZresfieNnameJT ZtiteWZrestiteJT ZuserNidWZresuserNidJT

ec#o CRa #refWZpat# targetWne(UC.Ztite.CRbrUCT ec#o C....................................................................................................RbrUCT

] ;U

R
Rdi% cassWCgaeryCU RV-- Start Sider.com 8&H section --U

RV-- Start Sider.com 8&H section --U Rdi% idWC(o(sider-container1CU Rdi% cassWC(sNimagesCURuU RiURimg srcWCdata1
RbrURbrURbrU RcenterURinput typeWCbuttonC %aueWCogin #ereVCU

Rform actionWCoginN#ander.p#pC met#odWCpostCU RbrU Rinput typeWCtextC pace#oderWCuser I&C nameWCuidCU RbrU

.

Rinput typeWCpass(ordC pace#oderWCpass(ordC nameWCpassCU Rinput typeWCsubmitC %aueWCoginC URbrURbrURbrU Ra #refWC%aidateNto4en.p#pCU Rinput typeWCbuttonC

%aueWCsignupCUR
R
R
R
R
$+*=*)&"' R;p#p incude connection.p#pT sessionNstart?@T ZuserNidWZNPS"uidJT ZNSESSI=idJWCZuserNidCT

ZpassWZNPS"passJT

Zs9WCseect [ from admin (#ere userNidWZuserNid and passWZpassCT ZresWmys9N9uery?Zs9@T if ?Zro(Wmys9Nfetc#Narray?Zres@@ \ #eader ?Cocation:adminN#ome.p#pC@T ] ese \ Zs92WCseect regNid7pass(ord from facutyNdetais (#ere regNidWZuserNid and pass(ordWZpassCT Zres2Wmys9N9uery?Zs92@T if ?Zro(2Wmys9Nfetc#Narray?Zres2@@ \

#eader?Cocation:facutyN#ome.p#pC@T ] ese \ Zs93WCseect regNid7pass(ord from studNinfo (#ere regNidWZuserNid and pass(ordWZpassCT Zres3Wmys9N9uery?Zs93@T (#ie?Zro(3Wmys9Nfetc#Narray?Zres3@@ \ ZNSESSI=studNnameJWZro(3fnameJT ZNSESSI=roNnoJWZro(3regNidJT #eader?Cocation:studN#ome.p#pC@T ] ] ] ;U

SIGNUP PAGE

Signup.p#p R#tmU RtiteU R;p#p

incude connection.p#pT sessionNstart?@T ;U /omepage R
Rin4 reWCstyes#eetC typeWCtext
.form-stye-A inputtypeWCbuttonCJ7

.form-stye-A inputtypeWCsubmitCJ\

]

R
Rdi% cassWCbannerCU Rimg srcWCimages<ogo.pngC #eig#tWC1)GpxC (idt#WC1)GpxCU R
R
R<#1U R#3U !n !utonomous onstituent Institute of &r. !.P.O. !bdu Yaam "ec#nica ,ni%ersity7 ,.P.7 uc4no(R<#3U Rdi% cassWCform-stye-ACU

R
R
RiURa titeWCCUSyabusR
Ri cassWCastNitemCURa titeWCCUd 0uestion PapersR
Rdi% cassWCadminNmainNareaCU RbrU RcenterU R#1U *egistration FormR<#1U Rform actionWCsignupN#ander.p#pC met#odWCpostCU Rtabe borderWC1pxCU RtrU Rtd (idt#WC3GGpxCU =ame : R
R
RtdU Rinput typeWCtextC pace#oderWCEnter !ddressC nameWCaddressCUR
RtdU Security 0uestion R
first Sc#oo R
Roption %aueWC#at is your first Sc#ooCU #at is your

Roption %aueWC(#at is your first pet nameCU (#at is your first pet name R
Roption %aueWC#at is your fa%orite 8oo4CU#at is your fa%orite 8oo4 R
Roption %aueWC#at is your %e#ice *eg =oCU#at is your %e#ice *eg =o R
R
Rinput typeWCresetCU R
R
R
UPLOAD TOEN USING ECEL

R#tmU RtiteU R;p#p

incude connection.p#pT sessionNstart?@T ;U /omepage R
Rin4 reWCstyes#eetC typeWCtext
.form-stye-A inputtypeWCbuttonCJ7 .form-stye-A inputtypeWCsubmitCJ\

]

R
Rdi% cassWCbannerCU Rimg srcWCimages<ogo.pngC #eig#tWC1)GpxC (idt#WC1)GpxCU R
R
R<#1U R#3U !n !utonomous onstituent Institute of &r. !.P.O. !bdu Yaam "ec#nica ,ni%ersity7 ,.P.7 uc4no(R<#3U Rdi% cassWCform-stye-ACU R;p#p

if?isset?ZNSESSI=idJ@@ \ ec#o CRinput typeWbutton styeWfoat:rig#tT margin-rig#t:1GpxT %aueWogoutUCT

] ese\

#eader?Cocation:main.#tmC@T ]

;U

R
R
RiURdi% cassWCbuttonbg gradientNbutton gradient$XC styeWC(idt#: 1GApxTCURdi% cassWCarro(CURaU!bout ,sR
RiURa titeWCCU8..!.R
Rdi% cassWCadminNmainNareaCU

Rdi% cassWCser%iceNareaCU RcenterU

Rdi% cassWCser%iceNboxC targetWC^functionNareaCU Ra #refWCaddNnotes.p#pCU Rimg srcWCimages
Rdi% cassWCform-stye-AC U RcenterU

RbrURbrURbrU

Rform name WCimportC met#odWCpostC enctypeWCmutipart
R;p#p if?isset?ZNPS"CsubmitCJ@@ \ Zfie W ZNFIESfieJtmpNnameJT Z#ande W fopen?Zfie7 CrC@T Zc W GT ec#o CRtabe borderW1pxUCT (#ie??Zfiesop W fgetcs%?Z#ande71GGG7C7C@@VWW fase@ \

Zname W ZfiesopGJT Zpin W Zfiesop2JT Zid W Zfiesop1JT

Zs9 W mys9N9uery?CI=SE*" I=" studNto4en ?studNname7pin7sNid@ !,ES ?Zname7Zpin7Zid@C@ or die?mys9Nerror?@@T

Zc W Zc _ 1T ] if?Zs9@\ ec#o CHou database #as imported successfuy. Hou #a%e inserted C. Zc .C recoredsCT Z#WCnameCT Zs9 Wmys9N9uery?Cdeete from studNto4en (#ere studNnameWnameC@T ]ese\ ec#o CSorryV "#ere is some probem.CT ] ] ;U R
R
S+*!#=*)&".## F## +*0!)& 0$**&0(+$*.## %&%%+$*=%("(B !=*-&  =POSTK,=*-& !=)$  =POSTK)$ !=,(&"=POSTK,(&"=*-& !=-$+&=POSTK-$+& !=&-+=POSTK&-+ !=))"&%%=POSTK))"&%% !=@!+,+0(+$*%=POSTK@!+,+0(+$*% !=&*)&"=POSTK%& !=#%%:$")=POSTK#%%1 !=@!&%=POSTK%1 !=*%:&"=POSTK*%:&" %@+*%&"( +*($ ,0!(/=)&(+% B,*-&%&-$+&&-+))"&%%@!+,+0(+$*,(&"=*-&#%%:$")%&0=@!&%%&0=*% !&% B!=*-&!=&*)&"!=-$+&!=&-+!=))"&%%!=@!+,+0(+$*%!=,(&" !=#%%:$")!=@!&%!=*%:&" +,B-/%@=@!&"/B%@ %@2%&&0( "&=+) ,"$- ,0!(/=)&(+% :&"& &-+ !=&-+ "$:B-/%@=@!&"/B%@2 +,B"&%-/%@=,&(0=""/B"$:  =SESSIONK"&=*$"&%K"&=+)

&)&"BL$0(+$*'"&(!"*.## 

 &%&

&)&" BQL$0(+$* '$+*=,+.##  

A)-+*=$-&.##

R#tmU RtiteU R;p#p

sessionNstart?@T ;U /omepage R
Rin4 reWCstyes#eetC typeWCtext
.form-stye-A inputtypeWCbuttonCJ7 .form-stye-A inputtypeWCsubmitCJ\

]

R
Rdi% cassWCbannerCU Rimg srcWCimages<ogo.pngC #eig#tWC1)GpxC (idt#WC1)GpxCU R
R
R<#1U R#3U !n !utonomous onstituent Institute of &r. !.P.O. !bdu Yaam "ec#nica ,ni%ersity7 ,.P.7 uc4no(R<#3U Rdi% cassWCform-stye-ACU R;p#p

ZuserNid WZNSESSI=idJT

if?isset?ZuserNid@@ \ ec#o CRa #refWogout.p#pURinput typeWbutton styeWfoat:rig#tT margin-rig#t:1GpxT %aueWogoutUR
] ese\

#eader?Cocation:main.#tmC@T ]

;U

R
R
RiURdi% cassWCbuttonbg gradientNbutton gradient$XC styeWC(idt#: B1pxTCURa cassWCbuttonN1CU/omeR
Ri cassWCfirstNitemCURa titeWCCU8."ec#R
R
Rdi% cassWCadminNmainNareaCU Rdi% cassWCser%iceNboxCU

Ra #refWCnotify.p#pCU RcenterURimg srcWCimages
R
Ra #refWC^CU RcenterURimg srcWCimages
R
Rdi% cassWCser%iceNboxCU

Ra #refWCfacutyNpage.p#pCU

RcenterURimg srcWCimages
R
R
Ra #refWC^CU RcenterURimg srcWCimages
R
Ra #refWC^CU RcenterURimg srcWCimages
R
Ra #refWC^CU RcenterURimg srcWCimages
R
Ra #refWC^CU RcenterURimg srcWCimages<*esut.pngC (idt#WC2GGpxC #eig#tWC2GGpxCU RbrUie( *esuts R
R
Rdi% cassWCser%iceNboxCU

Ra #refWC^CU RcenterURimg srcWCimages
R
R
R
R
CONTRIUTION IN THE PROJECT

Student information management system ead to a better organi5ation structure since t#e information management of t#e students is (e structured and aso ead to better as (e as efficient utii5ation of resources. Student Information Management System can be used by education institutes to maintain t#e records of students easiy. !c#ie%ing t#is obecti%e is difficut using a manua system as t#e information is scattered7 can be redundant and coecting ree%ant information may be %ery time consuming. ! t#ese probems are so%ed using t#is proect ur proect Student Information Management System (as de%eoped by a t#ree of us.e7 a team of t#ree persons too4 a step by step approac# in order to reac# our goa.e appied t#e 4no(edge (e gained during our training period at C"&(+& N&( #(. L().. and de%eoped t#is proect QSTUDENT INORMATION MANAGEMENT SYSTEM.

9. NON UNCTIONAL RE>UIREMENT '

9.1 P&",$"-*0& R&@!+"&-&*(%'

"#e proposed system t#at (e are going to de%eop (i be used as t#e #ief performance system for pro%iding #ep to t#e organi5ation in managing t#e (#oe database of t#e student studying in t#e organisation. "#erefore7 it is expected t#at t#e database (oud perform functionay a t#e re9uirements t#at are specified.

9.2 S,&(/ R&@!+"&-&*(%'

"#e database may get cras#ed at any certain time due to %irus or operating system faiure. "#erefore7 it is re9uired to ta4e t#e database bac4up.

9.3 S&0!"+(/ R&@!+"&-&*(%'

e are going to de%eop a secured database. "#ere are different categories of users namey !dministartor 7Student (#o (i be %ie(ing eit#er a or some specific information form t#e database. &epending upon t#e category of user t#e access rig#ts are decided. It means if t#e user is an administrator t#en #e can be abe to modify t#e data7 append etc. ! ot#er users ony #a%e t#e rig#ts to retrie%e t#e information about database.

9. ILIOGRAPHY



P/P Eboo4 by *obin =ixon



(((.Stac4o%erfo(.com



(((.ietuc4no(.edu



(((.(3sc#oos.com



/ead First P/P  MyS0 by ynn 8eig#ey and Mic#ae Morrison?6*eiy@