|
|
|
 |
판매가 |
74,800원 → 73,500원  2% |
|
|
마일리지 |
 0% 0원 |
|
|
발행일 |
2000-10-05 | 중량: 0.48 kg | 사이즈: 18.8*23.2*1.4 cm
|
|
ISBN |
0201702258 | 9780201702255
|
|
기타정보 |
원서 | 270쪽
| $ 54.99
|
|
|
예상출고일
|
7~12일 소요예정 (근무일기준) |
|
배송비 |
무료배송
|
| |
|
정가, 판매가는 항공 운임료 포함 |
|
|
|
 |
| 프로그래밍
|
|
|
|
|
|
|
도서재고 |
미국 실시간 현지재고 - Ware House1 : 0 권, Ware House2 : 1 권
|
|
|
주의사항 |
- 현지사정에 의해 지연, 품절 될 수 있습니다.- 해외주문원서는 취소 및 반품이 불가능합니다(단, 파본이나 오발송은 제외 입니다.)- 수입절차/입고소요기간 자세히 |
|
|
 |
|
Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask: "How exactly am I supposed to write use cases?" Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable.
In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a "nuts-and-bolts" tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises—with answers—to illuminate the most important points.
|
 |
|
 |
Preface.
Acknowlegments.
1. Introduction.
What Is a Use Case (More or Less)?
USE CASE 1. Buy Stocks over the Web.
USE CASE 2. Get Paid for Car Accident.
USE CASE 3. Register Arrival of a Box.
Your Use Case Is Not My Use Case.
USE CASE 4. Buy Something (Casual Version).
USE CASE 5. Buy Something (Fully Dressed Version).
Steve Adolph: “Discovering” Requirements in New Territory.
Requirements and Use Cases.
Use Cases as Project-Linking Structure.
Figure 1: The “Hub-and-Spoke” Model of Requirements.
When Use Cases Add Value.
Manage Your Energy.
Warm Up with a Usage Narrative.
Usage Narrative: Getting “Fast Cash” .
Exercises.
PART I. THE USE CASE BODY PARTS.
2. The Use Case as a Contract for Behavior.
Interactions between Actors with Goals.
Actors Have Goals.
Figure 2: An Actor with a Goal Calls on the Responsibilities of Another.
Goals Can Fail.
Interactions Are Compound.
A Use Case Collects Scenarios.
Figure 3: Striped Trousers: Scenarios Succeed or Fail.
Figure 4: The Striped Trousers Showing Subgoals.
Contract between Stakeholders with Interests.
Figure 5: The Sud Serves the Primary Actor, Protecting Offstage Stakeholders.
The Graphical Model.
Figure 6: Actors and Stakeholders.
Figure 7: Behavior.
Figure 8: Use Case as Responsibility Invocation.
Figure 9: Interactions as Composite.
3. Scope.
Table a Sample In/Out List.
Functional Scope.
The Actor-Goal List.
Table a Sample Actor-Goal List.
The Use Case Briefs.
Table Sample Use Case Briefs.
Design Scope.
Figure 10: Design Scope Can Be Any Size.
Using Graphical Icons to Highlight the Design Scope.
Design Scope Examples.
Enterprise-to-System Examples.
USE CASE 6 Add New Service (Enterprise).
USE CASE 7 Add New Service (Acura).
Many Computers to One Application.
USE CASE 8 Enter and Update Requests (Joint System).
USE CASE 9 Add New Service (into Acura).
USE CASE 10 Note New Service Request (in BSSO).
USE CASE 11 Update Service Request (in BSSO).
USE CASE 12 Note Updated Request (in Acura).
Figure 11: Use Case Diagrams for Acura-BSSO.
Figure 12: A Combined Use Case Diagram for Acura-BSSO.
Nuts and Bolts Use Cases.
USE CASE 13 Serialize Access to a Resource.
USE CASE 14 Apply a Lock Conversion Policy.
USE CASE 15 Apply an Access Compatibility Policy.
USE CASE 16 Apply an Access Selection Policy.
USE CASE 17 Make Service Client Wait for Resource Access 49
The Outermost Use Cases.
Using the Scope-Defining Work Products.
Exercises.
4. Stakeholders and Actors.
Stakeholders.
The Primary Actor.
Why Primary Actors Are Unimportant (and Important).
Actors versus Roles.
Characterizing the Primary Actors.
Table a Sample Actor Profile Table.
Supporting Actors.
The System Under Discussion.
Internal Actors and White-Box Use Cases.
Exercises.
5. Three Named Goal Levels.
User Goals (Blue, Sea-Level).
Figure 13: Use Case Levels.
Two Levels of Blue.
Summary Level (White, Cloud/ Kite).
USE CASE 18 Operate an Insurance Policy+.
The Outermost Use Cases Revisited.
Subfunctions (Indigo/Black, Underwater/Clam).
Summarizing Goal Levels.
Using Graphical Icons to Highlight Goal Levels.
Finding the Right Goal Level.
Finding the User's Goal.
Raising and Lowering Goal Levels.
Figure 14: Ask “Why” to Shift Levels.
A Longer Writing Sample: “Handle a Claim” at Several Levels.
USE CASE 19 Handle a Claim (Business).
USE CASE 20 Evaluate Work Comp Claim.
USE CASE 21 Handle a Claim (Systems) +.
USE CASE 22 Register a Loss.
USE CASE 23 Find a Whatever (Problem Statement).
Exercises.
6. Preconditions, Triggers, and Guarantees.
Preconditions.
Minimal Guarantees.
Success Guarantee.
Triggers.
Exercises.
7. Scenarios and Steps.
The Main Success Scenario.
The Common Surrounding Structure.
The Scenario Body.
Action Steps.
Guidelines.
GUIDELINE 1: Use Simple Grammar.
GUIDELINE 2: Show Clearly “Who Has the Ball” .
GUIDELINE 3: Write from a Bird's Eye View.
GUIDELINE 4: Show the Process Moving Forward.
GUIDELINE 5: Show the Actor's Intent, Not the Movements.
GUIDELINE 6: Include a “Reasonable” Set of Actions.
Figure 15: A Transaction Has Four Parts.
GUIDELINE 7: “Validate,” Don't “Check Whether” .
GUIDELINE 8: Optionally Mention the Timing.
GUIDELINE 9: Idiom: “User Has System a Kick System B” .
GUIDELINE 10: Idiom: “Do Steps x-y Until Condition” .
To Number or Not to Number.
Exercises.
8. Extensions.
Extension Basics.
The Extension Conditions.
Brainstorm All Conceivable Failures and Alternative Courses.
GUIDELINE 11: Make the Condition Say What Was Detected.
Rationalize the Extensions List.
Rollup Failures.
Extension Handling.
GUIDELINE 12: Indent Condition Handling.
Failures within Failures.
Creating a New Use Case from an Extension.
Exercises.
9. Technology and Data Variations.
Figure 16: Technology Variations Using Specialization in UML.
10. Linking Use Cases.
Sub Use Cases.
Extension Use Cases.
Figure 17: UML Diagram of Extension Use Cases.
When to Use Extension Use Cases.
Exercises.
11. Use Case Formats.
Formats to Choose From.
Fully Dressed.
USE CASE 24 Fully Dressed Use Case Template.
Casual.
USE CASE 25 Actually Login (Casual Version).
One-Column Table.
Table 1 One-Column Table Format of a Use Case.
Two-Column Table.
Table 1 Two-Column Table.
RUP Style.
USE CASE 26 Register for Courses.
If-Statement Style.
Occam Style.
Diagram Style.
The UML Use Case Diagram.
Forces Affecting Use Case Writing Styles.
Consistency.
Complexity.
Standards for Five Project Types.
For Requirements Elicitation.
USE CASE 27 Elicitation Template—Oble a New Biscum.
For Business Process Modeling.
USE CASE 28 Business Process Template—Symp a Carstromming.
For Sizing the Requirements.
USE CASE 29 Sizing Template—Burble the Tramling.
For a Short, High-Pressure Project.
USE CASE 30 High-Pressure Template: Kree a Ranfath.
For Detailed Functional Requirements.
USE CASE 31 Use Case Name—Nathorize a Permion.
1Conclusion.
1Exercise.
PART II. FREQUENTLY DISCUSSED TOPICS.
12. When Are We Done.
On Being Done.
13. Scaling Up to Many Use Cases.
Say Less about Each One (Low-Precision Representation).
Create Clusters of Use Cases.
14. CRUD and Parameterized Use Cases.
CRUD Use Cases.
USE CASE 32 Manage Reports.
USE CASE 33 Save Report.
Parameterized Use Cases.
15. Business Process Modeling.
Modeling versus Designing.
Work from the Core Business.
Figure 18: Core Business Black Box.
Figure 19: New Business Design in White Box.
Work from Business Process to Technology.
Figure 20: New Business Design in White Box (Again).
Figure 21: New Business Process in Black-Box System Use Cases.
Work from Technology to Business Process.
Linking Business and System Use Cases.
Rusty Walters: Business Modeling and System Requirements.
16. The Missing Requirements.
Precision |
|
|
 |
| 준비 중입니다. |
|
|
|
|
|
|
|
|
|
|
|
|
Home > 
POD(Printed On Demand)
