Towards use case based software reuse

Kuniharu Yamada, Shingo Takada, Norihisa Doi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Citation (Scopus)

Abstract

The benefits of software reuse is said to increase if reuse is considered early in the development process. Consequently, recent years have seen more work on reusing requirements. However, most of these work focus on reusing just requirements without considering other artifacts, such as design and code. Such artifacts, however, are related to each other, i.e. design and code are created to realize requirements, and software reuse should take this into account. This paper proposes an approach to software reuse based on use cases. Our approach takes an initial set of use cases as "keys" to search for reusable software artifacts, including use cases, class diagrams, and code of previously developed applications. We have implemented a tool called ARC that is based on our proposed approach. It enables the developer to start reuse early in the development process while enabling him/her to use the reused requirements in the design and coding phases.

Original languageEnglish
Title of host publicationProceedings of the Eighth IASTED International Conference on Software Engineering and Applications
EditorsM.H. Hamza
Pages725-730
Number of pages6
Publication statusPublished - 2004 Dec 1
EventProceedings of the Eighth IASTED International Conference on Software Engineering and Applications - Cambridge, MA, United States
Duration: 2004 Nov 92004 Nov 11

Publication series

NameProceedings of the Eigtht IASTED International Conference on Software Engineering and Applications

Other

OtherProceedings of the Eighth IASTED International Conference on Software Engineering and Applications
CountryUnited States
CityCambridge, MA
Period04/11/904/11/11

Keywords

  • Software development
  • Software reuse
  • Software tools
  • Use case

ASJC Scopus subject areas

  • Engineering(all)

Fingerprint Dive into the research topics of 'Towards use case based software reuse'. Together they form a unique fingerprint.

Cite this