1.4 Airline Learning Activity

Airline 1.4: Update the Class Diagram to Include Method Parameters

Create three separate Violet files: a class diagram, a sequence diagram, and an activity diagram. Complete each diagram in its own section below. Copy the text inside the plain-text markers without typing the markers.

1.Add parameters to the existing class operations
A Save your Airline 1.3 class diagram as 1.4

Open your Airline 1.3 class diagram and use Save As to create Airline 1.4 LastName.class.violet.html. Preserve the 1.3 file. Keep the five classes, all attributes, and the five existing associations with 1 at both ends. Do not add a Gate-to-Jet association.

B Update the two operation signatures

In Jet, change + TaxiToGate() to + TaxiToGate(timeTaken: double). In Gate, change + ConfirmArrival() to + ConfirmArrival(gateName: string). A parameter name and type belong inside the operation's parentheses, not in the attributes compartment.

C Check all five operation entries

Airport contains + DeplaneArrival(). Jet contains + CommunicateGate(), + OpenCargoDoor(), and + TaxiToGate(timeTaken: double). Gate contains + ConfirmArrival(gateName: string). Leave the operations compartments of Airline and Terminal empty. Keep Gate's + Name: string attribute and the other fields unchanged. Do not add return-type text in this module.

Update the Sequence Diagram to Show Method Parameters
2.Use your Airline 1.3 sequence diagram as the baseline
A Save your 1.3 sequence diagram as 1.4

Open your Airline 1.3 sequence diagram. Use Save As to create Airline 1.4 LastName.seq.violet.html, replacing LastName with your last name. Preserve your 1.3 file and the existing five calls and activation nesting.

B Match the four participant lifelines

Keep the participants in this left-to-right order: MainWindow : Window, CWA : Airport, Airplane : Jet, and GateA : Gate. Rename the 1.3 participant Airport : Airport to CWA : Airport. This changes its displayed instance name, not its class or its position in the interaction.

C Add the two parameter labels

For this diagram, show the formal parameter names and types on the two call arrows. These labels summarize the method inputs; they are not concrete C# argument expressions. Use the exact labels below rather than inventing argument values.

Change the Jet self-call from TaxiToGate() to TaxiToGate(timeTaken: double). Change the Airport-to-Gate call from ConfirmArrival() to ConfirmArrival(gateName: string). Keep DeplaneArrival(), CommunicateGate(), and OpenCargoDoor() unchanged.

D Check receivers and nested call order

Read the calls from top to bottom: MainWindow → CWA DeplaneArrival(); CWA → Airplane CommunicateGate(); Airplane → itself TaxiToGate(timeTaken: double); CWA → Airplane OpenCargoDoor(); CWA → GateA ConfirmArrival(gateName: string).

Keep the TaxiToGate activation nested inside CommunicateGate on the same Jet lifeline. Finish that nested work before OpenCargoDoor, then ConfirmArrival. Keep exactly four participants and five calls. Do not add return values or dashed return arrows.

Create an Activity Diagram Representing an if Statement
3.Read the luggage-check code

Inside an existing luggage-processing method, PlaneSideCheckLuggage is a Boolean input. OpenCargoDoor() performs that action and returns void. Model only this excerpt.

Airline source to diagram
if (PlaneSideCheckLuggage)
{
    OpenCargoDoor();
}
A Draw the condition and its one conditional action

Connect the start to PlaneSideCheckLuggage. Label true and false routes true and false. True reaches action OpenCargoDoor. False goes directly to the final node. Connect OpenCargoDoor directly to that same final node. Use one start, one decision, one action, and one final node; do not add a merge diamond.

B Check both inputs

With true, OpenCargoDoor runs once. With false, the activity ends without running that action. Do not add an else action, another decision, or a loop.

Save and Submit
4.Save, check, and submit your diagrams
A Save the required Violet diagram files

Submit one class diagram, one sequence diagram, and one simple-if activity diagram. Use Airline 1.4 LastName as the base filename, replacing LastName with your last name. The class, sequence, and activity diagram-type suffixes distinguish the three files. Keep Violet's generated .violet.html extension and diagram-type suffix.

B Check scope, labels, and paths before packaging

Check every exact label, field type, direction, multiplicity, value, and reference target against this page. Open the saved files in Violet and inspect for missing connections, unreadable crossings, or clipped text.

C ZIP the saved diagram files

Put the diagram files at the ZIP root, not inside another folder. Name the archive Airline 1.4 LastName.zip. Do not include C# snippets, unrelated assignments, or instructor reference files.

D Submit the ZIP to the Feedback System

Use the matching Airline activity. Review the feedback, correct your diagrams, save, rebuild the ZIP, and resubmit as needed.

E Submit the resulting feedback URL to Canvas

Paste the resulting URL into the matching Canvas assignment. Keep your editable Violet files for later work.