Hi Bill and Mike,
I also agree on all points.
The ultimately broad scenario (one for all Print) doesn't really
work well, IMHO.
On Jun 20, 2011 at 2:38 AM, Michael Sweet <msweet at apple.com> wrote:
> On Jun 15, 2011, at 12:22 PM, William Wagner wrote:
>> **... **
> In short, I suggest:****
> 1. Our terminology be not inconsistent with typical design terminology
> 2. We define our approach and terminology in the “Best Practices”
> 3. We be consistent in terminology and level within the “Best
> Practices” document and among the various projects (It would be very
> confusing to have a Use Case in one document become a Scenario in another.)
> 4. We not lose the “story” aspect and the sequence of what the user
> does and what the “system” must do… Joe is on vacation at Yellowstone and
> needs to print out the map to a lost gold mine in Wyoming that his friend in
> New York City just found. Perhaps the story is farfetched, but it includes
> many aspects of the general problem that must be considered.****
>>> I agree on all points.
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> cloud mailing list
>cloud at pwg.org>https://www.pwg.org/mailman/listinfo/cloud>>
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...