ISO/IEC JTC1/SC22/WG9 N426r2, 17 July 2003


Date of presentation of proposal:
National Body

A proposal for a new work item shall be submitted to the secretariat of the ISO/IEC joint technical committee concerned with a copy to the ISO Central Secretariat.

Presentation of the proposal - to be completed by the proposer Guidelines for proposing and justifying a new work item are given in ISO Guide 26.

Guide for the use of the Ada Ravenscar Profile in High-Integrity Systems
Provide a complete definition of the Ravenscar Profile, a rationale, and guidelines and examples of usage. The profile is useful to high-integrity real-time applications wishing to make use of the concurrency features of Ada.

Purpose and justification
The Ravenscar Profile has been developed by an informal group of experts meeting under the auspices of a series of International Workshops on Real-Time Ada Issues. It has now gained de facto status as a standard. The Profile defines a coherent set of tasking features that together enable small, efficient and certifiable run-times to be produced, and applications developed that conform to the requirements of fixed priority scheduling analysis. The language changes needed to define Ravenscar (new pragmas and pragma identifiers) within Ada have recently been agreed by WG9. The purpose of this technical report is to provide an practioner-oriented description of the profile, a full rationale for the features it includes, and an extensive set of examples of use. The profile is already supported by vendors and there is considerable industrial interest. A guide for its use within an ISO technical report will significantly enhance take up and impact.

As the base document for this Technical Report is already publicly available, the resulting Technical Report will also be made publicly available in accordance with guidelines previously approved by JTC1.

Programme of work

If the proposed new work item is approved , which of the following document(s) is (are) expected to be developed?
____ a single International Standard more than one International Standard (expected number: ........ )
____ a multi-part International Standard consisting of .......... parts
____ an amendment or amendments to the following International Standard(s) ....................................
__X__ a technical report , type 3

Relevant documents to be considered: The proceedings of the 9th, 10th and 11th International Workshops on Real-Time Ada Issues, plus other relevant publications.
Cooperation and liaison: No formal liaison is anticipated on this item, but WG9 maintains Category C Liaison with the two leading Ada professional societies, ACM SIGAda and Ada Europe.
Preparatory work offered with target date(s)
A Report has recently been published by the University of York, UK. This is provided by the university via the UK National Body as a contribution to the project. It is attached as the first draft of the technical report, suitable for PDTR registration. PDTR ballot will occur by July 2004. DTR ballot will occur by Dec 2004.

Will the service of a maintenance agency or registration authority be required? No
- If yes, have you identified a potential candidate?
- If yes, indicate name

Are there any known requirements for coding? No
-If yes, please specify on a separate page

Are there any known requirements for cultural and linguistic adaptability? No
- If yes, please specify on a separate page

Does the proposed standard concern known patented items? No
- If yes, please provide full information in an annex

Comments and recommendations of the JTC 1 Secretariat - attach a separate page as an annex, if necessary

Comments with respect to the proposal in general, and recommendations thereon:
It is proposed to assign this new item to JTC 1/SC 22/WG 9

Voting on the proposal - Each P-member of the ISO/IEC joint technical committee has an obligation to vote within the time limits laid down (normally three months after the date of circulation).

Date of circulation:
Closing date for voting:
Signature of JTC 1 Secretary:
Lisa A. Rajchel

Criterion Validity: Explanation:
A Business Requirement    
A.1 Market Requirement Essential:
See above justification.
A.2 Regulatory Context Essential:
Supportive: X
Not Relevant:
 The use of the de facto standard has already helped certification for high-integrity applications.
B. Related Work    
B.1 Completion/Maintenance of current standards Yes: X
 The work provides early notification of potential modifications to the Ada language standard.
B.2 Commitment to other organization


No: X

 But informal liaison will be maintained with the participants in the current de facto process.
B.3 Other Source of standards Yes: X
See above for sources of de facto documents.
C. Technical Status    
C.1 Mature Technology Yes: X
This is a standardization of existing practice.
C.2 Prospective Technology Yes: N/A
C.3 Models/Tools Yes: N/A
D. Conformity Assessment and Interoperability    
D.1 Conformity Assessment Yes:
D.2 Interoperability Yes: X
 The work supports "portability" of concurrent programs among various platforms.
E. Other Justification    

Notes to Proforma

A. Business Relevance. That which identifies market place relevance in terms of what problem is being solved and or need being addressed.

A.1. Market Requirement. When submitting a NP, the proposer shall identify the nature of the Market Requirement, assessing the extent to which it is essential, desirable or merely supportive of some other project.

A.2 Technical Regulation. If a Regulatory requirement is deemed to exist - e.g. for an area of public concern e.g. Information Security, Data protection, potentially leading to regulatory/public interest action based on the use of this voluntary international standard - the proposer shall identify this here.

B. Related Work. Aspects of the relationship of this NP to other areas of standardization work shall be identified in this section.

B.1 Competition/Maintenance. If this NP is concerned with completing or maintaining existing standards, those concerned shall be identified here.

B.2 External Commitment. Groups, bodies, or fora external to JTC1 to which a commitment has been made by JTC for cooperation and or collaboration on this NP shall be identified here.

B.3 External Std/Specification. If other activities creating standards or specifications in this topic area are known to exist or be planned, and which might be available to JTC1 as PAS, they shall be identified here.

C. Technical Status. The proposer shall indicate here an assessment of the extent to which the proposed standard is supported by current technology.

C.1 Mature Technology. Indicate here the extent to which the technology is reasonably stable and ripe for standardization.

C.2 Prospective Technology. If the NP is anticipatory in nature based on expected or forecasted need, this shall be indicated here.

C.3 Models/Tools. If the NP relates to the creation of supportive reference models or tools, this shall be indicated here.

D. Any other aspects of background information justifying this NP shall be indicated here.

D. Conformity Assessment and Interoperability

D.1 Indicate here if Conformity Assessment is relevant to your project. If so, indicate how it is addressed in your project plan.

D.2 Indicate here if Interoperability is relevant to your project. If so, indicate how it is addressed in your project plan.