Project Management
Requirements
Stakeholder
means that
Are the items that the customer needs to cover, basically the performance and tastes that he wants to cover
involves...
Engineers
Managers
Customer
easy?
It is a very complicated task for the manager to have the first idea about the project.
The success or failure of the project depends on this choice.
What is it?
Is anyone who has a direct interest in or benefits from the system
that is to be developed.
they are:
.
Business operations and product, marketing, internal and external
Product managers, marketing, internal and external customers
End users, consultants, product engineers, software engineers, maintenance, etc.
All of them have different ideas 
For this reason, all of your opinions should be taken into account
But who decides?
Project manager master may make the final decision about which requirements make the cut.
Requirements Engineering
These are techniques that lead to an understanding
understanding of the requirements.
When does it start?
It begins during the communication activity and continues in the modeling activity.
It should be adapted to the needs of the process, the project, the product and the people doing the work.
It provides the mechanism for understanding what the customer wants and analyzing feasibility, etc.
A project start when a need is known or a potential new market or service is discovered. Stakeholders from the business community (business managers, product marketing) define a business case for the idea by performing an in-depth analysis to ensure success in the project.
It has:
Elicitation is the practice of investigating and discovering the requirements of a system from users, customers, etc.
Collaborative requirements gathering
- The meeting is guided by a facilitator
- Use materials that allow for easy understanding
- A methodology is proposed so that ideas flow smoothly.
- They have rules for preparation and participation.
- Meetings with interested personnel
Kind of problems
Understanding
Volatility
Scope
The boundary is poorly defined, customers give ideas that only confuse.
Customers don't really know what they want, they don't realize the constraints.
Requirements change over time, either due to customer or project needs.
When to stop in requirements engineering? At the point where you have a firm foundation to start with design.
.
Elaboration
This task focuses on developing a refined requirements model that identifies various aspects of the function based on information obtained from the customer to information that emerges later. It is based on creating and refining scenarios that describe how the end user will interact with the product.
Negotiation
This is an important part where you differentiate between what you need and what is a whim.
Specification
It is helpful to use written documents or sketches to make it clear what was agreed upon.
VALIDATION
Examines the specification to ensure that all requirements have been performed in a consistent manner with no imperfections.
Functional Requirements
It is an important phase because the specifications and requirements must be clear and without tendency to errors of argumentation or requests.
Functional Requirements are the form or way that the product should take in different situations or cases.
In this point we have
User Requirements
System Requirements
It focuses on the specifications of how the product will work, as well as the limitations it will have.
These requirements specify what will be delivered to the customer, it is a description of the product in great detail because the customer will know it, to avoid confusion or non-conformities in the delivery, it is important to consider the points of the machine in the design of the same
involves
involves
Client, System end-users, Managers
Client, Engineers, Designers, Programers
Non Functional Requirements
They are restrictions in terms of services or functions, the restrictions can be of time, in terms of process, standards.
They are applied as a whole, not so much in the characteristics or system. They also focus on performance, safety and availability.
Non-functional requirements must be met, otherwise the product will not work and will directly affect the structure.
Product requirements
These requirements specify the behavior of the product (speed of response, performance, reliability, safety, usability).
Organizational requirements
External requirements
These requirements are general requirements derived from the policies and procedures of the customer's and developer's organization (operational processes, programming language, standards to be applied, environmental requirements for product operation).
These requirements contemplate all factors external to the system and its development process (Regulatory, Legislative, Ethical Requirements).