PA187 Project managment and project

Faculty of Informatics
Spring 2024
Extent and Intensity
1/0/4. 5 credit(s) (plus extra credits for completion). Type of Completion: z (credit).
Taught in person.
Teacher(s)
RNDr. Jaroslav Ráček, Ph.D. (lecturer)
doc. Ing. RNDr. Barbora Bühnová, Ph.D. (alternate examiner)
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
Timetable
Tue 20. 2. 19:00–19:50 D3
Prerequisites
( PB175 Project managment and project && ( PV168 Seminar in Java programming || PV178 Introduction to C#/.NET )) || SOUHLAS
These prerequisites can be replaced by a request for an exception stating the extent to which you have knowledge of the courses.
Course Enrolment Limitations
The course is also offered to the students of the fields other than those the course is directly associated with.
fields of study / plans the course is directly associated with
Course objectives
The course aim is to make students experience a real work on a specified complex software, where student's primary task is to develop a specific functionality. They will also be responsible for the integration of the programming results into the production version of the software involved, and the role of a technical team leader. The teaching of the course will be connected with the teaching of the bachelor's course PB175 Project Management and Project. Unlike PB175, however, PA187 students will be expected to fulfill more senior roles in joint teams.
Learning outcomes
After successful completion student will be able:
- to understand a complex project specification and orient in a complex code
- to effectively manage a team to develop and test (validate) specified functionality in accordance with the project specification
- to integrate results (code) into a production version of the software involved
- to document and pass over results of her work in a form that allows taking over by another developer or team (developing the same software product)
Syllabus
  • Time steps:
  • - Selection of the project from a provided list or accepted student's project specification proposal
  • - Team work on the project
  • - Regular consultations with the technical supervisor
  • - Regular consultation with a faculty supervisor (assigned whem the technical supervisor is not a faculty)
  • - Final project report (text and code), formally accepted by the teacher.
Literature
  • ROBERT.C., Martin. Clean Code: A Handbook of Agile Software Craftsmanship. New York: Prentice Hall, 2008. ISBN 978-0-13-235088-4. info
Teaching methods
Independent (or team) work on a selected software project, under a technical supervisor and eventually also additional supervisor from the FI MU (in case of external technical supervision).
Assessment methods
Final report from the project (includes text and code), formally accepted by the teacher.
Language of instruction
Czech
Further Comments
Study Materials
The course is taught annually.
The course is also listed under the following terms Spring 2022, Spring 2023.
  • Enrolment Statistics (recent)
  • Permalink: https://is.muni.cz/course/fi/spring2024/PA187