From: Didar Zowghi (didar@it.uts.edu.au)
Date: Wed May 22 2002 - 22:59:28 EST
Mohamed
This was one of the first discussions we had on the good old SRE mailing
list in 1995. I used to archive all the discussions in my less busy days :-)
May I suggest you read it and see if it helps answer your question. You can
find it in:
ftp://ftp.mpce.mq.edu.au/jrcase/sre-archive/design-vs-req
Cheers
Didar
> Hi every one
>
> As I understand, the tradtional definition of requirements engineering
> is to document "what" the system should do based on the customer needs
> rather than how it should do it. Well, I noticed recently that some
> people that I met in person and some papers also say that this is an
> old definition and the real world makes us put things about the "how"
> which is neglected in the original definition. I would like to open
> this issue for discussion and see what other people have to say abou
> it...........
>
> Best regards
> *******************************************************
> Mohamed Sami Shehata
> Ph.D. Student
> University of Calgary
> 2500 University Drive N.W. Calgary, Alberta, Canada, T2N 1N4
> Tel: +(403)210-5478 (W)
> +(403)202-9161 (H)
> http://www.enel.ucalgary.ca/~shehata
> *************************************************
>
>
> --------------------------------------------------------------------------
This archive was generated by hypermail 2.1.6 : Fri Feb 21 2003 - 11:30:39 EST