![]() Ma, Qin ![]() in Software and Systems Modeling (2022) Detailed reference viewed: 21 (2 UL)![]() ; ; Ma, Qin ![]() in Data and Knowledge Engineering (2022), 141 Detailed reference viewed: 12 (2 UL)![]() ; Ma, Qin ![]() in Lecture Notes in Business Information Processing (2022) Detailed reference viewed: 11 (1 UL)![]() ; ; Ma, Qin ![]() Report (2021) Detailed reference viewed: 67 (4 UL)![]() ; ; Ma, Qin ![]() in Enterprise Modelling and Information Systems Architectures (2021), 16 Detailed reference viewed: 78 (3 UL)![]() ; Ma, Qin ![]() in Advances in Conceptual Modeling - ER 2021 Workshops CoMoNoS, EmpER CMLS, St. John's, NL, Canada, October 18-21, 2021, Proceedings (2021) Detailed reference viewed: 53 (10 UL)![]() Ma, Qin ![]() in The Practice of Enterprise Modeling - 14th IFIP WG 8.1 Working Conference, PoEM 2021, Riga, Latvia, November 24-26, 2021, Proceedings (2021) Detailed reference viewed: 26 (1 UL)![]() ; Ma, Qin ![]() in Lecture Notes in Business Information Processing 400 (2020) While ADOxx is a popular platform for the creation and use of enterprise modeling languages, it provides only limited support for a well-formedness check of created enterprise models. In this paper, we ... [more ▼] While ADOxx is a popular platform for the creation and use of enterprise modeling languages, it provides only limited support for a well-formedness check of created enterprise models. In this paper, we propose to complement the meta modeling platform ADOxx with Alloy, which natively provides extensive model checking capabilities, so as to enable a well-formedness check of enterprise models created in ADOxx. Using the e3value modeling language as a point of departure, we particularly provide (a) a partial ADOxx implementation of e3value, (b) a proof-of-concept XML2Alloy parser, which allows for converting e3value models created in ADOxx into Alloy format, so that (c) e3value well-formedness constraints stated in Alloy can be used to check the valid- ity of an e3value model with the Alloy Evaluator. Beyond the specific proof-of-concept, we also discuss further possibilities of using ADOxx in conjunction with Alloy, particularly in checking the soundness of meta models underlying an enterprise modeling language. [less ▲] Detailed reference viewed: 49 (0 UL)![]() Kelsen, Pierre ![]() ![]() ![]() in Journal of Object Technology (2020), 19(2), 151-22 Creating models and transforming them using current MDE techniques is not easy: it generally requires mastering several non-trivial languages such as a metamodeling languages and a model transformation ... [more ▼] Creating models and transforming them using current MDE techniques is not easy: it generally requires mastering several non-trivial languages such as a metamodeling languages and a model transformation language. We propose a two-pronged approach for tackling language complexity for the case of model-to-text transformations. We first allow the user to define the metamodel in an example-driven fashion in which (s)he incrementally builds a set of examples and automatically infers the metamodel from them. The example-driven approach is based on a new object-modelling notation named OYAML that is both human- and machine- readable. Second we break down the complexity of writing the transformation itself by separately defining the functional decomposition of the transformation function using a new modelling language named FUDOMO. This will then allow the user to describe the precise behaviour in a general purpose programming language that (s)he is familiar with. Because they do not need to be very expressive, OYAML and FUDOMO are small languages when compared to commonly used metamodeling and model-to-text transformation languages. We provide a web-based tool, also named FUDOMO, that assists the user in this example-driven approach to model-to-text transformations and currently supports the use of Javascript and Python for defining the precise behaviour of model transformations. [less ▲] Detailed reference viewed: 140 (3 UL)![]() ; ; et al in WIRTSCHAFTSINFORMATIK 2019 PROCEEDINGS (2019) Detailed reference viewed: 43 (2 UL)![]() ; Ma, Qin ![]() in 2018 International Conference on Information Management & Management Science (2018) Detailed reference viewed: 200 (5 UL)![]() ; ; Ma, Qin ![]() in Joint International Conference of Service Science and Innovation and Serviceology (2018) Detailed reference viewed: 77 (7 UL)![]() Ma, Qin ![]() ![]() in 12th International Symposium on Theoretical Aspects of Software Engineering (2018) Detailed reference viewed: 148 (7 UL)![]() ; ; Ma, Qin ![]() in IEEE 12th International Conference on Research Challenges in Information Science (2018) Detailed reference viewed: 90 (1 UL)![]() ; ; Ma, Qin ![]() in Lecture Notes in Business Information Processing 305 (2017) Detailed reference viewed: 103 (3 UL)![]() ; Ma, Qin ![]() in 19th IEEE Conference on Business Informatics, CBI 2017, Thessaloniki, Greece, July 24-27, 2017, Volume 2: Workshop Papers (2017) Detailed reference viewed: 110 (5 UL)![]() Ma, Qin ![]() in In Proceedings of the 22nd International Working Conference on Requirements Engineering: Foundation for Software Quality (LNCS 9619) (2016) Detailed reference viewed: 82 (2 UL)![]() ; De Kinderen, Sybren ![]() ![]() in Proceedings of the 17th IEEE Conference on Business Informatics, Lisbon Portugal, July 13-16, 2015, Volume 1 (2015) Detailed reference viewed: 114 (0 UL)![]() Colombo Tosatto, Silvano ![]() ![]() ![]() in Frontiers of Computer Science (2015), 9(1), 55-74 In general the problem of verifying whether a structured business process is compliant with a given set of regulations is NP-hard. The present paper focuses on identifying a tractable subset of this ... [more ▼] In general the problem of verifying whether a structured business process is compliant with a given set of regulations is NP-hard. The present paper focuses on identifying a tractable subset of this problem, namely verifying whether a structured business process is compliant with a single global obligation. Global obligations are those whose validity spans for the entire execution of a business process. We identify two types of obligations: achievement and maintenance. In the present paper we firstly define an abstract framework capable to model the problem and secondly we define procedures and algorithms to deal with the compliance problem of checking the compliance of a structured business process with respect to a single global obligation. We show that the algorithms proposed in the paper run in polynomial time. [less ▲] Detailed reference viewed: 194 (16 UL)![]() De Kinderen, Sybren ![]() ![]() in Applied Ontology (2015) Conceptual modeling languages are purposeful artifacts, hence their design should also start from the purpose that they serve. Such purposeful design addresses the requirements engineering concern of a ... [more ▼] Conceptual modeling languages are purposeful artifacts, hence their design should also start from the purpose that they serve. Such purposeful design addresses the requirements engineering concern of a language specification being aligned with the goals of its users. Thereby relevance of the language is ensured, instead of developing a language for language’s sake. We posit that this addresses some known issues that are due to a misalignment between a language’s specification and the goals of its intended users. In this paper, we introduce vGREL, a goal- and value-oriented approach for purposeful language development. vGREL helps language engineers to start the design of conceptual modeling languages with requirements engineering exercises. To this end vGREL provides (1) a purpose driven requirements engineering process for language design; (2) a value profile for the Goaloriented Requirements Language (GRL) to enable analysis and reasoning during the process and capture its results; and leverages (3) the software tool support of GRL for decision making during language design. To illustrate vGREL, we apply it to a case study on responsibility-based access rights management. Furthermore, we present reflections on vGREL from the language engineer involved in the case study. [less ▲] Detailed reference viewed: 136 (5 UL) |
||