Project Paper Contents

Project paper (final report) is the main document, which reflects all stages and results of work. It should be prepared according to requirements of enterprise standard "Текстові документи у сфері навчального процесу. Загальні вимоги до виконання". Final report should be prepared using text editor and stored in PDF format.

The project paper should have a cover and contain such basic structural elements:

• Title page
• Project task
• Project director's review
• Abstracts in Ukrainian and English
• Table of Contents
• Introduction
• Main part
• Conclusions
• List of sources
• Appendices (if necessary)

The title page is the first page of the project paper.

Abstract is a brief annotation of jour project. It must be short and informative. Abstract also contains a number of pages, key words and project summary, which should shortly reveal the object of the study, the purpose of the work, the methods used, the main results, the field of application, conclusions on the further development. Abstract cannot exceed 1 page.

The contents lists the introduction, titles of all sections, and paragraphs of the main part of the explanatory note, conclusions, list of sources of information and appendices names. The numbers of pages on which the relevant material begins are given.

Introduction (1 to 2 pages) starts from new page and summarizes the topic of work, its purpose and contains common information about project domain.

Main part should be split into chapters. Each chapter starts from a new page.

The first chapter (4 to 10 pages) should contain an overview of the mathematical methods used in the semester project, an overview of the requirements of the Unified Modeling Language (UML) and design methods. In describing the programming environment, it is necessary to focus on the tools that are directly used in the semester project. The section should have a content header. The last paragraph of the first section should highlight the statement of the research task (problem statement). The chapter title like "Referential part" is not allowed.

In second chapter (4 to 10 pages) should contain description of the software design. Requirements for the software are defined in the form of a Use Case diagram with detailed comments. Class diagrams for concept and specification are given. Sequence diagrams should be implemented for different uses. The scheme of interaction of the modules providing the implementation of the program (in the form of a Package diagram) should be given. The tests that are planned to apply for testing programs are given.

The third chapter (4 to 10 pages) contains description of developed software and its testing. Interaction with the user should be illustrated by the corresponding pictures. An analysis of the results is carried out. A brief user's guide is also needed.

Conclusions section contains resume of your work. They work at all stages is summarized and recommendations on the use of the results should be given. The conclusions should also contain propositions concerned with the further development of the work.

List of sources contains references to books and articles used in main part of your paper. References to sources in the form of their numbers in square brackets should be given in the appropriate places in the text. The sources are given in the order in which they first appear in the text. The bibliographic descriptions of the references in the list must be in accordance with the standards.

The appendices contain diagrams and charts that take up a full page, source code, as well as other auxiliary materials.

The project paper without appendices should contain at least 16 pages (starting from the contents page).

In addition to a printed document, an electronic version of the note in PDF format, presenation, and source code of software in electronic form are provided for the defence of the semester project.