The production Process

Our compromise with quality and software process guarantees the appropriate use of the Unified Software Development Process. Our process employs UML notation (Unified Modeling Language), in each of the different steps. We specialize in the construction of solutions based on the Java and Microsoft platform and tools.

The Unified Software Development Process is the set of procedures, activities, controls, tools, training and, in general, the whole experience accumulated, which are improved day by day with a continuous improvement mentality, with an aim to surpass the expectations of the client.

We are convinced that a robust software development process is the base for a consistently successful implementation of projects. A well-defined process allows a careful analysis of the parameters affecting the performance level of our professionals and the quality of the resulting software products.

A process can never be improved if no assessment of its capacity and maturity is available. To improve our process we are helped by software specialists that measure and analyze the efficiency of the process with statistical tools, comparing against well-known quality systems like SEI-CMM and ISO-9001.

To attain our level of on-time and quality delivery in our projects, automated controls are applied which provide our managers with valuable information to guide decision-making during the project. An orientation towards risks identification and elimination contributes to on-time delivery. Risks are handled by means of an iterative and incremental process, where progress is effectively validated in each iteration with the client.

We know that software implies more than a running program. A quality software is a flexible, robust, and documented system that is efficiently employed by users, fulfilling their needs. The life cycle does not end with software release, because with high likelihood the internal and external conditions of the business will evolve (company growth, macro-economy, etc.), so that systems will demand modifications and extensions. Without good documentation and a robust architecture these changes will entail a large risk, with a concomitant important and unnecessary cost for the client.

The architecture of the systems we develop is based on the UML notation that supports the object-oriented paradigm with components, which assures, in conjunction with our quality assurance plan, the flexibility and robustness of our systems. The use of CASE tools for architecture analysis and design, together with reuse management result in a reduction of development time and therefore of project cost, as well as in an increase of quality resulting from using tested components from different currently in operation.

Part of the documentation generated when following the Unified Process is the following:

· Requirements specification
· System architecture (UML and Data Model)
· User Manual
· Deployment Manual
· Tests specification
· Installation disks
· Source code

Quality is a means, not an end, and therefore at Inar we will never be completely satisfied with our performance and quality levels. Our compromise with the client makes us constantly push for new methods and tools to be able to offer better solutions.