Analysis of Fusion Process Model—Case Study


Fusion Process Model is a software process model to enhance the software development process. Fusion process model have five fundamental phases and one fusion process controller to control and co-ordinate the overall development process. Fusion Process Model uses 3C-Model to generalize the process of solving the problem in each phase. 3C-Model, which helps in implementing component based development approach and provides firmer control over the software development process. Because of the component driven approach, the risk associated with cost and time is limited to component only and ensure the overall quality of software system, reduce the development cost and time by considering the changing requirements of customer, risk assessment, identification, evaluation and composition of relative concerns at each phase of development process. We have implemented Fusion Process Model to the design of a real world information system and evaluated this implementation with the initial project estimation.

Share and Cite:

R. Kaur and J. Sengupta, "Analysis of Fusion Process Model—Case Study," Journal of Software Engineering and Applications, Vol. 5 No. 3, 2012, pp. 119-128. doi: 10.4236/jsea.2012.53019.

Conflicts of Interest

The authors declare no conflicts of interest.


[1] A. Jansen and J. Bosch, “Software Architecture as a Set of Architecture Design Decision,” 5th Working IEEE/IFIP Conference on Software Architecture, Pittsburgh, 6-10 November 2005, pp. 109-120.
[2] J. Lee, “Software Engineering with Computational Intelligence,” Springer Publication, 2003, pp. 183-191.
[3] X. Ferre and S. Vegas, “An Evaluation of Domain Analysis Methods”, 4th CASE/IFIP8 International Workshop in Evaluation of Modeling in System Analysis and Design, 1999, pp. 2-6.
[4] B. Boehm, “Software Engineering Economics,” IEEE Transaction on Software Engineering, Vol. 10, No. 1, 1984, pp. 4-21. doi:10.1109/TSE.1984.5010193
[5] B. Boehm, “A Sprial Model of Software Development and Enhancement,” IEEE Computer, Vol. 21, No. 5, 1988, pp. 61-72. doi:10.1109/2.59
[6] A. Hamid and S. E. Madnick, “Lesson Learned from Modeling the Dynamics of Software Development”, Communication ACM, Vol. 32, No. 12, 1989, pp. 14-26.
[7] J. Ropponen and K. Lyytinen, “Components of Software Development Risk: How to Address Them?” A Project Manager Survey, IEEE Transaction on Software Engineering, Vol. 26, No. 2, 2000, pp. 98-112.
[8] N. Medvidovic and R. M. Taylor, “A Classification and Comparison Framework from Software Architecture Description Languages,” IEEE Transactions on Software Engineering, Vol. 26, No. 1, 2000, pp. 70-93. doi:10.1109/32.825767
[9] R. Kaur and J. Sengupta, “New Approach in Software Development-Fusion Process Model,” Journal of Software Engineering and Applications, Vol. 3, No. 10, 2010, pp. 998-1004. doi:10.4236/jsea.2010.310117
[10] R. Kaur and J. Sengupta, “Development and Analysis of 3C-Model for Software Development Lifecycle,” IEEE 2nd International Conference on Computer Engineering and Technology (ICCET 2010), Chengdu, 16-18 April 2010, pp. 688-691.

Copyright © 2023 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.