[1] Requirements
In this chapter I will describe the project requirements. The idea is to develop a basic e-commerce. Its specified features to an user can buy an item inside our app and features to an merchant control his sales.
Each requirement is described as a user story. A user story is a simple description of a feature making it clear who is the author or persona of that activity, the action that the author can take, and why the story exists. Each user story has some artifacts involved:
- definition of done: is a simple description of what flow the user should do so that developers can define when they have finished their activity;
- wireframe: in order to guide the development and flow that the user will have inside the application, it is important the work of designers in order to create a better experience. As this is not always possible, a prototype of average fidelity is created for each screens showing how the components (buttons, inputs, etc ...) a certain history fit visually;
- activities: a list of developer-focused activities, which can be used for a more technical description.
User Stories
1) As an unauthenticated user, I can browse all items
Definition of Done: An user can navigate in the initial page and see all items.
Wireframes:
2) As an unauthenticated user, I can browse all items by categories
Definition of Done: An user can use a select input to filter the categories.
Wireframe: same of user story 1.