scholarly journals Safety Critical Software Development Methodologies in Avionics

2020 ◽  
Vol 2020 (2) ◽  
pp. 59-71
Author(s):  
Pawel Zakrzewski ◽  
Janusz Narkiewicz ◽  
Darren Brenchley

AbstractThis article summarizes avionics safety-critical software development methodologies and implications of the DO-178C standard from an Agile application perspective. We explain the safety-critical software categorization. It also outlines the main differences and advantages of different approaches to the development process, from Waterfall through the V-model to Iterative and Incremental. Agile principles are explained as well as a Scrum – which is a popular framework in the non-safety-critical software industry. The application of Agile, for safety-critical software considerations, is based on the practical knowledge of the authors, and looks at the potential solution from a DO-178C standard, size of the project, scalability, and organizational culture points of view. Definition of the Agile type of framework, consistent with the certification process and existing standards, has been highlighted as a potential game-changer for the avionics industry.

2012 ◽  
Vol 45 (24) ◽  
pp. 165-170 ◽  
Author(s):  
Mustafa S. Durmuş ◽  
Uğur Yıldırım ◽  
Oytun Eriş ◽  
Mehmet T. Söylemez

Author(s):  
Jhon Alexander Holguín Barrera

Actualmente la industria del software tiene grandes retos para la construcción y mantenimiento del software en términos de calidad, costos y tiempo. Para esto se han generado diversidad de metodologías, marcos de trabajo, normas y modelos que permiten afrontar estos retos, pero es complejo que la aplicación de solo un referente logre cumplir con todo lo requerido, y por lo general se toman elementos de varios modelos o metodologías. El presente estudio contiene la definición de un proceso de desarrollo de software en una PYME a través de la integración de varios de estos marcos de trabajo (Scrum, PSP e ISO 25000) analizados bajo los lineamientos dados por SWEBOK y apoyados por tecnicas como GQM, que permitan dar un aporte positivo en el cumplimiento de estos objetivos.Palabras Claves: ISO25000, Procesos, PSP, Scrum, SWEBOKCurrently, the software industry has big challenges for the construction and maintenance of software in terms of quality, costs and time. For this the industry generated diversity of methodologies, frameworks, standards and models that meet these challenges, but is complex to accomplish this with the single application of only one reference that meets the goal, usually elements from various models and methodologies are taken. This study contains the definition of a software development process inside of a SME (Small and Medium Enterprise), through the integration of several of this frameworks (Scrum, PSP, and ISO25000) analyzed under the guidelines given by SWEBOK and supported by techniques such as GQM, that allow to make a positive contribution to meet this goals.Keywords: ISO25000, Process, PSP, Scrum, SWEBOK


Kybernetes ◽  
2019 ◽  
Vol 49 (4) ◽  
pp. 1305-1324
Author(s):  
Leandro Antonelli ◽  
Mariángeles Hozikian ◽  
Guy Camilleri ◽  
Alejandro Fernandez ◽  
Julian Grigera ◽  
...  

Purpose The design of tests is a very important step in the software development process because it allows us to match the users’ expectations with the finished product. Considered as a cumbersome activity, efforts have been made to automatize and alleviate the burden of test generation, but it is still a largely neglected step. The study aims to propose taking advantage of existing requirement artifacts, like scenarios that describe the dynamic of the domain in a very early stage of software development, to obtain tests from them. Design/methodology/approach In particular, the approach proposed complement the scenarios that are textually described with a glossary, the language extended lexicon. Thus, a set of rules to derive tests from scenarios is also proposed. The tests are then described using the task/method model. Findings The main findings of this study consist of an extension of a previously presented set of rules. And, a tool based on a media wiki platform that makes possible to record scenarios and the language extended lexicon and implement the rules to obtain the tests. Originality/value The main originality of this study is the glossary which complements scenarios, the semantic support to obtain tests and the tool to automatize the approach.


10.28945/4116 ◽  
2018 ◽  
Vol 17 ◽  
pp. 181-200
Author(s):  
Jeevamol Joy Kochumarangolil ◽  
Renumol V G

