Engineering Methods

Academic year 2025/26

 
 

Project

 
 

Within the Engineering Methods course, you will develop a project proposal for its subject focus in the form of an application for research and development project solutions, a review of the current state in the field in the form of an article, and a presentation. The goal is to stimulate creativity and create space for implementing your own ideas, develop your communication skills, and practice technical writing and presentation methods. You work on the project and its components as a team and are evaluated as a team. The project and its components require work outside of exercises.

The project consists of these parts:

  1. Project Focus (5 points)
  2. Preliminary Project Version (20 points)
  3. Project Presentation (30 points)
  4. Project and Its Components (30 points)

The basic student obligations for project implementation are defined in the completion requirements.

Submission deadlines for individual project parts are listed in the Exercises / Submission Deadlines section. All project parts are submitted to the AIS system, for which corresponding submission locations will be created.


1. Project Focus

Develop a specification of the project focus; project title, its acronym, and brief annotation within a maximum of 2000 characters. This specifically concerns three items: VV-A1-03; VV-A1-04; VV-A1-09, from the applied research application form (Appendix 5 – Applied Research Application Template [pdf, 844 kB]). In the annotation, clearly state what you plan to focus on.

Write using diacritics.

The project title and focus are subject to approval and possible modifications by the instructor.

To be submitted: source (LaTeX) document with project focus specification .tex and its .pdf output. Content relevant to the three items is mandatory: VV-A1-03; VV-A1-04; VV-A1-09, from the applied research application form.

Evaluation

The evaluation method is as follows: clear and transparent intent – 5 points; mostly clear and transparent intent or inadequate or missing own title, acronym – 2–4 points; unclear and vague intent – 0–1 points

^


2. Preliminary Project Version

The first version of the proposal you submit should have approximately 50–60% of the expected final version scope (point 4). It is clear that at this stage the proposal will be unevenly developed, but its idea and some measurable indicators and goals should already be clear. Part of the project intent description will be an accompanying document in the form of a review article. In it, characterize the sources, state of knowledge, scientific foundations, and previous results that form the basis for project implementation.

It is very important that you reference sources already in the earliest versions of the article. Over time, it becomes increasingly difficult to remember the context and appropriately reference the source.

The article certainly won't be created by first studying everything, then thinking it through, and then writing in order from introduction to conclusion (this could be called a waterfall approach). The process is rather such that after establishing a working title, writing a summary (abstract), and determining the framework structure of the article (section titles), you develop individual aspects that you address across all parts of the article (this is the so-called iterative and incremental approach).

The following questions may help you when writing the article:

  • What do you deal with and why (how do others define it and how would you define it)?
  • What is the state in the field (with references to sources)?
  • What do you consider a significant problem in this area and why (support in literature)?
  • Is there any solution and what kind?
  • Is your solution similar to others (even from other areas and only from a certain perspective)?
  • What is the article about, what have we contributed to you, and what remains open?

Prepare the article as an article class document according to the example article and bibliography.

To be submitted:

  • forms VV-A through VV-E applied research application file in LaTeX and PDF format
  • form VV-F project subject intent file in LaTeX and PDF format
  • source form of review article:
    • LaTeX file with review article text
    • BibTeX file with bibliography
    • (if the review article contains) images in source format (in which they were created) and in the format in which they are inserted into the article
    • (if the review article contains) tables in source format and in the format in which they are inserted into the article (if not created directly in LaTeX)
  • review article in PDF format

Evaluation

For the preliminary project version to be evaluated with a non-zero number of points:

  1. it must correspond to the project focus (submitted according to point 1) including modifications by the instructor
  2. it must be written in LaTeX and must be translatable to PDF format
  3. the review article must have at least 4 pages of the specified format
  4. the review article must reference a source that primarily guided you to the given topic and at least 7 other related sources (in text) and BibTeX must be used for this

The evaluation method is as follows:

Forms VV-A through VV-F, according to evaluation criteria for assessing applied research and development projects, part C; Appendix 2 – Evaluation Process and Evaluation Criteria – Slovak version [pdf, 166 kB]:
  • Excellence – 5 points (High level (excellent level): The project intent is clearly and convincingly formulated, with innovative and well-justified procedures and high application impact. The problem being solved is highly current and original, with potential to bring breakthrough solutions. Project goals are very clearly defined, realistic and measurable. The methodology is correctly chosen, detailed and fully supports goal achievement. Solver outputs are excellent, with demonstrable contribution to practice. The solver and team are internationally recognized experts, with clear vision for further development and capacity building. Significant involvement of young workers with emphasis on their growth and expertise building. High competence of all involved organizations and individuals - 5 points; Medium level (good excellence): Project intent and procedures are reasonably justified, have clear application level, though with certain limitations. The problem being solved is current, originality is partial or only in some aspects. Project goals are clear and mostly achievable. Methodology is relevant, but with minor weaknesses in connection to goals. Solver outputs are quality and have application potential. The solver and team demonstrate good level of expertise and professional competence, there is also potential for further growth. Young workers are involved, but rather marginally. Competence of involved organizations and individuals is good, but not completely balanced – 3–4 points; Low level (weak excellence): Project intent is unclear, proposed procedures are insufficiently justified or inappropriate. The problem being solved has low currency or is already being solved in other projects without originality. Project goals are indefinite, unrealistic or only formally declared. Methodology is incorrectly chosen, without connection to project goals. Solver outputs are low quality or do not demonstrate applicability. The solver and team show limited expertise and experience, lacking vision for further development. Weak or no participation of young workers. Competence of involved organizations and individuals is insufficient – 0–2 points)
  • Impact – 5 points (High level (excellent impact): The project has fundamental contributions to knowledge development, applied research and innovation – brings new or significantly improved products, technologies, services or social innovations. Results are clearly usable for applicant/user in Slovakia and abroad, with high application potential. Economic and social benefit is significant and demonstrable (e.g., increased added value, job creation, quality of life improvement, environmental benefits). Measures for result maximization and communication are systematic, thoughtful and ensure broad project impact – 5 points; Medium level (good impact): The project has clear contributions to knowledge and innovation development, though not completely breakthrough. Results are usable for applicant/user, mainly in Slovakia, with limited potential for abroad. Economic and social benefit is identifiable, but partially limited. Measures for result maximization and communication are defined, but with reserves in scope or quality – 3–4 points; Low level (weak impact): Project contribution to knowledge, research and innovation is limited, little original or only declarative. Declared results have low usability, are difficult to apply for applicant/user in Slovakia and abroad. Economic and social benefit is unclear, little demonstrable or negligible. Measures for result maximization and communication are inadequate or absent – 0–2 points)
  • Implementation – 5 points (High level (excellent implementation): The project is processed clearly, comprehensibly, with logically connected goals, steps and procedures. The project plan is realistic, detailed with clear schedule, milestones and well-defined work packages. Project management is well set up, with effective management processes and control mechanisms. Implementation risks are thoroughly identified, with systematically prepared risk mitigation strategies. Budget is transparent, realistic and clearly connected to project goals and outputs. Existing workplace infrastructure is quality, provides guarantee of excellent project solution and goal achievement – 5 points; Medium level (good implementation): The project is processed clearly, procedures and goals are logical, though not completely detailed. Project plan and schedule are appropriately set, contain basic milestones and work packages, with certain weaknesses in details. Project management is defined, management processes are functional, but not always completely systematic. Implementation risks are identified, mitigation methods are proposed, but only partially developed. Budget is mostly justified and appropriate, with minor reserves. Existing infrastructure is sufficient for project solution, even if not at top level – 3–4 points; Low level (weak implementation): The project is processed unclearly, with low comprehensibility and illogical connection of goals and procedures. Project plan is incomplete or unrealistic, schedule is inappropriate, clear milestones or work packages are missing. Project management is insufficiently defined, management processes are weak or missing. Implementation risks are not identified or mitigation methods are not proposed. Project financial security is weak, budget is inappropriately set or unjustified. Existing workplace infrastructure is insufficient, does not provide guarantee of quality solution – 0–2 points)
Review article:
  • text organization, stylization and work with sources – 5 points (clear and transparent structure, clear and correctly formulated sentences and correct references to correctly listed sources – 5 points; mostly clear and transparent structure, mostly clear sentences or minor errors in formulations and minor errors in referencing sources or in listing sources – 3–4 points; unclear and vague structure, unclear but still comprehensible sentences or major errors in formulations or major errors in referencing sources or in listing sources – 0–2 points)

