DAARIUS methodology

The DAARIUS methodology is a structured, scalable, and team-based system design methodology. It provides traceable underpinning for key design decisions and uses the simple executable models available in the systems engineering.

Benefits of the DAARIUS methodology are that:
    • it quickly provides a system overview with an understanding of what is key and where the trade-offs are;
    • it enables understanding the business and system consequences of system design decisions,
      via explicit reasoning;
    • it delivers a systematic system design approach with a consistent system representation.

In organizations, complexity is increasing on multiple levels: business, system, technology, processes, and organizational level. In this increasingly complex environment, the challenge is to make business-critical decisions. This requires reasoning about system aspects/qualities across disciplines and departments.

The DAARIUS methodology offers a systematic, team-based way-of-working. This includes the capturing and organizing existing knowledge in an organization. This knowledge can be decomposed into a central set of system views, stakeholder views, individual domain views, and building blocks views. In these views ownership for these parts of the system can be explicitly defined. Between these views, relations and dependencies can be made explicit, by using selected parameters of the system. The use of simple, executable models is leveraged for analysis, to make trade-offs and decisions. The captured knowledge, its relations, and analyses enable clear communicating and collaborating across disciplines in the system design team.

Reasoning, communication and decision making for system design

The Daarius methodology consists of a method, a structure, a language, and the DAARIUS tool. The language is the formalism used to express the system in the system structure. The structure restricts and organizes the information to keep it understandable, it provides multiple levels of abstraction and contains views for the knowledge domains. The DAARIUS method describes the steps to come to this organized information. Finally, the DAARIUS tool supports the formalism and the structure, such that information can be recorded, to reduce the storage effort and additionally support executable models.


DAARIUS methodology including a process, structure, formalism, and the supportive DAARIUS tool.

The DAARIUS methodology has been developed in the CANVAS project.


  • 2019 - A3 for DAARIUS methodology download
  • 2019 - A DAARIUS methodology example: a design trade-off exploration for an e-bike download video
  • 2019 - DAARIUS system design workshop download
  • INCOSE Dutch System Architecting Conference¹ download

Scientific publications
    • 2019 - Decision support methodology for evolutionary embedded system design, IEEE ISSE conference
    • 2019 - A knowledge domain structure to enable system wide reasoning and decision making,
      CSER conference doi

Articles (Dutch)
    • 2017 - Het architectenspel¹ - Mechatronica Machinebouw, see publication
    • 2017 - Jongleren met specs² - Mechatronica Machinebouw, see publication

Other Documents
    • 2018 - Model-Based System Architecting¹: 'Cook Book' for Dilemma Exploration download
    • 2018 - Model-Based System Architecting¹: 'Cook Book' for Dilemma Exploration with
      DAARIUS tool instructions download
    • 2017 - DAARIUS tool download   
    • 2017 - MBSA explanation video
    • 2017 - Model-Based System Architecting¹ - poster ESI symposium download
    • 2017 - Windfarm - poster ESI symposium download
    • 2017 - MBSA¹ - poster ESI symposium download
    • 2017 - DF tool² - poster ESI symposium download

¹ Previously the DAARIUS methodology was called Model-Based System Architecting (MBSA)
² Previously the DAARIUS tool was called Design Framework (DF)


+31 88 866 54 20 (secretariat)
Tjerk Bijlsma
Richard Doornbos
Wouter Tabingh Suermondt

Richard Doornbos

+31 (0)88 866 54 20 (secr)

“I’m interested in systems architecting and architectures in the broadest sense, architecting methods, and model-based development.”