#NON FUNCTIONAL REQUIREMENTS SOFTWARE#

These properties are addressed in ISO/IEC 9126–4 The usability is about how easy it’s for a user to use the platform and achieve the expected results with effectiveness, efficiency and satisfaction.

Good supportability results in more efficient maintenance and reduces operational costs.

Provide information that is useful for identify exceptions, debug and isolate the root of problems.

Installation and configuration of the system.

#NON FUNCTIONAL REQUIREMENTS SOFTWARE#

SupportabilityĪlso known as a serviceability, it refers to the ability of a software system to ease technical support in some areas: In this section are described different types of Non Functional Requirements in the same order shown in Arquitecto Software. Batch Sequential architecture can have a negative impact in usability while a MVC architecture has a great perform in this area. In order to evaluate which software architecture is the best for a digital project, it is necessary to know first which are the non functional requirements for the same.Įach software architecture style has different impact on each Non functional requirement. It allows to deliver great features without compromising the whole system and add complexity and technical debt. Why you should know about Non Functional RequirementsĮven if you are not a software architect, and you are a developer, taking care about non functional requirements it’s crucial. Non functional requirements, also known as Quality Attributes, arise from the needs of users, budget restrictions, company politics, interoperability with other software or hardware, external factors like security regulations or privacy legislation. As a result, a flight control system that does not meet reliability requirements will be insecure and therefore unusable. They can be much more critic than any other requirement. Non functional requirements are directly related with emergent properties of a software system and specify or restrict them. Requirements can be the base of a contract offer or the base contract itself in software projects. Requirements are the description of a services provided by a system and their operative restrictions.ĭiscover, analyse, document and verify requirements is the process known as Requirement Engineering. Previous to know about non functional requirements it is important to know what is a requirement in software engineering. What are Non Functional Requirements in software architecture