Business Analysis - It Non-Functional Requirements

Learn how to uncover non functional requirements, techniques for making your applications full proof.

What you'll learn

Learn the key non functional ITRequirements concepts to thrive in the complex ITSoftware architecture delivery model

Non Functional Requirements basics – learn what a NFR is, what they do, and how they do it

Learn the ilities, -ities and -ness example usability, security and robustness etc.

Learn not what the software will do, but how the software will do it, for example, software performance requirements, software external interface requirements,

Learn how to Uncover Non-functional Requirements?

Learn NFR Approach. Learn How to validate NFR?

Requirements

This course covers all of the fundamentals - no prior knowledge is required

Description

Defining and addressing the nonfunctional requirements (NFRs) for a system are among the most important of a software architect’s / business analyst responsibilities. NFRs are the system quality attributes for a system, as distinct from the functional requirements, which detail a system’s business features and capabilities.Broadly, functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be.Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs.Functional requirements are usually in the form of "system shall do <requirement>", an individual action or part of the system, perhaps explicitly in the sense of a mathematical function, a black box description input, output, process and control functional model or IPO Model. In contrast, non-functional requirements are in the form of "system shall be <requirement>", an overall property of the system as a whole or of a particular aspect and not a specific function. The system's overall properties commonly mark the difference between whether the development project has succeeded or failed.Non-functional requirements are often mistakenly called the "quality attributes" of a system, however there is a distinction between the two. Non-functional requirements are the criteria for evaluating how a software system should perform and a software system must have certain quality attributes in order to meet non-functional requirements. Example: A system may be required to present the user with a display of the number of records in a database. This is a functional requirement. How current this number needs to be, is a non-functional requirement. If the number needs to be updated in real time, the system architects must ensure that the system is capable of displaying the record count within an acceptably short interval of the number of records changing.

Overview

Section 1: Introduction

Lecture 1 Introduction

Lecture 2 Chapter 1

Section 2: Why Non functional Requirements?

Lecture 3 Chapter 2

Lecture 4 Chapter 3

Lecture 5 Chapter 4

Lecture 6 Chapter 5

Lecture 7 Chapter 6

Lecture 8 Chapter 7

Lecture 9 Chapter 8

Lecture 10 Chapter 9

Lecture 11 Chapter 10

Business Analyst, Software Developers, Architect, Project Managers and everyone who builds Software and want to know fundamentals on NFR quickly.