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)

Methodology discovering non-functional requirements


Business scenarios will be the key outcome of the analysis phase related to NFRs. These business scenarios may have interlinked user scenarios.

As an example, numerous business scenarios will be interlinked with the business continuity processes. Similar outcomes will be associated for scenarios with regard to availability events. The user scenario analysis will become complex with the sourcing of applications. However, specifications for business scenarios related to NFRs can benefit the organization from a planning and strategy perspective, specifically when these specifications are leveraged by different teams engaged in documenting NFRs, and in developing and maintaining business entities.

Non-functional requirements scenarios, which includes user stories, business scenarios, and so on, are the key output of this phase. The charting of NFRs to standards and best practices is also part of the life cycle. Architecting non-functional requirements...