ICT508-QMP-2
docx
keyboard_arrow_up
School
Murdoch University *
*We aren’t endorsed by this school
Course
508
Subject
Information Systems
Date
Nov 24, 2024
Type
docx
Pages
6
Uploaded by ConstablePantherPerson858
Assignment 2 - QMP
EduStream
1
PROJECT TESTING
1.1
Introduction to Project Testing
The detailed project testing approaches, strategies, and techniques are explained in the
associated Test Plans.
However, the general principles that are applicable to this project
include the information provided in the following subsections.
The table in Appendix 1 also
maps how key functional and non-functional tests will be implemented during the project.
1.1.1
Functional Testing
It is a software testing method where software testing is carried out against functional
requirements. Functional testing tests each software functionality by providing appropriate
input and verifying the output against the functional requirement. The following are the key
functional tests that will be applied within the EduStream project:
Unit Testing:
Unit testing refers to the software testing phase where developers examine separate sections
of software, either manually or through automation. The primary objective of unit testing is to
confirm that each software component functions as intended.
For instance, in the EdMI project, DemSet should evaluate the User Interfaces. An example
of a module might be the login page. During unit testing, DemSet might assess individual
features like whether the username input accepts specific characters or if the password input
conceals the entered password with typical obscured characters like black dots.
Integration Testing:
Integration testing involves merging individual units and evaluating them as collective groups
or modules. This testing level aims to identify any discrepancies when individual components
interact or function collectively.
Continuing the previous example, while unit testing focused on singular components,
integration testing might examine the entire login module, ensuring that all its elements, like
the username, password, and "remember me" options, function harmoniously.
System Testing:
Murdoch University
Page 1
Assignment 2 - QMP
EduStream
Once every sub-group has cleared the Integration Testing phase, they are assembled to
undergo System Testing. This comprehensive testing phase evaluates the entire system,
ensuring that all components function harmoniously.
The EduStream system includes testing the integrated software and processes to see if it
meets the required specifications. For example, the system testing would investigate whether
users are accurately redirected to the homepage after a user logs in if the displayed content is
pertinent, and whether any inconsistencies or errors emerge.
Acceptance Testing:
Acceptance Testing is a comprehensive system examination performed by the end users. The
primary focus here is on ensuring that what's delivered aligns with the organisation's initial
specifications rather than on the system's technical intricacies, which should have been
addressed in earlier test stages.
For the EduStream system, this will encompass methods like black box testing, alpha and
beta tests, operational acceptance evaluations, and contract tests. These assessments will be
executed by the final gaming and educational video platform users, ensuring that the system
adheres to the client's expectations and requirements.
1.1.2
Non-Functional Testing
Non-Functional Testing represents one of the two primary Quality Control (QC) testing
divisions. It assesses the system's efficiency in executing its designated tasks. Specifically, it
evaluates the system's performance, reliability, and maintainability.
The Non-Functional Testing approach may encompass the following:
Availability Testing:
This evaluates how consistently the system is operational throughout its lifecycle (i.e., its
reliability to function when required). For instance, with EduStream, this would involve
testing the Game Server's readiness to handle Client demands.
Compatibility Testing:
This assesses how well the system aligns with newer and older system components versions.
In the context of EduStream, compatibility tests would be crucial in examining the Client
Software against anticipated Windows releases while ensuring compatibility with preceding
Windows versions.
Murdoch University
Page 2
Assignment 2 - QMP
EduStream
Compliance Testing:
This ensures that the system aligns with relevant standards and mandates for individual
components or the entire system. EduStream would require a compliance test of its Client
Database against the Privacy Act 1988 (Cth) requirements to ensure that it meets its legal
obligations in this regard.
Configuration Testing:
This ensures the system's components align with the necessary configuration criteria to
function as intended. As a case in point, EduStream would need to validate the TCP/IP
protocol setup to verify that the Client Application and different system servers are
communicating appropriately.
Interoperability Testing:
This assesses the capability of different system elements to function cohesively with one
another.
Security Testing:
This involves a set of examinations to gauge the system's vulnerability to potential security
breaches. Such testing would be especially vital for EduStream's Client Database, where
client personal details are kept. Given the protection mandates of the Privacy Act 1988,
unauthorised access could pose severe repercussions for the company.
Performance testing:
Performance testing evaluates a system's efficiency in fulfilling user needs and behaviour
under operating scenarios. This encompasses various types of tests:
Load Testing checks the system under realistic demands.
Stress Testing pushes the system to its limits to identify its breaking point.
Endurance Testing gauges the system's sustained capacity to manage a continuously
expected workload.
Spike Testing examines the system's reaction to sudden and drastic changes in load or
demand.
Usability Testing:
Murdoch University
Page 3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Assignment 2 - QMP
EduStream
This assesses how user-friendly and intuitive the system is for its users. For instance,
EduStream must conduct usability evaluations on components like the Web-Front-End to
ensure a smooth user experience.
1.2
Practical Implementation
1.2.1
Overview of the Testing Regime for the Client Software
As an example of the practical implementation of this approach, this section outlines the
testing regime that will be applied to develop the Client Software (Workstream 2).
Unit Testing:
For the Client Software created by StreamTech, it's essential to test the software's
compatibility across various platforms and operating systems. This requires planning to cover
all potential hardware-environment combinations. The testing will be conducted in Sydney at
StreamTech's headquarters, supervised by their Project Manager for the Client Software
Team. Results will be communicated to the EduStream Project Office in Perth. The testing
will look for software defects and evaluate compatibility and usability due to diverse
platforms and the software's role in user experience. To execute these tests, specific hardware
and operating systems will be provided to StreamTech. Cost-saving measures include using a
single Android and Apple phone for their respective OS tests and a high-spec computer to
simulate both Windows and Apple operating systems. TV simulator software will replicate
Smart TV operating systems. If testing is delayed, more computers might be supplied by
EdMI. The testing will commence after StreamTech completes the code in the first week of
November.
Integration Testing:
The Client Software testing phase is pivotal as it broadens the testing scope to encompass all
interconnected system components. Specifically, the testing will evaluate how the Client
Software interacts with the Web-Front-End, Client Database, and Security protocols set by
DemSet. To successfully execute Integration Testing for the Client Software sub-group, a
collaborative effort between StreamTech in Sydney, DemSet in Melbourne, and EdMI in
Perth requires meticulous planning and clear communication. The lead Project Managers and
the development teams for each component (Client Software, Client Database, Web) will
coordinate this effort around mid-November. This timeline ensures that Unit Testing for the
Client Software and Client Database can be completed in early November.
System Testing:
Murdoch University
Page 4
Assignment 2 - QMP
EduStream
It involves evaluating the complete system ensuring every component has successfully
undergone both Unit and Integration Testing. With Perth being the initial system node, the
components of the Test Environment will stay in their original places, serving as a secondary
testing node. It's imperative to ensure that all equipment needed for a full CDN setup is at
hand to facilitate this System Testing. All project teams, their Project Managers and the
EduStream Project Office will collaboratively coordinate non-functional testing, covering
areas such as Availability, Compatibility, Compliance, Configuration, Interoperability,
Security, Performance, and Usability.
Acceptance Testing:
This testing phase will be executed in a fully functional environment that includes CDN
nodes, data centres, and client applications accessible to EdMI's clients participating in the
Beta. While it will encompass non-functional aspects such as Availability, Compatibility,
Compliance, Configuration, Interoperability, Security, Performance, and Usability, there will
be a specific focus on Load Testing, Stress Testing, Endurance Testing, and Spike Testing.
Murdoch University
Page 5
Project Management Plan (QMP) – Appendix 1
EduStream
Availability
Compatibility
Compliance
Configuration Interoperability Recoverability
Security
Performance
Regression
Usability
Unit
Hardware
ü
ü
ü
?
?
ü
ü
?
?
Software
(Including interfaces)
ü
ü
ü
ü
ü
ü
ü
ü
ü
Network/Connectivity
ü
ü
ü
ü
ü
?
Integration
Hardware
ü
ü
ü
ü
ü
ü
Software
(Including interfaces)
ü
ü
ü
ü
ü
ü
ü
ü
Network/Connectivity
ü
ü
ü
ü
System
Hardware
ü
ü
ü
ü
ü
ü
ü
Software
(Including interfaces)
ü
ü
ü
ü
ü
ü
ü
ü
ü
Network/Connectivity
ü
ü
ü
ü
ü
ü
ü
Acceptance
Hardware
ü
ü
ü
ü
ü
Software
(Including interfaces)
ü
ü
ü
ü
ü
ü
ü
ü
Network/Connectivity
ü
ü
ü
ü
ü
ü
ü
The symbols in the cells of this table mean the following:
or Yes = This type of test would generally be applied for this element of the testing regime
? = This type of test may be applied to this element of the testing (but it will be situation-dependent)
Blank = This type of testing is typically
not
done for this type of functional testing.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help