10th IEEE International Symposium on
      Object/component/service-oriented Real-time distributed Computing
                                  May 7-9, 2007
                            Santorini Island, Greece

         Sponsor: IEEE Computer Society TC on Distributed Processing
                  In cooperation with: OMG, IFIP WG 10.4

                   Web Site:  http://ise.gmu.edu/isorc07

 -----------------------------------------------------------------------
|                            Important Dates                            |
|-----------------------------------------------------------------------|
|               Paper Submissions:       *Extended to* December 8, 2006 |
|               Acceptance Notification: January 20, 2007               |
|               Camera-Ready Papers:     February 5, 2007               |
 ----------------------------------------------------------------------- 
   SCOPE
   This is the tenth IEEE Computer Society symposium dealing with the
   rapidly expanding field of object/component/service-oriented real-
   time distributed computing (ORC) technology. The principal theme 
   of ISORC is the use of the object-oriented computing paradigm - 
   which has prevailed in many non-real-time applications in the past 
   decade - in a wide variety of real-time applications. In the ISORC
   series, this paradigm emphasizes its spirit of openness where 
   diverse views and new approaches to challenging issues can be 
   freely discussed.
 
   TOPICS OF INTEREST
   Papers pertaining to all aspects of ORC are sought, including but not
   limited to the following:
 
   Programming and system engineering: ORC paradigms, object/component
   models, languages, RT Corba, Embedded .NET, RT RMI, RT Java, UML,
   model-driven development of high integrity applications, specification,
   design, verification, validation, testing, maintenance, system of 
   systems, etc.
 
   Distributed computing and communication infrastructures:
   Internet QoS (quality of service), real-time communication,
   networked computing platforms, protocols, peer-to-peer computing,
   sensor networks,inter-operability, security, trusted and dependable
   systems, fault tolerance, virtual subnets for ORC.
 
   System software: real-time kernels and operating systems, middleware
   support for ORC, QoS management, extensibility, synchronization, 
   resource allocation, scheduling,fault tolerance, security.
 
   Applications: embedded systems (automotive, avionics, consumer
   electronics, building systems, sensors, etc), multimedia processing,
   RT Web-based applications and use of XML, real-time object-oriented 
   simulations.
 
   System evaluation: output accuracy, timeliness, worst-case execution
   time, dependability, end-to-end QoS, overhead, fault detection and
   recovery time.
 
   Papers dealing with other issues that are related to the
   specification, design, implementation, and evaluation of ORC 
   systems are also welcome.
 
   To promote dialogues between researchers and users of ORC, 
   contributions from industry are particularly welcome.
 
   CONFERENCE SESSION FORMATS
 
   Following the tradition of ISORC, the conference program will 
   consist of sessions of different formats:
      - presentations of regular and short papers,
      - a number of panel discussions, and
      - special sessions devoted to reporting industrial advances
 
   GUIDELINES FOR MANUSCRIPTS
 
   Research Papers.
      Papers should describe original work and be 20 double-spaced pages
      (6,000 words) or less in length.
 
   Papers presenting Industrial Advances.
      Industrial papers and practitioner reports, describing experiences
      of using ORC technology in application or tool development 
      projects, are an integral part of the technical program of ISORC. 
      A majority of these papers are expected to be shorter and less 
      formal than research papers. They should clearly identify, and 
      discuss in detail, the issues that represent notable industrial 
      advances. Reports with project metrics supporting their claims 
      are particularly sought, as well as those that show both benefits 
      and drawbacks of the approaches used in the given project.
 
   Short Synopses.
      Short papers (about 5 double-spaced pages in length) on substantial
      real-time applications are also invited, and should contain enough
      information for the program committee to understand the scope of 
      the project and evaluate the novelty of the problem or approach.
 
   According to program committee guidelines, papers presenting practical
   techniques, ideas, or evaluations will be favored. Papers reporting
   experimentation results and industrial experiences are particularly 
   welcome. Originality will not be interpreted too narrowly.
 
   Papers that are based on severely unrealistic assumptions will not be
   accepted however mathematically or logically sophisticated the 
   discussion may be. All accepted submissions will appear in the 
   proceedings published by IEEE. A person will not be allowed to present 
   more than 2 papers at the symposium.
 
   PAPER SUBMISSION
 
   Please submit your paper in portable postscript or pdf format (all
   uncommon fonts embedded) by email to:   [EMAIL PROTECTED]


   ORGANIZERS:
   Symposium Co-Chairs:
      Rob Pettit, The Aerospace Corporation, USA
      Jean-Pierre Banatre University of Rennes, France
      Tatsuo Nakajima, Waseda University, Japan
      Stathes Hadjiefthymiades, University of Athens, Greece

   Program Co-Chairs:
      Miguel A. de Miguel, Tech. Univ. Madrid, Spain
      Vana Kalogeraki, University of California Riverside, USA
      Doo-Hyun Kim, Konkuk University, Korea
----
[[ Petri Nets World:                                                ]]
[[              http://www.informatik.uni-hamburg.de/TGI/PetriNets/ ]]
[[ Mailing list FAQ:                                                ]]
[[ http://www.informatik.uni-hamburg.de/TGI/PetriNets/pnml/faq.html ]]
[[ Post messages/summary of replies:                                ]]
[[                               [email protected] ]]

Reply via email to