WEEK 10 Written Assignment
docx
keyboard_arrow_up
School
Bellevue University *
*We aren’t endorsed by this school
Course
521
Subject
Information Systems
Date
Jun 18, 2024
Type
docx
Pages
7
Uploaded by CorporalFlyMaster1110
WEEK 10 Written Assignment
Rakesh Saidugari
Masters in computer information systems, Bellevue University
CIS521-T301 System development and deployment (2245-1)
Robert Hettinger
May 19, 2024
To: Tim Smith
From: Rakesh saidugari
Date: 05/19/2024
Subject: Proposal for Ensuring Quality through Comprehensive Testing Strategies
Dear Tim,
Introduction
Tim Smith, the dedicated owner of Down Town Car Repair, is committed to exceeding customer
expectations through exceptional service. To align with Tim's high standards, the proposed
automation application for his business must undergo rigorous testing to ensure it meets and
surpasses all quality benchmarks. This proposal outlines the specific testing that will be
conducted, highlighting their roles in enhancing the application's quality and reliability.
1. Functional and Non-Functional Testing
a. Functional Testing
Functional testing ensures that the application functions correctly according to the specified
requirements. This type of testing involves checking various features and functionalities of the
application to ensure they work as expected. It includes:
Unit Testing
: Testing individual components or modules of the application to ensure
they work correctly in isolation (Sommerville, 2016).
Integration Testing
: Testing the interactions between different modules or components
to ensure they function seamlessly (Sommerville, 2016).
System Testing
: Testing the complete and integrated application to ensure it meets all
functional requirements (Sommerville, 2016).
User Acceptance Testing (UAT)
: Conducting tests with real users to ensure the
application meets their needs and expectations (Sommerville, 2016).
b. Non-Functional Testing
Non-functional testing evaluates aspects of the application that are not related to specific
functionalities but are crucial for the system's overall performance, usability, and reliability. This
includes:
Performance Testing
: Assessing the application's responsiveness, stability, and
scalability under various load conditions (Pressman & Maxim, 2014).
Security Testing
: Identify vulnerabilities and ensure the application is secure against
potential threats (Pressman & Maxim, 2014).
Usability Testing
: Evaluating the user interface and experience to ensure the application
is easy to use and meets user expectations (Pressman & Maxim, 2014).
Compatibility Testing
: Ensuring the application works correctly across different
devices, browsers, and operating systems (Pressman & Maxim, 2014).
Reliability Testing
: Verifying the application's ability to perform consistently over time
without failures (Pressman & Maxim, 2014).
2. White Box and Black Box Testing
a. White Box 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
White box testing, also known as precise or glass box testing, involves testing an application's
internal structures or workings. Testers can access the source code and use this knowledge to
design test cases. This approach includes:
Code Coverage Analysis
: Testing all code paths, branches, and conditions
(ISO/IEC/IEEE 29119-1:2013).
Path Testing
: Testing different execution paths through the code to ensure all possible
paths are exercised (ISO/IEC/IEEE 29119-1:2013).
Unit Testing
: Testing individual units or components based on their internal logic and
implementation (ISO/IEC/IEEE 29119-1:2013).
b. Black Box Testing
Black box testing focuses on testing the application without knowing its internal implementation.
Testers interact with the application as end-users would, based solely on the requirements and
functionality. This approach includes:
Functional Testing
: Verifying that the application behaves correctly according to the
requirements (Myers et al., 2011).
Regression Testing
: Ensuring that new changes or additions do not break existing
functionality (Myers et al., 2011).
User Acceptance Testing (UAT)
: Involving real users to validate the application against
their needs and expectations (Myers et al., 2011).
3. Integrating Testing Approaches into the Testing Strategy
To ensure the quality of the proposed application for Down Town Car Repair, the following
comprehensive testing strategy will be implemented:
a. Functional Testing Strategy
1.
Unit Testing
: Each application module, such as customer management, inventory
tracking, and billing, will undergo unit testing to ensure they function correctly in
isolation. Automated testing tools will run tests frequently and catch issues early in
development (Sommerville, 2016).
2.
Integration Testing
: Once individual modules are validated, integration testing will be
conducted to ensure they work together seamlessly. For example, integrating customer
management and billing modules will be tested to ensure accurate bill generation
(Sommerville, 2016).
3.
System Testing
: The complete application will be tested to verify that all functionalities
work as expected. Test cases will cover all user scenarios, from creating bids to tracking
inventory and generating bills (Sommerville, 2016).
4.
User Acceptance Testing (UAT)
: Real users, including Tim and a select group of
customers, will be involved in UAT to validate the application against real-world
scenarios. Their feedback will be crucial in refining the application to meet user
expectations (Sommerville, 2016).
b. Non-Functional Testing Strategy
1.
Performance Testing
: The application will be tested under various load conditions to
remain responsive and stable. This will include simulating multiple users, creating bids,
tracking inventory, and generating bills simultaneously (Pressman & Maxim, 2014).
2.
Security Testing
: Security experts will conduct vulnerability assessments and
penetration testing to identify and mitigate potential security risks. This will protect the
application against threats such as data breaches and unauthorized access (Pressman &
Maxim, 2014).
3.
Usability Testing
: The user interface will be evaluated to ensure it is intuitive and easy
to use. Usability testing sessions with real users will help identify areas for improvement,
enhancing the overall user experience (Pressman & Maxim, 2014).
4.
Compatibility Testing
: The application will be tested on different devices, browsers, and
operating systems to ensure it works correctly across various platforms. This guarantees
all users a consistent experience, regardless of their chosen device or browser (Pressman
& Maxim, 2014).
5.
Reliability Testing
: Long-term testing will ensure the application performs consistently
over time. This will involve running the application continuously and monitoring failures
or performance degradation (Pressman & Maxim, 2014).
Conclusion
By implementing a comprehensive testing strategy that includes both functional and non-
functional testing and white box and black box approaches, we will ensure that the proposed
application for Down Town Car Repair meets and exceeds Tim's expectations. This rigorous
testing process will validate the application's correctness and functionality and ensure its
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
performance, security, usability, compatibility, and reliability. Through this meticulous
approach, Tim can be confident that the application will enhance his business operations,
providing exceptional customer service.
Sincerely,
S. Rakesh.
References
Myers, G. J., Sandler, C., & Badgett, T. (2011).
The Art of Software Testing
(3rd ed.). Wiley.
Sommerville, I. (2016).
Software Engineering
(10th ed.). Pearson.
Pressman, R. S., & Maxim, B. R. (2014).
Software Engineering: A Practitioner's Approach
(8th
ed.). McGraw-Hill Education.
ISO/IEC/IEEE 29119-1:2013. (2013).
Software and systems engineering — Software testing —
Part 1: Concepts and definitions
. ISO.