In software industry Requirement defines what our end goal is that customers exactly need and what will make our company to increase its business.It could be a product or service company which makes software products or offers services in various software fields, the most important thing is the requirement and how well the requirements are met.
Under Waterfall model, the Requirement documents are huge docs as the whole product is implemented in one phase. But this is not the case with Agile/SCRUM because in these methodologies the requirements are given for small functionalities or features as the product is prepared in a step by step manner.
User Story: A user story is a requirement for any functionality or feature which is written down in one or two lines and max up to 5 lines. A user story is usually the simplest possible requirement and is about one and only one functionality (or one feature).
It will be developed by Business Analyst based on the requirement specification.
It is a detailed description of the Specification in a simplified version with realtime scenarios.
The most commonly used standard format for a User Story creation is stated below:
As a (user role/customer), I want to (goal to be accomplished) so that I can (reason of the goal).
While writing a test case for a module, you write different tests for that module say, Creating a user.There may be several ways to create a user like, creating a user through wizard or through uploading set of users.
These are all the things we can call as a scenarios.
Based on Use case and scenarios, test cases will be written by the testers in software testing company.
One more thing, user stories aren't just single sentence affairs. The product owner also writes acceptance criteria, which define the boundaries of a user story, and are used to confirm when a story is completed and working as intended.
An acceptance criterion is a set of accepted conditions or business rules which the functionality or feature should satisfy and meet, in order to be accepted by the Product Owner/Stakeholders.
As a QA it is very important to understand the user story and its acceptance criteria profoundly with not even a single doubt remaining at the ‘start of testing’.