Aim/Purpose: This paper presents the findings of an Activity-Oriented Teaching Strategy (AOTS) conducted for a postgraduate level Software Engineering (SE) course with the aim of imparting meaningful software development experience for the students. The research question is framed as whether the activity-oriented teaching strategy helps students to acquire practical knowledge of Software Engineering and thus bridge the gap between academia and software industry. Background: Software Engineering Education (SEE) in India is mainly focused on teaching theoretical concepts rather than emphasizing on practical knowledge in software development process. It has been noticed that many students of CS/IT background are struggling when they start their career in the software industry due to inadequate familiarity with the software development process. In the current context of SE education, there is a knowledge gap between the theory learned in the classroom and the actual requirement demanded by the software industry. Methodology: The methodology opted for in this study was action research since the teachers are trying to solve the practical problems and deficiencies encountered while teaching SE. There are four pedagogies in AOTS for fulfilling the requirements of the desired teaching strategy. They are flipped classroom, project role-play for developing project artifacts, teaching by example, and student seminars. The study was conducted among a set of Postgraduate students of the Software Engineering programme at Cochin University of Science and Technology, India. Contribution: AOTS can fulfil both academic and industrial requirements by actively engaging the students in the learning process and thus helping them develop their professional skills. Findings: AOTS can be molded as a promising teaching strategy for learning Software Engineering. It focuses on the essential skill sets demanded by the software industry such as communication, problem-solving, teamwork, and understanding of the software development processes. Impact on Society: Activity-oriented teaching strategies can fulfil both academic and industrial requirements by actively engaging the students in the SE learning process and thus helping them in developing their professional skills. Future Research: AOTS can be refined by adding/modifying pedagogies and including different features like an online evaluation system, virtual classroom etc.


UML class model is an essential element of today's software development process. In modern software development methodologies, it is considered a key contributor in every phase of software development. It may be automatically converted into other UML models and even in programming code. However, the erroneous model generates other erroneous models. The model verification technique checks the presence of error in the UML class model. This paper's main objective is to introduce a technique for the completely automatic and expressive transformation of the UML class model's qualified association into ontology. Because the current verification method does not support the transformation and verification of qualified associations. Later on, the ontology-based reasoning method is presented to verify qualified associations and their constraints.


2014 ◽  
Vol 6 (1) ◽  
pp. 5-16
Author(s):  
Germinal Isern

Abstract This position paper presents the factors involved in the successful software development and what is the impact of some methodologies like Agile in this process. Global software development projects may be a total success or an anticipated disaster for simple reasons that usually have nothing to do with the technology involved, with the time differences, or the product being built, but because of subtle intercultural factors. How do the language, the race, the gender, the religion, and the location affects the software development process from analysis and design to implementation, testing and maintenance? Do all these factors impact in the same way if we are working with a local team, and offshore development team or even a global virtual team? Is any specific software development methodology better suited for your particular case? How could you decide what’s the better approach? What will be the results and what our goals? The issues at stake are not superficial matters of the ways how people dress, or how clear do they speak in our local language, or what they like to eat, or their small daily behaviors, but are based in the fundamental differences in the systems of values that govern our lives. So institutions, corporations and global companies have to raise the level of awareness of their employees worldwide on the cultural differences, through various programs for intercultural or diversity training. But this poor model of cultural awareness is not enough to overcome some of the obstacles that intercultural differences bring to the table. So this paper will list and describe this important intercultural factors that directly impact in the software development process and how certain software development methodologies could be used in order to have a more systematic look or set of guidelines that would allow the team managers to evaluate and to decide how theuse of each one of these software development methodologies for local teams, non local teams and virtual teams will affect positively or negatively the outcomes of software development practices.


2021 ◽  
Author(s):  
Pau Julià ◽  
David Salvador ◽  
Marc Peña

Software development methodologies have evolved during the last years to reduce the time to market to the minimum possible. Agile is one of the most common and used methodologies for rapid application development. As the agile manifesto defines in its 12 principles, one of its main goals is to satisfy the customer needs through early and continuous delivery of valuable software. Significantly, that none of the principles refers to security. In this paper, we will explain how Typeform integrates security activities into the whole development process, reducing at the same time the phases on the S-SDLC to reduce friction and improve delivery while maintaining the security level.


2020 ◽  
Author(s):  
Yosi sinta deby

ABSTRAKPerkembangan teknologi pada computer sangatlah pesat seiring dengan perkembangan software nya yang sering digunakan. Salah satu ialah dalam bidang pendidikan , komputer ini sangatlah berperan penting. Sekarang banyak sekali software yang sudah tersedia untuk mendukung dan meningkatkan mutu kualitas pendidikan. Tulisan ini akan mengkaji bagaimana komputer digunakan sebagai media pembelajaran, metodologi perkembangan perangkat lunak.ABSTRACTThe development of technology on computers is very rapid along with the development of software that is often used. One is in the field of education, this computer is very important. Now a lot of software is available to support and improve the quality of education quality. This paper will examine how computers are used as learning media, software development methodologies.


Sign in / Sign up

Export Citation Format

Share Document