SYS 366 Use Case Review SYS 366 Contents

SYS 366 Use Case Review SYS 366

Contents SYS 366 2

Use Case Reviews n n n Seeks to uncover flaws in use cases Final review might validate use cases Involves relevant stakeholders SYS 366 3

Types of Reviews n Informal n n n Take the form of a walkthough Can be conducted multiple times in the development cycle to get feedback Formal n n Usually for approval, not for feedback Often approves the results of the informal review which preceded it SYS 366 4

Walkthoughs n n Lead participants through use case step -by-step Can use storyboards to show steps in user interface dialogs Gain important feedback from participants More effective than sending out use cases for review SYS 366 5

When to Hold Reviews n Informal n n n Often, to get feedback Part of the iterative development process Formal n Once, at the end of requirements preparation SYS 366 6

Motivation n n Many participants will not want to review use cases or not see the purpose Motivate them! n n n Invite only those who need to be there Explain why their input is needed Explain the goals and the use case process Explain what they have to do Show them what’s in it for them SYS 366 7

Who Should Attend n n n Use case analysts Related developers Testers People from related business area No more that 4 -7 people in total SYS 366 8

The Review Meeting n Moderator n n Author n n The creator of the use case who can provide additional details Recorder n n Chairs the meeting and keeps it on track Takes minutes of the meeting Participants n Those providing feedback SYS 366 9

Things to Check n n n Actors and use cases have meaningful names Use case diagrams convey the main message Each use case provides value Actors without use cases and vice versa No communication between actors SYS 366 10

Interface Issues n n n Prototypes and storyboards provide feedback on the user interface Allow interface problems to be detected early Help participants visualize how the system will work SYS 366 11