Integration von Legacy-Systemen mit Electronic Commerce Anwendungen

Immer mehr Unternehmen der Old-Economy (Energieversorgungsunternehmen, Versicherungsunternehmen, Kreditinstitute) öffnen sich dem elektronischen Handel, um einerseits neue Märkte zu erschließen und andererseits bestehende Märkte zu sichern und auszubauen. Im Gegensatz zu Unternehmen der New Economy (Amazon, EBay, Consors), die über eine auf die Anforderungen des Electronic Commerce speziell ausgerichtete Hard- und Softwareinfrastruktur verfügen, haben die Unternehmen der Old-Economy Legacy-Systeme im Einsatz, mit denen sie ihr bisheriges Geschäft unterstützt und abgewickelt haben. Die Daten und Funktionalitäten dieser Legacy-Systeme sollen in neuen zusätzlichen Electronic Commerce Anwendungen zur Unterstützung des elektronischen Handels genutzt werden. Die Möglichkeiten der Integration einer bestehenden Hard- und Softwareinfrastruktur mit neu entwickelten Electronic Commerce Anwendungen sowie die Integration der bisherigen Geschäftsprozesse mit elektronischen Geschäftsprozessen wird in diesem Beitrag beschrieben

Enterprise Computing: Band 1Einführung in z/OS: Band 2z/OS Internet Integration: Band 3Praktische Übungen unter z/OS

Das vorliegende Buch entstand aus einer zweisemestrigen Vorlesung „Enterprise Computing“, die wir gemeinsam über viele Jahre als Teil des Bachelor- oder Master-Studienganges an der Universität Leipzig gehalten haben. Das Buch führt ein in die Welt des Mainframe und soll dem Leser einen einführenden Überblick geben. Band 1 ist der Einführung in z/OS gewidmet, während sich Band 2 mit der Internet Integration beschäftigt. Ergänzend werden in Band 3 praktische Übungen unter z/OS dargestellt

Software maintenance by program transformation in a wide spectrum language

This thesis addresses the software maintenance problem of extracting high-level designs from code. The investigated solution is to use a mathematically-based formal program transformation system. The resulting tool, the Maintainer's Assistant, is based on Ward's [177] WSL (wide spectrum language) and method of proving program equivalence. The problems addressed include: how to reverse engineer from code alone (the only reliable source of information about a program [158]), how to express program transformations within the system, what kinds of transformations should be incorporated, how to make the tool simple to use, how to perform abstraction and how to create a tool suitable for use with large programs. Using the Maintainer's Assistant, the program code is automatically translated into WSL and the transformations, although tested for valid applicability by the system, are interactively applied by the user. Notable features include a mathematical simplifier, a large flexible transformation catalogue and, significantly, the use of an extension of WSL, A4etaWSL, for representing the transformations. MetaWSL expands WSL by incorporating a variety of extensions, including: program editing statements, pattern matching and template filling functions, symbolic mathematics and logic functions, statements for moving within the program’s syntax tree and statements for repeating an operation at each node of the tree. Using MetaWSL, 80% of the 601 transformations can be expressed in less than 20 program statements. The Maintainer's Assistant has been used on a wide variety of examples of up to several thousand lines, including commercial software written in IBM 370 assembler. It has been possible to transform initially unstructured programs into a hierarchy of procedures, facilitating subsequent design recovery. These results show that program transformation is a viable method of renovating old (370 assembler) code in a cost elective way, and that MetaWSL provides an effective basis for clearly and concisely expressing the required transformations

Extraction of objects from legacy systems: an example using cobol legacy systems

In the last few years the interest in legacy information system has increased because of the escalating resources spent on their maintenance. On the other hand, the importance of extracting knowledge from business rules is becoming a crucial issue for modern business: sometime, because of inappropriate documentation, this knowledge is essentially only stored in the code. A way to improve their use and maintainability in the present environment is to migrate them into a new hardware / software platform reusing as much of their experience as possible during this process. This migration process promotes the population of a repository of reusable software components for their reuse in the development of a new system in that application domain or in the later maintenance processes. The actual trend in the migration of a legacy information system, is to exploit the potentialities of object oriented technology as a natural extension of earlier structured programming techniques. This is done by decomposing the program into several agent-like modules communicating via message passing, and providing to this system some object oriented key features. The key step is the "object isolation", i.e. the isolation of .groups of routines and related data items : to candidates in order to implement an abstraction in the application domain. The main idea of the object isolation method presented here is to extract information from the data flow, to cluster all the procedures on the base of their data accesses. It will examine "how" a procedure accesses the data in order to distinguish several types of accesses and to permit a better understanding of the functionality of the candidate objects. These candidate modules support the population of a repository of reusable software components that might be used as a basis of the process of evolution leading to a new object oriented system reusing the extracted objects

