Requisitos

Requirements Reuse for Software Development
Oscar L´ pez Villegas o Technological Institute of Costa Rica San Carlos Regional Campus [e-mail] ´ Miguel Angel Laguna University of Valladolid Department of Informatics [e-mail]

Abstract
This paper presents doctoral research addressing the problem of applying a reuse based approach to the early phases of software development, reusing requirements models. Our proposal is aimed at defining meta-model for requirements diagrams, a Petri net based approach for representation of requirements models, and an approach to compare the requirements proposed by the software developer against the domain requirements models stored in a repository. Being able to determine the similarity between the requirements models, through an operative support, makes it possible to answer the developer´s queries ensuring the system requirements satisfaction by selecting assets from complex structures called mecanos.

nents to make the same application, or a similar one, over and over. True software reuse consists of the systematic use of experience and previously developed systems as assets which have to be cultivated to effectively better the future development of applications. The asset term refers to any reusable product in the software life cycle (models and domain architectures, requirements, designs, code, data base components, documentation, tests) [9]. Different models of software reuse have been established, e.g. domain engineering - application engineering, proposed by U.S. Department of Defense [5], and the development for - development with reuse, proposed by REBOOT [9]. Activities of development for reuse and development with reuse are related to a components library and based on operative support to enact, manage and use the reusable components. The assets may be reused from two perspectives: composition and generation. In composition the assets are taken as passive elements which act like construction