Dines Bjørner
Technical University of Denmark, DK-2800 Lyngby, Denmark
db@it.dtu.dk
http://www.it.dtu.dk/~db
Abstract
Before software can be designed its requirements must be stated. Before requirements can be stated the application domain must be described. In this talk we outline basic facets of domain engineering while, in the interest of brevity and time, focusing on a very simple two overhead foil technical example of a domain description: That of the strategic, tactical and operational (resource) management as well as the operations of an enterprise: From resource acquisition/"down-sizing" via spatial allocation and scheduling to task allocation and actual deploy- ment.
We modestly suggest that large scale application domain descriptions be the researched and developed: For transportation (road, rail, air, sea), financial service industry(banking, insurance, broherage, bond & stock exchange, portofolio management, clearing, etc.), manufacturing industry (consumer, producer, supplier and trader), healthcare sector (from rural nurse and clinics, via physicians, test labs., and hospitals, to health insurance, phramacies and govt. regulatory agencies), etc. Such domain models have shown useful in readily serving as bases for speedily developed requirements and software - thus alleviating some of the problems mentioned in the PITAC report.
Last Updated: June 1, 2000 by Elisabetta Ferrando