requirements-management

Can a single use case be partially implemented, or implemented over several phases? How to track & prioritize components?

亡梦爱人 提交于 2019-12-11 17:40:34
问题 My requirements experience has been primarily with user stories, not use cases. I've been recently added to a project as a product owner, and the customer is ~80% done with the use cases. Many of the use cases include what would be over a dozen user stories, and the team is discussing how to implement some of the use cases over multiple phases, or how to partially implement to meet schedule. This wouldn't be a problem with stories, but I'm not sure the best way to approach with use cases. Can

Software Requirements Analysis [closed]

风格不统一 提交于 2019-12-09 10:49:16
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . There are many tools out there for writing and managing requirements, but are there any good ones for reviewing them? I'm not talking about managing reviews, but automation tools that look for common requirement blunders (such as using negative requirements, or ones that are worded in a way that makes testing

Software Requirements Analysis [closed]

给你一囗甜甜゛ 提交于 2019-12-03 13:58:02
Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. There are many tools out there for writing and managing requirements, but are there any good ones for reviewing them? I'm not talking about managing reviews, but automation tools that look for common requirement blunders (such as using negative requirements, or ones that are worded in a way that makes testing difficult). More of a screening tool that someone writing requirements can use to screen their document before