Att sätta sig in i andra utvecklares kod kan vara svårt och tidskrävande. Kodkonventionerär framtagna i syfte att underlätta underhållsarbetet för andra utvecklare som arbetar medsamma projekt, då det sällan är personen som skrev programmet som sedan underhållersamma program. För lite fokus läggs på kvalitétsaspekten i utvecklingsfasen av projektvilket kostar företag pengar och resurser. Denna studie har för avsikt att undersöka hurhögskoleingenjörsstudenter inom datateknik vid olika lärosäten i Sverige förhåller sig tillJavas kodkonventioner, och om det går att urskilja en signifikant skillnad i kodkvalitémellan lärosäten i avseende på identifierare, kommentarer samt format och struktur. Enwebbenkätundersökning genomfördes vars empiri analyserades med hjälp av ANOVA somär en vedertagen metod för hypotesprövning. 21 av 23 ANOVA-test visade att ingen signifikantskillnad förekom mellan lärosätena i avseende på identifierare, kommentarer samtformat och struktur. Resultatet visade även att de kvalitétsaspekter studenterna tyckerär viktiga och prioriterar att lägga tid på är också de aspekter som studenterna tycks hastörst förståelse och kunskap kring. / To get acquainted with other developers code can be difficult and time consuming. Codeconventions are developed in order to facilitate maintenance work for other developersworking on the same project, where the person who wrote the program rarely is the personthat maintains the same program. Little attention is paid to the aspect of quality ina projects development phase, which costs companies money and resources. This studyintends to investigate how students studying for a Bachelor of Science in Engineering inComputer Science at various universities in Sweden relate to Java code conventions, andif it is possible to discern a significant difference in code quality between these universitiesin terms of identifiers, comments, format and structure. An online survey was conductedwhose empirical data was analyzed using ANOVA, which is a recognized method forstatistical hypothesis testing. 21 of 23 ANOVA test showed that no significant differenceexisted between the institutions in terms of identifiers, comments and format and structure.The results also showed that the aspects of quality, which the students think are themost important, are also in fact the aspects they have the greatest understanding andknowledge about.

Software developers, maintainers, and testers rely on documentation to understandthe code they are working with. However, software documentation is perceivedas a waste of effort because it is usually outdated. How documentation evolvesthrough a set of releases may show whether there is any relationship between timeand quality. The results could help future developers and managers to improvethe quality of their documentation and decrease the time developers use to analyzecode. Previous studies showed that documentation used to be scarce and low inquality, thus, this research has investigated different variables to check if the qualityof the documentation changes over time. Therefore, we have created a tool thatwould extract and calculate the quality of the comments in code blocks, classes,and methods. The results have agreed with the previous studies. The quality of thedocumentation is affected to some extent through the releases, with a tendency todecrease.