use case <<include>> vs. <<generalize>>

Hi I would like to have your opinion about the following:

I design the use case "Process File".

There are 3 situations of processing the file:
- scan and process
- browse and process
- get mail attachment and process.

What is the best way to describe it in use case model?:

- Use case "Process", in the uc, script with 3 options?
or
- Three use cases: "scan file" "browse" "mail" with <<include>>
relation to 4th use case "Process"?
or
- One use case "Process", with <<generalize>> relation to the 3 use
cases "scan","browse","mail"?

Thank you.

.

Relevant Pages

  • Stonemasons and Coders
    ... >>I would disagree with that opinion. ... It is one thing for a journeyman stonemanson to ... > You are confusing ancient stonemasons with modern programmers and all ... adjust the design of the structure to compensate ...
    (comp.programming)
  • Re: Hyperlinks
    ... http://www.snipesfamily.net/index_files/DAVE.htm The issue is that Publisher ... the design checker tool will find some of these issues. ... I am betting that you are using a script on your home page that you are not ... I have seen a lot of Publisher produced sites that load ...
    (microsoft.public.publisher.webdesign)
  • Re: notice and warning
    ... You expect some piece of data from a post in your script, ... prefer $_REQUEST over $_POST. ... the different meanings the input should have based on how it arrives. ... that's bad design. ...
    (comp.lang.php)
  • Re: WISDOM of Crowds (Iden?ify -Uare the missing data)
    ... "You don't do good software design by committee." ... Aggregation. ... designing something would be for the group's opinion to be aggregated ... Collective Wisdom Shapes Business, Economies, Societies and Nations ...
    (sci.logic)
  • Re: Id like a better understanding of the debate
    ... the creation of a test of design would be extremly ... Who says anyone has to satisfy your opinion about this issue? ... problem in science. ... this seems to be the perception on ID: that ID is religion. ...
    (talk.origins)