0% found this document useful (0 votes)
41 views6 pages

Full Dressed Use Case For Fiwivle System

The document describes three use cases for a FiWiVle online learning system: 1) Process Login, where an end-user logs into the system, 2) Upload Quiz, where a lecturer uploads a quiz for students to complete, and 3) Upload Assignments, where a student uploads a completed assignment. Each use case specifies the scope, level, actors, stakeholders, preconditions, postconditions, main flow, and extensions. The use cases focus on authentication, uploading and accessing course content, and managing assignments.

Uploaded by

SuperFly Smith
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views6 pages

Full Dressed Use Case For Fiwivle System

The document describes three use cases for a FiWiVle online learning system: 1) Process Login, where an end-user logs into the system, 2) Upload Quiz, where a lecturer uploads a quiz for students to complete, and 3) Upload Assignments, where a student uploads a completed assignment. Each use case specifies the scope, level, actors, stakeholders, preconditions, postconditions, main flow, and extensions. The use cases focus on authentication, uploading and accessing course content, and managing assignments.

Uploaded by

SuperFly Smith
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Full Dressed Use Case for FiWiVle System

Complete Quiz
Upload Quiz
Upload Assignments
Access Grades
Messaging
Process Login
Upload Documents
Assign Grades
Download Assignments

Use Case 1 Process Login

Scope: System-wide

Level: User-goal

Primary Actor: End-User

Supporting Actor: Records Management System

Stakeholders and In- • User: A user would like to login,


terests:
• Stakeholder 2 name: his interests

Preconditions:

Postconditions:

Main Success Scenario:


1. The first action
2. The second action

Extensions:
2.a Invalid login data:
1. System shows failure message
2. User returns to step 1
5.a Invalid subsriber data:

1. System shows failure message


2. User returns to step 2 and corrects the errors

1
Special Requirements: • first applicable non-functional requirement
• second applicable non-functional requirement

Technology and Data Variations List:


1a. Alternative first action with other technology

Frequency of Occurrence:

2
Use Case 1 Complete Quiz

Scope: System-wide

Level: User-goal

Primary Actor: Student

Description When a student is viewing his/her course container, they


will be able to see quizzes assigned to them by the lecturer

Stakeholders and In- • Student: A student wants to complete quizzes as-


terests: signed to them by a lecturer and to be informed of
the status of their attempt ie (grade of the quiz and
whether or not the quiz has successfully completed.)

• Lecture: his interests

Preconditions: • The student is authenticated.


• The student is viewing the course container to which
the quiz is assigned.

Preconditions: • The students responses to the quiz has been saved.


• The student sees a message indicating the status of
the quiz (completed/grade)*fix

Main Success Scenario:


1. The student selects the quiz they are assigned.

2. FiWiVLE display’s the quiz summary.


3. Student selects the option to begin the quiz
4. Student fills in their responses to the questions in the quiz.

Extensions:

3
3.a Quiz start time has not started:
1. System shows failure message
2. Student returns to step 2
3.a Student has used all attempts at quiz:
1. System shows failure message
2. Student returns to step 2.

4.a Allotted duration for the quiz has elapsed, or the end time for the quiz has been
reached. :
1. System shows status of the quiz to student.
2. Student returns to step 2

Special Requirements: • The quiz should maintain state i.e

Technology and Data Variations List:


1a. Alternative first action with other technology

Frequency of Occurrence:

Use Case 2 Upload Quiz

Scope: System-wide

Level: User-goal

Primary Actor: Lecturer

Description When a lecturer is viewing their course container. They


will be able to assign quizzes to the students, and specify
options such as, start-time, end-time, duration,.

Stakeholders and In- • Lecture: The lecturer would like to assign quizzes
terests: to students, for practice, or as a component of their
course grade.
• Student: his interests

Preconditions: • The Lecturer is authenticated.


• The Lecturer is viewing the course container to which
they want the quiz to be assigned.

4
Postconditions: • The quiz is added to the course container.

Main Success Scenario:


1. The lecturer select’s the option to create a quiz .
2. The lecturer specifies the details for the quiz(duration, start-time, end-time, stu-
dents allowed to do quiz).

3. Lecturer adds the questions to be done for the quiz.


4. Lecturer finalizes by confirming the specified details and questions.
5. Quiz is available on the course container for the student(s).

Extensions:
5.a Lecture does want the quiz to be visible:
1. Lecturer can see and edit the quiz.
2. Quiz is not visible to the student(s) on the container

Frequency of Occurrence:

Use Case 3 Upload Assignments

Scope: System-wide

Level: User-goal

Primary Actor: Student

Stakeholders and In- • Lecturers: Want’s to add a section where, students


terests: can upload thier attempt at an assignment.

• Student: Wants to upload assignments.

Preconditions: • Student is authorized.


• The student is viewing the course container for the
assignment.

Postconditions: The assignment is uploaded, and is available to be accessed


by the Lecturer.

Main Success Scenario:

5
1. The student selects assignment section.
2. FiWiVLE display’s the assignment summary.

3. Student attaches the file to be uploaded.


4. Student confirm’s the assignment that will be uploaded.
5. Message is displayed showing status of the upload.

Extensions:
4.a Student no longer wants to upload thier assignment :
1. Student return’s to step 2.
2.a Assignment is not open for submission.
1. Student is prevented from uploading

2.a Assignment due time has passed and late submissions not allowed.
1. Student is prevented from uploading.

Special Requirements: • first applicable non-functional requirement


• second applicable non-functional requirement

Technology and Data Variations List:


1a. Alternative first action with other technology

Frequency of Occurrence:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy