Studies on coordination of systems development process

This thesis examines coordination of systems development process in a contemporary software producing organization. The thesis consists of a series of empirical studies in which the actions, conceptions and artifacts of practitioners are analyzed using a theory-building case study research approach. The three phases of the thesis provide empirical observations on different aspects of systemsdevelopment. In the first phase is examined the role of architecture in coordination and cost estimation in multi-site environment. The second phase involves two studies on the evolving requirement understanding process and how to measure this process. The third phase summarizes the first two phases and concentrates on the role of methods and how practitioners work with them. All the phases provide evidence that current systems development method approaches are too naïve in looking at the complexity of the real world. In practice, development is influenced by opportunity and other contingent factors. The systems development processis not coordinated using phases and tasks defined in methods providing universal mechanism for managing this process like most of the method approaches assume.Instead, the studies suggest that managing systems development process happens through coordinating development activities using methods as tools. These studies contribute to the systems development methods by emphasizing the support of communication and collaboration between systems development participants. Methods should not describe the development activities and phases in a detail level, butshould include the higher level guidance for practitioners on how to act in different systems development environments.

Exploring the role and transformative potential of human rights in development practice and food security : case study from Malawi

Avhandlingen är en analys av den roll som mänskliga rättigheter spelar i utvecklingssamarbete i allmänhet och tre matsäkerhetsprojekt i Malawi i synnerhet. Författaren undersöker huruvida mänskliga rättigheter kan bidra till samhälleliga förändringsprocesser. Undersökningen har en diskursiv syn på mänskliga rättigheter; rättigheter ses som sociala konstruktioner skapade av människor, konstruktioner som förändras i takt med att aktörerna ger dem ny mening. Människorättsbaserade utvecklingsstrategier riktar uppmärksamheten mot olika aktörers skyldigheter samt vikten av att mänskliga rättigheter inte kränks genom utvecklingspolitiska beslut. En analys som utgår från mänskliga rättigheter kan leda till att nya frågor lyfts fram: vem har skyldigheter, vem har rättigheter, och varför förverkligas inte dessa? Fokus flyttas till hur politiska, ekonomiska och juridiska strukturer kan förändras så att de främjar mänskliga rättigheter. Författaren använder empiriskt material från Malawi för att visa vilken roll mänskliga rättigheter och så kallade människorättsprinciper spelar inom tre projekt: (1) ett mathjälpsprojekt; (2) ett rättighetsbaserat projekt med fokus på att stärka strategier för livsuppehälle; (3) ett juridiskt projekt inom ramen för vilket man skapat ett lagförslag om rätten till föda. Analysen visar att det rättighetsbaserade projektet strävade efter den mest djupgående samhälleliga förändringen. Människorättsprinciperna ansvarighet och deltagande handlade inte endast om verksamheten inom projektet utan man strävade även efter att stärka dessa principer mellan medborgare och myndigheter. Rättigheter, som ett sätt att tala, tänka och handla, inte som abstrakta juridiska normer, påverkade de lokala aktörernas sätt att kräva bl.a. tjänster av lokala myndigheter. Teoretiskt kan man säga att det rättighetsbaserade projektet representerar ett aktörsperspektiv på mänskliga rättigheter där aktörernas egna uppfattningar om vad de är berättigade till samt krav på myndigheters ansvar formade vilken mening rättigheterna kom att få.

Foot Health In Older People - Development of a preventive, evaluative instrument for nurses

Foot health is a part of overall health in every age group and its importance increases during ageing. Health care professionals are in a vital position for preventing foot health problems, and identifying and caring them in older people. Despite the rather high number of studies conducted in the field of foot health in older people, reliable and valid nurse-administered foot health assessment instruments seem to be lacking. By identifying foot health in older people, it is possible to develop nursing interventions to enhance safe, independent living at home. The purpose of this three-phase study was to develop an instrument to assess the level of foot health in older people and evaluate foot care practices from the perspective of older people themselves and nurses in home care. The ultimate goal is to prevent foot health problems by increasing the attention paid to older people’s feet and recognizing those foot health problems which need further care; thus not focus on different foot health problems. The study was conducted in different phases and contexts. In phase 1, a descriptive design with a literature review from the Medline (R) and CINAHL databases to explore foot health in older people and nurses’ role in foot health care and pre-post design intervention study in nursing home with nursing staff (n=16) and older residents (n=43) were conducted. In phase 2, a descriptive and explorative study design was employed to develop an instrument for assessing foot health in older people (N=651, n=309, response rate 47%) and explore the psychometrics of the instrument. The data were collected from sheltered housing and home care settings. Finally, in phase 3, descriptive and explorative as well as cross-sectional correlational survey designs were used to assess foot health and evaluate the foot self-care activities of older people (N=651, n=309, response rate 47%) and to describe foot care knowledge and caring activities of nurses (N=651, n=322, response rate 50%) in home care in Finland. To achieve this, the Foot Health Assessment Instrument (FHAI) developed in phase 2 was used; at the same time, this large sample also was used for the psychometric evaluation of the FHAI. The data analysis methods used in this study were content analysis, descriptive and inferential statistics including factor and multivariate analysis. Many long-term diseases can manifest in feet. Therefore, the FHAI, developed in this study consisted of items relating to skin and nail health, foot structure and foot pain. The FHAI demonstrated acceptable preliminary psychometric properties. A great deal of different foot health problems in older people were found of which edema, dry skin, thickened and discoloured toenails and hallux valgus were the most prevalent foot health problems. Moreover, many older people had difficulties in performing foot self-care. Nurses’ knowledge of foot care was insufficient and revealed a need for more information and continuing education in matters relating to foot care in older people. Instead, nurses’ foot care activities were mainly adequate, though the findings indicate the need for updating foot care activities to correspond with the evidence found in the field of foot care. Practical implications are presented for nursing practice, education and administration. In future, research should focus on developing interventions for older people and nurses to promote foot health in older people and to prevent foot health problems, as well as for further development of the FHAI.

Clinical Learning Environment and Supervision. Development and Validation of the CLES Evaluation Scale

The purpose of the study is: (1) to describe how nursing students' experienced their clinical learning environment and the supervision given by staff nurses working in hospital settings; and (2) to develop and test an evaluation scale of Clinical Learning Environment and Supervision (CLES). The study has been carried out in different phases. The pilot study (n=163) explored the association between the characteristics of a ward and its evaluation as a learning environment by students. The second version of research instrument (which was developed by the results of this pilot study) were tested by an expert panel (n=9 nurse teachers) and test-retest group formed by student nurses (n=38). After this evaluative phase, the CLES was formed as the basic research instrument for this study and it was tested with the Finnish main sample (n=416). In this phase, a concurrent validity instrument (Dunn & Burnett 1995) was used to confirm the validation process of CLES. The international comparative study was made by comparing the Finnish main sample with a British sample (n=142). The international comparative study was necessary for two reasons. In the instrument developing process, there is a need to test the new instrument in some other nursing culture. Other reason for comparative international study is the reflecting the impact of open employment markets in the European Union (EU) on the need to evaluate and to integrate EU health care educational systems. The results showed that the individualised supervision system is the most used supervision model and the supervisory relationship with personal mentor is the most meaningful single element of supervision evaluated by nursing students. The ward atmosphere and the management style of ward manager are the most important environmental factors of the clinical ward. The study integrates two theoretical elements - learning environment and supervision - in developing a preliminary theoretical model. The comparative international study showed that, Finnish students were more satisfied and evaluated their clinical placements and supervision with higher scores than students in the United Kingdom (UK). The difference between groups was statistical highly significant (p= 0.000). In the UK, clinical placements were longer but students met their nurse teachers less frequently than students in Finland. Arrangements for supervision were similar. This research process has produced the evaluation scale (CLES), which can be used in research and quality assessments of clinical learning environment and supervision in Finland and in the UK. CLES consists of 27 items and it is sub-divided into five sub-dimensions. Cronbach's alpha coefficient varied from high 0.94 to marginal 0.73. CLES is a compact evaluation scale and user-friendliness makes it suitable for continuing evaluation.

Development of data sheets for statistical evaluation of fatigue data

To enable a mathematically and physically sound execution of the fatigue test and a correct interpretation of its results, statistical evaluation methods are used to assist in the analysis of fatigue testing data. The main objective of this work is to develop step-by-stepinstructions for statistical analysis of the laboratory fatigue data. The scopeof this project is to provide practical cases about answering the several questions raised in the treatment of test data with application of the methods and formulae in the document IIW-XIII-2138-06 (Best Practice Guide on the Statistical Analysis of Fatigue Data). Generally, the questions in the data sheets involve some aspects: estimation of necessary sample size, verification of the statistical equivalence of the collated sets of data, and determination of characteristic curves in different cases. The series of comprehensive examples which are given in this thesis serve as a demonstration of the various statistical methods to develop a sound procedure to create reliable calculation rules for the fatigue analysis.

