Search results

Artificial intelligence (AI) is the most progressive commodity among current information system applications. In-house development and sales of beneficial products are difficult for many software development and service companies (SDSCs). SDSCs have some implicit concerns about implementing AI software development due to the complexity of AI technology; they require an evaluation framework to avoid development failure. To fill the void, this study identified the factors influencing SDSCs when developing AI software development.

Based on complex adaptive systems theory, three aspects were developed as the main factors of hierarchy, namely, employees' capabilities, environmental resources and team capabilities. Fuzzy analytic hierarchy process (FAHP) was used to assess the SDSCs' attitude. Based on SDSCs, attitudes toward implementing AI software projects were collected to calculate the hierarchy of factors.

The outcome of FAHP is used as understanding the key factors of SDSCs for selecting an AI software project, toward the improvement of overall project planning. Employees' stress resistance was considered as a priority for the project, although professional AI skills and resources were also important.

This study suggested three variables developed using complex adaptive systems. This study contributes to a better understanding of the critical aspects of developing AI software projects in SDSCs. The study's findings have practical and academic implications for SDSCs and subsequent academic development, broadening the scope of AI software development research.

This study aims to investigate the effects of organizational culture factors on the selection of software process development models and develops a conceptual model for selecting and adopting process development models with an organizational culture approach, using 12 criteria and their sub-criteria defined in Fey and Denison’s model (12 criteria).

The research hypotheses were investigated using statistical analysis, and then the criteria and sub-criteria were selected based on Fey and Denison’s model and the experts’ viewpoints. Afterward, the organizational culture of the selected company was measured using the data from 2016 and 2017, based on Fey and Denison’s questionnaire. Due to the correlation between the criteria, using the decision-making trial and evaluation technique, the correlation between sub-criteria were determined, and by analytical network process method and using Super-Decision software, the process development model was preferred to the 12 common models in information systems development.

Results indicated a significant and positive effect of organizational culture factors (except the core values factor) on the selection of development models. Also, by changing the value of organizational culture, the selected process development model changed either. Sensitivity analysis performed on the sub-criteria implied that by changing and improving some sub-criteria, the organization will be ready and willing to use the agile or risk-based models such as spiral and win-win models. Concerning units where the mentioned indicators were at moderate and low limits, models such as waterfall, V-shaped and incremental worked more appropriately.

While many studies were performed in comparing development models and investigating their strengths and weaknesses, and the impact of organizational culture on the success of information technology projects, literature indicated that the impact of organizational sub-culture prevailing in the selection of development process models has not been investigated. In this study, new factors and indicators were addressed affecting the selection of development models with a focus on organizational culture. Correlation among the factors and indicators was also investigated and, finally, a conceptual model was proposed for proper adoption of the models and methodologies of system development.

Cost-benefit (C/B) analysis helps to determine the economic feasibility of business software investments. Research literature and published practices do not recognize substantial software maintenance costs in C/B analysis. Current analyses emphasize the benefits of an initial investment but do not consider the recurring benefits of each enhancement during the software lifecycle. Such analyses could lead to incorrect investment decisions and lost business opportunities. This article aims to review current research on software lifecycle costs and develop a theoretically sound C/B analysis.

This article reviews current C/B analyses and discusses their shortcomings in treating the significant recurring maintenance costs. It analyzes the findings of various studies on software maintenance and synthesizes these findings to identify the nature of various maintenance costs and their benefits. Based on the synthesis, it theorizes various cost and benefit elements for inclusion in a revised C/B analysis.

This article identifies each recurring maintenance cost relevant to C/B analysis. It also identifies recurring benefits from each enhancement that hitherto have been omitted. Finally, this article discusses how these costs and benefits should be treated in the revised C/Bs analysis.

This is a conceptual paper proposing a new C/B analysis and requires an empirical validation.

This article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.

This article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.

This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.

The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.

Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.

This research aims to investigate the process of value creation, value delivery, and value capture in project-based companies. Most previous research focused on companies that operate regularly and offer manufactured products or services. This research used companies in the field of information technology that developed software to explain how value creation, value delivery, and value capture occurred. A case study with qualitative research was applied to analyze between cases. Empirical findings showed that companies carry out six activities to ensure that value creation, value delivery, and value capture can be realized in the software development process. The six activities were iterative and not a rigid sequence. This research was limited to the software industry, and further research can test the results of this study by using a survey to increase the generalizability theory developed in this study.

