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

1
Object-Oriented and Classical Software
Engineering Sixth Edition, WCB/McGraw-Hill,
2005Stephen R. Schachsrs_at_vuse.vanderbilt.edu
2
CHAPTER 12 Unit E
OBJECT-ORIENTED ANALYSIS
3
Continued from Unit 12D
4
12.15.2 Buy a Masterwork Use Case

• The maximum price of a masterwork is computed by
  first treating the painting as if it were a
  masterpiece, and then adjusting the result

5
The Five Classes That Enter into This Use Case

• User Interface Class
• Compute Masterwork Price Class
• This class models the computation of the price
  Osbert should offer
• It creates a masterwork object and passes it to
  Compute Masterpiece Price Class as if it were a
  masterpiece
• Compute Masterpiece Price Class
• Masterpiece Class
• Auctioned Painting Class

6
Buy a Masterwork Use Case (contd)

• Class diagram (classes that enter into the use
  case)

Figure 12.37
7
Buy a Masterwork Use Case (contd)

• One possible scenario of the use case

Figure 12.38
8
Buy a Masterwork Use Case (contd)

• The remaining use cases are similar to those for
  the use case Buy a Masterpiece

9
12.15.3 Buy Other Painting Use Case

• Class diagram

Figure 12.39
10
Buy Other Painting Use Case (contd)

• Scenarios and interaction diagrams (collaboration
  diagrams, sequence diagrams), and associated
  flows of events are left as an exercise (Problems
  12.16 through 12.19)

11
Modifying the Main Menu

• The main menu must reflect buying the three
  different types of painting explicitly
• Buy a Painting must be replaced by
• Buy a Masterpiece,
• Buy a Masterwork, and
• Buy Other Painting

12
Modifying the Main Menu (contd)

• The revised screen is generated by
•  User Interface Class

Figure 12.40
13
Modifying the Main Menu (contd)

• The corresponding textual interface is

Figure 12.41
14
Continued in Unit 12F