Introducing agile practices into development processes of safety critical software

2018 ◽  
Author(s):  
Katarzyna Łukasiewicz ◽  
Janusz Górski
Keyword(s):  
Safety Critical ◽  
Agile Practices ◽  
Development Processes

Rapid Pattern-Oriented Scenario-Based Testing for Embedded Systems

2011 ◽  
pp. 222-262 ◽  
Author(s):  
Wei-Tek Tsai ◽  
Ray Paul ◽  
Lian Yu ◽  
Xiao Wei
Keyword(s):  
Medical Devices ◽  
Rapid Test ◽  
Regression Testing ◽  
Safety Critical ◽  
Industrial Sites ◽  
Test Script ◽  
Software Changes ◽  
Development Processes ◽  
Key Features ◽  
Agile Process

Systems change often, and each change requires reverification and revalidation. Modern software development processes such as agile process even welcome and accommodate frequent software changes. Traditionally, software reverification and revalidation are handled by regression testing. This chapter presents a pattern-oriented scenario-based approach to rapidly reverify and revalidate frequently changed software. Key features of this approach are (1) classifying system scenarios into reusable patterns; (2) application of a formal completeness analysis to identify missing scenarios; (3) identifying scenario patterns (SPs) and corresponding verification patterns (VPs) and robustness patterns (RBPs); (4) rapid test script generation by reusing test script templates. This approach is also compatible with formal approaches such as model checking. This approach has been used at industrial sites to test safety-critical medical devices with significant savings in cost and effort. The chapter presents several examples to illustrate the effectiveness and efficiency of this approach.

scholarly journals Lessons learnt from IEC61508 software assessments

2018 ◽  
Author(s):  
R H Campbell ◽  
R M Phillips ◽  
C Allsopp
Keyword(s):  
Software Development ◽  
Safety Management ◽  
Critical Systems ◽  
Specific System ◽  
Safety Critical ◽  
Lessons Learnt ◽  
Variable Environments ◽  
Management Processes ◽  
Development Processes ◽  
Safety Critical Systems

With the advances in platform automation and the publication of NAN 06/2018 - Software integrity (previously NAN 02/2016), there has been a drive towards compliance to IEC61508 in the naval domain.  Over the last few years Frazer-Nash have conducted a number of Original Equipment Manufacturer (OEM) audits and assessments to determine whether the requirements for safety critical software development in IEC61508 have been followed for a specific system or if a supplier's development processes are in line with the aspects of the standard which focus on software development, namely Part 3 - Software requirements.  These audits have revealed some common problems across suppliers and highlighted that IEC61508 requires both organisational safety management processes as well as those specific for a system. As the naval industry looks to adopt the processes outlined in IEC61508 or an equivalent standard, this paper will present some of the lessons learnt from our IEC61508 assessments and offer some advice for new and existing suppliers.  The paper will highlight some of the issues going forward as the development of safety critical systems is not a new concept but the specific factors arising in the naval domain from operating in variable environments, changing safe state conditions and ever increasing function complexity, present a key challenge. Included in the paper will be a view on how other industries are tackling IEC61508 compliance and where the strategies that have been adopted may be applicable in the naval domain as well as new tools which could assist with the development of safety critical systems. 

Systematic literature review – improving business processes by implementing agile

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Anna Schmitt ◽  
Sabrina Hörner
Keyword(s):  
Literature Review ◽  
Software Development ◽  
Systematic Literature Review ◽  
Business Processes ◽  
Business Environment ◽  
Primary Sources ◽  
Content Type ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Approach

PurposeNumerous approaches from the field of economics already exist for the improvement of business processes. In the field of software development, work has been done on improving development processes. For years, the focus here has been on agile approaches. Although various approaches for improving business processes exist, it is becoming increasingly difficult to adapt business processes to the fast-moving conditions of the market and the business environment. Agile approaches address this issue. Thus, not only software development processes, but also business processes should benefit from agile approaches.Design/methodology/approachTo this end, values and principles of the Agile Manifesto, agile methods such as Scrum, and various agile practices such as the Kanban board should be applied in business processes. This paper examines the work already done on this topic. With the help of a systematic literature review (SLR), literature studies dealing with the implementation of the agile approach in business processes are identified.FindingsThis paper presents, investigates and contrasts 12 primary sources dealing with agile and business processes and shows how they are different/ equal regarding three research questions.Originality/valueWe provide an overview of existing approaches handling the combination of agile and business processes to improve business processes.

SaaS Requirements Engineering for Agile Development

2013 ◽  
pp. 64-93 ◽  
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

SaaS Requirements Engineering for Agile Development

2015 ◽  
pp. 660-688
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

SaaS Requirements Engineering for Agile Development

2014 ◽  
pp. 351-380
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

Sign in / Sign up

Export Citation Format

Share Document