Building Requirements with Style

PowerPoint Presentation

Building Requirements With StyleCole CioranProgram Manager Requirements Definition and ManagementMay 29, 2015 2015 Blueprint Software Systems Inc. All rights reserved.

1 2015 Blueprint Software Systems Inc. All rights reserved.

Building requirements with stylePresenter: Cole CioranProgram Manager, Requirements Definition and ManagementActing VP Education, IIBA Toronto Chapter

Description: There are a wide variety of opinions about requirements. Cole will shed a little light on why the question is so contentious and help you understand what makes for a great requirement.

Learning Objectives: After this session, you will be able to:Understand the problem with requirementsIdentify the difference between requirements, examples, and modelsWrite better requirements!

2015 Blueprint Software Systems Inc. All rights reserved.2



Discussionof the Method

Favourite books introduce World Caf/facilitation format3 2015 Blueprint Software Systems Inc. All rights reserved.

What is a Requirement? 2015 Blueprint Software Systems Inc. All rights reserved.4

I think this question is a little bit like mission impossible fuse burning down4 2015 Blueprint Software Systems Inc. All rights reserved.

2015 Blueprint Software Systems Inc. All rights reserved.5What

How

Facile5 2015 Blueprint Software Systems Inc. All rights reserved.

Is What vs How Good Enough?Not really. For example:Solution requirements will dictate how a system must respond to user input in a very detailed mannerThis definition is often used to divide who documents requirements as opposed to what a requirement isThis creates more confusion as it makes the question dependent on the role as opposed to what is being created 2015 Blueprint Software Systems Inc. All rights reserved.6


So, What is a Requirement? 2015 Blueprint Software Systems Inc. All rights reserved.7A requirement is about your relationship to a decision. If its your decision to make then its design. If not, then it is a requirement.- Alistair Cockburn

So It depends7 2015 Blueprint Software Systems Inc. All rights reserved.

What is the Industry Standard? 2015 Blueprint Software Systems Inc. All rights reserved.8

Example: CIHI and Business Rules8 2015 Blueprint Software Systems Inc. All rights reserved.

2015 Blueprint Software Systems Inc. All rights reserved.9Everyone has adifferent definition.

Example: Business Rules9 2015 Blueprint Software Systems Inc. All rights reserved.

The Requirements Definition ProblemThere are multiple overlapping industry standardsConsulting companies market competing definitionsPractice leaders provide conflicting definitionsOrganizations implement their own standardsImmature practices result in multiple definitionsEveryone has a different definition



A Good Rule of Thumb? 2015 Blueprint Software Systems Inc. All rights reserved.11

If it has requirement in its name it is a requirement

What do you think?11 2015 Blueprint Software Systems Inc. All rights reserved.

Example: Business Rules 2015 Blueprint Software Systems Inc. All rights reserved.12OrganizationDefinitionTony Morgan Business Rules and Information Systems (2002)A compact statement about an aspect of the business. It is a constraint in the sense that a business rule lays down what must or must not be the case.Ronald Ross Principles of the Business Rules Approach (2003)A directive intended to influence or guide business behaviour.Barbara von Halle Business Rules Applied (2001)The set of conditions that govern a business event so that it occurs in a way that is acceptable to the business.IIBA BABOK 3.0A specific, practicable, testable directive that is under the control ofthe business and that serves as a criterion for guiding behaviour, shaping judgments, or making decisions.Object Model GroupA proposition that is a claim of obligation or necessity that is under business jurisdiction.Business Rules GroupA business rule is a statement that defines or constrains some aspect of the business.WikipediaAbusiness ruleis a rule that defines or constrains some aspect of businessand always resolves to either true or false.


What About? 2015 Blueprint Software Systems Inc. All rights reserved.13Constraint

Risk

Specification

Glossary

Principle

Value

Goal

Heuristic

Need

Objective

Rule

Stakeholder

Diagram

These are just a few of the types of artifacts our customers create in their systems13 2015 Blueprint Software Systems Inc. All rights reserved.

2015 Blueprint Software Systems Inc. All rights reserved.14How do we make sense of all of this?

Start with the fundamentals - 14 2015 Blueprint Software Systems Inc. All rights reserved.

Breakout One What Makes Up a Requirement?Facilitator: Share the definition for your requirement typeWhat have you called requirements that match this definition?What are some examples of this type of requirement?What do these examples have in common?Where are they different?



2015 Blueprint Software Systems Inc. All rights reserved.16Exemplia Gratia

e.g.

Id Est

i.e.

The Romans gave us two terms that cover most of what we call requirements16 2015 Blueprint Software Systems Inc. All rights reserved.

Exemplia Gratia e.g. or For ExampleUsed to provide an examplee.g. A user storyAs a traveler I want to fly to my destination so that I get there sooner.



What Makes a Good Example?Something to be imitated, an exemplar of success, a model of claritye.g. A user storyAs a , I want so that .



The problem is 2015 Blueprint Software Systems Inc. All rights reserved.19

Add video of early airplane fail19 2015 Blueprint Software Systems Inc. All rights reserved.

Which is why 2015 Blueprint Software Systems Inc. All rights reserved.20


Id Est i.e. or That IsUsed to restate an idea more clearly and offer more informationi.e. Requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.



