Running head: LAB 3 - PROTOTYPE TEST PLAN/PROCEDURE FOR ELDERS
1
Lab 3 – Prototype Test Plan/Procedure for ELDERS
Ben Cortina
CS 411W
Janet Brunelle
April 17, 2013
Version 1Table of Contents
1
OBJECTIVES .......................................................................................................................... 1
2
REFERENCES ......................................................................................................................... 1
3
TEST PLAN............................................................................................................................. 1
3.1
Testing Approach ............................................................................................................. 1
3.2
Identification of Tests ...................................................................................................... 1
3.3
Test Schedule ................................................................................................................... 1
3.4
Fault Reporting and Data Recording ............................................................................... 1
3.5
Resource Requirements ................................................................................................... 1
LAB 3 - Prototype Test Plan/Procedure for ELDERS
3.6
2
Test Environment ............................................................................................................. 2
4
TEST RESPONSIBILITIES .................................................................................................... 2
5
TEST PROCEDURE ................................................................................................................ 2
5.1
6
Test Case Names and Identifiers...................................................................................... 2
TRACEABILITY TO REQUIREMENTS ............................................................................... 2
List of Tables
Table 1. ELDERS Prototype Test Cases by Category .................................................................... 8
Table 2. ELDERS Prototype Test Schedule .................................................................................... 9
Table 3. ELDERS Traceability Matrix
521
OBJECTIVES
The Endangered Language Documentation, Extension, and Revival System (ELDERS)
will provide a community with a means to store and expand their language. ELDERS will be
designed to ensure the language will thrive by focusing on the three most important elements of
language revival: documentation, expansion, and education. While the language must expand,
without a well-documented origin, the language would have no root from which to grow.
Therefore, ELDERS will offer services that allow communities to store the alphabet of their
language, words and their appropriate attributes, and grammar structure. Development of the
language should be entirely community driven. This is why ELDERS will offer language
expansion tools in the form of a suggestion and voting system for new words. For a language to
thrive, there must be a growing user base. To support and enable expansion, ELDERS will
provide educational material such as history, grammar tutorials, and word games.
LAB 3 - Prototype Test Plan/Procedure for ELDERS
The ELDERS prototype will be designed to show off the most important features of
ELDERS. It will implement several key features: documentation, culture, access control, word
approval process, and notifications. The prototype will come will full support for documenting
the language and archiving the changes to the language while being developed through
ELDERS. The history section of the website will be fully functional to allow the culture to be
well defined. To ensure privacy, ELDERS will allow the community to set access privileges on
each certain elements. The prototype will contain a system that allows user to suggest, vote on,
and approve new words. The notification system will also be implemented in the ELDERS
prototype.
The prototype will undergo testing to ensure all the features above have been properly
implemented. This will be done by proving every requirement has been met. This test plan and
procedure will detail the approach, timeline, and requirements for performing these tests.
2
REFERENCES
Cortina, Ben. (2013). Lab 1 – ELDERS Description. Norfolk, VA: Author.
Cortina, Ben. (2013). Lab 2 – Prototype Product Specification for ELDERS. Norfolk, VA:
Author.
3
TEST PLAN
The test plan consists of the approach, identification, schedule, reporting procedures,
requirements, and environment of the tests being performed.
3.1
Testing Approach
All of the tests being run during the presentation are aimed to prove every requirement
for the prototype of ELDERS has been met. Table 1 shows that the tests have been divided into
3
LAB 3 - Prototype Test Plan/Procedure for ELDERS
4
twelve major categories. This division was based on which area of the prototype the element
being tested falls under. The tests will be executed in numerical order, based on the test case ID.
The prototype will be running from a virtual machine at Old Dominion University.
During the presentation ELDERS will be accessed via a computer connected to the internet.
Most of the test cases will be run with the goal of proving functionality. Test cases with this goal
will be performed by a person acting as a user of ELDERS. Another person will be monitoring
back-end data such as the database. This will allow the viewers to see the changes taking affect
in the database. There are also test cases with the goal of showing a component was implemented
as specified by the requirements. Cases such as these will not be executed using the public user
interface.
The system will be prepared with real Nottoway words and history. Existing Accounts,
access tiers, and all other information will have been created solely for the purpose of executing
the test cases. Any elements added or created during the presentation will also be solely for the
purpose of executing the test cases.
3.2
Identification of Tests
Table 1 lists all the test case ID, description, and purpose for each test case that will
performed during the presentation. Further detail on each test case will be covered in Section 5.1.
Category
ID
1
Description
Access Control
Test Test Case Description
Case
ID
Objective
1.1
View access tiers and
tier permissions
Show that access tiers and
permissions are implemented.
1.2
Request higher tier
status
Show a user may request a
higher tier status.
Create new access tier
Demonstrate process of creating
a new access tier.
1.3
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Category
ID
Description
Test Test Case Description
Case
ID
1.4
Show that the permissions for an
access tier may be edited.
Verify Access checks
Show that all access checks are
in place.
Create new user
Prove that an account can be
created.
2.2
Alert user if username
already exists
Show that username redundancy
is prevented
2.3
Verify password
requirements
Verify that the password
restrictions are in place.
2.4
Login as existing
account
Demonstrate that registered
users are able to log in.
2.5
Login with incorrect
information
Show that invalid logins call an
error.
2.6
Reset account
password
Verify that a password may be
reset.
Change notification
settings
Demonstrate that a user may
change their notification
preferences.
Council to vote on
suggested word(s)
To expand the Nottoway
Language
Restrict only one vote
per council member
Ensure that the Council can
only make one vote on a
suggested word.
User change vote
Change vote due to common
error.
1.6
2.1
User Accounts
2.7
3.1
3.2
3
Voting
Change default account Verify that the default tier may
tier
be changed.
Edit account tiers
1.5
2
Objective
3.3
3.4
Words that have
When the majority of votes are
reached threshold mark in the words favor.
as approved
3.5
Able to add new word
to dictionary
Expand the dictionary upon
“approved” words.
5
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Category
ID
Description
Test Test Case Description
Case
ID
Search Nottoway
words in English
To test whether searching by
English returns the correct
information.
Alert of failed search
To notify the user that the word
searched is not in the database.
4.3
Suggest and show
suggestions of failed
search
To suggest alternatives for a
returned fail search
4.4
Edit words that are
suggested
To give Council an opportunity
to change suggested words
Search Nottoway
words in Nottoway
To test whether searching by
Nottoway returns the correct
information.
Alert of failed search
To test whether users receive a
notification when they search
for a Nottoway word that
doesn’t exist.
4.7
Nottoway filtered by
letter
To test that the word filter
functions correctly.
5.1
History of the
Nottoway viewable
To test that the Nottoway
history is displayed.
6.1
Suggested words by
users
To test a list of suggested words
by users
6.2
Prompt to suggest word To notify the suggested word if
if no suggested word
the word does not exist
exists
6.3
User input of suggested To test that a suggested word
word
can be inputted
6.4
User submission of
suggested word
To test that a suggest word can
be submitted
Edit website settings
To test that the settings on the
website have been changed by
the administrator
4.1
4.2
4
Searching
4.5
4.6
5
6
7
History
Suggestions
Administration
Objective
7.1
6
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Category
ID
Description
Test Test Case Description
Case
ID
7.2
8.1
8
Forum
8.1
9.1
9.2
9.3
9
Edit website
permissions
To test the website's permission
level
Access Forum
To test that the Forum is
displayed.
Create access
controlled sub forums
To test that a user’s forum
account is the same as their
ELDERS account.
View the Nottoway
database
Viewing the database proves
that it exists.
Backup the database
Prove that the DB is being
backed up.
Create a MySQL user
Users must exist in order to
access the DB.
9.4
Assign users sufficient Make sure that user’s privileges
database privileges
are set.
9.5
View the ALPHABET Make sure that the ALPHABET
table schema
table has the expected columns.
9.6
View the
Make sure that the table has the
HISTORICAL_DICTI right columns.
ONARY table schema
9.7
View the
Make sure that the table has the
EXPANDED_DICTIO right columns.
NARY table schema
9.8
View the
NUM_VOTES table
schema
Make sure that the table has the
right columns.
9.9
Prove password
encryption
Make sure that the passwords
are encrypted in the DB.
Access syllabary chart
To test that the Syllabary is
displayed.
Browse grammar
Verify the user can access the
Nottoway grammar.
Database
10.1
10
Objective
Language
10.2
7
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Category
ID
Description
Test Test Case Description
Case
ID
Can be viewed on
11.1 mobile devices
11
12
Versatility
Maintenance
Objective
Confirming the ability for
ELDERS to be viewed on a
mobile device.
Can be functional for
Confirming that ELDERS can
all major web browsers be used correctly through
11.2
different web browsers that are
commonly used.
Check for software
12.1 update
Show that there is a means to
update software used by
ELDERS
Table 1. ELDERS Prototype Test Cases by Category
3.3
Test Schedule
For the first five minutes, one of the developers of the prototype will be presenting
ELDERS while the rest of the developers prepare the test enviroment. After that, the test cases
will be executed as described in Table 2.
Start Time Duration Test Objective
(Minutes) (Minutes)
Category Dependencies
Comments
5
6
Prove access tier
functionality
1
none
none
11
6
Show functional user
accounts
2
none
none
17
5
Demonstrate the voting
system
3
none
none
22
5
Dazzle with amazing
searching
4
none
none
27
5
Blow minds with excellent 5, 6, 7,
history linkage, word
and 8
suggesting, and
administration, lets not
forget the handy dandy
forum
none
none
8
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Start Time Duration Test Objective
(Minutes) (Minutes)
Category Dependencies
Comments
32
8
Run through the Database
functionality
9
none
none
40
5
Finish up with language
content, versatility of the
app and maintaining the
webapp
10, 11,
and 12
none
none
9
Table 2. ELDERS Prototype Test Schedule
3.4
Fault Reporting and Data Recording
During the presentation, there will be a group member with the task of recording the
outcome of the test cases. This person will be referred to as the Test Recorder. They will handle
all fault and data reporting. For each test case, the success or failure of the test case will be
written down. Additionally, reasons for failure, errors that occur, and thoughts from the audience
will be recorded.
3.5
Resource Requirements
The ELDERS prototype will be run on a virtual machine at Old Dominion University.
This machine will be located outside the room and connected to the internet. The person running
the test cases as a user will be on a computer which is connected to the internet. This computer
will also need to be connected to a projector to allow the audience to view the test case
execution. All major browsers (Chrome, Firefox, Safari, and Internet Explorer) will need to be
installed on this computer. The person viewing the back-end will be using a separate computer
with an internet connection and a means to display the back-end to the viewers. The Test
Recorder will record the results with either a computer or pen and pencil. Lastly, an Apple
computer will be brought to the presentation with Safari, Chrome, and Firefox installed.
3.6
Test Environment
LAB 3 - Prototype Test Plan/Procedure for ELDERS
10
Initial setup will require ensuring the necessary computers are able to connect to the
projector and all necessary software is installed. The Test Recorder will sit by a surface on which
they can perform their task. The person executing the test cases will be seated at the computer
which is connected to the projector. The screen of this computer will be displayed on the
projector screen. The presenter will stand near the screen. The audience will sit facing the
presenter and projector screen to allow them to see each action being executed.
4
TEST RESPONSIBILITIES
In the ELDERS prototype presentation, there will be two presenters, two test users, a
database monitor, and a test recorder. The primary speakers will be Tatiana Livingston and
George Calhoun, who will work together in presenting the prototype. One of the two presenters
will take the other’s job if he/she is unable to attend. They will also provide an introduction and
narrative of each test case. Ben Cortina and Josh Fetherolf will be test users as well as operating
the computer. Taking turns, each test user will execute the test case, explain what they are doing
as well as show the expected results. Terry Stilwell will be the database monitor, responsible for
displaying and explaining changes to the database when applicable. Robert Matson is the test
recorder. He will keep the testing on track and will record what has been done and the result. He
will also record what needs to be done should any errors occur.
5
TEST PROCEDURE
A detailed set of test cases has been prepared for testing ELDERS. Each test has
been designed to ensure that the ELDERS prototype meets its requirements. These tests will be
described in Section 5.1.
5.1
Test Case Names and Identifiers
LAB 3 - Prototype Test Plan/Procedure for ELDERS
All test cases provided are designed to ensure that all the requirements of
ELDERS have been met. A unique identification number has been provided for each test case.
The requirement numbers are also shown with the test cases to show why each test case was
created.
Test Category: 1
Description: View access tiers and tier permissions
Test Case: 1.1
Case Name: Access
tier viewing
Requirements
Fulfilled: 3.1.1.1
Purpose: Show that access tiers and permissions are
implemented.
Version: 1.0
Written By: Ben
Cortina
Setup Conditions:
 Logged in as user with permission to view access tiers
