About: Change request is a research topic. Over the lifetime, 1262 publications have been published within this topic receiving 15231 citations. The topic is also known as: request for change & modification request.
TL;DR: In this paper, the authors describe a computing system comprising a World Wide Web application (200, 210) with a user interactive record field, which receives a record field entry and responds to a context change request.
Abstract: In one embodiment, the invention of a computing system comprising a World Wide Web application (200, 210) with a user interactive record field is described. The record field receives a record field entry. The application receives a context change request. Responsive to the context change request, the application dynamically transmits the record field entry to a server (255) for storage in a database (290).
TL;DR: In this paper, a system for providing wireless telecommunications services to mobile devices includes structure and functionality for location-based services, and includes both server and client/mobile device apparatuses.
Abstract: A system for providing wireless telecommunications services to mobile devices includes structure and functionality for location-based services, and includes both server and client/mobile device apparatuses. One apparatus includes a data store storing at least a first record associated with a first wireless device or a second record associated with a second wireless device. A computer is coupled to the data store and is configured to receive a request from the first wireless device to obtain location information associated with the second wireless device. The computer is configured to receive a change location privileges request, and to update the first or second records in the data store based on the received change request. Other apparatuses provide additional structures and functions.
TL;DR: In this article, the authors describe techniques for providing information about a current state that is modeled with multiple state attributes, including a request related to the modeling of the current state with the multiple attributes.
Abstract: Techniques are described for providing information about a current state that is modeled with multiple state attributes. In some situations, the providing includes receiving from a module a request related to the modeling of the current state with the multiple state attributes. In such situations, the providing further includes, without further intervention related to the request by the module, determining that the request cannot currently be satisfied, and indicating to the module that the request cannot currently be satisfied, monitoring at later times after the indicating to determine whether the request can be satisfied, and indicating to the module that the request can be satisfied if it is determined at one of the later times that the request can currently be satisfied.
TL;DR: In this paper, the authors present a distributed document version control system that allows the client to take an action with respect to a distributed electronic document, based on a request from the client.
Abstract: Systems and techniques to provide distributed document version control. In general, in one implementation, the technique includes: receiving a request to take an action with respect to a distributed electronic document, identifying, in response to the request, information associated with the distributed electronic document, the associated information indicating a second electronic document different from the distributed electronic document, and imparting information concerning the second electronic document to force the action to be taken with respect to the second electronic document. Receiving the request can occur at a server, and the request can be from a client to take the action with respect to the distributed electronic document, retained locally at the client. The associated information can be retained at the server, and imparting the second document information can involve relating the second document information (e.g., the second document or a link to it) from the server to the client.
TL;DR: The findings reveal that the main causes of requirements volatility were changes in customer needs, developers' increased understanding of the products, and changes in the organization policy.
Abstract: Investigating the factors that drive requirements change is an important prerequisite for understanding the nature of requirements volatility. This increased understanding will improve the process of requirements change management. We mainly focus on change analysis to identify and characterize the causes of requirements volatility. We apply a causal analysis method on change request data to develop a taxonomy of change. This taxonomy allows us to identify and trace the problems, reasons and sources of changes. Adopting an industrial case study approach, our findings reveal that the main causes of requirements volatility were changes in customer needs (or market demands), developers' increased understanding of the products, and changes in the organization policy. During the development process, we also examined the extent of requirements volatility and discovered that the rate of volatility was high at the time of requirements specification completion and while functional specification reviews were conducted.