Your SlideShare is downloading. ×
Draft Request For Proposal Unified Component Model for Distributed, Real-Time and Embedded Systems
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Draft Request For Proposal Unified Component Model for Distributed, Real-Time and Embedded Systems

353
views

Published on

Draft Request For Proposal Unified Component Model for Distributed, Real-Time and Embedded Systems . …

Draft Request For Proposal Unified Component Model for Distributed, Real-Time and Embedded Systems .
mars/2013-03-01

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
353
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Draft Request For ProposalUnified Component Model for Distributed, Real-Time and Embedded Systems mars/2013-03-01
  • 2. Draft RFP Draft RFP posted to the OMG before the 4 week deadline Published as mars/2013-02-05 Based on initial feedback a revised draft RFP has been published as mars/2013-02-192 Copyright © 2013
  • 3. Main requirements Proposals shall specify a component model for Distributed, Real-Time and Embedded Systems. This component model shall be an evolution of the Lightweight CCM specification Proposals shall be independent of any particular middleware standard3 Copyright © 2013
  • 4. Component Model Proposals shall provide a user extensible, event driven programming model, that supports both thread pools as well as a single-threaded/non re-entrant threading model as the default Proposals shall follow a component, container, and connector based architecture Proposals shall not have CORBA as a mandatory dependency Proposals shall provide a IDL defined PSM Proposals shall not provide language bindings to specific programming languages such as C, C++, C++11, or Java, but shall instead leverage the OMG IDL language mappings4 Copyright © 2013
  • 5. Container Proposals shall provide support for a simple, lightweight CIF container that encapsulates a flexible event queue/dispatch and threading model. The container provides the execution environment for UCM application components Proposals shall provide support for scheduling timers (sporadic and recurring) with application supplied event handlers, using at least monotonic and system time Proposals shall support the integration of technical services through the concept of service connectors which are connectors that have only one instance within a container5 Copyright © 2013
  • 6. Generic Interaction Support Proposals shall use the CCM Generic Interaction Support (GIS) connector concepts, and GIS extensions to the IDL grammar for the specification of UCM components, ports, template modules, connectors, mirror ports, interfaces, and other supporting types in IDL Proposals shall offer support for UCM GIS extended port types that implement a middleware agnostic publish subscribe information exchange pattern. Proposals shall leverage the DDS4CCM specification to the maximum practical extent Proposals shall offer support for UCM GIS extended port types that implement a middleware agnostic request-reply information exchange pattern6 Copyright © 2013
  • 7. Deployment Proposals shall address the interface of a UCM component implementation framework (CIF) to a deployment framework that is compliant with the OMG Deployment and Configuration of Component- based Distributed Applications (DEPL) specification Proposals shall address standardized component and connector life cycle state model with appropriate callback operations compatible with a DEPL deployment framework Proposals shall address reconfiguration and redeployment options for modification of a UCM domain at run-time7 Copyright © 2013
  • 8. RFP Schedule There are a lot of aspects to UCM At the OMG Reston and Berlin technical meetings a Component Information Day (CID) is scheduled to get more feedback from the user community We need to give interested parties enough time to work on UCM, we don’t want a paper specification8 Copyright © 2013
  • 9. RFP Schedule Event or Activity Actual Date Preparation of RFP by TF RFP placed on OMG document server “Four week rule” Approval of RFP by Architecture Board, Review by TC TC votes to issue RFP September 2013 LOI to submit to RFP due December 1, 2013 Initial Submissions due and placed on OMG document server February 13, 2014 Voter registration closes April 1, 2014 Initial Submission presentations March 17, 2014 Preliminary evaluation by TF March 17, 2014 Revised Submissions due and placed on OMG document server November 5, 2014 Revised Submission presentations December 8, 2014 Final evaluation and selection by TF , Recommendation to AB and TC December 8, 2014 Approval by Architecture Board, Review by TC December 8, 2014 TC votes to recommend specification December 2014 BoD votes to adopt specification March 20159 Copyright © 2013