Test Case Activity
Pass/Fail
Comments
1 Access
Expected Result
Access tiers are
displayed.
Permissions for each
tier are visible.
administration page
2 Access access tiers
3 Click on a access
tier to view
permissions
Test Category: 1
Description: Request higher tier status
Test Case: 1.2
Case Name:
Requesting tier
status
Requirements
Fulfilled: 3.1.1.1.2
Purpose: Show a user may request a higher tier status.
Version: 1.0
Written By: Ben
Cortina
Setup Conditions:
 Logged in as existing user
Test Case Activity
Pass/Fail
Comments
Expected Result
11
LAB 3 - Prototype Test Plan/Procedure for ELDERS
1 Request higher tier
Access tier request is
noted.
status
2 Log in as user
with permissions
to set access tiers
3 VIew pending tier
promotion
requests.
4 Note the request is
listed
Test Category: 1
Description: Create new access tier and prove its creation
Test Case: 1.3
Case Name: Create
new access tier
Requirements
Fulfilled: 3.1.1.2.1,
3.1.1.2.3, 3.1.1.2
Purpose: Demonstrate process of creating a new access tier.
Version: 1.0
Written By: Ben
Cortina
Setup Conditions:
 Logged in as user with permissions to create access tiers
Test Case Activity
Pass/Fail
Comments
1 Access
Expected Result
Access tier is created
and user is assigned
to the new tier.
administration
page
2 Access access tiers
3 Create new tier
4 Set existing user
to newly created
tier
Test Category: 1
Description: Change the default account tier
Test Case: 1.4
Case Name: Change
default account tier
Version: 1.0
Written By: Ben
Cortina
12
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.1.1.1.1,
3.1.1.2.2, 3.1.1.2
Purpose: Verify that the default tier may be changed.
Setup Conditions:
 Logged in as user with permissions change access tiers settings
