Functional and non-functional requirements can make or break your IT project. Defining solution-level requirements (aka functional and non-functional requirements) is a core competency for anyone in an organization responsible for defining future Information Technology (IT) applications. This book will give the reader a set of simple, repeatable techniques for extracting solution-level specifications from business and stakeholder requirements.

Functional requirements such as “calculate sales tax” or “enter order” can also be expressed in Process Model Diagrams. However, non-functional requirements such as “2 second response time (performance)” or “only c-level managers will be allowed to execute this function (security)” are most often expressed in natural language.

My co-author, Angela, and I have used the techniques presented in this book on hundreds of IT projects around the globe and we know the value each provides. Using these approaches will improve your ability to identify and document requirements at the level of detail that solution providers (vendors or developers) need to deliver the right technology for their organization.

Regardless of your job title or role, if you are involved in defining future business solutions, this book will help you communicate your business needs to solution providers. It will reduce the potential for misunderstandings that undermine IT’s ability to deliver the right technology for the business.

In this book you will learn how to:

-Decompose Business and Stakeholder Requirement Statements to identify Functional and Non-Functional Requirements

-Give those responsible for designing, building, and/or buying the solution the kind of information they need to make the decisions that are right for the business

-Identify Informational, Performance, and Constraining Requirements from a list of Functional Requirements

-Document and manage Business, Stakeholder, Functional and Non-Functional Requirements

-Capture and clarify Business Rules and External Constraints that mandate limits to the delivered solution

-Develop measurable Solution Requirements that facilitate End-User Acceptance Testing

HOW TO GET THE MOST OUT OF THIS BOOK?

To maximize the learning effect, you will have optional, online exercises to assess your understanding of each presented technique. You will run across chapter titles prefaced with the phrase “Exercise”. Those chapters contain a link to a web-based exercise that we have prepared to give you an opportunity to try the presented technique yourself.

THIS BOOK IS PART OF A SERIES

“Functional and Non-Functional Requirements – Simply Put!” is book 5 in the series "Business Analysis Fundamentals - Simply Put!". This series gives you a basic understanding of many core concepts in business analysis. It also teaches how to do the most common business analysis activities.

Each book has value on its own. It either provides an overview or demonstrates specific business analysis techniques. We do not expect everyone reading the series to become a professional business analyst, but it is a great first step. The world sorely needs good business analysts. Get your start with the series today!

Book 1: Business Analysis Defined
Book 2: How to Write Effective Requirements for IT - Simply Put! Use Four Simple Rules to Improve the Quality of Your IT Requirements
Book 3: Requirements Elicitation Techniques - Simply Put! Helping Stakeholders Discover and Define Requirements for IT Projects
Book 4: Data Flow Diagrams - Simply Put! Process Modeling Techniques for Requirements Elicitation and Workflow Analysis
Book 5: Functional and Non-Functional Requirements - Simply Put! Simple Requirements Decomposition / Drill-Down Techniques for Defining IT Application Behaviors and Qualities
Book 6: Requirements Elicitation Interviews and Workshops — Simply Put! Best Practices, Skills, and Attitudes for Requirements Gathering on IT Projects