A New Approach to Software Development Fusion Process Model

Rupinder Kaur, Jyotsna Sengupta

.

DOI: 10.4236/jsea.2010.310117                

Abstract

There are several software process models that have been proposed and are based on task involved in developing and maintaining software product. The large number of software projects not meeting their expectation in terms of functionality, cost, delivery schedule and effective project management appears to be lacking. In this paper, we present a new software fusion process model, which depicts the essential phases of a software project from initiate stage until the product is retired. Fusion is component based software process model, where each component implements a problem solving model. This approach reduces the risk associated with cost and time, as these risks will be limited to a component only and ensure the overall quality of software system by considering the changing requirements of customer, risk assessment, identification, evaluation and composition of relative concerns at each phase of development process.

Keywords

Process Model, Fusion Process Model, Component Driven Development Approach, 3C-Model

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1]	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), 16-18 April 2010, Chengdu, China, pp. 688-691.
[2]	W. W. Royce, “Managing the Development of Large Software System,” Proceedings 9th International Conference on Software Engineering, IEEE Computer Society, USA, 1987, pp. 328-338.
[3]	W. S. Humphrey and M. I. Kellner, “Software Process Modeling: Principles of Entity Process Models,” Technical Report, ACM Press, New York, February 1989, pp. 331-342.
[4]	D. Graham, “Incremental Development and Delivery for Large Software System,” IEEE Computers, Vol. 25, No. 11, 1992, pp. 1-9.
[5]	B. Boehm, “Software Engineering Economics,” IEEE Transaction on Software Engineering, Vol. 10, No. 1, 1984, pp. 4-21.
[6]	B. Boehm, “Anchoring the Software Process,” IEEE Transaction on Software Engineering, Vol. 13, No. 4, 1996, pp. 79-82.
[7]	B. Boehm, “A Sprial Model of Software Development and Enhancement,” IEEE Computer, Vol. 21, No. 5, 1988, pp. 61-72.
[8]	B. Boehm and D. Port, “Escaping the Software Tar Pit: Model Clashes and How to Avoid Them,” Software Engineering Note, Vol. 24, No. 1, 1999, pp. 36-48.
[9]	B. Boehm and P. Bose, “A Collaborative Spiral Software Process Model Based on Theory W. Processing of ICSP,” IEEE Press, New York, 1994.
[10]	A. Egyed and B. Boehm, “Analysis of System Requirements Negotiation Behavior Patterns,” 7th Annual International Symposium Engineering, USA, 1997, pp. 269- 276.
[11]	F. P. Deek, J. A. M. McHugh and O. M. Eljabiri, “Strategic Software Engineering: An Interdisciplinary Approach,” Auerbach Publications, USA, 2005, pp. 31-35.
[12]	A. Cline, “Joint Application Development (JAD),” 2010. http://www.carolla.com/ wp-jad.htm
[13]	W. Scacchi, “Process Models in Software Engineering,” Institute for Software Research, University of California, Irvine, October 2001.
[14]	J. Neighbors, “The Draco Approach to Constructing Software from Reusable Components,” IEEE Transaction on Software Engineering, Vol. 10, No. 5, 1984, pp. 564- 574.
[15]	A. Jansen and J. Bosch, “Software Architecture as a Set of Architecture Design Decision,” IEEE Computer Society, 2005, pp. 109-120.
[16]	R. Hilliard, “IEEE Std. 1471 and Beyond,” January 2001, pp. 1-3.
[17]	J. Lee, “Software Engineering with Computational Intelligence,” Springer Publication, New York, 2003, pp. 183- 191,
[18]	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.
[19]	A. Hamid and Madnick, “Lesson Learned from Modeling the Dynamics of Software Development,” Communication ACM, Vol. 32, No. 12, 1989, pp. 14-26.
[20]	J. Ropponen and 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.
[21]	B. Boehm, “Software Engineering Economics,” IEEE Transaction on Software Engineering, Vol. 10, No. 1, 1984, pp. 4-21.
[22]	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.