Product Platform Development from the Product Lines' Perspective: Case of Switching Platform

In the era of fast product development and customized product requirements, the concept of product platform has proven its power in practice. The product platform approach has enabledcompanies to increase the speed of product introductions while simultaneously benefit from efficiency and effectiveness in the development and production activities. The product platforms are technological bases, which can be used to develop several derivative products, and hence, the differentiation can be pushed closer to the product introduction. The product platform development has some specific features, which differ somewhat from the product development of single products. The time horizon is longer, since the product platform¿slife cycle is longer than individual product's. The long time-horizon also proposes higher market risks and the use of new technologies increases the technological risks involved. The end-customer interface might be far away, but there is not a lack of needs aimed at the product platforms ¿ in fact, the product platform development is very much balancing between the varying needs set to it by thederivative products. This dissertation concentrated on product platform development from the internal product lines' perspective of a singlecase. Altogether six product platform development factors were identified: 'Strategic and business fit of product platform', 'Project communication and deliverables', 'Cooperation with product platform development', 'Innovativeness of product platform architecture and features', 'Reliability and quality of product platform', and 'Promised schedules and final product platform meeting the needs'. From the six factors, three were found to influence quite strongly the overall satisfaction, namely 'Strategic and business fit of product platform', 'Reliability and quality of product platform', and 'Promised schedules and final product platform meeting the needs'. Hence, these three factors might be the ones a new product platform development unit should concentrate first in order to satisfy their closest customers, the product lines. The 'Project communication and deliverables' and 'Innovativeness of product platform architecture and features' were weaker contributors to the overall satisfaction. Overall, the factors explained quite well the satisfaction of the product lines with product platform development. Along the research, several interesting aspects about the very basic nature of the product platform development were found. The long time horizon of the product platform development caused challenges in the area of strategic fIT - a conflict between the short-term requirements and long term needs. The fact that a product platform was used as basis of several derivative products resulted into varying needs, and hence the match with the needs and the strategies. The opinions, that the releases of the larger product lines were given higher priorities, give an interesting contribution to the strategy theory of powerand politics. The varying needs of the product lines, the strengths of them as well as large number of concurrent releases set requirements to prioritization. Hence, the research showed the complicated nature of the product platform development in the case unIT - the very basic nature of the product platform development might be its strength (gaining efficiency and effectiveness in product development and product launches) but also the biggest challenge (developing products to meet several needs). As a single case study, the results of this research are not directly generalizable to all the product platform development activities. Instead, the research serves best as a starting point for additional research as well as gives some insights about the factors and challengesof one product development unit.

Implementing Agile Software Development Methods in a Small Organization

Currently there is a vogue for Agile Software Development methods and many software development organizations have already implemented or they are planning to implement agile methods. Objective of this thesis is to define how agile software development methods are implemented in a small organization. Agile methods covered in this thesis are Scrum and XP. From both methods the key practices are analysed and compared to waterfall method. This thesis also defines implementation strategy and actions how agile methods are implemented in a small organization. In practice organization must prepare well and all needed meters are defined before the implementation starts. In this work three different sample projects are introduced where agile methods were implemented. Experiences from these projects were encouraging although sample set of projects were too small to get trustworthy results.

Introducing Continuous Integration for C and C++ Software Development Projects on Linux Platform

Software integration is a stage in a software development process to assemble separate components to produce a single product. It is important to manage the risks involved and being able to integrate smoothly, because software cannot be released without integrating it first. Furthermore, it has been shown that the integration and testing phase can make up 40 % of the overall project costs. These issues can be mitigated by using a software engineering practice called continuous integration. This thesis work presents how continuous integration is introduced to the author's employer organisation. This includes studying how the continuous integration process works and creating the technical basis to start using the process on future projects. The implemented system supports software written in C and C++ programming languages on Linux platform, but the general concepts can be applied to any programming language and platform by selecting the appropriate tools. The results demonstrate in detail what issues need to be solved when the process is acquired in a corporate environment. Additionally, they provide an implementation and process description suitable to the organisation. The results show that continuous integration can reduce the risks involved in a software process and increase the quality of the product as well.

Challenges and Means for the Front End Activities of Software Development

The front end of innovation is regarded as one of the most important steps in building new software products or services, and the most significant benefits in software development can be achieved through improvements in the front end activities. Problems in the front end phase have an impact on customer dissatisfaction with delivered software, and on the effectiveness of the entire software development process. When these processes are improved, the likelihood of delivering high quality software and business success increases. This thesis highlights the challenges and problems related to the early phases of software development, and provides new methods and tools for improving performance in the front end activities of software development. The theoretical framework of this study comprises two fields of research. The first section belongs to the field of innovation management, and especially to the management of the early phases of the innovation process, i.e. the front end of innovation. The second section of the framework is closely linked to the processes of software engineering, especially to the early phases of the software development process, i.e. the practice of requirements engineering. Thus, this study extends the theoretical knowledge and discloses the differences and similarities in these two fields of research. In addition, this study opens up a new strand for academic discussion by connecting these research directions. Several qualitative business research methodologies have been utilized in the individual publications to solve the research questions. The theoretical and managerial contribution of the study can be divided into three areas: 1) processes and concepts, 2) challenges and development needs, and 3) means and methods for the front end activities of software development. First, the study discloses the difference and similarities between the concepts of the front end of innovation and requirements engineering, and proposes a new framework for managing the front end of the software innovation process, bringing business and innovation perspectives into software development. Furthermore, the study discloses managerial perceptions of the similarities and differences in the concept of the front end of innovation between the software industry and the traditional industrial sector. Second, the study highlights the challenges and development needs in the front end phase of software development, especially challenges in communication, such as linguistic problems, ineffective communication channels, a communication gap between users/customers and software developers, and participation of multiple persons in software development. Third, the study proposes new group methods for improving the front end activities of software development, especially customer need assessment, and the elicitation of software requirements.

Evaluating the success of software development projects in Russia, Ukraine, and Belarus

The size and complexity of projects in the software development are growing very fast. At the same time, the proportion of successful projects is still quite low according to the previous research. Although almost every project's team knows main areas of responsibility which would help to finish project on time and on budget, this knowledge is rarely used in practice. So it is important to evaluate the success of existing software development projects and to suggest a method for evaluating success chances which can be used in the software development projects. The main aim of this study is to evaluate the success of projects in the selected geographical region (Russia-Ukraine-Belarus). The second aim is to compare existing models of success prediction and to determine their strengths and weaknesses. Research was done as an empirical study. A survey with structured forms and theme-based interviews were used as the data collection methods. The information gathering was done in two stages. At the first stage, project manager or someone with similar responsibilities answered the questions over Internet. At the second stage, the participant was interviewed; his or her answers were discussed and refined. It made possible to get accurate information about each project and to avoid errors. It was found out that there are many problems in the software development projects. These problems are widely known and were discussed in literature many times. The research showed that most of the projects have problems with schedule, requirements, architecture, quality, and budget. Comparison of two models of success prediction presented that The Standish Group overestimates problems in project. At the same time, McConnell's model can help to identify problems in time and avoid troubles in future. A framework for evaluating success chances in distributed projects was suggested. The framework is similar to The Standish Group model but it was customized for distributed projects.

Towards increased productivity and quality in software development using agile, lean and collaborative approaches

