An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach srs@vuse.vanderbilt.edu.

Slides:

Advertisements

Similar presentations

Use Cases  A use case depicts an interaction between the software program and the user (actors)  Example: Withdraw Money Customer Teller.

Advertisements

Slide 11.1 Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. Object-Oriented and Classical Software Engineering Eighth Edition,

Systems Analysis and Design in a Changing World, Fourth Edition

Slide 6C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 6B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 11C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Contemporary Engineering Economics, 4 th edition, © 2007 When Projects Require Financing Activities Lecture No. 41 Chapter 10 Contemporary Engineering.

Slide 11D.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 7D.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 10B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 8B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 7B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 5A.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 8A.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 7C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 5D.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 7A.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 5C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 6A.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

UML Activity Diagram. Activity Diagram  The main reason to use activity diagrams is to model the workflow behind the system being designed.  Activity.

Slide 19.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 11B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 5B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 7E.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 12E.121 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.

Slide 11.1 Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen.

Classification of UML Diagrams

FINANCE IN A CANADIAN SETTING Sixth Canadian Edition Lusztig, Cleary, Schwab.

Use Cases 1. Last week  Introduction to software engineering  How is it different from traditional engineering?  Introduction to specification  Operational.

1 Analysis Extracting from Use Cases to Create Diagrams.

Slide 0.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 20.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 12A.1 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.

Slide 12.1 Object-Oriented and Classical Software Engineering Chapter 12 Object Oriented Analysis.

Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.

Copyright © 2015, 2011, and 2007 Pearson Education, Inc. 1 Chapter 12 Business and Consumer Loans Section 5 Real Estate Loans.

THE ANALYSIS WORKFLOW  The specification document  Informal specifications  The analysis workflow  Extracting the entity classes  Functional modeling:

Slide 12.1 © The McGraw-Hill Companies, 2007 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach.

CHAPTER 13 OBJECT-ORIENTED ANALYSIS. Overview l The analysis workflow l Extracting the entity classes l The elevator problem case study l The test workflow:

How to Complete Entrance Counseling Studentloans.gov.

Slide 6D.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

Slide 12D.88 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.

Slide © The McGraw-Hill Companies, 2007 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach.

I can compute the maturity value and interest rate of a single payment loan.

Slide 10.1 Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen.

Slide 12F.135 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.

CHAPTER 12 OBJECT-ORIENTED ANALYSIS. Overview Extracting the entity classes Object-oriented analysis: The elevator problem case study Functional modeling.

Ingram, S. Entrepreneurship Planning the Small Business: Planned Financing.

Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2010 Stephen R. Schach

7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.

1 of 53 THE OBJECT-ORIENTED DESIGN WORKFLOW. 2 of 53 Overview The Design Workflow Traditional versus Object-Oriented Design Formats of the Attributes.

Slide 11.1 Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen.

Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R

Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R

Figure 7.1 MSG Foundation Information System Estimate Funds

Implementation workflow Implementation workflow

Object-Oriented Static Modeling of the Banking System - I

Annuities Chapter M7 Learning Objectives

Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach

We act as though comfort and luxury were the chief requirements of life, when all that we need to make us really happy is something to be enthusiastic.

Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach

Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach

An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach

Chapter 1: Introduction

effects of changing conditions

Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach

An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach

Copyright © 2004 The McGraw-Hill Companies, Inc. All rights reserved.

Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach

Process of Developing Project Cash Flows

Presentation transcript:

An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach srs@vuse.vanderbilt.edu

THE REQUIREMENTS WORKFLOW II CHAPTER 5 — Unit B THE REQUIREMENTS WORKFLOW II

Continued from Unit 5A

Revising the Requirements: MSG (contd) (3) Total estimated mortgage payments for the week and (4) Total estimated grant payments for the week: Use case Compute Weekly Repayment Amount models the computation of both the estimated mortgage payment and the estimated grant payment for each mortgage separately Summing these separate quantities gives The total estimated mortgage payments for the week, and The total estimated grant payments for the week

Revising the Requirements: MSG (contd) Now the use cases need to be reorganized Use case Compute Weekly Repayment Amount also models borrowers updating their weekly income Split Compute Weekly Repayment Amount into two separate use cases Use case Estimate Payments and Grants for Week, and Use case Update Borrowers’ Weekly Income

Estimate Payments and Grants for Week

Estimate Payments and Grants for Week (contd)

Update Borrowers’ Weekly Income

Third Iteration of the Revised Use-Case Diagram The two new use cases are shaded

Estimate Funds Available for Week Use case Estimate Funds Available for Week models the computation that uses the data obtained from three other use cases Estimate Investment Income for Week Estimate Operating Expenses for Week Estimate Payments and Grants for Week

Estimate Funds Available for Week (contd) Second iteration of use case

Estimate Funds Available for Week (contd) Second iteration of description of use case

«include» Relationship Correct use case (top); incorrect use case (bottom)

«include» Relationship (contd) The bottom diagram models use cases Estimate Funds Available for Week, and Estimate Payments and Grants for Week as two independent use cases However, a use case models an interaction between the information system itself and users of the information system (actors)

Continued in Unit 5C