IT 304 Test Plan
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
304
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
11
Uploaded by msheba08
Bathsheba Myers
IT 304 6-3 Create a System Test Plan
Dr. Kazi Zunnurhain
October 5, 2023
1
Test Plan
Test Plan Components
Responses
Test Procedures and Strategy
What kind of tests will be completed during
the testing phase? What are the tasks that
need to be completed in the testing phase?
How will each testing task be completed?
Testing conducted by end-users or clients to
determine if a system meets their needs and
requirements is referred to as User
Acceptance Testing (UAT).
Task of Testing: The objective is to ensure
that the system satisfies user demands and
anticipations.
Approach for Completion: Members
constituting end-users, namely patients,
receptionists, nurses, hospital doctors, and
pharmacologists will carry out the User
Acceptance Test. They will execute usual
errands such as scheduling appointments,
synthesizing patient records, data inputting,
and managing prescriptions. The development
of test scenarios and cases will authenticate
absolute Testing.
Integration Testing:
Testing Task: To ensure that different system
components and interfaces work together
seamlessly.
How It Will Be Completed: Test data
representing various patient scenarios will be
used to assess how well the system integrates
with different data sources and external
systems, such as pharmacy interfaces.
Security Testing:
Testing Task: Evaluating the system's security
mechanisms to protect patient data.
How It Will Be Completed: Ethical hacking,
penetration testing, and vulnerability
assessments will be conducted to identify
potential security weaknesses. Access control
and authentication mechanisms will be
thoroughly tested to ensure data privacy
(STEEL KIWI, 2023).
Performance Testing:
Testing Task: Assessing system performance
2
Test Plan Components
Responses
under different load conditions.
How It Will Be Completed: The system will
be subjected to various scenarios, such as
peak usage times, to evaluate its response
time, resource utilization, and scalability.
Load testing tools will simulate multiple users
accessing the system simultaneously.
Regression Testing:
Testing Task: Ensuring that new updates or
changes do not introduce defects into
previously working functionalities.
How It Will Be Completed: A suite of test
cases will be executed to verify that existing
features remain intact after system updates or
enhancements. Automated testing scripts can
help expedite this process.
Usability Testing:
Testing Task: Assessing the user-friendliness
of the system's interface.
How It Will Be Completed: End-users,
including patients and healthcare
professionals, will provide feedback on the
system's ease of use. Usability testing
sessions will be conducted, and user feedback
will be collected.
Data Privacy Testing:
Testing Task: Ensuring that only authorized
individuals can access specific patient
records.
How It Will Be Completed: Test scenarios
will involve attempting to access patient data
without proper authorization. The system's
access control mechanisms will be rigorously
tested.
Functional Testing:
Testing Task: Validating that each functional
requirement outlined in the system
specifications is met.
How It Will Be Completed: Test cases
corresponding to each functional requirement
will be executed, covering features like
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
Test Plan Components
Responses
patient check-in, data recording, prescription
processing, and appointment scheduling.
IT Personnel
What kind of professional staff will be needed
to complete each task?
User Acceptance Testing (UAT):
IT Personnel Needed: End-users, including
patients, receptionists, nurses, doctors, and
pharmacists.
Roles and Responsibilities: End-users will
participate in UAT to ensure that the system
meets their needs and expectations. They will
provide feedback, identify issues, and validate
the system's usability and functionality.
Integration Testing:
IT Personnel Needed: Integration Testers,
System Administrators, and Database
Administrators.
Roles and Responsibilities: Integration testers
will focus on validating the seamless
integration of various system components and
interfaces. System and database
administrators will ensure that data flows
smoothly across the system.
Security Testing:
IT Personnel Needed: Security Analysts,
Ethical Hackers, and Penetration Testers.
Roles and Responsibilities: Security analysts
will oversee the assessment of the system's
security mechanisms. Ethical hackers and
penetration testers will simulate cyber-attacks
to identify vulnerabilities and weaknesses.
Performance Testing:
IT Personnel Needed: Performance Testers
and System Administrators.
Roles and Responsibilities: Performance
testers will design and execute tests to
evaluate the system's performance under
different load conditions. System
administrators will monitor system resources
during Testing.
Regression Testing:
IT Personnel Needed: Quality Assurance
(QA) Testers and Test Automation Engineers.
4
Test Plan Components
Responses
Roles and Responsibilities: QA testers will
ensure that existing functionalities remain
intact after system updates. Test automation
engineers may develop automated scripts for
regression testing.
Usability Testing:
IT Personnel Needed: Usability Testers, User
Experience (UX) Designers.
Roles and Responsibilities: Usability testers,
who may include patients and healthcare
professionals, will assess the user-friendliness
of the system's interface. UX designers may
provide input on interface improvements.
Data Privacy Testing:
IT Personnel Needed: Data Privacy
Specialists and Security Analysts.
Roles and Responsibilities: Data privacy
specialists will oversee Testing to ensure that
patient data is protected. Security analysts
may also be involved in assessing access
control mechanisms.
Functional Testing:
IT Personnel Needed: QA Testers, Business
Analysts.
Roles and Responsibilities: QA testers will
validate that each functional requirement is
met. Business analysts may be consulted to
ensure that business processes are properly
tested.
Task Dependencies and Timeline
When will the tasks be completed, and what
are the task dependencies?
User Acceptance Testing (UAT):
Timeline: UAT will commence after
Integration Testing is completed.
Task Dependencies: Dependent on the
successful completion of Integration Testing
to ensure that the integrated system functions
as expected.
Integration Testing:
Timeline: Integration Testing will start after
the Security Testing environment is set up.
Task Dependencies: Dependent on having a
secure environment ready for Testing to
5
Test Plan Components
Responses
prevent security vulnerabilities from being
introduced during integration.
Security Testing:
Timeline: Security Testing should begin after
the environment is set up for Performance
Testing.
Task Dependencies: Dependent on the
Performance Testing environment being
available for security assessment to ensure
system vulnerabilities are identified and
addressed.
Performance Testing:
Timeline: Performance Testing should start
after Regression Testing is completed.
Task Dependencies: Dependent on Regression
Testing to ensure that new changes do not
negatively impact existing functionalities.
Regression Testing:
Timeline: Regression Testing should start as
soon as the system is stable enough for
Testing.
Task Dependencies: Dependent on the system
being stable enough for Testing to avoid
unnecessary testing cycles.
Usability Testing:
Timeline: Usability Testing can run
concurrently with Functional Testing but
should be completed before Data Privacy
Testing.
Task Dependencies: Dependent on Functional
Testing to ensure that usability issues related
to system functionality are identified and
addressed.
Data Privacy Testing:
Timeline: Data Privacy Testing should begin
after Usability Testing is completed.
Task Dependencies: Dependent on Usability
Testing to ensure that user interface elements
related to data privacy are tested.
Functional Testing:
6
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
Test Plan Components
Responses
Timeline: Functional Testing should begin as
soon as the system is stable for Testing.
Task Dependencies: Minimal dependencies,
but the availability of a stable system is
critical.
Test Data
What test data will be gathered and collected
from completing the testing tasks?
User Acceptance Testing (UAT):
Test Data: Test data for UAT will include real-
world scenarios mimicking actual patient
interactions with the system. This may
include sample patient profiles, appointment
schedules, and medical records.
Integration Testing:
Test Data: Integration testing requires data
that represents the flow of information
between different system components.
Sample data for this phase will include data
transfers between various modules and
databases.
Security Testing:
Test Data: Security testing will involve the
use of simulated security breaches, such as
penetration testing. Test data will include
various attack scenarios to identify
vulnerabilities and assess the system's
resistance to them.
Performance Testing:
Test Data: Performance testing requires
realistic data to evaluate system
responsiveness and resource utilization. Test
data will include a range of patient data,
transaction volumes, and usage patterns.
Regression Testing:
Test Data: Regression testing will utilize a set
of predefined test cases with both valid and
invalid data to ensure that new updates or
changes do not introduce defects into
previously working functionalities.
Usability Testing:
Test Data: Usability testing will involve real
7
Test Plan Components
Responses
users interacting with the system. Test data
will include user profiles, sample tasks, and
scenarios representing common user
interactions.
Data Privacy Testing:
Test Data: Data privacy testing will focus on
ensuring that sensitive patient data is properly
protected. Test data will include various types
of patient records with sensitive information,
such as medical histories and personal
identifiers.
Functional Testing:
Test Data: Functional Testing requires a wide
range of test cases covering different
functionalities of the system. Test data will
include input data to trigger specific
functionalities and expected output data.
Reflection
What ethical decisions will you have to make
during the testing phase? (See activity prompt
for guiding questions.)
Data Privacy and Security: Ensuring the
privacy and security of patient data is
paramount. Ethical decisions may involve
determining how to anonymize or
pseudonymize patient data for testing while
protecting sensitive information from
unauthorized access. Decisions also need to
be made about who has access to what data
during Testing (Farhud & Zokaei, 2021).
Handling of Vulnerabilities: If security testing
identifies vulnerabilities or weaknesses in the
system, ethical decisions must be made
regarding how to address them. This includes
deciding whether to prioritize the fixing of
certain vulnerabilities to protect patient data
and comply with ethical obligations.
Informed Consent: In cases where real users
or patient data are involved in Testing, ethical
decisions should be made regarding informed
consent. Users and patients should be aware
that their data or interactions may be part of
the testing process, and they should have the
option to opt-out if they wish.
8
Test Plan Components
Responses
Testing Impact on Patients: Decisions
regarding the potential impact of Testing on
patient care and safety are critical. Ethical
considerations involve ensuring that testing
activities do not disrupt patient care, lead to
incorrect medical decisions, or compromise
patient safety.
Transparency: Ethical testing practices often
involve transparency. Decisions may need to
be made regarding how much information
about the testing process should be shared
with relevant stakeholders, including patients,
healthcare professionals, and regulatory
bodies.
Compliance with Regulations: Ethical
decisions include ensuring compliance with
healthcare regulations such as HIPAA (Health
Insurance Portability and Accountability Act)
and other data protection laws. Decisions will
need to be made about how to align testing
practices with legal requirements.
Non-Discrimination: Ethical Testing must
avoid discrimination based on factors like
race, gender, or age. Decisions about test data
and test scenarios should be made to avoid
bias and discrimination in the system's
functionality.
Reporting Findings: Decisions must be made
regarding how to report testing findings,
especially if vulnerabilities or ethical issues
are identified. Transparency in reporting and
taking responsible actions to address issues is
ethically important.
Resource Allocation: Ethical decisions may
involve prioritizing testing efforts based on
the potential impact on patient care and
safety. Decisions should ensure that critical
areas receive adequate attention and
resources.
9
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
Reference.
STEEL KIWI. (2023).
Privacy and Security in Healthcare: A Must-read for Healthtech
Entrepreneurs
. Steelkiwi.com. https://steelkiwi.com/blog/privacy-and-security-in-
healthcare/#:~:text=Use%20two%2Dfactor%20authentication%20to
10
Farhud, D. D., & Zokaei, S. (2021). Ethical Issues of Artificial Intelligence in Medicine and
Healthcare.
Iranian Journal of Public Health
,
50
(11).
https://doi.org/10.18502/ijph.v50i11.7600
11