What is UML / why. UML is graphical and notational representation for software system requirements analysis and design. (Software Engineering )

Transcription

1 What is UML / why UML is graphical and notational representation for software system requirements analysis and design. (Software Engineering ) UML notation represents the state of art in term of Object Oriented modeling language Natural evolution of the notations used by Booch, OMT (Object Modeling Team), described by James Rumbaugh. 1

2 Unified Modeling Language history and development Origin Representing Element Booch Embley Fusion Gamma et al Harel Jacobson Meyer Odell OMT Shlaer- Mellor Wirfs-Brock Categories and subsystems Classes and composite objects Operation descriptions, massage numbering Frameworks patterns and notes Statecharts Use cases Pre and post conditions Dynamic classification, emphasis on events Association (object modeling team) Objects lifecycle Responsibilities and collaboration 2

3 Unified Modeling Language history and development In 1994 efforts were heightened for unification of methods toward a unified modeling language The main players in this joining efforts are Jim Rumbaugh, Grady Booch and Ivan Jacobson June 1996 version 0.9 released represented a substantial evolution of the Unified Method. Then the Unified Method was transformed into UML (Unified Modeling Language) 3

4 The Unified Modelling Language e Unified Modeling Language (UML) was developed jointly by Grady Booch, Ivar cobson, and Jim Rumbaugh at Rational Software Corporation, with contributions from her leading methodologists, software vendors, and many users. Based on extensive e of the Booch, OMT, and Jacobson methods, the UML is the evolution of these and her approaches to business process, object, and component modelling. The UML ovides the application modelling language for: Business process modelling with use cases Class and object modelling Component modelling Distribution and deployment modelling Database Design 4

5 UML defines several models for representing systems The class model captures the static structure The state model expresses the dynamic behavior The use case model describes the requirements of the user The interaction model represents the scenarios and massages flows The implementation model shows the work units The deployment model provides details that pertain to process allocation 5

6 Use case Diagram : Describes the behavior of the system from users standpoint by using actions and relations. It represents an image of the system functionality Determines the system requirements specifications. 6

7 7

8 User Expresses Understand Analyst Use case Implement Designs Verifies programmer Tester Architect 8

9 Relationship between Use cases The communication relationship Trigger Use case Actor The actor triggers relationship between the actor and Use case 9

10 Relationship between Use cases The uses relationship Use case A <<uses>> Use case B An instance of the source use case also include the behavior described by target use case 10

11 Relationship between Use cases The extend relationship <<extends>> Use case B Use case A The source use case extends the behavior of the destination use case 11

12 Use case example Transfer by computer <<extends>> Transfer <<uses>> Local customer Remote customer Identification 12

13 Class diagram Describes the static structure of the system in term of classes and relationship between those classes. Association of the class describes a set of links to the classes. Objects in the system are class instance,and the links are association instances. 13

14 Class diagram Class name Attributes Name : type = initial value Operations Function Name () 14

15 Class diagram: Example Rectangle class Rectangle Length : int Width : int Area ( ) 15

16 Class diagram 16

17 Class diagram Association Association represent structural relationships between classes and other classes or objects Symbolizes a piece of information with the lifecycle to the general dynamics of objects instances. Most associations are binary, they connect two classes 17

18 Class diagram Association naming A Name B Person Work for Company 18

19 Class diagram Role naming in association Company Employer Person Employee 19

20 Class diagram Multiplicity of Association 1 one an only one 0..1 zero or one M..N from M to N (natural integer) * from zero to any positive integer 0..* From zero to any positive integer 1..* from 1 to any positive integer 20

21 Class diagram Multiplicity of Association Car 1 1 Engine Person 1 0..* Account 21

22 Class diagram Reflexive association : a class linked to itself Person Parent 0..2 Children * 22

23 Class diagram Association classes : An association may be represented by a class to add attributes and operations to that association Student Performs Assignment Attributed association Grade 23

24 Class diagram N-ary Association: A class could be link to more than one other class Room Student Teacher The course class join all other classes Begin End Course 24

