A Vision of DevOps Requirements Change Management Standardization

DevOps (development and operations) aims to shorten the software development process and provide continuous delivery with high software quality. To get the potential gains of DevOps, the software development industry considering global software development (GSD) environment to hire skilled human resources and round-the-clock working hours. However, due to the lack of frequent communication and coordination in GSD, the planning and managing of the requirements change process becomes a challenging task. As in DevOps, requirements are not only shaped by development feedback but also by the operations team. This means requirements affect development, development affects operations and operations affect requirements. However, DevOps in GSD still faces many challenges in terms of requirement management. The purpose of this research project is to develop a DevOps requirement change management and implementation maturity model (DevOps-RCMIMM) that could assist the GSD organizations in modifying and improving their requirement management process in the DevOps process. The development of DevOps-RCMIMM will be based on the existing DevOps and RCM literature, industrial empirical study, and understanding of factors that could impact the implementation of the DevOps requirement change management process in the domain of GSD. This vision study presents the initial results of a systematic literature review that will contribute to the development of maturity levels of the proposed DevOps-RCMIMM

Tinjauan Sistematis Terhadap Persyaratan Manajemen Perubahan dalam Proyek Pengembangan

Changes in software development are unavoidable and can occur due to changing needs of users, stakeholders, and the presence of new technologies. Analysis of the impact of changes greatly affects the cost and time of project work that can affect the success of the project. With the analysis, can help reduce the impact caused. Therefore, proper change management in software development projects is required. In this paper we present a review of the need for change management in software development. The writing of this paper is done to answer the problems that arise based on the discussion of the journals studied. The problems include: 1. what are the causes of change management, 2. What is the impact of change? 3. What methods can be used to cope with change? 4. What tools can be used to cope with change? The method used in writing this review is to draw conclusions based on the discussion obtained from the grouping of journals related to change management and the need for change management sourced from ScienceDirect and IEEE. The results obtained from this review are to answer four questions that arise and draw conclusions about the methods and tools that are often used in large case studies in change management. The method that is often used to support the management of requirements change is Requirements Change Management (RCM). RCM consists of 3 stages (1) Understanding changes (2) Analysis of changes and (3) Finalizing changes to this method can be assisted with web tools. The web is often used to support change management needs because it can be used to manage quantitative and qualitative data. Keywords: Change Management; Software Development, Requirement Change Management (RCM

Role of critical success factors in offshore quality requirement change management using SLR

In software engineering field, requirement change management is a challenging job. Ignoring incoming changes results in customer displeasure. It may also result in late product transportation. Managing requirement changes in poor way is the main cause of product failure. It has more diverse effect in global software outsourcing. In software quality requirement change management, it is necessary to address success factors in order to accomplish the requirements of the customers. In this paper, systematic literature review approach is used for documentation and scrutinization of success factors. Total sixteen success factors were recognized having great impact on quality software requirement change management. Our identified success factors like 'Proper Requirement Change Management', 'Rapid Delivery', 'Quality Software Product, Access to Market', 'Project Management', 'Skills and Methodologies', 'Low Cost/Effort Estimation', 'Clear Plan and Road Map', 'Agile Processes', 'Low Labor Cost', 'User Satisfaction', 'Communication/Close Coordination', 'Proper Scheduling and Time Constraints', 'Frequent Technological Changes', 'Robust Model', 'Geographical juncture/Cultural differences' are the crucial factors that affect software quality requirement change. Company size and different database have been used for the analysis of success factors. The databases/search engine used are Google scholar, Science Direct, IEEE Explore and Springer for the exploration of success factors. Companies are analyzed on the basis of their size such as small, medium and large.Qatar Foundation - grant No. UREP27-020-1-003

An improved requirement change management model for agile software development

Business requirements for software development projects are volatile and continuously need improvement. Hence, popularity of Agile methodology increases as it welcomes requirement changes during the Agile Software Development (ASD). However, existing models merely focus on change of functional requirements that are not adequate to achieve software sustainability and support change requirement processes. Therefore, this study proposes an improved Agile Requirement Change Management (ARCM) Model which provides a better support of non-functional requirement changes in ASD for achieving software sustainability. This study was carried out in four phases. Phase one is a theoretical study that examined the important issues and practices of requirement change in ASD. Then, in phase two, an exploratory study was conducted to investigate current practices of requirement changes in ASD. The study involved 137 software practitioners from Pakistan. While in phase three, the findings from the previous phases were used to construct the ARCM model. The model was constructed by adapting Plan-Do-Check-Act (PDCA) method which consists of four 4 stages. Every stage provides well-defined aims, processes, activities, and practices. Finally, the model was evaluated by using expert review and case study approaches. There were six experts involved to verify the model and two case studies which involved two software companies from Pakistan were carried out to validate the applicability of the proposed model. The study proposes the ARCM model that consists of three main components: sustainability characteristics for handling non-functional requirements, sustainability analysis method for performing impact and risk analysis and assessment mechanism of ARCM using Goal Question Metrics (GQM) method. The evaluation result shown that the ARCM Model gained software practitioners’ satisfaction and able to be executed in a real environment. From the theoretical perspective, this study introduces the ARCM Model that contributed to the field of Agile Requirement Management, as well as the empirical findings that focused on the current issues, challenges and practices of RCM. Moreover, the ARCM model provides a solution for handling the nonfunctional requirements changes in ASD. Consequently, these findings are beneficial to Agile software practitioners and researchers to ensure the software sustainability are fulfilled hence empowers the companies to improve their value delivery

Deep Learning In Software Engineering

Software evolves and therefore requires an evolving field of Software Engineering. The evolution of software can be seen on an individual project level through the software life cycle, as well as on a collective level, as we study the trends and uses of software in the real world. As the needs and requirements of users change, so must software evolve to reflect those changes. This cycle is never ending and has led to continuous and rapid development of software projects. More importantly, it has put a great responsibility on software engineers, causing them to adopt practices and tools that allow them to increase their efficiency. However, these tools suffer the same fate as software designed for the general population; they need to change in order to reflect the user’s needs. Fortunately, the demand for this evolving software has given software engineers a plethora of data and artifacts to analyze. The challenge arises when attempting to identify and apply patterns learned from the vast amount of data. In this dissertation, we explore and develop techniques to take advantage of the vast amount of software data and to aid developers in software development tasks. Specifically, we exploit the tool of deep learning to automatically learn patterns discovered within previous software data and automatically apply those patterns to present day software development. We first set out to investigate the current impact of deep learning in software engineering by performing a systematic literature review of top tier conferences and journals. This review provides guidelines and common pitfalls for researchers to consider when implementing DL (Deep Learning) approaches in SE (Software Engineering). In addition, the review provides a research road map for areas within SE where DL could be applicable. Our next piece of work developed an approach that simultaneously learned different representations of source code for the task of clone detection. We found that the use of multiple representations, such as Identifiers, ASTs, CFGs and bytecode, can lead to the identification of similar code fragments. Through the use of deep learning strategies, we automatically learned these different representations without the requirement of hand-crafted features. Lastly, we designed a novel approach for automating the generation of assert statements through seq2seq learning, with the goal of increasing the efficiency of software testing. Given the test method and the context of the associated focal method, we automatically generated semantically and syntactically correct assert statements for a given, unseen test method. We exemplify that the techniques presented in this dissertation provide a meaningful advancement to the field of software engineering and the automation of software development tasks. We provide analytical evaluations and empirical evidence that substantiate the impact of our findings and usefulness of our approaches toward the software engineering community

Customising software products in distributed software development a model for allocating customisation requirements across organisational boundaries

Requirements engineering plays a vital role in the software development process. While it is difficult to manage those requirements locally, it is even more difficult to communicate those requirements over organisational boundaries and to convey them to multiple distribution customers. This paper discusses the requirements of multiple distribution customers empirically in the context of customised software products. The main purpose is to understand the challenges of communicating and allocating customisation requirements across distributed organisational boundaries. We conducted an empirical survey with 19 practitioners, which confirmed that communicating customisation requirements in a DSD context is a significant challenge. We therefore propose a model for allocating customisation requirements between a local, customer-based agile team and a distributed development team that uses a traditional development approach. Our conjecture is that the model would reduce the challenge of communicating requirements across organisational boundaries, address customers’ requirements and provide a focus for future empirical studies

Introducing Inventiveness into the Patent System: Submission to the Review of the National Innovation System

Because of the potential impact of the patent system on innovation diffusion, particularly on continuous and/or incremental innovation, patent policy should be of central importance to the review of the national innovation system. Substantial empirical evidence shows that most industrial innovations are not induced by the patent system. Even in very large markets, such as the USA, only a minority of patents are likely to be induced by the patent system. To the extent that patents do induce innovations, it is the inventiveness of the innovation which gives rise to possible social benefits (externalities, mainly in the form of knowledge spillovers) which may offset the costs of a patent system and thus give rise to a net economic benefit. On the basis of this evidence about the inducement effect of the patent system, and evidence on the current very low inventiveness standard for patent grant, policy proposals are put forward to re-introduce inventiveness into the patent system, thus making it potentially welfare-enhancing. These proposed changes would also have a major impact in ameliorating the negative impact of the patent system on continuous/incremental innovation