Can u help me with forming system sequence diagram please.

Lab7 Use Case Description and System-Level Sequence Diagram

You are given:

• A description of the interaction of the actor with the Manage Courses component of a proposed system

What to do:

• For each of the following use cases, create a use case description/specification (in MS word) and one SSD (in starUML). Please use the template provided at the end of this file.
  • AddCourse
  • RemoveCourse
  • UpdateCourse
  • AddHeadInstructorToCourse

Use Case Scenarios:

Manage Courses

A system administrator (SA) performs all of the work in the Manage Courses use case. The SA is the only actor to interact with the proposed system.

When the system administrator (SA) requests to add a course, a list of programs is displayed (each course can only belong to one program). The SA chooses a program, enters the course name, description, code, length and start date and requests to add. If a course with the same name or code already exists in the DB, the SA is given an error and asked to re-enter or cancel. If the course does not already exist the SA is asked to confirm and the course is added to the DB.

A course can only be removed if there are no current registrations for that course. The course is not actually removed, just marked inactive. To request course removal the SA enters the course code and the system displays the course informationname, code, description, any current sections, etc. The SA then requests to remove the course. The system checks to make sure there are no current registrations. If there are, the SA is given an error and is not allowed to remove the course. If there are no registrations the SA is asked to enter her/his password as an extra verification. If the password is invalid, an error message appears and the SA can either try again (up to 3 tries before being locked out) or cancel. If verification is successful, the course is marked inactive in the database and the information for the deleted course is displayed showing the updated status.

To update a course the SA is first shown a list of all courses in a specific program. The SA then selects the course that is to be updatedall the course details are displayed. The SA then makes the required changes (only course description can be changed) and requests to save. The updated data is verified to ensure there are no illegal characters. IF there are then the SA is given a message and asked to either fix the errors or cancel. If all is well the updated course is displayed and the SA is asked to confirm. On confirmation the changes are saved to the DB and the course list is again displayed. The SA can continue selecting courses for update until no more updates are required at which point the main course management menu is displayed.

Only active instructors can be added to courses; and courses must be active for an instructor to be added. When a SA requests to add a head instructor to a course, a list of programs is displayed and the SA must select a program. Once a program is selected a list of active courses in that program that do not yet have a head instructor is displayed and the SA selects one of the courses. All of the course information for the selection is displayed as well as a list of active instructors. The SA selects one of the instructors and requests to add as a head instructor to the course. The system requests confirmation, the SA confirms, and the instructor is added as head instructor and the updated course showing the newly added head instructor is displayed. If the SA cancels, the list of instructors is again displayed and the SA can choose another instructor or cancel out of the use case.

System Sequence Diagram?