ICT2622
Assignment 03
Unique No: 739655
Due 5 August 2025
,ICT2622
Assignment 3
Unique No: 739655
05 August 2025
Visuals & Case Diagrams provided
Question 1
1.1 What Should Be the Primary Objective of Each Iteration?
The primary objective of each iteration is to deliver a working, tested portion of the
system that contributes to the overall solution. This aligns with iterative development
principles where each increment is functional and customer-focused, not just partially
complete code. It applies because real-world feedback during each cycle allows the
team to correct course and refine the system progressively.
For example, in a public transport ticketing system, delivering a QR-code scanning
feature in the first iteration allows early validation from commuters and conductors. This
confirms not only technical feasibility but also usability in everyday conditions. The
objective isn't just partial delivery—it’s meaningful progress that users can evaluate and
the team can build upon.
1.2 State Any Two Benefits of Iterative Development
Risk management is a key benefit because each cycle surfaces potential problems
early. This is important since risks related to misunderstood requirements or technical
feasibility can be addressed before they escalate. For instance, if a payment gateway
integration fails during the first iteration of a shopping app, the issue is contained and
repairable before the full launch.
Adaptability is another benefit. Iterations support the incorporation of changing
stakeholder needs without overhauling the entire project plan.
, This is especially valuable in dynamic environments where user expectations evolve
quickly. If a logistics system originally planned only for desktop use suddenly needs
mobile access, the requirement can be introduced in a future iteration, preserving
previous progress.
1.3 What Is the Purpose of User Acceptance Testing?
User Acceptance Testing (UAT) verifies whether the system fulfills real-world business
requirements as interpreted by the end users. This is the correct application of testing
because it focuses not only on technical correctness but on fitness for purpose. It
ensures the product works under realistic conditions and meets users’ expectations.
For instance, a hospital information system may pass all internal tests, but UAT might
reveal that doctors find the patient record interface too complex, leading to delays
during emergencies. This outcome shows why UAT is essential—it validates usability
and relevance before deployment, reducing the risk of failure in actual usage.
Assignment 03
Unique No: 739655
Due 5 August 2025
,ICT2622
Assignment 3
Unique No: 739655
05 August 2025
Visuals & Case Diagrams provided
Question 1
1.1 What Should Be the Primary Objective of Each Iteration?
The primary objective of each iteration is to deliver a working, tested portion of the
system that contributes to the overall solution. This aligns with iterative development
principles where each increment is functional and customer-focused, not just partially
complete code. It applies because real-world feedback during each cycle allows the
team to correct course and refine the system progressively.
For example, in a public transport ticketing system, delivering a QR-code scanning
feature in the first iteration allows early validation from commuters and conductors. This
confirms not only technical feasibility but also usability in everyday conditions. The
objective isn't just partial delivery—it’s meaningful progress that users can evaluate and
the team can build upon.
1.2 State Any Two Benefits of Iterative Development
Risk management is a key benefit because each cycle surfaces potential problems
early. This is important since risks related to misunderstood requirements or technical
feasibility can be addressed before they escalate. For instance, if a payment gateway
integration fails during the first iteration of a shopping app, the issue is contained and
repairable before the full launch.
Adaptability is another benefit. Iterations support the incorporation of changing
stakeholder needs without overhauling the entire project plan.
, This is especially valuable in dynamic environments where user expectations evolve
quickly. If a logistics system originally planned only for desktop use suddenly needs
mobile access, the requirement can be introduced in a future iteration, preserving
previous progress.
1.3 What Is the Purpose of User Acceptance Testing?
User Acceptance Testing (UAT) verifies whether the system fulfills real-world business
requirements as interpreted by the end users. This is the correct application of testing
because it focuses not only on technical correctness but on fitness for purpose. It
ensures the product works under realistic conditions and meets users’ expectations.
For instance, a hospital information system may pass all internal tests, but UAT might
reveal that doctors find the patient record interface too complex, leading to delays
during emergencies. This outcome shows why UAT is essential—it validates usability
and relevance before deployment, reducing the risk of failure in actual usage.
