Student Name
Student ID 26
Assignment 2: Software Test Document
(Backstage Management System)
Document Version Number 1.1
Group Members
Document Versions
Version
#
Implemented
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0
05/31/2020
05/31/2020
Test Plan draft
1.1
06/01/2020
06/01/2020
Functional testing
1.2
06/02/2020
06/02/2020
Integration Testing
Table of Contents
1. Introduction 4
1.1. System Overview 4
1.2. Objective 4
2. Test Plan 4
2.1. Scope 4
2.2. Requirement Traceability Matrix (RTM) 5
2.3. Non-Functional Requirements for Testing 6
2.4. Test Approach 6
3. Test Cases 6
3.1. Register Competitor 6
3.2. Importing Data from Guidebook 8
3.3. Configurable Screens 9
3.4. Multiple Sites 10
3.5. Maintain Historic Results 11
3.6. Print outs/ Reporting 12
3.7. Admin Panel 13
3.8. Group/ School Registration 14
3.9. Data Security 15
3.10. Data Backup / Restore 16
3.11. Usability 16
4. Appendix 18
4.1. GANTT Chart 18
4.2. Network Diagram 19
4.3. Resource Allocation Plan 20
4.4. Budget 21
1. Introduction
1.1. System Overview
This project is about developing eStage Information system for managing Backstage activities. The project handling process is given to Royal South Street Society for developing the entire system. Currently, the organization is managing all their data in excel sheets. Sometimes, it becomes difficult to search for a particular record set. Also, in security perspective, anyone from the company can access the excel files whether its authorized or unauthorized users. The booking system for the company is very messy ie sometimes they forget to take the payment from the customer. Hence, the management decided to implement Backstage Management System ie eStage that can be used to automate all processes. The main objective of the report is to develop test cases for the system Backstage management System. In this document, we are developing test plan, test cases. Also, project scheduling and budget estimation will be done in this report.
1.2. Objective
The Test Plan document can be used to track the important data which is required to viably characterize the way to deal with be utilized in the testing of the OBMS. The Test Plan document is made amid the Planning Phase of the task. The main audience of this document is the project manager, project team, and testing team. A bit of this document can be shared with client whereas other part can be shared with stakeholders. We will try to perform requirement based testing in the context of nine functional and three non-functional requirement mentioned in SRS document.
2. Test Plan
2.1. Scope
The scope of the test plan is to test the developed backstage management system that can automate all business processes of the Royal South Street Society. The testing done in this plan will be unit testing, integration testing system testing and acceptance testing. The system will be tested on the basis of functional and non-functional requirements by adopting agile method.
2.2. Requirement Traceability Matrix (RTM)
S.No
Item to Test
Test Description
Test Date
Responsibility
Test Case No
1
Register Competitor
The competitor has to register before participating in the competition.
1st June 2020
Project Manager, Developer, DBA
T1
2
Importing Data from guidebook
In this, we have to test whether data is imported correctly from guidebook to the BMS system.
3rd June 2020
Project Manager, HR personnel
T2
3
Configurable screens
The screens must be configurable at user end in order to get particular record set from the database.
5th June 2020
PM, User, key staff, DBA
T4
4
Multiple Sites
This test case is to test that the system can accessed at multiple sites.
7th June 2020
PM, key User
T5
5
Maintain historic results
All the historic results must be saved into the test. The test case is to check whether the previous competition result is saved into the system or not. It can be done by retrieving the data by choosing particular historic dates.
9th June 2020
PM, User, key staff
T6
6
Print outs/ Reporting
In this test, we will check that whether all the reports can be retrieved in an organized way.
12th June 2020
PM, Developer, DBA
T7
7
Admin Panel
The admin panel must have administrative rights. This test case is to check whether all the options in admin panel are working properly or not.
15th June 2020
PM, User, CEO
T8
8
Group/ School Registration
There must be an option for registering groups or schools by the competitor itself.
21st June 2020
PM, Developer, User
T9
2.3. Non-Functional Requirements for Testing
S.No
Item to Test
Test Description
Test Date
Responsibility
Test Case No
1
Data Security
The data must be saved in encrypted for better security of data
22nd June 2020
Project Manager, Developer, User
T10
2
Data backup/ Restore
The data backup must be scheduled on daily basis.
24th June 2020
Project Manager, HR personnel
T11
3
Usability
The testing is to check whether the system is easy to use.
26th June 2020
User
T12
2.4. Test Approach
A test plan will be developed that can be used to test all above mentioned functional and non-functional requirements. Unit test, functional testing and acceptance testing will be best options for testing above requirements. Some test cases will be prepared on the basis of particular user requirement. After developing test plan, the same will be approved from the management authority. The stakeholders will be shown the test results in order to verify that all system requirements are working properly.
3. Test Cases
3.1. Register Competitor
Register Competitor
Test Stage
Unit testing, Functional testing
Test Date:
1st June 2020
Tester:
Mr. Hitesh Sharma (PM), Ms. Simona (Developer), Mr. Vinay (DBA)
Test Case Number:
T1
Test Case Description:
The testing will be done for checking that the competitors can easily register themselves in the system.
Results:
Pass
Incident Number, if applicable:
T1
INTRODUCTION
Requirement(s) to be tested:
This requirement is tested by opening the registration form and entering the detailed information of the competitor. The system must save all data in the database by clicking on submit button.
Roles and Responsibilities:
Developer – Developers must check all the code that has been written by her step by step.
Project manager – The PM is responsible to check whether the “Register Competitor” is working or not.
Set Up Procedures:
The data must be entered into the Competitor Registration form by the tester.
Stop Procedures:
The procedure will be stopped when the system saves all data into the database.
Technological Requirements
Hardware:
Windows based MySQL database
Software:
Web browser should be installed into the system with java plugins as this is web based application.
Procedural Requirements:
Raw...