2.1 Airline Learning Activity

2.1 Airline Learning Activity — overview

Use the goals, acceptance criteria, and nested tasks below to prepare and complete this activity. Follow the stated scope carefully.

1.Gather your resources

A Open the assignment resources

2.1 Start Diagrams.zip Feedback System Go to the completion checklist

Represent the class view

2.Review the notation example

A Identify the notation used in this view

Class diagram notation example. class Example { - value : int + Example(value : int) + Value : int {get} + Accept(item : Other) : Other } Example --> Other : item — Class diagram notation example

2.1.1 How to Represent Object Parameters in a Class Diagram

3.Open your Airline 1.5 Diagram

If you need start diagrams you can download them here.

2.1 Start Diagrams.zip

A Verify the required change or observation

Check the result against this instruction: Open your Airline 1.5 Diagram

4.Give the DeplaneArrival a parameter named terminal of type Terminal

A Verify the required change or observation

Check the result against this instruction: Give the DeplaneArrival a parameter named terminal of type Terminal.

5.Give the OpenCargoDoor a parameter named key of type Key

A Verify the required change or observation

Check the result against this instruction: Give the OpenCargoDoor a parameter named key of type Key.

6.Verify the diagram against the evidence

A Inspect the rendered diagram

Open or render your diagram, inspect every label and relationship, and compare it with the code or debugger state. Resolve syntax errors, clipped labels and unreadable crossings before submission.

Represent the sequence view

7.Review the notation example

A Identify the notation used in this view

Sequence notation example. participant Caller participant Receiver Caller -> Receiver : Accept(item) activate Receiver Receiver --> Caller : returned object deactivate Receiver — Sequence notation example

2.1.2 How to Represent Object Parameters in a Sequence Diagram

8.Open your Airline 1.5 Diagram

A Verify the required change or observation

Check the result against this instruction: Open your Airline 1.5 Diagram

9.Give the DeplaneArrival a parameter named terminal of type Terminal

A Verify the required change or observation

Check the result against this instruction: Give the DeplaneArrival a parameter named terminal of type Terminal.

10.Give the OpenCargoDoor a parameter named key of type Key

A Verify the required change or observation

Check the result against this instruction: Give the OpenCargoDoor a parameter named key of type Key.

11.Verify the diagram against the evidence

A Inspect the rendered diagram

Open or render your diagram, inspect every label and relationship, and compare it with the code or debugger state. Resolve syntax errors, clipped labels and unreadable crossings before submission.

Represent the activity view

12.Review the notation example

A Identify the notation used in this view

Nested decisions example. start if (Object exists?) then (yes) if (Condition is satisfied?) then (yes) :Perform conditional action; endif :Perform action common to the outer branch; endif stop — Nested decisions example

2.1.3 How to Represent Nested If Statements in an Activity Diagram

13.Open a new Activity Diagram in Violet

A Verify the required change or observation

Check the result against this instruction: Open a new Activity Diagram in Violet

14.Represent the nested if statement showed in the code below

if (ticket != null)
{
    if (ticket.PassengerName == Plane.SeatName)
    {
          this.PunchTicket(ticket);
    }
this.GiveGreeting();
}

A Verify the required change or observation

Check the result against this instruction: Represent the nested if statement showed in the code below.

15.Verify the diagram against the evidence

A Inspect the rendered diagram

Open or render your diagram, inspect every label and relationship, and compare it with the code or debugger state. Resolve syntax errors, clipped labels and unreadable crossings before submission.

Save diagrams and submit to the Feedback System and Canvas

16.Save and submit

A Carry out the source requirement

Save diagrams and submit to the Feedback System and Canvas

Completion checklist

17.Review the required evidence

A Check every acceptance criterion

Return to each user story and confirm that you can demonstrate its acceptance criteria. Use the task checkboxes to track completion; a checked box is not a substitute for testing or inspecting the required evidence.

Represent the class view Represent the sequence view Represent the activity view

B Follow this activity’s submission instructions

Use the submission or attendance instructions in this page. For a Feedback System submission, upload the requested ZIP, review and resolve the feedback, and submit the resulting URL to the matching Canvas activity. For a Canvas quiz, enter only the requested answers; for an oral final, complete the scheduling and attendance steps.

Under Construction