Today I will talk about "Product requirements”, from a conceptual point of view, and how they have been handled under the AMR-One Project, where an autonomous mobile robot for the industry is developed.
The concept
Requirements Engineering is one of the processes of Systems Engineering, that is focused on defining, documenting, and maintaining requirements.
In the Waterfall Model, requirements engineering is presented as the first phase of the development process while Agile Methodologies, like Scrum, assume that requirements engineering continues through the lifetime of a system.
Basically, a requirement is a singular documented need that a particular design, product, or process must be able to perform.
Once all stakeholders are aligned, the requirements serve as a compass, providing clear direction toward a product's purpose while creating a shared understanding among business and technical teams.
The steps
The steps to follow with the requirements are in summary:
- Eliciting and expressing requirements (getting the Requirements from the client)
- Prioritizing requirements, for example in the form of:
- Must be done
- Should be done
- Could be done
- Analyzing requirements to ensure they are complete, clear, and consistent
- Analyzing also requirements from the technical point of view to ensure they are feasible in terms of time, cost and execution.
Types of requirements
- Business requirements (Define why the product is needed)
- Business rules (budget, policies or regulations, brand uniformity requirements,…)
- User Requirements (what tasks the users can do with the product)
- Functional Requirements (describe what the product should do)
- Non-functional Requirements (describe how well a product must perform)
- External interfaces
- Physical settings
- Development constraint
No comments:
Post a Comment