software architects

Development Methodology

We study in detail the needs of your project to determine the best solution at the level of architecture and technology. We remain neutral on the technology decision, our experience covers both a variety of operating systems (Windows family and Linux / Unix in particular) and development environments (C, Java, C #, PHP, XML / SOAP, JSON, etc.)...

Having defined the details of the project, we offer a technical and economical proposal without any compromise, including information on the estimated deadlines for the implementation and all the details needed to make the decision to work with us.

Having agreed on the technical and economic terms, we can start working from our offices. Although it may vary depending on the project type, implementation typically consists of the following phases:

  • Preliminary phase: during this phase all the necessary information for the development is completed.
  • Development phase: the development itself. In general, if the development involves the evolution or replacement of an existing solution, this phase is performed in a parallel environment to avoid interference with the current operation.
  • Test phase: once the development is finished, testing begins. In order to accomplish this phase, whenever technically possible, a test environment is provided, accessible by the customer to validate the work before the deployment. It will also enable customer access to a ticketing management system where you can track any found issues.
  • Delivery: Once the tests are performed and all the detected issues have been solved, the solution is integrated in its real environment. If the project is an evolution or replacement, the main priority is always to minimize the service interruption. All code written for your project becomes their property.
  • Warranty: work has a warranty period during which all problems and / or defects found are adrressed. We also offer the possibility of extending the standard warranty period with a customized proposal that includes ticketing management for an easy tracking of issues.

Meet some of our success stories to value the diverse nature of our projects.

Coding Standards

We have very clear criteria about how should the style of programming be.

We submit our code to metrics, in order to keep it as clear and reusable as possible. Some parameters that we consider: cyclomatic complexity, lines of code for objects and files, number of method parameters, etc. We want the code to be easily reassumable if we need to adapt, it evolve it or correct it.

We also have criteria on how to name variables or methods, or how to comment code.

Database integrity

When designing a database we have special care so that the design is compatible with the maximum security level of data integrity.

To do this we consider the concepts of normalization of the database, and always we start from the premise to reach at least the third normal form (3NF).

Test Cases

Our aim is that errors should not be corrected after the solution is deployed.

To do this we establish a relevant test case set depending on the type of project, covering the specified requirements, and correcting any defects in the earliest stages.

If the nature of the project requires a trial period before its use, we establish a time frame during which the problems are not exposed to the end user and the real environment.