Eric J. Byrne, David A. Gustafsson, "A Software Re-engineering Process Model", Proceedings. The 16 th Annual International Computer Software and Applications Conference, IEEE Comput. Soc. Press, 1992, p.25-30.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....indicate that the bottom diagram can be replaced by the top diagram. As such, the implication is that the behavior of G1 is refined by G2. G 2 G 1 Figure 2.1: G1 as an abstraction of G2 Byrne described the re engineering process using a graphical model similar to the one shown in Figure 2. 2 [10, 11]. The process model appears in the form of two sectioned triangles, where each section in the triangles represents a different level of abstraction. The higher levels in the model are concepts and requirements. The lower levels include designs and implementations. The relative size of each of the ....

E. J. Byrne and D. A. Gustafson, "A Software Re-engineering Process Model," in COMPSAC, ACM, 1992.

.... software from the original requirements is considered to be a solution for handling legacy code because much of the functionality of the existing software has been achieved over a period of time and must be preserved for many reasons, including providing continuity to current users of the software [2]. One of the most difficult aspects of re engineering is the recognition of the functionality of existing programs. This step in re engineering is known as reverse engineering. Identifying design decisions, intended use, and domain specific details are often the main obstacles to successfully ....

Eric J. Byrne and David A. Gustafson. A Software Re-engineering Process Model. In COMPSAC. ACM, 1992.

.... the original requirements is considered to be a solution for handling existing (legacy) code because much of the functionality of the existing software has been achieved over a period of time and must be preserved for many reasons, including providing continuity to current users of the software [20]. One of the most difficult aspects of re engineering is the recognition of the functionality of existing programs. This step in re engineering is known as reverse engineering. Identifying design decisions, intended use, and domain specific details are often the main obstacles to successfully ....

E. J. Byrne and D. A. Gustafson, "A Software Re-engineering Process Model," in COMPSAC, ACM, 1992.

.... Re Engineering is the examination and alteration of a system to reconstitute it in 3 a new form, which potentially involves changes at the requirements, design, and implementation levels [5] Byrne described the re engineering process using a graphical model similar to the one shown in Figure 1 [1, 2]. The process model appears in the form of two sectioned triangles, where each section in the triangles represents a different level of abstraction. The higher levels in the model are concepts and requirements. The lower levels include designs and implementations. The relative size of each of the ....

Eric J. Byrne and David A. Gustafson. A Software Re-engineering Process Model. In COMPSAC. ACM, 1992.

....single modules, components or functions of a system. This section is more about which strategy one should use for reengineering a complete system where several modules must be changed. One can t say that one approach is better than another in general since every reengineering project is unique [7]. I ve chosen to call the different approaches redevelopment, partial reengineering and incremental reengineering. 3.2.1 Redevelopment I think this approach is only suitable for smaller systems or when the code for a system is too complex to understand due to poor documentation. What you do if ....

....This has the advantage of being very flexible. The reengineering process can stop whenever it is not cost effective and new features can be tested by the end users as soon as possible. A complete cycle should not span more than a few weeks at the most. The only disadvantage found (Byrne et al.[7]) is that the length of time required to produce the final target system will be longer . Byrne et al. only compares incremental reengineering with his equivalence to redeveloping. However they state that partial reengineering can reduce costs and project time . It seems that Byrne et al. never ....

Eric J. Byrne, David A. Gustafsson, "A Software Re-engineering Process Model", Proceedings. The 16 th Annual International Computer Software and Applications Conference, IEEE Comput. Soc. Press, 1992, p.25-30.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC