Welcome to the InfoSci Platform
Requirements Elicitation by Defect Elimination: An Indian Logic Perspective

Requirements Elicitation by Defect Elimination: An Indian Logic Perspective

G. S. Mahalakshmi, T. V. Geetha
Copyright: © 2012 |Pages: 20
ISBN13: 9781466602618|ISBN10: 1466602619|EISBN13: 9781466602625
DOI: 10.4018/978-1-4666-0261-8.ch021
Cite Chapter Cite Chapter

MLA

Mahalakshmi, G. S., and T. V. Geetha. "Requirements Elicitation by Defect Elimination: An Indian Logic Perspective." Software and Intelligent Sciences: New Transdisciplinary Findings, edited by Yingxu Wang, IGI Global, 2012, pp. 372-391. https://doi.org/10.4018/978-1-4666-0261-8.ch021

APA

Mahalakshmi, G. S. & Geetha, T. V. (2012). Requirements Elicitation by Defect Elimination: An Indian Logic Perspective. In Y. Wang (Ed.), Software and Intelligent Sciences: New Transdisciplinary Findings (pp. 372-391). IGI Global. https://doi.org/10.4018/978-1-4666-0261-8.ch021

Chicago

Mahalakshmi, G. S., and T. V. Geetha. "Requirements Elicitation by Defect Elimination: An Indian Logic Perspective." In Software and Intelligent Sciences: New Transdisciplinary Findings, edited by Yingxu Wang, 372-391. Hershey, PA: IGI Global, 2012. https://doi.org/10.4018/978-1-4666-0261-8.ch021

Export Reference

Mendeley
Favorite

Abstract

This paper aims to develop an Indian-logic based approach for automatic generation of software requirements from a domain-specific ontology. The structure of domain ontology is adapted from Indian logic. The interactive approach proposed in this paper parses the problem statement, and the section of domain ontology, which matches the problem statement, is identified. The software generates questions to stakeholders based on the identified concepts. The answer is analysed for presence of flaws or inconsistencies. Subsequent questions are recursively generated to repair the flaw in the previous answer. These answers are populated into requirements ontology, which contains problem specific information coupled with the interests of the stakeholder. The information gathered is stored in a database, which is later segregated into functional and non-functional requirements. These requirements are classified, validated and prioritized based on combined approach of AHP and stakeholders’defined priority. Conflict between requirements is resolved by the application of cosine correlation measure.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.