Buy Use Cases Book by Daryl Kulak from book shop
Book 1
Book 2
Book 3
Book 1
Book 2
Book 3
Book 1
Book 2
Book 3
Book 1
Book 2
Book 3
Home > Computing and Information Technology > Computer programming / software engineering > Software Engineering > Use Cases: Requirements in Context
Use Cases: Requirements in Context

Use Cases: Requirements in Context


     0     
5
4
3
2
1



Available


X
About the Book

*Reduce the incidence of duplicate and inconsistent requirements; *Communicate requirements that are understandable to both users and developers; *Prototype the right system well before the design phase is underway; *Document the entire requirements process clearly and efficiently. Use Cases: Requirements in Context first examines the difficulties of requirements gathering and briefly introduces both use cases and the Unified Modeling Language (UML). Using detailed examples that run through the book, it then elaborates a four-step method for establishing requirements--an iterative process that produces increasingly refined requirements. Drawing on their own extensive experience, the authors offer practical advice on how to manage this process, including guidance on planning, scheduling, and estimating. They also reveal common mistakes and pitfalls to avoid. This detailed, hands-on book shows you how to: *Describe object relationships and interactions with use case diagrams and scenarios; *Specify functional and non-functional requirements; *Create the candidate use case list; *Break out detailed use cases and add detail to use case diagrams; *Add triggers, preconditions, basic course of events, and exceptions to use cases. Other topics include stakeholder interviews, use case name filters, the context matrix, user interface requirements, team organization, and quality assurance.

Table of Contents:
1. Preface The Trouble with Requirements. First and Least of All... What Is a Requirement? Functional Requirements. Nonfunctional Requirements. Requirements Gathering, Definition, and Specification. The Challenges of Requirements Gathering. Finding Out What the Users Need. Documenting Users' Needs. Avoiding Premature Design Assumptions. Resolving Conflicting Requirements. Eliminating Redundant Requirements. Reducing Overwhelming Volume. Ensuring Requirements Traceability. Issues with the Standard Approaches. User Interviews. Joint Requirements Planning Sessions. Requirements Lists. Prototypes. Those Troublesome Requirements. 2. Moving to Use Cases. It's All About Interactions. Hello World!. The Unified Modeling Language. Nine Diagrams. Extending the UML with Stereotyping. Introducing Use Cases, Use Case Diagrams, and Scenarios. The Goals of Use Cases. How Use Case Diagrams Show Relationships. The Use Case Template. Paths and Scenarios. Use Cases Apply Here. Use Cases for Inquiry-Only Systems. Use Cases for Requests for Proposals. Use Cases for Software Package Evaluation. Use Cases for Non-Object-Oriented Systems. Applying Use Cases to the Requirements Problem. 3. A Use Case—Driven Approach to Requirements Gathering. Requirements Specifications Tools. Principles for Requirements Success. Four Steps for Gathering Requirements. The Role of the Problem Statement. The Role of the Statement of Work. The Role of the Risk Analysis. The Role of the Prototype. The Roles of Use Cases. Use Cases Are Effective Communication Vehicles. Use Cases Can Be Used for Functional and Nonfunctional Requirements. Use Cases Help Ensure Requirements Traceability. Use Cases Discourage Premature Design. The Role of the Business Rules Catalog. Managing Success. 4. The Facade Iteration. Objectives. Steps in the Facade Iteration. Create a Problem Statement. Identify and Review Existing. Documentation and Intellectual Capital. Get the Executive Sponsor's Unique Viewpoint. Identify the Users, Customers, and Related Groups. Interview the Stakeholders. Find the Actors. Create the Facade Use Cases. Start the Business Rules Catalog. Create a Risk Analysis. Create a Statement of Work. Get Informal Approval from the Executive Sponsor. Tools. System Context Use Case. Use Case Name Filters. Candidate Use Case List. Actor Filter. Verb Filter. Noun Filter. Packages As Placeholders for Functionality. Facade Filter. Peer Review. User Review. Deliverables. Roles. Context. Summary. 5. The Filled Iteration. Objectives. Steps. Break Out Detailed Use Cases. Create Filled Use Cases. Collect and Document Nonfunctional Requirements. Add Business Rules. Test the Filled Use Cases. Put Some Things Off. Tools. The Stakeholder Interview. IPA Filter. White Space Analysis Filter. Abstraction Filter. Testing Use Cases with Scenarios. Review. Additional Use Cases. Deliverables. Roles. Context. Summary. 6. The Focused Iteration. Objectives. What Are Focused Use Cases? Steps. Create the Context Matrix. Remove Duplicate Processes. Bring Focus to Each Use Case. Scope Changes During This Iteration. Strategies for Change. Risks and Assumptions. Review. Opportunities Not Taken. System Damage. Client Sign-Off. Tools. Context Matrix. Dependency Filter. Surplus Functionality Filter. Narrow the Focus of the System. Identify Surplus Functionality Inside the Use Case. Vocabulary Filter. Deliverables. Roles. Context. Summary. 7. The Finished Iteration. Objectives. Steps. Add User Interface Requirements. Abstract and Combine Nonfunctional Requirements. Make Final Scope Decisions and Get Sign-Off. Baseline the Requirements. Tools. Use Case Review. Deliverables. Roles. Context. Summary. 8. Managing the Requirements Activity. Managing the Iterative, Incremental Lifecycle. Why Switch from Waterfall? The Meaning of ''Incremental''. The Meaning of ''Iterative''. From Waterfall to Iterative and Incremental. Developers Love It, but Managers Struggle. The Role of the Scenario in Management. Using Scenarios to Plan, Schedule, and Estimate. You Know the Plan Is Wrong. The Atmosphere During Requirements Gathering. Hectic Activity. Fear of the Future. Free-Flowing Adaptability. Managing Application and Architecture Requirements. Ensuring Quality in Requirements. Provide Unique Identification for Use Cases and Business Rules. Use a Database to Store Use Cases and Business Rules. Identify Change Cases. A Management Challenge. 9. Working in Teams. Organizing by Team. Splitting Up the Work. Deploying Configuration Management. Avoiding Quality Problems. Catch All the Requirements. Create Consistent Use Cases. Avoid Use Case Redundancy. 10. Classic Mistakes. Mistakes, Pitfalls, and Bruised Knees. Classic Mistakes: Make Them and Move On. 11. The Case for Use Cases. A. Use Cases Beyond Requirements. Business Modeling. Requirements Gathering. Analysis. Design. Use Case Hierarchies for User Interface Design. Using Scenarios As Units of Work for Transaction Processing. Architectural Use Cases. Using Actors As Security Profiles. Using Scenarios to Manage Security. Using Scenarios to Manage Prefetch. Construction. Testing. Deployment. Project Management. B. Case Study: Sell Property. The Facade Iteration. Problem Statement. Statement of Work. Risk Analysis. Facade Use Cases. The Filled Iteration. Risk Analysis. Filled use Cases. Business Rules. Context Matrix. Nonfunctional Requirements. Testing Using Scenarios. The Focused Iteration. Risk Analysis. Focused Use Cases. Business Rules. The Finished Iteration. Risk Analysis. Finished Use Cases. Business Rules. C. Case Study: Track Costume Sales. The Facade Iteration. Problem Statement. Statement of Work. Risk Analysis. Facade Use Cases. Business Rules. The Filled Iteration. Statement of Work. Filled Use Cases. Business Rules. Context Matrix. Nonfunctional Requirements. Testing Using Scenarios. The Focused Iteration. Risk Analysis. Focused Use Cases. Business Rules. The Finished Iteration. Finished Use Cases. Business Rules. Bibliography. Index. 0201657678T04062001

About the Author :
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


Best Sellers


Product Details
  • ISBN-13: 9780201657678
  • Publisher: Pearson Education (US)
  • Publisher Imprint: Addison Wesley
  • Height: 233 mm
  • No of Pages: 352
  • Sub Title: Requirements in Context
  • Width: 187 mm
  • ISBN-10: 0201657678
  • Publisher Date: 16 May 2000
  • Binding: Paperback
  • Language: English
  • Spine Width: 17 mm
  • Weight: 544 gr


Similar Products

Add Photo
Add Photo

Customer Reviews

REVIEWS      0     
Click Here To Be The First to Review this Product
Use Cases: Requirements in Context
Pearson Education (US) -
Use Cases: Requirements in Context
Writing guidlines
We want to publish your review, so please:
  • keep your review on the product. Review's that defame author's character will be rejected.
  • Keep your review focused on the product.
  • Avoid writing about customer service. contact us instead if you have issue requiring immediate attention.
  • Refrain from mentioning competitors or the specific price you paid for the product.
  • Do not include any personally identifiable information, such as full names.

Use Cases: Requirements in Context

Required fields are marked with *

Review Title*
Review
    Add Photo Add up to 6 photos
    Would you recommend this product to a friend?
    Tag this Book Read more
    Does your review contain spoilers?
    What type of reader best describes you?
    I agree to the terms & conditions
    You may receive emails regarding this submission. Any emails will include the ability to opt-out of future communications.

    CUSTOMER RATINGS AND REVIEWS AND QUESTIONS AND ANSWERS TERMS OF USE

    These Terms of Use govern your conduct associated with the Customer Ratings and Reviews and/or Questions and Answers service offered by Bookswagon (the "CRR Service").


    By submitting any content to Bookswagon, you guarantee that:
    • You are the sole author and owner of the intellectual property rights in the content;
    • All "moral rights" that you may have in such content have been voluntarily waived by you;
    • All content that you post is accurate;
    • You are at least 13 years old;
    • Use of the content you supply does not violate these Terms of Use and will not cause injury to any person or entity.
    You further agree that you may not submit any content:
    • That is known by you to be false, inaccurate or misleading;
    • That infringes any third party's copyright, patent, trademark, trade secret or other proprietary rights or rights of publicity or privacy;
    • That violates any law, statute, ordinance or regulation (including, but not limited to, those governing, consumer protection, unfair competition, anti-discrimination or false advertising);
    • That is, or may reasonably be considered to be, defamatory, libelous, hateful, racially or religiously biased or offensive, unlawfully threatening or unlawfully harassing to any individual, partnership or corporation;
    • For which you were compensated or granted any consideration by any unapproved third party;
    • That includes any information that references other websites, addresses, email addresses, contact information or phone numbers;
    • That contains any computer viruses, worms or other potentially damaging computer programs or files.
    You agree to indemnify and hold Bookswagon (and its officers, directors, agents, subsidiaries, joint ventures, employees and third-party service providers, including but not limited to Bazaarvoice, Inc.), harmless from all claims, demands, and damages (actual and consequential) of every kind and nature, known and unknown including reasonable attorneys' fees, arising out of a breach of your representations and warranties set forth above, or your violation of any law or the rights of a third party.


    For any content that you submit, you grant Bookswagon a perpetual, irrevocable, royalty-free, transferable right and license to use, copy, modify, delete in its entirety, adapt, publish, translate, create derivative works from and/or sell, transfer, and/or distribute such content and/or incorporate such content into any form, medium or technology throughout the world without compensation to you. Additionally,  Bookswagon may transfer or share any personal information that you submit with its third-party service providers, including but not limited to Bazaarvoice, Inc. in accordance with  Privacy Policy


    All content that you submit may be used at Bookswagon's sole discretion. Bookswagon reserves the right to change, condense, withhold publication, remove or delete any content on Bookswagon's website that Bookswagon deems, in its sole discretion, to violate the content guidelines or any other provision of these Terms of Use.  Bookswagon does not guarantee that you will have any recourse through Bookswagon to edit or delete any content you have submitted. Ratings and written comments are generally posted within two to four business days. However, Bookswagon reserves the right to remove or to refuse to post any submission to the extent authorized by law. You acknowledge that you, not Bookswagon, are responsible for the contents of your submission. None of the content that you submit shall be subject to any obligation of confidence on the part of Bookswagon, its agents, subsidiaries, affiliates, partners or third party service providers (including but not limited to Bazaarvoice, Inc.)and their respective directors, officers and employees.

    Accept

    Fresh on the Shelf


    Inspired by your browsing history


    Your review has been submitted!

    You've already reviewed this product!