Re: Use cases and visualization information
- From: "Rebecca Wirfs-Brock" <rebecca.wirfsbrock@xxxxxxxxx>
- Date: 25 Mar 2006 20:54:11 -0800
Antonio Santiago wrote:
Thanks a lot for the reply, it was very clarify for me.
Only one more thing, I made a mistake, I mean "confusing" instead
"merging" at:
I think I am merging requirements, use cases and final utilities for
the user (for example: change colors or properties) but I need some
light.
Anyway, the following sentence is a good answer for me.
Anything that the
user does with the application would be described in a use case, which
simply orders the required functionalities the user accesses into a
usage context.
Thanks.
--
-----------------------------------------------------
Antonio Santiago Pérez
( email: santiago<<at>>grahi.upc.edu )
( www: http://www.grahi.upc.edu/santiago )
( www: http://asantiago.blogsite.org )
-----------------------------------------------------
GRAHI - Grup de Recerca Aplicada en Hidrometeorologia
Universitat Politècnica de Catalunya
-----------------------------------------------------
.
- References:
- Use cases and visualization information
- From: Antonio Santiago
- Re: Use cases and visualization information
- From: H. S. Lahman
- Re: Use cases and visualization information
- From: Antonio Santiago
- Use cases and visualization information
- Prev by Date: Re: Tools for drawing simple object/pattern diagrams?
- Next by Date: Re: Use cases and visualization information
- Previous by thread: Re: Use cases and visualization information
- Next by thread: Re: Use cases and visualization information
- Index(es):