Develop A Sequence Diagram For Each Use Case

Develop a sequence diagram for each use case

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 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 saves 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 sends 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 outside the allowable range.” Click on “OK” to try again. Activity Diagram: — Robust Analysis — Use case 4: View and manage Classes Page Normal Flow 1. The admin selects a school and a faculty. The system returns a list of classes based on the selection. 2. The admin indicates they wish to edit a class. 3. The system provides a form for editing the class. 4. The admin fills it appropriately and submits it. 5. The system saves the changes and returns the new information. Alternate Flows: The admin selects a class from the list returned by the system. The system displays all courses for the class. The admin indicates their wish to update the courses for that class. The system proceeds to save the changes and notifies the notifiable entities. Activity Diagram: — Robust Analysis — Use case 5: View and manage Rubrics Page Normal Flow 1. The admin selects a school and a faculty. 2. The system returns a list of rubrics based on the selection. 3. The admin indicates they wish to update a Rubric’s details. 4. The system provides a form for editing the rubric. 5. The admin fills it appropriately and submits it. 6. The system saves the changes and returns a success message. 7. The system provides a form for adding a new faculty. 8. The admin fills it appropriately and submits it. 9. The system verifies the information and saves the changes. Alternate Flows: The admin selects a school from the list returned by the system. The system displays all rubrics for the school. The admin indicates their wish to remove a rubric from a faculty. The system proceeds to save the changes, and notifies the notifiable entities. Activity Diagram: — Robust Analysis — Use case 6: View and manage Faculty Page Normal Flow 1. The admin fills in the login form and submits. 2. The system verifies their credentials and logs them in to their account. 3. The admin selects an option they wish to perform. 4. The system processes their requests and alerts the admin of either a success or failure status. 5. The admin indicates they wish to logout of the system. 6. The system securely logs them out of their session. 7. The system provides a form for adding a new faculty. 8. The admin fills it appropriately and submits it. 9. The system verifies the information and saves the changes. Alternate Flows: None. Activity Diagram: — Robust Analysis — Use case 7: View and manage Teams Page Normal Flow 1. The admin selects a class. 2. The system then displays teams for the selected class. 3. The admin indicates their wish to update the list of team members. 4. The system saves the changes and returns a success message. 5. The admin selects a class. 6. The system then provides a form for creating a new team. 7. The admin fills out the form accordingly and submits it. 8. The system saves the changes and returns a success message. Alternate Flows: None. Robust Analysis — Salendri Udaysri Yadav

Paper For Above instruction

Develop a sequence diagram for each use case

The creation of sequence diagrams is fundamental in modeling the interactions between actors and systems within different use cases. In this context, detailed sequence diagrams for seven typical use cases in an academic or administrative system are developed to illuminate user-system interactions, process flows, and decision points. These diagrams will help clarify how various roles—such as Admin, Faculty, and Student—interact with the system in different scenarios, ensuring precise understanding for developers and stakeholders.

Use Case 1: User Login

The sequence diagram for user login involves multiple actors and steps. The process begins with the User (Admin, Faculty, or Student) clicking the login link or entering the URL, prompting the system to display the login page. Upon entering credentials and selecting roles, the User submits this information. The system then retrieves a list of users and checks for the entered username. If the username exists, the system compares input passwords. A successful match results in starting an authenticated session and redirecting to the Faculty View page. If the username is invalid or password mismatch occurs, appropriate error messages are displayed, and the login is retried. The system also provides a “forgot username” feature, which prompts the user to enter their email, and, if successful, sends the username via email.

Use Case 2: Admin Adds Student

In the process where an Admin adds a new student, the sequence begins with the Admin selecting the Students tab, prompting the system to retrieve and display the current student list. The Admin clicks “New Student”, which directs the system to show the add student form. After filling in student details—selecting institute names and entering data—and clicking save, the system validates and stores the data if valid, then displays a success message. This sequence ensures accurate data entry and confirmation of the new student record.

Use Case 3: Team Member Comments on Assessment

For a student commenting on peer assessments, the sequence involves the student clicking “Make a Comment”, with the system verifying login status before displaying a comment input form. The student writes and submits the comment, which is validated for length and content. If valid, the comment is sent for instructor approval, with status states and machine logic supporting different outcomes—approved, disapproved, or revised. Validation messages guide the student if the comment exceeds permitted length.

Use Case 4: Manage Class Page

The sequence for managing class pages starts with the admin selecting a school and faculty, prompting retrieval of associated classes. The admin can then choose to edit class details, which loads an editing form. After entering updates and submitting, the system saves and confirms changes. Additional flows include updating courses for a specific class, ensuring the class data remains current and accurate.

Use Case 5: Manage Rubrics

The process involves selecting a school and faculty, leading to a list of rubrics. The admin can update rubric details by filling and submitting an editing form, which gets saved and confirmed. The admin can also add new faculties, with similar validation and storage. Removing rubrics involves selecting and confirming deletions, with the system updating records and notifying appropriate entities.

Use Case 6: Manage Faculty Page

This sequence begins with admin login verification, followed by performing requested actions such as adding or editing faculty details. Success or failure messages are displayed accordingly. The process emphasizes secure login, data validation, and clear user feedback, maintaining professional standards in system management.

Use Case 7: Manage Teams

Team management involves the admin selecting a class, which results in displaying associated teams. Changes to team members are saved with confirmation messages. Creating new teams follows a similar pattern—filling out a form, submitting, and confirming the update, ensuring effective team structure management within the system.

Conclusion

In sum, these sequence diagrams offer a comprehensive visualization of user interactions and system processes across various use cases. They support clarity in design, aid in identifying potential bottlenecks, and foster system robustness through precise, step-by-step modeling. Properly constructed diagrams play an essential role in system development, improving communication among stakeholders and ensuring alignment with user requirements.

References

• Object Management Group. (2017). UML Specification. https://www.omg.org/spec/UML/2.5.1
• Jacobson, I. (2015). The Object-Oriented Software Engineering Approach. Addendum to UML Standard. Springer.
• Fowler, M. (2010). UML Distilled, Third Edition. Addison-Wesley.