1,720,986 research outputs found
Software process engineering systems: models and industry cases
Full text linkAbstractThe work with software processes has become an entire field of its own. It should be considered a process, where the product is process improvement and maintenance service to the host organization. The process professionals should also strive towards good product engineering practices in their work, apply the same quality criteria to their processes, and maintain and improve their own work practices. The time has come for Software Process Engineering.A number of models and articles related to Software Process Engineering exist, mostly developed to support process improvement activities. Each model approaches the subject from its particular angle and as such they all have their own limitations and strengths.For those responsible for process engineering efforts in their respective organisations, the multitude of choices can be sometimes confusing. The models and methods are at times conflicting or competing, operate at different granularity levels, and answer to different needs. There is a clear need for a study that gathers what has been published, categorises them and thus provides a wider perspective to what the Software Process Engineering literature has to offer for process engineers — mainly for operative and strategic managers — at large.This literature study summarises what the literature has to offer. The models and articles are presented here in a concise form, to provide an overview of the state-of-the-art and state-of-the-practice of Software Process Engineering models today.Abstract
The work with software processes has become an entire field of its own. It should be considered a process, where the product is process improvement and maintenance service to the host organization. The process professionals should also strive towards good product engineering practices in their work, apply the same quality criteria to their processes, and maintain and improve their own work practices. The time has come for Software Process Engineering.
A number of models and articles related to Software Process Engineering exist, mostly developed to support process improvement activities. Each model approaches the subject from its particular angle and as such they all have their own limitations and strengths.
For those responsible for process engineering efforts in their respective organisations, the multitude of choices can be sometimes confusing. The models and methods are at times conflicting or competing, operate at different granularity levels, and answer to different needs. There is a clear need for a study that gathers what has been published, categorises them and thus provides a wider perspective to what the Software Process Engineering literature has to offer for process engineers — mainly for operative and strategic managers — at large.
This literature study summarises what the literature has to offer. The models and articles are presented here in a concise form, to provide an overview of the state-of-the-art and state-of-the-practice of Software Process Engineering models today
Software process engineering in a multi-site environment : An architectural design of a software process engineering system
Full text linkAbstractA fundamental problem in the software engineering community is how to achieve a state of continuous improvement. Over the last ten years a number of studies have been made concerning various tools, methods and software process improvement project life-cycle models, but the problem persists and in many cases the software process improvement program dies off within a year.This thesis takes the assumption that the answer cannot be reduced to a single tool or method, as there are no silver bullets to complex problems. Instead the entire Software Process Engineering system should be studied to find out what elements are necessary for sustaining improvement activity on a long-term basis. Through understanding the fundamental elements of a Software Process Engineering system, the organization can manage and improve the system, tune it up to the environment and make it efficient and effective. When the system is operational, the software process improvement program, which is a part of the system, can be sustained.This research studies a case in which the Software Process Engineering system of a large, multi-site telecommunications company was successfully revised to meet the increasing improvement challenges. The revised system has proven to be capable of sustaining continuous improvement and case is used here to derive architectural design models of a Software Process Engineering system.Two such models are established here. One is a system model that is independent of implementation and identifies the main elements of a Software Process Engineering system. With the help of this model, those responsible for process improvement in their organizations can design, evaluate, and revise complete Software Process Engineering systems. The other model is a design of a multi-site Software Process Engineering organization, and identifies not only the operative part of the organization but also the key non-operative elements that a Software Process Engineering system needs to work with. With the help of this model a multi-site organization can set up the operative Software Process Engineering organization and plan for strategies for managing the cooperation with the interfacing entities up front, rather than ending up managing such contacts on a reactive fashion.Academic Dissertation to be presented with the assent of the Faculty of Science, University of Oulu, for public discussion in Raahensali (Auditorium L 10), on August 14th, 1999, at 12 noon.Abstract
A fundamental problem in the software engineering community is how to achieve a state of continuous improvement. Over the last ten years a number of studies have been made concerning various tools, methods and software process improvement project life-cycle models, but the problem persists and in many cases the software process improvement program dies off within a year.
This thesis takes the assumption that the answer cannot be reduced to a single tool or method, as there are no silver bullets to complex problems. Instead the entire Software Process Engineering system should be studied to find out what elements are necessary for sustaining improvement activity on a long-term basis. Through understanding the fundamental elements of a Software Process Engineering system, the organization can manage and improve the system, tune it up to the environment and make it efficient and effective. When the system is operational, the software process improvement program, which is a part of the system, can be sustained.
This research studies a case in which the Software Process Engineering system of a large, multi-site telecommunications company was successfully revised to meet the increasing improvement challenges. The revised system has proven to be capable of sustaining continuous improvement and case is used here to derive architectural design models of a Software Process Engineering system.
Two such models are established here. One is a system model that is independent of implementation and identifies the main elements of a Software Process Engineering system. With the help of this model, those responsible for process improvement in their organizations can design, evaluate, and revise complete Software Process Engineering systems. The other model is a design of a multi-site Software Process Engineering organization, and identifies not only the operative part of the organization but also the key non-operative elements that a Software Process Engineering system needs to work with. With the help of this model a multi-site organization can set up the operative Software Process Engineering organization and plan for strategies for managing the cooperation with the interfacing entities up front, rather than ending up managing such contacts on a reactive fashion
Order-delivery process for modular consulting services
Full text linkThe aim of this thesis was to research how the service business, the service order-delivery process and service providers’ productivity can be developed. The research consists of theoretical study, an empirical case study and development recommendations for the case company.
The service business can be developed by productising the service offering to create prerequisites for repeatability and scalability, defining and implementing the order-delivery process for productive service delivery and improved process performance. Services should be managed more like tangible products, and evidence of service should be offered to the customer. Value delivery and capture should be taken into account when designing value delivery systems. The service delivery process should have a modular structure where the beginning (order) and the end (post-mortem) phases of the process are standard and the centre of the process is modular and can be tailored to fit the customer’s needs. The modular part of the service process is built from service process modules that are put together for each of the service modules or products. The service process blueprinting should be done using a product-service blueprint that directs the user to take all of the required aspects into account during the process design.
The case company’s main challenges in the service business revolved around the same topics as the challenges in the service business in general. Firstly, the case company had not productised its offering. Secondly, the order-delivery process for consulting services was not Lean or mature. Thirdly, the value delivery and the value capture were not managed.
A new order-delivery process for business consultation services of the case company was developed. The process is three-phased and includes the order, delivery and post-mortem process stages. The process is blueprinted using a product-service blueprint method and the process description includes tasks and documents that are required to deliver value to the customer and capture value for the service-providing company. Linkage between the process development and service productisation activities are also discussed.
The results of the study can be utilised for service business development, service order-delivery process development and service productization purposes. The results are applicable for consultative services and further research is required to verify the model’s suitability for other services.Tämän diplomityön tavoitteena on tutkia palveluliiketoimintaa, palveluiden tilaus-toimitusprosesseja ja sitä, miten palveluyritysten tuottavuutta voidaan parantaa. Tutkimus koostuu teoreettisesta tutkimuksesta, empiirisestä tapaustutkimuksesta ja kehityssuosituksista kohdeyritykselle.
Palveluliiketoimintaa voidaan kehittää ensinnäkin tuotteistamalla palvelutarjooma. Tuotteistus toimii edellytyksenä palveluiden toistettavuudelle ja skaalautuvuudelle. Toiseksi voidaan määrittää ja käyttöönottaa tilaus-toimitusprosessi, jonka avulla saavutetaan parempi tuottavuus ja prosessien suorituskyky. Palveluita tulisi hallita nykyistä enemmän kuin fyysisiä tuotteita ja asiakkaalle tulisi toimittaa fyysisiä todisteita palvelusta. Arvoketjua suunnitellessa tulisi ottaa huomioon myös arvon toimittamisen ja vangitsemisen näkökulmat. Palvelun toimitusprosessilla tulisi olla modulaarinen rakenne, jossa prosessin alku (tilaaminen) ja loppu (jälkiselvittely) ovat standardiosia ja prosessin keskiosa muodostuu moduuleista. Moduulit voidaan räätälöidä asiakastarpeen mukaan. Modulaarinen osa muodostuu palveluprosessimoduuleista, jotka ovat tuotekohtaisia. Palveluprosessi tulisi mallintaa käyttämällä tuote-palvelu prosessisuunnitelmamallia, joka ohjaa mallin käyttäjän ottamaan kaikki prosessisuunnittelun kannalta oleelliset seikat huomioon prosessikehitystyössä.
Kohdeyrityksen päähaasteet palveluliiketoiminnassa ovat tyypillisiä palveluliiketoiminnan haasteita. Kohdeyritys ei ensinnäkään ollut tuotteistanut tarjoamaansa. Toiseksi tilaus-toimitusprosessi konsultointipalveluille ei ollut kilpailukykyinen eikä kypsä. Kolmanneksi arvon toimittaminen ja vangitseminen ei ollut hallittua.
Kohdeyrityksen konsultointipalveluille kehitettiin tilaus-toimitusprosessi. Prosessi sisältää tilaus-, toimitus- ja jälkikäsittelyvaiheet. Prosessi on mallinnettu käyttäen erityistä tuote-palveluprosesseille tarkoitettua suunnittelumallia ja prosessikuvaus sisältää tehtävät ja dokumentit, jotka vaaditaan arvon toimittamiseen asiakkaalle ja arvon vangitsemiseen palvelua toimittavalle yritykselle. Prosessikehitystyön ja palveluiden tuotteistamisen välistä suhdetta on käsitelty myös työssä.
Työn tuloksia voidaan hyödyntää palveluliiketoiminnan kehittämiseen, palveluiden tilaus-toimitusprosessien suunnitteluun ja palveluiden tuotteistamiseen. Tulokset ovat hyödynnettävissä konsultatiivisille palveluille ja tutkimuksen tulosten sovellettavuutta muun tyyppisille palveluille tulee vielä tutkia
Going Beyond Counting First Authors in Author Co-citation Analysis
Full text linkThe present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
Software process engineering systems:models and industry cases
No full textThe work with software processes has become an entire field of its own. It should be considered a process, where the product is process improvement and maintenance service to the host organization.The process professionals should also strive towards good product engineering practices in their work, apply the same quality criteria to their processes, and maintain and improve their own work practices. The time has come for Software Process Engineering.A number of models and articles related to Software Process Engineering exist, mostly developed to support process improvement activities. Each model approaches the subject from its particular angle and as such they all have their own limitations and strengths.For those responsible for process engineering efforts in their respective organisations, the multitude of choices can be sometimes confusing. The models and methods are at times conflicting or competing, operate at different granularity levels, and answer to different needs. There is a clear need for a study that gathers what has been published, categorises them and thus provides a wider perspective to what the Software Process Engineering literature has to offer for process engineers - mainly for operative and strategic managers - at large.This literature study summarises what the literature has to offer. The models and articles are presented here in a concise form, to provide an overview of the state-of-the-art and state-of-the-practice of Software Process Engineering models today
Software process engineering in a multi-site environment:an architectural design of a software process engineering system: Dissertation
No full textA fundamental problem in the software engineering community is how to achieve a state of continuous improvement. Over the last ten years a number of studies have been made concerning various tools, methods and software process improvement project life-cycle models, but the problem persists and in many cases the software process improvement program dies off within a year.This thesis takes the assumption that the answer cannot be reduced to a single tool or method, as there are no silver bullets to complex problems. Instead the entire Software Process Engineering system should be studied to find out what elements are necessary for sustaining improvement activity on a long-term basis. Through understanding the fundamental elements of a Software Process Engineering system, the organization can manage and improve the system, tune it up to the environment and make it efficient and effective. When the system is operational, the software process improvement program, which is a part of the system, can be sustained.This research studies a case in which the Software Process Engineering system of a large, multi-site telecommunications company was successfully revised to meet the increasing improvement challenges. The revised system has proven to be capable of sustaining continuous improvement and case is used here to derive architectural design models of a Software Process Engineering system.Two such models are established here. One is a system model that is independent of implementation and identifies the main elements of a Software Process Engineering system. With the help of this model, those responsible for process improvement in their organizations can design, evaluate, and revise complete Software Process Engineering systems. The other model is a design of a multi-site Software Process Engineering organization, and identifies not only the operative part of the organization but also the key non-operative elements that a Software Process Engineering system needs to work with. With the help of this model a multi-site organization can set up the operative Software Process Engineering organization and plan for strategies for managing the cooperation with the interfacing entities up front, rather than ending up managing such contacts on a reactive fashion
Variations on the Author
Full text link“Variations on the Author” discusses two of Eduardo Coutinho’s recent films (Um Dia na Vida, from 2010, and Últimas Conversas, posthumously released in 2015) and their contribution to the general question of documentary authorship. The director’s filmography is characterized by a consistent yet self-effacing form of authorial self-inscription: Coutinho often features as an interviewer that rather than express opinions propels discourses; an interviewer that is good at listening. This mode of self-inscription characterizes him as an author who is not expressive but who is nonetheless markedly present on the screen. In Um Dia na Vida, however, Coutinho is completely absent form the image, while Últimas Conversas, on the contrary, includes a confessional prologue that moves the director from the margins to the center of his films. This article examines the ways in which these works stand out in the filmography of a director who offers new insights into the notion of cinematic authorship
Appropriate Similarity Measures for Author Cocitation Analysis
Full text linkWe provide a number of new insights into the methodological discussion about author cocitation analysis. We first argue that the use of the Pearson correlation for measuring the similarity between authors’ cocitation profiles is not very satisfactory. We then discuss what kind of similarity measures may be used as an alternative to the Pearson correlation. We consider three similarity measures in particular. One is the well-known cosine. The other two similarity measures have not been used before in the bibliometric literature. Finally, we show by means of an example that our findings have a high practical relevance.information science;Pearson correlation;cosine;similarity measure;author cocitation analysis
Software process engineering in a multi-site environment:an architectural design of a software process engineering system: Dissertation
No full textA fundamental problem in the software engineering community is how to achieve a state of continuous improvement. Over the last ten years a number of studies have been made concerning various tools, methods and software process improvement project life-cycle models, but the problem persists and in many cases the software process improvement program dies off within a year.This thesis takes the assumption that the answer cannot be reduced to a single tool or method, as there are no silver bullets to complex problems. Instead the entire Software Process Engineering system should be studied to find out what elements are necessary for sustaining improvement activity on a long-term basis. Through understanding the fundamental elements of a Software Process Engineering system, the organization can manage and improve the system, tune it up to the environment and make it efficient and effective. When the system is operational, the software process improvement program, which is a part of the system, can be sustained.This research studies a case in which the Software Process Engineering system of a large, multi-site telecommunications company was successfully revised to meet the increasing improvement challenges. The revised system has proven to be capable of sustaining continuous improvement and case is used here to derive architectural design models of a Software Process Engineering system.Two such models are established here. One is a system model that is independent of implementation and identifies the main elements of a Software Process Engineering system. With the help of this model, those responsible for process improvement in their organizations can design, evaluate, and revise complete Software Process Engineering systems. The other model is a design of a multi-site Software Process Engineering organization, and identifies not only the operative part of the organization but also the key non-operative elements that a Software Process Engineering system needs to work with. With the help of this model a multi-site organization can set up the operative Software Process Engineering organization and plan for strategies for managing the cooperation with the interfacing entities up front, rather than ending up managing such contacts on a reactive fashion
- …
