A Comparative Template for Reliable Requirement Specification

Abstract

ABSTRACT For documenting the groundwork pitch of requirements, many types of requirement specification template are available containing some specific requirement parameter which eventually recites the root requirement for constructing the design, but they are not good enough to make the template reliable requirement specification. In this paper a reliable requirement specification template has been proposed having some reliable parameter which will assess the reliability of the individual requirement before finalizing the requirement documentation which reflects the reliability of requirements at early stage of software development. Keywords Software Reliability, requirement specification 1. INTRODUCTION Many years of the effort have gone into study of hardware reliability particularly in the area of complex electronic assemblies; however the research scholars and practitioners are giving attention to software reliability estimation as the major research area since last two decades. [3] Since the software reliability becomes the most important characteristics regarding computer system so it is necessary to measure and manage the reliability of the computer software, for that purpose many software reliability models have been proposed for the study of software reliability but as we know that most of the models are made for estimating reliability at testing phase which comes into later stage of Software Life Cycle (SLC). The failure of software depends on rooted defects that didn‟t come into face at early stage of requirement gathering which carried on in the further phases of development and testing and these defects will greatly affect the reliability of the software. If the reliable requirements are gathered at initial stage then the probability of software failure (program behavior doesn‟t meet the user‟s requirement within the given time of execution i.e. failure totally depends on the leakage of user oriented concept) will certainly be decrease specifically. For giving weightage to early Requirement Suzanne and James Robertson proposed a „Quality Gateway to find requirements related defects as early as they can be identified and hence prevent them from being incorporated in the design and implementation.‟ For that purpose they have suggested Volere specification template for software specification [1, 2]