版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)
文檔簡介
《計(jì)算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化《計(jì)算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化1ModuleApieceofcodeMethodsClassModule(package)Coupling:amongpiecesCohesion:internalapieceModuleApieceofcode2What’sthedifferencebetweenStructuralmethodsandOOmethodsCouplingCouplingisthemeasureofthestrengthofassociationestablishedbyaconnection
fromonemoduletoanotherStructuralmethodsAconnectionisareferencetosomelabeloraddressdefinedelsewhereOOmethodsInteractioncouplingComponentcouplingInheritancecouplingWhat’sthedifferencebetween3MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO4SingleinteractioncouplingMethodInvokeorAttributeAccessbetweentwoclassMostsimilartotheclassicaldefinitionofcouplingbetweenmodulesNotincludinginheritanceParameterandAttributenotincludingClassTypeSingleinteractioncouplingMet5StrengthofSingleinteractioncouplingStrengthofSingleinteraction6PrinciplesofinteractioncouplingPrinciplesfromModularization1:《GlobalVariablesConsiderHarmful》2:《TobeExplicit》3:《DonotRepeat》4:ProgrammingtoInterfacePrinciplesofinteractioncoup7MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO8ComponentcouplingAbstractionDefineoneplace,usingmanyplaceClass-Level,Object-LevelComponentcouplingThecomponentrelationshipbetweenclassesisdefinedbytheuseofaclassasdomainofsomeinstancevariableofanotherclassNotincludingInheritanceUsuallyClass-LevelneededAttributeType:howtoexplicitComponentcouplingAbstraction9FourKindsofComponentcouplingWholevariable:AggregationParameter:MethodParameterCreator:Creatorinsomemethod’slocalHidden:GivenbyanotherobjectFourKindsofComponentcoupli10HiddenComponentcouplingTheworstcoupling:ImplicitThecouplingbetweentwoclassesCandC’
isratedhiddenifC’
showsupneitherinthespecificationnorintheimplementationofCalthoughanobjectofC’
isusedintheimplementationofamethodofCAsimilarproblemisencounteredifthereturnvalueofamethodinvocationisimmediatelyusedasinputparameterinanothermethodinvocationdisallowtheuseofcascadingmessagesTobeexplicit!HiddenComponentcouplingThew11HiddenComponentcouplingHiddenComponentcoupling12TheLawofDemeterExampleTheLawofDemeterExample13PrinciplesofComponentCouplingPrinciple5:TheLawofDemeterYoucanplaywithyourself.Youcanplaywithyourowntoys,butyoucan'ttakethemapartYoucanplaywithtoysthatweregiventoyou.Youcanplaywithtoysyou'vemadeyourself.PrinciplesofComponentCoupli14南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件15ScatteredComponentCouplingWeratetwoclassesCandC’
asscatteredcoupledifC’
isusedasdomaininthedefinitionofsomelocalvariableorinstancevariableintheimplementationofCyetC’
isnotincludedinthespecificationofCCommonandacceptableAggregation:GlobalLocalinstance:LocalWhichisbetter?ManyConnectionsVSStrongerSingleConnectionScatteredComponentCouplingWe16SpecifiedComponentCouplingWeratetwoclassesCandC’
asspecifiedcoupledifC’
isincludedinthespecificationofCwheneveritisacomponentofCGetSpecified,DesignbyContract——SufferedInterfaceVSRequiredInterfaceSufferedInterface:SpecifiedRequiredInterface:UsedScatteredComponentCouplingcanbeimprovedtoSpecifiedcomponentcouplingwithcommentsSpecifiedComponentCouplingWe17PrinciplesofComponentCouplingPrinciple4:ProgrammingtoInterfaceProgrammingtoRequiredInterface,notonlySufferedInterfaceDesignbyContractContractofModule/ClassRequiredmothods/ProvidedmethodsContractofMethodsPreCondition,PostCondition,InvariantPrinciplesofComponentCoupli18PrinciplesofComponentCoupling
Principles6:InterfaceSegregationPrinciple(ISP)ProgrammingtoSimplerInterfaceManyclient-specificinterfacesarebetter
thanonegeneralpurposeinterfaceClientsshouldnotbeforcedtodependuponinterfacesthattheydonotuse.R.Martin,1996PrinciplesofComponentCoupli19PrinciplesofComponentCoupling
——ISPExplainedMultipurposeclassesMethodsfallindifferentgroupsNotallusersuseallmethodsCanleadtounwanteddependenciesClientsusingoneaspectofaclassalsodependindirectlyonthedependenciesoftheotheraspectsISPhelpstosolvetheproblemUseseveralclient-specificinterfacesPrinciplesofComponentCoupli20PrinciplesofComponentCoupling
——ISPExample:UIsUIsareisolatedfromeachotherCanaddaUIwithchangesinServer→otherUIsnotaffectedTheServer"collects"interfacesNewUI→ServerinterfacechangesAllotherUIsrecompilePrinciplesofComponentCoupli21南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件22MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO23InheritanceCouplingParentinformationisspecifiedforchildrenWithaparentreference,howmanyinformationaclientneededwheninteracting?ModificationRefinementExtensionInheritanceCouplingParentinf24ModificationInheritanceCouplingModifyingwithoutanyrulesandrestrictsWorstInheritanceCouplingIfaclientusingaparentref,theparentandchildmethodareallneededImplicitTherearetwoconnections,morecomplexHarmtopolymorphismModificationInheritanceCoupl25RefinementInheritanceCouplingdefiningnewinformationtheinheritedinformationisonlychangedduetopredefinedrulesIfaclientusingaparentref,thewholeparentandrefinementofchildareneeded1+connectionsNecessary!RefinementInheritanceCouplin26ExtensionInheritanceCoupling
thesubclassonlyaddsmethodsandinstancevariablesbutneithermodifiesnorrefinesanyoftheinheritedonesIfaclientusingaparentref,onlytheparentisneeded1connectionExtensionInheritanceCoupling27HowInheritancereducecoupling?Remember:inRefinementandExtensioninheritancecoupling,theinteractioncouplingbetweensuper-classandsubclassisignoredHowInheritancereducecouplin28PrinciplesofInheritCoupling
AllderivedclassesmustbesubstituteablefortheirbaseclassBarbaraLiskov,1988Functionsthatusepointersorreferencestobaseclassesmustbeabletouseobjectsofderivedclasseswithoutknowingit.R.Martin,1996Principle7:LiskovSubstitutionPrinciple(LSP)PrinciplesofInheritCoupling29LSP:
exampleLSP:example30LSP:
exampleLSP:example31InheritanceAppearsSimple
IsaSquareaRectangle?
Rectr=newRect();setWidth=4;setHeight=5;assert(20==getArea());classSquareextendsRect{//Squareinvariant,height=widthsetWidth(x){setHeight()=x}setHeight(x){setWidth(x)}}//violateLSP?InheritanceAppearsSimple
Is32InheritanceAppearsSimpleclassBird{
//hasbeak,wings,...
public:virtualvoidfly();
//Birdcanfly};classParrot
:publicBird{//Parrotisabird
public:virtualvoidmimic();
//CanRepeat
words...};classPenguin:publicBird{
public:voidfly(){
error(“Penguinsdon’tfly!”);}};InheritanceAppearsSimpleclas33PenguinsFailtoFly!voidPlayWithBird(Bird&abird)
{
abird.fly();
//OKifParrot.
//ifbirdhappenstobePenguin...OOOPS!!}Doesnotmodel:
“Penguinscan’tfly”Itmodels
“Penguinsmayfly,butiftheytryitiserror”
Run-timeerrorifattempttoflynotdesirable
ThinkaboutSubstitutability-FailsLSPPenguinsFailtoFly!voidPlay34LSPSummaryLSPisaboutSemanticsandReplacementUnderstandbeforeyoudesignThemeaningandpurposeofeverymethodandclassmustbeclearlydocumentedLackofuserunderstandingwillinducedefactoviolationsofLSPReplaceabilityiscrucialWheneveranyclassisreferencedbyanycodeinanysystem, anyfutureorexistingsubclassesofthatclassmustbe100%replaceableLSPSummaryLSPisaboutSemant35LSPSummaryDesignbyContractAdvertisedBehaviorofanobject:advertisedRequirements(Preconditions)advertisedPromises(Postconditions)Whenredefiningamethodinaderivateclass,youmayonlyreplaceitspreconditionbyaweakerone,anditspostconditionbyastrongeroneB.Meyer,1988Derivedclassservices
shouldrequireno
moreandpromisenoless
LSPSummaryDesignbyContractW36南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件37Principle8:FavorCompositionOverInheritanceUseinheritforpolymorphismUsedelegatenotinherittoreusecode!Principle8:FavorCompositio38Coad'sRulesofUsingInheritanceUseinheritanceonlywhenallofthefollowingcriteriaaresatisfied:Asubclassexpresses"isaspecialkindof"andnot"isaroleplayedbya"AninstanceofasubclassneverneedstobecomeanobjectofanotherclassAsubclassextends,ratherthanoverridesornullifies,theresponsibilitiesofitssuperclassAsubclassdoesnotextendthecapabilitiesofwhatismerelyanutilityclassCoad'sRulesofUsingInherita39Inheritance/CompositionExample1Inheritance/CompositionExampl40Inheritance/CompositionExample1(Continued)Inheritance/CompositionExampl41Inheritance/CompositionExample2Inheritance/CompositionExampl42classObject{ public:virtualvoidupdate(){}; virtualvoiddraw(){}; virtualvoidcollide(Objectobjects[]){};};classVisible:publicObject{public:virtualvoiddraw(){ /*drawmodelatpositionofthisobject*/};private:Model*model;};classSolid:publicObject{public:virtualvoidcollide(Objectobjects[]){ /*checkandreacttocollisionswithobjects*/};};classMovable:publicObject{ public:virtualvoidupdate(){ /*updateposition*/};};classObject{43MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO44CouplingMetricsbetweenclassesCouplingbetweenobjectclasses(CBO)Acountofthenumberofotherclasses:whichaccessamethodorvariableinthisclass,orcontainamethodorvariableaccessedbythisclassNotincludingInheritanceWanttokeepthislowCouplingMetricsbetweenclass45CouplingMetricsbetweenclassesDataabstractioncoupling(DAC)ThenumberofattributehavinganADTtypedependentonthedefinitionsofotherclassesWanttokeepthislowCouplingMetricsbetweenclass46CouplingMetricsbetweenclassesCeand&D(efferentandafferentcoupling)Ca:Thenumberofclassesoutsidethiscategorythatdependuponclasseswithinthiscategory.Ce:ThenumberofclassesinsidethiscategorythatdependuponclassesoutsidethiscategoryWanttokeeptheselowCouplingMetricsbetweenclass47CouplingMetricsbetweenclassesDepthoftheInheritancetree(DIT)themaximumlengthfromthenodetotherootofthetreeasDITgrows,itbecomesdifficulttopredictbehaviorofaclassbecauseofthehighdegreeofinheritancePositively,largeDITvaluesimplythatmanymethodsmaybereusedCouplingMetricsbetweenclass48CouplingMetricsbetweenclassesNumberofchildren(NOC)countofthesubclassesimmediatelysubordinatetoaclassasNOCgrows,reuseincreasesasNOCgrows,abstractioncanbecomedilutedincreaseinNOCmeanstheamountoftestingwillincreaseCouplingMetricsbetweenclass49MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO50CohesionofAttributesSeparablerepresentmultipleunrelateddataabstractionscombinedinoneobjectmultifacetedrepresentmultiplerelateddataabstractionsNon-delegatedSomeattributerepresentapartofanotherclass:notinthirdnormalformConcealedsomeattributeandreferencingmethodswhichmayberegardedasaclassofitsownModel:informationalstrengththeclassrepresentsasinglesemanticallymeaningfulconceptualCohesionofAttributesSeparabl51CohesionofmethodsMethodsofaClassareCommoncouplingAllmethodsserveOneResponsibilityInformationalCohesionRelativefunctions(functionalCohesion)Principle9:SingleResponsibilityPrincipleCohesionofmethodsMethodsof52SingleResponsibilityPrinciple(SRP)AclassshouldhaveonlyonereasontochangeRobertMartinRelatedtoandderivedfromcohesion,i.e.thatelementsinamoduleshouldbecloselyrelatedintheirfunctionResponsibilityofaclasstoperformacertainfunctionisalsoareasonfortheclasstochangeSingleResponsibilityPrincipl53SRPExampleSRPExample54SRPExampleSRPExample55SRPSummaryClassshouldhaveonlyonereasontochangeCohesionofitsfunctions/responsibilitiesSeveralresponsibilitiesmeanseveralreasonsforchanges→morefrequentchangesSoundssimpleenoughNotsoeasyinreallifeTradeoffswithcomplexity,repetition,opacitySRPSummaryClassshouldhaveo56南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件57MeasureclasscohesionLackofcohesioninmethods(LCOM)WanttokeepthislowManyotherversionsofLCOMhavebeendefinedMeasureclasscohesionLackof58MeasureclasscohesionIfLCOM>=1,thentheclassshouldbeseparatedMeasureclasscohesionIfLCOM59PrinciplesofinteractioncouplingPrinciplesfromModularization1:《GlobalVariablesConsiderHarmful》2:《TobeExplicit》3:《DonotRepeat》4:ProgrammingtoInterfacePrinciplesofinteractioncoup60MorePrinciples4:ProgrammingtoInterface(DesignbyContract)5:TheLawofDemeter6:InterfaceSegregationPrinciple(ISP)7:LiskovSubstitutionPrinciple(LSP)8:FavorCompositionOverInheritance9:SingleResponsibilityPrincipleMorePrinciples4:Programming61《計(jì)算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化《計(jì)算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化62ModuleApieceofcodeMethodsClassModule(package)Coupling:amongpiecesCohesion:internalapieceModuleApieceofcode63What’sthedifferencebetweenStructuralmethodsandOOmethodsCouplingCouplingisthemeasureofthestrengthofassociationestablishedbyaconnection
fromonemoduletoanotherStructuralmethodsAconnectionisareferencetosomelabeloraddressdefinedelsewhereOOmethodsInteractioncouplingComponentcouplingInheritancecouplingWhat’sthedifferencebetween64MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO65SingleinteractioncouplingMethodInvokeorAttributeAccessbetweentwoclassMostsimilartotheclassicaldefinitionofcouplingbetweenmodulesNotincludinginheritanceParameterandAttributenotincludingClassTypeSingleinteractioncouplingMet66StrengthofSingleinteractioncouplingStrengthofSingleinteraction67PrinciplesofinteractioncouplingPrinciplesfromModularization1:《GlobalVariablesConsiderHarmful》2:《TobeExplicit》3:《DonotRepeat》4:ProgrammingtoInterfacePrinciplesofinteractioncoup68MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO69ComponentcouplingAbstractionDefineoneplace,usingmanyplaceClass-Level,Object-LevelComponentcouplingThecomponentrelationshipbetweenclassesisdefinedbytheuseofaclassasdomainofsomeinstancevariableofanotherclassNotincludingInheritanceUsuallyClass-LevelneededAttributeType:howtoexplicitComponentcouplingAbstraction70FourKindsofComponentcouplingWholevariable:AggregationParameter:MethodParameterCreator:Creatorinsomemethod’slocalHidden:GivenbyanotherobjectFourKindsofComponentcoupli71HiddenComponentcouplingTheworstcoupling:ImplicitThecouplingbetweentwoclassesCandC’
isratedhiddenifC’
showsupneitherinthespecificationnorintheimplementationofCalthoughanobjectofC’
isusedintheimplementationofamethodofCAsimilarproblemisencounteredifthereturnvalueofamethodinvocationisimmediatelyusedasinputparameterinanothermethodinvocationdisallowtheuseofcascadingmessagesTobeexplicit!HiddenComponentcouplingThew72HiddenComponentcouplingHiddenComponentcoupling73TheLawofDemeterExampleTheLawofDemeterExample74PrinciplesofComponentCouplingPrinciple5:TheLawofDemeterYoucanplaywithyourself.Youcanplaywithyourowntoys,butyoucan'ttakethemapartYoucanplaywithtoysthatweregiventoyou.Youcanplaywithtoysyou'vemadeyourself.PrinciplesofComponentCoupli75南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件76ScatteredComponentCouplingWeratetwoclassesCandC’
asscatteredcoupledifC’
isusedasdomaininthedefinitionofsomelocalvariableorinstancevariableintheimplementationofCyetC’
isnotincludedinthespecificationofCCommonandacceptableAggregation:GlobalLocalinstance:LocalWhichisbetter?ManyConnectionsVSStrongerSingleConnectionScatteredComponentCouplingWe77SpecifiedComponentCouplingWeratetwoclassesCandC’
asspecifiedcoupledifC’
isincludedinthespecificationofCwheneveritisacomponentofCGetSpecified,DesignbyContract——SufferedInterfaceVSRequiredInterfaceSufferedInterface:SpecifiedRequiredInterface:UsedScatteredComponentCouplingcanbeimprovedtoSpecifiedcomponentcouplingwithcommentsSpecifiedComponentCouplingWe78PrinciplesofComponentCouplingPrinciple4:ProgrammingtoInterfaceProgrammingtoRequiredInterface,notonlySufferedInterfaceDesignbyContractContractofModule/ClassRequiredmothods/ProvidedmethodsContractofMethodsPreCondition,PostCondition,InvariantPrinciplesofComponentCoupli79PrinciplesofComponentCoupling
Principles6:InterfaceSegregationPrinciple(ISP)ProgrammingtoSimplerInterfaceManyclient-specificinterfacesarebetter
thanonegeneralpurposeinterfaceClientsshouldnotbeforcedtodependuponinterfacesthattheydonotuse.R.Martin,1996PrinciplesofComponentCoupli80PrinciplesofComponentCoupling
——ISPExplainedMultipurposeclassesMethodsfallindifferentgroupsNotallusersuseallmethodsCanleadtounwanteddependenciesClientsusingoneaspectofaclassalsodependindirectlyonthedependenciesoftheotheraspectsISPhelpstosolvetheproblemUseseveralclient-specificinterfacesPrinciplesofComponentCoupli81PrinciplesofComponentCoupling
——ISPExample:UIsUIsareisolatedfromeachotherCanaddaUIwithchangesinServer→otherUIsnotaffectedTheServer"collects"interfacesNewUI→ServerinterfacechangesAllotherUIsrecompilePrinciplesofComponentCoupli82南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件83MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO84InheritanceCouplingParentinformationisspecifiedforchildrenWithaparentreference,howmanyinformationaclientneededwheninteracting?ModificationRefinementExtensionInheritanceCouplingParentinf85ModificationInheritanceCouplingModifyingwithoutanyrulesandrestrictsWorstInheritanceCouplingIfaclientusingaparentref,theparentandchildmethodareallneededImplicitTherearetwoconnections,morecomplexHarmtopolymorphismModificationInheritanceCoupl86RefinementInheritanceCouplingdefiningnewinformationtheinheritedinformationisonlychangedduetopredefinedrulesIfaclientusingaparentref,thewholeparentandrefinementofchildareneeded1+connectionsNecessary!RefinementInheritanceCouplin87ExtensionInheritanceCoupling
thesubclassonlyaddsmethodsandinstancevariablesbutneithermodifiesnorrefinesanyoftheinheritedonesIfaclientusingaparentref,onlytheparentisneeded1connectionExtensionInheritanceCoupling88HowInheritancereducecoupling?Remember:inRefinementandExtensioninheritancecoupling,theinteractioncouplingbetweensuper-classandsubclassisignoredHowInheritancereducecouplin89PrinciplesofInheritCoupling
AllderivedclassesmustbesubstituteablefortheirbaseclassBarbaraLiskov,1988Functionsthatusepointersorreferencestobaseclassesmustbeabletouseobjectsofderivedclasseswithoutknowingit.R.Martin,1996Principle7:LiskovSubstitutionPrinciple(LSP)PrinciplesofInheritCoupling90LSP:
exampleLSP:example91LSP:
exampleLSP:example92InheritanceAppearsSimple
IsaSquareaRectangle?
Rectr=newRect();setWidth=4;setHeight=5;assert(20==getArea());classSquareextendsRect{//Squareinvariant,height=widthsetWidth(x){setHeight()=x}setHeight(x){setWidth(x)}}//violateLSP?InheritanceAppearsSimple
Is93InheritanceAppearsSimpleclassBird{
//hasbeak,wings,...
public:virtualvoidfly();
//Birdcanfly};classParrot
:publicBird{//Parrotisabird
public:virtualvoidmimic();
//CanRepeat
words...};classPenguin:publicBird{
public:voidfly(){
error(“Penguinsdon’tfly!”);}};InheritanceAppearsSimpleclas94PenguinsFailtoFly!voidPlayWithBird(Bird&abird)
{
abird.fly();
//OKifParrot.
//ifbirdhappenstobePenguin...OOOPS!!}Doesnotmodel:
“Penguinscan’tfly”Itmodels
“Penguinsmayfly,butiftheytryitiserror”
Run-timeerrorifattempttoflynotdesirable
ThinkaboutSubstitutability-FailsLSPPenguinsFailtoFly!voidPlay95LSPSummaryLSPisaboutSemanticsandReplacementUnderstandbeforeyoudesignThemeaningandpurposeofeverymethodandclassmustbeclearlydocumentedLackofuserunderstandingwillinducedefactoviolationsofLSPReplaceabilityiscrucialWheneveranyclassisreferencedbyanycodeinanysystem, anyfutureorexistingsubclassesofthatclassmustbe100%replaceableLSPSummaryLSPisaboutSemant96LSPSummaryDesignbyContractAdvertisedBehaviorofanobject:advertisedRequirements(Preconditions)advertisedPromises(Postconditions)Whenredefiningamethodinaderivateclass,youmayonlyreplaceitspreconditionbyaweakerone,anditspostconditionbyastrongeroneB.Meyer,1988Derivedclassservices
shouldrequireno
moreandpromisenoless
LSPSummaryDesignbyContractW97南京大學(xué)-軟件工程-14面向?qū)ο竽K化課件98Principle8:FavorCompositionOverInheritanceUseinheritforpolymorphismUsedelegatenotinherittoreusecode!Principle8:FavorCompositio99Coad'sRulesofUsingInheritanceUseinheritanceonlywhenallofthefollowingcriteriaaresatisfied:Asubclassexpresses"isaspecialkindof"andnot"isaroleplayedbya"AninstanceofasubclassneverneedstobecomeanobjectofanotherclassAsubclassextends,ratherthanoverridesornullifies,theresponsibilitiesofitssuperclassAsubclassdoesnotextendthecapabilitiesofwhatismerelyanutilityclassCoad'sRulesofUsingInherita100Inheritance/CompositionExample1Inheritance/CompositionExampl101Inheritance/CompositionExample1(Continued)Inheritance/CompositionExampl102Inheritance/CompositionExample2Inheritance/CompositionExampl103classObject{ public:virtualvoidupdate(){}; virtualvoiddraw(){}; virtualvoidcollide(Objectobjects[]){};};classVisible:publicObject{public:virtualvoiddraw(){ /*drawmodelatpositionofthisobject*/};private:Model*model;};classSolid:publicObject{public:virtualvoidcollide(Objectobjects[]){ /*checkandreacttocollisionswithobjects*/};};classMovable:publicObject{ public:virtualvoidupdate(){ /*updateposition*/};};classObject{104MainContentsCouplingofOOInteractionCouplingComponentCouplingInheritCouplingCouplingMetricofOOCohesionofOOMainContentsCouplingofOO105CouplingMetricsbetweenclassesCouplingbetweenobjectclasses(CBO)Acountofthenumberofotherclasses:whichaccessamethodorvariableinthisclass,orcontainamethodorvariableaccessedbythisclassNotincludingInheritanceWanttokeepthislowCouplingMetricsbetweenclass106CouplingMetricsbetweenclassesDataabstractioncoupling(DAC)ThenumberofattributehavinganADTtypedependentonthedefinitionsofotherclassesWanttokeepthislowCouplingMetricsbetweenclass107CouplingMetricsbetweenclassesCeand&D(efferentandafferentcoupling)Ca:Thenumberofclassesoutsidethiscategorythatdependuponclasseswithinthiscategory.Ce:ThenumberofclassesinsidethiscategorythatdependuponclassesoutsidethiscategoryWanttokeeptheselowCouplingMetricsbetweenclass108CouplingMetricsbetweenclassesDepthoftheInheritancetree(DIT)themaximumlengthfromthenodetotherootofthetreeasDITgrows,itbecomesdifficultto
溫馨提示
- 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。
最新文檔
- 2024年版企業(yè)破產(chǎn)重整合同
- 2024年度無息個(gè)人婚禮籌備借款協(xié)議書下載3篇
- 2025年日喀則貨運(yùn)資格證模擬考試
- 2024年停薪留職期間員工社會(huì)保險(xiǎn)及福利協(xié)議合同3篇
- 2025購房合同的范本 購房合同樣本
- 2025年柳州貨運(yùn)從業(yè)資格證考試卷
- 洛陽理工學(xué)院《內(nèi)科護(hù)理學(xué)2》2023-2024學(xué)年第一學(xué)期期末試卷
- 2024年墓地環(huán)境優(yōu)化協(xié)議3篇
- 汽車俱樂部噴泉建設(shè)合同
- 2024年度家電品牌全國巡回展銷合同范本3篇
- 【MOOC】法理學(xué)-西南政法大學(xué) 中國大學(xué)慕課MOOC答案
- 遼寧省普通高中2024-2025學(xué)年高一上學(xué)期12月聯(lián)合考試語文試題(含答案)
- 儲(chǔ)能運(yùn)維安全注意事項(xiàng)
- 2024蜀繡行業(yè)市場趨勢分析報(bào)告
- 電力法律法規(guī)培訓(xùn)
- 北京交通大學(xué)《成本會(huì)計(jì)》2023-2024學(xué)年第一學(xué)期期末試卷
- 2024年世界職業(yè)院校技能大賽“智能網(wǎng)聯(lián)汽車技術(shù)組”參考試題庫(含答案)
- 【課件】校園安全系列之警惕“死亡游戲”主題班會(huì)課件
- 化工企業(yè)冬季安全生產(chǎn)檢查表格
- 2024年工程勞務(wù)分包聯(lián)合協(xié)議
- 蜜雪冰城員工合同模板
評(píng)論
0/150
提交評(píng)論