How Accurate is Scientific Software?
IEEE Transactions on Software Engineering
A survey of software inspection checklists
ACM SIGSOFT Software Engineering Notes
Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis
Using symbolic execution for verifying safety-critical systems
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
C++ in safety critical systems
Annals of Software Engineering
The T Experiments: Errors In Scientific Software
IEEE Computational Science & Engineering
How Goes CSE? Thoughts on the IEEE CS Workshop at Purdue
IEEE Computational Science & Engineering
A Critical Look at Quality in Large-Scale Simulations
Computing in Science and Engineering
Reexamining the Fault Density-Component Size Connection
IEEE Software
Does OO Sync with How We Think?
IEEE Software
Exploring the Role of Diagnosis in Software Engineering
IEEE Software
Methods and Languages for Safety-Related Real-Time Programming
SAFECOMP '98 Proceedings of the 17th International Conference on Computer Safety, Reliability and Security
Fine grained patterns for real-time systems
UML for real
SCS '04 Proceedings of the 9th Australian workshop on Safety critical systems and software - Volume 47
Language subsetting in an industrial context: A comparison of MISRA C 1998 and MISRA C 2004
Information and Software Technology
A direct path to dependable software
Communications of the ACM - A Direct Path to Dependable Software
Managing Complexity in Software Development with Formally Based Tools
Electronic Notes in Theoretical Computer Science (ENTCS)
Embedded System Paranoia: a tool for testing embedded system arithmetic
Information and Software Technology
Stop the software architecture erosion: building better software systems
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
| Hi-index | 0.00 |
From the Publisher:Software failure in high-profile areas, such as aerospace, defence and medicine frequently makes the headlines because of the potentially disastrous consequences. The huge and recent growth in the use of software development has particularly serious implications for such safety-critical and high-integrity systems. Despite its popularity and the excellent tool support available, C is only suitable for use in these areas within firm constraints and guidelines. Safer C: Developing Software for High-integrity and Safety-critical Systems highlights the 'holes' in C, but also demonstrates clearly that, employed correctly, C can be used to write software of as high intrinsic quality as other languages. Beginning with a broad overview of safety in software, the book provides a critique of C as a safety-critical language, based on the author's extensive measurements of commercial C quality. Complexity, safer subsets, standards and tools are all examined. Essential rules of good working practice and guidelines for immediate implementation are presented and a direct comparison is made of specific safety-related features in C and other commonly-used languages. This important and timely book contains vital information for all developers working with C, whether in high-integrity areas or not, who need to produce reliable and effective software. Special features include: much needed guidance for all software developers using C, not just those working on high-integrity and safety-critical systems; practical points for immediate implementation based on the use of safer subsets; and an examination of poorly understood legal implications of software safety and references to standards throughout.