3.4 Date Night Assignment

Under Construction

This page is currently being built. Please check back soon.

A platypus
3.4 Date Night Assignment — 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
Date Night 3.4.zip Feedback System Go to the completion checklist
Download the starting code
2.Complete the required preparation
A Carry out the source requirement

Download the starting code.

This is the same starting code used in this week's object and sequence diagram assignments.

Date Night 3.4.zip

Extract the contents of the zip file to the location of your choice
3.Complete the required preparation
A Carry out the source requirement

Extract the contents of the zip file to the location of your choice.

Represent the class view
4.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
  • New
  • Changed
  • Removed
5.Using the given starting code, create a UML class diagram to represent the classes listed below, as well as any interfaces they implement

Bus Destination Car

A Verify the required change or observation

Check the result against this instruction: Using the given starting code, create a UML class diagram to represent the classes listed below, as well as any interfaces they implement.

6.Do not depict any fields. Depict properties and methods relevant to implementing interfaces as well as the following:
A The neighborhoodBus field on the Destination class
B The NeighborhoodBus property on the Destination class
7.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 object view
8.Review the notation example
A Identify the notation used in this view
Object identity and list order example. object "items : List<Example>" as items object "first : Example" as first { value = 7 } object "second : Example" as second { value = 9 } items --> first : [0] items --> second : [1]
Object identity and list order example
  • New
  • Changed
  • Removed
9.Set a breakpoint on the closing curly brace of ParkVehicle method of theValet class. Start the application. The breakpoint should be hit. Press Continue (F5) to hit the breakpoint again
A Verify the required change or observation

Check the result against this instruction: Set a breakpoint on the closing curly brace of ParkVehicle method of theValet class. Start the application. The breakpoint should be hit. Press Continue (F5) to hit the breakpoint again.

10.Create a UML object diagram to represent this Valet. Fold in the home, keyRack, and location fields. Depict the parkingGarage and all of its sub-objects
A Verify the required change or observation

Check the result against this instruction: Create a UML object diagram to represent this Valet. Fold in the home, keyRack, and location fields. Depict the parkingGarage and all of its sub-objects.

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 sequence view
12.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
  • New
  • Changed
  • Removed
13.Remove all other breakpoints. Set a breakpoint on the line of code that calls Personalize within the GoShopping method in the Guy class. Start the application. Click, Go on county fair date. Using the given starting code, create a UML sequence diagram to represent the flow of the application, starting with call to the Personalize method. Include all method calls within the Personalize method

The first or "root" object lifeline on your diagram should be named harry: Guy.

Use [ ] square brackets instead of < > angle brackets when notating a call to an inherited base method.

A Verify the required change or observation

Check the result against this instruction: Remove all other breakpoints. Set a breakpoint on the line of code that calls Personalize within the GoShopping method in the Guy class. Start the application. Click, Go on county fair date. Using the given starting code, create a UML sequence diagram to represent the flow of the application, starting with call to the Personalize method. Include all method calls within the Personalize method.

14.The first, unnamed activation bar, on the harry: Guy lifeline represents the GoShopping method, but you need only depict the call to Personalize on your diagram and not the previous code/calls. Specifically, exclude calls to the following methods:

DriveVehicleToLocation FindItem PurchaseItem

A Verify the required change or observation

Check the result against this instruction: The first, unnamed activation bar, on the harry: Guy lifeline represents the GoShopping method, but you need only depict the call to Personalize on your diagram and not the previous code/calls. Specifically, exclude calls to the following methods:

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.

Represent the activity view
16.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
  • New
  • Changed
  • Removed
17.Using the given starting code, create a UML activity diagram to represent the logic of the contents of the Gal.AcceptGift method
A Verify the required change or observation

Check the result against this instruction: Using the given starting code, create a UML activity diagram to represent the logic of the contents of the Gal.AcceptGift method.

18.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 the diagram and submit
19.Save and submit
A Carry out the source requirement

Save the diagram and submit.

B Save the file
C Zip and submit to the Feedback System
D Correct any mistakes based on Feedback
E Submit the resulting Feedback to Canvas as a URL
Completion checklist
20.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 object 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.