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.
- Mission & Scope
- Goal Conflicts
- Agreed Priorities
- Acceptance Criteria
In my next post I will talk about improving the quality of written requirements.