Dagens programvaruindustri står inför alltmer komplicerade utmaningar i en värld där programvara är nästan allstädes närvarande i våra dagliga liv. Konsumenten vill ha produkter som är pålitliga, innovativa och rika i funktionalitet, men samtidigt också förmånliga. Utmaningen för oss inom IT-industrin är att skapa mer komplexa, innovativa lösningar till en lägre kostnad. Detta är en av orsakerna till att processförbättring som forskningsområde inte har minskat i betydelse. IT-proffs ställer sig frågan: “Hur håller vi våra löften till våra kunder, samtidigt som vi minimerar vår risk och ökar vår kvalitet och produktivitet?” Inom processförbättringsområdet finns det olika tillvägagångssätt. Traditionella processförbättringsmetoder för programvara som CMMI och SPICE fokuserar på kvalitets- och riskaspekten hos förbättringsprocessen. Mer lättviktiga metoder som t.ex. lättrörliga metoder (agile methods) och Lean-metoder fokuserar på att hålla löften och förbättra produktiviteten genom att minimera slöseri inom utvecklingsprocessen. Forskningen som presenteras i denna avhandling utfördes med ett specifikt mål framför ögonen: att förbättra kostnadseffektiviteten i arbetsmetoderna utan att kompromissa med kvaliteten. Den utmaningen attackerades från tre olika vinklar. För det första förbättras arbetsmetoderna genom att man introducerar lättrörliga metoder. För det andra bibehålls kvaliteten genom att man använder mätmetoder på produktnivå. För det tredje förbättras kunskapsspridningen inom stora företag genom metoder som sätter samarbete i centrum. Rörelsen bakom lättrörliga arbetsmetoder växte fram under 90-talet som en reaktion på de orealistiska krav som den tidigare förhärskande vattenfallsmetoden ställde på IT-branschen. Programutveckling är en kreativ process och skiljer sig från annan industri i det att den största delen av det dagliga arbetet går ut på att skapa något nytt som inte har funnits tidigare. Varje programutvecklare måste vara expert på sitt område och använder en stor del av sin arbetsdag till att skapa lösningar på problem som hon aldrig tidigare har löst. Trots att detta har varit ett välkänt faktum redan i många decennier, styrs ändå många programvaruprojekt som om de vore produktionslinjer i fabriker. Ett av målen för rörelsen bakom lättrörliga metoder är att lyfta fram just denna diskrepans mellan programutvecklingens innersta natur och sättet på vilket programvaruprojekt styrs. Lättrörliga arbetsmetoder har visat sig fungera väl i de sammanhang de skapades för, dvs. små, samlokaliserade team som jobbar i nära samarbete med en engagerad kund. I andra sammanhang, och speciellt i stora, geografiskt utspridda företag, är det mera utmanande att införa lättrörliga metoder. Vi har nalkats utmaningen genom att införa lättrörliga metoder med hjälp av pilotprojekt. Detta har två klara fördelar. För det första kan man inkrementellt samla kunskap om metoderna och deras samverkan med sammanhanget i fråga. På så sätt kan man lättare utveckla och anpassa metoderna till de specifika krav som sammanhanget ställer. För det andra kan man lättare överbrygga motstånd mot förändring genom att introducera kulturella förändringar varsamt och genom att målgruppen får direkt förstahandskontakt med de nya metoderna. Relevanta mätmetoder för produkter kan hjälpa programvaruutvecklingsteam att förbättra sina arbetsmetoder. När det gäller team som jobbar med lättrörliga och Lean-metoder kan en bra uppsättning mätmetoder vara avgörande för beslutsfattandet när man prioriterar listan över uppgifter som ska göras. Vårt fokus har legat på att stöda lättrörliga och Lean-team med interna produktmätmetoder för beslutsstöd gällande så kallad omfaktorering, dvs. kontinuerlig kvalitetsförbättring av programmets kod och design. Det kan vara svårt att ta ett beslut att omfaktorera, speciellt för lättrörliga och Lean-team, eftersom de förväntas kunna rättfärdiga sina prioriteter i termer av affärsvärde. Vi föreslår ett sätt att mäta designkvaliteten hos system som har utvecklats med hjälp av det så kallade modelldrivna paradigmet. Vi konstruerar även ett sätt att integrera denna mätmetod i lättrörliga och Lean-arbetsmetoder. En viktig del av alla processförbättringsinitiativ är att sprida kunskap om den nya programvaruprocessen. Detta gäller oavsett hurdan process man försöker introducera – vare sig processen är plandriven eller lättrörlig. Vi föreslår att metoder som baserar sig på samarbete när processen skapas och vidareutvecklas är ett bra sätt att stöda kunskapsspridning på. Vi ger en översikt över författarverktyg för processer på marknaden med det förslaget i åtanke.

Complexity Optimization in Product Development with Modularization

A company’s competence to manage its product portfolio complexity is becoming critically important in the rapidly changing business environment. The continuous evolvement of customer needs, the competitive market environment and internal product development lead to increasing complexity in product portfolios. The companies that manage the complexity in product development are more profitable in the long run. The complexity derives from product development and management processes where the new product variant development is not managed efficiently. Complexity is managed with modularization which is a method that divides the product structure into modules. In modularization, it is essential to take into account the trade-off between the perceived customer value and the module or component commonality across the products. Another goal is to enable the product configuration to be more flexible. The benefits are achieved through optimizing complexity in module offering and deriving the new product variants more flexibly and accurately. The developed modularization process includes the process steps for preparation, mapping the current situation, the creation of a modular strategy and implementing the strategy. Also the organization and support systems have to be adapted to follow-up targets and to execute modularization in practice.

Software Test Process Development

