CSIS 641
SOFTWARE DEVELOPMENT LIFE CYCLE: QUALITY ASSIGNMENT INSTRUCTIONS
OVERVIEW
Metrics, measures to test software quality, can be used throughout the modeling, design, and
testing process. In this Software Development Life Cycle: Quality Assignment, you will
develop metrics at different points in the software development process. To ensure the software
meets requirements, you will build testing requirements and a testing guide. Mobile applications
use the basic principles for all software testing. The unique nature of mobile apps includes the
consideration of specialized issues. Therefore, this Software Development Life Cycle: Quality
Assignment simulates the quality assurance and testing of a mobile application.
INSTRUCTIONS
1. Metrics. Recommend and describe metrics for the church mobile app:
a. 5 requirements model metrics
b. 5 user interface design metrics
c. 5 testing metrics
2. Testing Guide. Develop a testing guide for the church mobile app. The guide should
provide language that you have learned in this course. Begin with an outline of topics
and then narrow to an appropriate level of detail useful to a tester. Create a
“publishable” guide that conforms to current APA style.
Answer the following questions in a document. Include appropriate headings in your document.
Your Software Development Life Cycle: Quality Assignment document should meet the
following criteria:
Contain appropriate headings
At least 5 pages excluding the title page, abstract, and reference page
APA Style
At least 3 citations
Acceptable citations include the textbook, the Bible, and scholarly books and articles
Note: Your assignment will be checked for originality via the Turnitin plagiarism tool.
1
Software Development Life Cycle: Quality Assignment
Name
Course Name
Course Number
Professor
Date
2
Abstract
Testing is essential in application development, and a testing plan ensures a seamless
testing process. Identifying specific application metrics helps guide what the testing team will
look for during the testing process. Requirements model metrics that will be used for the
mobile church application are availability, compatibility, video and audio sermon
capabilities, high performance, and security metrics. The user interface design metrics for the
mobile church application include ease of usability, compatibility, user-friendliness,
attractiveness, and high performance. The testing metrics include User interface design,
compatibility, security, performance, and reliability testing (Biørn-Hansen et al., 2020). The
testing guide will help the testing team check if the mobile church application meets the
requirements metrics through steps that will help with adequate testing. The measures include
identifying testing needs, deciding the testing to be performed, deciding the devices to be
used for testing, choosing between emulators and simulators, creating test cases, tracking and
managing the defects, and documenting the whole process.
3
Metrics
Requirements Model Metrics
The mobile church application should always be available, where it continuously runs
with little unnoticeable or no interruptions. The availability requirement ensures that the
application functions correctly and meets all the business requirements. Availability
requirement is determined by specific KPIs like the downtime and uptime allowed for the
application (Kaur, 2020). Another requirement model is that the application should have
video sermon capabilities where a user can access the sermon recordings. The sermons
should also be available in audio format, allowing users to listen to the sermons while doing
other things (Punchoojit & Hongwarittorrn, 2017). This allows the users to access the
sermons from anywhere at any time.
Another requirement is the mobile church application should be compatible with the
different operating systems of the various mobile phones enabling users with the different
types of phones (Kaur, 2020). The compatibility should be according to hardware
specifications, operating system, and browser compatibility (Kaur, 2020). The mobile church
application should provide a whole user experience on all the various mobile phone operating
systems. High performance is a requirement for the model where the mobile church
application should work smoothly even with man users using the application simultaneously.
The application should hold a lot of transactions at the same time without affecting the
response time of each user (Kaur, 2020).
Another requirement is a security feature because people will be using the application
to make donations and offerings; hence the mobile application should have security features
that will help to protect users' payment details. Security features are essential because the
application will also store other personally identifiable information about the congregation;
hence protecting this information is needed (Kaur, 2020). Security for the mobile church
4
application may look unimportant, but hackers are accelerating their efforts to acquire
consumers' personally identifiable data, and a church application may be a target. The
security requirement should focus on the different security postures of the various operating
systems. Some of the security requirements that will be required include encryption,
authentication, and anti-virus (Kaur, 2020).
User Design Interface Metrics
The user design interface of the mobile church application should be easy to use to
ensure that anybody can use the application with ease. Ease to use provides that users are
engaged; since this is a church application, people are required to be engaged. Specific
mobile phones and operating systems have different user design specifications, like the text
size and the various buttons and controls (Hertzum, 2020). Screen size and compatibility are
essential because people have various phones; if the screen size is too small or too big, it will
affect the user experience. The user interface should be user-friendly, where the users do not
have difficulty looking for the application's features (Hertzum, 2020).
There are some specifications about where certain buttons should be, how they look,
and their names which are standard for most mobile applications making it easy for the users
to identify the different features of the application. The application should be attractive to the
user because a tedious application does not encourage users to use it (Hertzum, 2020). The
attractiveness of an application promotes engagement; however, the application should not
use too many colors that may make the application look disorganized discouraging people
from using it. Another user interface design metric is a high performance, where the
application should return user requests as soon as the user has made the request. Long
response time may cause the user to be impatient, leading to them abandoning the request and
possibly using the application (Hertzum, 2020).
Testing Metrics
5
The application's compatibility across all the mobile operating systems should be
tested to ensure that it provides its users full application capabilities. Compatibility testing
should include the different operating system versions available to ensure the application
capabilities are available for all mobile phones (Biørn-Hansen et al., 2020). User interface
design testing checks if the application correctly displays on the different mobile phones and
their screen sizes. User interface design testing checks how the application captures the user's
request and relays the response to the user. Security testing will check if the mobile church
application has the necessary security measures to protect users' data. Security testing checks
for any vulnerabilities that hackers may use to access users' data, ensuring the measures
implemented are sufficient to keep the data safe (Biørn-Hansen et al., 2020).
Performance testing will help check if the mobile church application meets the
performance requirements. Performance testing will check if the application can handle many
requests simultaneously without it being slow, affecting the user experience. Performance
testing checks the application's speed of returning user requests and how fast the application
opens (Biørn-Hansen et al., 2020). Reliability testing will help check if the application is
available at all times and if it does not frequently crash. Reliability testing checks for the
number of defects the application has that may affect the functioning of the application
(Biørn-Hansen et al., 2020). It checks how long an application may last without crashing or
interruptions and how well it works according to the specific KPIs.
Testing Guide
The testing of the mobile application involves checking an application's usability,
functionality, and user experience (Punchoojit & Hongwarittorrn, 2017). Mobile application
testing is a process that developers do to review the application's quality and if it meets the
requirements. Testing is quite expensive, but many companies are now choosing to test the
application at the early development stages to reduce testing efforts at the end of the project,
6
making the project more costly (Punchoojit & Hongwarittorrn, 2017). Testing for the mobile
church application includes the following steps: identifying testing needs, deciding the testing
to be performed, deciding devices to be used for testing, choosing between emulators and
simulators, creating test cases, tracking and managing the defects, and documenting the
whole process.
The first stage is to identify the testing needs, where the testers decide what they will
test in the mobile church application, checking if all the metrics have been met. Here the
testers have to determine the scope of the testing process, what they aim to achieve, and the
test coverage. The scope of testing the application includes checking the application's
mobility, interoperability, security, and functionality (Punchoojit & Hongwarittorrn, 2017).
This ensures that the testing process is focused and the team knows their roles. The second
step is identifying the testing to be performed according to the testing needs. In this stage, the
various metrics that will be used to check the quality of the application are identified, which
will guide the testers on what to do (Punchoojit & Hongwarittorrn, 2017).
The third stage is to decide on devices to be used for testing where the strategy is and
the device to be tested. The testers should determine the mobile devices' resolutions and
operating systems in which they want the mobile church application to function. After
identifying the mobile device's features, the next step is choosing whether to test the mobile
church application with emulators or simulators. Emulators and simulators can copy how
mobile devices work and check how the application will work in real-time (Bordi, 2018).
Emulators are the same as the mobile device, including the hardware components, while a
simulator is a virtual tool that imitates how the application will work for the mobile device
(Bordi, 2018).
Testing the mobile church application using real mobile devices will be expensive
hence the need to use simulators and emulators. Using emulators or simulators depends on
7
the specific application needs, what the team aims to accomplish, and the type of
infrastructure the client uses (Bordi, 2018). Emulators are best suitable for debugging the
application, and one can modify the application; however it may take a lot of time to get
results. Simulators create an identical environment to the device's operating system, enabling
the team to test if the application matches the device's specific features (Bordi, 2018).
The fifth step is to create test cases which will be used to ensure all the critical aspects
of the testing are covered. The functionality determines the test cases that the application
should have and the tools that will be used to test the mobile church application (Bordi,
2018). This stage identifies the tools needed during testing to make the process fast and
effective. Here the tester can choose whether to automate the testing process or execute the
testing manually. Automation or manual execution depends on the testing needs, scope, and
time available before the application is released to the market (Bordi, 2018).
The next step is to track and manage the defects according to the mobile church
application and according to the test cases formed. The test cases will help the tester identify
the application's flaws and solve them to ensure it works smoothly (Bordi, 2018). Testing
should be done from the early stages of development and often to identify defects and solve
them as soon as they are identified. Solving the defects soon helps to reduce costs for testing
the application compared to identifying the testing at the last stages of the application
development (Bordi, 2018).
Documenting the whole process is the final step of testing, where the entire process
should be written as a report. The report should include the passed and failed tests, the defects
identified, those solved, and any other remarks that the testers may have towards the
developers (Bordi, 2018). Documenting the whole process is essential because it ensures that
all defects are identified, helping to make tracking easier and justify the decisions made
8
during the testing process. The document will assist with future decision-making because it
will help make an informed decision based on past experiences.
9
References
Biørn-Hansen, A., Rieger, C., Grønli, T. M., Majchrzak, T. A., & Ghinea, G. (2020). An
empirical investigation of performance overhead in cross-platform mobile
development frameworks. Empirical Software Engineering, 25(4), 2997-3040.
Bordi, K. (2018). Overview of test automation solutions for native cross-platform mobile
applications.
Hertzum, M. (2020). Usability Testing: A Practitioner's Guide to Evaluating the User
Experience. Synthesis Lectures on Human-Centered Informatics, 13(1), i-105.
Kaur, S. (2020). Software Testing for Mobile Applications. Retrieved from
https://www.ijresm.com/Vol.3_2020/Vol3_Iss2_February20/IJRESM_V3_I2_141.pdf
Punchoojit, L., & Hongwarittorrn, N. (2017). Usability studies on mobile user interface
design patterns: a systematic literature review. Advances in Human-Computer
Interaction, 2017.
OUTLINE
SOFTWARE DEVELOPMENT LIFE CYCLE: QUALITY ASSIGNMENT
Thesis statement: Testing is essential in application development, and a testing plan ensures
a seamless testing process. Identifying specific application metrics helps guide what the
testing team will look for during the testing process. Requirements model metrics that will be
used for the mobile church application are availability, compatibility, video and audio sermon
capabilities, high performance, and security metrics. The user interface design metrics for the
mobile church application include ease of usability, compatibility, user-friendliness,
attractiveness, and high performance. The testing metrics include User interface design,
compatibility, security, performance, and reliability testing. The testing guide will help the
testing team check if the mobile church application meets the requirements metrics through
steps that will help with adequate testing. The measures include identifying testing needs,
deciding the testing to be performed, deciding the devices to be used for testing, choosing
between emulators and simulators, creating test cases, tracking and managing the defects, and
documenting the whole process.
I. Abstract
II. Metrics
A. Requirements Model Metrics
B. User Design Interface Metrics
C. Testing Metrics
III. Testing Guide
IV. References
