1.6 Airline Learning Activity

Airline 1.6: Update the Class Diagram to Show a Gate Reference to a Jet

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.

1.Show the Gate reference to Jet
A Save a 1.6 copy of your Airline class diagram

Open 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.

B Add the Gate-to-Jet association

Draw a directed association from Gate to the existing Jet class, with the arrowhead at Jet. Label the connecting line + Plane. Put multiplicity 1 at the Jet end and leave the Gate end unlabeled, matching the supplied 1.6 end diagram. This association represents the public reference field Plane of type Jet; show its name on the line rather than duplicating it in Gate's field compartment.

C Check the single change from 1.5 to 1.6

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.

Update the Object Diagram to Show Two References to One Jet
2.Use your Airline 1.2 object diagram as the baseline
A Save your 1.2 object diagram as 1.6

Open your Airline 1.2 object diagram. Use Save As to create Airline 1.6 LastName.object.violet.html, replacing LastName with your last name. Preserve the original 1.2 file. Keep the six objects: one Airline, one Airport, one Jet, one Terminal, and two Gates.

B Preserve the baseline values and references

Keep Airline's Name = AeroWisco and EmployeeCount = 12, Airport's Name = CWA and Employees = 10, and Jet's LengthInMeters = 33.84, Model = 319, Manufacturer = Airbus, and Name = Spirit of the Forest.

Keep Airline's Airport reference to the Airport, Airport's MainTerminal reference to the Terminal, and Terminal's GateA and GateB references to their respective Gates. GateA has Number = 3A, HasSkyway = true, and PlaneSideCheckLuggage = false. GateB has Number = 3B, HasSkyway = false, and PlaneSideCheckLuggage = true.

C Connect GateA to the existing jet

Add a reference field named Plane inside the Gate reached through GateA (Number 3A). Draw its reference arrow to the existing Jet named Spirit of the Forest. Keep Airline's Airplane arrow pointing to that same Jet. Leave GateB as it was in 1.2.

Create an Activity Diagram Representing Nested if Statements
3.Read the nested luggage-check code

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.

Airline source to diagram
if (PlaneSideCheckLuggage)
{
    OpenCargoDoor();
}
else
{
    if (Overhead)
    {
        CheckBins();

        if (!Found)
        {
            AskFlightAttendant();
        }
    }
    else
    {
        HighFivePassengers();
    }
}
A Draw the conditions and their actions

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.

B Check each route

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.

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

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.

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.6 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.