Abstract
For the (distributed) development of certain highly innovative software-intensive systems such as semi-autonomous robots, it is not clear which life cycle approach to follow best. Especially in a (local) research environment, the development may typically happen in some bottom-up form of prototyping. In contrast, standard systems engineering would (still) prescribe a waterfall life cycle. Software engineering would strongly suggest some form of iterative and incremental development. Iterative development has high potential for improvements in general systems engineering, but in contrast to pure software development it also has inherent limits. We investigate these issues and propose a new iterative but not incremental life cycle approach. It involves iterations of requirements engineering and architecting, but not of low-level design, implementation and testing. The reason for the latter is inherently given by costs and required time for hardware development.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
