Hot answers tagged

3

No, this is not a common practice. QAs are and should be kept in light and every communication involved related to the requirements. The sole purpose of the documentation created during the requirement gathering phase is to keep it updated and validate the application according to that document, so this document serves as the single point of information for ...


2

In short: A user story describes desired behaviour of the system focussing on results and written in plain understandable language. More formally: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. A bug is something wrong in the system. Either a violation of ...


1

I would answer i and iii for these reasons: i) verification is the act of saying 'does this actually do what we built?'. The intention of software development is to build software that works the way you intended. iii) verification during unit testing or continuous testing helps the developer correct mistakes they have made as part of a continuous loop, or ...


1

I've seen this kind of specifications in companies where their users are provided with specific devices, as for example, doctors inside a hospital to access to the patients clinical registers... because they know that the app (or web) will be used only for a reduced set of devices. Another example, is when you are focusing on a specific market (China, US, ...



Only top voted, non community-wiki answers of a minimum length are eligible