




版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報或認(rè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)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 2025年懸架系統(tǒng):鋼板彈簧合作協(xié)議書
- 江西省南昌市第一中學(xué)2025年高考全國統(tǒng)考預(yù)測密卷化學(xué)試卷含解析
- 2025年油罐計量系統(tǒng)項目建議書
- 急性腎衰竭的護(hù)理措施
- 2025年無汞可充電堿錳電池項目發(fā)展計劃
- 深度解析《GBT 43918-2024交流標(biāo)準(zhǔn)電能表》
- 陜西藝術(shù)職業(yè)學(xué)院《山水畫》2023-2024學(xué)年第二學(xué)期期末試卷
- 陜西財經(jīng)職業(yè)技術(shù)學(xué)院《家居無障礙設(shè)計》2023-2024學(xué)年第二學(xué)期期末試卷
- 陜西鐵路工程職業(yè)技術(shù)學(xué)院《機(jī)電工程專業(yè)英語》2023-2024學(xué)年第一學(xué)期期末試卷
- 隨州職業(yè)技術(shù)學(xué)院《動畫角色設(shè)計》2023-2024學(xué)年第一學(xué)期期末試卷
- (完整版)《計算機(jī)控制系統(tǒng)》課后題答案-劉建昌等科學(xué)出版社
- 兒童保健規(guī)范化門診標(biāo)準(zhǔn)(2021年版)
- 金融服務(wù)與管理專業(yè)群建設(shè)方案
- 供配電系統(tǒng)畢業(yè)設(shè)計
- 《藝術(shù)學(xué)概論考研》課件藝概緒論
- 中職一年級數(shù)學(xué)課外活動趣味數(shù)學(xué)基礎(chǔ)知識競賽課件(必答+選答+風(fēng)險題含倒計時PPT)
- 班級共讀《一年級大個子二年級小個子 》班級讀書會(課堂PPT)
- 啟閉機(jī)房腳手架工程施工專項方案
- 防毒面具使用說明
- 工藝評審記錄表
- 浦東改革開放30周年(課堂PPT)
評論
0/150
提交評論