Object Oriented Concepts

1. Object Oriented Concepts

2. Movement toward Objects • Instead of data-oriented or process-oriented Analysis, many firms are now moving to object-oriented analysis. • In 1997, Unified Modeling language (UML) was accepted as the standard. • You need to understand what these concepts are… after that, it is very similar to the methods we’ve practiced.

3. Object Concepts • An object is a person, place, event, or thing about which we want to capture information. • Each object has properties (or attributes). • The state of an object is defined by the value of its properties and relations with other objects at a point in time. • Objects have behaviors -- things that they can do -- which are described by methods (or operations). Code!!! • Objects do not use primary or foreign keys, instead each instance is assigned a unique identifier (UID) when it is created.

4. The major difference between an Object and an Entity (from ERD) Entity Object * Attribute (identifier) Attribute Attribute Attribute Method Method Methods!

5. An Object and Object Instances

6. Class • A class is a general template we use to define and create specific instances or objects. • Move from general to specific down a “family tree”.

7. Class Hierarchy

8. Inheritance • Classes are arranged in a hierarchy • Superclasses or general classes are at the top • Subclasses or specific classes are at the bottom • Subclasses inherit attributes and methods from the superclasses above them • Classes with instances are concrete classes • Abstract classes only produce templates for more specific classes

9. Inheritance

10. Messages & “Polymorphism” • Messages are information sent to objects to trigger methods. • “Polymorphism” – “Many shapes” • when the same message can be interpreted differently by different classes of objects.

11. Polymorphism

12. Encapsulation • Binding or hiding the data and methods within an object • The message is sent without considering how it will be implemented • The object can be treated as a “black-box”

13. Defines a set of nine object diagramming techniques The key building block is the use case Diagrams are tightly integrated syntactically and conceptually to represent an integrated whole Application of UML can vary among organizations UML

14. 4 Major UML Diagrams • Use Case (very similar to what we’ve done). • In UML, these are kind of a hybrid between our Use Cases and a Context Diagram. • Sequence Diagram. • Shows interaction between classes for a particular Use Case.

15. 4 Major UML Diagrams • Class Diagram. • Similar to ERD, only it shows classes instead of entities. • Statechart Diagram. • Shows the state of an object at a given point.

16. Integration of four UML Diagrams