2.

3 Software Engipeering

Short Questions with Answers

Q1. What are the requirement engineering process functions.
Answer :
1 Inception
2 Elicitation

3 Elaboration

4 Negotation
5 Sepcification
6. Val1dation

7 Requirerments managements
02. List the elements of requirements models.
Answer :

1 Scenario based elements

2 Flow oriented elements

3 Class based elements

4. Behavioural elements
elaboration.
Q3. Define inception, clitation and
Answer :
problamatic for
means begining. It is usuall said that, "Will begining is half done". But it is aways
Incaption
he develope that, from where to start. engineering
out the truth or replay from "any body" In relation with reauirement
Elication means, 'to draw
to define what is required.
lication is a task that helps the customer
the model focuses on "how the end user wull interact with the
Elaboration is a analsysis modeling" action
ystem

4. List out the eliciting requirements.

Answer :
carried out by series of following steps,
Eliciting requirements' step is
1.
Collaborative requirements gathering
2 Quality function development
3 User scenaring
4 Elicitation work product.
R5. analysis modeling.
What are techniques &
Answer :
are
The two analysis modeling techniques
1 Structured analysis
2 Object oriented analaysis
Xerox/Photocopying of this book is a CRIMINAL Act. Anyone found guity is LIABLE to face LEGA procaedings
Narring
 Q6. Define ngineering
eliments?scenario based modeling and its There are two types of models.
Answer: 1 Dataflow model
In
scenario
in usersbased modeling the system is
represented
eiements are point of view.
2 State cahrt diagram
Scenario based Q13. What is data model?
1
Use are diagrams Answer:
2
3
Activity diagrams Data modelling is the basic step in the
an.
Swim lane diagrams modelling. In data modelling in the
Q7. What is an examined independent of processing. data objects
analysis? analyst and what is role of Q14. What is data object,
attribute relations
Answer : Answer:
The "software
build the model engineer" also called as
using requirement stated"analysis"
Data object is a collection of attributes tha.
as an aspect, characteristics, quality or
customer. by the
object.
desciptor
of:
Q8. What is the role of Attrbutes are used
domain analysis? to name an instance of
Answer: object.

Domian analysis is "the Relationship represents the connection betue

and specification of common identification" analysis the data objects.
specific application domain". requirements from a
Q15. What is object model?
Q9. VWhat is system mode? Answer :
Answer:
Object model is reated for the system proces
The system model is a graphical representaion objcet oriented programming approach. These
that is used to describe various processes of the system. created for interactive systems.
Q10. What are the types of system model? Q16. What is structured methods?
Answer : Answer :
1 Context model
Applying the structured methods mez
2. Behauioral model designing different models to represent that parti
Data model system.
3

4 Object model. Q17. Define feasibility study?

Q11. What is context model? Answer:
Answer : The feasibility study forms the initial step n
Context model is a graphical representation of requirements engirneering process.
specified.
the system in which the system boundaries are The feasibility study process when
system
This is the model which represents the information related to the following aspects.
enviroment in which system is working. 1. The business requirements
behavioural model?
Q12. What is 2 The context to which current syster

Answer : capable of satisiyingof the syste

aa ad tonde[cribe the
Behavioral models 3. A brief description of the system.
behavior ofa sysan
procaed
Overall this bool e a CRIMINAL ActAnyone found guity is
Xerox/Photocopying of LIABLE to face LEGAL
rring :
2.5
Software Engineering
Q18. What is cardinaltiy and modality?
Answer:

Cardinality in data modelling, cardinality specified howthe number of occurrences of one

tothe number off occurrences of another object. object is related
Modality indicates tohether or not a particular data object must participate in the
relationship.
o19. Define view points.
Ans:er:

Inthe technical aspects, the sources which remain information providers in the requirerments discovery
phase are often referred to as "view points.
020. Define use cases?
Answer :

Use case is the essential feature of the UML notation used in 0 system models. Use case acts as a scenario
in the real world concept for describing the requirement.
 Software Engineering 2.6
Essay Questions with Answers
2.1 SOFTWARE REQUIREMENTS
Q1. Describe functional and non functional requirements of software.
Answer:
Software system requirements can be classified as,
1 Functional requirements
2. Non -functional requirement
1
FunctionalRequirements
(i) Functional requirements should describe all the required functionality or system.
(ii) The customer should provide state out of service. It should be clear how the system should react to
particular inputs and how a particular system should behave in particular situation.
(ii) Functional requirements are heavily dependent upon the type of software, expected uses and the
type of system where the software is used.
(iv) Functional requirement may be high level statements of what the system should do but functional
system requirements should describe the system services indetail.
Problems associated with requirements.
(i) Requirements imprecision
(üi) User intention
(i) Developer interpretation
(iv) Requirement completeness and consistency
2.. Non - Functional Requirements
(i) The non - functional requirements define system properties and constraints. Various properties of a
system can be,
(a) Rehabilitee
(b) Storage requirements
Constraints of the system can be
Input
Output
Capability
System representations etc.
(ii) Process requirements may also specify programming language or development method.
lii) Non- functional requirements are more critical than functional requirements. If the non -functionl
is of no use.
requirements do not meet then the complete system

