Understanding Software Requirements

What are functional requirements in software development?

• Functional requirements are the specific behaviors and functions that a software system must perform.

• Functional requirements refer to the hardware specifications needed for software deployment.

• Functional requirements are the non-functional aspects like performance and security.

• Functional requirements are the aesthetic design elements of a software system.

Give an example of a functional requirement.

• The system shall allow users to log in using their email and password.

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

• The system shall display the current date and time.

• The system shall provide a user manual for reference.

What is the purpose of non-functional requirements?

• The purpose of non-functional requirements is to specify the criteria that judge the operation of a system, such as performance, usability, reliability, and security.

• To outline the budget and resources required for the project.

• To specify the user roles and permissions within the system.

• To define the programming languages used in development.

List three types of non-functional requirements.

• Maintainability

• Performance, Security, Usability

• Scalability

• Compatibility

How do functional and non-functional requirements differ?

• Functional requirements describe system behaviors; non-functional requirements describe system performance attributes.

• Functional requirements are always measurable; non-functional requirements are subjective and cannot be quantified.

• Functional requirements are related to system security; non-functional requirements are related to system architecture.

• Functional requirements focus on user interface design; non-functional requirements focus on user experience.

What is a use case diagram?

• A use case diagram shows the interactions between actors and the system, representing the system's functionalities.

• A use case diagram is a detailed technical specification of the software.

• A use case diagram outlines the hardware requirements for a system.

• A use case diagram is a flowchart of the system's architecture.

What elements are typically included in a use case diagram?

• Components, Interfaces, Diagrams

• Actors, Scenarios, Processes

• Actors, Use Cases, Relationships

• Users, Features, Flows

Explain the role of actors in a use case diagram.

• Actors represent users or systems that interact with the system, defining its boundaries and interactions.

• Actors do not interact with the system at all.

• Actors are only responsible for system maintenance.

• Actors represent internal components of the system.

What is the significance of use cases in software requirements?

• Use cases are only relevant for technical documentation.

• Use cases are unnecessary for understanding user needs.

• Use cases are significant as they clarify user interactions and requirements, ensuring a shared understanding among stakeholders.

• Use cases are primarily used for coding standards.

How can non-functional requirements impact system performance?

• Non-functional requirements can significantly impact system performance by defining benchmarks for response times, resource usage, and scalability.

• Non-functional requirements are solely about security measures.

• Non-functional requirements only affect user interface design.

• Non-functional requirements have no impact on system performance.