Book Image

Mastering Non-Functional Requirements

By : Sameer Paradkar
Book Image

Mastering Non-Functional Requirements

By: Sameer Paradkar

Overview of this book

Non-functional Requirements are key to any software/IT program and cannot be overlooked or ignored. This book provides a comprehensive approach to the analysis, architecture, and measurement of NFRs. It includes considerations for bespoke Java, .NET, and COTS applications that are applicable to IT applications/systems in different domains. The book outlines the methodology for capturing the NFRs and also describes a framework that can be leveraged by analysts and architects for tackling NFRs for various engagements. This book starts off by explaining the various KPIs, taxonomies, and methods for identifying NFRs. Learn the design guidelines for architecting applications and systems relating to NFRs and design principles to achieve the desired outcome. We will then move on to various key tiers/layers and patterns pertaining to the business, database, and integrating tiers. After this, we will dive deep into the topics pertaining to techniques related to monitoring and measurement of NFRs, such as sizing, analytical modeling, and quality assurance. Lastly, we end the book by describing some pivotal NFRs and checklists for the software quality attributes related to the business, application, data, and infrastructure domains.
Table of Contents (14 chapters)

NFR - Simulation


Non-functional simulation (testing) targets non-functional requirements: the way a system performs, rather than specific behaviors. This is in contrast to functional testing, which targets functional requirements that describe the functions of a system and components. The names of non-functional tests are often used interchangeably because of the overlap between various non-functional requirements.

For example, performance is a broad term and will have coverage for attributes like reliability and scalability.

Non-functional testing is concerned with NFRs and is designed specifically to evaluate the readiness of a system according to the various quality attributes which are not covered by frequent functional testing. For example, in functional testing, it might be revealed that the function of inputting data into a set of cells within a database works, but usability testing (a part of non-functional testing) shows that persisting a version of the document requires two minutes...