Introduction to RE Flashcards
1
Q
- Why are requirements important in software development?
A
- They help clearly define the client’s needs detect errors early and ensure the product meets the client’s needs. They are crucial for project/product success.
2
Q
- How are requirements related to project/product success?
A
- Studies show that about half of the factors associated with project or product success are related to requirements quality.
3
Q
- Why are end users’ demands becoming more significant?
A
- As products become more sophisticated there is a greater need for clear detailed requirements to meet users’ high expectations.
4
Q
- What is the definition of Software Requirements?
A
- Software requirements are specific descriptions of a client’s needs defined through the requirements engineering process.
5
Q
- What is Requirements Engineering (RE)?
A
- It involves all lifecycle activities devoted to identifying analyzing documenting and validating user requirements to ensure the system satisfies user needs.
6
Q
- Why is Requirements Engineering crucial in software development?
A
- Errors introduced at the requirements stage are the most expensive to fix. RE lays the foundation for design coding testing and acceptance of the system.
7
Q
- What is the Software Requirements Specification (SRS)?
A
- The SRS is a document that describes the complete external behavior of the proposed software system used in subsequent stages like design coding and testing.
8
Q
- Why has Requirements Engineering become more important?
A
- Due to faster product development high employee turnover and outsourcing effective RE ensures products meet customer needs and comply with regulations.
9
Q
- How has outsourcing affected Requirements Engineering?
A
- Outsourcing and offshoring mean specifications must be created for teams with limited or no domain expertise making accurate and comprehensive requirements essential.
10
Q
- What is the main aim of Requirements Engineering in the SDLC?
A
- The goal is to produce a Requirements Specification Document (RSD) or Software Requirement Specification (SRS) that outlines the system’s external behavior.
11
Q
- What is the definition of Requirements Engineering according to the systematic process?
A
- Requirements Engineering systematically analyzes and documents requirements using proven techniques tools and languages to ensure the system meets user needs.
12
Q
- What are some misconceptions about Requirements Engineering?
A
- Misconception 1: Anyone can become a Requirements Engineer with just a little training. Misconception 2: Non-functional and functional requirements can be handled separately. Misconception 3: Processes that work for a small number of requirements will scale for larger projects.
13
Q
- What are some key success factors in Requirements Engineering?
A
- A full-time qualified chief architect an effective requirements management process strong collaboration between marketing sales and requirements engineering teams trained and experienced requirements engineers identifying all stakeholders early in the project.
14
Q
- What is the role of a Chief Architect in Requirements Engineering?
A
- The chief architect ensures technical continuity and vision and manages both functional and non-functional requirements.
15
Q
- What are non-functional requirements?
A
- Non-functional requirements define the system’s quality attributes such as performance scalability security and usability.
16
Q
- What are functional requirements?
A
- Functional requirements describe the specific behaviors or functions of the system such as processing tasks inputs and outputs.
17
Q
- What is the significance of a Requirements Management Process?
A
- A structured requirements management process ensures traceability change management and helps maintain alignment between the evolving requirements and the product development.
18
Q
- Why are Requirements Reviews important?
A
- Requirements reviews ensure the accuracy completeness and consistency of the requirements especially when there are changes or additions.
19
Q
- What does “Requirements Elicitation” involve?
A
- It involves gathering and analyzing requirements from stakeholders marketing and sales teams to define the product’s features and scope.
20
Q
- What is the role of Subject Matter Experts (SMEs) in Requirements Engineering?
A
- SMEs provide critical domain knowledge to ensure that the requirements accurately reflect real-world needs and constraints.
21
Q
- What is the purpose of Requirements Engineering Artifact Modeling?
A
- It defines a reference model for RE providing the core set of RE artifacts and guiding the development and maintenance of project-specific processes.
22
Q
- What are some of the key components of the RE artifact model?
A
- A measurable reference model for RE artifacts a process tailoring approach for specialized needs RE artifact-centered process guidelines that define levels of completion and quality.
23
Q
- What is the relationship between marketing and requirements engineering?
A
- Strong collaboration is needed to ensure accurate definition of product features informed by market and customer needs.
24
Q
- What are “trace matrices” in Requirements Engineering?
A
- Trace matrices are used to track relationships between different requirements ensuring that changes are consistently applied throughout the system.
25
Q
- Why do Requirements Engineering processes need to scale?
A
- As the number of requirements increases the complexity of managing them also increases requiring well-defined processes to handle larger projects.
26
Q
- What is the importance of Stakeholder Identification in Requirements Engineering?
A
- Identifying all stakeholders early ensures that their needs and expectations are captured reducing the risk of miscommunication or missed requirements.
27
Q
- What role does “prototyping” play in Requirements Engineering?
A
- Prototyping helps gather rapid feedback from stakeholders allowing for refinement and validation of requirements during the development process.
28
Q
- What are “change management” practices in Requirements Engineering?
A
- Change management practices ensure that changes to requirements are properly controlled documented and communicated throughout the project.
29
Q
- What is meant by “traceability” in the context of Requirements Engineering?
A
- Traceability refers to the ability to track the relationships between requirements design elements and testing to ensure consistency and completeness.
30
Q
- What is the role of the “Requirements Specification Document (RSD)”?
A
- The RSD documents all requirements serving as the foundation for design development and testing activities.
31
Q
- What are functional vs. non-functional requirements examples?
A
- Functional: The system must process customer orders. Non-functional: The system must handle 1000 orders per second.
