Software Requirements Flashcards

1
Q

Why are requirements important in software development?

A
  • Studies show that about half of the factors associated with project or product success are requirements related. Requirements help define the client’s needs detect errors early and ensure the product meets the client’s needs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the impact of end users becoming more demanding?

A
  • As users become more demanding and products become more sophisticated it’s essential to start with good requirements to ensure the right product is built correctly.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are software requirements?

A
  • Software requirements are the specific description of a client’s needs and are defined through the requirements engineering process.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is Requirements Engineering (RE)?

A
  • Requirements Engineering is a crucial activity in the software development life cycle that helps avoid expensive errors later by identifying and defining requirements early.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Why is Requirements Engineering critical in the SDLC?

A
  • Errors in requirements are costly to fix if detected late. RE ensures that requirements are well-documented and validated which supports design coding and testing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What does the Software Requirements Specification (SRS) document include?

A
  • The SRS describes the external behavior of the software and is used in design coding testing and acceptance testing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why has Requirements Engineering become more important?

A
  • The pace of product development has increased employee turnover is higher and outsourcing has changed the dynamics of the software life cycle making effective RE more essential.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the impact of faster product development?

A
  • Customers often demand new versions of a product within a year making quick and accurate requirements gathering more crucial than ever.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How has turnover and technology change affected Requirements Engineering?

A
  • With higher employee turnover and technology shifts it’s harder to maintain consistent domain expertise which makes thorough requirements engineering even more important.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How has outsourcing affected Requirements Engineering?

A
  • Outsourcing requires clear and comprehensive requirements as teams with limited domain expertise are involved in the development process.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Why is Requirements Engineering critical in regulated industries?

A
  • In regulated industries such as aviation or pharmaceuticals poor requirements can lead to compliance issues and safety concerns making good RE essential.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the goal of Requirements Engineering in the SDLC?

A
  • The goal is to produce the Requirements Specification Document (RSD) or Software Requirement Specification (SRS) that defines the complete external behavior of the software system.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What does Requirements Engineering involve?

A
  • RE includes identifying analyzing documenting and validating user requirements through a systematic process that ensures the system meets user needs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Why is understanding requirements crucial before solving a problem?

A
  • It’s essential that the software engineering team fully understands the requirements to avoid building a system that doesn’t meet customer needs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are misconceptions about Requirements Engineering?

A
  • Misconception 1: Any subject matter expert can become a requirements engineer with little training. Misconception 2: Functional and non-functional requirements can be handled separately. Misconception 3: Processes that work for a small number of requirements will scale.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What does it take to be a Requirements Engineer?

A
  • Requirements engineers need strong communication and engineering skills organizational ability high-quality written and visual presentation skills and the ability to model business processes.
17
Q

Why can’t non-functional and functional requirements be handled separately?

A
  • Functional and non-functional requirements are related and impact each other so handling them separately may cause iterative changes and issues.
18
Q

What is the challenge with scaling Requirements Engineering processes?

A
  • RE processes need to be carefully crafted for larger projects as the complexity grows and managing requirements at scale becomes more difficult.
19
Q

What is the role of the Chief Architect in Requirements Engineering?

A
  • The Chief Architect provides technical continuity and vision manages non-functional requirements like performance and scalability and ensures the implementation of functional requirements.
20
Q

What is an Effective Requirements Management Process?

A
  • An effective process includes proper change management and traceability which are critical for keeping the project on track and ensuring all requirements are met.
21
Q

What is the importance of collaboration between marketing

22
Q

What is the significance of Requirements Reviews?

A
  • Requirements reviews ensure the accuracy completeness and consistency of the requirements especially when there are changes or new features added.
23
Q

What is the role of Subject Matter Experts (SMEs) in Requirements Engineering?

A
  • SMEs provide critical domain knowledge and help ensure that requirements are accurate and realistic.
24
Q

What is the importance of identifying all stakeholders early in the project?

A
  • Identifying all stakeholders ensures that their needs and expectations are captured reducing the risk of misunderstandings or missed requirements.
25
Q

What is the purpose of Requirements Engineering Artifact Modeling?

A
  • The purpose is to define a reference model for RE that supports communication and development of specifications and guides the establishment of project-specific RE processes.
26
Q

What are the key components of Requirements Engineering Artifact Modeling?

A
  • Key components include a measurable reference model for RE a process tailoring approach and guidelines for defining completion levels to measure project progress.
27
Q

What is the benefit of a Requirements Artifact Model?

A
  • It helps in supporting interdisciplinary communication ensuring all teams work with a consistent set of specifications and artifacts throughout the project.
28
Q

What are some initial activities in Requirements Engineering?

A
  • Early activities include analyzing marketing information understanding user needs consolidating requirements into a coherent specification and assessing the impact of these requirements on the business.
29
Q

What are some key success factors in Requirements Engineering?

A
  • Key factors include having a full-time qualified chief architect an effective requirements management process trained engineers and the identification of all relevant stakeholders.