It appears Grant has provided some pointers to information on the current status of Rosetta. To summarize quickly, the P1699 LRM Subcommittee continues to meet weekly and has discharged over 350 issues in our design database so far. We have released 2 updates to the draft standard this year with a third planned in conjunction with the Rosetta special session at FDL'08. Hopefully we'll have a version for ballot this time next year. Grant has already mentioned the software defined radio work where Rosetta is being used to solve true system-level design problems. In addition, two companies that I am aware of are developing Rosetta tools.
No language that does not deal with design constraints, heterogeneity, and cross-cutting concerns as first-class design issues can rightly be called a system-level design language. This is where we are trying to take Rosetta. There are no exemplars for us to work from, making the task of getting Rosetta where it needs to be exceptionally challenging. That said, we're making progress on the language standard, developing application areas, and prototype tools.
(For full disclosure, I am chair of the IEEE P1699 Rosetta Working Group and Founder of Cadstone, LLC, a developer of Rosetta tools.)
Gabe, you have written an interesting column. I wanted to update what you said about Rosetta and system design a bit (for full disclosure, I am on the board of Cadstone, a company headed by Perry Alexander that is developing Rosetta-based tools). I wouldn't characterise its current status as languishing, but I would say that its current direction is towards true system-level design and away from the EDA and nascent ESL tools industries. There is current work going on in Software-Defined Radio that is really at the system level, discussed on the Rosetta web site at https://wiki.ittc.ku.edu/rosetta_wiki/index.php/Examples
that is a good example. In addition, Perry is talking at FDL 2008 in Stuttgart in September and the standardisation effort via IEEE DASC continues. It just appears to me that this level of system design is so separate from what is done in EDA and ESL that new and different communities of users are likely to be the mainstream for this language and associated tools for a long time to come, and these applications and communities do seem to be developing.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.