Overlaying Conceptualizations for Managing Complexity of Scenario Specifications

Most conventional conceptual modeling approaches are not putting into a foreground interaction dependencies between actors. This is one of the main reasons why it is difficult to apply them for managing complexity of conceptual representations. The goal of this paper is to present conceptual modeling method, which allows constructing graphical representations of scenarios with a more comprehensible structure. Using simple interaction loops between organizational and technical components help designers to separate crosscutting concerns in system engineering without the requirement to specify a complete solution. The examples of sequential, iterative, parallel and alternative behavior are analyzed to demonstrate conceptual descriptions of use-case scenarios. The overlaying and underlying interaction loops among actors are easier to understand, extend and maintain.

[1]  Joerg Evermann,et al.  Ontology Based Object-Oriented Domain Modeling: Representing Behavior , 2009, J. Database Manag..

[2]  Takeo Kanade,et al.  Future Internet – FIS 2008 , 2009 .

[3]  Remigijus Gustas,et al.  Conceptual Modeling and Integration of Static and Dynamic Aspects of Service Architectures , 2010, ONTOSE.

[4]  Monique Snoeck,et al.  Object-Oriented Enterprise Modelling with MERODE , 1999 .

[5]  Gerd Wagner,et al.  The Agent-Object-Relationship metamodel: towards a unified view of state and behavior , 2003, Inf. Syst..

[6]  Jan L. G. Dietz,et al.  DEMO: Towards a discipline of organisation engineering , 2001, Eur. J. Oper. Res..

[7]  Eva Söderström,et al.  Information Systems Engineering: From Data Analysis to Process Networks , 2008 .

[8]  Gustas Remigijus,et al.  Pragmatic-Driven Approach for Service-Oriented Analysis and Design , 2008 .

[9]  Terry Winograd,et al.  Understanding computers and cognition - a new foundation for design , 1987 .

[10]  Bernhard Thalheim,et al.  Conceptual Modeling for E-Business and the Web , 2000, Lecture Notes in Computer Science.

[11]  M. Bunge Treatise on basic philosophy , 1974 .

[12]  Nicola Guarino,et al.  Towards an Ontological Foundation for Services Science , 2009, FIS.

[13]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[14]  Martin Glinz,et al.  Problems and deficiencies of UML as a requirements specification language , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[15]  Glenford J. Myers,et al.  Structured Design , 1999, IBM Syst. J..

[16]  Ivar Jacobson,et al.  Aspect-oriented software development with use cases , 2005, Addison Wesley object technology series.

[17]  Remigijus Gustas Modeling Approach for Integration and Evolution of Information System Conceptualizations , 2011, Int. J. Inf. Syst. Model. Des..

[18]  Peter J. Denning,et al.  Completing the Loops , 1995 .

[19]  Jaap Gordijn,et al.  Business Modelling Is Not Process Modelling , 2000, ER.