© 2005 course technology1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa.

Slides:



Advertisements
Similar presentations
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
Ch 12: Object-Oriented Analysis
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
UML Class Diagram and Packages Written by Zvika Gutterman Adam Carmi.
Object Oriented System Development with VB .NET
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. slide 1 CS 125 Introduction to Computers and Object- Oriented Programming.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter Chapter 1 Introduction to Object-Oriented Programming and.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. slide 1 CS 125 Introduction to Computers and Object- Oriented Programming.
1 Basic Object Oriented Concepts Overview l What is Object-Orientation about? l What is an Object? l What is a Class? l Constructing Objects from Classes.
Chapter Chapter 1 Introduction to Object-Oriented Programming and Software Development.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 4 th Ed Chapter Lecture 1 Introduction to Computers and Object-
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 4 th Ed Chapter Chapter 1 Introduction to Object-Oriented Programming.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Chapter 9 Domain Models 1CS6359 Fall 2012 John Cole.
Object-Oriented Analysis and Design
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Object Oriented Software Development
Object Orientation An Object oriented approach views systems and programs as a collection of interacting objects. An object is a thing in a computer system.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter Chapter 1 Introduction to Object-Oriented Programming and.
11 1 Object oriented DB (not in book) Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Learning objectives: What.
1 A Student Guide to Object- Orientated Systems Chapter 4 Objects and Classes: the basic concepts.
OBJECT AND CLASES: THE BASIC CONCEPTS Pertemuan 8 Matakuliah: Konsep object-oriented Tahun: 2009.
Sadegh Aliakbary Sharif University of Technology Fall 2011.
1 Chapter 2 (Cont.) The BA’s Perspective on Object Orientation.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
1 UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mrs. Eman ElAjrami 2008 University.
Introduction To System Analysis and Design
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
System Analysis System Analysis - Mr. Ahmad Al-Ghoul System Analysis and Design.
1 Object-Oriented Systems Development Bahrami © Irwin/ McGraw-Hill Chapter 2: Object Basics Object-Oriented Systems Development Using the Unified Modeling.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Systems Analysis & Design 7 th Edition Chapter 5.
Object-Oriented Design Simple Program Design Third Edition A Step-by-Step Approach 11.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
1 Chapter 4 Analyzing End-to-End Business Processes.
Systems Analysis and Design in a Changing World, 6th Edition
BCS 2143 Object Oriented Design Using UML. Objectives Objects Interactions Finding Classes Relationship Between Classes Attribute and Operation Class.
Week III  Recap from Last Week Review Classes Review Domain Model for EU-Bid & EU-Lease Aggregation Example (Reservation) Attribute Properties.
Design Model Lecture p6 T120B pavasario sem.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
Software Engineering Zhang Shuang
1 Unified Modeling Language, Version 2.0 Chapter 2.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
OOPS CONCEPT.  OOPS  Benefits of OOPs  OOPs Principles  Class  Object Objectives.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter Chapter 1 Introduction to Object-Oriented Programming and.
Sadegh Aliakbary Sharif University of Technology Fall 2010.
CHAPTER 6 OBJECT ANALYSIS.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
DATA REQIREMENT ANALYSIS
Object-Oriented Analysis and Design
The Object-Oriented Thought Process Chapter 1
Mastering UML with Rational Rose 2002
Object Oriented Concepts
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
Presentation transcript:

© 2005 course technology1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mr. Ahmed Al Astal Chapter 2 The BA’s Perspective on Object Orientation

© 2005 course technology2 2 University Of Palestine Chapter Objectives At the end of this chapter, you will 1. Understand how OO affects the BA role on IT projects. 2. Understand key OO concepts: Objects Operations and attributes Encapsulation Classes Entity classes Relationships Generalization Association Aggregation Composition Polymorphism System use cases Business use cases Unified Modeling Language (UML)

© 2005 course technology3 University Of Palestine What Is OO? OO is an acronym for “object-oriented.” The OO analyst sees a system as a set of objects that collaborate by sending messages (that is, requests) to each other. OO affects the way the BA analyzes and models the requirements. OO affects the way the software engineer (technical systems analyst) designs the system specifications. OO affects the way the code itself is structured: Object- Oriented Programming Languages (OOPL) such as C++ and the.NET languages, support OO concepts and structures.

