Agile Architecture

1. Agile Architecture Odessa Johannes Brodwall, Chief scientist Exilesoft Global

2. What is an architect? From greekArkhi-Tecton Tecton: Builder Arkhi: Chief. Like “Arch angel” Or “Arch nemesis”

3. What is an architect? “Chief builder”

4. What is an architect? (Exilesoft definition)

5. A solution architect is someone who understands the problem of the customer and uncoversand communicates a feasible solution

6. A solution architect is someone who understands the customer’s problem (including contraints, context, domain knowledge) and uncovers (though a team effort) and communicates (with credibility) a feasible solution (primarily, but not exclusively technical)

7. Uncover problemvision, stakeholders, usage flow Describe problemcontext and domain model Describe solutiondeployment, implementation model Simplify architecturefeature oriented structure Deliver softwarerainbow plans

8. Describing architecture Simplifying architecture Delivering architecture Delivering software • Delivering architecture

9. Part I:

10. Describing architecture

11. Understanding problem Uncovering solution Communicating architecture

12. Understanding the problem

13. (Tool time)

14. For some stakeholder Who has a goal The Odessa agile user group (?) Is a type of activity Which gives a capability. Unlike most relevant alternative This has a distinguishing attribute.

15. For __________________ Who ________________ The Odessa agile user group (?) Is a _________________ Which ________________. Unlike ______________________ This _______________________.

16. Example «Smidig» conference application

17. Example vision statement

18. For Agile practitioners Who need to expand on their experience and network TheSmidig conference Is a networking event Which connects you with other Agile practitioners. Unlike traditional conferences Thispresents the experience of many people through lightning talks.

19. For Conference organizers Who want to organize a good conference TheSmidig conference app Is a web application Which eliminates unnecessary work. Unlike commercial conference apps Thisis optimized for the large number of talks we have and allows us to make changes fast.

21. Example stakeholders

22. Organizer Attendee Description Volunteer Works in evenings Has network Description Experienced New speaker Passionate Description Knows about agile Works in project Norwegian Speaker Duties Select talks Follow up payments Duties Register talk Upload slide Give talk Duties Pay for conference Get approval to go Values Easy selection process Good information overview Never lose a participant Financial transparency Values Constructive feedback on talk Easy CfP Fast answer Values Easy registration

23. Sponsor Description Busy Manager Not very interested Duties Provide logo Pay sponsorship Values Informal communication Easy evaluation

24. Example usage flow

25. Attendance • Agile project practitioner wants to learn • Attendee goes to Smidig website • Attendee registers • Attendee pays • Attendee receives confirmation mail • Organizer can see the registration • Organizer sends reminder email to attendee to come • Organizer prints badges for attendees • Attendee shows up at Smidig and has an excellent time

27. Speaker • Agile experts wants to share knowledge • Potential speaker goes to Smidig website • Potential speaker registers personal info • Potential speaker registers talk • Potential speaker receives registration confirmation email • Organizer sees registered talk and can market speaking opportunities • Organizer accepts talk for confence • Speaker receives acceptance email • Alternative: Speaker withdraws talk – organizer updates the talk and selects another • Organizer prints badges for speakers • Speaker shows up at Smidig and gives talk

28. /Understanding the problem

29. Uncovering a solution

30. Example context model

31. Paypal Smidig2011.no Printing company Participant Speaker Organizer

32. Example domain model

33. User • Name • Email • Company • Phone • Password • Accepts email? • Registration • Ticket type • Price • Paid amount • Paypal ref • Payment date • Invoice address [optional] * * • Comment • Title • Text • Created date Speaker * * • Talk • Title • Description • Tags[] • Slide file • Status : {pending, accept, reject} • Email_sent • Position • Period • Stage • Title • Time of day • Day

34. Example deployment model

35. html/http Heroku git push git pull git push Smidig-conference (Rails) Paypal http github git.heroku smtp Web user Developer Smtp.dreamhost.com PostgreSQL smidigdb

36. Example implementation diagram

37. Paypal.com Browser Smidig2012.no 1. POST /users Save user info 2. Redirect to paypal with return_url and notify_url 3. Perform payment 4. POST /payment_notifications Update user info 5. Redirect to return_url 5. GET /user/<id> Show user info

38. /Uncovering a solution

39. Communicating a solution

41. Vision Stakeholders Usage flow Context Domain model Implementation Deployment

42. Does the architect have to do this herself?

43. Team effort

45. /Communicating a solution

46. /Describing architecture

47. Part II:

48. Simplifying architecture

49. Lasagna architecture Feature oriented architecture Deployment constraints

50. Lasagna architecture