A presentation given at the DDD meet-up in New York on January 5th, 2011. Should be a good introduction to DDD for teams with lots of legacy software stuck in various stages of the software a death cycle.

1. Breaking the software death cycle SPIRAL march with DDD Daniel doubrovkine | Jan 2011 @dblockdotorg application security, inc. http://code.dblock.org 1

4. Enterprise product #fail “This failure is a management problem. Sales needed new features. Product management designed the features. My team implemented the features that product management told me to implement. It got harder to add new features. It was their fault.” - K. 4

6. Talking about #fail at your daily espresso venue

7. Pride in shipping, not in the product

8. Sum of individuals is far larger than progress of company

9. Discussions about other companies hiring in the open

10. Outlook and face-to-face procrastination

11. Blind faith in open headcounthttp://programmers.stackexchange.com/questions/25181/what-are-the-symptoms-events-or-actions-of-a-software-death-cycle 5

12. Breaking the death cycle 6

14. Your goal is a product you can be proud of

17. Wiki 9

19. wiki 11 http://appseclink/prodmanagement/DbProtect%20Ranger%20Wiki/Asset.aspx

21. WIki 13 http://appseclink/prodmanagement/DbProtect%20Ranger%20Wiki/Forms/EditForm.aspx?ID=407

23. wiki 15 http://appseclink/prodmanagement/DbProtect%20Ranger%20Wiki/Object%20Privilege.aspx

25. wiki 17 http://appseclink/prodmanagement/DbProtect%20Ranger%20Wiki/Principal.aspx

27. Write a user story

28. Refactor agreed-upon taxonomy

29. Have a place to start next time!18

30. wiki 19

34. Defined ‘endpoints’ as connection information (eg. IPv4 address).

35. Organized endpoints in ‘profiles’ to submit to jobs.

37. Knew that ‘job managers’ edit connection information.

38. Learned that credentials are never used separately from connection information.

39. Merged credentials into endpoints.23

41. Knew that the system connects to assets.

42. Learned that the system connects to databases, operating systems, WMI, remote registry using different protocols.

43. Learned that those ‘things’ have a lot in common and called it ‘asset service’.

44. Cohesion: asset service already existed from search context!24

47. fits naturally with agile teams

48. requires participation of people and a significant commitment in time

49. extremely simple and efficient barrier between pigs and chickens26

50. questions 27 Daniel Doubrovkine | Jan 2011 @dblockdotorg application security, inc. http://code.dblock.org