The purpose of this study is to conduct a bibliometric analysis to discover the published information on the subject of “Library Automation Software.”

This study is based on bibliometric research to analyze the growth of literature on the subject area “Library Automation Software.” The data were retrieved from the leading database Web of Science to analyze the scholarly publications on the topic during 2001–2022. To analyze the bibliometric data on the subject, the VOSviewer, Biblioshiny and MS Excel software were used.

Results manifest that the topic of “Library Management Systems” has been greatly used by several authors as a title to publish their research work. The USA emerged as the most productive country. The most used keywords to retrieve literature on the topic were “Library Automation,” “Library Management Systems,” “KOHA,” “Integrated Library Systems” and “Open Source Software.”

To the best of the authors’ knowledge, this is the first bibliometric study in Pakistan that has been conducted to measure the productivity of literature at the international level on library automation.

The software development team reviews the testing phase to assess if the reliability growth of software is as per plan and requirement and gives suggestions for improvement. The objective of this study is to determine the optimal review time such that there is enough time to make judgments about changes required before the scheduled release.

Testing utilizes majority of time and resources, assures reliability and plays a critical role in release and warranty decision-making reviews necessary. A very early review during testing may not give useful information for analyzing or improving project performance, and a very late review may delay product delivery and lead to opportunity loss for developers. Therefore, it is assumed that the optimal time for review is in the later stage of testing when the fault removal rate starts to decline. The expression for this time point is determined using the S-curve 2-D software reliability growth model (SRGM).

The methodology has been illustrated using the real-life fault datasets of Tandem computers and radar systems resulting in optimal review time of 14 weeks and 26 months, respectively, which is neither very early in testing nor very near to the scheduled release. The developer can make changes (more resources or postpone release) to expedite the process.

Most of the literature studies focus on determination of optimal testing or release time to achieve considerable reliability within the budget, but in this study, the authors determine the optimal review time during testing using SRGM to ensure the considerable reliability at release.

The purpose of this study is to examine the state of the literature on knowledge sharing in open source software (OSS) development communities by examining the existing research and identifying the knowledge gaps and opportunities that can inform areas for future research.

A systematic literature review was conducted of literature published between January 2011 and February 2023. A total of 24 papers were identified and reviewed.

The findings reveal that the literature on knowledge sharing in OSS development communities from developing countries are limited. Additionally, there exists a limited focus on the development of frameworks to support knowledge sharing in OSS communities. The transient nature of OSS development contributors’ results in knowledge loss; thus, knowledge retention needs further investigation.

This study only included papers whose titles, keywords or abstracts included the search keywords “knowledge sharing” and “Open Source Software”. While the keywords were carefully applied, when applying the search, it cannot be ruled that some relevant studies might have been missed. The study was also limited to conferences and journal papers published in English. Despite the limitations, the study provides a systematic review of knowledge sharing in OSS communities and presents findings that can be useful to researchers and practitioners interested in this area.

The study provides a systematic literature review of published papers and identifies themes and future research areas on knowledge sharing in OSS communities. Additionally, this review offers insights into future research avenues for theory, content and context on knowledge sharing in OSS development communities.

This study aims to examine how three types of information technology (IT) capability (supplier technological capability, customer technology-sensing capability and relatedness of IT infrastructure) facilitate knowledge acquisition by the customer when the supplier is dominant in the supplier-customer relationship.

The unit of analysis was project. The authors designed two different questionnaires that were responded by the project manager of an enterprise resource planning (ERP) software supplier and the contact person of the customer organization in the same project, respectively. The two questionnaires were matched by means of project name. The final sample included a total of 136 projects. The authors used ordinary least squares to test the research hypotheses.

The authors found that supplier power advantage negatively influenced knowledge acquisition by the customer. The three types of IT capability did not have direct impacts on knowledge acquisition. The moderating effect of customer technology-sensing capability was not significant either. However, supplier technological capability and relatedness of IT infrastructure attenuated the negative effect of supplier power advantage on knowledge acquisition, indicating that both factors promoted knowledge acquisition.

Knowledge acquisition is important for the success of software implementation in the supplier-customer relationship. There is limited evidence in the literature on how to apply externally oriented IT capability to enhance knowledge management, improve knowledge acquisition and manage the business relationship that is typically dominated by the software supplier. The authors provide evidence to examine related issues.