Openwings Systems Specification Request

Openwings Specification Request (OSR)

Title:

Openwings Systems (OSR_005)

Summary:

The Systems Expert team is responsible for the overall architecture design. Members of the systems expert team are, by default, on the first level review team for all specifications. The systems team has responsibility for the following documents:

Section 1. Identification

Submitting Member and Specification Lead:

Expert Nominee Qualifications:

Candidates for this expert team should have the following qualifications:

1. Served as systems architect on a major software effort
2. Understanding of the issues related to integrating 3^rd party components in a systems-of-systems environment
3. Strong background in three or more of the following technology areas:
• Experience with the Java2 platform (mandatory requirement)
• Component and Service-Oriented Architectures
• High Availability Design
• Middleware technologies (CORBA, JMS, RMI, DCOM, etc)
• Security (JAAS, JCE, JSSE)
• Interface Definition Languages

Section 2: Request

2.1 Please describe the proposed Specification:

The Systems Expert team is responsible for the overall architecture design. Members of the systems expert team are, by default, on the first level review team for all specifications. The systems team has responsibility for the following documents:

1. Architecture Description Specification
2. Naming Specification
3. Interface Specification
4. Availability Specification
5. Component Developers Manual

The Architecture Specification describes the component model and modeling language being used in Openwings.  The naming specification describes entities will be named in Openwings.  The interface specification provides rules for defining various kinds of interfaces.  The Availability specification describes the techniques utilized in Openwings for Availability.  It allocates availability features to the other services in Openwings.  The Component Developers Manual provides instructions on how to use the reference implementation of Openwings.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

J2SE is largely targeted towards desktop and webtop applications on the front end.  J2EE is largely targeted towards E-Commerce and back end servers.   J2ME is targeted towards the device market.   This specification has a system focus on networked components, which includes the front end, back end, and devices; hence this specification targets all three Java platforms.  The J2ME configurations to be considered should go down to the CDLC configuration.

2.3 What need of the Openwings community will be addressed by the proposed specification?

The specifications defined under this effort define the context for the development of the rest of the specifications in Openwings.

2.4 Why isn't this need met by existing specifications?

No other specifications cover architecture, naming, interfaces or availability.

2.5 Please give a short description of the underlying technology or technologies:

These specifications will use Architecture Description Language (ADL), Unified Modelling Language (UML), and Universal Resource Locators (URLs).

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

The availability specification is the only one that defines interfaces.  In particular it defines interfaces for bit reporting in net.openwings.availability.

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No.

2.8 Are there any security issues that cannot be addressed by the current Openwings security model?

The Availability Specification raises issues about performance that relate to QoS attacks.

2.9 Are there any internationalization or localization issues?

This OSR is targeted towards systems that may be internationally deployed and hence use the internationalization features of Java.  It is anticipated that the existing internationalization infrastructure will be sufficient for this OSR.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

n/a

2.11 Please describe the anticipated schedule for the development of this specification.

Currently draft specifications serve as a starting point for this specification.  The following schedule applies:

Once the expert team is formed the finalized schedule will be made available.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology.

The Motorola IISG (now General Dynamics C4 Systems)/Sun Openwings team, has previously generated work that is being contributed as a basis for this OSR.  In particular the following contributions available at http://www.openwings.org/download.cfm#specs are relevant.

• Openwings White Paper
• Openwings Naming Specification (Alpha version 0.7)
• Openwings Architecture Specification (Alpha version 0.7)
• Openwings Interface Specification (Alpha version 0.7)
• Openwings Availability Specification (Alpha version 0.7)
• Openwings Component Developers Manual (Alpha version 0.7)

3.2 Explanation of how these items might be used as a starting point for the work.

The existing specifications will serve as the starting draft for the specifications produced under this effort.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the OSR.

None.

home | vision | search | in the news | faq | registration | open forum | tutorial | bug database
 API | download | expert teams | process management office | projects | links | terms of use

© Copyright 2001-2006 General Dynamics C4 Systems. All rights reserved.