addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Software Architecture Decomposition

  • Sep 30, 2014 · 5:30 PM
  • This location is shown only to members

IDesign's approach to large system analysis design is by using volatility to decompose a system into its comprising services, contrasting it with the most common mistake done in architecture, using functionality to identify services. You will also see how to overcome the real hurdles architects face perusing volatility-based decomposing, simple and practical techniques for identifying areas of volatility, common telltale signs or "smells" when your design is still functional when using the Method, IDesign's approach for system architecture.

The session includes demos.

Join or login to comment.

  • Stuart C.

    Sadly a diary conflict has forced me not be able to make this meetup.

    Good luck and I hope it goes well.

    September 30, 2014

    • Russ C.

      Sadly I can't make it tonight. Best of luck tonight and hope to see you at the next one.

      September 30, 2014

25 went

Our Sponsors

  • Fishburners

    Australia's largest startup space hosts our event

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy