Online Backstage Management System (OBMS) Software Test Plan Document

This document presents a comprehensive test plan for the Online Backstage Management System (OBMS), a system designed to manage competitors in various sections. The plan encompasses a master test plan, unit test plan, integration test plan, and system test plan. It outlines the purpose, objectives, roles, and responsibilities of the testing team, including developers, project managers, and stakeholders. The test plan defines the scope, covering integration, user acceptance, and regression testing, while excluding user certifications and unit testing by external teams. Detailed test cases are provided, along with a traceability matrix and a Gantt chart for project management. The document also includes budget considerations and document approval procedures, ensuring a structured approach to software testing. The testing strategy includes unit, integration, system, user acceptance, and regression tests, with clear responsibilities assigned to the development team and other stakeholders. This ensures that the system is fully functional and all requirements are met.

Running head: ONLINE BACKSTAGE SOFTWARE TESTING 1
Online Backstage Software Testing
[Student name]
[University name]

2Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Table of Contents
1 Summary.............................................................................................................................................3
2 Test plan - including requirements traceability matrix........................................................................4
2.1 Master test plan...........................................................................................................................4
2.2 Instruction...................................................................................................................................4
2.3 Purpose........................................................................................................................................4
2.4 Test Objectives............................................................................................................................4
2.5 Roles and Responsibilities............................................................................................................5
2.6 Test Scope....................................................................................................................................6
2.7 Processes and References............................................................................................................6
2.8 Items to Be Tested.......................................................................................................................6
2.8.1 Overview of Test Inclusions................................................................................................7
2.8.2 Overview of Test Exclusions...............................................................................................8
2.9 Test Approach..............................................................................................................................8
2.9.1 Unit Test.............................................................................................................................10
2.9.2 Integration Test..................................................................................................................13
2.9.3 System Tests......................................................................................................................16
2.10 Test Environment (tools, system, databases)............................................................................18
2.11 Test Cases..................................................................................................................................18
2.11.1 System test cases...............................................................................................................18
2.11.2 System traceability matrix.................................................................................................19
2.12 Gantt chart.................................................................................................................................20
2.12.1 Test Milestones..................................................................................................................20
2.12.2 Gantt chart diagram...........................................................................................................21
2.13 Budget.......................................................................................................................................21
2.14 Document Approval...................................................................................................................22
Reference..................................................................................................................................................22

3Running head: ONLINE BACKSTAGE SOFTWARE TESTING
1 Summary
The system development is a major process where the development team conducts system
requirements analysis, the system design and the system development. This is report about the
test plan for the proposed Online Backstage Management System that is meant to record the
various competitors who are classified according to sections.
This report covers the various aspects in the test plan that includes the master test plan, the unit
test plan, integration test plan and system test plan.
The report however highlights the various test cases, traceability matrix test scope, test objective,
test purpose, roles and responsibilities of involved people, the items to be tested , the items not to
be tested, the test approach to be used, the test environment, the Gantt chart and the test
document approvals.
The system testing will therefore be important to ensure each system unit is fully functional and
all the entire integrated system is also functional.

4Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2 Test plan - including requirements traceability matrix
2.1 Master test plan
2.2 Instruction
This is the test plan document that is meant to define the process of doing the master test plan.
After the outlining of the master test plan the test plan documents will be constantly be reviewed
and then be approved by the selected technical development team of this project and the selected
business team member’s representatives. In case there are some changes that will be introduced
while executing or testing the system project, the master test plan document will be updated and
re-approved by both technical team and business representative team members.
2.3 Purpose
This test plan is designed due to the following purposes:
i. Documenting the entire tests processes.
ii. Describing of the test strategy which includes the test levels.
iii. To include the various test activities that will be performed.
iv. Documenting those who will be performing the testing activities.
2.4 Test Objectives
The following are the master plan objectives:
i. Providing the 100% test coverage of the documented system requirements.
ii. To cover the system software design documented elements.
iii. To do the execution of the various test cases during the users functional testing.
iv. To do the execution of the performance testing.
v. Creating, maintaining and controlling the tests environments.

5Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2.5 Roles and Responsibilities
The table below shows the various major roles and responsibilities included in the master test
plan.
Table 1: Roles and Descriptions
Roles Descriptions
Developers Team These are the people who are responsible of designing,
developing and coding the entire system components.
Developers Manager This is the person that will assist the development and
implementation of the entire system master test plan.
Program Manager This is the person that is responsible of planning and
executing the proposed project and also plays a role in
assisting the developer manager in creating the master
test plan.
Stake holders These are the people who hold a place in the organization
and their responsibility would likely affect the system
results.
Tests Analysts These are the people who will be doing the full system
execution of testing processes which includes the
verifying the system technical requirements and the
validating the business requirements.
Tests Leads This is a person that is either seasoned tests analyst or
test team members that is responsible of leading and
coordinating the various activities that are related to the
various aspects of tests that are based on the approved
mater tests plans and schedules.
Test Team/Testers These are the people who will be responsible of
executing the tests and ensuring that the testing
environment is adequately supporting the planned tests
activities.
Test Environment Team These are the people that are responsible of establishing,

6Running head: ONLINE BACKSTAGE SOFTWARE TESTING
maintaining and controlling the test environment.
2.6 Test Scope
This master test plan is going to be used in testing of all Online Backstage Management System
requirements with exception of few requirements and the selected requirements will be tested by
the development team and other stake holders with a reason to ensure that the system is fully
functional and all requirements are meet. However in this master plan the tests will cover the
integration, user acceptance, level and regression testing.
This test plan will not include the user certifications which will be done by the finance team and
unit testing that will be done by the external team.
2.7 Processes and References
The following are the various processes that guide the master test plan implementation.
i. Test Preparation
ii. Product Build
iii. Independent Test and Evaluation
The following are the references that support the implementation of Master Test Plan:
i. Business Requirement Document (BRD) Version 1.1, 08/2019
ii. Requirements Specification Document (RSD) Version 1.1, 08/2019
iii. System Design Document (SDD) Version 1.1, 08/2019
iv. Requirements Traceability Matrix (RTM) Version 1.1, 08/2019
v. Risk Log Version 1.1, 08/2019
2.8 Items to Be Tested
During the master plan testing there are various items that will be tested and they are different
range, these items can be categorized as follows:
i. Application software.
ii. Hardware system.
iii. Developed system.
iv. Project source codes
v. System objects codes.
vi. Jobs control codes.

7Running head: ONLINE BACKSTAGE SOFTWARE TESTING
vii. System documentation.
2.8.1 Overview of Test Inclusions
The following are the various tests that will be done in the master test plan to ensure that system
is functioning properly and the executing environment is well configured.
BR
# Feature
Responsible party or
groups
1. User logon, admin IT
2. User logoff IT, A/P Director
3. Register competitor by section IT, A/P Director
4. Register competitor by group / school. IT, Controller
5. Distribute Updated Information to key
Staff
IT
6. Import data from guidebook. IT, A/P Director
7. Print reports IT, A/P Director
8. Backup data IT, Controller
9. Restore data IT
10. Configure screens IT, A/P Director
11. Recording of Results IT, A/P Director
12. Update Section information IT, Controller
13. Move competitor between sections. IT
14. Displaying Competitor information IT, A/P Director
15. No client install IT, Controller
16. Setting Security passwords IT, A/P Director
17. Administration panel IT, Controller
18. Register by Section IT, Controller
19. Welcome screen IT
20. Display Sections that the Competitor is in IT, A/P Director
21. Data backup / restore IT, A/P Director
22. Field validation IT, Controller
23. TV display IT

