1 1 0 0 0 0 0 0 1 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 0 0 218000000 1 32 1024 768 2697000000 0 2479000000 0 218000000 10.000000 1.000000 2 4478 65 1 22050 0 49 0 Modeling Class Interactions, Behaviors, and States 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 1 218000000 610000000 1 32 1024 768 2697000000 218000000 2087000000 218000000 610000000 10.000000 1.000000 2 4478 65 1 22050 0 49 1 Step 1: Identify and Classify Use-Case Design Classes 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 2 610000000 818000000 1 32 1024 768 2697000000 610000000 1879000000 610000000 818000000 10.000000 1.000000 2 4478 65 1 22050 0 49 2 Step 2: Identify Class Attributes 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 3 818000000 957000000 1 32 1024 768 2697000000 818000000 1740000000 818000000 957000000 10.000000 1.000000 2 4478 65 1 22050 0 49 3 Step 3: Identify Class Behaviors and Responsibilities 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 4 957000000 1154000000 1 32 1024 768 2697000000 957000000 1543000000 957000000 1154000000 10.000000 1.000000 2 4478 65 1 22050 0 49 4 Condensed Behavior List 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 5 1154000000 1475000000 1 32 1024 768 2697000000 1154000000 1222000000 1154000000 1475000000 10.000000 1.000000 2 4478 65 1 22050 0 49 5 CRC Card Listing Behaviors and Collaborators of a Class 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 6 1475000000 1765000000 1 32 1024 768 2697000000 1475000000 932000000 1475000000 1765000000 10.000000 1.000000 2 4478 65 1 22050 0 49 6 Another Sequence Diagram 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 7 1765000000 1973000000 1 32 1024 768 2697000000 1765000000 724000000 1765000000 1973000000 10.000000 1.000000 2 4478 65 1 22050 0 49 7 Step 4: Model Object States 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 8 1973000000 2168000000 1 32 1024 768 2697000000 1973000000 529000000 1973000000 2168000000 10.000000 1.000000 2 4478 65 1 22050 0 49 8 Object State Example 1 C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week7\Chap18bSummary\Chap18bSummary.avi 0 9 2168000000 2696000000 1 32 1024 768 2697000000 2168000000 1000000 2168000000 2696000000 10.000000 1.000000 2 4478 65 1 22050 0 49 9 State Machine Diagram 1 0 Modeling Class Interactions, Behaviors, and States 1 0 218000000 Step 1: Identify and Classify Use-Case Design Classes 1 1 610000000 Step 2: Identify Class Attributes 1 2 818000000 Step 3: Identify Class Behaviors and Responsibilities 1 3 957000000 Condensed Behavior List 1 4 1154000000 CRC Card Listing Behaviors and Collaborators of a Class 1 5 1475000000 Another Sequence Diagram 1 6 1765000000 Step 4: Model Object States 1 7 1973000000 Object State Example 1 8 2168000000 State Machine Diagram 1 9 32 0000 Teaching Notes In this activity we want to identify and categorize the 72660000 design objects required by the functionality that was specified in each use case, and identify 145320000 the object interactions, their responsibilities, and their behaviors. 218000000 Teaching Notes The interface object column contains a list of objects 261550000 mentioned in the use case that the users directly interface with, such as screens, windows, 305100000 card readers, and printers. The only way an actor or user can interface with a system is via 348650000 an interface object. Therefore, there should be at least one interface object per actor or 392200000 user. The controller object column contains a list of objects that 435750000 encapsulate application logic or business rules. As a reminder, a use case should 479300000 reveal one controller object per unique user or actor. The entity object column 522850000 contains a list of objects that correspond to the business domain objects whose attributes 566400000 were referenced in the use case. 610000000 No additional notes. 818000000 No additional notes. 957000000 Teaching Notes Behaviors can be detected by identifying verbs in a use case 989830000 narrative. This is a partial list. See the text for the full list of 1022660000 behaviors Some of the behaviors assigned to entity classes would 1055490000 eventually be implemented with persistence classes. However, the entity class would maintain 1088320000 the responsibility of calling the persistence class. Thus the entity class would retain the 1121150000 behavior. 1154000000 Teaching Notes CRC stands for Class Responsibility Collaboration. 1189660000 The CRC card contains all use-case behaviors and responsibilities that have been 1225320000 associated with an object. A CRC card for the object type MEMBER ORDER is depicted in the 1260980000 figure above. Notice that the CRC card contains all use case behaviors and responsibilities 1296640000 that have been associated with the object type MEMBER ORDER. Also in the figure above, the 1332300000 MEMBER ORDER object needs collaboration from the MEMBER ORDERED PRODUCT object to 1367960000 retrieve information about each of the products being ordered. Remember if an object needs 1403620000 another object’s attribute to accomplish a behavior, the collaborating object needs to 1439280000 have a behavior or method to provide that attribute. 1475000000 No additional notes. 1765000000 Teaching Notes The concept of state is depicted on the next slide. 1973000000 No additional notes. 2168000000 Teaching Notes State machine diagrams are not required for all objects, just 2256000000 those that have clearly identifiable states and complex behavior. 2344000000 The solid circle represents the object’s initial state. The object transitions through a 2432000000 life cycle of different states represented by rounded-corner rectangles 2520000000 Each arrow represents an event that triggers a change from one state to another 2608000000 The solid circle inside the hollow circle represents the object’s final state.