Requirements Reuse for Software Development
Oscar L´ pez Villegas o Technological Institute of Costa Rica San Carlos Regional Campus firstname.lastname@example.org ´ Miguel Angel Laguna University of Valladolid Department of Informatics email@example.com
This paper presents doctoral research addressing the problem of applying a reuse based approach to the early phases of softwaredevelopment, reusing requirements models. Our proposal is aimed at deﬁning 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 anoperative 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 effectivelybetter 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) . Different models of software reuse have been established, e.g. domain engineering - application engineering, proposed by U.S. Department of Defense , and thedevelopment for - development with reuse, proposed by REBOOT . 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 constructionblocks to compose software applications. On the other hand, in generation, the assets are viewed as active elements which might be transformed to obtain software applications. It could also be thought of as some hybrid compositiongeneration, as has been proposed at the University of Valladolid in the MRG approach (in Spanish, Modelo de Reutilizaci´ n GIRO). The MRG is based on ﬁne grain elements o(they can be of three kinds: analysis, design, and implementation) and large grain elements (structures that are formed by related assets of different levels of abstraction) where the generation of large grain elements can take place by composition of ﬁne grain elements in reuse time. This hybrid focus provides great ﬂexibility in the reuse process because the assets recovered from the repositoryare used to generate the new required elements, according to developer necessities. Software requirements have to be treated adequately inside of a reuse strategy. Both in composition and generation environments the reuse process is triggered by a set of requirements which are proposed by the developer. These requirements are supposed to satisfy reusing assets which are stored in the repository.Requirements have to previ-
Software production has a three-constrain-set: quality standards, time-to-market, and requirements. Software applications must satisfy strict quality standards, they must be produced as soon as possible, and they must satisfy a deﬁned set of system requirements. Related to quality standards and time-to-market, several software reuse approaches asalternative ways of solution have been proposed. Software reuse is aimed to signiﬁcantly increment the quality and productivity of software artifacts. Software quality is favored by using proven and validated components. Software productivity is improved by reducing timeto-market for software applications. Besides qualiﬁed software is supposed to adequately satisfy the system requirements, software...
Ler documento completo
Por favor, assinar para o acesso.