Visualizing
Software Architecture
with the C4-model
Haarlem Software Developer Meetup
@mcbeelen
KvK 53479335
Lichtfabriekplein 1, 2031 TE Haarlem
P.O. Box 2031 , 2002 CA Haarlem
+31 (0)88 248 1632,
info@ximedes.com
www.ximedes.com
Meetup
Sponsor:
Agenda
1. Introduction
2. Presentation from YouTube by Simon Brown
3. Drawing Session
4. Show drawings and retro
Visualizing
Software Architecture
with the C4-model
Visualization is
any technique for
creating images, diagrams,
or animations
to communicate a
message
It’s about the questions,
where if you get the
answers wrong
it might just be
the end of your
.... project!
.... product.
.... carrier?
Architecture represents
the significant design decisions
that shape a system,
where significant is measured
by cost of change
Grady Booch
Best known for developing UML
with Ivar Jacobson and James Rumbaugh
What is Software Architecture?
Software application architecture is the
processof defining a structured solution
that meets all of the technical and operational requirements,
while optimizing common quality attributes
such as performance, security, and manageability.
It involves a series of decisions based on a wide range of factors,
and each of these decisions can have considerable impact
on the quality, performance, maintainability, and overall success of the application.
1: Why
2: What
3: How
Feature:
Document the Software Architecture
In order to ……
As a …….
I want to ……
Scenario:
Scenario:
Target Audience
http://www.disciplinedagiledelivery.com/
https://www.youtube.com/watch?v=Ym9nhVZs89o
Drawing
https://structurizr.com/express
Text to Image Code to ImageBy Hand
Auxiliary Tools
www.websequencediagrams.com
https://erdplus.com
www.planttext.com
Credits
Simon Brown (@simonbrown)
http://www.codingthearchitecture.com/
https://c4model.com/
https://leanpub.com
/visualising-software-architecture
/c/HaarlemSoftwareDevelopmentMeetup

Visualizing Software Architecture with C4 Model

Editor's Notes

  • #6 A image is worth more then a thousand pictures. Some techniques are cheap, some are more expensive
  • #7 Nice quote from …. Well I could remember nor find in in my twitter timeline. You are allowed to contributed to me, but….
  • #8 Spend significant time on enabling us to ‘write down aspects of our software architecture’
  • #10 What are we going to document? At least the outcome, I hope. Some of the input: Requirements, Measurements, Estimations, Assumptions.
  • #11 Working software over comprehensive documentation Agile Manifesto
  • #12 Developers! Me, myself and I in distinct moments in time. Future new developers. Stakeholders?
  • #14 While there is value for the bottom items, I value the items on the top more!