Tuesday, April 29, 2008

Offshore Software Development

Our goal is to keep you up to date on the issues related to the offshore outsourcing especially in the field of software development. We will discuss the risks and best practices, tips and techniques and other issues related to offshore software outsourcing.
It is a well known fact that the offshore outsourcing (or any kind of outsourcing for that matter), known and unknown risks . It is important to find out whether your offshore outsourcing providers are aware of these risks and has a plan to either mitigate or eliminate. Top 5 risks of offshore outsourcing are as follows:
Requirement (MIS) dangers understanding Quality Data Security Discipline Process (CMM) project timeline " " Requirement (MIS) understanding it often happens that the requirements are in a hurry To build the project started as soon as possible. That& 39;s okay if the project is being done inhouse. However, if they outsourced, it is a risk. If the specifications have not been properly or are incomplete or do not have enough details, the project will have problems in various fronts such as Project Understanding - what needs to be done and delivered, project planning - compilation fixed dates for the delivery, Change Controls - Many Change Control produces are later in the project life cycle, could, of course, the delay of the project and the increase cost.Per the study under the leadership of the Software Engineering Institute, not enough understanding or the clarity around the customer requirements is one of the top reasons why software - Projects fail or be delayed. To mitigate this risk, make sure that your provider has the obligation to understand phase before the start of the phase-encoding. The requirement understanding phase should be over several rounds of discussion with all parties fully understand and document their requirements in the software specification documents. This phase is independent of the chosen technology for the project. For the web-based projects, providers should also prepare the HTML mock-ups which is an excellent way to the application flow. [This mock-ups should be reused during the coding for embedding the application method calls.] The first phase of a software development project must comply with the requirements of development. The goal of the requirements development phase is to address the needs of customers and their implementation in the requirements specification of what the system must do. Requirements Development consists of three related activities: analysis of requirements, it is about the determination of acceptance, the ability to implement and testability. Inspection requirements, by discussing the proposed requirement in detail. The goal is to identify the problems and errors in connection with the requirements of ambiguities or inconsistencies. Gathering user requirements, through questioning of potential users on the system they want, building the interactive prototypes, the writing Pflichtenheft documents.
The available from this phase is a detailed requirements document, which should be jointly reviewed and signed off.
We invite you to visit Ours. NET Center of Excellence and offshore outsourcing blog
To learn more about how Hanu software can help your business grow, give us a call at 6099452242 or visit our website www.hanusoftware.com
www.hanusoftware.com, www. vannova.com



Bookmark it: del.icio.usdigg.comreddit.comnetvouz.comgoogle.comyahoo.comtechnorati.comfurl.netbloglines.comsocialdust.comma.gnolia.comnewsvine.comslashdot.orgsimpy.com

No comments: