Atlantis Software pretends to be different from the competition. This section explains the main reasons, in other words,
it explains why you should work with us.
Talking about our Quality means explaining the Quality Management at Atlantis Software.
We are convinced that the foundation to achieve a qualitative result is to adopt a qualitative approach based on :
- best practices,
- approved guidelines,
- repetitive processes,
- and methodologies.
The whole process itself must be based based on a methodology, this is what we call Total Quality Management.
Using a methodology means that we can repeat the process. It also means that this process is documented, controlled,
measured and improved.
All the companies pretend to produce quality and to fullfil client requirements. But how can they assure you that the end-result
will conform to a precise Quality definition?
Atlantis Software uses the definition of David A. Garvin (associated professor of business administration at Harvard Business
School) in his paper published by Harvard Business Review in 1987. He gives eight dimensions:
- Performance. Main operational characteristics of a given product.
- Features. Aspects of a product that even not mandatory for the correct
functionality, are well accepted by the client (nice to have).
- Reliability. It is the correct work of the product along the time.
- Conformity to the specifications.
- Durability. Time to failure.
- Perceived Quality. It'a about the opinion that people has about a product or a
We also consider our CRM approach (see the Services section for more information about this approach) that is part of
Atlantis Software Quality System.
At all the stages of the work, the client must be assured and re-assured that the work is under control and converging to the
final qualitative result but not by words and promises, instead by facts. Preferably tangible and measurable facts. In order to
achieve this, we will explain our whole process because only what is clearly concieved can be clearly stated.
Any company should be able to explain its Quality process, this is the first step of any Quality System. As such, this is what
we are going to explain hereafter, first giving the big picture and then explaining every aspect of the process.
Hereafter, we give the main process, some of the methodologies we use, some of the Quality standards / norms we use and
we show how and when they interact with the different process.
At the very base of Atlantis Software Quality System is the set of Corporate Governance rules.
The Quality Assurance methodologies and frameworks we use are part of our Corporate Governance rules.
The Different processes rely on a precise Project Management Methodology that is heavily inspired by existing ones (PMP and
Prince 2). We identify 4 phases that are described here below. Each phase relies on proven methodologies / best practices
and key tasks (those lasts are not described here). The result of a process is a set of deliverables that must be approved,
validated and / or signed by the client. This set of deliverables is the input the next phase. Our methodology implies that it is
not accepted to start a new phase as long as the previous phase has not been completed (it always ends with the client's
The phase 1 is the Sales and Estimation Process. This phase is responsible for estimating the project in terms of resources
(effort and expertise required), time frame and budget required. Our methodology requires to consult the client to
understand the project and in parallel to calculate the estimation. Once the estimation is produced, it is presented to the client
and discussed to see if it matches the client's possibilities. The final step of this process is the client's acceptance and the
contract sign-off. To achieve a qualitative result, we rely on Information Analysis / Business Analysis methodologies in order
to gather the requirements and on estimation best practices as well as previous similar projects to calculate a precise
estimation. The client is always consulted in order to be sure that we reach the desired objective.
The phase 2 is the Project Start-up Process. This phase is the initiation of the project. We gather all the information that
have been collected till then, we discuss with the client about additional project considerations (communication process during
the project, deliverables, quality management, scheduling etc) and we write them in a precise document: the Project Quality
Plan. The result is presented to the client who can ask for changes in the various aspects. Eventually the final document must
be accepted and signed by the client. This document is the reference document for all the projects. Any change to the project
implies to accept a new Project Quality Plan. It is a contractual document. This document is part of any proven Project
Management Methodology, including our methodology. The different existing Quality norms require to be the most acuracy
and this is what we do. The client is always at the center of our processes and in any case before we move to the next
process, the client must validate / accept the current one.
The phase 3 is the Project Execution process. This phase is the concrete development of the project. The first step is to
complete the functional analysis. For this, we rely mainly on UML. Depending on the complexity of the project, we use some
or all the schemas of this method. The client must validate this step before we move to the Architecture study. This
Architecture consists mainly of studying consideration about the database design, user interface & navigation design
(ergonomy issues) and security threats and issues. We use existing methodologies to achieve the desired result. The client is
always consulted to take his remarks into consideration.
Once the architecture study is completed, it will serve as input to the code construction (programs development). Depending
on the complexity of the project, the architecture study can be more or less complex and take more or less time. As already
stated, each step requires the client's validation before we move on. It has to be said though that the more we move into
technical details, the less the client is consulted, unless the client is a technical person obviousely. Consulted can mean
The schema gives an order into the development but in practice it is up to the team to change that order for the best of the
project. The development methodology is selected as early as possible and can be updated during the development process.
It is clear that any change request from the client will lead to a possible new estimation. A change in the estimation
(resources, time frame and budget) depends on the complexity of the change and its impact on the work that has been
completed till then. Our processes are made in order to minimize the need for a change but they can still occur obviousely.
Tests are organized at any stage of the development, the different tests we run are part of a test plan. This last is required by
the Testing methodology we use (TMap). The client is always responsible for his own tests and acceptance tests. This phase
is made of loops. We can repeat the steps of this phase as long as we find it necessary, it is not a straightforward process.
For example, we can develop part of the code, part of the interface and test it to check it the set of developed features
matches the functional specifications, then develop another part of the code etc.
Once the development is supposed to be completed and tested, the client is required to validate and approve the completion
of the phase. In the case he is not entirely satisfied and/or finds issues, he communicates the list of issues to the team that
controls the work done. It is then decided to move to the production environment of the client (unless previous agreements
were taken during the sales process). Here also we apply best practices to tackle security issues and proper server
configuration of the server. Additional tests are run on the production environment to be sure that everything runs fine. The
client is responsible for running his own acceptance tests and inform the team about any issue. The phase is supposed to be
completed with the client validation and acceptance.
The phase 4 is the Project Run-down Process. This phase is the very end of the project. It mainly consists in internal
activities (shutting-down the infrastructure, the project organization, internal evaluations, updating the projects repository,
updating and improving our methodology and processes) and last reporting and reviews addressed to the client, transfering
the knowledge to the client about the project as well as last reviews and reports. The project ends entirely with the client
satisfaction evaluation and survey. This survey is very important in our methodology as it is the base for furure improvement
of our processes and better client satisfaction in the future. The client will be asked to evaluate several aspects of the project.
The whole process is then internally reviewed taking into account the client evaluation and remarks and improved if
The Quality Assurance system of Atlantis Software is updated and future enhancements are brought in order to better serve
our clients. This system may seam heavy but this is th price for a real Quality. We are not the cheapest offshore software
providers but Quality has a price and we provide our clients with an affordable Quality.