Search results for "Software development"
showing 10 items of 278 documents
Comparison of problem solving tools in lean organizations
2017
As global market competition is getting fiercer, and companies are looking at ways to stay on top, more and more organizations are looking at Lean Manufacturing and lean tools to support them in achieving their goals. Especially within the automotive industry, lean practices are very well received. The speed at which the automotive industry is evolving, especially but not only, in countries like Romania, leads to the need to carefully analyze lean manufacturing concepts, examine them against local production conditions, and to develop and standardize them. One of the most important things to take into consideration here is the application of an adequate problem solving technique to avoid wa…
Chemical separation and MC-ICPMS analysis of U, Th, Pa and Ra isotope ratios of carbonates
2018
Diagenetic alteration of fossil reef corals may have severe effects on the reliability of 230Th/U-ages. The widely applied criteria introduced to test for the reliability of coral 230Th/U-ages are often not sufficient to identify all altered ages. The combination of 230Th/U- with 231Pa/U-dating has been suggested as a promising method to identify altered ages. Furthermore, 226Ra/230Th ratios can provide information about the diagenetic history during the last 10 000 years. Here we present a method to chemically separate U, Th, Pa and Ra from the same aliquot of a carbonate sample. The isotope ratios of our mixed U–Th–Pa–Ra spike are calibrated using a secular equilibrium material treated in…
A framework for intention-driven requirements engineering of innovative software products
2011
Requirements engineering is highly challenging particularly when designing innovative software products. This is so because there are no corresponding products, ultimate needs of actors are difficult to capture, the products may have unforeseeable impacts on the actors’ behavior, and it is hard to find out how value-added and competitive the product actually is. In this paper, we propose a novel framework for intention-driven requirements engineering of innovative software products, which combines technological, social and business viewpoints. We illustrate its use with a short example related to the domain of web mapping services and augmented reality. peerReviewed
Composition of a New Process to Meet Agile Needs Using Method Engineering
2005
The need of developing a new software engineering process to allow the quick prototyping of some robotic applications and meet the requests by some companies for a development process that was shorter than PASSI, gave us the opportunity of applying our studies on the assembling of a new SEP by reusing parts (called method fragments) from other processes. In this paper we discuss our approach that, starting from the method engineering paradigm, adapts and extends it considering specific agent-oriented issues like the multi-agent system meta-model. The final result of our experiment (Agile PASSI) is presented together with the requirements that motivated its structure. © Springer-Verlag Berli…
Components of software development risk: how to address them? A project manager survey
2000
Software risk management can be defined as an attempt to formalize risk oriented correlates of development success into a readily applicable set of principles and practices. By using a survey instrument we investigate this claim further. The investigation addresses the following questions: 1) What are the components of software development risk? 2) how does risk management mitigate risk components, and 3) what environmental factors if any influence them? Using principal component analysis we identify six software risk components: 1) scheduling and timing risks, 2) functionality risks, 3) subcontracting risks, 4) requirements management, 5) resource usage and performance risks, and 6) person…
Use and Identification of Components in Component-Based Software Development Methods
2000
New software systems are needed ever more but to keep up with this trend software developers must learn to create quality software more efficiently. One approach is to (re-)use components as building blocks of the new software. Recently there has been more interest to create component-based software development methods to support this. In this article we first set out requirements for reuse-based software development and then evaluate three component-based methods, namely Catalysis, OMT++, and Unified Process. As a conclusion we argue that evaluated methods produce prefabricated components and that component-based means that software developers can change better components to existing syste…
Developing Software with Domain-Driven Model Reuse
2015
This chapter presents an approach to software development where model-driven development and software reuse facilities are combined in a natural way. It shows how model transformations building a Platform Independent Model (PIM) can be applied directly to the requirements specified in RSL by domain experts. Further development of the software case (PSM, code) is also supported by transformations, which in addition ensure a rich traceability within the software case. Alternatively, the PSM model and code can also be generated directly from requirements in RSL, thus providing fast development of the final code of at least a system prototype in many situations. The reuse support relies on a si…
Attention Shaping and Software Risk—A Categorical Analysis of Four Classical Risk Management Approaches
1998
This paper examines software risk management in a novel way, emphasizing the ways in which managers address software risks through sequential attention shaping and intervention. Software risks are interpreted as incongruent states within a socio-technical model of organizational change that includes task, structure, technology, and actors. Such incongruence can lead to failures in developing or implementing the system and thus to major losses. Based on this model we synthesize a set of software risk factors and risk resolution techniques, which cover the socio-technical components and their interactions. We use the model to analyze how four classical risk management approaches—McFarlan's p…
A root cause analysis method for preventing erratic behavior in software development: PEBA
2019
Measures taken to prevent faults from being introduced or going undetected can secure development of highly reliable software systems. One such measure is analyzing root causes of recurring faults and preventing them from appearing again. Previous methods developed for this purpose have been reactive in nature and relied heavily on fault reporting mechanisms of ogranizations. Additionally, previous efforts lack a defined mechanism for innovating corrective actions. In this study, we strive to complement the existing methods by introducing a proactive and qualitative method that does not rely on fault data. During the course of the research, in addition to an extensive literature search, an …
Future directions in Agile research: Alignment and divergence between research and practice
2017
Editorial article Since the publication of Agile Manifesto in 2001, agile methods have transited from a grass- root initiative among enthusiastic advocates and developers to a mainstream software development approach adopted by both small and large companies worldwide. Meanwhile research on agile methods has grown rapidly and steadily into an established research area, evidenced by dedicated conferences (e.g., XP conference series, research track of previous Agile Conference series), special issues and sections in top Information Systems and Software Engineering journals. However, practitioners and consultants have largely driven the advancement in agile field, and agile research has lagged…