Quiz 3 Flashcards
Which of the following options is NOT correct about documenting requirements?
- Documenting requirements helps with communicating requirements efficiently.
- Documenting requirements is not necessary in agile development
- Documenting requirements helps in bridging the gap between Stakeholders and the system builders
- Documenting requirements helps in having a basis for contracts and acceptance decisions.
Documenting requirements is not necessary in agile development
This statement is incorrect as documenting requirements is essential even in agile environments.
Consider a scenario where an organization is developing a medical device software internally, and it falls under strict regulatory guidelines. Which statement best describes the requirements specification approach they should take?
- They can ignore full-fledged requirements since the development is internal.
- They should opt for a brief outline of requirements without any contractual obligations.
- They should solely rely on agile artifacts like user stories without detailed specifications.
- They would need full-fledged requirements due to the regulated environment.
They would need full-fledged requirements due to the regulated environment.
Full-fledged requirements ensure compliance with regulatory guidelines.
In the context of agile requirements specification, which of the following statements is true?
- User stories are the most abstract level of requirement representation.
- A product backlog is primarily organized around system visions and epics.
- Epics and features serve an intermediate level of abstraction, grouping user stories.
- Use cases and scenarios are primarily used to replace user stories.
Epics and features serve an intermediate level of abstraction, grouping user stories.
This helps in organizing requirements effectively.
What purpose does a system vision serve in agile requirements specification artifacts?
- To provide a detailed breakdown of tasks and activities for the development team.
- To replace the need for a product backlog.
- To serve as a primary collection of user stories.
- To offer an abstract overview of the system being developed.
To offer an abstract overview of the system being developed.
The system vision guides the overall development direction.
Which of the following statements best illustrates the comprehensive nature of documenting functionality in requirements?
- Only the normal behavior of the system needs to be specified.
- Functionality documentation is primarily about specifying dynamic system behavior.
- The focus should only be on data usage, not its structure.
- It should encompass data usage and structure, results, preconditions, processing, and both normal and abnormal system behaviors.
It should encompass data usage and structure, results, preconditions, processing, and both normal and abnormal system behaviors.
This ensures a complete understanding of system functionality.
Which of the following is NOT listed as a general rule when documenting requirements?
- Record metadata such as source, author, date, and status
- Requirements should always be large and comprehensive
- Use structure templates for consistency
- Adapt the level of detail based on the associated risk with a requirement
Requirements should always be large and comprehensive
This is incorrect, as requirements should be concise and relevant.
Which statement about agile user stories is INCORRECT?
- They can optionally include the expected benefit.
- They are always written from a developer’s perspective.
- They provide a single sentence about a requirement
- They are accompanied by acceptance criteria for clarity.
They are always written from a developer’s perspective.
User stories should be written from the user’s perspective.
Consider you’re designing a user story for an online bookstore. Which of the following fits the standard template for user stories in an agile context?
- “Implement a feature for book recommendations.”
- “As a reader, I want to easily search for books by genre so that I can quickly find the type of book I’m interested in.”
- “As a developer, I want to code the payment gateway.”
- “Build a system that allows book purchase.”
“As a reader, I want to easily search for books by genre so that I can quickly find the type of book I’m interested in.”
This follows the user story format emphasizing user needs.
A user story for an e-commerce platform states: “As a shopper, I want to view related products so that I can explore similar items.” Based on the guidelines provided, which of the following would NOT be a suitable acceptance criterion?
- If a product has no related items, a message should be displayed indicating so.
- Related products should be displayed within 1 second of accessing a product’s detail page.
- The platform should have a user-friendly interface.
- At least 5 and at most 10 related products should be displayed.
The platform should have a user-friendly interface.
This is too vague and lacks measurable criteria.
Which statement about use case diagrams is TRUE?
- They primarily express the expectations of developers.
- They provide a detailed implementation of system functionalities.
- They can answer questions like “Who interacts with the system?”
- They model processes and workflows.
They can answer questions like “Who interacts with the system?”
This highlights the role of use case diagrams in identifying stakeholders.
In the context of use case relationships, if Use Case A generalizes Use Case B, which of the following is TRUE?
- A and B have entirely independent behaviors.
- B inherits the behavior of A and can extend or overwrite it.
- Only A is executable.
- A inherits all relationships from B.
B inherits the behavior of A and can extend or overwrite it.
Generalization allows for reuse and extension of behaviors.
In the context of use case relationships, if Use Case P is associated with Actor Q, which of the following is TRUE?
- Actor Q inherits the behaviors of Use Case P.
- Use Case P can only be executed by Actor Q.
- Actor Q interacts or communicates with Use Case P.
- Use Case P generalizes Actor Q.
Actor Q interacts or communicates with Use Case P.
This reflects the relationship between actors and use cases.
Which is NOT a typical error to avoid in use case diagrams?
- Including too few use cases.
- Modeling processes or workflows.
- Detailed functional decomposition into separate use cases.
- Positioning actors inside system boundaries.
Including too few use cases
Modeling processes is essential for clarity in use case diagrams.
Which statement about actors in use case diagrams is INCORRECT?
- Specific users can adopt multiple roles simultaneously.
- Actors represent roles that users adopt.
- Actors are part of the system and lie within system boundaries.
- Human and non-human entities can both be actors.
Actors are part of the system and lie within system boundaries.
Actors represent external roles, not internal components.
One advantage of use case diagrams is that they:
- Provide a detailed breakdown of all system functionalities.
- Always replace the need for detailed system documentation.
- Clearly show the internal functions and data required for interactions.
- Offer an abstract overview of the system from the actors’ perspectives.
Offer an abstract overview of the system from the actors’ perspectives.
This helps in understanding system interactions without delving into details.
When identifying use cases, which is a best practice to consider?
- Ignore unexpected events within the system.
- Avoid allowing an actor to query or modify system information.
- Only focus on the main tasks an actor can perform.
- Consider if an actor should be informed about unexpected events within the system.
Consider if an actor should be informed about unexpected events within the system.
This ensures comprehensive coverage of use cases.
Given the following Use-Case diagram:
Customer — (Browse Products)
|————- (Add to cart) <—«extend» – (View Recommendations)
|————- (Checkout) < —«extend»– (Apply Discount)
Which use-case is optionally executed when the “Add to Cart” use-case is executed?
- Apply Discount
- View Recommendations
- Browse Products
- Checkout
View Recommendations
Given the Use-Case diagram:
Employee ——– (Submit Application) < —«extend»–(Provide References)
^
|
«include»
|
(Schedule Interview)
What is the mistake in the above diagram regarding the relationships?
- “Provide References” should be an include relationship
- Both a and b
- “Schedule Interview” should be an extend relationship
- No mistake
“Schedule Interview” should be an extend relationship
True or False: In agile development, there is always a classic requirements specification document.
False
Agile methodologies often prioritize flexibility over traditional documentation.
True/False: In agile requirements, actions should be taken only if they contribute value.
True
This principle aligns with the agile focus on delivering value.
True/False: When specifying requirements in natural language, subordinate clauses are only used for making the requirements more precise.
False
Subordinate clauses can complicate understanding if overused.
Which of the following options are NOT correct about user feedback in app store reviews or social media platforms (Select all options that apply).
- User feedback does not contain valuable information for software evolution.
- The quality of feedback provided varies from user to user.
- User feedback is rare.
- User feedback is unstructured.
- User feedback is rare
- User feedback does not contain valuable information for software evolution.
Which of the following statements about UML (Unified Modeling Language) is NOT accurate?
- UML is specific to the waterfall software process.
- UML is a general-purpose modeling language suitable for various applications, from mobile apps to satellites.
- UML can be used across the entire life cycle of software development, promoting iterative refinement of models.
- UML can have both graphical and textual representations.
UML is specific to the waterfall software process.
