Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

Modeling should be an independent scientific discipline

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio

Eche un vistazo a continuación

1 de 34 Anuncio

Modeling should be an independent scientific discipline

Descargar para leer sin conexión

Software modeling started as a paradigm to help developers build better software faster by enabling them to specify, reason and manipulate software systems at a higher-abstraction level while ignoring irrelevant low-level technical details. But this same principle manifests in any other domain that has to deal with complex systems, software-based or not. We argue that bringing to other engineering and scientific fields, our modeling expertise is a win–win opportunity where we can all learn from each other as we all model, but in complementary ways. Nevertheless, to fully unleash the benefits of this collaboration, we must go beyond individual efforts trying to adapt single techniques from one field to another. It requires a deeper reformulation of modeling as a whole. It is time for modeling to become an independent discipline where all fields of knowledge can contribute and benefit from.

Software modeling started as a paradigm to help developers build better software faster by enabling them to specify, reason and manipulate software systems at a higher-abstraction level while ignoring irrelevant low-level technical details. But this same principle manifests in any other domain that has to deal with complex systems, software-based or not. We argue that bringing to other engineering and scientific fields, our modeling expertise is a win–win opportunity where we can all learn from each other as we all model, but in complementary ways. Nevertheless, to fully unleash the benefits of this collaboration, we must go beyond individual efforts trying to adapt single techniques from one field to another. It requires a deeper reformulation of modeling as a whole. It is time for modeling to become an independent discipline where all fields of knowledge can contribute and benefit from.

Anuncio
Anuncio

Más Contenido Relacionado

Similares a Modeling should be an independent scientific discipline (20)

Más de Jordi Cabot (20)

Anuncio

Más reciente (20)

Modeling should be an independent scientific discipline

  1. 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. 2. My background (as it affects my perspecitve)
  3. 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. 4. Why this reflection?
  5. 5. Need to reclaim the key role of modeling and bring it into the limelight
  6. 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. 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. 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. 9. Low-code is trending
  10. 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. 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. 12. We have a scientific (recognition) problem…
  13. 13. Even more important thanks to new opportunities
  14. 14. Modeling can be helpful in other domains
  15. 15. “Formalizing” and automatic analysis in some domains
  16. 16. Cheaper solutions for others
  17. 17. • 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
  18. 18. Our proposal
  19. 19. 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
  20. 20. Modeling as a transdisciplinary dicipline
  21. 21. Why a discipline • A way to give modeling the recognition it deserves, increase its visibility, and attract the talent and resources it needs
  22. 22. Object of research Body of knowledge Theories and concepts Terminology Reserach methods Teaching Can it be a discipline?
  23. 23. First steps
  24. 24. 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
  25. 25. Community • Identify key players in other fields • Invite them to join the initiative
  26. 26. 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”
  27. 27. 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
  28. 28. 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
  29. 29. Economies of modeling • Methods to compute the ROI of modeling • Needed to discuss the benefits of adopting modeling in different scenarios
  30. 30. Publishing • To involve researchers, they must be able to get something out of their time • Interdisciplinary publishing is really tough
  31. 31. Conclusion
  32. 32. Cleary, there is interest
  33. 33. jordi.cabot@icrea.cat @JordiCabot jordicabot.com Let’s keep discussing and refining the new discipline of modeling

Notas del editor

  • As important as the proposal itself
  • Our solution is not that “original”
  • We have a marketing problema!!!
  • We have a marketing problem!!!
  • Right now, low-code
  • Though let’s always keep in mind that “AI ISSSSSS Software!!!
  • For sure, we’re not the only ones modeling
  • Building an ECAD modeling tool with SysML and EMF as a much cheaper solutions than dedicated ECAD editors
  • 1. Disciplines have a particular object of research, although the object of re- search may be shared with another discipline. Our object of research is to provide languages, operations and tools to create and manipulate ab- stractions that facilitate the comprehension, reasoning and manipulation of complex technical, social, biological and natural systems, and not only software-based ones. We partner together with other disciplines to reach these goals. 2. Disciplines have a body of accumulated specialist knowledge referring to their object of research, which is specific to them and not generally shared with another discipline. Software modeling has a well-defined body of knowl- edge [10] that characterizes the specific contributions of modeling as a knowledge field. 3. Disciplines have theories and concepts that can organize the accumulated specialist knowledge effectively. Modeling comprises a good number of theo- ries (some grounded on formal methods, some on more empirical evidence) to compare, merge and organize the growing number of modeling concepts and techniques being developed. 4. Disciplines use specific terminologies or a specific technical language ad- justed to their research object. Over the years, modeling has precisely de- fined a set of core terminology (model, metamodel, DSL, transformation, etc.). New terms are then contextualized in terms of the existing ones (e.g. the positioning of low-code [11, 25]). 5. Disciplines have developed specific research methods according to their spe- cific research requirements. Research methods in modeling are mostly de- rived from research methods in software engineering adapted to the speci- ficities of modeling. More work on developing more specific methods that can be employed when applying modeling in other fields will be needed. 6. Disciplines must have some institutional manifestation in the form of sub- jects taught at universities or colleges. Modeling courses are part of the syllabus in most computing curricula, and discussions on how to better teach modeling are an important part of every modeling conference (e.g. see the annual Educators Symposium at the Models conference). There was even an attempt to create a full postgraduate course on model-driven engineering [13]. Even if short-lived, this experience showed that modeling is rich enough to be the focus of a full teaching specialization.
  • To see the implications of intent recognition, let’s dive in the NLP
  • We have some expertise on the latter
  • If you want to keep exploring and Building these tòpics together ...

×