Getting loose coupling

Designing and Maintaining Software (DAMS)
 Louis Rose

Recap: DIP “High-level modules should not depend on low-level modules. Both should depend on abstractions.”
 
 “Abstractions should not depend on details. Details should depend on abstractions.” - Bob Martin
 http://www.objectmentor.com/resources/articles/dip.pdf

Tactics Inject dependencies to avoid coupling
 with specific implementations Invert control to avoid coupling
 with implementations “Tell, Don’t Ask” to avoid coupling
 with intermediaries Introduce gateways to avoid coupling
 with external services

Inject Dependencies class Pizza def initialize(temperature, duration) @temperature = temperature @duration = duration end def bake Oven.new(@temperature, @duration).cook(self) end end Pizza.new(200, 30).bake

Inject Dependencies class Pizza def initialize(temperature, duration) @temperature = temperature @duration = duration end def bake Oven.new(@temperature, @duration).cook(self) end end Pizza.new(200, 30).bake

Inject Dependencies class Pizza def initialize(oven) @oven = oven end def bake @oven.cook(self) end end Pizza.new(Oven.new(200, 30)).bake
 Pizza.new(Barbeque.new(:smoky, 30)).bake

Invert Control connection = Connection.new(@credentials) connection.open connection.send("foo") connection.send("bar") connection.flush connection.close

