Managing Software Requirements: A Use Case Approach Dean Leffingwell, Don Widrig
Publisher: Addison-Wesley Professional

Software systems must achieve, managing tradeoffs among the goals, and converting them into operational requirements. Managing Software Requirements Dean Leffingwell Don The Case Study 21. Managing Software Requirements: A Use Case Approach (Addison-Wesley Object Technology Series). Managing This approach gives the team a logical approach to defining where software. Managing Software Requirements: A Use Case Approach, Second. "Many projects fail because developers fail to build the right thing. 1) Use cases are for requirements only, which is not true. In my next blog I will describe how we adapted use cases to backlog driven development and managing cross-cutting concerns. A pattern-based approach [Barcalow 1997, Schumacher 2003, Fernandez 2001, Kienzle 2002,. Googling “use case” yields 6 times more hits than Googling “user story”, but software development should not be driven by popularity. In fact o The use-case approach can accommodate a wide range of levels of detail without introducing new and potentially confusing concepts. Requirements engineers evaluate the various requirements elici- tation techniques—such as structured or unstructured interviews and use and misuse cases— and select one.