A knowledge based component/service repository to enhance analysts' domain knowledge for requirements analysis

Padmal Vitharana, Hemant Jain, Fatemeh Zahedi

Research output: Contribution to journalArticlepeer-review

20 Scopus citations


Knowledge of the business domain (e.g., insurance claim, human resources) is crucial to analysts' ability to conduct good requirements analysis (RA). However, current practices afford little assistance to analysts in acquiring domain knowledge. We argue that traditional reuse repositories could be augmented by adding rich faceted information on component/services and artifacts such as business-process templates to help analysts acquire domain knowledge during RA. In this paper, we present the design of a Knowledge Based Component Repository (KBCR) for facilitating RA. Then, we report on the design and development of a KBCR prototype. We illustrate its application in a system that is populated with components and process templates for the auto insurance claim domain. An empirical study was conducted to assess its effectiveness in improving RA. Results showed that KBCR enhanced analysts' business domain knowledge and helped them better prepare for RA. Our key research contribution is to offer analysts a rich repository (i.e., KBCR) containing domain knowledge that they could utilize to acquire domain knowledge that is crucial for carrying out RA. While repositories of reusable components have been employed for some time, no one has used such repositories to help analysts acquire domain knowledge in order improve the RA of the system.

Original languageEnglish (US)
Pages (from-to)24-35
Number of pages12
JournalInformation and Management
Issue number1
StatePublished - Jan 2012


  • Component-based development
  • Design research
  • Domain knowledge
  • Requirements analysis

ASJC Scopus subject areas

  • Management Information Systems
  • Information Systems
  • Information Systems and Management


Dive into the research topics of 'A knowledge based component/service repository to enhance analysts' domain knowledge for requirements analysis'. Together they form a unique fingerprint.

Cite this