|Hour/sem||Lectures||Sem. Exercises||Lab. exercises||Comp. exercises||Other|
|Guarantee:||Eysselt Miloš, Ing., CSc., DCSY|
|Faculty:||Faculty of Information Technology BUT|
|Department:||Faculty of Information Technology BUT|
| || ||The fundamental goal of this course is to support the individual creative student work during the engineering project solving and its formal description.|
| || ||Students will receive an individual project specification from various computer science areas in order to work them out individually under the supervising of some skilled leaders. Students will proceed as follows: problem analysis, solution, verification, implementation, documentation, presentation. During their work, the students will follow all the required instructions concerning requests on contents and volume of the project, the project adjustment, the literature, the language quality and written report typography as well as project parts consigned in the electronic form. The course is successfully completed when the written report and realised project outputs are given to the faculty board.|
|Knowledge and skills required for the course:|
| || ||Knowledge from the present study.|
|Learning outcomes and competences:|
| || ||Knowledges and experiences with engineering project building and its documentation.|
|Syllabus of numerical exercises:|
| ||Seminars with a supervisor about the solved problems.|
- Duncan, W.R.: A guide to the Project Management Body of Knowledge. Project Management Institute, 1996, Standards Committee, 176 p., ISBN 1-880410-16-3.
- ISO 2145: Documentation - Numbering of divisions and subdivisions in written documents, 1978.
- ISO 7144: Documentation - Presentation of theses and similar documents, 1986.
- Documentation - Bibliographic references. Content, form and structure, 1987.
| ||How to write technical reports and theses? (In Czech).|
| || ||Consultations with the supervisor.|
| || ||Technical report (about 20 pages), electronic documentation, successful defence of results.|