EE 446 EMBEDDED ARCHITECTURE Embedded System in UML (2)

Size: px

Start display at page:

Download "EE 446 EMBEDDED ARCHITECTURE Embedded System in UML (2)"

Homer Park
5 years ago
Views:

1 EE 446 EMBEDDED ARCHITECTURE Embedded System in UML (2) Airs Lin PART I CLASS DIAGRAMS

2 System Analysis and Design. Identify the information system s purpose 2. Identify the information system s actors and features 3. Identify Use Cases and create a Use Case Diagram 4. Identify Objects and their Classes and create a Class Diagram 5. Create Interaction/Scenario Diagrams 6. Create Detail Logic for Operations 7. Repeat activities 6 as required to refine the blueprints Objects Objects have three responsibilities: What they know about themselves (e.g., Attributes) What they do (e.g., Operations) What they know about other objects (e.g., Relationships)

Defining Class A CLASS is a template (specification, blueprint) for a collection of object that share a common set of and Relationships A RELATIONSHIP is what a class or an object knows about another

3 Defining Class A CLASS is a template (specification, blueprint) for a collection of object that share a common set of and Relationships A RELATIONSHIP is what a class or an object knows about another class or object Generalization (Class to Class) (Superclass/Subclass) Inheritance E: Person FacultyPerson, StudentPerson, Staff... E: ModesOfTravel Airplane, Train, Auto, Cycle, Boat... [Object] Associations FacultyInformation CourseInformation StudentInformation CourseInformation [Object] Aggregations & Composition (Whole Part) Assembly Parts Group Members Container Contents

4 Class Diagram Notation Class Generalization Relationship Object Association Object Aggregation Association Object Composition Association n n..* Will always be Class Diagram Notation Class { { Member membernumber firstname lastname telephone address city etc... checkoutvideo checkinvideo buyitem etc... Epanded view of a Class into its three sections: Top: Class Name Middle: Bottom:

5 Symbols for Class Diagram MyClass +mydata: string; +MyClass(); +myfunction(param: string): string; UML Symbols: + (plus sign) = public visibility (minus sign) = private visibility # (hash sign) = protected visibility ~ (tilde) indicates a destructor (in front of an operation) or package (as a visibility symbol).. (ellipsis) indicates a range of values : (colon) separates a name from a type, (comma) separates items in a set Class Diagram Relationships Class Generalization Object Association Aggregation Composition

Generalization (Class to Class) SuperClass SubClass; SuperType SubType A Generalization follows a is a or is a kind of heuristic from a specialization class to the ge

6 Generalization (Class to Class) SuperClass SubClass; SuperType SubType A Generalization follows a is a or is a kind of heuristic from a specialization class to the generalization class. (e.g., student is a person, video is a kind of inventory). Common, and relationships are located in the generalization class and are inherited by the specialization classes Unique, and relationships are located in the specialization classes. Inherited and may be overridden or enhanced in the specialization class depending on programming language support Generalization Eample

Poor Generalization Eample (violates the is a or is a kind of heuristic) Generalization Inheritance Common Unique Generalization a a2 a3 o o2 o3 Specialization a4 a5 a6 o4 o5

7 Poor Generalization Eample (violates the is a or is a kind of heuristic) Generalization Inheritance Common Unique Generalization a a2 a3 o o2 o3 Specialization a4 a5 a6 o4 o5 o6 One Way Inheritance from the Generalization to the Specialization (a = attribute; o = operation) Generalization a a2 a3 o o2 o3 Specialization a a2 a3 a4 a5 a6 o o2 o3 o4 o5 o6

8 Generalization Multiple Inheritance Generalization a a2 a3 o4 o5 Specialization a6 a7 a8 o6 o7 o8 Generalization2 a4 a5 o o2 o3 inherited a A2 a3 a4 a5 inherited o o2 o3 o4 o5 Generalization Multiple Classification <<abstract>> Person Female Male Physicaltherapist Nurse Doctor role Patient patient Gender {complete} Discriminator # #2 #3

9 Associations Relationships between instances (objects) of classes Conceptual: Associations can have two roles (bi directional): Source target Target source Roles have multiplicity To restrict navigation to one direction only, an arrowhead is used to indicate the navigation direction No inheritance as in generalizations Object Association Relationship Pattern Class A b) Object Aggregation Associations Whole Class B Part Part2 PartN Class A Class B c) Object Composition Associations (y may not be ) Whole a) Object Associations y Part y Part2 y PartN

