Re:Ask HN: What tools and work methodology for Systems Engin...
by hclalpha on Sunday December 18, 2016 @02:04AM
(#13204705)
We're in the very particular business of Aircraft Simulation, specifically integrating real parts in a custom made simulation environment for pilots to train in. The products get certified based on functionality/realism level (Level D which requires motion/feel/view), thus we have very few low-level documentation requirements as compared to typical Aircraft design. We do test the platforms internally pretty correctly as they get audited by FAA/EASA autorities before certification. In the end, however, we end-up maintaining, updating and re-certifying the many-years-old platforms with the authorities for pretty much the full flying life of the fleet of planes we simulate, and for each of the updates delivered, often struggling to figure out the architecture of our old platforms (or our competitors even, as we provide updates for theses too).
Thanks for your input!
Re:Ask HN: What tools and work methodology for Systems Engin...
by BOOSTERHIDROGEN on Sunday December 18, 2016 @02:13AM
(#13204725)
Do you work as instrument engineer in power plant industry? I'm not quite sure what kind of project that you have to use IEEE SWEBOK?
My experience is in fields of instrumentation and control for electrical power generation and transmission, and steelworks automation. The projects I have worked on use IEEE SWEBOK and OMG SYSML as a minimum. The management have traditional engineering background (mechanical, electrical, civil and chemical) so design documentation is extensive and then updated to "as built" status when commissioned. Generally we create models and perform extensive validation and scenario testing before committing to production code.