The Generalized Requirement Approach for Requirement Validation with Automatically Generated Program Code

Abstract

Requirements gathering is one of the first steps in the software development process. Gathering business requirements, especially when the final product requirements are dictated by a known client, can be a difficult process. Although clients know their own business best, often an idea about a new business product is obscure and described using general terms that contribute greatly
to common misunderstandings. Business requirement verification in the event that requirements are gathered using text and graphics can be a slow, error-prone, and expensive process. Misunderstandings and omitted requirements contribute to the need for revisions and increase project costs and delays. This article proposed a new approach to the business software development process that is focused on the validation of business requirements during the requirement negotiation process.

The process of the business requirement negotiation is guided by a set of predefined questions. These questions are guidelines for specifying a sufficient level of requirement details in order to generate sources and executable code for requirement validation without manual programming. Besides requirement documenting, tracking, and validating, this method addresses requirement management syndromes and the specification of an insufficient level of details.