ACS-3913Fall 2009 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;

Slides:

Advertisements

Similar presentations

Object Design Examples with GRASP

Advertisements

Feb 2003 R McFadyen1 Contracts (Ch 13) Used to help understand requirements more completely based on assertions; assertions are applicable to any.

Jan 23, Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented.

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Oct 22, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

March Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.

Fall 2009AXS-3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Oct Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns P. 248: “The assignment of responsibilities and design of collaborations.

Object-Oriented Analysis and Design

Jan 2005 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;

NJIT Use Case Model Operation Contracts Prepared By: Sumit Sharma.

Chair of Software Engineering Einführung in die Programmierung Introduction to Programming Prof. Dr. Bertrand Meyer Lecture 4: The Interface of a Class.

Chair of Software Engineering Einführung in die Programmierung Introduction to Programming Prof. Dr. Bertrand Meyer Lecture 4: The Interface of a Class.

6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)

Domain model: visualizing concepts

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Feb Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

September 2002 R McFadyen1 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3.

Chapter 10 Class and Method Design

Object-Oriented Analysis and Design

Eiffel Language and Design by Contract Contract –An agreement between the client and the supplier Characteristics –Expects some benefits and is prepared.

November Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Sept Ron McFadyen1 Extend Relationship.

Slide 1 Chapter 10 Class and Method Design. Slide 2 REVISITING THE BASIC CHARACTERISTICS OF OBJECT-ORIENTATION.

Use Case Model Operation Contracts Prepared By: Sumit Sharma and Sravanthi Gillala.

חוזים – Contracts 1. Larman – Chapter 10 – SSDs 10.2 What are System Sequence Diagrams? (introduction) Use cases describe how external actors interact.

9/18/011 Software Requirements Analysis and Design (Continued)

Object-Oriented Analysis and Design

Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative Development Part III Elaboration Iteration I – Basic1.

CSSE 374: More GRASP’ing and Use Case Realization Steve Chenoweth Office: Moench Room F220 Phone: (812) These.

INFO 620Lecture #51 Information Systems Analysis and Design Sequence and Collaboration Diagrams INFO 620 Glenn Booker.

CSSE 374: Operations Contracts and Logical Architectures Steve Chenoweth Office: Moench Room F220 Phone: (812)

What is a domain model? “A domain model captures the most important types of objects in the context of the business. The domain model represents the ‘things’

SOEN 6011 Software Engineering Processes Section SS Fall 2007 Dr Greg Butler

Object Oriented Analysis and Design System Events & Contracts.

SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler

Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.

Object Design Examples with GRASP (Ch. 18)

Use Case Model Operation Contracts Chapter 11 Applying UML and Patterns Craig Larman.

111 Protocols CS 4311 Wirfs Brock et al., Designing Object-Oriented Software, Prentice Hall, (Chapter 8) Meyer, B., Applying design by contract,

Review ♦ System sequence diagram ♦ Domain model

1 Lecture 6: Operation Contracts. 2 Overview  What is contract ?  The guidelines for writing contracts for the system operations.  Use Case realizations.

Operation Contracts: Getting ready to open the “System” black box All material from Applying UML and Patterns, 3 rd Edition, Craig Larman, chapter 11.

Larman ch. 131 Use-Case Model : Adding Detail with operation contracts Larman ch. 13.

Analysis 3: Associations, Attributes, Operations, Contracts CMPT 371 Fall 2004 J.W. Benham.

Chapter 11 Operation Contracts. What They Are An operation is a specification of a transformation or query that an object may be called on to execute.

COMP 6471 Software Design Methodologies Winter 2006 Dr Greg Butler

Operation Contracts. Primary way to describe system behavior is with use cases Operation contracts provide more details in terms of state changes to objects.

Week 4 Operational Contracts Requirements to Design Logical Architecture.

Fall 2009ACS-3913 Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.

Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.

OO Methodology Elaboration Phase Iteration 1- Part 3.

1 Chapter 9: Operation Contracts Chapter 13 in Applying UML and Patterns Book.

AP Java Ch. 4 Review Question 1  Java methods can return only primitive types (int, double, boolean, etc).

Object Design More Design Patterns Object Constraint Language Object Design Specifying Interfaces Review Exam 2 CEN 4010 Class 18 – 11/03.

Use-Case Model: Adding Detail with Operation Contracts.

1 Design Model Use-Case realizations with GRASP Larman chapter 17.

Testing It is much better to have a plan when testing your programs than it is to just randomly try values in a haphazard fashion. Testing Strategies:

1 Object Oriented Analysis and Design System Events & Contracts.

OO Methodology Elaboration Phase Iteration 1- Part 2.

TK2023 Object-Oriented Software Engineering

Chapter 9 Domain Models.

Design by Contract Jim Fawcett CSE784 – Software Studio

Design by Contract Jim Fawcett CSE784 – Software Studio

System Sequence Diagrams and Operation Contracts

Used to help understand requirements more completely

Slides by Steve Armstrong LeTourneau University Longview, TX

Operation Contracts Ch. 11.

Design Model: Creating Design Class Diagrams

Presentation transcript:

ACS-3913Fall 2009 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions; assertions are applicable to any element of the UML text discusses contracts for system operations; contracts are applicable to execution of any software component

ACS-3913Fall 2009 Ron McFadyen2 Domain Model Use Case Model text diagram SSD System operation contracts Design Model

ACS-3913Fall 2009 Ron McFadyen3 Contracts A contract is a technique for describing system operations in terms of state changes to objects in a Domain Model Contracts are based on work by Bertrand Meyer … Eiffel programming language and the concept of assertion a statement, a constraint or declaration, that must be true a false value indicates a bug

ACS-3913Fall 2009 Ron McFadyen4 Contracts Contract Components (Larman) Operation - name and parameters Cross References – where (use cases) operation used Preconditions – noteworthy assumptions about the state of the system or Domain Model objects Postconditions - state of objects after the operation completes objects:any new ones? any attributes modified? associations: any new or modified associations? Larman’s version is very informal

ACS-3913Fall 2009 Ron McFadyen5 Contracts Example Operation:enterItem (itemID : ItemID, quantity : integer) Preconditions there is a Sale underway Postconditions a SalesLineItem instance was created an association between the sale and the sales line item was created an attribute, quantity, was modified an association between the product description and the sales line item was created