Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  High Level Requirement - Testability ?
Previous Previous
Next Next
New Post 3/8/2012 9:45 AM
User is offline DBR
1 posts
No Ranking

High Level Requirement - Testability ? 

So, the basic requriement writing recommendation states that high level requirement shall be design independent. I have this requirement

"The system shall have the capability to compute XYZ ". Let's say XYZ = Speed.

The lower level decomposition states the necessary inputs, outputs, equations, etc. needed for the computation. Which can be easily verified.

However, I get into the issue of verifiying this High level requriement. How can we verify this requirement ?....Or is this is a bad requirement that needs modification, if yes, then how....but remember at a high level, the requriements needs to be design independent and only answer the "What?" the system does...not "How?" the system does it...

any help would be appreciated. 

New Post 3/8/2012 5:28 PM
User is offline David Wright
141 posts
7th Level Poster

Re: High Level Requirement - Testability ? 

 Where did you get that " basic requriement writing recommendation states that high level requirement shall be design independent"? Because, all requirements are design independent.

Defining the computation is also design-independent. We could say these days that the computation is a business rule, not a requirement, because it exists irrespective of your writing of requirements or eventual inclusion in a system.

But I digress, your question is about verification of a high-level requirement. If your SME or sponsor reads it and says "that is my requirement", then it has been verified. If you are asking about how to validate a requirement, that is different.

David Wright

David Wright
Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  High Level Requirement - Testability ?

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...



Copyright 2006-2022 by Modern Analyst Media LLC