This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Control Software Interface for Managing System Requirements
Technical Paper
2004-01-0363
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
Not all software tools are created equal and not all software tools are created to perform the same tasks. Therefore, different software tools are used to perform different tasks. However, being able to share the information between the different software tools, without having to manually re-enter (duplicate) any of the information, can save a lot of time and improve the quality of the product. The control software interface presented in this paper, allows system engineers to exchange data between software tools in an efficient manner which maximizes each tools capabilities and ultimately reduces development time and improves the quality of the product.
Recommended Content
Authors
Citation
Rushton, G., Wesley, A., Zakarian, A., and Grigoryan, T., "Control Software Interface for Managing System Requirements," SAE Technical Paper 2004-01-0363, 2004, https://doi.org/10.4271/2004-01-0363.Also In
Software/Hardware Systems, Systems Engineering, Advanced Electronics Packaging, and Electromagnetic Compatibility (Emc)
Number: SP-1857; Published: 2004-03-08
Number: SP-1857; Published: 2004-03-08
References
- Rushton, G. Zakarian, A. Grigoryan, T. 2002 “Algorithms and Software for Development of Modular Vehicle Architectures” SAE World Congress 2002-01-0140
- Wesley, A. Rushton, G. Zakarian, A. Grigoryan, T. 2003 “Requirements Models and Requirements Documents: Bridging the Gap with the DOORS API” Telelogic Users Group - TUG 2003
- Rushton, G. Zakarian, A. 2000 “Modular Vehicle Architectures: A Systems Approach” Proceedings of the Tenth Annual International Symposium of the International Council on Systems Engineering 29 35
- Rushton, G. Merchant, V. 2000 “Vehicle Electrical/Electronic System Design Considerations” SAE World Congress 2000-01-0131