2 marks .doc

8/13/2019 2 marks .doc

http://slidepdf.com/reader/full/2-marks-doc 1/52

CS2301 SOFTWARE ENGINEERING L T P C 3 0 0 3

UNIT I SOFTWARE PRODUCT AND PROCESS 9

Introduction – S/W Engineering Paradigm – Verification – Validation – Life Cycle Models – System Engineering – Computer Based System – Business Process Engineering

Oerie! – Product Engineering Oerie!"

UNIT II SOFTWARE REQUIREMENTS 9

#unctional and $on%#unctional – Soft!are &ocument – 'e(uirement Engineering

Process – #easi)ility Studies – Soft!are Prototyping – Prototyping in t*e Soft!are

Process – &ata – #unctional and Be*aioral Models – Structured +nalysis and &ata

&ictionary"

UNIT III ANALYSIS, DESIGN CONCEPTS AND PRINCIPLES 9

Systems Engineering % +nalysis Concepts % &esign Process +nd Concepts – Modular

&esign – &esign ,euristic – +rc*itectural &esign – &ata &esign – -ser Interface

&esign – 'eal .ime Soft!are &esign – System &esign – 'eal .ime Eecuties – &ata

+c(uisition System – Monitoring +nd Control System"

UNIT IV TESTING 9

.aonomy Of Soft!are .esting – .ypes Of S/W .est – Blac0 Bo .esting – .esting

Boundary Conditions – Structural .esting – .est Coerage Criteria Based On &ata #lo!Mec*anisms – 'egression .esting – -nit .esting – Integration .esting – Validation

.esting – System .esting +nd &e)ugging – Soft!are Implementation .ec*ni(ues

UNIT V SOFTWARE PROJECT MANAGEMENT 9

Measures +nd Measurements – 1IP#2s La! – Soft!are Cost Estimation – #unction

Point Models – COCOMO Model – &elp*i Met*od – Sc*eduling – Earned Value

+nalysis – Error .rac0ing – Soft!are Configuration Management – Program Eolution

&ynamics – Soft!are Maintenance – Pro3ect Planning – Pro3ect Sc*eduling– 'is0 Management – C+SE .ools

TOTAL= 45 PERIODS

TET !OO"S#

4" Ian Sommerille5 6Soft!are engineering75 Seent* Edition5 Pearson Education +sia5

899:"8" 'oger S" Pressman5 6Soft!are Engineering – + practitioner2s +pproac*75 Sit*

Edition5 Mc;ra!%,ill International Edition5 899<"

REFERENCES#

4" Watts S",ump*rey57+ &iscipline for Soft!are Engineering75 Pearson Education5

899:"8" =ames #"Peters and Witold Pedryc>57Soft!are Engineering5 +n Engineering

+pproac*75 Wiley%India5 899:"

?" Step*en '"Sc*ac*5 6 Soft!are Engineering75 .ata Mc;ra!%,ill Pu)lis*ing Company

Limited5 899:"

@" S"+"Ael0ar57Soft!are Engineering75 Prentice ,all of India Pt5 899:"

8/13/2019 2 marks .doc


CS2301 $ SOFTWARE ENGINEERING

S%ORT QUESTIONS AND ANSWERS

UNIT$ISOFTWARE PRODUCT AND PROCESS

1&W'() *+ -(.) / S)(- E.*.--*.6

.*e application of a systematic5 disciplined5 (uantifia)le approac* to t*e

deelopment5 operation maintenance of soft!are "ieD.*e application of Engineering

to

Soft!are"

2&W'() (- )'- 7'((7)-*+)*7+ S)(-6

• Soft!are is engineered or deeloped5 it is not manufactured in t*e classical sense"

• Soft!are doesn2t !ear out"

• +lt*oug* t*e industry is moing to!ard component )ased assem)ly5 most

soft!are continues to )e custom )uilt"

3&W'() (- )'- 8'(+-+ P/- +:*. L86

Pro)lem definition identifies t*e pro)lem to )e soled"

.ec*nical deelopment Sole t*e Pro)lem t*roug* some .ec*nology"

Solution Integration &eliers t*e result

Status uo'epresents t*e Current status affairs"

4&L*+) ;) )'- (7)*:*)*-+ L*.-( S-<;-.)*( M-&

Soft!are re(uirement analysis -nderstand t*e nature of t*e pro)lem5information domain5 function etc"

&esign.ranslates t*e re(uirement in to Soft!are representation"

Code generation.ranslates design in to Mac*ine%reada)le form"

.esting .est t*e Logical internals functional eternals of t*e System"

5&M-.)*. +- )'- (/(7>+ RAD -&

• $ot suita)le for large%scale pro3ects"

• Commitment of deelopers customers are needed"

• $ot appropriate !*en tec*nical ris0s are *ig*"

?&W'() (- )'- )8-+ 7'(.-+ -.7;.)-- ;*. )'- S;88) 8'(+-@

Correction – .o uncoer defects in t*e Soft!are

+daptation – .o accommodate c*anges to its enironmentEn*ancement – .o proide additional functionalities"

Preention F .o sere t*e needs of its end users"

&D-*.- !;+*.-++ 87-++ -.*.--*.&

8/13/2019 2 marks .doc


W*en t*e contet of t*e engineering !or0 focuses on a )usiness enterprise"

B&W'() (- )'- ---.)+ C8;)- /(+- S+)-+6

Soft!areG Computer programs5 data structures5 related document,ard!areG Electronic deices5 inter connectiity deices5 Electro mec*anical

deices"

PeopleG -sers Operators&ata)ase Gorgani>ed collection of information"

&ocumentationG &escriptie information

ProceduresG Steps t*at define t*e specific use of eac* system element"

9&D-*.- S)(- L*-77-&

Soft!are Lifecycle is t*e period of time )eginning !it* t*e concept for a

Soft!are product ending !*eneer t*e Soft!are is no longer aaila)le for use"

SLC H SLCM +ctiities"

10&W'() (- )'- ;.7)*.+ ()( (7'*)-7);-6

• It proides t*e information needed for a )usiness function"

• Identify t*e data o)3ects and t*eir relations*ip"

EgG Customer +ttri)utesG Company name

Contact informationProduct information

Past purc*ase

11&D-*.- S+)- M-*.6

• &efine t*e processes t*at sere t*e needs of t*e ie! under consideration"• 'epresent t*e )e*aior of t*e processes and t*e assumptions on !*ic* t*e

)e*aior is )ased"

• Eplicitly define )ot*

• eogenous endogenous input to t*e model"

• 'epresent all lin0ages t*at !ill ena)le t*e engineer to )etter understand t*e ie!"

12&S)()- )'- S+)- E.*.--*. %*-(7'6

.*e !orld ie! is composed of a set of domains &iD5!*ic* can eac* )e a system5

or system of systems"

WV H J&45&85&?5KKK""5&nEac* domain is composed of specific elements E3D"

&i H JE45 E85 E?5KK""Em

Eac* element is implemented )y specifying t*e tec*nical components C0Dt*at

ac*iee t*e necessary function for an element"E3 H JC45C85C?KKK""C@"

13&M-.)*. +- )'- (7)+ ) /- 7.+*-- ;*. S+)- M-*.&

8/13/2019 2 marks .doc


• +ssumptions

• Simplifications

• Limitations

• Constraints

• Preferences"

14&W'() (- )'- *--.) (7'*)-7);-+ -:-8- ;*. !PE6

&ata arc*itecture frame!or0 for t*e information needs of a )usiness"

+pplication arc*itecture incorporates t*e role of people )usiness procedures"

.ec*nology infrastructure foundation for t*e data application arc*itecture"

15&D-*.- V-**7()*. V(*()*.&

V-**7()*.G .*e set of actiities t*at ensure t*at soft!are correctly implements a

specific function"

V(*()*.G .*e set of actiities t*at ensure t*at t*e soft!are *as )een )uilt istracea)le to customer re(uirements"

8/13/2019 2 marks .doc


UNIT$IISOFTWARE REQUIREMENTS

1&W'() *+ -(.) / S+)- R-<;*--.)+6

• Set out t*e system serices and constraints in detail"

• Seres as a contract )et!een t*e system )uyer t*e system deeloper"

1&W'() (- )'- )8-+ S)(- ++)- -<;*--.)+6

• F;.7)*.( -<;*--.)+G Serices t*e system s*ould proide"

• N.$;.7)*.( -<;*--.)+G Constraints on t*e serices"

• D(*. -<;*--.)+G reflect c*aracteristics of t*e domain"

2&W*)- . )'- ;.7)*.( -<;*--.) (. L*/( (.(--.) ++)-&

• .*e user s*ould a)le to searc* eit*er all of t*e initial set of data)ases or select a

su)set of data)ases or select su)set from it"

• .*e system s*all proide appropriate ie!ers for t*e user to read documents in

t*e document store"

• Eery order s*all )e allocated a uni(ue identifier"

3&M-.)*. +- )'- N)()*.+ -<;*--.)+ +8-7**7()*.&

• Structured natural languageG -se standard form or .emplates"

• &esign description languageG Programming language is used"• ;rap*ical notationG .et annotations is used"

• Mat*ematical SpecificationsG Based on finite state mac*ines or sets"

4&W*)- . )'- SRC A ( .-

F;.7)*. +dd node

D-+7*8)*. +dds a node to an eisting design"

I.8;)+ $ode type5 $ode position5 &esign Identifier

S;7- $ode type5 $ode position user

&esign identifier data)ase

O;)8;) &esign identifier

P-7.*)*. .*e design is open displayed on t*e user2s screenS*- --7)+ $one

5&D-*.- R-<;*--.) E.*.--*.&

'e(uirement Engineering is a process t*at inoles all of t*e actiities re(uired to

create and maintain a system re(uirements document"

.*e four generic 'e(uirement Engineering actiities areG#easi)ility study5 'e(uirement Elicitation +nalysis5 'e(uirement

8/13/2019 2 marks .doc


Specification5 Validation"

?&M-.)*. +- )'- 87-++ (7)*:*)*-+ R-<;*--.) E*7*)()*. (.(+*+&

• &omain -nderstanding

• 'e(uirement Collection

• Classification• Conflict resolution

• Prioritisation

• 'e(uirement C*ec0ing

&W'() (- )'- 8*.7*8- +)(-+ VORD -)'6

V*-8*.) *-.)**7()*.G Identify t*e serices proided to eac* ie!point"

V*-8*.) +);7);*.G ;rouping related ie!points in to *ierarc*y"

V*-8*.) 7;-.)()*.G 'efining t*e description

V*-8*.) ++)- (88*.G Identify o)3ects in OO&

