SØG - mellem flere end 8 millioner bøger:
Viser: Writing Effective Use Cases
Writing Effective Use Cases Vital Source e-bog
Alistair Cockburn
(2000)
Pearson International
199,00 kr.
179,10 kr.
Leveres umiddelbart efter køb
Writing Effective Use Cases Vital Source e-bog
Alistair Cockburn
(2000)
Pearson International
167,00 kr.
150,30 kr.
Leveres umiddelbart efter køb
Writing Effective Use Cases Vital Source e-bog
Alistair Cockburn
(2000)
Pearson International
196,00 kr.
176,40 kr.
Leveres umiddelbart efter køb
Writing Effective Use Cases
Alistair Cockburn
(2001)
Sprog: Engelsk
Pearson Education
483,00 kr.
434,70 kr.
ikke på lager, Bestil nu og få den leveret
om ca. 10 hverdage
om ca. 10 hverdage
Detaljer om varen
- 1. Udgave
- Vital Source 90 day rentals (dynamic pages): 304 sider
- Udgiver: Pearson International (Oktober 2000)
- ISBN: 9780321605801R90
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. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.
Licens varighed:
Bookshelf online: 90 dage fra købsdato.
Bookshelf appen: 90 dage fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Bookshelf online: 90 dage fra købsdato.
Bookshelf appen: 90 dage fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Detaljer om varen
- 1. Udgave
- Vital Source 180 day rentals (dynamic pages): 304 sider
- Udgiver: Pearson International (Oktober 2000)
- ISBN: 9780321605801R180
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. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.
Licens varighed:
Bookshelf online: 180 dage fra købsdato.
Bookshelf appen: 180 dage fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Bookshelf online: 180 dage fra købsdato.
Bookshelf appen: 180 dage fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Detaljer om varen
- 1. Udgave
- Vital Source 365 day rentals (dynamic pages): 304 sider
- Udgiver: Pearson International (Oktober 2000)
- ISBN: 9780321605801R365
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. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.
Licens varighed:
Bookshelf online: 5 år fra købsdato.
Bookshelf appen: 5 år fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Bookshelf online: 5 år fra købsdato.
Bookshelf appen: 5 år fra købsdato.
Udgiveren oplyser at følgende begrænsninger er gældende for dette produkt:
Print: 2 sider kan printes ad gangen
Copy: højest 2 sider i alt kan kopieres (copy/paste)
Detaljer om varen
- Paperback: 304 sider
- Udgiver: Pearson Education (Juli 2001)
- ISBN: 9780201702255
Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use Cases, Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations. Cockburn begins by answering the most basic questions facing anyone interested in use cases: "What does a use case look like? When do I write one?" Next, he introduces each key element of use cases: actors, stakeholders, design scope, goal levels, scenarios, and more. Writing Effective Use Cases contains detailed guidelines, formats, and project standards for creating use cases -- as well as a detailed chapter on style, containing specific do's and don'ts. Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals. The book includes practice exercises with solutions, as well as a detailed appendix on how to use these techniques with UML. For all application developers, object technology practitioners, software system designers, architects, and analysts.
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.
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.
Writing Effective Use Cases
Butikker og åbningstid
Handler du som firma
Forretningsbetingelser
Porto og forsendelse
Data & cookiepolitik
Handler du som firma
Forretningsbetingelser
Porto og forsendelse
Data & cookiepolitik
Polyteknisk Boghandel og Forlag A/S - Anker Engelundsvej 1 - 2800 Lyngby
Tlf 77 42 43 44 - email poly@polyteknisk.dk - CVR 34072655 - Sydbank Reg: 6748 Konto 0001107927
Tlf 77 42 43 44 - email poly@polyteknisk.dk - CVR 34072655 - Sydbank Reg: 6748 Konto 0001107927
Polyteknisk Boghandel
har gennem mere end 50 år været studieboghandlen på DTU og en af Danmarks førende specialister i faglitteratur.
Vi lagerfører et bredt udvalg af bøger, ikke bare inden for videnskab og teknik, men også f.eks. ledelse, IT og meget andet.
Trykt eller digital bog?
Ud over trykte bøger tilbyder vi tre forskellige typer af digitale bøger:
Vital Source Bookshelf: En velfungerende ebogsplatform, hvor bogen downloades til din computer og/eller mobile enhed.
Du skal bruge den gratis Bookshelf software til at læse læse bøgerne - der er indbygget gode værktøjer til f.eks. søgning, overstregning, notetagning mv. I langt de fleste tilfælde vil du samtidig have en sideløbende 1825 dages online adgang. Læs mere om Vital Source bøger
Levering: I forbindelse med købet opretter du et login. Når du har installeret Bookshelf softwaren, logger du blot ind og din bog downloades automatisk.
Adobe ebog: Dette er Adobe DRM ebøger som downloades til din lokale computer eller mobil enhed.
For at læse bøgerne kræves særlig software, som understøtter denne type. Softwaren er gratis, men du bør sikre at du har rettigheder til installere software på den maskine du påtænker at anvende den på. Læs mere om Adobe DRM bøger
Levering: Et download link sendes pr email umiddelbart efter købet.
Ibog: Dette er en online bog som kan læses på udgiverens website.
Der kræves ikke særlig software, bogen læses i en almindelig browser.
Levering: Vores medarbejder sender dig en adgangsnøgle pr email.
Vi gør opmærksom på at der ikke er retur/fortrydelsesret på digitale varer.