Non-functional Requirements
The non-functional requirements describe the qualities that your product must have. In another way, how well it does the things it does. Such requirements make the product attractive, usable, fast, reliable or safe. Non-functional requirements are used to specify response times, or accuracy limits on calculations. Non-functional requirements are given when the product needs to have a particular appearance or be used by people in particular circumstances.
Functional Versus Non-functional Requirements
Use Cases and Non-functional Requirements
Non-functional Requirements Types
10 Look and Feel:
The spirit of the product’s appearance.
11 Usability and Humanity:
The product’s ease of use, and any special considerations needed for better user experience.
12 Performance:
How fast, how safe, how many, how available, and how accurate the functionality must be.
13 Operational:
The operating environment of the product, and any considerations that must be taken into account for this environment.
14 Maintainability and Support:
Expected changes, and the time needed to make them; also the specification of the support to be given to the product.
15 Security:
Access, confidentiality, recoverability, and auditability of the product.
16 Cultural and Political:
Special requirements that come about because of the culture and customs of people who can come in contact with the product.
17 Legal:
The laws and standards that apply to the product.
Continuing with Non-functional Requirements, I wold like to explain more about Privacy
ReplyDeletePrivacy is a concern to more and more people, as well as to organizations.
We are dealing with privacy under the heading of security, but these requirements
could also be envisioned as legal requirements; most Western countries
have laws governing privacy of personal information held within computer systems.
Your own concern is most likely writing the requirements for what the
product has to do to ensure the privacy of its data. This capability is partly
controlled by access, as we discussed earlier, and partly by the product ensuring
that its data is not sent or distributed to unauthorized people.
For example, if data held within the product can be printed, the product
loses control of that data. Obviously, printed pages can be removed from the
organization’s office, in which case they are no longer secure and privacy can
no longer be guaranteed. In the United Kingdom, there have been several
recent cases of sensitive government information being printed and then
falling into the wrong hands. In one case—we are not making this up—the
documents were left on a commuter train in a folder marked “Top Secret.”
If your organization holds personal information about its customers, then
a little effort expended at the requirements stage might well prevent significant
fines being levied later if that private information is ever released, either
accidentally or intentionally, from the organization.
further explaining the non-functional requirements
ReplyDeleteINTEGRITY
Integrity means that the data held by the product corresponds exactly to
what was delivered to the product from the adjacent system (the authority
for the data). You must consider requirements for preventing the loss or corruption
of data and, should the worst happen, recovering lost or corrupted
data. Your product, when it goes into production, will hold data that is
important to the owning organization—integrity requirements are intended
to protect that data.
taking an example from TD bank if customer have different figures on his or her application and bank has different on there would a conflict and they have to sort it out afterwards. so integrity is really important in requirement when even we are dealing with figures.
As Harjeet mentioned before, the non-functional requirement must show to the end user the qualities that the product must have.
ReplyDeleteSome non-functional requirements are critical for the success of a new product or service. For example, the Look and Feel requirement is installed to make sure the project is following the branding standard of your organization. The company has an internal area responsible for this standard, for example, the design team.
The performance requirement is also important because its responsible to tell the project team if a task is been performed in given amount of time, some tasks also need to be done with a specific level of accuracy. Some aspects are important to the performance requirement, for example: speed to complete a task, safety to the operator, ranger of allowable values, etc.
To our TD app, these two non-function requirements are really important. Firstly, the app needs to show to the user that they are using a TD product and the Look and Feel help the project team. Second the performance is important because since this is a application, the transaction should be quickly and the app need to answer the customers’ request as fast as the customer internet is.