2.4.2 Systems engineering saves the day
暂无分享,去创建一个
This paper is an experience report about how adding a systems engineer to a project helped the team achieve a second-place result in a competition despite overwhelming technical and programmatic obstacles. The setting of the case in this report is Trondheim where the co-author joined a student team that should design and construct a car to compete in the Shell Eco-marathon. The project started August 2010 and ended May 2011, but the systems engineer joined the project late, and started his work in the middle of January 2011. The paper takes the reader on a journey following the steps taken to introduce and apply systems engineering techniques in a project that was time and resource constrained. The paper demonstrates the effectiveness of simple techniques, such as the “Systems Engineering Wall,” to implement systems engineering practices and improve team communications. The conclusion is that the systemic and systematic approaches of systems engineering, in this instance, helped the team achieve a winning result.
[1] Herbert Negele,et al. Coping with changes : Causes, findings, and strategies , 2000 .
[2] Yacov Y. Haimes,et al. Principles and guidelines for project risk management , 2002 .
[3] A. Terry Bahill,et al. The systems engineering started in the middle process: A consensus of systems engineers and project managers , 2001 .
[4] Peter L. Jackson,et al. Systems engineering metrics and applications in product development: A critical literature review and agenda for further research , 2008 .