Test Case Activity
Pass/Fail
Comments
1 Access
2
3
4
5
Expected Result
User account should
be in the default tier.
administration
page
Access access tiers
Change default
access tier.
Create a new
account.
Show that new
account is in the
new default tier
Test Category: 1
Description: Change a access tier’s permissions
Test Case: 1.5
Case Name: Edit
account tiers
Requirements
Fulfilled: 3.1.1.2,
3.1.1.2.4, 3.1.1.2.5,
3.1.1.2.5.*
Purpose: Show that the permissions for an access tier may be
edited.
Version: 1.0
Written By: Ben
Cortina
Setup Conditions:
 Logged in as user with permission to edit access tiers
Test Case Activity
Pass/Fail
Comments
Expected Result
13
LAB 3 - Prototype Test Plan/Procedure for ELDERS
1 Access
2
3
4
5
6
Permission change is
reflected in accounts
from that tier.
administration
page
Access access
tiers.
Click on a access
tier to edit
permissions
Show every
permission from
3.1.1.2.5 is listed
Edit at least one
permission.
Prove that the
permission is
changed for an
account in that
access tier
Test Category: 1
Description: Verify Access checks
Test Case: 1.6
Case Name: Access
Checks
Requirements
Fulfilled: 3.3.2.2
Purpose: Show that all access checks are in place.
Version: 1
Written By: Ben
Cortina
Setup Conditions:
● Component source code accessible
● Logged in as user with permission to edit access tiers
Test Case Activity
Pass/Fail
Comments
Expected Result
14
LAB 3 - Prototype Test Plan/Procedure for ELDERS
For each permission,
1 Access the user
tiers.
2 Show that the
permission is
assignable
3 In the relevant
source code, show
the section that
prevents access
Once,
4 Attempt to access
with an account
that does not have
the permission
The access is
prevented for the
tested feature and
every feature uses a
similar system to
block access.
Test Category: 2
Description: The method of creating an account
Test Case: 2.1
Case Name:
Account Creation
Requirements
Fulfilled: 3.1.1.3,
3.1.1.3.1, 3.1.1.3.3,
3.1.1.3.4
Purpose: Prove that an account can be created.
Version: 1.0
Written By: George
Calhoun
Setup Conditions:
 At website home page
Test Case Activity
1 Click the Create
Pass/Fail
Comments
Expected Result
account is created
an Account Link
2 Fill in Account
Details
3 Click Register
Test Category: 2
Description: The method of creating an account
15
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 2.2
Case Name:
Account Creation
Version: 1.0
Written By: George
Calhoun
Requirements
Fulfilled: 3.1.1.3.2
Purpose: Show that username redundancy is prevented
Setup Conditions:
● At website home page
● An already created account
Test Case Activity
Pass/Fail
Comments
Click the Create
an Account Link
2 Fill in Account
Details with an
already used
username
3 Click Register
Expected Result
receive notification
that username is
already in use
1
Test Category: 2
Description: The method of creating an account
Test Case: 2.3
Case Name:
Account Creation
Requirements
Fulfilled: 3.1.1.3.3.*
Purpose: Verify that the password restrictions are in place.
Version: 1.0
Written By: George
Calhoun
Setup Conditions:
At website home page
Test Case Activity
Click the Create
an Account Link
2 Fill in Account
Details with an
improper
username
3 Click Register
1
Pass/Fail
Comments
Expected Result
Receive alert that the
password does not
fulfill the
requirements
16
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Category: 2
Description: Making sure registered users are able to log into
ELDERS
Test Case: 2.4
Case Name: log in
Requirements
Fulfilled: 3.1.1.4,
3.1.1.4.1, 3.1.1.4.2
Purpose: Demonstrate that registered users are able to log in.
Version: 1.0
Written By: George
Calhoun
Setup Conditions:
● At website home page
● Account created
Test Case Activity
Pass/Fail
Comments
Fill out User
name
2 Fill out password
correctly
3 click log in
Expected Result
be logged into your
account
1
Test Category: 2
Description: Making sure only registered users are able to log
into ELDERS
Test Case: 2.5
Case Name:
Incorrect log in
Requirements
Fulfilled: 3.1.1.5,
3.1.1.5.1, 3.1.1.5.2
Purpose: Show that invalid logins call an error.
Version: 1.0
Written By: Ben
Cortina
Setup Conditions:
● At website home page
● Account created
Test Case Activity
Pass/Fail
Comments
Expected Result
17
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Fill out User
name
2 Fill out password
incorrectly
3 click log in
4 Repeat steps 1-3
with incorrect
username
18
Does not allow the
user to sign in and
presents them with an
error
1
Test Category: 2
Description: Regaining access to an account when the password is
forgotten
Test Case: 2.6
Case Name:
password reset
Requirements
Fulfilled: 3.1.1.6.*
Purpose: Verify that a password may be reset.
Version: 1.0
Written By: George
Calhoun
Setup Conditions:
● At website home page
● Account created
Test Case Activity
Pass/Fail
Comments
Click forgot
password link
2 fill out box with
an incorrect email
address for
account
3 repeat step 2 with
correct email
4 use information
in email to reset
password
Expected Result
Error message after
step 2
email sent to the
email address after
step 3
1
Test Category: 2
Description: Changing why and how often you receive
notifications
Test Case: 2.7
Case Name: change
notification settings
Version: 1.0
Written By: George
Calhoun
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.1.1.8
Purpose: Demonstrate that a user may change their notification
preferences.
Setup Conditions:
● At website home page
● Account created
● Account logged in
Test Case Activity
1
2
Pass/Fail
Comments
go to account
setting
change
notifications
Expected Result
notifications changed.
Test Category: 3
Description: Voting
Test Case: 3.1
Case Name:
Suggested Word
Vote
Requirements
Fulfilled: 3.1.2.1
Purpose: To expand the Nottoway Language
Version: 1
Written By: Josh
Setup Conditions:
 User logon tab in voting section.
