GenFusion, LLC. uses the CarbonFuseTM methodology as a technique for developing business system requirements. Using CarbonFuseTM allows for an effective method of gathering requirements and building system designs. Following this methodology we reduce development time, costs and software errors.
The CarbonFuseTM process begins at the beginning of the project lifecycle assisting our clients in making decisions and analyzing problems. We have utilized the CarbonFuseTM methodology to help our clients assess the role or direction of their organization or business area. The CarbonFuseTM methodology is composed of four separate fuses known as requirements, design, develop, and test.
Requirements: Upon gathering our client’s needs we transform them to business requirements in which we group together to start our Design fuse. This step in the process is known as our Requirements fuse.
Design: In the Design fuse, we take the business requirements we have gathered in the Requirements fuse and start breaking them into technical requirements using the Unified Modeling Language (UML). This is an industry standard language for specifying, visualizing, and documenting the artifacts of software systems. It creates a “blueprint” for the construction of the application and creates traceability between the technical requirements and our client’s business requirements. This leads us to faster development and because this is an industry standard language, we use it to effectively communicate with all members of our team.
Develop: The Develop fuse begins with the start of development and during this fuse we are also writing unit tests on our code. This ensures an appropriate testing method for each smaller section of the application, allowing us to regression test if we further develop these sections in the future. This step allows us to quickly pinpoint any imperfections and resolve them efficiently.
Test: Upon completing all cycles of development we move into our next fuse of this process which is the Test fuse. This fuse tests our application with the client’s end users as well as a full system test. Using an issue-tracking tool allows our software testers to document any issues with the application they find and our developers to resolve those issues quickly and effectively. At the completion of this phase we have a final sign-off from our testers and from our client’s as we release our application into the public domain.