[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
10.5555/776816.776881acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

Towards systematic recycling of systems requirements

Published: 03 May 2003 Publication History

Abstract

Many (technical) systems are not developed from scratch but as an evolution of existing systems. Consequently, a large portion of the system requirements employed can be recycled when building the next version of the product. Usually, this recycling step is performed unsystematically, i.e. simply by copying and modifying complete requirements documents.In this paper, we present in a case study a lightweight requirements recycling approach which evolved from observations and concrete needs of projects at Daimler-Chrysler Passenger Car Development. The basic idea of the approach is separation of model-dependent from model-independent requirements on the same level of abstraction. This notion is supported by document structures, criteria for identifying reusable requirements and tool support.The paper presents the core elements of the approach and provides observations and valuable experiences we made in the projects.

References

[1]
T. Biggerstaff, A. Perlis (Ed.). Software Reusability. Volume 1, Concepts and Models. ACM Press Frontier Series, 1989.
[2]
F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal. A System of Patterns. John Wiley & Sons. 1996.
[3]
P. Clemens and L. Northrop. Software Product Lines: Practices and Patterns. Addison Wesley, 2001.
[4]
A.M. Davis. Predictions and Farewells. IEEE Software. Vol. 15, No. 4, pp. 6--9, 1998.
[5]
F. Kiedaisch, M. Pohl, J. Weisbrod, S. Bauer, and S. Ortmann, Experiences on Outsourcing Requirements Specifications, In Proc. of EuroSPI'01, pp. 10--16 to 10--31, 2001.
[6]
A.v. Knethen, B. Paech, F. Kiedaisch, and F. Houdek. Systematic Requirements Recycling through Abstraction and Traceability. In Proc. of the IEEE Joint Int. Requirements Eng. Conf, pp. 273--281, Sept. 2002.
[7]
J. Kuusela and J. Savolainen. Requirements Engineering for Product Lines. In Proc. of the 22nd Int. Conf. on Software Eng., ICSE'00, pp. 61--69, June 2000.
[8]
D. Parnas, P. Clements, and D. Weiss. The Modular Structure of Complex Systems. IEEE Transaction on Software Engineering. Vol. 11, pp. 259--266, 1985.

Cited By

View all
  • (2019)The impact of requirements on systems development speedRequirements Engineering10.1007/s00766-019-00319-824:3(315-340)Online publication date: 1-Sep-2019

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '03: Proceedings of the 25th International Conference on Software Engineering
May 2003
841 pages
ISBN:076951877X

Sponsors

Publisher

IEEE Computer Society

United States

Publication History

Published: 03 May 2003

Check for updates

Qualifiers

  • Article

Conference

ICSE03
Sponsor:

Acceptance Rates

ICSE '03 Paper Acceptance Rate 42 of 324 submissions, 13%;
Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 14 Jan 2025

Other Metrics

Citations

Cited By

View all
  • (2019)The impact of requirements on systems development speedRequirements Engineering10.1007/s00766-019-00319-824:3(315-340)Online publication date: 1-Sep-2019

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media