Software Engineering Questions

ch4
choose the correct answer :
1-A structured document setting out detailed descriptions of the
system’s functions, services and operational constraints ,that’s type
of :
a) User Requirements
b) System Requirements
c) Customer Requirements
d) All of the above

2- …………… are real-life examples of how a system can be

used :
a) Scenarios and user stories
b) User Requirements
c) Requirement of System
d) Requirements Specification

3- ………… requirements May state what the system should

not do.
a) functional
b) non functional
c) domain
4- …….. who are responsible for installing and maintaining the
system.
a) Doctors
b) patients
c) IT stuff

5- …………….. are the descriptions of the system

services and constraints that are generated during
the requirements engineering process.

• Requirements validation
• Requirements elicitation
• System requirements
• None of them

6- …………….. are the constraints on the system from

the domain of operation

. • Domain requirements
• Functional requirements
• Non-Functional requirements
• None of them

7- ............is any person or organization who is

affected by the system in some way and so who has
a legitimate interest
a) end users
b) system management
 c) stakeholders
d) owners
8- ............describe that there should be no conflicts or
contradictions in the descriptions of the system
facilities

a) Requirements Completeness
b) Non-Functional Requirements
c) Requirements Consistency
d) Functional Requirement
9- .............describe that they should include
descriptions of all facilities required

a) Requirements Completeness
b) Non-Functional Requirements
c) Requirements Consistency
d) functional Requirement

10- Statements in natural language plus diagrams of the

services the system provides and its operational
constraints. Written for customers.
a. System requirements
b. Stakeholders requirements
c. User requirements
d. Manager requirements
11- Which of them not a reader for system
requirement :
a. system end users
b. client managers
c. client engineers
d. software developers

12- Constraints on the services or functions offered by

the system such as timing constraints, constraints on the
development process, standards.
a. Domain requirements
b. Non-functional requirements
c. Functional requirements

13- Constraints on the system from the domain of

operation :
a. Domain requirements
b. Non-functional requirements
c. Functional requirements

14- May state what the system should not do :

a. Domain requirements
b. Non-functional requirements
c. Functional requirements
15- Functional requirements should include
descriptions of all facilities required.
a. Consistent
b. Complete

16- Requirements which are a consequence of

organisational policies and procedures e.g. process
standards used, implementation requirements.
a. Product requirements
b. Organisational requirements
c. External requirements
17- Requirements which arise from factors which are
external to the system and its development process e.g.
interoperability requirements, legislative requirements.
a. product requirements
b. Organisational requirements
c. External requirements
18- Requirements which specify that the delivered
product must behave in a particular way e.g. execution
speed, reliability.
a. product requirements
b. Organisational requirements
b. External requirements
19- Requirements specification:
a. Interacting with stakeholders to discover their
requirements
b. Groups related requirements and organises them
into coherent clusters.
c. Prioritising requirements and resolving requirements
conflicts
d. Requirements are documented and input into the
next round of the spiral.
20- Requirements discovery:
a. Interacting with stakeholders to discover their
requirements
b. Groups related requirements and organises them
into coherent clusters.
c. Prioritising requirements and resolving requirements
conflicts
d. Requirements are documented and input into the
next round of the spiral.

21- Concerned with demonstrating that the

requirements define the system that the customer
really wants.
a. Requirements Validation
b. Requirements Checking
22- Which requirement Technique for Systematic
manual analysis of the requirements.
a. Test-case generation
b. c. Prototyping
c. Requirements reviews
23- Which requirement Technique for Using an
executable model of the system to check
requirements.
a. Test-case generation
b. Prototyping
c. Requirements reviews
24- Which requirement Technique for Developing
tests for requirements to check testability.
a. Test-case generation
b. Prototyping
c. Requirements reviews

25- …….. The requirements are written in natural

language on a standard form or template.
a) Design description
b) Structured natural language
c) Graphical notations
d) Mathematical specifications

26- …………. provide detailed, specific information that

is related to the application being developed
a) System models
b) System evolution
c) Appendices
d) System requirements
27- …………….are a kind of scenario that are included in
the UML .
a) System models
b) Use case
c) System evolution
d) System requirements

28- ……………..Systematic manual analysis of the

requirements.
a) Test-case generation
b) Prototyping
c) Requirements reviews
d) System requirements

29- Requirements elicitation stages include :

a) Requirements discovery
b) Requirements classification and organization
c) requirements prioritization and negotiation
d) All of the above

30-Process of gathering information about the

required and existing systems and distilling the user
and system requirements from this information.
a) Requirements discovery
b) user requirements
c) system requirements
d) none of the above
Answer the questions :
Q1. How can you check the requirements ?
1. Validity. Does the system provide the functions which best support
the customer’s needs?
2. Consistency. Are there any requirements conflicts?
3. Completeness. Are all functions required by the customer
included?
4. Realism. Can the requirements be implemented given available
budget and technology
5. Verifiability. Can the requirements be checked?

Q2. How can you check the reviews ?

1- Verifiability–Is the requirement realistically testable?
2- Comprehensibility–Is the requirement properly understood?
3- Traceability–Is the origin of the requirement clearly stated?
4- Adaptability–Can the requirement be changed without a large impact
on other requirements?

Q3.Draw the graphic of Requirements Change Management :

Q4. Problems with Natural Language:

1. Lack of clarity
2. Requirements confusion
3. Requirements amalgamation

Q5. Scenarios should include :

1. description of the starting situation.
2. description of the normal flow of events;
3. description of what can go wrong;
 4. Information about other concurrent activities;
5. description of the state when the scenario finishes.

Q6- describe requirements evolution by drawing:

Q7- What are the types of Stakeholder :

– End users
– System managers
– System owners
– External stakeholders
Q8- What are the types of requirements :
-user requirements
-system requirements
Q9- List Non-Functional Classifications...?
• Product requirements
• Organizational requirements
• External requirements
Q10- List System Stakeholder types...?
• End users
• System managers
• System owners
• External stakeholders
Q11- Draw Use Cases for the Mentcare System ?

Q12- compare between Organizational requirements,

External requirements and Product requirements?
• Product requirements
specify that the delivered product must behave in a
particular way
• Organizational requirements
Requirements which are a consequence of organizational
policies and procedures (e.g. process standards
used,implementation requirements)
• External requirements
 Requirements which arise from factors which are external to
the system and its development process (e.g.interoperability
requirements, legislative requirements

Q13- Briefly compare between User requirements and

System requirements?
• User requirements
natural language
diagrams of services and constraints
• System requirements
document of detailed descriptions of services
, function and constraints. part of contract(client and
contractor)

Q14 - Draw The Requirements Elicitation and Analysis

Process