Software documentation is one of the most important aspects of the software development process, as it allows the transfer of knowledge between individuals, regardless of their background and their technical knowledge. In particular, Application Programming Interfaces provide the basic structure for the communication and integration between different software systems. Therefore, providing solid API documentation is fundamental for the software development process as it represents one of the main learning tools for developers trying to learn new technologies. While researchers have studied the fundamentals of good API documentation design for over twenty years, most studies only focused on the point of view of developers. However, with the rising amount of companies offering Software-as-a-Service products, it has also become important to produce documentation that is accessible to people with limited technical knowledge, i.e. customer representatives.  In order to fill this research gap, a case study was conducted in collaboration with a software company. By using a design science approach, this project focused on creating an API playground environment where users could interact with various APIs offered by the company. The results were evaluated through a questionnaire for user feedback and with an interview conducted with developers from the company. While the outcome of the evaluation was positive, the limited scope of the project prevented some important aspects of API documentation such as navigation from being thoroughly examined, therefore more extensive research is needed in the future.

Syftet med denna empiriska studie var att granska hur sjuksköterskan dokumente-rar smärta på en postoperativ avdelning och hur åtgärder i samband med smärt-lindring följs upp. Studien genomfördes på Universitetssjukhuset i Malmö genom granskning av journaler för 14 patienter som givit sitt samtycke att delta i studien. Analysen resulterade i tre kategorier: god/tillfredsställande, delvis tillfredsställan-de och bristfällig/obefintlig dokumentation. Resultatet av studien visade brister gällande dokumentation av smärta. Avsaknad av användning av visuell analog skala, smärtans karaktär och uppföljning av smärtlindring kunde noteras i ett fler-tal journaler. Bristerna var särskilt uttalade i fråga om dokumentation av uppföljning. Vidare forskning på området är angelägen för att kunna ta itu med problemet och i framtiden bör sjuksköterskan få fördjupa sina kunskaper i utbildningen eller på sin arbetsplats. / The aim of this empirical study was to examine how nurses document pain in a postoperative unit and the follow up of the alleviation of pain. The study was car-ried out in Malmö University Hospital, Sweden, through examining journals from 14 patients whom agreed to participate. The analyse identified three categories: good/satisfying, partly satisfying and deficient/non-existing documentation. Fur-thermore the study showed qualitative shortages concerning documentation of pain e.g. Lack of using a pain scale, pain character and follow up of alleviation of pain could be seen in many journals. Further research in this area is needed to be able to handle the problem and in service training as well as increased focus on the documentation problems in basic nurse training is recommended.

In an effort to process my grief associated with the death of my grandmother, I created a series of drawings, documenting my daily life in Massachusetts. This body of work constitutes my thesis. In total, I made one thousand and sixty one drawings, each undergoing a series of identical, repeated processes, which represent the number of days lived there. The simplicity, detail and sheer volume of drawings in the installation chronicles a relatable story through complex means. Creating the drawings was a methodical act of remembrance, the practice allowing quiet reflection on each day and its respective history. This body of work inhabits and portrays a space between experience and memory. It was a cathartic, private practice, which permits viewers only to witness the outcome, the installation; the legacy of time spent. Creating the work was a meditative, tactile way of both marking and processing time; time spent mourning the loss of my grandmother, accessing memories, and healing.

This study attempted to determine if a low-cost, minimally time consuming intervention could increase document completion – specifically end of shift reports. Using a concurrent multiple baseline design, automated phone calls reminded staff to complete their end of shift reports. Participants were the staff members at 16 group homes. All participants were trained Direct Support Professionals. The dependent variable was completion of end of shift reports as a percent of opportunities. There was a measurable response to the intervention. Overall, the percent of completion increased from 4% in baseline to 22% during intervention. The agency desired a much higher response level so a future research opportunity could address the limitations of this study by exploring the motivating operations impacting document completion and identifying individual staff rather than using aggregate data.

In today's industry the DevOps work-style is adopted in more and more companies. Following the work-style often leads to companies being more efficient at delivering new feature and high quality software at higher speeds.However, one thing that the DevOps work-style fail to address is the process of writing good and reliable non-code documentation. The non-code documentation often becomes a bottleneck for the companies following the work-style and is in need of an updated process to make it more effective and sustainable over time. In this thesis, the problem is addressed by designing and building a prototype system capable of automating the process of creating non-code documentation. In order to create a system capable of automating the process and thus increasing the flow and efficiency of the DevOps work-style, the prototype system has been built by combining powerful pre-existing tools like Pandoc, LaTeX and Docker together. The resulting system is implemented in a platform like GitLab or Bitbucket and can be used to automatically generate documentation with new releases. The documents are written in plain-text markdown files, letting the user focus on the content rather than the aesthetics of the document. This resulted in an increase of creating non-code documents 33.8% faster than existing methods like using Microsoft Word. Finally, the prototype system also generates more aesthetically looking documentation.

