PV258 Requirements Engineering in Agile Software Development

Fakulta informatiky
jaro 2016
Rozsah
2/0. 2 kr. (plus ukončení). Ukončení: zk.
Vyučující
Bruno Rossi, PhD (přednášející), prof. RNDr. Tomáš Pitner, Ph.D. (zástupce)
doc. Ing. RNDr. Barbora Bühnová, Ph.D. (přednášející)
Garance
doc. RNDr. Eva Hladká, Ph.D.
Katedra počítačových systémů a komunikací – Fakulta informatiky
Dodavatelské pracoviště: Katedra počítačových systémů a komunikací – Fakulta informatiky
Rozvrh
Čt 12:00–13:50 A319
Předpoklady
No prerequisites are compulsory. The students are expected to have good understanding of software development models (as taught in PB007), and some basic knowledge about object-oriented development and programming (e.g. Java). Good level of spoken and written English is also appreciated.
Omezení zápisu do předmětu
Předmět je otevřen studentům libovolného oboru.
Předmět si smí zapsat nejvýše 40 stud.
Momentální stav registrace a zápisu: zapsáno: 0/40, pouze zareg.: 0/40, pouze zareg. s předností (mateřské obory): 0/40
Cíle předmětu
At the end of the course students should: have a clear idea of processes, tools and techniques used in requirements engineering;
understand concepts such as agile requirements elicitation, modelling, validation and verification.
be able to model requirements up to the design phase;
be able to conduct an agile development iteration;
making reasoned decisions about prioritization of requirements;
understand the differences between different requirements modelling approaches (agile and non-agile);
Osnova
  • Introduction, course modality and evaluation. Review of traditional development processes (waterfall, RUP, etc...);
    From lean to agile. Overview of SCRUM, XP, and other agile approaches;
    The Requirements Engineering (RE) process. RE differences for Agile and traditional development processes;
    The traditional distinction in functional vs non-functional (quality) requirements and how these are managed within agile approaches;
    The agile approach in modelling requirements: from user stories to acceptance testing;
    User stories, CRC cards, acceptance tests. The product and sprint backlogs. How to automate acceptance testing. Code examples by using the Java programming language;
    Managing requirements prioritization in traditional versus agile approaches. From the Analytic Hierarchy process to the planning game in agile;
    Effort estimation: using planning poker for effort estimation and to determine project velocity;
    Release planning in agile vs traditional development models;
    Emergence of the software architecture from requirements: the agile view;
Literatura
  • LEFFINGWELL, Dean. Agile software requirements : lean requirements practices for teams, programs, and the enterprise. Upper Saddle River, NJ: Addison-Wesley, 2011, xxxv, 518. ISBN 9780321635846. info
Výukové metody
Frontal lectures and a small interesting group project developed during lectures to see the practical application of theory and techniques seen during the course;
Metody hodnocení
100 minutes examination with questions about the material seen during the course.
Vyučovací jazyk
Angličtina
Informace učitele
Bruno Rossi is Assistant Professor, Department of Computer Systems and Communications, member of LASARIS (Lab of Software Architectures and Information Systems). More details at the profile page: http://lasaris.fi.muni.cz/members/brossi
Další komentáře
Studijní materiály
Předmět je vyučován jednorázově.
Předmět je zařazen také v obdobích jaro 2015, jaro 2017, jaro 2018, jaro 2019, jaro 2020, jaro 2021, jaro 2022, jaro 2023, jaro 2024.