毕业设计（论文）文献翻译：软件开发概念和设计方法

毕业设计（论文）--文献翻译原文题目SoftwareDevelopmentConceptsandDesignMethodologies译文题目软件开发概念和设计方法专业信息与计算科学姓名学号指导教师

SoftwareDevelopmentConceptsandDesignMethodologiesDuringthe1960s,mainframesandhigherlevelprogramminglanguageswereappliedtomanyproblemsincludinghumanresourcesystems,reservationsystems,andmanufacturingsystems.Computersandsoftwarewereseenasthecureallformanybusinessissuesweresometimesappliedblindly.Systemssometimesfailedtosolvetheproblemforwhichtheyweredesignedformanyreasonsincluding:•Inabilitytosufficientlyunderstandcomplexproblems.•Notsufficientlytakingintoaccountend-userneeds,theorganizationalenvironment,andperformancetradeoffs.•Inabilitytoaccuratelyestimatedevelopmenttimeandoperationalcosts•LackofframeworkforconsistentandregularcustomercommunicationsAtthistime,theconceptofstructuredprogramming,top-downdesign,stepwiserefinement，andmodularityemerged.Structuredprogrammingisstillthemostdominantapproachtosoftwareengineeringandisstillevolving.Thesefailuresledtotheconceptof"softwareengineering"basedupontheideathatanengineering-likedisciplinecouldbeappliedtosoftwaredesignanddevelopment.Softwaredesignisaprocesswherethesoftwaredesignerappliestechniquesandprinciplestoproduceaconceptualmodelthatdescribesanddefinesasolutiontoaproblem.Inthebeginning,thisdesignprocesshasnotbeenwellstructuredandthemodeldoesnotalwaysaccuratelyrepresenttheproblemofsoftwaredevelopment.However,designmethodologieshavebeenevolvingtoaccommodatechangesintechnologycoupledwithourincreasedunderstandingofdevelopmentprocesses.Whereasearlydesignmethodsaddressedspecificaspectsofthedevelopmentprocess,currentmethodsattempttoaddresstheentirescopeofsoftwaredevelopment.Softwaredesignmethodsareoftenclassifiedinreferencetotheperiodinwhichtheywereintroducedandtheproblemsatthattime.Drivenbycodingandtestingproblems,toolsandmethodsweredeveloped.Earlymethodsfocusedonmodularityandtop-downdevelopment,andinformationhidingthroughabstraction.Thisledtothedevelopmentofstructuredlanguages,structuredanalysis,anddataflowanalysis.Inthelastdecadeorso,theexpenseinvolvedinautomationhasshiftedfromhardwaretopeople.Therefore,thesoftwareengineeringcommunityhasbeenfocusedonobjectoriented(O-O)designandtheconceptofre-usablecodeinordertoreducethehumancostcomponent.InefficientdesignsanddevelopmentmethodologieshavebeenaddressedwithComputerAidedSoftwareEngineering(CASE)tools,andfourthgenerationdesignlanguages.Thishasbeendoneinanattemptreplacethetraditionalwaterfalllifecycleprocessmodelunderwhichmostexistingsoftwarehasbeendeveloped.SoftwareDesignFundamentalsSoftwaredesignmethodsallaimtoprovidethesoftwaredesignerwithasystemblueprint.Thisblueprintusuallyhasthreeaspects:data,architectural,andprocedural.•Datadesignreferstothedata'sorganization,relationships,accessandprocessingmethods.•Architecturaldesigndefinesthecomponentsofthesystemandtheirrelationships.•Proceduraldesignbuildsonthedataandarchitecturaldesignphasestodescribetheprocessingdetailsofthesystem.Eventhoughtherearenumerousdesignmethodologies,theirbasicconceptsareverysimilar-Allsoftwaredesignmethodspartitiontheproblemandsoftwareintosmallerpiecesinordertoreducecomplexity.Theyallstrivetoidentifydatastructuresandfunctions,andprovidemeasurementsforsoftwarequality.Someofthecommonprinciplesinsoftwaredesigninclude:stepwiserefinement,softwarearchitecture,programstructure,datastructure,softwareprocedures,modularity,abstraction,andinformationhiding.ModernDesignMethodologiesConventionalsoftwaredevelopmentpracticescangenerallybemappedontothetraditionallife-cyclephasesofanalysis,functionalspecification,design,implementation,testing,andmaintenance.Thisthoughtprocessisinadequatefortoday'scomplexinformationsystems.Asthedemandforsoftwareisgrowingmuchfasterthanthenumberofdevelopers,adheringtoconventionaltechniquessuchasthewaterfallmethodrequirestoomuchtime,toomanypeople,andisdifficulttomanage.Hence,manynewsoftwaredevelopmenttechnologieshavearisen.Newlydevelopedpracticesandmodelsdonotattempttoseparatephasesofsoftwaredevelopment,suchasspecificationandimplementation,butinsteadfocusontheconceptofprogramtransformationthroughstepwiserefinementanditeration.1.Object-OrientedTechnologyObject-Oriented(O-O)softwaredesigntechnologyisfundamentallydifferentfromthetraditionalmethodsdescribedabove.Withtraditionalmethods,eachmoduleisrecognizedamajorstepintheoverallprocessandtheprocessgoesfromonesteptothenext.Ontheotherhand,O-Odesignisstructuredaroundamodelofobjectsandthefunctionstheyperform.O-OprogrammingcanbetracedtothesimulationlanguageSIMULA,ahighlevellanguagedevelopedinthelate60'sthatintroducedobjectclassesasamethodtoencapsulatedata.Later,inthe1970s,Smalltalkwasintroducedasacompletegrapghdesignandcodingasdetailisaddedtothedesign.Thisprovidesacommonlanguagethroughouteachstageindevelopment.O-OisbestappliedwithspecificallydesignedO-Odevelopmenttools,butitisimportanttorememberthatasamethodologyisitnotspecifictoanyprogramminglanguage.Manydifferentprogramminglanguagescanbeusedtoimplement0-0technologyanddesignmethodologies.Insteadofproceduresandfunctionspassingdatabackandforth,inobjectorienteddesign,thesystemisviewedasacollectionofobjectswithmessagespassedfromobjecttoobject.Eachobjecthasitsownsetofassociatedoperations.Object-orienteddesignisbasedontheideaofinformationhidingandmodularizationofbothdataandprocessing.Itisbestusedwhenneitherdatastructurenorprocessingoperationsarewelldefinedaheadoftime.Thisisquiteusefulintoday'sbusinessenvironmentwhererequirementsarealwayschangingandnotverywelldefined.Thus,ithasbecomequitepopular!Theconceptofobjectsperformingservicesisanaturalwayofthinkingforbothdevelopersandcustomers.Thisfacilitatesunderstandingtheproblemdomainandamorenaturaldesign.Inaddition,therearemanybenefitsofobject-orienteddevelopment.Theseinclude:•Inheritancecapitalizesonthecommonaltyofattributesandservicesallowingcodeandobjectstobere-used..Informationhidingmakessystemsmorestablebylocalizingchangestoobjectsandtherebymakingthemreusable..Theobject-orienteddevelopmentprocessisconsistentfromanalysis,throughdesign,tocoding.MoreinformationonObjectOrientedProgrammingprinciplescanbefoundinChapter4-OrganizationofProgrammingLanguagesandProgrammingConcepts.2、PrototypingPrototypingwasinventedbecauseendusersparticipatinginthedevelopmentphasefounditdifficulttounderstandrequirementspecificationsandconceptualmodels.However,whenitfirstbeganbeingusedinthe1980s,mostconventionallifecycledevelopersconsidereditexpensiveandtimeconsuming.Sincethattime,usersanddevelopershaveusedprototypessuccessfullyasacommunicationstooltodemonstratesystemrequirements.Afterseveralprototypeiterations,developershaveabetterunderstandingofuserrequirementsandusershaveabetterideaofhowthesystemwilleventuallywork,

