2009
05.26

Outsourcing Software Development involves repositioning of software development activities by a company to third party service vendors or software firms that may be located in offshore destinations. It can save you time and money if you know what you need. Development is a specialized task that involves huge investments and a specialized workforce.Outsourcing the same could give the companies a chance to develop software at a lower rate, employ specialized labor at a cheaper cost, promote software research and save time. This is the reason why most companies decide to outsource their software development activities to offshore destinations, like India.

Whether you need a dynamic, database-driven website or a fully functioning e-commerce website, Outsourcing Software Development services in India have the creative talent and technical expertise to accommodate your company’s web development needs. Any company can save about 40% of its expenses by outsourcing project overseas. There is no doubt thatit is a most effective way to stretch your budget. Many organizations use Outsourcing their Software Development projects to India to reduce their costs.

The traditional approach to outsourcing development projects typically follows a single strategy. You begin by negotiating a contract, which may be based on previously defined requirements or may include the effort of gathering, documenting and validating fresh requirements. The Outsourcing service then works to your requirements to develop the system. Regular communication helps resolve potential misunderstandings.

Advantages of Outsourcing Software Development:

*Getting access to specialized labor at low rates
*Cutting human resource costs
*Cutting operational costs
*Reducing software project expenditure
*Ensuring proper project management
*Software research at lower rates
*Reducing training costs

The success of any outsourced project depends on many factors; Companies specially in US and Canada are looking to outsource their software development projects to India and Indian Companies are becoming a profitable choice for them. This is because they, being a mid sized and growing custom software development companies, understand their client’s business process very well and can then convert it into IT solutions, thereby fulfilling the client’s needs and requirements.

So for the software development companies, irrespective of whether they are in US, Canada or EU, willing to outsource their projects should try out Indian companies to know the quality and expertise they cherish. Because it is always better to try out before trusting.

2009
05.16

Win Mobile DevelopmentToday the most sophisticated smart phones, and even some Pocket PCs and Portable Media Centers, run on Windows Mobile Operating System from Microsoft. Last year Microsoft’s mobile shipment almost doubled, signifying that demand for Windows Mobile powered smart phones has significantly increased, and will continue to do so over the years. Currently in version 6.1, Windows Mobile can be thought of as a scaled down version of the popular Windows Operating System. It has the mobile versions of the popular Microsoft Office suite, and also the Outlook mobile, the very popular email client. For various multimedia uses, it bundles Windows Media Player. For internet browsing, it has a mobile version of Microsoft Internet Explorer. It has a taskbar similar to the one found in the Desktop version of the Windows Operating System. A user can access the device’s various programs and options using the taskbar, similar to the desktop version. HTC Corporation is currently the biggest major smartphone manufacturer which uses Windows Mobile.

2009
05.05

How do we take care of mobile porting?
Porting done at our end includes 4 parts:

  1. UI management
  2. Memory Management (Heap Size and RMS Size)
  3. Connection Management (if using network connection)
  4. Testing and bug fixing.

1. UI Management:

  1. This includes all screens present in application. We follow following standards to port an application:Conditional Compilation: this reduces porting time for different screen size and also for different platforms.
  2. We port application based on screen size. All UI is managed by dynamic co-ordinates dependent on screen width and height.
  3. Using of Font height if we are using canvas to draw a wrapped text or list in a screen.
  4. Resize of images if required.

Porting Time:

UI management depends on number of screens and also on existing scheme used. If static co-ordinate system is used then it increases porting time. Usually porting time for first build takes around 4-5 days if UI has to be managed as above and will reduce the porting time for all subsequent builds to 2 days.

2. Memory Management:
Under memory management we consider Heap Size and RMS Size available for Applications/Games. We need to have an optimized code whether it is related with variable objects or RMS data.

We should not keep any data into heap which is not required frequently. So we should create objects only at that time when required.

In case of RMS data we should check for available size.

Porting Time:

This field is entirely based on implementation of existing logic. If application uses is well optimized then we need to just test it for various builds. Otherwise we need to manage them to make them available for more handsets which would require around 2 days if needed.

3. Connection Management:

In those applications which uses network connections we need to manage connections also because some of devices has limited active connections so we need to close network connections and also open streams to make application running successfully.

Porting Time:

This also depends on implementation if required then it would take 1 day to optimize.

4. Testing and Bug Fixing

After porting on every first handset of the family, only testing will be required for all the other handset of the same family covering around 1-2 handsets in a day if tested against NSTL or other authorized Test Cases.

Estimation for each application:

Since all the above will be implemented for this particular estimation, porting on first build of each application would require around 5-8 days but will reduce the porting time for all subsequent builds to 2-3 days depending on device specific issues.

After porting on every first handset of the family, testing will be done for all the other handset of the same family against NSTL Test Cases, covering around 1-2 handsets in a day.

Apart from this we would require around 3 days to study each application initially to understand the UI flow and application architecture.