Rosetta Study Group Report

IEEE DASC

1. Broad market potential

• Applications: heterogeneous model integration – ESL, System-Level Design, System Security, Constraint

Modeling

• Suppliers:– Current: EDAptive Computing, Inc; Cadstone LLC– Potential: Tool providers in diverse areas, ranging from

traditional EDA vendors to providers of high-assurance systems

• Users:– Current: EDAptive Computing; Cadstone; Galois Connections;

National Security Agency– Potential: Lockheed Martin; Intel; Northrop Grumman; any

electronic system provider with heterogeneous modeling needs

2. Compatibility with related standards

• UML: – Solves a complimentary problem– UML models system structure while Rosetta models system

behavior– Ongoing discussions with SysML developers.

• EDA languages:– Serves as a “semantic backplane” for language integration– Domains for integrating traditional languages such as VHDL,

Verilog and SystemC are planned– Original Rosetta roadmap calls explicitly for EDA Language

integration– Early efforts have been highly successful

3. Distinct identity

• Formal semantics for heterogeneous modeling and model composition

• Engineer-friendly language support for heterogeneous modeling and model composition

• Extensible support for representing and integrating multiple models of computation

• Declarative specification style supporting static analysis, simulation and semi-formal techniques

4. Technical feasibility

• Draft LRM well advanced and available for review on the Rosetta website

• Tools in production by multiple vendors and made publicly available• Applications demonstrated in

– traditional silicon modeling

– power-aware design

– security-aware design

– real-time system design

– mechanical system design

– many others

• Texts already available through Morgan Kaufmann

5. Viable volunteer leadershipand participation

• Chair: Perry Alexander• Vice Chair: TBD• Secretary: David Barton• Technical Editor: Peter Ashenden• Other participants from: EDAptive Computing,

Ashenden Designs, Cadstone, Tensilica, Xilinx, NSA, Galois Connections, Intel, Univ. of Kansas, Trento Univ., Univ. of Tennessee, Manchester Univ., and others

6. Realistic objectives

• Much of the base language standard development complete

• Domain specifications: in research form, need to be updated– Dot standard

7. Opportunity to establish new areas of expertise

• Introduces systems engineering to EDA

• Liaison with– IEEE S2ESC,– IEEE Engineering of Computer-Based

Systems TC– IEEE Complex Systems TC (ongoing)– SysML and OMG (ongoing)

IP Issues

• Rosetta language– Developed initially at University of Kansas– Disclosed through publication– No known IP issues

• Draft LRM– Currently © Ashenden Designs– Will assign to IEEE if project approved

• No patent or other IP interest claimed– Developers all understand the need for a standard

Proposed PAR: Scope• Briefly detail the projected output including technical boundaries.

• A standard for the Rosetta specification language and its base collection of domains. The language definition will specify concrete and abstract syntax, denotational semantics for language constructs, and required libraries for AST definition and reflection. The domain definition will specify a collection of base modeling domains required of all Rosetta implementations. The standard document will include both formal definitions and descriptive text.

Proposed PAR: Purpose• Briefly, clearly and concisely explain "why" the document is being created.

• As electronic system complexity continues to grow, so does the need to integrate design information from multiple, heterogeneous design domains, each with their own vocabulary and semantics. Existing design languages typically allow specification of requirements in one or two, predefined domains. In contrast, Rosetta provides support for developing, composing and analyzing specification models from multiple, concurrent domains. Rosetta enables the system-level approach mandated by current design complexity.

Proposed PAR: Reason

• Give the specific reason for the standardization project. Focus on explaining the problem being addressed, the benefit to be provided and the stakeholders for the project.

• In the late 1990’s, the Semiconductor Industry Council identified requirements for a system-level design language motivating Rosetta language development. Rosetta allows systems architects to assess design trade-offs at the system level, mix specifications from multiple domains, and predict emergent interactions between subsystems. It allows system engineers and IP providers to define design constraints as first-class models. Finally, it provides a precise, formal semantics for tool venders supporting formal and semi-formal analysis and integration of analysis results. Rosetta stakeholders recognize the importance of standards in mitigating risk making ad hoc or proprietary languages unacceptable. Thus, a standard is required for wider adoption in industry and academia.

Coordination

• IEC TC93– Liaison member: Alex Zamfirescu

• IEEE Engineering of Computer-Based Systems TC (proposed)

• INCOSE (proposed)

• OMG SysML Committee (proposed)

Schedule

• First draft for WG review: Sep-07

• Draft for ballot: Dec-07

• RevCom submittal: Jun-08

Study Group Results

• Two teleconferences– Updates to the PAR– Development of the report– Development of delivery schedule

• Unanimous approval to send this report and PAR to the DASC SC– 6 of 7 active SG Members voting