Java implementation strategy of software engineering

Because of the many features of the Java language and the popularity of internet and embedded systems, Java porting of software that has been put into use in C + + language has become more and more significant in software activities and the particularity of this activity process, For the process of management control and development methods and traditional software activities are different, so discussed the strategy for porting, and a transplant project---LED navigation system transplant as an example to prove the effectiveness of these strategies?

Keywords: Software engineering; Java; Software methods

1th Chapter Introduction

Because of the interpretive nature of Java, portability, platform independence, and security, Java has become more widely used in applications such as embedded systems, which have high requirements for cross-platform and security. For enterprises and institutions, the original system for Java transplant, On the one hand, can avoid the high cost of the system redevelopment, the long cycle? System integration and other adverse factors, on the other hand, can realize the smooth transition of the system, to achieve a smaller cost system upgrade? Therefore, the adoption of software engineering strategy to guide the process of the entire system is very meaningful?

Chapter 2nd Transplantation Program

The porting scheme can be divided into 3 categories: functional porting, system structure porting and complete porting of implementation.

(1) Function transplant: Discard all logic and language structure, reuse target language to realize the function of source engineering? The target engineering features produced by a functional transplant are independent of the source engineering and are conducive to the production of high-quality code and easy maintenance of the project. But is a functional transplant more like a new development process than a porting process? Its management is similar to the traditional software process, with various lifecycle models and object-oriented software methods available.

(2) System structure transplant: In the class? At the package level, the general interface and logical structure of the source engineering are retained, and their implementation is rewritten. For a source project that has undergone the whole life cycle, the system logic structure is basically satisfied, and the porting of system structure can be based on the basic structure of retaining source engineering. To achieve high quality of target engineering? But there must be a deep understanding of the function of the structure and the links between it, and it is noteworthy that if the programmer's understanding is biased, the result can be catastrophic and difficult to fix.

(3) Complete porting: Preserving the logical structure of source engineering to preserve its language structure as far as possible? Source engineering code Reuse degree is high, transplant work machine simple? Programmers only need to have a general understanding of the overall structure, and their attention can be completely focused on their work? Development progress can be measured accurately, the cycle is short? High efficiency? However, the quality of the target project generated by the full porting is not superior to the source engineering? If the lack of effective management, it is difficult to ensure the quality of the project? Based on the above reasons, this article mainly discusses the implementation of the full migration strategy? There are no special instructions, and the porting activity below refers to the complete porting of the implementation.

3rd Chapter Pretreatment

If you are porting only part of the source engineering functionality, you can effectively reduce the number of code that needs to be ported by using code definitions to retain the structure you need to migrate? This process is simple, only for the source engineering of all the retention functions of the structure of the pass and record the call structure, which is not recorded can be defined outside the scope of the transplant?

Define the number of valid lines of code in the 1:step-code, which is a simple measure of system size?

LED aerial display system transplant project using this definition, the amount of engineering code from the original 13362steps, reduced to the definition of 11069steps? Effectively reduce the workload?

It should be noted that if the developer of the source project is designated as a porting programmer, the time of this process can be greatly shortened, or even skipped over this process? LED aerial display System transplant project, we used 1 people/month to do this phase is enough to ensure the correct transplant knowledge?