Requirements engineering for the design of conceptual modeling languages

2015 ◽  
Vol 10 (1) ◽  
pp. 7-24 ◽  
Author(s):  
Sybren de Kinderen ◽  
Qin Ma
Keyword(s):  
Requirements Engineering ◽  
Conceptual Modeling ◽  
Modeling Languages

Human-Centered Conceptualization and Natural Language

2006 ◽  
pp. 280-286
Author(s):  
Javier Andrade ◽  
Juan Ares ◽  
Rafael García ◽  
Santiago Rodríguez ◽  
Andrés Silva
Keyword(s):  
Software Engineering ◽  
Conceptual Model ◽  
Computational Models ◽  
Focal Point ◽  
Software Process ◽  
Conceptual Modeling ◽  
Modeling Languages ◽  
Future Trends ◽  
Human Beings ◽  
Human Problem

Conceptual modeling appears to be the heart of good software development (Jackson, 2000). The creation of a conceptual model helps to understand the problem raised and represents the human-centered/problem-oriented moment in the software process, as opposed to the computer-centered/software-oriented moment of the computational models (Blum, 1996). The main objective of human computer interaction (HCI) is also precisely to make human beings the focal point that technology should serve rather than the other way round. The conceptual models are built with conceptual modeling languages (CMLs), whose specification involves constructors and rules on how to combine these constructors into meaningful statements about the problem. Considering the criterion of the representation capability of the CMLs in software engineering, their main drawback is that they remain too close to the development aspects (Jackson, 1995). The constructors are too much oriented toward the computational solution of the problem, and therefore, the problem is modeled with implementation concepts (computer/software solution sensitivity) rather than concepts that are proper to human beings (human/problem sensitivity) (Andrade, Ares, García & Rodríguez, 2004). This stands in open opposition to what we have said about the moments in the software process and HCI. Moreover, this situation seriously complicates the essential validation of the achieved conceptual model, because it is drawn up in technical terms that are very difficult to understand by the person who faces the problem (Andrade et al., 2004). The semantics of the constructors determines the representation capability (Wand, Monarchi, Parsons & Woo, 1995). Since the constructors are too close to implementation paradigms, the CMLs that currently are being used in software engineering are incapable of describing the problem accurately. Suitable human/problem-related theoretical guidelines should determine which constructors must be included in a genuine CML. This article, subject to certain software-independent theoretical guidelines, proposes the conceptual elements that should be considered in the design of a real CML and, consequently, what constructors should be provided. The Background section presents the software-independent guidelines that were taken into account to identify the above-mentioned conceptual elements. The Main Focus of the Article section discusses the study that identified those elements. Finally, the Future Trends section presents the most interesting future trends, and the final section concludes.

Ontology Based Object-Oriented Domain Modeling

2011 ◽  
pp. 37-60
Author(s):  
Joerg Evermann ◽  
Yair Wand
Keyword(s):  
Information System ◽  
Conceptual Modeling ◽  
Object Oriented ◽  
Modeling Languages ◽  
Domain Modeling ◽  
Application Domain ◽  
Structural Elements ◽  
Software Modeling ◽  
Software Models

An important step in developing the requirements for an information system is analyzing the application domain. In this step, conceptual models are used for representing an application domain. However, while languages for software design are available and widely used, no generally accepted language exists for conceptual modeling. This work suggests the use of object-oriented software modeling languages also for conceptual modeling. Such use can support a more accurate transition from domain modes to software models. As software-modeling languages were not intended for modeling application domains, their constructs lack the required semantics. While previous papers addressed the representation of structural elements of domains using object concepts, this paper addresses behavioral aspects, related to change and interaction. The proposed semantics are based on a mapping between ontological concepts that describe behavior and object-oriented constructs related to dynamics. Based on these mappings, modeling rules are proposed to guide the modeler in creating ontologically well-formed models. The mappings and rules are exemplified using UML and are demonstrated using a case study.

Ontology Based Object-Oriented Domain Modeling

2009 ◽  
pp. 505-527
Author(s):  
Joerg Evermann ◽  
Yair Wand
Keyword(s):  
Conceptual Modeling ◽  
Object Oriented ◽  
Modeling Languages ◽  
Domain Modeling ◽  
Application Domain ◽  
Structural Elements ◽  
Software Modeling ◽  
Software Models ◽  
Domain Models

An important step in developing the requirements for an information system is analyzing the application domain. In this step, conceptual models are used for representing an application domain. However, while languages for software design are available and widely used, no generally accepted language exists for conceptual modeling. This work suggests the use of object-oriented software modeling languages also for conceptual modeling. Such use can support a more accurate transition from domain models to software models. As software-modeling languages were not intended for modeling application domains, their constructs lack the required semantics. While previous papers addressed the representation of structural elements of domains using object concepts, this paper addresses behavioral aspects, related to change and interaction. The proposed semantics are based on a mapping between ontological concepts that describe behavior and object-oriented constructs related to dynamics. Based on these mappings, modeling rules are proposed to guide the modeler in creating ontologically well-formed models. The mappings and rules are exemplified using UML and are demonstrated using a case study.

An overview of the unified modeling language and diagrammatic modeling language design in software engineering

2003 ◽  
Vol 11 (2-3) ◽  
pp. 151-159 ◽  
Author(s):  
M. Naci Akkøk
Keyword(s):  
Software Engineering ◽  
Unified Modeling Language ◽  
Conceptual Modeling ◽  
Language Design ◽  
Modeling Language ◽  
Modeling Languages ◽  
Modeling Tools ◽  
Short Account ◽  
Unified Modeling ◽  
Body Of Knowledge

The need to manage the immense complexity in software engineering makes tools and methods essential, and requires that they be designed in accordance with well-defined principles. Surprisingly, there is yet no explicit body of knowledge for designing diagrammatic modeling languages (DMLs), despite the fact that they are used extensively as the primary conceptual modeling tools in software engineering. This paper provides an overview of the new and growing field of DML design that aims at compiling such a body of knowledge. The paper starts with relevant definitions and a brief introduction of the current de-facto standard DML of software engineering called the Unified Modeling Language (UML), and offers a short account of efforts and directions in DML design.

Sign in / Sign up

Export Citation Format

Share Document