Object Oriented Analysis Design OOAD 1

Object Oriented Analysis & Design (OOAD) 1

OOAD • It focuses on objects where system is broken down in terms of the objects that exist within it. • Functions (behaviour) and data (state) relating to a single object are self-contained or encapsulated in one place. 2

Objects • Object is an abstraction of something in a problem domain, reflecting the capabilities of the system to keep information about it, interact with it, or both. • Objects are entities in a software system which represent instances of real-world and system entities 3

Objects Object Identity Behaviors State An employee “Mr. John” Join(), Retire() Joined, Retired. A book “Book with title Object Oriented Analysis Design” Add. Exemplar, Rent, available, reserved A sale “Sale no 0015, 15/12/98” Send. Invoiced(), Cancel(). Invoiced, cancelled. 4

Object Class • Class is a description of a set of objects that share the same attributes, operations, methods, relationship and semantics. • Object classes are templates for objects. They may be used to create objects. • An object represents a particular instance of a class. 5

Term of objects • Attribute: data items that define object. • Operation: function in a class that combine to form behavior of class. • Methods: the actual implementation of procedure (the body of code that is executed in response to a request from other objects in the system). 6

Employee object & class Class Object Employee 16 name: John address: M Street No. 23 date. Of. Birth: 02/10/65 employee. No: 324 socialecurity. No: E 342545 department: Sale manager: Employee 1 salary: 2340 stauts: current tax. Code: 3432 …. Eployee 16. join(02/05/1997) Eployee 16. retire(03/08/2005) Eployee 16. change. Detail(“X 7 Street No. 12”)

Encapsulation and Data Hiding • Packaging related data and operations together is called encapsulation. • Data hiding: hides the internal data from external by methods (interface). 8

Encapsulation l private attributes and methods are encapsulated within the class, they cannot be seen by clients of the class l public methods define the interface that the class provides to its clients Customer private attributes public methods - num. Customers = 0 - MIN_BUDGET = 200 - name: String - address: String - budget: int + print. Num. Customer( ): void + place. Order( ): void Customer class 9

Object communication • Objects communicate with each other by sending messages – a message is a method call from a message-sending object to a message-receiving object – a message consists of • an object reference which indicates the message receiver • a method name (corresponding to a method of the receiver), and • parameters (corresponding to the arguments of the calling method) – a message-receiving object is a server to a messagesending object, and the message-sending object is a client of the server 10

Message Passing message name = “Alex” address = “ 1 Robinson Rd” budget = 2000 place. Order( ): void alex take. Order(“sofa”, name, address, “ 120799”) 199 return value message name = “Lawrence” employee. No =15 commission = 200 take. Order( ): int lawrence. take. Order(“sofa”, “ 1 Robinson Rd”, “ 120799”) object reference method name parameters 11

Message Passing Customer Sales. Person - num. Customers = 0 - MIN_BUDGET = 200 - name: String - address: String - budget: int - MAX_ PRICE = 200 - name: String - employee. No: String - commission: int + print. Num. Customer( ): void + place. Order( ): void alex client + take. Order( ): void take. Order lawrence server 12

Inheritance • Object classes may inherit attributes and services from other object classes. • Inheritance represents the generalization of a class. 13

A generalisation hierarchy 14

Library Item Library class hierarchy Catalogue Number Acquisition date Cost Type Status Number of copies Acquire () Catalogue () Dispose () Issue () Return () Published item Title Publisher Book Author Edition Publication date ISBN Magazine Year Issue Recorded item Title Medium Film Director Date of release Distrib Computer program Version Platform 15

User class hierarchy 16

Multiple inheritance • Rather than inheriting the attributes and services from a single parent class, a system which supports multiple inheritance allows object classes to inherit from several super-classes • Can lead to semantic conflicts where attributes/services with the same name in different super-classes have different semantics • Makes class hierarchy reorganisation more complex 17

Multiple inheritance 18

Advantages of inheritance • It is an abstraction mechanism which may be used to classify entities • It is a reuse mechanism at both the design and the programming level • The inheritance graph is a source of organisational knowledge about domains and systems 19

Problems with inheritance • Object classes are not self-contained. they cannot be understood without reference to their superclasses • Designers have a tendency to reuse the inheritance graph created during analysis. Can lead to significant inefficiency • The inheritance graphs of analysis, design and implementation have different functions and should be separately maintained 20

