1 / 11

SYS366

SYS366. Use Case Review. Contents. Use Case Reviews. Seeks to uncover flaws in use cases Final review might validate use cases Involves relevant stakeholders. Types of Reviews. Informal Take the form of a walkthough Can be conducted multiple times in the development cycle to get feedback

glorialopez
Download Presentation

SYS366

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SYS366 Use Case Review

  2. Contents SYS366

  3. Use Case Reviews • Seeks to uncover flaws in use cases • Final review might validate use cases • Involves relevant stakeholders SYS366

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

  5. Walkthoughs • 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 SYS366

  6. When to Hold Reviews • Informal • Often, to get feedback • Part of the iterative development process • Formal • Once, at the end of requirements preparation SYS366

  7. Motivation • Many participants will not want to review use cases or not see the purpose • Motivate them! • 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 SYS366

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

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

  10. Things to Check • 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 SYS366

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

More Related