Navigation

Agile Requirements

News


  • [book] bibtex
    D. Leffingwell, Agile software requirements: lean requirements practices for teams, programs, and the enterprise, Addison-Wesley Professional, 2010.
    @book{leffingwell2010agile, title={Agile software requirements: lean requirements practices for teams, programs, and the enterprise},
      author={Leffingwell, Dean},
      year={2010},
      publisher={Addison-Wesley Professional} }
  • G. Lucassen, F. Dalpiaz, J. M. E. M. van der Werf, and S. Brinkkemper, "Improving agile requirements: the Quality User Story framework and tool," Requirements Engineering, vol. 21, iss. 3, pp. 383-403, 2016.
    @Article{Lucassen2016,
      author="Lucassen, Garm and Dalpiaz, Fabiano and van der Werf, Jan Martijn E. M. and Brinkkemper, Sjaak", title="Improving agile requirements: the Quality User Story framework and tool", journal="Requirements Engineering", year="2016", month="Sep", day="01", volume="21", number="3", pages="383--403", abstract="User stories are a widely adopted requirements notation in agile development. Yet, user stories are too often poorly written in practice and exhibit inherent quality defects. Triggered by this observation, we propose the Quality User Story (QUS) framework, a set of 13 quality criteria that user story writers should strive to conform to. Based on QUS, we present the Automatic Quality User Story Artisan (AQUSA) software tool. Relying on natural language processing (NLP) techniques, AQUSA detects quality defects and suggest possible remedies. We describe the architecture of AQUSA, its implementation, and we report on an evaluation that analyzes 1023 user stories obtained from 18 software companies. Our tool does not yet reach the ambitious 100 {\%} recall that Daniel Berry and colleagues require NLP tools for RE to achieve. However, we obtain promising results and we identify some improvements that will substantially improve recall and precision.", issn="1432-010X", doi="10.1007/s00766-016-0250-x", url="https://doi.org/10.1007/s00766-016-0250-x" }
  • [inproceedings] bibtex
    F. Paetsch, A. Eberlein, and F. Maurer, "Requirements engineering and agile software development," in Proc. WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003., 2003, pp. 308-313.
    @INPROCEEDINGS{1231428,
      author={F. {Paetsch} and A. {Eberlein} and F. {Maurer}},
      booktitle={WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003.},
      title={Requirements engineering and agile software development},
      year={2003},
      volume={},
      number={},
      pages={308-313},
      abstract={This article compares traditional requirements engineering approaches and agile software development. Our paper analyzes commonalities and differences of both approaches and determines possible ways how agile software development can benefit from requirements engineering methods.},
      keywords={software development management;formal specification;program verification;requirements engineering;agile software development;requirement validation;Programming;Collaborative software;Collaborative work;Documentation;Customer satisfaction;Software engineering;Knowledge engineering;Collaboration;Context modeling;System analysis and design},
      doi={10.1109/ENABL.2003.1231428},
      ISSN={1080-1383},
      month={June},
     }
  • [inproceedings] bibtex
    R. Elamin and R. Osman, "Towards Requirements Reuse by Implementing Traceability in Agile Development," in Proc. 2017 IEEE 41st Annual Computer Software and Applications Conference (COMPSAC), 2017, pp. 431-436.
    @INPROCEEDINGS{8029969,
      author={R. {Elamin} and R. {Osman}},
      booktitle={2017 IEEE 41st Annual Computer Software and Applications Conference (COMPSAC)},
      title={Towards Requirements Reuse by Implementing Traceability in Agile Development},
      year={2017},
      volume={2},
      number={},
      pages={431-436},
      abstract={Requirements reusability within agile development improves software quality and team productivity. One method to implement requirements reusability is traceability, in which relations and dependencies between requirements and artifacts are identified and linked. In this paper, we propose a semiautomated methodology to implement traceability in the agile development process in order to achieve requirements reusability. The main feature of our methodology is the coupling of semi-automated semantic trace generation with the outputs of the agile development process, thus facilitating requirements and artifact reuse. In contrast to previous work, this methodology is specifically designed for practical agile processes and artifacts. Our methodology will be implemented as a component within an existing open source agile tool in order to have minimal impact on the development process. This paper fills a current gap in the area of requirements reusability through traceability and contributes to the limited existing work in agile traceability methodologies.},
      keywords={software prototyping;software quality;software reusability;requirements reuse;requirements reusability;software quality;team productivity;agile development process;semi-automated semantic trace generation;artifact reuse;open source agile tool;agile traceability methodologies;Tools;Automation;Semantics;Couplings;Software;Manuals;Productivity;Requirements reus;Requirements traceabilit;Agile development;Automatio;Requirements reusability},
      doi={10.1109/COMPSAC.2017.250},
      ISSN={0730-3157},
      month={July},
     }
Webmaster/f+nz (meier@stmnbte.unxrkxwi-old/sodenbuhdqrg.deeu) (Changed: 2020-07-31)