Software Engineering

Thorough analysis of software application Online Backstage Management System, including test plan, test case documents, and Gantt chart. Includes strategies, interface testing, usability testing, and user acceptance testing.

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student
Name of the University
Author Note

1SOFTWARE ENGINEERING
Summary
The purpose of this report is to thoroughly analyse the requirements of the software
application Online Backstage Management System performs software testing by providing
the test plan and test case documents along with Gantt chart for the complete process. First
the report talks about the strategies involved in carrying out the test in the test plan while
also providing the requirement traceability matrix or RTM. Thereafter the report moves to
the Test Case section where the report explains the interface testing, usability testing and
user acceptance testing that has been conducted to prepare the test cases according to the
business and functional requirements present in the requirements traceability matrix. After
talking in detail about the test cases that have been created the report lays out the timeline
with the help of the Gantt chart. Following that, the budgeting and pricing involved in the
software testing process is calculated and mentioned after which the report ends by
providing observations in the conclusions section.

2SOFTWARE ENGINEERING
Table of Contents
Introduction................................................................................................................................3
Test Plan Document...................................................................................................................3
Purpose...................................................................................................................................3
Scope......................................................................................................................................3
Testers....................................................................................................................................3
Method...................................................................................................................................3
Environment...........................................................................................................................4
Timing....................................................................................................................................4
RTM.......................................................................................................................................4
Test Acceptance Criteria........................................................................................................5
Test Deliverables....................................................................................................................5
Test Case Document..................................................................................................................6
User Interface Testing............................................................................................................6
Usability Testing....................................................................................................................6
User Acceptance Testing........................................................................................................6
Gantt Chart...............................................................................................................................20
Budgeting.................................................................................................................................20
Conclusion................................................................................................................................21
Bibliography.............................................................................................................................22

3SOFTWARE ENGINEERING
Introduction
This report is about thoroughly analysing the requirements of the software application
Online Backstage Management System performs software testing by providing the test plan and test
case documents along with Gantt chart for the complete process. The report begins by talking about
all the strategies involved in carrying out the test in the test plan while also providing the
requirement traceability matrix or RTM. Thereafter the report moves to the Test Case section where
the report explains the interface testing, usability testing and user acceptance testing that has been
conducted to prepare the test cases according to the business and functional requirements present
in the requirements traceability matrix. After talking in detail about the test cases that have been
created the report lays out the timeline with the help of the Gantt chart. Following that, the
budgeting and pricing involved in the software testing process is calculated and mentioned after
which the report ends by providing observations in the conclusions section.
Test Plan Document
Purpose
The test plan mentions the approach of testing undertaken and the framework driving the
test procedure of Online Backstage Management System (OBMS). In this report, functional testing of
the OBMS application has been performed which deals with providing inputs and validating the
outcomes.
Scope
The scope of the application varies depending on the business requirements and the
corresponding functional requirements. These are mentioned in the requirement traceability matrix.
Testers
The testers are the personnel who perform the test design and execution. They can include
the test team, the test lead and the test analyst.
Method
The test process is conducted with the help of the test cases identified for the application
OBMS using the test management Tools. The test management Tool used for testing OBMS
application is HP Quality Center.

4SOFTWARE ENGINEERING
Environment
The software has been tested in the windows operating system platform on version
Windows 10 Professional and Windows Server 2016. The browsers used are Internet Explorer 9,
Google Chrome 32 and Mozilla Firefox 27.
Timing
The testing process commenced after the completion of exploratory tests on OBMS. These
exploratory tests are generally conducted when the build becomes ready to be tested.
RTM
Requirement Traceability Matrix (RTM)
Online Backstage Management System
Business Requirement Functional Requirement Test Cases
Business
ReqID Business Req Desc
Functional
ReqID Functional Req Desc Priority Test Case ID
BRQ01 User Role Selection FRQ001 Role Selection Screen High TC001
FRQ002
User Roles in
Dropdown High TC002
FRQ003 Password verification High TC003
BRQ02 Page Menu FRQ004 Competitors link High
TC005,
TC008,
TC009,
TC010
FRQ005 Discipline link High
TC006,
TC011,
TC012
FRQ006 Section link High
TC007,
TC013,
TC014
BRQ03 Home Page contents FRQ007 Competitor Button High
TC005,
TC008,
TC009,
TC010
FRQ008 Discipline Button High
TC006,
TC011,

5SOFTWARE ENGINEERING
TC012
FRQ009 Section Button High
TC007,
TC013,
TC014
FRQ010 Home Button Medium TC015
FRQ011 Logoff Button High TC016
FRQ012 Redirects Medium
TC004,
TC015,
TC020
BRQ04 Miscellaneous Buttons FRQ013 Enter Results Button High
TC032,
TC033
FRQ014 New Button High
TC017,
TC018,
TC019
FRQ015 Edit Button High
TC021,
TC022,
TC023
FRQ016 Print Button High TC024
FRQ017 Help Button High TC025
Test Acceptance Criteria
The respective criteria for testing to commence are the following:
1. The functional requirements should be ready before the test design phase starts
2. The test cases need to be approved as also signed-off before Test execution can start.
3. Development of application should be complete with unit testing having Passed and relevant
information shared with testers to prevent redundant defects.
4. Test environment should have application installed as well as configured and in test ready
shape.
Test Deliverables
SL# Deliverables Author Reviewer Date
1. Test Plan Test Lead Business
Analyst sign-
29/05/2019

6SOFTWARE ENGINEERING
off
2. Functional Test
Cases
Test Team Business
Analyst sign-
off
28/05/2019
4. Weekly Status
Report
Test Team Test Lead 03/06/2019,
05/06/2019
5. Test Closure Test Lead Project
Manager
06/06/2019
Test Case Document
The test case document table includes the most relevant functional test cases for the
software application Online Backstage Management System. The testing techniques used in the
process are:
User Interface Testing
In this type of test the test cases involves examination of the interface buttons, links, tabs,
mouse clicks and other functions of application (GUI).
Usability Testing
In this type of test the test cases involve outcomes gained from repeated execution of
functionalities. These can include test cases for view pages which can be executed multiple time and
the outcome compared to check reliability of the application code.
User Acceptance Testing
In this test, the test cases include examining the application performance from the user’s
perspective. Here testers put themselves in the place of target users and try to find defects. The key
users for OBMS are Stage manager, Chairperson and Adjudicator.
Test Cases
TestCa
seID
Test
Scenario TestCase Steps Expected Result Actual Result
Pass/
Fail
Rema
rks
TC001 Validate
User
Role
dropdo
Verify
that user
is asked
to select
Click
start
applicati
on
A dialogue box
should appear
with a dropdown
menu containing
A dialogue box
appears with a
dropdown menu
containing user
Pass n/a

7SOFTWARE ENGINEERING
wn role
when
starting
eStage
applicati
on
button user roles roles
TC002 Validate
User
Role
dropdo
wn
Verify
that user
roles are
present
in role
dropdow
n
Click
start
applicati
on
button
A dialogue box
should appear
with a dropdown
menu containing
user roles
A dialogue box
appears with a
dropdown menu
containing user
roles
Pass n/a
Click on
the
arrow
below
Role
The dropown
should contain
the following
roles to choose
from - Stage
Manager,
Chairperson,
GreenRoom,
Registration,
Administrator,Ad
judicator
The dropown
contains the
following roles to
choose from -
Stage Manager,
Chairperson,
GreenRoom,
Registration,
Administrator,Ad
judicator
TC003 Validate
User
Role
dropdo
wn
Verify
that user
is asked
for
passwor
d when
signing
in as
Administ
rator
Click
start
applicati
on
button
A dialogue box
should appear
with a dropdown
menu containing
user roles
A dialogue box
appears with a
dropdown menu
containing user
roles
Pass n/a

8SOFTWARE ENGINEERING
Click on
the
arrow
below
Role
The dropown
should contain
the following
roles to choose
from - Stage
Manager,
Chairperson,
GreenRoom,
Registration,
Administrator,Ad
judicator
The dropown
contains the
following roles to
choose from -
Stage Manager,
Chairperson,
GreenRoom,
Registration,
Administrator,Ad
judicator
Select
Administ
rator
Administrator
should show up
under Role and
password field
should appear
under that
Administrator
shows up under
Role and
password field
appears under
that
TC004 Validate
Login to
Home
Page
Verify
that
users
redirecte
d to
applicati
on home
page
after
signing
in
Click Sign
in after
selecting
any of
the Roles
from
dropdow
n
The eStage
application
homepage
should open with
date and time
The eStage
application
homepage opens
showing date
and time
Pass n/a
TC005 Validate
Page
Menu
Content
s
Verify
competit
ors page
opens
from
Page
Find
page
menu to
the right
side of
home
Should direct
user to
competitors
page
Directs user to
competitors
page
Pass n/a

9SOFTWARE ENGINEERING
menu page and
click on
competit
or page
TC006 Validate
Page
Menu
Content
s
Verify
disciplin
e page
opens
from
Page
menu
Find
page
menu to
the right
side of
home
page and
click on
disciplin
es link
Should direct
user to
disciplines page
Directs user to
disciplines page
Pass n/a
TC007 Validate
Page
Menu
Content
s
Verify
sections
page
opens
from
Page
menu
Find
page
menu to
the right
side of
home
page and
click on
sections
link
Should direct
user to sections
page
Directs user to
sections page
Pass n/a
TC008 Validate
Competi
tor Page
Content
s
Verify
competit
or page
lists all
users
sorted
by last
name
Click on
competit
ors from
menu
bar or
page
menu
The competitors
page should
open and user
names should be
sorted by last
name.
The competitors
page opens and
user names are
sorted by last
name.
Pass n/a
TC009 Validate
Competi
Verify
that
Select
any of
Users with the
alphabet as start
Users with the
alphabet as start
Pass n/a

10SOFTWARE ENGINEERING
tor Page
Content
s
users
with
starting
letter of
last
name
can be
listed by
selecting
the
alphabet
the
alphabet
s from A
to Z
letter of last
name should get
listed
letter of last
name gets listed
TC010 Validate
Competi
tor Page
Content
s
Verify
details of
users are
shown
when
clicked
on a
competit
or
Click on
the one
of the
competit
ors listed
Details of the
respective
competitor
should be shown
Details of the
respective
competitor is
shown
Pass n/a
TC011 Validate
Disciplin
es Page
Content
s
Verify
disciplin
e page
shows
list of
disciplin
es for
current
event
and
location
Click on
disciplin
es link
from
menu
bar or
page
menu
The list of
disciplines for
current events
and locations
should be listed
The list of
disciplines for
current events
and locations
gets listed
Pass n/a
TC12 Validate
Disciplin
e details
Verify
details of
disciplin
Click on
any of
the
The details of the
respective
discipline should
Details of the
respective
competitor is
Pass n/a

11SOFTWARE ENGINEERING
e shown
upon
clicking
on a
disciplin
e
disciplin
es listed
be shown shown
TC013 Validate
Sections
Page
Content
s
Verify
that the
sections
page
contains
sections
in the
chosen
event
Click on
sections
link from
menu
bar or
page
menu
The list of upto
25 sections
within the
chosen event
should be
present
The list of upto
25 sections
within the
chosen event is
present
Pass n/a
TC014 Validate
Section
details
Verify
details of
a section
is
available
when
clicked
Click on
one of
the
sections
listed
within
the
event
Details of the
respective
section should
be shown
Details of the
respective
section is shown
Pass n/a
TC015 Validate
Home
button
Verify
Home
button
brings
user
back to
home
page
Click on
the
home
button
User should be
taken to the
home page
User is taken to
the home page
Pass n/a
TC016 Validate
Logoff
button
Verify
logoff
button
Click on
the
logoff
The user should
be logged out
and redirected to
The user is
logged out and
redirected to
Pass n/a