© 2005 course technology4 University Of Palestine The UML Standard UML is an acronym for Unified Modeling Language, a widely accepted standard for OO. The UML standards cover terminology and diagramming conventions. This book uses the latest version of that standard, UML 2.

© 2005 course technology5 University Of Palestine Cognitive Psychology and OO? As a Business Analyst, your job is to get inside the heads of your stakeholders so that you can extract what they know about a piece of the real world—a business system—and pass it on to the developers, who will simulate that system on a computer.

© 2005 course technology6 Objects Are the physical and conceptual things we find in the universe around us. Hardware, software, documents, human beings, and even concepts are all examples of objects. For purposes of modeling his or her company, a System Analyst could view employees, buildings, divisions, documents, and benefits packages as objects. University Of Palestine

© 2005 course technology7 The BA Perspective on Objects You begin to analyze a business system by asking stakeholders to describe its business objects. A business object is something the business (and the IT system that automates it) must keep track of, or that participates in business processes. Examples of such an object might include an invoice, a customer service representative, and a call. University Of Palestine

© 2005 course technology8 Attributes and Operations Because we are able to recognize an object again after having seen it once, the internal representation of the object must include a record of its properties. For example, we remember that a shirt object’s color is blue and its size is large. In OO, color and size are referred to as attributes; blue and large are attribute values. Every object has its own set of attribute values University Of Palestine

© 2005 course technology9 Attributes and Operations (Cont.) Something else we remember about an object is its function. For example, the first time you saw a crayon, it took you some time to learn that it could be used to scribble on the walls. Unfortunately for your parents, the next time you saw that crayon, you knew exactly what to do with it. Why? Because you remembered that scribble was something you could do with that object. In OO, scribble is referred to as an operation. University Of Palestine

© 2005 course technology10 The BA Perspective on Attributes and Operations The next step in analyzing a business system is to find out what attributes and business operations apply to each object. For example, two attributes that apply to an account object Attributes and Operations are balance and date last accessed; two operations that relate to the object are deposit and withdraw. University Of Palestine

© 2005 course technology11 University Of Palestine Operations and Methods Going one step further, you don’t just remember what you can do with an object, you also remember how you do it. For example, you know that you can place a call with a particular mobile phone—but you also remember that to do so, you must follow a particular procedure: first you enter the phone number and then you press the send key. In OO terms, place a call is an operation; the procedure used to carry it out is called a method.

© 2005 course technology12 University Of Palestine The BA Perspective on Operations and methods Next, you take each operation and ask stakeholders what procedure they use to carry it out. You document the procedure as a method. For example, you ask stakeholders what procedure they follow when withdrawing funds from an account. They tell you that they first check to see if there is a hold on the account and whether there are sufficient funds available for withdrawal. You document this procedure as the method used to carry out the withdraw operation.

© 2005 course technology13 University Of Palestine Operations and Methods Going one step further, you don’t just remember what you can do with an object, you also remember how you do it. For example, you know that you can place a call with a particular mobile phone—but you also remember that to do so, you must follow a particular procedure: first you enter the phone number and then you press the send key. In OO terms, place a call is an operation; the procedure used to carry it out is called a method.

© 2005 course technology14 University Of Palestine C++ Example: class Student { private: int stunum; public: void setstunum(int sn); int getstunum(); }; void Student::setstunum(int sn) { stunum = sn; } int Student::getstunum() { return stunum; } Attribute Operations Methods

© 2005 course technology15 University Of Palestine Encapsulation Every day you use objects without knowing how they work or what their internal structure is. This is the OO principle of encapsulation: Only an object’s operations are visible to other objects. Attributes and methods remain hidden from view.

© 2005 course technology16 University Of Palestine OO Concept: Classes Class: A classifier that describes a set of objects that share the same specifications of features, constraints, and semantics. A class is a category. All objects that belong to the same category have the same attributes and operations (but the values of the attributes may change from object to object).

© 2005 course technology17 University Of Palestine Example: If you say that two objects belong to the class Samsung camera phone, you know a number of things about them: The same attributes apply to both objects. For example, you know that both objects will have a serial number, a phone number, and various camera settings. Each object will have its own values for these attributes. The same operations apply to both objects. For example, you can place a call and take a picture with each of these objects. The same methods apply. For example, the procedure for placing a call is the same for both phones.