Tutorial 3: domain engineering – using domain concepts to guide software design

  • Authors:

  • Iris Reinhartz-Berger;Arnon Sturm;Yair Wand

  • Affiliations:

  • Department of Management Information Systems, University of Haifa, Haifa, Israel;Department of Information System Engineering, Ben-Gurion University of the Negev, Beer Sheva, Israel;Department of Management Information Systems, University of Haifa, Haifa, Israel

  • Venue:
  • ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

As the variability of information and software systems has increased, the need for an engineering discipline concerned with building reusable assets (such as specification sets, patterns and components) on one hand and representing and managing knowledge in specific domains on the other hand has become crucial. This discipline, called domain engineering, supports the notion of a domain, defined as a set of applications that use a set of common concepts for describing requirements, problems and capabilities. The purpose of domain engineering is to identify, model, construct, catalog, and disseminate a set of software artifacts that can be applied to existing and future software in a particular application domain. As such, it can support the effective and efficient management and development of software assets. Hence, it is important to introduce this discipline among software engineering practitioners and researchers.