Proof techniques for hierarchically structured programs
Communications of the ACM
IEEE Transactions on Computers
An alternative to chaos or maintainable systems
ACM-SE 15 Proceedings of the 15th annual Southeast regional conference
The relationship between design and verification
Journal of Systems and Software
Software development for reliable software systems
Journal of Systems and Software
The functional life cycle model and its automation: USE.IT
Journal of Systems and Software
Software requirements and specifications: A survey of needs and languages
Journal of Systems and Software
| Hi-index | 0.03 |
The key to software reliability is to design, develop, and manage software with a formalized methodology which can be used by computer scientists and applications engineers to describe and communicate interfaces between systems. These interfaces include: software to software; software to other systems; software to management; as well as discipline to discipline within the complete software development process. The formal methodology of Higher Order Software (HOS), specifically aimed toward large-scale multiprogrammed/multiprocessor systems, is dedicated to systems reliability. With six axioms as the basis, a given system and all of its interfaces is defined as if it were one complete and consistent computable system. Some of the derived theorems provide for: reconfiguration of real-time multiprogrammed processes, communication between functions, and prevention of data and timing conflicts.