Download Full Version Scripting-and-Programming-Foundations WGU Exam

Comprehensive and Detailed Explanation From Exact Extract:

In Agile software development, the process is iterative and focuses on delivering working software incrementally. According to foundational programming principles and Agile methodologies (e.g., Certiport Scripting and Programming Foundations Study Guide, Agile Manifesto), the design phase involves creating detailed plans for the software, including identifying objects (e.g., classes in object-oriented programming) to be implemented.

Agile Phases Overview:

Analysis: Defines requirements and goals (e.g., user stories, project scope).

Design: Creates detailed plans, including system architecture, data models, and objects/classes to be written.

Implementation: Writes and integrates code for the designed components.

Testing: Verifies that the implemented code meets requirements.

Option A: "Design." This is correct. During the design phase in Agile, the team translates requirements into technical specifications, often producing a list of objects (e.g., classes, modules) to be coded. For example, in an object-oriented project, the design phase identifies classes like User, Order, or Product.

Option B: "Testing." This is incorrect. Testing verifies the implemented code, not the creation of a list of objects.

Option C: "Implementation." This is incorrect. Implementation involves writing the code for the objects identified during the design phase.

Option D: "Analysis." This is incorrect. Analysis focuses on gathering requirements and defining what the system should do, not specifying technical objects.

Certiport Scripting and Programming Foundations Study Guide (Section on Software Development Life Cycle: Agile).

Agile Manifesto: “Principles of Agile Development”

Sommerville, I., Software Engineering, 10th Edition (Chapter 4: Agile Software Development).

Comprehensive and Detailed Explanation From Exact Extract:

In Agile, the analysis phase (often part of sprint planning or backlog refinement) involves gathering and refining requirements, typically as user stories or features, based on stakeholder input. According to foundational programming principles and Agile methodologies (e.g., Certiport Scripting and Programming Foundations Study Guide, Agile Manifesto), the analysis phase focuses on defining what the system should do.

Agile Analysis Phase:

Identifies and prioritizes requirements, often incorporating customer feedback.

Produces user stories or feature lists (e.g., “add new animation effects”).

Option A: "Deciding that new capabilities in the animation application will be written as functions without the need for any new objects." This is incorrect. This decision involves technical design (e.g., choosing procedural vs. object-oriented approaches), which occurs in the design phase, not analysis.

Option B: "Sending the application to customers for additional evaluation after new features are added." This is incorrect. This occurs during testing or deployment phases (e.g., sprint review or user acceptance testing), not analysis.

Option C: "Deciding to add five new capabilities to the animation application based on customer feedback." This is correct. In Agile, analysis includes refining the product backlog by adding new features (capabilities) based on customer feedback, such as new animation effects or tools.

Option D: "Writing the code for five new capabilities." This is incorrect. Writing code occurs during the implementation phase, not analysis.

Certiport Scripting and Programming Foundations Study Guide (Section on Agile Analysis).

Agile Manifesto: “Customer Collaboration”

Cohn, M., User Stories Applied (Chapter 2: Agile Requirements).

The algorithm depicted in the image is a simple loop that iterates 5 times. Each iteration multiplies the current value of i by 2 and adds it to the variable sum. The loop starts with i equal to 1 and sum equal to 0. Here’s the breakdown:

First iteration: i = 1, sum = 0 + (1 * 2) = 2

Second iteration: i = 2, sum = 2 + (2 * 2) = 6

Third iteration: i = 3, sum = 6 + (3 * 2) = 12

Fourth iteration: i = 4, sum = 12 + (4 * 2) = 20

Fifth iteration: i = 5, sum = 20 + (5 * 2) = 30

However, the algorithm includes a condition that checks if sum is greater than 10. If this condition is true, the algorithm outputs the value of i and stops. This condition is met during the third iteration, where sum becomes 12. Therefore, the algorithm outputs the value of i at that point, which is 3.

 A student’s grade point average (GPA) is a numerical representation that typically includes a decimal to account for the precision of the average (e.g., 3.75). Therefore, it should be declared as a floating-point data type to accommodate the decimal part. Since a student’s GPA can change over time with the addition of new grades, it should be declared as a variable rather than a constant.