Design of Quality Model during Reengineering of Legacy System

α
bestanil2005
bestanil2005
σ
Dr. Anil Kumar
Dr. Anil Kumar
ρ
Ashok Kumar
Ashok Kumar
α to σ Maharshi Dayanand University
ρ Banaras Hindu University Banaras Hindu University

Send Message

To: Author

Design of Quality Model during Reengineering of Legacy System

Article Fingerprint

ReserarchID

8OKVF

Design of Quality Model during Reengineering of Legacy System Banner

AI TAKEAWAY

Connecting with the Eternal Ground
  • English
  • Afrikaans
  • Albanian
  • Amharic
  • Arabic
  • Armenian
  • Azerbaijani
  • Basque
  • Belarusian
  • Bengali
  • Bosnian
  • Bulgarian
  • Catalan
  • Cebuano
  • Chichewa
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Corsican
  • Croatian
  • Czech
  • Danish
  • Dutch
  • Esperanto
  • Estonian
  • Filipino
  • Finnish
  • French
  • Frisian
  • Galician
  • Georgian
  • German
  • Greek
  • Gujarati
  • Haitian Creole
  • Hausa
  • Hawaiian
  • Hebrew
  • Hindi
  • Hmong
  • Hungarian
  • Icelandic
  • Igbo
  • Indonesian
  • Irish
  • Italian
  • Japanese
  • Javanese
  • Kannada
  • Kazakh
  • Khmer
  • Korean
  • Kurdish (Kurmanji)
  • Kyrgyz
  • Lao
  • Latin
  • Latvian
  • Lithuanian
  • Luxembourgish
  • Macedonian
  • Malagasy
  • Malay
  • Malayalam
  • Maltese
  • Maori
  • Marathi
  • Mongolian
  • Myanmar (Burmese)
  • Nepali
  • Norwegian
  • Pashto
  • Persian
  • Polish
  • Portuguese
  • Punjabi
  • Romanian
  • Russian
  • Samoan
  • Scots Gaelic
  • Serbian
  • Sesotho
  • Shona
  • Sindhi
  • Sinhala
  • Slovak
  • Slovenian
  • Somali
  • Spanish
  • Sundanese
  • Swahili
  • Swedish
  • Tajik
  • Tamil
  • Telugu
  • Thai
  • Turkish
  • Ukrainian
  • Urdu
  • Uzbek
  • Vietnamese
  • Welsh
  • Xhosa
  • Yiddish
  • Yoruba
  • Zulu

Abstract

The purpose of this paper is design such kind of model that will improve the quality of system during reengineering[1] of legacy system that why this model is known as Quality Model. During reengineering of object oriented system[2,3], the methodology is design in such a way that will create a link/bridge between problem detection and problem correction in the legacy system, as well as simultaneously improvement in object oriented design, that can be used during later reengineering and also reduces the complexity as compared to object oriented design [4,5,6]. The further design of legacy system in such a way to specifying, how branches can be selected, how behavior is preserved and how code transformation applied. Quality of model, depends upon two factor favor and disfavor, attach to each branches, software quality is directly proportional to maintenance cost. Quality model is used for two purpose sketch and blueprint. Sketch is used a thinking tool, which help developer communicates, some aspects of a system and alternative about, what are about to be done. Blueprint intends to be comprehensive and definitive. It is used for guiding the implementation.

References

18 Cites in Article
  1. S Muthu,L Whitman,H Cheraghi (1999). Business process reengineering: a consolidated methodology.
  2. Grady Booch,Michael Vilot (1990). The design of the C++ Booch Components.
  3. Rebecca Wirfs-Brock,Brian Wilkerson,Lauren Wiener (1990). Designing Object Oriented Software.
  4. Andreas Flores,Alejandra Cechich,Rodrigo Ruiz (null). Automatic Verification of OOD Pattern Applications.
  5. Martin Fowler (1997). Reusable Simulation Models in an ObjectOriented Framework.
  6. Bertrand Meyer (1997). Object-oriented software construction.
  7. Paolo Tonella (2001). Concept analysis for module restructuring.
  8. Norman Wilde,Ross Huitt (1992). Maintenance support for object-oriented programs.
  9. Paolo Tonella,Giuliano Antoniol (1999). Object Oriented Design Pattern Inference.
  10. Ian Sanjiv Gossain,Graham Object Modeling and Design Strategies.
  11. Thomas Davenport,J Short (1990). The New Industrial Engineering: Information Technology and Business Process Redesign.
  12. Thomas Davenport (1993). Process Innovation: Reengineering work through information technology.
  13. Thomas Davenport (1995). Will participative makeovers of business processes succeed where reengineering failed?.
  14. Martin Fowler (1999). Refactoring: Improving the Design of Existing Code.
  15. J Bosch,P Molin,M Mattson,P Bengtsson (1999). Object oriented frameworks-problems and experiences.
  16. J Bosch (1999). Design of an object-oriented framework for measurement systems.
  17. M Mattsson,J Bosch (1997). Framework composition problems, causes and solutions.
  18. M Mattsson (1996). Object-oriented frameworks survey of methodological issues.

Funding

No external funding was declared for this work.

Conflict of Interest

The authors declare no conflict of interest.

Ethical Approval

No ethics committee approval was required for this article type.

Data Availability

Not applicable for this article.

How to Cite This Article

bestanil2005. 1970. \u201cDesign of Quality Model during Reengineering of Legacy System\u201d. Unknown Journal GJCST Volume 11 (GJCST Volume 11 Issue 8): .

Download Citation

Journal Specifications
Keywords
Version of record

v1.2

Issue date

May 7, 2011

Language
en
Experiance in AR

Explore published articles in an immersive Augmented Reality environment. Our platform converts research papers into interactive 3D books, allowing readers to view and interact with content using AR and VR compatible devices.

Read in 3D

Your published article is automatically converted into a realistic 3D book. Flip through pages and read research papers in a more engaging and interactive format.

Article Matrices
Total Views: 20425
Total Downloads: 10972
2026 Trends
Related Research

Published Article

The purpose of this paper is design such kind of model that will improve the quality of system during reengineering[1] of legacy system that why this model is known as Quality Model. During reengineering of object oriented system[2,3], the methodology is design in such a way that will create a link/bridge between problem detection and problem correction in the legacy system, as well as simultaneously improvement in object oriented design, that can be used during later reengineering and also reduces the complexity as compared to object oriented design [4,5,6]. The further design of legacy system in such a way to specifying, how branches can be selected, how behavior is preserved and how code transformation applied. Quality of model, depends upon two factor favor and disfavor, attach to each branches, software quality is directly proportional to maintenance cost. Quality model is used for two purpose sketch and blueprint. Sketch is used a thinking tool, which help developer communicates, some aspects of a system and alternative about, what are about to be done. Blueprint intends to be comprehensive and definitive. It is used for guiding the implementation.

Our website is actively being updated, and changes may occur frequently. Please clear your browser cache if needed. For feedback or error reporting, please email [email protected]

Request Access

Please fill out the form below to request access to this research paper. Your request will be reviewed by the editorial or author team.
X

Quote and Order Details

Contact Person

Invoice Address

Notes or Comments

This is the heading

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

High-quality academic research articles on global topics and journals.

Design of Quality Model during Reengineering of Legacy System

Dr. Anil Kumar
Dr. Anil Kumar Maharshi Dayanand University
Ashok Kumar
Ashok Kumar Banaras Hindu University

Research Journals