MANAGING-CLOUD-SECURITY practice question 8 of 15

Which tool should a developer use to describe the requirements they have gathered for a code improvement they are tasked with making as part of a current release?

Full set: 80 questions

Domain Cloud Security Fundamentals

Answer options
A: Cases
B: Stories Correct answer
C: Cookies
D: Notes
Correct Answer:
B. Stories
Explanation

In Agile software development methodologies, which are central to modern cloud application lifecycles, "User Stories" are the standard tool for describing requirements. A user story is a concise, informal description of a feature or improvement from the end-user's perspective. It captures the "who," "what," and "why" of a requirement without delving into technical implementation details. This makes it the ideal artifact for a developer to articulate the requirements they have gathered for a specific code improvement task within a release cycle, ensuring clarity and alignment with user needs.

Why Incorrect

A. Cases: This term is ambiguous. While it could refer to "use cases," "stories" are the more specific and standard artifact for this purpose in Agile development frameworks like Scrum.
C. Cookies: Cookies are small data files stored on a user's computer by a web browser. They are a technical component for session management, not a tool for documenting requirements.
D. Notes: While a developer may take personal notes, this is an informal and unstructured method. It is not a formal tool for communicating requirements to a team or tracking work.

References

1. Cohn

M. (2004). User Stories Applied: For Agile Software Development. Addison-Wesley Professional. In Chapter 2

"Writing Stories

" Cohn defines user stories as a primary means to express functional requirements in Agile projects (pp. 15-17).

2. Atlassian. (n.d.). User stories | Examples and template. Atlassian Agile Coach. Retrieved from https://www.atlassian.com/agile/project-management/user-stories. This official vendor documentation defines a user story as "an informal

general explanation of a software feature written from the perspective of the end user or customer."

3. Lucassen

G.

Dalpiaz

F.

van der Werf

J. M. E.

& Brinkkemper

S. (2016). The use and effectiveness of user stories in practice. In 2016 IEEE 24th International Requirements Engineering Conference (RE) (pp. 205-214). IEEE. https://doi.org/10.1109/RE.2016.29. This peer-reviewed paper analyzes the practical application of user stories as a central tool for requirements elicitation and documentation in software projects.

Scroll to Top