Author of the publication

06351 Summary -- Methods for Modelling Software Systems (MMOSS).

, , , , and . MMOSS, volume 06351 of Dagstuhl Seminar Proceedings, Internationales Begegnungs- und Forschungszentrum fuer Informatik (IBFI), Schloss Dagstuhl, Germany, (2006)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

 

Other publications of authors with the same name

Cross-Organizational Workflows: A Classification of Design Decisions., , , and . CAiSE Short Paper Proceedings, volume 161 of CEUR Workshop Proceedings, CEUR-WS.org, (2005)Semantic and Pragmatic Interoperability: A Model for Understanding., , , and . EMOI-INTEROP, volume 160 of CEUR Workshop Proceedings, CEUR-WS.org, (2005)Towards Security Requirements: Iconicity as a Feature of an Informal Modeling Language., , , , and . REFSQ Workshops, volume 1796 of CEUR Workshop Proceedings, CEUR-WS.org, (2017)Experiment: Understandability of Goal Modeling with ARMOR., and . REFSQ Workshops, volume 1138 of CEUR Workshop Proceedings, page 76-81. CEUR-WS.org, (2014)Surveying the factors that influence maintainability: research design., and . ESEC/SIGSOFT FSE, page 385-388. ACM, (2005)Analyzing SAFe Practices with Respect to Quality Requirements: Findings from a Qualitative Study., , , and . PROFES, volume 13126 of Lecture Notes in Computer Science, page 233-248. Springer, (2021)An Approach That Stimulates Architectural Thinking during Requirements Elicitation: An Empirical Evaluation., , , and . ICSOFT, page 187-195. ScitePress, (2020)Agile Quality Requirements Elaboration: A Proposal and Evaluation., , and . ICSOFT, page 668-679. SCITEPRESS, (2023)Multi-Perspective Requirements Engineering for Networked Business Systems: A Framework for Pattern Composition., , and . WER, page 26-37. (2005)Exploiting a Goal-Decomposition Technique to Prioritize Non-functional Requirements., , , , and . WER, page 190-196. (2007)