Solution Manual For Software Engineering: Theory And Practice, 4th Edition

Solution Manual For Software Engineering: Theory And Practice, 4th Edition helps you understand textbook content with detailed solutions and explanations for each problem.

Owen Collins
Contributor
4.7
47
6 months ago
Preview (16 of 54 Pages)
100%
Purchase to unlock

Page 1

Solution Manual For Software Engineering: Theory And Practice, 4th Edition - Page 1 preview image

Loading page ...

..Chapter1:Whysoftwareengineering?1.Thistypeofsituationcouldbeindicativeofacrisisinthattheinadequaciesofsoftwarecontributedtothetragiclossoflife.Thefactthatthepilotreliedcompletelyonthesoftwaretoguidetheplaneturnedauserinterfaceerrorintoasevereaccident.Ingeneral,ofcourse,aviationisbetteroffbecauseofsoftwareengineeringbecausethehighreliabilityofaviationsoftwarehasmadeflyingsaferandmorecost-effective.Thesituationthatcausedtheaccidentisreallyauserinterfaceproblem.Duringdevelopment,moreuserfeedbackcouldhavebeendesignedintothesoftware(sothatthepilotmighthavebeennotifiedthathehadtypedinthecodeforBogota,notCali)andmoreusabilitytestingcouldhavebeendone(sothatthemisunderstandingmighthavesurfacedbeforethesoftwarewasinstalledintheairplane).Theotherissueisthatofsystemboundary.Althoughtheaeronauticalchartsusedbypilotsareoutsidetheboundaryofthecomputersystem,thedevelopersneedtohaveknowledgeofthemandthecodesandabbreviationstheycontain.2.Oneexampleistheprocessingandsynthesisofsensordata.Iflotsofreal-timesensordataareflowingintothesoftwaresystem,thehardpartisgettingthetimingrightsothatanaccuratepictureoftheoverallsystemisobtained.Forinstance,ifthesoftwareiscontrollingtheshapeofthewingofaplane,basedonreal-timesensordataabouttheairspeed,pressure,temperature,etc.,decisionsmustbebasedonup-to-dateinformationfromthesensors,evenwhenflyingthroughrapidlychangingconditions(likeastorm).Theactualpollingofthesensorsiseasy;therelationshipsarehard.Therelationshipsaremorecomplicatedstillwhendealingwithasynchronouschangestothewingshape.3.Errorsaremisunderstandingthatresideinthedeveloper’sthoughtprocesses.Whenthatmisunderstandingleadsthedevelopertowritesomethinginadevelopmentartifact(specification,design,code,testdata,etc.)thatisnotcorrect,thatincorrectinformationiscalledafault.Whenthefaultcausesthesoftwaretobehaveinanincorrectmannerorproduceincorrectresults,thatbehavioriscalledafailure.Anexampleofanerroriswhenadevelopermistakenlybelievesthatthediameterofacircleisthreetimesitsradius.Thiserrorcouldleadtoafaultintherequirementsdocumentifthisdeveloperwritesarequirementthatsaysthatthesystem,whengivenaradiusasinputandacommandtocomputethediameter,shouldreturnthreetimestheradius.Or,theerrorcouldleadtoafaultinthedesignifthedesignforthemoduleforconvertingradiiintodiametersincludesthefaultyformula.Or,iftheformularelatingradiusanddiameterisnotspecifiedineithertherequirementsorthedesign,afaultcouldstillbeintroducedinthecodeifthedeveloperencodeshis/hererroneousunderstandingoftheformula.Ifthefaultisintroducedintherequirementsorthedesignandpropagatestothecode,thenitmaybecomeafailureifthatpartofthecodeisexercisedandconsequentlyproducesawrongoutput.However,ifthetestdatacontainedafaultthatcausedthecodeforcomputingthediameternottobeexecutedduringtest,thenthiswouldallowafailuretooccurduringoperationaluse,whenthatcodeisexercised.4.Acountoffaultsis2misleadingmeasureofproductqualitybecausethereusuallyisnotaone-to-onecorrespondencebetweenfaultsandfailures.Ifmanyfaultsarelocatedincodethatisneverorrarelyexecuted,thentheyareunlikelytoresultinmanyfailures,whichisusuallyamorerelevantmeasureofquality.Ontheotherhand,ifjustonefaultislocatedincodethatisexercisedheavilyinregularuse,itcouldresultinnumerousfailures,andthuslow-qualitysoftware.Furthermore,neitheracountoffaultsnoracountoffailuresgivesanindicationoftheseverityoftheproblems.5.InonesmalldivisionofNASA,agroupofsoftwaredeveloperswhodevelopedsoftwaretosupportsatellitemissionsdecidedtobuildanobject-orientedlibraryofsoftwarecomponents.Itwasestimatedthatsuchalibrarywoulddrasticallyreducedevelopmenttimeinthisdivision,andwouldevenallowthephysicistsandflightdynamicsanalystsinthedivisiontoputtogethertheirownapplicationsratherthanrelyingonsoftwaredeveloperstowritetheprogramstheyneededformissionsupport.Thelibrarywasbuiltusinganarchitecturebasedonmanyyearsofexperienceinthisdomain,usingsoundsoftwareengineeringprinciples,andwastestedextensively.Thecomponentsinthelibrarywereofveryhightechnicalquality.However,thelibrarywasoflimitedvaluetoitsintendedcustomers,thephysicistsandanalysts,becausetherewerenotoolsordocumentationthatfacilitateditsuse.Usersofthelibraryhadtohaveadeepunderstandingnotonlyoftheapplicationdomain,butalsoofobjectorientationandsoftwaredevelopment,aswellasthestructureofthelibraryitself.Thus,thelibrarywasnotthesuccessitwashopedtobe.1

Page 2

Page 3

Page 4

Page 5

Page 6

Page 7

Page 8

Page 9

Page 10

Page 11

Page 12

Page 13

Page 14

Page 15

Page 16

Preview Mode

This document has 54 pages. Sign in to access the full document!

Study Now!

XY-Copilot AI
Unlimited Access
Secure Payment
Instant Access
24/7 Support
Document Chat

Related Documents

View all