8Running head: ONLINE BACKSTAGE SOFTWARE TESTING
(Tycho, 2014).
2.8.2 Overview of Test Exclusions
The below are the various components and features and combination of those components that
will not be done test:
BR
# Feature
1. Maintain historical records
2. Resemble existing system
3. Multiple sites
4. Roles
5. Discipline
6. Section
7. Displaying the Competitor
8. Competitor sequence number
9. Communication tool
10. PDA compatibility
11. Debating
2.9 Test Approach
In this section it entails the various testing strategies that are going to be followed in the
conducting the master test plan (Specialist, 2018).This shows the way the team of developers
plans covers the various activities that are specified in the building of the system, conducting the
independent tests and carrying the system evaluation of the proposed Online Backstage
Management System.
The below is the system testing strategy that will how the various tests, who will carry out tests
and when the tests will be carried.
Test Type Description Comment
Unit Test This is the test that will test individual
system component and it is carried out by
This is done by the team of system
developers after completing every

9Running head: ONLINE BACKSTAGE SOFTWARE TESTING
the system developers to ensure all
components are fully functional.
system stage to ensure full system
functionality.
Integration Test This type of test that is carried by the
system developers and they test how the
various integrated components works,
however it helps to detect if the changed
functionalities are functional end to end.
This is a test that is done by the
developers after integrating the
various unit components to check if
the system is fully functional after
some changes are made.
System Test This is type of test that is done to test the
system environment functionality, this
entails the system software, database
systems, the hardware and the
communication system, However the test
is done before system is installed to the
organization to ensure smooth execution
of the system.
This is the test that is done by the
system developers and also the
network and database administrators
to ensure the system installation
environment is fully functional.
User Acceptance
Test
This is the test that is meant to be carried
out by the business owners, and it mainly
tests the various changes made according
to the system end user requirements.
This is a test that is done after full
implementation of the system by the
development team that is done to
check if all the system requirements
are fully implemented.
Regression Test This is type of test done to the entire
system to ensure that any unimplemented
functionality does not affect the entire
project work and entire system use.
This is the test done by the team of
developers and the system owners.
User Certification
Test
This is type of test that is done after the
entire system is fully implemented and
installed to the organization environment
and this is done to ensure that entire
system had been installed successfully.
This is the test done by the system
owner and in case of hitches they alert
the team of developers.
(Stephen, 2014).

10Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2.9.1 Unit Test
This is the test that is done by the system Developers Team, Developers Manager, Program
Manager, Tests Analysts, Tests Leads, and Test Team/Testers to check the functionality of the
system during the system development process (Paige, 2015).
Test item Role Responsibility
Login form module Developers Team
Developers Manager
Program Manager
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing Login form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Registration form module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing registration form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Guide book module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing guide book module
 Logging system defects
 Documenting tests results.
 Communicating tests results to

11Running head: ONLINE BACKSTAGE SOFTWARE TESTING
management.
 Giving any recommendation on system
improvement
Report print form module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing report print form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Data backup module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing data backup module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Data restore module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing data restore module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Screens configuration module Tests Analysts  Providing technical directions.

12Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Tests Leads
Test Team/Testers
 Acquiring testing resources.
 Executing the screen configuration module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Results module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing results module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Section module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing section module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
competitor module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing competitor module
 Logging system defects
 Documenting tests results.

13Running head: ONLINE BACKSTAGE SOFTWARE TESTING
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
2.9.2 Integration Test
This is the tests that are done by the developers and the test team to ensure that the integrated
system components are working efficiently as per the system owner requirement. The below is a
table showing the unit test the assigned roles and responsibility given.
Test item Role Responsibility
admin login Developers Team
Developers Manager
Program Manager
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Try to do the admin login
 Logging admin login defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
system improvement in admin
login.
competitor registration Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the competitor registration
 Logging competitor registration
defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
system improvement in competitor
registration

14Running head: ONLINE BACKSTAGE SOFTWARE TESTING
updating section information Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the updating section
information.
 Logging updating section
information defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
system improvement in updating
section information.
moving competitor between
sections
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the moving competitor
between sections.
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
system improvement
recording results Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the recording results
process.
 Logging recording results defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on

15Running head: ONLINE BACKSTAGE SOFTWARE TESTING
system improvement in recording
results.
displaying competitor
information
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the displaying competitor
information test
 Logging displaying competitor
information defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
system improvement in displaying
competitor information
backup and restore data Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Perform the backup and restoration
of data.
 Logging backup and restore data
defects.
 Documenting tests results.
 Communicating tests results to
management (Michael, 2017).
 Giving any recommendation on
system improvement in backup and
restore data
2.9.3 System Tests
This is the test that is done by the system developers, stakeholders and the tester team and they
test the entire installed system to ensure that the system is fully functional. The below shows the
various system tests team members and their respective roles.

16Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Test item Role Responsibility
Database system Developers Team
Developers Manager
Program Manager
Database admin
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing database system
 Logging database defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
database improvement
Operating system Developers Team
Developers Manager
Program Manager
System admin
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing Operating system software
 Logging operating system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
modifying Operating system.
Network system Developers Team
Developers Manager
Program Manager
Network admin
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing Network system
 Logging Network system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on Network
system improvement
Test environment Developers Team
Developers Manager
Program Manager
 Providing technical directions.
 Acquiring testing resources.
 Analysing the test environment

17Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Tests Analysts
Tests Leads
Test Team/Testers
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on test
environment improvement.
Computer hardware Developers Team
Developers Manager
Program Manager
Computer technicians
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing Computer hardware.
 Logging Computer hardware.defects.
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
Computer hardware. System
improvement.
Test data Developers Team
Developers Manager
Program Manager
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Checking the test data
 Logging Test data invalidity.
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on
changing on the Test data.
2.10 Test Environment (tools, system, databases)
The following is the list of the items that are necessary for testing the system according to the system test
plan.
Tools Description Version
Win Runner Automated scripts generating tool. 5.0

18Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Load Runner Automated scripts generating tools. 2.5
Unix Shell Scripts Scripts language. n/a
Manual input Manual data capturing through the system interface. n/a
Clear Case Tools used for tracking the defects. n/a
System
Test System Online Backstage Management System n/a
Computer systems Ground floor n/a
Operating systems Windows 7/8/10 n/a
Computer network system Ground floor n/a
Database
System Test database System_test_database n/a
(Martin, 2017).
2.11 Test Cases
2.11.1 System test cases
Test case(TC#) Test case description
TC#01 Verifying if the system enables User and admin logon
TC#02 Verifying if the system enables User logoff
TC#03 Verifying if the system enables the display of Welcome screen
TC#04 Verifying if the system enables access to Administration panel
TC#05 Verifying if the system enables admin to Register competitor by section
TC#06 Verifying if the system enables the admin to Register competitor by group / school.
TC#07 Verifying if the system enables admin to do Setting of Security passwords
TC#08 Verifying if the system enables Field validation
TC#09 Verifying if the system enables Distribution of the Updated Information to key Staff
TC#10 Verifying if the system enables Importing of data from guidebook.
TC#11 Verifying if the system enables the Printing of reports
TC#12 Verifying if the system enables the Recording of Results
TC#13 Verifying if the system enables the Backup of data

19Running head: ONLINE BACKSTAGE SOFTWARE TESTING
TC#14 Verifying if the system enables the Restoring of data
TC#15 Verifying if the system enables the admin to Configure screens
TC#16 Verifying if the system enables the TV display
TC#17 Verifying if the system supports PDA compatibility
TC#18 Verifying if the system enables clients install computers to network
TC#19 Verifying if the system enables staffs to Record the Results
TC#20 Verifying if the system enables the admin to Update Section information
TC#21 Verifying if the system enables the admin to Move competitor between sections.
TC#22 Verifying if the system enables admin to Register competitors by Section
TC#23 Verifying if the system enables the Displaying of Sections that the Competitor is in
TC#24 Verifying if the system enables the Displaying of Competitor information
2.11.2 System traceability matrix
BR#_NO Business
requirement(BR#)
Functional
requirement_ID#
Functional requirements/use
cases(FR#)
Priority Test case
ID#
BR#_1 Login form module FR_1 User logon, admin High TC#01
FR_2 User logoff High TC#02
FR_3 Welcome screen High TC#03
BR#_2 Registration form
module
FR_4 Administration panel High TC#04
FR_5 Register competitor by
section
High TC#05
FR_6 Register competitor by group
/ school.
High TC#06
FR_7 Setting Security passwords High TC#07
FR_8 Field validation High TC#08
BR#_3 Guide book module FR_9 Distribute Updated
Information to key Staff
High TC#09
FR_10 Import data from guidebook. High TC#10
BR#_4 Report print form FR_11 Print reports High TC#11

20Running head: ONLINE BACKSTAGE SOFTWARE TESTING
module FR_12 Recording of Results High TC#12
BR#_5 Data backup module FR_13 Backup data High TC#13
BR#_6 Data restore module FR_14 Restore data High TC#14
BR#_7 Screens configuration
module
FR_15 Configure screens High TC#15
FR_16 TV display High TC#16
FR_17 PDA compatibility High TC#17
FR_18 No client install High TC#18
BR#_8 Results module FR_19 Recording of Results High TC#19
BR#_9 Section module FR_20 Update Section information High TC#20
FR_21 Move competitor between
sections.
High TC#21
FR_22 Register by Section High TC#22
BR#_10 competitor module FR_23 Display Sections that the
Competitor is in
High TC#23
FR_24 Displaying Competitor
information
High TC#24
(Michael, 2013).
2.12 Gantt chart
2.12.1 Test Milestones
The below is the test plan tasks and the set test dates to perform the test for each task, however these
tasks are set to ensure that they are able to meet set milestone.
Task Milestone Date
Setup Test Environment 30/06/2019
Complete Unit Testing 15/07/2019
Complete Integration Testing 30/07/2019
Complete system Testing 15/08/2019
Complete User Acceptance Testing 30/08/2019
Complete Regression Testing 15/09/2019

21Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Complete User Certification Testing 30/09/2019
2.12.2 Gantt chart diagram
(Elmasri, 2013).
2.13 Budget
The execution of the test plan will require some resources that will be installed and services , all
these will require some financial allocation as shown in the below test plan budget.
No Resource name Units cost
1. Computer
system
10 $2000
2. network router 2 $80
3. Network switch 5 $100
4. Network cable 1000 m $500
5. Printers 2 $200
6. Printing papers 10 cartons $30
7. Report writing - $20

22Running head: ONLINE BACKSTAGE SOFTWARE TESTING
8. TV displays 2 $200
9. PDA systems 2 $200
Total = $3,300
(Dick, 2018).
2.14 Document Approval
The below are the signatures to acknowledge that the test plan outlined above is completed and
accurately done. The next project steps will follow upon receiving the approval from the
management, however if there will be any changes to the system during the development process
the test plan will be updated and reapproved.
Approved by:
Printed name
Approved by:
Title
Approved By:
Signature/Date
System owner
representative
IT Representative
Reference
Dick,B.(2018). IT Project Management Essentials: Information Systems Project Methodology
Kindle Edition.New York:Amazon Digital Services LLC.
Elmasri,E.(2013). Database Systems: Models, Languages, Design and Application
Programming. India: PEARSON EDUCATION.
Michael, J.(2013). Database Design for Mere Mortals: A Hands-On Guide to Relational
Database Design.USA:Wesley Professional.
Martin,K.(2017). Designing Data-Intensive Applications: The Big Ideas Behind Reliable,

23Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Scalable, and Maintainable Systems.India:O'Reilly Media.
Michael,J.(2017).Human Resource Information Systems: Basics, Applications, and Future
Directions.New York :SAGE Publications, Inc.
Paige,B.(2015). Business Driven Information Systems with MISource 2007 and Student CD. New
York: McGraw-Hill.
Stephen,H.(2014).Management Information Systems with student CD and MISource. New
York:McGraw-Hill.
Specialist,I.(2018). CISSP Certified Information Systems Security Professional Study Guide
2018.New York:Independently published
Tycho,p.(2014).Personal Finance Simplified: The Step-By-Step Guide for Smart Money
Management Paperback.New York:Tycho Press.