2. What are the user requirements? Explain it.

nswer:

ser Requirements
describefunctional and non functional requirements in such away that they are understandable
It should technicalIknowledge.
who don'tt have detailed
system uses
book is a CRIMINAL Act. Anyone found guilty is LIABLE to face LEGAL proceedings
Xerox/Photocopyingofthis
rning:
.7
|set requiremet are defined usinu nowal
ngnaqe,tables and d qrams because there aethe
presentationsthat can be understood by all
uwTS
Various problms that can arise nhe
quiementspecitications when reuirennents ore qiven
natural languaqe.
Lack of Varity
Sometimes requirements are qiven in ambiquous
hanner. It is expected that text should help in clear and
orecise understanding « the requirements.
Requirements Confusilon
There may be confusion in functional
equirements and non -lunctionalrequirements system
goals and design information.
Requirement Mixture
There may be a chance of specifying several
equirements together as a single requirement.
Guidelines for writing user Requirements
Prepare a standard format and use it for all
requirements.
Apply constituency in the language use -'shall'
for mandatory requirements 'shauld' for
desirable.
3. The text which is mentioning the key
requirements should be highlighted.
Avoid the use of computer jargon. It should be
written in simple language.
Q3, Explain the system requirements and
interface specification.
Answer :
System Requirements
System requirements are more detailed
Specification of system functions, services and
Constraints than user requirements.
They are intended to be a basis for designing
he system.
They may be incorporated into the system
Contract.
The system requirements can be expressed using
System models.
The requirernents specify what the systern does
and design specifies how it does.
System reguirements should simply describe the
kternal behaviour of the systern and its operational
Warring : Xerox/Photocopying of thls book s a CRIMINAL Act. Anyone found guilty is UABLE to face LEGAL procadings
Sottware Enginerring
esary o ive all the eqiremets in tletail
Uolly valual layunw is uel t wite ytor
requements speifit ain al user reiremerts
Interface Speifltation
Soneinvs thee is alreatly vzistiy ystern wheh
can be used with the newly rvatvl twae ysterr
This conjunetion of oll oycte with rew ycturt is talleal
syslem intertace
There are three types of interfacos that taf he
leined.
Procedural Interfaces
These are popularly knun ns npplieatin
prograrmrming interface (APl) such ptuuus
are intended'b offer servite that tfiay he upr)
by calling procedures.
2. Data Structure
Data structure are the descriptors of data. They
play an irnportant role in oranization of data
for given algorithrn.
The data structures can be passed rorn ne uh
systern to anothe.
3 Representation of Data
This level of specification is used certain
prograrnning lanquages like ADA
For realtirne applications these kind cf interface
are ten useful.
The intertace should be defined in unarnbgrs
manner but such interfaces can be understori
only after special training.
Q4. Describe the software requirenent
documents.
Answer:
It is the specification of the ystern. It shesd
include both a definition and a specification of
requirernents. It is not a design docurnent. As fas as
possible, it should set of what the systern shoud do
rather than how it should do it.
Software Requirement Specification
It provides a basis for creating the sttware
requirernent specification (SRS) The SRS is uetul in
estimating cost, planning tearn actvities, pertorrnirg tah
 Sottware Eugueerlng