Test Case Activity
1
2
3
4
5
User accesses
administration
page
User searches for
word
User prompted of
non-existing
word
Selects either
search or vote
User changes
their vote
Pass/Fail
Comments
Expected Result
User has the
opportunity to
expand the Nottoway
language by voting.
19
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Category: 3
Description: Voting
Test Case: 3.2
Case Name: Voting
Restrictions to One.
Requirements
Fulfilled: 3.1.2.1.1
Purpose: Ensure that the Council can only make one vote on a
suggested word.
Version: 1
Written By: Josh
Setup Conditions:
 User logon and each vote only is obtained only once.
Test Case Activity
Pass/Fail
Comments
User access
administration
page
2 User votes on
word
3 Restricted to one
vote per user
Expected Result
A user has one vote.
1
Test Category: 3
Description: Voting
Test Case: 3.3
Case Name: Able to
Change Vote.
Requirements
Fulfilled: 3.1.2.1.2
Purpose: Change vote due to common error.
Version: 1
Written By: Josh
Setup Conditions:
 User logon tab in voting section.
Test Case Activity
User accesses
administration
page
2 User accesses
past votes
3 User changes
vote
1
Pass/Fail
Comments
Expected Result
Users are able to
change vote at a later
time. This updates in
the database as still
counting only one
vote per member.
20
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Category: 3
Description: Voting
Test Case: 3.4
Case Name:
Threshold Stamp of
Approval.
Requirements
Fulfilled: 3.1.2.1.3*
Purpose: When the majority of votes are in the words favor.
Version: 1
Written By: Josh
Setup Conditions:
 Database will have a count on each word.
Test Case Activity
Pass/Fail
Comments
Enough user
votes have been
received
2 Words that have
reached threshold
of votes are
marked as
approved
Expected Result
Total number of user
votes have reached
the majority so the
suggested word is
now added.
1
Test Category: 3
Description: Voting
Test Case: 3.5
Case Name: Adding
New Word to
Dictionary
Requirements
Fulfilled: 3.1.2.2
Purpose: Expand the dictionary upon “approved” words.
Version: 1
Written By: Josh
Setup Conditions:
 Database sees a majority vote and prompts the admin to add to dictionary
Test Case Activity
Pass/Fail
Comments
Expected Result
21
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Administrator
notified that word
has reached
threshold
2 Administrator
access
administration
panel
3 Administrator
adds new word to
dictionary
Administrator adds
suggested word that
has reached threshold
of user votes to the
dictionary.
1
Test Category: 4
Description: Searching the database for an English word
Test Case: 4.1
Case Name:
Successful English
Search
Requirements
Fulfilled: 3.1.2.6,
3.1.2.6.2.*, 3.1.2.6.2
Purpose: To test whether searching by English returns the
correct information.
Version: 1
Written By: Tatiana
Setup Conditions:
 At dictionary search page
Test Case Activity
22
Pass/Fail
Comments
Set search to
English to
Nottoway
2 Enter an English
word that is in the
database
3 Search
Expected Result
The searched word
and all of the data
stored for it are
displayed.
1
Test Category: 4
Description:
Test Case: 4.2
Case Name: Search
Fail
Version: 1
Written By: Terry
Stilwell
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.1.2.6.1
Purpose: To test what the search will return if it fails to find a
word
Setup Conditions:
 At dictionary search page
Test Case Activity
Pass/Fail
Comments
Set search to
English to
Nottoway
2 Enter an English
word that isn’t in
the database
3 Search
Expected Result
User is alerted of
failed search
1
Test Category: 4
Description:
Test Case: 4.3
Case Name: Search
Fail Suggestions
Version: 1
Written By: Terry
Stilwell
Requirements
Purpose: To suggest alternatives for a failed search
Fulfilled: 3.1.2.6.1.a3.1.2.6.1.c
Setup Conditions:
 At dictionary search page
Test Case Activity
Pass/Fail
Set search to
English to
Nottoway
2 Enter an English
word that isn’t in
the database
3 Search
Expected Result
Should see suggested
words, and votes for
suggested words
1
Test Category: 4
Comments
Description:
23
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 4.4
Case Name: Edit
words that are
suggested
Version: 1
Requirements
Fulfilled: 3.1.2.6.1.d
Purpose: To give the user an opportunity to change suggested
words
24
Written By: Terry
Stilwell
Setup Conditions:
 At dictionary search page
Test Case Activity
Pass/Fail
Comments
Set search to
English to
Nottoway
2 Enter an English
word that isn’t in
the database
3 Search
4 Get a list of
suggested words
Expected Result
Should be able to edit
the word or words
that are suggested
1
Test Category: 4
Description: Searching the database for a Nottoway word
Test Case: 4.5
Case Name:
Version: 1
Successful Nottoway
Search
Requirements
Fulfilled: 3.1.2.7,
3.1.2.7.2.*, 3.1.2.7.2
Purpose: To test whether searching by Nottoway returns the
correct information.
Written By: Tatiana
Setup Conditions:
 At dictionary search page
Test Case Activity
Pass/Fail
Comments
Expected Result
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Set search to
Nottoway
2 Enter a Nottoway
word that is in the
database
3 Search
25
The searched word
and all of the data
stored for it are
displayed.
1
Test Category: 4
Description: Failed search notification
Test Case: 4.6
Case Name: Search
Fail
Requirements
Fulfilled: 3.1.2.7.1
Purpose: To test whether users receive a notification when they
search for a Nottoway word that doesn’t exist.
Version: 1
Written By: Tatiana
Setup Conditions:
 At dictionary search page
Test Case Activity
Pass/Fail
Comments
Set search to
Nottoway
2 Enter a Nottoway
word that isn’t in
the database
3 Search
Expected Result
Notify user word
doesn’t exist
1
Test Category: 4
Description: Filter by word
Test Case: 4.7
Case Name: Filter
Requirements
Fulfilled: 3.1.2.4
Purpose: To test that the word filter functions correctly.
Version: 1
Written By: Tatiana
Setup Conditions:
 On the syllabary chart page
