This document discusses bringing software architecture back into agile development processes. It proposes using lightweight documentation approaches like wikis, diagrams, and architecture decision records to capture essential architectural information. This ensures compliance with standards like those for medical device software while maintaining an evolutionary approach. Tools are suggested to integrate architecture documentation into existing developer workflows and provide oversight for compliance officers.

1. Bringing the Software
Architecture back into Agile
Vlad Știrbu
APIdays Finland
CompliancePal@VladStirbu

2. CompliancePal
Software is eating the world
Marc Andreessen
https://a16z.com/2016/08/20/why-software-is-eating-the-world/
https://earthobservatory.nasa.gov/images/82693/earthrise-revisited

3. CompliancePal
https://www.dlr.de/dlr/en/Portaldata/1/Resources/bilder/portal/xl_galerie/STS_135_Launch_16_9_xl.jpg
Software intensive products
2015
DevOps
Today
DevOps ++
1970
Waterfall
2001
Agile

4. CompliancePal
Model Driven Architecture
UML
CASE tools

5. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
CompliancePal

6. CompliancePal
Wikis
UML-ish Diagrams

7. “Documentation is not real work.”
(not to be named) Lead Front-End Developer
CompliancePal

8. ISO 62304: Medical software development life cycle
CompliancePal

9. The Documentation Sprint
CompliancePal
Requirements
Wikis
Commits
Configurations
Tests
Containers
Deployments

10. The Documentation Sprint
CompliancePal

11. https://twitter.com/rsiilasmaa/status/849940433358778369
CompliancePal

12. Software as Medical Device Certification
CompliancePal

13. Visualising software architecture with C4
System Context - how the software system fits into the world around it
Container - the high-level technical building blocks
Component - the components inside an individual container
Code - how that component is implemented.
CompliancePalhttp://c4model.com

14. Practical architecture management with C4
{
“info”: {
“version”: “1.0.0”,
...
},
“elements”: [
{
"id": "patient",
"name": "Patient",
"description": "The patient that uploads the data",
"type": "person",
"location": "external"
},
...
],
“relationships”: [
{
"source": "patient",
"destination": "service",
"description": "Uploads measurements"
},
...
]
}
CompliancePal

15. Lightweight Architecture Decision Records
CompliancePal
In a world of evolutionary
architecture, it's important to
record certain design
decisions for the benefit of
future team members as well
as for external oversight.
http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions

16. Custom workflows for collecting ADR
CompliancePal

17. Custom workflows for collecting ADR
CompliancePal

18. Custom workflows for collecting ADR
CompliancePal

19. Seamless experience
GitHub CompliancePal
Developer/
Architect
Compliance
Officer
commit
notification
checks
Team chat
problems
view
Backlog
compliance issues
status
CompliancePal

20. Software architecture is not just
diagrams. It provides the context
for tooling, and improves the
transparency within team and with
external stakeholders.
CompliancePal

21. vlad@compliancepal.eu
@VladStirbu
CompliancePal