ad ta hing (he lealls prooress When SRS consists of allthe
develytent a tivity throughout the (i)
related to be functionality rperequiforrmerarne
attributes, designs constraints o
lvpicallv sottware designers Ise lELE STD 830 interfaces. exler
188 av the basis for the entie software
specification. When labels and| corresponding
lhe stanlanltemplate for writing SRS IR as given (ii)
are mentionedIfor allthe figures, relerer
bekow

Documents title
and tables in the
SRS.
daga
the inns.
n
(ii) When expected responses to
Author (S) is mentioned by considently validih,
invalidity of an input.
Attiation
3. Unambiglous
Addhess
When requirements are understood corter
Date then only unambignious SRS can be writen
Docment verslon. means only one interprectation can be m
I Intoduction only one interpretation can be made froma
specified requirements.
Ppose of this document In other words, there should be an unig
Scope of this document interpretation of each statement in SRS. I
Overview particular term there are multiple meanings th
those terms there are multiple meanings the
General description those terms should be mentioned in gross a
terms should be mentioned in gross any w
Functionalrequirement propose meaning. The requirements shouldn
lntertace nequiement be mentioned in the same manner.
5
Retomance requirement 4. Consistent
Nonfunctional: If there are not conflicts in the specitie
Security reliability requirement then SRS is said to be consistent
Portability, reusability Three types of conflicts that may occur in aS
7. Design constraints (1) Logical or Temporal Conflict
When one requirement specifies that eve
Operation scenarios x should occur before event y and if anoth
Peliminary schedule requirement specifies that event yshou
occur before event x. Then it create
10 Budget
temporal conflict.
11. Appndices (ii) Characteristics conflicts of real-wof
Q5. What are the characteristlcs of SRS. object
Answer: Ifone requirement suggest to make USe
1 Correct "radio button" and other specifies
"check box button" then represen
The SRS must be coect. That means all the
requiennents must be conectly mentionus, or the conflictingcharacteristics.
equinements must be realistic by nature. For
(iii) Two different description about
instance whie developing a world processing same real world object
sottware, if there is arequirement lor spell check If onne requirement is specifying 'enter'a
fac lity and if software can't find the speling errors other specifies 'submit'. Then it desc
from the doument, then that means requirement one and the same action. This can create
0s incorrect conflict.
5
2 Complete Stability
specified
Iomake the SRScomplete,itshoukdtobe create
In SRS, it is not possible to specify allth
want a allth
what asotvare designer complete only in requirements.
essential
The SRS must contain must!
wofhware The SRSis said to be
followinq situations clear and requirement
explicit. each requirement
t this book is a CRIMINAL AG. Anyone found guity is LARI E di
 Sottware Engineering
2.9
Verifiable
6
The SRS should be written in such a manner thet the reouteneuts thal ae sefed within mus e
satisfied by the software.
Tracable
1
If origin of requirement is properly given or reference of the veuiveeuts are coretly mentoied When
such arequirement is called as traceable requirement.
Various types of tractability are,
Forward tracability : Each requirement is referred in the SRS document by its unque number (n
reference number.
(i) Backward traceability
then it is backward traceability
It the reterence to the requirement is mentioned in earlier docurment,

92 REQUIREMENT ENGINEERING PROCESS

engineering process activities.
06. With the help of neat diagram depict the requirement
Answer :
understand the system requirements. The proceeS
The requirements engineering processes are used to
used for requirement engineering vary widely.
maintain system requirement specification docurment.
The goal of engeering process is to create and

Requirements Requirements Requirerments

Feasibility Elicitation specification
validation
study and analysis

System models Used and system

Feasibility requirements
DED State
report chart model

SRS
ER Class
model
diagram
Engineering Process
Figure : Requirement validation of
various activities such as discovery, analysis and
A requirement engine is a process in which
ysTem requirements are done. requirements validation
feasibility study of the system and ends up with
Itbegins with activities are arranged in theiterative manner. In the early
activity where the
This process is athree stage understanding the system by understandingthe high- level non
is spent on
stage of this process most of the time
requirements.
and user
hunctional Irequirements
generic activities that are
common to all processes
are,
1ne
1 Requirement clicitation
2 Requirement analysis
3 Requirement validation
4 Requirement management.
engineering process can also be viewed as structured analysis method in which the system is
Requirement system prepared.
analWarningysis :fullyXeroxdsome
model are
JPhotocopving of this book is a CRIMINAL Act. Anyone found guilty is LIABLE to face LEGAL prcceedings
 Software Engineering
Q7. Explain about feasibility studies.
Answer:
Feasibility Studies
while.
Itis astudy made to decide whether or not the nroposed system is worth
The focus of feasibility study is to check.
1 If the system contributes to organizational objectives.
2
Ifthe system can be engineered using current technology.
3 If the system is within the given budget.
4. Ifthe system can be integrated with other useful systems.
The implementation of feasibility siudy is based on the information assessment, intormation collection:
report writing.

While performing the feasibility study, following questionnaires to the people in the organization sho°:
asked.
1 What if the system wasn't implemented
2 What are current process problems.
3 How will the proposed system help.
4 What willbe integration problems.
5 In new technology needed? with what skills?
6 What facilities must be supported by the proposed system.
Types of easibility
1. Technical feasibility
The technical feasibility is the study of configuration of the system. While studying the system ccafiguat
followingthings are to be studied.
i) What is that exact configuration of the system?
ii) How many workstation are required.
iil How diferent units are inter connected? and are they
working smoothly while interaction nected
What should be the speed at which the input is given and at
generated.
what speed the output has to
2. Operational Feasibility
It is based on the human factors and political as pects. The
answers in the following question. operational feasibility can be performed
(i) What change will be brought with the system.
(i) What are the factors that are disturbing organizational structive
(ii)Which are the new skills that are required for
3. Economic Feasibility imprOvement in operations.
This kind of feasibility is donefor costofbenefit analysis.
In this
are identified andthe corresponding costs are determined. If thestudy
identified
the benefitsof are Cost syst
effectiver
proposed
thenthe decision is made whether or not to design
benefits
the
and
4.
ManagementFeasibility implement the system.
It means checking whether the management will accept the proposed project or not. If the top
agree upon the project idea
management does not then it is
considered
: Xerox/Photocopying ofthis book issa CRIMINAL Act. Anyone found guilty is asLIABLE
a nonto face LEGA
project
feasible proceet
Warning
 Software Engineering
LegalFeasibility
5. findlv outtwhether the proposed projectis uly acceptable or not
lt means
Tine Feasibility
It means
identitvingwhether proposed project wl be completed with in
the the stipulated time o not If
the proects uns tor a long time then it is Considero, to be infeasible project.
Social Feasibility
feasibility.
1.
Whether the roject will|be acceptable by the Peopl o not is called a social
Q8. Explainthe requirement elicitation and anal-sis process.
Answer

Proces
Requirennent Requirements
clasification prioritization
discovery

Requirement Requirements
discovery documentation

Analysis Process
Figure : Requirement Elicitation and possible
elicitation means discovery of all posible requirements. After identifying all
Requirement
Tequirements the analusis on these requirements can be done. certain information such
end-users or customers in order to find out
Sottware engineers communicate the expected performance level of the system.
From
from the system, the
ds: application domain, expected services decided.
this information even constraints of the system can be
1 Stake Holders person(s) who will be
commonlvused term insoftware engineering. The stake holders means the
This is a
affected bythe sñstem. engineers can be stake holders.
engineers or. Software
Example : End uses, system maintains
2
Kequirement Elicitation and Analysis Process
a Requirement Discovery
withthe customers the requireents can be identified
By having effectivee communication
b) Kequirement Classification and Discovery
be catesorized systematically depending upon their nature.
Allthe unstructured requirements can
c)
Requirenment Prioritization
There are some conflicting requirements. Hence the requirements are prioritized first If there are
are made and only realistic prioritized
some unrealistic requirements the negotiations requirements
are collected. If any cconflict occurs then it is reSolved by requirements engineers.

d) Requirement Documentation
This is the speecification of allthe requirements. And an important requinenment document is ereated.

CRIMINAL Act. Anyone found guilty is LL\BLE to tace LEGAL proceedings

of this book is a
hotocopying
Software Engineering
3. Requirement Discovery abit the Sstem The sourves of information for
Itgathering
means finding all relevant intormation
are documentation. requirens s
sstemstakehoders and specification some other system which
kind
Various methods of requirement discovery a Conducting
Interviews
ü)
Obervations
Creating use case scenario0s
Q9. State and explain various requirements validation techniques. Also discuss requiremer
reviews.
Answer :
Definition
Detinitionvalidation is a proces in which it is checked that whether the gathered requirements represe
the same systenm that customer really wants.
validat
In requirements validation the requiement erors are fixed. Requirements error COsts are high so
is very important. Fixing an implementation error.
Requirement checking can be done in following manner.
(1) Validity: Does the system provide the functions which best supports the customer sneeds?
(Ü) Cusistancy :Are they any requirements conficts?
(iü) Completeness: Are allfunctions required by the customer incuded?
(iv) Realism : Can the requirements be implemented according to budget and technology.
(v) Venifiability : Can be requirements be checked.
Requirements Validation Technics

Requirement
reviews

Test Requirement
case validation
generaton techniques
Prototyping

1. Requirements Reviews
Requirement reviewis a systematic manual analysis analysis of the requirements
The requinement review should be taken out after formulation of requirement definition And b'
in revieus
the customer and contractor staff should be involved
(a Godcommunications should take please between developers, customers and users. Such a hea
communication helps to resolve problems at over easily stage
2. Prototyping
using exicutable model ofs ,
The requirements can be checked
Testing Case Generation
3.
tests occurred developed for requirements. The requirement checkcanb
In this techniques the various
carried out with
testable?
(0) Verifiability : Is the requirement realistically
properiy and derstood?
R) Comprehensibility : Is the requirement
(üi)
Traceability Is the origin of the requirement cleary stated?
Adaptability Can be requirement be changed without alargeimpact on other requirernens
(iN of this book is a CRIMINAL Act. Anyone found guity is LIABLE to face LE
XeroxPhotocopying
Warning:
 Software Engineering
13
about
Discuss requirement management?
Answer

Requirement management is the process of managing change requirement during the requirement
gineeringprocess andI system development.
Requirements are always incomplete and inconsistent. New requirements occur during the process as
business beeds change and a better understanding of the system iss developed.

SystemCustomers may specity the requirements form business perspective that can conflit which end user
requiements.
the development of the system. Its business and the technical l environment may get changed.
l During
-Ling and Volatile Requirements
Eduring Requirements
of the organisation. These
These are the stable requirements that are derived from the core activities
Cnirements are dependent open the application domain of the software.
olatite Requirements
that those requirements may get changed during the
For certain requirements it there is a possibility
then such requirements are called volatile requirements.
elopment stage or after the system becomes operational,
Ipes of Volatile Requirements
Mutable Requirements called as
change in the environment, if the requirements get change then such requirements are
If due to
mutable requirement.
2 Consequential Requirements
due to introduction of computer based systems, such requirements ars
Requirement that gets changes
called consequential requirements.
. Emergent Requirements get
the system during the development stage certain requirement may
Bue to customers understanding of
changed.
Compatibility Requirement in an organisation are called
which depend upon the specificsystem or business process
Kequiremnents
compatible requirements.
quirement Management Planning
Requirements
Requirement are individually identifies
identification

Process plan followed when

Change management analysis a requirement change
process

The amount of information about

Traceability requirement relationship is
maintained
policies

Thetool support which is required to

Case tool managed requirement
support
changes
CRIMINAL Act. Anyone found guilty is LIABLE to face LEGAL proceedings
m9: book is a
of this
XeroWPhotocopying
 f2222

Software Engineering
Q1. What is traceabilitv? Explain different types of
Answer :
traceability.

Traceability
It is one of the
essential
requirements traceability is used activities of good requirement management, which helps to
to ensure that the right products are being developed at identty skn
Software development life cycle. It helps to reduce the effort required to each phase ol
determine the impact of requested
in order to trace the progress of the software ch
development.
In simple manner,traceability is defined as an approach to trace the
product level requirement and its sources. The IEEE standard defines trustability asrelationship
the
between each
can be developed two or more degree of which a relatiom
products of the development two or more products of the development
especially products allowing master - subordinate relationship to one another. proxe
Types of Traceability
1. Data Source Tracebility
It helps to provide source information of requirements to the
stakeholders as well as
any changes occur, this source information become useful to the stakeholders to rationales Whee
change in the requirements. identifyor analuze
2.
Requirement Traceability
It helps to determine whether the changes in
requirements are necessary or not.
3. Design and Implementation Traceability
It help to
determine the changes made in requirements that can be affected on the system design
implementation.
Q12. Discuss about VORD method in detail?
Answer:
VORD Method

The view point oriented requirement definition (VORD) is a method of

proposed by kotonya and some nervily.
requirements elicitation and anl
has been designed as a service framework for
requirements discovery and analysis. It also inc
different steps in order to translate the analysis intoan object oriented system model.
A viewpoint - oriented analysis has a major ability to
identity several perspectives and provides at
work for discovering process in the requirements designed by various stateholders
There are four strategies of the VORD method, which helps in
Fivct three stages of the VORD method are concerned with view the requirement discovery and analyss
point and service identification. The last
deals with the mapping and transformation of analysis.

VORD
method

View point View poin: Viewpoint

identification Structuring View point
documentation system mapping
Xerox/Photocopying of this book is a
CRIMINAL Act. Anyone found guilty is proce
Warning: LIABLE to face LEGAL
2.15
Seftware Engineer ng
1
View Point ldentification
This stage involves discoveing viewpoints. in onder toeceive suste services. i olso
services that are provided to each view Doint lt an. es the sus em servico based identites the spe itie
on which the
points can be desIgned. It IS eSsential in nequinements dscovery anc ana:sis to . nt1fy the iewpont \iw nd
Services.

2 View Point Structuring

This stage involves grouping similar view points into a hieranchy form. In tne fist stage. the similar v.ew
points lased on the specific services ane identified.
3. View Point Documentation
This stage involves defining the description of the ilentified viwpoints end services. In this st ge.
documentation is prepared in order to obtain the information of i'entified view points an i services.
4. View Point System Mapping
It involves transforming the analysis of the identified view point and services to an object oriented de ign
model.
Q13. Elaborate on a requirements management planning in detail.
Answer :

Requirements Management Planning

It is the tirst step nthe requirement management rocess. Planning is necessary for managing ihe
requirements in all the stazes of the project. Requirements m nagement 's expansion some of the activities that
should be planned during requirement management stage ar ,
1 ldentification
requirement
Each of the reguirement must be identified individually so that they can be ref erred by other
later and also to be used in traceability assessments.
2 Change Management Process
Some important activities of requiremnent change process are
a Conducting problem analysis and change specification.
b Analysis of changes and its cost estimation.
c) Change implementation.
3. Traceability Policies
requirements and the systen: design and requirements
It shows the relationship that exists between the
which Iias to be recorded and maintained.
Case Tool Support
These are the tools that are used to process large amounts of intormation about the requirements Thre
requirements and system design.
are many relationships that exist between the