Test Case Activity
Pass/Fail
Comments
Expected Result
LAB 3 - Prototype Test Plan/Procedure for ELDERS
1
Click on a letter
in the chart
All the words that
begin with that letter
are displayed
Test Category: 5
Description: Displaying the Nottoway history
Test Case: 5.1
Case Name: History
Requirements
Fulfilled: 3.1.2.8
Purpose: To test that the Nottoway history is displayed.
Version: 1
Written By: Tatiana
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
Pass/Fail
Comments
Click link to the
Nottoway history
Expected Result
The Nottoway
History is displayed
Test Category: 6
Description: Suggested words by users
Test Case: 6.1
Case Name:
Suggestions
Requirements
Fulfilled: 3.1.2.9
Purpose: To show what words have been already suggested by
current users
Version: 1
Written By: Robert
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
26
Pass/Fail
Comments
Show suggested
words by user
Expected Result
Suggested words are
displayed
Test Category: 6
Description: Prompt to suggest words
Test Case: 6.2
Case Name:
Suggestions
Version: 1
Written By: Robert
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.1.2.9
Purpose: To let the users know about suggested word
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
Pass/Fail
Comments
Prompt to
suggested word if
no word exists
Expected Result
No words have been
suggested, it notifies
users of a suggested
word from the user
Test Category: 6
Description: Input suggested word
Test Case: 6.3
Case Name:
Suggestions
Requirements
Fulfilled: 3.1.2.9.1
Purpose: To be able to input a suggested word
Version: 1
Written By: Robert
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
Pass/Fail
Comments
User inputs a
suggested word
Expected Result
The suggested word
can be inputted
Test Category: 6
Description: Submit suggested words
Test Case: 6.4
Case Name:
Suggestions
Requirements
Fulfilled: 3.1.2.9.2
Purpose: To be able to submit a suggested word
Version: 1
Written By: Robert
Setup Conditions:
 On ELDERS Website
Test Case Activity
Pass/Fail
Comments
Expected Result
27
LAB 3 - Prototype Test Plan/Procedure for ELDERS
1
User submits a
suggested word
The suggested word
will be submitted to a
list of suggested
words
Test Category: 7
Description: Website settings
Test Case: 7.1
Case Name:
Administration
Requirements
Fulfilled: 3.1.2.10
Purpose: To changes settings on the website
Version: 1
Written By: Robert
Setup Conditions:
 On ELDERS database
Test Case Activity
1
Pass/Fail
Comments
Edit website
settings
Expected Result
The edit in the
settings has changed
for the website
Test Category: 7
Description: Website permissions
Test Case: 7.2
Case Name:
Administrations
Requirements
Fulfilled: 3.1.2.10
Purpose: To change permissions for administrators and users
Version: 1
Written By: Robert
Setup Conditions:
 On ELDERS database
Test Case Activity
1
Pass/Fail
Comments
Edit website
permissions
Test Category: 8
Expected Result
Permissions have
changed for who can
and cannot access
areas
Description: Displaying the Forum
28
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 8.1
Case Name: Forum
Version: 1
Requirements
Fulfilled: 3.1.2.11
Purpose: To test that the Forum is displayed.
29
Written By: Tatiana
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
Pass/Fail
Comments
Click link to the
Forum page
Expected Result
The Forum is
displayed
Test Category: 8
Description: Corresponding forum account and ELDERS
account
Test Case: 8.2
Case Name: Forum
Account
Requirements
Fulfilled: 3.1.2.11.2
Purpose: To test that a user’s forum account is the same as their
ELDERS account.
Version: 1
Written By: Tatiana
Setup Conditions:
 On ELDERS Website, User is logged in
Test Case Activity
1
Pass/Fail
Comments
Click link to the
Forum page
Expected Result
The Forum is
displayed and the
User is logged in to
the forum with an
account that
corresponds with
their ELDERS
account.
Test Category: 9
Description: Database
Test Case: 9.1
Case Name: View
DB
Version: 1
Written By: Terry
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.3.1.1
Purpose: Viewing the database proves that it exists.
Setup Conditions:
 MySQL installed and Nottoway database created
Test Case Activity
Pass/Fail
Comments
SSH into server
and then connect
to MySQL
2 Type “show
databases;”
Expected Result
You will see the
database listed.
1
Test Category: 9
Description: Database
Test Case: 9.2
Case Name: DB
Backup
Requirements
Fulfilled: 3.3.1.2,
3.3.4.1
Purpose: Prove that the DB is being backed up.
Version: 1
Written By: Terry
Setup Conditions:
 Cron job in place with mysqldump that specified date in the file name
Test Case Activity
Write a script that
includes the
mysqldump
command
2 Make sure the
script creates a
file with the date
of the dump
3 Manually run the
cron job or wait
until the time set
(midnight)
1
Pass/Fail
Comments
Expected Result
You will see the
backed up file in the
specified directory of
the script.
30
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Category: 9
Description: Database
Test Case: 9.3
Case Name:
MySQL user
Requirements
Fulfilled: 3.3.1.3
Purpose: Users must exist in order to access the DB.
Version: 1
Written By: Terry
Setup Conditions:
 MySQL installed with a root mysql account with highest privileges
Test Case Activity
1
2
3
4
5
Pass/Fail
Comments
Log into mysql
with the root
account
Create a mysql
user using the
appropriate
syntax
Set privileges for
that mysql user
Flush the
database
Query the DB for
a list of users
Expected Result
You will see a list of
users that includes
the newly created
one.
Test Category: 9
Description: Database
Test Case: 9.4
Case Name:
MySQL User
Privileges
Requirements
Fulfilled: 3.3.1.4
Purpose: Make sure that user’s privileges are set.
Version: 1
Written By: Terry
Setup Conditions:
 MySQL user already created
Test Case Activity
Pass/Fail
Comments
Expected Result
31
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Once logged into
mysql, create a
user, a new table,
set privileges for
the new user to
write to that table,
and flush
privileges
2 Using the new
user, insert
information into
the new table
3 Query the new
table to see the
inserted row
32
The new user will be
able to write to the
new table and the
change can be seen.
1
Test Category: 9
Description: Database
Test Case: 9.5
Case Name:
ALPHABET Table
Requirements
Fulfilled: 3.3.1.5*
Purpose: Make sure that the ALPHABET table has the expected
columns.
Version: 1
Written By: Terry
Setup Conditions:
 The ALPHABET table is already created with the proper columns.
Test Case Activity
Pass/Fail
Log into mysql
using a user with
privileges to read
the ALPHABET
table
2 Change to the
Nottoway DB
3 Type describe
ALPHABET
Expected Result
You will see the table
with the proper
columns
1
Test Category: 9
Comments
Description: Database
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 9.6
Case Name:
Version: 1
HISTORICAL_DIC
TIONARY Table
Requirements
Fulfilled: 3.3.1.6*
Purpose: Make sure that the table has the right columns.
33
Written By: Terry
Setup Conditions:
 HISTORICAL_DICTIONARY is created with proper columns.
Test Case Activity
Pass/Fail
Comments
Log into mysql
using a user with
privileges to read
the
HISTORICAL_D
ICTIONARY
table
2 Change to the
Nottoway DB
3 Type describe
HISTORICAL_D
ICTIONARY
Expected Result
You will see the table
with the proper
columns
1
Test Category: 9
Description: Database
Test Case: 9.7
Case Name:
EXPANDED_DICT
IONARY Table
Requirements
Fulfilled: 3.3.1.7*
Purpose: Make sure that the table has the right columns.
Version: 1
Written By: Terry
Setup Conditions:
 EXPANDED_DICTIONARY table is created and has right columns
