Software Development Management Research Articles

Programmer Selection Using Modified Fuzzy Mamdani Method

Selection of candidate of the programmer is a complex and tiring process. Software development manager must work hard to guarantee that only qualified candidates will be selected. This study the parameters needed by the programmer are proper and adequate knowledge, skills, attitudes, and productivity. Knowledge, skills, attitudes, and productivity are the four competencies that every programmer must-have. The four components above are very important in developing an IT company. This study proposes a classification model of programmer selection based on certain criteria, parameters, and attributes. This study modifies the Fuzzy Mamdani Method as the approach for determining the feasibility of the programmer. The proposed model has satisfied result of percent of accuracy with 75.57% level. The result indicates that the proposed model has produced a sufficient solution to be used in the real situation for selecting the feasible programmer.

Remote navigation signal management and monitoring software development based on data collected from AIS and ENC

The Navigation signal management and monitoring requires a lot of information and needs continuous operation in order to assure the navigation safety, therefore, the signal need to monitoring and managing. To monitoring and managing the navigation signal and navigation control, there are several methods applied such as directly operation by workers, by sensor or by remote control through AIS. Based on the data collected from AIS and ENC, the research group has developed the remote navigation signal managing and monitoring software through the internet. This paper describes the process of the software design and development.

Managing Software Development Projects for Success: Aligning Plan- and Agility-Based Approaches to Project Complexity and Project Dynamism

In general, project complexity and project dynamism are recognized as potent characteristics that influence, usually in a negative way, the outcome of software development projects. However, with respect to the two dominant paradigms for managing software development projects (i.e., plan-based project approach and agility-based project approach), there is less agreement as to which one is better. Emerging research suggests that the preeminence of one approach over another is a matter of fit between the project management approach and the project context, including its complexity and dynamism. We contribute to this line of research by studying the moderating influence of the two project management approaches on the relationship between project complexity and project dynamism on project outcomes. Our analysis of data gathered from a survey of software development professionals shows that managing dynamism is critical for realizing project success, and an agility-based project approach is best suited for mitigating dynamism’s negative effects on project success.

ELIXIR Europe on the Road to Sustainable Research Software

ELIXIR (ELIXIR Europe 2019a) is an intergovernmental organization that brings together life science resources across Europe. These resources include databases, software tools, training materials, cloud storage, and supercomputers. One of the goals of ELIXIR is to coordinate these resources so that they form a single infrastructure. This infrastructure makes it easier for scientists to find and share data, exchange expertise, and agree on best practices. ELIXIR's activities are divided into the following five areas: Data, Tools, Interoperability, Compute and Training, each known as “platform”. The ELIXIR Tools Platform works to improve the discovery, quality and sustainability of software resources. The Software Development Best Practices task of the Tools Platform aims to raise the quality and sustainability of research software by producing, adopting, and promoting information standards and best practices relevant to the software development life cycle. We have published four (4OSS) simple recommendations to encourage best practices in research software (Jiménez et al. 2017) and the Top 10 metrics for recommended life science software practices (Artaza et al. 2016). The 4OSS simple recommendations are as follows: Develop a publicly accessible open source code from day one. Make software easy to discover by providing software metadata via a popular community registry. Adopt a license and comply with the licenses of third-party dependencies. Have clear and transparent contribution, governance and communication processes. Develop a publicly accessible open source code from day one. Make software easy to discover by providing software metadata via a popular community registry. Adopt a license and comply with the licenses of third-party dependencies. Have clear and transparent contribution, governance and communication processes. In order to encourage researchers and developers to adopt the 4OSS recommendations and build FAIR (Findable, Accessible, Interoperable and Reusable) software, the best practices group, in partnership with the ELIXIR Training platform, The Carpentries (Carpentries 2019, ELIXIR Europe 2019b), and other communities, are creating a collection of training materials (Kuzak et al. 2019). The next step is to adopt, promote, and recognise these information standards and best practices. The group will address this by (i) developing comprehensive guidelines for software curation, (ii) through training researchers and developers towards the adoption of software best practices and (iii) improvement of the usability of Tools Platform products. Additionally, a direct outcome of this task will be a software management plan template, connected to a concise description of the guidelines for open research software; and production of a white paper for the software development management plan for ELIXIR, which can be consequently used to produce training materials. We will work with the newly formed ReSA (Research Software Alliance) to facilitate the adoption of this plan for the broader community.