25 Class diagram Association qualifier: a restriction is implemented by means of a particular attribute or set of attribute of a class Chessboard row Column 1 Square 25

26 Class diagram Aggregations asymmetric association, in which one of the ends plays a more important role than the other end. A class is part of anther class The attribute values of one class propagate to the attribute value of another class An action of one class implies an action of another class The object of one class are subordinate of the objects of another class 26

27 Class diagram Aggregations A B Person Owner 1..* 0..* Building 27

28 Class diagram Composition A particular case of aggregation, attributes are physically contained in the aggregation. Aggregate 0..1 * Component 28

29 Class diagram Composition Car Is equivalent to Engine Car Engine Cylinder carburetor 29

30 Class diagram Generalization : expresses the fact that the elements of one class are also described by another class The generalization relationship signifies is or is kind of Animal Cat Dog Raccoon 30

31 Object diagram some times called instance diagram As in class diagram object diagram represents the static structure of the system. Illustrates the objects and links, that are instances of classes Show the context before and after the interaction (like values ) 31

32 Object diagram Representation of objects and links :Car Color=red :Engine :wheel1 :wheel2 :wheel3 :wheel4 Equivalent to class diagram Car color 1 1 engine 1 4 wheel 32

33 Collaboration Diagram Collaboration diagrams illustrate interactions between objects The interaction between objects : Massages and commands Parameters and arguments Conditional massages Control massages An active object is that holding control ( own a flow of control) The interaction between objects define which object is active and which is passive in a given period of time. 1 : read :scanner :Word processing 2: write :printer 33

34 Collaboration Diagram Collaboration diagram not explicitly representing the time of control ( unlike sequence diagram coming next) The control is presented by the massages number sending orders. 1: go up :carbine :elevator 3:Close 2: Turn on :light :door 34

35 Sequence diagram Display interaction from temporal standpoint. Represents an interaction between objects that focuses on the massages broadcast and object s time activity. Two main usage of Sequence Diagrams: 1. Close to the user view Documentation of Use Case, focuses on the description of the interaction This modeling corresponds to events accurse with the application domain having no differentiation between control flow and data flows in the sense of programming languages. 35

36 Sequence diagram e.g.1 caller phonec phoner recipient Pick up Dial tone Dial Ring Pick up Hello 36

37 Sequence diagram Two main usage of Sequence Diagrams: 1. Close to the user view 2. More software-oriented : Allows the precise representation of interactions between objects Allows the representation of activation for objects ( the time that an object performs an action ) Represents transition between object with control flow, determined by conditions and massage passing. 37

38 e.g.2 UML Diagrams Sequence diagram A B While X loop massage end loop if X A massage B C else end if massage 38

39 Activity Diagram Represents the execution state of mechanism as a sequence of steps grouped sequentially as parallel control flow branches. Display the activities carried by the system in smooth and pre-planned steps. The transitions of the activities occurs into Activity Diagram normally automatic transition (not like statechart) In most cases the activity diagram comes as a natural reflection of Use Case and Sequence diagram terms of activities runs in the systems. 39

40 Activity Diagram e.g.1 (non parallel activities) Client salesman Counter Inquire Estimate Order Order [made] Bill Pay Order [paid] delivery Delivery reciept 40

41 Activity Diagram e.g.2 ( parallel activities) (swimlanes) Teacher Student Board Teach Learn Supervise exam Sit exam Evaluate laheddin Junaidi 41

42 Statechart diagram State machine Describe the behavior of object of class in terms of states and events A state machine is an abstraction of all possible behaviors of an object The state machine in UML is deterministic, has start, and end, and has no ambiguous transitions. alaheddin Junaidi 42

43 Statechart diagram State machine The state machine triggers transitions by Events, these events may have additional conditions or Guards. Each state in the state machine may have Operations and Activities as well as variables parameters State A entry/ do Action/op exit/ Event State B entry/ do Action/op exit/ 43

44 State machine example: UML Diagrams Statechart diagram Company * Person Age Loss of Employment Actively employed Unemployed Hiring Older than 60 Older than 60 Retired 44

