版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)
文檔簡介
《計算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化《計算與軟件工程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《計算與軟件工程II》
Ch14“面向?qū)ο蟆钡哪K化《計算與軟件工程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等.壓縮文件請下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責。
- 6. 下載文件中如有侵權(quán)或不適當內(nèi)容,請與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 大學(xué)工作計劃模板合集5篇
- 消防演練活動總結(jié)
- 音樂組教研工作計劃(錦集5篇)
- 幼兒園班級計劃撰寫培訓(xùn)心得
- 暑假學(xué)生學(xué)習(xí)計劃模板合集八篇
- 豎笛興趣小組的活動計劃
- 二年級下學(xué)期數(shù)學(xué)教學(xué)計劃三篇
- 我的青春夢想演講稿合集15篇
- 餐飲簡單辭職報告(9篇)
- 中國與周邊國家的領(lǐng)土糾紛
- GB/T 12234-2019石油、天然氣工業(yè)用螺柱連接閥蓋的鋼制閘閥
- 四川氏宗親新春聯(lián)誼會策劃方案
- 耳鳴、耳聾課件
- 屠宰宰豬場輕工行業(yè)雙控體系建設(shè)文件風(fēng)險分級管控體系
- 醫(yī)院護工培訓(xùn)-教學(xué)課件
- 考研考博-英語-中國礦業(yè)大學(xué)(北京)考試押題卷含答案詳解
- 欄桿百葉安裝施工方案
- 低壓配電電源質(zhì)量測試記錄
- 安徽省水利工程質(zhì)量檢測和建筑材料試驗服務(wù)收費標準
- 2022課程標準解讀及學(xué)習(xí)心得:大單元教學(xué)的實踐與思考
- OA協(xié)同辦公系統(tǒng)運行管理規(guī)定
評論
0/150
提交評論