> A task can have paramaters -- it means the same procedure
> can be applied in different situations, given that different
> data is supplied. Parameters, though internally stored as
> task attributes, are conceptually not part of the task.
>
I think that the parameters are part of the task because they model the
information that the task works on. I guess you are making an distinction
between parameters and inputs/outputs, but I don't understand what the
distinction is.
My "model" of tasks is that when I do something, there is info that I need to
accomplish the task, and there is info I might produce. All these info is
modeled using input and output parameters.
> An object can have parameters -- what does it mean for an
> object to have parameters? How would we describe the
> concept of object parameter to a designer? Is the meaning of
> parameters in objects different from that of tasks? What is
> the difference between object parameters and object attributes?
>
This is a tougher question because in my mind objects have attributes, not
parameters. To anwer the question (last part of the question), there are no
parameters, only attributes.
Pedro Szekely
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292
Phone: 310/822-1511, Fax: 310/823-6714
URL: http://www.isi.edu/isd/szekely.html