Software requirements: Prototyping, legacy software, and document analysis.

Abstract

This paper presents a literature review about alternatives for determination of requirements in software development projects. The literature searching begins from a fundamental principle, request information about methods of determination of requirements that do not need a high percentage of interaction with users or customers. This usually happens because users or customers don’t have time as it happens when traditional methods are used.

The search for information was made taking into account the low interaction with the user or customer and in this vein, it was needed to expand the search horizon until 2000 and it includes classic texts in the study area. The search results provided insights about the techniques of requirements engineering, whose main characteristic is to minimize the interaction with users, such as, prototyping, document analysis and legacy software which are the closest ones to the search condition.