PV258 Software Requirements Engineering

Fakulta informatiky
jaro 2018
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)
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
Po 10:00–11:50 A318
Předpoklady
No prerequisites are compulsory. The students are expected to have an understanding of software development models and different UML diagram types (as taught in the PB007 Software Engineering course). The course is taught entirely in the English language.
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
Objectives of the course are to:
- provide an overview of different Software Requirements types (functional vs non-functional (quality), constraints, business requirements, business rules, user and system requirements);
- explain the Software Requirements Process (ISO/IEC/IEEE 29148 Standard for Requirements Engineering) also in agile contexts;
- provide the instruments for the definition of user requirements;
- describe different software requirements elicitation modalities;
- provide approaches for requirements analysis and verification & validation;
- provide approaches to manage requirements prioritization;
- provide approaches for software requirements effort estimation;
- describe the software architecture and the relevance in the context of software requirements.
- describe how to decompose system models: abstraction, & different system views for the definition of the software architecture from the requirements;
- describe how to model Non-Functional Requirements (NFR);
Výstupy z učení
At the end of the course students will:
- have a clear understanding about processes, tools and techniques used in requirements engineering;
- understand the concepts of software requirements elicitation, modelling, validation and verification;
- be able to model software requirements rigorously according to the latest requirements engineering standards;
- be able to conduct a prioritization process for software requirements according to different approaches;
- be able to make a reasoned choice about the best approach for requirements modelling given the context of a project;
- be able to proper manage requirements and their quality concerns;
- understand the differences between different requirements modelling approaches (agile and non-agile);
- be able to generate and maintain a software requirements specification document
Osnova
  • - Software Requirements types (functional vs non-functional (quality), constraints, business requirements, business rules, user and system requirements);
    - The Software Requirements Process (ISO/IEC/IEEE 29148 Standard for Requirements Engineering);
    - Business Requirements: vision, scope, context diagram, ecosystem maps, events lists, feature trees, the goal-design scale;
    - User Requirements: User Stories & Use cases modelling;
    - Requirements elicitation modalities: Stakeholders Analysis, design/brainstorming workshops, prototyping, pilot experiments, cost/benefit & risk analysis;
    - Requirements analysis. (C)lass (R)esponsability (C)ollaborators cards. Linking Requirements to UML Analysis Models;
    - Requirements Verification & Validation: Consistency checks, CRUD checks, Acceptance Testing;
    - Managing requirements prioritization. Analytic Hierarchy (AHP) process, Software Quality Deployment Function (SQFD), the Agile Planning Game;
    - Requirements Effort estimation & Project Velocity: Early models of effort estimation (LOCs based). Three modalities of estimation: COCOMO II, k-Nearest Neighbour, Planning Poker;
    - Emergence of the software architecture from requirements. Decomposing system models: abstraction, & different system views. The Attribute-Driven Design (ADD) Method;
    - Modelling Non-Functional Requirements (NFR): SQuaRE (Software product Quality Requirements and Evaluation) & ISO/IEC 25010;
    - From Lean to Agile Methodologies. Overview of SCRUM, XP, and other agile approaches in relation to Requirements Engineering;
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
  • BASS, Len, Paul CLEMENTS a Rick KAZMAN. Software architecture in practice. 2nd ed. Boston: Addison-Wesley, 2003, xxii, 528. ISBN 0321154959. info
  • LAUESEN, S. Software Requirements: Styles & Techniques. Addison-Wesley Professional, 2002. ISBN 978-0-201-74570-2. 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
Další komentáře
Studijní materiály
Předmět je vyučován každoročně.
Předmět je zařazen také v obdobích jaro 2015, jaro 2016, jaro 2017, jaro 2019, jaro 2020, jaro 2021, jaro 2022, jaro 2023, jaro 2024, jaro 2025.