requirements Appendix F: Test Case Results – Document Analyzer Detailed Procedure Steps Expected Actual Results (Chrome) Actual Results Step Description Results/Method of Step # (Firefox) Recording Uploading Documents The uploaded For large DOCX as Overall: With minimal use using the Automated documents are well as PDF of the User Guide, the tool parser expected to be samples (example, is fairly intuitive about how .Make sure you have a broken-down into a 600 KB docx file to import a document. The DOCX and a PDF file on separate with 24 pages, or “Import” button was easy your local computer paragraphs, with a 2000KB PDF file to find on the DB view. ready to upload Names and with 300 pages), Once in the import portion .From Database View, relationships the upload of the tool, it’s easy to click on the drop-down created based on progress bar runs upload the document. It is next to the the documents’ indefinitely, not unclear as to what class a “Import” menu Titles and completing even user should select for their .Choose “Analyzer” Numbering Schemes after 30 minutes. document. Other fields .Click on “Upload If user goes back used to label the imported Document” (Right to the Database document seem DA-001 Panel) view while the straightforward. .Select the document to upload bar is still Tool seems to get hung upload(either the PDF pending, it turns when saving uploaded or the DOCX file) out that the document. .When prompted document has in PDF: Imported the MEEPAS “Would you like to fact been Project Report using a PDF Auto parse this uploaded, which and labeled it under the Document using indicates that the class “Statement”. Once Analyzer?”, choose a issue is with the uploaded, the analyzer did Starting Number Upload Progress not import the entire (example 1.0) and click bar’s design. document. It only imported YES three parts of the .Once uploading document and seems to completes, list of the parse those parts randomly. created entities shows. Innoslate does store the
requirements Appendix F: Test Case Results – Document Analyzer Detailed Procedure Steps Step # Step Description Expected Results/Method of Recording Actual Results (Firefox) Actual Results (Chrome) DA-001 Uploading Documents using the Automated parser .Make sure you have a DOCX and a PDF file on your local computer ready to upload .From Database View, click on the drop-down next to the “Import” menu .Choose “Analyzer” .Click on “Upload Document” (Right Panel) .Select the document to upload(either the PDF or the DOCX file) .When prompted “Would you like to Auto parse this Document using Analyzer?”, choose a Starting Number (example 1.0) and click YES .Once uploading completes, list of the created entities shows. The uploaded documents are expected to be broken-down into separate paragraphs, with Names and relationships created based on the documents’ Titles and Numbering Schemes For large DOCX as well as PDF samples (example, a 600 KB docx file with 24 pages, or a 2000KB PDF file with 300 pages), the upload progress bar runs indefinitely, not completing even after 30 minutes. If user goes back to the Database view while the upload bar is still pending, it turns out that the document has in fact been uploaded, which indicates that the issue is with the Upload Progress bar’s design. Overall: With minimal use of the User Guide, the tool is fairly intuitive about how to import a document. The “Import” button was easy to find on the DB view. Once in the import portion of the tool, it’s easy to upload the document. It is unclear as to what class a user should select for their document. Other fields used to label the imported document seem straightforward. Tool seems to get hung when saving uploaded document. PDF: Imported the MEEPAS Project Report using a PDF and labeled it under the class “Statement”. Once uploaded, the analyzer did not import the entire document. It only imported three parts of the document and seems to parse those parts randomly. Innoslate does store the
SYST699_SPEC_Innovations_Final_Report_11Dec2012.docx