p.1
Introduction to Requirements Engineering
What is the focus of Lecture #1?
Introduction to Software Requirements.
p.2
Introduction to Requirements Engineering
What is the main focus of the requirements engineering process?
To understand and apply it for elicitation, specification, modeling, and analysis of software and system requirements.
p.3
Definition and Types of Software Requirements
What is the title of the book by Wiegers and Beatty?
Software Requirements, 3rd Edition (2013).
p.20
Cost and Frequency of Requirement Errors
What does the first category of errors involve?
Creation of technical design from a set of correct requirements.
p.5
Definition and Types of Software Requirements
How does Webster's dictionary define a requirement?
Something required, wanted, or needed.
p.4
Sources of Requirements and Stakeholder Analysis
What is meant by stakeholder's environment?
The stakeholder's environment refers to the context in which stakeholders operate, including their needs, constraints, and interactions.
p.10
Project Success and Failure Factors
What is a key goal in software development?
To develop quality software on time and within budget that meets customers' real needs.
p.20
Cost and Frequency of Requirement Errors
What are the two categories of errors discovered during the design of a development project?
1. Creation of technical design from a set of correct requirements. 2. 'Leaked' into the design phase of the project.
p.22
Cost and Frequency of Requirement Errors
What is the potential cost increase when a defect is discovered in a software application?
50–100 times the original cost.
p.25
Project Success and Failure Factors
Why is managing software requirements critical for project success?
It helps in aligning the project outcomes with stakeholder needs.
p.23
Cost and Frequency of Requirement Errors
What are warranty costs?
Costs associated with fulfilling warranty obligations for a product.
p.4
Project Success and Failure Factors
What are root causes of project success and failures?
Root causes can include unclear requirements, lack of stakeholder involvement, poor project management, and inadequate resources.
p.13
Software Project Success Triangle
What is a common challenge in managing the Software Project Success Triangle?
Achieving a balance between time, cost, and scope while meeting quality standards.
p.8
Sources of Requirements and Stakeholder Analysis
Who are stakeholders in a system?
People affected by the system.
p.24
Elicitation, Specification, and Validation Processes
What is the purpose of elicitation in requirements engineering?
To gather information from stakeholders.
p.4
Sources of Requirements and Stakeholder Analysis
What are the sources of requirements?
Sources of requirements can include stakeholders, existing documentation, regulations, and user feedback.
p.23
Cost and Frequency of Requirement Errors
What does product liability refer to?
Legal responsibility of a manufacturer or seller for producing a defective product.
p.13
Software Project Success Triangle
What is the significance of balancing the Software Project Success Triangle?
To ensure project success and meet stakeholder expectations.
p.6
Definition and Types of Software Requirements
What does the response of software against the input refer to?
The behavior of the software system based on given inputs.
p.5
Definition and Types of Software Requirements
What is the definition of 'want'?
Something you would like to have.
p.24
Elicitation, Specification, and Validation Processes
What is the goal of specification in requirements engineering?
To structure customer input and derived requirements into written documents and diagrams.
p.4
Definition and Types of Software Requirements
What is a requirement?
A requirement is a condition or capability needed by a user to solve a problem or achieve an objective.
p.13
Software Project Success Triangle
What happens if the scope of a project increases?
It may require more time and cost to complete.
p.10
Importance of User Involvement and Management Support
What defines good software according to stakeholders?
It meets expectations of being correct, reliable, maintainable, and user-friendly.
p.10
Cost and Frequency of Requirement Errors
What is important regarding the cost of software?
The total cost incurred over all phases of its life cycle should be minimal and within budget.
p.8
Sources of Requirements and Stakeholder Analysis
What role do stakeholders play in a project?
They influence and are influenced by the project outcomes.
p.20
Cost and Frequency of Requirement Errors
What does the second category of errors refer to?
'Leaked' into the design phase of the project.
p.25
Definition and Types of Software Requirements
What is a key challenge discussed in the chapter regarding software requirements?
Understanding and managing the requirements effectively.
p.23
Cost and Frequency of Requirement Errors
What are service costs in the context of software?
Costs incurred for a company representative to visit a customer's location for software reinstallation.
p.6
Definition and Types of Software Requirements
What is a complete description of what the software system will do called?
A complete specification of the desired external behavior of the software system.
p.12
Definition and Types of Software Requirements
Why is the decision on what to build difficult to rectify later?
Because it significantly impacts the resulting system.
p.23
Cost and Frequency of Requirement Errors
Why is documentation important?
It provides necessary information and guidelines for users and support teams.
p.3
Definition and Types of Software Requirements
What is the title of the book by Pressman and Maxim?
Software Engineering: A Practitioner’s Approach, 8th Edition.
p.5
Definition and Types of Software Requirements
What is the definition of 'need'?
Something you have to have.
p.9
Definition and Types of Software Requirements
What is meant by 'Application Domain'?
The specific area or context in which a software application is intended to operate.
p.5
Definition and Types of Software Requirements
What is the difference between 'wanted' and 'needed'?
Need refers to essentials, while want refers to desires.
p.4
Cost and Frequency of Requirement Errors
What is the frequency of requirement errors?
The frequency of requirement errors refers to how often mistakes occur in the requirements phase of a project.
p.9
Definition and Types of Software Requirements
What does 'Existing System' refer to?
The current software or system in use before any new development or changes are made.
p.24
Elicitation, Specification, and Validation Processes
What is the validation process in requirements engineering?
Asking the customer to confirm that the written requirements are accurate and complete, and correcting errors.
p.13
Software Project Success Triangle
How does the Software Project Success Triangle affect project management?
Changes in one component (Time, Cost, Scope) can impact the others.
p.7
Definition and Types of Software Requirements
What is a capability in the context of a system?
A requirement that must be met or possessed by a system to satisfy a contract, standard, specification, or other formally imposed document.
p.14
Project Success and Failure Factors
What is the first step in resolving any problem?
To understand the root causes.
p.12
Definition and Types of Software Requirements
What happens if the decision on what to build is done wrong?
It cripples the resulting system.
p.24
Elicitation, Specification, and Validation Processes
What does analysis involve in the requirements process?
Understanding and classifying information into various categories.
p.4
Cost and Frequency of Requirement Errors
What is the cost of requirement errors?
The cost of requirement errors includes the expenses incurred due to rework, delays, and potential project failure.
p.7
Definition and Types of Software Requirements
According to IEEE Std 729, what can a capability be considered as?
A constraint, condition, or functionality.
p.6
Definition and Types of Software Requirements
What should software requirements not describe?
How the software system will do what it does.
p.21
Defect Origins and Removal Efficiency
What phenomenon does the study by Snyder and Shumate focus on?
The leakage phenomenon in software projects.
p.6
Definition and Types of Software Requirements
What are some forms that software requirements may take?
Abstract statements of services, detailed mathematical functions, part of the bid of contract, the contract itself, or part of the technical document.
p.25
Definition and Types of Software Requirements
What is the primary focus of Chapter 1 in 'Managing Software Requirements'?
The Requirements Problem.
