Conceptual Application Domain Modelling

Application domain description precedes requirements engineering, and is the basis for the development of a software or information system that satisfies all expectations of its users. The greatest challenge in this area is the evolution of the application domain itself. In this paper we address this problem by explicit consideration of application cases that are defined by user profiles and intentions and the system environment, i.e. scope and context. User profiles and intentions are captured through the concept of persona. We show how the application domain description can be mapped to requirements and discuss engineering of application domain descriptions.

[1]  Colette Rolland.  From Conceptual Modeling to Requirements Engineering , 2006, ER.

[2]  Dao Nam Anh,et al.  Formal modelling of large domains , 1996, Proceedings 1996 Asia-Pacific Software Engineering Conference.

[3]  Michael R. Hansen,et al.  A Theory of Duration Calculus with Application , 2007, Domain Modeling and the Duration Calculus.

[4]  David B. Lowe,et al.  Web system requirements: an overview , 2003, Requirements Engineering.

[5]  Eamonn O'Neill,et al.  Participatory task modelling: users and developers modelling users' tasks and domains , 2004, TAMODIA '04.

[6]  Bernhard Thalheim,et al.  Software Quality and Life Cycles , 2005, ADBIS Research Communications.

[7]  John Krogstie,et al.  Interactive Models for Supporting Networked Organisations , 2004, CAiSE.

[8]  Jana Lewerenz.  Automatic generation of human computer interaction in heterogeneous and dynamic environments based on conceptual modelling , 2000 .

[9]  Bernhard Thalheim,et al.  Life Cases - An Approach to Address Pragmatics in the Design of Web Information Systems , 2007, WEBIST.

[10]  Bernhard Thalheim,et al.  Pragmatics of storyboarding for web information systems: usage analysis , 2007, Int. J. Web Grid Serv..

[11]  Janos Sztipanovits,et al.  Towards a formal foundation for domain specific modeling languages , 2006, EMSOFT '06.

[12]  Roel Wieringa.  Design Methods for Reactive Systems , 2003 .

[13]  Barry Boehm,et al.  A view of 20th and 21st century software engineering , 2006, ICSE.

[14]  Axel van Lamsweerde,et al.  Formal refinement patterns for goal-driven requirements elaboration , 1996, SIGSOFT '96.

[15]  Roel Wieringa,et al.  Design methods for reactive systems - Yourdon, Statemate, and the UML , 2003 .

[16]  Dines Bjørner,et al.  Software Engineering 3 - Domains, Requirements, and Software Design , 2006, Texts in Theoretical Computer Science. An EATCS Series.

[17]  Bernhard Thalheim,et al.  Conceptual modelling of web information systems , 2005, Data Knowl. Eng..

[18]  Michael Jackson,et al.  A Reference Model for Requirements and Specifications , 2000, IEEE Softw..

[19]  Bernhard Thalheim,et al.  Towards a Theory of Genericity Based on Government and Binding , 2006, ER.

[20]  Leszek A. Maciaszek.  Requirements Analysis & System Design , 2007 .

[21]  Bernhard Thalheim,et al.  Entity-relationship modeling - foundations of database technology , 2010 .

[22]  Bernhard Thalheim,et al.  Integrating Context in Modelling for Web Information Systems , 2003, WES.

[23]  G. Pólya,et al.  How to Solve It. A New Aspect of Mathematical Method. , 1945 .

[24]  Lin Padgham,et al.  A Description Logic for Composite Objects for Domain Modeling in an Agent-Oriented Application , 1996, Description Logics.

[25]  Bernhard Thalheim,et al.  Formalization of User Preferences, Obligations and Rights , 2007 .

[26]  Michele Missikoff,et al.  A Method for Ontology Modeling in the Business Domain , 2005, EMOI-INTEROP.