1 CS 426/CPE 426 Senior Projects Chapter 5: Advanced Use Case Modeling [Arlow and Neustadt, 2005] February 14, 2008.

Slides:



Advertisements
Similar presentations
CS 221 Chapter 2 Excel. In Excel: A1 = 95 A2 = 95 A3 = 80 A4 = 0 =IF(A1
Advertisements

Fig. 4-1, p Fig. 4-2, p. 109 Fig. 4-3, p. 110.
Slide 1Fig. 2.1a, p.25. Slide 2Fig. 2.1b, p.25 Slide 3Table 2.1, p.25.
Slide 1Fig. 22.1, p.669. Slide 2Fig. 22.3, p.670.
Slide 1Fig. 17.1, p.513. Slide 2Table 17.1, p.514.
P.464. Table 13-1, p.465 Fig. 13-1, p.466 Fig. 13-2, p.467.
Fig. 11-1, p p. 360 Fig. 11-2, p. 361 Fig. 11-3, p. 361.
Activity Diagrams [Arlow and Neustadt, 2005] CS 425 / 625 Seminar on Software Engineering University of Nevada, Reno Department of Computer Science & Engineering.
Chapter 5: Advanced Use Case Modeling [Arlow and Neustadt, 2005] CS 426/CPE 426 Senior Projects University of Nevada, Reno Department of Computer Science.
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426/CPE 426 Senior Projects University of Nevada, Reno.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.
1 CS 426 Senior Projects Chapter 9: Relationships Chapter 10: Inheritance and Polymorphism [Arlow and Neustadt, 2005] February 12, 2009.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
Table 6-1, p Fig. 6-1, p. 162 p. 163 Fig. 6-2, p. 164.
1 CS 426/CPE 426 Senior Projects Chapter 5: Advanced Use Case Modeling [Arlow and Neustadt, 2002] February 13, 2007.
1 CS 691z/791z Topics in Software Engineering Chapter 13: Activity Diagrams & Chapter 19: Basic Statecharts [Arlow and Neustadt, 2002] March 8, 2007.
1 CS 426 Senior Projects Chapter 7: Classes and Objects & Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2002] February 14, 2006.
Chapter 5: Advanced Use Case Modeling [Arlow and Neustadt, 2005] CS 426/CPE 426 Senior Projects University of Nevada, Reno Department of Computer Science.
1 CS 426 Senior Projects Chapter 9: Relationships Chapter 10: Inheritance and Polymorphism [Arlow and Neustadt, 2002] February 27, 2007.
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] February 10, 2009.
1 CS 426 Senior Projects Chapter 14: Activity Diagrams [Arlow and Neustadt, 2005] February 17, 2009.
1 CS 691z/791z Topics in Software Engineering Chapter 20: Advanced Statechart Modeling [Arlow and Neustadt, 2002] March 8, 2007.
1 CS/CPE 426 Senior Projects Chapter 21: State Machines Chapter 22:Advanced State Machines [Arlow and Neustadt 2005] March 24, 2009.
1 CS 426 /CPE 426 Senior Projects Chapter 7: Classes and Objects & Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] February 19, 2008.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] February 5, 2009.
1 CS 691z / 791z Topics on Software Engineering Chapter 17: Interfaces and Subsystems [Arlow & Neustadt, 2002] March 6, 2007.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Figure 1.1 The observer in the truck sees the ball move in a vertical path when thrown upward. (b) The Earth observer views the path of the ball as a parabola.
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] CS 790M Project preparation (II) University of Nevada, Reno Department of Computer Science & Engineering.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
Chapter 14: Activity Diagrams November 2015 [Arlow and Neustadt, 2005] CS 425/625 Senior Projects University of Nevada, Reno Department of Computer Science.
Chapter 6: The Analysis Workflow Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426 Senior Projects in.
Chapter 9: Relationships Chapter 10: Inheritance and Polymorphism [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada,
Fig. 6-CO, p p. 185a p. 185b p. 185c p. 185d.
Chapter 16: The Design Workflow Chapter 17: Design Classes
Chapter 4: Use Case Modeling
CS 691z / 791z Topics on Software Engineering
February 12 – 19, 2018.
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
Chapter 19: Interfaces and Components
CS 426 Senior Projects Chapter 9: Relationships
UML Activity Diagrams & State Charts
CS/CPE 426 Senior Projects
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes
Chapter 5: Advanced Use Case Modeling
Chapter 4: Use Case Modeling
Chapter 14: Activity Diagrams
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes
Chapter 19: Interfaces and Components
CS/CPE 426 Senior Projects
Chapter 19: Interfaces and Components
Data Mining, Second Edition, Copyright © 2006 Elsevier Inc.
Chapter 14: Activity Diagrams
Chapter 4: Use Case Modeling
Fig. 6-CO, p. 211.
Chapter 14: Activity Diagrams
07CO, p. 190.
CS 420/620 HCI Use Case Modeling Project Preparation
CS 425 Software Engineering
CS 791Z State Machines & Advanced State Machines
CS 425/625 Software Engineering
02CO, p. 24.
Interfaces and Components
CS 426 CS 791z Topics on Software Engineering
CS 426 CS 791z Topics on Software Engineering
Chapter 19: Interfaces and Components
Presentation transcript:

1 CS 426/CPE 426 Senior Projects Chapter 5: Advanced Use Case Modeling [Arlow and Neustadt, 2005] February 14, 2008

2 Outline Actor generalization Use case generalization Inclusion: > Extension: > When to use advanced use case modeling

3 Roadmap Fig. 5.1 [Arlow & Neustadt 2005]

4 Actor Generalization. Fig. 5.2 [Arlow & Neustadt, 2005]

5.Actor Generalization Fig. 5.3 [Arlow & Neustadt, 2005]

6 Use Case Generalization… Table 5.1 [Jim Arlow and Ila Neustadt 2005]

7.Use Case Generalization.. Fig. 5.4 [Arlow & Neustadt 2005]

8..Use Case Generalization. Fig. 5.5 [Arlow & Neustadt 2005]

9 …Use Case Generalization Fig. 5.6 [Arlow & Neustadt, 2005]

10 Inclusion.. Fig. 5.7 [Arlow & Neustadt 2005]

11.Inclusion. Fig. 5.8 [Arlow & Neustadt, 2005]

12..Inclusion Fig. 5.9 [Arlow & Neustadt 2005]

13 Extension…. Fig [Arlow & Neustadt 2005]

14.Extension... Fig [Arlow & Neustadt 2005]

15..Extension.. Fig [Arlow & Neustadt 2005]

16 …Extension. Fig [Arlow & Neustadt 2005]

17 ….Extension Fig [Arlow & Neustadt 2005]

18 When to use advanced features Use advanced features when they simplify the model Heavy use of > should be avoided Many stakeholders, including object modelers misunderstand > Avoid use case generalization unless abstract parent use cases are used