Requirements Traceability – The What, Why, and How

“All things are poisons, for there is nothing without poisonous qualities. It is only the dose which makes a thing poison.” (Paracelsus) Requirements traceability is a concept related to requirements management which often provokes negative thoughts of complex tools,...

Business Requirements vs Functional Requirements? Who Cares?

What are business requirements? A common answer I get when asking for an example of a business requirement is a sentence like: “The system shall facilitate the automation of email to the customer.” Is that a business requirement? Well of course it must be. The...

TA DA! Beyond Requirements Excerpt

I’m excited to announce that the book I’ve been working on for the last three years is available! In celebration (and a little promotion), I thought I would share an excerpt. I chose the excerpt below because it discusses some helpful concepts for analysts, regardless...

I have requirements approval! … Now what?

You deserve a pat on the back! You made it through discovery, requirements preparation, requirements elicitation (and probably a lot of negotiation), and came out the other end with a pristine, beautifully prepared business requirements document (BRD). It is time to...

The iTunes Impact on Requirements Analysis

Originally posted on BA Times in February 2013. Once upon a time BAs were required to write long requirements documents that told an entire story. This story started with business requirements, functional and non-functional requirements, which fed detail design...

Why do we need detailed business requirements?

Eliciting business requirements is a critical skill for a business analyst. Although we hear the phrase business requirements over and over again by software vendors, by training companies, by business analysts of various industries, and by speakers in our IIBA...
Page 1 of 212

Pin It on Pinterest