OOSD External Lab Record
OOSD External Lab Record
OOSD External Lab Record
To reduce the expenses of the college by reducing the number of employees for entry and maintenance of records. To manage data more efficiently. To attract talented students and lecturers to choose the appropriate course according to their interest and talent. To reduce data redundancy and inconsistency. To display results on the internet. To make the software interface as user"friendly as possible.
'ecturer ( %erson teaching a particular sub)ect in the college *tudent ( %erson intending to either )oin some course in the college or already admitted +anagement ( The body managing the overall working of the college Database ( The total data stored through which the various actors interact and get re#uired information. $t is continually updated for each procedure completed. D A ( %erson in"charge of managing the database
%. &ener'l Descr (t on
!roduct !ers(ect $e This system is dependent on the database system of the college for providing details to students and other users. $t interfaces the users with a special user screen that has different features from the normal user screens. $t re#uires the users to login using a password. !roduct )unct on The various functions performed by the software are,
'ogin ( -ualifies users according their class and provides security and also improves the effectiveness of the software. Admission ( Allows students to get admitted to the college or check their marks if they are already admitted. .pdating of marks ( !elps the lecturers to update marks of students. /esults ( 0hich displays the marks in the website. +anagement of database ( Assists the D A in maintaining the database.
User C*'r'cter st cs The users are re#uired of possessing the following #ualities, highly motivated and conscientious1 computer literate not necessarily professionals1 related to the concerned college. &ener'l Constr' nts The system shall follow the following constraints in its design phase. 2ot more than 34 students are allowed to be admitted in a course. Atomicity of actions must be ensured.
3.1.2
3.1.3
Updating marks Steps involved 5hecking the validity of the lecturer and verifying the password. Accepting the marks of the individual student of a particular course1 if entered by an authori&ed lecturer. .pdating the changes according to the marks allotted. Inputs .ser name and password of the lecturer. 5ourse and semester of the student1 whose marks are to be entered. /oll number and marks of the individual students. Processing The lecturer logins in order to enter the marks of their respective students. The system checks for the validity of the user name and password and allows access to the re#uired view 6example ( the lecturer can not access the salary database7 The database is updated according to the marks allotted by the lecturer. The changes are saved and displayed on the college results website. Outputs A message should be displayed after updating the marks in the database. Constraints The user must be included in the list of lecturers and have a valid user name and password The view must be created such that the lecturer must have access to the marks field of his own students A lecturer cannot have privileges to manipulate other areas of database. esults Steps involved Accepting the roll number Display the results for a given roll number Inputs 5ourse and semester /oll number Processing The student accesses the college website for the results. The system checks for the availability of marks for the semester and if available displays the results The student can only check the marks but cant update. Outputs 8or valid input1 display the result $f roll number is not valid1 display error message Constraints The course and roll number must be related to the concerned college. "anagement o# $ata%ase Steps involved Adding1 updating or deleting student information in the student database. Adding1 updating or deleting lecturer information in the lecturer database. Adding1 updating or deleting course information in the course database. Allocation and de"allocation of roles and privileges. +odifying the information1 constraints governing the college. Inputs .ser name and password to authori&e the D A.
3.1.4
3.1.!
*election of task. .ni#ue identification key incase the D A selects to update database so that concerned data item can be accessed. Processing The D A uses this function to manage the changes in database1 which occur due to other user cases1 and to perform other tasks specified for a D A. The D A logs into the system and then performs the re#uired task. Outputs 5onfirmation to the changes made. $n case any failure1 D A is informed and the changes are cancelled. Constraints Atomicity should be ensured1 that a particular task should perform totally or should be completely aborted. The changes made in the database should not be in conflict with the constraints specified. E-tern'l nterf'ce re,u rements External interfaces must be maintained by the central database as interpreted by the operator. *tudents re#uire a different interface as there is no need for them to login. !ard and soft copy reports shall be the only output maintained. These outputs shall be controlled by authori&ed management personnel.
!erform'nce Re,u rements All user re#uests shall be responded to within 3 to 9 seconds. /esponse shall be measured from the last entry keystroke to the appearance of an on screen reply. Des .n Constr' nts Design and development of the system shall confirm to college standards. The system is a )ava application which runs with the help of a reliable database management system. Attr "utes 3.!.1 Securit& 3.!.2 *ecurity of all files shall be a ma)or design re#uirement. Only authori&ed users shall be permitted to access the database. %asswords shall be assigned only by the authori&ed management personnel. Three unsuccessful access attempts shall be recorded in transaction log1 access shall be denied after the third unsuccessful attempt.
"aintaina%ilit& *oftware product documentation shall include design specification1 a commented listing 6a comment for every three executable lines of code71 a set of executable test cases and appropriate results. A user manual shall be provided in a reproducible form. elia%ilit& The college largely relies upon the database and so the system needs to be reliable.
3.!.3
Ot*er re,u rements 3.'.1 $ata%ase An efficient database management system shall be used as a back end1 which facilitates reliable and affective transactions.
3.'.2
Operations A backup of the database is created after each particular interval of time1 which can be used for recovery if needed.
Test n. All modules of the systems need to be tested separately and also the system as a whole to assure that the system works properly as per the re#uirement specification. Alpha and beta testing can be used for this purpose.
4. UML DIAGRAMS
Use case Diagrams
login
lecturer
offer courses
user
<<include>>
<<extend>>
bill generation
mode of payement
maintainanace of database
Cl'ss D '.r'ms
-niversity
name : String affiliation : String address : String code : integer admission( offer!ourses( '++& '
DBAdmin
name : String id : Integer
maintains
'++& '
enrolls
assign Courses
updates
'++&
'++& &
Student
name : String roll(no : Integer course(id : Integer takeAdmission( c)eck"esults( pay*ee( '++&
,ecturer
name : String lecturer(id : Integer course(id : Integer login( offer!ourse( update%arks(
DataBase
admissionDetails( courseDetails( %arksDetails(
attends
'++&
teaches
'++&
'++&
!ourse
course(id : Integer lecturer(id : Integer offer!ourse(
Se,uence D '.r'ms0
system
database
.: give options(
System
database
2: aut)ori4e(
lecturer
system
dba
database
.: en1uire for username and pass3ord /: enter username and pass3ord 0: c)eck for validity
2: validate 5: give options 6: select offer courses option 7: get course details 8: give course details '9: display course details '': select course to offer '.: send details '/: save c)anges '0: logout
,ecturer
System
DBA
DataBase
.: en1uire for username and pass3ord /: enter username and pass3ord 0: c)eck for validity 2: :alidate 5: en1uire for course and semester details
6: enter course and semester details 7: c)eck for validity of course and semester 8: validate course and semester '9: accept student marks
'': enter marks for all students '.: send details to dba '/: save c)anges '0: logout of system
student
system
database
/: give course ; semister( 0: c)eck for validity of course ; semister( 2: validate( 5: en1uire for roll number if validated(
system
database
/: give necessary details and documents( 0: c)eck for avai lability of seats and el igibility(
DBA
database
8: logoff(
Coll'"or't on D '.r'ms
': access t)e net( /: select functions to be performed( user .: give options( 2: perform t)e function( system
database
': access t)e net( /: enter username and pass3ord( user .: ask for t)e username and pass3ord( System
2: aut)ori4e(
database
': acess net and select login option /: enter username and pass3ord 6: select offer courses option '': select course to offer '0: logout lecturer .: en1uire for username and pass3ord 5: give options '9: display course details 2: validate 8: give course details system
'.: send details 0: c)eck for validity 7: get course details '/: save c)anges dba database
': acess net and select update option /: enter username and pass3ord 6: enter course and semester details '': enter marks for all students '0: logout of system ,ecturer .: en1uire for username and pass3ord 5: en1uire for course and semester details '9: accept student marks
System
DataBase
': access net ; select admission option( /: give necessary details and documents( student .: provide relevant form for t)e selected course( 2: admit if selection criteria are met( 6: allot roll number and dispatc) necessary billing( system
database
': access net ; select result option( /: give course ; semister( 6: enter roll number( student .: provide result form( 5: en1uire for roll number if validated( '9: display result( 2: validate( 8: validate and give result( 0: c)eck for validity of course ; semister( 7: c)eck for validity of roll number( system
database
': access net ; select namagement option( /: enter user name ; pass3ord( 5: select task to be performed( 6: enter data( 8: logoff( DBA .: en1uire for username ; pass3ord( system
Act $ t/ D '.r'ms
login
DBA
Allocation of privilages
log off
enter t)e user name and pass 3ord = / times > retry on failure verify pass3ord on success Allo3 access to database
Available
!)eck for availability of courses @ot Available Abort t)e process @ot Aligible
!)eck *or Aligibility Aligible Accept details t)roug) online form Admit t)e Student into course Allot "ollnumber and Dispatc) Billing to t)e student
!)eck *or :alidity #f !ourse And Semester Abort t)e $rocess Invalid :alid Invalid Accept "oll number
@ot :alid
Abort t)e process #ptions:':-pdate Student Database+ . -pdate ,ecturer Database / -pdate !ourse Database 0 Allot "oles And $rivilages?2 #t)er %odifications
,ogBoff
,ogin By ,ecturer
:erification #f $ass3ord Invalid Abort t)e $rocess :alid Accept !ourse and Semester from ,ecturer
,ogBoff
user
system
dba
data base
provide option
provide details
update database
save c)anges
ID,A
on Access
error < print report Display Antry < ,ogin Axit < log off
on !ompletion
Com(onent D '.r'ms
course enrollment+exe
database+exe
student
lecturer
dba
student+exe
lecturer+exe
dba+exe
De(lo/ment D '.r'ms
$rinter
internet @e3Device /
0rite the following contents of Each Diagram, :. ;. 3. <. 9. =. Aim Of Experiment /e#uirement *pecification Theory %rocedure to Draw the Diagram Observations and Analysis of Observations 5onclusions
Use C'se S(ec f c't on: $n order to better understand the various scenarios of a use case1 it is to be detailed. This is possible by writing use case specification. $t helps in making re#uirements complete1 consistent and unambiguous. The typical format of use case specification 6Detailing a use case7 is as follows, Use C'se ID: Use C'se N'me: Cre'ted 9/: D'te Cre'ted: Actors: Descr (t on: !recond t ons: !ost cond t ons: Norm'l )lo:: Altern't $e )lo:s: )re,uenc/ of Use: 9us ness Rules: Assum(t ons: