1 Design Object Oriented Solutions Object Oriented Analysis & Design Lecturer: Mr. Mohammed Elhajj

2 Basic Object-Oriented Concepts Object/Class/Message Encapsulation Interfaces Inheritance Polymorphism

3 Structured Programming Approach Basic, Pascal and C are examples of structured programming languages The structured Programming Approach is based on the Functional Decomposition procedure To solve a problem, identify the different steps of the solution and then design/code each step separately Programs in these languages consists of a set of “operational elements” E.g. Procedures, Functions, Operations, Methods, etc

4 Database approach A Database model consists of “data elements”, known as “data objects” Each “Data Object” is characterised by a set of attributes or properties However, no operations are assigned to the “Data Objects” A similar concepts can be found in “structured programming”: Structures is a collection of data with no operations.

5 Object-Oriented Approach C++, JAVA, C# are object-oriented programming languages Objects are the elements in these languages. They have both data (properties, attributes) and behaviour (functions, operations, methods) So, the OO approach can be assumed as combination of the database and the structured programming ones OO approach is more realistic, closer to our interpretation of the world

6 Object Oriented Modelling A system consists of objects Objects interact by exchanging messages Each object is the instance of a general category: class Objects have data & behaviour Data & behaviour of an object may or may not be accessible by other objects Classes are organised in hierarchical trees

7 Benefits of OOAD Modelling is closer to the human interpretation of the world Easy to extend Easy to test Easy to reuse

8 Developing Object Oriented Solutions Introduction to UML Lecturer: Mr. Mohammed Elhajj

9 Some UML sources

10 Learning outcomes of this session Scope & History of UML Software Development Processes Review of UML diagrams

11 UML questions What is UML? What UML is not? Why do we need UML?

12 What is UML? The Unified Modelling language (UML) is a graphical language for visualising specifying constructing documenting applies to software systems businness modelling non-software systems

13 What UML is not? It is not a software development process. It is not a visual programming language. It is not a software modelling tool.

14 Why do we need UML?

15 Why do we need UML? To establish a common language among the people of the software development community. UML is independent on the process, the programming language and the software tool.

16 UML History Object Oriented Programming Languages (mid ’60s till today) Method Wars (Early ’90s) UML 0.8 (1995), UML 1.0 (1996) by Three Amigos UML ( ) managed by OMG ( ) UML 2.0 (2004-today)

17 Software Development Processes Waterfall Model Spiral Model Unified Process Rational Unified Process and many more…

18 Waterfall Model

19 Spiral Model

20 Unified Process: Iterative-Incremental

21 UML Summary Use Case Diagram Class Diagram Sequence Diagram Collaboration Diagram State Diagram Activity Diagram Package Diagram Component Diagram Deployment Diagram } Interaction Diagrams } Physical Diagrams

22 System Views Use Case View Use Case Diagram Static View Class Diagram Package Diagram Component Diagram … Dynamic View Sequence Diagram Collaboration Diagram Activity Diagram State Diagram …

23 Summary UML is a graphical modelling language used mainly for Object Oriented Systems UML is not a software development process. Many software development processes use the UML diagrams, e.g. the Unified Process The current version is UML 2.0 UML provides a wide range of diagrams Different diagrams are used to represent different system views