12SOFTWARE ENGINEERING
logs user
off and
redirects
to login
screen
button login screen login screen
TC017 Validate
New
button
function
ality
Verify
records
can be
added
using
'New'
button
for
competit
ors
In
competit
ors page
click on
'New'
button
A form should be
loaded asking
user to fill in the
fields
A form is loaded
asking user to fill
in the fields
Pass n/a
Click on
Save
after
respectiv
e fields
are filled
The new
competitor
should get added
The new
competitor gets
added
TC018 Validate
New
button
function
ality
Verify
records
can be
added
using
'New'
button
for
disciplin
es
In
disciplin
es page
click on
'New'
button
A form should be
loaded asking
user to fill in the
fields
A form is loaded
asking user to fill
in the fields
Pass n/a
Click on
Save
after
The new
discipline should
get added
The new
discipline gets
added

13SOFTWARE ENGINEERING
respectiv
e fields
are filled
TC019 Validate
New
button
function
ality
Verify
records
can be
added
using
'New'
button
for
sections
In
setions
page
click on
'New'
button
A form should be
loaded asking
user to fill in the
fields
A form is loaded
asking user to fill
in the fields
Pass n/a
Click on
Save
after
respectiv
e fields
are filled
The new section
should get added
The new section
gets added
TC020 Validate
cancel
button
when
adding
records
Verify
records
user is
taken to
home
page if
clicked
on
cancel
after
filling
form
In
setions
page
click on
'New'
button
A form should be
loaded asking
user to fill in the
fields
A form is loaded
asking user to fill
in the fields
Pass n/a
Click on
Cancel
after
respectiv
User should be
redirected to
home page
User is
redirected to
homepage

14SOFTWARE ENGINEERING
e fields
are filled
TC021 Validate
Edit
button
function
ality in
view
pages
Verify
edit
function
ality is
available
in
competit
ors page
Open a
view
page by
clicking
the
competit
or link
The Edit option
should be
available in the
competitors
page
The Edit option is
available in the
competitors
page
Pass n/a
TC022 Validate
Edit
button
function
ality in
view
pages
Verify
edit
function
ality is
available
in
disciplin
es page
Open a
view
page by
clicking
the
disciplin
es link
The Edit option
should be
available in the
disciplines page
The Edit option is
available in the
disciplines page
TC023 Validate
Edit
button
function
ality in
view
pages
Verify
edit
function
ality is
available
in
sections
page
Open a
view
page by
clicking
the
sections
link
The Edit option
should be
available in the
sections page
The Edit option is
available in the
sections page
Pass n/a
TC024 Validate
Print
button
function
ality
Verify
print
button
allows
printouts
when
required
Open a
view
page and
sort user
records
as
desired
User records
should get sorted
and displayed as
per conditions
applied
User records get
sorted and
displayed as per
conditions
applied
Pass n/a
Find Print icon should Print icon is

15SOFTWARE ENGINEERING
print
icon in
top right
portion
of the
view
page
be available in
top right portion
of the view page.
available in top
right portion of
the view page.
TC002
5
Validate
help
button
Verify
help
button is
present
in every
page.
Browse
pages of
eStage
applicati
on
Every page
should have the
help button
denoted by a '?'
symbol
Every page
should have the
help button
denoted by a '?'
symbol
Pass n/a
TC002
6
Validate
Registra
tion role
Verify
only
users
with
registrati
on role
can
register
record
Open a
view
page and
click on
register.
Only users
logged in as
Registration
should be able to
register new
records.
Only users
logged in as
Registration is
able to register
new records.
Pass n/a
TC002
7
Validate
Registra
tion role
Verify
only
users
with
registrati
on role
can
conduct
bulk
registrati
on
Clink on
competit
orss
page
The view page
containing list of
competitors
should open
The view page
containing list of
competitors is
openning
Pass n/a
Select Competitor/ Competitor/

