1. Unified Modeling Language Overview 1. Object-orientation: Terms and concepts. 2. Use Cases: Requirements model 3. Class Diagram: The static model 4. Behavioral Modeling: The four dynamic diagrams 5. Implementation: The two physical models Software and Language Technology Engineering IR&D
2.
3.
4.
5.
6. An Example of a Class Employee Name DateOfBirth HomePhoneNo Title (etc.) listDepartmentsWorked() assignToSupervisior() computeVacation() listEmployees() (etc.) Class Name Attributes Operations
27. Idle lift receiver and get dial tone Idle State Dialing Substates Dialing Start Dial entry and start dialog exit / stop dial tone entry and num.append(n) digit(n) num.isValid( )
28.
29. Activity Diagram with Swimlanes Office Clerk Insurance Agent Loan Officer Edit Incoming Paper Complete Request Check Life insurance Draw Up Deed Calculate Mortgage Pay Provision to Agent Write Insurance Policy Index documents
30.
31.
32.
33.
34.
35.
36. Diagrams in View Context Structural View Implementation View User View Behavioral View Environment View Class Diagrams Object Diagrams Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams Component Diagrams Deployment Diagrams Use Case Diagrams
37.
38.
39. Class Diagram Format actor class interface relationship system class boundary system class System Class: An abstract representation of the SoS, System, Subsystem or Configuration Item (e.g., a class of ship, airplane, truck, satellite, HWCI, or CSCI). Actor Class: An abstract role represented by an individual or a group of individuals, organizations, or external systems that interact with the system class. system class
40. Actor and Use Case Format actor class value or service relationship use case system boundary Use Case Name should be a statement of the goal (or service) desired by the actor expressed as an active verb and a quantifiable noun (e.g., start engines and maneuver satellite).
This is a brief introduction to the Unified Modeling Language. Before looking into the UML we will recap a few principles and terms of object-orientation. We’ll then look at each of the eight different UML diagrams and show where they are used in the system development life cycle.
![Introduction ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)