| |
| Methodology |
| |
|
ASA’s mission is to take an individual approach to each customer.
Therefore the standard workflow of a project can vary depending on the
clients' needs and requirements. |
|
| Projects can vary as follows: |
| |
| » Development from scratch based on raw specification. |
|
| » Development from scratch based on detailed specification/migration.
|
|
| » Completion of existing application. |
|
| » Integration of applications. |
| |
|
If detailed specification cannot be provided, the experts of our
company compose specs through detailed negotiations with the client,
studying data domain and marketing strategy. |
| |
|
After the client approves specification we provide several technical
proposals (including justification of architecture and development
tools) and project schedule. The author of the approved proposal is
appointed as a project leader. |
| |
|
Project schedule usually composed so that the customer would receive
executable prototype as soon as possible (during first two weeks). Such
an approach mitigates risks considerably at initial stages of the
project. During the project, an executable prototype along with weekly
reports and the source code are provided on regular basis. After
completion of coding, we test an application and deliver source code to
the customer. |
| |
|
As a rule, the payment for small sized projects is expected to be on
sources delivery. The payment for large sized projects is expected on
delivery of intermediate versions/code that is defined beforehand or
regularly. |
| Back » |