Scribd
Upload
124 views4 pages

Actor Goal List

The document contains 5 use cases for an admission test management system: 1. Take Test - Allows a candidate to log in and take an exam by displaying questions and saving answers. 2. Set Format - Allows a formatter to create exam categories, set timing, marks criteria, and save the format. 3. Submit Questions - Allows a question setter to enter questions and solutions in each category. 4. Manage User - Allows an administrator to create, modify, or delete users like question setters and formatters. 5. Generate Report - Allows a coordinator to select criteria and generate reports for higher authorities.

Uploaded by

Mani Khan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
124 views4 pages

Actor Goal List

The document contains 5 use cases for an admission test management system: 1. Take Test - Allows a candidate to log in and take an exam by displaying questions and saving answers. 2. Set Format - Allows a formatter to create exam categories, set timing, marks criteria, and save the format. 3. Submit Questions - Allows a question setter to enter questions and solutions in each category. 4. Manage User - Allows an administrator to create, modify, or delete users like question setters and formatters. 5. Generate Report - Allows a coordinator to select criteria and generate reports for higher authorities.

Uploaded by

Mani Khan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

ACTOR GOAL LIST

ACTOR GOAL
Candidate • Perform Test.

Test Formatter • Set Timing.


• Set Paper Format.
• Set Marks Criteria.
Question Setter • Add Questions in each category with solution.

Question Reviewer • Review Questions.

Administrator • Manage Users.

Program Coordinator • Generate Reports.

Dean/HOD • View Reports.


Use Case UC1 : Take Test
Scope : Admission System
Level : User Goal
Primary Actor : Candidate
Stakeholder/Interest : Examination Faculty
Preconditions : Candidate must be registered.
Success Guarantee : All the attempted questions are saved.
Main Success Scenario :
User System
1. Use Case begins when candidate enter his/her 2. System verify the candidate data and generate test.
credentials into the system.
3. Candidate start test. 4. System display the test.
5. Candidate select the answer. 6. System display next question.
7. After an interval of time system saves answer of
attempted questions.
8. Candidate ends the test. 9. System saves all the answers of attempted questions
and terminates the use case.

Extensions :

*a. Power Failure


1. On starting system candidate re-enter his/her 2. System verify the candidate data and open the
credential. remaining test.
2a. Invalid Data
1. System ask to re-enter credentials.
5a. Skip Question
1. Candidate skip question. 2. System saves the skip question.
5b. Exit
1. Candidate select to exit test. 2. System asks for sure.
3. if user select Yes. 4. System re saves all the answers of attempted
questions and terminates the use case.
5. if user select No. 6. System return to use case.
6a. Question Ends
1. System re saves all the answers of attempted
questions and terminates the use case.

Frequency of occurrence : 1

_____________________________________________________
Use Case UC2 : Set Format
Scope : Admission System
Level : User Goal
Primary Actor : Formatter
Stakeholder/Interest : Reviewer.
Preconditions : Formatter must be logged in and decision to make format is taken by higher authorities.
Success Guarantee : Paper Formate is made and saved successfully.
Main Success Scenario :
User System
1. Formatter creates categories.
2. Formatter enter Marks ,time and number of 3. System saves the whole format.
question for each categories.

Extensions :

*a. Power Failure


1. On starting system formatter re-enter his/her 2. System verify the formatter data.
credential.
3. Formatter re-enter the format and commit. 4. System saves whole format
Frequency of occurrence : Depends upon Administration.

_____________________________________________________

Use Case UC3 : Submit Questions


Scope : Admission System
Level : User Goal
Primary Actor : Question Setter
Stakeholder/Interest : Reviewer
Preconditions : Categories are made and question setter must be logged in.
Success Guarantee : Question saved in each category successfully.
Main Success Scenario :
User System
1. Question Setter enters questions and also solution in 2. System saves question and solutions in each
each category. category.

Extensions :

*a. Power Failure


1. On starting system, question setter re-enter his 2. System verify the question setter data and open the
credential. remaining empty categories.

Frequency of occurrence : 1

_____________________________________________________
Use Case UC4 : Manage User
Scope : Admission System
Level : User Goal
Primary Actor : Administrator
Stakeholder/Interest : Question Setter, Formatter, HOD/Higher Authorities, Reviewer
Preconditions : Administrator must be logged in and decision to manage users is taken by higher authorities.
Success Guarantee : User created or deleted or modified and account successfully saved.
Main Success Scenario :
User System
1. Administrator select a user to modify. 2. System displays the selected user options.
3. Administrator then enter regarding user details. 4. System saves the modified user.

Extensions :

*a. Power Failure


1. On starting system administrator re-enter his/her 2. System verify the administrator data.
credential.
1a. Candidate selected
1. System ask to enter list of candidates.
2. Administrator enters candidate list. 3. System save all the candidate list.

Frequency of occurrence : 1
_____________________________________________________

Use Case UC5 : Generate Report


Scope : Admission System
Level : User Goal
Primary Actor : Program Coordinator
Stakeholder/Interest : HOD/DEAN/Higher Authorities
Preconditions : Test is completed and result is generated. User logged in.
Success Guarantee : Desiring Report is generated.
Main Success Scenario :
User System
1. User select a criteria to generate report. 2. System generate the report
Extensions :
*a. Power Failure
1. On starting system user re-enter his/her credential. 2. System verify the user data.
3. User re-enter criteria. 4. System generate the report.
5. User commit and select to send report to higher
authorities

Frequency of occurrence : Depend upon higher authorities order.

_____________________________________________________

You might also like