Catalogue Search | MBRL
Search Results Heading
Explore the vast range of titles available.
MBRLSearchResults
-
DisciplineDiscipline
-
Is Peer ReviewedIs Peer Reviewed
-
Reading LevelReading Level
-
Content TypeContent Type
-
YearFrom:-To:
-
More FiltersMore FiltersItem TypeIs Full-Text AvailableSubjectPublisherSourceDonorLanguagePlace of PublicationContributorsLocation
Done
Filters
Reset
54,953
result(s) for
"software process"
Sort by:
Incremental software architecture : a method for saving failing IT implementations
\"This book will depict rare insights into actual failed-to-perform software systems, followed by comprehensive root-cause analyses identifying the reasons for their unsuccessful execution in production. Remedies will be provided that offer strategies to tackle the chief issues. Last, architecture and design best practices will conclude the discussion. The book will assist users to: Mitigate risks of software development projects Increase return on investments (ROI) Provide effective tools to assess technological achievability and viability Introduce software design best practices for enterprise architecture efforts Identify actual software construction value proposition Foster software assets reuse and consolidation Accelerate time-to-market \"-- Provided by publisher.
Software Process Improvement by Managing Situational Method Engineering Knowledge
2024
Organizational processes have been recognized as valuable knowledge assets. Situational Method Engineering (SME) processes are particularly valuable as they are used for engineering other processes: SME processes help construct bespoke Software Development Methodologies (SDMs) for specific software-engineering project situations. Every SDM has a Software Development Process (SDP) at its heart, which specifies the activities that should be performed throughout the project, the products that should be produced, and the people that should be involved. Existing SME methods suffer from certain weaknesses that are rooted in loss of knowledge within their processes; for instance, the method engineers' experience, which is a kind of tacit knowledge, is not properly captured and utilized in these processes. Managing SME process knowledge helps alleviate these weaknesses through reusing the software developers' experience and maintaining the method engineers' knowledge. We propose an evaluation framework that can be used for assessing an SME method's ability to manage process knowledge. We also provide a model that guides the improvement of existing SME methods in their support for Knowledge Management (KM), and also helps engineer new SME methods that provide adequate KM support. We have assessed the applicability of the proposed evaluation framework and improvement model by using them to enhance eight prominent SME methods, and also by applying them to four industrial case studies.
Journal Article
Kanban change leadership : creating a culture of continuous improvement
\"This book provides an understanding of what is necessary to properly understand change management with Kanban as well as how to apply it optimally in the workplace\"-- Provided by publisher.
Understanding the gap between software process practices and actual practice in very small companies
2016
This paper reports on a grounded theory to study into software developers’ use of software development processes in actual practice in the specific context of very small companies. This study was conducted in three very small software product companies located in Ecuador. The data collection was based on semi-structured qualitative interviews with software project managers, focus group with software developers and was supplemented by the literature and document studies. We interviewed two types of participants (managers and developers), so as to ensure that we elicited a holistic perspective of how they approached the software development process in actual practice. The goal was to study what practices are actually used and their opinion and attitude toward the potential adopting of an international standard (ISO/IEC 29110) specifically designed for very small companies. With the collected data, we performed an analysis utilizing grounded theory coding techniques, as this methodology promotes the focus on uncovering the real concerns of the participants. This study highlighted three areas of concern: customer, software product and development tasks coordination and tracking. The findings in this study give an insight toward the work products as they relate to software development process practices in very small companies and the important factors that must be considered to assist project success.
Journal Article
The Impact of Design and Code Reviews on Software Quality: An Empirical Study Based on PSP Data
2009
This research investigates the effect of review rate on defect removal effectiveness and the quality of software products, while controlling for a number of potential confounding factors. Two data sets of 371 and 246 programs, respectively, from a personal software process (PSP) approach were analyzed using both regression and mixed models. Review activities in the PSP process are those steps performed by the developer in a traditional inspection process. The results show that the PSP review rate is a significant factor affecting defect removal effectiveness, even after accounting for developer ability and other significant process variables. The recommended review rate of 200 LOC/hour or less was found to be an effective rate for individual reviews, identifying nearly two-thirds of the defects in design reviews and more than half of the defects in code reviews.
Journal Article
A Redesigning Software Procedure in Improved Software Management using Machine Learning
by
Shyamsunder, M
,
Shwetha, S.
,
Nethravathi, R.
in
AI (Artificial Intelligence)
,
Algorithms
,
Change management
2020
SPR is a software engineering process that improves organizational efficiency in responding to quality outcome challenges, change management and productivity improvement, product quality and competitive advantage. To include improvements to the required considerations and agreements of SEM, SPR, implements, inherits and explores the architecture of procedure change. Machine learning is a key part of SPR in software development organizations. The objective of this paper is to integrate automation technology such as ML into the SDLC of software product development and to increase the conceptual focus on its life cycle development and highlight ML methods in SPM, and how to execute ML in SEM methods. ML algorithms for empirical analysis and discussion of the specific performance and reuse of tasks that we have attempted to achieve in SEM. An observed study of software methods involves the control system of self determining software implementation. In the current period, ML gives better validity in few SEM areas. The main aim of this research is the practical as well as systematic study and also literature survey to advance the wanted standard software, between their qualified evaluation of existing procedures and their carry for SQE.
Journal Article
A Readiness Model and Factors Influencing Blockchain Adoption in Malaysia’s Software Sector: A Survey Study
by
AL-Ashmori, Ammar
,
Al-Mekhlafi, Al-Baraa Abdulrahman
,
Thangarasu, Gunasekar
in
Attitudes
,
Banks
,
Behavior
2023
The technology of Blockchain may open up new potential for innovation and distinction. It can enable the software sector to develop more safe and transparent systems that can function in an environment without trust. The adoption rate still needs to be higher despite the potential advantages; the relatively low adoption rate may be attributable to issues such as a lack of awareness, the difficulty of adoption, and ambiguity surrounding legal and regulatory frameworks. Considering technical, organizational, and environmental aspects, this study aims to determine the primary factors impacting the readiness of software firms to adopt Blockchain technology. The research on adopting Blockchain technology in the Malaysian software sector is limited. Using a quantitative method, the researchers used structural equation modeling to analyze 251 survey responses from the Malaysian software sector. In light of the findings, eight hypotheses were considered significant, and one hypothesis was rejected. At the same time, the R2 indicated that all these variables explained 71% of the dependent variable’s variance, which is considered substantial. Overall, it makes it easier for firms in the software sector to use Blockchain technology, which would increase the overall competitiveness of Malaysia’s software sector in the international market.
Journal Article
A knowledge management-driven and DevOps-based method for situational method engineering
by
Dehghani, Razieh
,
Ramsin, Raman
in
Knowledge management
,
Software development
,
Software engineering
2023
Earlier software development processes (SDPs), such as waterfall processes, were mainly focused on process steps and did not address people- and product-related issues. Emergence of Software development methodologies (SDM) has created a new paradigm for developing software systems. A SDM is a special kind of technically engineered framework for organizing SDPs; this framework is expected to specify three main interwoven elements, namely people, products, and process. It has since become evident that it is impossible to provide a general-purpose SDM for developing all the various kinds of software systems, and it has thus become essential to construct the most appropriate methodology for the system development situation in hand, a practice commonly called Situational Method Engineering (SME). The problem with existing SME methods is lack of adequate attention to the role of people who might seek or possess valuable knowledge about the project situation. This knowledge can be tacit information that is hidden in the developer’s mind, or it might be explicitly available. This paper proposes a knowledge management (KM)-driven and DevOps-based SME method as a new integrated multi-view methodological paradigm that satisfies the need for sharing human experience in engineering SDMs. The method has been proposed by reusing general SME practices and complementing them by embedding appropriate KM and DevOps practices to alleviate the weaknesses of previous SME methods. Furthermore, the proposed method has been evaluated through four case studies and also by conducting a criteria-based comparison with eight prominent SME methods.
Journal Article
Software Process Tailoring: An Empirical Investigation
2007
A well-defined software process is critical for success in software projects. Software process tailoring refers to the activity of tuning a standardized process to meet the needs of a specific project. We conducted two case studies that address the research question: How is a software process tailored to suit its context? This study identifies process tailoring as a key mechanism to address the challenges faced by a project and develops a model that describes how a process is tailored to resolve these challenges. The model identifies a set of environmental factors, challenges, project goals, process tailoring strategies, and their influences on each other. Specifically, the findings demonstrate the duality of the software process, showing how the project context (i.e., project goals, environmental factors, and challenges) and tailoring decisions dynamically interact with each other and construct the context in which the project is developed and the process is tailored.
Journal Article
Software process improvement: a systematic mapping study on the state of the art
by
Kuhrmann, Marco
,
Münch, Jürgen
,
Diebold, Philipp
in
Applied research
,
Classification
,
Computer science
2016
Software process improvement (SPI) has been around for decades: frameworks are proposed, success factors are studied, and experiences have been reported. However, the sheer mass of concepts, approaches, and standards published over the years overwhelms practitioners as well as researchers. What is out there? Are there new trends and emerging approaches? What are open issues? Still, we struggle to answer these questions about the current state of SPI and related research. In this article, we present results from an updated systematic mapping study to shed light on the field of SPI, to develop a big picture of the state of the art, and to draw conclusions for future research directions. An analysis of 769 publications draws a big picture of SPI-related research of the past quarter-century. Our study shows a high number of solution proposals, experience reports, and secondary studies, but only few theories and models on SPI in general. In particular, standard SPI models like CMMI and ISO/IEC 15,504 are analyzed, enhanced, and evaluated for applicability in practice, but these standards are also critically discussed, e.g., from the perspective of SPI in small-to-medium-sized companies, which leads to new specialized frameworks. New and specialized frameworks account for the majority of the contributions found (approx. 38%). Furthermore, we find a growing interest in success factors (approx. 16%) to aid companies in conducting SPI and in adapting agile principles and practices for SPI (approx. 10%). Beyond these specific topics, the study results also show an increasing interest into secondary studies with the purpose of aggregating and structuring SPI-related knowledge. Finally, the present study helps directing future research by identifying under-researched topics awaiting further investigation.
Journal Article