Florin Patras
02 July 2009
0 Comments
{
Documentation

It is our strong believe that working software solutions are not complete without full documentation. For this reason we go to great length to document the product throughout the entire development cycle. Code40 acknowledged that defining, designing, developing, testing and deploying have to be thoroughly documented in order to ease client's understanding of the project and to remove the technical information gap between the programming process and operational and maintenance process.

As a first step we encourage our customers to hand over all the documentation effort of the project toward the Code 40 team. Starting with the Product Definition document, as described by the Microsoft Solutions Framework methodology, the project team builds valuable knowledge and insight about the business process and general market conditions in which the product is going to function.

All documentation following the acceptance of the Product Definition is then developed by the Code 40 Technical Authors in tight communication with your organization so that the resulting project artifacts describe the future project to the lowest detail.

Throughout the life cycle of the project the project manager will publish reports and build documentation following intermediate releases which are usually schedules every two weeks.

During the prototyping phase Code40 can provide dedicated teams which constitute a suitable solution for projects that have very volatile specifications. Please see AcceptEmail and SmartPix as reference of projects which we have successfully built in this manner for our clients.

Florin Patras
02 July 2009
0 Comments
{
Maintenance

The software maintenance phase involves changes to the software in order to correct defects and deficiencies found during field usage as well as the addition of new functionality to improve the software's usability and applicability.

Despite the application of various methodologies during development, state of the art development practices do not yet support shipping software that is completely free from defects — and there are good reasons to believe that they will never do so. Even if the development process can eliminate vulnerability issues and defects from final releases, new features can always improve the existing project. Thus, product teams must prepare to respond to newly discovered requirements and features within finalized software.

Nevertheless, this activity of maintenance is notable, considering the fact those two-thirds of a software system's lifetime cost involves maintenance. As such Code40 offers full maintenance support for products developed both in house and by third parties.

Florin Patras
02 July 2009
0 Comments
{
Architecture

The architecture of your future system represents the foundation upon which a successful solution can be built. During the technical specification of the product the initial constraints of the architecture such as: scalability, availability, and feature flexibility are determined. Based on these constraints our Senior Engineers envision the architecture of the product and determine the required technologies.

The structure of the system that we will be creating will most likely employ a sophisticated mix of industry standard design patterns and cutting edge innovations. We draw inspiration from proven solutions and build upon certified framework such as Microsoft Enterprise Library and Microsoft Application Blocks. Throughout the lifecycle of the project our engineers will refine and reengineer the design striving to achieve the best solution.

Code40 holds experienced Architects and Designers, with proved qualities in .NET, BizTalk and Web Applications for the electronic payment industry.

Our practices are based on long commercial experience and are guided by MSF.

Florin Patras
02 July 2009
0 Comments
{
Development

Agile development

In the competitive business world, we have realized that software solutions must be able to adapt to the requirements of the domain without imposing any constraints. Our dedicated teams can become part or your company structure, giving you full control over the project life-cycle.

This is why Code40 was quick to embrace Agile Development methodologies, which are specifically designed to cope with the inevitable changes of the scope which you will encounter while developing your solution. To accommodate this we have chosen a short internal release cycle that will give you the opportunity to steer the course of the project as it is being built.

Through our methodology we can offer you the possibility to capture that unique market opportunity. Our short release cycles mean that you always have a stable and fully working version of the application that you can deploy.

Test Driven Development

The quality and security of the Code40 software is a mandatory requirement. By implementing a solid testing framework and process in place we continuously try to produce a defect free job. We understand that the quality of the software can set the edge for our customers in the market. Fewer bugs mean that we can concentrate more to add features to you applications.

Constant integration

The third pillar of modern application development is the practice of constant integration. Constant integration is designed to discipline development and avoid "big-bang" integration problems that appear in the last stage of development.

The daily builds that we perform automatically represent the pulse of your project. We ensure that you always have access to review the stream of successful daily builds, a clear indication that the application is on the right course. Of course each of the automated build also implies that we run all automated tests.