Instructions for preparing the report for crediting the software engineering internship
Objectives of the report
The purpose of this report is to apply for credit for the module "Software Technology Practical Training" (SWTPra) on the basis of the completed training programme. The aim of the report is to clearly demonstrate the extent to which the learning objectives of the SWTPra (see module description in the module handbook) were covered by the training.
Formal requirements
- Cover page: A separate page with name, matriculation number, contact details and the information "Crediting SWTPra on the basis of the IT specialist training programme" or "Crediting SWTPra on the basis of the training programme for information technology assistants".
- Length: The content of the report should be at least 5 to a maximum of 10 pages. The cover sheet and appendices do not count towards these 5 to 10 pages.
- Appendix (optional): Extracts from the report booklet, illustrations, tables or diagrams can be added.
- Language and style: A coherent continuous text must be written in German.
- Figures/tables: These must be labelled and explained in the text.
- Structure and spelling: The report should have a clear structure, correct spelling and a common thread.
- Page limits: The maximum number of pages does not have to be exhausted.
- Dataprotection: Personal data of third parties (e.g. names of customers or employees) must be anonymised if you are attaching extracts from documents.
Structure and content of the report
In the first section, describe the general conditions of the training programme:
- Where was the training done?
- How was the training programme structured?
- What tasks and activities were undertaken during the training programme?
- Which projects were you involved in? What were your tasks there?
- Which process models or procedures were used in development projects within the company (e.g. Scrum)? What role did you play?
- How were projects planned and documented (e.g. effort estimates, project plans, requirements specifications)?
- Which technologies were used? (e.g. programming languages, tools, frameworks, etc.)
Each of the following SWTPra learning objectives must be addressed individually and it must be explained how and by what means this objective was covered in the training programme. Projects or other training situations should be specified and the respective tasks and activities as well as their relation to the learning objectives should be described.
Reference should also be made to relevant sections of the report booklet, the project work or other training documents (e.g. vocational school content). Specific examples should be given of practical activities, projects, tasks or responsibilities undertaken during the training programme.
Learning objectives of the SWTPra:
- Identify and explain the challenges of developing a software solution based on a division of labour
- Name, describe and practically apply current software development methodologies
- Name, differentiate and compare various software quality assurance methods and apply some of them in practice
- Recognise and assess the software architecture and code quality of third-party components
- Develop and document a running software system consisting of several components using different technologies based on a division of labour
(Tip: An overview table can also be prepared in which the learning objectives are assigned to the respective training components).
Describe two aspects that you have learnt from your training experience and that you would do differently or better in a future software project. Please note:
- Reference to the learning objectives: Refer to one or more of the learning objectives of SWTPra and explain how your experience in the training programme has contributed to them.
- Possible subject areas: The two aspects should come from different subject areas. Possible subject areas are: Working in a team, project planning/execution (e.g. use of process models such as Scrum), software architecture/design, documentation (e.g. requirements or design documentation).
- Justification: Explain why you would approach these points differently or more consciously today and what added value this would have for future software projects.
- Scope: Describe each aspect on at least half a page so that your considerations are presented in a comprehensible and sufficiently differentiated way.
Appendix, supporting documents and evidence
Add extracts or references to the training documents (e.g. project work, report booklet, training certificate) that provide evidence of the skills and experience mentioned. Make sure to anonymise personal data of third parties.