CHAPTER 6 OBJECT ANALYSIS.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Systems Analysis and Design 8th Edition
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Object-Oriented Analysis and Design
Department of Computing
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Introduction To System Analysis and Design
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© 2005 Prentice Hall8-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Basic OOP Concepts and Terms
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
System Analysis and Design
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Unified Modeling Language
Chapter 5: Modeling Systems Requirements: Events and Things
Introduction To System Analysis and design
CMIS 470 Structured Systems Design
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
Systems Analysis and Design in a Changing World, Fifth Edition
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Intro to UML - OO Class Diagrams Week 5 CMIS570. Plan for Tonight Object terms Unified Modeling Language history Class Diagrams Intro to Oracle Oracle.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Unified Modeling Language, Version 2.0
5 Systems Analysis and Design in a Changing World, Fourth Edition.
System Analysis System Analysis - Mr. Ahmad Al-Ghoul System Analysis and Design.
Chapter 7 System models.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis & Design 7 th Edition Chapter 5.
To navigate the slide presentation, use the navigation bar on the left OR use your right and left arrow keys. Move your mouse over the key terms throughout.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Basic OOP Concepts and Terms. In this class, we will cover: Objects and examples of different object types Classes and how they relate to objects Object.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
OBJECT ORIENTED APPROACH WITH THE UML
Chapter 11 Inheritance © 2008 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved. Marilyn Bohl/Maria Rynn Tools for Structured and Object-Oriented.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
DATA REQIREMENT ANALYSIS
The Movement To Objects
Object-Oriented Analysis and Design
Unified Modeling Language
Business System Development
Chapter 6 Object Modeling
Chapter 20 Object-Oriented Analysis and Design
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Basic OOP Concepts and Terms
Chapter 5.
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

CHAPTER 6 OBJECT ANALYSIS

Chapter Objectives Explain how object-oriented analysis can be used to describe an information system Define object modeling terms and concepts, including objects, attributes, methods, messages, classes, and instances Explain relationships among objects and the concept of inheritance Draw an object relationship diagram

Chapter Objectives Describe Unified Modeling Language (UML) tools and techniques, including use cases, use case diagrams, class diagrams, sequence diagrams, state transition diagrams, and activity diagrams Explain the advantages of using CASE tools in developing the object model Explain how to organize an object model

Introduction You learn about object-oriented analysis, which is another way to view and model system requirements You use object-oriented methods to document, analyze, and model the information system

Overview of Object-Oriented Analysis Object-oriented (O-O)- analysis describes an information system by identifying things called objects. Object- represents a real person, place, event, or transaction Object-oriented analysis is a popular approach that sees a system from the viewpoint of the objects themselves as they function and interact End product of object oriented analysis is an Object model-represent the information system in terms of objects and object-oriented concepts.

Object-Oriented Terms and Concepts Unified Modeling Language (UML)-widely used method of visualizing and documenting an information system. An objects has: Attributes Methods Message Class Instance-is a specific member of a class

The PARENT object includes four attributes and two methods Objects The PARENT object includes four attributes and two methods

Objects The CHILD object includes five attributes and five methods

Objects The DOG object includes six attributes and four methods

Objects The STUDENT object includes seven attributes and six methods The INSTRUCTOR object includes eight attributes and six methods

Attributes characteristics that describe the object If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object Some objects might have a few attributes; others might have dozens Object can have a specific attribute called a State

A method defines specific tasks that an object can perform Methods A method defines specific tasks that an object can perform Just as objects are similar to nouns and attributes are similar to adjectives, methods resemble verbs that describe what and how an object does something The MORE FRIES method requires the server to perform seven specific steps

Messages Is a command that tells an object to perform certain method Polymorphism-concept that message gives different meanings to different objects Black box-message to the object triggers changes within the object without specifying how the changes must be carried out Black box is an example of Encapsulation-all data and methods are self contained

Message: ADD FITNESS-CLASS Tells the STUDENT class to perform all the steps needed to add fitness class instance

An example of polymorphism, the message GOOD NIGHT produces different results, depending on which object receives it

Messages A major advantage of O-O designs is that systems analysts can save time and avoid errors by using modular objects, and programmers can translate the designs into code, working with reusable program modules that have been tested and verified An INSTRUCTOR object sends an ENTER GRADE message to an instance of the STUDENT RECORD class

Classes An object belongs to a group or category called a class All objects within a class share common attributes and methods Object witin a class can be grouped into Subclasses Superclass

Classes The VEHICLE class includes common attributes and methods CAR,TRUCK,MINIVAN and SCHOOL BUS are instances of the VEHICLE class

Relationships Among Objects and Classes Relationship enable objects to communicate and interact as they perform business functions and transactions required by the system. Relationships describe what objects need to know about each other, how objects respond to change in other objects and the effects of membership in classes, superclasses and subclasses Inheritance-the strongest relationship Enable Child to derive one or more of its attributes from another object, called aParent

Inheritance relationship exists between the INSTRUCTOR and EMPLOYEE objects. The INSTRUCTOR (child) object inherits characteristics from the EMPLOYEE (parent) class and can have additional attributes of its own

Relationships Among Objects and Classes Object Relationship Diagram Provide overview of the system Model shows he objects and how they interact to perform business functions and transaction

Object Modeling with the Unified Modeling Language The UML uses a set of symbols to represent graphically the various components and relationships within a system It mainly is used to support object-oriented systems analysis and to develop object models

Use Case Modeling Use case represents the steps in a specific business function or process Actor (external entity)- initiates a use case by requesting the system to perform a function or process Symbol for a use case is an oval with a label that describes the action or event Use cases also can interact with other use cases

Use Case Modeling When the outcome of one use case is incorporated by another use case, we say that the second case uses the first case Use case description- When you identify use cases, try to group all the related transactions into a single use case

Use Case Diagrams Use case diagram-visual summary of several related use cases within a system or subsystem System boundary-what is included in the system After you identify the system boundary, you place the use cases on the diagram, add the actors, and show the relationships

Class Diagrams Class Diagram-shows the object classes and relationships involved in a use case Evolves into a physical model and finally becomes a functioning information system Each class appears as a rectangle, with the class name at the top, followed by the class’s attributes and methods Cardinality-describes how instances of one class relate to instances of another class

Class Diagrams

Nature of the relationship Examples of UML notations that indicate the nature of the relationship between instances of one class and instances of another class UML notation Nature of the relationship Example Description 0..* Zero or many An employee can have no payroll deductions or many deductions 0..1 Zero or one An employee can have no spouse or one spouse 1 One and only one An office manager manages one and only one office 1..* One or many One order an include one or many items ordered Employee Payroll Deduction 1 0..* Employee Spouse 1 0..1 Office Manager Sales Office 1 1 Item Ordered Order 1 1..*

Sequence Diagrams Sequence diagram- showing the interaction among classes during a specified time period Include symbols that represent Classes-classes that send or receive messages Lifelines-represent the time Messages- Focuses-indicates when object sends or receives a message

FITNESS CLASS SCHEDULE STUDENT MANAGER FITNESS CLASS SCHEDULE REGISTRATION RECORD request fitness class Check Notify Pay Register X The sequence diagram for the ADD NEW STUDENT use case

State Transition Diagrams Shows how an object changes from one state o another, depending n events that effect the object The small circle to the left is the initial state, or the point where the object first interacts with the system Reading from left to right, the lines show direction and describe the action or event that causes a transition from one state to another The circle at the right with a hollow border is the final state

State Transition Diagrams Example of a state transition diagram for bank account

Activity Diagrams Activity diagram- resembles a horizontal flowchart that shows the actions and events as they occur Show the order in which the actions take place and identify the outcome Sequence diagrams, state transition diagrams, and activity diagrams are dynamic modeling tools that can help a systems analyst understand how objects behave and interact with the system

Activity Diagrams Activity diagram shows the actions and events involved in withdrawing cash from an ATM machine

CASE Tools Object modeling requires many types of diagrams to represent the proposed system Creating the diagrams by hand is time-consuming and tedious, so systems analysts rely on CASE tools to speed up the process and provide an overall framework for documenting the system components

Organizing the Object Model You should develop an object relationship diagram that provides an overview of the system You should organize your use cases and use case diagrams so they can be linked to the appropriate class, state transition, sequence, and activity diagrams It is much easier to repair a diagram now than to change the software later

Chapter Summary This chapter introduces object modeling, which is a popular technique that describes a system in terms of objects The Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system At the end of the object modeling process, you organize your use cases and use case diagrams and create class, sequence, state transition, and activity diagrams

Review questions What is object oriented analysis? Define an object and give an example. Define an attribute and give an example. Define a method and give an example. Define a use case and use case diagram.

Apply your knowledge Ipoh Community College has a typical school registration process. Student support services include faculty advisors and tutors. The administration has asked you as IT manager to develop an object oriented model for new registration system. List possible objects in the new registration system, including their attributes and methods Identify possible use cases and actors Create a use case diagram that shows how students register