Posted: April 13th, 2023

UML Diagram

INFS 720 – Systems Analysis and Design Assignment 06
Page 1 of 2
The context is the Internship Application (automated presentation scheduling, evaluation and feedback).
Recall that preconditions are assumed to be true so do not include any information in your sequence
diagrams to support the pre-conditions (to be clear, do not bother with login interactions). Also, to
simplify the exercise, do not include the alternative or exception flows. Just focus on the normal flow.
Based on the UC-3 Configure Schedule use case below, create a UML sequence diagram and associated
UML class diagram. Be sure to include properly named messages, parameters and if appropriate,
relevant return information.
Annotate your sequence diagram decisions with "by xxxxx" notations indicating how you applied the
initial 5 GRASP principles to your design. See figure 17.4 where the author notes, "by Creator" as an
example and the presentation slides.
Use Lucidchart or similar program to create your diagrams and save them in PDF document. Submit the
PDF files to D2L.
ID and Name: UC-3 Configure schedule
Created By: Dave Bishop Date Created: 1/1/2016
Primary Actor: Instructor Secondary Actors: None
Description: Configure the semester schedule for a section of EGR 405. Designate a start date
and end date for the presentation schedule. Also designate the default number of
slots per meeting date.
Trigger: Start of a semester
Preconditions: PRE-0. The current user is an authenticated Instructor
PRE-1. The list of semesters has been populated
PRE-2. The list of sections has been populated
Postconditions: POST-1. An empty schedule is created commencing with the designated start date
and concluding with the specified end date.
POST-2. Each meeting date has the designated number of empty slots available.
POST-3. The schedule’s availability to students will conform to the instructor’s
designation via the “release to students” component.
Normal Flow: 1.0 Configure schedule
1. The system asks the Instructor for the desired semester and section.
2. The Instructor supplies the semester and section letter
3. The system requests the first day of presentations
4. The Instructor supplies the first day of presentations
5. The system requests the last day of presentations
6. The Instructor supplies the last day of presentations
7. The system requests the number of presentation slots per meeting date
INFS 720 – Systems Analysis and Design Assignment 06
Page 2 of 2
8. The Instructor supplies the number of presentation slots per meeting date
9. The system requests whether to release the schedule to students or not
10. The Instructor indicates whether to release or not
11. The system provides a means to initiate the creation of the schedule
12. The Instructor indicates to create the schedule
Alternative Flows: 12.1 A schedule exists for the semester and section
1. Warn the Instructor that continuing will wipe out existing schedule information
and ask the Instructor if s/he wants to continue
2. If yes – remove the existing schedule and create the new schedule
3. If no – inform the Instructor that no changes will be made and leave the
existing information
Exceptions: 12.1 Violation of Business Rules
1. The system will not create a schedule
2. Display the appropriate informational message(s)
12.2 Navigate away from page without creating a schedule
1. The system will not create a schedule
Priority: High
Frequency of Use: Low
Business Rules: BR-1, BR-2, BR-3
Other Information:
Assumptions:
Business Rules for Internship App
ID Rule Definition Type of
Rule
Static or
Dynamic
Source
BR-1 A presentation schedule’s start date must be
less than the presentation schedule’s end date
Fact Static Instructor
BR-2 A presentation schedule’s end date must be
greater than the presentation schedule’s start
date
Fact Static Instructor
BR-3 The start and end date must be on the same
day of the week
Fact Static Instructor