About the company
Company profile
News
Competitive advantages
Social contribution
About Ukraine
Software development
Our services
Areas of expertise
Software testing
Solutions
Our solutions
Success stories
Testimonials
Outsourcing
Outsourcing to us
Technologies
Business models
Quality assurance
3d modeling & rendering
Architectural modelling
Technologies & tools
Contact us
Contacts and locations
Vacancies
Site Map


Login
Register


 

Outsourcing to us

Infopulse Ukraine has been operating on offshore software development market for more than 14 years and has completed successfully more than 50 projects including large projects, majority of them - starting from the legacy code base.

Our typical software development project includes the following phases:

1. Start of the project and initial requirements collection.
Infopulse provides business analysis and consulting services. We can start our cooperation from definition of the requirements and creation of initial documents. In case of necessity our analyst can visit client so as to determine prerequisites together with specialists from the customer’s side.

2. Analysis, planning, design and architecture of the system.
We have a number of highly experienced software development analysts and architects, experienced in various industry and software domains. With their assistance, precise and efficient project-plan and system architecture are created. On this stage the project-team is finally installed.

3. Coding, development, and testing.
As a software development lifecycle model we use iterative development approach following RUP methodology with average length of iteration about 2 months. Alternatively we apply XP practices with short 2-weeks iterations. Continuous integration and automated tests are used in both cases.

4. Delivery, maintenance and support.
Normally, when we start new project we develop all requirements (documentation and models) using Rational Rose (or Rational XDE for .NET), because we want to offer to our customers best results and we need to know all aspects for customer needs and wishes. We perform reverse engineering of existing applications and, on that basis, create new specifications for the software to be. This part of work could be made by us alone or together with customer or customer can do it himself. Anyway this is a starting point to develop high-level planning. This planning could be discussed (to define some specific for customer dates, milestones and so on).

Than we do an analysis part and after analysis we can develop real project planning what will satisfy both sides, make technical choices and design the future system. We work very closely with our customers to make sure we cover their functional needs and fit to their technical line. For project management we use MS Project for planning. We also have project site (which could be accessed from outside of our company for our partner), where all project specific data will be located (like documentation, CVS, discussion boars, time tracking application, bug tracking and so on.

After that we execute design and implementation (when source code is written), QA/stabilization (when developed functionality is tested and possible defects are registered), deployment (is done via an installation file, installation instructions and a user manual are delivered as well) and deliverable (when project documentation and components with source code are delivered to the customer) of the project according to previously development project plan. Delivery schedule is a subject for discussion. Deliverables are subjects for detailed specification in Project Plan document developed prior to project start.

In order to improve quality of provided services we implemented corporate quality management system and passed ISO 9001 certification in 2004. Moreover, our specialists have been trained directly by teachers from Rational Software on RUP methodology, particularly on requirements management with use-cases, OOAD, configuration and change management and other disciplines.

Within project development exact set of project documentation is specific to each customer and depends on his requirements on project deliverables, but typical documentation set includes (but not limited to):

  • Contract, Statement of Work, Project scope, Acceptance Criteria, Milestones and deadlines, Team Orgchart
  • Requirements Specification, Vision, Use Cases, Requirements repository
  • Design documentation (UML), System Architecture Document
  • Test plan, Test specs, Test Cases, Test Reports
  • Project Plans, Project status reports
  • Release notes, Training Materials
  • End-User documentation

We are sure that with our experience, technological and organizational maturity we are able to realize mentioned project successfully, with high quality, on time and on budget.

 

 
© 2008, Infopulse Ukraine.
All rights reserved.