Lab 3 v.2 - Prototype Test Plan/Procedure
CS411W
Patrick Bourque
RED AI
4/16/2008
ii
Table of Contents
Table of Contents ............................................................................................................................ 2
Table of Figures .............................................................................................................................. 2
Table of Tables ............................................................................................................................... 2
1
Objectives ............................................................................................................................... 1
2
References ............................................................................................................................... 2
3
Test Plan.................................................................................................................................. 2
3.1 Testing Approach .......................................................................................................... 3
3.2 Identification of Tests ................................................................................................... 4
3.3 Test Schedule ................................................................................................................ 7
3.4 Fault Reporting and Data Recording ............................................................................ 7
3.5 Resource Requirements ................................................................................................ 7
3.6 Test Environment .......................................................................................................... 9
3.7 Testing Responsibilities .............................................................................................. 10
4
Test Procedures ..................................................................................................................... 10
5
Traceability to Requirements ................................................................................................ 16
Table of Figures
Figure 1: RED AI MFCD ............................................................................................................... 3
Figure 2: E&CS Room .................................................................................................................... 9
Table of Tables
Table 1: Functional Categories & Test Category 1 ........................................................................ 5
Table 2: Test Categories 2 – 5 ........................................................................................................ 6
Table 3: RED AI Script................................................................................................................... 8
Table 4: Test Cases 1.1.1 – 1.1.6 .................................................................................................. 11
Table 5: Test Cases 1.2.1 – 1.3.2 .................................................................................................. 12
Table 6: Test Cases 1.3.3 – 3.1 ..................................................................................................... 13
Table 7: Test Cases 3.2 – 3.7 ........................................................................................................ 14
Table 8: Test Cases 3.8 – 4.2. ....................................................................................................... 15
Table 9: Test Cases 4.2.2 – 5.1 ..................................................................................................... 16
Table 10: Traceability Matrix ....................................................................................................... 17
ii
Lab 3 v.2 – Test Plan / Procedure
RED AI
1 Objectives
On the 9th day of the 9th month of the year 2007, five intrepid Computer Scientists joined
efforts under the direction of then Computer Productivity Initiative CEO Janet Brunelle at Old
Dominion University in Norfolk, VA to bring into this world the system that would come to be
known as RED AI. The first of its kind Restaurant Efficiency Decision Artificial Intelligence,
RED AI is an Expert System designed to model an operational restaurant, analyze key profit
factors, and provide managers and owners with suggestions to positively affect profit. Through
the use of a graphical, intuitive user interface, owners, managers, and employees will provide the
system with all necessary manner of raw restaurant data. A relational database will store this
data for future analysis by state-of-the-art software Efficiency Engines. Efficiency Engines will
draw data from the database and perform calculations according to rules in the included
knowledge-based rule sets. Each rule will reflect some concept of restaurant efficiency and,
based on the current state of the restaurant model in the database, will give RED AI the ability to
offer meaningful suggestions to restauranteurs. For the purpose of preview, a prototype capable
of demonstrating the potential claimed by the RED AI development team was prescribed in
March 2008 by way of the Product Specification document. At the cause of requirements
imposed from the Product Specification, this document seeks to encapsulate the breadth and
depth of testing a program must endure to prove worthy of status as a RED AI product prototype.
Thirty-three test cases in five categories have been identified as the minimum set of tests
a program must pass to be termed a RED AI product prototype. The five categories are Setup,
Access, Data Taking, Efficiency Engine, and Performance Optimization. The Setup category
includes tests to ensure the login process, general look and feel, and some administrative
functions are available. The Access category ensures that each access level has appropriate
-1-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
authority using the system. The Data Taking tests deal with the programs various methods of
input, as well as ensuring data integrity and the ability to edit any erroneous data that may have
been entered. The Efficiency Engine tests ensure the expert algorithms are correctly understood
by the system and the suggestions they generate are presented appropriately. Performance
Optimization tests will be conducted to ensure the the various proceses of the prototype complete
in a timely manner.
2 References
Mullis, S. (2006, October 30). Running a Restaurant: Start up costs. Retrieved January 30, 2008,
from AllExperts: http://en.allexperts.com/q/Running-Restaurant-2285/Start-costs.htm.
RED AI. (2008). Lab 1.1 - Product Description. Norfolk: ODU CS - CPI.
RED AI. (2008). Lab 2.1 - Product Specification. Norfolk: ODU CS - CPI.
RED AI. (2007). Feasibility Presentation. Norfolk: ODU CS – CPI.
3 Test Plan
The RED AI prototype demonstration will showcase the achievement of “passing” status’
for a comprehensive subset of identified test cases. The prototype major functional component
diagram (MFCD), shown in Figure 1, will act as the frame of reference to the various program
modules which comprise the prototype. A demo-centric approach will be taken in selecting and
organizing test cases to allow a clear and concise concurrence by the expert review panel during
demonstration. The demonstration script and development team responsibilities will be
designed, and necessary resources and environmental requirements will be identified.
-2-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
3.1 Testing Approach
The RED AI prototype consists of three main modules. First, the graphical user interface
(GUI) will act as the sole user interface to the system during demonstration. The GUI will
contain features allowing users to add and edit database data. The efficiency engines will be
managed from the GUI, and program settings can be controlled as well. The database will
contain the “restaurant model” as described in the first section of this document. Its contents will
be available to both the GUI and the Efficiency Engines. The Efficiency Engines will each have
an associated rule set which, when applied to the data, will produce efficiency suggestions. The
complete requirements for each of these modules are given in RED AI Lab 2 – Product
Specification.
To facilitate prototype demonstration, tests to satisfy the requirements given in Lab 2 will
be categorized and grouped into sets based on the order in which their completions would be
encountered during a natural demonstration of the prototype. A natural demonstration of the
RED AI prototype would proceed through five distinct phases, or functional categories.
Figure 1: RED AI MFCD
-3-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
First among functional categories is system setup. This category will include tests which
address program installation and startup. Tests for blank database initialization and user account
assignment will be found here, as well. Second, access control will be tested. For a given user
type, certain program features will be enabled or restricted. Third, the demonstration will test the
ability to enter and edit data in the database. Fourth, the efficiency engine process and output
functionality will be tested. Performance and time test review will make up the fifth test
category.
Another purpose of prototype testing is risk mitigation. The RED AI development team
identified some potential risks during feasibility and marketing studies in the Fall of 2007.
Among these were concerns over the usual quality of manual input and the ability of the
development team to produce reliable restaurant efficiency rules with associated suggestions.
The impact of each of these can be assessed and addressed as the prototype goes through its
testing phase. At the very least, the lowest level input interfaces must be utterly simple and selfexplanatory. Offering simple and quick data entry will help forestall the onset of apathy. In
passing all efficiency engine and performance tests, the prototype will be able to serve as a
testbed for the research and refining of efficiency rules. A fully-functional efficiency engine will
allow effective Phase II collaboration with restaurant experts and the validation of necessary
rules.
3.2 Identification of Tests
With the functional categories described in section 3.1 come the test sets which conspire
to satisfy the functional requirements of the RED AI Lab 2 Requirements Checklist. Tables 1
and 2 delineate the categorical hierarchy of test cases and their respective traceability to specific
requirements. Specific test case procedures are given in section 4 of this document.
-4-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Functional Categories
Category Number Category Name
1 Setup
2 Access
3 Taking Data
4 Efficiency Engine
5 Performance
Set Number
1.1
1.2
1.3
1. Setup
Set Name
Setup
Set up users
Manage rules
Description:
Case Number
1.1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1 Setup
Tests initial setup of program
Name
Verify login
Verify login screen objects
Bad login
Good login
Verify look and feel
Swap to Blank
Traceability
R14
R14
R15, R16
R15, R17
R19
R13, R26
Description:
Case Number
1.2.1
1.2.2
1.2.3
1.2.4
1.2 Set up users
Tests adding users to RED AI
Name
Add an admin type
Add a manager type
Add a front end type
Add a back end type
Traceability
R24
R24
R24
R24
Description:
Case Number
1.3.1
1.3.2
1.3.3
1.3 Manage rules
Tests managing the rules
Name
Edit service efficiency
Edit menu efficiency
Edit inventory efficiency
Traceability
R1, R2, R25
R1, R2, R25
R1, R2, R25
Table 1: Functional Categories & Test Category 1
-5-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Case Number
2.1
2.2
2.3
2.4
Description:
Case Number
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Set Number
2. Access Control
Tests administrative login
Name
Traceability
Login as an admin type
R18, R20, R21, R22, R23, R27, R31
Login as manager
R18, R20, R21, R22, R27, R31
Login as front end manager
R18, R20, R27
Login as back end manager R18, R20, R27
3. Take the data
Tests management of data
Name
Traceability
Edit staff
R28-30, R9, R10
Edit customer
R28-30, R9-11
Edit orders
R28-30, R9, R11
Edit inventory
R28-30, R9, R12
Edit menu
R28-30, R9, R11, R12
Input staff
R32-24, R9, R10
Input customer
R32-24, R9-11
Input orders
R32-24, R9, R11
Input inventory
R32-24, R9, R12
4. Efficiency Engine
Set Name
4.1 Process
4.2 Output
Description:
Case Number
5.1
Description:
Case Number
4.1.1
4.1.2
4.1.3
4.1 Process
Tests the process used by efficiency engines
Name
Service efficiency process
Menu efficiency process
Inventory efficiency process
Traceability
R3, R7, R35
R3, R7, R35
R3, R7, R35
Description:
Case Number
4.2.1
4.2.2
4.2.3
4.2 Output
Tests the output from efficiency engines
Name
Service efficiency output
Menu efficiency output
Inventory efficiency output
Traceability
R5, R36, R37
R5, R36, R37
R5, R36, R37
5. Performance Testing
Tests performance of RED AI prototype
Name
Traceability
Performance
R4, R6, R8
Table 2: Test Categories 2 – 5
-6-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
3.3 Test Schedule
The test schedule will govern the run-time demonstration process. The time allotted for
the RED AI prototype demonstration is 45 minutes. In this time, test cases spanning a sufficient
breadth and depth of of functional requirements must be completed. To effectively manage this
time and assist expert review panel members in following the demonstration events, the RED AI
demonstration script (Table 3) has been created.
3.4 Fault Reporting and Data Recording
During prototype demonstration, RED AI development team members will keep track of
all completed tests and their status, whether passing or failing. A checklist of all predicted test
encounters will be displayed during the demonstration. As each test case completes, its
displayed status will be updated.
3.5 Resource Requirements
The RED AI development team will require certain resources for successful
demonstration of the RED AI prototype. A machine offering Microsoft Windows XP or later
operating system must be present at the demonstration location. This machine must have
internet access and the ability to control multiple wall-mounted display devices. A RED AI
installation CD must be present at the time of testing. Review panel notebooks and assembled
concordance worksheets must be delivered to the testing site. Two secondary computer systems,
each capable of controlling a wall mounted display, must be present. A member of the ODU
Computer Science systems group must be present. The demonstration will require a whiteboard,
either wall mounted or on an easel, and one working dry erase marker
-7-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Time
Elapsed
~
RED AI PROTOTYPE DEMONSTRATION SCRIPT
Demo Event
PROBLEM
SOLUTION
BUDGET
15:00
INSTALL
UPDATE
ADMIN LOGIN
BLANK DB
SET UP USERS
18:00
MANAGER LOGIN
EDIT MENU
EDIT INVENTORY
EDIT MENU
SCHEDULE STAFF
25:00
BACKEND LOGS IN
RECIEVES SHIPMTS
FRONTEND LOGS IN
CUSTOMER DATA
ORDER DATA
31:00
MANAGER LOGIN
CHECK SVC EFF.
NOTICE ERROR
FIX CUST
CHECK ORDERS
CHECK SVC EFF.
OWNER LOGIN
CHECK MEN EFF.
CHECK INV EFF.
NOTICE ERROR
FIX RULE
CHECK INV EFF.
42:00
LOAD "PERFECT" RST
LOAD DEMO 1
LOAD DEMO 2
if time – LOAD DEMO 3
45:00
What it shows
ACT 1. THE PITCH
state the problem, so they believe it's a real problem
talk about ways to solve it
SBIR
ACT 2. SYSTEM SETUP
it's installed, we can access it from the start menu
we can go out into the world and get updates
check access control
should be nice and blank, with only root user
ability to add users
ACT 3. MODEL SETUP
check access control
edit tab - menu button works
edit tab - inventory button works
show ability to interface w/ relational database
input tab - staff button
ACT 4. TAKE THE DATA
check access control
input tab - inventory
check access control
input tab - customer
input tab - orders
ACT 5. MASSAGE THE DATA
3:00
7:00
6:00
11:00
output tab - svc efficency
THE SUGGESTIONS HAVE MEANING!!!
edit tab - customer
edit tab - orders
shows changing data changes suggestions
check access control
output tab - men efficency
output tab - inv efficency
THE SUGGESTIONS HAVE MEANING!!!
settings tab - update rules
shows changing rules changes suggestions
ACT 6. REALISTIC APPLICATION
show no rules broken
show 1 of each rule broken
show another of each rule broken
show another of each rule broken
ACT 7. CLOSURE
3:00
~
Table 3: RED AI Script
-8-
Time
Required
15:00
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
3.6 Test Environment
The RED AI prototype demonstration will take place in the ODU Engineering &
Computation Sciences (ENCS) third floor conference room. The ENCS conference room layout
is shown in Figure 2. Prior to demonstration initiation, the development team will ensure all
requirements given in section 3.5 are met with respect to the facilities available. The
Figure 2: E&CS Room
demonstration will begin with Microsoft Powerpoint slides shown syncrhonously on all four
viewing apparatus. The expert review panel will be seated along the west wall facing the center
of the room. During the actual demonstration, Projector Screen 1 and TV 2 will display the
running copy of the prototype. TV 1 will display a real-time checklist of test cases and their
status. Projector Screen 2 will be available to display any pertinent figures or diagrams to assist
in understanding of prototype concepts. The development team will move about the room as
required by the prototype demonstration script.
-9-
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
3.7 Testing Responsibilities
The RED AI development team members will conduct the prototype demonstration.
Alex Caulkins will welcome the review panel and introduce the first presenter, Patrick Bourque,
for a discussion of the societal problem RED AI is designed to address and what makes RED AI
a well-founded solution. Alex will resume the floor and discuss Phase II budget concerns. The
prototype demonstration will begin with Michael Janda, the upset restaurant owner, receiving a
complimentary beta install of RED AI from David Harris the RED AI travelling salesman. After
users accounts are created, Patrick, the restaurant manager, will construct a menu, inventory, and
recipes with the help of Alex and the expert review panel, and then schedule the staff for a day of
work. The backend manager, Matthew Crainer, will log shipments received while Brian
Terribile, the frontend manager, will enter customer flow and order data. At the end of the first
day of RED AI data modelling, the manager and owner will review efficiency reports, searching
for non-sequitur data elements and any rules which produce inappropriate suggestions. The
formal demonstration will close with a presentation of pre-seeded restaurant models, each
violating different subsets of rules, to show the potential of the initial production RED AI
release.
4 Test Procedures
Detailed test procedures have been prepared to ensure that the test cases can be
performed in an effective and efficient manner. Each test case has been assigned a unique name
and reference number. The requirements being tested by each case are identified along with the
necessary initialization steps, inputs, procedures, and expected results.
- 10 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.1.1 Verify Login
This test will ensure the program starts and the login screen is displayed correctly
Install program
n/a
Click on Windows Start Menu > All Programs > Old Dominion University > RED AI
Login screen is displayed
1.1.2 Verify Login Screen Objects
This test will verify the User is able to input correct data
Login is displayed
n/a
Visually inspect login screen
Verify username password fields are displayed and cancel and login buttons
1.1.3 Bad Login
This test will verify that a bad login will not allow User to access main screen
Login screen is displayed
User data and/or password not in User tables
On click of login button will check User table in db; no match is found; and allow retry
Will display error message
1.1.4 Good Login
This test will verify that a good login will allow User to access main screen
Login screen is displayed
User data and/or password in User tables
On click of login button will check User table in db; match is found;
Will display main screen
1.1.5 Look and Feel
This test will ensure main screen looks like a regular windows program
Complete 1.1.1 and 1.1.4
n/a
Look at main screen
Looks like windows program
1.1.6 Swap to Blank Database
Ensure swapping current db with the blank db will maintain the integrity of both db's
The User is on the settings tab
n/a
Click on swap db button
Blank db will be activated and old db will be saved in archive under the same name
When blank DB gets swapped it will be saved under filename "newDB.mdb"
Table 4: Test Cases 1.1.1 – 1.1.6
- 11 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.2.1 Add Admin Type
This test will verify that you can add a new user of type administrator
Must be on settings tab
User name and password of new user
The user will select to edit users and enter the new users information
A new administrator is available for login after user has been saved and closed
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.2.2 Add Manager Type
This test will verify that you can add a new user of type manager
Must be on settings tab
User name and password of new user
The user will select to edit users and enter the new users information
A new manager is available for login after user has been saved and closed
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.2.3 Add Front End Type
This test will verify that you can add a new user of type front end
Must be on settings tab
User name and password of new user
The user will select to edit users and enter the new users information
A new front end employee is available for login after user has been saved and closed
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.2.4 Add Back End Type
This test will verify that you can add a new user of type manager
Must be on settings tab
User name and password of new user
The user will select to edit users and enter the new users information
A new back end employee is available for login after user has been saved and closed
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.3.1 Edit Service Efficiency
This test will verify that the rules can be modified
The User must be on the settings tab
n/a
The User will click on the manage rules button and select service efficiency
A text based window with the rule file will be displayed
Modifying the text file should also be reflected after save and close
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.3.2 Edit Menu Efficiency
This test will verify that the rules can be modified
The User must be on the settings tab
n/a
The User will click on the manage rules button and select menu efficiency
A text based window with the rule file will be displayed
Modifying the text file should also be reflected after save and close
Table 5: Test Cases 1.2.1 – 1.3.2
- 12 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
1.3.3 Edit Inventory Efficiency
This test will verify that the rules can be modified
The User must be on the settings tab
n/a
The User will click on the manage rules button and select inventory efficiency
A text based window with the rule file will be displayed
Modifying the text file should also be reflected after save and close
2.1.1 Login as Admin Type
This test will ensure the Admin type has appropriate permissions
Complete test 1.2.1: Add Admin User
User name password as given in test 1.2.1
Check tab availability and button functionality
Permissions concurrent to lab 2 version 2 appendix 1: access control matrix
2.1.2 Login as Manager Type
This test will ensure the Manager type has appropriate permissions
Complete test 1.2.2: Add Manager Type
User name password as given in test 1.2.2
Check tab availability and button functionality
Permissions concurrent to lab 2 version 2 appendix 1: access control matrix
2.1.3 Login as Front End Type
This test will ensure the Front End type has appropriate permissions
Complete test 1.2.2: Add Front End Type
User name password as given in test 1.2.3
Check tab availability and button functionality
Permissions concurrent to lab 2 version 2 appendix 1: access control matrix
2.1.4 Login as Back End Type
This test will ensure the Back End type has appropriate permissions
Complete test 1.2.3: Add Back End Type
User name password as given in test 1.2.4
Check tab availability and button functionality
Permissions concurrent to lab 2 version 2 appendix 1: access control matrix
3.1 Edit Staff
This test will ensure that the edit staff button works
On edit tab
Data that you need to change
Click on the edit staff button and then add, delete, or change some or all the data
On save and close the data is updated in the database
Table 6: Test Cases 1.3.3 – 3.1
- 13 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
3.2 Edit Customer
This test will ensure that the edit customer button works
On edit tab
Data that you need to change
Click on the edit customer button and then add, delete, or change some or all the data
On save and close the data is updated in the database
3.3 Edit Orders
This test will ensure that the edit orders button works
On edit tab
Data that you need to change
Click on the edit orders button and then add, delete, or change some or all the data
On save and close the data is updated in the database
3.4 Edit Inventory
This test will ensure that the edit inventory button works
On edit tab
Data that you need to change
Click on the edit inventory button and then add, delete, or change some or all the data
On save and close the data is updated in the database
3.5 Edit Menu
This test will ensure that the edit menu button works
On edit tab
Data that you need to change
Click on the edit menu button and then add, delete, or change some or all the data
On save and close the data is updated in the database
3.6 Input Staff
This test wil ensure that the input staff button works
Logged in as front end and on the input tab
Data to be entered
Select input staff button and enter data into required fields
On save and close the data is updated in the database
3.7 Input Customer
This test wil ensure that the input customers button works
Logged in as front end and on the input tab
Data to be entered
Select input customer button and enter data into required fields
On save and close the data is updated in the database
Table 7: Test Cases 3.2 – 3.7
- 14 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
3.8 Input Orders
This test wil ensure that the input orders button works
logged in as back end and on the input tab
Data to be entered
Select input orders button and enter data into required fields
On save and close the data is updated in the database
3.9 Input Inventory
This test wil ensure that the input inventory button works
Logged in as manager and on the input tab
Data to be entered
Select input inventory button and enter data into required fields
On save and close the data is updated in the database
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.1.1 Service Efficiency Process
Ensure selected rule set can be parsed and appropriate tables can be accessed
Output tab is selected and sufficient service data is available
n/a
Select the desired effciency and the expected results is process flow
Brings resulted efficiencies to service efficiency output screen without error
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.1.2 Menu Efficiency Process
Ensure selected rule set can be parsed and appropriate tables can be accessed
Output tab is selected and sufficient menu data is available
n/a
Select the desired effciency and the expected results is process flow
Brings resulted efficiencies to menu efficiency output screen without error
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.1.3 Inventory Efficiency Process
Ensure selected rule set can be parsed and appropriate tables can be accessed
Output tab is selected and sufficient inventory data is available
n/a
Select the desired effciency and the expected results is process flow
Brings resulted efficiencies to inventory efficiency output screen without error
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.2.1 Service Efficiency Output
Ensure output screen displays populated service efficiency suggestion list
Complete test case 4.1.1
n/a
Look at the output screen
Output screen displays suggestions as shown in lab 2 version 2 figure 10: sample output
n/a
Table 8: Test Cases 3.8 – 4.2.
- 15 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.2.2 Menu Efficiency Output
Ensure output screen displays populated menu efficiency suggestion list
Complete test case 4.1.2
n/a
Look at the output screen
Output screen displays suggestions according to lab 2 version 2 figure 10: Sample output
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
4.2.3 Inventory Efficiency Output
Ensure output screen displays populated inventory efficiency suggestion list
Complete test case 4.1.3
n/a
Look at the output screen
Output screen displays suggestions according to lab 2 version 2 figure 10: Sample output
n/a
Description:
Initialization:
Input:
Procedure:
Results:
Notes:
5.1 Performance
Ensure prototype demonstration complete within the alloted time frame
Setup test environment according to Lab 3
n/a
Follow demonstration script in Lab 3
Demonstration is completed and on time
Table 9: Test Cases 4.2.2 – 5.1
5 Traceability to Requirements
As the the cases given in tables 4 through 9 of this document were designed to test the
functionality of the RED AI prototype, the relationships between these tests and the functional
requirements outlined in Lab 2 version 2 are presented in Table 10: Traceability Matrix. Test
cases are given, by name and number, across the top of the table. Requirements are given by
name and serial number on the left side. A mapping from serial number to Requirements
Checklist number is given on the right. Test case functional categories are indicated across the
bottom of the table.
- 16 -
Bourque
Lab 3 v.2 – Test Plan / Procedure
RED AI
Table 10: Traceability Matrix
- 17 -
Bourque