16SOFTWARE ENGINEERING
competit
or or
school to
be
registere
d
School should
get selected
School gets
selected
Open
the
register
link and
and click
edit
The edit sections
should appear
and on clicking
save, bulk
registration is to
be fianlize
The edit sections
appear and on
clicking save,
bulk registration
is finalized
TC002
8
Validate
Stage
Manage
r Role
Verify
role of
Stage
manager
in
moving
competit
ors
Login as
Stage
Manager
and click
on the
move
link
User should be
taken to the
move competitor
page
User is taken to
the move
competitor page
Pass n/a
Choose
the new
section
where
the
competit
or is to
be
moved
to
The new section
should get
reflected in the
dropdown field
The new section
gets reflected in
the dropdown
field
Click on
update
button
Moving of the
competitor
should get
completed
Moving of
competitor gets
completed

17SOFTWARE ENGINEERING
TC029 Validate
Stage
Manage
r Role
Verify
role of
Stage
manager
in
withdra
wing
competit
ors
Click on
link
'Withdra
w' to
remove
competit
or
The competitor
should get
withdrawn from
the section
The competitor
gets withdrawn
from the section
Pass n/a
Check if
the the
competit
or has a
strike
through
intendin
g they do
not exist
in the
section
The competitor
should have a
strike through
denoting they
are not
competing in
that section
The competitor
has a strike
through denoting
they are not
competing in
that section
TC030 Validate
Stage
Manage
r Role
Verify
change
of
sequenc
e of
competit
ors using
'Up' link
Login as
Stage
Manager
and click
on the
up link
The competitor
should get
shifted above the
previous
competitor
The competitor
gets shifted
above the
previous
competitor
Pass n/a
TC031 Validate
Stage
Manage
r Role
Verify
change
of
sequenc
e of
competit
Login as
Stage
Manager
and click
on the
down
The competitor
should get
shifted below the
next competitor
The competitor
gets shifted
below the
previous
competitor
Pass n/a

18SOFTWARE ENGINEERING
ors using
'Down'
link
link
TC032 Validate
Chairper
son Role
Verify
chairpers
on can
enter
and edit
competit
or's
results
Login as
Chairper
son and
click on
the icon
to enter
competit
or
results
The user should
be taken to a
screen to enter
competitor
results
The user is taken
to a screen to
enter competitor
results
Pass n/a
Click on
edit
button
to enter
competit
or
results
The user should
be able to enter
competitor
results
The user is able
to enter
competitor
results
TC033 Validate
Adjudica
tor Role
Verify
adjudicat
or can
enter
and edit
competit
or's
results
Login as
adjudicat
or and
click on
the icon
to enter
competit
or
results
The user should
be taken to a
screen to enter
competitor
results
The user is taken
to a screen to
enter competitor
results
Pass n/a
Click on
edit
button
to enter
competit
or
The user should
be able to enter
competitor
results
The user is able
to enter
competitor
results

19SOFTWARE ENGINEERING
results

20SOFTWARE ENGINEERING
Gantt Chart
The following Gantt chart presents the activities conducted over the corresponding
timelines.
ID Task
Mode
Task Name Duration Start Finish Predecessors
1 OBMS Application 9 days Mon 27-05-19Thu 06-06-19
2 Test Plan 3 days Mon 27-05-19Wed 29-05-19
3 SRS Document 2 days Mon 27-05-19Tue 28-05-19
4 Test Plan Document1 day Wed 29-05-19Wed 29-05-193
5 Test Case 5 days Thu 30-05-19Wed 05-06-194
6 Interface Testing 2 days Thu 30-05-19Fri 31-05-19
7 Usability Testing 1 day Mon 03-06-19Mon 03-06-196
8 User Acceptance
Testing
2 days Tue
04-06-19
Wed
05-06-19
7
9 Budgeting 1 day? Thu 06-06-19Thu 06-06-198
S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T
20 May '19 27 May '19 03 Jun '19 10 Jun '19 17 Jun '19 24 Jun '19
Budgeting
The following budget table provides the pricing and cost incurred in conducting the test
process of the OBMS application. The overall cost amounted to a total of 750 dollars.
1st phase Test Budget
SL# Items Description Qty Cost
S01 Training
Test Course
Content - $50
S02 Consulting
Resource
Selection
Process - $100
S03 Facilities
Infrastructure
costs - $200
S04 Hardware
Physical
Equipment for
Testing 7 $150
S05
Instruction
Materials On job training - $100
S06 Software
Licenses
Licenses of
required
3 $100

