WAQS Object Oriented Analysis – Use Case Diagrams
WAQS analysis consists of use case diagrams identified for Administration module,
Teacher Module and Student Module. The diagrams are presented in this appendix. It also
provides use case description for each of the use case.
A.1 Admin Module
A.1.1 Administrator Login
Use Case Diagrams
Admin
Login
Figure A.1.1.1 Administrator’s Login Use Case
Use Case Description
Table A.1.1.1 Administrator’s Login Use Case Description
Name
Administrator Login Use Case
Description
This use case allows the administrator to login to the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Admin already registered in the system
Post-conditions
Administrator is successfully login to the system
Flow of Events
1. Admin login to the system
2. The system checked if the user Id and password for
Administrator is valid.
3. If the admin is valid, the system allows user to proceed to the
next task, else [A1]
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.1.2 Maintain Teacher Profile
Use Case Diagrams
Add Teacher Profile
Update Teacher Profile
<<include>>
Admin
View Teacher Profile
<<include>>
Delete Teacher Profile
Figure A.1.2.1 Maintain Teacher Profile Use Case Diagram
Use Case Description
Table A.1.2.1 Add Teacher Profile Use Case Description
Add Teacher Profile
This use case allows the administrator to register the teacher profile
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Teacher Profile has not been created before.
Post-conditions
Teacher Profile has been successfully registered in the system
Flow of Events
1. The admin enters the teacher profile such as first name, last
name, address, phone number, sex, email, staff number and
user id.
2. The admin submits the teacher profile.
3. The system checks if the teacher profile already exist by
checking staff number and identification no with status is
active in the system
4. If the staff number does not exist, go to [5] else [A1]
5. The system checks the user id if it is already exist in the system
and the status is active
6. If the user id does not exist in the system, go to [7] else [A1]
7. The system registers the teacher profile in the system
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.1.2.2 Update Teacher Profile Use Case Description
Name
Update Teacher Profile
Description
This use case allows the administrator to update the teacher
profile in the system
Actor
Administrator
Name
Description
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
None
None
Teacher profile has already registered in the system
Teacher Profile has been successfully updated in the system
1. The admin searches the teacher profile (include View
Teacher Profile Use Case)
2. The admin updates the teacher profile
3. The admin submits the teacher profile
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.1.2.3 View Teacher Profile Use Case Description
View Teacher Profile
This use case allows the administrator to view the teacher profile
that had been registered in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Teacher profile has already registered in the system
Post-conditions
Teacher Profile has been successfully viewed from the system
Flow of Events
1. The admin searches the teacher profile by entering one of the
criteria or combination any of the criteria below:
- identification no
- first name
- user id
- staff no
2. The admin submits the criteria entered
3. The system checks if the teacher profile exist based on the
information given
4. If the teacher profile exist, the system displays a list
summary of teacher profile, else go to [A1]
5. The admin selects the required teacher profile
6. The system displays the selected teacher’s profile in details
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.1.2.4 Delete Teacher Profile Use Case Description
Delete Teacher Profile
This use case allows the administrator to delete the teacher profile
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Teacher profile has already registered in the system
Post-conditions
Teacher Profile has been successfully deleted in the system
Flow of Events
1. The admin searches the teacher profile (include View
Teacher Profile Use Case)
2. The admin selects the required teacher profile to be deleted
3. The system deletes the selected teacher’s profile
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.1.3 Maintain Student Profile
Use Case Diagrams
Add Student Profile <<include>>Display Class based on
Forms
<<include>>
Update Student Profile
Admin
View Student Profile
<<include>>
Delete Student Profile
Figure A.1.3.1 Maintain Student Profile Use Case Diagram
Use case Description
Table A.1.3.1 Add Student Profile Use Case Description
Add Student Profile Use Case
This use case allows the administrator to register the student profile
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student class has been created in the system
Post-conditions
Student Profile has been successfully registered in the system
Flow of Events
1. The admin selects the form and student’s class (Include
Display student’s class based on form)
2. The admin enters the student profile
3. The admin submits the student profile
4. The system checks if the student profile already exist by
checking identification no with status is active in the system
5. If the identification no does not exist, go to [6] else [A1]
6. The system checks the user id if it is already exist in the system
and the status is active
7. If the user id does not exist in the system, go to [8] else [A1]
8. The system registers the student profile in the system
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
Table A.1.3.2 Update Student Profile Use Case Description
Update Student Profile Use Case
This use case allows the administrator to update the student
profile in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student profile has already registered in the system
Post-conditions
Student Profile has been successfully updated in the system
Flow of Events
1. The admin searches the student profile (include View
Name
Description
2.
3.
Alternative Paths
Student Profile Use Case)
The admin updates the student profile
The admin submits the student profile
Can be aborted at any time
1. [A1] Display error message
Table A.1.3.3 View Student Profile Use Case Description
View Student Profile Use Case
This use case allows the administrator to view the student profile
that had been registered in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student profile has already registered in the system
Post-conditions
Student Profile has been successfully viewed in the system
Flow of Events
1. The admin selects the form and student’s class (Include
Display student’s class based on form).
2. The admin searches the student profile by entering one of the
criteria below:
- Student’s form and class name
- Student’s form and class name and first name
- Student’s form and class name and
identification no
- Student’s form and class name and user id
- Student’s form and class name and user id
- Student’s form and class name and user id and
identification no
Name
Description
3.
4.
5.
6.
7.
Alternative Paths
The admin submits the search criteria for the student profile.
The system check if the student profile exist by searching the
information given.
If the student profile does exist, the system display a list
summary of the student’s profile, else go to [A1].
The admin selects the required student profile.
The system displays the selected student profile’s details.
Can be aborted at any time
1. [A1] Display error message
Table A.1.3.4 Delete Student Profile Use Case Description
Delete Student Profile Use Case
This use case allows the administrator to delete the student profile
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student profile has already registered in the system
Post-conditions
Student Profile has been successfully deleted in the system
Flow of Events
1. The admin searches the student profile (include View
Student Profile Use Case).
2. The admin submits the student’s profile to be deleted.
3. The system deactivates the student profile.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.1.4 Maintain Subject
Use Case Diagrams
Add Subject
<<include>>
Update Subject
Admin
<<include>>
View Subject
Delete Subject
Figure A.1.4.1 Maintain Subject Use Case Diagram
Use Case Description
Table A.1.4.1 Add Subject Profile Use Case Description
Add Subject Use Case
This use case allows the administrator to add the subject profile in
the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Subject profile has not been created before
Post-conditions
Subject has been successfully registered in the system
Flow of Events
1. The admin selects the student’s form.
2. The admin enters the subject profile.
3. The admin submits the subject profile.
4. The system checks if the subject profile already exist by
checking subject code for the forms with status is active in the
system.
5. If the subject code does not exist, go to [6] else [A1].
6. The system registers the subject profile in the system.
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
Table A.1.4.2 Update Subject Profile Use Case Description
Update Subject Profile Use Case
This use case allows the administrator to update the subject
profile in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Subject profile has already registered in the system
Post-conditions
Subject Profile has been successfully updated in the system
Flow of Events
1. The admin searches the subject profile (include View Subject
Profile Use Case).
2. The admin updates the subject profile
Name
Description
3.
Alternative Paths
The admin submits the subject profile to be updated.
Can be aborted at any time
1. [A1] Display error message
Table A.1.4.3 View Subject Profile Use Case Description
View Subject Profile Use Case
This use case allows the administrator to view the subject profile
that had been registered in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Subject profile has already registered in the system
Post-conditions
Subject Profile has been successfully viewed in the system
Flow of Events
1. The admin searches the subject profile by entering one of the
criteria below:
- Student’s form
- Student’s form and subject code
- Student’s form and subject name
- Subject code
- Subject code and student’s form
- Subject code and subject name
Name
Description
2.
3.
4.
5.
6.
Alternative Paths
The admin submits the selected search criteria
The system checks if the subject profile already exist by
searching the criteria given and the status is active.
If the subject profile does exist, display a list summary of the
subject profile, else go to [A1]
The admin chooses the required subject profile.
The system displays the details of the chosen subject’s
profile.
Can be aborted at any time
1. [A1] Display informative message
Table A.1.4.4 Delete Subject Profile Use Case Description
Delete Subject Profile Use Case
This use case allows the administrator to delete the subject profile
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Subject profile has already registered in the system
Post-conditions
Subject Profile has been successfully deleted in the system
Flow of Events
1. The admin searches subject profile (include View Subject
Profile Use Case).
2. The admin submits the selected subject profile to be deleted.
3. The system deletes the subject profile.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display informative message
A.1.5 Maintain Student’s Class
Use Case Diagrams
Add Student Class
Update Student Class
<<include>>
Admin
<<include>>View Student Class
Delete Student Class
Figure A.1.5.1 Maintain Student’s Class Use Case Diagram
Use Case Description
Table A.1.5.1 Add Student’s Class Use Case Description
Add Student Class Use Case
This use case allows the administrator to add the student class in the
system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student class not been registered before
Post-conditions
Student class has been successfully registered in the system
Flow of Events
1. The admin selects the student’s forms.
2. The admin enters the class profile.
3. The admin submits the class profile.
4. The system checks if the class profile already exist by checking
class name for the forms with status is active.
5. If the class name does not exist, go to [6] else [A1]
6. The system registers the class profile in the system
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
Table A.1.5.2 Update Student’s Class Use Case Description
Update Student Class Profile Use Case
This use case allows the administrator to update the student class
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student class profile has already registered in the system
Post-conditions
Student class profile has been successfully updated in the system
Flow of Events
1. The admin searches the student class profile (include View
Student Class Profile Use Case)
2. The admin updates the class profile
3. The admin submits the class profile
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.1.5.3 View Student’s Class Use Case Description
View Student Class Profile Use Case
This use case allows the administrator to view the student class
that had been registered in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student Class profile has already registered in the system
Post-conditions
Student Class Profile has been successfully viewed in the system
Flow of Events
1. The admin searches the subject profile by entering one of the
criteria below:
- Student’s form
- Class name
- Student’s form and class name
Name
Description
2.
3.
4.
5.
6.
Alternative Paths
The admin submits the search criteria.
The system checks if the class profile exist by searching the
criteria given with status is active.
If the class profile exist, the system list down the class
profile information, else go to [A1].
The admin selects the required student’s class.
The system displays the details information of the selected
student’s class.
Can be aborted at any time
1. [A1] Display informative message
Table A.1.5.4 Delete Student’s Class Use Case Description
Delete Student Class Profile Use Case
This use case allows the administrator to delete the student class
in the system
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student Class profile has already registered in the system
Post-conditions
Student Class Profile has been successfully deleted in the system
Flow of Events
1. The admin searches the subject profile (include View Student
Class Profile Use Case).
2. The admin selects the class profile to be deleted.
3. The admin submits the class profile to be deleted.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display informative message
A.1.6 Maintain Reset Password
Use Case Diagrams
<<include>>
Reset Password for
Teachers
Admin
View Teacher Profile
<<include>>
Reset Password for Students
View Student Profile
Figure A.1.6.1 Reset Password Use Case Diagram
Use Case Description
Table A.1.6.1 Reset Password for Teacher Use Case Description
Reset Password for Teacher Use Case
This use case allows the administrator to reset the Teacher’s
password
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Teacher profile has already registered in the system
Post-conditions
Password teacher has been successfully reset by the system
Flow of Events
1. The admin searches the teacher profile (include View Teacher
Profile Use Case
2. Upon successfully find the teacher profile, the admin submits
the request to reset the teacher password.
3. If the password is successfully, the system change the password
to the default, else [A1]
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
Table A.1.6.2 Reset Password for Student Use Case Description
Reset Password for Student Use Case
This use case allows the administrator to reset the student’s
password
Actor
Administrator
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student has already registered in the system
Post-conditions
Password student has been successfully reset by the system
Flow of Events
1. The admin searches the student profile (include View Student
Profile Use Case
2. Upon successfully finds the student profile, the admin submits
the request to reset the student password.
3. If the password is successfully, the system change the password
to the default, else [A1].
Alternative Paths
Can be aborted at any time
[A1] Display error message
Name
Description
A.2 Teachers Module
A.2.1 Maintain Teacher Login
Use Case Diagrams
Teacher
Login
Figure A.2.1.1 Teacher’s Login Use Case Diagram
Use Case Description
Name
Description
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
Alternative Paths
Table A.2.1.1 Teacher’s Login Use Case
Teacher’s Login Use Case
This use case allows the teacher to login to the system
Teacher
None
None
Teacher profile has been created
Teacher is successfully login to the system
1. The teacher login to the system
2. The system checks if the user Id and password for the teacher is
valid.
3. If it is valid, the system allows the teacher to proceed to the
next task, else [A1]
Can be aborted at any time
1. [A1] Display error message
A.2.2 Maintain Chapter(s)
Use Case Diagrams
Add Chapter
Teacher
<<include>>
Update Teacher
<<include>>
Display Subject based on
Forms
<<include>>
View Chapter
<<include>>
Delete Chapter
Figure A.2.2.1 Maintain Chapter(s) Use Case Diagram
Use Case Description
Table A.2.2.1 Add Chapter(s) Use Case Description
Add Chapter(s) Use Case
This use case allows the teacher to add the chapter of the subject in
the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Subject profile has been created in the system
Post-conditions
Chapter Profile has been successfully registered in the system
Flow of Events
1. The system displays subject based on chosen form (include
Display Subject of Form Use Case).
2. The teacher adds the chapter profile in the system.
3. The teacher submits the profile to the system.
Alternative Paths
Name
Description
Table A.2.2.2 Update Chapter(s) Use Case Description
Update Chapter (s) Use Case
This use case allows the teachers to update the chapter’s profile
of the subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Chapter profile has already registered in the system
Post-conditions
Chapter Profile has been successfully updated in the system
Flow of Events
1. The system displays the subject based on chosen form
(include View Chapter Use Case).
2. The teacher updates the chapter profile.
3. The teacher submits the profile into the system.
Name
Description
Alternative Paths
Table A.2.2.3 View Chapter(s) Use Case Description
View Chapter (s) Use Case
This use case allows the teacher to view the chapter of the
subject that had been registered in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Chapter profile has already registered in the system
Post-conditions
Chapter Profile has been successfully viewed from the system
Flow of Events
1. The system displays the subject based on chosen form
(include Display Subject based on Form Use Case).
2. The teacher chooses subject.
3. The teacher submits the information to be searched.
4. The system displays all the chapter profile belongs to the
subject else go to [A1].
5. The teacher chooses the required chapter profile.
6. The system displays the detail information of the selected
chapter profile.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.2.2.4 Delete Chapter(s) Use Case Description
Delete Chapter (s) Use Case
This use case allows the teacher to delete the chapter of the
subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Chapter profile has already been registered in the system
Post-conditions
Chapter Profile has been successfully deleted in the system
Flow of Events
1. The system displays the subject based on chosen form
(include View Chapter Use Case).
2. The teacher chooses the chapter to be deleted.
3. The teacher submits the selected chapter to be deleted.
4. The system deactivates the selected chapter, else go to [A1].
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
A.2.3 Maintain Content of Domain Knowledge
Use Case Diagrams
Add Content Domain
Knowledge
<<include>>
Display Subject based on
Form
<<include>>
Teacher
Update Content Domain
Knowledge
<<include>>
Delete Content Domain
Knowledge
Display Chapter based on
Subject
<<include>>
<<include>>
<<include>>
Display List of Content
Domain Knowledge
Figure A.2.3.1 Maintain Content of Domain Knowledge Use Case Diagram
Use Case Description
Table A.2.3.1 Add Content of Domain Knowledge Use Case Description
Add Content Domain Knowledge Use Case
This use case allows the teacher to add the content of the domain
knowledge which based on the chapter’s subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter profile for the subject has been created
Post-conditions
Content of domain knowledge has been successfully added in the
system
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject based on Form Use Case).
2. The teacher choose subject.
3. The system displays the entire chapter that belongs to the
subject (include Display Chapter based on Subject Use Case).
4. The teacher chooses the required chapter.
5. The teacher click on ‘Add Topics’ button to add the content of
the topics.
6. The teacher enter the detail information of the topics such as:
 Topic no
 Topic name
 Topic description
Name
Description
7.
The teacher click on the ‘Add’ button to add the content into
the database, else go to [A1]
Alternative Paths
1.
[A1] System displays an error message.
Table A.2.3.2 Update Content of Domain Knowledge Use Case Description
Update Content Domain Knowledge Use Case
This use case allows the teacher to update the content of the domain
knowledge which based on the chapter’s subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Content of the domain knowledge has been created
Post-conditions
Content of domain knowledge has been successfully updated in the
system
Flow of Events
1. The teacher chooses the subject (include View Content Domain
Knowledge Use Case).
2. The teacher updates the details information of the topics such
as:
 Topic no
 Topic name
 Topic description
3. The teacher clicks on the ‘Update’ button to add the content
into the database.
Name
Description
Alternative Paths
1.
[A1] System displays an error message.
Table A.2.3.3 Display List of Content Domain Knowledge Use Case Description
Display List of Content Domain Knowledge Use Case
This use case allows the teacher to display the content of the
domain knowledge
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Content of the domain knowledge has been created
Post-conditions
Content of domain knowledge has been successfully display in the
system
Flow of Events
1. The system displays the subject based on the chosen form
(include Display Subject by Form Use Case).
2. The teacher chooses the require subject.
3. The system displays the entire chapters that belong to the
subject (include Display Chapter of Subject Use Case).
4. The teacher chooses the chapter.
4. The teacher clicks on the ‘List Contents’ button to list all the
content of the topics.
5. The system displays a list of contents belongs to the selected
chapter.
5. The teacher chooses the contents details to be displayed.
6. The system displays the details information of the content.
7. The teacher updates the details information of the topics, else
go to [A1].
Name
Description
Alternative Paths
Name
Description
1.
[A1] System displays an error message.
Table A.2.3.4 Delete Content of Domain Knowledge Use Case Description
Delete Content Domain Knowledge Use Case
This use case allows the teacher to delete the content of the domain
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
Alternative Paths
knowledge
Teacher
None
None
1. Subject profile has been created
2. Chapter for the subject has been created
3. Content of the domain knowledge has been created
Content of domain knowledge has been successfully deleted in the
system
1. The teacher chooses the required subject (include View
Content of Domain Knowledge Use Case)
2. The teacher clicks on the ‘Delete’ button to delete the selected
content.
3. The system deletes the content from the database, else go to
[A1]
1.
[A1] System displays an error message.
A.2.4 Maintain Difficulty Level of Domain Knowledge
Use Case Diagrams
<<include>>
Add Difficulty Level
<<include>>
Display Chapter based
onSubject
<<include>>
Teacher
View Difficulty Level
<<include>>
<<include>>
<<include>>
Display Subject based of
Forms
Update Difficulty Level
Delete Difficulty Level
Figure A.2.4.1 Maintain Difficulty Level of Domain Knowledge Use Case Diagram
Use Case Description
Name
Description
Table A.2.4.1 Add Difficulty Level(s) Use Case Description
Add Difficulty Level(s) Use Case
This use case allows the teacher to add the difficulty level of the
domain knowledge which based on the chapter’s subject in the
system
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
Alternative Paths
Teacher
None
None
1. Subject profile has been created
2. Chapter for the subject has been created
Difficulty level of domain knowledge has been successfully added
in the system
1. The system displays the subject based on the chosen form
(include Display Subject based on Form Use Case).
2. The teacher chooses the subject.
3. The system displays the entire chapters that belong to the
subject (include Display Chapter based on Subject Use Case).
4. The teacher chooses the required chapter.
5. The teacher enters the difficulty level for the chapter.
6. The teacher submits the entered information.
7. The system adds the difficulty level of the domain knowledge
in the system.
-
Table A.2.4.2 Update Difficulty Level(s) Use Case Description
Update Difficulty Level(s) Use Case
This use case allows the teacher to update the difficulty level of
the domain knowledge which based on the chapter’s of the
subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Content of the difficulty level has been successfully updated in
the system
Flow of Events
1. The teacher chooses the subject (include View Difficulty
Level Use Case).
2. The teacher updates the difficulty level of the domain
knowledge.
3. The teacher submits the updates information of the difficulty
level of the domain knowledge.
Alternative Paths
Name
Description
Table A.2.4.3 View Difficulty Level(s) Use Case Description
View Difficulty Level(s) Use Case
This use case allows the teacher to view the difficulty level of the
domain knowledge which based on the chapter’s of the subject
that had been registered in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Difficulty level has been successfully viewed from the system
Flow of Events
1. The system displays the subject based on the chosen form
(include Display Subject based on Form Use Case).
2. The teacher chooses the required subject.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter of Subject Use Case).
4. The teacher chooses the required chapter.
5. The teacher clicks on ‘View’ button to view the difficulty
Name
Description
level.
The system checks if the selected difficulty level for the
chapter already exists in the system.
7. If the difficulty level does exist, go to 8, else go to [A1].
8. The system displays a list of difficulty level belongs to the
chapter.
9. The teacher chooses the required difficulty level.
10. The system displays the details of the selected difficulty level
of the domain knowledge.
Can be aborted at any time
1. [A1] Display error message
6.
Alternative Paths
Table A.2.4.4 Delete Difficulty Level(s) Use Case Description
Delete Difficulty Level(s) Use Case
This use case allows the teachers to delete the difficulty level of
the domain knowledge which based on the chapter’s of the
subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Difficulty level has been successfully deleted from the system
Flow of Events
1. The teacher chooses the subject (include View Difficulty
Level of Domain Knowledge Use Case).
2. The teacher chooses the difficulty level to be deleted.
3. The teacher submits the difficulty level into the system.
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Name
Description
A.2.5 Maintain Rules
Use Case Diagrams
<<include>>
Add Rule
Display Subject based on
Forms
<<include>>
<<include>>
Teacher
Update Rule
<<include>>
Display Difficulty Level
based on Chapter
<<include>>
<<include>>
<<include>>
View Rule
Delete Rule
<<include>>
Display Chapter based on
Subject
Figure A.2.5.1 Maintain Rules Use Case Diagram
Use Case Description
Table A.2.5.1 Add Rule(s) Use Case Description
Add Rule(s)
This use case allows the teacher to add the rules of the domain
knowledge which is based on the subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty level of the chapter has been created
Post-conditions
Rules has been successfully added in the system
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject based on Form Use Case).
2. The teacher chooses the subject.
3. The system displays all chapter belongs to the subject (include
Display Chapter based on Subject Use Case) that has been
created.
4. The teacher chooses the chapter at which the rules to be added.
5. The teacher clicks on ‘add rule’ button.
6. The system popup another screen to add rule.
7. The teacher fills in the information such as:
a. Rule name and description
b. The condition of the rules (which means if the
condition of this rules if fulfill, then only the system
will proceed to the next action)
c. The action that need to be done if the condition (7 b)
is met.
Name
Description
8.
9.
The teacher submits the rules entered.
The system adds the rule in the database.
Alternative Paths
Table A.2.5.2 Update Rule(s) Use Case Description
Update Rule(s)
This use case allows the teacher to update the rules of the domain
knowledge which is based subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Content of the difficulty level has been successfully updated in
the system
Flow of Events
1. The system displays rules to be updated (include View Rules
Use Case)
2. The teacher updates the information below:
a. Rule name and description
b. The condition of the rules (which means if the
condition of this rules if fulfill, then only the system
will proceed to the next action)
c. The action that need to be done if the condition (2
b) is met.
Name
Description
3.
The teacher submits the rules updated.
Alternative Paths
4.
The system updates the rule in the database.
1.
[A1] System display error messages
Table A.2.5.3 View Rule(s) Use Case Description
View Rule(s)
This use case allows the teacher to view the rules of the domain
knowledge which is based on the subject that had been registered
in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Difficulty level has been successfully viewed from the system
Flow of Events
1. The system displays the subject based on chosen form
(include Display Subject based on Form Use Case).
2. The teacher chooses the required subject.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter based on Subject Use Case) that
has been created.
4. The teacher clicks on ‘View’ button to view the rules.
5. Teacher choose rules at which the rules to be viewed.
6. Teacher click on ‘radio’ button
7. The systems popup another screen to view the rule.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.2.5.4 Delete Rule(s) Use Case Description
Delete Rule(s)
This use case allows the teacher to delete the rules of the domain
knowledge based on the subject in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Difficulty level has been successfully deleted from the system
Flow of Events
1. The system displays rule to be deleted (include View Rules
Use Case).
2. The teacher clicks on the ‘Delete’ button to delete the rules.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.2.6 Maintain Questions
Use Case Diagrams
<<include>>
Add Question
Display Subject based on
Form
<<include>>
Update Question
Teacher
<<include>>
<<include>>
<<include>>
<<include>>
Search Question
Display Chapter based on
Subject
<<include>>
<<include>>
Delete Question
Display Difficulty Level
based on Chapter
Figure A.2.6.1 Maintain Questions Use Case Diagram
Use Case Description
Table A.2.6.1 Add Question(s) Use Case Description
Add Question(s) Use Case
This use case allows the teacher to add the questions of the domain
knowledge which is based on the difficulty level in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
Post-conditions
Question successfully created in the database
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject based on Form Use Case).
2. The teacher chooses the subject.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter based on Subject Use Case) that has
been created.
4. The teacher chooses the required chapter.
5. The system displays a list of difficulty level belongs to the chapter
(include Display Difficulty Level based on Chapter Use Case).
6. The teacher chooses the difficulty level.
7. The teacher enters the questions, answer, the correct option for the
answer, hints for the questions including the contents of the
domain knowledge that refer to the question.
8. The teacher clicks on the ‘Add’ button.
9. The system inserts the question into the database, else go to [A1].
Name
Description
Alternative Paths
Can be aborted at any time
[A1] Display error message
Table A.2.6.2 Search Question(s) Use Case Description
Update Question(s) Use Case
This use case allows the teacher to update the questions of the domain
knowledge which is based on the difficulty level in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
4. Question has been created
Post-conditions
Question successfully updated in the database
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject by Form Use Case).
2. The teacher chooses subject and chapter.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter of Subject Use Case) that has been
created.
4. The teacher chooses the required chapter.
5. The system displays a list of difficulty level belongs to the chapter
(include Display Difficulty Level based on Chapter Use Case).
6. The teacher chooses the difficulty level.
7. The teacher clicks on the ‘Search’ button.
8. The system displays the entire questions belong to the selected
difficulty level, else go to [A1].
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.2.6.3 Update Question(s) Use Case Description
Update Question(s) Use Case
This use case allows the teacher to update the questions of the domain
knowledge which is based on the difficulty level in the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
4. Question has been created
Post-conditions
Question successfully updated in the database
Flow of Events
1. The teacher chooses the question to be updated by clicking on the
question number (include Search Question Use Case).
2. The system displays the details information of the selected
question which are questions, answer, the correct option for the
answer, hints for the questions including the contents of the
domain knowledge that refer to the question
3. The teacher clicks on the ‘update’ button.
4. The system updates the modified question in the database; else go
to [A1].
Name
Description
Alternative Paths
Name
Can be aborted at any time
1. [A1] Display error message
Table A.2.6.4 Delete Question(s) Use Case Description
Delete Question(s) Use Case
Description
This use case allows the teacher to delete the questions of the domain
knowledge which is based on the difficulty level in the system
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Teacher
None
None
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
System successfully deleted from the database
1. The teacher chooses the question to be deleted by clicking on the
question number (include Search Question Use Case).
2. The system displays the details information of the selected
question which are questions, answer, the correct option for the
answer, hints for the questions including the contents of the
domain knowledge that refer to the question.
3. The teacher clicks on the ‘Delete’ button.
4. The system deletes the selected question in the database; else go to
[A1].
Post-conditions
Flow of Events
Alternative Paths
1.
[A1] Display error message
A.2.7 Maintain Quiz Configurations
Use Case Diagrams
<<include>>
Add Quiz Configuration
Display Subject based on Form
Update Quiz Configuration
<<include>>
<<include>>
<<include>>
Teacher
<<include>>
<<include>>
View Configuration
<<include>>
<<include>>
Display Chapter based on Subject
Display Difficulty Level based on
Chapter
Delete Quiz Configuration
Figure A.2.7.1 Maintain Quiz Configuration Use Case Diagram
Use Case Description
Table A.2.7.1 Add Quiz Configuration Use Case Description
Add Quiz Configuration Use Case
This use case allows the teacher to add the quiz configurations in the
system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Subject profile has been created
2. Chapter for the subject has been created
3. Difficulty Level has been created
4. Quiz configuration has not been created before for the chosen
subject
Post-conditions
Quiz configuration successfully created in the database
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject based on Form Use Case).
2. The teacher chooses the subject.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter based on Subject Use Case).
4. The teacher chooses the chapter.
5. The system displays the entire difficulty level that has been
created for the chapter’s (include Display Difficulty Level based
on Chapter Use Case).
6. The teacher chooses at which difficulty level the quiz should start.
7. The teacher enters other information as follows:
 Quiz Name
 Quiz Configuration
 Questions per Page
 Marks per Each Questions
