Muutke küpsiste eelistusi

Use Cases: Requirements in Context [Pehme köide]

3.69/5 (51 hinnangut Goodreads-ist)
,
  • Formaat: Paperback / softback, 352 pages, kõrgus x laius x paksus: 233x187x17 mm, kaal: 544 g
  • Ilmumisaeg: 16-May-2000
  • Kirjastus: Addison Wesley
  • ISBN-10: 0201657678
  • ISBN-13: 9780201657678
Teised raamatud teemal:
  • Pehme köide
  • Hind: 51,84 €*
  • * saadame teile pakkumise kasutatud raamatule, mille hind võib erineda kodulehel olevast hinnast
  • See raamat on trükist otsas, kuid me saadame teile pakkumise kasutatud raamatule.
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Lisa soovinimekirja
Use Cases: Requirements in ContextSuurem pilt
  • Formaat: Paperback / softback, 352 pages, kõrgus x laius x paksus: 233x187x17 mm, kaal: 544 g
  • Ilmumisaeg: 16-May-2000
  • Kirjastus: Addison Wesley
  • ISBN-10: 0201657678
  • ISBN-13: 9780201657678
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780201657678.html
Märksõnad:
Software developers are increasingly recognizing the value of careful up-front requirements gathering in enhanced efficiency and reduced software defects. The best way to gather requirements accurately and precisely is with use cases and UML -- and this book walks you through the entire process, step-by-step. Both an excellent tutorial and a handy reference, Use Cases: Requirements in Context begins with a detailed overview of requirements gathering, its key challenges, and why traditional approaches often fail. Next, understand the key concepts underlying use cases; use case diagrams and scenarios; relationships and interactions; and the role of use cases in each major type of software development project. Review the four steps of the requirements gathering process, from problem statement through prototype; then walk through each iteration of the use case, step-by-step. The book includes insightful coverage of managing the requirements gathering process, building teams, and assuring quality -- plus a full chapter on the classic mistakes made in requirements gathering, and how to avoid them. For all systems analysts, project managers, and software engineers.

Muu info

