This panel will lay the foundation for understanding the needs of Large Systems so that OO practitioners can:• appreciate the problems faced;• understand the issues involved; and• re-orient the approaches to provide a viable solution when participating in similar efforts.Specifically, this panel will establish the foundation for discussions on Large Systems by establishing concepts, exposing terminology, and highlighting the state-of-the art.Large applications are usually complex and display one or more of the following dimensions of largeness:• Processing power: requiring tens to hundreds of gigabytes of memory and hundreds of gigaflops performance• High connectivity: highly-connected, systems can show aggregate behavior with complex characteristics: they can become chaotic.• Online access: Archival of terabytes of information, with the need to provide online access to information• Archival and online retrieval: The two technologies (database and archival storage), however, currently do not interoperate. There is a need to develop interfaces to integrate these two technologies.• Data-intensive scientific applications: These involve constructing a data handling infrastructure that simplifies the effort required to maintain petabyte archives, identify relevant data sets within the archive, move, the data to processing platforms, and distribute the data sets across multiple nodes.• Internet access: Large applications often require simultaneous access of information by millions of users worldwide;they must provide acceptable response times.• Scaleable architecture: The systems must be prepared to support exponential growth of application load.Is OOT up to the task? OO practitioners will be encountering some of these application domains in the near future. Some may have already gained some experience in trying to solve these problems. However, the literature in OO does not provide sufficient evidence to believe that OO is ready for such large systems today. Part of the problem is the cross-disciplinary nature of these problems requires a steep learning curve for OO practitioners to be effective. The modeling of these problems with an OO approach is also a challenge. Current 00 methods do not do a good job of supporting multiple views of a domain, and multiple layers of a complex application domain.

Article SafeBots: a paradigm for software security controls Share on Authors: Robert Filman Software Technology Center, Lockheed Martin Missiles and Space, 3251 Hanover Street, O/H1-41 B/255, Palo Alto, California Software Technology Center, Lockheed Martin Missiles and Space, 3251 Hanover Street, O/H1-41 B/255, Palo Alto, CaliforniaView Profile , Ted Linden Software Technology Center, Lockheed Martin Missiles and Space, 3251 Hanover Street, O/H1-41 B/255, Palo Alto, California Software Technology Center, Lockheed Martin Missiles and Space, 3251 Hanover Street, O/H1-41 B/255, Palo Alto, CaliforniaView Profile Authors Info & Claims NSPW '96: Proceedings of the 1996 workshop on New security paradigmsSeptember 1996 Pages 45–51https://doi.org/10.1145/304851.304863Online:17 September 1996Publication History 7citation419DownloadsMetricsTotal Citations7Total Downloads419Last 12 Months1Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access

This paper describes the software architecture and the initial algorithms that have proved to be effective for a real time robot planning system. The architecture is designed to incorporate planning technology from research on artificial intelligence while at the same time supporting the high performance decision making needed to control a fast-moving autonomous vehicle. The symbolic representation of the vehicle's plan is a key element in this architecture. Our initial algorithms use an especially efficient version of dynamic programming to find the best routes. The route is then translated into a symbolic plan. Replanning happens at several levels with the cost of replanning proportionate to the scope of the changes. This software is currently running in an environment which simulates the vehicle and perception systems, but it will be transferred to the DARPA Autonomous Land Vehicle built by Martin Marietta Denver Aerospace [Lowrie 86].

In a distributed office system, authentication data (such as passwords) must be managed in such a way that users and machines from different organizations can easily authenticate themselves to each other.The authentication facility must be secure, but user convenience, decentralized administration, and a capability for smooth, long-term evolution are also important.In addition, the authentication arrangements must not permit failures at a single node to cause systemwide down time.The design used in the Xerox 8000 Series products is described.This design anticipates applications in an opennetwork architecture where there are nodes from diverse sources and one node does not trust authentication checking done by other nodes.Furthermore, in some offices encryption will be required to authenticate data transmissions despite hostile intruders on the network.Requirements and design constraints when applying encryption for authentication in office systems are discussed.It is suggested that protocol standards for use in office systems should allow unencrypted authentication as well as two options for encrypted authentication.Issues that will arise as an office system evolves to deal with increasingly sophisticated threats from users of the system are described.