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> Hello All,<o:p></o:p> <o:p> </o:p> I have the following questions and/or concerns about the latest Scan Service Requirements document.  <o:p></o:p> “Network Scan Service use Cases and Requirements”  January 31, 2008.<o:p></o:p> <o:p> </o:p> Comments beyond typo and editing corrections<o:p></o:p> <o:p> </o:p> <ol style='margin-top:0in' start=1 type=1> <li class=MsoNormal style='mso-list:l1 level1 lfo1'>The current definition for the term “Scan Document” does not actually state is contains the scanned digital document itself.  It states that it contains the “Scan Document Information”.   <o:p></o:p></li> <ol style='margin-top:0in' start=1 type=a> <li class=MsoNormal style='mso-list:l1 level2 lfo1'>If this is true, then the term “Digital Document” definition becomes; “The digitized data of the Hardcopy Document.”<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level2 lfo1'>If this is true, then the term “Scan Document Data” definition becomes:“The digitized data of the Hardcopy Document.   This term is used interchangeable with Digital Document throughout this document.”<o:p></o:p></li> </ol> <li class=MsoNormal style='mso-list:l1 level1 lfo1'>The term “Template Manager Service” has contained in its definition the wording “ … the interfaces for creating, …maintaining” .    I need clarification of the terms “interfaces”, “creating” and “maintaining”.  Does the word “interfaces” mean the Application Programming Interfaces (APIs) or does it mean the user (gui/line-commands/etc) interfaces;  I believe it is means APIs but which is the intent?  The word creating has the same implication of a GUI or user-interface.   However, it may have meant “to create a new template”.  I would contend that the “Template Manager Service” would provide the services of store and retrieve only.  To create a new template, the Scan Client would get an existing template or the default template by a retrieve command to the  “Template Manager Service”; the user would modify the retrieve template; the Scan Client would then request the  “Template Manager Service” to store the modified template under a new name.   Thus, the  “Template Manager Service” only performs store and retrieve.   As for the word “maintaining”, what does this mean?  What is being “maintained”?<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level1 lfo1'>In the definition for “Scan Job Receipt”, is the lower-case word “element” meant to be the “XML term” “Element”.  If not, I would suggest changing the word “element” to remove ambiguity with the XML term “Element”.  Would the word “attribute” be better?   If the term “element” means “Element”, then it needs to be capitalized.<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level1 lfo1'>Should the term “Scan Service Discovery” be added to section 3.2 as term?<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level1 lfo1'>For Use Case 2:<o:p></o:p></li> <ol style='margin-top:0in' start=1 type=a> <li class=MsoNormal style='mso-list:l1 level2 lfo1'>I admit to being confused at this point.   I thought we were going to eliminate the first paragraph of the use-case.   I though this was going to be simple use-case of “Walk up Scanning using an existing Scan Job Template” and not “Walk up Scanning using a pre-defined Scan Job Template”.   Thus, if this is the former case, the first paragraph can be removed.   The discussion we had over the phone was that an IT-department would restrict the user by having a scan client that would not allow restricted fields to be set.<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level2 lfo1'>The word “boundaries” should be changed, since in scanning boundaries will imply the physical scanning area and not boundaries (in pages) between documents.<o:p></o:p></li> <li class=MsoNormal style='mso-list:l1 level2 lfo1'>This use-case has what I call “Implied Requirements” or “Inferred Requirements” that can not be directly identified by the use-case or the processing steps.  For example,  Design Req: 2.6 “Must Honor” is not even hinted at in the use-case or the processing steps but this does seem to be the use-case to include it. (We could expand the pervious use-case to discuss these kinds of details.)   What I would suggest and have done in my own work is to have a requirements section called “Implied Requirement” as a separate section of the design requirements.  These requirements that are not directly identifiable by the use-case but are “under the covers” or that “must be included” to make the use-case be functional.  Therefore I would like to suggest the following document modification<o:p></o:p></li> </ol> </ol> <o:p> </o:p> 6.2.2 Requirements<o:p></o:p> <o:p> </o:p>    6.2.2.1 Precondition Requirements<o:p></o:p>                Precondition Req: 2.1  The Scan Client SHALL use the Scan Service Directory requirements of section 6.7<o:p></o:p> <o:p> </o:p>    6.2.2.2 Design Requirements<o:p></o:p>                Design Req:  2.1 …………………….<o:p></o:p> <o:p> </o:p> <![if !supportLists]>6.2.2.3    <![endif]>Implied Requirements<o:p></o:p> Implied Req: 2.1 The Scan Service SHALL support a “Must Honor” ………………<o:p></o:p> <o:p> </o:p> More later…<o:p></o:p> <o:p> </o:p> Glen<o:p></o:p> <o:p> </o:p>  <o:p></o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>