Disposition Plan Template for Software Development Projects by Ivan_Walsh

VIEWS: 80 PAGES: 8

Use the Disposition Plan Template to explain how to dispose of an Information System in a structured manner so data can be transferred correctly to new systems and, should the need arise, reactive the disposed system. You can modify this MS Word template to suit your technical and system requirements.

More Info
									Disposition Plan
                                    Template
                    Version X.x ●December 2, 2010



      Use the Disposition Plan to explain how to dispose of
      an Information System in a structured manner so data
      can be transferred correctly to new systems and,
      should the need arise, reactive the disposed system.
      This plan needs to be modified depending on your
      technical and system requirements.
                                                  [YOUR COMPANY LOGO]




                                                          Company Name




                                                        Street Address 1




                                                        Street Address 2




                                                               City




                                                          Zip/Postal Code




                                                             Country




                                           Tel: +xxx-x-xxx-xxxx Fax: + xxx-x-xxx-xxxx




       Last edited: 02 December 2010
       Copyright © 2010 [Company]. All rights reserved.
       No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
       translated into any language, in any form or by any means, electronic, mechanical, photocopying, recording,
       or otherwise, without prior written permission from [Company].


Document Name: 8c954846590347d0b36d.doc

© Company 2010. All rights reserved.                                                                                 Page 2 of 8
All copyright, confidential information, patents, design rights and all other intellectual property rights of
whatsoever nature contained herein are and shall remain the sole and exclusive property of [Company]. The
information furnished herein is believed to be accurate and reliable.
However, no responsibility is assumed by [Company] for its use, or for any infringements of patents or other
rights of third parties resulting from its use.
The [Company] name and [Company] logo are trademarks or registered trademarks of [Company].
All other trademarks are the property of their respective owners
[Company Name]                                                  8c954846590347d0b36d.doc
[Project Name]                                                            [Version Number]




                                 Disposition Plan
                                       [Organization Name]


                                       [Project Name]
                             Version: [Version Number]   Revision Date [Date]


     Executive Sponsor
     [Name]                                   [Email]                 [Telephone]

     Signature                                                        Date




     Technology Sponsor
     [Name]                                   [Email]                 [Telephone]

     Signature                                                        Date




     Project Manager
     [Name]                                   [Email]                 [Telephone]

     Signature                                                        Date




     Security Officer
     [Name]                                   [Email]                 [Telephone]

     Signature                                                        Date




Document Name: 8c954846590347d0b36d.doc

© Company 2010. All rights reserved.                                                Page 4 of 8
[Company Name]                                                                                                  8c954846590347d0b36d.doc

[Project Name]                                                                                                                   [Version Number]

Table of Contents
1 INTRODUCTION......................................................................................................................................7

  1.1 PURPOSE ...............................................................................................................................................7

  1.2 SCOPE ..................................................................................................................................................7

  1.3 OBJECTIVES.............................................................................................................................................8

  1.4 INTENDED AUDIENCE..................................................................................................................................8

   ~~~...........................................................................................................................................................8




                                                                                                  Document Name: 8c954846590347d0b36d.doc
Page 5 of 8                                                                                              © Company 2010. All rights reserved
[Company Name]                                                           8c954846590347d0b36d.doc
[Project Name]                                                                     [Version Number]


        Document History
Paper copies are valid only on the day they are printed. Contact the author if you are in any doubt about
the accuracy of this document.



Revision History
 Revision Number         Revision Date    Summary of Changes              Author




Reference Documents
Please see the following documents for more information:

 Document Name                                                 Version                Author




Distribution List
This document has been distributed to:

 Name                                     Position             Company                Action




Document Name: 8c954846590347d0b36d.doc

© Company 2010. All rights reserved.                                                           Page 6 of 8
[Company Name]                                                              8c954846590347d0b36d.doc

[Project Name]                                                                           [Version Number]

1             Introduction
    Introduce the Disposition Plan by placing it in context with the rest of the Software Development
    LifeCycle. In general, the Disposition Plan is used to explain how to dispose of an Information System
    in a structured manner so data can be transferred correctly to new systems and, should the need
    arise, reactive the disposed system. This plan needs to be modified depending on your technical and
    system requirements.
    Another consideration with the Disposition Plan is to ensure that all records, data, and files are
    disposed of and/or retained in line with legalization and compliance laws. This means that, rather than
    destroy any data, you need to ensure that all software, hardware, and data is disposed of in
    accordance national laws and industry regulations. You can transfer software and system data to
    other systems, migrate it to new systems, or archive the data for future use. Hardware can be made
    available for use by other systems, or discarded if it no longer applicable.

1.1           Purpose
    [Describe the purpose of the Disposition Plan. Provide the Information System’s name and identify key
    information about the system undergoing disposition, for example, the rationale behind this decision.]
    •    Notification – Inform all system users of the planned date after which the system will no longer
         be available.

    •    Data Transfer – Identify a designation storage location and transfer the data to be archived onto
         storage media. Coordinate tasks with the Project Management team to ensure data is transferred
         correctly from the current system to new systems.

    •    Prioritize Tasks – Identify and prioritize software to be stored including communications,
         systems and application software.

    •    Data Migration – Coordinate data migration with the Project Managers of other systems so that
         the current system software and data is migrated correctly to new systems.

    •    Data Archives – Identify where to store life-cycle products, such as technical documentation, in
         secure locations.

    •    Equipment Disposal – Identify equipment used by the system and how/where it will be
         disposed.

    •    Progress Reporting – Update the Disposition Plan when you have successfully disposed of
         data, software, and hardware.

    •    Project Closure – Outline the steps to shutdown the project, including how project staff will be
         re-allocated, where project records will be stored, and when you will handover project facilities.


1.2           Scope
    [Outline the business and/or technical reasons why the system will be disposed of, for example,
    redundant technology, maintenance costs, security risks, compliance issues. Discuss alternative
    sources to the same functionality, if applicable.]




                                                                   Document Name: 8c954846590347d0b36d.doc
Page 7 of 8                                                               © Company 2010. All rights reserved
[Company Name]                                                           8c954846590347d0b36d.doc
[Project Name]                                                                     [Version Number]

1.3            Objectives
   [Identify the objectives of the Disposition Plan. This is to end system operations in a structured
   manner and ensure that system components and data are successfully archived and/or incorporated
   into other systems.]

NOTE: The system will no longer exist as an independent entity when this project is completed.

The Disposition Plan ensures that the systems life cycle is completed correctly by carefully planning. This
involves reducing disruptions to other organizations and business units that use the system and the
operation of other systems that use the data, processes, or software provided by the current system.


1.4            Intended Audience
   [Optional] Identify the intended users for this document, the sections most relevant for each reader,
   and the purpose for which the users may utilize the information in this document.

 User           Relevant Sections                             Uses




                                                         ~~~

            Download the Microsoft Word Template at
    http://www.klariti.com/Disposition-Plan-Template/




Document Name: 8c954846590347d0b36d.doc

© Company 2010. All rights reserved.                                                           Page 8 of 8

								
To top