Contract First Design: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "http://www.scrum-breakfast.com/2013/06/xm-principle-4-contract-first-design.html When designing a solution: *Design the interfaces based on outside parameters, e.g. load fac...")
 
No edit summary
Line 1: Line 1:
http://www.scrum-breakfast.com/2013/06/xm-principle-4-contract-first-design.html
http://www.scrum-breakfast.com/2013/06/xm-principle-4-contract-first-design.html
This means design the interface between modules first - not the modules themselves.


When designing a solution:
When designing a solution:

Revision as of 14:10, 11 June 2013

http://www.scrum-breakfast.com/2013/06/xm-principle-4-contract-first-design.html

This means design the interface between modules first - not the modules themselves.

When designing a solution:

  • Design the interfaces based on outside parameters, e.g. load factors, or communication and power requirements.
  • Only architect the connections up front, not the individual components.
  • Leave room to grow, i.e. over engineer these interfaces, because changing these fundamental contracts may be expensive.