^


3. Project Presentation

Prepare a presentation for the project proposal in LaTeX or Prezi. In the presentation, focus on the most important and most interesting matters. The presentation should have at least 7 slides. You will present orally for 15 to 20 minutes and all team members will actively participate. The presentation will also include discussion for 20 to 30 minutes. To start the discussion, two teams will be selected for each team and assigned the role of discussants. Other attendees can join the general discussion afterwards.

The presentation should contain at least one diagram prepared in an adequate graphic tool (e.g., MS Visio, Blender, Gimp, UMLet, etc.). An Open Source alternative is also sufficient.

The presentation should contain at least one table. The table must be prepared in an adequate tool (e.g., MS Excel or Open Source alternative) and contain values determined based on formulas (need not be numerical).

To be submitted:

  • depending on the tool used:
    • in case of LaTeX: source form of presentation slides in LaTeX (TEX) and presentation slides in PDF format
    • in case of Prezi: link to online presentation and export to PDF
  • source form of images (.png, etc.) and tables (.xls, .xlsx, etc.)

Evaluation

For the presentation to be evaluated with a non-zero number of points:

  1. it must correspond to the project focus (submitted according to point 1) including modifications by the instructor
  2. it must be written in LaTeX and translatable to PDF format, or in Prezi format
  3. it must have at least 7 slides

Team presentation evaluation consists of parts:

  • presentation slides – 8 points (presenter is evaluated)
  • article presentation delivery – 10 points (presenter is evaluated)
  • discussion contribution – 12 points (discussants are evaluated)
The evaluation method is as follows:

  • presentation slides – 8 points
    • diagram – 2 points (corresponding to topic – 2 points; with less clear connection – 1 point; without connection or no diagram at all – 0 points)
    • table – 2 points (corresponding to topic – 2 points; with less clear connection – 1 point; without connection, without formulas or no table at all – 0 points)
    • scope and organization of slides – 4 points (scope maintained, clear and transparent presentation – 4 points; mostly clear and transparent presentation – 2-3 points; unclear and vague presentation – 0-1 points)
  • article presentation delivery – 10 points (clear presentation – 10 points; mostly clear presentation – 7-9 points; weaker presentation and/or time violation – 4-6 points; gross errors in presentation and/or gross time violation – 0–3 points)
  • discussion contribution – 12 points (professionally conducted relevant discussion including related questions - 10-12 points; mostly professionally conducted relevant discussion including related questions - 7-9 points; poorly conducted discussion, less professional and/or fewer questions - 4-6 points; unprofessional discussion about matters not related to subject content, or few related questions - 0-3 points)

^


4. Project and Its Components

Forms VV-A through VV-F and the review article represent the development of their preliminary version according to point 2.

The expected scope of form VV-F must not exceed 15 pages of the specified format.

The expected scope of the review article is 7 pages of the specified format. The article should contain at least one diagram prepared in an adequate graphic tool and one table prepared in an adequate tool or directly in LaTeX.

To be submitted:

  • forms VV-A through VV-E applied research application file in LaTeX and PDF format
  • form VV-F project subject intent file in LaTeX and PDF format
  • source form of review article in LaTeX (LaTeX files with text, BibTeX file with bibliography and images created in graphic tools including export to PDF for LaTeX) and tables (if created in MS Visio tool, also in this format including possible export to PDF for LaTeX)
  • article in PDF format

Evaluation

For the project and its components to be evaluated with a non-zero number of points:

  1. it must correspond to its focus (submitted according to point 1)
  2. it must be written in LaTeX and translatable to PDF format
  3. it must reference at least 12 sources (in text) and BibTeX must be used for this

The evaluation method is as follows:

