This document proposes that modeling should become an independent scientific discipline to better realize its full potential. Currently, modeling is seen primarily as a tool within software engineering, but it is applicable across many domains. An independent modeling discipline could bring together experts from different fields, develop a common body of knowledge and terminology, and help modeling gain more recognition and resources. Some initial steps suggested include making modeling tools more usable and accessible across domains, identifying economic benefits to promote adoption, and facilitating interdisciplinary publishing and education around modeling concepts and applications. The overarching goal is for modeling to serve all domains through a transdisciplinary approach.

1. Modeling should be an independent
scientific discipline
@JordiCabot / jordicabot.com / modeling-languages.com
Jordi Cabot, Antonio Vallecillo
Cabot, J., Vallecillo, A. Modeling should be an independent
scientific discipline. Softw Syst Model (2022).
https://doi.org/10.1007/s10270-022-01035-8 (Open access)

2. My background (as it affects my
perspecitve)

3. SOM research lab -
Our mission
Interested in the broad area
of systems and software
engineering, especially
promoting the rigorous use
of software models and
engineering principles in
all software engineering
tasks.
Flickr/clement127

4. Why this reflection?

5. Need to reclaim the key role of modeling
and bring it into the limelight

6. • Grady Booch – history of softwre engineering
The entire history of software engineering is that of
the rise in levels of abstraction
- Grady Booch

7. • Everything is a model
• The key role of modeling and abstraction in software engineering
• Their key role also beyond software itself
I think we all agree

8. Low-code application platforms accelerate app
delivery by dramatically reducing the amount of
hand-coding required – Forrester Report
BUT we have a marketing problem…

9. Low-code is trending

10. Low-code is trending because
•Much clearer message: Everybody understands
that low-code means “less coding”. MDD is much
more confusing
•Sounds familiar, as the marketing msg is still focus
on the code
•Simpler pipeline, no transformation chains, one-
shot modeling.
•Low-code tools are better <- Usability issues!!!

11. "Given the final model, the complete computerized
information system can be automatically
generated“
"we arrive at a specification from which executable
code can be automatically generated"
Already topics at CAiSE’91

12. We have a scientific (recognition) problem…

13. Even more important thanks to new opportunities

14. Modeling can be helpful in
other domains

15. “Formalizing” and automatic analysis in some
domains

17. Cheaper solutions for others

18. • But we can still help with our particular modeling
perspective and expertise
– By building a useful set of abstractions and precise
notations to use them
– “Machinery” to automatically reason on, process and
exchange models build with these abstractions
There is plenty of modeling in other domains

19. Our proposal

20. To unleash the full potential of modeling we need to break free of
our traditional positioning within software engineering and
cooperate with scientists and engineers from other domains.
The best way to achieve this is for modeling to become an
independent discipline that serves all the rest.
WIN-WIN proposition -> we help others and learn from them

21. Modeling as a
transdisciplinary dicipline

22. Why a discipline
• A way to give modeling the recognition it
deserves, increase its visibility,
and attract the talent and resources it
needs

23. Object of
research
Body of
knowledge
Theories and
concepts
Terminology
Reserach
methods
Teaching
Can it be a discipline?

24. First steps

25. Be inclusive
• Understand (and collect) how different
communities model
• Build bridges among different models and
study the benefits of different combinations
of such models
• Develop the proper tooling for this

26. Community
• Identify key players in other fields
• Invite them to join the initiative

27. Teaching modeling
• MBEBOK could be a starting point
• Combine a set of core concepts with specializations
for specific domains
– Specialization goes beyond tech concepts, e.g.
effective use of modeling in the domain X based on
the profile of user there
• Different education paths for “modeling users” and
“modeling devs”

28. User driven DSLs
• New DSLs are needed for many domains
where use of modeling is informal
• But these domains are far from our knowledge
• We need to involve the end-users
• Lack of prof modelers -> non-tech people
creating DSLs

29. Usability
• Modeling tools are not that usable, especially for
non experts
• Can we bring modeling to the tools they already
use?
• How to facilitate the modeling process?
– AI to the rescue
– Generation of models from data / docs

30. Economies of modeling
• Methods to compute the ROI of modeling
• Needed to discuss the benefits of adopting
modeling in different scenarios

31. Publishing
• To involve researchers, they must be able to
get something out of their time
• Interdisciplinary publishing is really tough

32. Conclusion

33. Cleary, there is interest

34. jordi.cabot@icrea.cat
@JordiCabot
jordicabot.com
Let’s keep discussing and
refining the new
discipline of modeling