Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA BINTI TAHIR

2

Define object, attribute and behavior 1 Explain Object-Oriented Analysis and Design (OOAD) method in solving problem 2 Understand the fundamental of Unified Modeling Language (UML) 3 Describe general UML elements 4 Analyze a problem using object-oriented analysis and design (OOAD) 5 Design classes form which objects will be created using UML Class Diagram 6 3 © 2011 | PN AZRINA BINTI TAHIR

Objects ▫ Instance of a class. ▫ Can be defined as a thing. ▫ Set of attribute and behavior. Attribute ▫ Characteristic of the object ▫ State of an object Behavior ▫ Process or operation of the object that usually modify the state of an attribute. © 2011 | PN AZRINA BINTI TAHIR 4

5 ObjectCar Attribute-Color -No of tire -No of door -Chassis Operation-Driving

© 2011 | PN AZRINA BINTI TAHIR 6 Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects. Each object represents some entity of interest in the system being modeled, and is characterized by its class, its state (attribute), and its behavior. It also can be define as a process of analyzing and designing a system from an object-oriented point of view. Various models can be created to show the static structure, dynamic behavior, and run-time deployment of these collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling Language (UML).

© 2011 | PN AZRINA BINTI TAHIR 7 To emphasize a problem domain and logical solution from the perspective of objects (things, concepts or entities) OO Analysis ▫ To find and describe the objects or concepts in the problem domain. ▫ For example in the Library Information System, some of the concepts include Book, Library and Patron. OO Design ▫ To define software objects (attributes and operations) and how they collaborate to fulfill the requirements that will be implemented in an OO programming language. ▫ For example in the Library Information System, a Book is an object that have a title as it attribute and getChapter as the method. OO Programming ▫ Design components are implemented.

The Unified Modeling Language or UML is a language for specifying, visualizing, constructing and documenting the artifacts of software systems, as well as for business modeling and other non-software system. It is also a graphical modeling language that is used to express designs. It is a standardized language in which to specify the artifacts and components of a software system. It is important to understand that the UML describes a notation and not a process. It does not put forth a single method or process of design, but rather is a standardized tool that can be used in a design process. © 2011 | PN AZRINA BINTI TAHIR 8

There is nine(9) diagram that can be used in UML :- © 2011 | PN AZRINA BINTI TAHIR 9 DiagramDescription Use case diagram show actors (people or other users of the system), use cases (the scenarios when they use the system), and their relationships Class diagramThe class diagram is core to object-oriented design. It describes the types of objects in the system, show classes and the relationships between them Sequence diagramshow objects and a sequence of method calls they make to other objects. Collaboration diagram show objects and their relationship, putting emphasis on the objects that participate in the message exchange State diagramshow states, state changes and events in an object or a part of the system Activity diagramshow activities and the changes from one activity to another with the events occurring in some part of the system Component diagram show the high level programming components (such as KParts or Java Beans). Deployment diagram show the instances of the components and their relationships. Entity relationship diagram show data and the relationships and constraints between the data.

UML offers a standard way to visualize a system's architectural blueprints, including elements such as: ▫ activities ▫ actors ▫ business processes ▫ database schemas ▫ (logical) components ▫ programming language statements ▫ reusable software components. © 2011 | PN AZRINA BINTI TAHIR 10

© 2011 | PN AZRINA BINTI TAHIR 11 To analyze a problem (case study), there will be three(3) main factor to be considered which is:- ▫ Identify problem domain ▫ Identify objects ▫ Identify object attributes and operations Example of case study: DirectClothing Inc. Sells shirts from their catalog. Business is growing 30 percent per year and they need a new order entry system. You have been contracted by DirectClothing to design the new system. DirectClothing produces a catalog of clothing every six months and mails it to subscribers. Each shirt in the catalog has an item identifier (ID), one or more colors (each with a different color code), one or more sizes, a description and a price. DirectClothing accepts cheques and credit cards. to place an order, customers can call DirectClothing to order directly from a customer service representative (CSR) or customers can mail or fax an order form to DirectClothing.

© 2011 | PN AZRINA BINTI TAHIR 12 A problem domain is the scope of the problem that need to be solve. For example, “Create a system allowing order entry people to enter and accept payment for an order”.

© 2011 | PN AZRINA BINTI TAHIR 13 Objects can be physical or conceptual. Object have attributes (characteristics). ▫ Size, name, shape and so on. Object have operations (the things they can do) Setting a value, displaying a screen or increasing speed.

© 2011 | PN AZRINA BINTI TAHIR 14

© 2011 | PN AZRINA BINTI TAHIR 15 Additional criteria for recognizing objects: Relevance to the problem domain Does the object exist within the boundaries of the problem domain? Is the object required for the solution to be complete? Is the object required as part of an interaction between a user and the solution? Independent existence For an item to be an object and not an attribute of another object, it must exist independently in the context of problem domain. Possible objects in the DirectClothing case study as follow:

Attributes are data: ▫ Order ID ▫ Customer ID  Operations are action:  Delete Item  Change ID © 2011 | PN AZRINA BINTI TAHIR 16 Order object

Object with another object as an attribute © 2011 | PN AZRINA BINTI TAHIR 17

Possible attributes and operations for objects in the DirectClothing, Inc. case study © 2011 | PN AZRINA BINTI TAHIR 18

© 2011 | PN AZRINA BINTI TAHIR 19

© 2011 | PN AZRINA BINTI TAHIR 20 To design a class you need to identify: ▫ Object (class name) ▫ Attributes (variables name) ▫ Operations (methods name) Syntax: ClassName attributeVariableName [range of values] … methodName() …

Example: © 2011 | PN AZRINA BINTI TAHIR 21 Shirt shirtID Price Description Size colorCode R=Red, B=Blue, G=Green calculateShirtID() displayInformation()