Software Requirements and Specification Lecture 1

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the purpose of requirements engineering?

To market the software product to potential clients

To develop the coding structure of a software product

To design the user interface of a software product

To systematically determine the requirements for a software product (correct)

According to the lecture, what is the difference between 'wanted' and 'needed'?

Wanted is essential for the software system, while needed is a desired feature

Wanted is a desired feature, while needed is essential for the software system (correct)

Wanted is related to hardware requirements, while needed is related to software requirements

Wanted and needed have the same meaning in the context of software requirements

How are software requirements described?

A detailed description of the coding structure of the software system

A complete description of what the software system will do without describing how it will do it (correct)

A summary of the project management plan for the software system

An overview of the marketing strategy for the software system

What do software requirements represent?

The complete specification of the desired external behavior of the software system Signup and view all the answers

According to IEEE, what is a software requirement?

A condition or capability that must be met or possessed by a system Signup and view all the answers

What forms part of the bid of contract or the contract itself?

Software requirements Signup and view all the answers

What are software requirements not concerned with?

Outlining the marketing strategy for the software system Signup and view all the answers

What does a complete description of software requirements include?

The services and/or constraints provided by the software system Signup and view all the answers

What is not a part of software requirements?

The coding structure of the software system Signup and view all the answers

What should always be kept in mind when determining software requirements?

The difference between wanted and needed Signup and view all the answers

According to IEEE Std 729, what are examples of stakeholders?

People affected in some way by the system Signup and view all the answers

What does the quote 'One person’s floor is another person’s ceiling' refer to in the context of software requirements?

Different levels of detail at which stakeholders describe requirements Signup and view all the answers

According to Fred Brooks, what is the most challenging part of building a software system?

Deciding what to build Signup and view all the answers

Which of the following is an example of a software requirement?

The system shall maintain records of all payments made to employees on accounts of salaries, bonuses, travel/daily allowances, medical allowances, etc. Signup and view all the answers

What are non-functional requirements also known as?

Quality attributes Signup and view all the answers

Which statements describe functional requirements?

Statements of services the system should provide – Reaction to particular inputs – Behavior in particular situations Signup and view all the answers

What type of requirements capture abnormal behavior as exception handling?

Functional requirements Signup and view all the answers

'Sequencing and parallelism' are captured by which type of requirement?

'Functional requirements' Signup and view all the answers

'The system shall interface with the central computer to send daily sales and inventory data from every retail store' is an example of which kind of requirement?

Functional requirement Signup and view all the answers

What is the most difficult part of building a software system according to Fred Brooks?

Deciding what to build Signup and view all the answers

Study Notes

Purpose of Requirements Engineering

Ensures the alignment of software functionality with stakeholder needs and expectations.
Facilitates clear communication among all project stakeholders to minimize misunderstandings.

Difference Between 'Wanted' and 'Needed'

'Wanted' refers to desirable features or enhancements that may improve user experience but are not essential.
'Needed' signifies the critical functionalities that are essential for the system to operate effectively.

Description of Software Requirements

Described using natural language, formal methods, use case scenarios, and graphical models for clarity and precision.

Representation of Software Requirements

Represent the functionalities, behaviors, and constraints of a software system that fulfill user needs and business objectives.

IEEE Definition of a Software Requirement

A software requirement is a condition or capability needed by a user to solve a problem or achieve an objective.

Bid of Contract Components

Software requirements form an integral part of the bid of contract or the contract itself, detailing what is to be delivered.

Exclusions in Software Requirements

Not concerned with how the requirements are implemented or the design specifics of the software.

Complete Description of Software Requirements

Includes functional requirements, non-functional requirements, constraints, performance criteria, and use cases.

Elements Excluded from Software Requirements

Implementation details or design specifications are not part of the software requirements.

Considerations in Determining Software Requirements

Should always prioritize stakeholder needs, feasibility, and system constraints while assessing the requirements.

IEEE Std 729 Stakeholders

Examples include end-users, customers, project managers, developers, and quality assurance teams, each influencing the requirements.

Meaning of the Quote 'One Person’s Floor is Another Person’s Ceiling'

Highlights subjective interpretations of requirements where one stakeholder sees a baseline level of functionality, while another considers it as the maximum capability required.

Fred Brooks on Challenges of Building Software Systems

Identifies managing changing requirements and stakeholder communication as the most challenging aspects of software system development.

Example of a Software Requirement

“The system shall generate monthly performance reports” qualifies as a clear, measurable software requirement.

Non-Functional Requirements Alias

Also known as quality attributes or system attributes, focusing on system performance, usability, reliability, etc.

Descriptions of Functional Requirements

Specify what the system should do, detailing actions and tasks, often presented in clear statements or use cases.

Requirement Type for Abnormal Behavior

Exception handling is captured through error handling requirements which address unexpected inputs or system failures.

Requirement Type for 'Sequencing and Parallelism'

Typically captured by workflow or process requirements that define the order and concurrency of tasks.

Example of a Specific Requirement

“The system shall interface with the central computer to send daily sales and inventory data from every retail store” is a functional requirement outlining an action.

Fred Brooks on the Difficulty in Software System Development

Indicates the complexity of handling continuously evolving requirements and user expectations as the toughest challenge.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Description

Learn about the basics of software requirements, including understanding what is a requirement, sources of requirements, levels of requirements, importance, kinds of requirements, and examples.