Customer Support Web Portal Login
VDS Project Methodology

VDS begins the process of understanding the client organization, its industry, and its information requirements with an Assessment, which typically consists of a visit to the client site and follow-up report.
During the Assessment, VDS defines the scope of the project by identifying the business and technical requirements. In addition, the business case is outlined, stakeholder groups are identified and the project is planned in terms of tasks, effort and duration.
VDS Design process includes several key tasks:
Establish Prototype Tools And Guidelines for the user interface and code.
Assess the current technology infrastructure and develop a plan for revisions based on current status and anticipated needs.
Develop a complete prototype with a working model.
Establish the development environment tools and guidelines, and develop a complete, representative slice of the application.
Create Test Plans for all software modules, database failure and recovery procedures, and software integration.
Transition from Design to Constructions at the end of Visualization is marked by presentation of the design documents and updated Project Plan, and official acceptance by the stakeholders.
Several concurrent activities occur during Construction:
Instantiation is completed, allowing a working model to be built. Breaking the process into Instantiation and Propagation provides the flexibility necessary to deploy incrementally.
Data Transformation Analysis and Implementation are important for applications that rely on incorporating existing and outside sources of data.
Transition Planning includes scheduling system rollout, ensuring hardware and software will be in place, and finalizing user and administrator training plans.
Testing occurs on several levels as the application development progresses. Developers check their individual work, the Quality Assurance team develops and executes test suites against integrated modules, and stakeholders review the application for completeness, accuracy, and ease of use.
Writing the User and Administration Documentation begins in this stage.
Acceptance of the Construction deliverables marks the transition to Deployment.
The length and structure of Deployment varies significantly from project to project, depending on the application architecture and the landscape of the production environment.
During Transition, VDS and the Stakeholders perform final integration testing, and VDS provides training for end-users and application administrators.
For applications with legacy data, Cut-Over begins with the execution of a carefully rehearsed data conversion process. To ensure continuous business operations throughout the data conversion process, contingency plans are created in advance, and ready to deploy if necessary.
Maintenance concludes the Deployment stage, beginning as the tested application is installed in the production environment.
The ongoing maintenance support process follows the following:
The Customer submits a support request (in accordiance with their maintenance agreement) via the support helpdesk phone number or the customer support web portal.
A support ticket is created in VDS’ support web site’s issue tracking system which is used to track an issue through to its resolution.
Our standard methodology is followed for additional issues and enhancements as described above.
© 2007, Visual Data Software Corporation. All Rights Reserved. | Terms of Use | Privacy Policy