Design Tactics - Modifiability
= 26 items
(filtered by ) / - Localize ChangesRestricting modifications to a small set of modules will generally reduce the cost.
- Know Your Dependencies
- Syntax of Data/Service.The data that is produced by A and consumed by B must be consistent with the type (or format) of data assumed by B
- Semantics of Data/ServiceThe data produced by A and consumed by B must be consistent with the assumptions of B.
- Sequence of Data/ServiceB must receive the data produced by A in a fixed sequence.
- Identity of an InterfaceThe identity (name or handle) of the interface must be consistent with the assumptions of B.
- Location (Runtime)The runtime location of A must be consistent with the assumptions of B.
- Quality of Service/DataThe quality of the data or service provided by A must be consistent with B's assumptions.
- ExistenceFor B to execute correctly, A must exist.
- Resource BehaviorThe resource behavior of A must be consistent with B's assumptions.
- Maintain Semantic CoherenceEnsure that module responsibilities work together without excessive reliance on other modules.
- Abstract Common ServicesModifications to commons services will need to be made only once rather than in each module.
- Anticipate Expected ChangesEvaluate an assignment of responsibilities baed on the set of envisioned changes.
- Generalize the ModuleThe more general a module, the more likely that requested changes can be made by adjusing the input language rather than by modifying the module.
- Limit Possible OptionsRestricting the possible options reduces the effect of these modifications.
- Prevention of Ripple EffectsA ripple effect from a modification is the necessity of making changes to modules not directly affected by it.
- Hide InformationIsolate changes within one module and prevent changes from propagating to others.
- Maintain Existing InterfacesMaintaining the interface and its syntax allows a module to remain unchanged.
- Restrict Communication PathsData production/consumption introduces dependencies that cause ripples.
- Defer Binding TimeBinding at runtime means that the system has been prepared for that binding and all of the testing and distribution steps have been completed.
- Runtime RegistrationSupports plug-and-play operation at the cost of additional overhead.
- Configuration FilesSet parameters at startup.
- Polymorphism allows late binding of method calls.Allows late binding of method calls.
- Component ReplacementAllows load time binding.
- Adherence to Defined ProtocolsAllows runtime binding of independent processes.