Running head: Lab 3 – LASI Prototype Test Plan and Procedures
Lab 3 – LASI Prototype Test Plan and Procedures
Red Team
Brittany Johnson
CS411W
Janet Brunelle
April 17, 2013
Version 1
1
Lab 3 – LASI Prototype Test Plan and Procedures 2
Table of Contents
1.
2.
3.
Objectives ................................................................................................................... 3
References ................................................................................................................... 4
Test Plan...................................................................................................................... 4
3.1
Testing Approach ................................................................................................ 4
3.2
Identification of Tests ......................................................................................... 6
3.3
Test Schedule ...................................................................................................... 8
3.4
Fault Reporting and Data Recording .................................................................. 8
3.5
Resource Requirements ...................................................................................... 8
3.6
Test Environment ................................................................................................ 9
3.7
Test Responsibilities ........................................................................................... 9
4. Test Procedures ........................................................................................................... 9
4.1
Test Case Names and Identifiers......................................................................... 9
5. Traceability to Requirements ...................................................................................... 9
List of Figures
Figure 1. Prototype Major Functional Component Diagram .......................................................... 5
List of Tables
Table 1. Identification of Tests ....................................................................................................... 7
Table 2. LASI Prototype Test Schedule ......................................................................................... 8
Lab 3 – LASI Prototype Test Plan and Procedures 3
1. Objectives
LASI stands for Linguistic Analysis for Subject Identification. It is a stand-alone theme
finding application conceived by the Old Dominion University CS410 Red Group. It is designed
to be a decision support tool for large, multi-document linguistic analysis and allow for more
accurate and consistent results. LASI will be able to detect themes across many documents and
can provide both individual and cross document analysis to determine a single theme.
Linguistic Analysis is the contextual study of written works and how the words combine
to form and overall meaning. Themes are the subject-object-verb relationships that help the
reader to comprehend and summarize what has been read. LASI will be a decision support tool
to assist users in determining common themes across multiple documents. It is even more
difficult to come to a conclusion when the number of documents increases because the theme
across all of the documents may not be the theme of each of the individual documents. The
complexity of a topic and the reader’s familiarity with it plays an important role in
comprehension. The reader’s comprehension, along with the ability to summarize the material is
important in being able to communicate the content of a document. Thus, it is often difficult for
people to identify a common theme over a large set of documents in a timely, consistent, and
objective manner.
The purpose of this Test Plan and Procedure is to establish the overall approach, testing
sequence, and specific tests to be conducted to demonstrate successful operation of the LASI
prototype. The two primary objectives in conducting these tests are to validate the functionality
of the LASI prototype and demonstrate a proof of concept. These objectives will be shown
through the test cases provided in this document.
Lab 3 – LASI Prototype Test Plan and Procedures 4
2. References
Johnson, Brittany. (2013). Lab 1 – LASI Product Description. Old Dominion University.
Department of Computer Science.
Johnson, Brittany (2013). Lab 2 – LASI Prototype Product Specification. Old Dominion
University. Department of Computer Science.
3. Test Plan
The following sections of the test plan will discuss the types of tests to be performed, the
testing schedule, reporting procedures, resource requirements, the testing environment, and team
member responsibilities.
3.1
Testing Approach
Performance of the LASI prototype will be verified through a combination of component
and system tests. The major functional components of the prototype are shown in Figure 1.
[This space intentionally left blank.]
Lab 3 – LASI Prototype Test Plan and Procedures 5
Graphic User Interface
File Management
Start-up Screen
Create Project
File Converter
Create Project View
Documents Returned
Project Preview
Begin Analysis
Part-of-Speech
Tagger
In Progress View
Results View
Algorithm
Results Aggregator
Word &Phrase Binder
Individual Documents
Subject
All Documents
Tagged
File Parser
Object
Attributive
Figure 1. Prototype Major Functional Component Diagram
The system tests will exercise multiple components concurrently, removing the need to perform
separate tests on every component independently. All data being used in the testing of the LASI
prototype will all be real. As the test user progresses through the user interface tests the related
system tests will be showed. The first category will cover the functionality of the LASI user
interface. These tests will demonstrate that the user is able to create a new project, preview the
documents and then view the final results after analysis. The second test category will cover the
file management system, making sure that the program is able to load and convert documents
correctly from DOC, DOCX format to plaintext and TAGGED. The third test category deals
with the Tagged File Parser reading TAGGED files correctly and the text to their correct Word
and Phrase types. The fourth test category deals with word associations and correctly binding
direct and indirect objects to a verb. The last test category deals with the weighting algorithm
Lab 3 – LASI Prototype Test Plan and Procedures 6
and how individual words and phrases need to be weighted. All tests will be conducted in a
controlled environment. Verification of user interface tests will be completed through
observation.
3.2
Identification of Tests
Table 1 shows the test cases that will be performed, grouped by category. Specific details
for each test will be discussed in section 4.1.
[This space intentionally left blank.]
Lab 3 – LASI Prototype Test Plan and Procedures 7
Category ID
1
2
3
4
Category
User Interface
Test Case
1.1
Name
Description
New Project
Verify that the user has the ability to create a new project.
1.2
Load Project
1.3
File Type
1.4
Document Limit
Verify that the user has the ability to load a project
Verify that DOC, DOCX, and TXT are the only file type that can be
added to the project.
Only 5 documents may be added to a single project.
Documents added to the project will be displayed in a document queue
and documents can be removed from the document queue.
Verify that all fields must be completed to create a new project.
Verify that when a project is created the user will be navigated to the
loaded project page and the documents are displayed.
Verify that the user can add documents to the project once it is created.
Project is still limited to 5 documents at any time.
Verify that the user can remove documents from the project once it is
created. Project is still limited to 1 document to start analysis.
Verify that the Processing Screen displays a visual indication of
progress and that user has the ability to cancel analysis.
Verify that the Results Screen displays the results in multiple views.
Verify that the top results view provides a visual summary of the
analysis in both the individual and collective document scopes.
Verify that the top results view provides the user with the ability to
change the graphical view of the top results.
1.5
Document Queue
1.6
Field Verification
1.7
Document Display
1.8
Adding Documents
1.9
Removing Documents
1.10
Canceling Analysis
1.11
Results Screen
1.12
Top Results View
1.13
Top Results Graph
1.14
Word Relationships View
1.15
Word Count & Weighting View
1.16
2.1
2.2
2.3
Export Results
Input File Path Verification
Conversion of .DOC to .DOCX
Conversion of .DOCX to TXT
2.4
Converting .TXT to .TAGGED
2.5
Backups to Project Directory
3.1
Accepted Formats
3.2
Tagged File Parser at Word Level
3.3
Tagged File Parser at Phrase
Level
4.1
Subject Binder Test
4.2
Object Binder Test
4.3
Object Binder Fail test
4.4
4.5
5.1
5.2
5.3
5.4
5.5
Thesaurus Test
Adverb Binder Test
Word Weight - Instantiation
Phrase Weight - Instantiation
Word Weight - Duplicates
Synonyms
Word Associations
Word weight increase on phrase
association.
Phrase weight increase on word
association.
Phrase weight increase on phrase
association.
File Manager
Tagged File
Parser
Word Association
5.6
5.7
5.8
5
Weighting
5.9
Common word weight exclusion
5.10
Distance as weight modifier
5.11
Word weight for individual
document.
Word weight for project.
Phrase weight for individual
document.
Phrase weight for project.
Aggregate weight
5.12
5.13
5.14
5.15
Verify that the Word Relationships View displays visuals to show all
relationships and bindings of words.
Verify that the Word Count and Weighting view is presented with the
quantitative data used in the analysis
Verify that the user is able to export results.
The File Manager shall only accepts existent files in supported formats
The file manager must be able to convert a DOC file to DOCX.
The file manager must be able to convert a DOCX file to TXT file.
The File Manager shall invoke the SharpNLP tagger to process each
TXT file.
The file manager shall provide functionality to backup up the entire
project directory.
The Tagged File Parser will only attempt to parse the contents of a
.TAGGED file.
The Tagged File Parser shall only attempt to parse the contents of a
.TAGGED file.
The Tagged File Parser shall only attempt to parse the contents of a
.TAGGED file.
The Subject binder determines which noun phrases are the subjects of
verb phrases.
The Object binder determines which noun phrases are the direct
objects and indirect objects of verb phrases
The Object binder test makes sure that sentences not containing a
direct or indirect object are not bound as having one.
The Thesaurus correctly identifies synonyms.
Adverb binder binds adverb phrases to the adjective/verb modified
A test for the initial equivalent weights of each Word.
A test for the initial equivalent weights of each Phrase.
A test for weighting multiple instances of the same Word.
A test for weighting Synonyms of the same Word.
Test for incrementing the weight of a Word for each association.
The weight of a word shall be increased when a phrase is associated
with it.
The weight of a phrase shall be increased when a word is associated
with it.
The weight of a phrase shall be increased when another phrase is
associated with it.
The weights of commonly used words such as “the”, “a”, “to”, etc.
shall be excluded.
The distance between words and phrases shall be used as a weight
modifier.
Each word shall store its weight in respect to the document containing
it.
Each word shall store its weight in respect to all the documents.
Each phrase shall store its weight in respect to the individual document
containing it.
Each phrase shall store its weight in respect to all the documents.
There shall be an aggregate weight computed across all documents.
Table 1. Identification of Tests
Lab 3 – LASI Prototype Test Plan and Procedures 8
3.3
Test Schedule
The LASI team has been allotted 60 minutes for the setup and demonstration of the
prototype. The first five minutes will be used for setup, followed by a 10 minute introduction to
the concept of LASI. After the introduction, the test cases will be executed according to the
schedule shown in Table 2.
Start Time
(hours:min)
0:15
0:25
0:30
0:35
0:50
Duration
(Minutes)
10
5
5
15
10
Test Objective
Test Event
Dependencies
Comments
User Interface
File Manager
Tagged File Parser
Word Association
Weighting
1.1, 1.3-1.16
2.1-2.5
3.1-3.3
4.1-4.5
5.1-5.15
None
None
None
None
None
None
None
None
None
None
Table 2. LASI Prototype Test Schedule
3.4
Fault Reporting and Data Recording
Each test case is written in the unit-test template. One team member will be tasked with
recording the results of each test on a printed checklist. Functional test results will be recorded as
passing or failing. Verification of user interface tests will be completed by observing the
response of the system.
3.5
Resource Requirements
The LASI prototype demonstration will require that laptop being used to present have at
least 8.0 GB of RAM, a Quad-Core CPU and be running Windows 64-bit Operating System. The
laptop used in the demonstration must have Microsoft Visual Studios installed. At most five
documents need to be ready to be used as test data to submit for analysis. At least one of the
documents needs to be analyzed by hand to show for comparison. The test user needs to have the
LASI program running from Visual Studios to show both the user interface as well as the
underlying algorithms of the LASI prototype.
Lab 3 – LASI Prototype Test Plan and Procedures 9
3.6
Test Environment
The prototype will be demonstrated in the first floor presentation room of the Dragas
building. The laptop will be at the front of the room hooked up to a projector for everyone to see.
3.7
Test Responsibilities
Each group member will have some test responsibility for the prototype presentation
though that is yet to be decided. One group member will be responsible for operating the laptop
used for the presentation. One group member will introduce the LASI prototype. One group
member will record the results for each test. Each team member will present a category of test
cases.
4. Test Procedures
Detailed test procedures have been prepared to ensure that the test cases can be performed in an
effective and efficient manner.
4.1
Test Case Names and Identifiers
Test case table has been printed separately.
5. Traceability to Requirements
Traceability matrix has been printed separately.