From: Adriano Comai (comai@analisi-disegno.com)
Date: Mon Dec 23 2002 - 03:55:24 EST
Donald, all
> I imagine that it is more complex, the more complex the
> requirements process
> is, and less complex, the simpler the contractual relationship is between
> the customer and development organization.
do you think the customer and the supplier, at the beginning of every project, need to agree upon a specific requirements life cycle?
(I don't refer to the state model here, but to the business rules that govern the transitions between states).
and that, if applicable, this life cycle (these business rules) have to be specified in the contract?
Adriano Comai
http://www.analisi-disegno.com
> -----Messaggio originale-----
> Da: Donald Firesmith [mailto:donald_firesmith@hotmail.com]
> Inviato: sabato 21 dicembre 2002 14.25
> A: comai@analisi-disegno.com; re-online@it.uts.edu.au
> Oggetto: Re: R: [re-online] Lifecycle of requirements
>
>
> Adriano Comai,
> The requirements life cycle is my own, not anything officially OPEN, at
> least not yet. It probably would not hurt to write it up, draw a state
> transition diagram, and make it more formal. Part of it seems relatively
> obvious, although that just may be because I came up with it in
> response to
> your question.
>
> I imagine that it is more complex, the more complex the
> requirements process
> is, and less complex, the simpler the contractual relationship is between
> the customer and development organization.
> I do feel that it should be driven by the requirements engineering tasks
> that are performed and these are fairly standardized.
>
> I will work on a STD and send it to the group for comment.
>
> Donald Firesmith
> Firesmith Consulting
> Affordable Consulting and Training in:
> - Process Engineering
> - Requirements Engineering
> - System and Software Architecture
> - Object-Oriented Design
> - Object-Oriented Testing
> http://www.donald-firesmith.com
This archive was generated by hypermail 2.1.6 : Fri Feb 21 2003 - 11:30:49 EST