Norbert Oswald


Future unmanned aerial systems demand capabilities to perform missions automatically to the greatest possible extent. Missions like reconnaissance, surveillance, combat, or SEAD usually consist of recurring phases and contain resembling or identical portions such as autonomous flight control, sensor processing, data transmission, communication or emergency procedures. To avoid implementing many similar singular solutions, a systematic approach for the design of an unmanned avionic software architecture is needed. Current approaches focus on a coarse system design, do not integrate off-the-shelf middleware, and do not consider the needs for having on-board intelligence. This paper presents a reference software architecture to design and implement typical missions of unmanned aerial vehicles based on a CORBA middleware. The architecture is composed of identical components and rests upon the peer-to-peer architectural style. It describes the internal structure of a single component with respect to autonomous requirements and provides a framework for the rapid development and implementation of new components. The framework separates functionality and middleware by hiding ORB specific statements from components. Experimental tests simulating a reconnaissance mission using various ORB implementations indicate the benefits of having an architectural design supporting multi-lingual multi-process distributed applications.


  1. Binns, P. and Vestal, S. (1993). Formal real-time architecture speci cation and analysis. In In Tenth IEEE Workshop on Real-Time Operating Systems and Software, New York.
  2. Brooks, R. (1986). A layered control system for a mobile robot. 3rd Symposium. MIT Press, pages 367-372.
  3. Cheyer, A. and Martin, D. (2001). The open agent architecture. Journal of Autonomous Agents and Multi-Agent Systems, 4(1):143-148. OAA.
  4. Clements, P., Kazman, R., and Klein, M. (2002). Evaluating software architectures: Methods and case studies. Technical report, SEI, Series in Software Engineering.
  5. Coglianese, L. and Szymanski, R. (1993). Dssa-adage: An environment for architecture-based avionics development. In AGARD'93.
  6. Dashofy, E., Hoek, A., and Taylor, R. (2002). An infrastructure for the rapid development of xml-based architecture description languages. In The 24th International Conference on Software Engineering, Orlando.
  7. Dashofy, E., Medvidoc, N., and Taylor, R. (1999). Using off-the-shelf middleware to implement connectors in distributed software architectures. In International Conference on Software Engineering, Los Angeles.
  8. Dissaux, P. (2004). Using the aadl for mission critical software development. In ERTS conference, Toulouse.
  9. Douglass, B. (2002). Real-Time Design Pattern. Addison Wesley.
  10. Feiler, P., Lewis, B., and Vestal, S. (2003). The sae avionics architecture description language (aadl) standard: A basis for model-based architecture-driven embedded systems engineering. In RTAS 2003, Washington. vorhanden.
  11. Garlan, D., Monroe, R., and Wile, D. (2000). Acme: Architectural description of component-based systems. Technical report, CMU, Software Engineering Institute.
  12. Garlan, D. and Shaw, M. (1993). An introduction to software architecture. In Ambriola, V. and Tortora, G., editors, Advances in Software Engineering and Knowledge Engineering.
  13. Hansen, S. (2003). Integration of autonomous system components using the jaus architecture. In AUVSI Unmanned Systems 2003, Baltimore.
  14. JAUS (2004). Joint architecture for unmanned systems.
  15. Kortenkamp, D., Bonassao, R., and Murphy, R., editors (1998). Arti cial Intelligence and Mobile Robots. MIT Press.
  16. Maes, P. (1994). Mmodelling adaptive autonomous agents. Arti cial Life, 1(1):135-162.
  17. Medvidoc, N. (1999). Architecture-based Speci -cationTime Software Evolution. PhD thesis, University of California.
  18. Medvidoc, N., Oreizy, P., Robbins, J., and Taylor, R. (1996). Using object-oriented typing to support architectural design in the c2 style. In SIGSOFT'96. ACM Press.
  19. Medvidovic, N. and Taylor, R. N. (2000). A classi cation and comparison framework for software architecture description languages. Software Engineering, 26(1):70-93.
  20. Nilsson, N. (1980). Principles of Arti cial Intelligence. Tioga Press.
  21. Nitto, E. D. and Rosenblum, D. (1999). Exploiting ADLs to specify architectural styles induced by middleware infrastructures. In Int. Conf. on Software Engineering, pages 13-22.
  22. Ryan, C., Kuhns, F., Schmidt, D., Othman, O., and Parsons, J. (2000). The design and performance of a pluggable protocol framework for real-time distributed object computing middleware. In ACM/IFIP, editor, Proceedings of the Middelware 2000 Conference.
  23. Schrage, D. P. and Vachtsevanos, G. (1999). Software enabled control for intelligent UAVs. In 1999 IEEE International Conference on Control Applications.
  24. Wills, L., Kannan, S., Sanders, S., Guler, M., Heck, B., Prasad, J., Schrage, D., and Vachtsevanos, G. (2001). An open platform for recon gurable control. IEEE Control Systems Magazine, 21(3).

Paper Citation

in Harvard Style

Oswald N. (2004). TOWARDS A CONCEPTUAL FRAMEWORK- BASED ARCHITECTURE FOR UNMANNED SYSTEMS . In Proceedings of the First International Conference on Informatics in Control, Automation and Robotics - Volume 2: ICINCO, ISBN 972-8865-12-0, pages 118-126. DOI: 10.5220/0001137501180126

in Bibtex Style

author={Norbert Oswald},
booktitle={Proceedings of the First International Conference on Informatics in Control, Automation and Robotics - Volume 2: ICINCO,},

in EndNote Style

JO - Proceedings of the First International Conference on Informatics in Control, Automation and Robotics - Volume 2: ICINCO,
SN - 972-8865-12-0
AU - Oswald N.
PY - 2004
SP - 118
EP - 126
DO - 10.5220/0001137501180126