Deal support Document List 2

You can use an Acquisition Plan Document when managing software projects that involve acquiring software and bringing products and services in-house. An Acquisition Plan also help you plan how you to take possession of a business, service or software that you plan to acquire, for example, during a merge or when partnering with another software company.

You can use an Availability Plan Document to describe how your system will be made available by capturing the hardware and software aspects of your solution setup.

You can use a Bill of Materials document to list the parts for building a product/service, including software application, infrastructure equipment and physical buildings. The Bill of Materials lists all the subassemblies, intermediates, parts, and raw materials that are part of a parent assembly, showing the quantity of each required to make an assembly.

You can use a Operations Guide Document that will help you run your IT environment more efficiently. It provides tables, charts, and matrices for server monitoring, backups, scheduling tasks, monitoring systems, managing inventory, and performing follow-up reports on outstanding issues.

You can use a Maintenance Plan Document to provide Tech Support personnel with the information necessary to maintain IT systems effectively.

You can use an Interface Control Document to describe the relationship between system components in terms of data items and messages passed, protocols observed and timing and sequencing of events. Interface Control Documents (ICD) are a key element of systems engineering as they define and control the interface(s) of a system, and thereby bound its requirements.

You can use an Installation Guide document when installing software and for the preparation, training, and conversion from existing systems.

You can use a Functional Requirement document to define a function of a software system and how the system must behave when presented with specific inputs or conditions. These may include calculations, data manipulation and processing and other specific functionality.

You can use a Design Document to describe how you intend to design a software product and provide a reference document that outlines all parts of the software and how they will work. This document gives the software development team an overall guidance of the architecture of the software project.

You can use a this Deployment Plan document is a ‘how-to’ guide to implement a solution into a live production environment. It provides detailed deployment guidelines and helps drive the deployment phases.

You can use a Database Design Document to map the logical data model to the target database management system with consideration to the system’s performance requirements.

You can use a Data Conversion Plan document to cover conversion types, security , strategy, data conversion , tasks, planning, and conversion requirements.