ArticlesLinksForumAbouthomeFAQSite MapContact
  >> Please select a category

 • Body Of Knowledge

 • Operating Systems

 Windows - Mac OS  
 Migrating to HP-UX / Tru64 UNIX  
 Windows - Linux  
 Unix - Windows  
 Migrating to Sun Solaris  
 Unix - Mac OS X  
 Migrating to Linux  
 Cross-Platform Solutions  
 Java For Mac OS X  

 • OS Versions

 Mac OS 8/9 - Mac OS X  
 Unix Variants - Linux  
 Win16 - Win32  

 • Databases

 FoxPro - DB/2  
 Legacy File Formats - RDBMS  

 • Languages

 VB - VB .NET  
 C/C++ - C#  
 C - Java  
 Fortran/Pascal / Cobol - C/C++  

 • Frameworks/Libraries

 MFC / PowerPlant - wxWindows  
 PowerPlant - Cocoa  

 • Technologies

 J2EE - .NET  
 Migrating to .NET  
 DCOM - .NET Remoting  

 • Development Tools

 MSVC - Codewarrior  

 • Web Platforms

 ASP - ASP .Net  
 JSP - ASP.Net  
 ASP - PHP  
 Apache Tomcat - Web Objects  
 ASP - Web Objects  

 • Miscellaneous

  Suggest a category   
PortingGurus WWW

Body Of Knowledge .



Porting: A Business Decision  

Porting is a significant, if oft-neglected, strategy for software businesses. Multi-platform products have multiple benefits, while bringing with them possible headaches. The porting process itself carries a few risks. In this white paper, we discuss the pros and cons of porting. We also consider some pitfalls, and finally outline options available for porting.


Porting: Test Techniques  

While justifying the need of a separate testing strategy for ported applications, this paper discusses testing methodology for porting projects. Portions of this document talk about the stage-wise testing approach and then elaborate each one to create a substantial and comprehensive process. Best practices gained from practical experiences make this paper a good guide for testing software ports.


Porting: Development Techniques  

This paper discusses software-porting process in details highlighting the steps involved in the process. It also talks about significant issues faced in a typical porting process and suggests appropriate strategies that should be used to make the whole process simpler.


Architecture Reconstruction

Evaluation of an architecture's properties is critical to successful system development. However, reasoning about a system's intended architecture must be recognized as distinct from reasoning about its realized architecture. As design and eventually implementation of an architecture proceed, faithfulness to the principles of the intended architecture is not always easy to achieve. This is particularly true in cases where the intended architecture is not completely specified, documented or disseminated to all of the project members. In our experience, this is the rule and well specified, documented, disseminated and controlled architectures are the exception. This problem is exacerbated during maintenance and evolutionary development, as architectural drift and erosion occur. However, if we wish to transfer our reasoning about the properties of a system's intended architecture to the properties of the implemented system, we must reconstruct the architecture of the realized system.


Reengineering: The Horseshoe Model

Integration between systems has always been difficult; there is little systematic reuse of assets between systems; and new software quickly becomes a liability. In conjunction with the recent architectural reconstruction work, a conceptual "horseshoe" model was developed that distinguishes different levels of reengineering analysis and provides a foundation for transformations at each level, especially for transformations to the architectural level.


Migration Planning

All organizations face the task of migrating from legacy systems to new target systems. Such migration efforts are often complex engineering efforts and require a migration plan to supplement the development plan. The migration plan addresses issues associated with phasing out the legacy systems and moving to the new system. These issues include user interface compatibility, database compatibility, transition support, system interface compatibility, and training. Using a migration plan, a development organization can help a user community make the transition in an orderly fashion.


The OAR Method - Options Analysis for Reengineering

The Options Analysis for Reengineering (OAR) method is a systematic, architecture-centric approach for identifying and mining reusable software components within large, complex software systems.


Reengineering Publications

The following technical reports, technical papers (i.e., conference and workshop papers, book, etc.), and presentations represent the cumulative efforts of various aspects of reengineering being addressed at the SEI. All of the conference and workshop publications are currently in postscript (.ps) or portable document format (.pdf) formats


From One Code Base to Many Platforms Using Visual C++

The Article decribes general porting strategies and guidelines to port code from Windows to MAC OS and UNIX platforms. It also provides an insight on porting Win16 Code to 32-Bit Windows


UNIX Application Migration Guide

Articles cover the different aspects of the migration—including analysis, planning, porting of code, and testing of the migrated application.


The Software Porting Primer

This paper gives the reader a basic understanding of software porting. In it we review the significant issues involved in the development of portable software and in porting existing software to new platforms and computing environments.



Description not available.



Description not available.



Description not available.



home faq site map contact us 

sponsored by: mindfire solutions