SOFTWARE ENGINEERING
REQUIREMENTS ACCURATE
QUESTIONS AND ANSWERS WITH
SOLUTIONS 2024
Requirements Engineering - ANSWER The process of understanding and defining functionalities and
constraints of proposed systems. Usually the first stage of software life cycle
Software Requirements Specification (SRS) - ANSWER A document produced by requirements
engineering
Software Requirements - ANSWER Desired behavior: customers know what the system shall do and
software engineers know what to build. Means of communication with customer and many other
stakeholders
Requirements deal with - ANSWER Objects, states, and functions
Software Requirements stakeholders - ANSWER Contribute to requirements of systems. Consist of
clients, customers, end users, software engineers, domain experts, lawyers or auditors, market
researchers
Requirements Analysts - ANSWER Determine requirements
Functional Requirements - ANSWER What the system is supposed to do. Mapping from input to output
Non-functional (quality) Requirements - ANSWER Usability, performance, security, reliability,
maintainability, portability
Process constraints - ANSWER Resources, documentation, standards
Design constraints - ANSWER Physical environment, interface, users
, Requirements Problems - ANSWER Over-specification, under-specification, contradictory requirements,
ambiguous requirements, unknown requirements, bad assumptions about environment, changing
requirements
Requirements Characteristics - ANSWER Correct, consistent, complete, concise, traceable, unambiguous,
understandable, verifiable
Goal of Requirements Engineering - ANSWER Determine the requirements of a system and specify what
behavior is realized
Requirements Engineering Process - ANSWER 1. Work with stakeholders to elicit the requirements
2. Analyze and model the requirement
3. Document the requirements in a SRS
4. Validate the requirements specification
Requirements Tasks - ANSWER Understand the problem from the stakeholder's point of view, extract the
essence of the stakeholders' requirements, negotiate a set of requirements with agreement from all
stakeholders and set relative priorities, and record results in an SRS
Gathering process - ANSWER Also known as elicitation. Includes functions that the system should
perform and non-functional requirements that the system should exhibit
Requirements Elicitation - ANSWER Is critical and difficult, analysts must understand the system from
each stakeholder's point of view, analysts resolve conflicting views, analysts prioritize requirements
Elicitation Techniques - ANSWER Understand problems for the existing system by reviewing
documentation, observing current system, conducting questionnaires and interviews, and
apprenticeship; for now systems do brainstorming
Analyzing the Existing System - ANSWER What is used, what isn't, what is missing; what works well, what
doesn't; how the system is used, how it was intended to be used, what new ways we want it to be used;
risks
REQUIREMENTS ACCURATE
QUESTIONS AND ANSWERS WITH
SOLUTIONS 2024
Requirements Engineering - ANSWER The process of understanding and defining functionalities and
constraints of proposed systems. Usually the first stage of software life cycle
Software Requirements Specification (SRS) - ANSWER A document produced by requirements
engineering
Software Requirements - ANSWER Desired behavior: customers know what the system shall do and
software engineers know what to build. Means of communication with customer and many other
stakeholders
Requirements deal with - ANSWER Objects, states, and functions
Software Requirements stakeholders - ANSWER Contribute to requirements of systems. Consist of
clients, customers, end users, software engineers, domain experts, lawyers or auditors, market
researchers
Requirements Analysts - ANSWER Determine requirements
Functional Requirements - ANSWER What the system is supposed to do. Mapping from input to output
Non-functional (quality) Requirements - ANSWER Usability, performance, security, reliability,
maintainability, portability
Process constraints - ANSWER Resources, documentation, standards
Design constraints - ANSWER Physical environment, interface, users
, Requirements Problems - ANSWER Over-specification, under-specification, contradictory requirements,
ambiguous requirements, unknown requirements, bad assumptions about environment, changing
requirements
Requirements Characteristics - ANSWER Correct, consistent, complete, concise, traceable, unambiguous,
understandable, verifiable
Goal of Requirements Engineering - ANSWER Determine the requirements of a system and specify what
behavior is realized
Requirements Engineering Process - ANSWER 1. Work with stakeholders to elicit the requirements
2. Analyze and model the requirement
3. Document the requirements in a SRS
4. Validate the requirements specification
Requirements Tasks - ANSWER Understand the problem from the stakeholder's point of view, extract the
essence of the stakeholders' requirements, negotiate a set of requirements with agreement from all
stakeholders and set relative priorities, and record results in an SRS
Gathering process - ANSWER Also known as elicitation. Includes functions that the system should
perform and non-functional requirements that the system should exhibit
Requirements Elicitation - ANSWER Is critical and difficult, analysts must understand the system from
each stakeholder's point of view, analysts resolve conflicting views, analysts prioritize requirements
Elicitation Techniques - ANSWER Understand problems for the existing system by reviewing
documentation, observing current system, conducting questionnaires and interviews, and
apprenticeship; for now systems do brainstorming
Analyzing the Existing System - ANSWER What is used, what isn't, what is missing; what works well, what
doesn't; how the system is used, how it was intended to be used, what new ways we want it to be used;
risks