Invert Control connection = Connection.new(@credentials) connection.open connection.send(“foo") connection.send("bar") connection.flush connection.close

Invert Control Connection.perform(@credentials) do |connection| connection.send("foo") connection.send("bar") end

Client code no longer specifies when it’s called
 Hollywood Principle: “Don’t call us, we’ll call you”

Connection.perform? class Connection def self.perform(@credentials) connection = Connection.new(@credentials) connection.open yield connection.flush connection.close end end

Recap: Law of Demeter “Talk only to your neighbours” allowance yourself

example self

your own toys

formatter

toys you’ve been given

printable

toys you’ve made yourself

out

class Printer attr_reader :formatter def print(printable) out = TempFile.new
 ... end end

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.wallet.withdraw(self.cost) end end

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.wallet.withdraw(self.cost) end end

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.wallet.withdraw(self.cost) end end

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.wallet.withdraw(self.cost) end end

Courier is now coupled to how a customer stores their money!


Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.wallet.withdraw(self.cost) end end

Courier is now coupled to how a customer stores their money!
 But, really, a courier only cares that they get paid, not how.

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.request_payment(self.cost) end end

Courier is now coupled to how a customer stores their money!
 But, really, a courier only cares that they get paid, not how.

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.request_payment(self.cost) end end
 
 class Customer def request_payment(amount) @wallet.withdraw(amount) end end


 But, really, a courier only cares that they get paid, not how.

Tell, Don’t Ask class Courier def deliver_to(customer, parcel) drive_to(customer.address) customer.give(parcel) customer.request_payment(self.cost) end end
 
 class Customer def request_payment(amount) @wallet.withdraw(amount) end end


 But, really, a courier only cares that they get paid, not how.

Introduce Gateways class Order def bill braintree_id = Braintree.find_user(@user.email).braintree_id Braintree.charge(braintree_id, @amount) end end class Refund def run transaction_id = Braintree.find_transaction(@order.braintree_id) Braintree.refund(transaction_id, @amount) end end

Order and Refund are coupled to this payment processor (Braintree).
 What if we want to use a Braintree2 gem? Or switch to Stripe?

Introduce Gateways class Order def bill user_id = PaymentGateway.find_user(@user.email).id PaymentGateway.charge(user_id, @amount) end end class Refund def run transaction_id = PaymentGateway.find_transaction(@order) PaymentGateway.refund(transaction_id, @amount) end end

Introduce Gateways class Order def bill PaymentGateway.charge(@user, @amount) end end class Refund def run PaymentGateway.refund(@order, @amount) end end

Prefer gateways that have interfaces closer to the client code.
 Changes to the external service are then isolated in the gateway.

Summary Dependencies are powerful yet perilous Depend on abstractions using:
 - dependency injection
 - inversion of control
 - tell, don’t ask
 - gateways

Avoid Ordering Dependencies class Oven def initialize(temperature, duration) @temperature = temperature @duration = duration end end Oven.new(200, 30)

Avoid Ordering Dependencies class Oven def initialize(temperature:, duration:) @temperature = temperature @duration = duration end end Oven.new(temperature: 200, duration: 30) Oven.new(duration: 30, temperature: 200)

Avoid Ordering Dependencies class Oven def initialize(temperature: 200, duration:) @temperature = temperature @duration = duration end end Oven.new(temperature: 200, duration: 30) Oven.new(duration: 30, temperature: 200)
 Oven.new(duration: 30)

Designing and Maintaining Software (DAMS) - GitHub

Getting loose coupling. Designing and Maintaining Software (DAMS). Louis Rose ... should not depend on low-level modules. Both should depend on abstractions.” “Abstractions should not depend on details. Details should depend on abstractions.” - Bob Martin http://www.objectmentor.com/resources/articles/dip.pdf ...

107KB Sizes 0 Downloads 256 Views

Recommend Documents

Designing and Maintaining Software (DAMS) - GitHub
ASTs are tree data structures that can be analysed for meaning (following JLJ in SYAC 2014/15) ... More Cohesive. Avoids Duplication. Clearer. More Extensible.

Designing and Maintaining Software (DAMS) - GitHub
Open-source. Influenced by Perl, Smalltalk, Eiffel, Ada and Lisp. Dynamic. Purely object-oriented. Some elements of functional programming. Duck-typed class Numeric def plus(x) self.+(x) end end y = 5.plus(6) https://www.ruby-lang.org/en/about · http

Designing and Maintaining Software (DAMS) - GitHub
Page 1. Getting Lean. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Lean software… Has no extra parts. Solves the problem at hand and no more. Is often easier to change (i.e., is more habitable). Page 3. The Advice I Want to Give.

Designing and Maintaining Software (DAMS) - GitHub
Why not duplicate? Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Habitable Software. Leaner. Less Complex. Loosely Coupled. More Cohesive. Avoids Duplication. Clearer. More Extensible ??? Page 3. Bad Practice. Page 4. Don't Repeat Yo

Designing and Maintaining Software (DAMS) - GitHub
“We have tried to demonstrate that it is almost always incorrect to begin the decomposition of a system into modules on the basis of a flowchart. We propose instead that one begins with a list of difficult design decisions or design decisions which

Designing and Maintaining Software (DAMS) - GitHub
Tools: Vagrant. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Bugs that appear in production and that can't be reproduced by a developer on their machine are really hard to fix. Problem: “It works on my machine”. Page 3. Why does

Designing and Maintaining Software (DAMS) - GitHub
Clear Documentation. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Bad documentation. Misleading or contradictory find_customer(id). CustomerGateway. Used to look up a customer by their customer number. Page 3. Bad documentation. Red

Designing and Maintaining Software (DAMS) - GitHub
%w.rack tilt date INT TERM..map{|l|trap(l){$r.stop}rescue require l};. $u=Date;$z=($u.new.year + 145).abs;puts "== Almost Sinatra/No Version has taken the stage on #$z for development with backup from Webrick". $n=Module.new{extend. Rack;a,D,S,q=Rack

Designing and Maintaining Software (DAMS) - GitHub
R&D: sketch habitable solutions on paper, using UML. 4. Evaluate solutions and implement the best, using TDD. Probably start again at 3. 5. Give to the product owner to validate. Probably start again at 1. 6. Put into production for customers to eval

Designing and Maintaining Software (DAMS) - GitHub
Habitable Software. Leaner. Less Complex. Loosely Coupled. More Cohesive. Avoids Duplication. Clearer. More Extensible ??? Page 3. Lean. “Perfection is finally achieved not when there is no longer anything to add, but when there is no longer anythi

Designing and Maintaining Software (DAMS) - GitHub
Fixes issue #42. Users were being redirected to the home page after login, which is less useful than redirecting to the page they had originally requested before being redirected to the login form. * Store requested path in a session variable. * Redi

Designing and Maintaining Software (DAMS) - GitHub
Designing and Maintaining Software (DAMS). Louis Rose ... Loosely coupled software is… Flexible: the ... http://www.objectmentor.com/resources/articles/dip.pdf ... Monthly. Sales. Reporting. Sales. Data. Provider. MySQL. Database. Access ...

Designing and Maintaining Software (DAMS) - GitHub
What is it? Several pieces of data are often used together. Why is it problematic? Behaviour that operates on the clump has no home. (and consequently is often duplicated). When does it arise? High cohesion of the clump has not been detected. D

Designing and Maintaining Software (DAMS) - GitHub
Observers. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Page 3. Delivery people need to know when pizzas are ready class Pizza def initialize(delivery_person). @delivery_person = delivery_person end def bake cook # blocking call. @d

Designing and Maintaining Software (DAMS) - GitHub
“We want the reading of code to be easy, even it makes the writing harder. (Of course, there's no way to write code without also reading it, so…)” - Bob Martin. Clean Code. Prentice Hall, 2009. Page 5. Page 6. User Experience. “A person of av

Designing and Maintaining Software (DAMS) - GitHub
Automatically detect similar fragments of code. class StuffedCrust def title. "Stuffed Crust " +. @toppings.title +. " Pizza" end def cost. @toppings.cost + 6 end end class DeepPan def title. "Deep Pan " +. @ingredients.title +. " Pizza" end def cost

Designing and Maintaining Software (DAMS) - GitHub
Ruby Testing Frameworks. 3 popular options are: RSpec, Minitest and Test::Unit. We'll use RSpec, as it has the most comprehensive docs. Introductory videos are at: http://rspec.info ...

Designing and Maintaining Software (DAMS) - GitHub
Clear Names. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Naming is hard. “There are only two hard things in Computer. Science: cache invalidation and naming things.” - Phil Karlton http://martinfowler.com/bliki/TwoHardThings.ht

Designing and Maintaining Software (DAMS) - GitHub
Coupling Between Objects. Counts the number of other classes to which a class is coupled (other than via inheritance). CBO(c) = |d ∈ C - (1cl U Ancestors(C))| uses(c, d) V uses(d, c). - Chidamber and Kemerer. A metrics suite for object-oriented des

Designing and Maintaining Software (DAMS) - GitHub
Reducing duplication. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Tactics. Accentuate similarities to find differences. Favour composition over inheritance. Know when to reach for advanced tools. (metaprogramming, code generation).

Designing and Maintaining Software (DAMS) - GitHub
Plug-ins. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Problem. Page 3. Current Architecture. Shareable. Likeable. Food. Pizza. Liking and sharing foods are primary business concerns, so shouldn't be implemented as delegators. Page

Designing and Maintaining Software (DAMS) - GitHub
When we are testing the way that a unit behaves when a condition is met, use a stub to setup the condition. Solution: use stubs for queries class Subscription ... def bill(amount) unless payments.exists(subscription_id: id) payments.charge(subscripti

Designing and Maintaining Software (DAMS) - GitHub
Getting Cohesion. Designing and Maintaining Software (DAMS). Louis Rose. Page 2. Single Responsibility. Principle. A class should have only one reason to change. - Martin and Martin. Chapter 8, Agile Principles, Patterns and Practices in C#, Prentice

Designing and Maintaining Software (DAMS) - GitHub
Size != Complexity. “Imagine a small (50 line) program comprising. 25 consecutive "IF THEN" constructs. Such a program could have as many as 33.5 million distinct control paths.” - Thomas J. McCabe. IEEE Transactions on Software Engineering, 2:4,