華東交通大學外教Lecture-4-Software-Process-models-Software-process-activities-Coping-with-change-Rational-Unified_第1頁
華東交通大學外教Lecture-4-Software-Process-models-Software-process-activities-Coping-with-change-Rational-Unified_第2頁
華東交通大學外教Lecture-4-Software-Process-models-Software-process-activities-Coping-with-change-Rational-Unified_第3頁
華東交通大學外教Lecture-4-Software-Process-models-Software-process-activities-Coping-with-change-Rational-Unified_第4頁
華東交通大學外教Lecture-4-Software-Process-models-Software-process-activities-Coping-with-change-Rational-Unified_第5頁
已閱讀5頁,還剩44頁未讀, 繼續免費閱讀

下載本文檔

版權說明:本文檔由用戶提供并上傳,收益歸屬內容提供方,若內容存在侵權,請進行舉報或認領

文檔簡介

SoftwareEngineering

UsmanFarooq

sf_usman@

Goal(s)ofthislecture

TounderstandsoftwareprocessmodelsTounderstandsoftwareprocessactivitiesTounderstandhowtocopewithchangesTounderstandrationalunifiedprocess2

SoftwareProcessesCoherentsetofactivitiesforspecifying,designing,implementingandtestingsoftwaresystems.Insimplewords,asetofactivitiesthatleadstothedevelopmentorproductionofasoftwareproduct.Whenyouworktobuildaproductorsystem,it’simportanttogothroughaseriesofpredictablesteps(roadmap)thathelpsyoucreateatimely,highqualityresult.Theroadmapthatyoufollowiscalleda“softwareprocess.”

SoftwareProcessesTherearemanydifferentkindsofsoftwareprocesses,butallmustincludefouractivitiesthatareimportanttosoftwareengineering:-SoftwareSpecificationSoftwareDesignandImplementationSoftwareValidationSoftwareEvolution4

SoftwareProcessesThereisnoidealprocessandmostorganizationshavedevelopedtheirownsoftwaredevelopmentprocesses.Theselectionofsoftwareprocesseshighlydependsuponthetypeofthesystembeingdeveloped.Forexample:-SafetycriticalsystemrequiresaverystructureddevelopmentprocessThesystemwithrapidlychangingrequirements,alessformal,flexibleprocessisuseful.5

SoftwareProcessesCategorizationTherearetwocategoriesofsoftwareprocesses:-PlanDrivenProcessesAgileProcesses6

GenericSoftwareProcessModelsWaterfallModelSeparateanddistinctphasesofspecificationanddevelopmentIncrementalDevelopmentSpecificationanddevelopmentareinterleavedThesystemisdevelopedasaseriesofversions(increments),witheachversionaddingfunctionalitytothepreviousversion.Reuse-OrientedSoftwareEngineeringThesystemisconstructedorassembledfromexistingcomponents.7

WaterfallModel8

WaterfallModelStagesRequirementsanalysisanddefinitionSystemandsoftwaredesignImplementationandunittestingIntegrationandsystemtestingOperationandmaintenance9

DrawbacksofWaterfallModelInflexiblepartitioningoftheprojectintodistinctstages.ThismakesitdifficulttorespondtochangingcustomerrequirementsTherefore,thismodelisonlysuitablewhenprojectsrequirementsarequitecertaini.e.:-Customersrequirementsarewellknowninadvance.10

IncrementalDevelopment11

IncrementalDevelopmentExploratoryDevelopmentObjectiveistoworkwithcustomersandtoevolveafinalsystemfromaninitialoutlinespecification.Shouldstartwithwell-understoodrequirementsThrow-awayprototypingObjectiveistounderstandthesystemrequirements.Shouldstartwithpoorlyunderstoodrequirements.12

BenefitsofIncrementalDevelopmentCostrelatedwithaccommodatingcustomerrequirementsisminimized.EarlycustomerfeedbackCustomerfeedbackhelpsinidentifyingtheproblemsearlier.Morerapiddeliveryanddeploymentofusefulsoftwaretothecustomerispossible,evenifallthefunctionalityhasnotbeenincluded.13

ProblemswithIncrementalDevelopmentLackofprocessvisibilityasprojectmanagersneedsregulardeliverablestomeasureprogress.Ifsystemisdevelopedquickly,thenitisnotcosteffectivetoproducedocumentsthatreflecteveryversionofthesystem.Systemsareoftenpoorlystructuredbecauseregularchangesaimstocorruptitsstructure.Specialskills(e.g.inlanguagesforrapidprototyping)mayberequired.14

ApplicabilityofIncrementalDevelopmentForsmallormedium-sizeinteractivesystems.Forpartsofthelargesystemse.g.userinterfaceForshortlifetimesystems.Notsuitableforlargeproject.Why?Becauseinlargeprojectstherearedifferentteamsthatdevelopdifferentpartsofthesystem.Largesizeprojectneedsastableframeworkorarchitectureandtheresponsibilitiesofthedifferentteamsworkingonpartsofthesystemneedtobeclearlydefinedwithrespecttothatarchitecture.Soithastobeplannedinadvanceratherthandevelopincrementally.15

Reuse-OrientedSoftwareEngineering16

Reuse-OrientedSoftwareEngineeringBasedonthesystematicreusewheresystemsareintegratedfromexistingcomponentsorCOTS(Commercial-off-the-shelf)systems.ProcessstagesComponentanalysisRequirementsmodificationSystemdesignwithreuseDevelopmentandintegrationThisapproachisbecomingmoreimportantbutstilllimitedexperiencewithit.17

ReuseOrientedSoftwareEngineeringBenefits:Reuseorientedsoftwareengineeringhelpsinsavingdevelopmenttime,cost,budgetandrisksassociatedwithsoftwareprojects.Drawbacks:Requirementscompromisesareinevitableandthismayleadtoasystemthatdoesnotsatisfythecustomerneedsandexpectations.Somecontroloverthesystemevolutionislostasnewversionsofthereusablecomponentsarenotunderthecontroloforganizationusingthem.18

SoftwareProcessActivities1.SoftwareSpecificationorRequirementsEngineeringTheprocessofestablishingwhatservicesarerequiredandtheconstraintsonthesystem’soperationanddevelopment.Importantandcriticalphaseofsoftwaredevelopment.Thisstageifnotdoneproperlyorefficientlywillcreateproblemsinthelaterstagesofsoftwaredevelopmentsuchasdesign,implementationetc.19

StagesofRequirementsEngineeringProcessTherearefourmainstagesofrequirementsengineeringprocess:-FeasibilityStudyRequirementselicitationandanalysisRequirementsspecificationRequirementsvalidation20

StagesofRequirementsEngineeringProcess.21

SoftwareProcessActivities2.SoftwareDesignandImplementationTheprocessofconvertingthesystemspecificationintoanexecutablesystem.SoftwareDesignDesignasoftwarestructurethatrealizesthespecification.ImplementationTranslatethisstructureintoanexecutableprogram.Theactivitiesofdesignandimplementationarecloselyrelatedandmaybeinter-leaved.22

DesignProcessActivitiesArchitecturalDesignAbstractspecificationInterfaceDesignComponentDesignDataStructureDesignAlgorithmDesign23

TheSoftwareDesignProcess.24

DesignMethodsSystematicapproachestodevelopingasoftwaredesign.Thedesignisusuallydocumentedasasetofgraphicalmodels.PossiblemodelsData-flowmodelEntity-relation-attributemodelStructuralmodelObjectmodels.25

ProgrammingandDebuggingTranslatingadesignintoaprogramandremovingerrorsfromthatprogram.Programmingisapersonalactivity-thereisnogenericprogrammingprocess.Programmerscarryoutsomeprogramtestingtodiscoverfaultsintheprogramandremovethesefaultsinthedebuggingprocess.26

TheDebuggingProcess.27

SoftwareProcessActivities4.SoftwareValidationVerificationandvalidationisaimedtoshowthatasystemconformstoitsspecificationandmeetstherequirementsofthesystemcustomer.Includescheckingandreviewprocessesandsystemtesting.Systemtestinginvolvesexecutingthesystemwithtestcasesthatarederivedfromthespecificationnn

oftherealdatatobeprocessedbythesystem.28

TheTestingProcess.29

TheTestingStagesUnitTestingIndividualcomponentsaretestedModuleTestingRelatedcollectionsofdependentcomponentsaretested.Sub-systemTestingModulesareintegratedintosub-systemsandtested.ThefocushereshouldbeoninterfacetestingSystemTestingTestingofthesystemasawhole.Testingofemergentproperties.AcceptanceTestingTestingwithcustomerdatatocheckthatitisacceptable30

TheTestingPhases.31

SoftwareProcessActivities5.SoftwareEvolutionSoftwareisinherentlyflexibleandcanchange.Asrequirementschangethroughchangingbusinesscircumstances,thesoftwarethatsupportsthebusinessmustalsoevolveandchange.Althoughtherehasbeenademarcationbetweendevelopmentandevolution(maintenance)thisisincreasinglyirrelevantasfewerandfewersystemsarecompletelynew.32

SoftwareEvolution33

CopingwithChangeTwoApproachestoreducecostofrework:-ChangeAvoidanceChangeToleranceChangeAvoidanceWherethesoftwareprocessconsistsactivitiesthatcananticipatedpossiblechangesbeforesignificantreworkisrequired.Forexample,aprototypesystemmaybedevelopedtoshowsomeimportantfunctionsorfeaturesofthesystemtocustomers.Theycanexperimentwiththeprototypeandrefinetheirrequirementsbeforecommittingtohighsoftwareproductioncosts.34

CopingwithChangeChangeToleranceWheretheprocessisdesignedsothatchangescanbeaccommodatedatrelativelylowcost.Thisnormallyincludessomesortofincrementaldevelopment.Proposedchangesmaybeimplementedinincrementsthathavenotyetbeendeveloped.Ifthisisimpossible,thenonlyasingleincrementmayhavetobealteredtoincorporatethechange.35

CopingwithChangeCopingwithchangingsystemrequirementsSystemPrototypingIncrementalDelivery36

SoftwarePrototypingRapidsoftwaredevelopmenttovalidaterequirements.Inthepast,thedevelopedsystemwasnormallythoughtofasinferiorinsomewaytotherequiredsystemsofurtherdevelopmentwasrequired.Now,theboundarybetweenprototypingandnormalsystemdevelopmentisblurredandmanysystemsaredevelopedusingandevolutionaryapproach.37

SoftwarePrototypingUsesofsoftware/systemprototypingTheprincipaluseistohelpcustomersanddevelopersunderstandtherequirementsforsystem.Requirementelicitation:UserscanexperimentwithaprototypetoseehowthesystemsupportstheirworkRequirementvalidation:Theprototypecanrevealerrorsandomissionsintherequirements.Prototypingcanbeconsideredasariskreductionactivitywhichreducesrequirementsrisks.38

SoftwarePrototypingBenefitsMisunderstandingsbetweensoftwareusersanddevelopersareexposed.Missingservicesmaybedetectedandconfusingservicesmaybeidentified.Aworkingsystemisavailableearlyintheprocess.Theprototypemayserveasabasisforderivingasystemspecification.39

SoftwarePrototypingProcess40

IncrementalDeliveryRatherthandeliverthesystemasasingledelivery,thedevelopmentanddeliveryisbrokendownintoincrementswitheachincrementdeliveringpartoftherequiredfunctionality.Userrequirementsareprioritizedandthehighestpriorityrequirementsareincludedinearlyincrements.Oncethedevelopmentofanincrementisstarted,therequirementsarefrozenthoughrequirementsforlaterincrementscancontinuetoevolve.41

IncrementalDelivery.42

SpiralModelProcessisrepresentedasaspiralratherthanasasequenceofactivitieswithbacktracking.Eachloopinthespiralrepresentsaphaseintheprocess.Nofi

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯系上傳者。文件的所有權益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網頁內容里面會有圖紙預覽,若沒有圖紙預覽就沒有圖紙。
  • 4. 未經權益所有人同意不得將文件中的內容挪作商業或盈利用途。
  • 5. 人人文庫網僅提供信息存儲空間,僅對用戶上傳內容的表現方式做保護處理,對用戶上傳分享的文檔內容本身不做任何修改或編輯,并不能對任何下載內容負責。
  • 6. 下載文件中如有侵權或不適當內容,請與我們聯系,我們立即糾正。
  • 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論