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)

Closing thoughts


Software quality attributes are a critical factor in the longstanding success of any enterprise. Quality attributes increase organizational profitability, reduce maintenance cost, achieve loyalty, and customer fulfillment. Quality audits help ensure that the software achieves value and efficiency. However, it is crucial to perform software quality audits in a consistent and planned manner. These audits should be carried out throughout the SDLC, to verify and validate artifacts produced at the end of the various SDLC phases. Effective quality audits should not only focus on process conformance, but also incorporate software architecture, design, build, and testing to improve confidence in software quality.

Audit and accountability

Every stakeholder involved in an IT initiative must be held responsible for meeting the quality-attribute requirements. The process should be rolled-out, publishedm and understood by all the key stakeholders. Quality audits are not only held to find...