Protection in programming languages
Communications of the ACM
Procedures as persistent data objects
ACM Transactions on Programming Languages and Systems (TOPLAS)
HOPL-II The second ACM SIGPLAN conference on History of programming languages
The persistent store as an enabling technology for integrated project support environments
ICSE '85 Proceedings of the 8th international conference on Software engineering
Programming with abstract data types
Proceedings of the ACM SIGPLAN symposium on Very high level languages
SYNVER: A system for the automatic synthesis and verification of synchronization processes
ACM '74 Proceedings of the 1974 annual conference - Volume 1
Verifying formal specifications of synchronous processes
POPL '76 Proceedings of the 3rd ACM SIGACT-SIGPLAN symposium on Principles on programming languages
History of programming languages---II
On understanding data abstraction, revisited
Proceedings of the 24th ACM SIGPLAN conference on Object oriented programming systems languages and applications
Web applications: spaghetti code for the 21st century
Web applications: spaghetti code for the 21st century
| Hi-index | 0.00 |
System reliability is an important aspect of operating system construction. Because of this, a number of researchers have proposed design methodologies [e. g., 1, 2, 3] which are intended to produce more reliable software. Although the methodologies differ, there seem to be some important properties that they have in common. One property is the decomposition of the system into components or modules which make as few assumptions as possible about the other components. We will call this the “minimal assumptions” property. Minimizing the assumptions one component makes about another component means that subsequent maintenance and extensions can be done with a smaller probability of introducing errors. A programmer is less likely to overlook critical, obscure interconnections if such interconnections are severely restricted.