The problem is 2015 Blueprint Software Systems Inc. All rights reserved.22

Add video of early airplane fail22 2015 Blueprint Software Systems Inc. All rights reserved.

Which is why 2015 Blueprint Software Systems Inc. All rights reserved.23


The Delicate DanceToo much detail constrains solutions, limits professional judgment, and creates inflexible systemsToo little detail results in gaps and unexpected outcomesThe challenge is to find the right level of detail and granularity at each stage in an organizations practiceMethods like scaled agile, iterative development, wagile, and so forth try to make the best of both worlds 2015 Blueprint Software Systems Inc. All rights reserved.24


What About Models?


Are models requirements? Ae they requirements or examples25 2015 Blueprint Software Systems Inc. All rights reserved.

Models Add Clarity and Relate RequirementsEvery model is designed to answer one or more questionsIf something in model doesnt speak to the question then it does not belong in the modele.g.A use case diagram answers the question of how use cases and actors are relatedBusiness rules should be extracted from business process models 2015 Blueprint Software Systems Inc. All rights reserved.26


Breakout Two What Makes a Requirement?Facilitator: Share definition and what has been done so farWhat templates or standards have you have seen for this requirement type?What are the key pieces you see in these standards?What pieces do we not need?What pieces would we need to make a complete requirement?



What Makes Writing Requirements so Hard? 2015 Blueprint Software Systems Inc. All rights reserved.28


How do you Write a Good Requirement? 2015 Blueprint Software Systems Inc. All rights reserved.29


What Makes Writing Requirements so Hard?Analysts need to make sense of the competing needs of a multitude of stakeholdersThe need to facilitate agreement around what those decisions are among senior leadersThe discipline is still maturingThere is no one source of truth for standardsThere is no common style guide for writing them either 2015 Blueprint Software Systems Inc. All rights reserved.30


What Makes a Good Requirement? 2015 Blueprint Software Systems Inc. All rights reserved.31CharacteristicThe Requirement:UnitaryAddresses one and only one thing.CompleteIs fully stated in one place without any missing information.AtomicThe requirement does not contain any conjunctions. e.g. and, or.TraceableThe requirement must meet all or part of a documented need for change.CurrentThe requirement be based on current conditions that apply to the organization.ConciseMust be objectively stated without jargon, acronyms, opinions, or vague language. It can only be interpreted in one way.Specified ImportanceMust specify how important it is. e.g. is it critical to the success of the solution, or is it a nice to have?VerifiableThe implementation of the requirement can be verified.


Seven Principles For Writing Great RequirementsDont write about the writingDont confuse the subject with your workOnly hedge when you shouldAvoid clichs like the plagueAvoid abstract nouns, not ideasDont turn your verbs into nounsAdopt an active, conversational style



Otherwise, Bring on the ZombiesIn the first part of this requirement we will explore the difficulty in creating alignment around the definition of a requirement. We might be able to institutionalize a universal taxonomy that will become the gold standard for the enterprise. If we can create alignment among the stakeholder community we create affirmation as to that universal taxonomy


How could we make this better?33 2015 Blueprint Software Systems Inc. All rights reserved.

Our customers need a common definition of what a requirement is in order to improve project delivery.


Not bad whats wrong with it?34 2015 Blueprint Software Systems Inc. All rights reserved.

Our customers must define what a requirement is in order to reduce the cost of rework on projects.


So, Is this a requirement or an example?35 2015 Blueprint Software Systems Inc. All rights reserved.

In the End it is ComplexThe definition will depend uponThe industry and productStandards the organization followsPeople and their capabilitiesRelationships between decision makersWhat people have learned or notTaking the time to make senseHistory of the organization with requirements 2015 Blueprint Software Systems Inc. All rights reserved.36

COE example36 2015 Blueprint Software Systems Inc. All rights reserved.

Breakout Three Give it Some StyleFacilitator: Share the definition and work so farWhat terms have you used to define the pieces of requirements?What standard definitions do we need to make those terms clear?Based on these terms, what would be a stylish example?How could we refine this example to make it clear, concise and compelling?



Summing it all UpRequirements, examples, and models co-existExamples and models show how the requirements fit togetherRequirements make sure we have covered all of the basesOur job as analysts is to make sure our stakeholders are confident that they will get what they needClear, concise, and compelling requirements do just that! 2015 Blueprint Software Systems Inc. All rights reserved.38


What Does This Have to do With Blueprint?Our customers must define what each artifact in Blueprint is in order to use the tool to reduce the cost of rework on projects.They will need requirements, models, and examplesThey need to understand how they are all relatedIndustry standard and best practice is a starting pointThe definition will have to be right for the organizationWe cannot force one on themWe must help them come to a definition 2015 Blueprint Software Systems Inc. All rights reserved.39


2015 Blueprint Software Systems Inc. All rights reserved.40How might better requirements help you?

Start with the fundamentals - 40 2015 Blueprint Software Systems Inc. All rights reserved.

Ragtime DanceScott JoplinPiano Rolls from archive.org, track 02014-10-03T12:48:50Ragtime161623.89

Date post:	15-Apr-2017
Category:	Business
Upload:	nicholas-cole-cioran
View:	262 times
Download:	1 times