Managing to release early, often and on time in the OpenStack software ecosystem

The dictum of “Release early, release often.” by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. However, there are very few empirical studies addressing release management in this context. It is already known that most open source software communities adopt either a feature-based or time-based release strategy. Both have their own advantages and disadvantages that are also context-specific. Recent research reports that many prominent open source software projects have overcome a number of recurrent problems by moving from feature-based to time-based release strategies. In this longitudinal case study, we address the release management practices of OpenStack, a large scale open source project developing cloud computing technologies. We discuss how the release management practices of OpenStack have evolved in terms of chosen strategy and timeframes with close attention to processes and tools. We discuss the number of practical and managerial issues related to release management within the context of large and complex software ecosystems. Our findings also reveal that multiple release management cycles can co-exist in large and complex software ecosystems such as OpenStack.

Computational Reproducibility: The Elephant in the Room

Examines the concept of computational reproducibility. Reports on the development of software programming and addresses the challenges of managing software development and developing reliability software update and maintenance procedures.

A model of requirements engineering in software startups

Abstract Context Over the past 20 years, software startups have created many products that have changed human life. Since these companies are creating brand-new products or services, requirements are difficult to gather and highly volatile. Although scientific interest in software development in this context has increased, the studies on requirements engineering in software startups are still scarce and mostly focused on elicitation activities. Objective This study overcomes this gap by answering how requirements engineering practices are performed in this context. Method We conducted a grounded theory study based on 17 interviews with software startups practitioners. Results We constructed a model to show that software startups do not follow a single set of practices but, instead, build a custom process, changed throughout the development of the company, combining different practices according to a set of influences (Founders, Software Development Manager, Developers, Market, Business Model and Startup Ecosystem). Conclusion Our findings show that requirements engineering activities in software startups are similar to those in agile teams, but some steps vary as a consequence of the lack of an accessible customer.

Effectual application development on digital platforms

The development of novel software applications on digital platforms differs radically from traditional software development. In this position paper, we posit that software development managers and teams face unique challenges in platform environments and require new development approaches to be successful. While traditional software development approaches have focused on achieving application-market match, platform-based applications must also achieve application-platform match, application-market match, value propositions exceeding platform’s core value propositions, and novelty. We argue that these desired properties support a new vision of the software development team as entrepreneurs. To support this positioning insight, we discuss the limitations of existing software development approaches and introduce an innovative approach for application development on digital platforms that is grounded in the theory of effectuation from the field of entrepreneurship. We investigate an existing application development environment (Apache Cordova) on digital platforms to see if the concepts of effectuation are present. The preliminary findings provide support for the promise of effectual development methods. We conclude with a call for innovative effectual methods of software development on digital platforms and an accompanying research agenda.

How Agile Development and Its Tools Support Digital Transformation

Digital transformation is the enabler for new reform of businesses, socialites and governments. It is also the platform to the 2030 Vision in Saudi Arabia and in many other countries. Agile Manifesto succeeded to manage software development in a rapid and reliable fashion. Furthermore, incremental delivery of software release ensure that software audiences are engaged while delivering the product, their comments are considered in every function and any changes in requirements are based on imperial use of the software. This ensure the delivery of functionalities matching customer demands as well as reduce project failure risk. For this reason, Agility has been adopted in most software companies as a guaranteed and easy way to implement the digital solutions for their companies. This paper examines the characteristics of agile frameworks, such as Scrum and XP, and Agile tools, such as Jira, Agilo, and others, that facilitate digital transformation. Then compare productivity and efficacy of agile frameworks with traditional SDLC methods. The paper is concluded with the features of agile framework that enable digital transformation such as incremental development, flexible requirements and customer engagement.

IT Crisisology: The New Discipline for Managing Software Development in Crisis

This paper discusses crises in software product development. It defines a development crisis and presents the new discipline of IT Crisisology, which systematically studies and addresses crises in software production. Essential ingredients of this IT Crisisology discipline include models, methods, tools, patterns and practices. The IT Crisisology framework developed addresses technology, business and human factors; for each kind of factors, it uses a dedicated set of the above-mentioned ingredients. These include tradeoff optimization, agility matrix, models for knowledge transfer and data lifecycle, to name a few. For enterprise scale development, these ingredients are further enhanced and improved. In case of systematic application, the suggested IT Crisisology framework allows for better disciplined, predictable, and manageable software product development, even in the event of a crisis.

Tailoring Agile-Based Software Development Processes

Software development process tailoring is a standard and regular practice of software development companies. Without realizing it as a regular and well-defined standard approach, companies perform it on an ad-hoc basis. Due to which, process tailoring could not be developed into a formal process and approach to managing software development, processes and projects. Software development process paradigm shift from conventional software development approaches to the agile methodologies left many companies struggling with the reusability of the existing processes and defining new processes from scratch. Limited work on process tailoring and lack of a formal approach, particularly for overwhelmingly used agile methodologies, affected the acknowledgment of this process. Addressing this limitation, present research work formulates a process tailoring framework to tailor agile-based software development processes. The proposed framework recommends tailoring three key processes of agile methodologies based on the project state considering the client’s perspective and requirements. The existing literature have been reviewed to develop a theoretical framework which is verified and validated through structured interviews and case study of real projects. The framework provides a formal and a structured approach to tailor agile-based processes and methodologies.

Формалізація процесу управління ризиками розроблення програмного забезпечення

Розроблено підхід до формалізації процесу управляння ризиками розроблення програмного забезпечення (ПЗ), який дає змогу ідентифікувати та оцінити несприятливі ситуацій під час реалізації етапів програмного проекту, а також уможливлює розроблення стратегій і тактик їх передбачення, сприйняття та подолання негативних наслідків від їх прояву. З'ясовано, що управління ризиками розроблення ПЗ потрібно розглядати як процес, який дає змогу визначити особливості такого управління, основні категорії наявних ризиків, ризик-орієнтовний підхід до управління ними. Уточнено підходи до ідентифікації ризиків розроблення ПЗ, їхнього ґрунтовного аналізу, планування та моніторингу, що дало змогу поміняти модель діяльності проектного менеджменту загалом і змінити модель поведінки керівника проекту зокрема на різних етапах реалізації програмного проекту. Удосконалено методику визначення можливих джерел появи ризиків розроблення ПЗ й ідентифікації потенційних ризикових подій, сформовано структуровану множину наявних ризиків реалізації програмних проектів і розроблено їх формалізовані моделі для проведення відповідних розрахунків. Розроблено методику визначення ймовірностей настання потенційних ризикових подій у відповідних їх множинах, запропоновано підхід до розподілу вартості реалізації програмного проекту за цими множинами загалом і потенційними ризиковими подіями зокрема, визначено частки та величини можливих збитків від настання ризикових подій, встановлено пріоритети їх пом'якшення та ранжування. Уточнено заходи із запобігання чи знешкодження ризиків розроблення ПЗ, удосконалено методику визначення ймовірності зменшення або усунення різних ризикових подій, визначено правила і політику реалізації програмного проекту, розроблено їх формалізовані моделі.

Regularized Fuzzy Neural Networks to Aid Effort Forecasting in the Construction and Software Development

Predicting the time to build software is a very complex task for software engineering managers. There are complex factors that can directly interfere with the productivity of the development team. Factors directly related to the complexity of the system to be developed drastically change the time necessary for the completion of the works with the software factories. This work proposes the use of a hybrid system based on artificial neural networks and fuzzy systems to assist in the construction of an expert system based on rules to support in the prediction of hours destined to the development of software according to the complexity of the elements present in the same. The set of fuzzy rules obtained by the system helps the management and control of software development by providing a base of interpretable estimates based on fuzzy rules. The model was submitted to tests on a real database, and its results were promissory in the construction of an aid mechanism in the predictability of the software construction.

METHODS OF SELECTING ACCEPTABLE STRATEGIES OF SOFTWARE DEVELOPMENT

Currently, software is used in many areas of human activity. But the developers of software systems often have problems that leads to exceeding the time and budget of development, as well as reduces the quality and security of software. The paper proposes a methodology developed by the authors, which allows you to standardize the process of creating software. The proposed approach greatly facilitates the organization of the process of collective development and management of software development, improves the quality of the developed software, reduces the risks of the developer and the customer and also reduces the time spent on the creation of software and the cost of its development. The developed technique fully standardizes the software development process, from the moment of creation of specification and ending with the introduction and support of the software product.

Evaluation of a process for architectural assumption management in software development

• An architectural assumption management process with guidelines is developed. • Two case studies were conducted to validate the process. • The process can help to make architectural assumptions explicit. • The process can help to identify and reduce invalid architectural assumptions. Architectural assumption management is critical to the success of software development projects. In this paper, we propose an Architectural Assumption Management (AAM) process, comprised of four AAM activities: Architectural Assumption Making, Description, Evaluation, and Maintenance. Evaluating the AAM process in architectural assumption management, regarding the ease of understanding and the effort of conducting the AAM process, as well as the effectiveness of using the AAM process to make architectural assumptions explicit and to identify and reduce invalid architectural assumptions. An explanatory study with 88 first-year master students in software engineering, and an exploratory study with five practitioners from five companies. (1) the ease of understanding the AAM process is moderate for first-year master students but easy for practitioners; (2) the effort of conducting the AAM process is moderate for first-year master students; (3) Making and Evaluation took the students more time than Description and Maintenance; (4) the practitioners considered Evaluation as the most time consuming activity; (5) the AAM process can help to make architectural assumptions explicit and to identify and reduce invalid architectural assumptions in projects. The majority of the students and practitioners agreed that Architectural Assumption Evaluation is the most helpful activity for all these three aspects. For other activities, there are different opinions about their helpfulness; and (6) there are various factors identified that can impact the aforementioned results. Being aware of and properly adjusting these factors can facilitate the application of the AAM process in projects. The AAM process aims at systematically managing architectural assumptions in software development. The results of the case studies provide preliminary empirical evidence for the evaluation of the AAM process.

Research Process on Software Development Model

Software development model is the form of the organization and management of software development which affects the quality of software development directly, and it is one of the most important research contents of software engineering too. Firstly, we analyze and summarize a series of software development models for total thirteen types which are applied in software development generally, and survey the characteristics of each model. Secondly, some of the improved software development models and their applications according to certain application fields are introduced briefly. Finally, as the future research work, both software development based on 4GT (The Fourth Generation Technology) and software intelligent development based on data-driven in big data era are prospected in this paper.

Agile Movement from IT Industry to Non-IT Industry: A Review and Analysis

Software engineering is comparatively a new addition in the vocabulary of traditional engineering discipline. Being a late joiner, software engineering obtained many of its process foundation from traditional engineering domains. But the ever-changing business needs and the growing complexity that are required to be addressed in a software application, have kept software engineers on their toes to continuously improve the development process to meet and to manage the challenges in it. Agile project management has been the most significant development in IT industry to manage software development process that could deliver quality software product at an extremely high speed compared to any of the predecessor methods. The key abstraction of all the flavors of agile methods is adaptability towards change. This adaptability is achieved by the use of quality practices and practitioners in a closely integrated working environment that also involves the customers in the development process more than ever before. IT industry has acknowledged the significant success of the agile process and has been a buzz-word for a decade in the IT industry. The paper is built upon a comparative study of the application of Agile project management in both IT and non-IT industries. It further discusses the adaptability of agile methods and its potential to benefit the Non-IT industry in managing the quality of deliverables while maintaining high delivery speed. The discussion extends its boundaries to cover the reason for less acceptance of Agile process in non-IT industry and put forth an argument against the suitability of some of the success-factors in the case of non-IT industries, while they enabled a high acceptance of the Agile process in IT-industry.

Computer Network Management Software

The development of network management software is gradually mature with the development of network. The software is diff erent to distinguish due to the wide range of network management software in the current market. This paper aims to help readers to identify the suitable network management software for their daily use. In this article, we gather information from the investigation of network management system used by enterprises and from network inquiries. The article discusses some issues related to the network management software including the commonly used software, the application of the software, the use of the software base on diff erent users, the characteristics of diff erent software, the consideration of specifi c software, as well as development trend.

Comprendiendo la Aplicabilidad de Scrum en el Aula: Herramientas y Ejemplos

Las metodologías ágiles permiten flexibilizar y gestionar el desarrollo de software siendo Scrum un marco que permite el desarrollo y mantenimiento de productos complejos, reduciendo el riesgo durante la realización de un proyecto trabajando de manera colaborativa. Debido a su capacidad para potenciar la autoorganización y cooperación, son cada vez más los profesionales que están explorando cómo aplicar Scrum en la educación. Consecuentemente, el objetivo que persigue el presente artículo es evidenciar los distintos tópicos que se consideran a la hora de trabajar con Scrum, presentando tres ejemplos de aplicación de metodologías ágiles en el aula.

Global sourcing and development: New drivers, models, and impacts

Global sourcing and development: New drivers, models, and impacts