Sounds like crap.

But can you tell the difference between them? If not, look below.

1. Non-functional requirements are cross-border requirements.

A non-functional requirement is often related to multiple functions and is cross-border. It is precisely because of this crosscutting feature that non-functional requirements are more difficult to analyze and implement than ordinary functional requirements.

2. Non-functional requirements are more likely to make users dissatisfied.

When the software is delivered to users, some non-functional requirements are not realized, which will make users more dissatisfied. For example, it runs slowly. Can not meet the user's requirements for non-functional needs, it is more likely to lead to delayed delivery or even cancellation of the project.

3. Non-functional requirements have a greater impact on software architecture.

Cross-border non-functional requirements are very complex to implement, so they usually have a greater impact on software architecture. For example, architecture design should not allow high performance requirements (high running or processing speed) to span multiple layers in the software architecture. Because the modification of software architecture in the later stage of software development will take up a lot of time and affect the project delivery, it is in item.

Non-functional requirements should be analyzed from the beginning to judge the impact on software architecture.

4. Nonfunctional requirements are more likely to be mutually exclusive.

Non-functional requirements are usually mutually exclusive. Such as security requirements and availability requirements; Robustness requirements and performance requirements, etc. This is the problem to be solved in GJB5000A's special practice of requirement development process domain "analyzing requirements to achieve balance".

5. The description of non-functional requirements needs more details.

Non-functional requirements need more detailed description than functional requirements. When functional requirements are not specified, requirements analysts still know how to get there.

Realize it; As for the description of performance requirements such as "the response time should be as fast as possible", the requirements analyst can't judge what impact it has on the software architecture, and he doesn't know whether the implemented software meets the requirements.

Finally, in fact, this paper is not talking about the difference between non-functional requirements and functional requirements, but making developers pay more attention to the analysis, design and implementation of non-functional requirements, and can consider the impact of non-functional requirements on software architecture, project schedule, testing strategy and project cost in the early stage of the project.

This is exactly:

Requirements attach importance to nonfunctionality because it affects superfunctionality.

Users are even more dissatisfied with the progress and cost of the architecture.