look,andl.Thenumberoftimestheprototypeisincrementallyrefineddependsonhowwelltheuserrequirementsandunderstood.Italsodependsontheusersneedtoaddrequirementsorchangepreviouslystatedrequirements.Afterestablishinganoverallarchitectureandframework,thesystemisdevelopedanddeliveredinincrements.Usersmayexperimentwithandusedeliveredincrementswhileothersarebeingdeveloped.Forinstance,thefirstprototypemaybedeliveredthatimplementsacertainscreenwithonlysomeactivemenuitems.Whileusersareexperimentingwiththisscreenandmenuitems,otherscreensandmenuitemsareconcurrentlybeingdevelopedwhichlaterwillbecombinedwiththeexistingprototypeasitevolves.Oncetheuserissatisfiedthattheprototypemeetsrequirements,theprototypeistransformedintothe"system".Thiseffortdependsonseveralfactors.Itmayincludeaddingfunctionalitythatwasn'tinitiallyrecognizedasrequired,replacinginefficientpartsoftheprototypetomeetperformancecriteria,oradaptingtheprototypetofittheuser'shardwareenvironment.Prototypingcanbeginveryearly,aftersomepreliminaryrequirementsanalysishasdeterminedthebasicfunctionality,scope,andenvironmentoftheproposedsoftware.Contrarytothetraditionalwaterfallmethod,intheprototyping,functionalspecificationsarenotfixed.Rather,usersareencouragedtomodifytheirrequirementsastheythemselvesbegintounderstandthembetter.Thisisbecauseusersoftendon'treallyknowwhattheywantuntiltheyseeitonthescreen.Theprototypingprocessofdemonstration,review,andrefinementgetstheusermoreinvolvedinthedevelopmentprocess,givingthemasenseofownershipduringtheprocessandatfinalsystemdelivery.However,duetothemindsetof"prototype",usersoftenfinditdifficulttoverifythattheprototypesatisfiestheirrequirements.Therefore,guidelinesmustbeestablishedtodeterminewhento

stopiteratingandtheprototypetofinalproduct.

软件开发概念和设计方法在20世纪60年代，大型机和高级程序语言被用来解决包括人力资源系统、专有系统和制造系统等许多问题。计算机和软件被视为解决所有商业问题的万能药，有时候甚至被盲目的应用。因为很多设计上的原因，这些系统并不是万能的。主要因素如下：1．不能完全理解复杂的问题2．没有充分满足终端用户的需求，组织环境和性能折中3．没有准确估计开发时间和运行成本4．缺乏一致，规范的客户通讯框架这个时候，结构化的编程，自上而下设计的概念出现了。对软件工程来说，结构化编程至今仍是最重要的方法且不断发展。“软件工程”概念的出现则是基于这样的构想：一个类似工程学的学科可以应用于软件的设计和开发。软件设计是一种方法，软件设计人员可以籍此应用技术和规则生成一种描述并定义问题解决方法的模型。最初，设计方法一直未能构建好，而且模型也不能准确地描述软件开发的问题。然而，随着我们对开发过程的深入理解，设计方法已经不断适应技术的变化了。生命周期过程的模型下开发的，但人们开始尝试寻找这种模型的替代品。一、软件设计基础软件设计方法最终的目标就是向软件设计者提供一张系统蓝图。它通常有三个方面：数据，构架和过程。．数据设计指的是数据的组织、关系、访问和处理方法。．构架设计定义系统组件和它们之间的关系。．过程设计建立在数据和构架设计阶段之上描述系统的处理细节。尽管设计方法众多，但它们的基本概念非常相似。为了减少复杂度，几乎所有软件设计方法都把问题和软件分割成较小的部分用于标识数据结构、功能以及度量软件品质。软件设计包括以下这些普遍原则：逐步求精、软件构架、程序结构、数据结构、软件过程、模块化、抽象和信息隐藏。二、现代设计方法常规的软件开发实践通常能被映射到传统的生命阶段上，包括分析、功能说明、设计、实现、测试和维护。然而对软件需求的增长比软件开发者数量增长要快，遵守常规的技术你瀑布模型）耗时太长，过多人员的参与也带来了管理上的困难，显然常规的思考过程对于今天的复杂信息系统是不够的。因此，产生了许多新的软件开发技术。最新发展出的实践和模型井不试图把软件开发分割成多个阶段（如说明和实现），而是注重于通过逐步求精和迭代把概念转换成程序。1、面向对象的技术面向对象的软件设计技术从根本上有别于传统的设计方法。传统方法中，每个模块被当作全局过程的一个主要步骤，一步一步地往下走；而面向对象的设计围绕着对象模型和对象所执行的功能进行结构化。面向对象的编程可以追溯到仿真语言SIMULA。SIMULA是一种20世纪60年代后期的高级语言，引入了“对象类”作为封装数据的方法。到了20世纪70年代，Smalltalk被作为一种完全的图形用户界面（GUI）面向对象的编程环境被引入。甚至在30年以后，Smalltalk仍然是度量其他所有面向对象语言的标准。由于面向对象的概念日趋成熟，最近十年这种软件开发方法已经流行起来。同时，软件业注意的焦点己经从编码和结构化过程转移到通过设计和柔韧性来节省劳动力成本和时间。柔韧性变得十分关键，因为系统随着需求的变化而快速改变：变得更大，更复杂和更不稳定。在面向对象中，分析和设计没有真正分开。在分析期间，系统对象及其特性和关系一起被确定。这些对象可以护，这样就给整个开发过程中的所有阶段提供了一种公用的语言。采用面向对象方法最好是使用专门设计的面向对象的开发工具，但是请一定记住它是一种方法而不是特指任何编程语言。许多不同的编程语言都可以用来实现面向对象技术和设计方法。和过程、功能往返传递数据的方式不同，在面向对象的设计中，系统被看成一个由很多互相传递消息的对象组成的集合，每个对象都有它自己关联操作的集合。面向对象的设计基本构想是把数据和过程进行信息隐藏和模块化，它最适用于数据结构或者过程操作没有被提前的定义好的情况。这对