IDHAYA ENGINEERING COLLEGE FOR WOMEN

CHINNASALEM 606 201.

Reg. No.:
CIAT II
CS6403/ Software Engineering
(Common to B.E CSE & B.Tech I.T)
Year/Sem: II/IV
Date
: 13. 03. 2015

Maximum: 60 marks
Time : 1 hour 40 mins

PART A (6 x 2 = 12 marks)
Answer ANY 6 Questions
1. What is requirement engineering?
Requirement engineering is the process of establishing the services
that the customer requires from the system and the constraints under
which it operates and is developed.
2. Define software prototyping.
Software prototyping is defined as a rapid software development for
validating the requirements
3. What are the characteristics of SRS?
i. Correct The SRS should be made up to date when appropriate requirements are
identified.
ii. Unambiguous When the requirements are correctly understood then only it is
possible to write an unambiguous software.
iii. Complete To make SRS complete, it should be specified what a software designer
wants to create software.
iv. Consistent It should be consistent with reference to the functionalities identified.
v. Specific The requirements should be mentioned specifically.
vi. Traceable What is the need for mentioned requirement?
4. What are functional requirements?
Functional requirements are statements of services the system should
provide how the system should react to particular input and how the
system should behave in particular situation.
5. Define Petri Net.
Petri nets
a. Technique for specifying systems that have potential
problems with interrelations
A Petri net consists of four parts:
b. A set of places P
c. A set of transitions T
d.
An input function I
e. An output function O
6. What are non-functional requirements?
Non-functional requirements
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.
7. Define Ethnography
Ethnography is effective for understanding existing processes but
cannot identify new features that should be added to a system.
8. What are the requirement engineering processes?
Feasibility studies
Requirement elicitation and analysis
Requirements validation
Requirement management

9. What are the system requirements?

System requirements set out the systems functions, services and operational constraints in detail.
The system requirements document should be precise. It should define exactly what is to be
implemented. It may be the contract between the system buyer and the software developer
10. What is the outcome of feasibility study?
The outcome of feasibility study is the results obtained from the following questions:
Which system contributes to organizational objectives?
Whether the system can be engineered? Is it within the budget?
Whether the system can be integrated with other existing system?

1.

PART B
Answer ALL Questions
a Explain in detail about Functional requirements. (16)

Functional requirements for the MHC-PMS

A user shall be able to search the appointments lists for all clinics.
The system shall generate each day, for each clinic, a list of patients who are
expected to attend appointments that day.
Each staff member using the system shall be uniquely identified by his or her 8digit employee number.
Requirements imprecision
Requirements completeness and consistency
(or)
b. Explain the software requirement document (16)

Chapter

Description

System requirements
specification

This should describe the functional and nonfunctional

requirements in more detail. If necessary, further detail
may also be added to the nonfunctional requirements.
Interfaces to other systems may be defined.

System models

This might include graphical system models showing the

relationships between the system components and the
system and its environment. Examples of possible

models are object models, data-flow models, or semantic

data models.
System evolution

This should describe the fundamental assumptions on

which the system is based, and any anticipated changes
due to hardware evolution, changing user needs, and so
on. This section is useful for system designers as it may
help them avoid design decisions that would constrain
likely future changes to the system.

Appendices

These should provide detailed, specific information that

is related to the application being developed; for
example, hardware and database descriptions. Hardware
requirements define the minimal and optimal
configurations for the system. Database requirements
define the logical organization of the data used by the
system and the relationships between data.

Index

Several indexes to the document may be included. As

well as a normal alphabetic index, there may be an index
of diagrams, an index of functions, and so on.

2. a. Explain about Requirement Engineering.

a. Feasibility study
b. Requirements elicitation and analysis;
c. Requirements validation;
d. Requirements management.

(or)
b Explain in detail about non functional
requirements. 16)

3. a. i) Write note on Petri net (8)

A major difficulty with specifying real-time systems is timing
Synchronization problems
Race conditions
Deadlock
Often a consequence of poor specifications
Petri nets
Technique for specifying systems that have potential problems with interrelations
A Petri net consists of four parts:
A set of places P
A set of transitions T
An input function I
An output function O

ii) Briefly write requirement

change management (8)

(or)
b.

Explain classical analysis in detail 16)