scholarly journals Assumptions Underlying Agile Software-Development Processes

2005 ◽  
Vol 16 (4) ◽  
pp. 62-87 ◽  
Author(s):  
Daniel Turk ◽  
France. Robert ◽  
Bernhard Rumpe
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Processes ◽  
Agile Software

Usability Engineering in Agile Software Development Processes

2016 ◽  
pp. 208-221
Author(s):  
Muhammad Aminu Umar ◽  
Sheidu Salami Tenuche ◽  
Sahabi Ali Yusuf ◽  
Aminu Onimisi Abdulsalami ◽  
Aliyu Muhammad Kufena
Keyword(s):  
Software Development ◽  
User Interaction ◽  
Agile Software Development ◽  
Functional Requirements ◽  
Usability Engineering ◽  
Agile Processes ◽  
Software Product ◽  
Development Processes ◽  
Software Development Methodologies ◽  
Agile Software

As the popularity and acceptance of agile software development methodologies increases, the need to integrate usability engineering in the design and development processes is imperative. While, agile the focus is on technical and functional requirements not on end-user interaction, usability is usually only dealt with on the side. Combining this two in practice will go a long way in development of better product. Since the success and acceptance of software product depends not only on the technologies used but how well it integrates user-oriented methods. Therefore, this chapter puts together works on how usability engineering has been integrated with agile processes.

Fitting Security into Agile Software Development

2018 ◽  
Vol 9 (1) ◽  
pp. 47-70 ◽  
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Security Engineering ◽  
Software Products ◽  
Common Criteria ◽  
Engineering Models ◽  
Development Processes ◽  
Agile Software ◽  
The Cost ◽  
Security Incidents

Security objectives in software development are increasingly convergent with the business objectives, as requirements for privacy and the cost of security incidents call for more dependable software products. The development of secure software is accomplished by augmenting the software development process with specific security engineering activities. Security engineering, in contrast to the iterative and incremental software development processes, is characterized by sequential life cycle models: the security objectives are thus to be achieved by conflicting approaches. In this study, to identify the incompatibilities between the approaches, the security engineering activities from Microsoft SDL, the ISO Common Criteria and OWASP SAMM security engineering models are mapped into common agile software development processes, practices and artifacts.

scholarly journals Applications supporting utilization of agile methods in software development process

2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Methods ◽  
Tabular Form ◽  
Software Development Process ◽  
Internet Applications ◽  
Technical Requirements ◽  
Development Processes ◽  
Agile Software

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

scholarly journals OntoAgile: an ontology for agile software development processes

DYNA ◽  
2019 ◽  
Vol 86 (209) ◽  
pp. 79-90
Author(s):  
Wilson Alfredo Ortega Ordoñez ◽  
César Jesús Pardo Calvache ◽  
Francisco José Pino Correa
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Processes ◽  
Software Processes ◽  
Agile Software

Currently, there is a broad portfolio of agile approaches to software development, however, in many cases their implementation is done informally and without a proper institutionalization of the agile values and principles. Although there are some proposals related to the adoption and assessment of agile approaches, efforts have been made without having a common terminology which has led to confusion and terminological conflict affecting the implementation of these approaches in organizations. This article proposes the ontology called OntoAgile, which aims to suggest a common and consistent terminology that allows sharing the knowledge generated around the implementation of the agile approaches in the software processes in a generic and formal way. Similarly, OntoAgile facilitates the assessment of the agility of the software processes from the identification of the relationships between the elements of the software processes and the agile principles and values. OntoAgile was assessed satisfactorily by three cases of application.

Prototype Design in Agile Product Development Processes for Technical Systems

2019 ◽  
Author(s):  
Michael Riesener ◽  
Christian Doelle ◽  
Sebastian Schloesser ◽  
Guenther Schuh
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Development ◽  
Time To Market ◽  
Industrial Practice ◽  
Development Processes ◽  
Technical Systems ◽  
Agile Software ◽  
Product Specifications

Abstract Agile development processes such as Scrum have been successfully applied in the software industry for many years. Based on experience, industrial practitioners indicate three predominant benefits of agile development processes compared to traditional software development processes. First of all, development results better fit customers’ and other stakeholders’ needs. That is because they are intensively involved in the development process by receiving, applying and assessing functional software increments in a defined cadence throughout the development process. Secondly, agile development processes better cope with unexpected changes in the development process due to the built-in process flexibility. Lastly, development speed has significantly increased in most of the agile software development projects, resulting in a shorter time-to-market. Especially in the context of radical innovations for technical systems, manufacturing companies are striving for approaches to optimize their development processes in a similar direction. Traditional plan-oriented development approaches such as VDI 2221 or Cooper’s Stage-Gate Process turn out to be insufficiently customer oriented, too inflexible and project duration is usually too long to reach an adequate time-to-market. For that reason, a large community in academia and industrial practice is developing and implementing approaches to adapt agile software development practices for the development of technical systems. However, a current study in industrial practice reveals that out of 23 objectives, that are expected when introducing agile development processes to technical systems, the three objectives mentioned above, show the largest negative deviations from expected benefit to realized benefit. Therefore, the overall goal of this research is to address these gaps by developing an explicit methodological approach for an agile development of technical systems. It turns out, that mainly the role of prototyping and the way product specifications are handled during the development process change significantly in the course of introducing agility to development of technical systems. Agile practitioners strive to not necessarily define product specifications comprehensively upfront, as it is postulated in plan-oriented development processes. In contrast, product specifications, which are of major importance to the overall development project, are specified and validated with customers and other stakeholders in early prototypes. Therefore, prototypes are realized in a defined cadence throughout the development process to gradually specify and validate the product. However, the way product specifications are prioritized and selected in the development of technical systems has to differ substantially from the general way Scrum or other existing agile development processes propose. That is because technical systems are characterized by multiple technical interrelations, resulting in informational dependencies for the development process. For that reason, a prioritization along criteria such as customer value, development effort and risk seems too narrow in the context of technical systems. In fact, the prioritization of product specifications has to consider both, the value being generated by their realization as well as the informational dependencies towards other specifications. Furthermore, when designing a prototype, time constraints need to be particularly considered due to lead times in parts delivery and prototype production. Therefore, this paper introduces a methodology to prioritize and select technical design parameters in agile development processes. The methodology can be applied in the cyclical sprint planning that aims at defining the scope of the next prototype to be developed. As outlined above, the major paradigms of value generation, informational dependencies as well as lead-time and effort are crucial when adapting agile for technical systems and are consequently implemented in the methodology. These paradigms are operationalized to explicitly address the mentioned major objectives of agile development processes, which are currently showing are large gap between expected benefit and realized benefit in industrial practice. The methodology is applied to the real development process of an RGB laser light source for digital cinema projectors, which is summarized as a case study in the paper. Insights from this application are equally discussed as the resulting next steps in further developing and aligning the methodology to the needs of industrial practice.

Challenges and Solutions for Addressing Software Security in Agile Software Development

2018 ◽  
Vol 9 (1) ◽  
pp. 1-17
Author(s):  
Ronald Jabangwe ◽  
Kati Kuusinen ◽  
Klaus R Riisom ◽  
Martin S Hubel ◽  
Hasan M Alradhi ◽  
...  
Keyword(s):  
Software Development ◽  
Software Security ◽  
Agile Software Development ◽  
Functional Requirements ◽  
Process Dynamics ◽  
Relevance Assessment ◽  
Security Practices ◽  
Development Context ◽  
Development Processes ◽  
Agile Software

There has been a surge in the number of software security threats and vulnerabilities in recent times. At the same time, expectations towards software and data security are growing. Thus, there is a need to ensure that security-related tasks are effectively integrated in the software development processes. However, integrating security practices with agile software development is not trivial due to, for instance, differences in process dynamics and the concentration on functional vs non-functional requirements. In this article, the authors present a literature review on the challenges and solutions when adopting security in an agile software development context. Their findings suggest that there are ongoing efforts to integrate security-practices in agile methods, but more research is needed to make the processes more optimized and simpler for developers. A rigor and relevance assessment on primary studies highlights a need for improving the manner in which studies on the topic are performed as well as reported.

Sign in / Sign up

Export Citation Format

Share Document