agile

The State Machine Diagram

One of the challenges faced by requirements analysts is the need to communicate the complex behavior of systems in an understandable yet rigorous and verifiable way. A significant amount of the effort in the requirements process is devoted to translating the users’ needs and goals from ‘the language of the …

Read More

Fun with CRC cards

Use cases have become an indispensable tool for requirements elicitation and documentation. They have the advantage of being relatively easy to write and, if written well, they are relatively easy to read and understand. This advantage comes in part from the fact that they are created using ‘natural’ language text. …

Read More

Are your requirements smarter than a 5th grader?

There was a neat article in the July 13 Dr Dobbs Agile Modeling Newsletter. http://www.ddj.com/dept/architect/201001273 It basically argued that you could evaluate the quality of a document based on a set of criteria: C = The percentage of the document that is currently “correct”.R = Thechance that the document will …

Read More

Agile Development

Someone asked me the other day about agile development. Should we do it? Can we reduce the time we spend on requirements if we are doing agile development? Is it only good for some kinds of projects? If you’re reading this blog there is a good chance you know about …

Read More

Goal-Oriented Requirements

This thread is going to be about Goal Oriented techniques. There’s been some good academic work in this area — you could look up Goal-Oriented Requirements Engineering (GORE) — and some successes in practice. I’ve been following this area for about 10 years, and have used it for a few …

Read More

Agile… Again

Some people have pointed out that the reason I don’t like agile methods is because I am trying to sell services which depend on “traditional” requirements. The reason I like “traditional” requirements is because I don’t like screwed up projects. Everyone is trying to sell something and the Agile gurus …

Read More

Legacy Migrations

We recently finished a project fully documenting a very large existing system. The ecosystem was made of about 30 applications working together and was obviously very complex. This is not unusual in large organizations. The goal of the project was to understand enough about the existing requirements of the system …

Read More

Traditional software requirements don’t work?

Recently I have talked to a number of clients that have referred to the fact that traditional requirements don’t work. It didn’t take long to ferret out that they were referring to creating software requirements using a waterfall model. I want to state for the record that I completely agree …

Read More