The Experts below are selected from a list of 824109 Experts worldwide ranked by ideXlab platform
Christof Ebert - One of the best experts on this subject based on the ideXlab platform.
-
lean Software Development
IEEE Software, 2012Co-Authors: Christof Ebert, Pekka AbrahamssonAbstract:This special issue addresses lean Software Development. What principles deliver value, and how are they introduced to best manage change?
-
Lean Software Development
IEEE Software, 2012Co-Authors: Christof Ebert, Pekka Abrahamsson, Nilay OzaAbstract:Lean Software Development is the application of the principles of the Toyota product Development system to Software Development. Toyota has been extremely successful developing complex new vehicles, which include a vast amount of embedded Software, in a very short time and always on time. This tutorial examines the underlying engineering principles Toyota uses to develop vehicles and shows how they can be applied to Software Development. When correctly applied, lean Software Development results in high quality Software that is developed quickly and at the lowest possible cost. Moreover, the success of many of the practices of Agile Software Development can be explained by understanding the principles of Lean Software Development.
-
global Software Development for the practitioner
International Conference on Software Engineering, 2006Co-Authors: Philippe Kruchten, Yvonne Hsieh, Eve Macgregor, Deependra Moitra, Wolfgang Strigel, Christof EbertAbstract:This International Workshop on Global Software Development for the Practitioner (GSD2006) was held in conjunction with the 28th International Conference on Software Engineering (ICSE 2006) on May 23rd, 2006 in Shanghai, China. The workshop was motivated by the industry trend towards developing Software in globally distributed settings: geographically distributed teams, or outsourcing parts of the Software Development to other organizations in other parts of the world. Topics presented and discussed in the workshop focused on grounded, practical strategies and techniques that address the geographic, temporal, organizational, and cultural boundaries inherent in global Software projects.
Bernhard Rumpe - One of the best experts on this subject based on the ideXlab platform.
-
assumptions underlying agile Software Development processes
arXiv: Software Engineering, 2014Co-Authors: Daniel Turk, Bernhard RumpeAbstract:Agile processes focus on facilitating early and fast production of working code, and are based on Software Development process models that support iterative, incremental Development of Software. Although agile methods have existed for a number of years now, answers to questions concerning the suitability of agile processes to particular Software Development environments are still often based on anecdotal accounts of experiences. An appreciation of the (often unstated) assumptions underlying agile processes can lead to a better understanding of the applicability of agile processes to particular situations. Agile processes are less likely to be applicable in situations in which core assumptions do not hold. This paper examines the principles and advocated practices of agile processes to identify underlying assumptions. The paper also identifies limitations that may arise from these assumptions and outlines how the limitations can be addresses by incorporating other Software Development techniques and practices into agile Development environments.
-
Assumptions Underlying Agile Software-Development Processes
Journal of Database Management, 2005Co-Authors: Daniel Turk, Bernhard RumpeAbstract:Agile processes focus on the early facilitation and fast production of working code, and are based on Software-Development process models that support iterative, incremental Development of Software. Although agile methods have existed for a number of years now, answers to questions concerning the suitability of agile processes to particular Software-Development environments are still often based on anecdotal accounts of experiences. An appreciation of the (often unstated) assumptions underlying agile processes can lead to a better understanding of the applicability of agile processes to particular situations. Agile processes are less likely to be applicable in situations in which core assumptions do not hold. This article examines the principles and advocated practices of agile processes to identify underlying assumptions. It also identifies limitations that may arise from these assumptions and outlines how the limitations can be addressed by incorporating other Software-Development techniques and practices into agile Development environments.
Oisin Cawley - One of the best experts on this subject based on the ideXlab platform.
-
a conceptual framework for lean regulated Software Development
International Conference on Software and System Process, 2015Co-Authors: Oisin Cawley, Ita Richardson, Xiaofeng Wang, Marco KuhrmannAbstract:A growing number of companies are discovering that their Software Development processes must be in compliance with some form of regulation. This is particularly so when it comes to safety-critical or business-critical systems such as Automotive Software, Robotics, Medical Devices or Finan- cial Management systems. These regulations aect the soft- ware Development process itself in various forms. Further- more, much attention is being given to ways of improving the eciency of businesses, for example, by adopting lean principles. This raises the question for how to adopt lean principles for Software Development within a regulated envi- ronment? This poster presents the results of our empirical research into lean and regulated Software Development. Built from a combination of data sources, we have developed a conceptual framework comprising ve primary components. In addition the relationships they have with both the central focus of the framework (the situated Software Development practices) and with each other are indicated.
-
leagile Software Development an experience report analysis of the application of lean approaches in agile Software Development
Journal of Systems and Software, 2012Co-Authors: Kieran Conboy, Oisin CawleyAbstract:In recent years there has been a noticeable shift in attention from those who use agile Software Development toward lean Software Development, often labelled as a shift ''from agile to lean''. However, the reality may not be as simple or linear as this label implies. To provide a better understanding of lean Software Development approaches and how they are applied in agile Software Development, we have examined 30 experience reports published in past agile Software conferences in which experiences of applying lean approaches in agile Software Development were reported. The analysis identified six types of lean application. The results of our study show that lean can be applied in agile processes in different manners for different purposes. Lean concepts, principles and practices are most often used for continuous agile process improvement, with the most recent introduction being the kanban approach, introducing a continuous, flow-based substitute to time-boxed agile processes.
Ville Leppanen - One of the best experts on this subject based on the ideXlab platform.
-
security in agile Software Development a practitioner survey
Information & Software Technology, 2021Co-Authors: Kalle Rindell, Jukka Ruohonen, Johannes Holvitie, Sami Hyrynsalmi, Ville LeppanenAbstract:Abstract Context: Software security engineering provides the means to define, implement and verify security in Software products. Software security engineering is performed by following a Software security Development life cycle model or a security capability maturity model. However, agile Software Development methods and processes, dominant in the Software industry, are viewed to be in conflict with these security practices and the security requirements. Objective: Empirically verify the use and impact of Software security engineering activities in the context of agile Software Development, as practiced by Software developer professionals. Method: A survey ( N = 61 ) was performed among Software practitioners in Finland regarding their use of 40 common security engineering practices and their perceived security impact, in conjunction with the use of 16 agile Software Development items and activities. Results: The use of agile items and activities had a measurable effect on the selection of security engineering practices. Perceived impact of the security practices was lower than the rate of use would imply: This was taken to indicate a selection bias, caused by e.g. developers’ awareness of only certain security engineering practices, or by difficulties in applying the security engineering practices into an iterative Software Development workflow. Security practices deemed to have most impact were proactive and took place in the early phases of Software Development. Conclusion: Systematic use of agile practices conformed, and was observed to take place in conjunction with the use of security practices. Security activities were most common in the requirement and implementation phases. In general, the activities taking place early in the life cycle were also considered most impactful. A discrepancy between the level of use and the perceived security impact of many security activities was observed. This prompts research and methodological Development for better integration of security engineering activities into Software Development processes, methods, and tools.
Diane Kelly - One of the best experts on this subject based on the ideXlab platform.
-
scientific Software Development viewed as knowledge acquisition
Journal of Systems and Software, 2015Co-Authors: Diane KellyAbstract:Why scientists in risk-averse application domains are not "end-user programmers".Characteristics of scientists who develop Software in risk-averse domains.Presentation of knowledge acquisition Software Development model.Why traditional Development methodologies hamper Development of scientific Software.Observations of how scientists develop Software outside methods. This paper presents a model of Software Development based on knowledge acquisition. The model was formulated from 10 years of studies of scientific Software and scientists who develop Software as part of their science. The model is used to examine assumptions behind Software Development models commonly described in Software engineering literature, and compare these with the observed way scientists develop Software. This paper also explains why a particular type of scientist, one who works in a highly risk-averse application domain, does not conform to the common characterization of all scientists as "end-user programmers". We offer observations of how this type of scientist develops trustworthy Software. We observe that these scientists work outside the ubiquitous method-based Software Development paradigms, using instead a knowledge acquisition-based approach to Software Development. We also observe that the scientist is an integral part of the Software system and cannot be excluded from its consideration. We suggest that use of the knowledge acquisition Software Development model requires research into how to support acquisition of knowledge while developing Software, how to satisfy oversight in regulated application domains, and how to successfully manage a scientific group using this model.
