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)

Pivotal NFR classification


This section describes pivotal NFRs and its various domain checklists.

Integrity

The degree to which the information is accurate and authentic.

Infrastructure domain

Will a different identification (user-ID) and authentication (password) be used for the test environment and the production environment?

Business domain

The following is the domain checklist:

  • Has the security within the user organization been arranged (see checklist for security)?
  • Is an efficient production scheme set up with a balanced regulation of priorities between the applications and with the supporting functions, such as the back-up procedure?
  • Is access to the computer center restricted to the people who belong there?
  • Is the computer center housed in a building that is optimally proof against stroke of lightning, fire, electricity failure, and water damage?
  • Will the input be checked?
  • Are passwords being used?
  • Will attempts for access be checked?
  • Has the choice for subsystems been argued?
  • Have all integrity...