The term Model-Based Development and Verification is typically used to describe system development approaches, in which models are created and systematically transformed into concrete implementations. Many Software Development Life Cycles (SDLC) were created over the years. Although they define different strategies for executing software development, validation, and verification, it is observable that such models differ only in granularity and sequence of processes' executions. As RTCA DO-178C and DO-331 do not enforce a specific SDLC, the main contribution of this paper is to present how objectives and activities can be organized in four traditional Software Development Life Cycles (Waterfall, V, Spiral, and Incremental), when Model-Driven Design (MDD) is used. This paper provides a generic way to organize the SDLC, satisfying the RTCA DO-178C and DO-331 objectives for a Level A software.
Tailoring Traditional Software Life Cycles to Ensure Compliance of RTCA DO-178C and DO-331 with Model-Driven Design
01.09.2018
623141 byte
Aufsatz (Konferenz)
Elektronische Ressource
Englisch