Posted by: Neal Middlemore | March 25, 2011

10 Steps to Better Requirements

Requirements Engineering is not difficult but it is easy to get swamped by the information and this can lead to unclear sets of requirements which can lead to a whole lot of trouble down the line. Let’s face it, if a set of requirements could possibly be misinterpreted then you pretty much guarantee that it will be.

Ian Alexander is a well respected author of several books on requirements management and Ian recommends addressing the following 10 areas to achieve better requirements management. I have included just the headings to read the article for yourself please go to Ian’s site.

  1. Mission & Scope
  2. Stakeholders
  3. Goals
  4. Goal Conflicts
  5. Scenarios
  6. Shall-Statements
  7. Justifications
  8. Assumptions
  9. Agreed Priorities
  10. Acceptance Criteria

In my next post I will talk about improving the quality of written requirements.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: