Ontological Evaluation of the Requirements Model in IS Reengineering: Shifting From a Traditional To a ComponentBased Paradigm,Used

Ontological Evaluation of the Requirements Model in IS Reengineering: Shifting From a Traditional To a ComponentBased Paradigm,Used

In Stock
SKU: DADAX3838349024
Brand: LAP Lambert Academic Publishing
Sale price$135.44 Regular price$193.49
Save $58.05
Quantity
Add to wishlist
Add to compare

Processing time: 1-3 days

US Orders Ships in: 3-5 days

International Orders Ships in: 8-12 days

Return Policy: 15-days return on defective items

Payment Option
Payment Methods

Help

If you have any questions, you are always welcome to contact us. We'll get back to you as soon as possible, withing 24 hours on weekdays.

Customer service

All questions about your order, return and delivery must be sent to our customer service team by e-mail at yourstore@yourdomain.com

Sale & Press

If you are interested in selling our products, need more information about our brand or wish to make a collaboration, please contact us at press@yourdomain.com

The vast majority of present legacy information systems were implemented using the traditional paradigm that consists of modeling techniques used by system analysts such as System Flow Charts and Data Flow Diagrams (DFD) to capture, during the analysis phase, the activities within a system. However, with recent developments, particularly trends towards eCommerce applications, platform independence, reusability of prebuilt components, many organizations are realizing they will need to reengineer their systems into new component based systems that meet these trends given the limitations of legacy systems to adapt to these new technical requirements. There is a high degree of interest and concern in establishing whether or not a full migration to a more portable and scalable componentbased architecture will be able to represent the legacy business requirements in the underlying requirements model of the reengineered information systems. As a result, this study poses the question: Is the resulting componentbased requirements model ontological equivalent to the legacy requirements model when shifting paradigms in the reengineering process?

⚠️ WARNING (California Proposition 65):

This product may contain chemicals known to the State of California to cause cancer, birth defects, or other reproductive harm.

For more information, please visit www.P65Warnings.ca.gov.

Recently Viewed