• Program
  • Day 1
  • Day 2
08:50 AM - 09:00 AMIntroduction
09:00 AM - 10:00 AMThe Role of The Architect By Barry O'Reilly & Daniella Eklund

Interactive Keynote

10:30 AM - 11:30 AMThe Rise and Fall and Rise of Artificial Intelligence By Grady BoochIBM Fellow

Speaking remote

It is perhaps in the very nature of our humanity that we seek to build machines in our own image. The history of computing is filled with attempts to do so, and even today, fueled by a perfect storm of an abundance of data, access to extraordinary amounts of computational power, and advances in neural algorithms, we see such efforts renewed. In this presentation, I’ll look at AI through the lens of software architecture: how it has evolved, what has worked and what has not, and what remains to be done.

11:30 AM - 12:30 PMThe Lost Art of Software Modelling By Simon BrownAuthor "Software Architecture for Developers" | Creator of the C4 software architecture model and the founder of Structurizr

”Big design up front is dumb. Doing no design up front is even dumber.” This quote epitomises what I’ve seen during our journey from ”big design up front” in the 20th century, to ”emergent design” and ”evolutionary architecture” in the 21st. In their desire to become ”agile”, many teams seem to have abandoned architectural thinking, up front design, documentation, diagramming, and modelling. In many cases this is a knee-jerk reaction to the heavy bloated processes of times past, and in others it’s a misinterpretation and misapplication of the agile manifesto.

As a result, many of the software design activities I witness these days are very high-level and superficial in nature. The resulting output, typically an ad hoc sketch on a whiteboard, is usually ambiguous and open to interpretation, leading to a situation where the underlying solution can’t be communicated, assessed, or reviewed. The same is true of long-lived documentation, which is typically a collection of disconnected diagrams that are out of sync, and out of date. Modelling can help resolve many of these problems, but that’s a tough thing to sell to mainstream developer audiences these days – teams are either not aware of modelling, or they associate it with bad experiences using complicated CASE tools from the past. Join me for a discussion about the lost art of software architecture modelling, and my experiences of how it can be reintroduced to the agile generation.

01:30 PM - 02:30 PMArchitectural Mistakes in Cloud Computing By Magda Wojnarowska-PietrzakCloud and Infrastructure Architect

Public cloud adoption has increased rapidly in recent years due to its convenience, scalability and agility. Despite many benefits, being in a rush to adopt cloud technologies, leads to architectural mistakes that may result in poor performance, security vulnerabilities, and increased costs. Cloud’s ease of use comes with a potential for mistakes that can have consequences. In this presentation, I will discuss common mistakes occurring during a cloud adoption.

I will highlight the mistakes in areas like costs, network, security, monitoring, roles and responsibilities. I will also provide some insights about organizational pitfalls that may occur along the way.

Through this presentation, you will gain a better understanding of the potential problems concerning the public cloud and learn what to consider for designing a cloud architecture. By taking a proactive approach, you can ensure a secure, efficient, and cost-effective cloud environment for your business needs.

03:00 PM - 04:00 PMData Science as Software Engineering By Megan BloemsmaData Scientist turned Software Engineer at Microsoft

Data science has been booming! ChatGPT fills your feeds and there are self-proclaimed ’AI experts’ everywhere. But does data science actually add value for companies?

In this talk we’ll take a look at how we got to this point, share experiences of implementing data science projects at companies and discuss how software engineering will play a key role in its future.

04:05 PM - 05:05 PMTechnical Neglect By Kevlin HenneyIndependent Software Development Consultant, Trainer, Speaker and Writer

Many developers evoke the mischievous spirit and day-to-day burden of technical debt to explain the misfortunes and troubles of their codebase and delivery. While unmanaged technical debt weighs down an architecture and exerts drag on its schedule, it is more often an effect than a cause. In this talk, we will look at what is and is not meant by technical debt — and other metaphors — with a view to properly attributing the root and recurring cause as technical neglect than technical debt. Without seeing technical neglect for what it is, we will continue to misattribute our problems to an effect rather than a cause.

05:30 PMDinner & Mingle
09:00 AM - 12:00 PM// WORKSHOP // Lean Coffee By IASA Sverige

In Swedish.

Vi inleder med en introduktion till vad Iasa är och senaste status på Iasa:s nya bok.

Det går inte alltid som man tänkt sig…

Men, det gäller att dra lärdom och även förmedla sina erfarenheter till andra. I denna workshop kommer workshopledarna dela med sig av tillfällen när det inte gick så bra och vilka lärdomarna blev. Därefter kommer vi i mindre grupper även detta år köra Lean Coffee. Vilka ämnen som diskuteras bestämmer ni som är med på workshopen, men förslag runt ämnet ”Det går inte alltid som man tänkt sig” kommer finnas.

Välkommen till en intressant och givande workshop i sann Lean Coffee-anda!

Har du inte möjlighet att delta men ändå vill testa på Lean Coffee så håller Iasa virtuella Lean Coffee med jämna mellanrum. Du hittar dem på LinkedIn under Iasas:s kanal/grupp.

09:00 AM - 12:00 PM// WORKSHOP // Designing Intentional Group Experiences as an Architect 🌱 By Dan YoungWhen & How Studios

In English.

