FI:PV260 Software Quality - Course Information
PV260 Software QualityFaculty of Informatics
- Extent and Intensity
- 2/2/0. 3 credit(s) (plus extra credits for completion). Recommended Type of Completion: zk (examination). Other types of completion: k (colloquium).
- doc. Ing. RNDr. Barbora Bühnová, Ph.D. (lecturer)
Bruno Rossi, PhD (lecturer)
RNDr. Ondřej Krajíček (lecturer)
Mgr. Michal Abaffy (seminar tutor)
Mgr. Radim Göth (seminar tutor)
RNDr. Stanislav Chren (seminar tutor)
- Guaranteed by
- doc. Ing. RNDr. Barbora Bühnová, Ph.D.
Department of Computer Systems and Communications - Faculty of Informatics
Supplier department: Department of Computer Systems and Communications - Faculty of Informatics
- Prerequisites (in Czech)
- PB007 Software Engineering I && ( PV168 Seminar in Java programming || PV178 Introduction to C#/.NET )
- Course Enrolment Limitations
- The course is also offered to the students of the fields other than those the course is directly associated with.
The capacity limit for the course is 70 student(s).
Current registration and enrolment status: enrolled: 0/70, only registered: 0/70, only registered with preference (fields directly associated with the programme): 0/70
- Fields of study the course is directly associated with
- there are 59 fields of study the course is directly associated with, display
- Course objectives
- The aim of the course is to introduce students into both theoretical and practical aspects of software quality (quality attributes, metrics, conflicts) and supportive processes (activities contributing to building software quality along the development process), and develop critical thinking that will allow them to identify code flaws and future problems early during the software development life cycle. Students will also become familiar with code refactoring and different dimensions of software testing.
- Learning outcomes
- At the end of the course students will:
understand different aspects of software quality (quality attributes, metrics, conflicts) and supportive processes (activities contributing to building software quality along the development process);
be able to identify code flaws related to reliability, performance, scalability, maintainability and testability;
be able to refactor existing code to improve the discussed quality attributes;
have practical experience with different dimensions of software testing and related tools.
- Roadmap to software quality engineering methods.
- Software measurement and metrics, and their role in quality improvement.
- Quality in software development, Clean Code & SOLID principles.
- Bad code smells and code refactoring.
- Focus on quality attributes and conflicts between them.
- Static code analysis and code reviews.
- Requirements and test cases. From unit testing to integration testing.
- Best practices in software testing and testability. Popular testing strategies.
- Performance engineering and performance testing.
- Challenges of quality management in cloud applications.
- Continuous integration and issue tracking.
- Software quality management process.
- Quality and testing in agile.
- ROBERT.C., Martin. Clean Code: A Handbook of Agile Software Craftsmanship. New York: Prentice Hall, 2008. ISBN 978-0-13-235088-4. info
- FOWLER, Martin. Refactoring :improving the design of existing code. Boston: Addison-Wesley, 2000. xxi, 431 s. ISBN 0-201-48567-2. info
- FENTON, Norman E. and Shari Lawrence PFLEEGER. Software metrics :a rigorous and practical approach. 2nd ed. Boston: PWS Publishing, 1997. xii, 638 s. ISBN 0-534-95425-1. info
- PEZZE, M and M YOUNG. Software Testing And Analysis: Process, Principles And Techniques. Hoboken, N.J.: John Wiley & Sons Inc, 2007. 488 pp. ISBN 978-0-471-45593-6. info
- Teaching methods
- Lectures, using: presentations, examples, practical self-work solution to exercises;
Seminar (computer lab) sessions involving practical work on the topics of the lectures (in the case of the company-led seminar groups, selected topics may be elaborated more deeply than others to increase the knowledge transfer from the involved experts);
Team projects within the seminars.
- Assessment methods
- Students will be assigned medium-size practical assignments (spanning across multiple weeks) within the seminars. The goal of the assignments will be to let the students improve the quality of the provided code by applying the techniques discussed during the course in terms of software measurement for quality improvement, refactoring and testing approaches.
Additionally, there will be a written test at the end, testing the knowledge gained by the students during the semester.
To pass the course, the students must reach at least 70 points out of 100 (45 for seminar assignments, 35 for the final written test, 10 points for activity in seminars, 10 points for activity in lectures).
- Language of instruction
- Further Comments
- The course is taught annually.
The course is taught: every week.