A new metric for detecting conflict in functional software requirements /
Abstract (Summary)Typically, the development of software system starts with a goal. The goal is implemented by following a methodology consisting of phases. Initially, the goal is formulated as functional requirements when stakeholders of the software system meet and discuss what the software system should do in order fulfill satisfy needs. The functional software requirement document is then converted to software design document either through conceptual model, software code or both. After, the system is tested rigorously before it is implemented. Since the development of a software system consists of phases with each phase depending on prior stages, an inconsistency made in the initial phase of development such as in the requirement specification phase, may be propagated into other phases. A methodology for detecting conflict in functional software requirements through level of Potential Structural Inconsistency (PSI) is presented in this research. This is accomplished, by representing functional software requirements stated in natural language as structural model (i.e. conceptual model) and similarities between these models are obtained as a level of potential structural inconsistency. Sample functional software requirements are analyzed using this methodology and the inconsistency is compared with a particular type of conflict. In conclusion, various inferences are made based on the new methodology and recommendations are given for further improvements and future research.
School:Iowa State University
School Location:USA - Iowa
Source Type:Master's Thesis
Date of Publication: