contestada

The development team is expected to determine both functional and nonfunctional requirements. Some analysts may have strong business backgrounds which help them to understand the functional requirements quite well, but have a harder time even knowing what is important in the nonfunctional area. Similarly an analyst may have strong programming and other technical skills but not understand workflows or business process well.

Please respond to the following questions in a forum posting:

If you do not have a strong technical background, how do you ensure that you have found out all of the important nonfunctional requirements? How do you test or validate that you are not missing important things?

Similarly if you do not have a strong business process background, or very much knowledge about the problem domain (e.g. the business area being supported), how do you ensure that you have asked all the important questions and that your requirements are accurate, thorough, and comprehensive?

What are some techniques that might help you to have good interviews that get to the root of the issues?

Respuesta :

The development team is expected to determine both functional and nonfunctional requirements. Some analysts may have strong business backgrounds which help them to understand the functional requirements quite well, but have a harder time even knowing what is important in the nonfunctional area. Similarly an analyst may have strong programming and other technical skills but not understand workflows or business process well is responded in the following way

Explanation:

1.The functional requirement is describing the behavior of the system as it relates to the system's functionality. The non-functional requirement elaborates a performance characteristic of the system. Typically non-functional requirements fall into areas such as: Accessibility. Capacity, current and forecast.

2.Typical functional requirements include:

  • Business Rules.
  • Transaction corrections, adjustments and cancellations.
  • Administrative functions.
  • Authentication.
  • Authorization levels.
  • Audit Tracking.
  • External Interfaces.
  • Certification Requirements.

3.In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. They are contrasted with functional requirements that define specific behavior or functions.

4.A non-functional requirement defines the performance attribute of a software system. Types of Non-functional requirement are Scalability Capacity, Availability, Reliability, Recoverability, Data Integrity, etc. Example of Non Functional Requirement is Employees never allowed to update their salary information.

5.NFR's that constitute part of the product's scope belong on the Product Backlog. They can then be prioritized relative to other items by the Product Owner. This implies that they might not be necessary for every releasable increment.

6.Functional requirement. In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a specification of behavior between outputs and inputs

7.

Otras preguntas