Abstract
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.
Highlights
A wide array of process models for organizing the process of software development has emerged over the last few decades
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
Summary
A wide array of process models for organizing the process of software development has emerged over the last few decades. The reuse model follows the component based approach, but this approach is not guided by domain analysis It does not provide complete life cycle for software development because it considers only those systems which can be built using existing components only. Where the software process model approaches divide the development process into various phases/activities or according to functionality These models still don’t follow the technique of technically analyzing the problem, where the technical problems are identified and divided into sub-problems that are first independently solved and later integrated into the overall solution. The solution space analysis approach is still not integrated into software process models It aims to identify the right solution domains for the given problems and extract the relevant knowledge from these domains to come up with a feasible solution.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
