COIS 3040H Lecture Notes - Lecture 8: Late Binding
Document Summary
Restrict dependencies: restricts the modules which a given module interacts with r depends on. Refactor: undertaken when two modules are affected by the same change because they are (at least partial) duplicates of each other. Abstract common services: where two modules provide not-quite-the-same but similar services, it may be cost-effective to implement the services just once in a more general (abstract) form. In general, the later in the life cycle we can bind values, the better. If we design artifacts with built-in flexibility, then exercising that flexibility is usually cheaper than hand-coding a specific change: however, putting the mechanisms in place to facilitate that late binding tends to be more expensive. Is about the degree to which two or more systems can usefully exchange meaningful information. Like all quality attributes, interoperability is not a yes-or-no proposition but has shades of meaning. Goal of interoperability tactics: for two or more systems to usefully exchange information they must, know about each other.