TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Date: Mon, 26 Feb 2007 20:43:44 +0000
Reply-To: "Team Ada: Ada Programming Language Advocacy (83 & 95)" <[log in to unmask]>
From: Simon Wright <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Sender: "Team Ada: Ada Programming Language Advocacy (83 & 95)" <[log in to unmask]>
Parts/Attachments: text/plain (21 lines)
On 24 Feb 2007, at 09:06, Zoe Brain wrote:

> I'm doing my PhD on automotive software development. We already  
> have a nice model compiler that takes requirements (not designs)  
> expressed in xtUML and generates Ada-95 systems from them. Contact  
> and ask about their BILBY model compiler.

My experience of xUML (actually its predecessor, and from a  
competitor at that) was that you ended up doing quite a lot of  
design, and even programming -- just not in Ada.

> We hope to apply that to automotive systems soon - measuring  
> footprint, real-time performance and so on. After that, re-jig the  
> model compiler so it produces SPARK-95, and code  that complies  
> with avionics standards and is also formally provable.

Presumably for any really interesting SPARK annotations you'd have to  
decorate the model? The model compiler can make deductions from the  
model but I would have expected them to be about modelling (eg  
multiplicities), not so much about automotive systems.