Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
Springer-Verlag Berlin Heidelberg
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.
2008
1999
Abstract Nowadays software applications are present everywhere and producing them is a hard task: software firms are facing an increasing demand for new applications with higher quality and lower prices, but it is often difficult to exploit this business chance. This paper presents a case study regarding the adoption of domain analysis inside a software firm with the purpose to improve the software process and to introduce software reuse practices.
1999, VTT SYMPOSIUM
This paper suggests collaborative sense-making as a way to view the process toward creating mutually intelligible representations of requirements that can serve as bridges between different stakeholder communities over the software development lifecycle. In order to do this, we describe the types of obstacles that can impede representational literacy across communities of practice coming together in a design effort. We then offer representational morphing as a strategy for addressing these obstacles, and show how it ...
2001, Software Quality Journal
Management problems in the development of software have been addressed over the last years by a strong focus on the improvement of the development processes. Software process improvement (SPI) activities are characterized by an internal focus on a software development department and its procedures. However, the quality of the product is hardly addressed in software process improvement programs. This paper presents the application of a model for product focused SPI (P-SPI) and describes experiences with this model in practice. The main conclusions are that P-SPI puts products to be developed in a central position in improvement programs, results in fulfilling specific quality goals of a company and project, and industrial experiments show interesting benefits. Applying the approach in industrial projects showed that P-SPI is relatively cheap and gives fast results and high benefits.
2000
2010
2002, Software Metrics, 2002. …
2006
The Importance of Metrics in Search Based Software Engineering Mark Harman King's College London, Strand, London, WC2R 2LS Abstract. This paper was written to accompany the author's keynote talk at the Mensura Conference 2006. The keynote will present an overview of Search Based Software Engineering (SBSE) and explain how metrics play a crucial role in SBSE. 1 Search Based Software Engineering (SBSE) The aim of SBSE research is to move software engineering problems from human based search to machine-based search [15, 27].
2012, IEEE Transactions on Software Engineering
BACKGROUND-Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE-This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD-The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies, and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS-Seven distinct evaluation strategies were identified, wherein the most common one, “Pre-Post Comparison,” was applied in 49 percent of the inspected papers. Quality was the most measured attribute (62 percent), followed by Cost (41 percent), and Schedule (18 percent). Looking at measurement perspectives, “Project” represents the majority with 66 percent. CONCLUSION-The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that “Pre-Post Comparison” was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.
2000, IEEE Transactions on Software Engineering
The focus of this paper is to outline the experience of a European based software organization utilizing the IDEAL model, while implementing a tailored Capability Maturity Model (CMM) software process improvement program. The goal was to achieve process improvement rather than a specific CMM maturity level. In doing this, the IDEAL model was extensively researched and employed. The benefits and limitations of the IDEAL model are presented as experienced. Further details on this research are available in [1]. Research was carried out on a number of software process improvement paradigms prior to the selection of the CMM. A key element of this approach was to see the requirements of the organization as paramount and immediate. It was deemed important to achieve process improvement in specific Key Process Areas regardless of their position in the CMM. This provided the flexibility for future investment in SPI to capitalize on the current work.
2004
In today's software development organizations, methods and tools are employed that frequently lack sufficient evidence regarding their suitability, limits, qualities, costs, and associated risks. The need to select the best-suited method, technique or tool in a given business context is becoming more and more important. From a business perspective the trade-off between time-to-market, quality, and cost is a crucial factor for the decision process.
2001, Proceedings 2001 Australian Software Engineering Conference
2000, Lecture Notes in Computer Science
2002, Proceedings of the 2002 ACM symposium on Applied computing - SAC '02
1989, The Journal of Physical Chemistry
2004, Empirical Software Engineering
This paper describes an industrial experience in process improvement at one of the Unisys development labs in Australia. Following a capability maturity model (CMM) mini-assessment, the organization is undertaking significant changes in the requirements management process, which include the introduction of group session approaches to requirements analysis and a structured method for writing requirements. An empirical evaluation which investigated other aspects of the process improvement than the CMM model indicates tangible benefits as well as perceived long-term benefits during design and testing. Findings confirm that a more thorough requirements analysis results in more clearly defined, better understood and specified requirements, and an enhanced ability to address the market needs and product strategy requirements. The catalyst behind these improvements included project management leadership, managing the human dimension, collaboration among stakeholders and senior management support.
1998
ABSTRACT The state-of-the practice in requirements engineering is currently such that organisations wishing to improve their requirements processes find it hard to discover, evaluate and apply good practice. Good practice certainly exist but dissemination of practical experience is poor. Standards coverage of the requirements process is also patchy.
2004
As part of the research project 15504MPE, an assessment method with the objective of process improvement adapted to small brazilian software companies based on the standard ISO/IEC 15504 is being developed. The objective of the customization is to facilitate the application of 15504 also in small software companies in order to enable quality and productivity improvement. The method includes an
2009, Studies in Computational Intelligence
2008, Proceedings of the 13th international conference on Software engineering - ICSE '08
2008, Information & Software Technology
2007, Software Process: Improvement and Practice
2010, Journal of Software: Evolution and Process
Information & Software Technology
2007, Australasian Computing Education Conference
We propose a maturity model for computing edu- cation which is inspired by the Capability Maturity Model (CMM) used in software engineering. Similar to CMM, the Computing Education Maturity Model (CEMM) can be used to rate educational organisa- tions according to their capability to deliver high- quality education on a five level scale. Furthermore, CEMM can be used in order
2006, Information & Software Technology
This textbook comprises software and system engineering processes, advanced process technologies, software process management, and foundations of process improvement. The goal of this textbook is to provide knowledge and skills for understanding, designing, analyzing, applying, deploying, and improving software and system engineering processes. After reading this book, the reader should be able to: - understand the benefits of using software process models and process management, - identify goals for process modeling and management, - understand the underlying principles of software process modeling, management, and improvement, - analyze the advantages and disadvantages of different process modeling techniques and notations, - design and model software development processes for different purposes, - apply methods and notations for process modeling, - understand existing industrial software and system development processes, - analyze software and system development processes, - apply process management effectively for different purposes, - understand the importance of software process improvement, - identify software-related improvement goals for an organization and set priori-ties for improvement, - understand process maturity frameworks (e.g., CMMI), - understand the differences between existing process improvement approaches, - critically evaluate software process improvement approaches, - understand important mediators and obstacles when modeling, deploying, managing, and improving software development processes, - name and distinguish different lifecycle process models, - develop process handbooks, - deploy a prescriptive process model to an organization, understand the use of simulation in software process modeling, - be able to distinguish different types of process simulation models.
2010
Abstract Over the years software quality is becoming more and more important in software engineering. Like in other engineering disciplines where quality is already a commodity, software engineering is moving into these stages. The Team Software Process (TSP) was created by the Software Engineering Institute (SEI) with the main objective of helping software engineers and teams to ensure high-quality software products and improve process management in the organization.
2012
While we have learned a great deal from Software Process Improvement (SPI) research to date, no earlier study has been designed from the outset to examine the relationship between SPI and business success in software development small-to-medium-sized companies (software SMEs).
1988, Chemical Physics Letters
2010, International Journal of Computer Applications
For many years, industry and research communities have studied Software Process Improvement in enterprises. However, that research applied mainly to large enterprises. In 1998, the University of Namur (Belgium) began a research project on Software Process Improvement in small settings (fewer than 60 employees), mainly in Wallonia to begin with, where improvements have been evident. Then, experimentations have been conducted in several dozen enterprises in 3 countries by this university, the ÉTS (École de technologie supérieure, University of Québec, (Canada)) and the CETIC (Centre d'Excellence en Technologies de l'Information et de la Communication). After many assessments within Very Small Enterprises we found some constant about weaknesses and strength of those enterprises. The first section define what is a small enterprise, the second section present the approach and methodology, the section three present different assessment results in the last 7 years (1999-2006) and i...
Computer Standards & Interfaces
Harmonization plays an important role in organizations that are seeking to resolve manifold needs at their different hierarchical levels through multiple models such as CMMI, ISO 90003, ITIL, SWEBOK, COBIT, amongst others. A great diversity of models involves a wide heterogeneity not only about structure of their process entities and quality systems, but also with regards to terminology. This article presents an ontology which: provides the main concepts related to harmonization of multiple models; is supported by a web tool and; has been applied for the harmonization of COBIT 4.1, Basel II, VAL IT, RISK IT, ISO 27002 and ITIL.
2002
2010, Proceedings of the 18th International Conference …
2013, Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
2014
Funde d b y the Aus trian g ov ernmen t, the State of U pper Aus tria, the J ohan nes Kepler Univ ersity Linz Abstract. The paper presents an update of the change of expectations and most recent new approaches regarding software processes and their improvement following the Software Process Improvement Hype Cycle introduced earlier by the author as an extension of the Gartner Hype Cycle idea. Software process assessment and improvement can itself be considered on the more abstract level as a quest for compliance with best practices. Etics and regulatory regimes explicitly addressing safety-critical systems mean however stringent compliance requirements beyond the commitment to improve process capability. New approaches are necessary for software engineers to fulfill the considerably growing expectations regarding quality under much slower changing development budget and deadline constraints. Open Services for Lifecycle Collaboration (OSLC) is the emerging initiative inspired by the web which is currently at the technology trigger stage along its hype cycle with the potential to have a determining impact on the future of Software Process Compliance Engineering. Abstract. The paper presents an update of the change of expectations and most recent new approaches regarding software processes and their improvement following the Software Process Improvement Hype Cycle introduced earlier by the author as an extension of the Gartner Hype Cycle idea. Software process assessment and improvement can itself be considered on the more abstract level as a quest for compliance with best practices. Etics and regulatory regimes explicitly addressing safety-critical systems mean however stringent compliance requirements beyond the commitment to improve process capability. New approaches are necessary for software engineers to fulfill the considerably growing expectations regarding quality under much slower changing development budget and deadline constraints. Open Services for Lifecycle Collaboration (OSLC) is the emerging initiative inspired by the web which is currently at the technology trigger stage along its hype cycle with the potential to have a determining impact on the future of Software Process Compliance Engineering.
This thesis aims at developing software-intensive systems architecture for the Healthcare Industry to meet information assurance, legislative security and privacy standards by proposing an architecture and framework - “SARCHIA” using data mining and statistical techniques. “SARCHIA” can help the software industry guard against unauthorized access to Health Information. SARCHIA will help companies to track compliance in the healthcare industry by leveraging SARCHIA framework and architecture. The framework will be evaluated through a case study from the healthcare industry. SARCHIA will do the auditing, impact analysis of Key Compliance Attributes (KCA) on Key Quality Attributes (KQA), and will regulate financial and health information, and identify related risks.