scispace - formally typeset
Search or ask a question

Showing papers on "Software as a service published in 1989"


Patent
03 Mar 1989
TL;DR: In this article, a central service data-processor system (130) communicating with the customer system (110) and having a data base for converting machine, software, and symptom data into instructions, hardware and software module lists, and service call schedules.
Abstract: Automated problem analysis and resolution of a customer data--processing system uses a central service data-processor system (130) communicating with the customer system (110) and having a data base for converting machine, software, and symptom data into instructions, hardware and software module lists, and service call schedules. The customer system detects data concerning its own configuration and problem symptoms for communication to the service system. The service system itself orders repair modules, and electronically communicates software fixes to the customer system.

15 citations


Proceedings ArticleDOI
27 Nov 1989
TL;DR: An intelligent network which allows software definition of a wider range of objects than has previously been possible is presented and improves efficiency and flexibility in developing a service system and in realizing customized services.
Abstract: An intelligent network which allows software definition of a wider range of objects than has previously been possible is presented. In addition to conventional software definition of customized service specifications, customer environments for this software definition and network functions requiring the services are also software-defined. Software-defining subjects are clearly categorized, according to their skill levels, into system designers, service designers, and customers. Division of the service implementation process, based on this categorization, improves efficiency and flexibility in developing a service system and in realizing customized services. >

12 citations


Proceedings ArticleDOI
H.S. Burns1, R.A. Halliburton1
27 Nov 1989
TL;DR: The authors report on a project designed on the principle that significant advances in software productivity and quality can only come from diverse yet coordinated attacks across many fronts, which lends themselves to building systems that work on an end-to-end basis from nearly the beginning of the development cycle.
Abstract: The authors report on a project designed on the principle that significant advances in software productivity and quality can only come from diverse yet coordinated attacks across many fronts. The two primary fronts link detailed customer involvement with the use of modern software technology options such as object-oriented design and application generators. The authors assert that these technology thrusts lend themselves to building systems that work on an end-to-end basis from nearly the beginning of the development cycle. When coupled with strong customer involvement and living requirements, the system evolves to cleaner, simpler designs that approach the original customer vision. Specifically, the project dealt with technology initiative involving TRANSVU II, a new operations system designed to support telecommunications network providers in the operation of high-capacity largely digital transmission networks. >

6 citations


Proceedings ArticleDOI
R. Cooper1
03 Jan 1989
TL;DR: Some simple facilities for managing a software database are outlined, and implementation techniques equally applicable to more sophisticated systems are described.
Abstract: The use of persistent programming languages to construct tools for maintaining the complex modular structure of large-scale application programs transforms the problem into a database maintenance problem. The application construction environment can be considered to be a database of software libraries, and standard database techniques can be used to handle the modules. The persistent language PS-Algol provides a good basis for manipulating such libraries, as it has the appropriate graphics facilities, first-class procedures, delayed binding, delayed type-checking, strong type-checking and a compiler callable at run-time. It is shown how these features help by concentrating on two issues: module version management and the control over the binding together of two modules. Some simple facilities for managing a software database are outlined, and implementation techniques equally applicable to more sophisticated systems are described. >

5 citations



Journal ArticleDOI
TL;DR: The recent U. S. Supreme Court case BV Engineering v. UCLA copyright infringement litigation illustrates a continuing problem related to software protection, where users may or may not make copies of their purchased or leased software.
Abstract: The recent U. S. Supreme Court case BV Engineering v. UCLA copyright infringement litigation illustrates a continuing problem related to software protection (10). The microcomputer software market continues to expand and technology changes at the same time methods of software protection become obsolete and fail to protect developer's interests. With a steady increase in the size and complexity of software, software costs have become a major concern to the user. As a result, the incentive may not be to develop or purchase new software but instead to steal another's creations and infringe upon another's intellectual endeavors (8). Protection of software from unauthorized use has become a major issue of every software developer. This causes a heated battle among software developers, software lock busters and software users. The dispute is over whether users may or may not make copies of their purchased or leased software.

1 citations