Abstract

Introduction of software reuse into the development process significantly alters the life-cycle model, and has a tremendous impact on all of its software development phases. This also includes the phase of requirements engineering, its activities and the tools used in the process. To deal with the consequences of incorporating reuse in the early phases of software development, we suggest the use of a special process model, capable of simultaneously meeting the goals of software reuse and the goals of requirements engineering. The RARE (Reuse Assisted Requirements Engineering) method proposes such a model. RARE places a particular emphasis on two aspects of requirements processing, i.e. requirements classification and domain mapping. Both of these aspects are especially helpful in the automation of requirements refinement into reusable designs.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.