| J. Bisbal et al., "Legacy Information Systems: Issues and Directions", IEEE Software, vol. 16, no.5, 1999, pp. 103111. |
....systems evolution problems is the migration, i.e. moving the applications and the databases to new platform and technologies. Migration also is an expensive and complex process. But it greatly increases the IS control and evolution to meet future busi ness requirements. The scientific literature ([3], 4] mainly identifies two migration strategies: rewriting the legacy IS from scratch or migrating by small incremental steps. The incremental strategy allows the migration projects to be more controllable and predictable in terms of deadline and budget. The difficulty lies in the determination ....
Bisbal, J., Lawless, D., Wu, B., Grimson, J.: "Legacy Information Systems: Issues and Directions", 1EEE Software, September/October 1999.
....all of them resulting in an implementation of the system (see Section 3. 1) 2 software prototyping, including data mining, approximate query evaluation, and exploring design alternatives (see Section 4) This research was initially motivated in the context of Legacy Information Systems Migration [4], where the need to identify a sample of an existing operational database is essential to the success of any migration project [23] see Section 4.2.2) It has been reported that as much as 60 [8] of total software development costs are devoted to enhancing existing applications, to add or ....
....application and therefore operational data should be used to populate a prototype database in this context. 4.2.2 Legacy Information System Migration A particular type of information system development project is that of Legacy Information System Migration. This can be de ned as follows [4]. Legacy Information System Migration: Moving an information system to a more exible environment which allows information systems to be easily maintained and adapted to new requirements, retaining original system data and functionality without having to completely redevelop them. In this ....
[Article contains additional citation context not shown here]
J. Bisbal, D. Lawless, B. Wu, and J. Grimson. Legacy information systems: Issues and directions. IEEE Software, 16(5):103-111, September /October 1999.
....a sample of the database [9] Information System Development Data intensive applications development requires prototype databases to support several stages of the development process, e.g. validation, testing, users training. In particular, in the context of Legacy Information System Migration [3], a Sample Database has been identi ed as essential to the success of the migration process [13] Most of these applications of database sampling randomly select the tuples to be included in the Sample. In some cases, e.g. query estimation, this is clearly the appropriate approach as more ....
....information to build a Prototype Database that will support a legacy information system migration project. It remains to be clari ed why, in this context, a Sample of an existing (migrating) database, as opposed to the entire database, must be used. Legacy migration can be de ned as follows [3]: Legacy Information System Migration Moving an information system to a more exible environment which allows information systems to be easily maintained and adapted to new requirements, retaining original system data and functionality without having to completely redevelop them. In the context ....
J. Bisbal, D. Lawless, B. Wu, and J. Grimson. Legacy information systems: Issues and directions. IEEE Software, 16(5):103-111, September/October 1999.
....specify the Feeder System(s) and query(s) to be used to populate the specified record components. It should be noted that the specification of the healthcare record and the queries can only reflect what the Feeder system returns. Feeder Systems are autonomous. They are also commonly legacy systems [Bisbal99], which means they are frequently inflexible providing data to external systems in one single pre defined format. It is not therefore either feasible or desirable for a Synapses Server to dictate new requirements or expect the Feeder System to be re engineered simply to ease co operation with the ....
J. Bisbal, D. Lawless, B. Wu, and J. Grimson. `Legacy Information Systems: Issues and Directions', IEEE Software, 16(5), pp.103-111, Sep./Oct. 1999.
No context found.
J. Bisbal et al., "Legacy Information Systems: Issues and Directions", IEEE Software, vol. 16, no.5, 1999, pp. 103111.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC