This case describes the implementation of an online travel management system at FED-AK, the Alaska office of a U.S. government agency. The previous system was intended to accomplish the same functionality, but due to ...
详细信息
This case describes the implementation of an online travel management system at FED-AK, the Alaska office of a U.S. government agency. The previous system was intended to accomplish the same functionality, but due to employee resistance, it was used only as a forms generator in conjunction with a paper- and mail-based process. The new system is integrated, which compels employees to use all the functionality provided. It also incorporates many lessons learned from the old system-in particular, extensive training and online help functions. The system is expected to significantly reduce the cost of travel by minimizing errors, enforcing policies, and reducing transaction costs. The system will also lead to faster reimbursement of employee travel expenses.
In 2006, the University of Alaska Anchorage (UAA) upgraded the telephone system at its main campus in Anchorage from a traditional private branch exchange (PBX) architecture to a Voice over Internet Protocol (VoIP) sy...
详细信息
In 2006, the University of Alaska Anchorage (UAA) upgraded the telephone system at its main campus in Anchorage from a traditional private branch exchange (PBX) architecture to a Voice over Internet Protocol (VoIP) system. This case describes the organizational decisions that led to the change;the scope and the process of upgrading;and the current status of the new VoIP system. The actual migration to VoIP was completed less than a year after the start of the project. The transition process went smoothly. User satisfaction with the performance of the VoIP system is very high. Based on extensive interviews with decision makers and the technical personnel involved, this case also describes financial considerations (including "creative" ways to stretch a limited budget), outsourcing considerations, training related issues, as well as lessons learned.
Component-based software structuring principles are now commonplace at the application level;but componentization is far less established when it comes to building low-level systems software. Although there have been ...
详细信息
Component-based software structuring principles are now commonplace at the application level;but componentization is far less established when it comes to building low-level systems software. Although there have been pioneering efforts in applying componentization to systems-building, these efforts have tended to target specific application domains (e. g., embedded systems, operating systems, communications systems, programmable networking environments, or middleware platforms). They also tend to be targeted at specific deployment environments (e. g., standard personal computer (PC) environments, network processors, or microcontrollers). The disadvantage of this narrow targeting is that it fails to maximize the genericity and abstraction potential of the component approach. In this article, we argue for the benefits and feasibility of a generic yet tailorable approach to component-based systems-building that offers a uniform programming model that is applicable in a wide range of systems-oriented target domains and deployment environments. The component model, called OpenCom, is supported by a reflective runtime architecture that is itself built from components. After describing OpenCom and evaluating its performance and overhead characteristics, we present and evaluate two case studies of systems we have built using OpenCom technology, thus illustrating its benefits and its general applicability.
In the knowledge economy, a firm's intellectual capital represents the only sustainable source of competitive advantage;accordingly, the ability to learn, and to manage the learning process are key success factors...
详细信息
In the knowledge economy, a firm's intellectual capital represents the only sustainable source of competitive advantage;accordingly, the ability to learn, and to manage the learning process are key success factors for firms. The knowledge management approach to learning in organizations has achieved limited success, primarily because it has focused on knowledge as a resource rather than on learning as a people process. Many world-class organizations, such as Procter & Gamble, Cisco systems and Deloitte Consulting, are now employing a new breed of systems known as Learning Management systems (LMS) to foster and manage learning within their organizations(1). This article reports on the deployment of an LMS by a major US multinational, CEM Corporation, and proposes a framework for understanding learning in organizations, which highlights the roles that LMS can play in today's knowledge-intensive organizations.
This paper compares and contrasts the design philosophies and implementations of two computer system families: the IBM S/360 and its evolution to the current zSeries line, and the Tandem (now HIP) Nonstop (R) Server. ...
详细信息
This paper compares and contrasts the design philosophies and implementations of two computer system families: the IBM S/360 and its evolution to the current zSeries line, and the Tandem (now HIP) Nonstop (R) Server. Both systems have a long history;the initial IBM S/360 machines were shipped in 1964, and the Tandem Nonstop System was first shipped in 1976. They were aimed at similar markets, what would today be called enterprise-class applications. The requirement for the original S/360 line was for very high availability;the requirement for the Nonstop platform was for single fault tolerance against unplanned outages. Since their initial shipments, availability expectations for both platforms have continued to rise and the system designers and developers have been challenged to keep up. There were and still are many similarities in the design philosophies of the two lines, including the use of redundant components and extensive error checking. The primary difference is that the S/360-zSeries focus has been on localized retry and restore to keep processors functioning as long as possible, while the Nonstop developers have based systems on a loosely coupled multiprocessor design that supports a "fail-fast" philosophy implemented through a combination of hardware and software, with workload being actively taken over by another resource when one fails.
暂无评论