With our strong belief that the success of a software engineering company severely based on a proper process, we implemented the Quade River, the internal development process of Quadesoft. It not only assures us the quality deliverables, but also, gives us a greater flexibility doing what we do best. There had been a time where we were doing many experiments with finding the right process for us. In the beginning for 2007, we were able to mix the best practices of RUP and Agile concepts and create a tailored process unique to us, as we called the “Quade River”. We have seen customers waiting for a release for a longer periods after an official sign-off. After a considerable waiting time, that product they have got could be completely different from what they wanted it to be. To overcome this, a comprehensive requirement workshop could be a solution although it might be a cost and schedule overhead. When it comes to Quadesoft, we address this problem in a different manner. We create a requirement workshop by giving a customer release, as soon as the initial sign-off. That release will be the tool where we craft the application according to the incoming requests. As the customer is being given a release, as soon as the project kicked off, they will have the ability to work with the project from the inception and tailor it according to the needs. We apply the other standard project management methodologies for the above mentioned process. Therefore, we have a PMI (Project management Institute) standard methodology managing core Agile driven process. We have seen an ultimate success in the blend of these two practices.

Project Initialization At every project initialization we take a little time analyze what the basic requirements, what are the current platforms, migration strategies, current business values etc. According to our process, we would not spend more time on the requirement workshop, but we would only gather the minimum information needed to create the basic building blocks of the application. Our technical staff contributes to this process tremendously and their expert judgment will be used extensively. Customer would have a high level feature list at this time for his product and based on the facts we gathered and the feature list, we will initialize a iteration driven project delivery model and deliver the initial release of the project to the customer in no time. We would then use that as the primary tool of requirement engineering and the project will be progressively elaborated from there onwards. Iterative Model After a project kick-off, Quadesoft follows a rapid iterative development model according to our process. By being in the agile concepts, we have short iterations, or sprints, which are limited to 2 weeks to 1 month maximum. At the end of every iteration, customer would get a workable release of the application’s next version. This is based on the agreed feature list at the initial stage. The kind of approach gives the customer greater flexibility on requesting an upcoming feature rather quicker than the planed schedule due to time to market factors. This is one of the key reasons where customers prefer to work with us. Quadesoft uses its own Issue Reporting system. It is used internally in the company for Quality Assurance purposes as well as for customers, for reporting issues upon the customer acceptance of every iteration. Engineering & Development Engineering and architectural approach of every project plays a vital role of project success in Quadesoft. We are capitalizing on this factor by utilizing the best resources we have. With the highly skilled team, we come up with the best solution for every project we undertake. We have internal brainstorm sessions, “Murder Board” sessions and finalize the right technology. While end of the every iteration or sprint we have a code review session to eliminate the problems within the code and it will be applied to the existing code base. Quadesoft maintains its own high coding standards derived from the Microsoft best practices and from our “Lessons Learnt Repositories” in order to preserve the quality nature of the software development.

Quadesoft Data Persistent Framework Quadesoft Data Persistent layer is purely written in C# using Microsoft technologies. It has the ability to connect to any kind of a data source once the correct adapter is extended. It could be utilized for any database driven application with its API, and necessary adapter. We have encountered instances where customers have their data in unorthodox formats. While they wanted to keep those formats unchanged, we have extended our Data Access Layer (DAL) by extending it, by developing a new data adapter for it. The beauty of this is, front-end developers could continue their development by using the API even without the adapter is not present. By using this framework for every development, we have maximized the meaning for reusable components. Quadesoft Content Management Framework As today’s businesses evolve, they move away from the traditional information presentation models. Businesses have more dynamic, ever changing information to be presented via their websites. With the integration of Quadesoft Content Management Framework (QCMF), our customers can manage and manipulate their own data easily and efficiently. QCMF is completely writer in C# based on ASP.NET 2.0 technologies by combining the Quadesoft Data Access Framework, AJAX and many other Open Source technologies. It is being used in every project that needs a CMS and it has its own API for extensibility.

Microsoft Technologies Quadesoft’s first preference always goes to Microsoft when it comes to technology selection. We have exiled in Microsoft technologies over the years and Quadesoft consist Microsoft Certified engineers, which will guarantee our customers, that the product been developed to the quality standards. By having a vision of becoming Gold Partners of Microsoft, Quadesoft highly embrace on cutting-edge technology of Microsoft. Open Source Technologies In Quadesoft, there are many Open Source software been used for various tasks. It had remarkably played a vital role from software development to IT infrastructure management. Some of the Open Source components are the core components of our frameworks. We have engineers who are also identified contributors for famous open source products. While using these for development, we use tools such as VM Ware ESXS Server for our IT infrastructure management.