1.2. The Porting Process
Developers involved in porting projects tend to follow similar steps when porting any software application. These steps include scoping, analyzing, porting, and testing. Each step in the process builds a foundation for the next step in the process. Each step, when done properly, makes the next step of the process easier to accomplish. Figure 1-1 shows the high-level steps taken during a porting project.
Figure 1-1. High-level steps taken during a porting project
Scoping is the step in which the project manager asks the porting expert and a domain expert to get together to identify the products, development, and test environment the application to be ported relies on. The key areas to identify during the scoping process include product dependencies, development environment components, build environment components, and test environment components:
In most cases, the scoping step leads to identifying associated risks that will be assumed by the project as a whole when it begins. Some risks that can be identified in the scoping step are included in the following scenarios:
Scoping is an involved step in the porting process that takes into account every new piece of information that can be learned from asking the right questionsquestions about documentation, packaging, and performance tuning, to name a few. These and others are mentioned in the "sample porting questionnaire" near the end of this chapter.
There are two views in the analysis step of the porting process: a project management point of view, and a porting point of view. From a project management point of view, analysis is the step that assesses the various porting issues and risks identified in the preceding step and what impact they bring to the porting project as a whole. The analysis step involves the formulation of the project plan, which includes identifying scope and objectives, creating work schedules, procuring resources needed, and assigning roles within the project.
Identification of scope and objectives defines the boundaries and responsibilities of the project manager and the members of the project team. Boundaries are clearly identified sets of work that need to be done for the project. For example, a simple statement such as "Module A in application XYZ needs to be ported and tested on platform B" can be a good start to defining the boundaries of the work.
After boundaries have been identified, tasks for the porting work can be defined, leading to a work breakdown schedule. The work breakdown schedule helps define which tasks need to be done and whether those tasks can be done in sequence or in parallel. In addition, the work breakdown schedule identifies the resources needed. An overall schedule for the entire porting project results from identifying tasks and resources needed.
From a porting point of view, analysis is a step in the porting process during which a porting engineer examines the application architecture in more detail. The porting engineer begins to identify the APIs and system calls used in the application. In addition, the application is assessed as to its use of dynamic linking and loading, networking, threads, and more. This analysis feeds information back to the project manager that can be used to formulate more detailed tasks and accurate schedules.
Porting is the step in the process during which the porting engineers perform their assigned tasks. Depending on the application and the work breakdown schedule that resulted from the preceding step, porting engineers may only be able to work their assigned tasks in a serial fashion. Serial tasks are a product of tightly coupled applications. This means that some modules of the application are highly dependent on other parts of the application and that these modules can be worked on only when the part they depend on is ported. A prime example of this is the build environment. If the build environment was designed to build the whole application as a monolithic procedure, chances are all modules depend on common configuration files that need to be modified before any porting work can be performed.
If the porting tasks are independent of each other, however, the work effort can be parallelized. Loosely coupled modules can be worked on separately and simultaneously by different porting engineers. A key example of this are shared libraries that can be built independently of each other, do not have common components, and exist for other modules to build on. Identifying which tasks can be done in parallel is important and should be done as part of the analysis step of the process.
The porting engineers' task of compiling the code on the Linux platform includes identifying and removing architectural dependencies and nonstandard practices if possible. Identifying and removing architectural dependencies means heeding compiler errors and warnings produced at compile time and correcting them as needed. Removing architectural dependencies and nonstandard practices involves examining and changing the code to use more portable structures or coding standards. Experienced and quality-conscious porting engineers usually do the latter as they correct compiler errors and warnings.
The porting effort includes porting the build environment to the Linux platform, too. This task should be identified during the scoping step. Although some build environments are portable, some are not. Making sure the build environment does not create any potential problems is a task easily overlooked and needs to be scoped and analyzed with extreme caution.
After the application has been portedmeaning it compiles on the Linux platform without errorsthe porting engineer is expected to run unit tests on the application. The unit tests can be as simple as executing the application to determine whether it produces any runtime problems. If runtime problems are detected, they are debugged and fixed before the application is handed to the testing group; the test group then runs more thorough tests on the ported software.
During testing, the assigned testers run the ported application against a set of test cases, which vary from simple execution of the application to stress-type tests that ensure the application is robust enough when run on the Linux platform. Stress testing the application on the target platform is where most porting problems related to architectural dependencies and bad coding practices are uncovered. Most applicationsespecially multithreaded applicationsbehave differently during stress testing on a different platform, in part because of different operating system implementations, especially in the threading area. If problems are found during testing, porting engineers are called in to debug and fix them.
Some application porting may also include porting a test harness to test the application. Porting this test harness is a task that is also identified during scoping and analysis. Most of the time, the testers need to be trained on the application before they can test it. Learning about the application is a task that is independent of the porting tasks and can be performed in parallel.
If bugs are found, they are fixed and the source recompiled; the testing process repeats until the application passes all testing requirements.
When the port is complete, the development phase ends, and the support phase begins. Some of the porting engineers are retained to help answer any porting-specific questions the customer may have. In addition, the developers are expected to train the customer on configuring and running the application on the Linux platform. The typical support phase lasts from 60 to 90 days after the port. During this time, the porting engineers train and answer technical support and sales personnel questions regarding the newly ported application on the Linux environment. After the technical support and sales personnel have been trained in the newly ported product, the porting engineer's task is done.