Traditional approach or Software Development Life cycle:
VTLGlobal manages the process from conception to completion. Under this approach our software development outsourcing team is responsible for the whole development life cycle. Depending on the requirements we follow different models of Software development Life Cycle (SDLC), but the most common is waterfall method. We divide project in different stages and output of each stage becomes the input for another. We keep the process simple and make sure at no time we move away from the targeted goals.
The common stages:
1). Project planning, feasibility study: In this phase our Software development strategy making team establishes a high-level view of the intended project and determines its goals.
2). Requirement definition: Refines project goals into defined functions and operation of the intended application.
3). System analysis: Analyze end-user information needs.
4). Systems design: VTL's software development team describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudo-code and other documentation.
5). Implementation/development: The real code is written here.
6). Integration and testing: Our team brings all the pieces together into a special testing and maintenance environment, then checks for errors, bugs and interoperability.
7). Acceptance, installation, deployment: This is the final stage of initial development. Our team puts the software into production and runs actual business.
8). Maintenance i.e. "What happens during the rest of the software's life": changes, correction, additions, move to a different computing platform or say migration and porting and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
 |
|
 |
|
"Our team understands that all problems cannot be specified in advance, so we re-iterate earlier software development stages a number of times as the offshore outsourced project progresses. We prototype parts of the entire process, this approach helps demonstrate a proof of concept and more accurately reflects the disorders. Finally our teams do nightly compilations (called a build) of the entire project, bringing together all the current components. They established release dates and spend considerable effort to stabilize the code before it is actually released/submitted". |
|
 |
|
 |
|
