Project Management: Testing Strategies, DevOps, and IFRS Track Project

This project management assignment delves into the critical aspects of software testing within the context of project management, with a specific focus on functional and non-functional testing methodologies. It begins by emphasizing the importance of requirements and action plans in initiating a project, followed by an overview of the software development process, highlighting the distinction between functional and non-functional requirements. The assignment details the purpose of functional testing, its various methods (white box, black box, usability, integration, smoke, and sanity testing), and its significance in ensuring application functionality. It then explores non-functional testing, which evaluates application competency and effectiveness under various conditions, focusing on aspects like response speed and operation time. Test scenarios are discussed, along with the impact of non-functional testing on user satisfaction and the different types of non-functional tests. The assignment also integrates DevOps, emphasizing its role in modern software development, including automated testing, continuous integration, and the need for testers to possess specific technical skills. The assignment concludes with a case study of IFRS Track Installation, including a test plan outline, introducing the project's stakeholders and items to be tested.

Running head: PROJECT MANAGEMENT
Project Management
Name of Student-
Name of University-
Author’s Note-

1PROJECT MANAGEMENT
Requirements are actually considered as the basics for starting any task or project. Action
plan is taken to collect requirement and proceed with the task accordingly. The process that is
included in software development states the main purpose of developing the application or the
system. The requirements are divided as functional requirements and non-functional
requirements (Kim et al., 2019). Functional requirement states the result that are expected from
system as well as non-functional requirement states the features that are to be included in the
application system.
Functional testing includes process in method of software development that helps in
testing the software to check that it complies with the functional requirements stated for the
application. Functional testing is needed in application development because this helps to ensure
all the functionalities for the application is fulfilled. Functional testing includes evaluating as
well as comparing all the function of the application that are included in business application.
The testing of functional requirement is done with functional specification (Banerjee &
Aggarwal, 2020). The different functional testing methods that are used are while box testing,
black box testing, usability testing, integration testing, smoke testing, and sanity testing.
The testing that are carried out in non-functional testing includes different productive
techniques of testing for evaluating as well as assessing non-functional traits for the software
application. The main reason of carrying out non-functional requirement is evaluating
competency as well as effectiveness that the application is having and those are to be considered
under variant as well as unforeseen conditions. This testing is mainly performed on the non-
functional requirement of the application system. This testing tests the speed of response for the
application, the time that the software takes to perform operation. Test scenarios are needed for
non-functional testing and the requirements that are stated by the clients.

2PROJECT MANAGEMENT
The testing for non-functional requirement mainly describes the attributes of testing the
software and are not associated with particular actions including scalability, performance,
behavior of application, and security (Lewis, 2017). The testing carried out as non-functional
testing in application development has great impact on the customer and on the user satisfaction
for the application. The readiness for the system is mainly evaluated in non-functional testing
satisfying different testing criteria that are not included in functional testing. This helps in
measuring as well as comparing results of testing as the non-functional attributes of the
application. The different testing types that are included in non-functional testing are availability
testing, compatibility testing, compliance testing, installing testing, documentation testing,
reliability testing and many others.
Functional testing is considered as an important aspects of testing as this helps in
verifying the system is ready for its release. The tests included in functional testing helps in
defining the working system in useful manner (Li et al., 2020). All the client requirements that
are specified as functional requirement are specified in functional testing. Individual pieces of
the application are tested using the functional testing feature.
The importance of carrying out non-functional testing is it helps to test the performance,
reliability, availability and other such parameters of the application. It is expected as non-
functional testing helps in increasing the efficiency, efficiency, portability and maintainability of
application. This also helps to reducing production risk and the cost of the application included
in development process. In non-functional testing, prioritizing the requirements are important.
The quality attributes for the application system are to be ensured using the non-functional
testing.

3PROJECT MANAGEMENT
In software development method of DevOps, the non-functional testing mainly includes
considerations to deploy an application successfully (Camacho, Marczak & Cruzes, 2016). The
testing process on DevOps are carried out in software development up to the delivery of the
application system. The testers developing a system using DevOps does not only focus on the
non-functional as well as on functional testing. Testing in DevOps development occurs in all the
steps and choosing the tools as well as technologies in testing system of DevOps model is much
important. With the choice of tools, ability of the organization can be evaluated in delivering the
application or the services.
DevOps include automated testing and creates an environment where the codes can be
included in the system quickly and also includes results of performance testing and security
testing before delivery of the application (Dave, Patel & Prajapati, 2018). For carrying out
DevOps testing, the testers are expected to have basic knowledge of networking and basic
scripting and python knowledge. They should also be aware with tools of performance testing
such as Gatling, JMeter and should be ready to do resilience testing and operations testing.

4PROJECT MANAGEMENT
References
Banerjee, D., Yu, K., & Aggarwal, G. (2020). Object Removal Software Test Automation. IEEE
Access.
Dave, M. S., Patel, M. H., & Prajapati, M. A. (2018). Non-functional testing in agile
development.
Kim, H. K., Yeo, H., Hwang, H. J., Ramos, C., & Marreiros, G. (2016). Effective mobile
applications testing strategies.
Lewis, W. E. (2017). Software testing and continuous quality improvement. Auerbach
publications.
Li, C. L., Xue, D. X., Wang, Y. H., Xie, Z. P., & Staehelin, C. (2020). A method for functional
testing constitutive and ligand-induced interactions of lysin motif receptor proteins. Plant
Methods, 16(1), 1-10.
Camacho, C. R., Marczak, S., & Cruzes, D. S. (2016, August). Agile team members perceptions
on non-functional testing: influencing factors from an empirical study. In 2016 11th
international conference on availability, reliability and security (ARES) (pp. 582-589).
IEEE.