T-Reqs: Tool support for managing requirements in large-scale agile system development

Eric Knauss, Grischa Liebel, Jennifer Horkoff, Rebekka Wohlrab, Rashidah Kasauli, Filip Lange, Pierre Gildert

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

10 Citations (Scopus)

Abstract

T-Reqs is a text-based requirements management solution based on the git version control system. It combines useful conventions, templates and helper scripts with powerful existing solutions from the git ecosystem and provides a working solution to address some known requirements engineering challenges in large-scale agile system development. Specifically, it allows agile cross-functional teams to be aware of requirements at system level and enables them to efficiently propose updates to those requirements. Based on our experience with T-Reqs, we i) relate known requirements challenges of large-scale agile system development to tool support; ii) list key requirements for tooling in such a context; and iii) propose concrete solutions for challenges.

Original languageEnglish
Title of host publicationProceedings - 2018 IEEE 26th International Requirements Engineering Conference, RE 2018
EditorsDaniel Amyot, Walid Maalej, Guenther Ruhe
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages502-503
Number of pages2
ISBN (Electronic)9781538674185
DOIs
Publication statusPublished - 12 Oct 2018
Event26th IEEE International Requirements Engineering Conference, RE 2018 - Banff, Canada
Duration: 20 Aug 201824 Aug 2018

Publication series

NameProceedings - 2018 IEEE 26th International Requirements Engineering Conference, RE 2018

Conference

Conference26th IEEE International Requirements Engineering Conference, RE 2018
Country/TerritoryCanada
CityBanff
Period20/08/1824/08/18

Bibliographical note

Publisher Copyright:
© 2018 IEEE.

Other keywords

  • Large-scale agile
  • Requirements engineering
  • Tooling

Fingerprint

Dive into the research topics of 'T-Reqs: Tool support for managing requirements in large-scale agile system development'. Together they form a unique fingerprint.

Cite this