Domain-Specific Requirement Engineering

For domain specific software, i.e. software developed to satisfy certain needs in a particular domain, domain experts (who are usually not software engineers and may not be knowledgeable about computing) play an important role. In order to involve domain experts in the software development process it is important to use a vocabulary that is familiar to them (i.e., based on domain abstractions), a paradigm which is called domain-specific software engineering [1]. Domain-specific models and languages are already well accepted, but Bryant, Gray & Mernik [1] proposed in addition that requirement specification should be carried out in a domain-specific manner. They argue “Providing a requirement specification in terms of domain abstractions will also make such specifications easier for domain experts who are not software engineers to validate, because the specification will be expressed in terms of concepts which they understand”. We want to go one step further and allow domain experts and other stakeholders to be actively involved in the requirements engineering process. For this purpose, we are developing a number of tools.

[1]    B.R. Bryant, J. Gray, and M. Mernik, "Domain-specific software engineering," In Proceedings of the FSE/SDP workshop on Future of software engineering research, ACM, 2010, pp. 65-68.

Related Publications