Map of the Lower Geyser Basin of the Upper Madison River

Kartta kuuluu A. E. Nordenskiöldin kokoelmaan

Congenital upper limb defects in Finland 1993-2005

Background: Interest in limb defects has grown after the thalidomide tragedy in the 1960s. As a result, congenital malformation registries, monitoring changes in birthprevalence and defect patterns, have been established in several countries. However, there are only a few true population based studies on birth prevalence of upper limb defects. The burden of hospital care among these children, specifically in terms of the number of admissions and total time spent in hospital, is also unknown. Aims and Methods: This study is based on information gathered from the Finnish Register of Congenital malformations (FRM) and the Finnish Hospital Discharge Register (FHDR). A total of 417 children born between 1993 and 2005 with an upper limb defect were gathered from the FRM. The upper limb defects were classified using the International Federation of Societies for Surgery of the Hand -classification that enables comparison with previous and future studies. Birth and live birth prevalence, sex and side distribution, frequency of associated anomalies as well as the proportion of perinatal and infant deaths according to the different subtypes were calculated. The number of hospital admissions, days spent in hospital, number and type of surgical operations were collected from the FHDR. Special features of two subgroups, radial ray defects (RRD) and constriction band syndrome (CBS), were explored. Results: Upper limb defects were observed in 417 of 753 342 consecutive births and in 392 of 750 461 live births. Birth prevalence was 5.5 per 10 000 births and 5.2 per 10 000 live births. Multiple anomalies or a known syndrome was found in 250 cases (60%). Perinatal mortality was 139 per 1000 births and infant mortality 135 per 1000 live births (overall Finnish perinatal mortality <5 per 1000 births and infant mortality 3.7 per 1000 live births). Altogether, 138 infants had RRD and 120 (87%) of these had either a known syndrome or multiple major anomalies. The proportion of perinatal deaths in RRD group was 29% (40/138) and infant deaths 35% (43/123). Fifty-one children had CBS in upper limbs. Fifteen of these (29%) had other major anomalies associated with constriction rings. The number of hospital admissions per year of children with congenital upper limb defects was 11-fold and the time spent in hospital 13-fold as compared with the general paediatric population. Conclusions: Birth prevalence of congenital upper limb defects was 5.5 per 10 000 births and 5.2 per 10 000 live births. RRD was especially associated with other major anomalies and high mortality. Nearly one third of the children with CBS also had other major anomalies suggesting different aetiologies inside the group. The annual burden of hospital care of children with congenital upper limb defects was at least 11-fold as compared with the general paediatric population.

Model-based testing of software systems : functionality and performance

Software is a key component in many of our devices and products that we use every day. Most customers demand not only that their devices should function as expected but also that the software should be of high quality, reliable, fault tolerant, efficient, etc. In short, it is not enough that a calculator gives the correct result of a calculation, we want the result instantly, in the right form, with minimal use of battery, etc. One of the key aspects for succeeding in today's industry is delivering high quality. In most software development projects, high-quality software is achieved by rigorous testing and good quality assurance practices. However, today, customers are asking for these high quality software products at an ever-increasing pace. This leaves the companies with less time for development. Software testing is an expensive activity, because it requires much manual work. Testing, debugging, and verification are estimated to consume 50 to 75 per cent of the total development cost of complex software projects. Further, the most expensive software defects are those which have to be fixed after the product is released. One of the main challenges in software development is reducing the associated cost and time of software testing without sacrificing the quality of the developed software. It is often not enough to only demonstrate that a piece of software is functioning correctly. Usually, many other aspects of the software, such as performance, security, scalability, usability, etc., need also to be verified. Testing these aspects of the software is traditionally referred to as nonfunctional testing. One of the major challenges with non-functional testing is that it is usually carried out at the end of the software development process when most of the functionality is implemented. This is due to the fact that non-functional aspects, such as performance or security, apply to the software as a whole. In this thesis, we study the use of model-based testing. We present approaches to automatically generate tests from behavioral models for solving some of these challenges. We show that model-based testing is not only applicable to functional testing but also to non-functional testing. In its simplest form, performance testing is performed by executing multiple test sequences at once while observing the software in terms of responsiveness and stability, rather than the output. The main contribution of the thesis is a coherent model-based testing approach for testing functional and performance related issues in software systems. We show how we go from system models, expressed in the Unified Modeling Language, to test cases and back to models again. The system requirements are traced throughout the entire testing process. Requirements traceability facilitates finding faults in the design and implementation of the software. In the research field of model-based testing, many new proposed approaches suffer from poor or the lack of tool support. Therefore, the second contribution of this thesis is proper tool support for the proposed approach that is integrated with leading industry tools. We o er independent tools, tools that are integrated with other industry leading tools, and complete tool-chains when necessary. Many model-based testing approaches proposed by the research community suffer from poor empirical validation in an industrial context. In order to demonstrate the applicability of our proposed approach, we apply our research to several systems, including industrial ones.

The functional fit between collaborative software and work systems:Qualification of work system needs to software functionality

The study develops an approach that tries to validate software functionality to work systems needs in SMEs. The formulated approach is constructed by using a SAAS based software i.e., work collaboration service (WCS), and SMEs as the elements of study. Where the WCS’s functionality is qualified to the collaboration needs that exist in operational and project work within SMEs. For this research constructivist approach and case study method is selected because the nature of the current study requires an in depth study of the work collaboration service as well as a detailed study of the work systems within different enterprises. Four different companies are selected in which fourteen interviews are conducted to gather data pertaining. The work systems method and framework are used as a central part of the approach to collect, analyze and interpret the enterprises work systems model and the underlying collaboration needs on operational and project work. On the other hand, the functional model of the WCS and its functionality is determined from functional model analysis, software testing, documentation and meetings with the service vendor. The enterprise work system model and the WCS model are compared to reveal how work progression differs between the two and make visible unaddressed stages of work progression. The WCS functionality is compared to work systems collaboration needs to ascertain if the service will suffice the needs of the project and operational work under study. The unaddressed needs provide opportunities to improve the functionality of the service for better conformity to the needs of enterprise and work. The results revealed that the functional models actually differed in how operational and project work progressed within the stages. WCS shared similar stages of work progression apart from the stages of identification and acceptance, and progress and completion stages were only partially addressed. Conclusion is that the identified unaddressed needs such as, single point of reference, SLA and OLA inclusion etc., should be implemented or improved within the WCS at appropriate stages of work to gain better compliance of the service to the needs of the enterprise an work itself. The developed approach can hence be used to carry out similar analysis for the conformance of pre-built software functionality to work system needs with SMEs.