Showing papers on "Implementation published in 2003"

Model-based verification of Web service compositions

Abstract: In this paper, we discuss a model-based approach to verifying Web service compositions for Web service implementations. The approach supports verification against specification models and assigns semantics to the behavior of implementation model so as to confirm expected results for both the designer and implementer. Specifications of the design are modeled in UML (Unified Modeling Language), in the form of message sequence charts (MSC), and mechanically compiled into the finite state process notation (FSP) to concisely describe and reason about the concurrent programs. Implementations are mechanically translated to FSP to allow a trace equivalence verification process to be performed. By providing early design verification, the implementation, testing, and deployment of Web service compositions can be eased through the understanding of the differences, limitations and undesirable traces allowed by the composition. The approach is supported by a suite of cooperating tools for specification, formal modeling and trace animation of the composition workflow.

OMG Data-Distribution Service: architectural overview

Abstract: The OMG Data-Distribution Service (DDS) is an emerging specification for publish-subscribe data-distribution systems. The purpose of the specification is to provide a common application-level interface that clearly defines the data-distribution service. The specification describes the service using UML, thus providing a platform-independent model that can then be mapped into a variety of concrete platforms and programming languages. The OMG DDS attempts to unify the common practice of several existing implementations [2, 5] enumerating and providing formal definitions for the QoS (Quality of Service) settings that can be used to configure the service. This paper introduces the OMG DDS specification, describes the main aspects of the model, QoS settings, and gives examples of the communication scenarios it supports.

Critical success factors of enterprise resource planning systems implementation success in China

Abstract: ERP implementation issues have been given much attention since two decades ago due to its low implementation success. Nearly 90 percent of ERP implementations are late or over budget (Martin, 1998) and the success rate with ERP implementation is about 33%. In China, the success rate of implementing ERP systems is extremely low at 10% (Zhu and Ma, 1999) which is much lower than that in West countries. This study attempts to study critical success factors affecting enterprise resource planning (ERP) systems implementation success in China with focus on both generic and unique factors. User satisfaction and White's ABCD classification method are used to judge whether an ERP system implementation is a success or a failure. Survey methodology and structural equation modeling technique of PLS-graph are used to collect and analyze data. Discussions on the results of data analysis are made.

Strategic issues in customer relationship management (CRM) implementation

Abstract: The number of customer relationship management (CRM) implementations has grown dramatically in recent years. However, few academic studies of the issues associated with the implementation of the concept are available. This paper offers a modest contribution through the analysis of a case study of a CRM implementation at a UK‐based manufacturing company. The case study illustrates that CRM is a complex and holistic concept, organised around business processes and the integration of information technologies. The study also highlights that implementing CRM requires effective leadership, sourcing, targeting and evaluation strategies.

Polychrony for system design

Abstract: Rising complexities and performances of integrated circuits and systems, shortening time-to-market demands for electronic equipments, growing installed bases of intellectual property (IP), requirements for adapting existing IP blocks with new services, all stress high-level design as a prominent research topic and call for the development of appropriate methodological solutions. In this aim, system design based on the so-called "synchronous hypothesis" consists of abstracting the nonfunctional implementation details of a system and lets one benefit from a focused reasoning on the logics behind the instants at which the system functionalities should be secured. With this point of view, synchronous design models and languages provide intuitive (ontological) models for integrated circuits. This affinity explains the ease of generating synchronous circuits and verify their functionalities using compilers and related tools that implement this approach. In the relational mathematical model behind the design language SIGNAL, this affinity goes beyond the domain of purely synchronous circuits, and embraces the context of complex architectures consisting of synchronous circuits and desynchronization protocols: globally asynchronous and locally synchronous architectures (GALS). The unique features of the relational model behind SIGNAL are to provide the notion of polychrony: the capability to describe circuits and systems with several clocks; and to support refinement: the ability to assist and support system design from the early stages of requirement specification, to the later stages of synthesis and deployment. The SIGNAL model provides a design methodology that forms a continuum from synchrony to asynchrony, from specification to implementation, from abstraction to concretization, from interfaces to implementations. SIGNAL gives the opportunity to seamlessly model circuits and devices at multiple levels of abstractions, by implementing mechanisms found in many hardware simulators, while reasoning within a simple and formally defined mathematical model. In the same manner, the flexibility inherent to the abstract notion of signal, handled in the synchronous-desynchronized design model of SIGNAL, invites and favors the design of correct by construction systems by means of well-defined transformations of system specifications (morphisms) that preserve the intended semantics and stated properties of the architecture under design. The aim of the present article is to review and summarize these formal, correct-by-construction, design transformations. Most of them are implemented in the POLYCHRONY tool-set, allowing for a mixed bottom–up and top–down design of an embedded hardware–software system using the SIGNAL design language.

A highly regular and scalable AES hardware architecture

Abstract: This article presents a highly regular and scalable AES hardware architecture, suited for full-custom as well as for semicustom design flows. Contrary to other publications, a complete architecture (even including CBC mode) that is scalable in terms of throughput and in terms of the used key size is described. Similarities of encryption and decryption are utilized to provide a high level of performance using only a relatively small area (10,799 gate equivalents for the standard configuration). This performance is reached by balancing the combinational paths of the design. No other published AES hardware architecture provides similar balancing or a comparable regularity. Implementations of the fastest configuration of the architecture provide a throughput of 241 Mbits/sec on a 0.6 /spl mu/m CMOS process using standard cells.

The Impact of Information Technology Infrastructure Flexibility on Strategic Alignment and Application Implementations

Abstract: IT infrastructure flexibility is now being viewed as an organizational core competency that is necessary for organizations to survive and prosper in rapidly-changing, competitive, business environments. Using data from 200 U.S. and Canadian companies, this study examines the impact of the four components of IT infrastructure flexibility (compatibility, connectivity, modularity, and IT personnel) on strategic IT-business alignment and the extent to which various applications are implemented within an organization. The “extent” of implementation refers to the the organization’s experience with the particular application and the degree to which the application is implemented and used throughout the organization. The findings from analysis of a structural model provide evidence that connectivity, modularity, and IT personnel (among other considerations that we discuss in the paper) make significant, positive impacts on strategic alignment and that all four components result in significant, positive impacts on the applications implementation. The study reinforces the importance of IT infrastructure flexibility to organizations as one source for sustainable competitive advantage.

OMG data distribution service: architectural overview