B&W'() (- )'- *--.) )8-+ 7'-7>+ 7(*- ;) ;*. R-<;*--.)

V(*()*.6

Validity c*ec0sConsistency c*ec0s

Completeness c*ec0s

'ealism c*ec0sVerifia)ility"

9&D-*.- T(7-(/**)

• .racea)ility is t*e oerall property of re(uirements specification !*ic*

reflects t*e ease of finding related re(uirements"

• .*ree types of tracea)ility information to )e maintained areG

Source tracea)ility information'e(uirement tracea)ility information

&esign tracea)ility information

10&D( )'- 8*.7*8- +)(-+ C'(.- (.(--.) 87-++&

Identify pro)lem

11&S)()- )'- 8*( /-7)*:-+ (.(+*+ M-&

• .o descri)e !*at t*e customer re(uires

• .o esta)lis* a )asis for t*e creation of a soft!are design• .o define a set of re(uirements t*at can )e alidated once t*e soft!are is )uilt"

Pro)lem analysis C*ange specification

C*ange analysis

costingC*ange

Implementation

8/13/2019 2 marks .doc


12&D-*.- D()( /-7)+, ())*/;)-+ -()*.+'*8&

D()( /-7)G 'epresentation of any composite information t*at must )eunderstood )y a soft!are" It can )e any eternal entity"

A))*/;)-+G &efine t*e properties of t*e &ata o)3ect

R-()*.+'*8G Connecting t!o different data o)3ect"EgG O/-7) A))*/;)-+ R-()*.+'*8

Person $ame

+ge+ddress

O!ns

Car Ma0e

ModelBody type

13&D-*.- C(*.(*) M(*)&

C(*.(*)G Specification of t*e num)er of occurrences of one t*at can )erelated to num)er of occurrences of anot*er"

M(*)G .*e Modality of a relations*ip is 9 if t*ere is no eplicit need for t*erelations*ip to occur or t*e relations*ip is optional" .*e modality is 4 if an occurrence of

t*e relations*ip is mandatory"

14& D-*.- )'- C(*.( M(*) :(;-+ )'- ()( /-7)+ (.;(7);-

(.

6Car7"

.*e relations*ip is 6)uilds7

15&S)()- E.)*) R-()*.+'*8 *((&

E'& depicts relations*ips )et!een data o)3ects".*e E'& is t*e notation t*at is used to conduct t*e data modeling actiity"

.*e primary components inoled in t*e E'& areG

&ata o)3ects5 attri)utes relations*ips and arious types of indicators"

1?&D-*.- D()( F D*((&

+ &ata flo! diagram is a grap*ical representation t*at depicts information flo!

t*e transforms t*at are applied as data moe from input to output".*e )asic form of a data flo! diagram 5also 0no!n as a data flo! grap* or a

)u))le c*art"

1&W'() *+ -(.) / I.()*. C.)*.;*)6

W*en !e refine a fundamental model for a system5 t*e information flo!

continuity must )e maintained "ie5 input output to eac* refinement must remains t*esame"

Person

Car

Manufacturer )uild Car

8/13/2019 2 marks .doc