21SOFTWARE ENGINEERING
applications
S07 Travel
Commuting
and inspection - $50
Total $750
Conclusion
In conclusion, the above report succeeds in clearly analyses the requirements of the
software application Online Backstage Management System performs software testing by providing
the test plan and test case documents along with Gantt chart for the complete process. The report
begins by talking about all the strategies involved in carrying out the test in the test plan while also
providing the requirement traceability matrix or RTM. Thereafter the report moves to the Test Case
section where the report explains the interface testing, usability testing and user acceptance testing
that has been conducted to prepare the test cases according to the business and functional
requirements present in the requirements traceability matrix. After talking in detail about the test
cases that have been created the report lays out the timeline with the help of the Gantt chart.
Following that the report ends by calculating and mentioning, the budgeting and pricing involved in
the software testing process.

22SOFTWARE ENGINEERING
Bibliography
Abelson, J., Li, K., Wilson, G., Shields, K., Schneider, C. and Boesveld, S., 2016. Supporting quality
public and patient engagement in health system organizations: development and usability testing of
the P ublic and P atient E ngagement E valuation T ool. Health Expectations, 19(4), pp.817-827.
Binder, R.V., 2018, April. Optimal scheduling for combinatorial software testing and design of
experiments. In 2018 IEEE International Conference on Software Testing, Verification and Validation
Workshops (ICSTW) (pp. 295-301). IEEE.
Brokman, M., Perez, D. and Gelbard, R., 2018. An Optimal Point is not Enough: The Motivation to
Cope with Complex Software Project Planning. Procedia computer science, 138, pp.705-713.
Cho, I., Kim, E., Choi, W.H. and Staggers, N., 2016. Comparing usability testing outcomes and
functions of six electronic nursing record systems. International journal of medical informatics, 88,
pp.78-85.
Hui, Z.W., Huang, S., Chen, T.Y., Lau, M.F. and Ng, S., 2017, October. Identifying failed test cases
through metamorphic testing. In 2017 IEEE International Symposium on Software Reliability
Engineering Workshops (ISSREW) (pp. 90-91). IEEE.
Nidagundi, P. and Novickis, L., 2016. Introduction to lean canvas transformation models and metrics
in software testing. Applied Computer Systems, 19(1), pp.30-36.
Pagulayan, R.J., Steury, K.R., Fulton, B. and Romero, R.L., 2018. Designing for fun: User-testing case
studies. In Funology 2 (pp. 419-433). Springer, Cham.
Pandit, P. and Tahiliani, S., 2015. AgileUAT: A framework for user acceptance testing based on user
stories and acceptance criteria. International Journal of Computer Applications, 120(10).
Pinto, V.H.S.C., Oliveira, R.R., Vilela, R.F. and Souza, S.R., 2018. Evaluating the User Acceptance
Testing for Multi-tenant Cloud Applications. In CLOSER (pp. 47-56).
Rahman, M. and Gao, J., 2015, March. A reusable automated acceptance testing architecture for
microservices in behavior-driven development. In 2015 IEEE Symposium on Service-Oriented System
Engineering (pp. 321-325). IEEE.
Sonderegger, A., Schmutz, S. and Sauer, J., 2016. The influence of age in usability testing. Applied
Ergonomics, 52, pp.291-300.

23SOFTWARE ENGINEERING
Vos, T.E., Kruse, P.M., Condori-Fernández, N., Bauersfeld, S. and Wegener, J., 2015. Testar: Tool
support for test automation at the user interface level. International Journal of Information System
Modeling and Design (IJISMD), 6(3), pp.46-83.