Update the class diagram to show the Gate-to-Jet reference, update the object diagram to show the shared Jet, then create an activity diagram for the nested luggage decisions. Save all three diagrams as separate Violet files. Copy exact diagram text from the literal spans without typing their surrounding markers. Submit diagrams, not a C# project.
Airline class diagramOpen your Airline 1.5 class diagram. Use Save As to create Airline 1.6 LastName.class.violet.html, replacing LastName with your last name. Preserve your original 1.5 file. Keep all five classes: Airline, Airport, Terminal, Gate, and Jet. Retain their existing fields and operations, including the parameter and return-type changes from 1.4 and 1.5.
The new + Plane association is the only addition. Keep the five existing associations and their 1 multiplicities at both ends: Airline → Airport + Airport, Airline → Jet + Airplane, Airport → Terminal + MainTerminal, and the two Terminal → Gate lines + GateA and + GateB. Your completed class diagram has five class boxes and six association lines.
Keep Jet's operations + CommunicateGate(): string, + OpenCargoDoor(), and + TaxiToGate(timeTaken: double): bool, Airport's + DeplaneArrival(), and Gate's + ConfirmArrival(gateName: string). The class diagram now defines two reference paths to Jet; the object diagram will show Airline's Airplane and GateA's Plane reaching the same instance.
Use your Airline 1.5 activity diagram as the baseline. Save a copy as Airline 1.6 LastName.activity.violet.html. PlaneSideCheckLuggage and Overhead are Boolean inputs. CheckBins updates the Boolean Found to indicate whether the item was found. Model only this excerpt.
if (PlaneSideCheckLuggage)
{
OpenCargoDoor();
}
else
{
if (Overhead)
{
CheckBins();
if (!Found)
{
AskFlightAttendant();
}
}
else
{
HighFivePassengers();
}
}Connect the start to PlaneSideCheckLuggage. Its true route reaches OpenCargoDoor, then the final node. Its false route reaches a second decision, Overhead.
From Overhead, false reaches HighFivePassengers, then the final node. The true route reaches CheckBins, then decision !Found. From !Found, true reaches AskFlightAttendant, then the final node; false reaches the final node directly. Label every decision outcome true or false.
With PlaneSideCheckLuggage true, only OpenCargoDoor runs. Otherwise, Overhead false runs HighFivePassengers; Overhead true runs CheckBins. After CheckBins, run AskFlightAttendant only when Found is false. All routes reach the same final node.
Submit one class diagram, one object diagram, and one activity diagram. Use Airline 1.6 LastName as the base filename, replacing LastName with your last name. Keep Violet's generated .violet.html extension and diagram-type suffix.
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.
Put the diagram files at the ZIP root, not inside another folder. Name the archive Airline 1.6 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.