Blueprint For Implementation Research Articles

The European digital money picture: Europay’s role and strategy in developing the market

Explores the rapidly changing world of electronic purse transactions and presents a case study of the development strategy employed by Europay International. Considers the impending convergence of European standards and the role of the newly formed CEPSCo Corporation charged with managing the Common Electronic Purse Specification as a blueprint for purse implementations throughout Europe and beyond. Looks at how digital money fits into Europe’s payment industry, identifies common trends and highlights the decisions which must be made by the banking community in order to realize the fastest return on their chip investment.

Linking Strategic Information Systems Concepts to Practice: Systems Integration at the Portfolio Level

Surveys during the past two decades have consistently shown that many of the most critical management concerns with information systems arise at the portfolio, rather than application, level. Architecture-driven planning with a view to the implementation of integrated information systems structures has been widely canvassed as a means of dealing with portfolio-level issues, particularly the problems of inconsistent data and uncoordinated processes which have affected many organizations in recent years. The benefits anticipated from this type of initiative have been such that many organizations have persisted with architecture-based strategies despite reports of high failure rates. This paper reports on some research into IS integration planning in the organization Telstra (formerly Telecom Australia)) during a period of 40 years. The research was conducted as an interpretive case study, with practitioners’ assessments and perspectives on IS planning being incorporated in the data analysis. The focus of the study was on four critical assumptions, which were identified during an initial review of the theoretical literature as having to hold true for an organization to expect success with this form of planning. The study revealed that none of these assumptions held reliably throughout the period studied, a point fundamental to understanding why relatively little progress was made towards published integration targets. The paper then canvasses the view that though traditionally understood as blueprints for implementation, information systems architectures could be reconceptualized as knowledge assets, with independent value as sources of core planning concepts. The conclusion drawn is that their use in this type of role could facilitate the achievement of many, if not all, of the benefits anticipated from more comprehensive approaches.

Linking strategic information systems concepts to practice: systems integration at the portfolio level

Surveys during the past two decades have consistently shown that many of the most critical management concerns with information systems arise at the portfolio, rather than application, level. Architecture-driven planning with a view to the implementation of integrated information systems structures has been widely canvassed as a means of dealing with portfolio-level issues, particularly the problems of inconsistent data and uncoordinated processes which have affected many organizations in recent years. The benefits anticipated from this type of initiative have been such that many organizations have persisted with architecture-based strategies despite reports of high failure rates. This paper reports on some research into IS integration planning in the organization Telstra (formerly Telecom Australia)) during a period of 40 years. The research was conducted as an interpretive case study, with practitioners' assessments and perspectives on IS planning being incorporated in the data analysis. The focus of the study was on four critical assumptions, which were identified during an initial review of the theoretical literature as having to hold true for an organization to expect success with this form of planning. The study revealed that none of these assumptions held reliably throughout the period studied, a point fundamental to understanding why relatively little progress was made towards published integration targets. The paper then canvasses the view that though traditionally understood as blueprints for implementation, information systems architectures could be reconceptualized as knowledge assets, with independent value as sources of core planning concepts. The conclusion drawn is that their use in this type of role could facilitate the achievement of many, if not all, of the benefits anticipated from more comprehensive approaches.

The Case of Leroy Hendricks: A Blueprint for Successful Implementation of a Sexual Predator Statute

The handling and care of dangerous sexual predators has typically been a function of the criminal justice system. Recently, however, the state of Kansas became the focus of a Supreme Court challenge regarding the states' use of civil confinement following the completion of the criminal sanction as it's method for protecting society from dangerous sexual predators. The Court held that the procedure did not constitute double jeopardy, or any other Constitutional violation. Leroy Hendricks, the case principal, the state statute and policy implications are discussed.

Book Reviews

Schabracq, Marc J., Winnibst, Jacques A.M. and Cooper, Cary L., Handbook of Work and Health PsychologyBandura, Albert, Self‐efficacy: the exercise of controlWiggins, Jerry S. The Five‐Factor Model of Personality. Theoretical PerspectivesArredondo, Patricia, Successful diversity management initiatives: a blueprint for planning and implementation

Real-Time Object-Oriented Modeling

