![]() ![]() This is bad because we are enforcing implementation decisions at the requirements level. Our only choice is to over-specify the requirement by defining how this fairness is to be achieved (for example, by explicitly queueing the requests). However, if the requirements are now refined to state that every request must be eventually served (this is a fairness requirement which we cannot express in a safety-only semantic framework). This is easily specified without liveness. The order in which these requests are processed is required to be nondeterministic. This database must handle multiple, parallel requests from clients. Paul Gibson, Dominique Méry, in Object-Oriented Technology and Computing Systems Re-engineering, 1999 9.1.2 Temporal logic and livenessĬonsider the specification of a shared database. Such systems currently have millions of registered users. ![]() Shared-database systems have become very popular in all types of organizations in the past decade, however. Similarly, workers in the technical support area were also able to benefit from the product because they were also not subject to the competitive environment that most consultants worked in. They were used to working together, and the shared database system supported their efforts. Those at the top were able to make good use of the product because they were beyond the competition that marked the rest of the firm. In one interesting case, in a consulting firm where information was highly valued and was therefore kept private, the only groups that were successful in using a shared database system were those at the very top of the organization and those in the technical support area. Furthermore, in organizations where the reward structure is based on keeping information personal and private, the introduction of groupware alone is not capable of instilling an atmosphere of sharing and trust. In situations where people do not understand the possibilities for groupware, they will either use it the same way they use stand-alone software tools or they will not use it at all. To those who had not been properly educated to understand the communication and collaboration aspects of groupware, the tools seemed to be like other stand-alone tools they were already familiar with, such as e-mail. When these systems were first available in the late-1980s, people in adapting organizations were not quite sure what to make of them. George, in Encyclopedia of Information Systems, 2003 B Shared DatabasesĪ similar history exists for shared databases. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |