Functional size is among the few software size measures for which well-structured and standardized methods exists for its measurement. Although Functional Size Measurement(FSM) methods have gone a long way, one ongoing criticism on FSM methods is the discrepancies in the measurement results of the same software obtained by different measures. In this thesis study the sources of discrepancies that involve the functional properties of measurands and constructs of the FSM method models are investigated in two exploratory case studies. In the light of the findings, a software functionality model for functional size measurement is proposed. The model is founded on a characterization of software functionality from a requirements engineering point of view and it aims is to facilitate reliable size measurements on the basis of formalized concepts and rules. Two case studies are conducted in order to evaluate the applicability of the model and validate its effectiveness.

Yes / To identify a subset of software issues occurring in daily Swedish healthcare practice and devise a set of local solutions to overcome the challenges. Methods: A sample of 46 incident reports was collected from one of Sweden's national incident reporting repositories, ranging from June 2019 to December 2021. The reports were first subjected to an algorithm to identify if they were health information technology-related incidents and were analysed using an existing framework, i.e., the Health Information Technology Classification System, to identify the software-related incidents. The incidents associated with software issues were then subjected to thematic analysis, in which themes were extracted and presented under the category assigned by the existing framework used. Results: Of 46 reports, 45 (with one exception) were included using the algorithm. Of 45 incidents, 31 software-related incidents were identified using the classification system. Six types of software issues were identified, including software functionality (n = 10), interface with other software systems or components (n = 10), system configuration (n = 7), interface with devices (n = 2), record migration (n = 1) and increased volume of transactions (n = 1). Each issue was further categorised into different themes; for example, software interface-related problems were grouped into ‘two patients being active in the system simultaneously’ (n = 6) and ‘transfer of patient information’ (n = 4). Conclusions: The study provided some insights into software issues and relevant consequences. A set of local solutions were devised to overcome the present challenges encountered in Swedish healthcare in their daily clinical practice. Systematic identification and characterisation of such software challenges should be a routine part of clinical practice for all major health information technology implementations. / This work has been part of being an Affiliated Researcher at the Department of Medicine and Optometry, Linnaeus University, Sweden. A publishing grant was received from Linnaeus University as a part of the University Library's research support.

This thesis proposes a new methodology to extend the software performance engineering process. Common performance measurement and tuning principles mainly target to improve the software function itself. Hereby, the application source code is studied and improved independently of the overall system performance behavior. Moreover, the optimization of the software function has to be done without an estimation of the expected optimization gain. This often leads to an under- or overoptimization, and hence, does not utilize the system sufficiently. The proposed performance improvement methodology and framework, called dynamic performance stubs, improves the before mentioned insufficiencies by evaluating the overall system performance improvement. This is achieved by simulating the performance behavior of the original software functionality depending on an adjustable optimization level prior to the real optimization. So, it enables the software performance analyst to determine the systems’ overall performance behavior considering possible outcomes of different improvement approaches. Moreover, by using the dynamic performance stubs methodology, a cost-benefit analysis of different optimizations regarding the performance behavior can be done. The approach of the dynamic performance stubs is to replace the software bottleneck by a stub. This stub combines the simulation of the software functionality with the possibility to adjust the performance behavior depending on one or more different performance aspects of the replaced software function. A general methodology for using dynamic performance stubs as well as several methodologies for simulating different performance aspects is discussed. Finally, several case studies to show the application and usability of the dynamic performance stubs approach are presented.

Tikslas:Ištirti kompiuterizuotam natų rašymui skirtas technologijas. Tyrimo objektas:Natų saugojimo formatai ir jų kūrimo programinė įranga. Problemos analizė:Kompiuterizuotam natų rašymui yra sukurta nemažai specialios programinės įrangos ir jų rezultato saugojimo formatų. Tačiau susistemintos informacijos apie tokių technologijų privalumus ir trūkumus rasti gan sunku, todėl vartotojai patys turi jas bandyti ir atrasti jiems labiausiai tinkančias. Tyrimo metodologija:Teoriniai tyrimo metodai: literatūros apžvalga ir analizė. Praktiniai tyrimo metodai: natografijos failų formatų apimties skirtumo tyrimas, natų rašymui skirtos programinės įrangos funkcionalumo įvertinimo bei patrauklumo vartotojui stebėjimas ir tyrimas. Naudotos priemonės:Sibelius 6, Harmony Assitant, Quick Score Elite Level II, Denemo – tyrimo duomenų gavimui ir kūrimui; Microsoft Excel 2003 – tyrimo duomenų aprašymui ir susisteminimui; SPSS Statistics 17.0 – tyrimo duomenų apdorojimui, analizei ir pateikimui; Microsoft Word 2003 – darbo rengimui ir pateikimui. Tyrimo apimtis: Failų formatų apimtis lyginta atsižvelgiant į: failo dydį, natų formato tipą, formato skaitomumą vartotojui, failo apimtį ir jos sumažinimo galimybę. Programinės įrangos funkcionalumas ištirtas įvertinant funkcijų kiekio santykį atitinkamose funkcionalumo grupėse: teksto įterpimas ir apiforminimas, lapo formatavimas, pasirinktų natų ir ženklų atvaizdavimas penklinėje, partitūros rašymas MIDI klaviatūra ir kompiuterio klaviatūra, muzikos... [toliau žr. visą tekstą] / Many various science areas are gradually relocating to information technology space and the recording of notes is not an exception. Hence, there are many different note recording and preserving formats and special software intended for the creation of such formats. However, because of comparatively rapid IT advancement it is usually hard to follow the all existing IT solutions and select the most proper, therefore, the objective of this work is to examine the technologies intended for the recording and preserving notes on the computer. During the time of this work the following examinations were completed: • The examination of note preserving formats; • The analysis of note recording software functionality; • The research of note recording software appeal; After completing the review of note preserving formats it was clear that they can be categorized into three groups: ascii, xml and binary. The note preserving formats which are based on ascii and xml codes are more coherent for the common user and take less hard disk space. After analyzing the note recording software the final results reveal that the Harmony Asisstant program is highly advanced and supports most functions. The Sibelius 6 is also very advanced and functional. After completing the note recording software appeal survey it was discovered that the respondents consider Sibelius 6 as the most appealing and coherent program.