{"title":"Innovation Welcome: An Agile Approach to Model-Based Development of Safety-Critical Embedded Systems","authors":"J. Mills, R. Turin, J. Mangas, S. Ranville","doi":"10.1109/ICSA-C.2018.00045","DOIUrl":null,"url":null,"abstract":"From concept to production, intelligent tools are needed to pave the way for stress-free development of complex automotive embedded systems. While automotive products depend more and more on software as the distinguishing feature to achieve a competitive edge, the addition of software features to the overall system functionality comes at a hefty price. As the development times become shorter and shorter, the simultaneous increase in complexity demands diligent partitioning of the software development tasks and ultimately the collaboration of many multi-disciplinary development teams that work in parallel. This leads to a multitude of independently developed software artifacts, each of which will eventually be required to seamlessly integrate into the overall system architecture. Of course, such a seamless integration can ultimately only be achieved if the artifact development follows a very disciplined, if not rigid, development process. However, the more the process is policed, the more the feature engineers will be required to follow procedure and the less they will be able to exploit their creative potential. This is a conundrum that is hard to solve. Rigid development rules are necessary to ensure functional safety, artifact integrity, and consistency throughout the development process. On the other hand, agile development that facilitates product innovation on a functional level is necessary to gain a competitive edge. The two objectives, if viewed within the context of a traditional software development process, are competing objectives and one typically has to be content with a compromise. But what if there is a way to achieve both objectives simultaneously? What if there is a way to delegate the policing to a suite of intelligent development tools that shelter each feature developer when unleashing his/her creative potential? This presentation describes a new, agile, architecture-centric software development paradigm and a companion tool framework that facilitates stress and error-free software development across all stages of a production software development program that is highly agnostic to the specific business rules of an organization.","PeriodicalId":261962,"journal":{"name":"2018 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2018 IEEE International Conference on Software Architecture Companion (ICSA-C)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSA-C.2018.00045","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
From concept to production, intelligent tools are needed to pave the way for stress-free development of complex automotive embedded systems. While automotive products depend more and more on software as the distinguishing feature to achieve a competitive edge, the addition of software features to the overall system functionality comes at a hefty price. As the development times become shorter and shorter, the simultaneous increase in complexity demands diligent partitioning of the software development tasks and ultimately the collaboration of many multi-disciplinary development teams that work in parallel. This leads to a multitude of independently developed software artifacts, each of which will eventually be required to seamlessly integrate into the overall system architecture. Of course, such a seamless integration can ultimately only be achieved if the artifact development follows a very disciplined, if not rigid, development process. However, the more the process is policed, the more the feature engineers will be required to follow procedure and the less they will be able to exploit their creative potential. This is a conundrum that is hard to solve. Rigid development rules are necessary to ensure functional safety, artifact integrity, and consistency throughout the development process. On the other hand, agile development that facilitates product innovation on a functional level is necessary to gain a competitive edge. The two objectives, if viewed within the context of a traditional software development process, are competing objectives and one typically has to be content with a compromise. But what if there is a way to achieve both objectives simultaneously? What if there is a way to delegate the policing to a suite of intelligent development tools that shelter each feature developer when unleashing his/her creative potential? This presentation describes a new, agile, architecture-centric software development paradigm and a companion tool framework that facilitates stress and error-free software development across all stages of a production software development program that is highly agnostic to the specific business rules of an organization.