Exam (elaborations)
INF3705 Assignment 2 (COMPLETE ANSWERS) 2024 - DUE 6 September 2024
- Course
- INF3705
- Institution
- University Of South Africa
100% TRUSTED workings, explanations and solutions: For assistance contact
[Show more]
Content preview
INF3705Assignment 2
(COMPLETE
ANSWERS)
2024 - DUE 6
September 2024
, Question 1 [15 marks] Explain the difference between Development testing
and Test-driven development.
Development testing and Test-driven development (TDD) are both approaches to software
testing, but they differ in their timing, methodology, and primary objectives.
1. Development Testing:
Timing: Development testing typically occurs after the code has been written or
during the development process.
Methodology: It involves testing the software incrementally as it is being
developed. Developers write test cases to verify the correctness of individual units
or components of the software.
Objective: The primary goal of development testing is to identify and fix defects
in the code before it is released to a wider audience. It helps ensure that each
component of the software functions correctly in isolation.
2. Test-driven Development (TDD):
Timing: TDD, on the other hand, occurs before the code is written.
Methodology: In TDD, developers write test cases before they write the actual
code. These test cases define the desired behavior or functionality of the code.
The code is then written in small increments to pass these test cases.
Objective: The main objective of TDD is to drive the development process by
focusing on writing code to fulfill specific test cases. This iterative approach helps
ensure that the code meets the requirements and remains maintainable and
extensible.
In summary, development testing focuses on testing the software during or after development to
identify and fix defects, while TDD emphasizes writing test cases before writing the actual code
to drive the development process and ensure code quality from the outset.
Question 2 [09 marks] What are the strategic options for legacy system
evolution? When would you normally replace all or part of a system rather
than continue maintenance of the software?
Strategic options for legacy system evolution typically involve several approaches aimed at
modernizing or improving an existing system while considering factors such as cost, time, and
business needs. Some common strategic options include:
1. Reengineering or Refactoring:
This involves restructuring or rewriting the existing codebase to improve its
maintainability, scalability, or performance without changing its external
behavior.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying this summary from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller Solutionist. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy this summary for R46,92. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
67232 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy summaries for 14 years now