SOLUTIONSModule:SoftwareEngineeringModuleCodeEBU5304PaperATimeallowed2hoursFilenameSolutions_1213_EBU5304_ARubricANSWERALLTHREEQUESTIONS.ExaminersDrPaulaFonsecaDrMatthewHuntbachEBU5304(2013)PaperA–SOLUTIONSPage2Question1a)Thequestionsconcerntheconceptsofcohesionandcoupling:i)Brieflydescribetheconceptofcohesioninthecontextofsoftwaredevelopmentandindicatehowitrelatestocoupling.ii)ThestatementinFigure1describesamoduleinahypotheticalsoftwaresystem.Explainwhythemoduleislikelytohavealowdegreeofcohesion.Figure1Donotwriteinthiscolumni)Cohesionreferstothenumberofdependencieswithinasubsystem[1mark].Itprovidesameasureoftheleveloffunctionalintegrationwithinamodule[1mark].Ideally,asubsystemshouldhavehighcohesion[1mark].Thereisatrade-offbetweencouplingandcohesion[1mark]:1.Ifcohesionisincreased,thismeansdecomposingthesystemintosmallersubsystems,whichinturndecreasescoupling[1mark].2.Ifcouplingisdecreased,thismeansminimisingthenumberofsubsystems,whichinturnincreasescohesion[1mark].ii)Themodule“ProcessPurchase”canbeexpectedtohaverelativelylowcohesion,becauseitinvolvesverydifferentfunctionalities[1mark];printingareceiptforusebythecustomerislogicallyquitedifferentfromupdatingadatalog[1mark].8marksModule“ProcessPurchase”removesthepurchasedproductfromtheinventory,printsareceiptforthecustomerandupdatesthelog.EBU5304(2013)PaperA–SOLUTIONSPage3b)ThequestionsbelowrefertothesystemdescriptioninFigure2.Figure2i)ThefirststepthatthedevelopmentteamdecidestoundertakeistocreatearequirementsdocumenttodescribethesysteminFigure2.Fromthelistbelow,selectthosethatarevalidfunctionalrequirements;anystatementsfoundtobeinvalidfunctionalrequirementsmustbejustified.Youmustalsoidentifyanynon-functionalrequirements.1.Oncethepaymentprocessiscomplete,thesystemshouldrespondinthefollowingway:a)iftheuserhaspaidthecashierdirectly,orhaspaidatthepumpbutdoesnotdesireareceipt,thenreturntotheinitialstate;b)otherwise,printareceipt.2.Arecordshouldbekeptforeachcashier.Eachrecordshouldstorethelastname,firstname,andempl...