This workshop delivered by Dan Young and co-designed with Mike Rozinsky from When & How Studios supports architects, consultants or others who have the responsibility of convening meetings, workshops or other group-work within their organisations or clients. The material taught in this session has been developed from Dan & Mike’s conversations and experiences, during thousands of hours spent designing and delivering events with individuals and organisations all over the world.

What will you get from this?

Perhaps you are…

– Looking for a mental model to help you approach meetings or workshops ?

– Curious about the potential of bringing participation into your presentation style?

– Keen to challenge your default way of preparing for events?

– Wanting to feel more confident and prepared when you walk into the room, or the Zoom?

Join us to further your group-work design practice by thinking more deeply about how to be intentional, leveraging the When & How Studios 16 Design Aspects as a guide.

To get the most out of the workshop, please bring something to take notes in and ideally a laptop or other device to access online materials or resources.

09:00 AM - 12:00 PM// WORKSHOP // How Do You Know an Architect is an Architect? By Barry O'Reilly & Tanya O'ReillyCreator of ”Residuality theory" / Educational Consultant

In English.

This workshop investigates the question of assessment and certification. How do you know that the person you’re interviewing actually is an architect? How do you know they can deliver across various projects? How do non-technical hiring managers and project managers know that a candidate has real architectural knowledge? In this session two researchers – one in architecture and one in educational assessment will discuss novel ways of establishing credentials and assessing architectural knowledge. 

09:00 AM - 12:00 PM// WORKSHOP // EA Modeling using C4 and ArchiMate By Anders Larsson & Martin SvenssonDomain Architects & members of the EA function at Inera

In English.

Like the saying “A picture is worth a thousand words”, Inera found that “An Enterprise Architecture model says more than a thousand Excel matrices”. To express an Enterprise Architecture (EA), the most crucial decisions are to select a suitable modeling-language and -tool. We discovered that the ArchiMate language and the tool Archi met all our functional and non-functional requirements, completely for free. When it came to expressing the software architecture aspect of our software systems, we had a bit of a struggle. ArchiMate is a bit too flexible and complex for us architects to use in a consistent way, which became confusing for our non-technical users. C4 came to the rescue, it’s not as flexible and complex and way more intuitive. And since it’s designed to be notation- and tooling-independent, we could easily introduce it into our model.

In this workshop, we will teach you how to express software architecture with C4 notation in ArchiMate. And how to relate it to other aspects of the EA. We will begin with a presentation and end with practical work in the Archi modeling tool.

Bring your own device for the practical work and, if you already have Archi installed, you will get a flying start. (https://www.archimatetool.com/)

12:50 PM - 01:50 PMAI in the service of democracy By Anders ArptegAI engineer, Scientist and Investor

The Swedish Security Service has been scaling up the data and AI efforts in recent years, but why and how can AI be used by the service? Many organizations want to scale their digitalization and AI capabilities, but how can these capabilities ”scale with style?” AI has been around for over 70 years, but why is it accelerating at an exponential rate today? How are investments in AI being made in different parts of the World, and how do the Swedish and European investments compare? These are some of the questions that will be addressed in this talk, in the context of using AI in the service of democracy.

01:50 PM - 02:50 PMModelling and Reality By Einar W. HøstSoftware Developer

To make sense of the world, we rely on our brains’ capability to form fictions that we call ”categories” of things and experiences. This capability is both automatic and hidden: we can’t avoid doing it, yet we don’t know exactly how we do it. We know that differences and similarities play a role, but how? When we try to be more deliberate about the process, for instance because we want to write software based on our categories, we call it modelling. In the process, we tend to replace our intuitive but ill-defined common-sense categories with more precise technical categories. But precision comes at a cost. In this talk, we’ll look at different perspectives on categorization, see that nothing remains the same for long, and that edge cases are just regular cases that got unlucky.

03:15 PM - 04:15 PMOrder and Emergence: Self-Organisation in Nature By Dr Riccardo M Bennett-LovseyCTO, Architect and Technical Lead

No one can predict the future, least of all software engineers. As our society bears witness to an age of increasing complexity, how does one even begin to judge the validity of today’s KPI/OKR/KRA/TLA against the backdrop of the unpredictable?

Mother Nature takes a simpler approach: do what you can and try not to die. While the rest of the cosmos marches down the inevitable path towards maximum disorder, Nature seemingly never stops creating expansive islands of ever-increasing order. By exploring the boundaries of mathematics and chaos, structure and self-organisation can be found everywhere from economics and social networks, to chemistry and biology. But how is this possible?

This talk highlights several key ideas that have emerged over the past century, and tells the story of how Nature evolves, reacts and experiments to create amazing structures, limited only by the universe itself. On our journey, we will explore the awesome power of weather systems, the elegance of the human brain, the unfair reputation of waterfalls, and the reasons why pandas are pointless.

Barry O'Reilly
04:15 PM - 05:00 PMArchitecture as Difference and Repetition By Barry O'ReillyFounder of Black Tulip Technology and creator of ”Residuality theory"

It turns out that the never-ending discussion on ”What is architecture?” is almost 3000 years old. This session will use aspects of 20th century continental philosophy to explain why traditional architectural approaches should never work, why they sometimes do despite themselves, and what we should be doing instead.