Re: Use cases and visualization information

Responding to Santiago...

The application is a GIS (Geographic Information System). It Must be able to select the source of data and represent it graphically as an image, points, lines, etc, dependyng on the style of each feature.
Aslo the application must be able to show information in a stack layer, where each data is a layer. It must bring the user the possibility to move layers up/down, show/hide, etc.

The question is: what are requirements and what not? what are use cases and what not?
Are the options of move up/down a layer a requirement? a use case?

The short answer is Yes to all. The word 'must' is a pretty clear indicator of what the requirements are in your description. B-) The allowed interactions of the user are defined by requirements, so those interactions reflect the requirements in a use case organization.

I would suggest reading "Writing Effective Use Cases" by Cockburn.


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.

I don't know what you mean by this. Uses cases /are/ <a form of> requirements. IOW use cases are just one view of requirements rather than something to merge with <separate> requirements. In contrast, 'final utilities' sounds like something you are going to create in software. That would be a work product of implementation of the requirements, not a merger.

The ability of the user ot change colors would be a requirement because that is something the user needs to be able to do with the software. Whether the specific colors allowed or how they are coded to problem semantics may or may not be requirements. [They might simply be design decisions to make the product "look nice". However, if there is a formal GUI design that specifies them or they have intrinsic meaning in the problem context, then they are requirements.] 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.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
(888)OOA-PATH



.

Quantcast