ADVANCED SOFTWARE ENGINEERING

UNIT-II QUESTION BANK

REQUIREMENTS ANALYSIS AND SPECIFICATION

PART – A (One mark questions)

1. What are the types of requirements ?​

a) Availability​
b) Reliability​
c) Usability​
d) All of the mentioned
Ans : d) All of the mentioned

2. Select the developer-specific requirement ?​

a) Portability​
b) Maintainability​
c) Availability​
d) Both Portability and Maintainability
Ans : d) Both Portability and Maintainability

3. The user system requirements are the parts of which document ?​

a) SDD​
b) SRS​
c) DDD​
d) SRD
Ans : b) SRS

4. _________ and _________ are the two issues of Requirement Analysis.​

a) Performance, Design​
b) Stakeholder, Developer​
c) Functional, Non-Functional​
d) None of the mentioned
Ans : b) Stakeholder, Developer

5. The requirements that result from requirements analysis are typically expressed from one of three
perspectives or views.WhaT is that perspective or view ?​
a) Developer​
b) User​
c) Non-Functional​
d) Physical
Ans : d) Physical

6. What is the first step of requirement elicitation ?​

a) Identifying Stakeholder​
b) Listing out Requirements​
c) Requirements Gathering​
d) All of the mentioned
Ans : a) Identifying Stakeholder
7. What kind of approach was introduced for elicitation and modelling to give a functional view of the
system ?​
a) Object Oriented Design (by Booch)​
b) Use Cases (by Jacobson)​
c) Fusion (by Coleman)
d) Object Modeling Technique (by Rumbaugh)
Ans : b) Use Cases (by Jacobson)
8. Which two requirements are given priority during Requirement Management of a product ?​
a) User and Developer​
b) Functional and Non-functional​
c) Enduring and Volatile​
d) All of the mentioned
Ans : Enduring and Volatile

9. Considering the example of issue/return of a book, cataloging etc. in a library management.What type
of management requirement is being depicted here?​
a) Enduring​
b) Volatile​
c) Both Enduring & Volatile​
d) All of the mentioned
Ans : a) Enduring

10. Why is Requirements Management Important ? It is due to the changes​

a) to the environment​
b) in technology​
c) in customer’s expectations​
d) in all of the mentioned.
Ans : d) in all of the mentioned.

11. What functionality of Requirement Management Tool (RMT) is depicted by the statement: “the tool
should be able to automatically detect relations between artifacts. For example information retrieval
techniques, monitoring of change history, naming schemas or model transformations.”​
a) Automatic Link Detection​
b) Documentation Support​
c) Graphical Representation​
d) Automatic Link Creation and Change
Ans: a) Automatic Link Detection

12. Which of the following property does not correspond to a good Software Requirements Specification
(SRS) ?​
a) Verifiable​
b) Ambiguous​
c) Complete​
d) Traceable
Ans : b) Ambiguous

13. Which of the following property of SRS is depicted by the statement : “Conformity to a standard is
maintained” ?​
a) Correct​
b) Complete​
c) Consistent​
d) Modifiable
Ans: b) Complete

14. The SRS document is also known as _____________ specification.​

a) black-box​
b) white-box​
c) grey-box​
d) none of the mentioned
Ans: a) black-box
15. Which of the following is included in SRS ?​
a) Cost​
b) Design Constraints​
c) Staffing​
d) Delivery Schedule
Ans : b) Design Constraints

16. Consider the following Statement: “The data set will contain an end of file character.”What
characteristic of SRS is being depicted here ?​
a) Consistent​
b) Non-verifiable​
c) Correct​
d) Ambiguous
Ans: d) Ambiguous

17. Keeping the requirements of QFD in mind which of the following is not an example of an Expected
Requirement ?​
a) Ease of software installation​
b) Overall operational correctness and reliability​
c) Specific system functions​
d) Quality graphical display
Ans : c) Specific system functions

18. Which of the following Requirement Elicitation Techniques is applicable to messy, changing and
ill-defined problem situations ?​
a) Quality Function Deployment (QFD)​
b) Prototyping​
c) Soft Systems Methodology (SSM)​
d) Controlled Requirements Expression (CORE)
Ans: c) Soft Systems Methodology (SSM)

19. To ensure that a given root definition is rigorous and comprehensive, The Lancaster team proposed
several criteria that are summarized in the mnemonic CATWOE in Soft Systems Methodology
(SSM).Which of the following alphabet is representing an entirely different meaning to SSM ?​
a) C – Customer​
b) A – Actor​
c) T – Transformation​
d) E – ER Model
Ans: d) E – ER Model

20. The SRS document is also known as _____________ specification.​

a) black-box​
b) white-box​
c) grey-box​
d) none of the mentioned
Ans: a) black-box

21. Which of the following is included in SRS ?​

a) Cost​
b) Design Constraints​
c) Staffing​
d) Delivery Schedule
Ans : b) Design Constraints
22. SRS consists of?​
a) Problem statement​
b) Product design​
c) Problem statement & Product design​
d) None of the mentioned
Ans : c) Problem statement & Product design

23. Which is true about functional requirements?

a) A functional requirement is also called behavioral requirement
b) A functional requirement includes development and operational requirements
c) A functional requirement is a statement of how a software product must map program inputs to
program outputs
d) None of the mentioned
Ans: c) A functional requirement is a statement of how a software product must map program
inputs to program outputs

24. Which of the following does data requirements allow for data?​
a) Entering data​
b) Leaving data​
c) Storing data in product​
d) All of the mentioned
Ans: d) All of the mentioned

25. Technical level abstraction includes ______________​

a) User level requirement​
b) Physical level requirement​
c) Operational level requirement​
d) All of the mentioned
Ans: d) All of the mentioned

PART - B – TWO MARKS

