Object Oriented Design II-Software Engineering-Lecture Slides, Slides of Software Engineering

Download Object Oriented Design II-Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!

CS 501: Software Engineering

Fall 2000

Lecture 12

Object-Oriented Design II

docsity.com

Administration

• Presentations

Your will have three presentations this semester Everybody in the team should present at least once

• A case study: a new client Client satisfaction is the first requirement!

docsity.com

Requirements: the Long Term

Believe that your software will be in use 5 years from now.

• What happens at end of semester?

Packaging and hand-over Client's technical preferences (C++, Java)

• Some system decisions based on short-term considerations
• Which formats, protocols, etc. do you think will last? (IIOP, RMI, SNMP, ...)

docsity.com

Requirements, Design and Implementation

Remember the definitions. Example: Consistency between two players of a board game

• The requirement is .....
• The design is .....

What is a requirements specification?

docsity.com

Modeling Classes

Given a real-life system, how do you decide what classes to use?

• What terms do the users and implementers use to describe the system? They are candidates for classes.
• Is each candidate class crisply defined?
• For each class, what is its set of responsibilities? Are the responsibilities evenly balanced among the classes?
• What attributes and operations does each class need to carry out its responsibilities?

docsity.com

Noun Identification: A Library Example

The library contains books and journals. It may have several copies of a given book. Some of the books are reserved for short-term loans only. All others may be borrowed by any library member for three weeks. Members of the library can normally borrow up to six items at a time, but members of staff may borrow up to 12 items at one time. Only members of staff may borrow journals.

The system must keep track of when books and journals are borrowed and returned and enforce the rules. docsity.com

Noun Identification: A Library Example

The library contains books and journals. It may have several copies of a given book. Some of the books are reserved for short-term loans only. All others may be borrowed by any library member for three weeks. Members of the library can normally borrow up to six items at a time, but members of staff may borrow up to 12 items at one time. Only members of staff may borrow journals.

The system must keep track of when books and journals are borrowed and returned and enforce the rules. docsity.com

Candidate Classes

Library the name of the system Book Journal Copy ShortTermLoan event LibraryMember Week measure MemberOfLibrary repeat Item book or journal Time abstract term MemberOfStaff System general term Rule general term docsity.com

Relations between Classes

Book is an Item

Journal is an Item

Copy is a copy of a Book

LibraryMember

Item

MemberOfStaff is a LibraryMember

Is Item needed?

docsity.com

Operations

LibraryMember borrows Copy

LibraryMember returns Copy

MemberOfStaff borrows Journal

MemberOfStaff returns Journal

Item not needed yet.

docsity.com

Class Diagram

MemberOfStaff

Journal Copy is a copy of Book

1..* 1

LibraryMember

1

0..12^ 0..*

1

on loan^ on loan

docsity.com

Rough Sketch: Wholesale System

A wholesale merchant supplies retail stores from stocks of goods in a warehouse.

What classes would you use to model this business?

docsity.com

Rough Sketch: Wholesale System

RetailStore

Warehouse

Order

Invoice

Product

Shipment

Merchant

docsity.com

Rough Sketch: Wholesale System

Warehouse

Order

Invoice

Product

RetailStore^ Merchant

name address contactInfo financialInfo

Shipment

Responsibilities -track status of shipped products

Reversals

damaged() return() wrongItem()

responsibility (text field)

docsity.com

Expanding a Class:

Modeling Financial Information

RetailStore 1 * Transaction

association

Invoice

Which class is Payment responsible for the financial records for a store?

docsity.com

Modeling Invoice

Shipment

Invoice invoiceNumber +goodsShipped() -sendInvoice()

goodsShipped PartsList _adornments

• public_

- private

??? RetailStore

invoiceRecord

docsity.com

Lessons Learned

Design is empirical. There is no single correct design. During the design process:

• Eliding: Elements are hidden to simplify the diagram
• Incomplete: Elements may be missing.
• Inconsistency: The model may not be consistent

The diagram is not the whole design. Diagrams must be backed up with specifications.

docsity.com

Levels of Abstraction

The complexity of a model depends on its level of abstraction:

• High-levels of abstraction show the overall system.
• Low-levels of abstraction are needed for implementation.

Two approaches:

• Model entire system at same level of abstraction, but present diagrams with different levels of detail.
• Model parts of system at different levels of abstraction.

docsity.com

Component Diagram

HelloWorld.class

hello.java

hello.hml

hello.jpg

executable component

docsity.com

Actor and Use Case Diagram

• An actor is a user of a system in a particular role. An actor can be human or an external system.
• A use case is a a task that an actor needs to perform with the help of the system.

Borrow book

BookBorrower

docsity.com

Use Cases and Actors

• A scenario is an instance of a use case
• Actor is role, not an individual

(e.g., librarian can have many roles)

• Actor must be a "beneficiary" of the use case

(e.g., not librarian who processes book when borrowed)

In UML, the system boundary is the set of use cases.

docsity.com

Use Cases for Borrowing Books

Borrow copy of book

BookBorrower Return copy of book

Reserve book Extend loan docsity.com

Relationships Between Use Cases:

<>

BookBorrower

Check for reservation

Extend loan

<>

<>

Borrow copy of book

docsity.com

Relationships Between Use Cases:

<>

Borrow copy BookBorrower of book

Refuse loan

<>

docsity.com

Use Cases in the Development Cycle

• Use cases are a tool in requirements analysis
• Intuitive -- easy to discuss with clients
• Use cases are often hard to translate into class models
• Scenarios are useful to validate design

docsity.com