Tag Info

New answers tagged

5

To my understanding, LEAN development intends to optimize the development process of your team, with the focus on balancing between quality, costs and time. It is an organizational method, which does not embrace a specific syntax, language or notation. BDD, however, has its focus on "building the right software", and getting the requirements right, by using ...


0

Stumbled upon this during a google search and thought I would throw my opinion in. There is really no difference between a requirement and a user story. Both are stating the desired outcome or goal from a user perspective. The only difference is the way this goal or outcome is captured by a business analyst. In this case it is in the wording. Example: As ...


0

In the Sommerville sense: User requirements talk about the problem domain, the world of the user. They describe what effects need to be achieved. These effects are the combined responsibility of the software, the hardware, and the users. System requirements talk about the solution domain, the world of the software logic. They describe what the software ...


0

User requirements tell what application must/should do to satisfy user's needs. It a list of features an application must/should have, and it is used a guidance when you develop an application: then all points are checked, you are (probably) done. I tend to call this simply the "list of features". System requirements tell what system should have to be able ...


4

I'll speak to your examples. The first example of a "user requirement" is more like a wish or "feature." The way you can tell the difference between a feature and a requirement is that there's enough detail in the requirement to make it testable. Requirement 1 is not testable because, well, it's a wish. "I wish that the system had some reports for the ...



Top 50 recent answers are included