From: Adriano Comai (comai@analisi-disegno.com)
Date: Sat Dec 14 2002 - 20:07:43 EST
Tere,
something in the words you use reminds me of the RUP (Rational Unified Process). Is this the case? If it is, there are some misconceptions.
In the RUP, there are different disciplines (you can call them processes):
- requirements - analysis and design - implementation - ...
"Managing Requirements with Use Cases" is, in the RUP, a part of the requirements discipline, not a part of "analysis and design". The other documents you refer to (architecture, both "logic" and deployment, db design, class model ecc.) are produced in the context of the "analysis and design" discipline.
Hope this helps.
Adriano Comai
www.analisi-disegno.com
> -----Messaggio originale-----
> Da: owner-re-online@it.uts.edu.au
> [mailto:owner-re-online@it.uts.edu.au]Per conto di Tere Ventura
> Inviato: venerdì 13 dicembre 2002 23.54
> A: 're-online@it.uts.edu.au'
> Oggetto: [re-online] Requirements & Design
>
>
> In our company, now we do a process called "Analysis & Design". This
> process do the analysis document (Requirement wiht Use Cases) and the
> Design document (Logic architecture, data base design, class model,
> deployment architecture). This documents are used for the coding process
> ("Development Process").
>
> We are trying to improvement some process, and we want have a process
> called "Requirements Engineering". The question is:
>
> ¿Design process is part of Requierement Design . Design = software
> requirements? ¿Design process is part of Development Process (logic
> part)? or ¿Design is other process?
>
> Thanks
>
> Tere Ventura
> University of Mexico
>
>
>
> ------------------------------------------------------------------
> -------------
> 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 : Fri Feb 21 2003 - 11:30:48 EST