Harmonizing CMMI-DEV 1.2 and XP Method to Improve The Software Development Processes in Small Software Development Firms

Most software development organizations are small firms, and they have realized the need to manage and improve their software development and management activities. Traditional Software Process Improvement (SPI) models and standards are not realistic for these firms because of high cost, limited resources and strict project deadlines. Therefore, these firms need a lightweight software development method and an appropriate SPI model to manage and improve their software development and management processes. This study aims to construct a suitable software development process improvement framework for Small Software Development Firms (SSDFs) based on eXtreme Programming (XP) method and Capability Maturity Model Integration for Development Version 1.2 (CMMI-Dev1.2) model. Four stages are involved in developing the framework: (1) aligning XP practices to the specific goals of CMMI-Dev1.2 Key Process Areas (KPAs); (2) developing the proposed software development process improvement framework based on extending XP method by adapting the Extension-Based Approach (EBA), CMMI-Dev1.2, and generic elements of the SPI framework; (3) verifying the compatibility of the proposed framework to the KPAs of CMMI-Dev1.2 by using focus group method coupled with Delphi technique; and (4) validating the modified framework by using CMMI-Dev1.2 questionnaire as a main item to validate the suitability of the modified framework for SSDFs, and conducting two case studies to validate the applicability and effectiveness of this framework for these firms. The result of aligning XP practices to the KPAs of CMMI-Dev1.2 shows that twelve KPAs are largely supported by XP practices, eight KPAs are partially supported by XP practices, and two KPAs are not-supported by XP practices. The main contributions of this study are: software development process improvement framework for SSDFs, elicit better understanding of how to construct the framework, and quality improvement of the software development processes. There are possible avenues for extending this research to fulfil the missing specific practices of several KPAs, examining other agile practices and using CMMI-Dev1.3 to improve the framework, and conducting more case studie

Size Matters: Microservices Research and Applications

In this chapter we offer an overview of microservices providing the introductory information that a reader should know before continuing reading this book. We introduce the idea of microservices and we discuss some of the current research challenges and real-life software applications where the microservice paradigm play a key role. We have identified a set of areas where both researcher and developer can propose new ideas and technical solutions.Comment: arXiv admin note: text overlap with arXiv:1706.0735

Estimating, planning and managing Agile Web development projects under a value-based perspective

Context: The processes of estimating, planning and managing are crucial for software development projects, since the results must be related to several business strategies. The broad expansion of the Internet and the global and interconnected economy make Web development projects be often characterized by expressions like delivering as soon as possible, reducing time to market and adapting to undefined requirements. In this kind of environment, traditional methodologies based on predictive techniques sometimes do not offer very satisfactory results. The rise of Agile methodologies and practices has provided some useful tools that, combined with Web Engineering techniques, can help to establish a framework to estimate, manage and plan Web development projects. Objective: This paper presents a proposal for estimating, planning and managing Web projects, by combining some existing Agile techniques with Web Engineering principles, presenting them as an unified framework which uses the business value to guide the delivery of features. Method: The proposal is analyzed by means of a case study, including a real-life project, in order to obtain relevant conclusions. Results: The results achieved after using the framework in a development project are presented, including interesting results on project planning and estimation, as well as on team productivity throughout the project. Conclusion: It is concluded that the framework can be useful in order to better manage Web-based projects, through a continuous value-based estimation and management process.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

Interview Study on the Agile Development of Mechatronic Systems

In order to be as responsive as possible to changes in the dynamic context of mechatronic system development, companies are increasingly integrating agile approaches into their development processes. They are confronted with the challenges of adapting approaches that originate in software development to the conditions of physical development, without neglecting the experiences gained over many years regarding product and process knowledge. In addition, agile development approaches must be integrated into existing processes through a systematic implementation strategy. In order to gain an initial understanding of the current situation in mechatronic companies with regard to agile development approaches, an interview study was conducted with 18 participants from real development practice. This could show that the companies in mechatronic system development are currently at the beginning of agile transformation and need approaches that are modelled on the basis of real development projects and are best possible tailored to the needs of these companies through a clear technical orientation. The findings gained are not universally valid, but represent a basis for further research work

Oral Communication in Genre Theory and Software Development Workplaces

My dissertation defines how software developers have abandoned traditional documentation practices for other kinds of media that work better in their workplace practices. Ultimately, even though other media like white boards, sticky notes, and “oral communication” are vastly different than traditional, written software documentation, they match the fast paced, decision-making situations of contemporary developer communities. I focus particularly on oral communication because it is the most unacceptable means to “document,” according to traditional standards. I use North American Genre Theory to describe those decision-making situations contemporary developers and note how the theory does not account for all the documentation I expect to find. Via several projects and interviews I confirm that oral communication is a new means of “documentation” and reconciles North American Genre Theory

Doctor of Philosophy

dissertationManual annotation of clinical texts is often used as a method of generating reference standards that provide data for training and evaluation of Natural Language Processing (NLP) systems. Manually annotating clinical texts is time consuming, expensive, and requires considerable cognitive effort on the part of human reviewers. Furthermore, reference standards must be generated in ways that produce consistent and reliable data but must also be valid in order to adequately evaluate the performance of those systems. The amount of labeled data necessary varies depending on the level of analysis, the complexity of the clinical use case, and the methods that will be used to develop automated machine systems for information extraction and classification. Evaluating methods that potentially reduce cost, manual human workload, introduce task efficiencies, and reduce the amount of labeled data necessary to train NLP tools for specific clinical use cases are active areas of research inquiry in the clinical NLP domain. This dissertation integrates a mixed methods approach using methodologies from cognitive science and artificial intelligence with manual annotation of clinical texts. Aim 1 of this dissertation identifies factors that affect manual annotation of clinical texts. These factors are further explored by evaluating approaches that may introduce efficiencies into manual review tasks applied to two different NLP development areas - semantic annotation of clinical concepts and identification of information representing Protected Health Information (PHI) as defined by HIPAA. Both experiments integrate iv different priming mechanisms using noninteractive and machine-assisted methods. The main hypothesis for this research is that integrating pre-annotation or other machineassisted methods within manual annotation workflows will improve efficiency of manual annotation tasks without diminishing the quality of generated reference standards

Web Services-Enhanced Agile Modeling and Integrating Business Processes

In a global business context with continuous changes, the enterprises have to enhance their operational efficiency, to react more quickly, to ensure the flexibility of their business processes, and to build new collaboration pathways with external partners. To achieve this goal, they must use e-business methods, mechanisms and techniques while capitalizing on the potential of new information and communication technologies. In this context, we propose a standards, model and Web services-based approach for modeling and integrating agile enterprise business processes. The purpose is to benefit from Web services characteristics to enhance the processes design and realize their dynamic integration. The choice of focusing on Web services is essentially justified by their broad adoption by enterprises as well as their capability to warranty interoperability between both intra and inter-enterprises systems. Thereby, we propose in this chapter a metamodel for describing business processes, and discuss their dynamic integration by addressing the Web services discovery issue. On the one hand, the proposed metamodel is in line with the W3C Web services standards, namely, WSDL, SAWSDL and WS-Policy. It considers the use of BPMN standard to describe the behavioral aspect of business processes and completes their design using UML diagrams describing their functional, non-functional and semantic aspects. On other hand, our approach for integrating processes is in line with BPEL standard recommended to orchestrate Web services. To realize executable business processes, this approach recommends the use of semantic matching and selection mechanisms in order to produce agile systems.Comment: 26 pages, 9 figures, Book chapte