ADVANCE SOFTWARE ENGINEERING

USECASE ASSIGNMENT

RIDA MARYAM
I19-1298
MS-SE
EXPANDED USECASE 1:
USECASE NAME: REGISTER COURSE

SCOPE: Online University System

LEVEL: User Goal

PRIMARY ACTORS: Student

STAKEHOLDERS • Student/Academic Officer: Can add, delete or view

AND INTERESTS: Courses.

PRECONDITIONS: • Student should be logged in.

SUCCESS • Student adds, delete and view Courses.

GUARANTEE (POST • Student gets expected result.
CONDITIONS):

MAIN SUCCESS SCENERIO:

Actor action System Responsibility

1- Student enters the student ID

Number and Password.

2- System verifies that the

student ID Number and
Password is Valid.
3- System prompts the student
to select the current
semester or future semester.

4- Student enters the desired

semester.
 5- System prompts the student
to add, delete, view the
courses.
6- Student enters the desired
data.

7- System checks pre-

requisites for the course are
passed.
8- System adds student to the
offered course and displays
output.
9- Student logged out of the
system.

EXTENSIONS: a-Failure occurred:

1-Application signals error. And does not open the

application.

2-Backup server will help to reboot the application.

SPECIAL • The language of the system must be in English.
REQUIREMENTS: • Font should be large enough to make the text visible
from suitable distance.
• System must be compatible with multiple operating
systems.
• Response time should be less than 1 minute.
• Fast recovery from an unexpected failure.
• No garbage data.
• GUI must be user-friendly.

TECHNOLOGY AND No new technology is needed.

DATA VARIATIONS
LIST:

FREQUENCY OF Could be nearly continuous.

OCCURANCE:
EXPANDED USECASE 2:
USECASE NAME: ADD/DROP COURSE

SCOPE: Online University System

LEVEL: User Goal

PRIMARY ACTORS: Student/Academic Officer

STAKEHOLDERS • Student/Academic Officer: Can add/drop Courses.

AND INTERESTS:

PRECONDITIONS: • Student/Academic Officer should be logged in.

SUCCESS • Student adds/drop Courses.

GUARANTEE (POST • Student gets expected result.
CONDITIONS):

MAIN SUCCESS SCENERIO:

Actor action System Responsibility

1- Student enters the student ID

Number and Password.

2- System verifies that the

student ID Number and
Password is Valid.
3- Student wants to add/drop
courses.

4- System prompts the student

to select add/drop option.
 5- Student enters the desired
data.

6- System adds/delete student

from the offered course.
7- Student logged out of the
system.

EXTENSIONS: a-Failure occurred:

1-Application signals error. And does not open the

application.

2-Backup server will help to reboot the application.

SPECIAL • The language of the system must be in English.
REQUIREMENTS: • Font should be large enough to make the text visible
from suitable distance.
• System must be compatible with multiple operating
systems.
• Response time should be less than 1 minute.
• Fast recovery from an unexpected failure.
• No garbage data.
• GUI must be user-friendly.

TECHNOLOGY AND No new technology is needed.

DATA VARIATIONS
LIST:

FREQUENCY OF Could be nearly continuous.

OCCURANCE:
EXPANDED USECASE 3:
USECASE NAME: PURCHASE ITEM

SCOPE: Online Shopping System

LEVEL: User Goal

PRIMARY ACTORS: Customer

STAKEHOLDERS • Customer: Can add, delete items to the cart.

AND INTERESTS:

PRECONDITIONS: • Customer should be logged in.

SUCCESS • Customer adds, deletes and views items of the cart.

GUARANTEE (POST • Customer gets the receipt of the selected items.
CONDITIONS):

MAIN SUCCESS SCENERIO:

Actor action System Responsibility

1- Customer logs in to the

system.

2- System verifies the

customer.
3- System prompts the
customer with all available
items

4- Customer puts the desired

items to the cart.

5- System generates the receipt

for selected items.
 6- Customer logged out of the
system.

EXTENSIONS: a-Failure occurred:

1-Application signals error. And does not open the

application.

2-Backup server will help to reboot the application.

SPECIAL • The language of the system must be in English.
REQUIREMENTS: • Font should be large enough to make the text visible
from suitable distance.
• System must be compatible with multiple operating
systems.
• Response time should be less than 1 minute.
• Fast recovery from an unexpected failure.
• No garbage data.
• GUI must be user-friendly.

TECHNOLOGY AND No new technology is needed.

DATA VARIATIONS
LIST:

FREQUENCY OF Could be nearly continuous.

OCCURANCE: