What is more, the classification may be overlapping, for instance when performance requirements are simultaneously governed by specific business needs (e.g accuracy for high-frequency trading or missile target acquisition) and computing resources. Non functionality is in the Eye of the Beholder: users and stakeholders may have different opinions. To begin with, non functional requirements seem to cover a wide diversity of situations, defying any consensus about an objective and straightforward understanding: depending on the business under consideration (e.g avionics vs insurance claims processing) requirements like data standards or response time may be seen as regulatory or technical, and consequently classified as functional or non functional. Non Functionality is in the Eye of the Beholder Looking at non functional requirements from an architecture perspective could provide a more consistent understanding. ![]() More generally, non functional requirements are best considered within a comprehensive and reasoned taxonomy based on two criteria: on one hand they do not deal with business requirements as such but with the way they are supported by system functionalities on the other hand they are nonetheless bound to functional requirements and expressed at system boundaries. Conversely, requirements regarding an encryption service will be seen as functional by the project in charge. For instance, even if response time or confidentiality concerns can be elicited through focused discussion with users, associated requirements are usually, but not always, managed by supporting organizational units. To simplify, if business analysts have nothing to say about it, it’s non functional. ![]() ![]() Functional requirements deal with the What, non functional requirements deal with the How (Ariel Schlesinger)Īs it appears, most of those understandings provide relative answers depending on who’s asking the question and who’s answering it. Despite (or because) being widely used, the term “non functional” applied to requirements is also associated with a broad range of understandings to cite a few: qualities of a system that can be specified independently of specific applications any requirement with no direct impact on functionalities available to users requirements dealing with how to solve a problem, as opposed to what is to be solved any requirements which cannot be fully specified and tested under the authority responsible for “functional” ones.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |