Abstract: | Much of software engineering and knowledge engineering has concentrated on generic languages and methods which are supposed to be transferable between domains. By contrast, engineers working in real domains usually employ domain-specific methods and terminology which have evolved from their experience in getting the job done. This paper argues that we have paid too little attention to instantiating generic methods to the demaind of specific engineering problems. We advocate narrow but deep studies of careful chosen domains, with the aim of harnessing domain-specific problem descriptions to guide the construction of software specifications.
|