In this thesis, the components important for testing work and organisational test process are identified and analysed. This work focuses on the testing activities in reallife software organisations, identifying the important test process components, observing testing work in practice, and analysing how the organisational test process could be developed. Software professionals from 14 different software organisations were interviewed to collect data on organisational test process and testing‐related factors. Moreover, additional data on organisational aspects was collected with a survey conducted on 31 organisations. This data was further analysed with the Grounded Theory method to identify the important test process components, and to observe how real‐life test organisations develop their testing activities. The results indicate that the test management at the project level is an important factor; the organisations do have sufficient test resources available, but they are not necessarily applied efficiently. In addition, organisations in general are reactive; they develop their process mainly to correct problems, not to enhance their efficiency or output quality. The results of this study allows organisations to have a better understanding of the test processes, and develop towards better practices and a culture of preventing problems, not reacting to them.

Competence in intensive and critical care nursing - development of a basic assessment scale for graduating nursing students

Intensive and critical care nursing is a speciality in its own right and with its own nature within the nursing profession. This speciality poses its own demands for nursing competencies. Intensive and critical care nursing is focused on severely ill patients and their significant others. The patients are comprehensively cared for, constantly monitored and their vital functions are sustained artificially. The main goal is to win time to cure the cause of the patient’s situation or illness. The purpose of this empirical study was i) to describe and define competence and competence requirements in intensive and critical care nursing, ii) to develop a basic measurement scale for competence assessment in intensive and critical care nursing for graduating nursing students, and iii) to describe and evaluate graduating nursing students’ basic competence in intensive and critical care nursing by seeking the reference basis of self-evaluated basic competence in intensive and critical care nursing from ICU nurses. However, the main focus of this study was on the outcomes of nursing education in this nursing speciality. The study was carried out in different phases: basic exploration of competence (phase 1 and 2), instrumentation of competence (phase 3) and evaluation of competence (phase 4). Phase 1 (n=130) evaluated graduating nursing students’ basic biological and physiological knowledge and skills for working in intensive and critical care with Basic Knowledge Assessment Tool version 5 (BKAT-5, Toth 2012). Phase 2 focused on defining competence in intensive and critical care nursing with the help of literature review (n=45 empirical studies) as well as competence requirements in intensive and critical care nursing with the help of experts (n=45 experts) in a Delphi study. In phase 3 the scale Intensive and Critical Care Nursing Competence Scale (ICCN-CS) was developed and tested twice (pilot test 1: n=18 students and n=12 nurses; pilot test 2: n=56 students and n=54 nurses). Finally, in phase 4, graduating nursing students’ competence was evaluated with ICCN-CS and BKAT version 7 (Toth 2012). In order to develop a valid assessment scale of competence for graduating nursing students and to evaluate and establish the competence of graduating nursing students, empirical data were retrieved at the same time from both graduating nursing students (n=139) and ICU nurses (n=431). Competence can be divided into clinical and general professional competence. It can be defined as a specific knowledge base, skill base, attitude and value base and experience base of nursing and the personal base of an intensive and critical care nurse. Personal base was excluded in this self-evaluation based scale. The ICCN-CS-1 consists of 144 items (6 sum variables). Finally, it became evident that the experience base of competence is not a suitable sum variable in holistic intensive and critical care competence scale for graduating nursing students because of their minor experience in this special nursing area. ICCN-CS-1 is a reliable and tolerably valid scale for use among graduating nursing students and ICU nurses Among students, basic competence of intensive and critical care nursing was self-rated as good by 69%, as excellent by 25% and as moderate by 6%. However, graduating nursing students’ basic biological and physiological knowledge and skills for working in intensive and critical care were poor. The students rated their clinical and professional competence as good, and their knowledge base and skill base as moderate. They gave slightly higher ratings for their knowledge base than skill base. Differences in basic competence emerged between graduating nursing students and ICU nurses. The students’ self-ratings of both their basic competence and clinical and professional competence were significantly lower than the nurses’ ratings. The students’ self-ratings of their knowledge and skill base were also statistically significantly lower than nurses’ ratings. However, both groups reported the same attitude and value base, which was excellent. The strongest factor explaining students’ conception of their competence was their experience of autonomy in nursing. Conclusions: Competence in intensive and critical care nursing is a multidimensional concept. Basic competence in intensive and critical care nursing can be measured with self-evaluation based scale but alongside should be used an objective evaluation method. Graduating nursing students’ basic competence in intensive and critical care nursing is good but their knowledge and skill base are moderate. Especially the biological and physiological knowledge base is poor. Therefore in future in intensive and critical care nursing education should be focused on both strengthening students’ biological and physiological knowledge base and on strengthening their overall skill base. Practical implications are presented for nursing education, practice and administration. In future, research should focus on education methods and contents, mentoring of clinical practice and orientation programmes as well as further development of the scale.