No abstract

No abstract

The success of software projects depends on fully conveyed requirements. Contribution of stakeholders contributing in software requirements have a place with distinctive domains, because of which ambiguities, inconsistencies might arise moreover giving rise to incorrectness. Many tools are available for software requirements verification and validation but the issue of stakeholders belonging to different domains is still under consideration. As these requirements are not understood properly, it causes schedule delay and greater cost in the last stages of software. Requirements verification and validation are the most vital activities in requirement engineering that guarantees software quality and has an extraordinary impact on software cost and its success. The requirements verification and validation are an affirmation that the product requirements record is free of unwanted requirements and totally reliable. Keeping in mind the end goal of removing conflict, recognizing failures and making the product requirements document completely useful is the key component. So these requirements should be appropriately confirmed and accepted by the clients before conveying to the development team. Thus, ontology might be picked as an answer for checking and approving the requirements among stakeholders of distinctive domains. In this study improving requirement verification and validation process through ontology. We have used expert reviews and case study to evaluate the developed ontology that indicates different concepts, properties and constraints in the process of requirement verification and validation. With the help of the developed ontology, it is shown that its use for requirement verification and validation shows improvement in consistency, applicability and other factors.