Document Actions
Development
Every single project involves some sort of Software Development. This section describes the processes of our Software Factory: the processes, technologies and tools we use when developing completely new and/or customs solutions that are built from the ground up. Many of the concepts and methodologies described here are also used throughout our whole services portfolio, in fact, it is the software factory that sets most of our standards. It is worthwhile to note that a great part of our current revenue actually comes from the development of new/custom software solutions.
Technologies
Open Source has a very wide variety of languages and development platforms. We have specialized in three major languages and two major development platforms. Although we are not limited to these languages and platforms, we strive to maintain a very high level of expertise and they are the focus of our development business.Core Languages
 |
 |
 |
Core Platforms
 |
 |
Workflow
Our software development workflow is fundamentally based in the Unified Software Development Process. Nevertheless, we combine some traditional techniques in project management such as PMI's PMBoK and more radical concepts like eXtreme Programming (XP) and the so called "Promiscuous" model established by Linus Torvalds in the creation of the Linux Kernel.
The New Phases: Inception, Elaboration, Construction and Transition
Instead of seeing the development process as a set of discreet phases, the newer schools of software development are defining broader and more flexible process. The traditional "Waterfall" model are now mini-phases that occur within one iteration of a major phase. The model is a matrix that represents different levels of effort of each individual activity throughout the process. The following diagram illustrates the effort curves of each activity plotted against the major phases:
This model allows us to be very competitive and reduce risk associated with detailed and un-flexible specifications that were the norm in past. These specifications, lifted very early in the process usually wound up worthless when the system reached the final user's screen, at the end of the project, when it was already too late to change anything. The ne witerative technoques allow to trap requirements flaws and integrates the final user early in the process.
Our Tool-set
Our methodology is accompanied by a rich Open Source tool-set. Many of these tools are shared with our clients. For example, clients have access at any time to our project management systems and monitor the execution of the project
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Technologies dropped, technologies added