Test Case Activity
Pass/Fail
Comments
Expected Result
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Log into mysql
using a user with
privileges to read
the
EXPANDED_DI
CTIONARY
table
2 Change to the
Nottoway DB
3 Type describe
EXPANDED_DI
CTIONARY
34
You will see the table
with the proper
columns
1
Test Category: 9
Description: Database
Test Case: 9.8
Case Name:
NUM_VOTES
Table
Requirements
Fulfilled: 3.3.1.8*
Purpose: Make sure that the table has the right columns.
Version: 1
Written By: Terry
Setup Conditions:
 At website login page
Test Case Activity
Pass/Fail
Log into mysql
using a user with
privileges to read
the
NUM_VOTES
table
2 Change to the
Nottoway DB
3 Type describe
NUM_VOTES
Expected Result
You will see the table
with the proper
columns
1
Test Category: 9
Comments
Description: Database
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 9.9
Case Name:
Password
Encryption
Version: 1
Requirements
Fulfilled: 3.3.2.1
Purpose: Make sure that the passwords are encrypted in the DB.
35
Written By: Terry
Setup Conditions:
 A user is created and the password is encrypted in the DB
Test Case Activity
Pass/Fail
Comments
Log into mysql
with the root
account.
2 Query the
database with the
user and
password
columns from the
mysql.user table
Expected Result
You will see the
users and their
encrypted passwords
1
Test Category: 10
Description: Displaying the Syllabary
Test Case: 10.1
Case Name:
Syllabary
Requirements
Fulfilled: 3.1.2.3
Purpose: To test that the Syllabary is displayed.
Version: 1
Written By: Tatiana
Setup Conditions:
 On ELDERS Website
Test Case Activity
1
Pass/Fail
Comments
Click link to
language section
Test Category: 10
Expected Result
Syllabary chart
displayed
Description: Browse the Grammar
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case: 10.2
Case Name:
Grammar
Version: 1
Requirements
Fulfilled: 3.1.2.5
Purpose: Verify the user can access the Nottoway grammar.
Written By: Tatiana
Setup Conditions:
 On a page in the language section
Test Case Activity
1
Pass/Fail
Comments
Click on the
Grammar link
Expected Result
Display the basic
grammar rules of the
Nottoway language
Test Category: 11
Description: Viewing ELDERS on a mobile device
Test Case: 11.1
Case Name:
Mobility
Requirements
Fulfilled: 3.3.4.2
Purpose: Confirming the ability for ELDERS to be viewed on a
mobile device.
Version: 1
Written By: George
Setup Conditions:
 Using a mobile device
Test Case Activity
Pass/Fail
Comments
Expected Result
Navigate to the
ELDERS web
page using the
device
The ELDERS web
page looks the same
as when viewing it
through a computer.
Test Category: 11
Description: Viewing ELDERS through multiple web browsers
Test Case: 11.2
Case Name:
Versatility
1
Version: 1
36
Written By: George
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Requirements
Fulfilled: 3.3.4.3
37
Purpose: Confirming that ELDERS can be used correctly
through different web browsers that are commonly used.
Setup Conditions:
 On a computer with multiple Internet Browsers
Test Case Activity
1
2
3
4
5
Pass/Fail
Comments
Open Internet
Explorer
Navigate to
ELDERS web
page
Repeat steps 1
and 2 with
Firefox
Repeat steps 1
and 2 with
Chrome
Repeat steps 1
and 2 with Safari
Expected Result
All 4 browsers should
load ELDERS
without error, and
should all look
approximately the
same
Test Category: 12
Description: Check for software update
Test Case: 12.1
Case Name:
Software Update
Requirements
Fulfilled: 3.3.4.3
Purpose: Show that there is a means to update software used by
ELDERS
Version: 1
Written By: Ben
Cortina
Setup Conditions:
 On a computer with multiple Internet Browsers
