Requirement Analysis

Many companies fall flaw of not paying close attention to this stage, they may ignore this process and go by customer requirements as expressed. We have realized that certain clients limit themselves in explaining the technological solutions that they require, simply because that is the extent of technological compliance with their business as availed to them. In many cases, customers point at the solution used by a competitor, but without thoughts of something "better than what a competitor is using".

We believe that business satisfaction from technological solution is only complete if our side analyses both the technical requirements and the business process on which such technology would be applied. Then we can understand how to make recommendations on the best technology, platform, and how best to fill the blank spaces and provide a complete solution.

The requirements analysis stage is very important in off shoring as the service chain lacks complete business analysis in Asia. The ultimate goal here is to understand both the business of the client and expressed requirements, marry both if they match, then plan the application logic, architecture and Quality control based on the balance of business process and requirements expressed. This stage includes:

• A complete business model
• Logic Design and Application Architecture
• Prototyping
• NT (Navigational testing)
• URD (User Requirement Documentation)

A defect of the absence of Business Analysis in the software outsourcing service chain