Update your Airline 1.2 class diagram with arrival methods, then create a separate sequence diagram showing the arrival calls. Complete the class diagram first so each message matches a method in its receiver class. Read the supplied C# or requirements to build the diagrams; submit Violet diagrams rather than a C# project.
Copy exact diagram text from the literal spans without typing their surrounding markers. Put relationship names on connecting lines and branch conditions on arrows. The named instances help you follow identity; the values inside a box describe its current state.
Open your Airline 1.2 class diagram in Violet and save a copy with the base filename Airline 1.3 LastName. Keep the five classes: Airline, Airport, Terminal, Gate, and Jet.
Keep Gate's + HasSkyway : bool, + Name: string, and + PlaneSideCheckLuggage : bool. Keep every other attribute from your Airline 1.2 class diagram.
Enter each signature on its own line in the methods compartment below the fields. The + marks a public method. Empty parentheses mean there are no parameters. These methods return no value. Enter the signatures exactly as shown below, without adding return-type text.
| Class | Exact method text |
|---|---|
Airport |
+ DeplaneArrival() |
Jet |
+ CommunicateGate()+ OpenCargoDoor()+ TaxiToGate() |
Gate |
+ ConfirmArrival() |
Leave the methods compartments of Airline and Terminal empty.
Keep the five existing associations: Airline to Airport labeled + Airport, Airline to Jet labeled + Airplane, Airport to Terminal labeled + MainTerminal, and the two Terminal to Gate lines labeled + GateA and + GateB. Each existing association has 1 at both ends. Keep relationship names on the lines rather than duplicating them in the fields compartments. Check the five new methods. The completed diagram has five class boxes and five associations. Do not add a + Plane association; that addition belongs to Airline 1.6.
The participants are MainWindow : Window, Airport : Airport, Airplane : Jet, and GateA : Gate. Window is the interface that starts the interaction; keep it outside the five-class business design.
For this interaction, the local references airport, airplane, and gateA refer to the already-existing objects displayed as Airport : Airport, Airplane : Jet, and GateA : Gate. The method-body excerpts use those supplied local references; they do not add fields or association lines to your class diagram.
The excerpts below show the method bodies to trace. CommunicateGate calls the jet's own TaxiToGate method. TaxiToGate, OpenCargoDoor, and ConfirmArrival finish their work without making further modeled calls. All five methods take no parameters and return void.
// Inside the Window event handler
airport.DeplaneArrival();
// Inside Airport.DeplaneArrival
airplane.CommunicateGate();
airplane.OpenCargoDoor();
gateA.ConfirmArrival();
// Inside Jet.CommunicateGate
TaxiToGate();MainWindow : Window, Airport : Airport, Airplane : Jet, and GateA : Gate. These objects exist before the interaction, so their lifelines begin at the top.
MainWindow → Airport: DeplaneArrival(). Airport → Airplane: CommunicateGate(). While handling that call, Airplane → itself: TaxiToGate(). After CommunicateGate completes, Airport → Airplane: OpenCargoDoor(). Finally Airport → GateA: ConfirmArrival().
Keep Airport's activation open across its three calls. Place TaxiToGate as a nested self-call within the CommunicateGate activation, not as a call from Airport or GateA. End each called operation's activation when its work completes.
Point to the sender and receiver of all five calls. TaxiToGate is the third call in execution order but is made by the jet itself. For every call, find the matching method in the receiver's class. The self-call TaxiToGate() must match a method in Jet.
Submit two diagrams: the updated class diagram and the arrival sequence diagram. Use Airline 1.3 LastName as the base filename, replacing LastName with your last name. The class and sequence diagram-type suffixes distinguish the two files. Keep Violet's generated .violet.html extension and diagram-type suffix.
Check the class fields, methods, association labels, and multiplicities against the class-diagram instructions above. Check that all five sequence messages match methods in their receiver classes and follow the supplied source in order. Open the saved files in Violet and inspect for missing connections, unreadable crossings, or clipped text.
Put the diagram files at the ZIP root, not inside another folder. Name the archive Airline 1.3 LastName.zip. Do not include C# snippets, unrelated assignments, or instructor reference files.
Use the matching Airline activity. Review the feedback, correct your diagrams, save, rebuild the ZIP, and resubmit as needed.
Paste the resulting URL into the matching Canvas assignment. Keep your editable Violet files for later work.