Software developers are increasingly recognizing the value of careful up-front requirements gathering in enhanced efficiency and reduced software defects. The best way to gather requirements accurately and precisely is with use cases and UML -- and this book walks you through the entire process, step-by-step. Both an excellent tutorial and a handy reference, Use Cases: Requirements in Context begins with a detailed overview of requirements gathering, its key challenges, and why traditional approaches often fail. Next, understand the key concepts underlying use cases; use case diagrams and scenarios; relationships and interactions; and the role of use cases in each major type of software development project. Review the four steps of the requirements gathering process, from problem statement through prototype; then walk through each iteration of the use case, step-by-step. The book includes insightful coverage of managing the requirements gathering process, building teams, and assuring quality -- plus a full chapter on the classic mistakes made in requirements gathering, and how to avoid them. For all systems analysts, project managers, and software engineers.
Preface xv
The Trouble with Requirements
First and Least of All...
1(3)
What Is a Requirement?
4(5)
Functional Requirements
8(1)
Nonfunctional Requirements
9(1)
Requirements Gathering, Definition, and Specification
9(2)
The Challenges of Requirements Gathering
11(3)
Finding Out What the Users Need
11(1)
Documenting Users' Needs
12(1)
Avoiding Premature Design Assumptions
12(1)
Resolving Conflicting Requirements
12(1)
Eliminating Redundant Requirements
13(1)
Reducing Overwhelming Volume
13(1)
Ensuring Requirements Traceability
13(1)
Issues with the Standard Approaches
14(4)
User Interviews
14(1)
Joint Requirements Planning Sessions
14(1)
Requirements Lists
15(3)
Prototypes
18(1)
Those Troublesome Requirements
18(4)
Moving to Use Cases
It's All About Interactions
22(1)
Hello World!
23(3)
The Unified Modeling Language
26(8)
Nine Diagrams
28(5)
Extending the UML with Stereotyping
33(1)
Introducing Use Cases, Use Case Diagrams, and Scenarios
34(14)
The Goals of Use Cases
35(3)
How Use Case Diagrams Show Relationships
38(3)
The Use Case Template
41(5)
Paths and Scenarios
46(2)
Use Cases Apply Here
48(3)
Use Cases for Inauiry-Only Systems
49(1)
Use Cases for Requests for Proposals
50(1)
Use Cases for Software Package Evaluation
50(1)
Use Cases for Non-Object-Oriented Systems
50(1)
Applying Use Cases to the Requirements Problem
51(2)
A Use Case---Driven Approach to Requirements Gathering
Requirements Specification Tools
53(1)
Principles for Requirements Success
53(2)
Four Steps for Gathering Requirements
55(1)
The Role of the Problem Statement
56(1)
The Role of the Statement of Work
57(1)
The Role of the Risk Analysis
57(1)
The Role of the Prototype
57(2)
The Roles of Use Cases
59(1)
Use Cases Are Effective Communication Vehicles
59(1)
Use Cases Can Be Used for Functional and Nonfunctional Requirements
59(1)
Use Cases Help Ensure Requirements Traceability
59(1)
Use Cases Discourage Premature Design
60(1)
The Role of the Business Rules Catalog
60(2)
Managing Success
62(1)
The Facade Iteration
Objectives
63(3)
Steps in the Facade Iteration
66(8)
Create a Problem Statement
67(1)
Identify and Review Existing Documentation and Intellectual Capital
67(1)
Get the Executive Sponsor's Unique Viewpoint
68(2)
Identify the Users, Customers, and Related Groups
70(1)
Interview the Stakeholders
71(1)
Find the Actors
72(1)
Create the Facade Use Cases
72(2)
Start the Business Rules Catalog
74(1)
Create a Risk Analysis
74(1)
Create a Statement of Work
74(1)
Get Informal Approval from the Executive Sponsor
74(1)
Tools
74(9)
System Context Use Case
74(3)
Use Case Name Filters
77(1)
Candidate Use Case List
78(1)
Actor Filter
78(1)
Verb Filter
79(1)
Noun Filter
80(1)
Packages As Placeholders for Functionality
80(1)
Facade Filter
80(2)
Peer Review
82(1)
User Review
83(1)
Deliverables
83(1)
Roles
83(1)
Context
83(1)
Summary
84(1)
The Filled Iteration
Objectives
85(1)
Steps
86(15)
Break Out Detailed Use Cases
86(4)
Create Filled Use Cases
90(5)
Collect and Document Nonfunctional Requirements
95(4)
Add Business Rules
99(1)
Test the Filled Use Cases
99(1)
Put Some Things Off
100(1)
Tools
101(4)
The Stakeholder Interview
102(1)
IPA Filter
102(1)
White Space Analysis Filter
102(1)
Abstraction Filter
103(1)
Testing Use Cases with Scenarios
103(1)
Review
104(1)
Additional Use Cases
104(1)
Deliverables
105(1)
Roles
105(1)
Context
105(1)
Summary
105(2)
The Focused Iteration
Objectives
107(1)
What Are Focused Use Cases?
108(2)
Steps
110(1)
Create the Context Matrix
110(1)
Remove Duplicate Processes
110(1)
Bring Focus to Each Use Case
111(1)
Scope Changes During This Iteration
111(1)
Strategies for Change
112(1)
Risks and Assumptions
112(1)
Review
113(1)
Opportunities Not Taken
113(1)
System Damage
113(1)
Client Sign-Off
114(1)
Tools
114(4)
Context Matrix
114(1)
Dependency Filter
115(2)
Surplus Functionality Filter
117(1)
Narrow the Focus of the System
117(1)
Identify Surplus Functionality Inside the Use Case
117(1)
Vocabulary Filter
118(1)
Deliverables
118(1)
Roles
118(1)
Context
119(1)
Summary
119(2)
The Finished Iteration
Objectives
121(1)
Steps
122(6)
Add User Interface Requirements
122(3)
Abstract and Combine Nonfunctional Requirements
125(1)
Make Final Scope Decisions and Get Sign-Off
126(1)
Baseline the Requirements
127(1)
Tools
128(1)
Use Case Review
128(1)
Deliverables
128(1)
Roles
129(1)
Context
129(1)
Summary
129(4)
Managing the Requirements Activity
Managing the Iterative, Incremental Lifecycle
133(7)
Why Switch from Waterfall?
134(2)
The Meaning of ``Incremental''
136(1)
The Meaning of ``Iterative''
137(1)
From Waterfall to Iterative and Incremental
138(1)
Developers Love It, but Managers Struggle
139(1)
The Role of the Scenario in Management
140(1)
Using Scenarios to Plan, Schedule, and Estimate
140(1)
You Know the Plan Is Wrong
141(1)
The Atmosphere During Requirements Gathering
141(2)
Hectic Activity
142(1)
Fear of the Future
142(1)
Free-Flowing Adaptability
142(1)
Managing Application and Architecture Requirements
143(1)
Ensuring Quality in Requirements
143(2)
Provide Unique Identification for Use Cases and Business Rules
144(1)
Use a Database to Store Use Cases and Business Rules
144(1)
Identify Change Cases
144(1)
A Management Challenge
145(3)
Working in Teams
Organizing by Team
148(1)
Splitting Up the Work
149(1)
Deploying Configuration Management
149(1)
Avoiding Quality Problems
150(3)
Catch All the Requirements
150(1)
Create Consistent Use Cases
150(1)
Avoid Use Case Redundancy
151(2)
Classic Mistakes
Mistakes, Pitfalls, and Bruised Knees
153(1)
Classic Mistakes: Make Them and Move On
154(16)
The Case for Use Cases
Use Cases Beyond Requirements
Business Modeling
170(1)
Requirements Gathering
170(1)
Analysis
170(1)
Design
170(1)
Use Case Hierarchies for User Interface Design
171(1)
Using Scenarios As Units of Work for Transaction Processing
171(1)
Architectural Use Cases
172(1)
Using Actors As Security Profiles
172(1)
Using Scenarios to Manage Security
172(1)
Using Scenarios to Manage Prefetch
172(1)
Construction
173(1)
Testing
173(1)
Deployment
173(1)
Project Management
174(2)
Case Study: Sell Property
The Facade Iteration
176(1)
Problem Statement
176(1)
Statement of Work
176(1)
Risk Analysis
177(2)
Facade Use Cases
179(9)
The Filled Iteration
188(1)
Risk Analysis
188(2)
Filled Use Cases
190(14)
Business Rules
204(2)
Context Matrix
206(1)
Nonfunctional Requirements
207(3)
Testing Using Scenarios
210(1)
The Focused Iteration
211(1)
Risk Analysis
211(3)
Focused Use Cases
214(15)
Business Rules
229(3)
The Finished Iteration
232(1)
Risk Analysis
232(2)
Finished Use Cases
234(14)
Business Rules
248(4)
Case Study: Track Costume Sales
The Facade Iteration
252(1)
Problem Statement
252(1)
Statement of Work
252(1)
Risk Analysis
253(2)
Facade Use Cases
255(7)
Business Rules
262(3)
The Filled Iteration
265(1)
Statement of Work
265(1)
Filled Use Cases
266(12)
Business Rules
278(3)
Context Matrix
281(2)
Nonfunctional Requirements
283(2)
Testing Using Scenarios
285(1)
The Focused Iteration
286(1)
Risk Analysis
286(2)
Focused Use Cases
288(11)
Business Rules
299(3)
The Finished Iteration
302(1)
Finished Use Cases
302(9)
Business Rules
311(4)
Bibliography 315(2)
Index 317
Daryl Kulak is the president and CEO of Water-Logic Software (www.water-logic.com), an Internet business and technology consulting firm based in Columbus, Ohio. He is a graduate of the Northern Alberta Institute of Technology (NAIT) in Edmonton, Alberta. During much of his seventeen-year career managing software development projects in the United States and Canada, Daryl has focused on use cases, iterative/incremental development, and component design. Eamonn Guiney is a consultant at NewtonPartners (www.newtonpartners.com), a company that provides management consulting and system integration services to the money management industry. He is based in Sacramento, California. Eamonn creates business systems using a variety of tools, particularly object-oriented methodologies and use cases.

0201657678AB04012003