1. Slide 7A.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. 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

2. Slide 7A.2 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CHAPTER 7 — Unit A THE ANALYSIS WORKFLOW II

3. Slide 7A.3 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter Overview l Extracting Entity Classes: MSG Foundation Case Study l Initial Functional Model: MSG Foundation Case Study l Initial Class Diagram: MSG Foundation Case Study l Back to the Requirements Workflow l Initial Dynamic Model: MSG Foundation Case Study l Revising the Entity Classes: MSG Foundation Case Study l Extracting Boundary Classes: MSG Foundation Case Study

4. Slide 7A.4 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter Overview (contd) l Extracting Control Classes: MSG Foundation Case Study l Use-Case Realization: MSG Foundation Case Study l Incrementing the Class Diagram l More on Actors l More on Use Cases l Risk l Rapid Prototyping l Scenarios and the Client’s Needs

5. Slide 7A.5 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Extracting Entity Classes: MSG Foundation l Entity class extraction is performed by iterating three steps – Functional modeling – Class modeling – Dynamic modeling

6. Slide 7A.6 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Extracting Entity Classes: MSG Foundation l The first step is to perform functional modeling

7. Slide 7A.7 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Initial Functional Model: MSG Foundation l The seventh iteration of the use-case diagram

8. Slide 7A.8 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Manage a Mortgage Use Case l One possible extended scenario

9. Slide 7A.9 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Manage a Mortgage Use Case (contd) l A second extended scenario

10. Slide 7A.10 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Estimate Funds Available for Week Use Case l One possible scenario

11. Slide 7A.11 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Produce a Report Use Case l One possible scenario

12. Slide 7A.12 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Produce a Report Use Case (contd) l Another possible scenario

13. Slide 7A.13 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Modeling l The second step of entity class extraction is class modeling – The two-stage noun extraction method is used

14. Slide 7A.14 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Noun Extraction: MSG Foundation l Stage 1: Describe the information system in a single paragraph – Weekly reports are to be printed showing how much money is available for mortgages. In addition, lists of investments and mortgages must be printed on demand.

15. Slide 7A.15 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Noun Extraction: MSG Foundation (contd) l Stage 2: Identify the nouns in this paragraph – Weekly reports are to be printed showing how much money is available for mortgages. In addition, lists of investments and mortgages must be printed on demand. l The nouns are report, money, mortgage, list, and investment

16. Slide 7A.16 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Noun Extraction: MSG Foundation (contd) l Nouns report and list are not long lived, so they are unlikely to be entity classes (report will surely turn out to be a boundary class), l money is an abstract noun l This leaves two candidate entity classes – Mortgage Class and Investment Class

17. Slide 7A.17 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. First Iteration of the Initial Class Diagram

18. Slide 7A.18 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Second Iteration of the Initial Class Diagram l Operations performed on the two entity classes are likely to be very similar – Insertions, deletions, and modifications l All members of both entity classes have to be printed on demand – Mortgage Class and Investment Class should be subclasses of a superclass called Asset Class

19. Slide 7A.19 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Second Iteration of Initial Class Diagram (contd)

20. Slide 7A.20 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Back to the Requirements Workflow l The current 5 use cases include Manage a Mortgage and Manage an Investment l These can now be combined into a single use case, Manage an Asset

21. Slide 7A.21 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Eighth Iteration of the Use-Case Diagram l The new use case is shaded

22. Slide 7A.22 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Second Iteration of Initial Class Diagram (contd) l Now the attributes are added

23. Slide 7A.23 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Iteration and Incrementation l The phrase “iterate and increment” also includes the possibility of having to decrement what has been developed to date – A mistake may have been made, and backtracking is needed – As a consequence of reorganizing the UML models, one or more artifacts may have become superfluous

24. Slide 7A.24 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Initial Dynamic Model: MSG Foundation l The third step is dynamic modeling – A statechart is drawn that reflects all the operations, showing the events that cause the transition from state to state l The major source of information regarding the relevant operations is the scenarios

25. Slide 7A.25 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study

26. Slide 7A.26 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l The statechart reflects the operations of the complete MSG Foundation information system – The solid circle on the top left represents the initial state, the starting point of the statechart – The white circle containing the small black circle on the top right represents the final state – States other than the initial and final states are represented by rectangles with rounded corners – The arrows represent possible transitions from state to state

27. Slide 7A.27 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l In state MSG Foundation Information System Loop, one of five events can occur l An MSG staff member can issue one of five commands: – estimate funds for the week – manage an asset – update estimated annual operating expenses – produce a report, or – quit

28. Slide 7A.28 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l These possibilities are indicated by the five events – estimate funds for the week selected – manage an asset selected – update estimated annual operating expenses selected – produce a report selected, and – quit selected l An event causes a transition between states

29. Slide 7A.29 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l An MSG staff member selects an option by clicking on the menu l This graphical user interface (GUI) requires special software

30. Slide 7A.30 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l Here is an equivalent textual user interface that can run on any computer

31. Slide 7A.31 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Statechart: MSG Foundation Case Study (contd) l Example: – The MSG staff member clicks on the choice Manage an asset – The event “manage an asset selected” has now occurred – The system moves from its current state, MSG Foundation Information System Loop, to the state Managing an Asset – The operations that the MSG staff member can perform in this state »Add, delete, or modify a mortgage or investment appear below the line in the box with rounded corner

32. Slide 7A.32 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Revising the Entity Classes: MSG Case Study l The initial functional model, the initial class diagram, and the initial dynamic model are completed – Checking them reveals a fault l In the initial statechart, consider state Update Estimated Annual Operating Expenses with operation Update the estimated annual operating expenses – This operation has to be performed on the current value of the estimated annual operating expense

33. Slide 7A.33 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Revising the Entity Classes: MSG (contd) l But where is the value of the estimated annual operating expenses to be found? l Currently there is only one class (Asset Class) and its two subclasses – Neither is appropriate for storing the estimated annual operating expenses

34. Slide 7A.34 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Revising the Entity Classes: MSG (contd) l The only way a value can be stored on a long-term basis is as an attribute of an instance of that class or its subclasses l Another entity class is needed in which the estimated annual operating expenses can be stored – MSG Application Class

35. Slide 7A.35 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Third iteration of the initial class diagram: MSG l MSG Application Class has other attributes as well – Attributes that do not appertain to the assets

36. Slide 7A.36 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Continued in Unit 7B