Software Engineering Timeline: major areas of interest and multidisciplinary trends

Ingeniería del software. EvolucionSociety today cannot run without software and by extension, without Software Engineering. Since this discipline emerged in 1968, practitioners have learned valuable lessons that have contributed to current practices. Some have become outdated but many are still relevant and widely used. From the personal and incomplete perspective of the authors, this paper not only reviews the major milestones and areas of interest in the Software Engineering timeline helping software engineers to appreciate the state of things, but also tries to give some insights into the trends that this complex engineering will see in the near future

The hidden pitfalls of Kanban in software development

ABSTRACT: Objectives of the Study: The objective of this thesis is to explore the hidden pitfalls of Kanban in software development. The aim is to discover the reasons behind the pitfalls and actions that nourish Kanban's failure. Academic background and methodology: Software development industry has been shifting towards more iterative, responsive and people-oriented development methods, which present the values of lean and agile thinking. Being characterized as the antidote for bureaucracy, the shift towards agile development methodologies has been one of the most significant factors affecting the software industry. Kanban as an agile change management framework has been perceived as the fairy godmother of software development making the reasons behind struggling Kanban projects particularly interesting. Thesis interviews five agile experts in the software development and studies their experiences of unsuccessful Kanban implementations. Emphasis is given to similar experiences and perceptions on how Kanban fails to redeem its value proposition. Findings: The primary finding of the study is that an organization that is unable to change its mindset to support Kanban is a pitfall affecting the whole project, inevitably causing Kanban to fail. This is a challenge that all agile methods have in common. Agile can flourish only when agile values are being appreciated. The secondary finding is that many software teams claiming to be using Kanban have implemented only a shallow imitation of the real method thus creating a superficial implementation, which prevents achieving Kanban induced benefits. Thus, creating a superficial implementation, which prevents achieving Kanban induced benefits. Furthermore, the erroneous human interpretation of what Kanban really is and how to apply it correctly is a key factor contributing to the emerge of the pitfalls. Keywords: Kanban, software development, pitfall, agile, change management, framewor

Towards Solving the Blockchain Trilemma: An Exploration of Zero-Knowledge Proofs

Research on blockchain has found that the technology is no silver bullet compared to traditional data structures due to limitations regarding decentralization, security, and scalability. These limitations are summarized in the blockchain trilemma, which today represents the greatest barrier to blockchain adoption and applicability. To address these limitations, recent advancements by blockchain businesses have focused on a new cryptographic technique called Zero-knowledge proofs . While these primitives have been around for some time and despite their potential significance on blockchains, not much is known in information systems research about them and their potential effects. Therefore, we employ a multivocal literature review to explore this new tool and find that although it has the potential to resolve the trilemma, it currently only solves it in certain dimensions, which necessitates further attention and research

Creating a Software Assembly Line

This thesis describes a technical solution that improved the software development efforts needed to verify and validate a medical device, herein referred to as the “medical device.” The medical device had many software and hardware configurations that had to be developed, integrated, managed, and tested. There were a number of problems with the manual processes that were being used to verify and validate the product, so this project developed a system called the “Software Assembly Line” to continuously build software and automatically test it on multiple hardware configurations. As a result, software quality and predictability were improved, and the number of cycles required for formal verification and validation was reduced. The final project recommendation was to validate the Software Assembly Line according to 21CFR820.75, Process Validation

adobe medicus 2005 4 July-August

https://digitalrepository.unm.edu/adobe-medicus/1031/thumbnail.jp

A graph based process model measurement framework using scheduling theory

Software development processes, as a means of ensuring software quality and productivity, have been widely accepted within the software development community; software process modeling, on the other hand, continues to be a subject of interest in the research community. Even with organizations that have achieved higher SEI maturity levels, processes are by and large described in documents and reinforced as guidelines or laws governing software development activities. The lack of industry-wide adaptation of software process modeling as part of development activities can be attributed to two major reasons: lack of forecast power in the (software) process modeling and lack of integration mechanism for the described process to seamlessly interact with daily development activities. This dissertation describes a research through which a framework has been established where processes can be manipulated, measured, and dynamically modified by interacting with project management techniques and activities in an integrated process modeling environment, thus closing the gap between process modeling and software development. In this research, processes are described using directed graphs, similar to the techniques with CPM. This way, the graphs can be manipulated visually while the properties of the graphs-can be used to check their validity. The partial ordering and the precedence relationship of the tasks in the graphs are similar to the one studied in other researches [Delcambre94] [Mills96]. Measurements of the effectiveness of the processes are added in this research. These measurements provide bases for the judgment when manipulating the graphs to produce or modify a process. Software development can be considered as activities related to three sets: a set of tasks (τ), a set of resources (ρ), and a set of constraints (y). The process, P, is then a function of all the sets interacting with each other: P = {τ, ρ, y). The interactions of these sets can be described in terms of different machine models using scheduling theory. While trying to produce an optimal solution satisfying a set of prescribed conditions using the analytical method would lead to a practically non-feasible formulation, many heuristic algorithms in scheduling theory combined with manual manipulation of the tasks can help to produce a reasonable good process, the effectiveness of which is reflected through a set of measurement criteria, in particular, the make-span, the float, and the bottlenecks. Through an integrated process modeling environment, these measurements can be obtained in real time, thus providing a feedback loop during the process execution. This feedback loop is essential for risk management and control

Human Factors Influencing Contractors' Risk Attitudes: A Case Study of the Malaysian Construction Industry

Malaysia is one of the most rapidly developing countries among developing nations. The construction industry has played a major role in Malaysia’s rapid economic growth. Among the major sectors in Malaysia, the importance of the construction industry is unique regardless of the level of the country’s development. However, the attitude of the construction industry in Malaysia towards managing contractors’ risk attitudes is very weak. The introduction of the Occupational Safety and Health Act in 1994 by the Malaysian government made all industries in Malaysia to identify risks, conduct risk assessment and control risk. In addition, the Malaysian construction industry simultaneously implemented an integrated system to ensure consistency and better performance of projects. To identify the factors influencing contractors' risk attitudes, relevant literature was reviewed, and a questionnaire survey was conducted. This study focused on the G7 contractors operating in the Malaysian construction industry. One hundred and nineteen copies of a structured questionnaire were analysed with a response rate of 85%. Structural equation modelling was utilized to test the hypotheses developed for the study. Results showed that government policies played a moderating role in enhancing the relationship between human-related factors affecting contractors’ risk attitudes in the construction industry