Truth 11
You, the business analyst, will change the way the user thinks about his problem, either now or later.
While solving a problem, it is seen as a duty of a business analyst to describe the problem to the user. When people understand the problem appropriately, they themselves will look into solutions to improve the case of the problem.
Types of the requirements:
Functional requirements: A functional requirement essentially specifies something the system should do.
Non-functional requirements: A non-functional requirement specifies how the system should behave.
Constraints: Constraints are effectively global requirements, such as limited development resources or a decision by senior management that restricts the way you develop a system.
Aziz
You, the business analyst, will change the way the user thinks about his problem, either now or later.
While solving a problem, it is seen as a duty of a business analyst to describe the problem to the user. When people understand the problem appropriately, they themselves will look into solutions to improve the case of the problem.
Types of the requirements:
Functional requirements: A functional requirement essentially specifies something the system should do.
Non-functional requirements: A non-functional requirement specifies how the system should behave.
Constraints: Constraints are effectively global requirements, such as limited development resources or a decision by senior management that restricts the way you develop a system.
Aziz
Comments
Post a Comment