FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2134744371> ?p ?o ?g. }

• W2134744371 endingPage "8" @default.
• W2134744371 startingPage "5" @default.
• W2134744371 abstract "ABSTRACT Software re-engineering has become a vital field of computer science and an active research area. The nature of software re-engineering is to improve or transform existing software so it can be understood, controlled and reused as new software. Re-engineering is frequently challenged, because certain risks will threaten the project success. In this article we have described some risks and their classification what we believe to be the most important. From the analysis of risks, some mitigation techniques have been suggested from the existing literature that helps to make the re-engineering projects more beneficial. Keywords Software re-engineering, risks, mitigation, analysis. 1. INTRODUCTION Software Re-engineering is the examination, reorganization, analysis and alteration of an existing software system. It helps to system. The process of restructuring,make them more maintainable and to reconstitute it in a new form and the subsequent implementation of the modified system. This process involves in order to get the target system according to the new the restructuring or recoding of a component or all parts of legacy system without affecting its functionality [1]. Re-engineering is a combination of other processes such as reverse engineering, re-documentation, translation, and forward engineering. The main purpose is to understand the specification, design, implementation of the legacy system and then to implement its modernize form to improve its overall functionality and performance. The difficulty lies in the conceptual understanding of the legacy system. Usually requirements, design and documentation of programming code is no longer available, or is out of date, so it is not clear to the software engineer that what types of functions are to be shifted. Often the software system contains major functions that are not needed anymore, and those should not be re-coded to the new system [2]. The re-engineering process is not risk free and faces various types of risks as software engineering other approaches face. The risk identification is crucial in development and evolution of a legacy system. Risk identification is very important for effective risk assessment, risk analysis, and management and mitigation of risks. In our proposed work, the potential challenges and risks during transformation are analyzed and then categorized on the basis of severity and nature. A well monitoring technique has been described for the categorized risks. It will help a re-engineering system towards successful and easy maintenance and cost benefit with reduced risk." @default.
• W2134744371 created "2016-06-24" @default.
• W2134744371 creator A5084042667 @default.
• W2134744371 creator A5085621925 @default.
• W2134744371 creator A5086160928 @default.
• W2134744371 creator A5090596230 @default.
• W2134744371 date "2013-07-26" @default.
• W2134744371 modified "2023-09-26" @default.
• W2134744371 title "Analysis of Risks in Re-Engineering Software Systems" @default.
• W2134744371 cites W1846166538 @default.
• W2134744371 cites W1984614119 @default.
• W2134744371 cites W1998167229 @default.
• W2134744371 cites W2065140239 @default.
• W2134744371 cites W2119434795 @default.
• W2134744371 cites W2127896511 @default.
• W2134744371 cites W2130593207 @default.
• W2134744371 cites W2135835168 @default.
• W2134744371 cites W2141069252 @default.
• W2134744371 cites W2164753174 @default.
• W2134744371 cites W2171737466 @default.
• W2134744371 cites W2798883694 @default.
• W2134744371 doi "https://doi.org/10.5120/12783-9851" @default.
• W2134744371 hasPublicationYear "2013" @default.
• W2134744371 type Work @default.
• W2134744371 sameAs 2134744371 @default.
• W2134744371 citedByCount "1" @default.
• W2134744371 countsByYear W21347443712017 @default.
• W2134744371 crossrefType "journal-article" @default.
• W2134744371 hasAuthorship W2134744371A5084042667 @default.
• W2134744371 hasAuthorship W2134744371A5085621925 @default.
• W2134744371 hasAuthorship W2134744371A5086160928 @default.
• W2134744371 hasAuthorship W2134744371A5090596230 @default.
• W2134744371 hasBestOaLocation W21347443711 @default.
• W2134744371 hasConcept C115903868 @default.
• W2134744371 hasConcept C199360897 @default.
• W2134744371 hasConcept C2522767166 @default.
• W2134744371 hasConcept C2777904410 @default.
• W2134744371 hasConcept C41008148 @default.
• W2134744371 hasConceptScore W2134744371C115903868 @default.
• W2134744371 hasConceptScore W2134744371C199360897 @default.
• W2134744371 hasConceptScore W2134744371C2522767166 @default.
• W2134744371 hasConceptScore W2134744371C2777904410 @default.
• W2134744371 hasConceptScore W2134744371C41008148 @default.
• W2134744371 hasIssue "11" @default.
• W2134744371 hasLocation W21347443711 @default.
• W2134744371 hasLocation W21347443712 @default.
• W2134744371 hasOpenAccess W2134744371 @default.
• W2134744371 hasPrimaryLocation W21347443711 @default.
• W2134744371 hasRelatedWork W2085861978 @default.
• W2134744371 hasRelatedWork W2104185553 @default.
• W2134744371 hasRelatedWork W2338700700 @default.
• W2134744371 hasRelatedWork W2347547156 @default.
• W2134744371 hasRelatedWork W2356158875 @default.
• W2134744371 hasRelatedWork W2358927215 @default.
• W2134744371 hasRelatedWork W2360518820 @default.
• W2134744371 hasRelatedWork W2367699234 @default.
• W2134744371 hasRelatedWork W2374823395 @default.
• W2134744371 hasRelatedWork W4247880953 @default.
• W2134744371 hasVolume "73" @default.
• W2134744371 isParatext "false" @default.
• W2134744371 isRetracted "false" @default.
• W2134744371 magId "2134744371" @default.
• W2134744371 workType "article" @default.