Domain theory: practice and theories a discussion of possible research topics

Authors:
Dines Bjørner
Affiliations:
Department of Computer Science and Engineering, Institute of Informatics and Mathematical Modelling, Technical University of Denmark, Lyngby, Denmark
Venue:
ICTAC'07 Proceedings of the 4th international conference on Theoretical aspects of computing
Year:
2007

Citing 2
Cited 5

Software Engineering 1: Abstraction and Modelling (Texts in Theoretical Computer Science. An EATCS Series)

Software Engineering 1: Abstraction and Modelling (Texts in Theoretical Computer Science. An EATCS Series)
Software Engineering 3: Domains, Requirements, and Software Design (Texts in Theoretical Computer Science. An EATCS Series)

Software Engineering 3: Domains, Requirements, and Software Design (Texts in Theoretical Computer Science. An EATCS Series)

From Domain to Requirements

Concurrency, Graphs and Models
Domain science and engineering from computer science to the sciences of informatics. Part II: science

Cybernetics and Systems Analysis
Domains: their simulation, monitoring and control-a divertimento of ideas and suggestions

Rainbow of computer science
Compositionality: ontology and mereology of domains

Concurrency, Compositionality, and Correctness
Rôle of domain engineering in software development—why current requirements engineering is flawed !

PSI'09 Proceedings of the 7th international Andrei Ershov Memorial conference on Perspectives of Systems Informatics

Quantified Score

Hi-index	0.00

Visualization

Abstract

By a domain we mean a universe of discourse. Typical examples are (partially) man-made universes of discourse - such as Air Traffic, Airports, Financial Services (banks, insurance companies, securities trading [brokers, traders, stock exchanges]), Health Care (hospitals etc.), Secure IT Systems (according to Intl. ISO/IEC Standard 17799), The Market (consumers, retailers, wholesalers, producers, "the supply chain"), Transportation (road, air, sea and/or rail transport), etc. We shall outline how one might describe such (infrastructure component) domains, informally and formally - what the current descriptional limitations appear to be, and, hence, the prospects for future research as well as practice. The current paper is based on Part IV, Chaps. 8-16 of [3]. The volume is one of [1, 2, 3]. The aim of this paper is to suggest a number of areas of domain theory and methodology research.