2.3 SysTEM MODELS

model with neat diagram.
Q14, Explain the context
Answer :
Context Models
It is a graphical representation of the system in which the system boundaries are specified. This is the
nodel which represernt the system environmentsin which system is working. While deciding the environmental
actors of the Systemit is very much necessarytottake diction one certain aspects such as overal cost of the system
and time requiredto analyse such system.
ming : Xerox/Photocopying of this book is a CRIMINAL Act. Anyone found guitty s LIABLE to face LEGAL proceelings
 Software Engineering
This decision should be made in the early stage.
Maintenance
Accounting
systern system

Inventory monitoring Inventory Report generation

Control system,
system
system

Inventory Account
data base database

Context model for inventory control system. Consider the inventory control system for which the roes
model of the system can be created.

First of allusing the requirement of the system the system boundaries are decided and the dependerce
the system are specified in order to define the system environment.
System boundaries are clearly shown below and the environmental factors are defined. The inventr
control system is connected to various system such as inventory monitoring system. Accounting system, repr
generation system and maintain system. This is an architectural model in which and about that representation
inventory control system is given.
Thus context models are the architectural models in which environment of the
systemn is shown. T
relationship that exists with other systems is shown but nature of these relationships is not mentioned in:
context model. All these defined relationship help in finding the requirements of the
architectural model some process model can be used in conjugation system. To detail outs
with this. The process model is agar
graphical representation of system process. The order of execution of various events can be
help of such process model. understood with t

Order
Order
Specify the specification
order of items
Validate specification Estimate
order cost of
items
Suppliers Cost
Suppliers Find ist
specification
datapase supplierS
list Choose
Supplier

