![]() Will we ever learn anything? Do I even care anymore? I spent the afternoon sifting through web server “5xx” messages before sliding unconscious under the table. Last week, I volunteered to enter results for my local athletics club only to find that a new client-server system had been introduced to “facilitate” this. I expect the perpetrators of these software masterpieces will be busy on self-driving cars by now. In 2022, my neighbour’s car (a different manufacturer) was stolen the same way. In 2020, my car got stolen because some “coder” had decided that keyless was the way to go. We can devote serious intellectual time to a particular software feature only to find the whole thing has been undermined by some clown or other, usually in charge of a spreadsheet. Sometimes it’s not only awful but lethal - you only have to think as far as the Boeing 737 MAX debacle which brought the whole concept of safety-critical software into disrepute. We have a few new languages each decade to get excited about, but we still produce software which even charitably can be awful for no other reason than the management process which produced it. In and amongst all this angst, we don’t seem to have learned very much. ![]() We spend a great deal of time in computer science worrying about computer languages, their constituent symbols and their relative worth. Les Hatton - " Coding with meaningless symbols" ![]() Rust offers several advantages over the traditional use of C or C++, but also poses some new challenges. This talk will reflect on recent experience with Rust, with a particular focus on embedded and real-time systems, formal verification, and the emergence of a commercial ecosystem to support high-assurance development. There is increasing interest in the use of Rust in high-assurance software development. Rod Chapman, Protean Code - " What about Rust for Critical Systems?" But why is that? This presentation will discuss the origins of the C language, its limitations, and what can be done to address them – while leaving the rest of the day for the other presenters to provide alternatives. Location: This event will be held in-person at the Wellcome Collection, 183 Euston Rd, London NW1 2BE and online via Zoom.Īndrew Banks, MISRA - "The C language… you wouldn’t start from here!"ĭespite it’s known issues, the C language remains the go-to language for embedded systems. Nick Tudor, D-Risq - "Auto Code and Auto Verify – Is that all?" Paul Sherwood, Codethink - "Safety for software-intensive systems" ![]() Les Hatton, Kingston University and Oakwood Computing Associates - " Coding with meaningless symbols" Jonathan Pallant, Ferrous Systems stood in for Rod Chapman, Protean Code - "What about Rust for Critical Systems?" ![]() This seminar was held in London and blended online.Īndrew Banks, MISRA - “The C language… you wouldn’t start from here!” This seminar examined the future of coding for safety systems: what languages and techniques are likely to be used, how model-based approaches may be incorporated, what coding standards and guidelines may be applicable, the methodologies employed, and how verification and analysis can be integrated with the process of developing code. THE SAFETY-CRITICAL SYSTEMS CLUB, Seminar: The Future of Coding for Safety-Critical Systems Thursday 9 June, 2022 - London, UK and blended online ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |