1.  Today o Sequence Diagrams- View & Data Layers Message syntax o Design Class Diagrams o Cohesion & Coupling SheridanObject Oriented Methods1

2. 2SheridanObject Oriented Methods

3. SheridanObject Oriented Methods3

4.  One-to-many with superior to subordinate. The visibility goes from the superior to the subordinate  Mandatory relationships for existence. Visibility goes from independent to dependent  Object needs information from another object. Visibility goes to object with the information  Navigational arrows may be bidirectional 4SheridanObject Oriented Methods

5. SheridanObject Oriented Methods5

6.  UML does not distinguish between design class notation and domain model notation  Domain model class diagram shows conceptual classes in users’ work environment  Design class diagram specifically defines software classes  UML uses stereotype notation to categorize a model element by its characteristics 6SheridanObject Oriented Methods

7. 7SheridanObject Oriented Methods

8.  Navigation visibility o Describes which objects can interact with each other  Coupling o Measures how closely classes are linked  Cohesion o Measures the consistency of functions in a class  Separation of responsibilities o Divides a class into several highly cohesive classes Object Oriented Methods8 Sheridan

9.  Coupling – qualitative measure of how closely classes in a design class diagram are linked o Number of navigation arrows in design class diagram or messages in a sequence diagram o Loosely coupled – system is easier to understand and maintain  Cohesion – qualitative measure of consistency of functions within a single class o Separation of responsibility – divide low cohesive class into several highly cohesive classes o Highly cohesive – system is easier to understand and maintain and reuse is more likely 9SheridanObject Oriented Methods

10.  Reference & Example: o http://en.wikipedia.org/wiki/Coupling_(computer_programming) http://en.wikipedia.org/wiki/Coupling_(computer_programming) o http://www.scribd.com/doc/60141117/6/Tightly-Coupled-vs- Loosely-Coupled-Systems http://www.scribd.com/doc/60141117/6/Tightly-Coupled-vs- Loosely-Coupled-Systems o http://soa.sys-con.com/node/439723 http://soa.sys-con.com/node/439723 o http://stackoverflow.com/questions/2868627/why-should-a-web- architecture-be-loosely-coupled http://stackoverflow.com/questions/2868627/why-should-a-web- architecture-be-loosely-coupled SheridanObject Oriented Methods10

11. A multi layered system SheridanObject Oriented Methods11

12. SheridanObject Oriented Methods12

13. SheridanObject Oriented Methods13

14.  Example – Create new Customer for a Customer Relationship Management System (CRM) SheridanObject Oriented Methods14

15. SheridanObject Oriented Methods15

16. SheridanObject Oriented Methods16

17. SheridanObject Oriented Methods17

18. SheridanObject Oriented Methods18