Cost + supplier +
order specification
Place the
order of
Systen items
boundan
(These act..:e Order of
are done wrthr. items
the system
Accept the
order delivery

Delivery
Check the
del1ivery
Inventory
date base

Account Updale
inventory
datavase
Process model
Figure : Process Model
Xerr.x/Photocopying of this book is a
CRIMINAL Act.
Varning: Anyone found
2.17# Software Engineering
Q15. Explainthe Behavioural models?
Answer:

Behavioural models are used to describe the owor all bohatiour of a susterm. There are two types of models
hatdepictthe behavior ofthe systern.
Data flow model

State chart diagram

The data flow model represents the flow of data.
The state chart diagram represents the states that are occurring in the system.
These models can be used separately on together depending upon nature of application.
1. Data Flow Diagram
The data flow diagrams depict the information flow and the transforms that are applied on the dete
as it mowes from input to output.

The symbols that are used in data flow diagrarns are

The data flow diagram are used to represent the system Data store

at any levelof abstraction Flowof date

External entity
information flow and detailed
The DFD can be portioned into level that represent increase in
functionality.
model. In the context model the
A level 0DED is called as fundarmental system model or context
bubble with input and output indicated by incoming and
entire software systern is represented by a
outgoing arrows.
sub functions of overall system.
Each process shown in level 1 represented the
the basic functionalitu.
The number of levels in DFD can be increased until every process represen's
DFD, each bubble gets refined.
As the no. of levels gets increased in the
Designing Data Flow Diagram
Guideline for creating a DFD
systerm as a single bubble
Level0 DFD ie.context level DFD should depict the
1

carefully identified.
PTimaryinput and primary output should be
While dong therefinement isolate processes, data oojects and data stores to represent the next leuel
appropriately named.
Al the bubbles (orocesses) and arrows should be
One bubble at a time should be refined
to leve!
information fow continuity must be maintained from level
Warrinng: Xoroyiphotocening of this book is a GRiMNAL AGt. Ayone found guity is LABLE to face LEGAL proceedings
 Software Engineering 2.1
Ruler for Designed DFD
Nol process can have only outputs or only inputs. The process must have both outputs and inputs.
x,y

X,y X,

Level0 DFD

Entity Av Information Entity B

system

X!
Entity A< Process Entity B

Level 1DFD

R 2
Data store
Process Process
Lev I2 DFD

Process

W
2.3
Data store
R 2.2
Process Q
Process
Level 3 DFD

2.2.1
U
Process
2.2.2 S, S3
Process 2.2.3
Process
Waring: Xerox/Photocopying ofthis book is a CRIMINAL Act. Anyone found guilty is LABLE to face LEGAL procee
 19 Sotware Engineering
The verbphrases in the problem description can be identified as processes in the system.

There should not be a direct flow between data stores and external entity. This flow should go througha
proces.

Data store tables should be noun phrases from problem description.

No data should move directly between external entities. The data flow should go through process.

Source Sink

Generally source and sink lables are noun phrases.

system and therefore not represented in DFD.
Interactions between extern entities is outside scope of the
updation/insection/deletion.
Data flow from process to a data store is for
or using the information.
Data flow data store to process is for retrieving
problem description.
LU Data flow labels are noun phrases from
State Chart Diagram
diagram the following.
To understand the design of state chart
Data Model
examined
modelling. In data modeling the data objects are
Data modelling is the basic step in the analysis
indepently of processing.
model is created at the customer's level of abstraction
Ihe data domain is focussed. And a
relationships.
Data objects, attributes, and
Data Objects of dat
attributes (data items) that willbe man1pulated within the software. Each instance
It is a set of to the instances of object.
not perform without accessary
càn be identifier. The sustem can
attributes which themselves are data iteme
tach data obiect is described by the

Atributes properties of data object.

Attributes define
ypically there are three tupe of attributes.
Naming Attributes
These attributes are used to name an
instance of data object.
ng: Xerox/Photocopying of this boek is a CRIMINAL Act. Anyone found guitty is LIABLE to face LEGAL procsedings
Software
2.
Engineering
Descriptive Attributes
3.
ihese atnbutes are used to descrnbe the charactenistics or features ofthe data object
Referential Attributes
These are the attrbutes that are used in making the reference to another instance in
Relationship another tabe
Kelationship represents the connection between the data objects.
Cardinality and Modality
Cardinality in data modeling cardinality specifies how the no. of occurrences of one object is relats
no. of occurrence of another
object.
Modality indicates whether or not a particular data object must participate in the relationship.
1
One to one (1:1l) - one obiect can relate to only one other object.
2. One to may (1: N) -One object can relate to may
objects.
3 Many to many (M: N) - Some number of occurrences of an object can relate to sSome other
occurrences of another object.
Entity Relationship Diagram
The object relationship pair can be graphically represented pair can be
called entity relationship diagram (ERD). graphicaly represented by aca
The ERD is mainly used in data base applications but now it is more
commonly used in data des
The ERD was originally proposed by peter when for design of relational data
base systems.
The primary pupose of ERD is to represent to relationship between data
ERD are. objects various compone
1 Entity
a Drawn as a rectangle
b An entity is an object that exists and is
distinguishable.
c) Similar to a record in a PL with attributes.

Entity ’ representation
It is an object is distinguishable it is similar to record.

Entity weak entity

’ Attribute

Attribute) ’ Derived attribute

Auibute
’ Key - attribute

Attribute -’ Multivalued attributed

Relation
, Relationship
ship

Xerox/Photocopying of this book is a CRIMINAL Act. Anyone found quilty is LIABLE to face LEGAL proce
Warnring:
2.21 Software Engineering
Q16. Explain about the object models.
Answer:
The object model is created for the system processing obiect oriented programming approach. Generally
object models are created for interactive system. Such system can be implemented using object oriented PL
such
Java.
ac C++ or
For the creation of object model during requirement analusis the information about data and its processing
iscollected. The object model is a natural representation of real word l entities such which are requiredin infomation
processingsystems. Such entities can be student, book customer, account, ticket can and so on. These entities are
ypically called as object classes.
these entities can
The system can maniplate these entities bu performing some set of operation. Moreover
interact with other entities. These all things can be very well representation using object model.
Three types of models
1 Inheritance model

2 Object aggregation
3. Object behaviour model
Inheritance Model
1. object oriented
inherit some prperties form the parent class. In
It is aproperty by which the child class can there are some common atributes and services then inheritance
modeling some classes are identified and if
applied.
Ex :

