Our approach to development is to build a framework that supports: consistency, efficiency and scalability. We strive to streamline this process in order to provide our customers with workable solutions that are easy to use and understand. Reaching this goal facilitates open and direct communication between the business model (in practice and management) and the technical specifications (the limits and capabilities of technology). At the end of the day, solutions are only relevant if they actually do something productive.

The initial stage is focused on the determination of the business objectives. This is a reality check: can it be built (practically) and, if so, how? We want to build a strategic outline. To this end, the business analysis is crucial: our project team interacting with our customer's project team. The end result is the specification documentation with the detail of features, functionalities, technologies and timelines providing a strategic scope of the project. This is directly related to the quality and efficiency of the solution.

The planning process is the next critical step. The technical and creative briefs are presented to the client by the project team. These determine the preferences and requirements for the design and technology. The respective project teams (Quimbik & client) analyze the completed briefs and form the basis of the implementation plan. The end result of this phase is the creation of the build specification: detail of exactly what will be built, the technologies that will be used and the project plan with milestones. The systems architecture will be created, refined and ready for the build.

At this stage, Quimbik organizes their build teams, defines the channels of coordination and begins production. Quimbik will have comprehensively analyzed the technologies to be used, the licensing requirements, lead times, performance and compatibility issues. After the alpha version has been built and tested we make the necessary revisions on to the beta version. The client is presented with the beta version for demo & feedback purposes. The information generated from the beta feedback is incorporated and we proceed to quality assurance and load testing. This analysis and testing is carried forward through the rest of the process.

After additional testing, training and final approval from the client, the system/solution is deployed for commercial use. The system/solution goes from the controlled development environment into the open environment. The project team will closely monitor the launch to ensure the performance criteria follow the expectation of the client requirements.

Extend into the future; modifications and enhancements are part of the normal system/solution cycle. Utilization generates defining information for the evolution of technology. Improvements are incorporated; bugs & flaws are corrected platform (upgrades) issues are addressed. We maintain a detailed library of our body of work, emerging technical changes and the change & effect this may hold for our clients. We want to maximize the system/solution performance and customer satisfaction into the future. We see ourselves as your long-term technical partner and provide ongoing support and expertise accordingly.

back to solutions