| |
|
|
|
 |
|
 |
| |
The current company-approved standard for the software development is the
Microsoft Solution Framework industry standard.
Due to approved standards, the company applies the iterative development process. All project implementation phases are iterated until they fully satisfy changing customer needs.
Company´s project managers combine roles of system architects and team leaders. They are responsible for high-quality object-oriented system design with clear-cut and detailed product documentations, including all product-related diagrams, source code comments and user guides.
All employed programmers follow carefully designed coding conventions, and finally, the customer gets the self-explanatory source code for the project, which may be easily reused. |
|
 |
|
 |
|
Testimonials |
 |
| Rusty D.
|
It has been a pleasure working with Vitaliy
and his team over the last year.
The complexity and ever-changing
requirements of our project demanded
constant communication and a team
proficient in today`s newest technologies...
|
| More >> |
|
 |
 |
 |
| |
 |
About Web Development in ITCrimea |
 |
|
The project implementation is divided into four phases:
- Inception;
- Elaboration;
- Construction;
- Transition and Production.
Within the inception phase, the company´s project manager works closely with customers, gathers system requirements, and reflects them into initial project documentation – the project vision, supplementary documentation, and the business use cases.
The project manager builds a product team with the help of product managers when the initial project vision is prepared. The systematic meetings with product managers give the project manager the information about project risks and the initial system architecture concepts. All project risks are documented in details, and the product team starts risks-reducing process by making researches, prototyping the risks-reducing solutions and suggesting the best of them to the project manager. Accepted prototyped solutions are included into the risk management plan of the project.
Project managers initiate the elaboration phase of a project after all risk management plans were defined and carefully tested. As a result, product managers give the project manager a detailed project review, and system architecture (as flexible as it could be) along with all related project documentation (modified business use cases, detailed project view and related information). This allows the project manager to fix the project budget and the development timeline. This information is sent to the customer for approval.
When a customer approves project timeline and budget, the company starts a project development (construction) phase. At first, the product managers request the list of priorities for implementation from the customer. When all system functions are prioritized, the company involves the built product team into the use cases development process. Product managers are responsible for development workflows. Each implemented use case stops the development process (except for the core components) until the testers confirm that the system meets all the requirements and the customer accepts the implemented solution. Company is experienced in change management within the time range accepted by the customer.
When all use cases and core components of implementation are completed, it usually takes a week for the company to develop and pack the application into the set-up package. The existence of the set-up package indicates the beginning of the last, and the most important project phase – the transition and production. The product testing team "stress tests" the system in the local environment, and then performs transition of the package to the customer´s environment. After the "stress test" on the customer´s side has been completed, the project manager notifies the customer about the beginning of the user acceptance testing. The customer uses project user guides, and manually sets up, executes, and verifies the product functionality. After the customer accepts the product, the release version 1.0 is assigned to the product, and it goes into the production.
Product managers review the produced source code at each stage of the development process. DVD-RW drives are used as regular daily back-up facility. There are always several identical backup copies, stored in different places.
|
|
|
 |
|
 |
|
| |
|
|
|
|
