BACKGROUND Determination of relationships between transcranial Doppler (TCD)-based spectral pulsatility index (sPI) and pulse amplitude (AMP) of intracranial pressure (ICP) in 2 groups of severe traumatic brain injury (TBI) patients (a) displaying plateau waves and (b) with unstable mean arterial pressure (MAP). METHODS We retrospectively reviewed patients with severe TBI and continuous TCD m...

Software Process Improvement (SPI) is the modification of current software process methods in many software development organizations. It is the key of the continuous process improvement. In this paper, we introduce Software Process Improvement (SPI) and Quality Function Deployment (QFD); the SPI framework based on CMMI contains two portions: 1) SPI framework for CMMI staged model based on QFD ...

This paper is aimed at ident ify ing the potent ial role of SPI CE, especially SPI CE level 3, to achieving the proposed UK public sector efficiencies. SPI CE level 3 presents the process m aturity fram ework to address the level I I I of the SPICE model. Building upon the developments of level I I , SPI CE 3 advocates establishment of a process improvement infrast ructure to facilitate good pr...

Software development organizations are focusing on improving the process of software development so that the resultant software is of high quality and the development cost is low from the viewpoint of the competitive advantage. Software process improvement (SPI) is a methodical and continuous improvement approach for the software development processes to develop quality software. SPI establishe...

Working with software process improvement (SPI), using measurements and statistical methods, can easily be a challenge for SPI people. Workers dislike having their processes monitored and managers dislike being informed of their processes being less than perfect. The power needed by SPI people for carrying out their work may thus be challenged, and one way of facing up to this might be to argue...

Software Process Improvement (SPI) is a recognised systematic approach for improving the capability of software organisations. Such initiatives have met with a number of difficulties such as: scaling the SPI initiatives, setting realistic goals, the complexity of organisational changes, and the organisational culture. For organisations with no earlier experience with SPI, the first initiative m...

Software organisations have for many years struggled to mature engineering practices using a variety of approaches. Over the last decade a new approach, known as software process improvement (SPI), has emerged and become widely used in the software industry. In this paper we position SPI in the landscape of initiatives that can be used in software organisations to mature their operations. A map...

One of the most popular ways to improve the software development capability in organizations is to embark upon a Software Process Improvement (SPI) program often based on a normative model. Main concerns in such a SPI program includes creating commitment towards SPI, involving all parts of the organization in the SPI program, and creating opportunities for learning. We suggest the use of projec...

The successful implementation of Software Process Improvement (SPI) depends not only on the abilities of practitioners to identify processes modifications that may help to increase organizations capabilities to develop software, but also abilities to overcome barriers that can jeopardize the organizational change process provoked by SPI initiatives. The literature reports show that SPI practiti...

Software Process Improvement (SPI) encompasses the analysis and modification of the processes within software development, aimed at improving key areas that contribute to the organizations’ goals. The task of evaluating whether the selected improvement path meets these goals is challenging. On the basis of the results of a systematic literature review on SPI measurement and evaluation practices...