0% found this document useful (0 votes)
478 views85 pagesSoftware Engineering Quantum
Uploaded by
Shivam GuptaCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
478 views85 pagesSoftware Engineering Quantum
Uploaded by
Shivam GuptaCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
/ 85
PUBLISHED BY: Apram Singh
ions?
Quantum Publica
Jit of Quantum Page PYt. Ltd)
HARE Shar Sterns re,
Sted Ghai 201010
Phooe:0120-4160579 |
jgmaiLcom Website: www.quantumpag: cain
Email: pagequantums % ee
Delhi Office : 16590, ast Rohtas Nagar, Shahdara, Dethi-110032
AvRarsRs
tpetei e op edi
sy fom by any mans, without permiain,
‘niomaton contained is Has work & derived rom sources |
eleva tbe elle Every tfrthas een made tense
sccumcy however nether the pubisher nor the authors
friar the accuracy completeness of any information
pubs! Nee and neither the publisher nor the authors
shal be sponse for ay errs, omissions, oF damages
‘Software Engineering (CST : Sem-4 & 6)
Y
x
4
6
* Badtion © 201011
~ Eaton 2011-12,
~ Baition = 2072.13
Baition : 2079-14
Edition 2014.15
Edition : 2076-16
* Edition: 2016-17
* Edition : 2017.18
Price: Rs 90! only
Printed at: ira) Printers, Delhj10093 —
CONTENTS es
[UNIT INTRODUCTION (A Cw 1280,
Intoaction to Software EngoerngSftware Components Stra
Characteristics. Software Cr, Software Engsneching Posto,
‘Smlanty and Dfterences irom Convenor Experi Pe
Softvae Quality Attbutes Software Development Le Ce SDL)
Models: Water Fall Model, Prototype Model. Spica Mode.
Evolutionary Development Models, Irv Enhancement Mose
UUNTT:II: SOFTWARE REQUIREMENT SPECIFICATIONS SRS)
(21Ctw2410)
Requirement Engineering Process: Elicitation, Analysis,
Deumentation Review and Management of User Nees, Fea
Study, Information Modeling, Data Flow Diagrams, Entity
Relationship Diagrams, Decision Tables, RS Decument [EEE
Standards for SRS Software Quality surance (SQ). Venison
snd Validation. SQA Plans. Software Quality Frameworks 0
S000 Models SELCMM Mtoe,
UNIT: SOFTWARE DESIGN G1cw3360)
« Concept of Software Design Architectral Design Low Level
Desig Malarvaton, Desig Structure Carts, Pas Coc Foe
(Guar Coupling are Cohesion Mesure, Design Seteger Functor
(Gretel Deg Oct Oren Desig. Top Down sr Bor
Desi Software Measurement ant Neri Various Soe Orca
‘Measures Halesead's Stare Scene Funct Pont IP) Based
Measures, Cjlomatc Compleuty Measures Contd om Gap
UNITIV: SOFTWARE TESTING 1Cw4330)
esting Objectives, Unit Testing, Iteration Testing, Aceptance
‘Testing, Regression Testing. Testing for Functionality and Tesog
for Tesformance, Top-Down and Bottom Up Testing statepice
Test Drivers and Tes Stubs, Strata Testing (Wit Bon Testing,
unetona Testing (Back Box Testing, Test Bata Sut Preparation
‘Alpha and Beta Testing of Product Static Testing Stetesies
Formal Technical Reviews (Peer Resiews}, Walk Through, Code
nspection, Compliance with Design amd Coding Stands
UNITY: SOFTWARE MAINTENANCE ANDSPM. (5-1 Ct05-31.C)
‘Software at an Evolutionary Elity, New fot Mastnance Categonis
of Maintenance Preventive. Corctive and Perecve Matera
Coat of Mainteance, Software Re-Engieerng Reverse Engineering
Software Configuration Management Activites, Change Cmte]
Process, Software Version Contr. An Overview ol CASE Teel,
Estimation of Various Parameters sich 2s Cos! ors Schetule
Duration, Constructive Cost Models (COCOMO), Resource
Allocation Models, Sufteare Rsk Analyst ant Management
‘SHORT QUESTIONS ($Q-1CtSQ18¢)
‘SOLVED PAPERS (2012-13 70 2016-17) (SPC 9 SP.18C) Introduction
1-2CICSITSem-4)
CONCEPT OUTLINE
_£0 ia
Software eaincring: Setnare ane am
wal np opt one ae
lopment inl
| thts ener: *
Software contains computer programs, operating procedure and
sssociated documentation which is necessary for software |
system,
Software crisis : Software crisis is a set of difficulties or
problems encountered while developing software 4
A Concept Outline Part-1 woes BC)
B Long and Medium Answer Type Questions. rac | een
| Long. Type and Medium Answer Type
Parte. (2-9€ to 1-270)
f ‘Software Engineering Processes a
‘Similarity and Differences from Conventional Engineering Process
Software Quality Attributes
f Software Development Life Gycle (SDLC) Models : Waterfall Moctel
Prototype Model
Spiral Model .
Evolutionary Development Model
9c
~ 1-96
erative Enhancement Model
A Concept Outline :Part.2
B. Long ond Medium Answer Tope Questions
TAC (CSHT-Sem.4)
BERTI] want ao you thean by software engineerin
the objective / aim of software engineering
=a
Software enfineering
1
According to Bochm, “Software engineering is the practical application
of scientific knowledge in the design and construction of computer
‘programs and associated documentation required to develop, operate
and maintain them”,
Software enginceringis adiscipline whose aimis the production of fault
froe software that satisfies the user «needs and thats delivered on time
and within budget,
deals with cost effective solutions to practical problems by applying
scientific knowledge
Software engineering is the application of methods and scientific
knowledge to create practical cost-effective solutions forthe design,
construction, operation and maintenance of software
Objective/ aim of software engineerin
i. To understand user conceptual models and development of better
specifeation Software Engineeri 1-9C(CSIT-Semea)
rare Engineering _ IT Sem-4)
i Toimprove design language and reusable code
fil Tosataty the users requirements
and produstion
‘Toachiove love maintenance
urget and time.
ost
1% Toprovide the software within
vi Toachieve high performance
Reeta] Explain the components of software,
oR
‘What is principle aim of software engineering discipline ? Define
software components.
Principle aim of software engineering :lefer Q 1.1, Page 1-20, Unit-
Components of software :
i. Set of programs :
Program : program is «set of instruction
1 Its ecollection of source code and objects code. Examples of small
programs are factorial of number or print a sequence of number up to
sven limit.
A program is a subset of software and it becomes software only if
‘documentation and operating procedure manuals are prepared.
ii. Software documents
Software documentation consist all the deseription, programs, graphics
and instruction pertaining to design, coding, testing and preparations of
softwar. Good software contain following type of documentations
1. Analysisand specification _
2 Design
3 Coding
4 Testing
ili, Operating procedure:
Operating procedure provide information about what the software
is, bow to work with it, how to instal it on our system and hove to
control all the activities ofthe software,
>The main aim ofthis manual isto provide help to operating staff for
‘roducing desired output with the help of that particular software.
© Tteanbe divided in two parts
1 User manual
2 Operational manuals
1-4C(CSAT-Sem-4)
ues. | Define the term software engineeri
Introduction
Discuss the
various characteristics of software with examples.
|
Software engineering: Kefer Q.1.1, Page 1-20, Unit-l
Characteristies of software :
&
(ARTU 2012-15, Marks 10)
Software is developed or engineered, itis not manufactured in
classical sense!
1. Engineering / developing and manufacturing both are logically
different in working pattern and providing end product.
2. While for getting good quality of either hardware or softwares
‘good design is compulsory
3. But in manufacturing phase of hardware, a quality problem can
introduce if proper attention isnot paid atthe time of manufacturing
fas once a produc is manufactured it cannot be modified easily
4. While this type of problem does not exist in case of software as it
‘can be easily modified and errors can be removed at the same
Software does not wear out:
1. In introduction stage of both hardware and software, there are
‘chances of high failure rate.
2 Defects are corrected and then failure rate is reduced and steady
state comes.
Incase ofhardware ater some time this fuilure rate start sing
sina thehardware pata went with cme ch a
Catsed by cumulative effect af dust, sudden temperature char
(highow vibration and other envivonmestal matics
Hardware
Setteare
z Wearow |g
§ &
| _\ tant meray 3
é Laeatined
Fig. 1.0.1. Pailure curves. Sofware Engineering
Qeora
‘world environment must change or become progressively less useful.
1-8C(C8TF Sem)
ve tajurerowaf hardware relation with ime form a tub tke
‘= called “hath tub curve”,
eres aire ae dv (sone undiscovered
5 In cot geste erure are correeted the curve became flat and
cr et me atu eeate bec oboe which
sated care
thor practice the ea curve ot pane beaut stare
area oat becomes detefrate and requte aie
{ik Most software is custom-built rather than being assembled from
‘existing components
1 Nowadays industries are moving towards component based
‘sce f product which means al products arenot manufactured
tt the same place.
"Ths type of design uses some already manufactured hardware
clement available in the market
So that designer can concentrate on truly innovative element of
esi
4 While software ie designed as per the requirement ofthe user.
5. At heim of designing software, the developer triesto design and
implement software element in such away that they may be reuse
‘nmany different programs.
6 Forexample, GUTis build uring reusable component which ean be
sued to develop ather menus.
Software is intangible:
1. Intangibe products are those products which we cannot touch and
whose quality cannot be measured tatil the whole product is
Shecked
2 Forexample mall software program which is used to generate
telephone bl cannot be said ok by only checking that, its taking
the correct input as customer name, address, number of local and
STD ealletc until tis checked that itis producing correct output in
required format
Explain why « software system that is used
real
(AKTU 2018-16, Marks 15)
=a
Speeme ut change tbe progressively ess uel fora number
1-0 (CST Bem-4)
AFT oon
Introduction
Th presse of the yatin cae cha waa of working in ts
tnitenment and thi generates ew requiem If thse are
seesatied, the wefulne ofthe sytem declines
1 The busines in which the aysem i ned changer in reponse
Inarket force and thi alae generates new sytem reqiresnte
4 Theesternal legal and political rovirooment orth sytem changes
thd ginerates new requirements
4. New technologies become available that fer ignfcant benefie
the the apotem must change to take advatage of them
Sofware change is very important becsuse organizations are now
empletely dependent on their oftware systems snd have invested
Slonofdllarein thew system
Ther eystea are cic busines ass and they mus inven eer
hangetoaintain the value of theveaset.
‘ley probe fr eganizatonsisimplementing and managing change
tothuir lng ayoems vo hat they continue to upper their buss
persion
‘There ae mumber of diferent strategies for sofware change
‘Software maintenance: Changes othe software are made in
response to changed requirement but the fundamental etrortre
ath oftware remains sable‘This the mot common approach
nd sytem change
1h Architetural transformation This isa more radial approach
to nflware change than maintenance as it involves allo
gifrant changes tothe architecture af the software sata
Mot commany, systems evolve fm a cetraned, datacentre
architecture toclen sree architecture
© Software reengineering: This ierent from ther strategies,
in tha no new functionality sade to the system. Rather the
system is modified o make it easier to understand and change
Sen reenginering may involve sme srt] modictione
bat doo not usally involve major architectural change
following in brief:
Software characteristics
iL Difference between module and software component
ame |
i
Software characteristics : Refer Q 1, Page 1-4C, Unit-. 1-7 (CSIT-Sem-4)
Software Engineering
Difference between module and software component
Sky naar T__Settware component
Pt eagre erat | Metts wnat
rect ene el
=
2. Moriule is used to model the | Components are used to model a
system in function view. | systemin technical view.
3 Module is @ partitioned | Component is « runtime entity
system into implementation | ean be made up of modules),
finite, independent task | independent runnable unit. | |
| aesignment. Modules might
‘ormht not bea component
BEE explain the otowing statement “Software eogineering
aa tnyered technology (RT 3016-16, sacs)
‘Answer
Safrare developmen etotally layer Ulan Tat une, to devel
software, one will have to go from one layer te another.
‘Thelayers are related and each layer demands the fulfilment othe previous
layer
Fig. 1.6.18 the upward fowchart ofthe layers of software developmen:
Software engincering is divided into following four layers
LL Aquality focus
8. Any engincering approach must rest on quality
1. The “Bed Rock" tha supports software engineering isqualty fs.
2 Process:
18 Foundation fo
‘SE isthe process layer.
1-8C(CSIT-Som-4) Inteoduetion
b. SE process the GLUE that hols al the technology layers together
‘and enables the timely development of computer software
eTeforms the base for management control of software project.
Methods:
a. SEmethods provide the “Technical Questions" for building sofware.
1b. Methods contain abroad array of tasks that include communication
requirement analysis, design modeling, program construction
{esting and support
4 Tools
SE tools provide automated or semi-automated support for the
“Process” andthe “Methods”.
Tools are integrated so that information created by one tool can be
used by another.
(GeeLT. | What is software crisis ? Discuss main reasons and
results of software crisis.
newer
Software crsisis ast of difficulties or problems encountered while developing
sofware
Reasons of software crisis:
‘Communication gap between end user and software developer,
Misintrprtation of requirement, improper problem definition, no
knowledge about end user. covirenmeat. ®
3 High software cost compare te hardware cost
4 Changes in end user requirement increase the problem for developer.
‘5. Inaccurate scheduling and cot estimation of project.
6
2
5
ata collection and analysis is not up to mark or not done timely,
Increase insite of software.
Increase in complexity of problem area.
Results of software crisis:
Poor quality of software.
Late delivery of software,
High cost compare to estimate cost.
Not able to meet current demand for which it should accommodate 1-90 (CST Sem-4)
Software Engineering
ry (Pant 2] ee
~ je Engineering Proceses, Similarity and Differences from
aaa! ringincerng r Quality Attributes.
Fe rtp re emma or
ae Ne ae shane Molde
CONCEPT GUTLINE : PART-2
+ Software engineering procest:It isa set of activites that
leads tothe production of software product.
+ Conventional engineering process: is structured logical
approach to develop stable fina product,
+ Software quality : It ie the cenformance to impliet stated
functional and performance requirements, explicily documented
development standards and impeit characteristics that are
expected to ll professionally developed software.
Software development lifecycle It represents number of
identifiable stages under which software goes during its ie.
WRAY eta soxveaocleagneering process. How
‘tern! tm atvarecagnering pecewes?
=|
Conventional enginering procs is atructured logical approach to
develop a stable final product
2 Conventional engineering process uses the software tools to design and
analyz ther wn ayes
3 Therefore developed electronic document gues through analysis design
implementation and testi just lke software engineer
ing phases just like software engineering
1-10€ (C8T-Sem-4y Iotration
Difference between software engineering process snd conventional
engineering proces
| | science, information mathematics and
science and discrete | empires! Knowidgr
‘mathematics
| Constraction and
computers are cheap. manufacturing cowts are
0 sofware high. 20 conventional
engineering and | engineering may only be
‘consulting are often | 5% ofthe ont of +
| more than half ofthe | project.
| cost of projet.
& |Imnovation Otten new Only Koown and tested
untested elements are principle are applied ad
"pplied in software | untested innovations are
Replication | Replication iv ivi
Most development
effort “gece inte
requiretnignifiesst
building” new or development eforts
‘hanging old design to
auld new features
|
|
[iene
L
Many of conventional
cagineer: manage
| manafsccring of
| they allare treated as
| satu ‘engineers manage
| aayone
—___ managers
Qe18, | Explain software quality attributes,
(ARTO 201813, Mark 0
oR
Define software quality,
are quis i fl tay and
ofa and practi tht deste the dese
sini fate produces Minor eg
1. Conformance of requirements 1 C(CSIT-Sem-4)
Software Engineering = =
2 Fitness for the purpose
8 Levelofeatisfction
mites areas follows
major software quality art
oe rtnonally correct sit behave according to
1 Corecnen: Aste ft
Comat econ we
oan ate rlabefitves esiotpt een
2 Reb: Aor ponents ardor orn ie of ela
aoe
A Roburine
need teroqaremen
Trower
4. Ponble:Soeareterportabiity inte
Pere sec tora ete ha 0
comet
iyo weld understand a sytem
© Vader cenit andanoertansy.
Performance: nsefteareengoering performance equated wih
eee qa doe prtar its operation,
Tnteruporaiiny Ca ster operat mith another sytem,
eniiabl chick wether he properties the system be verified
Timelines: Tesi toler sytem on tine
10. ificiency'It isthe ability software system tofulfil ts purpose with,
‘bor pone utilization of necessary resources such as tine, storage,
‘ronsmnission channel, peripheral ee
Beiio_] Whar insorware quality? What are three dimensions of
software quality? Explain briefly. (ARTU2019-14 Marks 05]
(ARTO 2015-16, Mares 79]
1 expnn bow dos a sptem behave in suation not
hae wel ycorrect input, hardware failure, loss
sase with which a software
for which it
‘Anawer
Software quality : Refers Q.19, Page 1-100, Unit
‘Three dimensions of software quality are :
1. Quality of design : I is the extent to which the design reflects
product or service that satisfies customer needs and expectations. All
‘he necessary characterstes should be designed into the product oF
service atthe outie
uisciarteme nection
= Gah aneaninvawale Ale anc
pr oletrrepee diet cesses lpr
nae ae
Beaty ot sett wars yc 9 scale somes
ha feel aropsesnedirber rch bee
Paper cle npchenpteingtewssirae
noe
‘Que LIl.] Explain Software Development Life Cycle (SDLC).
Software Development Life Cycle (SDLC)
1. Software development life eyele a diagrammatic representation which
also provides description of various phases and their sequence in life
‘cle of software product,
2, Software lifecycle represente numberof identifiable stages under which
software goes during it life.
3. We have different lifecycle models, each one have its own advantages
nd discvantages
4. Wo can choose any one of them on the bass of
4. Development speed
Product quality
i, Project visibility
jv. Administrative overhead.
Risk exposure
Phases of software development life cycle models :
i. Requirement definition (system analysis and system specification)
|i System and component software) design
ii Implementation and unit testing
iv, Integration and system testing
Operation and maintenance Software Boginecring
Gee 11a] Define waterfall model.
1-136 (CSIT-Som-4)
1 eee
{tar dese |
Fig. 141.1. Sotrare development ie eye mode
End product ofeach phase:
The output of requirement defition is software roquirement
Jpectation SHS) document
The output of system and sofware design is entity relationship
‘A dagram data ow diagram (DED), flow cart ee
Tic stp of implementation rl uni testing iced program.
4. Thevuiputofinteprationandeytem tatingis ede without error
ous
€ Tre output of operation and maintenance phase i implemented
system fat runsing welt lent end
(ARTY 2014-16, Marks 2:5)
(ATU 2016-17, Marko 73]
Write the advantages and disadvantages of waterfall model, Why
the use of iterative waterfall is not grad for large projects ?
tare |
Waterfall model :
1
‘Waterfall Mode is sequential modelthat divides oftware development
intodfferent phases
‘In waterfall model progress is seen at owing steadily downwards ike
‘waterfall through the phases of feasibility study, analysis, design.
‘coding testing, implementation and maintenance
‘The dite
1. Feasibility study :
etcenif
Fig. 1.12.4. Waterfall model
1 phases of waterfall model are
This phase is used to check whether the new proposed system ie
‘economically, technically and operationally feasible vr not,
In this information is gathered about what outputs to be produce,
‘what input is required and what process can be wied and thea
Aliferent solution sravegies are formulated
© The uty otha phase is feasibly port.
»
2 Requirement analysis and specification
‘This phase analy and specifies the requirement of wer /customer
and document theen properly
Inrequirement analysis the data ae gathered from sser,
Binal the requirements organied tematic the frm af
locument called software requirement specification SRS)
‘document,
a
Te output ofthis phase i trae requirement peat SHS)
System and software designing phase : In design phase, overall
structure or architecture is developed which is transformation of
‘Tequiremet specified in software requirement specification SRS). There
are two iain types of design approach
8. Traditional design approach : In this function, software
equirement speciation SHS) document is decompd nto small
‘tub functions and information Now ameng theses functions are
lao checked. Wis done in two parts
1 Arbtectural design
2 Detailed design 1-18 (CSAT-Sem-4)
Software Engineering
wees
sn eam te
cong na model ert
‘ «In this phase, system design is translated into source code also.
‘a ence
ener ane fr dierent mods i done in selected
Ms ar
cp ofthrpase i proeaned dle
tapes cel ese tt
Peed at eit bir singed
ea a
b Tesvuctromaimtsng Aha tting ts dove dvlper
DAMIAN lt aon werent
Teemmeataia pasts ing wader re
& impeentuton/tntalaton and mntenence
rossi oh ner end antics
‘here in any upgradation required in hardware or software element
‘tuner oad.
Once the softwares properly installed there is need of maintaining
the sofware. This ensures that software is working properly at
Advantages of waterfall model :
Rasy to understand.
|i Esch stage has defined input and output
ii, Helps project planning.
Disadvantage of waterfall model :
eration not possible ait is one way street
it Requirements freezing at starting stage
Sequencing — stage cen start ntl he previous stage ia completed.
W Anwid model
_Difcatynaccommdaing change afer project development.
The uve of erative waterfall model for large project ia mot good
i Wsditcule opr how the new system willbe,
Cra cs en ay ape ston ne
16C (CSAT-Sem-4)
“
[GaeTHE] ws are the phases inthe waterfall model 7 Which
eee rc the masimum efor for developing» oftware?
Discuse with proper justification. (AKTU 2012-13, Marka 10]
Teal
Preis tera model Rafe Q. 112, Page 1-19 Ui
rar nse pss now the asimam efor fr developing fina
Suinoaton
‘This phase is not just about testing but contains activities such as document
reviews and code walkthroughs. It has a high degree of overlap with the
ther phases which resulte in higher quality in the final product. This phase
ts done by both the developers and the users,
Qaeaa| Expt
diagram.
the working of prototype model with suitable
oR
Discuss the prototype model. What is the effect of designing a
prototype on the overall cost of the software project ?
on
Explain about prototyping model of software development. What
are the advantages of it over waterfall model ? Discuss.
‘Anewer
‘There are certain drawbacks in waterfall model. This model was developed
to overcome from two main drawbacks of waterfall model. They are
|. Difficulty in predicting how the new system will be
4% Difficulty in predicting the entire requirements at very beginning of
Project, because even end users do not know all requirements initially
Prototype model:
1
A prototype is partially developed product. It has limited functional
‘capabilities, ow reliability and inefficient performance
The prototype model suggests that before developing the actual software,
working prototype ofthe system should be built
‘The model starts with an initial requirements gathering phase.
A cuick design in carried out and the prototype model is built using
‘several shortcuts, =—— *
‘The prototype product usually turns out to be a very crude version of
‘the actual system. The prototype model is shown in the Fig. 1.14.1 1-17 C(C8IT-Sem-4)
Customer evaluation
of pretotype
‘Acceptance by customer
Desi
}
Implement
i
Advantages
1 April products builtin the ntl stages, Therefore customers eta
‘chance tose the product early in the lifecycle and thus give necessa
cent ly vd cS "y
2% Requirements become clearer resulting inta an accurate produ.
er Tequirements canbe easily accommodated, as there is scope for
Fatih idtignand deslopmet i lio appr by th dl
Disadvantages rrietty
1 Developersin a
Dielopersin.« hurry may build prolatyps and end up with sub-optimal
fend user isnot satis
the project,
Poor documentation
ied with initia prototype, he may lose interest in
1-18 (C8IT-Sem-ad Introduetion
Effect of designing prototype on the overall cont of software
project
1 The prototype may be a usable program, but i not suitable as the final
softrare product. The reason may be poor performance, maintainabaity
sroverall quality
2 The cade for the prototype is thrown away: however the experience
gathered from developing the prototype helps in developing the actual
Sistem,
3. Therefore, the development ofa prototype might involve extra cost, but
overall cost might turnout tobe lower than that ofan equivalent systema
‘developed using the waterfall model
Que i6. | Explain evolutionary development model in brief.
Kaewer |
1. Evolutionary models are iterative type models which allow to develop
‘more complete versions ofthe software.
2 Inthis model, the system is frst broken down into several modules or
functional units that can be incrementally implemented and delivered
‘The developers first develop the core modules ofthe system.
4. ‘Thisinitial product skeleton is refined into inereasing lovels of capability
by adding new functionalities in successive versions
1n this approach, each successive version ofthe products functioning
system capable of performing some more useful work
5. This model is also known as the successive versions model.
130A 80 are mods ta stearate
The te ncaa deve cn aan
Adeantagen:
1. an delivery af portion ofthe system even thogh some 0
‘requirements are not yet decided. a =
2 Tho core modes et ested throughly thereby rec
enabuennl ee yughly, thereby reducing chances of
5. Use of carly releases as tol for requirements elicitation C1CSAT Sema)
sotware Engineering 4
mee 7
erase rues ttl
ode! ens be ased only for very ange problems, Where i = casier ty
Mens magules for incremental implementation
Garis] Woy are evolutionary models considered by many toe
«he best approach to software development in a modern context
(ARTO 2019-16 NP
Kemer |
sonar deer consiere’ tees appro nse ins
Praleapmentotanderoutwie are geting dhrter and shorty
SigcTit ieee moe dene tan e ders
Seam aca harden nd change toregurementn ar
Tarren before delve). we nod 8 ay Co rv
‘Soeur ererltionay ive.
ramodstesunertsnty better than m
Tae eeuionary proces cs
Pris alo the davery opera selutonsn an orn
seme and most portly. efits nha real bape
‘hen cupler sytem arb
GeLie] Explain why programs which are developed
cvolutionary development ar likely to be difficult to mai
= ,
epecieations of evoithnary development projects are
7 Tiara the proj enn, he develope and vali
orton of fteerecngiesting relapone anu.
2. Whenatysten is produced wing the evohtionary develbpmant.
{etd toed thot regards an erereding deen
2. Wihench modietion the tar bacmes increasingly dsoeanin
ros ater
4 Stem maintenance fing bogs er adding now fea
‘rsh bes reas in tanpered by thre problems as itis ae
{eesti the ourc of sin porly dexignedayeems
5. Also, keeping the documentation uptodate over successive “evolution
is commas, Poor docrattin also taker tninenance 0
Sica
© This ie why programs which are developed using evolu
development rely tobe difcul miata,
2
—
1-20€ (CSMT-Sem.4)
Introduction
Que] Drm nent sketch of spira mode! and explain
What are the
antiviti
Explain the spiral lifecycle model with its merits and demerita
‘oR.
Define spiral model.
1. The spiral model isa rsk-driven process model generatar for sftware
projects,
‘Based on the unique risk patterns ofa given project, the spiral model
fuides steam to adopt elements of ore of more proses madels suchas
incremental, waterfall. or evolutionary prototyping
Its main featureis sk avoudance rather than documentation or coding
4 This model is more lenble than any other model a numberof phases
through which the product willbe developed isnot Sued. t depeads oa
software requirement
5. Thetwo basic step ofthis model are
Identify the sub-problem whichis having highest risk
ji Finanhition for that particular preblem ak)
8 Generally there are four spirals in Bochm spiral if cyele model
7. The inner first spiralis concept development cycle. the second spiral
indieates new product development cycle, the third spiral represeate
Product enhancement cycle and fourth spiral is known as product
mmaintenanee eye,
‘
Bach phase ofthis model i split inte four quadrast (sections) having
“speci functions:
1 In the first quadrant, we do identification of objectives; find out
different alternative for achieving the objective and present
constraints,
Inthe second quadrant, we evaluate these alternatives onthe basis
of objective and constraints. Thema focus inthis step ic given on
evolution of alternative on the basis of risk at risk causes the
‘ances of unmet objectives. Tis model help in coping up many
rojet risks,
‘© Inthe third quadrant, project development and validation is carry
ut
Inthe fourth quadrant, the projet is reviewed and decision is made
Up whether to continue with a further loop of spiral or nat 1-21 €(CS1T-Sem-4)
rig 1183.
Advantages of Bochm spiral life eyele model
“This model ries to resolve all esl risks ivolved in the project
staring with the highest risk,
{iit documentation reuied as compared to waterfall model
fi Eficient use of prototyping and component based design
iis very sible model
Disadvantages of Bochm spiral lifecycle model:
{Thismodel ino suitable fr smal project
& Thisa time consuming mode.
{_Thecost fia alysis is igh which makes the model cosy.
‘Advantages of spiral model over traditional iterative process model :
i. Therish nalysisandvaldation tes eliminate errosin the carly phase
of development
ii The movie makes use af techniques like reuse, prototyping and
comnponet bated design
ii Iebeomes equivalent another feeyele mode in appropriate situations.
‘The model snot suitable for smallprjeets as cost of risk analysis may
exceed the actual est ofthe project
BETTI wy piel mat inated wma meet?
===
1. Thesml melita mer cause its eah sage i llowed
by explicit recognition of risk. aeen
-22¢ (CSIT-Bem-4)
2 Acydeof the spiral begins elaborating objectives such a performance
‘and functionality:
4. The next stop so reacve risks byinformaticn gathering sctivitie uch
‘more detailed analysis, prototyping and simulation
4. Once risks have been assessed, some development is carried out followed
ws planning activity fr the next phase of proces.
‘The spral model encompasses the strength ofthe waterfall model while
inching Fish analysis, risk management support and management
processes
QeeTRTT| Current trends in software engineering are moving
away from the waterfall model for large projects and moving toward
iterative methods such ax the spiral model? What are we gaining
land losing as a result ? Bxplain with suitable examples.
fawer
1 While in the spiral model, the customer is made aware of all the
‘happenings in the software development, inthe waterfall model the
customer fenot involved.
2 This often leads to situations, where the software is not developed
according tothe needs tothe customer.
8. Inthe waterfall mode, when the development process shifts tothe next
stage, there is no going back
4. Thinsiteu leads to roadblocks, eapecally during the coding phase
5. However, in the spiral model, since there are different iterations, it is
rather easier to change the design and make the software feasible
6 Inthe spiral model, ne can revisit the different phases of software
‘development, as many times as one wants, during the entire development
proces,
‘This alse helps in backtracking, reversing or revising the process.
‘8 However, the same s not possible in the waterfall model, which allows
ro auch scope,
Often people have the waterfall mode or spiral mode confusion due to
{Ue fact that the spiral mode seems tobe a complex model
10. Itcambe attributed tothe fact that there are many iterations, which go
into the model
1, Atthe same time, often there is ne dacumentation involved in the spiral
‘model, which makes it dificult to keep a tack ofthe entire process
12, On the other hand, the waterfall model hae sequential progression,
‘along with clear documentation ofthe entire process
1, This ensures one has a better hold over the eatire process
Introduction —_—_—S:-— ee 7
GEE reise nhc ode ine
Tomer |
arma sot benef wtrtlland rst i
Mviatmndlwelty nuts
eae develped inincrentscahineement
2 Ismet pantera ant lester in deve
de teeing ets teting er ech ree ey
Be an etingtrtral mel and protein
oa eliipn denningte stem requiem
4 totus apt pdt eon fee der
tae cuenta thn ret contol
eeamsel thom ete awh hoe be performed
‘Sarena
Tees dng ot ow fart prt fr aa prod
eae ete tuerowor nd sony enhancement dona
eevee uch eet ftom
i “ 1-290 (CSAT.Sem,
Software Engineer - oe
oo
name a ‘tare
lop omiea)-g ( Valine, (neato
(Siete 5
(erement “4 aremet
in why iis called incremental model. The model prioritizes
system requirement and implements them in group.
‘The process is iterated until the control list is empty and fs
‘implementation of system is done
In hi model developer tamaeles provide speciation v they 1
good control over system development. s
Advantages of iterative enhancement model :
Product delivered in partaso the cot of praduct i also distributed.
‘8 Easy eating as testing ofthe system is done after each increment
ii. User can see working of software in early stage
iv. User requirement become clearer.
vy Low faire risk
Disadvantages of iterative enhancement model ;
iL Totaleost of product development is high,
1-240 (C8TT-Sem-4) Introduction
ik Woll defined projet planning in required for distitntion of work,
fi Testing each model causes extra cot
GQaeTD. | What are software process models? Distinguish iterative
enhancement model and spiral model, (AKTU 201014) Mark
‘Answer
Software process model :
1. A-soltware/aystem process model isa description ofthe sequence of
‘eaties carried outin an software engineering project, andthe relative
‘order of these ativities
2 It provides a fixed generic framework that can be tailored toa specific
project.
Project specific parameters willinclude
Size (person-years)
b Budget
© Duration
Difference :
[RNa] Propertios | Iterative enhancement] Spiral model]
‘of model ‘model
1. |Handlelarge project | _Not Appropriate | Appropriste |
2 [east [Expensive
3. [Veerinvolvement High
4 |Tosting [After every iteration | At the end of |
| - — the each phase|
5. | Overlapping phases Yes Parallel No
development exists)
Rapid development High
‘QUeTRE: | Define the term *aoftware engineering”. Explain the
major differences between software engineering and other
traditional engineering disciplines. (AKTUB01#18, Marks 05 Lacicanenig
| Traditional
=e
a
‘and empirical knowledge.
Jin eefiware casvacering, | Tn traditional engineering, two
pe set roma concern | tain concerns fora product are
Wetec etdeclopment | cost of production and reliability
LIND Sovculity sbich are | measured by time to faitre
‘beasured by the number of
(ros per thousand lines of |
|eemeese |
{Software engineers often | Traditional engineers generally
ppp ew and untested | try to apply known and tstad
| Corns inatrare eet. | principles and limit the use of
| Untested innovations to only
| those necessary to create a
product that) meets ate
Feqirements
5. | Software engineers Sone traditional enginers solve
‘eaphasize projects that wil | long-ranged problems that
| ive for years ‘ensure for centuries
‘Gor 1A] Explain Rapid Application Development (RAD) model.
aero a aT
ame]
1 Rap Applian Developmen (RAD) is» sofware development
Contd int ses msn pang ae ora pete
othe RAD model heft module are developed paral
types anand ma th opt rd fata
‘product delivery. sy
RAD mde dstrbites the analy, design, build and test phases into &
series ofshort. iterative developmentgties
2
1-260 (CSIT-Bem-4)
Following are the various phases of the RAD model
1 Ruriness modeling =
fa The business model or the product under development is designed
in terme low of information andthe distribution of information
between various business channels,
bh A complete business analysis is performed to find the vital
{information for business
2 Data modeling:
‘2 The information gathered in the business modeling phase is
reviewed and analyzed to form sets of data objects vital for the
business.
The attributes of all datasets and the relation between these dats
objects are identified and defined
A Process modeling.
The data object sets defined in the data modeling phase are
converted to establish the business information flow needed to
‘achieve specific business objectives as per the business model
'b. Process descriptions for adding, deleting. retrieving or modifying a
ata object are given
4 Application generation: The actual system is built and coding is done
‘using automation tolsto convert process and data models into actual
rototrpes.
5 Testing and tamaver
The overall testing time is reduced in the RAD model as the
prototypes are independently tested during every iteration.
1h However, the data flow and the interfaces between all the
components need to be thoroughly tested with complete text
coverage.
Tone rane te
ain agers © MES
oni 1-47 €(CSITSem-4)
software Baines —
ETRE wr ae tne characteris of software process ?
(RISTO 2076-17, Marin vg]
tower |
Parr aretewrare recs carats
Fo asbiy Tews extents the proses ext ined
7 thes bw easy veto understand the process definition ?
anny. Deepen dar reset the roe
Sipe entree vie?
4 Hotannca: ante rcs otis in ite of unexpected probleme ?
etabiy tbe ress deed in suc away tha proces eros
ae topes ore thy eal in product errors?
hameatnaiity + Can the proceas evolve to reflect changing
ane aen aurenent rented process improvements”
4 Mapiiy How fa can be the proces of delivering a system rom a
renmesteatonbecompleled™
4. Sapporabiy To wat extent can CASE ol support he proce
VERY DMPORTANT QUESTIONS
“Following questions are very important. These questions
7" may be asked in your SBSSIONALS as well.
oa
t UNIVERSITY EXAMINATION.
1, Discuss software engineering and its components,
ame Refer Q 11aniQ 12
2. What is software crisis? Diseuss main reasons and results
of sotware crisis
me Refer Q.17
@.3, Differentiate between software engineering process and
conventional engineering process.
ame, Refer QL
Q.4. Write short note on waterfall model
aus Keter Q 112
1-280 (CSAT-Sem-4)
Introduction
Q.5. Buplain spiral mode
ame Refer 1.18
Q.6. What are software process models?
ame Refer Q. 1.22
08 Part ne
$Requiroent Baginering Proves
Bsn
Anaya
Decmetton
Reni and Management of User Newds
Feasibility Study
A Cant Outne Part
2 Langend edt Ansut Type Guoion.
a
{information Modeling + Data Flow Diagrame
1 Entity Relationship Diagrams * Decision Tables
SRS Document + IEE Standards or SRS
A. Concept Outline : Part-2 cn 2-100
3B Long nd Medium Answer Type Questions 2-100
Parts...
(2-30€ to 2-400)
‘Software Quality Assurance + Verfeation and Validation
‘SQA Plane * Software Quality Frameworks
‘* SELCMM Models
A Concept Outline: Part
B. Long and Medium Answer Type Questions
21 C(CSAT-Sem-4)
BACICHIT-Sem-4) Software Requirement Specifications (SRS)
PART-1
Aqua ageing Pra ltt li
endo Hee eed Mategenett of Ue Merde
poe ‘Feaotblity Study,
CONCEPT OUTLINE : PART-1
| | Requirement elicitation : It isthe process during whieh
tofirae requirement ae dsevered,expresaed and vevened
from ayn reqarements
«Requirement analyete 1 the scity during which the
Ferurtrngaered dug eatin are anaieed rents
TShoputee conse, msing represents
« Bockinemtaton lis he ctv whichis writen at th end
Strequemen’ citation snd anal.
«Feaaiity study sites determine whether developing the
[7 petit antec ete
|
stions-Answers
Long Answer Type and Medium Answer Type Questions
GueBT. ] Discuss the significance of requirement engineering.
Also, write the various steps of requirement engineering with proper
explanation.
‘Anawer
‘Significance of requirement engineering:
1. Requirement engineering is the procossof determining user expectations
for anew or modified product.
2 These user expectations, called requirements, must be quantifiable,
relevant und detailed,
8. Insoftware engineering, such requirements are often ealled functional
specifications
Requirements analysisis an important aspectof project management,
5. Requirements analysis involves frequent communie
users to determine specife feature expectations
5 Napoli tocreate a requirements spcifcaton thats complete correct,
‘nd understandable to both customers and developers
ion with system 2-3C(CSTT-Sem-4)
sotteare Enact
ts ahown in Fig. 2.1.1
rst of four SPE
Preble
Ly
(Bhictation SY
[Requirements
eae
— Analisis _T
[ Requirements
‘Documentation
Requirements
Review
ig. 211.1. Cracal process steps orequirement engineering
i. Requirements elicitation
"This is also known as gathering of requirements,
Hore, requirements are identified with the help of customer and
tating eysteme processes, if available
Requirements analysis:
“The requirements are analysedin oder to identify inconsistencies, |
defects, omissions ete
bb Wedescribe requirements in terms of relationships and also resolve |
confliets fan
‘ii, Requirements documentation :
‘4 Thisis the end product ofrequirements elicitation and analysis.
1 Therequirement documentation is very important as it will be the
foundation for the design ofthe software,
© The document is known as software requirements specification
(sks)
iv. Requirements review:
& Thereview processis carried out toimprove the quality ofthe SRS.
»
‘hTemay also he called as requirements verification,
© Formaximam benefits, review and verification should not be treat
se gdecrete activity tobe donc only atthe end ofthe preparationa
should be treated as continuous activity that is incorporated inte
the elicitation, analysis, and dacomentataon
DAC ICSIT-Sem-4) Software Requirement Spee fications (SKS,
Queda. | What ix the significance and use of requirement
‘engineering ? What are the requirement validation techniques ?
Tae
Significance of requirement engineering : Refer @. 2.1. Page 2-20,
Unite
Use of requirement engineering:
Requirement engineering x used in
1. Determining the feasibility of producing a particular productos part of
the product line
2 Determining the production, testing, and deployment of the particular
product
3. Determining the evolution ofthe product line thats the incorporation
ofchanges! that results from that product development Produc specie
‘equirementa often “grow up” to become product line requirements st
they can be slightly generalized or if they pop up tn mere than ae
product, That i the primary mechanism for the evoltion of software
Product lines over time
‘Requirement validation technique :
1. Test case generation In this technique, the various tet are developed
for requirements. The requirement liek can be carried out a
folowing
8. Verifiabllity:1s the requirement realistically testable?
% Comprehensiblity Is the requirement propery understood?
& Tenceability: Is the origin of requirement clearly stated?
Adaptability : Can a requirement he changed without a large
impact on other requirements
Automated consistency analysie: Ifthe requirements are expressed
‘ae fom of srutured or formal notations then CASE fos canbe
to check the consistency ofthe syatem, A database i
sreated using a CASE tool that checks the entire requretenta the
database using rules of method or notation. The report of al
‘nconsistencie fs identified and managed.
Prototyping : Prototyping is normally used for valida
nor for validating and cing
sew requirements of the tystom, This help to iaterpit arcompu,
snd provide an appropriate feedback about the requirements fo he re Basincerine = FSC (CRT Seu
~
Softwa
Jon i the activits AUD Which softyay
Jicitati
1 Requirement red, expressed, and revealed fro
yaa |
Feirements are disove
recurements
2 ts source may be
market analy
45 Ceznuernlogies are wsedtoinvole th user onthe basi egg
involvement required
ticuation procedure :A genera elicitation procedure contain fllowig|
steps
1 Identifying relevant cource of information i.
a Ver 1b Customer € Domain experts
2 Determining what informetion is needed by asking questions.
“Analyzing the gathered ioformation, looking for implications
inconsistencies, or unresolved issues
4. Confirming our understanding ofthe requirements with the user,
5. Creating requirement statements
Problems in requirement elicitation
User unable explain his requirements
Less knowledge of technology and may aot consider what is posible
‘Use of ifferent language by developer and user.
Lack of skills in developer.
Users not providing some information du to some reason,
Requirements are coming Frm different seurces,
WoeRA_ | What is system documentation ? Explain in detail
a]
1 System documentations written text oration that ether explainy
how system operates or how to use it
2 System documentation inches al the desriptions, graphics, progracs
‘dination pertaingta the eign plementation, and opera
Thee pte omen mala egy pen
i System design documentation a ae
1° Tepe tan topical tal
2 Mecuiatcanbedeed rom the ad prodcts of ana
stem design documentation consist the following
system requirement documentation, customary
2ac(cntT sem-4)
i. Operation documentati
Software Kequirement Spresfiations (SKS)
Formulation of the problem
eniility sue
overview of the aystern, ta sub aystem and their interfaces
‘output report and sereen displays
6 Datadictionary
jon ; Software documentation consist of
Software document
following
wen hardware specification : Description of equipment, peripberal
devices, communication hardware.
by System software + Description ofthe operating
are alather system oftware sch ax DBMS, sereen formatter,
‘Roms generator and communication software.
Aoplication software specification : Description of each
‘aplication program.
“a. File design or database design : Description ofeach fle wed i»
‘ators its access method andits organization
jon: Its goal isto help the operation staff, run
tn proper order, distribute the output, and handle the errors
Pe come during execution of programs. It eonsists of the following
‘Multiple system flowcharts with supportive narratives :
Description ofeach program, its purpose, and the execution of tbe
program.
bi Operation procedure for each program : Description of input
Peqoired and ite format, fle required, output produced, error
Conditions and operators required etc
.. User reference documentation :It consists ofthe following
‘Objectives of documentation :It provides outline ofthe purpose
and use ofthe document
1b Input documents It covers complete lst and samples of all the
input documents used by the system.
‘e. Output reports and sereen display :It contain the complete list
land sample of all eports, with their frequencies and distributions,
‘and examples of screen displays.
‘Processing logice and error conditions : It provide outline of
processing logic for each output report, error condition et
‘System maintenance staff documentation: I isthe list of computer
‘deyartment staff members who would be contacted i case of ay problem
thatthe user cannat rectify
TRI] wit tort note on review and managment of wer
~— oftware Engineering 7
Tae |
Review of user needs
2-7 CWCRIT Se
Teisamanul proces
organizations es
‘ey heck the requirements fr
me may be managed inthe SAIMe Way 0 prograg
es and omissions
‘The review proce
nations
Alternative
prople checking differ
ming activities are performed in user needs review
jst may be organined as broader activity with dit
at part ofthe document, “a7
Poli
1 Plana review
2 Review meeting
5 Pollow-ap actions
4 Document after reviee
5. Uinderstandabilty
{Checking for redundaney
Completeness
8 Consistency
8. Maptaility
10 Conformation of standards
Management of user needs:
Management of user needs is the process of documenting, analyzing,
‘racing, promitzing and agreing on requirements and then controling
‘hange and commicating to relevant stakeholders. Iisa continuous
‘races throughout a projec
‘Avoquirement isa capability to which a projet outeame (product or
service should conform
‘The purpose of management of user needs is to ensure that sn
ongatzation documents, verifies, and meets the neds ad expectations
its customers and internal o external stakebolder,
Following activities are performed in management of wer need
4 Tevestigation
Feastlty
Design
Constrseton ante
Requirements change management
Relesse
4
f
1 ivolvespople from bth lien and con
hat inves peo rm
Pac ccsrtsem-
Goons,
Sofware Requirement Specifications (SRS)
what do,you mean by feasibility study ? Explain variou
easiblity and important steps that are carried out,
tity study phase, dering
Treaty tudy is the analysis of sks, cote and benefits relating to
eomics, technology and user operations
“Treoutputof feasibility tudy is a document known a feasibility study
report.
‘The report must answer the following key questions
«Wal the new system provide a better way todo jobs
4 What the proposed system will do”
fii What will be the estimated cost of proposed system?
jv What will be the benefits from proposed system?
‘There areseveral typesof feasibility depending onthe aspect they covers
Some important feasibility is as follows
a Technical feasibility ; The technica feasibility study basically
‘hoterson alternatives for hardware, software and design approsch
todetermine the functional aspect of stem,
‘Operational feasibility : Operational feasibility is a measure of
haw people are abl to work with system. Tis type of feasibility
Uemands ifthe eyetor will work when developed and installed
Economical feasibility : Economical feasibility isa measure to
find out whether it is economically worthwhile to invest in the
project. Cost benefit analysis carried out te determine economical
feasibility.
‘The feasibility study involves following eight steps :
1
8
Forma project and appoint a project leader,
Prepare system flow chart.
Enumerate potential eandidate system.
Describe and identify the characteristics ofcandidate system.
Determine and evaluate performance and cost effectiveness of each,
candidat ester
Wieight system performance and cost data
Select best performance system,
Prepare and report final project directive to management.
Que27_ | Explain the cost benefit analysis to determine the
‘economic feasibility onthe basis of direct cost, indirect cost, tangible
benefits and intangible benefite, Sater gies
keower |
A The coat benefit analwis 1
fonts
com benefit anatyie 0 find out whether ig
ef ot Be
eee ‘to invest in the project
coomomicals worthwhile
nti god then the project is considered
pecenenry (0 determine the economie
fi Wht reture onthe invest
canomcally wortiile
se cea kemat oan performed rt iting al te coats asociatg
fk The direct comt/ tangible cont
ree direct costs directly associated with the project such ag
see panne she equipments (hardware like printer,
SSepters dink drive ee | software, salary to ata
Cont imolved in preparation of physical location such as aie
conditioner lights wiring ee
fi Operating cust s2eh a8 use of paper, pen drives ete.
1. The indirect cost intangible cost
rT inde cost not directly associated with projec, itis a
‘ent of operations that are directly associated with system of
Eerwen projet,
It isafen referred as overhewd,
{i Indirect cost involves time spend by ser in discussing problems
swith eysem analyst, gathering the data about the problems
2 Coat benefit analysis on the basis of benefite : The benefits can
tse be broadly claseified a tangible benefits and intangible benefits,
(Tangible benefite: The tangible benefits are directly measurable
They are
| Decreasing salary’ coet by automating manual procedure.
18 Preventing cot but frequent errors.
{Sending bills arin the month
‘Increasing contol over inventory level.
¥ Inereasein production
1b Intangible benefits: The intangible benefits are not directly
measurable. They are
2 Better service to customer.
Sopener quality of product.
i Upgrading or resting new customer services.
i Developing s new image in the market
edcing repetitive or monotonous work for employee.
ro Reopnirement Sgmeitcatins 5H
prec ica sem ss St
PART-2
neting, Data Flow Diagrams, Entity Raationship
Information ee Detain Tobles, SRS Document, IEEE
Standards for SRS.
~ GONGEPT OUTLINE : PART-Z
Structure analysis and design techniques
‘ preach
Sh Oppetonented approach
[Problem ratement language
‘yet
«+ SHS is specification fora particular software product prograsn
fr set of programs that performs certain function ina speefic
requirement
‘GeeRRT] What are the different approaches for information
‘modeling? Explain euch in brie
“Asower]
Folawag avr aprons fr iforsation
1. Informal approach =e
{© Tatra spon oo mtg ised hi aprech no
Eon anal cba
‘Taro dhe stom mal are eset bint id
‘of unalyst and directly translated -
oan ly from the mind ofthe analyst
‘2 Formal approach / structured approsch
4 In structured analysis techniques, we use functional based
‘decomposition while modeling the problem scoman
—
* 5 on performed in the
he th i re
5 crt gyn ng
Bea argc oe
\ ae
se aermerstured analysis ann desgo techniques (SADT) is designed
snlormation processing syste™s.
a A les and penton
Te pecfaton language is «combination of graphical Language |
sand aturl language
|S. Problem statement language (PSL)/ Problem statement analyzer
os
‘] Reprasents derived
Se =7 | etributes
1. [Double rectangles Represents weak entity
[Double nes Represents total
participation of an entity
| ina relationship set
Fig: 2181 Components of ER diagram.
THEI] wt are the advantages and disadvantages oH
Singram?
‘Anewer
Advantage of Edigrem
{Teiseasy and simple to understand with minimal training, Therefore ht
fel in be ued by the database designer to communscate dese
Software Requirement Specifications (SRS)
sacar sem
avez kag neem nits
en Ek odes pst nds conection rom one ae al
theater noes
Disndsontaes of BR digram
ted nit erection
i Ltedltnip representation
fi Norepresentatono date
fe Laoffoemation
BESET] toe date dieionary wet daring nttware
development?
on
What is a data dictionary definition ?
i. Data dictionary :
‘a. Data dictionaries are simple repositoriesto store information about
all dstaitems defined in DFDs,
tb Abthe requirements stage, thedata dictionary should atleast define
‘customer data items, to ensure that the customer and developer
tso the same definitions and terminologies.
\e Typical information stored inchudos:
1 The name ofthe data item is vol-explanatory
‘2 Aliase include other names by which this data item is ealled
for example, DEO for Data Entry Operator and DR for Deputy
Registrar.
8, Description/Purpose isa textual deseription of what the data
iter is used for or wi
4. Related data items capture relationships between data items
for example, total marks must always equal ointernal_marks.
plus external. marks.
5, Range of values records all possible values, for example, total
‘marks must be postive and between Oto 100,
6. Data fows capture the names ofthe procesies that generate
‘or receive the data item.
7. fata item is primitive, then data structure definition/orm
‘captures the physial structure ofthe data item,
8 Ifthe data is itself a data aggregate, then data structure
=|
sect eas/\, S
Fig. 221.1.
Que 222, ] What is Software Requirement Specification (SRS)
document ? Describe the goals of SRS. Also, give its importance.
OK
Write short note on SRS document. [ARTU 2013-14, Marks 05)
“Anewer
1. Software requirement species
akeholders and software designer
2. TheSRSis specification fra particular software product, program oF
setof program that performscertai functions in speci environment
3. Itserver.a umber of purses depending on who is writing i
4. First, the SRS could be written by the customer of a system
5 Second, the SRS could be written bya developer ofthe system,
6 The two scenarios create entirely different situations and establish
‘ealiely different purpose fr the document
First case, SRS is usedto define the cede and expectations of the
1. The second case, SRS is written to serve as a coutract document
between customer and developer.
is a communication tol between 2-080 (CSTTS
Software Requirement Specifications (SRS)
“The SRS document should view the system tobe developed ass blac
Pe SE should specity the externally visible behaviour ofthe ny xm
«6. Forthis reason, the SRS document is alo called aback br peciication
of meyatem
sicar.seadi
Software Bngineerin€ naacicasem)
ears comet
tcc ene
Needs
} tmesiee
eck
Spec a
sn ment pec
Inportnes eee andefTort recuied by deel
MOSS nce at ae tr ney aet
co vcore
ns bow an api Hina wth eae
2g din 2 in ray of
ace
seminal
eae ck as pert spe 4
ae ‘ity, maintainability, footprint, ‘security and speed of
meh cen vd na
TERT nce te
eput
bce
System
Fig. 2:88:1. The back ox view fa opto an performing fe factions,
[Gee BDA | Discune the organization of n SRS. Also, write important
issues of this organization.
or
is SRS known asthe black!
Specification SRS) documents, Why’ —
ee reeeat Define IEEE standard for SRS. [ARTO 2018-14, Marks
‘Answer ‘avwer_ |
‘Advantages of SRS documen Organization of SRS:
1 ASRS docunen: provides areferene for validationothe inal produd, [Fi Organization of the SRS document depends tow large extent oo the
2 Ath guy SRS duet in prerequisite to high quality stra sytem anya! himself bef oRen guided by the polices and standard
{elowed by the company”
|| Abigh quity SRS document reduces the dvelopnent cos
{Ll the ganization ofthe document andthe eeu toa large extent
4 Reduce the development fort ‘depend on the type of the product being developed.
5. Provide bass for entizating cont and ached ‘i Hlomever, irrespective of the compaay principles and product type, the
Serva bas fr eshancement ‘thre basi sues that any SRS document ehould discuss are
rote ete fr validation and vrifeation. 4 Fusetiona requirements,
Black box speciation 1b. Non functional requirements, and
1 SRS acunetsnldoay pect what he pte sould oad retain ‘© Guidelines for system implementation.
‘rom tating hom odo thee TERE standard of SRS:
2 Thsimeas thatthe SRSdacumsen should specify theexternal behaviour [F , Introduction
ofthe sytem and not discus the implementation issues, |
4 This view wth which a requirement epecifcation is written has been
mm asa rectangle) are not discussed at all,
shown in Fg 221 1s Document conventions
4 1oFig 2281 the SRS document describes the output produced forthe < Intended auences
itereot pee apt ods escrito othe peti eared Additional information
edie he it fo yt ew lip and te eal © Contact information#SRS team members
* t Software Engineer
i, Overall description
‘a Product perspetive
Product fanetion
ce Userclass and characteristics
Operating environment
e. User environment
{_Desigmpleentation constraints
‘e_ Assumptions and dependencies
fii, External interface requirement
a User interface
b Hardwareinterface
Software interface
“& Communication protocols and interfaces
fe. System features
System features part A
1. Deserition and priority
2 Actoneslt
‘8 anctional requirements
System features part B
1) Deseiption and priority
2 Actionesult
8 Punetionl requirements
\. Other non-funetional requirements
Performance requirements
Safety requirements
Seeunty requirements
Software quality atribtes|
© Projet documentation
{User documents
Vi. Other requirements
‘Appendix A: Terminslogy/Glosary/Defiitons list
Appendix B. Tobe determined
Important issues of organization
1
implemented rd sues
2 Sitwar devise ton
‘is what exactly required by thecawiones eres
a-2nC(CAMT-Sem-4) Software Requirement Specifications (SRS)
J) Without SRS document, it willbe very moch iffcult forthe maintenance
aaiincers to understand the functionality ofthe sytem
44 Tell be very much difficult for user document writers to write the
thsr's manuals properly without understanding the SRS document
FeeTRE [inv desirable charset god HS document
‘Answer
Software requirement specification has following main quality characteristic
i. Complete:
4 SRSshould be complete.
1. edefnesall situations that wil be encountered and system capability
toadéress them,
i, Consistent :
a Teshould be reliable.
‘Its capability function and performance level should be wel
matched.
iii, Accurate : It should specify the system capability in real world
‘cavironment and iteinteraetion with real world environment
ive, Modifiable: Logica and hierarchical structure of SRS should facilitate
‘easy modification on requirement.
Valid : A valid SRS ie one to which developer and customer can
‘understand wel thats why tis written in natural language.
vi, Verifiable: A verifiable SRSis reliable from one level of abst
another
‘Que 2.26, | What are the main activities of requirements analysis
and xpecificution ? Also discuss the desirable characteristics of good
onto
SRS document. (ARTO 2012-18, Mark 0)
newer
Activities: The main activites caried out during requirments analyst
‘nd specification phase are as follows
1. Requirements gathering and analysis
2 Requirements specification
‘Characteristics: Refer Q. 2:25, Page 2-28C, Unit’2
‘Que 227, | Lis ive desirable characteristics of ood SRS document.
Discuss the relative advantages offormal and informal requirements
specifications. (ARTO R046, Marks 05)
(ARTU 201637, Marks 10) 2-290 (CST Sey
Software Engineering
fer @.225, Page 2-280, Unit-2
ation: Re
Charncterintcn: Role 25 Tot
oan
Formal cement ‘peaiications wil ensure that the customer
1 Formal ecurmfreqiemet are et up every Paani,
Teaser fend eee
itinenie prgete needing tobe restarted from rath
ie en Ta
seeret tie
creer err
5 La een
aaa
2 elie ant atiteritl
Soesam cree
TeeRRET] Lint and incest major quality requirement of «
software requirement specification document ?
SSRS document should document the following
1. Fupetional requirements of the system :
‘©The functional requirements are the services which the end user
‘expets the final product to provide.
'b. The functional requirements of the system should clearly describe
sch of the functions thatthe system needs to perform along with
the corresponding input and output data st.
2 Non-functional requirements ofthe system :
‘© Non-functonal requirements deal withthe characteristics of the
4, ie tact eer actin.
© The non-functional requirements also include reliability issves
scurry a rent hun compu etre a
and physical constraints ete. * -—
230C(CRITSem4) Software Requirement Specifications (SRS)
A. Constraints on the system :
‘The constraints on the functions of a system may contain desirable
{the system ahould oF should not do. A constrain ean be
‘a Interface constraints
1 Performance constraints: response time, security reliability, storage
space ete.
«Operating constraints
Life cycle constraints
Aexbility ote
‘e Beonomic constraints
maintainability, rousaility, portability,
PART-3 ee
‘Software Quality Assurance (SQA): Verification and Validation,
‘SQA Plans, Software Quality Framworks,
1SO 9000 Models, SEI-CMM Model.
CONCEPT OUTLINE : PA
‘= S@A isthe quality that ensures customer satisfaction by offering
fll the eustomer deliverables on performance and standards.
+ Validation is “Are we building the right product”
1 180 9000 : I is a certification which serve as «reference for
‘contac between independent parties.
+ SEICMM model is astratogy for improving the software process, |
irrespective of actual life eycle model used.
Baa EBB,] Dincune verification and validation and their objectives.
1. Software verification is # act of activities that ensure that software
correctly implements a epecifi function ie,
“Are we building the product right”
2 Requirement validation suet of sctvitios that ensure thatthe software
‘that i going to be build is traceable to customer requirements ie Software Bagineerin
Objectives of verification and valication :
5
are we bulking the right produ
‘Traditionally software verifications
engineering methodol €
Guring development.
and validation is defined ass
ser ceavs and et cies performed by verification and validatiog
w saacosthe software prxiucts and the develop
‘eSftware hie eyele phase in parallel with,
Freer compltion of, the development effort
Thon provides early enifcton of eror, improving sft
performance entiation of program isl
Pa ateacks on two of major consnibutor of software failure
i Incormt or missing requirements and
4 Poor organization in software architecture
{Waly act as powerful isk managemeat tol
(We Vievaluate an
during cal
‘Determine thatit performs its intended Functions correctly
‘sure that it performs ao unplanned functions.
“Measure and assess the quality ani reliability of software
‘Ensure that quality is bil into the software and thatthe software wll
satisfy the software requirements
Setiiy the user that system i being developed according to standards
snd specifications,
Ee | Write » short note on software quality assurance.
aT mA
=z
Sofirare Quality Astrance (SGA) it proces that ensures thal
Aevelopd sofware neta and compos wth defined or standardized
ay pecans
Anan noing proce within he Sofware Development Life Cyl
(SDLChatrutney dks ie evel wtware to nae meets
Aer quay meses
SQA ele enue the deelpnent of high quality stare
SQA prin ue inplemeted nto typesof oftware developmen,
repudes ofthe userligsotar derlopment mel being sed
SQA incorporate nd implements eftwae testing macthodologi 1
teat software = coe
ater than checking for quit ter competion, SQA presses
forqslty inet pac of evelpent tlt sotware compl
PCM Dy greta sem
that quality ie built into software
Software Requirement Specieations (SRS)
‘With QA. the toftware development process moves into the nex.
anly once the currentprevious phase complies with the eqeined qealty
stassiards
Geet, | Explain Software Quality Aseurance SQA) wih ite cycle.
Tower |
Ineach phase of SDLC the SQA activities are as follows
ARTO 201617,
9)
‘Software initiation phase
‘a S@Ashould be involvod in writing and reviewing tie management
plan ta ensure that processes, procedures and standards identified
Inthe plan are appropriate clear accurate and venfiabie
b, During this phase, also SQA provides the quality assurance
‘management plan
Software requirements phase
During this phase, SQA makes eure thet software requirements «re
complete and testable, and properly expressed as uncial, performance
land interface requirements
‘Software design phase:
‘SQA activites during the design phase include
‘a. Toensure compliance with approved desig standards as specified
in the management plan,
1b. Assuring all software requirements are covered in softwere
components,
Ta ensure interface control documents are consistent with the
standard form and content
44. Toensure that allocated modules are included inthe etal desig
Software implementation phase :
‘SQA activites during the phase oimplementation incu checking
Results of coding and design activites including the schedule
contained isthe software develepoient plan.
Statusofall deliverables
© The activities of configuration management and software
development ibrary,
Software integration and test phase:
‘SQA activities ring the intogration phase and testing include
‘Test preparation and check ist of al the testing deliverables.
Ensure that all tests are performed according to test plans and
procedures. asses.
complete and accurate
re ompleted and the softwarg
1 SQAplarisa
=a plteson ll at
Ingres deta trates onal act
© prea plemeai
‘tne SQ plan inctode the folowing
ar etisty mich ensures the quality goals of
ties, which have Become par
Pret planning
odes of data, clases and abject, processes, design architecture
ss
‘Test pane for testing SRS
ser anal, ie belp
edit ond review
‘fe SQA plan mainly three kind of activities are performed :
1 Onpniation sect
2 Software pec
2 Conomer specific
ER wie otwae quality? Write the various
footinare gual
Refer 1.10, Page 1-110, Unt
HEEB] « sotwware development organization, identity
pousible for carrying out the quality assur
aplai the pricipal tasks they perform to meet
pe
setivtien
2-346 (CST Semm-4)
ee]
Sofware Requirement Specifications (SRS)
‘abe 24.1 shows the activities carried out forthe quality anuranc along
Tat pe peraon responnible foreach respective activity
‘Table 2341
5.No| Activitien
‘Any reaponsible person win
kkcows about the project
Development of standards,
L _ | rentae atiaton
4 | Auditing [Auditors
Principle tasks performed to enhance software quality are
1 Inapeetions :laspction means a carefuleheck or the quality of rae.
Tradone when a pece of work iscompleted, copies of work are distributed
tocororkere wh then examine the work tonate detects, A meeting
bhld tn discuss work and defects requiring to rework.
2. Reviews: Review is a QA activity that checks the quality of project,
Aliverables. This involves examining the software, its documentation
‘ind records of proces o discover errurs. Reviewing isa puble roesn=
sterror detection
5. Development of standards, procedures and guidelines ete
4 Auditing: Production of reports forthe top management summariing
the effectiveness of the quality system inthe organization.
[BSR wnt do you undertad y180 0cetiention? ve
tenets nd tmtathons
—a
rs0o0neeteaton:
1. Bogue ani Tuaalne model
inp p copes ln Ste ely
on
150 a ec tf gules or repeal igh gos
Sete
ialmporasto rela ht 50900 standart sant eis
iipckctan pecan tn no ere cnet ona pote
4 (oompetsceran ef thee stature Basel on pe ofa
bebe aertsnen ricer art >
ecco
— a
me
Po
ie —
saat paren
«Se teeta a
ex desi po buy the products from external Sourees ang
Sty oe ge Ps or Rn
Ss red am pen ogame
accom
meee many
copie tothe organizations onpge
ic anda Pg an nerve 48.
eer ae ey
Benefits of 180 9000 certification :
1 Continuous improvement
2 Ehminatewerifcation
‘8 Higher rel and perceived quality.
4 Boos eamplyee morale.
{5 Improved customer satisfaction.
Limitations of 180 9000 certification =
1 It oes not automatically lea to total quality management (TQM) ie,
‘antinuous improvement
2. Tedoee not provide any guideline for defining an appropriate process,
5 Its not full proof and thus variston in the eertifieatiou wor may
‘Que 836, ] What are the various 180 9001 requirements ?
=a
‘The main requiressents of 180 9001 a8 related to software development are
follows
1. Management responsibility +
Management must have an effective quality policy.
The responsibility and authority ofall thase whose work affect
uality must be defined and documented
2 Quality yetem,
(Contract reviews,
{Document controt
‘There must be poy
removal
Product identification,
Process contr
nepection and vesting
er procedure for document approval, issue and
2-90C (CT-Sem-4) Sofware Requirement Specifications (SRS)
cere pment : If inspection,
a SRE tame nw he ees paint rng
seats
we quai
—
Given software product
quent. 1d its requirement
specification document, explain how would you design the system
tent suite for this software product? [AKT 3074-15, Mark 19)
newer |
1. Foragiven software requirement specification and «software product,
tofocilitate development, we need to design a collection, or site. of text
‘cases that cover all the modules and functions in the system
2. Ifthe software we are writing is an extension ofan existing system. the
existing code base should ideally contain a complete suite of good unit
tests, Ifit does not, our first step is to complete the test suite for the
‘existing system. When we build the testsuite for the new system. will
be anchored in a reliable initial test suite
3. The preeristonee af atest euite provides pengrammar with “lice” goale
for tho code to achieve as they write, along with a suite of realistic
‘examples that can test the validity of the new code itelE
Atest auiteis a collection of “unit tests." The suite should have one unit
test for every module or class in the code base and one unit test foreach
‘A unit test should aim for 100% cade coverage and 100% use ease
‘overage. That is, every line of code in each module being tested should
be exercised by af least one call in the unittest. Moreover, every step of
‘each use case being tested should also be covered.
Designing a unit test for a domain class or database module begins by
‘riting atleast one eal for every function and constructor in that class
or module,
Designing a unittest for a user interface module must begia witha test
for every user option that appears on the form. Usually, these options
appear as buttons, means, textboxes, or other sidgets commom to an
interactive web page.
‘To unit test a use ease, we begin by indentifying as a “unit” those user
interface elements i, forms and associated modules that combine to
‘implement that use cate a com
RR ree eit nto 8
eat ae aioe Deel
[Explain briefly.
Ta ee pence actual ice model sed
2 CMM is used to judge the maturity of the software processes of an
27 smn,
oR
1 What does CMM level speci,
(ARTU 2018-14)
model (CMM) is strategy for imps
Tie ae
[Tooley ae meme Opting
ngnization ant identify the ke practices that are required t increase
thetmstunity of these processes.
The modelis based on best practices followed inthe organizations wi
ve
‘The ive CMM level of maturity are
Level 1: Initial
Atte level the processes followed by the organization sr
rot well defied
Procestes are nmature, Aa retul,
not available for sftware development
Further, success and failure of any projet depends on te
‘am members competence
Tere is no bass for predicting product quality, time for
‘eimpetion tc No Key Prcens Areas (KPA) are defined at
stable environmest
gascicsnt-sem4)
Software Requirement Specifications SRS)
Level: Repeatable :
“The level 2focusescon establishing base project management
se sitoybs vot mde he
roe sed om earlier experience. At this lve, organization
valled adiseiplined and organized organization.
fan be