Name
Description
8.
9.
Alternative Paths
The teacher click on the ‘Add’ button.
The system inserts the quiz configuration into the database; else go
to [A1].
Can be aborted at any time
1. [A1] Display error message
Table A.2.7.2 Update Quiz Configuration Use Case Description
Update Quiz Configuration Use Case
This use case allows the teacher to update the quiz configurations in
the system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Quiz configuration has been created before for the chosen subject
Post-conditions
Quiz configuration successfully updated in the database
Flow of Events
1. The teacher chooses at which difficulty level the quiz should be
updated (include View Quiz Configuration Use Case).
2. The teacher updates information required such as:
 Quiz Name
 Quiz Configuration
 Questions per Page
 Marks per Each Questions
Name
Description
3.
4.
The teacher click on the ‘update’ button.
The system updates the quiz configuration into the database; else
go to [A1].
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.2.7.3 Delete Quiz Configuration Use Case Description
Delete Quiz Configuration Use Case
This use case allows the teacher to delete the quiz configurations in the
system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Quiz configuration has been created before for the chosen subject
Post-conditions
Quiz configuration successfully deleted in the database
Flow of Events
1. The teacher chooses at which difficulty level the quiz should be
deleted (include View Quiz Configuration Use Case).
2. The teacher clicks on the ‘Delete’ button.
3. The system deletes the quiz configuration into the database; else
go to [A1].
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.2.7.4 View Quiz Configuration Use Case Description
View Quiz Configuration Use Case
This use case allows the teacher to view the quiz configurations in the
system
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Quiz configuration has been created before for the chosen subject
Post-conditions
Quiz configuration successfully viewed from the database
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject based on Form Use Case).
2. The teacher chooses the subject.
3. The system displays the entire chapter belongs to the subject
(include Display Chapter based on Subject Use Case) that has
been created and also the difficulty level that belongs to the
chapter. (include Display Difficulty Level based on Chapter Use
Case).
4. The teacher chooses the required chapter.
5. The system displays the entire difficulty level that has been
created for the chapter.
6. The teacher clicks on the ‘view’ button.
7. The system views the quiz configuration from the database.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.2.8 Student History Result Quiz
Use Case Diagrams
Display Class based on Form
<<include>>
Teacher
View Student History Result Quiz
<<include>>
<<include>>
Display Students based on Class
Display Subject based on Form
Figure A.2.8.1 Student History Result Quiz Use Case Diagram
Use Case Description
Table A.2.8.1 Student History Result Quiz Use Case Description
Name
Student History Result Quiz Use Case
Description
This use case allow the teacher to view the student history result quiz.
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Student has already take the quiz
Post-conditions
Student result history is successfully viewed from the database
Flow of Events
1. The system display subject based on chosen form (include Display
Subject by Form Use Case).
2. The teacher chooses the required subject.
3. The system displays all the classes that belong to the forms
(include Display Class based on Forms Use Case).
4. The teacher clicks on ‘View student history result quiz’ button.
5. The system displays all the students belong to the class (include
Display Students based on Class Use Case).
6. The teacher chooses the student to display their result history.
7. The system displays the details of the result history of the selected
students, else go to [A1].
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.3 Students Module
A.3.1 Student Login
Use Case Diagrams
Student
Login
Figure A.3.1.1 Student’s Login Use Case Diagram
Use Case Description
Table A.3.1.1 Student’s Login Use Case Description
Name
Student Login Use Case
Description
This use case allows the student to login to the system
Actor
Student
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Student has been registered in the system
Post-conditions
Student is successfully login to the system
Flow of Events
1. The student logs in to the system.
2. The system checks if the user Id and password for student is
valid.
3. If the student is a valid user, the system allows user to proceed
to the next task, else [A1]
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.3.2 Student Take Quiz
Use Case Diagrams
Get Quiz Configuration
Display Student Current and Next
Difficulty Level
Student
Perform Quiz
<<include>>
Select Questions
Display Chapter based on Subject
Perform Feedback
Figure A.3.2.1 Student Take Quiz Use Case Diagram
Use Case Description
Name
Description
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
Alternative Paths
Table A.3.2.1 Perform Quiz Use Case Description
Perform Quiz Use Case
This use case allows the student to take quiz.
Student
None
None
1. Student has already registered in the systems
Student’s successfully seats for the quiz
1. The system displays the subject based on chosen form (include
Display Subject by Form Use Case).
2. The student chooses the subject to view their latest and
recommended difficulty level of domain knowledge by clicking
‘View Latest Level of Knowledge’ button (refer to Use Case
Current and Next Recommended Difficulty Level of Domain
Knowledge).
3. Based on the subject selected, the system checks on the quiz
configuration (include Get Quiz Configuration Use Case).
4. The system displays a set of questions based on the recommended
difficulty level (include Select Question Use Case).
5. The student submits the answer.
6. The system checks the answer and does calculation.
7. The system displays the feedback information (include Perform
Feedback Use Case).
Can be aborted at any time
1. [A1] Display error message
Table A.3.2.2 Display Current and Next Difficulty Level Use Case Description
Display Student Current and Next Difficulty Level Use Case
This use case allows the student to view the current and next difficulty
level of domain knowledge
Actor
System
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Student has already registered in the system
Post-conditions
Student’s successfully view their current and next difficulty level of
domain knowledge
Flow of Events
1. The system checks on the latest student difficulty level based on
the subject selected.
2. The system checks on the student’s latest result.
3. The system checks on the rules created and get the recommended
difficulty level of domain knowledge.
4. The system displays the current and next recommended difficulty
level of domain knowledge.
Name
Description
Alternative Paths
Name
Description
Can be aborted at any time
1. [A1] Display error message
Table A.3.2.3 Get Quiz Configuration Use Case Description
Get Quiz Configuration Use Case
This use case allows the system to get the quiz configuration.
Actor
Extension Points
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
System
None
None
1. Quiz configuration has already created
1. Quiz Configuration has successfully get from the system
1. Based on the subject selected, the system gets the quiz
configuration details information.
2. The system returns all the information to the “Perform Quiz Use
Case”, else go to [A1].
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.3.2.4 Select Question Use Case Description
Name
Select Question Use Case
Description
This use case allows the system to select the questions for the quiz
Actor
System
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Quiz configuration has already created
Post-conditions
1. Quiz Configuration has successfully get from the system
Flow of Events
1. Based on the quiz configuration information, the system checks
the number of the question to be selected
2. Based on the recommended difficulty level, the system randomly
selects the questions id until it gets the total number of questions
required.
3. If the questions id is duplicate, the system will do randomization
again until it get the unique questions id, else go to 5.
4. Based on the selected questions id, the system searches the
question description.
5. The system displays the question description.
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.3.2.5 Perform Feedback Use Case Description
Name
Perform Feedback Use Case
Description
This use case allows the system to display the feedback information
Actor
Systems
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Student has already taken the quiz
Post-conditions
System successfully display the instance for the selected questions
Flow of Events
1. The system searches student’s result, a list of the question given
the wrong answer by the students and hints.
2. The system displays all the information above.
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.3.3 Student History Result Quiz
Use Case Diagrams
View Student History Result Quiz
Student
<<include>>
Display Subject based on Form
Figure A.3.3.1 Student History Result Quiz Use Case Diagram
Use Case Description
Table A.3.3.1 Student History Result Quiz Use Case Description
Student History Result Quiz Use Case
This use case allows the student to view their student history result
quiz.
Actor
Student
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Student has already seat for the quiz
Post-conditions
Student successfully viewed the result history from the database
Flow of Events
1. The system displays the subject based on chosen form (include
Display Subject by Form Use Case).
2. The student chooses the required subject.
3. The student clicks on ‘View student history result’ quiz.
4. The system displays the details of the result history of the selected
students.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
A.3.4 Use Cases Shared by All Modules
Use Case Description
Table A.3.4.1 Display Student’s Class based on Forms Use Case Description
Display Student’s Class based on Forms Use Case
This use case allows the system to display the student’s class based on
the forms
Actor
Student/Teacher
Extension Points
None
Name
Description
Extends
Pre-conditions/Assumptions
Post-conditions
Flow of Events
Alternative Paths
None
1. Forms has been created
2. Student’s Class has been created
1. Student’s Class successfully being displayed
1. The student or teacher selects the student’s form.
2. The system searches the student’s class based on the forms
selected.
3. The system displays the student’s class.
Can be aborted at any time
1. [A1] Display error message
Table A.3.4.2 Display Subject based on Forms Use Case Description
Display Subjects based on Forms Use Case
This use case allow the system to display the subjects based on the
forms
Actor
Student/Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Forms has been created
2. Subject has been created
Post-conditions
1. Student’s Class successfully being displayed
Flow of Events
1. The student or teacher selects the student’s form.
2. The system searches the subject based on the selected form.
3. The system displays the subject information.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.3.4.3 Display Chapters based on Subject Use Case Description
Display Chapter based on Subject Use Case
This use case allow the system to display the chapter based on the
subject
Actor
Student/Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Forms has been created
2. Subject has been created
3. Chapter has been created
Post-conditions
1. Student’s Class successfully being displayed
Flow of Events
1. The student or teacher selects the subject.
2. The system searches the chapter based on the subject selected.
3. The system displays the chapter information.
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message
Table A.3.4.4 Display Difficulty Level of Domain Knowledge based on Chapter Use Case Description
Name
Display Difficulty Level of Domain Knowledge based on Chapter
Use Case
Description
This use case allow the system to display the difficulty level of domain
knowledge based on the chapter
Actor
Student/Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
Post-conditions
Flow of Events
1.
2.
3.
4.
1.
1.
2.
3.
4.
5.
6.
Alternative Paths
Forms has been created
Subject has been created
Chapter has been created
Difficulty level has been created
Difficulty level has successfully being displayed
The student or teacher selects the subject.
The system searches the chapter based on the subject selected
(include Display Chapter Use Case).
The system displays the chapters.
The student or teacher selects the chapter.
The system searches the difficulty level based on the chapter.
The system displays the difficulty level information.
Can be aborted at any time
1. [A1] Display error message
Table A.3.4.1 Display Students based on Class Use Case Description
Display Student’s Class based on Forms Use Case
This use case allows the system to display the student class based on
the class
Actor
Teacher
Extension Points
None
Extends
None
Pre-conditions/Assumptions
1. Forms has been created
2. Student’s Class has been created
Post-conditions
1. Student’s profile is successfully displayed
Flow of Events
1. The teacher selects the student’s form.
2. The system gets the list of students based on the selected class.
3. The system displays the list of the students.
4. The teacher chooses the student profile to be displayed.
5. The system displays details of the student’s profile, else go to
[A1].
Name
Description
Alternative Paths
Can be aborted at any time
1. [A1] Display error message