Aplications
Flexible model and best practices to promote efficiency.
Flexibility, best practices and operational efficiency. BRQ works in all cycles
of applications, from staff augmentation to implementation and custom
development.
Tailored Development
Applications Management and
Maintenance
Software Factory
Testing Services
Staff Augmentation
Learn how to identify the best format for
the resolution of your problem by consulting the table below:
|
Model |
When to use? |
Strengths |
Weaknesses |
| Staff Augmentation |
The client needs to
expand its own development team. |
- Management and
development of resources remain with the suppliers.
- Simplifies the management of peaks and valleys in demand of the
client’s projects.
|
- Requires the
client to have the environment, project management and own processes.
- The risks related to the development process are undertaken by the
client.
|
| Code Factory |
When the volume of demands is too high and the client wants to subcontract
programming to achieve increase in scale.
|
- Allows the
client’s team to further dedicate to other activities of the development
cycle.
- High formality level.
- Increase in scale.
|
- Investments in the
factory setup.
- Level of design details.
- Difficulties in communication between teams geographically distant.
|
| Tests Factory |
When exemption in the
execution tests with subcontracting of a supplier to carry them out is desired |
-
Exemption in tests execution.
- Standardization.
- Specialization.
|
- Requires more
formality in projects documentation.
- Requires more structured process.
|
| Development Factory |
When the client wants to keep control on critical activities such as
requirements and architecture and subcontract modeling
|
- Reduces
communication problems and level of details of a code factory.
- Requires enhanced robustness in architecture requirements.
- Allows efficiency gains through reuse.
|
- Investments in the
factory setup.
- Requires maturity to carry the subcontracting out.
- Requires close follow up of the client’s analysts and architects.
|
| Software Factory |
When the development of
long running system or a smaller systems suites is desired. |
- Specialization in
the client’s domain.
- Formality and standardization.o
- Does not require on-site analyst and architect.
|
- Investments in
the factory setup.
- Necessity of subcontracting project management.
|
| Project |
Necessity to develop a
unique system which does not justify the setup of a factory and the level of
associated formality. |
Efficient and integrated teams, operating with a light process.
|
Does not leverage increase
in scale in the development of large systems or several smaller systems. |