System Architecture

Well defined elements and generic interfaces, gives a solid architecture

LEGO is a good example on well-designed objects with a generic interface. Basic objects used in numerus variation to create complex models.

Always through change of object attributes only.

“Individuals and interactions over processes and tools”

  • All objects can be combined in more than one way

  • Attributes only controls size, shape, and color

  • Numerus variations of small objects builds a complex model

LEGO concept used in system architecture combined with Agile thinking creates possibilities to build on knowledge instead of predictions

and handle changes repetitive based on feedback. Traditional approach to software development is often defined as process that follows

a design described by a blueprint. Agile system design is an iterative, four-step approach to process improvement referred to as the PDSA.

  • Plan, what do we want to achieve and why?

  • Do, how do we iteratively build minimum viable product (MVP)

  • Study, present and collect feedback.

  • Adapt, use feedback, and embrace change!

Architecture based on a rough plan on how to build a system on small well-defined objects, which fulfills a goal based on what to achieve

can give the impression of an incomplete architecture. An Agile empirical process model builds on existing and increasing

knowledge that guarantees a stable build of a minimum viable product that saves time and resources.

Trust in small elements to build complex systems