This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Systems Engineering Efforts - What, When and How Much?
Technical Paper
2004-01-2615
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
This paper describes the electrical system development for the headlight feature in an International High Performance Vehicle. Systems engineers developed several iterations of functional requirements, functional block diagrams, state diagrams, and body controller software requirements early in the development cycle at considerable engineering expense. The hardware design team found the functional block diagrams useful, however the software design team did not find the other artifacts useful. The software design teams chose to implement a design that was very similar to a current product offering and did not map to the system proposed by the systems engineering team. This paper provides examples of the Systems Engineering artifacts and shows when they were developed in the project timeline.
Recommended Content
Technical Paper | One-Wire Automotive Electrical Systems |
Progress In Technology | Design and the Reliability Factor |
Authors
Citation
Sevcovic, M. and Rotz, J., "Systems Engineering Efforts - What, When and How Much?," SAE Technical Paper 2004-01-2615, 2004, https://doi.org/10.4271/2004-01-2615.Also In
References
- International Truck and Engine Subsystem Segment Specification EED-S3-885 for the Headlight Subsystem
- Mil-Std 498 - Military Standard Software Development and Documentation http://wwwedms.redstone.army.mil/edrd/ref498/498s td.pdf