Report from the requirements group for real-time extensions for the Java platform

The Requirements Group for Real-time Extensions to the Java™ Platform includes representatives from companies and organizations whose expertise spans the computing industry and academia. Industry participants include desktop, server, and enterprise systems providers, embedded systems providers, device manufacturers, and real-time operating system vendors. The goal of the Group is to develop cross-disciplinary requirements for real-time functionality that is expected to be needed by real-time applications written in the Java™ programming language and executing on various platforms. See Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. The National Institute of Standards and Technology (NIST) sponsored the Requirements Group for Real-time Extensions to the Java™ Platform. The Requirements Group includes representatives from companies and organizations whose expertise spans the computing industry and academia. Industry participants include desktop, server, and enterprise systems providers, embedded systems providers, device manufacturers, and real-time operating system vendors. The Requirements Group met during a six-month period in a series of open workshops. Additionally, the Requirements Group continued discussions on the rt-java@raleigh.ibm.com mailing list. The goal of the Group was to develop cross-disciplinary requirements for real-time functionality that is expected to be needed by real-time applications written in the Java™ programming language and executing on various platforms. This document is the result of the Requirements Group's efforts. The requirements contained in this document were developed by group consensus. Therefore the requirements in total do not necessarily represent the opinions of all Requirements Group members or their organizations. In the Requirements Group workshops, consensus was declared only in cases where the agreement was overwhelming. Unless explicitly stated otherwise, consensus was reached on all requirements. In a few instances, a strong consensus could not be reached. Where strong consensus could not be reached, the requirement is marked as Open — no consensus. Content marked as Rationale or Discussion is not consensus-based content and should not be considered representative of the opinions of the Requirements Group in total. Rationale and Discussion paragraphs were drafted by members of the Requirements Group and primarily represent the opinions of the respective authors. These paragraphs serve to provide additional information to those applying the requirements to future specifications.