Documente online.
Zona de administrare documente. Fisierele tale
Am uitat parola x Creaza cont nou
 HomeExploreaza
upload
Upload




SQA Suite: Requirements Management with Use Cases v5.5 Instructor Manual

software


þ þ Contents

Module 0 About This Course  0-1



Course Materials 0-3

Course Objectives 0-4

Intended Audience 0-5

Course Outline 0-6

Why Are We Here? 0-8

Understanding Your Needs! - Exercise 0-12

Module 1 Best Practices of Software Engineering 1-1

Practice 1: Develop Software Iteratively 1-9

Practice 2: Manage Requirements 1-16

Practice 3: Use Component Architectures 1-21

Practice 4: Visually Model Software 1-26

Practice 5: Verify Software Quality 1-32

Practice 6: Control Changes to Software 1-38

Rational Unified Process Implements Best Practices 1-47

Bringing It All Together: The Iterative Model 1-55

Module 2 Introduction to RMUC 2-1

Agreement on What the System Should Do 2-5

Definitions: Requirements and Requirements Management 2-6

Requirements Specifications 2-7

Factors in Project Sucess 2-9

Use-Case Model - Major Concepts 2-12

A Sample Use-Case Model - Exercise 2-15

Benefits of a Use-Case Model 2-18

A Use-Case Model Helps with 'Scope Creep' 2-19

The High Cost of Requirement Errors 2-20

Involve the Whole Team in Requirements 2-21

Module 3 Analyzing the Problem 3-1

Steps in Problem Analysis 3-6

Step 1 - Gain Agreement 3-7

What Problem Are We Solving? - Exercise 3-12

Step 2 - Identify the Stakeholders - Exercise 3-13

Step 3 - Define the System Boundaries 3-14

Use Actors to Help Define Boundaries 3-15

Useful Questions in Identifying Actors 3-21

Identify Actors - Exercise 3-22

Step 4 - Identify Constraints 3-23

Formulating a Problem Statement - Exercise 3-24

RUP Workflow Detail: Analyze the Problem 3-29

Module 4 Understanding Stakeholder Needs 4-1

What are Sources for Our Requirements? 4-4

Techniques for Eliciting Stakeholder Needs 4-8

Requirements Workshops 4-9

Brainstorming 4-13

How Can A Use-Case Model Help Elicit Needs? 4-16

Useful Questions in Identifying Use Cases 4-20

Interviews 4-23

Questionnaires 4-32

Role Playing 4-34

What About Business Modeling? 4-35

Reviewing Customer Requirement Specs 4-37

RUP Workflow Detail: Understanding Stakeholder Needs 4-40

Module 5 Defining the System 5-1

Develop or Adopt Standard Templates 5-4

Sample Requirements Specifications 5-5

The Vision Document 5-6

Section 3: Product Position Statement 5-9

Documents In The Use-Case Model 5-13

Use-Case-Model Survey - Template 5-14

Actor Properties in the Use-Case-Model Survey 5-16

Use-Case Properties in the Use-Case-Model Survey 5-18

Interaction Between Actors and Use Cases 5-22

Useful Questions in Identifying Use Cases 5-26

Avoiding Functional Decomposition 5-32

RUP Workflow Detail: Define the System 5-38

Module 6 Managing the Scope of the System 6-1

Using Requirement Attributes 6-6

Using Attributes to Prioritize - Exercise 6-10

How to Prioritize Use Cases 6-11

How to Manage Scope 6-14

Gain Control of the Requirements Input 6-15

Gain Control of the Requirements Output 6-17

Gain Control of the Requirements Process 6-18

All Requests Go Through a Single Channel 6-19

The Product Champion 6-20

Managing Expectations 6-21

Improve Your Negotiation Skills 6-23

RUP Workflow Detail: Manage Scope 6-24

Module 7 Refining System Definition 7-1

Specifying the Software Requirements 7-5

How Do Use Cases Help Define Software Req's? 7-9

Use-Case Report 7-11

Sample Basic Flow of Events 7-14

Structuring of Alternative Flows 7-31

Use of Pre- and Post-Conditions 7-37

What about Non-Functional Requirements? 7-41

What about Design Constraints? 7-49

A "Traditional" SRS Template - Based on IEEE 830 7-53

Qualities of a Software Requirement Specification 7-61

How to Describe User Interfaces 7-77

Storyboarding 7-78

Prototyping 7-80

What Is Not In an SRS? 7-84

RUP Workflow Detail: Refine the System Definition 7-85

Module 8 Managing Changing Requirements 8-1

Why Do Requirements Change? 8-4

Requirements Management Architecture 8-5

What About Metrics for Requirements Management? 8-6

What is Requirements Traceability? 8-7

Change Management 8-24

Requirements Configuration Management 8-26

Structuring the Use-Case Model 8-28

What is an Include Relationship? 8-30

What Is An Extend Relationship? 8-34

What is Use-Case Generalization? 8-39

What is Actor-Generalization? 8-44

RUP Workflow Detail: Manage Change 8-51

Module 9 Requirements Across the Product Lifecycle 9-1

Requirements Across the Product Lifecycle 9-4

Inception Iterations: Typical Requirements Results 9-6

Elaboration Iterations: Typical Requirement Results 9-8

Construction Iterations: Typical Req. Results 9-10

Transition Iterations: Typical Requirements Results 9-12

Iteration Assessment 9-13

Reviewing Requirements 9-14

Reviewing Requirements - Walkthrough 9-16

Reviewing Requirements - Inspection 9-17

Reviewing Requirements - Formal Review 9-22

RMUC - Summary 9-25

Glossary  G-1

References  R-1

Appendices

Appendix A - Rational University Instuction Guide

Appendix B - Guidelines for Exercises and Handouts


Document Info


Accesari: 1070
Apreciat: hand-up

Comenteaza documentul:

Nu esti inregistrat
Trebuie sa fii utilizator inregistrat pentru a putea comenta


Creaza cont nou

A fost util?

Daca documentul a fost util si crezi ca merita
sa adaugi un link catre el la tine in site


in pagina web a site-ului tau.




eCoduri.com - coduri postale, contabile, CAEN sau bancare

Politica de confidentialitate | Termenii si conditii de utilizare




Copyright © Contact (SCRIGROUP Int. 2024 )