Lingnan College Hong Kong : prospectus 1983-1984

https://commons.ln.edu.hk/lingnan_calendar/1004/thumbnail.jp

CASE product evaluation & application in H.K.

by Chu Lung Yan, Cliff, Sung Sai Kit, Edmond.Thesis (M.B.A.)--Chinese University of Hong Kong, 1991.Bibliography: leaf 74.Chapter I. --- OVERVIEW OF STRUCTURED METHODOLOGY & CASE SOFTWARE --- p.1Chapter 1.1 --- Introduction --- p.1Chapter 1.1.1 --- Driving Force behind the CASE evolution --- p.1Chapter 1.1.2 --- Short Review of the CASE technology --- p.2Chapter 1.1.3 --- Benefits of CASE tools --- p.2Chapter 1.1.4 --- CASE Products --- p.5Chapter 1.2 --- Structured Methodology --- p.5Chapter 1.2.1 --- Software System Life Cycle --- p.5Chapter 1.2.2 --- Structured Analysis Methodology --- p.6Chapter 1.3 --- CASE Software Products --- p.9Chapter II. --- PROJECT FRAMEWORK & CASE EVALUATION FRAMEWORK --- p.11Chapter 2.1 --- Project objectives --- p.11Chapter 2.2 --- Methodology --- p.11Chapter 2.2.1 --- Literature Survey --- p.11Chapter 2.2.2 --- Questionnaire --- p.11Chapter 2.2.3 --- In-depth Interview --- p.11Chapter 2.2.4 --- Product Demonstration --- p.11Chapter 2.3 --- CASE Evaluation Framework --- p.12Chapter 2.4 --- Introducing CASE into the organization --- p.14Chapter III. --- PRODUCT EVALUATION --- p.17Chapter 3.1 --- Functional Evaluation of AD/Cycle --- p.19Chapter 3.1.1 --- Functional Overview --- p.19Chapter 3.1.2 --- Functional Description of Selected Products of AD/Cycle --- p.23Chapter 3.1.3 --- How well does AD/Cycle fit in the system development cycle --- p.25Chapter 3.2 --- Technological evaluation of AD/Cycle --- p.35Chapter 3.3 --- Functional evaluation of COHESION --- p.42Chapter 3.3.1 --- Digital's CASE Integration Framework --- p.42Chapter 3.3.2 --- Development Life Cycle Support --- p.44Chapter 3.3.3 --- Function Description on Selected Products --- p.47Chapter 3.4 --- Feature Comparison - Excelerator & DECdesign --- p.52Chapter 3.4.1 --- DECdesign under COHESION --- p.52Chapter 3.4.2 --- Excelerator under AD/Cycle --- p.58Chapter 3.4.3 --- Comparison summary --- p.63Chapter IV. --- APPLICATION OF CASE TECHNOLOGY IN HONG KONG --- p.64Chapter 4.1 --- Mailing Survey - Result summary --- p.64Chapter 4.1.1 --- Survey Result summary --- p.64Chapter 4.2 --- Interview result summaryChapter 4.2.1 --- "Interview IBM, as a CASE user" --- p.66Chapter 4.2.2 --- "Interview DEC, as a CASE user" --- p.68Chapter 4.2.3 --- Interview HongKong Bank --- p.69Chapter 4.2.4 --- Interview IBM CASE consultant --- p.72Chapter 4.3 --- Conclusion --- p.73BIBLIOGRAPHY --- p.74APPENDIX:Chapter A. --- Functional Description on selected products of AD/CycleChapter B. --- Survey resultsChapter C. --- Interview reportsChapter C.1 --- Interview IBM CASE consultantChapter C.2 --- Interview DEC in-house MIS consultantChapter C.3 --- Interview IBM - as a userChapter C.4 --- Interview HongKong BankChapter D. --- Details of Interviewee