Syftet med undersökningen var att undersöka faktorer av betydelse för sjuksköterskans dokumentation. Av speciellt intresse var information som inkluderades och exkluderades från dokumentationen samt sjuksköterskans tankar om framtidens dokumentation.Åtta sjuksköterskor (fem kvinnor, tre män) från en intensivvårdavdelning intervjuades. Varje inspelad intervju varade 45-60 minuter. Materialet analyserades med hjälp av kvalitativ innehållsanalys. I huvudsak riktade sig sjuksköterskans dokumentation till kollegor. Ett bra stilistiskt värdeneutralt skriftspråk eftersträvades eftersom patienten kunde läsa journalen. Medicinsk information som inte kunde relateras till det egna området samt allmän omvårdnadsinformation utelämnades ofta ur dokumentationen men rapporterades ibland muntligt till kollegor. Situationer som avvek från det normala vårdförloppet ansågs svåra att dokumentera. Kortfattad dokumentation som endast innehöll det mest väsentliga eftersträvades. Sjuksköterskor vars dokumentation ansågs alltför omfattande tillrättavisades av kollegor. Samtliga sjuksköterskor blev störda i dokumentationsarbetet. Majoriteten av respondenterna ansåg att standardvårdplanernas nuvarande utformning fungerade dåligt men förväntade sig att standardvårdplaner skulle utgöra grunden för omvårdnadsdokumentation i framtiden. Ett förbättrat dokumentationssystem önskades. Studien indikerar att medicinsk och omvårdnadsmässig information som inte anses relevant i den aktuella vårdsituationen utelämnas ur sjuksköterskans dokumentation. Fler studier behövs för att försäkra att omvårdnadsdokumentation i framtiden innehåller alla delar av omvårdnadsprocessen. / The purpose of this study was to examine factors of importance for nursing documentation. Of special interest was what the individual nurse included and excluded in his/her documentation as well as any thoughts and expectations on the documentation process in the future. Eight nurses (five female, three male) working in an intensive care unit were interviewed. Each taped interview lasted 45 – 60 minutes. The material was analyzed using a qualitative content analysis method. Documentation was mainly done for the benefit of colleagues. Patient rights to read their own chart ensured well-written entries. Medical information not related to their own specialty as well as general nursing information was often not documented, but was sometimes reported orally. Patients reacting in unusual ways were difficult to document in an objective manner. Brief documentation, containing only necessary data, was seen as ideal. Nurses using excessive documentation were reprimanded. All nurses perceived that it was impossible to document without interruptions. Most nurses viewed standardized care plans in their current format as difficult to use but believed that they would be the foundation of nursing documentation in the future. Improved documentation systems were desired in the future. This study indicates that medical and nursing information seen as irrelevant in the current situation is excluded from nursing documentation. Organizational culture has an impact on what is seen as relevant and the documentation system determines how information is recorded. Further studies are needed in order to ensure that future nursing documentation include all aspects of the nursing process.

<p> A description is given of the multi-technique nonlinear optimization system called OPTIPAC.</p> <p> The overall organization of the program is outlined and the significant features of each of the method subroutines are discussed. Considerable emphasis has been placed on the documentation for the system, and the two manuals which have been written are described briefly. The results of three test problems are included to demonstrate the value of having a variety of techniques in the package.</p> <p> A preliminary evaluation of OPTIPAC's performance is given, with relevant suggestions for further development.</p> / Thesis / Master of Engineering (MEngr)

No description available.

No description available.

<p> The experience shows that any shortcoming in defining the requirements for computer based systems imperils the deliverables of all the subsequent stages of their development. This importance is undeniable when dealing with manufacturing software-systems due to their significant role in all spheres of human life. These systems have very stringent non-functional requirements such as accuracy and real-time constraints. The development of manufacturing software-systems is very challenging and requires special caution, since any mistake might have broad impact on very expensive work-pieces or might lead to a machining accident with irreparable effects. The success of their development depends largely on the quality of their Software Requirements Specification Document (SRSD).</p> <p> We propose a new requirements template specifically designed for manufacturing systems. The template is structured to reflect their characteristics including multi-constraints and multi-disciplinary problems, multi-stage processes, multi-tasking, dynamic behavior, evolutionary nature, time-varying physical characteristics, and the usage of complex scientific models. A complementary usage of goal-driven, viewpoint oriented, and scenario-based approach is adopted for structuring the template content. To provide a high quality SRSD, the template is designed to enhance unambiguity, consistency, completeness, precision, non-redundancy, and good organization of the requirements document as well as other criteria including breadth of applicability and methodology independence.</p> <p> An automated tool for requirements management according to the proposed template has been designed and implemented. The requirements management tool provides relatively secure and easy-to-use capabilities for the documentation and the retrieval of the requirements. It accelerates capturing the requirements, improves system quality by enhancing the reduction of requirements errors, and helps in establishing a common understanding between the system builders and the stakeholders. In addition to a user friendly environment for changing the information, we developed a powerful dynamic report generator that can be configured by the user and that provides a simple way for retrieving the requirements and formatting them.</p> <p> Both the template and the tool have been validated using the requirements for a Tool Trajectory Planning for High Speed Machining system developed at the Aerospace Manufacturing Technology Centre, Institute for Aerospace Research (Montreal).</p> / Thesis / Master of Science (MSc)