Essay Available:
You are here: Home → Term Paper → IT & Computer Science
Pages:
1 page/≈275 words
Sources:
6 Sources
Level:
Harvard
Subject:
IT & Computer Science
Type:
Term Paper
Language:
English (U.S.)
Document:
MS Word
Date:
Total cost:
$ 6.48
Topic:
Online Student Attendance Management System Term Paper (Term Paper Sample)
Instructions:
the project was on uml design of online student attendance system.
the sample includes uml diagrams along with in-depth analysis of use case diagram and sequence diagram.
Content:
Use case diagram
Figure SEQ Figure \* ARABIC 1: Use case diagram
Use case descriptions
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”
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.
Use Case “UC64 -Add Subject for OSAMS”
Use Case
Add subject
Actors
Administrator
Description
Administrator adds a new subject in OSAMS.
Pre-Condition
The teacher should be logged in OSAMS system.
Post-Condition
Teacher has added a new subject successfully in OSAMS.
Type
Simple
Normal Course of Action
1) The administrator clicks “add subject” link on the interface of OSAMS.
2) A screen is displayed with subject’s name.
3) If entered data is valid, (A1)
3.1) Success message is displayed on the interface.
Alternate Course of Action
A1) An error message is displayed on the interface.
Use Case “UC65 - Suspend student in OSAMS”
Use Case
Suspend subject
Actors
Administrator, Student
Description
Administrator suspends a student in OSAMS.
Pre-Condition
The administrator should be logged in OSAMS system.
Post-Condition
Administrator has suspended the student successfully via OSAMS.
Type
Complex
Normal Course of Action
1) The administrator clicks “Leave status” link on the interface of OSAMS.
2) Administrator 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) Administrator clicks “Suspend” button.
4.2) Student receives a mail regarding the suspension.
Alternate Course of Action
A1) The administrator exits application.
Use Case “UC70 - Apply for leave in OSAMS”
Use Case
Apply for leave
Actors
Student
Description
Student applies for leave via OSAMS.
Pre-Condition
The student should be logged in OSAMS system.
Post-Condition
The student has successfully applied for leave in OSAMS system.
Type
Complex
Normal Course of Action
1) The student clicks “Apply Leave” link on the interface of OSAMS.
2) A screen with student ID, classs ID, duration of leave and type of leave is displayed.
3) If available leaves of that particular type > 0, (A1)
3.1) Student select the leave and select the from and to dates.
3.2) Student receives a mail regarding the leave status.
Alternate Course of Action
A1) The system displays warning message - “Consult teacher”
Class diagram
Figure SEQ Figure \* ARABIC 2: Class diagramCRC
Class Name: Person
ID: 1
Description: An abstract class.
Associated use case: - NA
Responsibilities:
Register
Collaborators - NA
Attributes:
Lastname (text)
Firstname (text)
Password (text)
Username (text)
Generalization: -
NA
Aggregation: -
NA
Other Association: -
NA
Class Name: Student
ID: 2
Description: An individual that needs to be managed.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC62 - Add student for OSAMS
UC63 - Mark Defaulter for OSAMS
UC70 - Apply for leave in OSAMS
Responsibilities:
Add student
Delete student
Update student
Notify student
Take attendance
Update Student count
Validate student
Collaborators –
Class
Attributes:
studentNo (number)
joinDate (date)
defaulter (text)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Administrator
ID: 3
Description: An individual that manages other users.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC62 - Add student for OSAMS
UC64 -Add Subject for OSAMS
UC65 - Suspend student in OSAMS
Responsibilities:
Register student
Register staff
Add course
Suspend student
Collaborators –
Attributes:
adminID (number)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Teacher
ID: 4
Description: An individual that manages attendance of students.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC63 - Mark Defaulter for OSAMS
Responsibilities:
Activate attendance
Get Attendance
Get student leave
Approve Leave
Reject Leave
Collaborators –
Class
Attributes:
adminID (number)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Class
ID: 5
Description: A many-to-many class between student and teacher
Associated use case: -
UC62 - Add student for OSAMS
Responsibilities:
Add student
Update cl...
Figure SEQ Figure \* ARABIC 1: Use case diagram
Use case descriptions
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”
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.
Use Case “UC64 -Add Subject for OSAMS”
Use Case
Add subject
Actors
Administrator
Description
Administrator adds a new subject in OSAMS.
Pre-Condition
The teacher should be logged in OSAMS system.
Post-Condition
Teacher has added a new subject successfully in OSAMS.
Type
Simple
Normal Course of Action
1) The administrator clicks “add subject” link on the interface of OSAMS.
2) A screen is displayed with subject’s name.
3) If entered data is valid, (A1)
3.1) Success message is displayed on the interface.
Alternate Course of Action
A1) An error message is displayed on the interface.
Use Case “UC65 - Suspend student in OSAMS”
Use Case
Suspend subject
Actors
Administrator, Student
Description
Administrator suspends a student in OSAMS.
Pre-Condition
The administrator should be logged in OSAMS system.
Post-Condition
Administrator has suspended the student successfully via OSAMS.
Type
Complex
Normal Course of Action
1) The administrator clicks “Leave status” link on the interface of OSAMS.
2) Administrator 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) Administrator clicks “Suspend” button.
4.2) Student receives a mail regarding the suspension.
Alternate Course of Action
A1) The administrator exits application.
Use Case “UC70 - Apply for leave in OSAMS”
Use Case
Apply for leave
Actors
Student
Description
Student applies for leave via OSAMS.
Pre-Condition
The student should be logged in OSAMS system.
Post-Condition
The student has successfully applied for leave in OSAMS system.
Type
Complex
Normal Course of Action
1) The student clicks “Apply Leave” link on the interface of OSAMS.
2) A screen with student ID, classs ID, duration of leave and type of leave is displayed.
3) If available leaves of that particular type > 0, (A1)
3.1) Student select the leave and select the from and to dates.
3.2) Student receives a mail regarding the leave status.
Alternate Course of Action
A1) The system displays warning message - “Consult teacher”
Class diagram
Figure SEQ Figure \* ARABIC 2: Class diagramCRC
Class Name: Person
ID: 1
Description: An abstract class.
Associated use case: - NA
Responsibilities:
Register
Collaborators - NA
Attributes:
Lastname (text)
Firstname (text)
Password (text)
Username (text)
Generalization: -
NA
Aggregation: -
NA
Other Association: -
NA
Class Name: Student
ID: 2
Description: An individual that needs to be managed.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC62 - Add student for OSAMS
UC63 - Mark Defaulter for OSAMS
UC70 - Apply for leave in OSAMS
Responsibilities:
Add student
Delete student
Update student
Notify student
Take attendance
Update Student count
Validate student
Collaborators –
Class
Attributes:
studentNo (number)
joinDate (date)
defaulter (text)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Administrator
ID: 3
Description: An individual that manages other users.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC62 - Add student for OSAMS
UC64 -Add Subject for OSAMS
UC65 - Suspend student in OSAMS
Responsibilities:
Register student
Register staff
Add course
Suspend student
Collaborators –
Attributes:
adminID (number)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Teacher
ID: 4
Description: An individual that manages attendance of students.
Associated use case: -
UC60-Login for OSAMS
UC61-Logout for OSAMS
UC63 - Mark Defaulter for OSAMS
Responsibilities:
Activate attendance
Get Attendance
Get student leave
Approve Leave
Reject Leave
Collaborators –
Class
Attributes:
adminID (number)
Generalization: - Person
Aggregation: -
Other Association: -
Class Name: Class
ID: 5
Description: A many-to-many class between student and teacher
Associated use case: -
UC62 - Add student for OSAMS
Responsibilities:
Add student
Update cl...
Get the Whole Paper!
Not exactly what you need?
Do you need a custom essay? Order right now:
Other Topics:
- Intellectual Property And Cloud Computing AssignmentDescription: How organizations and individuals usually use cloud computing services and how this usage increases the risks to intellectual property....1 page/≈550 words| 4 Sources | Harvard | IT & Computer Science | Term Paper |
- Internet Security The Management Of The Resources And AccessDescription: The increased reliance on the electronic communication and monetary transactions has grown the probabilities of network threats through different methods...9 pages/≈2475 words| 6 Sources | Harvard | IT & Computer Science | Term Paper |
- Database Management IT & Computer Science Term PaperDescription: The DBMS also referred as a tool which can access the data itself, format according to the system along with fields name, record structure and the structure of the file. In the present context, it is highlighted primarily on the role of an entity-relationship diagram that shows the proper relationship...10 pages/≈2750 words| 8 Sources | Harvard | IT & Computer Science | Term Paper |
