Communications of the ACM
POPL '83 Proceedings of the 10th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Module structure in an evolving family of real time systems
ICSE '79 Proceedings of the 4th international conference on Software engineering
The impact of mesa on system design
ICSE '79 Proceedings of the 4th international conference on Software engineering
Global variable considered harmful
ACM SIGPLAN Notices
Selective and locally controlled transport of privileges
ACM Transactions on Programming Languages and Systems (TOPLAS) - Lecture notes in computer science Vol. 174
Language features for flexible handling of exceptions in information systems
ACM Transactions on Database Systems (TODS)
Experience with a data base of programs
SDE 2 Proceedings of the second ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
A software development environment for law-governed systems
SDE 3 Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
IEEE Transactions on Software Engineering
A procedure and tools for transition engineering
SDE 4 Proceedings of the fourth ACM SIGSOFT symposium on Software development environments
The EACM code performance Anomaly detector
WADAS '91 Proceedings of the eighth annual Washington Ada symposium & summer SIGAda meeting on Ada: software: foundation for competitveness
Dependence Directed Reasoning and Learning in Systems Maintenance Support
IEEE Transactions on Software Engineering
What should we do about the evolution of software: a position paper
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
The main goal of the Darwin software development environment is to establish a rigorous authorization-based discipline which can be used to impose constraints on the structure and operations of software systems as well as on their process of development Such constraints might be desirable to serve the following needs: • The need to provide support and enforcement for such software engineering techniques as informationhiding, data abstraction and modularization, even when these techniques are not offered by the programming language itself. •The need to support rules which govern the real enterprise being served by the system, and which must be invariant of the evolutionary behaviou of the system. • The need to enforce managerial policies concerning the process of system development itself.