Inheritance and OOD • There are differing views as to whether inheritance is fundamental to OOD. – View 1. Identifying the inheritance hierarchy or network is a fundamental part of object-oriented design. Obviously this can only be implemented using an OOPL. – View 2. Inheritance is a useful implementation concept which allows reuse of attribute and operation definitions. Identifying an inheritance hierarchy at the design stage places unnecessary restrictions on the implementation • Inheritance introduces complexity and this is undesirable, especially in critical systems 21

Objects Association • Modeling an association between two classes means that there is some sort of relationship between objects of each class that may be connected. Student studies 0. . * 1. . * Course 22

Object aggregation • Aggregation model shows how classes which are collections are composed of other classes • Similar to the part-of relationship in semantic data models 23

Object aggregation Study pack Course title Number Year Instructor 1 1 1. . * Assignment OHP slides Slides Credits 1 1. . * Lectur e notes Text 0. . * Videotape Tape ids. 1 1. . * 1 1 1. . * Exercises #Problems Description Solutions Text Diagrams 24

Object Cohesion & Coupling • Cohesion of a component is a measure of how well it fits together. Each operation provides functionality which allows the attributes of the object to be modified, inspected or used as a basis for service provision. • Coupling is an indication of the strength of interconnections between program units. Highly coupled systems have strong interconnections, with program units dependent on each other (shared variables, interchange control function). Loosely coupled system which are independent. 25

Polymorphism • the ability of different objects to perform the appropriate method in response to the same message is known as polymorphism. • the selection of the appropriate method depends on the class used to create the object Shape radius calculate. Area( ) Circle name get. Name( ) calculate. Area( ) Square side calculate. Area( ) 26

Example Polymorphism class Shape { private String name; public Shape(String a. Name) { name=a. Name; } public String get. Name( ) { return name; } public float calculate. Area( ) { return 0. 0 f; } a generic action } // End Shape class inheritance class Circle extends Shape { private float radius; public Circle(String a. Name) { super(a. Name); radius = 1. 0 f; } public Circle(String a. Name, float radius) { super(a. Name); this. radius = radius; overloading } public float calculate. Area() { return (float)3. 14 f*radius; } } // End Circle class overriding 27

class Square extends Shape { private float side; public Square(String a. Name) { super(a. Name); side = 1. 0 f; } public Square(String a. Name, float side) { super(a. Name); this. side = side; } public float calculate. Area() { return (float) side*side; } } // End Square class 28

