Objectives-Object Oriented Analysis And Design-Lecture Slides, Slides of Object Oriented Analysis and Design

Concepts like action state, acctivity diagram, class diagram, constructiing and object, generalization, interaction diagram, software degin, state diagram use case diagram are main topics. Implemtentation are done using Unified Modelling Languae. This lecture includes: Objectives, UML, Introduction, Object, Modeling, Language, Unified, Attributes, Objects, Encapsulation

Typology: Slides

2011/2012

Uploaded on 08/12/2012

dhanvant
dhanvant 🇮🇳

4.9

(9)

89 documents

1 / 47

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
10-1
Objectives
Define object modeling and explain its benefits.
Recognize and understand the basic concepts
and constructs of object modeling.
Define the UML and its various types of
diagrams.
Evolve a business requirements use-case
model into a system analysis use-case model.
Construct an activity diagram.
Discover objects and classes, and their
relationships.
Construct a class diagram.
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f

Partial preview of the text

Download Objectives-Object Oriented Analysis And Design-Lecture Slides and more Slides Object Oriented Analysis and Design in PDF only on Docsity!

10-

Objectives

  • Define object modeling and explain its benefits.
  • Recognize and understand the basic concepts and constructs of object modeling.
  • Define the UML and its various types of diagrams.
  • Evolve a business requirements use-case model into a system analysis use-case model.
  • Construct an activity diagram.
  • Discover objects and classes, and their relationships.
  • Construct a class diagram.
  • 10-

Introduction to the UML

Unified Modeling Language (UML) – a

set of modeling conventions that is used

to specify or describe a software system

in terms of objects.

  • The UML does not prescribe a method for developing systems—only a notation that is now widely accepted as a standard for object modeling.

10-

Objects & Attributes

Object – something that is or is capable of being seen, touched, or otherwise sensed, and about which users store data and associate behavior.

  • Person, place, thing, or event
  • Employee, customer, instructor, student
  • Warehouse, office, building, room
  • Product, vehicle, computer, videotape Attribute – the data that represent characteristics of interest about an object.

10-

Behavior & Encapsulation

Behavior – the set of things that the

object can do that correspond to functions

that act on the object’s data (or attributes).

  • In object-oriented circles, an object’s behavior is commonly referred to as a method , operation , or service.

Encapsulation – the packaging of several

items together into one unit.

10-

Object Classes

Object Class – a set of objects that

share common attributes and behavior.

Sometimes referred to as a class.

10-

Inheritance

Inheritance – the concept wherein methods and/or attributes defined in an object class can be inherited or reused by another object class.

10-

Inheritance (cont.)

10-

UML Representation of

Generalization/Specialization

10-

Object/Class Relationships

Object/class relationship – a natural

business association that exists between

one or more objects and classes.

10-

Aggregation

Aggregation – a relationship

in which one larger ―whole‖

class contains one or more

smaller ―parts‖ classes.

Conversely, a smaller ―part‖

class is part of a ―whole‖

larger class

  • In UML 2.0 the notation for aggregation has been dropped

10-

Composition

Composition – an aggregation relationship in which the ―whole‖ is responsible for the creation and destruction of its ―parts.‖ If the ―whole‖ were to die, the ―part‖ would die with it.

10-

Polymorphism

Polymorphism – the concept that different objects can respond to the same message in different ways.

Override – a technique whereby a subclass (subtype) uses an attribute or behavior of its own instead of an attribute or behavior inherited from the class (supertype).

10-

UML 2.0 Diagrams

Diagram Description Use Case Depicts interactions between the system and external systems and users. In other words it graphically describes who will use the system and in what ways the user expects to interact with the system. The use-case narrative is used in addition to textually describe the sequence of steps of each interaction. Activity Depicts sequential flow of activities of a use case or business process. It can also be used to model logic with the system. Class Depicts the system's object structure. It shows object classes that the system is composed of as well as the relationships between those object classes. Object Similar to a class diagram, but instead of depicting object classes, it models actual object instances with current attribute values. The object diagram provides the developer with a "snapshot" of the system's object at one point in time. State Machine Models how events can change the state of an object over its lifetime, showing both the various states that an object can assume and the transitions between those states. Composite Structure Decomposes internal structure of class, component, or use case.docsity.com