Analysis Workflow-Object-Oriented Design-Lecture 6 Slides-Computer Engineering, Slides of Object Oriented Analysis and Design

Analysis Workflow, Objects, UML Object Notation, UML Class Notation, Instantiate Relationship, Visibility, Type, Attributes, Operations Signatures, Scope, Raman Ramsin, Lecture Slides, Object Oriented Design, Department of Computer Engineering, Sharif University of Technology, Iran.

Typology: Slides

2011/2012

Uploaded on 02/19/2012

hester
hester 🇮🇷

4.5

(13)

84 documents

1 / 15

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Department of Computer Engineering 1 Sharif University of Technology
Object-Oriented Design
Lecturer: Raman Ramsin
Lecture 6: Analysis Workflow
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Analysis Workflow-Object-Oriented Design-Lecture 6 Slides-Computer Engineering and more Slides Object Oriented Analysis and Design in PDF only on Docsity!

Department of Computer Engineering

Sharif University of Technology

Object-Oriented Design

Lecturer: Raman Ramsin

Lecture 6 : Analysis Workflow

Department of Computer Engineering

Sharif University of Technology

Analysis Workflow  The aim of the analysis workflow is to produce the Analysis Model.  The Analysis Model focuses on what the system needs to do, but leaves the details of how it will do it to the design workflow.  The Analysis Model defines and models:  Analysis classes - which model key concepts in the problem domain.  Use case realizations - which illustrate how instances of analysis classes can interact to realize system behavior specified by a use case.

Department of Computer Engineering

Sharif University of Technology

Analysis Modeling  Rules of thumb:  expect about 50 to 100 analysis classes in the analysis model of an average system  only include classes that model the vocabulary of the problem domain  do not make implementation decisions  focus on classes and associations - minimize coupling  use inheritance where there is a natural hierarchy of abstractions  keep it simple

Department of Computer Engineering

Sharif University of Technology

Objects  Object: "A discrete entity with a well-defined boundary that encapsulates state and behavior; an instance of a class."  Objects are cohesive units that combine data and function.  Encapsulation - the data inside an object is hidden and can only be manipulated by invoking one of the object's functions.  operations are specifications for object functions created in analysis  methods are implementations for object functions created in implementation

Department of Computer Engineering

Sharif University of Technology

UML Object Notation  No special symbols, punctuation marks, or abbreviations in object/class names.

Department of Computer Engineering

Sharif University of Technology

Classes and UML Class Notation  Class: "The descriptor for a set of objects that share the same attributes, operations, methods, relationships, and behavior.“

Department of Computer Engineering

Sharif University of Technology

Visibility

Department of Computer Engineering

Sharif University of Technology

Type  The Object Constraint Language (OCL) is a formal language for expressing constraints in UML models.  OCL defines standard operations for the UML primitive types (except UnlimitedNatural) and adds a new type called Real.

Department of Computer Engineering

Sharif University of Technology

Operations: Signatures

Operation (in p 1 :lnteger, inout p 2 :lnteger, out P 3 :lnteger, return P 4 :Integer, return P 5 :lnteger)

Department of Computer Engineering

Sharif University of Technology

Scope  Instance scope attributes and operations belong to or operate on specific objects:  instance scope operations can access instance-scope and class-scope operations/attributes;  Class scope attributes and operations belong to or operate on the whole class of objects:  class scope operations can only access other class scope operations.