Deal support Document List 1

You can use a Verification and Validation Plan Document to review, inspect, test, audit, and establish whether items, processes, services or documents conform to specified requirements. This helps ensure that the software being developed satisfies all functional requirements and that each step in the process of building the software yields the correct products.

You can use a Configuration Management Plan document to define Configuration Tasks, Configuration Items and Configuration Management Repositories

You can use a User Guide Document can be used to create user guides, user manuals, getting started guides and other types of technical documents. A User Guide is an online or printed book that describes how to use a software application.

You can use a Transition Plan Document to describe how project deliverables will be brought to full operational status, integrated into ongoing operations and maintained.

You can use a Test Plan Document to document the strategy that will be used to verify and ensure that a software product or system meets its design specifications and other requirements. It will help you define Release Criteria, identify Test Deliverables, prepare Budget Costs and describe the test environment to be used for the testing.

You can use a System/Subsystem Specification Document which helps you capture the system’s Characteristics, Partitions and Functions, Environment, Diagnostics, Data and Reports, Security, Control Points, Vulnerabilities, and Safeguards.

You can use a System Administrator Guide Document to deploy, support, and maintain applications in your organization.

You can use a Software Testing Document to save time when creating test forms, logs and checklists so your Test Department has a standardized approach to testing.

You can use a Software Requirements Specification (SRS) Document to describe the behavior of the software to be developed. It includes a set of use cases to describe the interactions between users and the software.

You can use a Setup Guide Document ensure that your customers can install their applications successfully and reduce the workload on your Helpdesk and Technical Support Dept.

You can use a Security Plan Document to describe the system’s security requirements, controls, and roles / responsibilities of authorized individuals.

You can use a Project Plan Document to develop your Work Breakdown Structure, Action Item Log, Deliverables List, Gantt Chart, Issue Log, Project Costs, Project Plan (Excel), Project Requirements Checklist, Risk Log, and Roles and Responsibilities matrix.