Polymorphism Example public class Shape. Demo. Client { public static void main(String argv[ ]) { Shape Shape c 1 = new Circle("Circle C 1"); c 2 = new Circle("Circle C 2", 3. 0 f); s 1 = new Square("Square S 1"); s 2 = new Square("Square S 2", 3. 0 f); shape. Array[ ] = {c 1, s 1, c 2, s 2}; rule of subtype for (int i = 0; i < shape. Array. length; i++) { System. out. println("The area of " + shape. Array[i]. get. Name( ) + " is " + shape. Array[i]. calculate. Area( ) + " sq. cm. "); } dynamic binding } // End main } // End Shape. Demo. Client 1 class 29

OO Analysis and Design OO Analysis - examines requirements from the perspective of the classes and objects found in the vocabulary of the problem domain. In other words, the world (of the system) is modelled in terms of objects and classes. OO Design - OO decomposition and a notation for depicting models of the system under development. Structures are developed whereby sets of objects collaborate to provide the behaviours that satisfy the requirements of the problem. 30

Object Oriented Analysis • • • Analyze the domain problem Describe the process systems Identify the objects Specify attributes Defining operations Inter-object Communication 31

Identifying Object • Objects can be: – External Entity (e. g. , other systems, devices, people) that produce or consume information to be used by system – Things (e. g. , reports, displays, letters, signals) that are part of information domain for the problem – Places (e. g. , book’s room) that establish the context of the problem and the overall function of the system. – Organizational units (e. g. , division, group, team, department) that are relevant to an application, – Transaction (e. g. , loan, take course, buy, order). 32

Example of candidate objects Just a Line management wishes to increase security, both in their building and on site, without antagonizing their employees. They would also like to prevent people who are not part of the company from using the Just a Line car park. It has been decide to issue identity cards to all employees, which they are expected to wear while on the Just a Line site. The cards records the name, department and number of the member of staff, and permit access to the Just a Line car park. A barrier and a card reader are placed at the entrance to the car park. The driver of an approaching car insert his or her numbered card in the card reader, which then checks that the card number is known to the Just a Line system. If the card is recognized, the reader sends a signal to raise the barrier and the car is able to enter the car park. At the exit, there is also a barrier, which is raised when a car wishes to leave the car park. When there are no spaces in the car park a sign at the entrance display “Full” and is only switched off when a car leaves. Special visitor’s cards, which record a number and the current date, also permit access to the car park. Visitor’s cards may be sent out in advance, or collected from reception. All visitor’s cards must be returned to reception when the visitor leaves Just a Line. 33

Candidate objects: Just a Line site car park number card reader system sign management employee card member of staff entrance signal visitor security people name access driver exit reception building company department barrier car space 34

Candidate objects’ rejection • duplicates: if two or more objects are simply different names for the same thing. • irrelevant: objects which exists in the problem domain, but which are not intended. • vague: when considering words carefully it sometimes becomes clear that they do not have a price meaning and cannot be the basis of a useful in the system. • general: the meaning is too broad. • attributes: as the attribute of objects. • associations: actually represents the relationships between objects. • roles: sometimes objects referred to by the role they play in a particular part of the system. 35

Rejected Candidate objects Rejection criteria Just a Line, member of staff duplicates with company, employee respectively management, company, building, site, visitor and reception irrelevant to the system security, people vague system too general name, department, attribute access association driver role 36

Rest Objects Car park Employee card reader space Staff Card Entrance barrier sensor Visitor’s card exit Full sign car 37

Define class attributes Car Park capacity spaces inc. spaces() dec. spaces() space left() Barrier type: up: boolean raise() lower() Full sign on: boolean switch on() switch off() Card Reader valid card nos. read card() card OK() 38

Data Dictionary Barrier: type + up type = [“Entrance”|”Exit”] up = [“true”|”false”] raise: if the barrier is not already raised, this operation takes as argument an object of the barrier class and returns an object of the same class, with the up attribute set to “true”. If the barrier is already up, the operation returns the error message “barrier is already raised” lower: if the barrier is not already lower, this operation takes as argument an object of the barrier class and returns an object of the same class, with the up attribute set to “false”. If the barrier is already down, the operation returns the error message “barrier already lowered”. 39

Objects Relationship Car Park 2. . * Barrier Car Park 1. . * 2. . * Card Reader Sensor 1. . * 1 Valid cards 1. . * Card Visitor’s Card Staff Card 40

Object behaviour modelling • A behavioural model shows the interactions between objects to produce some particular system behaviour that is specified as a usecase • Sequence diagrams (or collaboration diagrams) in the UML are used to model interaction between objects 41

Sequence Diagram for Entrance : User : Car. Park : Sensor : Card. Reader : Valid card : Barrier : Full Sign off Car present Check space left Yes Card number Card returned Card OK Raise Car not present lower Decrement Space Check space left Yes 42

OO Analysis and Design Object-Oriented (OO) development is very different from structured development: • Structured approach focuses on major functions within a system and on the data used by the functions. • OO approach focuses on the objects in a system and on the relationships between those objects. 43

· Unlike functional decomposition, OO views a complex problem as a meaningful collection of objects that collaborate to achieve some higher level behaviour => closely mirrors how people view complex problems => using OO should make the job of developing large, complex systems more manageable. 44

Object Oriented Model 45

Structured Model 46

Comparison OO: Systems decomposed into collections of data objects; function + data in one place => • System components more independent => more resilient to requirements and maintenance changes. • Inheritance and polymorphism are possible => reuse, extension, and tailoring of software/designs is possible. • Closely mirrors how humans decompose and solve complex. Structured: Systems decomposed into functions; functions and data modelled separately => • System components are more dependent on each other => requirements and maintenance changes more difficult • Inheritance and polymorphism not possible => limited reuse possible. • System components do not map closely to real-world entities => difficult to manage 47 complexity.

Comparison OO: Process allows for iterative and incremental development => • Integration of programs is series of incremental prototypes. • Users and developers get important feedback throughout development. • Testing resources distributed more evenly. • If time is short, coding and testing can begin before the design is finished. Structured: Process less flexible and largely linear => • Integration of programs is ‘big bang’ effect. • Users or developers provided with little or no feedback; see system only when it has been completed. • Testing resources are concentrated in the implementation stage only. • Coding and testing cannot begin until all previous stages 48 are complete.