forms VV-A through VV-F:
  • Excellence – 7 points (High level (excellent level): The project intent is clearly and convincingly formulated, with innovative and well-justified procedures and high application impact. The problem being solved is highly current and original, with potential to bring breakthrough solutions. Project goals are very clearly defined, realistic and measurable. The methodology is correctly chosen, detailed and fully supports goal achievement. Solver outputs are excellent, with demonstrable contribution to practice. The solver and team are internationally recognized experts, with clear vision for further development and capacity building. Significant involvement of young workers with emphasis on their growth and expertise building. High competence of all involved organizations and individuals - 5-7 points; Medium level (good excellence): Project intent and procedures are reasonably justified, have clear application level, though with certain limitations. The problem being solved is current, originality is partial or only in some aspects. Project goals are clear and mostly achievable. Methodology is relevant, but with minor weaknesses in connection to goals. Solver outputs are quality and have application potential. The solver and team demonstrate good level of expertise and professional competence, there is also potential for further growth. Young workers are involved, but rather marginally. Competence of involved organizations and individuals is good, but not completely balanced – 3–4 points; Low level (weak excellence): Project intent is unclear, proposed procedures are insufficiently justified or inappropriate. The problem being solved has low currency or is already being solved in other projects without originality. Project goals are indefinite, unrealistic or only formally declared. Methodology is incorrectly chosen, without connection to project goals. Solver outputs are low quality or do not demonstrate applicability. The solver and team show limited expertise and experience, lacking vision for further development. Weak or no participation of young workers. Competence of involved organizations and individuals is insufficient – 0–2 points)
  • Impact – 7 points (High level (excellent impact): The project has fundamental contributions to knowledge development, applied research and innovation – brings new or significantly improved products, technologies, services or social innovations. Results are clearly usable for applicant/user in Slovakia and abroad, with high application potential. Economic and social benefit is significant and demonstrable (e.g., increased added value, job creation, quality of life improvement, environmental benefits). Measures for result maximization and communication are systematic, thoughtful and ensure broad project impact – 5-7 points; Medium level (good impact): The project has clear contributions to knowledge and innovation development, though not completely breakthrough. Results are usable for applicant/user, mainly in Slovakia, with limited potential for abroad. Economic and social benefit is identifiable, but partially limited. Measures for result maximization and communication are defined, but with reserves in scope or quality – 3–4 points; Low level (weak impact): Project contribution to knowledge, research and innovation is limited, little original or only declarative. Declared results have low usability, are difficult to apply for applicant/user in Slovakia and abroad. Economic and social benefit is unclear, little demonstrable or negligible. Measures for result maximization and communication are inadequate or absent – 0–2 points)
  • Implementation – 7 points (High level (excellent implementation): The project is processed clearly, comprehensibly, with logically connected goals, steps and procedures. The project plan is realistic, detailed with clear schedule, milestones and well-defined work packages. Project management is well set up, with effective management processes and control mechanisms. Implementation risks are thoroughly identified, with systematically prepared risk mitigation strategies. Budget is transparent, realistic and clearly connected to project goals and outputs. Existing workplace infrastructure is quality, provides guarantee of excellent project solution and goal achievement – 5-7 points; Medium level (good implementation): The project is processed clearly, procedures and goals are logical, though not completely detailed. Project plan and schedule are appropriately set, contain basic milestones and work packages, with certain weaknesses in details. Project management is defined, management processes are functional, but not always completely systematic. Implementation risks are identified, mitigation methods are proposed, but only partially developed. Budget is mostly justified and appropriate, with minor reserves. Existing infrastructure is sufficient for project solution, even if not at top level – 3–4 points; Low level (weak implementation): The project is processed unclearly, with low comprehensibility and illogical connection of goals and procedures. Project plan is incomplete or unrealistic, schedule is inappropriate, clear milestones or work packages are missing. Project management is insufficiently defined, management processes are weak or missing. Implementation risks are not identified or mitigation methods are not proposed. Project financial security is weak, budget is inappropriately set or unjustified. Existing workplace infrastructure is insufficient, does not provide guarantee of quality solution – 0–2 points)
Review article:
  • text organization, stylization and work with sources – 9 points (clear and transparent structure, clear and correctly formulated sentences and correct references to correctly listed sources – 7-9 points; mostly clear and transparent structure, mostly clear sentences or minor errors in formulations and minor errors in referencing sources or in listing sources – 4–6 points; unclear and vague structure, unclear but still comprehensible sentences or major errors in formulations or major errors in referencing sources or in listing sources – 0–3 points)