NPRG030 Programming 2 – exercise - NPRG031

Adam Dingle's (lecturer's) web with information, syllabus, textbooks and other resources.

Exercise syllabus

1. week - notes
2. week - notes
3. week - notes
4. week - notes 01, notes 02
5. week - notes
6. week - notes
7. week - notes, (notes Dynamamic programming CZ)
8. week - notes
9. week - notes
10. week - notes
11. week - notes

Examination requirements:

1. Homeworks - the primary goal of the homework is to practice the material/ideas, etc. discussed in the lecture, the code you write is a practice tool (this means only self-written code from the scrath is allowed; no copy, no co-work, no StackOverflow or GPTChat, etc. any exceptions will be explicitly stated).
• Usually every week
• At least 70% points from homeworks to pass (recodex; programming and theoretical tasks, 1 week to submit, 15 tasks in total)
• 50%-70% points at the end of the semester, it will be possible to complete more assignments during the examination period
2. Skipped Final test - on the last exercise write and debug a C# program in 75 minutes
3. Semestral project - A larger C# work, including documentation and tests, for which you will have more time. Your project that demonstrates your abilities/skills discussed within the course (including algorithmic, architecture and code design, programming, knowledge of language, efficiency, security, style and best practices, ...). It should be written in an object-oriented way.
1. Proposal
• Submit to 15. 05. 2023 - submit on the Owl; enroll token: b2162756a25e; each of you has a personal thread of communication here
• The proposal must be approved; the Project developed for an unapproved assignment will be invalid
• Submit the specification in the form of a structured text consisting of all mandatory parts: student identification, subject, date; idea and basic description of the problem; problem formalization; the basic design of the problem solving algorithm; input and output form; form of interface (GUI, console, ...); interactivity
2. Project
• Submit final version to 10. 09. 2023 - hard deadline
• Minimal mandatory parts: approved proposal, program, programmer and user documentation, testing data
• Submit on the Owl; enroll token: b2162756a25e; each of you has a personal thread of communication here
• Submit by inserting a link to your Git repo
• You can use the faculty GitLab repository
4. Activity in class
5. Cheating is prohibited! Strictly controlled.

Contact

• Consultation: by appointment, before or after the exercise or by email; I usually go to exercise 20 minutes before the exercise starts.
• Email: jiri.sejnoha #na# mff.cuni.cz