User Stories & UML Flashcards
What is “Big Design Up Front”? What are the steps in traditional requirements analysis?
What are some problems with the “Big Design Up Front” approach?
What are the following problems with the “Big Design Up Front” approach?
Requirements Checklist
Intangible Software
What are the following problems with the “Big Design
Customer decisions
Requirements Changes
What does it mean that software requirements = communication? What is the difference between a project relying on those who view the software from a business perspective and those who develop the software?
What is the solution to having different perspectives on a software project? How is decision making handled?
What are user stories? What are the three main components?
Who are user stories written by? What language are they written in?
Example of good and bad user stories:
What are some of the common templates for user stories?
Why is conversation important to constructing user stories? What do user stories represent?
What is on the front / back of a user story?
What is a user story estimation? What are story points?
What is acceptance testing with regards to user stories?
What is Story-Driven Development? How does it work?
What is release planning with regards to story-driven development?
Example of story-driven development release planning:
What is prioritization with regards to story-driven development?
What are the differences between BDUF and story-driven development?
Good user stories must follow the INVEST acronym. What are the components of the INVEST acronym?
What does it mean for a user story to be independent? What are some of the problems with dependent stories?
What does it mean for a user story to be negotiable? Why is this important?
What does the amount of information have to do with a user story being negotiable?
What does it mean for a user story to be valuable? Valuable to who?
What does it mean for a user story to be esimatable? What are some reasons why a user story may not be estimable?
How would a developers lack of domain knowledge stop a user story from being estimatable?
Why would a developer’s lack of technical knowledge stop a user story from being estimatable?
Why would a story that is too big stop a user story from being estimatable?
What does the S in INVEST stand for? Why is this important?
What does the T in INVEST stand for? Why is this important? Should they be automated? What percent?
How would you summarize user stories:
What are some caveats with user stories?
What is UML?
What are the goals of UML?
What are UML diagrams? What do they allow for? What are some of the example?
What are UML class diagrams? Are class diagrams fully complete at the beginning of the development process?
What is a UML class diagram composed of?
Within a UML class diagram, what may attributes and operations include? What is the general form?
What is Associations in UML class diagrams? What are the different forms?
What is the difference between aggregation and composition in UML class diagrams? What do they look like?
What is generalization in UML class diagrams?
What is a dependency in UML class diagrams? What does it look like?
UML Class diagrams review
