Subject: Software Engineering Assignment

Use case 1: User Login:

Actor: Admin, Faculty, or Student

Basic Flow

1. User clicks the login link or enters the login URL into the browser.

2. The system displays login page.

3. User clicks login (Submit) button after entering the credentials and roles.

4. According to the role, the system retrieves a “User List”.

5. The system checks to see if the username exists in the “User List”.

6. If the account exists, the system compares the password.

7. If the input password is valid, based on the role provided, the system starts an authenticated session, retrieve Faculty List and displays View Faculty page (landing page).

Alternate Flow

Invalid username or password: The system checks to see if the username exists in the “Users”. If the username is not found, the system displays a message “Invalid username. Click on “OK” to try again.” The user clicks on the “OK” button. The system redisplays login page. User clicks on the forgot username link. The system asks user to enter his/her email address. User enters the email address associated with his/her account. The system displays a message ”Username was sent to your email.”

Activity Diagram for User Login.

Robust Analysis :-

Use Case 2: Admin Adds Student

s

Normal Flow:

1. Admin selects the “Students” tab in the “Admin home page”,

2. System retrieves Student list and displays “Student View” page.

3. Admin clicks “New Student” button.

4. System displays “Add student” page.

5. Admin Provides student details by selecting the institute name from dropdown box, enters student’s details

6. Admin clicks on “Save” button.

7. System validates the entered data;

8. System Save data to the database, if valid.

9. System displays successfully saved message on top of student list, which includes the new added student.

Activity Diagram for Admin Adds Student:-

Robust Analysis:-

Use case 3: Team Member Makes Comments on Assessment Done by other Members:

Basic Course:

1. Student clicks “Make a Comment” button on the “View Peer Assessment” Page.

2. The system checks the Session to make sure the student is logged in and then displays a Write Comment page with a multi-line Text box.

3. Student writes a comment on the comment box.

4. Student clicks on the “Save” button.

5. The system validates the comment (e.g. not too long, or too short).

6. If the comment validation is ok, the system displays a confirmation page, and send the comment to Instructor for approval.

States Machine for “comments on assessment”

Comments created by evaluate

Comments Approved by instructor

Comments displayed to students

Comments disapproved by instructor

Comments revised by evaluate

Alternate Course

Too long or short comment: The system displays a message “Comment length is out side the allowable range. Click on “OK” to try again.”

Activity Diagram:-

Robust Analysis:-

Use case 4: View and manage Classes Page

Activity Diagram:-

Robust Analysis:-

Use case 5: View and manage Rubrics Page

Activity Diagram:-

Robust Analysis:-

Use case 6: View and manage Faculty Page

Activity Diagram:-

Robust Analysis:-

Use case 7: View and manage Teams Page

Robust Analysis:-

Salendri Udaysri Yadav

700700707