Online Student Attendance Management System

11-09-16 cheapnisha 0 comment

Online Student Attendance Management System

Use Case “UC60-Login for OSAMS”

Use Case Login for OSAMS
Actors Teacher, Administrator, Student
Description Enable Teacher/Administrator/Student to access the online student management system OSAMS.
Pre-Condition The Teacher/Administrator/Student has a valid username and

password and is not currently logged in.

Post-Condition The Teacher/Administrator/Student can now access the

system and perform their operations.

Type Complex
Normal Course of Action 1) The user clicks ‘Log In’ on interface of the OASMS.

2) The OSMS shows a screen with username and password text fields along with submit button.

3) The user enters their username and password (A1)

3.1) The OSMS allows user to access the system  according to the access control mechanism.

Alternate Course of Action A1) User enters wrong credentials. OSMS notifies teacher/Administrator accordingly and again displays the login screen with appropriate error message.

Use Case “UC61-Logout for OSAMS”

Use Case Log out for WTS
Actors Teacher/ Administrator / Student
Description Disables logged in Teacher/ Administrator / Student to access the student attendance management system (OASMS).
Pre-Condition The Teacher/ Administrator / Student  is already logged in.
Post-Condition The Teacher/ Administrator / Student  cannot access the

system now.

Type Simple
Normal Course of Action 1) The user selects ‘Log Out’ from interface of OSAMS.

2) The OSAMS disables access to the system.

Alternate Course of Action None

Use Case “UC62 – Add student for OSAMS”

Use Case Add student
Actors Administrator, Student
Description Administrator can add new student in OSAMS system.
Pre-Condition The administrator should be logged in OSAMS system.
Post-Condition A new student has been added successfully.
Type Complex
Normal Course of Action 1) The administrator clicks “Add student” link on the interface of OSAMS.

2) A screen is displayed with firstname, lastname, class and teacher.

3) If details are valid, (A1)

3.1) Interface displays a success message.

 

Alternate Course of Action A1) The student add screen is displayed with appropriate error message.

Use Case “UC63 – Approve Leave for OSAMS”

Use Case Approve Leave
Actors Teacher, Student
Description Teacher can approve / disapprove leave of a student in OSAMS system.
Pre-Condition The teacher should be logged in OSAMS system.
Post-Condition A teacher has approved / disapproved leave of the student in OSAMS.
Type Complex
Normal Course of Action 1) The teacher clicks “Leave status” link on the interface of OSAMS.

2) A search screen is displayed with search button.

3) Teacher enters student ID and a screen is displayed with list of student’s name along with balance leave, leaves taken, approved leaves.

4) If balance leave > 0, (A1)

4.1) Teacher clicks “approve leave” button.

5) Notify student.

 

Alternate Course of Action A1) The teacher clicks “Reject Leave” button.

Use Case “UC63 – Mark Defaulter for OSAMS”

Solution 1: In software designing, people generally like Unified Modelling Language or UML. It also offers many different things to stakeholders.  The design of our solution has used UML’s diagrams to present the skeleton and interaction among different components of the system.

UMLs can be formal if needed and informarl as simple as a plain English language. UML could be used for all different types of applications and for all different cases. However the expectancies would be different for instance, some architecturally demanding systems could be designed in high level of details whereas some will only have packages indicating the place of code i.e., the functionality, GUI etc. in the overall system picture. This code could be obtained in a number of different ways.

One of the main goals of an UML is to simplify the communication between different project stakeholders. It also acts as a communication method between development teams, documentation of project and as a contract between developers and customers. In my opinion, this goal is definitely reached. The main strength of UML is that it is a highly effective tool when the project is in initiation stage apart from the strengths mentioned earlier. Diagrams at this point in the development of software tend to play their role best. On the other hand, at the later stages, UML might not do much good and perhaps could even be cumbersome to do so. One can also make use of packaged designs so as to shorten the overall time it takes for the completion of the diagram. UML’s strength is also prevalent when one has to reverse engineer an old code or a code, which is written in some other way. While implementation stage does not mean that the code is 100% generated but the developer could get a clear and commented code skeleton with different kinds of descriptions in the shape of a UML diagram.

Use Case Mark defaulter
Actors Teacher, Student
Description Teacher marks defaulter in OSAMS system.
Pre-Condition The teacher should be logged in OSAMS system.
Post-Condition Teacher marked defaulter to a particular student.
Type Complex
Normal Course of Action 1) The administrator clicks “Leave status” link on the interface of OSAMS.

2) A search screen is displayed with search button.

3) Teacher enters student ID and a screen is displayed with list of student’s name along with balance leave, leaves taken, approved leaves.

4) If balance < 0 and approved leave = 0, (A1)

4.1) Teacher clicks “Mark defaulter” button.

 

Alternate Course of Action A1) The teacher exits system.
Download