Ch14 - Recall The Team Skills 1. 2. Analyzing the Problem...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
01/17/12 1 Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires 2. Workshops 3. Brainstorming and idea reduction 4. Storyboarding 3. Defining the System 4. Managing Scope 5. Refining the System Definition 6. Building the Right System
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
01/17/12 2 Team Skill 3: Defining the System Define the system by focusing more on the features and deal with the increased amount of information . Ch 14: A Use Case Primer Ch 15: Organizing Requirements Information Ch 16: The Vision Document Ch 17: Product Management ( skipped )
Background image of page 2
01/17/12 3 Chapter 14 A Use Case Primer Use cases basics Benefits of use cases Steps of building use case model Use cases, storyboarding, and user interface design
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
01/17/12 4 Use Case Basics A use case describes a sequence of actions the system performs that yield an observable result of value to a particular actor. An actor is someone or something that interacts with the system. Users, other systems, or devices Documenting use cases by using use case templates: Name, decscriptions, Covered in the labs (UML Notes)
Background image of page 4
01/17/12 5 Use Case Basics Documenting use cases (Covered in the labs) by using use case templates: Name Description Actor(s) Flow of events Pre-conditions Post-conditions Etc . .. UML Diagrams
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
01/17/12 6 Example
Background image of page 6
01/17/12 7 The Benefits of Use Cases They are relatively easy to write and easier to read. They force developers to think through the design of a system from the perspective of a user. They engage the users in the requirements process: helping them understand the system that is being proposed. giving them a way to communicate and document their needs. They give context for the requirements of the system: One can understand why a requirement is what it is as well as how the system meets its objectives.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
01/17/12 8 The Benefits of Use Cases They provide an ordering mechanism for requirements: one can tell what has to happen before the next thing
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

Ch14 - Recall The Team Skills 1. 2. Analyzing the Problem...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online