PV260 Software Quality

Faculty of Informatics
Spring 2018
Extent and Intensity
2/2. 4 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).
Teacher(s)
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)
Supervisor
doc. RNDr. Eva Hladká, 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 21 fields of study the course is directly associated with, display
Course objectives
At the end of the course students should:
understand different aspects of software quality (quality attributes, metrics, conflicts) and supportive processes (activities contributing to building software quality along the development process);
develop critical thinking and 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.
Syllabus
  • Lect 1. Course organization. Roadmap to software quality engineering methods.
  • Lect 2. Software measurement and metrics, and their role in quality improvement.
  • Lect 3. Quality in software development, Clean Code & SOLID principles.
  • Lect 4. Bad code smells and code refactoring.
  • Lect 5. Focus on quality attributes and conflicts between them.
  • Lect 6. Static code analysis and code reviews.
  • Lect 7. Requirements and test cases. From unit testing to integration testing.
  • Lect 8. Best practices in software testing and testability. Popular testing strategies.
  • Lect 9. Performance engineering and performance testing.
  • Lect 10. Challenges of quality management in cloud applications.
  • Lect 11. Continuous integration and issue tracking.
  • Lect 12. Software quality management process.
  • Lect 13. Quality and testing in agile.
Literature
  • 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 bonus points for activity in seminars, 10 bonus points for activity in lectures).
Language of instruction
English
Further Comments
The course is taught annually.
The course is taught: every week.
The course is also listed under the following terms Spring 2015, Spring 2016, Spring 2017.
  • Enrolment Statistics (Spring 2018, recent)
  • Permalink: https://is.muni.cz/course/fi/spring2018/PV260

Go to top | Current date and time: 25. 9. 2017 13:24, Week 39 (odd)

Contact: istech(zavináč/atsign)fi(tečka/dot)muni(tečka/dot)cz, Office for Studies, access rights administrators, is-technicians, e-technicians, IT support | Use of cookies | learn more about Information System