CAP314: Unit 2

What is the primary need for a Software Requirements Specification (SRS)?

• To outline the software architecture and design.

• To provide a detailed project timeline and budget.

• To list all programming languages used in the project.

• To ensure a common understanding of software requirements among stakeholders.

List two techniques used for requirement gathering.

• Focus Groups

• Brainstorming Sessions

• Interviews, Surveys

• Document Analysis

What are functional requirements? Give an example.

• The system shall automatically generate reports every hour.

• The system shall allow users to change their profile picture.

• The system shall provide a dark mode for users.

• An example of a functional requirement is: 'The system shall allow users to log in using their email and password.'

Define non-functional requirements and provide an example.

• The system shall have a user-friendly interface.

• The system shall be deployed on a cloud platform.

• The system shall be developed using Java.

• An example of a non-functional requirement is 'The system shall be able to handle 1000 concurrent users without performance degradation.'

What characteristic of an SRS ensures it is understandable to stakeholders?

• Ambiguous terminology.

• Clarity and simplicity in language.

• Lengthy and detailed descriptions.

• Complex technical jargon.

Name three components typically found in an SRS.

• Stakeholder analysis

• System architecture

• Functional requirements, non-functional requirements, use cases

• Project timeline

What is the purpose of a requirements document structure?

• To organize and present project specifications clearly.

• To list team members and their roles.

• To define the project timeline.

• To create a budget for the project.

Explain the importance of problem analysis in requirement gathering.

• Problem analysis is only necessary for technical teams.

• Problem analysis ensures accurate identification of needs, prioritization of requirements, and alignment with business goals.

• It focuses solely on budget constraints.

• Problem analysis is irrelevant to project success.

What type of requirement specifies how the system should perform?

• System requirement

• Non-functional requirement

• Functional requirement

• User requirement

Identify one characteristic of a good requirement.

• Subjective and opinion-based

• Vague and confusing

• Overly complex

• Clear and unambiguous