attachment

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> < text > means remove text<o:p></o:p> [ text ] means include or add text<o:p></o:p> <o:p> </o:p> { message } means request or action<o:p></o:p> <o:p> </o:p> ( text ) means a question from me or I need clarification <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Line 225:<o:p></o:p> … other MFD functions [including a different scan job].<o:p></o:p> <o:p> </o:p> Line 237 … Physical Scan Job Ticket<o:p></o:p> {change} object {to} hardcopy<o:p></o:p> <o:p> </o:p> Line 237 … Physical Scan Job Template<o:p></o:p> {change} object {to} hardcopy<o:p></o:p> <o:p> </o:p> Line 237 … Scan Job <o:p></o:p> (how does this differ from Scan Document)<o:p></o:p> <o:p> </o:p> Line 237 … Scan Service (at last line of the definition)<o:p></o:p> … locally or remotely [to the MFD].<o:p></o:p> <o:p> </o:p> Line 237 … Scan Mailbox<o:p></o:p> (Isn’t scan to a mailbox out of scope?)<o:p></o:p> <o:p> </o:p> Line 237 … (new definition)<o:p></o:p> [Configured Scan Job Template   object   A Scan Job Template that has been modified (configured) to represent the end user Scan Intent.]<o:p></o:p> <o:p> </o:p> Line 237 … Scan Document Data<o:p></o:p> (Is there any real difference between Scan Document and Scan Document Data as defined?)<o:p></o:p> <o:p> </o:p> Line 237 … Scan Client (at last part of the definition)<o:p></o:p> ….with the end user [, Template Management Service, scan repository,] and a Scan Service.<o:p></o:p> <o:p> </o:p> Line 237 … Local Client <o:p></o:p> … Local Scan client [through out] <with> this document.<o:p></o:p> <o:p> </o:p> Figure 1 – Last Arrow (10b)<o:p></o:p> (10b) Store template [remotely] (if storage…..<o:p></o:p> <o:p> </o:p> Line 247 to line 249<o:p></o:p> … <Since Web Service ……………….. (to the end of line 249><o:p></o:p> <o:p> </o:p> Line 276<o:p></o:p> 6.1.1 Processing Flow <Requirements><o:p></o:p> <o:p> </o:p> Line 282 <o:p></o:p> … Scan Service <(scanner)>, the …<o:p></o:p> <o:p> </o:p> Line 283<o:p></o:p> … for each element [of the Scan Service].<o:p></o:p> <o:p> </o:p> Line 285<o:p></o:p> (Is the word “attributes” correct or should it be “elements” or  should it be “attributes and elements”?)<o:p></o:p> <o:p> </o:p> Line 287<o:p></o:p> … of the [C]<c>onfigured Scan …<o:p></o:p> <o:p> </o:p> Line 289 <o:p></o:p> … store the [C]<c>onfigured Scan …<o:p></o:p> <o:p> </o:p> Line 291<o:p></o:p> … validates the [Configured] Scan … ensure the [template]<temlate> is….<o:p></o:p> <o:p> </o:p> Line 292 <o:p></o:p> … … Scan Job Template [in the specified Template Repository]<at the repository> (local…<o:p></o:p> <o:p> </o:p> Line 294<o:p></o:p> ... that their [Configured] Scan Job Template….<o:p></o:p> <o:p> </o:p> Line 295<o:p></o:p> … remote Scan Client [application].<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Ended at the bottom of page 14<o:p></o:p> <o:p> </o:p> <o:p> </o:p> (Requirement section:  I had the understanding that a requirement statement must only state a single requirement.  That is there can not be an “and” unless it is a condition on a single requirement.   Therefore, the following suggestions separate the compound requirement statements into individual (testable) requirement statements.)<o:p></o:p> <o:p> </o:p> Line2 301 to list 314 become<o:p></o:p> <o:p> </o:p> Design Req 1.1  A Scan Service SHALL response to a “create new template” request from a Scan Client.<o:p></o:p> Design Req 1.2  A Scan Service, in response to a “create new template” request from a Scan Client, SHALL provide data elements that, at a minimum, are included in the default Scan Job Ticket.<o:p></o:p> Design Req 1.3  Data elements provided by a Scan Service SHALL contain the default values of descriptive and processing elements of a Scan Job Ticket.<o:p></o:p> Design Req 1.4  Data elements provided by a Scan Service SHALL contain the capabilities supported by the Scan Service.<o:p></o:p> Design Req 1.5  A Scan Client SHOULD validate that a Configured Scan Job Template is well formed.<o:p></o:p> Design Req 1.6  A Scan Client SHOULD validate that a Configured Scan Job Template has element values with the specified range of the elements.<o:p></o:p> Design Req 1.7  A Template Manager Service SHALL validate that a received new, modified or Configured Scan Job Template is well formed.<o:p></o:p> Design Req 1.8  A Template Manager Service SHALL validate that a received new, modified or Configured Scan Job Template has element values with the specified range of the elements.<o:p></o:p> Design Req 1.9  A Template Manager Service SHALL support storage of new, modified or Configured Scan Job Template for a specified Scan Client.<o:p></o:p> Design Req 1.10 A Template Manager Service SHALL support storage of new, modified or Configured Scan Job Template for a specified end user.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>