1B&D( ( DFD CFD ( )-+) .*)*. ++)- G(+ T;/*.- -.*.-&

DFD CFD

+)solute tan0 pressure Conerted

Pressure

+)oe pressure

Ma pressure

19&D-*.- !-'(:*( M-*.&

.*e state transition diagram represents t*e )e*aior of a system )y depicting its

states and t*e eents t*at cause t*e system to c*ange state"

20&D( )'- C.)-H) -:- DFD )'- S(- '- S)(-&

user commands +larm type

.elep*one

$um)er toneSensor status &isplay

information

21&W'() *+ -(.) / D()( *7)*.(6

.*e &ata dictionary is an organi>ed listing of all data elements t*at are pertinentto t*e system5 !it* precise5 rigorous definitions so t*at )ot* user system analyst !ill

*ae a common understanding of inputs5 outputs5 components of store intermediate

calculations"

22&D-*.- P7-++ S8-7**7()*.&

Process Specification is used to descri)e all flo! model processes t*at appear at

t*e final leel of refinement"C*ec0

Conert

pressureC*ec0

Conert

pressure

Safe*omesoft!are

Control

panelSensors

+larm

.elep*oneline

Control

Panel

display

8/13/2019 2 marks .doc


.*e content of t*e Process Specification include narratie tet5 a program design

language5 mat*ematical e(uations5 ta)les5 diagrams or c*arts"

23&W'() -+ ()( *7)*.( 7.)(*.+6

$ameG .*e primary name of t*e data"

+liasG ot*er names usedW*ere%used/,o!%usedG + listing of processes t*at use t*e data or control item"

Content descriptionG + notation for representing t*e content

Supplementary informationG Ot*er information li0e restrictions5 limitations etc"

24&W*)- . )'- D()( *7)*.( )'- ()( *)- T--8'.- N;/-&

$amesG .elep*one num)er

+liasesG none

W*ere used/,o! usedG assess against set%up&escription

.elep*one num)er H local num)erN long distance num)er

Local num)er H prefi access num)er

Long distance num)er H 4 area code local num)er +rea code H 99 N N <Q4

Prefi H R a t*ree digit num)er t*at neer starts !it* 9 or 4R

25&W'() *+ -(.) / T' (( P))8*.6

• ;iing t*e user a system !*ic* is incomplete and t*en modifying and augmenting

it as t*e user re(uirements )ecome clear"

• .*e o)3ectie is to alidate or derie t*e system re(uirements"

• Start !it* t*ose re(uirements t*at are not !ell understood since you need to find

more a)out t*em"

8/13/2019 2 marks .doc


U.*)$IIIANALYSIS, DESIGN CONCEPTS AND PRINCIPLES

1&W'() *+ )'- ;+- A7'*)-7);( -+*.6

.*e +rc*itectural design defines t*e relations*ip )et!een ma3or structuralelements of t*e soft!are5 t*e 6design patterns7 t*at can )e used 5and t*e constraints t*at

affect t*e !ay in !*ic* arc*itectural design patterns can )e applied"

2&D-*.- S)(- -+*.&

•Soft!are design is an iteratie process t*roug* re(uirements are translated into a6)lue print7 for constructing t*e soft!are"

• .*e )lue print depicts a *olistic ie! of soft!are"

3&M-.)*. +- )'- D-+*. 8*.7*8-+&

• .*e design process s*ould not suffer from tunnel ision"

• .*e design s*ould not reinent t*e !*eel"

• .*e &esign s*ould e*i)it uniformity integration"

• &esign is not coding 5coding is not design"

• .*e design s*ould )e tracea)le to t*e analysis model"

4&S)()- P7-;( (/+)(7)*.&

+ Procedural a)straction is a named se(uence of instructions t*at *as a specificand limited function"

EgG OpenWal0 to t*e door5 reac* out grasp t*e 0no)5 turn 0no) pull door

Step a!ay from moing door"

5&W'() -+ D()( (/+)(7)*. 7.)(*.+6

+ &ata a)straction is a named collection of data t*at descri)es a data o)3ectEgG door +ttri)utesG door type5 S!ing direction5 Opening mec*anism5 !eig*t"

?&W'() -+ M;(*) 7.7-8) -(.6

Soft!are arc*itecture em)odies modularity ie5 Soft!are is named in to

addressa)le components called modules5 t*at are integrated finally"

CP4P8D T CP4D CP8D

.*e perceied compleity of a pro)lem t*at com)ines p4 :p8 is greater t*an perceied compleity !*en eac* pro)lem is considered separately"

&M-.)*. +- )'- 7*)-*(+ ;+- ) -*.- --7)*:- ;( -+*. &

8/13/2019 2 marks .doc


• Modular decomposa)ility

• Modular Composa)ility

• Modular -nderstanda)ility

• Modular Continuity"

• Modular protection

B&D-*.- F(.$*. F(.$;)&

F(.$;) + measure of t*e num)er of modules t*at are directly controlled )yanot*er module"

F(.$*. Indicates *o! many modules directly control a gien module"

9&D*--.)*()- '*.)( 8()*)*.*. V-)*7( 8()*)*.*.&

%*.)( 8()*)*.*. V-)*7( 8()*)*.*.

1"&efines separate )ranc*es of t*e 1&.*e Control !or0 s*ould )eModular ,ierarc*y for eac* eac* distri)uted top%do!n in t*e program

ma3or program function structure"

2"Propagaton of fe!er side%effects 2",ig*er pro)a)ility of side effects"

3"Soft!are is easier to maintain 3"suscepti)le to side effects !*en

C*anges are made"

10& W*)- . )'- 7.7-8) F;.7)*.( *.-8-.-.7-&

• #unctional independence is ac*ieed )y deeloping modules !it* 6single

minded7 function and an 6aersion7 to ecessie interaction !it* ot*er modules"

• Independent modules 5is easier to deelop )ecause function may )e

compartmentali>ed5 interfaces are simplified"

• Independent modules are easier to maintain"

11&D*+)*.;*+' /-)--. -H8-7)- -<;*--.)+ (. -H7*)*. -<;*--.)+&

Epected re(uirements Eciting re(uirements'e(uirements are implicit to product

Customer does not state t*em eplicitly

'e(uirements reflect features t*at go )eyond t*e customer2s epectations and

proe t*em to )e ery satisfying !*en

present"

12&W'() *+ -(.) / +)(- 8))8*.6

Soft!are prototyping is a met*od of creating a model for t*e soft!are product".*is is deeloped )ased on t*e currently 0no!n re(uirements" Soft!are prototyping*elps

in t*e )etter understanding of t*e re(uired system" It is applied for complicated and large

systems" In soft!are prototyping5 t*e customer defines a set of general o)3ecties for t*esoft!are5 )ut does not identify t*e real input5 processing and output re(uirements"

13&W'() *+ )'- > 8;7) +)(- -+*. 87-++ (. ' -+ )'*+6

8/13/2019 2 marks .doc


+ design model t*at encompasses arc*itectural5 interface5 component leel and

t*eir representations is t*e primary !or0 product t*at is produced during soft!are

design"Soft!are engineers conduct eac* of t*e design tas0s"

14&D-*.- )'- )- +)(- (7'*)-7);-&.*e soft!are arc*itecture of a program or a computing system is t*e structure of

t*e system5 !*ic* comprises soft!are components5 eternally isi)le properties of t*ose

components and relations*ip among t*em" .*e arc*itecture is t*e manner in !*ic* t*earious components of t*e )uilding are integrated to form a co*esie !*ole"

U.*)$IV

TESTING

1&D-*.- /(7> /H )-+)*. +)()-&

Blac0 )o testing focuses on t*e functional re(uirements of t*e soft!are" .estcases are decided on t*e )asis of t*e re(uirements or specifications of t*e program and

internals of program are not considered" .est cases are generated )ased on program

code"

2&W'() *+ -(.) / +)(- 7'(.-6

Soft!are c*ange is defined as t*e c*ange in nature of soft!are as t*e re(uirementsof soft!are c*anges"

3&W' )-+)*. *+ *8)(.) *)' -+8-7) ) +)(-6

+ testing process focuses on logical internals of soft!are ensuring t*at all

statements *ae )een tested and all are functional eternals" W*ile testing5 !e eecute

t*e

entire program )efore it gets to t*e customer !it* specific indent of finding andremoing

all errors" In order to find t*e *ig*est num)er of errors5 test must )e conducted

systematically and test cases must )e designed using disciplined tec*ni(ues"

4&W*)- +') .)-+ . -8**7( -+)*()*. -+&

Estimation model for computer soft!are uses empirically deried formulas to predict effort as a function of line of codes LOCD and function points #PD" .*e alues

of

LOC and #P estimated are plugged into estimation model" .*e empirical data t*at

support most estimation models are deried from a limited sample of pro3ects" So5results

o)tained from models s*ould )e used 3udiciously" .*e model must )e tested and

compared !it* actual and predicted data

5&J;+)* )'- )- S)(- *+ -.*.---

Soft!are is engineered not manufactured" +lt*oug* some similarities eit )et!een soft!are deelopment and *ard!are manufacture5 t*e t!o actiities a r e

fundamentally different" Bot* actiities are dependent on people5 )ut t*e relations*ip

8/13/2019 2 marks .doc


)et!een people applied and !or0 accomplis*ed is entirely different" Bot* actiities

re(uire t*e construction of a 6Product7 )ut t*e approac*es are different2"

?& S)()- L-'(.+ F*)' (&

Oer t*e lifetime of a system5 t*e incremental c*ange in eac* release is

approimately constant"

&D-*.- +)(- +78-&

.*e first soft!are pro3ect management actiity is t*e determination of soft!arescope" Scope is defined ans!ering t*e follo!ing (uestions"

ContetG W*at constraints are imposed as a result of t*e contet"

Information o)3ectiesG W*at data o)3ects are re(uired for inputU

#unction and performanceG +re any special performance c*aracteristics to )e addressedU

B&D-*.- 87-++ ();*)&

In recent years t*ere *as )een a significant emp*asis on process maturity" .*e

Soft!are Engineering Institute" SEID *as deeloped a compre*ensie model predicatedon a set of soft!are engineering capa)ilities t*at s*ould )e present as organi>ations

reac*different leels of process maturity ".*e grading sc*ema determines compliance !it* a

capa)ility maturity model CMMD t*at defines 0ey actiities re(uired at different leels

of process maturity"

9&D*+)*.;*+' /-)--. (8'( )-+)*. (. /-)( )-+)*.&

+lp*a test Beta test

.*e alp*a test is conducted at t*e deeloper site" .*e soft!are is used in a natural

setting !it* t*e deeloper 6loo0ing oer

t*e s*oulder7 of t*e user and recording.*e )eta test is conducted at one or more

customer sites )y t*e end user of t*e

soft!are" .*e )eta test is a Lie applicationof t*e soft!are in an enironment t*at

pro)lems" cannot )e controlled )y t*e deeloper"

10&W'() *+ +)(- (7'*)-7);-".*e soft!are arc*itecture of a program or computing system is t*e structure or

structures of t*e system5 !*ic* comprises soft!are components5 t*e eternally isi)le

properties of t*ose components and t*e relations*ips among t*em"

11&W'() *+ -(.) / +)(- 7'(.-6

Once soft!are is put into use5 ne! re(uirement emerge and eisting re(uirementsc*ange as t*e )usiness running t*at soft!are c*anges parts of t*e soft!are may *ae to

)e modified to correct errors t*at are found in operation5 improe its performance or

ot*er non functional c*aracteristics" .*is entire means t*at 5after deliery 5soft!are

system al!ays eole in response to demands for c*anges"

8/13/2019 2 marks .doc


UNIT$V

SOFTWARE PROJECT MANAGEMENT

1& W*)- +') .)-+ . -+)*()*. -+&

Empirical estimation models can )e used to complement decomposition

tec*ni(ues and offer a potentially alua)le approac* in t*eir o!n rig*t" + model is )ased

on eperience and ta0es t*e form&HfiD

W*ere d –num)er of estimated alues

i –selected independent parameters

2&'() *+ +)(- -(+;-6

+ soft!are measure is a mapping from a set of o)3ects in t*e soft!areengineering !orld information a set of mat*ematical construct suc* as num)ers or

ectors of num)ers"

3&W'() *+ +)(- -)*76

+ soft!are metric is a simple (uantitatie measure deria)le from any attri)ute

of t*e soft!are life cycle

E"g"D LOC Line Of CodeD#unction point"

4&D-*.- +)(- -(+;--.)&

+ soft!are measurement is a tec*ni(ue or met*od t*at applies soft!are

measures to a class of soft!are engineering o)3ects to ac*iee a predefined goal"

5&W'() (- )'- 7'((7)-*+)*7+ +)(- -(+;--.)6

O)3ect of measurement

Purpose measurement

Source of measure

Measured property

Contet of measurement"

?&W'() *+ --++*. )-+)*.6

'egression testing is t*e re%eecution of some su)3ect tets t*at *ae already )een conducted to ensure t*at c*anges *ae not propagated unintended side effects"

&W'() *+ +>- )-+)*.6

Smo0e testing is an integration approac* t*at is commonly used !*en 6s*rin0!rapped7soft!are products are )eing deeloped"

8/13/2019 2 marks .doc


B&W'() *+ -7:- )-+)*.6

'ecoery testing is a system test t*at forces t*e soft!are to fail in a ariety of !ays and erifies t*at recoery is properly performed"

9&W'() *+ +-7;*) )-+)*.6Security testing attempts to erify t*at protection mec*anism )uilt into a system

!ill protect it from improper penetration"

10&W'() *+ +)-++ )-+)*.6

+ stress testing eecutes a system in a manner t*at demands resources in

a)normal (uantity5 fre(uency5 or olume"

11&W'() *+ 8-(.7- )-+)*.6

Performance testing is designed to test t*e run%time performance of soft!are

!it*in t*e contet of an integrated system"

12&W'() *+ 77()*7 78-H*)6Cyclomatic compleity is gien )y McCa)e" .*e general formula to compute

cyclomatic compleity isMHV ;DHE – $ 8P

W*ere

E%$um)er of edges $%$um)er of nodes

P%$um)er of unconnected pat*s of t*e grap*"

13&W'() *+ CASE6

C+SE tool stands for Computer +ided Soft!are Engineering" Computer +ided

Soft!are Engineering tools assists soft!are engineering manages and practitioners in

eery actiity associated !it* t*e soft!are process"

14&W'() *+ +)(- )-+)*.6

.*e testing process focuses on t*e logical internals of t*e soft!are5 ensuring t*atall statements *ae )een tested5 and on t*e functional eternals5 t*at is5 defined input

!ill

produce actual results t*at agree !it* re(uired results"

15&W'() *+ +);7);( )-+)*.6

Structural testing is testing t*e internal logic of a code"

1?&W'() *+ +)()--.) 7:-(-6

Statement coerage is t*e testing to test eery statement in t*e code *as )een

eecuted at least once"

1&W'() *+ /(.7' 7:-(-6

In )ranc* coerage testing eac* )ranc* in t*e code is eecuted at least once"

8/13/2019 2 marks .doc


1B&W'() *+ 8()' )-+)*.6

In pat* testing all possi)le logical pat*s in a program are tested"

19&W'() *+ COCOMO -6

COCOMO stands for COnstructie COst MOdel" It is used for cost

EffortHa R A&LOC )W*ere a and ) are t!o parameters of t*e model !*ose specific alues are selected upon

t*e class of t*e soft!are system"

20&W'() *+ ;.7)*. 8*.)6

#unction point is t*e si>e of measure it is also used to estimate t*e soft!are cost"

#unction point #PDH#unction Count #CD R Value ad3ustment factor V+#D"

#unction Count #CDH∑ ∑ i3 !i3

W*ere % $um)er of elements

! % Weig*t

Value ad3ustment factor V+#DH9"Q< 9"94 ∑ f i

21&W'() (- /;+*.-++ 87-++ -.*.--*. )+6

By modeling t*e strategic information re(uirements of an organi>ation5 )usiness

process engineering tools proide a 6meta%model7 from !*ic* specific informationsystems are deried"

22&W'() *+ ( 87-++ -*. (. (.(--.) )6

Process modeling and management tools are used to represent t*e 0ey elements

of a process so it can )e )etter understood" Suc* tools can proide lin0s to process

descriptions t*at *elp t*ose inoled in t*e process to understand t*e !or0 tas0s t*at are

re(uired to perform it"

23&W'() *+ /))$;8 (88(7'6

System deeloped starting from detailed modules" .esting starts from t*edetailed modules and proceeds up to t*e *ig*er leels of *ierarc*y"

24&D-*.- )8$. )-+)*.&

System deeloped starting from most general modules" .esting starts from t*e

most general module"

25&D-*.- /* /(. )-+)*.&

+ll modules integrated in a single step and tested as an entire system

2?& D-*.- +(.*7' )-+)*.".esting com)ines t*e ideas of )ottom%up and top%do!n testing )y defining a

certain target layer in t*e *ierarc*y of t*e module" .*e modules )elo! t*is layer is

testedfollo!ing )ottom%up approac*5 !*ereas t*ose a)oe t*e target layer are su)3ected to

topdo!n

testing"

8/13/2019 2 marks .doc


2&W'() *+ P(>*.+.+ L(6

Par0inson2s La! states t*at !or0 epands to fill t*e time aaila)le" .*e cost isdetermined )y aaila)le resources rat*er t*an )y o)3ectie assessment"

2B&W'() *+ +)(- (*.)-.(.7-6C*anges to t*e soft!are are made in response to c*anged re(uirements )ut t*e

fundamental structure of t*e soft!are remains sta)le"

29&W'() *+ (7'*)-7);( )(.+()*.6

.*is is a more radical approac* to soft!are c*ange t*en maintenance as it

inoles ma0ing significant c*anges to t*e arc*itecture of t*e soft!are system"

30&W'() *+ +)(- -$-.*.--*.6

$o functionality is added to t*e system" 'at*er5 t*e system is modified to ma0e

it easier to understand and c*ange" System re%engineering may inole some structural

modifications )ut does not usually inole ma3or c*ange"

31&D-*.- !>+ (&

Soft!are !as deliered late5 !as unrelia)le5 cost seeral times t*e original

estimates and often e*i)ited poor performance c*aracteristics"

32&W'() *+ D-8'* -6

In &elp*i met*od5 a num)er of parameters to )e determined )ased on as eperts

estimates"

.*e group estimate is ta0en as an aerage of t*e !eig*ted indiidual estimtes5computed as

EstimateHlo!er )ound of estimate@Rmost li0ely estimate upper )ound of estimateD/Q

VarianceHupper )ound of estimate%lo!er )ound of estimateD/Q

33&S)()- L-'(.+ F*+) ("

+ program t*at is used in real !orld enironment necessarily must c*ange or )ecome progressiely less useful in t*at enironment"

8/13/2019 2 marks .doc


CS1353 $SOFTWARE ENGINEERING

SAMPLE !IG QUESTIONS AND %INTS

UNIT 1SOFTWARE PRODUCT AND PROCESS

4"&efine Soft!are process modelU Eplain any one of it !it* a neat diagram

.*e strategy t*at encompasses process5 met*ods5 and tools"Eplanation of any of t*e eig*t process model"

8"Epalin t*e *ierarc*y of Business process Engineering "Enterprise

Business area +nalysis

Business System &esignConstruction Engineering

?"Eplain Soft!are Life cycle process&efinition of SLC5SLCM

Predeelopment process

&eelopment process"

@"Eplain Eolutionary process model

Incremental model

WI$%WI$ spiral modelSpiral model

Concurrent deelopment model

<"Eplain t*e different layers of Soft!are EngineeringU

.ools

Met*ods

Process+ (uality focus

U.*)$IISOFTWARE REQUIREMENTS

Q"Bulid t*e follo!ing systemG

6+ $et!or0 )ased course registration system for your -niersity7&eelop an E'& a contet leel model for t*e a)oe"

8/13/2019 2 marks .doc


Create an E'&

Create a leel 9 &#&"

:"Eplain .ransform Mapping !it* Safe*ome Soft!are

&efinition of .ransform Mapping

Eplain Safe*ome applicationsImplement .ransform mapping

"Eplain )riefly #unctional Modeling&efinition of #unctional Modeling

&ata #lo! &iagrams

Etensions for real time systems

"Eplain t*e arious &esign concepts in detail"

+)straction

'efinement

ModularityControl ,ierarc*y

Structural Partitioning&ata structure

Information *iding

49"&iscuss t*e arious p*ases of +nalysis Modeling"

&ata Modeling

#unctional Modeling Information flo!

Be*aioral Modeling.*e &ata dictionary

UNIT$IIIANALYSIS, DESIGN CONCEPTS AND PRINCIPLES

44"&iscuss )riefly Effectie Modular &esign"#unctional Independence"

Co*esion

Coupling

48"Epalin -ser Interface &esign actiities

Interface design models

Interface design process&efining Interface o)3ects actions

&esign Issues"

4?"&iscuss in detail Soft!are configuration ManagementU

.*e SCM process

Version ControlC*ange control

SCM standards

8/13/2019 2 marks .doc


4@"Eplain 'eal .ime Systems"

'eal .ime Soft!are design2System &esign

'eal time eecuties

4<"W*at is Soft!are +rc*itectureU Eplain it"

&efinition

Eplanation

U.*)$IV

TESTING

4Q"Eplain in detail Blac0 )o testing in detailSynta drien testing

&ecision ta)le )ased testing

Cause effects grap* in #unctional testing

4:",o! Boundary test conditions are ac*ieedU

#igureEplanation

4"Eplain in detail Structural testingUStatement coerage

Branc* coerage

Pat* coerage

Eample

4"Eplain in detail Soft!are .esting Strategies"

-nit testingIntegration testing

Validation testing

System testing

89"Eplain t*e test coerage criteria )ased on &ata flo! mec*anisms"

Basic )loc0

+ll%usec%use

p%use

du%pat*

8/13/2019 2 marks .doc


CS2301-SOFTWARE ENGINEERINGTWO MARKS(ALL UNITS)

1. What is softa!" "#$i#""!i#$%Software engineering is a discipline in which theories, methods andtoolsare applied to develop professional software.2& What is Softa!" %Software is nothing but a collection of computer programs that are

relateddocuments that are indented to provide desiredfeatures,functionalities and betterperformance.3& What a!" th" 'ha!a't"!isti's of th" softa!"%Software is engineered,not manufactured.Software does not wear out.Most software is custom built rather than being assembled fromcomponents.4. What a!" th" a!ios 'at"$o!i"s of softa!"%System software

Application softwareEngineering/Scientific softwareEmbedded softwareeb ApplicationsArtificial !ntelligence software". What a!" th" 'ha**"#$"s i# softa!"%#opying with legacy systems.$eterogeneity challenge%elivery times challenge&. +"fi#" softa!" ,!o'"ss.Software process is defined as the structured set of activities that are

re'uired to develop the software system.& What a!" th" f#.a/"#ta* a'tiiti"s of a softa!" ,!o'"ss%Specification%esign and implementation(alidationEvolution& What a!" th" /!"**a a'tiiti"s of a softa!" ,!o'"ss%Software pro)ect trac*ing and control.

8/13/2019 2 marks .doc


+is* management.Software uality Assurance.-ormal echnical +eviews.Software #onfiguration Management.or* product preparation and production.

+eusability management.Measurement.& What a!" th" /"!its of i#'!"/"#ta* /o."*%i. he incremental model can be adopted when tere are less numberof people involved in the pro)ect.ii. echnical ris*s can be managed with each increment.iii. -or a very small time span,at least core product can be delivered tothecustomer.10& List th" tas !"$io#s i# th" S,i!a* /o."*&

Csto/"! 'o//#i'atio# 4 !n this region it is suggested toestablish customer communication.5*a##i#$ 4 All planning activities are carried out in order todefine resources timeline and other pro)ect related activities.Ris a#a*6sis 4 he tas*s re'uired to calculate technical andmanagement ris*s.E#$i#""!i#$ 4 !n this the tas* region,tas*s re'uired to build oneor more representations of applications are carried outCo#st!'t a#. !"*"as" 4 All the necessary tas*s re'uired toconstruct,test,install the applications are conducted.Csto/"! "a*atio# 4 #ustomers feedbac* is obtained and

based on the customer evaluation re'uired tas*s are performed andimplemented at installation stage.11& What a!" th" .!aa's of s,i!a* /o."*%i. !t is based on customer communication.!f the communication is notproper then the software product that gets developed will not be theupto the mar*.ii. !t demands considerable ris* assessment.!f the ris* assessment isdoneproperly then only the successful product can be obtained.12& What is S6st"/ E#$i#""!i#$%

System Engineering means designing,implementing,deploying andoperating systems which include hardware,software and people.10& List th" ,!o'"ss /at!it6 *""*s i# SEIs CMM&L""* 17I#itia* 4 -ew processes are defined and individual efforts areta*en.L""* 27R","ata*" 4 o trac* cost schedule and functionality basicpro)ect management processes are established.

8/13/2019 2 marks .doc


L""* 37+"fi#". 4 he process is standardied, documented andfollowed.L""* 87Ma#a$". 4 2oth the software process and product are'uantitatively understood and controlled using detailed measures.L""* 97O,ti/i:i#$ 4 Establish mechanisms to plan and implement

change.14. What is a# "ff"'to! ,!o'"ss% he effector process is a process that verifies itself.he effectorprocesse3ists in certain criteria.19& +"fi#" th" 'o/,t"! as". s6st"/& he computer based system can be defined as a set or anarrangement of elements that are organied to accomplish some predefined goal byprocessinginformation5.

1;& What .o"s <"!ifi'atio# !",!"s"#t%(erification represents the set of activities that are carried out toconfirmthat the software correctly implements the specific functionality.1& What .o"s <a*i.atio# !",!"s"#t%(alidation represents the set of activities that ensure that thesoftware thathas been built is satisfying the customer re'uirements.1& What a!" th" st",s fo**o". i# t"sti#$%i. U#it t"sti#$ 4 he individual components are tested in this type of testing.

ii& Mo.*" t"sti#$ 4 +elated collection of independent componentsaretested.iii& S-s6st"/ t"sti#$ 4 his is a *ind of integration testing.(ariousmodules are integrated into a subsystem and the whole subsystem istested.i& S6st"/ t"sti#$ 4 he whole system is tested in this system.v. A''",ta#'" t"sti#$ 4 his type of testing involves testing of thesystemwith customer data.!f the system behaves as per customer need thenit is

accepted.1& What is th" s" of CMM%#apability Maturity Model is used in assessing how well anorganisationsprocesses allow to complete and manage new software pro)ects.20& Na/" th" Eo*tio#a!6 ,!o'"ss Mo."*s&i. !ncremental modelii. Spiral model

8/13/2019 2 marks .doc


iii. !67!6 spiral modeliv. #oncurrent %evelopment21& What is !"=i!"/"#t "#$i#""!i#$%+e'uirement engineering is the process of establishing the servicesthat

the customer re'uires from the system and the constraints underwhich it operates and isdeveloped.22& What a!" th" a!ios t6,"s of t!a'"ai*it6 i# softa!""#$i#""!i#$%i& So!'" t!a'"ai*it6 4 hese are basically the lin*s fromre'uirement tosta*eholders who propose these re'uirements.ii& R"=i!"/"#ts t!a'"ai*it6 4 hese are lin*s between dependantre'uirements.iii. +"si$# t!a'"ai*it6 4 hese are lin*s from re'uirements to

design.23& +"fi#" softa!" ,!otot6,i#$&Software prototyping is defined as a rapid software development forvalidating the re'uirements.28& What a!" th" "#"fits of ,!otot6,i#$%i. 8rototype serves as a basis for deriving system specification.ii. %esign 'uality can be improved.iii. System can be maintained easily.iv. %evelopment efforts may get reduced.v. System usability can be improved.29& What a!" th" ,!otot6,i#$ a,,!oa'h"s i# softa!" ,!o'"ss%

"i& Eo*tio#a!6 ,!otot6,i#$ 4 !n this approach of systemdevelopment,the initial prototype is prepared and it is then refined through numberof stages to final stage.ii. Th!o-aa6 ,!otot6,i#$ 4 9sing this approach a rough practicalimplementation of the system is produced. he re'uirement problemscanbe identified from this implementation. !t is then discarded. System isthen developed using some different engineering paradigm.

2;& What a!" th" a.a#ta$"s of "o*tio#a!6 ,!otot6,i#$%i. -ast delivery of the wor*ing system.ii. 9ser is involved while developing the system.iii. More useful system can be delivered.iv. Specification,design and implementation wor* in co7ordinatedmanner.2& What a!" th" a!ios Ra,i. ,!otot6,i#$ t"'h#i="s%i. %ynamic high level language development.

8/13/2019 2 marks .doc


ii. %atabase programming.iii. #omponent and application assembly.2& What is th" s" of Us"! I#t"!fa'" ,!otot6,i#$% his prototyping is used to pre7specify the loo* and feel of userinterface

in an effective way.2& What a!" th" 'ha!a't"!isti's of SRS%i& Co!!"'t 4 he S+S should be made up to date when appropriatere'uirements are identified.ii& U#a/i$os 4 hen the re'uirements are correctly understoodthenonly it is possible to write an unambiguous software.iii& Co/,*"t" 4 o ma*e S+S complete,it shold be specified what asoftwaredesigner wants to create software.i& Co#sist"#t 4 !t should be consistent with reference to the

functionalitiesidentified.& S,"'ifi' 4 he re'uirements should be mentioned specifically.vi. T!a'"a*" 4 hat is the need for mentioned re'uirement:hisshould becorrectly identified.30& What a!" th" o>"'ti"s of A#a*6sis /o."*i#$%i. o describe what the customer re'uires.ii. o establish a basis for the creation of software design.iii. o devise a set of valid re'uirements after which the software canbe

built.31& What is .ata /o."*i#$%%ata modeling is the basic step in the analysis modeling. !n datamodelingthe data ob)ects are e3amined independently of processing. he datamodelrepresents how data are related with one another.32& What is a .ata o>"'t%%ata ob)ect is a collection of attributes that act as an aspect,characteristic,'uality, or descriptor of the ob)ect.

33& What a!" att!it"s%Attributes are the one, which defines the properties of data ob)ect.38& What is 'a!.i#a*it6 i# .ata /o."*i#$%&#ardinality in data modeling, cardinality specifies how the number of occurrences of one ob)ect is related to the number of occurrences ofanotherob)ect.

8/13/2019 2 marks .doc


39& What .o"s /o.a*it6 i# .ata /o."*i#$ i#.i'at"s%Modality indicates whether or not a particular data ob)ect mustparticipatein the relationship.3;& What is ER+%

Entity +elationship %iagram is the graphical representation of theob)ectrelationship pair.!t is mainly used in database applications.3& What is +F+%%ata -low %iagram depicts the information flow and the transformsthatare applied on the data as it moves from input to output.3& What .o"s L""*0 +F+ !",!"s"#t%;evel< %-% is called as =fundamental system model or =conte3tmodel.!n the conte3t model the entire software system is representedby a single

bubble with input and output indicated by incoming and outgoingarrows.3& What is a stat" t!a#sitio# .ia$!a/%State transition diagram is basically a collection of states andevents.heevents cause the system to change its state.!t also represents whatactions are tobe ta*en on the occurrence of particular event.4<. +"fi#" +ata +i'tio#a!6. he data dictionary can be defined as an organied collection of allthe

data elements of the system with precise and rigorous definitions sothat user andsystem analyst will have a common understanding ofinputs,outputs,componentsof stores and intermediate calculations.81& What a!" th" "*"/"#ts of A#a*6sis /o."*%i. %ata %ictionaryii. Entity +elationship %iagramiii. %ata -low %iagramiv. State ransition %iagramv. #ontrol Specification

vi. 8rocess specification82& What a!" th" "*"/"#ts of ."si$# /o."*%i. %ata designii. Architectural designiii. !nterface designiv. #omponent7level design83& +"fi#" ."si$# ,!o'"ss&%esign process is a se'uence of steps carried through which the

8/13/2019 2 marks .doc


re'uirements are translated into a system or software model.88& List th" ,!i#'i,*"s of a softa!" ."si$#&i. he design process should not suffer from tunnel vision5.ii. he design should be traceable to the analysis model.iii. he design should e3hibit uniformity and integration.

iv. %esign is not coding.v. he design should not reinvent the wheel.>89& What is th" "#"fit of /o.*a! ."si$#%#hanges made during testing and maintenance becomes manageableandthey do not affect other modules.8;& What is a 'oh"si" /o.*"%A cohesive module performs only one tas*5 in software procedurewithlittle interaction with other modules. !n other words cohesive module

performsonly one thing.8& What a!" th" .iff"!"#t t6,"s of Coh"sio#%i& Coi#'i."#ta**6 'oh"si" 4 he modules in which the set !?of tas*sarerelated with each other loosely then such modules are calledcoincidentally cohesive.ii& Lo$i'a**6 'oh"si" 4 A module that performs the tas*s that arelogicallyrelated with each other is called logically cohesive.iii& T"/,o!a* 'oh"sio# 4 he module in which the tas*s need to be

e3ecuted in some specific time span is called temporal cohesive.i& 5!o'".!a* 'oh"sio# 4 hen processing elements of a modulearerelated with one another and must be e3ecuted in some specific orderthen such module is called procedural cohesive.v. Co//#i'atio#a* 'oh"sio# 4 hen the processing elements of amodule share the data then such module is called communicationalcohesive.8& What is Co,*i#$%#oupling is the measure of interconnection among modules in aprogram

structure. !t depends on the interface comple3ity between modules.8& What a!" th" a!ios t6,"s of 'o,*i#$%i& +ata 'o,*i#$ 4 he data coupling is possible by parameterpassing ordata interaction.ii& Co#t!o* 'o,*i#$ 4 he modules share related control data incontrolcoupling.

8/13/2019 2 marks .doc


iii& Co//o# 'o,*i#$ 4 he common data or a global data is sharedamongmodules.iv. Co#t"#t 'o,*i#$ @ #ontent coupling occurs when one modulema*es

use of data or control information maintained in another module.90& What a!" th" 'o//o# a'tiiti"s i# ."si$# ,!o'"ss%i. S6st"/ st!'t!i#$ @ he system is subdivided into principlesubsystems components and communications between thesesubsystemsare identified.ii. Co#t!o* /o."*i#$ 4 A model of control relationships betweendifferentparts of the system is established.iii& Mo.*a! ."'o/,ositio# 4 he identified subsystems aredecomposed

into modules.91& What a!" th" "#"fits of ho!i:o#ta* ,a!titio#i#$%i. Software that is easy to test.ii. Software that is easier to maintain.iii. 8ropagation of fewer sideeffects.iv. Software that is easier to e3tend.92& What is "!ti'a* ,a!titio#i#$%(ertical partitioning often called factoring suggests that the controlandwor* should be distributed top7down in program structure.

93& What a!" th" a.a#ta$"s of "!ti'a* ,a!titio#i#$%i. hese are easy to maintain changes.ii. hey reduce the change impact and error propagation.98& What a!" th" a!ios "*"/"#ts of .ata ."si$#%i& +ata o>"'t 4 he data ob)ects are identified and relationshipamongvarious data ob)ects can be represented using E+% or datadictionaries.ii. +ataas"s 4 9sing software design model, the data models aretranslatedinto data structures and data bases at the application level.

iii. +ata a!"hos"s 4 At the business level useful information isidentifiedfrom various databases and the data warehouses are created.99& List th" $i."*i#"s fo! .ata ."si$#&i. Apply systematic analysis on data.ii. !dentify data structures and related operations.iii. Establish data dictionary.iv. 9se information hiding in the design of data structure.

8/13/2019 2 marks .doc


v. Apply a library of useful data structures and operations.9;& Na/" th" 'o//o#*6 s". a!'hit"'t!a* st6*"s&i. %ata centered architecture.ii. %ata flow architecture.iii. #all and return architecture.

iv. Bb)ect7oriented architecture.v. ;ayered architecture.9& What is T!a#sfo!/ /a,,i#$% he transform mapping is a set of design steps applied on the %-% inorder to map the transformed flow characteristics into specificarchitectural style.9& What is a R"a* ti/" s6st"/%+eal time system is a software system in which the correctfunctionalitiesof the system are dependent upon results produced by the systemand the time at

which these results are produced.9& What is SCM%Software #onfiguration Management is a set of activities carried outforidentifying, organiing and controlling changes throughout thelifecycle of computer software.;0& What is SCI%Software #onfiguration !tem is information that is carried as part ofthesoftware engineering process.

;1& +"fi#" softa!" t"sti#$%Software testing is a critical element of software 'uality assuranceandrepresents the ultimate review of specification, design, and coding.;2& What a!" th" o>"'ti"s of t"sti#$%i. esting is a process of e3ecuting a program with the intend offinding anerror.Cii. A good test case is one that has high probability of finding anundiscovered error.

iii. A successful test is one that uncovers as an7yet undiscovered error.&0. What a!" th" t"sti#$ ,!i#'i,*"s th" softa!" "#$i#""! /sta,,*6 hi*","!fo!/i#$ th" softa!" t"sti#$%i. All tests should be traceable to customer re'uirements.ii. ests should be planned long before testing begins.iii. he pareto principle can be applied to software testing7<D of allerrors uncovered during testing will li*ely be traceable to <D of

8/13/2019 2 marks .doc


all program modules.iv. esting should begin in the small5 and progress toward testing inthe large5.v. E3haustive testing is not possible.vi. o be most effective, an independent third party should conduct

testing.;3& What a!" th" to *""*s of t"sti#$%i& Co/,o#"#t t"sti#$!ndividual components are tested. ests are derived fromdeveloper s e3perience.ii& S6st"/ T"sti#$ he group of components are integrated to create a systemor sub7system is done.hese tests are based on the systemspecification.;8& What a!" th" a!ios t"sti#$ a'tiiti"s%i. est planning

ii. est case designiii. est e3ecutioniv. %ata collectionv. Effective evaluation;9& W!it" sho!t #ot" o# *a' o? t"sti#$& he blac* bo3 testing is also called as behavioral testing. his methodfully focus on the functional re'uirements of the software. ests arederived thatfully e3ercise all functional re'uirements.;;& What is "=ia*"#'" ,a!titio#i#$%E'uivalence partitioning is a blac* bo3 techni'ue that divides the

inputdomain into classes of data. -rom this data test cases can be derived.E'uivalenceclass represents a set of valid or invalid states for input conditions.;& What is a o#.a!6 a*" a#a*6sis%A boundary value analysis is a testing techni'ue in which theelements atthe edge of the domain are selected and tested. !t is a test casedesign techni'uethat complements e'uivalence partitioning techni'ue. $ere instead offocusing on

input conditions only, the test cases are derived from the outputdomain.;& What a!" th" !"aso#s "hi#. to ,"!fo!/ hit" o?t"sti#$% here are three main reasons behind performing the white bo3testing.1. 8rogrammers may have some incorrect assumptions whiledesigning or implementing some functions.%ue to this there are

8/13/2019 2 marks .doc


1<chances of having logical errors in the program.o detect andcorrect such logical errors procedural details need to be e3amined.. #ertain assumptions on flow of control and data may leadprogrammer to ma*e design errors.o uncover the errors on logical

path,white bo3 testing is must.0. here may be certain typographical errors that remain undetectedeven after synta3 and type chec*ing mechanisms.Such errors can beuncovered during white bo3 testing.;& What is '6'*o/ati' 'o/,*"?it6%#yclomatic comple3ity is a software metric that gives the 'uantitativemeasure of logical comple3ity of the program. he #yclomatic comple3ity defines the number of independent pathsinthe basis set of the program that provides the upper bound for thenumber of tests

that must be conducted to ensure that all the statements have beene3ecuted atleast once.0& @o to 'o/,t" th" '6'*o/ati' 'o/,*"?it6% he cyclomatic comple3ity can be computed by any one of thefollowingways.1. he numbers of regions of the flow graph correspond tothe cyclomatic comple3ity.. #yclomatic comple3ity,(FGH,for the flow graph,G,isdefined asI

(FGHJE76K,E 77 number of flow graph edges,6 77 number of flow graph nodes0. (FGHJ8K1here 8 is the number of predicate nodes contained in theflow graph.1& +isti#$ish "t""# "!ifi'atio# a#. a*i.atio#&(erification refers to the set of activities that ensure that softwarecorrectly implements a specific function. (alidation refers to adifferent set of activities that ensure that the software that has beenbuilt is traceable to the customer re'uirements.

According to 2oehm, (erificationI5 Are we building the product right:5(alidationI5 Are we building the right product:52& What a!" th" a!ios t"sti#$ st!at"$i"s fo! 'o#"#tio#a*softa!"%i. 9nit testingii. !ntegration testing.iii. (alidation testing.iv. System testing.

8/13/2019 2 marks .doc


3& W!it" aot .!i"!s a#. sts&%rivers and stub software need to be developed to test incompatiblesoftware.

he .!i"!5 is a program that accepts the test data and prints the

relevant results. he st5 is a subprogram that uses the moduleinterfaces andperforms the minimal data manipulation if re'uired.8& What a!" th" a,,!oa'h"s of i#t"$!atio# t"sti#$% he integration testing can be carried out using two approaches.1. he non7incremental testing.. !ncremental testing.9& What a!" th" a.a#ta$"s a#. .isa.a#ta$"s of i$-a#$%A.a#ta$"s7 his approach is simple.+isa.a#ta$"s7 !t is hard to debug.!t is not easy to isolate errorswhile testing. !n this approach it is not easy to validate test results.

After performing testing, it is impossible to form an integrated system.;& What a!" th" "#"fits of s/o" t"sti#$%!ntegration ris* is minimied. he 'uality of the end7product isimproved. Error diagnosis and correction are simplified. Assessment ofprogram is easy.& What a!" th" 'o#.itio#s "?ists aft"! ,"!fo!/i#$ a*i.atio#t"sti#$%After performing the validation testing there e3ists two conditions. he function or performance characteristics are according to thespecifications and are accepted. he re'uirement specifications arederived and the deficiency list is created. he deficiencies then can be

resolved by establishing the proper communication with the customer.>. +isti#$ish "t""# a*,ha a#. "ta t"sti#$.Alpha and beta testing are the types of acceptance testing. A*,hat"stI he alpha testing is attesting in which the version of completesoftware is tested by the customer under the supervision ofdeveloper. his testing is performed at developer s site. "ta t"stI he beta testing is a testing in which the version of thesoftware is tested by the customer without the developer beingpresent. his testing is performed at customer s site.& What a!" th" a!ios t6,"s of s6st"/ t"sti#$%1. R"'o"!6 t"sti#$ @ is intended to chec* the system s ability to

recoverfrom failures.. S"'!it6 t"sti#$ 4 verifies that system protection mechanismpreventimproper penetration or data alteration.0. St!"ss t"sti#$ 4 %etermines brea*point of a system to establishma3imum service level.4& 5"!fo!/a#'" t"sti#$ 4 evaluates the run time performance of the

8/13/2019 2 marks .doc


software, especially real7time software.0& +"fi#" ."$$i#$&%ebugging is defined as the process of removal of defect. !t occurs asaconse'uence of successful testing.

1& What a!" th" 'o//o# a,,!oa'h"s i# ."$$i#$%!t" fo!'" /"tho.7 he memory dumps and run7time trac*sare e3amined and program with write statements is loaded toobtain clues to error causes. a' t!a'i#$ /"tho.7 he sourcecode is e3amined byloo*ing bac*wards from symptom to potential causes of errors.Cas""*i/i#atio# /"tho.7 his method uses binarypartitioning to reducethe number of locations where errors can e3ists.2& W!it" aot th" t6,"s of ,!o>"'t ,*a#&Ba*it6 ,*a# 4 his plan describes the 'uality procedures andstandards that will be used in a pro)ect. <a*i.atio# ,*a# 4 his plan

describes the approach, resources andschedule re'uired for system validation. Co#fi$!atio#/a#a$"/"#t ,*a# 4 his plan focuses on the configurationmanagement procedures and structures to be used. Mai#t"#a#'",*a# 4 he purpose of maintenance plan is to predictthe maintenance re'uirements of the system, maintenance cost andefforts re'uired. Staff .""*o,/"#t ,*a# 4 his plan describes howto develop thes*ills and e3perience of the pro)ect team members.3& +"fi#" /"as!"&Measure is defined as a 'uantitative indication of the e3tent, amount,

dimension, or sie of some attribute of a product or process.8& +"fi#" /"t!i's&Metrics is defined as the degree to which a system component,orprocesspossesses a given attribute.9& What a!" th" t6,"s of /"t!i's%+i!"'t /"t!i's 4 !t refers to immediately measurable attributes.E3ample @ ;ines of code, e3ecution speed. I#.i!"'t /"t!i's 4 !trefers to the aspects that are not immediately'uantifiable or measurable. E3ample @ functionality of a program.;& What a!" th" a.a#ta$"s a#. .isa.a#ta$"s of si:"

/"as!"%A.a#ta$"s7 Artifact of software development which is easilycounted. Many e3isting methods use ;B# as a *ey input. A large bodyof literature and data based on ;B# already e3ists.+isa.a#ta$"s7 Lhis method is dependent upon the programminglanguage. his method is well designed but shorter program may getsuffered. !t does not accommodate non procedural languages. !n earlystage of development it is difficult to estimate ;B#.

8/13/2019 2 marks .doc


& W!it" sho!t #ot" o# th" a!ios "sti/atio# t"'h#i="s&A*$o!ith/i' 'ost /o."*i#$ 4 the cost estimation is based on thesie of the software. E?,"!t >.$"/"#t 4 he e3perts from softwaredevelopment andthe application domain use their e3oerience topredict softwarecosts.

Esti/atio# 6 a#a*o$6 4 he cost of a pro)ect is computed bycomparing the pro)ect to a similar pro)ect in the same applicationdomain and then cost can be computed. 5a!i#so#s *a 4 he costis determined by available resourcesrather than by ob)ective assessment. 5!i'i#$ to i# 4 he pro)ectcosts whatever the customer ready to spend it.& What is COCOMO /o."*%#Bnstructive #Bst MBdel is a cost model, which gives the estimate of number of man7months it will ta*e to develop the software product.& Gi" th" ,!o'".!" of th" +"*,hi /"tho.&1. he co7ordinator presents a specification and estimation form to

each e3pert.. #o7ordinator calls a group meeting in which the e3perts discussestimation issues with the coordinator and each other.0. E3perts fill out forms anonymously.4. #o7ordinator prepares and distributes a summary of the estimates.". he #o7ordinator then calls a group meeting.!n this meeting thee3perts mainly discuss the points where their estimates varywidely.&. he e3perts again fill out forms anonymously.>. Again co7ordinator edits and summaries the forms,repeating steps" and & until the co7ordinator is satisfied with the overallprediction

synthesied from e3perts.0& What is th" ,!,os" of ti/"*i#" 'ha!t% he purpose of the timeline chart is to emphasie the scope of theindividual tas*. $ence set of tas*s are given as input to the timelinechart.1& What is E<A%Earned (alue Analysis is a techni'ue of performing 'uantitativeanalysisof the software pro)ect.!t provides a common value scale for everytas* of software pro)ect.!t acts as a measure for software pro)ect progress.

2& What a!" th" /"t!i's 'o/,t". .!i#$ "!!o! t!a'i#$a'tiit6% LErrors per re'uirement specification page. Errors percomponent7design level Errors per component7code level %+E7re'uirement analysis %+E7architectural analysis %+E7component leveldesign %+E7coding.3& Wh6 softa!" 'ha#$" o''!s%Software change occurs because of the following reasons. 6ewre'uirements emerge when the software is used. Lhe business

8/13/2019 2 marks .doc


environment changes. Errors need to be repaired. 6ew e'uipmentmust be accommodated. he performance or reliability may have tobe improved.8& W!it" aot softa!" 'ha#$" st!at"$i"s& he software change strategies that could be applied separately or

togetherareI Softa!" /ai#t"#a#'" 4 he changes are made in the softwaredue to re'uirements. A!'hit"'t!a* t!a#sfo!/atio# 4 !t is theprocess of changing onearchitecture into another form. Softa!" !"-"#$i#""!i#$ 4 6ewfeatures can be added to e3istingsystem and then the system is reconstructed for better use of it infuture.9& What is softa!" /ai#t"#a#'"%Software maintenance is an activity in which program is modified afterit

has been put into use.;& +"fi#" /ai#t"#a#'"&Maintenance is defined as the process in which changes areimplementedby either modifying the e3isting system s architecture or by addingnewcomponents to the system.& What a!" th" t6,"s of softa!" /ai#t"#a#'"%Co!!"'ti" /ai#t"#a#'" 4 Means the maintenance for correctingthe software faults. A.a,ti" /ai#t"#a#'" 4 Means maintenancefor adapting the

change in environment. 5"!f"'ti" /ai#t"#a#'" 4 Means modifyingor enhancing thesystem to meet the new re'uirements. 5!""#ti" /ai#t"#a#'" 4Means changes made to improve future maintainability.& What is a!'hit"'t!a* "o*tio#%Architectural evolution is the process of changing a system from acentralied architecture to a distributed architecture li*e client server.& @o th" CASE too*s a!" '*assifi".%#ASE tools can be classified bya. 2y function or useb. 2y user typeFe.g. manager,testerH,or

c. 2y stage in software engineering process Fe.g.re'uirements,testH.100& What a!" th" t6,"s of stati' t"sti#$ too*s% here are three types of static testing tools.Co." as". t"sti#$ too*s 4 hese tools ta*e source code as inputand generate test cases.S,"'ia*i:". t"sti#$ too*s 4 9sing this language the detailed testspecification can be written for each test case.R"=i!"/"#t-as". t"sti#$ too*s 4 hese tools help in designing

8/13/2019 2 marks .doc


the test cases as per user re'uirements.

U.*)$V

SOFTWARE PROJECT MANAGEMENT

84"Eplain t*e arious measures of Soft!are"

Program lengt*

Program olume measurePotential olume measure

Program leel

Effort .ime measure

88"&efine Soft!are Cyclomatic CompleityU ,o! it can )e calculatedU

&efinition

#igure Eplanation

#ormulaEample

8?"Eplain *o! Soft!are cost estimation can )e ac*ieed using #unction point modelU#igure Eplanation

8@"Eplain t*e COCOMO model in detail"

.*e )asic form of t*e COCOMO model"Eplanation

8<"Eplain &elp*i met*od of cost estimationEplanation !it* eample

8Q"&ra! t*e Sc*ematic representation of +nalysis actiity !it* t*e Concurrentdeelopment Model"

$one

-nder deelopment

-nderreie!

+!aiting

c*anges-nder

reision

&oneBaselined

CS1353 $SOFTWARE ENGINEERING

8/13/2019 2 marks .doc


SAMPLE !IG QUESTIONS AND %INTS

UNIT 1SOFTWARE PRODUCT AND PROCESS

4"&efine Soft!are process modelU Eplain any one of it !it* a neat diagram.*e strategy t*at encompasses process5 met*ods5 and tools"

Eplanation of any of t*e eig*t process model"

8"Epalin t*e *ierarc*y of Business process Engineering "

Enterprise

Business area +nalysisBusiness System &esign

Construction Engineering

?"Eplain Soft!are Life cycle process&efinition of SLC5SLCM

Predeelopment process

&eelopment process"

@"Eplain Eolutionary process model

Incremental modelWI$%WI$ spiral model

Spiral model

Concurrent deelopment model

<"Eplain t*e different layers of Soft!are EngineeringU

.ools

Met*odsProcess

+ (uality focus

U.*)$IISOFTWARE REQUIREMENTS

Q"Bulid t*e follo!ing systemG6+ $et!or0 )ased course registration system for your -niersity7

&eelop an E'& a contet leel model for t*e a)oe"

Create an E'&

Create a leel 9 &#&"

:"Eplain .ransform Mapping !it* Safe*ome Soft!are&efinition of .ransform Mapping

Eplain Safe*ome applications

Implement .ransform mapping

"Eplain )riefly #unctional Modeling

8/13/2019 2 marks .doc


&efinition of #unctional Modeling

&ata #lo! &iagrams

Etensions for real time systems

"Eplain t*e arious &esign concepts in detail"

+)straction'efinement

Modularity

Control ,ierarc*yStructural Partitioning

&ata structure

Information *iding

49"&iscuss t*e arious p*ases of +nalysis Modeling"

&ata Modeling

#unctional Modeling Information flo!

Be*aioral Modeling.*e &ata dictionary

UNIT$IIIANALYSIS, DESIGN CONCEPTS AND PRINCIPLES

44"&iscuss )riefly Effectie Modular &esign"

#unctional Independence"

Co*esionCoupling

48"Epalin -ser Interface &esign actiities

Interface design modelsInterface design process

&efining Interface o)3ects actions

&esign Issues"

4?"&iscuss in detail Soft!are configuration ManagementU

.*e SCM processVersion Control

C*ange control

SCM standards

4@"Eplain 'eal .ime Systems"

'eal .ime Soft!are design2

System &esign'eal time eecuties

4<"W*at is Soft!are +rc*itectureU Eplain it"&efinition

Eplanation

8/13/2019 2 marks .doc


U.*)$IV

TESTING

4Q"Eplain in detail Blac0 )o testing in detail

Synta drien testing

&ecision ta)le )ased testingCause effects grap* in #unctional testing

4:",o! Boundary test conditions are ac*ieedU#igure

Eplanation

4"Eplain in detail Structural testingUStatement coerage

Branc* coerage

Pat* coerageEample

4"Eplain in detail Soft!are .esting Strategies"-nit testing

Integration testing

Validation testingSystem testing

89"Eplain t*e test coerage criteria )ased on &ata flo! mec*anisms"

Basic )loc0 +ll%use

c%use

p%usedu%pat*

SIDTEEN MARKS(ALL UNITS)

1. E?,*ai# it"!ati" at"!fa** a#. s,i!a* /o."* fo! softa!" *if"'6'*" a#.a!ios a'tiiti"s i# "a'h ,has"&A#s"!7 It"!ati" at"!fa** /o."* he iterative waterfall model is as shown in the following figure.• +e'uirement gathering phase in which all re'uirements areidentified.• he deign phase is responsible for creating architectural view of thesoftware.

8/13/2019 2 marks .doc


• he implementation phase in which the software design istransformedinto coding.• esting is a *ind of phase in which the developed softwarecomponent is

fully tested.• Maintenance is an activity by which the software product can bemaintained.+e'uirements%esign!mplementation estingMaintenance2&S5IRAL MO+EL

• he spiral model is divided into number of frame wor*s. heseframewor*s aredenoted by tas* regions.• 9sually there are si3 tas* regions. !n spiral model pro)ect entry pointa3is isdefined.• he tas* regions areI#ustomer communication8lanning+is* analysis.Engineering.#onstruct and release.

#ustomer evaluation.+!aa's

• !t is based on customer communication.

• !t demands considerable ris* assessment&

2& E?,*ai# aot th" i#'!"/"#ta* /o."*&

• $ave same phases as the waterfall model.

• 8hases areAnalysis.%esign.#ode.

est.• !ncremental model delivers series of releases to customers called asincrements.• he first increment is called as core product. $ere only the documentprocessing facilities are available.• Second increment, more sophisticated document producing andprocessing

8/13/2019 2 marks .doc


facilities are available.• 6e3t increment spelling and grammar chec*ing facilities are given.M"!its

• his model can be adopted when there is less number of peopleinvolved in the pro)ect.

• echnical ris*s can be managed with each increment.• -or a very small time span, at least core product can be deliveredto the customer.RA+ Mo."*

• +apid Application %evelopment Model is the type of incrementalmodel.• Achieves the high speed development using component basedconstruction.5has"s

• 2usiness modeling

• %ata modeling• 8rocess modeling

• Application generation.

• esting and turnover&

3& E?,*ai# i# ."tai* aot th" softa!" ,!o'"ss&

• !t is defined as the structured set of activities that are re'uired todevelopthe software system.F#.a/"#ta* a'tiiti"s

• Specification

• %esign and implementation

• (alidation

• EvolutionCo//o# 5!o'"ss F!a/"o!

• 5!o'"ss f!a/"o! a'tiiti"s#ommunication8lanningModeling#onstruction%eployment.

• Tas S"ts%efines the actual wor* to achieve the software ob)ective.• U/!"**a a'tiiti"sSoftware pro)ect trac*ing and control+is* managementSoftware 'uality assurance-ormal technical reviewsSoftware configuration management

8/13/2019 2 marks .doc


or* product preparation and production+eusability management.Measurement.Ca,ai*it6 Mat!it6 Mo."*(CMM)L""* 17I#itia* 4 -ew processes are defined and individual efforts are

ta*en.L""* 27R","ata*" 4 o trac* cost schedule and functionality basicpro)ect management processes are established.L""* 37+"fi#". 4 he process is standardied, documented andfollowed.L""* 87Ma#a$". 4 2oth the software process and product are'uantitatively understood and controlled using detailed measures.L""* 97O,ti/i:i#$ 4 Establish mechanisms to plan and implementchange.

8& E?,*ai# i# ."tai* aot th" *if" '6'*" ,!o'"ss&

-igI System engineering process• System engineering process follows a waterfall model for theparallel development of different parts of the system.S6st"/ !"=i!"/"#ts ."fi#itio#

• hree types of re'uirementsAbstract functional re'uirements.System properties.9ndesirable #haracteristics.• System ob)ectives

• System re'uirement problem.Th" s6st"/ ."si$# ,!o'"ss5!o'"ss st",s

• 8artition re'uirements

• !dentify sub7systems.

• Assign re'uirements to sub7systems.

• Specify sub7system functionality.

• %efine sub7system interfaces.+e'uirement%efinitiondefinitionSystem

%esignSub7system%esignSystem!ntegrationSystemdecommissioningSystem

8/13/2019 2 marks .doc


evolutionSystem!nstallationS-S6st"/ .""*o,/"#t ,!o'"ss

• After system design it starts.

• !nvolve use of #BS F#ommercial7Bff7he7ShelfH.S6st"/ I#t"$!atio#

• !t is the process of putting hardware, software and people togetherto ma*e asystem.S6st"/ I#sta**atio#Iss"s a!"

• Environmental assumptions may be incorrect.

• here may be human resistance to the introduction of anew system.

• System may have to coe3ist with alternative systems for some

period.• here may arise some physical installation problems Fe.g. cablingproblemH.• Bperator training has to be identified.S6st"/ "o*tio#

• he lifetime of large systems is too long. hey must evolve to meetchangere'uirements.• he evolution may be costly.

• E3isting systems that must be maintained are sometimes called aslegacy systems.

S6st"/ +"'o//issio#i#$• a*ing the system out of service after its useful lifetime is called asSystem%ecommissioning.

9& E?,*ai# th" ,!otot6,i#$ a,,!oa'h"s i# softa!" ,!o'"ss&To a,,!oa'h"si& Eo*tio#a!6 ,!otot6,i#$ 4 !n this approach of systemdevelopment,the initial prototype is prepared and it is then refined through numberof stages to final stage.ii. Th!o-aa6 ,!otot6,i#$ 4 9sing this approach a rough practicalimplementation of the system is produced. he re'uirement problemscanbe identified from this implementation. !t is then discarded. System isthen developed using some different engineering paradigm.Eo*tio#a!6 ,!otot6,i#$

8/13/2019 2 marks .doc


O>"'ti"7

• he principal ob)ective of this model is to deliver the wor*ing systemto theend7user.• E3ample7A! systems.

A.a#ta$"s• -ast delivery of the wor*ing system.

• 9ser is involved while developing the system.

• More useful system can be delivered.

• Specification, design and implementation wor* is co7ordinatedmanner.5!o*"/s

• Management problems

• Maintenance problem

• (erification

<I#'!"/"#ta* +""*o,/"#t

• After designing the overall architecture the system is developed anddelivered in series of increments.Th!o-aa6 ,!otot6,i#$O>"'ti"7

• he principal ob)ective of this model is to validate or to derive thesystemre'uirements.• !t is developed to reduce re'uirement ris*s.A.a#ta$"s

• +e'uirement ris*s are very less.5!o*"/s

• !t can be undocumented.

• #hanges made during the software development proceed maydegradethe system structure.• Sometimes organiational 'uality standard may not be strictlyapplied.

;. E?,*ai# aot !a,i. ,!otot6,i#$ t"'h#i="s&

E?"'ta*" s,"'ifi'atio# *a#$a$"s&• 9sed to animate the system specification.

• !t is e3pressed in a formal, mathematical language to provide asystemprototype.<"!6 hi$h *""* *a#$a$"s.• hese are programming languages which include powerful datamanagement facilities.

8/13/2019 2 marks .doc


• hey simplify program development.A,,*i'atio# $"#"!ato!s a#. fo!th-$"#"!atio# *a#$a$"s.• hese are successful languages because there is a great deal of communality across data processing applications.

& E?,*ai# i# ."tai* aot .ata /o."*i#$&• %ata modeling ma*es use of the E+%.

• #onsists of 0 interrelated information. he data ob)ect.Attributes.+elationships.Ca!.i#a*it6 a#. Mo.a*it6

• #ardinality is the specification of the number of occurrences of oneob)ectthat can be related to the number of occurrences of another ob)ect.• Bne7to7one cardinality.

• Bne7to7many cardinality.

• Many7to7Many cardinality.

• Modality of a relation is < if there is no e3plicit relationship orrelation isoptional.• Modality is 1 if an occurrence of relationship is mandatory.E#tit6R"*atio#shi, +ia$!a/s

• #omponents are%ata Bb)ects.Attributes.

+elationships.(arious type indicators.

& E?,*ai# i# ."tai* aot F#'tio#a* Mo."*i#$&

• his model describes the computations that ta*e place within asystem.• his model is useful when the transformation from the inputs tooutputs iscomple3.• he functional model of a system can be represented by a data -low

%iagramF%-%H.+ata F*o +ia$!a/s+ata F*o G!a,h*" 'ha!t

• A %-% is a graphical representation that depicts the information flowandthe transforms that are applied as the data move from input to output.• ;evel < %-% also called as fundamental system model or conte3tmodel

8/13/2019 2 marks .doc


represents the entire software as a single bubble with input andoutput dataindicated by incoming and outgoing arrows.• ;evel 1 %-% contains " or & bubbles. Each bubbles can be refined at;ayers to depict more details.

E?t"#sio#s to R"a* Ti/" S6st"/s• ard and Meller e3tensions

• $atley and 8irbhai e3tension.

& E?,*ai# i# ."tai* aot St!'t!a* Mo."*i#$&

• Structural model includes a detail refinement of E+%,data flow modelandcontrol flow model.• #reating an E+%.

• E3ampleI Safe $ome Security System.

•%eveloping relationships and cardinality/Modality.• #reating a data flow model using the guidelines.

• #reating a control flow model which describes the structuralconnection of 8rocesses#ontrol flows#ontrol stores.• State automation

• 8rocess activation table.

10& E?,*ai# i# ."tai* th" ."si$# 'o#'",ts&

Ast!a'tio#• -unctional abstraction

• %ata abstraction

• #ontrol abstractionI#fo!/atio# hi.i#$

• Each module in the system hides the internal details of itsprocessing activities and modules communicate only through overdefined interfaces.St!'t!"

• !t permits the decomposition of a large system into smaller, more

manageable units with well defined relationships to the other unitsin a system.• 6etwor* is the most general form of structure.@i"!a!'hi'a* St!'t!"sSt!'t!" Cha!ts

• !t depicts the structure of subroutines in a system, the data passedbetween routines, can be indicated on the arcs connecting routines.Mo.*a!it6

• Modular system consists of well7defined, manageable units with

8/13/2019 2 marks .doc


well defined interfaces among units.Co#'!!"#'6

• !ndependent processes that can be activated simultaneously if multiple processors are available.Co,*i#$ a#. Coh"sio#

• +ata 'o,*i#$ 4 he data coupling is possible by parameterpassing or data interaction.• Co#t!o* 'o,*i#$ 4 he modules share related control data incontrol coupling.• Co//o# 'o,*i#$ 4 he common data or a global data is sharedamong modules.• Co#t"#t 'o,*i#$ @ #ontent coupling occurs when one modulema*es use of data or control information maintained in anothermodule.

11& E?,*ai# th" ."si$# ,!i#'i,*"s&

• he design process should not suffer from tunnel vision.

• he design should be traceable to the analysis model.

• %esign should not reinvent the wheel.

• he design should minimie the intellectual distance between thesoftwareand problem as it e3ists in the real world.• he design should be structured to degrade gently, even whenaberrantdata, events or operating conditions are encountered.• %esign is not coding, coding is not design.

• he design should be assessed for 'uality as it is being created, notafterthe fact.• he design should be reviewed to minimie conceptual FsemanticHerrors.

12& E?,*ai# th" ."si$# st",s of th" t!a#sfo!/ /a,,i#$&

• +eview the fundamental model.

• +eview and refine the %-% for the software.

• %etermine whether the %-% has the transform or transaction

mapping.• !solate the transform center by specifying incoming and outgoingflowboundaries.• 8erform first7level factoring.

• 8erform second7level factoring.0

8/13/2019 2 marks .doc


• +efine the first iteration architecture using design heuristics forimprovedsoftware 'uality.

13& E?,*ai# th" ."si$# st",s i# t!a#sa'tio# /a,,i#$&

• +eview the fundamental model.• +eview and refine the %-% for the software.

• %etermine whether the %-% has the transform or transactionmapping.• !dentify transaction center and the flow characteristics along each oftheaction paths.• -actor and refine the transaction structure and the structure of eachactionpath.•

+efine the first iteration architecture using design heuristics forimprovedsoftware 'uality.

18& E?,*ai# i# ."tai* aot th" !"a* ti/" s6st"/s&

• $ard and soft real time systems.

• +eal time and high performance.

• +eal7ime control.

• +eal time software design8eriodic Stimuli @ Bccur at predictable time intervals.Aperiodic Stimuli @ Bccur regularly

19& E?,*ai# th" t6,"s of softa!" t"sti#$&

• 9nit testing

• System testing

• !ntegration testing

• 9ser7acceptance testing

• End7to7End testing

• +egression testing

• E3ception testing

• %estructive testing

1;& E?,*ai# i# ."tai* aot *a' o? t"sti#$&• 2lac* bo3 or behavioral testing focuses on the functionalre'uirementsof the software.• !t is applied during the last stage of testing.

• Synta3 driven testing is suitable for the specification which aredescribed by a certain grammar.

8/13/2019 2 marks .doc


• %ecision table based testing is implemented when the originalsoftwarere'uirement have been formulated in the format of if7then5statements.• ;i'uid level control is the study of a simple control problem which is

designed to chec* the li'uid level. !t has sensors.• #ause effect graphs in functional testing.

1& E?,*ai# aot th" softa!" t"sti#$ st!at"$i"s&

• A strategic approach to software testing.

• (erification and (alidation.(erification refers to the set of activities that ensure that softwarecorrectly implements a specific function.(alidation refers to a different set of activities that ensure that thesoftware that has been built is traceable to the customerre'uirements.According to 2oehm,(erificationI5 Are we building the product right:5 L(alidationI5 Are we building the right product:5• Brganiation for software testing

• A software testing strategy.

• #riteria for completion of testing.

1& E?,*ai# i# ."tai* aot I#t"$!atio# t"sti#$&

• !t is a systematic techni'ue for constructing the program structure.

• I#'!"/"#ta* i#t"$!atio# 4 he program is constructed and tested

insmall increments.To,-.o# i#t"$!atio#

• !t is an incremental approach.

• Modules are integrated by moving downward through the controlhierarchy beginning with the main control moduleFmain programH.• Subordinate modules are incorporated by depth7first or breadth7firstmanner.otto/-, i#t"$!atio#

• his testing begins construction and testing with the components at

thelowest levels in the program structure.R"$!"ssio# t"sti#$

• !t is the re7e3ecution of some subset of tests that have already beenconducted to ensure the changes that have not been propagatedunintended side effects.S/o" t"sti#$

• !t minimies the integration ris*.

8/13/2019 2 marks .doc


• Error diagnosis and correction are simplified.

1& E?,*ai# i# ."tai* aot s6st"/ t"sti#$&

• System testing

• Stress testing

• Security testing.• 8erformance testing

20& E?,*ai# i# ."tai* aot SCM&

• Software #onfiguration Management is an umbrella activity that isapplied throughout the software process.SCM A'tiiti"s

• !dentify change.

• #ontrol change.

• Ensure the change is properly implemented.

• +eport change to others.N"". fo! SCM

• hen you build computer software change happens, you need tocontrol it effectively.SCI • Software #onfiguration !tem is information that is carried as partof thesoftware engineering process.

21& E?,*ai# aot softa!" 'ost "sti/atio#&

• Ma)or factors areI8rogramme ability.8roduct #omple3ity.8roduct sie.Available time.+e'uired reliability.

22& E?,*ai# i# ."tai* aot COCOMO /o."*&

• #onstructive #ost Model.

• Software cost estimation gives the estimation of how much months aman ta*e to develop a software product.• Application #omposition Model.

• Early design stage model• 8ost7architecture stage model.

• #B#BMB !! application composition uses ob)ect points.

• 6B8JFob)ect pointHN1<<7DreuseH/1<<O6B876ew Bb)ect 8oint.• 8roductivity +ate, 8+B%J6B8/person7Month.

8/13/2019 2 marks .doc


8/13/2019 2 marks .doc


• System Software tools.

• uality Assurance tools.

• %atabase management tools.

• S#M tools.

• Analysis and design tools.

• 8B/S!M tools.

• !nterface design and development tools.

• 8rototyping tools.

• 8rogramming tools.

• eb development tools.

• !ntegration and testing tools.

• Static analysis tools.

• %ynamic analysis tools.

• est management tools.

•#lient/server tools.• +e7engineering tools.

2 marks .doc

Documents