45 Statechart diagram Generalization A E1 B E2 E2 C A E1 B E2 C 45

46 Statechart diagram Aggregation X T E1 Y S U E3 Z E2 E1 A B E4 in Z E3 Z,A E1 E2 Z,B E3 X,A E3 Y,B E1 X,B 46

47 Statechart diagram History Washing Rinsing Drying H Open door Wait 47

48 Component Diagram Describe software components and their relationships within the implementation environment. Components are all kinds of elements that pertain piecing together of software application. Each component has : Specification : the type of the component interface Body : the component implementation and the its name. Body Specification 48

49 Component Diagram e.g. 49

50 Deployment Diagram Shows the physical layout of the various hardware components (nodes) that compose the system. Deployment diagram with its various nodes that appeared connected to each other by lines representing a communication infrastructure. TX Server TCP/IP Server DBMS IPX Pilot PC Printer 50

51 51

52 OMG & FIPA OMG Agent Working Group: recommends standards for agent technology where appropriate particularly the OMG s Object Management Architecture(OMA) ( ) FIPA (Federated Intelligent Physical Agents) has been working to develop and to promote standardization in the area of agents interoperability since It has an on going working program, meeting around the globe on quarterly basis, with excess of 50 member organizations. ( 52

53 AGENT Dictionary Definition Something that acts ome common properties of agents Autonomous - capable of initiating action independent of any other entity; erates without direct intervention externally. Communicative - communicates with other agents, such as humans, achines, and software agents (i.e., social). Adaptive/reactive - sensing and acting; responds in a timely fashion to anges in the environment. Mobile - able to transport itself from one environment or platform to other. Proxy- may act on behalf of someone or something. 53

54 Proactive - goal-oriented, purposeful; does not simply act in response to the environment. Intelligent - state is formalized by knowledge (i.e., beliefs, goals, plans,assumptions) and interacts with other agents using symbolic language. Temporally continuous - is a continuously running process. Character - believable "personality" and emotional state Able to learn and evolve - learning; changes its behaviour based on its previous experience. 54

55 AGENT Basic Definition An autonomous entity that can interact with its environment This is the most general sense of agent. Agents are not particularly useful unless they are autonomous, communicative, and reactive and arguably mobile. 55

56 SOFTWARE AGENT In other words, they are implemented using software. An autonomous software entity that can interact with its environment They are autonomous. They can react to other entities including humans, machines, and other software agents in various environments and platforms. 56

57 OFTWARE TECHNOLOGY ND AGENTS Software history is one of increasing Localization and encapsulation. Monolithic Programming Structured Programming Object- Oriented Programming Agent Programming Behavior Unit External Local Local Local State Unit External External External Local Local Unit Invocation External External (CALLed)) External (message) Local (rules, goals) 57

58 Initiator participant call-for-proposal refuse deadline An agent interaction protocol (AIP) not-understood propose accept-proposal reject-proposal inform cancel 58

59 Representing Agents with multiple roles agent Agent with multiple roles CA1 CA2 CA3 communication act (CA) 59

60 SOCIAL STRUCTURE Multi-Agent Systems (MAS) Modeling MAS using UML notation An agent is an autonomous entity (process) that interacts with its environment. A role is a class whose members participate in an action dependency or an interaction protocol. A group is a set of agents related through their roles. An environment consists of the conditions under which an entity (agent or object) exists. 60

61 SOCIAL STRUCTURE Multi-Agent Systems (MAS) Example : using UML notations Role * 1..* employs Played by * Consist of 1 Agent Environment 1..* 1..0 * * supported by Group 61

62 Conclusions & remarks Agents are an evolution, not a revolution. But, our usage of them will be revolutionary. UML diagram is convenient to be used in Agent Orienting modeling tool. In the real world their must be Objects as well as Agents It is mostly serious to identify which is an Agent and which is an Object A perfect Agent with all means is not exist ( even in the real world) their must be parameter and arguments to limit this Agency theory!!!!!!! 62