FI:PV258 Requirements Engineering - Informace o předmětu
PV258 Requirements Engineering in Agile Software Development
Fakulta informatikyjaro 2015
- 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
- St 12:00–13:50 C525
- Předpoklady
- The students (master or last-year bachelor) are expected to have good understanding of software development models (as taught in PB007), object-oriented development and Java programming. Good level of spoken and written English is a must.
- 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
- The main aim is to let students acquire theoretical insights and practical experience from processes, tools and techniques that are used in requirements engineering in agile software development. Students will gather insights about requirements engineering supported by agile methodologies, understanding also when the usage of such approaches is appropriate. After the course, students will have a good understanding about agile requirements elicitation, modelling, validation and verification.
- 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;
Modelling requirements with UML and using OCL to model the constraints in traditional development processes - the traditional distinction in functional vs non-functional (quality) requirements;
The agile approach in modelling requirements: from user stories to acceptance testing. Modelling of non-functional (quality) requirements in agile;
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;
Using the planning game 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;
- Introduction, course modality and evaluation. Review of traditional development processes (waterfall, RUP, etc...);
- 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 group projects with focus on the application of the 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ě.
- Statistika zápisu (jaro 2015, nejnovější)
- Permalink: https://is.muni.cz/predmet/fi/jaro2015/PV258