Collaborative Modelling (CoMo) Lab

TL;DR: CoMo brings together modern, industry-proven collaborative techniques to do the essential things experienced analysts, designers, and architects have long recommended and practiced with clients — sometimes under different names, notations, or perspectives.

As humans, we are constantly surrounded by models. They appear in research, engineering, business, and society at large. Every road or hiking map is a model; software systems abstract and represent parts of the real world and are therefore models as well. Models are not only tools for gaining insight in research — they are also used to design and improve products, software, and devices we use every day. We model for many different reasons: to capture and structure knowledge about a new domain, to document workshop outcomes, to specify requirements or designs, to align understanding within and across teams, to validate and verify implementations, and much more.

Modeling is often a collaborative activity, frequently carried out in interdisciplinary teams. However, not every audience immediately understands what a colored rectangle or a dashed line in a diagram is meant to convey. Modeling literacy helps people navigate todays world, interpret models correctly, and make informed design and usage decisions.The CoMo practices listed here can all provide input for conceptual data modeling; either directly or via Domain-Driven Design (DDD) as an intermediate step.

Collaborative approaches taught in the CoMo Lab:

 

Running Case: Fair Game 3002
To make the methods tangible, the lab revolves around a continuous case study, “Fair Game 3002”. This fictional but realistic digital platform supports sharing, selling, and playing computer games. The platform aims to create fair and transparent conditions for both gamers and independent game developers, while avoiding manipulative design patterns and taking ethical and societal impacts into account. Throughout the lab, students model this scenario from business vision down to system design, applying a sequence of collaborative modeling practices.

Materials & Access
On this learning platform, you will find slide PDFs and the lab exercises in the student version (no lecture notes or solutions). The source materials and full documentation are maintained on GitLab: https://gitlab.ost.ch/cal/collaborative-modelling-lab If you need access to the repository, please contact Stefan Kapferer.

TopicSlidesLab
Lab Overview / IntroSlidesLab 0
Product VisionSlidesLab 1
Domain Storytelling (DST)SlidesLab 2
EventStormingSlidesLab 3
Story Mapping and SplittingSlidesLab 4
Ethical SE: Stakeholder and Value Impact MappingSlidesLab 5
From CoMo to OOAD/DDD/OOP(siehe Repo; Entwurf)Lab 6
Big Picture and Transision(siehe Repo; Entwurf)Lab 7
Metadaten
Version
Bloomsche Taxonomy
  • K2 - verstehen
  • K3 - anwenden
  • K4 - analysieren
Sprache
  • Englisch
Anzahl Lektionen 7
Art des Unterrichts
  • Vorlesung
  • Übung (ohne Labor/Werkstätte)
  • Labor- oder Werkstatt-Übung
Voraussetzungen
Vorbereitungen, Bedingungen
Lernziele

Participants are able to:

  • Develop overall modeling competence and method awareness by learning when and why to use different collaborative modeling techniques, how they complement each other, and how to adapt them effectively in real projects.
  • Shape and communicate a clear product vision grounded in business goals, stakeholder needs, and differentiating value, and understand how that vision drives requirements and design decisions.
  • Model domains collaboratively using a shared visual language, turning real-world scenarios into structured representations of actors, activities, and work objects that bridge business understanding and software requirements.
  • Explore and structure business processes through events, commands, and system reactions in order to uncover domain behavior, responsibilities, and meaningful system boundaries.
  • Translate domain insight into a value-driven, navigable product backlog by using story mapping and story splitting to move from big-picture user journeys to small, implementable, high-quality user stories.
  • Incorporate ethical and stakeholder perspectives into design by identifying stakeholder groups, surfacing value conflicts, and deriving value-based requirements alongside functional and technical ones.
  • Transform analysis models into software design artifacts by evolving collaborative models into object-oriented analysis and design, UML representations, and Domain-Driven Design structures that support traceable architectural decisions.
  • Connect detailed models to the broader technical and organizational landscape by relating CoMo results to architecture, programming, business process modeling, database design, and other engineering practices.
Autor Kapferer, Stefan
Co-Autor:innen

Zimmermann, Olaf

Original-Studiengang Informatik
. Semester
Dateien
Zip-Datei 4066 (Typ: application/zip)

Der Lerninhalt ist schwierig!/The learning content is difficult!

No votes yet.
Please wait...

Der Lerninhalt ist praxisorientiert!/The learning content is practice-orientated!

No votes yet.
Please wait...

Das Material unterstützt mich!/The learning material supports me!

No votes yet.
Please wait...

Schreiben Sie einen Kommentar

Ihre E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert

Nach oben scrollen