1.​ What is functional requirement?

These are the Statements of services the system should provide, how the system
should react to particular inputs and how the system should behave in particular situations.
May state what the system should not do.
2.​ What is non functional requirement?

These are Constraints on the services or functions offered by the system such as
timing constraints, constraints on the development process, standards, etc. Often apply to the
system as a whole rather than individual features or services

3.​ What are the types of requirements?

•​ User requirements
Statements in natural language plus diagrams of the services the system
provides and its operational constraints. Written for customers.
•​ System requirements
 A structured document setting out detailed descriptions of the system’s
functions, services and operational constraints. Defines what should be
implemented so may be part of a contract between client and contractor.
4.​ How will you classify non functional requirements?
•​ Product requirements - Requirements which specify that the delivered product must
behave in a particular way e.g. execution speed, reliability, etc.
•​ Organizational requirements- Requirements which are a consequence of
organisational policies and procedures e.g. process standards used, implementation
requirements, etc
•​ External requirements - Requirements which arise from factors which are external to
the system and its development process e.g. interoperability requirements, legislative
requirements, etc.
5.​ What are the properties of non functional requirements?
•​ Speed
•​ Size
•​ Ease of use
•​ Reliability, Robustness, Portability
6.​ What is SRS?
The software requirements document is the official statement of what is required
of the system developers. It should include both a definition of user requirements and a
specification of the system requirements. It is NOT a design document. As far as
possible, it should set of WHAT the system should do rather than HOW it should do it.
7.​ What are the activities included in requirement engineering process
•​ Business (feasibility study)
•​ Discovering requirements (elicitation and analysis)
•​ Converting these requirements into some standard form (specification)
•​ Checking that the requirements actually define the system that the customer wants
(validation)
8.​ What are the problems of requirement analysis or elicitation?
•​ Stakeholders don’t know what they really want.
•​ Stakeholders express requirements in their own terms.
•​ Different stakeholders may have conflicting requirements.
•​ Organisational and political factors may influence the system requirements.
•​ The requirements change during the analysis process. New stakeholders may emerge
and the business environment may change.

9.​ What is feasibility study?

A feasibility study is a short, focused study that should take place early in the
requirement engineering process. It should answer three key questions.

•​ Does the system contribute to the overall objective of the organization?

 •​ Can the system be implemented within schedule and budget using current
technology?
•​ Can the system be integrated with other systems that are used?
•​
10.​What do you mean by stakeholders?

Stakeholder is anyone who must have some direct or indirect influence on the system
requirements. Stakeholder includes end users who will interact with the system and anyone
else in an organization who will be affected by it. Other system stakeholder’s might be
engineers who are developing or maintaining other related systems, business managers,
domain experts and trade union representative.

11.​What is requirement elicitation or discovery?

The process of gathering information about the required and existing systems and
distilling the user and system requirements from this information. Source of the
information during the requirements discovery phase include documentation, system
stake holders and specification of similar systems.

12.​What are the types of interviews?

•​ Closed interviews based on pre-determined list of questions
•​ Open interviews where various issues are explored with stakeholders.
•​
13.​What is scenario?
​ Scenarios are real-life examples of how a system can be used.
•​ They should include
o​ A description of the starting situation;
o​ A description of the normal flow of events;
o​ A description of what can go wrong;
o​ Information about other concurrent activities;
o​ A description of the state when the scenario finishes.
o​
14.​What is use case?

Use-cases are a scenario based technique in the UML which identify the actors in an
interaction and which describe the interaction itself. A set of use cases should describe all
possible interactions with the system. High-level graphical model supplemented by more
detailed tabular description. Sequence diagrams may be used to add detail to use-cases by
showing the sequence of event processing in the system.

15.​How the requirements are validated?

It is the process of checking that requirements actually define the system that the
customer really wants. It overlaps with analysis as it is concerned with finding
problems with the requirements.
Validity check
 Consistency check
Completeness checks
Realism checks
Verifiability
16.​List out the requirement validation techniques
•​ Requirements reviews- Systematic manual analysis of the requirements.
•​ Prototyping- Using an executable model of the system to check requirements.
Test-case generation - Developing tests for requirements to check testability.
•​
17.​What is data dictionary?
A data dictionary stores information about data items found in a DFD
•​ Name – identifies data item
•​ Alias – identifies other names
•​ Data structure ( type) – type of data( integer, char)
•​ Description – indicates how a data item is used
•​ Duration – life span of data
•​ Accuracy- high, medium low
•​ Range of values – allowable values of data item
•​ Data flow – identifies process that generate data
18.​What is a Petri net?
A petri net is a form of finite state machine useful in modeling concurrency and
asynchronous communication. It is used to describe and analyze the structure and
information flow in the system

19.​“An SRS is traceable “. Comment.

An SRS is traceable if the origin of each of its requirement is clear. Traceability is of two
types. They are a. Forward traceability b. backward traceability Forward traceability
means that each requirement should be traceable to some design and code elements. Backward
traceability requires that it be possible to trace design and code elements to the requirement they
support
20.​What are the components of State-oriented notations?
●​ Decision Table
●​ Even Table
●​ Transition Table
●​ Finite state mechanism
●​ Petri nets

PART – C

1.​ (i) Differentiate functional and non-functional requirements.

(ii) Give the steps involved in initiating requirements engineering

2.​ (i) What are called as non-functional requirements? Explain in detail.

 (ii) Summarize on user requirements and system requirements in detail

3.​ (i)Explain the different ways of writing a system requirement specification.

(ii) Describe the spiral view of system requirement.

4.​ Analyze about the requirement engineering process and how the requirements are
managed.

5.​ Explain in detail about the process of requirement elicitation and analysis (7m)

6.​ Explain in detail about requirement validation and management