meena requirement analysis document
TRANSCRIPT
-
7/29/2019 Meena Requirement Analysis Document
1/21
REQU IREM ENT ANALYSIS DOCUM ENT (RAD)
PROJECT NAM E
ATTENDANCE M AN AGEM ENT
SYSTEM OF ANITS COLLEGE
PROJECT TEAM M EM BERS
A.M EENA 309126510010
ABDUL SHABBER 30 91 26 51 0002
D.LAVANYA 309126510032
IV/ IV B.TECH C.S.E-A
OBJECT ORIENTED SOFTW ARE ENGIN EERING LAB
Subm i t ted by
A.M eena (309126510010)
-
7/29/2019 Meena Requirement Analysis Document
2/21
Table of Con t ent s:
1 . Revi si on H i sto ry
2 . In t ro d uct i on
Pur po se of t he syst em Scope o f t he syst em
Objective and success cr i t er ia of t he p ro ject
3 . Cur ren t System
4. Proposed System
Overview
Funct ion al Requi rem ent s
Non-funct ional Requi rements5 . Sy st e m M o d els
Scenarios
Use case m od el
Ob je ct m o d e l
Dynam ic m ode l
6 . Glo ssar y
-
7/29/2019 Meena Requirement Analysis Document
3/21
Revision of Hist or y
Version R1.0 26/ 08/ 2012 Created by a ll t eam m emb ers
Release com posed of req uirem ent analysis docum ent .
Preface
This docum ent addresses th e requirem ents of At tendance M anagemen t
System . The inten ded audience for th is docum ent are designers and th e cl ient
o f the pro ject .
Targeted aud ience
Client , Develop ers.
-
7/29/2019 Meena Requirement Analysis Document
4/21
1. INTRODUCTION
1.1 Purp ose of t he syst em
The prop osed system is ent i t led as At tendance m anagem ent system of ANITS is
deve loped to compute r i se a l l t he a t t endance de ta il s o f s tuden ts in t he co l lege and thesof tw are m ust be user-f r iendly, sim ple, fast accessing of data. This system w i l l be mo nito red
by th e Facul ty m em bers , Head of th e Depar tm ent , Pr inc ipa l and by t he Adm in ist ra to r . The
m ain func t ion of t h is system is every faculty m em bers engaged w i th d i f ferent c lasses are
requi red t o submi t t he at ten dance of stud ents present in t he c lass. Facul ty can subm i t the
at tend ance deta i ls in At t endance managemen t system and th e deta i ls can be ret r ieved
w henever necessary thro ugh i t . The m odi f icat ions on th e at tend ance deta i ls are don e by the
adm in ist ra to r . Every stud ent can v iew h is/ her a t t endance deta i ls on l ine.
1.2 Scop e of t he syst em
At ten dance management system enables the u ser to per f orm operat ion s l ike addi t ion of
at tend ance deta i ls, updat ion of a t t endance deta i ls, adding and delet ion o f s tudent record. I t
enables the user to use in ter face in terac t ive ly .
1.3 Objectives and Success cr i t er ia o f t he p ro ject
The success of t his pro ject depen ds on the fo l low ing object ives:
M ainta in ing at tend ance record of every stud ent .
M ainta in ing stud ent record of every stud ent .
Addi t ion of s tudent a t tend ance by the facul ty .
Updat ion o f every deta i l about t he at tend ance and stud ent record each stud ent in to
the database.
2. CURRENT SYSTEM
N one
-
7/29/2019 Meena Requirement Analysis Document
5/21
3. PROPOSED SYSTEM
3.1 Overview
The goal o f At t endance M anagem ent System is to m anage the at tendance deta i ls o f each
and every s tudent in th e co l lege. This sof tw are has the fac il i t y to stor e th e at ten dancedeta i ls o f a l l stud ents of every c lass and branch. One can enter in to the At ten dance
M anagem ent System us ing the i r username and passw ord, w hich is then ver i f ied in the
dat abase. Every faculty m ust subm it th e at ten dance det ai ls of t he c lasses in w hich the y are
engaged w i th , and d i rec t ly the m odi f icat ions are updated o nto the d atabase. For any
m odi f icat ions in the at t endance records, are done by th e adm in ist ra to r . Admin can even
add or de lete s tudent records. The requi red data can be ret r ieved easi ly . The in ter face w i l l
be user-f r ien dly. Data is w el l prot ected and m akes th e data pr ocessing fast and e asier.
3.2 Funct ion al Requirem ent s
The system suppo r ts thr ee ac tors main ly , they are:
Faculty , who adds the at tend ance of each and every s tudent
Admin is t ra to r , who m odi f ies the at tendance deta i ls i f requested and adds or de letes
the s tuden t record .
Student , who can on ly v iew h is/ her a t t endance deta i ls.
Att endance M anagem ent System , wh ich cont a ins a l l deta i ls about a t tend ance,
stud ents and facul ty .
3.2.1 Facult y
Logs in.
Selects appro priat e c lass and br anch.
Selects the subject t i t le.
Adds the at tend ance for each and every stud ent .
I f any m odi f icat ions are to be don e on th e at tendance, requests to adm in for
modi f icat ion.
Logs out .
3.2.2 Adm in istra t or
Logs in.
Checks for t he no t i f icat ion s.
I f any present , fu l f i ls the requested no t i f icat ion
Adds stud ent record for n ew s tudent s.
-
7/29/2019 Meena Requirement Analysis Document
6/21
Deletes stud ent record i f requ ested .
3.2.3 Student
Enters ro l l num ber .
Views h is/ her a t ten dance record.
3.2.4 At t endance M anagem ent System
Stor es the up dated in form at ion about the at t endance deta i ls.
Stor es the at t endance deta i ls o f each and every stud ent .
Sto res al l login det ai ls abou t u ser.
3.3 Non -funct ional Requirem ent s3.3.1 Usabi l i t y:
Usabi l it y is the ease of use and learnabi l i t y o f hum an m ade objec ts .
At ten dance management system shou ld be und erstandable by every user .
User can easi ly interact w ith t he system .
3.3.2 Rel iabi l i ty :
Rel iab i l i t y spec i f ies the capabi l i t y o f th e sof tw are to m ainta in i t s per form ance over t im e.
Always the at t endance system should be avai lab le for the user .
I f t he user en te rs w rong log in de ta i l s, t hen i t m ust p rom pt t he user to en te r co r rect
login det ai ls.
3.3.3 Perfo rm ance:
Perform ance requi remen ts are concerned w i th qu ant i f iab le at t r ibu tes of the system such as
response t ime, t hrou ghput , avai lab i l i t y and accuracy .
System shou ld quick ly respond for u ser requ est , th at is , system m ust imm ediate lyd isp lay the l ist o f s tudent s along w i th t he i r a t t endance deta i ls a f ter he/ she se lec ts the
class.
3.3.4 Supp ort abi l i ty:
Suppo r tab i l i t y requi rem ents are concerned w i th t he ease of changes to the system af ter
dep loyment . I t means system mu st be ab le t o suppor t f o r up g rada t ion .
-
7/29/2019 Meena Requirement Analysis Document
7/21
3.3.5 Avai labi l i t y:
The system shal l be availab le dur ing norm al co l lege operat ing ho urs .
3.3.6 User In terf ace:
This w orks as an in ter face betw een t he user and t he system by pro per ly gu id ing the user
how to u se i t and per for m operat ion s. Both Adm in and Facul ty can change the data in the
At ten dance M anagem ent System , whereas, stud ent can only v iew t he data. Any sor t o f
t ra in ing is not requi red for u sing the system . .I t is imp or t ant t hat t he system is easy to learn
because even a layman n eed to use it e f f ic ient ly . The input d ev ice is given to the keyboard
a n d t h e o u t p u t i s v ie w e d o n t h e m o n i t o r .
3.3.7 Hardw are Considerat ion:
The system shal l use an Oracle or Access datab ase, and ru n on any op erat in g system .
3.3 .8 Por tab i l i ty :
The At tendance M anagem ent System shal l run in any Operat ing system env i ronm ent t hat
cont ains Java Run t im e and t he M icrosof t Access datab ase.
3.3 .9 M ain ta inab i l ity :
The Atte ndan ce M anagem ent System is being develo ped in Java. Java is an ob ject or ien ted
program m ing language and shal l be easy to m ainta in .
3.3.10 System Interf acing:
The system shal l be a s tandalone pro duct t hat d oes not requi re any system in ter faces.
3.3.11 Err or Hand ling:
Our system handles the er rors in a very ef f ic ient m anner . It can to lerate t o w rong inpu ts and
prom pts the users to correc t t he input s. It g ives not i f icat ions as and w hen requ i red, gu id ing
the users to prop er ly u t i l i ze i t .
-
7/29/2019 Meena Requirement Analysis Document
8/21
4. SYSTEM M ODEL
4.1Scenarios:
1. Viewing of a t t endance by the s tudent :
Ram start s th e EZ schoo l system . The w ebsi te is now v isib le to ram.
Ram then se lects v iew at t endance.
Ram enters h is regist ra t ion num ber .
He now v iews h is a t tend ance and ex its .
2 . At tendance addi t ion by th e facul ty :
M eena sta r t s t he EZ schoo l system to pos t t he a t t endance .
She en ter s her log in det ai ls.
She then selects the appropr ia te branch, c lass and subjec t .
Now the l ist o f s tudent d eta i ls a long w i th t he at tend ances is d isp layed and M eenaupdat es the at tendance deta i l o f each and every stud ent .
Afte r she successful ly posts the at t end ance det ai ls, she logs out of th e EZ-school.
3 . At ten dance modi f icat ion by the admin:
Harish, the ad m inistrato r starts the EZ schoo l system .
He enters h is log in deta i ls.
Now Har ish checks for any not i f icat ions , i f there is any m odi f icat ion request sent by
the facul ty M eena, he successfu l ly m odi f ies the requ ested at tend ance.
Har ish then upda tes t he a t t endance o f t he studen ts t hose wh ich are mod i f i ed .
He adds the deta i ls o f t he s tudent s w ho h ave newly jo ined in t he co l lege ,de letes the
at tend ance records i f any stud ent leaves the co l lege. Afte r ful f i l l ing al l the req uirem ent s, Harish logs ou t of EZ schoo lsystem .
4.2Use case m od el:
The fol low ing are the use cases ini t iated by th e faculty:
Logs in to At tend ance management system .
Selects branch.
Sele cts class.
Adds at ten dance to every stud ent . Requ ests for any m od if icat ions.
The fo l lowing are t he use cases in i t ia ted by t he adm in:
Logs in to At tend ance management system .
The requested m odi f icat ion b y the facul ty is fu l f i l led by t he admin.
Adds stud ent record.
-
7/29/2019 Meena Requirement Analysis Document
9/21
Deletes stud ent record.
The fo l lowing are t he use cases in i t ia ted by t he At t endance m anagem ent system :
Updates the mod i f ied at tend ance.
Checks the lo gin det ai ls.
Updates at tendance record.
Updates stud ent record.
Use case Diagram :
I t descr ibes the system f rom an ex ternal po int o f v iew.
-
7/29/2019 Meena Requirement Analysis Document
10/21
Flow of event s:
1. Name: Login
Part ic ipating Actor : Facult y
Ent ry condi t ion : Enter the log in deta i ls
Flow o f events:
Faculty starts the system and o pens th e EZ schoo l system , the h om epage is now
disp layed, prom ping to enter her log in det a i ls or get reg isterd .
He enters h is log in deta i ls and th e in form at ion is sent t o an i ts at tend ance
m anagem ent system for ver i f icat ion.
I t acknow ledges back by displaying next page i f t he d etai ls are val id.
Otherw ise i t pro m pts to f i rs t reg ister t hem by enter ing t he deta i ls such as nam e,
DOB, gender , age, passwor d, qual i f icat ion , branch, and so on. Af ter enter ing th e requi red in form at ion, i t is then send to an i ts at t endance
m anagem ent system for ver i f icat ion.
Ant i s at tend ance system then acknow ledges the facul ty by d isp lay ing a nex t page.
Exit condi t ion : Faculty successful ly logs into th e ez schoo l si te an d start s the re quir ed
tasks.
2. Name: At tendance addi t ion
Part ic ipating Actor : Facult y
Ent ry condi t ion : subje ct select ion
Flow o f events:
The system p rom pt s th e faculty to select branch and c lass.
Now i t pr om pt s to select th e subject l ike Engl ish, OOSE, M ath s, M icropr ocessors, etc.
Faculty respon ds to t he system by select ing o ne subject n am e for examp le say OOSE.
The system sends that par t icu lar subjec t in for m at ion t o t he ani ts a t tend ance system
for ver i f icat ion. Ani ts at ten dance system then r espond s to t he request o f th e user by d isp lay ing the
l ist o f s tudent s re la ted w i th t hat subjec t i .e OOSE.
Facul ty then adds the At tend ance to the s tudent s re la ted w i th th at subjec t .
Exit condi t ion : Teacher logs out a f ter hav ing posted t he at tend ance.
-
7/29/2019 Meena Requirement Analysis Document
11/21
3. Name: Request for m odi f icat ion
Part ic ipating Actor : Faculty, Adm in
Ent ry condi t ion : Faculty send s requ ests to t he adm in
Flow of events:
W hi le adding the at tendance deta i ls, if facu l ty needs to m odi fy the at t endance of the
stud ents , then h e sends the request to adm in for m odi f icat ion.
The at tend ance m ust be updated befo re the m odi f icat ion is done.
Adm in gets the no t i f icat ion and m odi f ies the requ ested at t endance.
Exit condi t ion : Admin m odi f ies the at t endance and upd ates in database.
4. Name: Add/ Delete a stud ent record
Par t ic ipat ing A cto r : Adm in
Ent r y condi t ion: Adm in logs in to the system
Flow of events:
Adm in s tar ts the system , hom epage is d isp layed prom pt ing t o ent er h is login deta i ls.
He enters the log in id and passw ord, and t he in form at ion is sent t o an i ts a t tendance
m anagem ent system for ver i f icat ion.
I t ackno w ledges him back by displaying next page i f the det ai ls are val id, ot herw ise
displays a m essage inval id det ai ls .
Adm in adds record of th ose stud ents wh o jo ined recent ly and updat es the det a i ls
in to data base.
Simi lar ly , adm in deletes th e s tudent record w henever n ecessary .
Exit condi t ion : Admin saves the m odi f icat ion done t o t he par t icu lar sec t ion stud ents ,
updat es in to data base and logs out .
5 . Name: Roll n o
Par t ic ipat ing Acto r : Stu dent
Ent ry condi t ion : Enter a ro l l num ber
Flow of events:
Stud ent star ts the system , hom epage is d isp layed and pro m pts to enter h is ro l l no.
-
7/29/2019 Meena Requirement Analysis Document
12/21
Stud ent enters h is ro l l no.
The in for m at ion is sent to the database and i f i t is va lid th en t he database respond s
by displaying next page.
Otherw ise i t d isp lays a m essage inval id ro l l no .
Exit condi t ion : Stud ent en ters in to Ani ts a t tendance m anagem ent system .
6. Name: View at tendance
Par t ic ipat ing Acto r : Stu dent
Ent ry condi t ion : v iew s the at t endance
Flow of events:
Stud ent ent ers the ro l l no and the in form at ion is sent to t he database. The database respond s by displaying the next page cont aining at ten dance, i f the
at tend ance is updat ed.
Oth erw ise the dat abase respond s by displaying a new p age cont aining a m essage
a t t endance no t upda ted .
Exit condi t ion : Stud ents v iew r equi red at tend ance deta i ls and ex i ts .
4.3 Object m ode l
The object m odel descr ibes the st ruc tu re of t he system in term s of ob jects , a t t r ibu tes ,
associat ion s, and o perat ions.
The classes that are ident i f ied f ro m the above use case d iagram are:
Faculty:
At t r ibu tes : Name o f the facuty and an id(num ber) is g iven for each facul ty .
Operat ions : He/She has the r ight to on ly to add at t endance.
Ez schoo l syst em :
Att r ibu tes: It h as a nam e and an id being assigned t o t his class.
Operat ions : This class can per fo rm getdeta i ls and t ransferdeta i ls . Student :
At t r ibu tes : Every stud ent is assigned wi th a name and a ro l l num ber .
Operat ions : He has the r ight on ly to v iews his at tend ance.
Login:
Att r ibu tes: This class is assigned w ith a login id an d a p asswor d.
Branch:
Att r ibu tes: Every branch is assigned w ith a nam e and also the year.
-
7/29/2019 Meena Requirement Analysis Document
13/21
Class:
Att r ibu tes: Each c lass has a name and also a sect io n b eing assigned t o i t .
Att endance record:
At t r ibu tes : This c lass has the s tudent n ame, ro l l num ber , subjec t , year of stud y ,
branch in w hich he s tud ies, num ber of days he at t ended the c lass and h is % of
at tendance.
Operat ions : This class does the ac t ion of d isp lay ing th e at t endance.
Admin :
At t r ibu tes : Adm in is assigned wi t h a nam e and an id(num ber) .
Operat ions :He can per f orm the ac t ions such as add,mod i fy ,de lete and m ainta in
records.
Registrat ion:
At t r ibu tes : This c lass m ainta ins the n ame o f th e facul ty m em bers ,there log in
Detai l s, designa t ion and the i r da te o f b i r t h .
Ani ts a t tendance m anagement system :
Att r ibu tes: This class is assigned w ith a nam e and an id(nu m ber).
Operat ions: It can perfor m t he act ions such as veri fy ing, t ran sfer in g,and get t ing the
deta i ls o f t he s tudent s.
New student record :
Att r ibu tes: This c lass m aintains the nam e,rol lnum ,branch,year,c lass in w hich the
stud ent is adm i t ted.
Stud ent record:
At t r ibu tes : I t has the nam e, subjec t , and % of at t endance the s tudent acqui red.
-
7/29/2019 Meena Requirement Analysis Document
14/21
Class Diagram :I t is used to descr ibe the s t ruc ture of the system .
4.4 Dynamic m ode l
The dynamic m odel descr ibes the in tern al behav iour o f t he system . They are represented
w i th in terac t ion d iagram s, sta techar t d iagrams, and ac t iv i ty d iagrams.
Sequ ence Diagram s:
I t describes th e behavio ur as a sequ ence of m essages exchanged am ong a set of o bjects.
-
7/29/2019 Meena Requirement Analysis Document
15/21
1 . For Add it i on o f a t t endance and mod i f i ca t ions:
-
7/29/2019 Meena Requirement Analysis Document
16/21
1 . Fo r st ud en t :
-
7/29/2019 Meena Requirement Analysis Document
17/21
2. Collabor atio n Diagram:
Facul ty p os t ing the at tend ance
Stud ent v iewing h is a t tendance det a i ls
-
7/29/2019 Meena Requirement Analysis Document
18/21
St ate chart Diagram :
I t descr ibes the behav iour o f th e system in term s of sta tes of an ind iv idual ob jec t and
possible t ransit ion s bet w een stat es.
1 . A t t en d an ce ad d it i on :
-
7/29/2019 Meena Requirement Analysis Document
19/21
2 . U p d at i on o f a t te n da nce
3 . V ie w i ng o f At t e n dan ce
-
7/29/2019 Meena Requirement Analysis Document
20/21
Activi t y Diagram s:
I t descr ibes the behav iour o f t he system in ter m s of ac t iv it ies.
1.Faculty
-
7/29/2019 Meena Requirement Analysis Document
21/21
2.Admin
3.Student