Medical software
Medical software
Turning ideas into software

Email us now or call us in Moscow today +74959620386

Go

Technology

Questions:

What technologies do you usually recommend?
What is your technical expertise?
How stable is your technical team?
How detailed a set of requirements do you request from clients?
What can you do with just a one-page needs assessment?
What is your approach to software development?
How do you perform testing and quality assurance?
How is the communication process organized?
How do you deal with urgent bug fixing?
Do you provide post-development maintenance?
How do you ensure the quality of your services?
How flexible are you in regard to following client standards and/or methodologies for project development?
Do you offer different pricing models?
What do you base project estimates and schedules on?

Questions and Answers
What technologies do you usually recommend?
We are not tied to any single technology, preferring to recommend whatever works best for the project.

What is your technical expertise?
  • Case Tools: Rational Rose, Microsoft Visio, Erwin, Oracle Designer
  • Languages: CSP, C/C++/C#, VB/VB.NET, Java/J2EE/JSP, J2ME, PHP, ASP/ASP.NET, Delphi , Perl, ColdFusion, Assembler, Flash Action Script
  • Markup Languages: HTML, XHTML, XML, XSL
  • XML based web services: WSDL, SOAP
  • Databases: Caché, MS SQL, Oracle, MySQL, MS Access, PostgreSql, DB2
  • Technologies: .NET, J2EE, Swing, JDK, Win32 API, CORBA, MFC, AJAX
  • Java servers: JBoss, Tomcat, IBM WebSphere, iPlanet, BEA WebLogic
  • Platforms: Windows (Windows CE, Windows Smartphone), UNIX-based (Linux, Solaris, FreeBSD), Symbian, Open VMS


How stable is your technical team?
Our average attrition rate over the last 4 years was less than 9%. This compares very favorably with 15%-35% in India. Additionally, most of the developers we hire are mature and experienced, so, although they are constantly adding new skills to their repertoire, we aren't in a constant training mode.
 
 

How detailed a set of requirements do you request from clients?
Our clients' input has ranged from a one page needs assessment to multi-page, detailed specifications.
 
 

What can you do with just a one-page needs assessment?
Working from the needs assessment, our analysts go through multiple iterations to develop a detailed, formal spec that may include use cases, GUI, functionality prototypes, etc. Alternatively, we can start an XP-type process where requirements are identified as the customer reviews new prototypes which eventually become finished software.
 
 

What is your approach to software development?
The nature of projects dictates what software development approach we choose, thus, we adhere to an agile process based on Extreme Programming (XP) techniques adjusted to ISO 12207/ISO 15504 series requirements, or to Rational unified process. Read about some process highlights.
 
 
 

How do you perform testing and quality assurance?
Our dedicated team of testers uses automated testing tools to perform integration, delivery and beta testing. Unit testing is typically done by developers, and some projects follow a test-driven development approach.
 
 

How is the communication process organized?
  • To achieve the optimum development situation our preference is to have daily conversations between you and both your key NTR contacts:
    • An account manager who acts as your on-site representative to ensure that all requirements are met.
    • A project manager who schedules/oversees/liaises with the developers and others working on your project.

  • Both your key contacts are easily accessible via phone, email and instant messaging.
  • Based on an agreed-upon format, a status report will be issued at the end of every week by Friday 23:00 (GMT+3).
  • Emails in both directions receive 14-hour turnaround or, at the least, acknowledgement and a statement regarding when the full response can be expected.
  • We are available live within 12 hours after email request and we expect our clients to be available for live contact within 24 hours after an email request. (These refer to requests in addition to the normal daily interface described above.)
  • We track bugs and requests, including priority, using the OPT web-based project collaboration system that easily allows clients to enter information at any time.
  •  
     

How do you deal with urgent bug fixing?
Our project collaboration system includes a bug tracking mechanism that orders the issues based on their designated priority. Urgent bug fixing issues are assigned the highest priority so our project team addresses them immediately.
 
 

Do you provide post-development maintenance?
Yes. We provide our clients with a 90-day warranty period after delivery that includes bug-tracking and fixing. Feature enhancement and other new development are considered separate and can be handled by either a new development agreement or a post-warranty support contract.
 
 

How do you ensure the quality of your services?
We believe that quality originates from two sources: process and people.
 
 

How flexible are you in regard to following client standards and/or methodologies for project development?
Client methodologies and standards are welcome so long as our own quality standards remain unaffected.
 
 

Do you offer different pricing models?
We offer several pricing options - individually or in combination.
  • Per-project pricing: a fixed price quote for a project with a set of stable requirements.
  • Time-and materials-based pricing for research projects or projects where the requirements are fluid and/or lack clarity.
  • Dedicated development facility: a long-term agreement at lower per-hour rate with a team dedicated entirely to your development needs.


What do you base project estimates and schedules on?
We start with a comprehensive analysis of the project, including scope, deadlines, and other pertinent information. We then develop a detailed proposal based on this analysis, including the resources involved in the development phase, project delivery requirements, and project milestones. In addition, for mid-to-large projects we use both project-based top-down and Functional Points/COCOMO2-based approaches to ensure adequate project planning.
 
 


Survey

Take our survey, please. 

© 2006-2007 NTR Lab Valid XHTML 1.0 Transitional Valid CSS!