BEGIN:VCALENDAR
VERSION:2.0
PRODID:icalendar-ruby
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART:20220313T030000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20211107T010000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20260422T134035Z
UID:pMlz0Q
DTSTART;VALUE=DATE:20211208
DTEND;VALUE=DATE:20211218
CLASS:PUBLIC
CREATED:20210918T181146
DESCRIPTION: System Design Workshop for software architects and other syste
 m designers . These will all have async work co-ordinated over Slack\, and
  in-class work\, co-ordinated over Zoom\, on: \n\n \n December 8-10 and De
 cember 15-17\, 8 am - 12 pm Eastern Time ( 6 x 4 hr sessions) \n \n\n Over
 view\nWe work in small teams on creating a draft architecture\, and lectur
 e topics are driven by the concerns that are being addressed as we do so. 
 This allows us to work on shaping a system design\, moving from exploring 
 the system concept to architectural definition\, weaving guidance\, discus
 sion and practice.\nAs we iterate through architecture design with its tra
 de-offs\, decision making\, modeling and specification\, we grapple with: 
 \n\n \n system design: systems concepts\, uncertainty and complexity\, con
 text\, framing\, constraints\, forces and trade-offs. \n system capabiliti
 es and properties: understanding needs/concerns and designing system capab
 ilities and system properties including run-time qualities such as scalabi
 lity and reliability\, and development-time qualities such as evolvability
 /extensibility. \n architectural patterns: structural patterns such as lay
 ers\, hexagonal architecture\, and microservices\, and mechanisms that may
  be architecturally significant in various contexts. \n systems and archit
 ecture modeling including an introduction to (just enough\, as relevant) U
 nified Modeling Language (UML) and C4\, but drawing on other templates and
  modeling as appropriate to the design stage and its decision focus. \n ar
 chitectural views: structural views help document and communicate the arch
 itecture in terms of the components and their relationships\, and are usef
 ul in assessing architectural qualities like extensibility. Behavioral vie
 ws are useful in thinking through how the components interact to accomplis
 h their assigned responsibilities and evaluating the impact of what-if sce
 narios on the architecture. Behavioral views are especially useful in asse
 ssing run-time qualities such as performance and security. Execution views
  help in evaluating physical distribution options and documenting decision
 s. \n component specification\, interfaces and APIs: components are identi
 fied and assigned responsibilities\, and interfaces are designed. \n key a
 rchitectural design principles and heuristics\, including abstraction\, se
 paration of concerns\, postponing decisions\, and simplicity\, and related
  techniques such as interface hiding and encapsulation\, as well as system
  decomposition principles\, factoring and refactoring\, and good interface
  design. \n architecture improvement: we pause periodically to consider wh
 at it means to improve and evolve systems and their design\, and why\, whe
 n and how to do that. \n \n\n Instructor: Ruth Malan \n\n More information
 : www.ruthmalan.com \n
LAST-MODIFIED:20211207T084721
LOCATION:Remote
ORGANIZER:mailto:training@bredemeyer.com
SUMMARY:System Design Workshop December 2021
URL;VALUE=URI:https://ti.to/bredemeyer/system-design-dec-2021
URL;VALUE=URI:https://ti.to/bredemeyer/system-design-dec-2021
END:VEVENT
END:VCALENDAR