Abstract [en]

Since it has become more and more common with companies who buy and sell software, it has at the same time become more important to conduct the software in the right way, in order to sustain its integrity. There are many different methods to software documentation and testing. This report focuses on the method described in several standards from the Institute of Electronics and Electrical Engineers (IEEE) and the method that the consultant company PRC Engineering uses. Since PRC Engineering often reutilizes their software in different consultant projects, they are required to conduct their software in the right way. Today, PRC Engineering has a finished project that has not been tested or documented, which the company now would like to do. This to be able to reutilize parts of the programming code in future projects. The code is composed by several blocks, or modules as it is called, and in this master thesis the task has been to document and test three of these modules. In addition to that, the goal has been to develop the three modules in a way that increases the understanding of both the programming code and the graphical user interface. This will contribute to making it easier to reutilize them in the future. In order to carry out this master thesis, the report was divided into one theoretical and one practical part. The theoretical part is about the theory behind software documentation and testing, and is mainly based on previously published material. The practical part is about software testing and development in practice, and is mainly based on information from performed interviews with professional programmers. After the performed analysis of IEEE’s standards and PRC Engineering’s method for software documentation and testing, it was established that the methods are relatively alike, but that there is room for improvement of PRC’s method. After the examination of the three modules, suggestions of improvements could be made as well, especially in terms of the code’s structure and format, naming of different variables and internal documentation of the code, but also the user interface’s layout, format and color coding. During development of the user interface, color blindness was taken into consideration, which has not been done in these modules before. It is strongly recommended that PRC evaluates these suggestions, both when it comes to their method for software documentation and testing, and to the three modules, and implements these changes if desired.