CS 501 Software Engineering Lecture 13: Object-Oriented Design III, Slides of Software Engineering

Download CS 501 Software Engineering Lecture 13: Object-Oriented Design III and more Slides Software Engineering in PDF only on Docsity!

CS 501: Software Engineering

Fall 2000

Lecture 13

Object-Oriented Design III

docsity.com

Administration

Midterm examination

• Monday, October 16, 7:30 to 8:30 pm, Phillips 219
• Closed book
• About 5 questions on the material covered in lectures

docsity.com

Modeling Dynamic Aspects of Systems

Interaction diagrams: set of objects and their relationships including messages that may be dispatched among them

• Sequence diagrams: time ordering of messages
• Collaboration diagrams: structural organization of objects that send and receive messages Activity diagram: flow chart showing flow of control from activity to activity Statechart diagram: models a state machine

docsity.com

Bouncing Ball Diagrams

Example: http://www.cs.cornell.edu/

Client Servers

domain name

TCP

connection

HTTP get

docsity.com

Links

LibraryMember^ Copy

+borrowCopy() +returnCopy()

(^1) on loan 0..*

libMem:LibraryMember c:Copy

borrowCopy(c)

association

message

link

class

object

docsity.com

Sequence Diagram: Change in Cornell

Program

Cornellian

:MEngStudent

1 : getName()

sequence numbers added to messages

:PhDStudent

1.1 : name

2: new PhDStudent(name)

3: <>

docsity.com

Class Inheritance Diagram

Object

Component

Container

Panel

Applet

HelloWorld

ImageObserver

interface

docsity.com

Sequence Diagram:Painting Mechanism

:Thread :Toolkit :ComponentPeer target:HelloWorld

run run callbackLoop

handleExpose paint

docsity.com

Activity Diagram: Parallel Activities

Decompress

Stream video Stream audio

fork

join

start state

stop state docsity.com

State Diagram

State diagram for class Book

not borrowable

returned()

returned()

borrowable

borrowed()[not last copy]

borrowed()[last copy]

guard expression

docsity.com

Component Diagram

HelloWorld.class

hello.java

hello.hml

hello.jpg

executable component

docsity.com

Components and Classes

agent.dll

AgentAction

Policy

PatternSearch

docsity.com

Components and Classes

Classes represent logical abstractions. Components represent physical things.

Components may live on nodes.

Classes have attributes and operations directly. Components have operations that are reachable only through interfaces.

docsity.com

Interfaces

simulation.exe render.java

IRender

dependency

interface

realization

docsity.com