Rosetta Hompage

SLDG | Cadstone | EDAptive Computing | Ashenden Designs
[ Systems Level Design ] [ Participation ] [ Stories ]
[ Standard ] [ Overview ] [ Semantics ] [ Interactions ]
[ System-Level Design with Rosetta ] [ System-Level Design Semantics ]
[ Schmidt Trigger ] [ Alarm Clock ] [ Actuator and Spring ] [ Satellite Comm Link ]
[ Introduction ] [ Domain Semantics ] [ Specification Domains ] [ Mechanical Studies ]
[ Rhaskell ] [ ANTLR Java Parser ] [ Simulator ] [ Test Vector Generator ]
[ ITTC ] [ Cadstone ] [ NSF ] [ Rhaskell ] [ InterpreterLib ] [ Thread Pool Monad ]
[ Base Language ] [ Domain ] [ Reflection ] [ Tool Flow ]

System-Level Design

System-level design is characterized by the need to bring together information from multiple domains to predict the impacts of design decisions. To support system-level design, a language must allow heterogeneous specification while providing mechanisms to compose information across domains.

The goal of the Rosetta system-level design language is to compose heterogeneous specifications in a single semantic environment. Rosetta provides modeling support for different design domains employing semantics and syntax appropriate for each. Thus, individual specifications are written using semantics and vocabulary appropriate for their domains. Information is composed across specification domains by defining interactions between them. To achieve this end, Rosetta provides a collection of domains for describing system models called facets. Interactions provide a mechanism for defining constraints between domains.

define system models from one engineering perspective. Facets are written by extending a domain that provides vocabulary and semantics for the model. Using the design abstractions provided by its domain, a facet describes requirements, behavior, constraints, or function of a system.

provide vocabulary and semantics for defining facets. Each domain provides mechanisms for describing data, computation and communication models appropriate for one area of systems design.

define how information from one engineering domain is reflected in another. Domains do not share a common semantics, but instead share information when necessary using interactions. Thus, each design facet is defined using appropriate design abstractions from its domain rather than forcing a common design model across all facets.

expressions use facets, domains and interactions to compose models into system descriptions. Local design decisions can be evaluated from a systems perspective by using interactions to understand impacts in other system domains.

Work on Rosetta is ongoing with this website serving as a clearinghouse for language definition and usage information. The various pages in this site provide definition and tutorial documents as well as examples and standardization information.

Opportunities to Participate

Rosetta is intended to be a community effort. If you are interested in participating in language definition, standards development, tool development or domain semantics, please contact anyone on the Rosetta team for more information.

If you are simply interested in learning more, tracking Rosetta developments or participating in design discussions, three email lists are maintained sharing Rosetta information:

  • Rosetta List - An unmoderated discussion list for Rosetta language and semantics issues. Questions about usage definition should be posted here. To join this list, send email to The ITTC Majordomo Server with subscribe rosetta as the message body. To unsubscribe, use unsubscribe rosetta as the message body. To prevent spamming, you must be a list member to post questions to the list.
  • Rosetta Tools List - An unmoderated discussion list for Rosetta tools available from this site. Questions about tool development and tool usage should be posted here.To join this list, send email to The ITTC Majordomo Server with subscribe rosetta-tools as the message body. To unsubscribe, use unsubscribe rosetta-tools as the message body. To prevent spamming, you must be a list member to post questions to the list.
  • Rosetta Announcements List - A moderated, intentionally low-traffic list for Rosetta related announcements such as tool releases, documentation, and workshops. If you want to track Rosetta developments and announcements without wading through details, this is the appropriate list. To join this list, send email to The ITTC Majordomo Server with subscribe rosetta-info as the message body. To unsubscribe, use unsubscribe rosetta-info as the message body. To prevent spamming, you must be a list member to post questions to the list.

Stories

Cadstone, Inc. develops Rosetta Tools  Cadstone, Inc. has received initial private funding to develop tools for authoring and analyzing Rosetta specifications. Cadstone will concentrate on techniques for applying abstract interpretation to spcecifications.

Rosetta Consortium Forms  A consortium of individuals and companies will formally form in the first quarter of 2006 to complete the Rosetta standard and prepare for IEEE Standardization. If you would like to participate, please contact Perry Alexander or Praveen Chawla

EDAptive Computing wins award   Naval Air Systems Command (NAVAIR) has recently awarded a $46 million Small Business Innovation Research (SBIR) Phase III contract to EDAptive Computing, Inc. (ECI). The ECI CURE effort was spawned by the critical need to reduce time and dollar expenditure in the design, upgrade, and recertification process of weapon and other electronic systems. CURE is executed through a tool suite known as EDASTAR that is based on the System Level Design Language (SLDL), Rosetta. EDAptive EDASTART is a system engineering software tool and methodology that improves the quality (accuracy and completeness) of system designs and reduces the time and complexity for verification of those systems by leveraging Rosetta, an emerging SLDL standard, and ECI proprietary tools and methods.

 

About Us | Site Map | Privacy Policy | Contact Us | ©2005 Perry Alexander