QB104462

Sri Vidya College of Engineering and Technology Question bank – UNIT 2
UNIT 2 – 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.
CS8494- Software Engineering Prepared by P.Ramya, AP/CSE

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.
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

15 MARKS
1. write short notes on IEEE definition for software Requirement Document(8m)
• Preface
• Introduction
• Glossary
• User requirements definition
• System architecture
• System requirements specification
• System models
• System evolution
• Appendices
• Index
2. Explain in detail about the process of requirement elicitation and analysis (7m)
Requirements discovery,
Requirements classification and
organization, Requirements prioritization and
negotiation, Requirements specification.
3. Write short notes on petri nets and data dictionary with necessary
diagram Refer question 17 and 18
4. Explain in detail about structured analysis.

One view of requirements modeling, called structured analysis, considers data and
the processes that transform the data as separate entities.
Data objects are modeled in a way that defines their attributes and relationships.
Processes that manipulate data objects are modeled in a manner that shows how they
transform data as data objects flow through the system.
DFD level 0( context level diagram)
DFD level 1 and 2
5. Explain in detail about requirement validation and management

Refer question 15 and 16
Requirement management – planning and change management
ASSIGNMENT
1. Draw use case diagram form online booking system

2. Draw use case diagram for ATM and Library management system
3. Draw DFD diagram food ordering system and library management system

QB104462

Uploaded by

Copyright:

Available Formats

QB104462

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

QB104462

Uploaded by

Copyright:

Available Formats

Sri Vidya College of Engineering and Technology Question bank – UNIT 2

UNIT 2 – TWO MARKS

1. What is functional requirement?

CS8494- Software Engineering Prepared by P.Ramya, AP/CSE

7. What are the activities included in requirement engineering process

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

CS8494- Software Engineering Prepared by P.Ramya, AP/CSE

o Information about other concurrent activities;

14. What is use case?

15. How the requirements are validated?

CS8494- Software Engineering Prepared by P.Ramya, AP/CSE

1. write short notes on IEEE definition for software Requirement Document(8m)

4. Explain in detail about structured analysis.

5. Explain in detail about requirement validation and management

1. Draw use case diagram form online booking system

CS8494- Software Engineering Prepared by P.Ramya, AP/CSE

You might also like