Shall be taken as a General research objective: perform the elicitation, analysis, specification, and validation of requirements, which facilitate common understanding between customers and developers, for the development of the process of legalization in the Directorate-General for registries and notaries. It implies in general sense with this work as a novelty. The creation of a computer system that integrates and controls all the information relating to the legalization, which facilitate the paperwork associated with a document control and operation of the process of legalization and signature of the document. 2. Methodology from the beginning worked basically oriented towards obtaining the requirements that provide the features required for the realization of legalization in the MPPRIJ. The development of such work was first investigated different activities that possesses the engineering of Requirements, analyzing the advantages and disadvantages of each of the activities.
Planteandose the use of the elicitation of requirements, because that is the process during which the information that determine the desired characteristics and constraints which must satisfy the software system are identified. Existing techniques for the development of the elicitation, were then analysed to contribute to the improvement in terms of quality and cost reduction in the construction of the final product. It was determined to use the brainstorm to view a general of the legalization process identifying the needs that the system must satisfy, these early ideas were implemented through interviews in which is desarrollareon each of the features that your system should meet, they served as support In Situ observation techniques and the study of the documentation. To carry out the modeling of such system conducted a study of the different trends and technologies in the development of the software. For the selection of the same is tube into account the dimensions of the solution and knowledge of developers in such tools. It was determined using: RUP because it defines every moment of the life cycle of the software, which artifacts, with what level of detail and which roles should be created.