Formalization of the prediction and ranking of software development life cycle models

The study of software engineering professional practices includes the use of the formal methodology in a software development. Identifying the appropriate methodology will not only reduce the failure of software but will also help to deliver the software in accordance with the predetermined budget and schedule. In literature, few works have been developed a tool for prediction of the most appropriate methodology for the specific software project. In this paper, a method for selecting an appropriate software development life cycle (SDLC) model based on a ranking manner from the highest to the lowest scoring is presented. The selection and ranking of appropriate SDLC elaborate the related SDLC’s critical factors, these factors are given different weights according to the SDLC, then these weights are used by the proposed mathematical method. The proposed approach has been extensively experimented on a dataset by software practitioners who are working in the software industry. Experimental results show that, the proposed method represents an applicable tool in predicting and ranking suitable SDLC models on various types of projects, such as: life-critical systems, commercial uses systems, and entertainment applications.

Decision-Making Taxonomy of DevOps Success Factors Using Preference Ranking Organization Method of Enrichment Evaluation

Due to multitudes factors like rapid change in technology, customer needs, and business trends, the software organizations are facing pressure to deliver quality software on time. To address this concern, the software industry is continually looking the solution to improve processing timeline. Thus, the Development and Operations (DevOps) has gained a wide popularity in recent era, and several organizations are adopting it, to leverage its perceived benefits. However, companies are facing several problems while executing the DevOps practices. The objective of this work is to identify the DevOps success factors that will help in DevOps process improvement. To accomplish this research firstly, a systematic literature review is conducted to identify the factors having positive influence on DevOps. Secondly, success factors were mapped with DevOps principles, i.e., culture, automation, measurement, and sharing. Thirdly, the identified success factors and their mapping were further verified with industry experts via questionnaire survey. In the last step, the PROMETHEE-II method has been adopted to prioritize and investigate logical relationship of success factors concerning their criticality for DevOps process. This study’s outcomes portray the taxonomy of the success factors, which help the experts design the new strategies that are effective for DevOps process improvement.

Agile Scrum Issues at Large-Scale Distributed Projects

The agile model is a very vast and popular model in use in the software industry currently. It changes the way software is developed. It was introduced in 2001 to overcome deficiencies of software development in a workshop arranged by researchers and practitioners who were involved with the agile concept. They introduced the complete agile manifesto. The agile model has main components that make it more viable for use in well-organized software development. One of these is scrum methodology. The reason for the agile-scrum popularity is its use for small-scale projects, making small teams and allows change requests at any stage of a project from the client. It works for client satisfaction. Instead of so much popularity and distinctive features, agile-scrum also has some limitations when used for large scale projects development that makes it less efficient for development. This article discusses the agile-scrum methodology and its limitations when using for large-scale project organization.

Knowledge Management in University-Software Industry Collaboration

The university-software industry collaboration relationship has been represented a key resource, to the extent that together they can more easily promote technological development that underpins innovation solutions. Through a literature review, this chapter aims to explore the concepts and the facilitator or inhibitor factors associated with the collaboration relationships between university and software industry, taking knowledge management into account. This chapter is organized as follows. In the first section, the authors briefly introduce university, software industry, and knowledge management. The following section, based on the literature reviewed, provides a critical discussion of the university-software industry collaboration relationship, knowledge management in knowledge intensive organizations or community, and knowledge management in collaboration relationship between these two types of industries. Finally, in the rest of the sections, the authors point to future research directions and conclude.

Structuration and Learning in a Software Firm

This case study presents the evolution of a software firm from startup into early internationalization. Building on a structuration theory, the case is framed within a conceptual model that illustrates the way skills and routines co-evolve both at the level of the founding entrepreneur (agency) and of the firm (structure). As such, this article contributes to an emergent structurational view of technology-based entrepreneurship. Such views places emphasis on learning both at the individual and collective level, in terms of software engineering, commercial, managerial and strategic capabilities. In addition, it supports a dynamic perspective of entrepreneurship in the software industry by covering not only the startup phase but also early growth and consolidation of the firm.

The Cultural and Institutional Barrier of Knowledge Exchanges in the Development of Open Source Software

Open source software (OSS) gives developing countries inexpensive or free alternatives to proprietary software. It gives them the opportunity to develop software and software industry without starting from scratch. This chapter discusses the diffusion and development of OSS in Indonesia especially after the government took “Indonesia, Go Open Source” (IGOS) initiative. This initiative united government organizations, communities, R&D institutions, and universities. While the government's concern was to tackle piracy by replacing illegal software with OSS, the others sought to develop their own OSS. However, the openness of their software is only in terms of that they were developed using OSS development tools, while their mode of development remained closed, which was caused by cultural barrier and institutional incompatibility between government's regime of project administration and the governance of OSS development.