Module 1 Lesson 2 Flashcards
the planning phase of software development, specifically on gathering and analyzing requirements
What are the key steps in the requirements gathering process?
Brainstorming, assigning roles, listing assumptions, preparing questionnaires, interviewing stakeholders, and documenting requirements.
What is the purpose of brainstorming in requirements gathering?
To generate new ideas and find solutions for specific issues.
What is document analysis in the context of requirements gathering?
Reviewing existing documentation to gather relevant data and business objectives.
How are focus groups used in requirements gathering?
They gather information from a group by discussing a product or service to provide insights.
What is the role of interviews in the requirements gathering process?
Interviews allow in-depth discussions with stakeholders to understand their business needs and potential solutions.
What is the function of a questionnaire in requirements gathering?
A questionnaire collects quantified thoughts and data from a large group of participants quickly.
.
What are functional requirements in software development?
Functional requirements define what the software should do, including calculations, data handling, and user interactions.
What are non-functional requirements?
Non-functional requirements specify how the software performs its functions, covering areas like usability, reliability, and performance.
What is a Software Requirement Specification (SRS) document?
It is a detailed description of all product features and how they should perform.
What is a user story in software development?
A user story is a short, user-focused description of a feature, typically in the format: “As a (user role), I want to (goal) so that (reason).”
What is a use case?
A use case describes the steps or flow a user follows to achieve a specific purpose, reflecting all possible ways to interact with the system.
What is a Work Breakdown Structure (WBS)?
WBS is a visual breakdown of complex processes into smaller, manageable components for analysis.
In the FoodEats case study, what are some key functional requirements of the app?
Account creation, order placement, real-time tracking, and user reviews.
In the FoodEats case study, what are some key non-functional requirements?
Secure data handling, performance, device compatibility, and compliance with privacy regulations
