Software Re-engineering
|
Introducing Options Analysis for Re-engineering (OAR)
Organizations that own or use software assets require a structured and validated approach for making decisions on how to update, migrate, or reengineer their legacy assets. A model has recently been developed to understand technical transformations at different levels of abstraction.
|
|
Difference between Re-structuring and Forward Engineering
Highlighting the difference between Restructuring and Forward Engineering.
|
|
Conclusion drawn from comparison.
Conclusion of the maintenance problems of Hypertext in the light of lessons learned by discussing various characteristics of software development...
|
|
Lessons Learned -- Data quality
Lessons learned by the comparison of small and large scale programming with Hypertext development....
|
|
Lessons Learned -- Version control
Lessons learned by the comparison of small and large scale programming with Hypertext development....
|
|
Lessons Learned -- Reuse
Lessons learned by the comparison of small and large scale programming with Hypertext development....
|
|
Lessons Learned -- Structural Forms
Lessons learned by the comparison of small and large scale programming with Hypertext development....
|
|
Comparison of Large programs with Hypertext..... Contd.
Comparison of Large programs with hypertext in context of various characteristics.
|
|
Comparison of Large programs with Hypertext.
Comparison of Large programs with Hypertext in context of various characteristics.
|
|
Comparison of Small programs with hypertext.... Contd.
Comparison of Small programs with Hypertext in context of various characteristics...
|
|
Comparison of Small programs with Hypertext
Comparison of Small programs with Hypertext in context of various characteristics...
|
|
Hypertext and Software
Software and hypertext comparision.....
|
|
HYPERTEXT GROWTH AND PROBLEMS
Problems caused by extensive growth in Hypertext documents
|
|
Hypertext: The Next Maintenance Mountain
How the need to maintain Hypertext documents is growing day by day
|
|
Y2K MARKET ADAPTING FOR SMALL BUSINESS
Inclination of small-business community towards Y2K fix and evaluation....
|
|
FEDERAL AGENCIES REDEFINE “MISSION-CRITICAL”
Reconsideration and redefination of mission-critical systems by the Faderal Agencies in united states...
|
|
Latin America Faces Y2K Difficulties
Y2K difficulties in Latin America
|
|
Overview of Reflexion Model Technique.. 3
In this article I have discussed the last step of the Reflexion Model technique..
|
|
Overview of Reflexion Model Technique.. 2
This article is the continuation of the previous article.
|
|
Overview of Reflection Model Technique
The software reflexion model technique has been used to support design conformance tasks and to assess system structure
before implementing changes
|
|
Automated And Semi Automated Approaches
Tool-supported reengineering is usually based on bottom-up reverse engineering approaches in which the source code is analyzed and abstractions of the system are produced using automated and semi-automated techniques.
|
|
Reflexion Models for Reengineering
Reengineering large and complex software systems is often very costly. Reflexion models let software engineers begin with a structural high-level model that they can selectively refine to rapidly gain task-specific knowledge about the source code.
|
|
Is the Y2K really THAT big !!!
Year 2000 will have 30 days for the month of February...
|
|
April Fool's Bug in MS Windows!
Microsoft confirms the April Fool's Bug which can hit every Windows PC in the United States in 2001...
|
|
Some of Possible Solutions to the 2000 Problem (4)
Discuses several solutions to the year 2000 problem
|
|
Some of Possible Solutions to the 2000 Problem (3)
Discuses several solutions to the year 2000 problem
|
|
Some of Possible Solutions to the 2000 Problem (2)
Some of the problems relatd to the year 2000 are discussed and the solution is proposed....
|
|
Lessons Learned -- Structural Forms
Lessons learned by the comparison of small and large scale programming with Hypertext development....
|
|
Some of Possible Solutions to the 2000 Problem (1)
Discuses some of the possible solutions to the year 2000 problem .....
|
|
Freshly reported bugs in Non-Y2K complaint software
Freshly reported bugs in Non-Y2K complaint software...
|
|
Networking: Multiplying the error
The Y2K problems get compounded by the degree to which most large computer systems are networked and interdependent....
|
|
List of the Problems
The article discusses the problems involved in fixing the Y2K bug...
|
|
Scope of the Y2K Problems
The Y2K problem is not only limited to personal computers and mainframes, however, most electronic devices that make use of dates will have serious unpredictable problems.....
|
|
Fixing the Y2K Problem
In general, what rules should be followed to fix the problem. The articles doesn't include the technical details.
|
|
The Consequences of the Y2K Problem
In this article, the effects of the Y2K problem have been discussed.
|
|
The History of the Problem (2)
Continuation of the previous article regarding the history of the Year 2000 problem.
|
|
The History of the Y2K Problem (1)
History of the Y2K problem... what caused the problem ... why was it necessary in those days to save space ... costly memory ...
|
|
The Meaning of the Y2K Problem
The meaning of the Y2K problem .... discussion of different conditions which may lead to diferent anomalies.
|
|
The Year 2000 Roadblock - continued 2
What problems the enterprises will face at the offset of the next century and the nature of those problems.
|
| The Year 2000 Roadblock - continued 1 |
| The Year 2000 Roadblock |
| The Year 2000 Problem |
| Software Life-Cycle and Levels of Abstraction |
| What is Legacy Software? |
| Concluding the Reverse Engineering Process |
| Reviewing the Recovered Design and Generating its Documentation |
| Extracting the Control-Flow Information and Creating Diagrams |
| Recording the Data Flow in the Program |
| Recording the Functionality of the Program |
| Reviewing the Collected Information and Extracting the Structure of the Program |
| Collecting Information for the Reverse engineering process |
| Reverse Engineering Procedure |
| Support of program understanding for software maintenance (2) |
| Support of program understanding for software maintenance (1) |
| Software Maintenance |
| Automated support of software maintenance |
| The Design Recovery Process (3) |
| The Design Recovery Process (2) |
| The Design Recovery Process (1) |
| Design Recovery |
| Redocumentation |
| Restructuring |
| Reverse Engineering |
| Re-engineering..... a brief discussion |
Latest Articles