Chapter 4 Software Engineering questions with correct answers, Exams of Software Engineering

Chapter 4 Software Engineering questions with correct answers

Typology: Exams

2024/2025

Available from 02/03/2025

EXAMDOC
EXAMDOC 🇺🇸

4.4

(9)

22K documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Chapter 4 Software Engineering questions with correct
answers
What are functional requirements ? CORRECT ANSWER Statements of services the system
should provide, how the system should react to particular inputs, and how the system should
behave in particular situations. In some cases, the functional requirements may also explicitly
state what the system should not do.
What are non-functional requirements ? CORRECT ANSWER These are constraints on the
services or functions offered by the system. They include timing constraints, constraints o the
development process, and constraints imposed by standards. Non-functional requirements often
apply to the system as a whole, rather than individual system functions or services.
What is a software requirements document ? CORRECT ANSWER The official statement of
what is required of the system developers. Should include both a definition of user requirements
and a specification of system requirements.
It is NOT a design document. As far as possible, it should state WHAT the system should do
rather than HOW it should do it.
What is the distinction between the terms 'shall' and 'should' in a user requirements document,
which is written in a natural language ? CORRECT ANSWER 'Shall' normally indicates a
mandatory requirement. 'Should' indicates a desirable but not essential requirement.
What are the main advantages of using a standard format to specify requirements ? CORRECT
ANSWER All requirements have the same format so are easier to read. The definition of form
fields meant that writers are less likely to forget to include information. Some automated
processing is possible.
What are the principal stages of the requirements engineering process ? CORRECT ANSWER a.
Requirements elicitation.
b. Requirements analysis.
c. Requirements validation.
pf3

Partial preview of the text

Download Chapter 4 Software Engineering questions with correct answers and more Exams Software Engineering in PDF only on Docsity!

Chapter 4 Software Engineering questions with correct

answers

What are functional requirements? CORRECT ANSWER Statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in particular situations. In some cases, the functional requirements may also explicitly state what the system should not do. What are non-functional requirements? CORRECT ANSWER These are constraints on the services or functions offered by the system. They include timing constraints, constraints o the development process, and constraints imposed by standards. Non-functional requirements often apply to the system as a whole, rather than individual system functions or services. What is a software requirements document? CORRECT ANSWER The official statement of what is required of the system developers. Should include both a definition of user requirements and a specification of system requirements. It is NOT a design document. As far as possible, it should state WHAT the system should do rather than HOW it should do it. What is the distinction between the terms 'shall' and 'should' in a user requirements document, which is written in a natural language? CORRECT ANSWER 'Shall' normally indicates a mandatory requirement. 'Should' indicates a desirable but not essential requirement. What are the main advantages of using a standard format to specify requirements? CORRECT ANSWER All requirements have the same format so are easier to read. The definition of form fields meant that writers are less likely to forget to include information. Some automated processing is possible. What are the principal stages of the requirements engineering process? CORRECT ANSWER a. Requirements elicitation. b. Requirements analysis. c. Requirements validation.

What are the potential problems of requirements elicitation? CORRECT ANSWER Stakeholders don't know what they really want. Stakeholders express requirements in their own terms. Different stakeholders may have conflicting requirements. Organizational and political factors may influence the systems requirements. The requirements change during the analysis process, new stakeholders may emerge and the business environment change. What should be included in a scenario? CORRECT ANSWER 1. A description of what's expected when the scenario starts.

  1. Description of the normal flow of events.
  2. Description of what can go wrong and how to handle it.
  3. Information about concurrent activities.
  4. Description of the system state when the scenario finishes. What is a use-case? CORRECT ANSWER A use-case identifies a typical interaction with a system and the actors (human or computer) involved in that interaction. What is ethnography and how is it used in requirements elicitation? CORRECT ANSWER Ethnography is an observational technique that can be used to understand social and organizational requirements. It helps analysts discover implicit system requirements that reflect the actual rather than the formal processes in which people are involved. What checks should be applied during requirements validation? CORRECT ANSWER 1. Validity checks
  5. Consistency checks
  6. Completeness checks
  7. Realism Checks
  8. The verifiability of the requirements should be assessed. List 3 techniques in validating requirements? CORRECT ANSWER 1. Requirements reviews (Systematic manual analysis of the requirements.)