Test Case Activity
Pass/Fail
Comments
Expected Result
LAB 3 - Prototype Test Plan/Procedure for ELDERS
1
2
3
4
5
6
Open Joomla
administration
page
Navigate to the
Extension
Manager
Click Update
Click purge cache
Click Find
Updates
38
Any updates for
outdated Extensions
should be listed.
TRACEABILITY TO REQUIREMENTS
The purpose of each test is to prove a set of requirements have been met. Table 3
provides an extensive matrix with a requirement ID labeling each row and a test case ID on each
column. In the resulting grid, an X means that the requirement on that row is fulfilled by the test
case on that column.
Test Case ID
Component
Requirement
ID
3.1.1.1
Create Tiered
Account
3.1.1.1.1
System
3.1.1.1.2
1.1
1.2
1.3
X
X
X
3.1.1.2.1
X
3.1.1.2.2
3.1.1.2.4
1.5
X
3.1.1.2
3.1.1.2.3
1.4
X
X
X
X
X
3.1.1.2.5
Manage Tier
3.1.1.2.5.a
System
3.1.1.2.5.b
X
3.1.1.2.5.c
X
3.1.1.2.5.d
X
3.1.1.2.5.e
X
3.1.1.2.5.f
X
3.1.1.2.5.g
X
X
X
1.6
2.1
2.2
2.3
2.4
2.5
2.6
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
1.1
1.2
1.3
1.4
1.5
3.1.1.2.5.h
X
3.1.1.2.5.i
X
3.1.1.2.5.j
X
3.1.1.2.5.k
X
3.1.1.2.5.l
X
3.1.1.2.5.m
X
3.1.1.2.5.n
X
3.1.1.2.5.o
X
3.1.1.2.5.p
X
3.1.1.2.5.q
X
3.1.1.2.5.r
X
3.1.1.2.5.s
X
3.1.1.2.5.t
X
1.6
2.1
3.1.1.3
X
3.1.1.3.1
X
3.1.1.3.2
3.1.1.3.3
User
Registration
2.3
2.4
2.5
2.6
X
X
3.1.1.3.3.a
X
3.1.1.3.3.b
X
3.1.1.3.3.c
X
3.1.1.3.3.d
X
3.1.1.3.4
User Login
2.2
X
3.1.1.4
X
3.1.1.4.1
X
3.1.1.4.2
X
3.1.1.5
X
3.1.1.5.1
X
3.1.1.5.2
X
3.1.1.6
3.1.1.6.1
User Account
3.1.1.6.2
Management
3.1.1.7
3.1.1.8
3.1.2.1
Voting
3.1.2.1.1
3.1.2.1.2
X
X
39
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
3.1.2.1.2.a
3.1.2.1.3
3.1.2.1.3.a
Grammar
3.1.2.3
3.1.2.5
3.1.2.2
3.1.2.4
3.1.2.6
3.1.2.6.1
3.1.2.6.1.a
3.1.2.6.1.b
3.1.2.6.1.c
3.1.2.6.1.d
3.1.2.6.2
3.1.2.6.2.a
3.1.2.6.2.b
3.1.2.6.2.c
Dictionary
3.1.2.6.2.d
3.1.2.6.2.e
3.1.2.6.2.f
3.1.2.7
3.1.2.7.1
3.1.2.7.2
3.1.2.7.2.a
3.1.2.7.2.b
3.1.2.7.2.c
3.1.2.7.2.d
3.1.2.7.2.e
3.1.2.7.2.f
3.1.2.7.2.g
3.1.2.8
3.1.2.9
Website
3.1.2.9.1
3.1.2.9.2
3.1.2.10
Suggestion
3.1.2.11
1.1
1.2
1.3
1.4
1.5
1.6
2.1
2.2
2.3
2.4
2.5
2.6
40
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
1.1
1.2
1.3
1.4
1.5
1.6
2.1
2.2
2.3
2.4
2.5
2.6
4.2
4.3
4.4
4.5
4.6
3.1.2.11.1
3.1.2.11.2
Database
Creation
3.3.1.1
Database
Backup
3.3.1.2
Database Users
3.3.1.3
3.3.1.4
3.3.1.5
3.3.1.5.a
3.3.1.5.b
3.3.1.6
3.3.1.6.a
3.3.1.6.b
3.3.1.6.c
3.3.1.6.d
Database
Tables
3.3.1.6.e
3.3.1.7
3.3.1.7.a
3.3.1.7.b
3.3.1.7.c
3.3.1.7.d
3.3.1.7.e
3.3.1.8
3.3.1.8.a
3.3.1.8.b
Encryption
3.3.2.1
Authentication 3.3.2.2
Update
X
3.3.3.1
3.3.4.1
Reliability
3.3.4.2
3.3.4.3
Test Case ID
Component
Requirement
ID
Create Tiered 3.1.1.1
2.7
3.1
3.2
3.3
3.4
3.5
4.1
41
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Account
System
Requirement
ID
3.1.1.1.1
3.1.1.1.2
3.1.1.2
3.1.1.2.1
3.1.1.2.2
3.1.1.2.3
3.1.1.2.4
3.1.1.2.5
3.1.1.2.5.a
3.1.1.2.5.b
3.1.1.2.5.c
3.1.1.2.5.d
3.1.1.2.5.e
3.1.1.2.5.f
Manage Tier 3.1.1.2.5.g
System
3.1.1.2.5.h
3.1.1.2.5.i
3.1.1.2.5.j
3.1.1.2.5.k
3.1.1.2.5.l
3.1.1.2.5.m
3.1.1.2.5.n
3.1.1.2.5.o
3.1.1.2.5.p
3.1.1.2.5.q
3.1.1.2.5.r
3.1.1.2.5.s
3.1.1.2.5.t
3.1.1.3
3.1.1.3.1
3.1.1.3.2
User
Registration
3.1.1.3.3
3.1.1.3.3.a
3.1.1.3.3.b
3.1.1.3.3.c
3.1.1.3.3.d
2.7
3.1
3.2
3.3
3.4
3.5
4.1
4.2
4.3
4.4
4.5
4.6
42
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
2.7
3.1
3.2
3.3
3.4
3.5
4.1
4.2
4.3
4.4
4.5
3.1.1.3.4
3.1.1.4
3.1.1.4.1
User Login
3.1.1.4.2
3.1.1.5
3.1.1.5.1
3.1.1.5.2
3.1.1.6
X
3.1.1.6.1
User Account
3.1.1.6.2
Management
3.1.1.7
3.1.1.8
3.1.2.1
3.1.2.1.1
Voting
Grammar
3.1.2.1.2
X
X
X
X
3.1.2.1.2.a
3.1.2.1.3
X
3.1.2.1.3.a
X
3.1.2.3
3.1.2.5
3.1.2.2
X
3.1.2.4
3.1.2.6
X
3.1.2.6.1
Dictionary
X
3.1.2.6.1.a
X
3.1.2.6.1.b
X
3.1.2.6.1.c
X
3.1.2.6.1.d
X
3.1.2.6.2
X
3.1.2.6.2.a
X
3.1.2.6.2.b
X
3.1.2.6.2.c
X
3.1.2.6.2.d
X
3.1.2.6.2.e
X
3.1.2.6.2.f
X
3.1.2.7
X
4.6
43
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
2.7
3.1
3.2
3.3
3.4
3.5
4.1
4.2
4.3
4.4
4.5
3.1.2.7.1
X
3.1.2.7.2.a
X
3.1.2.7.2.b
X
3.1.2.7.2.c
X
3.1.2.7.2.d
X
3.1.2.7.2.e
X
3.1.2.7.2.f
X
3.1.2.7.2.g
X
3.1.2.9
Website
3.1.2.9.1
3.1.2.9.2
3.1.2.10
3.1.2.11
Suggestion
3.1.2.11.1
3.1.2.11.2
Database
Creation
3.3.1.1
Database
Backup
3.3.1.2
Database Users
3.3.1.3
3.3.1.4
3.3.1.5
3.3.1.5.a
3.3.1.5.b
3.3.1.6
3.3.1.6.a
3.3.1.6.b
Database
Tables
X
3.1.2.7.2
3.1.2.8
3.3.1.6.c
3.3.1.6.d
3.3.1.6.e
3.3.1.7
3.3.1.7.a
3.3.1.7.b
3.3.1.7.c
3.3.1.7.d
4.6
44
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
2.7
3.1
3.2
3.3
3.4
3.5
4.1
4.2
4.3
4.4
4.5
4.6
7.2
8.1
8.2
9.1
9.2
3.3.1.7.e
3.3.1.8
3.3.1.8.a
3.3.1.8.b
Encryption
3.3.2.1
Authentication 3.3.2.2
Update
3.3.3.1
3.3.4.1
Reliability
3.3.4.2
3.3.4.3
Test Case ID
Component
Requirement
ID
3.1.1.1
Create Tiered
Account
3.1.1.1.1
System
3.1.1.1.2
3.1.1.2
3.1.1.2.1
3.1.1.2.2
3.1.1.2.3
3.1.1.2.4
3.1.1.2.5
3.1.1.2.5.a
3.1.1.2.5.b
3.1.1.2.5.c
Manage Tier 3.1.1.2.5.d
System
3.1.1.2.5.e
3.1.1.2.5.f
3.1.1.2.5.g
3.1.1.2.5.h
3.1.1.2.5.i
3.1.1.2.5.j
3.1.1.2.5.k
3.1.1.2.5.l
3.1.1.2.5.m
3.1.1.2.5.n
4.7
5.1
6.1
6.2
6.3
6.4
7.1
45
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
4.7
3.1.1.2.5.o
3.1.1.2.5.p
3.1.1.2.5.q
3.1.1.2.5.r
3.1.1.2.5.s
3.1.1.2.5.t
3.1.1.3
3.1.1.3.1
3.1.1.3.2
3.1.1.3.3
User
Registration
3.1.1.3.3.a
3.1.1.3.3.b
3.1.1.3.3.c
3.1.1.3.3.d
3.1.1.3.4
3.1.1.4
3.1.1.4.1
User Login
3.1.1.4.2
3.1.1.5
3.1.1.5.1
3.1.1.5.2
3.1.1.6
3.1.1.6.1
User Account
3.1.1.6.2
Management
3.1.1.7
3.1.1.8
3.1.2.1
3.1.2.1.1
Voting
3.1.2.1.2
3.1.2.1.2.a
3.1.2.1.3
3.1.2.1.3.a
Grammar
Dictionary
3.1.2.3
3.1.2.5
3.1.2.2
3.1.2.4
X
5.1
6.1
6.2
6.3
6.4
7.1
7.2
8.1
8.2
9.1
9.2
46
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
4.7
5.1
6.1
6.2
6.3
6.4
7.1
7.2
X
X
8.1
8.2
9.1
9.2
3.1.2.6
3.1.2.6.1
3.1.2.6.1.a
3.1.2.6.1.b
3.1.2.6.1.c
3.1.2.6.1.d
3.1.2.6.2
3.1.2.6.2.a
3.1.2.6.2.b
3.1.2.6.2.c
3.1.2.6.2.d
3.1.2.6.2.e
3.1.2.6.2.f
3.1.2.7
3.1.2.7.1
3.1.2.7.2
3.1.2.7.2.a
3.1.2.7.2.b
3.1.2.7.2.c
3.1.2.7.2.d
3.1.2.7.2.e
3.1.2.7.2.f
3.1.2.7.2.g
3.1.2.8
X
3.1.2.9
Website
3.1.2.9.1
X
3.1.2.9.2
X
3.1.2.10
3.1.2.11
Suggestion
3.1.2.11.1
3.1.2.11.2
Database
Creation
3.3.1.1
Database
Backup
3.3.1.2
Database Users
3.3.1.3
3.3.1.4
X
X
X
X
X
X
X
47
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
4.7
5.1
6.1
6.2
6.3
6.4
7.1
7.2
8.1
8.2
9.1
9.2
3.3.1.5
3.3.1.5.a
3.3.1.5.b
3.3.1.6
3.3.1.6.a
3.3.1.6.b
3.3.1.6.c
3.3.1.6.d
Database
Tables
3.3.1.6.e
3.3.1.7
3.3.1.7.a
3.3.1.7.b
3.3.1.7.c
3.3.1.7.d
3.3.1.7.e
3.3.1.8
3.3.1.8.a
3.3.1.8.b
Encryption
3.3.2.1
Authentication 3.3.2.2
Update
3.3.3.1
3.3.4.1
Reliability
X
3.3.4.2
3.3.4.3
Test Case ID
Component
Requirement
ID
3.1.1.1
Create Tiered
Account
3.1.1.1.1
System
3.1.1.1.2
3.1.1.2
3.1.1.2.1
Manage Tier 3.1.1.2.2
System
3.1.1.2.3
3.1.1.2.4
3.1.1.2.5
9.3
9.4
9.5
9.6
9.7
9.8
9.9
10.1 10.2 11.1 11.2 12.1
48
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
3.1.1.2.5.a
3.1.1.2.5.b
3.1.1.2.5.c
3.1.1.2.5.d
3.1.1.2.5.e
3.1.1.2.5.f
3.1.1.2.5.g
3.1.1.2.5.h
3.1.1.2.5.i
3.1.1.2.5.j
3.1.1.2.5.k
3.1.1.2.5.l
3.1.1.2.5.m
3.1.1.2.5.n
3.1.1.2.5.o
3.1.1.2.5.p
3.1.1.2.5.q
3.1.1.2.5.r
3.1.1.2.5.s
3.1.1.2.5.t
3.1.1.3
3.1.1.3.1
3.1.1.3.2
3.1.1.3.3
User
Registration
3.1.1.3.3.a
3.1.1.3.3.b
3.1.1.3.3.c
3.1.1.3.3.d
3.1.1.3.4
3.1.1.4
3.1.1.4.1
User Login
3.1.1.4.2
3.1.1.5
3.1.1.5.1
3.1.1.5.2
User Account 3.1.1.6
9.3
9.4
9.5
9.6
9.7
9.8
9.9
10.1 10.2 11.1 11.2 12.1
49
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
9.3
9.4
9.5
9.6
9.7
9.8
9.9
10.1 10.2 11.1 11.2 12.1
Management 3.1.1.6.1
3.1.1.6.2
3.1.1.7
3.1.1.8
3.1.2.1
3.1.2.1.1
Voting
3.1.2.1.2
3.1.2.1.2.a
3.1.2.1.3
3.1.2.1.3.a
Grammar
3.1.2.3
3.1.2.5
3.1.2.2
3.1.2.4
3.1.2.6
3.1.2.6.1
3.1.2.6.1.a
3.1.2.6.1.b
3.1.2.6.1.c
3.1.2.6.1.d
3.1.2.6.2
3.1.2.6.2.a
3.1.2.6.2.b
Dictionary
3.1.2.6.2.c
3.1.2.6.2.d
3.1.2.6.2.e
3.1.2.6.2.f
3.1.2.7
3.1.2.7.1
3.1.2.7.2
3.1.2.7.2.a
3.1.2.7.2.b
3.1.2.7.2.c
3.1.2.7.2.d
3.1.2.7.2.e
3.1.2.7.2.f
X
X
50
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
9.3
9.4
9.5
9.6
9.7
9.8
9.9
10.1 10.2 11.1 11.2 12.1
3.1.2.7.2.g
3.1.2.8
3.1.2.9
Website
3.1.2.9.1
3.1.2.9.2
3.1.2.10
3.1.2.11
Suggestion
3.1.2.11.1
3.1.2.11.2
Database
Creation
3.3.1.1
Database
Backup
3.3.1.2
Database Users
Database
Tables
Encryption
3.3.1.3
3.3.1.4
X
X
3.3.1.5
X
3.3.1.5.a
X
3.3.1.5.b
X
3.3.1.6
X
3.3.1.6.a
X
3.3.1.6.b
X
3.3.1.6.c
X
3.3.1.6.d
X
3.3.1.6.e
X
3.3.1.7
X
3.3.1.7.a
X
3.3.1.7.b
X
3.3.1.7.c
X
3.3.1.7.d
X
3.3.1.7.e
X
3.3.1.8
X
3.3.1.8.a
X
3.3.1.8.b
X
3.3.2.1
X
Authentication 3.3.2.2
Update
3.3.3.1
Reliability
3.3.4.1
X
51
LAB 3 - Prototype Test Plan/Procedure for ELDERS
Test Case ID
Component
Requirement
ID
9.3
9.4
3.3.4.2
3.3.4.3
Table 3. ELDERS Traceability Matrix
9.5
9.6
9.7
9.8
9.9
10.1 10.2 11.1 11.2 12.1
X
X
52