The Experts below are selected from a list of 12681 Experts worldwide ranked by ideXlab platform
Katsiaryna Labunets - One of the best experts on this subject based on the ideXlab platform.
-
no search allowed what risk Modeling Notation to choose
Empirical Software Engineering and Measurement, 2018Co-Authors: Katsiaryna LabunetsAbstract:[Background] Industry relies on the use of tabular Notations to document the risk assessment results, while academia encourages to use graphical Notations. Previous studies revealed that tabular and graphical Notations with textual labels provide better support for extracting correct information about security risks in comparison to iconic graphical Notation. [Aim] In this study we examine how well tabular and graphical risk Modeling Notations support extraction and memorization of information about risks when models cannot be searched. [Method] We present results of two experiments with 60 MSc and 31 BSc students where we compared their performance in extraction and memorization of security risk models in tabular, UML-style and iconic graphical Modeling Notations. [Result] Once search is restricted, tabular Notation demonstrates results similar to the iconic graphical Notation in information extraction. In memorization task tabular and graphical Notations showed equivalent results, but it is statistically significant only between two graphical Notations. [Conclusion] Three Notations provide similar support to decision-makers when they need to extract and remember correct information about security risks.
-
ESEM - No search allowed: what risk Modeling Notation to choose?
Proceedings of the 12th ACM IEEE International Symposium on Empirical Software Engineering and Measurement, 2018Co-Authors: Katsiaryna LabunetsAbstract:[Background] Industry relies on the use of tabular Notations to document the risk assessment results, while academia encourages to use graphical Notations. Previous studies revealed that tabular and graphical Notations with textual labels provide better support for extracting correct information about security risks in comparison to iconic graphical Notation. [Aim] In this study we examine how well tabular and graphical risk Modeling Notations support extraction and memorization of information about risks when models cannot be searched. [Method] We present results of two experiments with 60 MSc and 31 BSc students where we compared their performance in extraction and memorization of security risk models in tabular, UML-style and iconic graphical Modeling Notations. [Result] Once search is restricted, tabular Notation demonstrates results similar to the iconic graphical Notation in information extraction. In memorization task tabular and graphical Notations showed equivalent results, but it is statistically significant only between two graphical Notations. [Conclusion] Three Notations provide similar support to decision-makers when they need to extract and remember correct information about security risks.
Pierrealain Muller - One of the best experts on this subject based on the ideXlab platform.
-
the unified Modeling language uml 98 beyond the Notation first international workshop mulhouse france june 3 4 1998 selected papers
1999Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:UML: The Birth and Rise of a Standard Modeling Notation.- Developing with UML - Some Pitfalls and Workarounds.- Supporting and Applying the UML Conceptual Framework.- Modeling: Is It Turning Informal into Formal?.- Best of Both Worlds - A Mapping from EXPRESS-G to UML.- Porting ROSES to UML - An Experience Report.- Making UML Models Interoperable with UXF.- Transformation Rules for UML Class Diagrams.- Semantics and Transformations for UML Models.- Automation of Design Pattern: Concepts, Tools and Practices.- Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams.- Informal Formality? The Object Constraint Language and Its Application in the UML Metamodel.- Reflections on the Object Constraint Language.- On Using UML Class Diagrams for Object-Oriented Database Design.- Literate Modelling - Capturing Business Knowledge with the UML.- Applying UML to Design an Inter-domain Service Management Application.- Booster*Process: A Software Development Process Model Integrating Business Object Technology and UML.- Hierarchical Context Diagrams with UML: An Experience Report on Satellite Ground System Analysis.- Extension of UML Sequence Diagrams for Real-Time Systems.- UML and User Interface Modeling.- On the Role of Activity Diagrams in UML - A User Task Centered Development Process for UML.- Structuring UML Design Deliverables.- Considerations of and Suggestions for a UML-Specific Process Model.- An Action Language for UML: Proposal for a Precise Execution Semantics.- Real-Time Modeling with UML: The ACCORD Approach.- The UML as a Formal Modeling Notation.- OML: Proposals to Enhance UML.- Validating Distributed Software Modeled with the Unified Modeling Language.- Supporting Disciplined Reuse and Evolution of UML Models.- Applying UML Extensions to Facilitate Software Reuse.- A Formal Approach to Use Cases and Their Relationships.- A Practical Framework for Applying UML.- Extending Aggregation Constructs in UML.
-
UML - UML: The Birth and Rise of a Standard Modeling Notation
The Unified Modeling Language. «UML»’98: Beyond the Notation, 1999Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:Officially the Unified Modeling Language UML is a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. For many, UML is much more than that and symbolizes the transition from code-oriented to model-oriented software production techniques. It is very likely that, in a historical perspective, UML will be given credit for the perspectives opened as well as for the direct achievements realized. This introductory paper presents some of the characteristics of the Notation and discusses some of the perspectives that have been and that are being opened by the UML proposal.
-
uml the birth and rise of a standard Modeling Notation
Lecture Notes in Computer Science, 1998Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:Officially the Unified Modeling Language UML is a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. For many, UML is much more than that and symbolizes the transition from code-oriented to model-oriented software production techniques. It is very likely that, in a historical perspective, UML will be given credit for the perspectives opened as well as for the direct achievements realized. This introductory paper presents some of the characteristics of the Notation and discusses some of the perspectives that have been and that are being opened by the UML proposal.
Jean Bezivin - One of the best experts on this subject based on the ideXlab platform.
-
the unified Modeling language uml 98 beyond the Notation first international workshop mulhouse france june 3 4 1998 selected papers
1999Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:UML: The Birth and Rise of a Standard Modeling Notation.- Developing with UML - Some Pitfalls and Workarounds.- Supporting and Applying the UML Conceptual Framework.- Modeling: Is It Turning Informal into Formal?.- Best of Both Worlds - A Mapping from EXPRESS-G to UML.- Porting ROSES to UML - An Experience Report.- Making UML Models Interoperable with UXF.- Transformation Rules for UML Class Diagrams.- Semantics and Transformations for UML Models.- Automation of Design Pattern: Concepts, Tools and Practices.- Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams.- Informal Formality? The Object Constraint Language and Its Application in the UML Metamodel.- Reflections on the Object Constraint Language.- On Using UML Class Diagrams for Object-Oriented Database Design.- Literate Modelling - Capturing Business Knowledge with the UML.- Applying UML to Design an Inter-domain Service Management Application.- Booster*Process: A Software Development Process Model Integrating Business Object Technology and UML.- Hierarchical Context Diagrams with UML: An Experience Report on Satellite Ground System Analysis.- Extension of UML Sequence Diagrams for Real-Time Systems.- UML and User Interface Modeling.- On the Role of Activity Diagrams in UML - A User Task Centered Development Process for UML.- Structuring UML Design Deliverables.- Considerations of and Suggestions for a UML-Specific Process Model.- An Action Language for UML: Proposal for a Precise Execution Semantics.- Real-Time Modeling with UML: The ACCORD Approach.- The UML as a Formal Modeling Notation.- OML: Proposals to Enhance UML.- Validating Distributed Software Modeled with the Unified Modeling Language.- Supporting Disciplined Reuse and Evolution of UML Models.- Applying UML Extensions to Facilitate Software Reuse.- A Formal Approach to Use Cases and Their Relationships.- A Practical Framework for Applying UML.- Extending Aggregation Constructs in UML.
-
UML - UML: The Birth and Rise of a Standard Modeling Notation
The Unified Modeling Language. «UML»’98: Beyond the Notation, 1999Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:Officially the Unified Modeling Language UML is a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. For many, UML is much more than that and symbolizes the transition from code-oriented to model-oriented software production techniques. It is very likely that, in a historical perspective, UML will be given credit for the perspectives opened as well as for the direct achievements realized. This introductory paper presents some of the characteristics of the Notation and discusses some of the perspectives that have been and that are being opened by the UML proposal.
-
uml the birth and rise of a standard Modeling Notation
Lecture Notes in Computer Science, 1998Co-Authors: Jean Bezivin, Pierrealain MullerAbstract:Officially the Unified Modeling Language UML is a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. For many, UML is much more than that and symbolizes the transition from code-oriented to model-oriented software production techniques. It is very likely that, in a historical perspective, UML will be given credit for the perspectives opened as well as for the direct achievements realized. This introductory paper presents some of the characteristics of the Notation and discusses some of the perspectives that have been and that are being opened by the UML proposal.
U Settmacher - One of the best experts on this subject based on the ideXlab platform.
-
New methods for clinical pathways—Business Process Modeling Notation (BPMN) and Tangible Business Process Modeling (t.BPM)
Langenbeck's Archives of Surgery, 2012Co-Authors: H Scheuerlein, F Rauchfuss, Y Dittmar, Rudiger Molle, Torsten Lehmann, Nicole Pienkos, U SettmacherAbstract:Purpose Clinical pathways (CP) are nowadays used in numerous institutions, but their real impact is still a matter of debate. The optimal design of a clinical pathway remains unclear and is mainly determined by the expectations of the individual institution. The purpose of the here described pilot project was the development of two CP (colon and rectum carcinoma) according to Business Process Modeling Notation (BPMN) and Tangible Business Process Modeling (t.BPM). Methods BPMN is an established standard for business process modelling in industry and economy. It is, in the broadest sense, a computer programme which enables the description and a relatively easy graphical imaging of complex processes. t.BPM is a modular construction system of the BPMN symbols which enables the creation of an outline or raw model, e.g. by placing the symbols on a spread-out paper sheet. The thus created outline can then be transferred to the computer and further modified as required. CP for the treatment of colon and rectal cancer have been developed with support of an external IT coach. Results The pathway was developed in an interdisciplinary and interprofessional manner (55 man-days over 15 working days). During this time, necessary interviews with medical, nursing and administrative staffs were conducted as well. Both pathways were developed parallel. Subsequent analysis was focussed on feasibility, expenditure, clarity and suitability for daily clinical practice. The familiarization with BPMN was relatively quick and intuitive. The use of t.BPM enabled the pragmatic, effective and results-directed creation of outlines for the CP. The development of both CP was finished from the diagnostic evaluation to the adjuvant/neoadjuvant therapy and rehabilitation phase. The integration of checklists, guidelines and important medical or other documents is easily accomplished. A direct integration into the hospital computer system is currently not possible for technical reasons. Conclusion BPMN and t.BPM are sufficiently suitable for the planned modelling and imaging of CP. The application in medicine is new, and transfer from the industrial process management is in principle possible. BPMN-CP may be used for teaching and training, patient information and quality management. The graphical image is clearly structured and appealing. Even though the efficiency in the creation of BPMN-CP increases markedly after the training phase, high amounts of manpower and time are required. The most sensible and consequent application of a BPMN-CP would be the direct integration into the hospital computer system. The integration of a modelling language, such as BPMN, into the hospital computer systems could be a very sensible approach for the development of new hospital information systems in the future.
-
new methods for clinical pathways business process Modeling Notation bpmn and tangible business process Modeling t bpm
Langenbeck's Archives of Surgery, 2012Co-Authors: H Scheuerlein, F Rauchfuss, Y Dittmar, Rudiger Molle, Torsten Lehmann, Nicole Pienkos, U SettmacherAbstract:Purpose Clinical pathways (CP) are nowadays used in numerous institutions, but their real impact is still a matter of debate. The optimal design of a clinical pathway remains unclear and is mainly determined by the expectations of the individual institution. The purpose of the here described pilot project was the development of two CP (colon and rectum carcinoma) according to Business Process Modeling Notation (BPMN) and Tangible Business Process Modeling (t.BPM).
-
New methods for clinical pathways—Business Process Modeling Notation (BPMN) and Tangible Business Process Modeling (t.BPM)
Langenbeck's archives of surgery, 2012Co-Authors: H Scheuerlein, F Rauchfuss, Y Dittmar, Rudiger Molle, Torsten Lehmann, Nicole Pienkos, U SettmacherAbstract:Purpose Clinical pathways (CP) are nowadays used in numerous institutions, but their real impact is still a matter of debate. The optimal design of a clinical pathway remains unclear and is mainly determined by the expectations of the individual institution. The purpose of the here described pilot project was the development of two CP (colon and rectum carcinoma) according to Business Process Modeling Notation (BPMN) and Tangible Business Process Modeling (t.BPM).
Jan C Recker - One of the best experts on this subject based on the ideXlab platform.
-
Seminal Contributions to Information Systems Engineering - How Much Language is Enough? Theoretical and Practical Use of the Business Process Modeling Notation
2013Co-Authors: Michael Zur Muehlen, Jan C ReckerAbstract:The Business Process Modeling Notation (BPMN) is an increasingly important industry standard for the graphical representation of business processes. BPMN offers a wide range of Modeling constructs, significantly more than other popular languages. However, not all of these constructs are equally important in practice as business analysts frequently use arbitrary subsets of BPMN. In this paper we investigate what these subsets are, and how they differ between academic, consulting, and general use of the language. We analyzed 120 BPMN diagrams using mathematical and statistical techniques. Our findings indicate that BPMN is used in groups of several, well-defined construct clusters, but less than 20% of its vocabulary is regularly used and some constructs did not occur in any of the models we analyzed. While the average model contains just 9 different BPMN constructs, models of this complexity have typically just 4-5 constructs in common, which means that only a small agreed subset of BPMN has emerged. Our findings have implications for the entire ecosystems of analysts and modelers in that they provide guidance on how to reduce language complexity, which should increase the ease and speed of process Modeling.
-
how much language is enough theoretical and practical use of the business process Modeling Notation
Conference on Advanced Information Systems Engineering, 2008Co-Authors: Michael Zur Muehlen, Jan C ReckerAbstract:The Business Process Modeling Notation (BPMN) is an increasingly important industry standard for the graphical representation of business processes. BPMN offers a wide range of Modeling constructs, significantly more than other popular languages. However, not all of these constructs are equally important in practice as business analysts frequently use arbitrary subsets of BPMN. In this paper we investigate what these subsets are, and how they differ between academic, consulting, and general use of the language. We analyzed 120 BPMN diagrams using mathematical and statistical techniques. Our findings indicate that BPMN is used in groups of several, well-defined construct clusters, but less than 20% of its vocabulary is regularly used and some constructs did not occur in any of the models we analyzed. While the average model contains just 9 different BPMN constructs, models of this complexity have typically just 4-5 constructs in common, which means that only a small agreed subset of BPMN has emerged. Our findings have implications for the entire ecosystems of analysts and modelers in that they provide guidance on how to reduce language complexity, which should increase the ease and speed of process Modeling.
-
CAiSE - How Much Language Is Enough? Theoretical and Practical Use of the Business Process Modeling Notation
Notes on Numerical Fluid Mechanics and Multidisciplinary Design, 2008Co-Authors: Michael Zur Muehlen, Jan C ReckerAbstract:The Business Process Modeling Notation (BPMN) is an increasingly important industry standard for the graphical representation of business processes. BPMN offers a wide range of Modeling constructs, significantly more than other popular languages. However, not all of these constructs are equally important in practice as business analysts frequently use arbitrary subsets of BPMN. In this paper we investigate what these subsets are, and how they differ between academic, consulting, and general use of the language. We analyzed 120 BPMN diagrams using mathematical and statistical techniques. Our findings indicate that BPMN is used in groups of several, well-defined construct clusters, but less than 20% of its vocabulary is regularly used and some constructs did not occur in any of the models we analyzed. While the average model contains just 9 different BPMN constructs, models of this complexity have typically just 4-5 constructs in common, which means that only a small agreed subset of BPMN has emerged. Our findings have implications for the entire ecosystems of analysts and modelers in that they provide guidance on how to reduce language complexity, which should increase the ease and speed of process Modeling.
-
Do Process Modelling Techniques Get Better? A Comparative Ontological Analysis of BPMN
2005Co-Authors: Jan C Recker, Marta Indulska, Michael Rosemann, Peter GreenAbstract:Current initiatives in the field of Business Process Management (BPM) strive for the development of a BPM standard Notation by pushing the Business Process Modeling Notation (BPMN). However, such a proposed standard Notation needs to be carefully examined. Ontological analysis is an established theoretical approach to evaluating modelling techniques. This paper reports on the outcomes of an ontological analysis of BPMN and explores identified issues by reporting on interviews conducted with BPMN users in Australia. Complementing this analysis we consolidate our findings with previous ontological analyses of process modelling Notations to deliver a comprehensive assessment of BPMN.