Abstract: The OMG data-distribution service (DDS) is an emerging specification for publish-subscribe data-distribution systems. The purpose of the specification is to provide a common application-level interface that clearly defines the data-distribution service. The specification describes the service using UML, thus providing a platform-independent model that can then be mapped into a variety of concrete platforms and programming languages. The OMG DDS attempts to unify the common practice of several existing implementations [(M. Boasson et al., July 1993), (Pardo-Castellote et al., 1999] enumerating and providing formal definitions for the QoS (quality of service) settings used to configure the service. This paper introduces the OMG DDS specification, and describes the main aspects of the model.

Planned or Prioritized? Two Options in Managing the Implementation of Strategic Decisions*

Abstract: This paper presents findings from a study of 55 cases of decision implementation. The research identifies a number of features that characterize the way implementation is managed which appear to enhance the chance of success. Analysis reveals patterns in the data indicating that these features fall into two groupings, giving rise to two distinct approaches to implementation management. These are termed the Experience-based approach and the Readiness-based approach from the initial conditions which give rise to each. Although following either approach may enhance decision performance, the greatest success is associated with a dual approach. Implementations that follow neither are generally less successful. A theory of implementation management is postulated, comprising a Planned Option and a Prioritized Option.

Implementation Partner Involvement and Knowledge Transfer in the Context of ERP Implementations

Abstract: Enterprise Resource Planning (ERP) systems are difficult and costly to implement. Studies show that a large portion of the overall implementation cost can be attributed to consulting fees. Indeed, hardly any organization has the internal knowledge and skills to implement an ERP system successfully without external help. Therefore, it becomes crucial to use consultants effectively to improve the likelihood of success and simultaneously keep the overall costs low. In this article the authors draw from agency theory to generate a framework that explains how consultant involvement and knowledge of the implementing organization can impact the outcome of the project. Portions of the framework are illustrated by examples from a series of interviews involving 12 companies that had implemented an ERP. It is suggested that choosing the right consultants and using their skills and knowledge appropriately, as well as transferring and retaining essential knowledge within the organization, is essential to the overall s...

Managerial Issues of Enterprise Resource Planning Systems

Abstract: The primary purpose of this text is to lay out the scope of ERP Systems implementation, explain the competitive advantages of using ERP Systems, and support general concepts with short case studies. This text covers the fundamental issues important in ERP implementation and management, starting from an information systems, information technology project management perspective. Each chapter will include a review of real cases of ERP implementations related to that particular chapter content. The text is meant to be software product independent, in order to enable schools to select their own ERP Systems software tools and use them as time permits. Table of contents Chapter 1: Enterprise Resource Planning SystemsChapter 2: ERP Modules and Historical DevelopmentChapter 3: ERP System Options and Selection MethodsChapter 4: Business Process Reengineering and Best PracticesChapter 5: ERP System InstallationChapter 6: ERP Project ManagementChapter 7: ERP Implementation and MaintenanceChapter 8: Business Intelligence Systems and ERPChapter 9: ERP and Supply ChainsChapter 10: Advanced Technology and ERP SecurityChapter 11: Trends in ERP

Enterprise Resource Planning in a large construction firm: implementation analysis

Abstract: In most large Dutch construction firms, Enterprise Resource Planning (ERP) systems have replaced nonintegrated information systems with integrated and maintainable software. The implementation of ERP systems in such firms is a difficult task. So far, ERP implementations have yielded more failures than successes. This study tries to understand the factors that lead to the success or failure of ERP in large construction firms by focusing on the fits between the following pairs of elements in ERP implementations: business and IT strategy, maturity of the IT infrastructure and the strategic role of IT, and the implementation method and organizational change. The premise of this study is that for an ERP implementation to be successful these elements must somehow fit together. Empirical research was conducted through a case study of three ERP implementations in different business units of a Dutch-based construction firm. Implementing different systems within one company is typical of the way large construction firms in the Netherlands have dealt with ERP. The study shows that the success of ERP implementations depends on consistent patterns between: IT strategy and business strategy, IT maturity and the strategic role of IT, and the implementation method and organizational change.

Analysis and Synthesis of Communication-Intensive Heterogeneous Real-Time Systems

Abstract: Embedded computer systemsare now everywhere: from alarm clocks to PDAs, from mobile phones to cars, almost all the devices we use are controlled by embedded computer systems. An important class of embedded computer systems is that of real-time systems, which have to fulfill strict timing requirements. As real-time systems become more complex, they are often implemented using distributed heterogeneous architectures. The main objective of the thesis is to develop analysis and synthesis methods for communication-intensive heterogeneous hard real-time systems. The systems are heterogeneous not only in terms of platforms and communication protocols, but also in terms of scheduling policies. Regarding this last aspect, in this thesis we consider time-driven systems, event-driven systems, and a combination of both, called multi-cluster systems. The analysis takes into account the heterogeneous interconnected nature of the architecture, and is based on an application model that captures both the dataflow and the flow of control. The proposed synthesis techniques derive optimized implementations of the system that fulfill the design constraints. An important part of the system implementation is the synthesis of the communication infrastructure, which has a significant impact on the overall system performance and cost. To reduce the time-to-market of products, the design of real-time systems seldom starts from scratch. Typically, designers start from an already existing system, running certain applications, and the design problem is to implement new functionality on top of this system. Hence, in addition to the analysis and synthesis methods proposed, we have also considered mapping and scheduling within such an incremental design process. The analysis and synthesis techniques proposed have been thoroughly evaluated using a solid experimental platform. Besides the evaluations, performed using a large number of generated example applications, we have also validated our approaches using a realistic case study consisting of a vehicle cruise controller.

Why some performance measurement initiatives fail: lessons from the change management literature

Abstract: Currently, there is great interest in performance measurement with many companies attempting to implement the balanced scorecard. However, there is also evidence that many of these implementations are not successful. In this second of two papers on performance measurement implementation, the change management literature is reviewed to create a better understanding of why so many initiatives fail. The paper concludes that one reason for the lack of success is that the published processes are all partial processes in that they create the desire for change and provide the first steps for change, but give little guidance on implementation. Another conclusion is that the participative nature of the design process limits the situations in which they should be applied.

System and method for implementing j2ee connector architecture

Abstract: Systems and methods in accordance with the present invention improve upon standard J2EE Connector Architecture implementations by adding functionality not included in the Architecture specification. An improved implementation can include, for example, packaging and development interfaces that allow any J2EE-compliant resource adapter to plug into J2EE applications in a modular manner. A connection manager (102) can provide a scalable application environment that can support a large number of clients requiring access to an EIS. A connection manager (102) can also provide active connection pool management and deployment. A transaction manager (104) can allow transaction management across multiple resource managers, while a resource adapter can provide support for integrated error logging and tracing. A password converter tool (106) can be used with the security management contract to parse and encrypt any passwords in the deployment descriptor.

The effect of national differences on multinational ERP implementation: An exploratory study

Abstract: Previous ERP implementation studies focused primarily on single-site and domestic implementations. The issue of ERP implementation at facilities across nations has been seldom discussed, although industry has indicated such a need. This exploratory study investigates the relationships between national differences and multi-national ERP implementation. Using case research that involves direct observation and systematic interview at four US and Taiwanese manufacturing firms, this study investigates what and how national differences affect implementation practices across nations. The results suggest that language, culture, politics, government regulations, management style, time zone, and labour skills impact several ERP implementation practices. Understanding such effects will enable companies to be more proactive in planning for multinational ERP implementation. Managerial implications of the findings and future research issues are discussed.

Roadmapping in the Corporation: Product-Technology Roadmaps Define and Communicate Product and Technology Strategy along with a Longer, Smarter View of the Future

Abstract: In a corporation, an important need for roadmapping is at the product-line level. Product-Technology Roadmaps in the corporate setting are used to define the plan for the evolution of a product, linking business strategy to the evolution of the product features and costs to the technologies needed to achieve the strategic objective. This article describes the experience of Lucent Technologies in deployment and use of the roadmapping methodology during the past several years. A small group shepherded the deployment and use of roadmaps during that time, and the format and application described here have evolved with the experience gained. Deploying roadmaps across a corporation helps achieve several key objectives. For each product line, roadmaps link market strategy to product plans to technology plans. Roadmaps created at the product line level are the base for corporate technology planning, identifying needs, gaps, strengths and weaknesses in a common language across the corporation. Roadmaps help focus attention on longer-term planning and improve communication and ownership of plans. Finally, the process helps focus a team's thinking on the few most important priorities at each step of the planning process: * Linking strategy to product plans to technology plans.--Creating the roadmap story means explicitly describing the why's for each key decision in the plan. Typically, strategies, product plans and technology plans are created independently by the people responsible for them. Roadmaps explicitly create the linkages, first linking strategic choices based on market needs and the competitive environment to product evolution and feature implementations, and then linking product plans to technology implementation plans. * Enabling corporate-level technology plans.--With roadmaps for several product lines, it is possible to look across the roadmaps for common needs that may be met by a single development program or technology acquisition. This can be done by analyzing a database of roadmaps or with cross-roadmap reviews where product teams come together to identify common needs. Time-to-market improvements and other platform opportunities can result. Besides overlaps, cross-roadmapping activity can address hidden gaps and identify key strengths that can be deployed in other areas of the business. * Focus on longer-term planning.--Today's business climate can lead to a focus on short-term thinking, often tied to the reporting needs of the budget cycle or the next deliverable. Roadmapping helps to focus the attention of the team on future product generations, initiating longer-term projects or technology acquisitions so that their outputs will be ready when needed. For technologies with long lead times, the choice to develop or acquire is a near-term decision with long-term consequences. * Improving communication and ownership of plans.--The use of a cross-functional team to create a product line plan allows the members of the team to develop a shared plan. All share in the creation of the plan, developing ownership across functions. Roadmapping provides a common vocabulary that is shared across the team with diverse backgrounds such as product management, marketing, sales, research and development, manufacturing, project management, logistics, etc. The team develops its roadmap in a step-by-step fashion, building on each team member's special knowledge. The process is usually iterative, as the team realizes that the plan it has set out is not feasible or that there is a better alternative. * Focus planning on the highest-priority topics.--A key goal of roadmapping is to identify and focus strategy and product development on the few most important elements for success. At every stage of roadmap development, the group strives to define the two or three most important drivers, elements or issues. In this way, the focus is kept on identifying the highest priorities. As the roadmap is developed and implemented, the team identifies gaps and the actions to close the gaps. …

Technology Roadmapping: Roadmapping the Corporation

Abstract: Product-technology roadmaps define and communicate product and technology strategy along with a longer, smarter view of the future. In a corporation, an important need for roadmapping is at the product-line level. Product-Technology Roadmaps in the corporate setting are used to define the plan for the evolution of a product, linking business strategy to the evolution of the product features and costs to the technologies needed to achieve the strategic objective. This article describes the experience of Lucent Technologies in deployment and use of the roadmapping methodology during the past several years. A small group shepherded the deployment and use of roadmaps during that time, and the format and application described here have evolved with the experience gained. Deploying roadmaps across a corporation helps achieve several key objectives. For each product line, roadmaps link market strategy to product plans to technology plans. Roadmaps created at the product line level are the base for corporate technology planning, identifying needs, gaps, strengths and weaknesses in a common language across the corporation. Roadmaps help focus attention on longer-term planning and improve communication and ownership of plans. Finally, the process helps focus a team's thinking on the few most important priorities at each step of the planning process: Linking strategy to product plans to technology plans.-Creating the roadmap story means explicitly describing the why's for each key decision in the plan. Typically, strategies, product plans and technology plans are created independently by the people responsible for them. Roadmaps explicitly create the linkages, first linking strategic choices based on market needs and the competitive environment to product evolution and feature implementations, and then linking product plans to technology implementation plans. Enabling corporate-level technology plans.-With roadmaps for several product lines, it is possible to look across the roadmaps for common needs that may be met by a single development program or technology acquisition. This can be done by analyzing a database of roadmaps or with cross-roadmap reviews where product teams come together to identify common needs. Timeto-market improvements and other platform opportunities can result. Besides overlaps, cross-roadmapping activity can address hidden gaps and identify key strengths that can be deployed in other areas of the business. Focus on longer-term planning.-Today's business climate can lead to a focus on short-term thinking, often tied to the reporting needs of the budget cycle or the next deliverable. Roadmapping helps to focus the attention of the team on future product generations, initiating longerterm projects or technology acquisitions so that their outputs will be ready when needed. For technologies with long lead times, the choice to develop or acquire is a near-term decision with long-term consequences. Improving communication and ownership of plans.The use of a cross-functional team to create a product line plan allows the members of the team to develop a shared plan. All share in the creation of the plan, developing ownership across functions. Roadmapping provides a common vocabulary that is shared across the team with diverse backgrounds such as product management, marketing, sales, research and development, manufacturing, project management, logistics, etc. The team develops its roadmap in a step-by-step fashion, building on each team member's special knowledge. The process is usually iterative, as the team realizes that the plan it has set out is not feasible or that there is a better alternative. Focus planning on the highest-priority topics.-A key goal of roadmapping is to identify and focus strategy and product development on the few most important elements for success. At every stage of roadmap development, the group strives to define the two or three most important drivers, elements or issues. …

Analyzing ERP Implementation at a Public University Using the Innovation Strategy Model

Abstract: Enterprise Resource Planning (ERP) systems have revolutionized the way companies are using information technology in their businesses. ERP was created in an effort to streamline business processes and has proven to be successful in many operations. Unfortunately, not all ERP implementations have met expectations. One way that businesses may be able to increase success rates is to embrace creativity and innovation in their ERP implementations. For businesses to do this, they must first understand how creativity originates and how that creativity can be integrated into business solutions. This article presents a case study that examines the ERP implementation at a public university and analyzes the applicability of the Innovation Strategy Model on public sector organizations.

Smart shopper: an agent-based web-mining approach to Internet shopping

Abstract: This paper presents an agent-based Web-mining approach to Internet shopping. We propose a fuzzy neural network to tackle the uncertainties in practical shopping activities, such as consumer preferences, product specification, product selection, price negotiation, purchase, delivery, after-sales service and evaluation. The fuzzy neural network provides an automatic and autonomous product classification and selection scheme to support fuzzy decision making by integrating fuzzy logic technology and the backpropagation feed forward neural network. In addition, a new visual data model is introduced to overcome the limitations of the current Web browsers that lack flexibility for customers to view products from different perspectives. Such a model also extends the conventional data warehouse schema to deal with intensive data volumes and complex transformations with a high degree of flexibility for multiperspective visualization and morphing capability in an interactive environment. Furthermore, an agent development tool named "Aglet" is used as a programming framework for system implementation. The integration of dynamic object visualization, interactive user interface and data mining decision support provides an effective technique to close the gap between the "real world" and the "cyber world" from a business perspective. The experimental results demonstrate the feasibility of the proposed approach for Web-based business transactions.

System and method for multiplatform implementation of abstract software modules in peer-to-peer network environments

Abstract: System and method for multiplatform implementation of abstract software modules in peer-to-peer networking environments. A module class may have one or more module specifications. Each module specification may have one or more module implementations configured to execute within a particular execution environment. A unique module class identifier may be assigned to the module class. A unique module specification identifier may be assigned to each module specification of the module class. In one embodiment, a module specification advertisement may be generated for each module specification. A module implementation advertisement may be generated for each module implementation. In one embodiment, the module specification identifier of the corresponding module specification is included in each module implementation advertisement.

Methods of teaching a computer science course for prospective teachers

Abstract: This article focuses on a "Methods of Teaching Computer Science in the High School" course (abbreviated MTCS). It presents the rationale and need for the course, and suggests optional course frameworks and implementations that are not limited to a particular programming language, programming paradigm, level of students, or curriculum.

Towards a General Relation Browser: A GUI for Information Architects

Abstract: The paper presents the case of ongoing efforts to develop and test generalizable user interfaces that provide interactive overviews for large-scale Web sites, portals, and other partitions of Web space. The interfaces are called Relation Browsers (RB) because they help people explore the relationships across different attribute sets, thus enabling understanding the scope and extent of the corpus through active exploration of different "slices" defined by different attribute value juxtapositions. The RB concept is illustrated through discussion of six iterations over a five year period that included laboratory usability studies, a field test, and implementations with a variety of data management problems. The current application to design concepts in a digital government setting is discussed, and the concept of the RB as the basis for an interface server is presented.