Professional Documents
Culture Documents
1.0
2.0
3.0
4.0
2011 | PN AZRINA BINTI TAHIR
Exception Handling
1 2 3 4 5
Define object, attribute and behavior Explain Object-Oriented Analysis and Design (OOAD) method in solving problem
6
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.
Object Attribute
Operation
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).
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.
show actors (people or other users of the system), use cases (the scenarios when they use the system), and their relationships
The class diagram is core to object-oriented design. It describes the types of objects in the system, show classes and the relationships between them show objects and a sequence of method calls they make to other objects. show objects and their relationship, putting emphasis on the objects that participate in the message exchange show states, state changes and events in an object or a part of the system show activities and the changes from one activity to another with the events occurring in some part of the system show the high level programming components (such as KParts or Java Beans).
Sequence diagram Collaboration diagram State diagram Activity diagram Component diagram
Deployment diagram
Entity relationship diagram
2011 | PN AZRINA BINTI TAHIR
show data and the relationships and constraints between the data.
10
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.
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.
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.
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.
14
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.
16
Attributes are data: Order ID Customer ID Operations are action: Delete Item Change ID
Order object
17
18
Possible attributes and operations for objects in the DirectClothing, Inc. case study
19
Order Order ID Date *Shirt(s) Total price *Form of payment *CSR Status
Catalog Shirt(s)
+ Calculate order ID + Calculate the total price + Add shirt to order + Remove shirt from order + Submit the order
+ Assign a customer ID
20
To design a class you need to identify: Object (class name) Attributes (variables name) Operations (methods name) Syntax: ClassName attributeVariableName [range of values] attributeVariableName [range of values] methodName() methodName()
21
Example: Shirt shirtID Price Description Size colorCode R=Red, B=Blue, G=Green calculateShirtID() displayInformation()