Equal rights for functional objects or, the more things change, the more they are the same
ACM SIGPLAN OOPS Messenger
An orthogonally persistent Java
ACM SIGMOD Record
A cooperative approach to support software deployment using the software dock
Proceedings of the 21st international conference on Software engineering
The Java Language Specification
The Java Language Specification
Workgroup Middleware for Distributed Projects*
WETICE '98 Proceedings of the 7th Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
Supporting Distributed Configuration Management in Virtual Enterprises
ICSE '97 Proceedings of the SCM-7 Workshop on System Configuration Management
Coordinated Editing of Versioned Packages in the JP Programming Environment
ECOOP '98 Proceedings of the SCM-8 Symposium on System Configuration Management
Replacing Copies with Connections: Managing Software across the Virtual Organization
WETICE '99 Proceedings of the 8th Workshop on Enabling Technologies on Infrastructure for Collaborative Enterprises
Modular system building with Java/sup TM/ packages
SEE '97 Proceedings of the 8th International Conference on Software Engineering Environments (SEE '97)
Structural unity of product, process and organization form in the GIPSY process support framework
SEE '97 Proceedings of the 8th International Conference on Software Engineering Environments (SEE '97)
| Hi-index | 0.00 |
Emerging technologies such as the Internet, the World Wide Web, Java™ technology, and software components are accelerating product life cycles and encouraging collaboration across organizational boundaries. The familiar coordination problems of large scale software development reappear in a context where tools used by collaborators must be less tightly coupled to one another than before. To the traditional notion of scale, based on the size of software systems, must be added a new dimension of scale: organizational complexity. Designing configuration management systems that scale well over both dimensions requires difficult trade-offs between reliability and flexibility. At the heart of these trade-offs is the aggregate information shared by collaborators: how it is represented, maintained, and understood by the people and tools using it. While designing a prototype development environment intended to scale in both dimensions, we have revisited the role played by naming. A proposed extension to the prototype's naming system addresses issues such as which objects should be named and how the shared naming system is constructed.