The "architecture" of a software system refers to its highest-level modular decomposition and the interrelationship patterns between its modules. An architecture serves as a blueprint for implementation and also as the chief determinant of a system's ability evolve. Consequently, there is an increased interest in methods for specifying and validating software architectures. One such method is based on the ROOM mode ling language which combines the object paradigm with mode ling abstractions devised specifically for distributed real-time software. To overcome the treacherous "architectural decay" phenomenon, whereby, over time, software diverges increasingly from its specification, ROOM formally constrains the implementation to its architectural specification. This is achieved primarily through full automated code generation, a technique that is panicularly challenging in real-time applications where stringent performance and memory requirements are the norm.

Successful diversity management initiatives: a blueprint for planning and implementation

Successful diversity management initiatives: a blueprint for planning and implementation

Real-time object-oriented modeling

Abstract The of a software system refers to its highest-level modular decomposition and the interrelationship patterns between its modules. An architecture serves as a blueprint for implementation and also as the chief determinant of a system's ability evolve. Consequently, there is an increased interest in methods for specifying and validating software architectures. One such method is based on the ROOM mode ling language which combines the object paradigm with mode ling abstractions devised specifically for distributed real-time software. To overcome the treacherous decay phenomenon, whereby, over time, software diverges increasingly from its specification, ROOM formally constrains the implementation to its architectural specification. This is achieved primarily through full automated code generation, a technique that is panicularly challenging in real-time applications where stringent performance and memory requirements are the norm.

Enterprise modeling for CIM information systems architectures: An object-oriented approach

Computer Integrated Manufacturing (CIM) information systems have become extremely important to the global competitiveness of most manufacturing firms. And although much has been written about CIM development and implementation many problems still plague practitioners. For example, lack of integration, islands of automation, sub-optimization of resources, and the inability to migrate to future technology are a few types of problems. Further, few methodologies have been developed that systematically address these issues. In this paper, we outline an Object-Oriented approach to modeling manufacturing enterprises. The approach offers a procedure and techniques for defining CIM information systems architectures which could serve as blueprints for CIM development and implementation in manufacturing enterprises.

Teaching decision makers to learn from scenarios: A blueprint for implementation: Planning Review, 20 (3), 18–22, (May/June 1992)

The insights gained from scenarios will be wasted unless companies effectively integrate them into the decision‐making process.

Teaching decision makers to learn from scenarios: A blueprint for implementation

The insights gained from scenarios will be wasted unless companies effectively integrate them into the decision‐making process.

Specifying an expert system

Abstract The success of numerous expert systems in practical applications warrants a more formal approach to their development and evaluation. Reliability assurance of expert systems requires a methodology for the specification and evaluation of these systems. Expert systems are a new class of software system, but some traditional techniques of software development may be adapted to their construction. However, the specification of an expert system differs from that of a more traditional software program in that parts of the specification are permitted to be only partially described when development starts. Specifications have two important purposes: as contracts between suppliers and clients, and as blueprints for implementation. A specification consists of a problem specification and a solution specification. The problem specification plays the role of contract and states explicitly what the problem to be solved is, and the constraints that the final product must satisfy. The solution specification plays the role of blueprint and has two major aspects: analyzing how a human expert solves the problem, and proposing an equivalent automated solution. We propose an approach to the specification of expert systems that is flexible, yet rigorous enough to cover the important features of a wide range of potential expert system applications. We describe fully each of the components of an expert system specification and we relate specification to the issues of evaluation and maintenance of expert systems.

The Computer Science and Engineering Core Curriculum

The guidelines for developing the CSE model curricula presented in the first paper of this issue were (1) to span the entire spectrum of computer science and engineering and provide the opportunity for in-depth study or specailization in any area of the field; (2) to bridge the traditional gap between hardware and software by emphasizing the interrelationship, common concepts, and inseparability of these two aspects of the field; and (3) to provide a blueprint for specific implementations.

Transformations in Cuban Agriculture After 1959

The Cuban government that took power on January 1, 1959, was going to drastically change rural Cuba. This fact sheet describes the most important agricultural policies during the 1959-1989 period, although in some instances it is necessary to mention events and policies before and after that period. A careful examination of the multitude of policies and agricultural organizations implemented during those 30 years provides an understanding of the confusion arising from the fact that Karl Marx did not leave an implementation blueprint to his followers. This is EDIS document FE481, a publication of the Department of Food and Resource Economics, Florida Cooperative Extension Service, UF/IFAS, University of Florida, Gainesville, FL. Published July 2004. 
 FE481/FE481: Transformations in Cuban Agriculture After 1959 (ufl.edu)