Person

Name sex
address age

Get-Info
display

Employee
Student
Exp - ID
Roll num Date of join
class marks Designation Salary

Programmer Design
Manager

Department Project assignment Assignment

proceedings
book is a CRIMINAL Act. Anyone found quity is LIABLE to face LEGAL
or this
Warnir g rYPhotocopying
 Software Engineering 2
2-object Aggregation
Computer
Model No.
Brand

Key board
Screen Memory

Aggregation

It is a has a relationship

3. Object Behavioural Model

The object behavioural model is for representing the sequence of events occurring in the system. Typic:
it is represented by a sequence diagram in UML.
Ex:

Course admin
Coerce Subject Teacher
Course administrate

Student
Create course
Register
Cour e ID
Get reg. ID Create s
Subje code

Assign teacher

Teacher assignment to
path unclear subject

Figure
QJ7. Explain about the structure l methods.
An: wer:

Apying the structured metho's means

designing
var: is structural models can be content models process difterent
models,
models to represnt that particularsst
reia ionshipd.a rams, object models. date diaqram. state en
chart dic rams.
The structured modelling provides the sustematic framev ork for system
elicitation and anaiysis. Along with these models modellirg as a part of requrer
quideline in system development. Not onv this use ot documentarion
CASL
is
essential in order provide line cer
to
generation tror thestem
modei. tresupport also hels to generate reports or c

of this boo is a c2
larr g Xerox/Photocopying
2.23

Oraubacks of Structured Method

SoftwareEngineering
Non functional
1 requirerhents can
MA he tepteented iefletseky using structured methss
2
It is hart to
predict whether the structured soetheds thatare aooied to
ving that probilern t not porticulat problem are an
3. Sornetirnes too rmuch docurnentation hite, The hasic
reyuiterrnents f the yem
4 The ystern nlels are repreented inroore ietail s ca ial weran Mt
ost in the unnecevary detais
urdertard the ystern be he s

o18. Discuss about the data models.

Answer:

It is one ot the essential aspects of any of the ysteros, being developed. Also we have rmodels to repreerit
the processing of logical data belonging to thee syiterns and such mcdels are cften referred as. romaatic data
models. Most of the between developnent rgarization trday relay on entity relation attribute modelling for
modelling data base systerns.
Thermain aspect of these rnodels are the entities, attributes and their relationships that exists arnong these
entities. This gained wide recognisations even in object oriented database modelling
Anew language referred as UML has acquired the position of entity relation attribute modelling. UML
dírectly did not support the data base modelling.
Example

On through analysis of the above model, we can conchude that, the model does expose most of its details.
As details are often a necessary aspect, they need to be stored in specified storage location in an ordely format.

Q19, Differentiate between data flow and state machine models.

Answer:
Data flow State machine

1. Data flow are the data processing models Show the systerns response to events
that show how data is processed as it
moves through the system.
It show the systen ; states and events cou ing.
2. It shows the data flow through a sequence
flow through a sequer ce of processing transac-ionfrom oi e state to another.

steps.
It is usei to m.odel eal - time systems
3. It is used to documeni a between design
Each sto tha is ta pn are on the basis
4. The input if each step s given by the
of the e Jents tnat o :cur in the environmer.
previous steps.
fhe output The in ut ot oe st: is calculated in
3. Input of ore step com ose
that step oniy
of another siep
data store Ounded Oral models - the stales that define the act ons
D. Rectangle repres nt tl 2
rectangles depict the :nctional prcessing
and arrows repruse it the transitions from
represent thedata one state to an.Tihe
of a system and arrows
another
ilow from one function to
CRIVAL Act. An yonc foud qutit is LIAnLE to
Kerox/Photocopving of this book is a
Warning: f3ce L2G
Software Engineering
Q20. Write the difference between view point template and service template.
Answer:
View point template Service template
1, Reference : The name of a view point on Reference :The name ofa service on which
which reference is given. is given.
2. Attributes : The properties or Rationale : Issue based on which service is
attributes provte
provide specific information of view point.
3.
Events : Areference toa set event scannets Specification :A reference to a list of service
which describes how the system effects to Specification, which may be expressed in different
view point events. notations.
4 Services: A reference to a set of service View points : A reference to a list of view poit
description. names,which receive the service.
5. Sub view points :The names of the view
Non-functional requirements.
points on which referenc are provided. Are reference to a set of non-functional
requiremes
which help to define the service.
6.
Service Provide:Areference to a list of system
objects, which provide the service.