Analysis of Independent Testing Approaches in Software Development

The report explores the concept of independent testing within the realm of software development. It begins by outlining different scenarios, starting with a team where a single programmer handles testing and code validation. It then progresses to a scenario where software testers work alongside programmers, often in organizations that are still refining their development processes. The report then focuses on fully independent testing, where dedicated software testers and developers operate at the same level of management. It also highlights the involvement of various specialists, such as business domain experts for usability, database developers for SQL code functionality, and security and certification testers. The report uses examples to illustrate these scenarios, including the practices of companies like Google and Oracle, emphasizing the importance of rigorous testing in complex systems to avoid significant losses. The report also includes an extensive bibliography for further reading on the topic.

Issues facing the object-oriented approach to software development
Name
Institution
Professor
Course
Date

Software development is coupled with various testing aspect. The testing aspect chosen
by a team of programmers depends on what they want to achieve from the proposed system. In
this case, the goal would be to evaluate independent testing as implemented in software
development. When working on software independent testing, it is important to note that, it is not
an instance but a range of possibilities set to evaluate the system. First, there might be no sense
of independence but a programmer within a team of developers who is mandated to test codes
from other programmers (Neto etal 2011, p. 410). A good example of such scenario is exhibited
by a small team of developers which does not need to hire software tester due to some
inefficiencies. In this case, software is not complex and team can validate their code on their
own. On the same note, software is not quite urgent and developers can take time to review their
code once they are done with code development.
Next, as software development narrows down its activities, within a team of software
development, there is group of software testers who work concurrently with programmers. Both
software development team and testers work under a development manager supervising the
entire process. An example in this case is found in organizations that have specialized in
developing software but they are yet to define their processes completely (Garousi & Mantyla
2016, p. 92-93). Tester with the group are still programmers but specialized in code validation.
They are able to identify code defects but mainly focus on functionality and security of the
software being developed.
Finally, a complete software independent testing involves a distinct team of software
testers and developers. Both project development team and software testers report at the same
level of management. This makes both teams equal and distinct in terms of their duties. With
pure independent testing, different specialists are involved. It might comprise the following

specialist in order to make sure all quality aspects are met. A business domain specialist who
makes sure system usability and friendliness is achieved (Afzal etal 2016, p. 23-24). The next
identity might be a technological expert such as database developer who evaluates SQL codes
and checks its functionality effectiveness. Other specialist who should be part of software testers
are systems security and certification testers who are meant to ensure security of the system is
given the highest priority. An example of complete independent testing is usually found in more
specialized organization that work on complex systems that every detail aspect is very important
since a single defect would result to huge losses. Mainly found in organizations such as Google
and Oracle.
Bibliography
Afzal, W., Alone, S., Glocksien, K. and Torkar, R., 2016. Software test process improvement
approaches: A systematic literature review and an industrial case study. Journal of Systems and
Software, 111, pp.1-33.
Garousi, V. and Mäntyla, M.V., 2016. When and what to automate in software testing? A multi-
vocal literature review. Information and Software Technology, 76, pp.92-117.
Neto, P.A.D.M.S., do Carmo Machado, I., McGregor, J.D., De Almeida, E.S. and de Lemos
Meira, S.R., 2011. A systematic mapping study of software product lines testing. Information and
Software Technology, 53(5), pp.407-423.