Developing Software-Dependent Artwork: Artist and Software Developers' Collaboration

Design management systems have been developed and researched for traditional product and service industries. For interaction design little research has been performed on design management. The objective of this paper is to describe aspects of and provisions for industrial interaction design that influence approaches to design management within system and software development. We discuss whether there are specific conditions for design management of interaction design within the software and system development industries. The research is based on three short case studies from industrial software development. We identify some of these specific conditions; the difference between a usage and a product perspective, the design tools and practices, and the modularized and distributed processes. These issues point towards challenges facing design management within the software and system development context, as well as the need for interaction design to clarify its position as a strategic resource in software companies. The conclusions point towards the need for continued research on strategic possibilities and alternatives to organize and manage design work in software and system development.

Graph theory has gained considerable popularity in many areas of application due to its versatility, including ease of modeling and visualization. In general, a graph can represent an arbitrary model of real-world objects and the relationships between them, which allows applying any known algorithms to it and subject it to other types of further analysis. The theoretical foundations of graphs are also widely used in the field of operations research. For example, the travelling salesman problem, finding the minimum spanning tree of a weighted graph, finding the shortest path between two vertices etc. The purpose of this work is to analyze the practical applications of graph theory, both in the process of software development and for software development in general, as well as in the subsequent maintenance and support of software systems. In addition to using the theoretical foundations of graphs in other branches of science, graph theory has also found wide application in solving many practical problems in different areas of human life, such as chemistry, sociology, logistics, biology, economics, technology and so on. Similarly, in software development, graph theory has taken its rightful place. Many kinds of problems are solved with its help, both in the process of software engineering and for the development of software engineering itself. The analysis of the graph theory application opportunities for software development and maintenance has shown that at most stages of the software development cycle, graphs are used only for modeling and visualization of various kinds of information, but there is almost no automated algorithmic analysis of the obtained models. This may indicate a promising direction for discovering additional opportunities of graph theory usage in the software development processes.

Chapter 7 - Science and Art in Collaboration—The Mindship Method

A human's words, facial expressions, gestures, tone of voice, and even keyboard force can all be used in conjunction with artificial intelligence technologies to perform emotion intelligence (EI) identification. The development of artificial emotional intelligence has made it possible for people and robots to interact in a manner that is more natural, similar to the way that humans engage with one another. The expansion of the internet of things and wearable technology has a positive impact on the development of emotion detection software in the healthcare sector. This system contributes to society by making use of many forms of technology. There is always going to be a trade-off between price and functionality. The development of software with emotional intelligence relies on the collection of extensive datasets and the development of reliable modelling techniques. This chapter uses case studies, computing, and AI-based research methods to analyze emotional intelligence systems and their effects on human-computer interaction in the healthcare sector.

The increasing popularity of agile software development has significantly changed the way organizations plan, design, and implement software applications. However, considering the complexity involved with software development, the decision to choose an agile approach over the traditional waterfall approach is not straightforward. Organizations should carefully evaluate a variety of factors when choosing a development approach. In this teaching case study, the authors provide a discussion case to facilitate the students’ learning of using agile vs. traditional approaches in software development. This case study is developed based on experiences of multiple real-world software development projects and the literature on software development. It is designed to reflect the complexities students are likely to encounter in actual software development projects. The case can be used in undergraduate or graduate level management information systems courses that cover agile software development approaches. Students can gain an understanding of factors to consider when choosing a development approach, which tailors to the organization, the project environment, and the project team.

Traditional software development organizations have rigid processes that can be difficult to change. One of the most critical challenges is the management processes that can ensure the customer’s desired level of quality and optimize the organization’s resources. Kanban represents one of the most well-known approaches that bring Lean principles, philosophies, and tools into software organizations. This study analyses the leadership behind the Lean methodology, based on which the Kanban software implementation method has been created, by doing a literature review focusing on lean leadership principles that can optimize the software delivery and implementation. Lean practices can be applied in almost any domain like accounting, services industry, product services, and even software development. Two basic concepts stay at the core of the Lean model that can be employed at any organization level. The first focuses on eliminating waste by optimizing processes and systems, and the second focuses on maximized customer value. Consequently, it can be affirmed that Lean is focused on maximizing customer value with a minimum amount of waste. Furthermore, a case study is presented that shows the Kanban implementation at a software development company. The practical case of the Kanban adoption is analyzed, highlighting the link between the leadership principles and the process development flow. Finally, key performance indicators are identified and instituted to guarantee the continuous improvement of the software delivery model. The software development projects driven by the Kanban project management approach reported essential improvements such as waste reduction, team communication, and collaboration enhancement, work in progress diminishment, productivity-boosting, better delivery predictability, and project visibility. Therefore, the type of leadership influences the software development projects’ performance. The findings suggest that Kanban effectively enhances the software development delivery model and team performance.KeywordsLeadershipKanbanLean practicesSoftware developmentSoftware implementationAgile transformation

One of the main goals of Software Engineering is to produce software with quality. But with the increasing use of agile methodologies in software development, it is observed that the existing quality assurance models do not adapt easily to these methods. In this context, the objective of this research is to propose critical factors of success (CFS) and tools for software development and management environment using agile methods, focusing on quality. Thus, initially, a literature review was conducted in SCOPUS and SCIELO bases, identifying 21 CFS, which were grouped into three categories: Individual; Organizational; and Technical / Process. Based on these factors, a questionnaire was applied to specialists in software management and development, reaching the sample of 101 respondents, with the most important CFS belonging to the Personal category, which reinforces the need for investment in this area. After this field research, a case study was done in a public company that uses traditional methods, making it possible to propose a development and management environment of software, adding the best practices, tools and CFS with the purpose of improve the quality of delivery of the final product. It was also observed the applicability of the agile Scrum method, allied to Kanban, taking advantage of the best practices of both, and how much was relevant in the context of the company, demonstrating the importance of agile methods to improve the quality and productivity of the whole team, including customers and sponsors. In addition, the present work generates an CFS base for knowledge of the academic community.

This paper focuses on the systematic mapping of monolithic applicationsto microservices architecture, a popular alternative in the software development industry.The research examines the advantages of microservices and the challenges organizationsencounter during the transition from monolithic systems. A case study of a financialapplication is presented, along with proposed techniques for identifying microserviceswithin monolithic systems using domain-driven development concepts.The study highlights the difficulties and benefits of migrating from monolithic to microservicesarchitecture, offering valuable insights for software architects and developers. Practicalimplications include a technique for identifying microservices on monolithic systemsusing domain-driven concepts and various communication protocols for service interaction.The findings suggest that this proposed technique can enhance work performanceand establish clear models, particularly for complex systems. However, it may have limitedeffectiveness in less complex systems. The paper contributes to the field of softwaredevelopment by providing practical solutions for companies considering a shift tomicroservices architecture and comparing the two architectural styles.

Security has become an important challenge in current software and system development. Most of designers are experts in software development but not experts in security. It is important to guide them to decide how and where to apply security mechanisms in the early phases of software development to reduce time and cost of development. To reach this objective, we propose to apply security expertise as security patterns at software design phase. Our methodology is based on the use of a component metamodel to capture the domain concepts and security patterns to encode solutions to security problem. The expected result is a model as design solution for specific domain. Here, we promote a modeling technique based on UML profiles to facilitate the integration of patterns solutions into model driven engineering approach (MDE). As a proof of concept, we illustrate the methodology to produce an UML profile associated with RBAC security pattern. A case study of GPS system is also provided to demonstrate the application of generated profile.

A critical problem in software development is the monitoring, control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between ‘actual’ and ‘official’ processes: "the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do" (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an indepth understanding of the ‘actual’ processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007). The goal of process mining is to better understand the development processes, to compare constructed process models with the ‘official’ guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the change control board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.

With the case study MetroEngineers, Sarah Langer, Ronny Gey, Diana Karadzhova-Beyer, and Andrea Fried highlight organizational deviance from standards in the software development of a service engineering company for rail vehicles called MetroEngineers. Despite the initial intention to develop software according to European standards, the case study explains the reasons why the software developers deviate from standards nonetheless. First, software development at MetroEngineers is provided for a Chinese market which is hardly regulated through standards. Deviations from standards are therefore hardly sanctioned, but even MetroEngineers itself has not established an adequate internal sanctioning system for standard deviations. Second, MetroEngineers’ software developers lack allocative and authoritative resources for standard enactment and a lively internal discourse on the importance of standard-compliant development involving middle management and the customer. This means that software developers are ambitiously trying to develop in accordance with European standards, but ultimately fail to overcome the various contradictions that arise in standard enactment. This chapter represents one of the two manipulation-oriented types of organizational deviance introduced in the book.

Software development requires substantial financial resources. This study aims to examine the cost estimation for software development. The complexity of the software, its intangibility as a non-physical product, the technology utilized, and human resources can all influence the determination of software development costs. The method used for cost estimation is Function Point Analysis with a case study approach. The researchers conducted a case study on the software development for an employee savings and loan cooperative at XYZ Company. The result of this study is a cost recommendation that can serve as a reference for selecting software development vendors by the cooperative's management.

agile information systems, flexible information systems development, distributed information systems development, global software development, software development, special issue

In this article, we discuss the impact of software developer motivation on projects. Motivation has been reported to be an important determinant of productivity and quality of work in many industries. In this article, we explore specifically how motivation impacts on development work in software engineering. We describe work previously done to suggest that software developers may have a different profile of motivators to other professionals. We present data collected from nine developers working in a software organisation that has been assessed at CMM level 5. We find that the developers working in this high maturity development environment are highly motivated. We also report relationships between motivation and progress in development work and describe the impact of motivating factors on specific aspects of software development. Our main conclusion is that good software developers are proactive, flexible and adaptable, prepared to share knowledge with team and follow good practice, for example, documenting work. Also, and in particular reference to this high maturity company, good software developers are able to resolve complex problems, innovative and eager to try new technology. The biggest motivators to such performance in a high maturity organisation are pay and benefits, recognition and opportunities for achievement. These are closely followed by technically challenging work, job security and senior management support. Cost, time, product quality — in terms of reliability — and user satisfaction are all moderately good indicators of project success. User satisfaction, however, is the best indicator of all four as its importance assumes a temporal significance as a project progresses. Finally, we found that technical competency, interpersonal skills and adherence to good practices impact favourably on software project success. Copyright © 2006 John Wiley & Sons, Ltd.

Coordination of interdependent tasks across geographical, temporal and socio-cultural boundaries has been identified as a critical antecedent to global software development (GSD) team performance. Since GSD teams are increasingly required to achieve software development agility and respond to changing business requirements, conventional plan-driven software development methods become inadequate to manage the cross-boundary dependencies. To cope with this issue, there is an emerging trend of implementing change-driven agile methods in GSD; we call this practice agile GSD. This paper focuses on the formulation of coordination strategies in agile GSD. We argue that Coordination Theory (CT) can serve as a useful lens to develop a deeper understanding of the formulation process. We present a case study in a leading software development company using agile GSD and present preliminary results by applying the lens of CT.