10 Multiplicities Class eactly one Class many (zero or more) 0.. Class optional (zero or one) m..n Class numerically specified Eample: Course CourseOffering Aggregation and Composition Aggregation (shared aggregation): is a specialized form of ASSOCIATION in which a whole is related to its part(s). is known as a part of or containment relationship and follows the has a heuristic three ways to think about aggregations: whole parts container contents group members Composition (composite aggregation): is a stronger version of AGGREGATION the part(s) may belong to only ONE whole the part(s) are usually epected to live and die with the whole ( cascading delete ) has > Composition A InvoiceItem belongs to eactly one Invoice. Destroy the Invoice and the InvoiceItem goes away has > Aggregation The collection of Wheel is not closely bound to the Car

11 Eample Aggregation and Composition Faculty Aggregation Composition SalesOrder (team teaching is possible)..*..* CourseTeaching SalesOrderLineItem (another: assembly > part) (another: hand > finger) Eample Composition Eist to: () Show relationships (2) Enforce integrity (3) Help produce results UniversityCourse In this eample: Removal of a University Course should also remove Students that are in the Course but not Student Information. StudentInformation 0 m 0 m StudentInCourse Removal of a Student should also remove the Courses that the Student is in but not the University Course. Removal of a Student in a Course should not affect either University Course or Student Information.

12 Multiplicity Eample # Whole 5 Part 3 2 PartN One Whole is associated with 5 Part One Part is associated with Whole One Whole is associated with 2 PartN One PartN is associated with 3 Whole W P P P P P P W W P P P W W W Multiplicity Eample #2 Class min. ma n Class2 Class3..n C * C2 C2 C C2 C2 C2 etc... C2 C C3 C3 C3 C3 C3 etc C3 C C C C C

13 Multiplicity Eample #3 StudentInformation CourseCompleted ClubMember Multiplicity Many to Many StudentInformation CourseInformation Becomes either StudentInformation SemesterTaken GradeEarned CourseInformation StudentCourseInformation Attributes that represent the union of the two classes are located in this association class. StudentInformation CourseInformation StudentCourseInformation SemesterTaken GradeEarned

14 UML (UNIFIED MODELING LANGUAGE) SEQUENCE DIAGRAM Sequence Diagram Sequence diagram Focus on communication between the objects, it is: An interaction diagram that shows processes operate with one another and in what order A construct of a Message Sequence Chart Shows object interactions arranged in time sequence Sometimes called event diagrams or event scenarios Typically associated with Use Case realizations in the Logical View of the system under development

15 Sequence Diagram Message Lifeline Sequence Diagram The beginning of a phone conversation

Elements in Sequence Diagram Lifeline A vertical line that represents the sequence of events that occur in a participant during an interaction, while time progresses

This participant can be an instance of a class, component, or actor Actor A participant that is eternal to the system that you are developing SyncMsg The sender waits

16 Elements in Sequence Diagram Lifeline A vertical line that represents the sequence of events that occur in a participant during an interaction, while time progresses down the line. This participant can be an instance of a class, component, or actor Actor A participant that is eternal to the system that you are developing SyncMsg The sender waits a response to a synchronous message before it continues. Elements in Sequence Diagram AsyncMsg A message that does not require a response before the sender continue Eecution Occurrence A vertical rectangle that appears on a participant s lifeline and represent the period when the participant is eecuting an operation

17 Elements in Sequence Diagram Create Message Endpoint A message that creates a participant. If a participant receives a create message, it should be the first it receives An asynchronous message from an unknown or an unspecified participant Self Message A message from a participant to itself. Elements in Sequence Diagram A collection of fragment. Each fragment can enclose one or more messages. Combined Fragment Fragment Guard Encloses a sequence of message that are defined in another diagram Can be used to state a condition relevant to whether the fragment will occur Interaction Use

18 Elements in Sequence Diagram

Lesson 11. W.C.Udwela Department of Mathematics & Computer Science

Lesson 11. W.C.Udwela Department of Mathematics & Computer Science Lesson 11 INTRODUCING UML W.C.Udwela Department of Mathematics & Computer Science Why we model? Central part of all the activities We build model to Communicate Visualize and control Better understand