Bewerbung & Aufnahme Bachelor

Tips on writing a project paper

As part of your application for the Bachelor's Degree Programmes in Automation Technology and Smart Automation, a description of a short technical project can be handed in as an additional, programme-specific document and submitted together with the required documents.

The first step is often the most difficult, which is why we are happy to provide you with tips on how to tackle this task. Please use photos, diagrams or graphics for illustration purposes. 

Please note that this approach is just one of many ways of structuring the short description. We request that you do not copy any of the wording from these tips. Convince us with your independently written project work!

Example structure for a short technical project

Introduction:

  • Project description: Give a brief overview of the project. Explain why you have chosen this project and the context in which it takes place (e.g. professional necessity, personal interest).
  • Objective: Describe what problem the project is intended to solve or what goal it is intended to achieve (e.g. automating a process, increasing efficiency, saving time).

Technical requirements and prerequisites:

  • Technical requirements: Briefly explain the hardware and software requirements. Which components or systems are required? Go into specific requirements, such as voltages, interfaces, programmes or control units.
  • Specialist knowledge and basics: Describe what basic knowledge of automation technology, mechanical engineering, computer science or electrical engineering is required.

Project planning and realisation:

  • Planning: Describe the steps required to complete the project. Make it clear how you have structured the project and which methods were used for planning (e.g. work packages, milestones).
  • Implementation steps: Explain how the individual steps were implemented in practice. Diagrams, photos or flowcharts can be used here to illustrate the technical implementation.
  • Technology used: Describe the technology and the components used. If software was programmed, provide an overview of the functionality and logic.

Tests and results:

  • Test procedure: Describe how the functionality was checked (e.g. through simulations, test runs or measurements).
  • Results: Explain the results achieved and compare them with the initial expectations or objectives. Describe whether the project has fulfilled the desired functions or whether adjustments were necessary.

Conclusion and reflection:

  • Summary of results: Summarise the most important results and reflect on whether the project can be considered successful.
  • Potential for improvement and outlook: Describe what could be improved and which next steps would be useful.