Software Requirements Specification (SRS) in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Software Requirements Specification (SRS)?

An SRS is a detailed document that describes what a software system should do and how it should perform. It serves as a guide for developers and stakeholders to understand the software's expected behavior and features.

beginner

Name two main types of requirements typically included in an SRS.

Functional requirements describe what the software should do, such as tasks or functions. Non-functional requirements describe how the software performs, like speed, security, and usability.

beginner

Why is an SRS important in software development?

An SRS helps ensure everyone involved understands the software goals clearly. It reduces misunderstandings, guides development, and provides a basis for testing and validation.

intermediate

What are some common sections found in an SRS document?

Common sections include Introduction, Overall Description, Specific Requirements, External Interface Requirements, and Appendices.

intermediate

How does an SRS help with project management?

It provides clear goals and scope, helping to plan tasks, estimate time and cost, and track progress. It also helps manage changes by documenting agreed requirements.

What does the 'functional requirements' section in an SRS describe?

A The hardware needed to run the software

B The budget for the software project

C The tasks and functions the software must perform

D The user interface colors and fonts

Functional requirements specify what the software should do, such as features and behaviors.

Which of the following is a non-functional requirement?

A The software should support multiple languages

B The software must allow users to log in

C The software must save user data

D The software should load pages within 2 seconds

Non-functional requirements describe how the software performs, like speed or reliability.

Who typically uses the SRS document?

A Developers, testers, and stakeholders

B Only end users

C Marketing team only

D Only software testers

The SRS is used by developers, testers, and stakeholders to understand and build the software.

What is the main goal of writing an SRS?

A To clearly define software requirements

B To design the software user interface

C To create a marketing plan

D To write the software code

The SRS clearly defines what the software should do and how it should behave.

Which section would you find information about how the software interacts with other systems?

A Introduction

B External Interface Requirements

C Specific Requirements

D Appendices

External Interface Requirements describe how the software connects with other systems or hardware.

Explain what a Software Requirements Specification (SRS) is and why it is important.

Think about how clear instructions help a team build software correctly.

Describe the difference between functional and non-functional requirements in an SRS.

Consider what the software must do versus how well it must do it.

Practice

1. What is the primary purpose of a Software Requirements Specification (SRS) document?

easy

A. To list the hardware requirements only

B. To provide the final source code of the software

C. To describe the marketing strategy for the software

D. To clearly describe what the software must do and how it should perform

Solution

1. Step 1: Understand the role of SRS

   The SRS defines the software's functions and performance requirements.

2. Step 2: Eliminate unrelated options

   Options about source code, hardware only, or marketing do not match the SRS purpose.

3. Final Answer:

   To clearly describe what the software must do and how it should perform -> Option D

4. Quick Check:

   SRS = Software functions and performance [OK]

Hint: SRS = What & how software works, not code or marketing [OK]

Common Mistakes:

• Confusing SRS with source code documentation
• Thinking SRS only lists hardware needs
• Assuming SRS is for marketing plans

2. Which of the following is a correct characteristic of a good SRS document?

easy

A. It is clear, complete, and consistent

B. It is ambiguous and open to interpretation

C. It contains only high-level marketing goals

D. It is written only after coding is complete

Solution

1. Step 1: Identify qualities of a good SRS

   A good SRS must be clear, complete, and consistent to avoid confusion.

2. Step 2: Reject incorrect traits

   Ambiguity, marketing-only content, or writing after coding contradict good SRS practices.

3. Final Answer:

   It is clear, complete, and consistent -> Option A

4. Quick Check:

   Good SRS = Clear & complete [OK]

Hint: Good SRS is clear and complete, never ambiguous [OK]

Common Mistakes:

• Believing ambiguity is acceptable
• Confusing SRS with marketing documents
• Writing SRS after coding instead of before

3. Consider this excerpt from an SRS:
"The system shall allow users to log in using a username and password."
What type of requirement is this?

medium

A. Performance requirement

B. Functional requirement

C. Design constraint

D. Usability requirement

Solution

1. Step 1: Identify the requirement type

   The statement describes a specific function the system must perform: user login.

2. Step 2: Match to requirement categories

   Functional requirements describe what the system should do; performance relates to speed, design constraints limit design choices, usability relates to ease of use.

3. Final Answer:

   Functional requirement -> Option B

4. Quick Check:

   Login feature = Functional requirement [OK]

Hint: Functions = Functional requirements, not performance or design [OK]

Common Mistakes:

• Confusing functional with performance requirements
• Thinking login is a design constraint
• Assuming login relates only to usability

4. A software team wrote this SRS statement:
"The system shall respond to user input within 5 seconds."
However, users report delays longer than 5 seconds. What is the likely issue?

medium

A. The SRS is ambiguous about response time

B. The requirement is not testable

C. The system does not meet the performance requirement

D. The requirement is a design constraint, not a performance metric

Solution

1. Step 1: Analyze the SRS statement

   The statement sets a performance requirement: respond within 5 seconds.

2. Step 2: Interpret user feedback

   Users experiencing delays longer than 5 seconds means the system fails to meet this requirement.

3. Final Answer:

   The system does not meet the performance requirement -> Option C

4. Quick Check:

   Delays > 5s = Performance failure [OK]

Hint: If system is slow, it fails performance requirements [OK]

Common Mistakes:

• Thinking the SRS is ambiguous when it is clear
• Assuming requirement is untestable
• Confusing performance requirement with design constraint

5. You are tasked with writing an SRS for a new mobile app. Which approach best ensures the SRS helps build the right software efficiently?

hard

A. Include detailed functional and non-functional requirements with clear acceptance criteria

B. Write only high-level goals and leave details for developers to decide

C. Focus mainly on the user interface design and ignore backend requirements

D. Use vague language to allow flexibility during development

Solution

1. Step 1: Identify best SRS writing practice

   A good SRS includes detailed functional and non-functional requirements with clear acceptance criteria to guide development.

2. Step 2: Evaluate other options

   High-level goals only, ignoring backend, or vague language lead to misunderstandings and inefficiency.

3. Final Answer:

   Include detailed functional and non-functional requirements with clear acceptance criteria -> Option A

4. Quick Check:

   Detailed & clear SRS = Efficient, correct software [OK]

Hint: Clear, detailed requirements avoid errors and speed development [OK]

Common Mistakes:

• Writing vague or incomplete requirements
• Ignoring backend or non-functional needs
• Leaving details to developers without guidance