Train the Trainers develops seminars and workshops for corporate training managers, who in turn train their employees. Your job at Train the Trainers is to put together the actual training materials.
Right now, you are up against a deadline. The new object modeling seminar has a chapter on cardinality, and the client wants you to come up with at least three more examples for each of the four cardinality categories listed in Figure 6‑16.
The four categories are zero or many, zero or one, one and only one, and one or many. Even though you are under pressure, you are determined to use examples that are realistic and familiar to the students. What examples will you submit?
See Figure 6 -16 in textbook and file attached
Figure 6-16 examples of UML notations indicate the nature of the relationship between instances of one class and instances of another class.
Chapter 6 Object Modeling Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 1 Learning Objectives (1 of 2) After this chapter, you will be able to: Demonstrate how object-oriented analysis can be used to describe an information system Explain what an object represents in an information system Explain object attributes Explain object methods Explain object messages Explain classes Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 2 Learning Objectives (2 of 2) Explain relationships among objects and classes Draw an object relationship diagram Demonstrate use of the UML to describe object-oriented systems, including use cases, use case diagrams, class diagrams, sequence diagrams, state transition diagrams, activity diagrams, and business process models Explain how tools can support object modeling Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 3 Object-Oriented Analysis Methodology is popular Integrates easily with object-oriented programming languages such as C++, Java, and Python Modular, reusable, and easy to maintain End product of O-O analysis is an object model Represents the information system in terms of objects and O-O concepts Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 4 Objects (1 of 2) Person, place, event, or transaction that is significant to the information system FIGURE 6-1 The PARENT object includes four attributes and two methods. Mary Smith, Ahmed Ali, and Anthony Greene are instances of the PARENT object. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. Objects (2 of 2) FIGURE 6-2 The CHILD object includes five attributes and five methods. James Smith, Amelia Ali, and Misty Greene are instances of the CHILD object. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 6 Attributes Describe the characteristics of an object Attributes of an object are defined during the system development process Objects possess a state Describes the object’s current status Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 7 Methods Tasks or functions that the object performs when it receives a message, or command FIGURE 6-3 The MORE FRIES method requires the server to perform seven specific steps. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 8 Message (1 of 2) Command that tells an object to perform a certain method Polymorphism: message gives different meanings to different objects FIGURE 6-4 In an example of polymorphism, the message GOOD NIGHT produces different results, depending on which object receives it. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 9 Message (2 of 2) Message to the object triggers changes within the object without specifying how the changes must be carried out An object can be viewed as black box Encapsulation: idea that all data and methods are self-contained Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. Classes (1 of 3) An object belongs to a group or category called a class All objects within a class share common attributes and methods Subclasses: categories within a class Super-class: class belonging to a general category Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 11 Classes (2 of 3) FIGURE 6-6 The VEHICLE class includes common attributes and methods. CAR, TRUCK, MINIVAN, and SCHOOL BUS are instances of the VEHICLE class. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 12 Classes (3 of 3) FIGURE 6-8 At the fitness center, the PERSON superclass includes common attributes and methods. EMPLOYEE is a class within the PERSON superclass. INSTRUCTOR is a subclass within the EMPLOYEE class. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 13 Relationships Among Objects and Classes (1 of 3) Relationships Enable objects to communicate and interact as they perform business functions and transactions Describe what objects need to know about each other Inheritance Strongest relationship Enables an object to derive one or more of its attributes from another object Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 14 Relationships Among Objects and Classes (2 of 3) FIGURE 6-9 An inheritance relationship exists between the INSTRUCTOR and EMPLOYEE objects. The INSTRUCTOR (child) object inherits characteristics from the EMPLOYEE (parent) class and can have additional attributes of its own. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 15 Relationships Among Objects and Classes (3 of 3) FIGURE 6-10 Object relationship diagram for the fitness center. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 16 The Unified Modeling Language (1 of 15) Uses a set of symbols to represent graphically the various components and relationships within a system Use case modeling Use case: represents steps in a specific business function or process An external entity, called an actor, initiates a use case by requesting the system to perform a function or process Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 17 The Unified Modeling Language (2 of 15) Use case description Documents the name of the use case, the actor, a description of the use case Provides a step-by-step list of the tasks and other key descriptions and assumptions FIGURE 6-11 In a medical office system, a PATIENT (actor) can MAKE APPOINTMENT (use case). Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 18 The Unified Modeling Language (3 of 15) FIGURE 6-13 The ADD NEW STUDENT use case description documents the process used to add a current student into an existing class at the fitness center. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 19 The Unified Modeling Language (4 of 15) Use case diagrams Visual summary of several related use cases within a system or subsystem The first step is to identify the system boundary which is represented by a rectangle System boundary: shows what is included in the system (inside the rectangle) and what is not included in the system (outside the rectangle) Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 20 The Unified Modeling Language (5 of 15) FIGURE 6-15 A use case diagram to handle work at an auto service department. Systems Analysis Design, 12th Edition. ©2020 Cengage. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. 21 The Unified Modeling Language (6 of 15) Class diagrams Show the object classes and relationships involved in a use case Each class appears as a rectangle, with the class name at the top, followed by the class’s attributes and methods Lines show relationships between classes and have labels identifying the action that relates the two classes Includes a concept called cardinality Describes how instances of one class relate to instances of