Re: [re-online] Why are we requirements engineers?

From: Andrew Gabb (agabb@tpgi.com.au)
Date: Fri Dec 12 2003 - 08:54:36 EST


Keith.Collyer@telelogic.com wrote:
> Why are we requirements engineers? By that (and applying good RE principles
> and removing ambiguity), I don't mean why are requirements engineers useful,
> but why did the people on the list choose to go into the field?

Good question, Keith.

I started as a scientist/software type firefighting performance problems in AusDoD systems (on the customer side). I got very frustrated with the state of these systems and went looking for the source of the fire. (T&E folks to this all the time.)

My path was as follows: 

In-service problems
In-project T&E deficiciencies of various types
In-project V&V so we knew more about the development (and could
predict and change it where appropriate). Contract problems, particularly the specifications. Solicitation problems
Customer requirements problems
Customer capability problems

Understandably, I found most of the sources of the fire in the last two - been there ever since. Of course, I've also had relatively brief visits to the others, because it's essential to experience the pain that poor requirements cause.

Andrew 

-- 
Andrew Gabb
email: agabb@tpgi.com.au       Adelaide, South Australia
phone: +61 8 8342-1021, fax: +61 8 8269-3280
-----

-------------------------------------------------------------------------------
To send a message to this mailing list send it to re-online@it.uts.edu.au.
To unsubscribe from this mailing list, email majordomo@it.uts.edu.au with the
message `unsubscribe re-online' in the BODY of the mail.

This archive was generated by hypermail 2.1.6 : Tue Dec 16 2003 - 12:20:51 EST