Simulation-Based Embedded Agile Development

Continuous deployment of software intensive products and services: A systematic mapping study

“…A plethora of evidence related to CD exists in organizational white papers and on-line blogs, where practitioners have voiced their experiences and expectations in moving to CD (e.g. Facebook 1 , IBM 2 , Microsoft 3 , Google 4 , Adobe 5 , Netflix 6 and IMVU 7 ). Accordingly, a body of academic literature is also emerging on this topic.…”

“…The central concept in Humble and Farley's approach is a deployment pipeline that establishes an automated end-to-end process to ensure that the system works at technical level, executes fairly automated acceptance tests and lastly deploys to a production or staging environment. 1 https://www.facebook.com/notes/facebook-engineering/ship-early-andship-twice-as-often/10150985860363920 (accessed 09, 2015) 2 http://www.ibm.com/developerworks/rational/library/continuousdeployment-rational-alm/ (accessed 09, 2015) 3 http://blogs.msdn.com/b/bharry/archive/2012/06/07/announcingcontinuous-deployment-to-azure-with-team-foundation-service.aspx (accessed 09, 2015) 4 https://air.mozilla.org/continuous-delivery-at-google/ (accessed 09, 2015) 5 http://steveblank.com/2014/01/06/15756/ (accessed 09, 2015) 6 http://steveblank.com/2014/01/06/15756/ (accessed 09, 2015) 7 http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doingthe-impossible-fifty-times-a-day/ (accessed 09, 2015)…”

“…In test automation, a variety of test suites: unit, functional, integration, and performance tests are executed at different phases [37] and with different scope: component, subsystem, partial product, product, release and customer [60]. These test suites use practices such as automated execution of test scripts on a build server after each code commit to test and check the status of the code or the build [1,48,54,76], automating acceptance testing [37,57], automatic testing of the production environment in non-embedded software [40] and simulation to demonstrate and test the quality of software much earlier for embedded software [3]. In addition, efficient prioritisation and the ordering of automated test execution are emphasised in order to ensure fast feedback to the development team as well as the proper use of resources [32,37].…”

“…Continuous integration (CI) is one of the main enablers of CD [61,62,34,32,75,3,1,37,47,48,54]. The main advantage of CI is that it automates tasks such as compiling code, running unit and acceptance tests, monitoring and validating code coverage, checking compliance with coding standards, static code analysis, automatic code review and building deployment packages [32,1,54,76,3]. Therefore, CI provides mechanisms to ensure that there is always a shippable product that has passed all of the testing phases [32,62].…”

“…Regarding the application domain, the main challenge of using CD in embedded systems is that physical assets and hardware equipment should also support CI in order to benefit from CD as a whole. To overcome this problem, in the avionics domain, Ard et al [3] propose a simulated integrated system that facilitates CI of embedded systems.…”