Docstoc

Software Development Plan SDP Template

Document Sample
Software Development Plan SDP Template Powered By Docstoc
					                Software Test Plan (STP) Template


Items that are intended to stay in as part of your document are in
bold; explanatory comments are in italic text. Plain text is used      Formatted

where you might insert wording about your project.


This document is an annotated outline for a Software Test Plan,
adapted from the IEEE Standard for Software Test Documentation
(Std 829-1998).

Tailor as appropriate. Where you decide to omit a section, you might
keep the header, but insert a comment saying why you omit the
element.




Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.doc
                                                         Software TestProject Management Plan




                         (Agency)
                         (Project)
           Software TestProject Management Plan




Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\PROJPLAN.dochttp://iat.ubalt.edu/courses/idia618.185_Sp04/reference/s
                                     oftware_template_template.doc
                                              Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.d
                                     oc             2
                                              08/10/0008/06/9902/05/99 11:27 AM2 of 52
                                                         Software TestProject Management Plan


Version: (n)
   Date: mm/dd/yyyy




Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\PROJPLAN.dochttp://iat.ubalt.edu/courses/idia618.185_Sp04/reference/s
                                     oftware_template_template.doc
                                              Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.d
                                     oc             2
                                              08/10/0008/06/9902/05/99 11:27 AM3 of 52
                                                               Software TestProject Management Plan




TABLE OF CONTENTS



1. INTRODUCTION                                                                                     31

   1.1 ObjectivesProject Overview
               31
   1.2 Testing StrategyProject Deliverables
                  31
   1.3 ScopeEvolution of the Software Project Management Plan
                                              41
   1.4 Reference Material                                                                   41
   1.5 Definitions and Acronyms                                                             51


2. TEST ITEMSPROJECT ORGANIZATION
          52

   2.1 Program Modulescess Model
       52
   2.2 Job Control ProceduresOrganizational Structure
              52
   2.3 User ProceduresOrganizational Boundaries and Interfaces
                            52
   2.4 Operator ProceduresProject Responsibilities
              62


3. FEATURES TO BE TESTEDMANAGEMENT PROCESS
          63
   3.1 Management Objectives and Priorities                                                 3
   3.2 Assumptions, Dependencies, and Constraints                                           3
   3.3 Risk Management                                                                      3
      Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\PROJPLAN.dochttp://iat.ubalt.edu/courses/idia618.185_Sp04/reference/s
                                           oftware_template_template.doc
                                                    Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.d
                                           oc             2
                                                    08/10/0008/06/9902/05/99 11:27 AM4 of 52
                                                                     Software TestProject Management Plan
    3.4 Monitoring and Control Mechanisms                                                   3
    3.5 Staffing Plan                                                                       3


4. FEATURES NOT TO BE TESTEDTECHNICAL PROCESS
                  64
   4.1 Methods, Tools, and Techniques                                                              4
   4.2 Software Documentation                                                                      4
   4.3 Project Support Functions                                                                   4


5. APPROACHWORK PACKAGES, SCHEDULES, AND BUDGET
                          65

    5.1 Component TestingWork Packages
        7       5
    5.2 Integration TestingDependencies
        7 5
    5.3 Conversion TestingResource Requirements
                57
    5.4 Job Stream TestingBudget Requirements
                57
    5.5 Interface TestingBudget and Resource allocation
                       57
    5.6 Security TestingSchedule
        57
    5.7 Recovery TestingNetwork Diagram
            58
    5.8 Performance Testing                                                                        8
    5.9 Regression Testing                                                                         8
    5.10 Acceptance Testing                                                                        8
    5.11 Beta Testing                                                                              8




TABLE OF CONTENTS (CONTINUED)




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        2
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan


6. PASS / FAIL CRITERIAROJECT SUCCESS CRITERIA
               88

    6.1 Suspension Criteria                                                                        8
    6.2 Resumption Criteria                                                                        8
    6.3 Approval Criteria                                                                          8



7. Testing Process                                                                                 9

    76.1 Test DeliverablesNetwork Diagram
       98
    76.2 Testing TasksProject Milestones
           98
    76.3 Responsibilities                 Approval Process
                       98
    76.4 ResourcesAcceptance Criteria
               98
    76.5 ScheduleCritical Success Factors
               98



87. Environmental RequirementsAdditional Components
                   108

    8.1 Hardware                                                                                   10
    8.2 Software                                                                                   10
    8.3 Security                                                                                   10
    8.4 Tools                                                                                      10
    8.5 Publications                                                                               10
    8.6 Risks and Assumptions                                                                      10


9. Change Management Procedures                                                                    11


10. Plan Approvals                                                                                 11
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        3
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

8. GLOSSARY OF TERMS                                                                               8

9. APPENDICES                                                                                      19




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        4
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

1. INTRODUCTION

     (NOTE 1: THE SOFTWARE TESTPROJECT MANAGEMENT PLAN GUIDELINES WERE DERIVED                                          Formatted
     AND DEVELOPED FROM IEEE STANDARD FOR SOFTWARE TEST DOCUMENTATION (829-
     1998)).1058.1
     STANDARD FOR SOFTWARE PROJECT MANAGEMENT PLANS (ANSI).

    (Note 2: The ordering of Software TestProject Management Plan (STPPMP)                                              Formatted
    elements is not meant to imply that the sections or subsections must be developed
    or presented in that order. The order of presentation is intended for ease of use, not
    as a guide to preparing the various elements of the Software TestProject
    Management Plan. If some or all of the content of a section is in another document,
    then a reference to that material may be listed in place of the corresponding
    content.)


    The Introduction section of the Software Test Plan (STP)PMP provides an overview of the                             Formatted
    project and the product test strategy, a list of testing deliverables, the plan for development
    and evolution of the STPPMP, reference material, and agency definitions and acronyms used
    in the STPPMP.

    The Software Test Plan (STP) is designed to prescribe the scope, approach, resources,                               Formatted
    and schedule of all testing activities. The plan must identify the items to be tested, the
    features to be tested, the types of testing to be performed, the personnel responsible for
    testing, the resources and schedule required to complete testing, and the risks
    associated with the plan.




             1.1 ObjectivesProject Overview
                  (       Describe, at a high level, the scope, approach, resources, and schedule of
                  the testing activities. Provide a concise summary of the test planproject
                  objectives, the products to be delivered, major work activities, major work
                  products, major milestones, required resources, and master high-level schedules,
                  and budget, and effort requirements.) The Project Overview describes the
                  relationship of this project to the agency mission, other projects, and business
                  impact.

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        5
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
             1.2 Testing StrategyProject Deliverables
                          Testing is the process of analyzing a software item to detect the                             Formatted
                  differences between existing and required conditions and to evaluate the
                  features of the software item. (This may appear as a specific document (such as
                  a Test Specification), or it may be part of the organization's standard test
                  approach. For each level of testing, there should be a test plan and an
                  appropriate set of deliverables. The test strategy should be clearly defined and the
                  Software Test Plan acts as the high-level test plan. Specific testing activities will
                  have their own test plan. Refer to section 5 of this document for a detailed list of
                  specific test plans.)
                  Specific test plan components include:
                     Purpose for this level of test,                                                                   Formatted: Bullets and Numbering
                                                                                                                        Formatted
                     Items to be tested,
                                                                                                                        Formatted
                     Features to be tested,                                                                            Formatted

                     Features not to be tested,                                                                        Formatted

                     Management and technical approach,                                                                Formatted

                     Pass / Fail criteria,                                                                             Formatted

                     Individual roles and responsibilities,                                                            Formatted

                     Milestones,                                                                                       Formatted

                     Schedules, and                                                                                    Formatted

                     Risk assumptions and constraints.                                                                 Formatted

                          Lists all of the items to be delivered to the customer.



             1.3      1.3 ScopeEvolution of the SPMP                                                                    Formatted: Bullets and Numbering

                  (       Specify the plans for producing both scheduled and unscheduled updates
                  to the Software TestProject Management Plan (change management). Methods for
                  distribution of updates shall be specified along with version control and
                  configuration management requirements must be defined.)
                  Testing will be performed at several points in the life cycle as the product is                       Formatted
                  constructed. Testing is a very 'dependent' activity. As a result, test planning
                  is a continuing activity performed throughout the system development life
                  cycle. Test plans must be developed for each level of product testing.
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        6
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan




             1.4               1.4 Reference Material                                                                   Formatted: Bullets and Numbering

                  (       Provide a complete list of all documents and other sources referenced in
                  the Software TestProject Management Plan. Reference to the following
                  documents (when they exist) is required for the high-level test plan:
                     Project authorization,
                     Project plan,
                     Quality assurance plan,
                     Configuration management plan,
                     Organization policies and procedures, and
                     Relevant standards.)




             1.5 Definitions and Acronyms
                  (      Specify definitions of all terms and agency acronyms required to properly
                  interpret the Software Test PlanPMP. Reference may be made to the Glossary of
                  Terms on the IRMC web page.)in Section 8.




                                                                                                                        Formatted: Bullets and Numbering
2. 2. TEST ITEMSPROJECT ORGANIZATION
    ( Specifyies the test items included in the plan. Supply references to the following item
    documentation:
            Requirements specification,                                                                                Formatted
                                                                                                                        Formatted: Bullets and Numbering
            Design specification,
                                                                                                                        Formatted
            Users guide,                                                                                               Formatted

            Operations guide,                                                                                          Formatted

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        7
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                       Software TestProject Management Plan
              Installation guide,                                                                                        Formatted

              Features (availability, response time),                                                                    Formatted

              Defect removal procedures, and                                                                             Formatted

              Verification and validation plans.)                                                                        Formatted




  process model for the project (system development life cycle (SDLC)), describes the project
  organizational structure, identifies organizational boundaries and interfaces, and defines
  individual responsibilities for the various project elements.

                        2.1 Program Modules2.1 Process Model
                        (       Outlines testing to be performed by the developer for each module
                        being built.)the relationships among major project functions and activities by
                        specifying the timing of major milestones, baselines, reviews, work products,
                        project deliverables, and sign-off that span the project. The process model or
                        system development life cycle (SDLC) approach may be described using a
                        combination of graphical and textual notations. The process model must
                        include project initiation and project closeout activities.



                    2.2 Job Control ProceduresOrganizational Structure
                        (      Describes testing to be performed on job control language (JCL),
                        production scheduling and control, calls, and job sequencing.)he internal
                        management structure of the project. Graphical devices such as hierarchical
                        organization charts or matrix diagrams may be used to depict the lines of
                        authority, responsibility, and lines of communications within the project.



                    2.3 User ProceduresOrganizational Boundaries and
Interfaces
                        (      Describes the testing to be performed on all user documentation to
                        ensure that it is correct, complete, and comprehensive.)administrative and
                        managerial boundaries between the project and the following entities: the
                        agency, the custom organization, subcontracted organizations, quality
                        assurance, or any other organizational entity interfacing with the project.



  C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                               20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                               e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                               VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                               QA\QAPLAN\PROJPLAN.doc                        8
                                               09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

                  2.4 Operator ProceduresProject Responsibilities
                      (D     Briefly describes the testing procedures to ensure that the application
                      can be run and supported in a production environment (include Help Desk
                      procedures)).responsibilities of project team members. A matrix of functions
                      and activities versus responsible individuals may be used to depict project
                      responsibilities.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        9
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan


3. Features To Be TestedMANAGEMENT PROCESS
    (IThis section dentify all software features and combinations of software features to be
    tested. Identify the test design specifications associated with each feature and each
    combination of features.)describes management objectives and priorities, project
    assumptions, dependencies, and constraints, risk management techniques, monitoring and
    control practices, and the staffing plan.

    3.1 Management Objectives and Priorities
            Explains the philosophy, goals, and priorities for management activities during the
    project. Topics to be specified may include: the frequency and mechanisms for project
    reporting, relative priorities among requirements, schedule, and budget for the project, risk
    management procedure to be followed, and statement of build versus buy approaches.

    3.2 Assumptions, Dependencies, and Constraints
            This section will state the assumptions on which the project is based, the external
    events the project is dependent upon, and the constraints under which the project is to be
    conducted.

    3.3 Risk Management
            Identify and assess the risk factors associated with the project. Describe the
    prescribed mechanisms for tracking the various risk factors (e.g., Kulik and Lazarus Project
    Self-Assessment and risk statistical analysis (RAMP) and implementing contingency plans.
    Risk factors that should be considered include contractual risk, technology risk, size and
    complexity risks, personnel acquisition and retention risks, and risks to achieving customer
    acceptance of the product.

    3.4 Monitoring and Control Mechanisms
            Explains the reporting mechanisms, report formats, information flows, review and
    audit mechanisms, and other tools and techniques to be used in monitoring, tracking, and
    controlling adherence to the Software Project Management Plan. The relationship of
    monitoring and control mechanisms to project support functions (e.g., SIPS, IRMC) shall be
    delineated in this section. Include a copy of the completed IRMC Project Proposal Checklist
    either in this section or in Section 9 Appendices). Detail the schedule and use of the IRMC
    Project Status Report (attached as Section 9 Appendices). Both the Project Proposal
    Checklist and the monthly Project Status Report are IRMC requirements.

    3.5 Staffing Plan
         Specify the numbers and types of personnel required to conduct the project.
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        10
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        11
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                       Software TestProject Management Plan




  4. FEATURES NOT TO BE TESTEDTECHNICAL PROCESS
          (Identify all features and specific combinations of features that will not be tested along
      with the reasons.)Describes the technical methods, tools, and techniques to be used on the
      project. In addition, the plan for software documentation shall be specified, and plans for
      project support functions such as quality assurance, configuration management, and
      verification and validation shall be identified.



4.1 Methods, Tools, and Techniques
           Specifies the computing system, development methodology, team structure, programming
           language, and other notations, tools, techniques, and methods to be used to specify,
           design, build, test, integrate, document, deliver, modify, or maintain the project
           deliverables. In addition, the technical standards, policies, procedures, and guidelines
           governing development shall be included or by reference to other documents. A Software
           Quality Assurance Plan will be required for the project. (Refer to Software Quality
           assurance Plan guidelines for instructions on completing an SQAP.)


                                                                                                                          Formatted
        4.2 Software Documentation
  Specifies directly, or by reference, the documentation plan
  for the software project. The documentation plan shall
  specify configuration management and version control
  requirements along with storage and media requirements.

       4.3 Project Support Functions
  This section shall contain, either directly or by reference,
  plans for the supporting functions of the software project.
  Supporting functions include (but may not be limited to):
                                                                                                                          Formatted: Bullets and Numbering
    Configuration management,
    Software quality assurance,
    Verification and validation plans,
  C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                               20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                               e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                               VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                               QA\QAPLAN\PROJPLAN.doc                        12
                                               09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
   Production support and operational support functions.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        13
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan



5. APPROACHWORK PACKAGES, SCHEDULES, AND BUDGET
    (DThis section escribeof the the overall approaches to testing. The approach should be
    described in sufficient detail to permit identification of the major testing tasks and estimation
    of the time required to do each task. Identify the types of testing to be performed along with
    the methods and criteria to be used in performing test activities. Describe the specific
    methods and procedures for each type of testing. Define the detailed criteria for evaluating
    the test results.)
    (For each level of testing there should be a test plan and the appropriate set of deliverables.
    Identify the inputs required for each type of test. Specify the source of the input. Also, identify
    the outputs from each type of testing and specify the purpose and format for each test output.
    Specify the minimum degree of comprehensiveness desired. Identify the techniques that will
    be used to judge the comprehensiveness of the testing effort. Specify any additional
    completion criteria (e.g., error frequency). The techniques to be used to trace requirements
    should also be specified.)




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        14
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                          Software TestProject Management Plan
     Software Project Management Plan will specify the work packages, identify the dependency
    relationships among them, state the project resource requirements, provide the allocation of
    budget and resources to work packages, and establish a project schedule.

             5.1 Component TestingWork Packages
                           (Testing conducted to verify the implementation of the design for one
                  software element (e.g., unit, module) or a collection of software elements.
                  Sometimes called unit testing. The purpose of component testing is to ensure that
                  the program logic is complete and correct and ensuring that the component works
                  as designed.)This subsection will define the work packages (work breakdown
                  structure (WBS)) for the activities and tasks that must be completed in order to
                  satisfy the project agreement. Each work package must be uniquely identified;
                  identification may be based on a numbering scheme and descriptive title. A
                  diagram depicting the breakdown of activities (Gantt Chart) may be used to
                  depict a hierarchical relationship among work packages.




             5.2 Integration TestingDependencies
                  ( Testing conducted in which software elements, hardware elements, or both
                  are combined and tested until the entire system has been integrated. The purpose
                  of integration testing is to ensure that design objectives are met and ensures that
                  the software, as a complete entity, complies with operational requirements.
                  Integration testing is also called System Testing.) This section will state the
                  ordering relations among work packages to account for interdependencies among
                  them and dependencies on external events. Techniques such as dependency lists,
                  activity networks, and the critical path method may be used to depict
                  dependencies among work packages.


             5.3 Conversion TestingResource Requirements
                  (       Testing to ensure that all data elements and historical data is converted
                  from an old system format to the new system format.)Identifies, as a function of
                  time, estimates of total resources required to complete the project. Numbers and
                  types of personnel, computer time, hardware, software, office facilities, travel,
                  training, and maintenance requirements are typical resources that should be
                  specified.


C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        15
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
             5.4 Job Stream TestingBudget Requirements
                  (Testing to ensure that the application operates in the production environment.)
                     Identifies, as a function of time, estimates of total budget dollars required to
                  complete the project.


             5.5 Interface TestingBudget and Resource Allocation
                  (T      esting done to ensure that the application operates efficiently and
                  effectively outside the application boundary with all interface systems.)Specify the
                  allocation of budget and resources to the various project functions, activities, and
                  tasks.


             5.6 Security Testing
                  (Testing done to ensure that the application systems control and auditability
                  features of the application are functional.)


             5.7 Recovery Testing
                  (Testing done to ensure that application restart and backup and recovery facilities
                  operate as designed.)


             5.8 Performance Testing
                  (Testing done to ensure that that the application performs to customer
                  expectations (response time, availability, portability, and scalability)).


             5.9 Regression Testing
                  (Testing done to ensure that that applied changes to the application have not
                  adversely affected previously tested functionality.)


             5.10 Acceptance Testing
                  (Testing conducted to determine whether or not a system satisfies the acceptance                      Formatted
                  criteria and to enable the customer to determine whether or not to accept the
                  system. Acceptance testing ensures that customer requirements' objectives are met
                  and that all components are correctly included in a customer package.)                                Formatted

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        16
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan


             5.11 Beta TestingSchedule
                  ( Testing, done by the customer, using a pre-release version of the product to                        Formatted
                  verify and validate that the system meets business functional requirements. The                       Formatted
                  purpose of beta testing is to detect application faults, failures, and defects.)                      Formatted



    Specify the schedule for the various project functions, activities, and tasks, taking into
    account the precedent relations and the required milestone dates. Schedules may be
    expressed in absolute calendar time or in increments relative to key project milestones.




6. PASS / FAIL CRITERIAROJECT SUCCESS CRITERIA
         ( Specify the criteria to be used to determine whether each item has passed or failed
         testing.)Describes the project milestones and checkpoints, key deliverables, acceptance
         criteria, and management approval process for project and product deliverables..

         6.1 Suspension Criteria
                  (Specify the criteria used to suspend all or a portion of the testing activity on test                Formatted
                  items associated with the plan.)                                                                      Formatted




         6.2 Resumption Criteria
                  (Specify the conditions that need to be met to resume testing activities after
                  suspension. Specify the test items that must be repeated when testing is resumed.)


         6.3 Approval Criteria
                  (Specify the conditions that need to be met to approve test results. Define the
                  formal testing approval process.)




                                                                                                                        Formatted
7. Testing Process
         (Identify the methods and criteria used in performing test activities. Define the specific
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        17
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                           Software TestProject Management Plan
         methods and procedures for each type of test. Define the detailed criteria for evaluating
         test results.)                                                                                                 Formatted




         7.1 Test Deliverables
                  (Identify the deliverable documents from the test process. Test input and output                      Formatted
                  data should be identified as deliverables. Testing report logs, test incident
                  reports, test summary reports, and metrics' reports must be considered testing
                  deliverables.)


         7.2 Testing Tasks
                  (Identify the set of tasks necessary to prepare for and perform testing activities.
                  Identify all intertask dependencies and any specific skills required.)


         7.3 Responsibilities
                  (Identify the groups responsible for managing, designing, preparing, executing,
                  witnessing, checking, and resolving test activities. These groups may include the
                  developers, testers, operations staff, technical support staff, data administration
                  staff, and the user staff.)


         7.4 Resources
                  (Identify the resources allocated for the performance of testing tasks. Identify the                  Formatted
                  organizational elements or individuals responsible for performing testing
                  activities. Assign specific responsibilities. Specify resources by category. If
                  automated tools are to be used in testing, specify the source of the tools,
                  availability, and the usage requirements.)                                                            Formatted



         7.5 Schedule
                  (Identify the high level schedule for each testing task. Establish specific                           Formatted
                  milestones for initiating and completing each type of test activity, for the
                  development of a comprehensive plan, for the receipt of each test input, and for
                  the delivery of test output. Estimate the time required to do each test activity.)                    Formatted

                  (When planning and scheduling testing activities, it must be recognized that the                      Formatted
                  testing process is iterative based on the testing task dependencies.)                                 Formatted




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        18
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan



                                                                                                                        Formatted
8. Environmental Requirements
    6.1 Network Diagram
           This subsection will define the project network diagram, including the critical path.
    The network diagram may be included as an Appendix.

    6.2 Project Milestones
            This section will identify the project milestones. A milestone is a clearly identifiable
    point in time that summarizes the completion of a related or important set of tasks (e.g.,
    design, testing). Milestones are commonly used as a reference point or summary of important
    events in a project.

    6.3 Approval Process
            Identifies the management process for obtaining approval of project deliverables, as
    well as any "go" / "no-go" decision points in the project.

    6.4 Acceptance Criteria
             Identifies the customer acceptance criteria for project implementation

    6.5 Critical Success Factors
           Describes critical success factors (such as within budget, on schedule, 100%
    functionality) identified by the client as well as the project quality goals. Identify and
    quantify all project goals. Prioritize the project goals: cost, schedule, or functionality.



.
7. Additional Components
   (Specify both the necessary and desired properties of the test environment including the
   physical characteristics, communications, mode of usage, and testing supplies. Also provide
   the levels of security required to perform test activities. Identify special test tools needed and
   other testing needs (space, machine time, stationary supplies. Identify the source of all needs
   that is not currently available to the test group.)     Certain additional components may be
   required. These may be included by appending additional sections to the Software Project
   Management Plan. Additional items of importance may include subcontractor management
   plans, security plans, architecture plans, independent verification and validation plans,
   training plans, hardware procurement plans, data conversion plans, installation plans,

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        19
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                          Software TestProject Management Plan
    system transition and rollout plans, or product maintenance and support plans.

         8.1 Hardware
                  (Identify the computer hardware and network requirements needed to complete
                  test activities.)


         8.2 Software
                  (Identify the software requirements needed to complete testing activities.)


         8.3 Security
                  (Identify the testing environment security and asset protection requirements.)


         8.4 Tools
                  (Identify the special software tools, techniques, and methodologies employed in
                  the testing efforts. The purpose and use of each tool shall be described. Plans for
                  the acquisition, training, support, and qualification for each tool or technique.)
                                                                                                                        Formatted


         8.5 Publications
                  (Identify the documents and publications that are required to support testing
                  activities.)


         8.6 Risks and Assumptions
                  (Identify significant constraints on testing such as test item availability, test
                  resource availability, and time constraints. Identify the risks and assumptions                       Formatted
                  associated with testing tasks including schedule, resources, approach and
                  documentation. Specify a contingency plan for each risk factor.)                                      Formatted




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        20
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan



9. Change Management Procedures

         (Identify the software test plan change management process. Define the change initiation,
         change review, and change authorization process.)



10. Plan Approvals
         (Identify the plan approvers. List the name, signature and date of plan approval.)




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        21
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

8.Glossary of Terms                                                                                                     Formatted: Bullets and Numbering

(AN INDEX OR GLOSSARY OF TERMS, USED THROUGHOUT THE SOFTWARE PROJECT MANAGEMENT PLAN IS
OPTIONAL BUT RECOMMENDED TO IMPROVE USABILITY AND PROVIDE DEFINITIONS OF COMMON TERMS USED
THROUGHOUT THE SYSTEM DEVELOIPMENT LIFE CYCLE.)



                                                         A

Acceptance Criteria – The list of requirements that must be satisfied prior to the customer
accepting delivery of the product.

Acceptance Test – Formal user performed testing performed prior to accepting the system
(sometimes called client acceptance test or user acceptance test).

Acquisition – Generic term for hardware, software, or services acquired from an outside
vendor or contractor.

Action Plan - A plan that describes what needs to be done and when it needs to be completed.
Project plans are action plans.

Activity - A specific project task, or group of tasks, that require resources and time to
complete.

Adaptive System – Describes software that has flexibility as the primary design point.

Application – Generic term for a program, or system, that handles a specific business function.

Application Software – A complete, self-contained program that can perform work for a user.
This is in contrast to system software such as an operating system, server processes, and
libraries that exist in support of application software.

Approval Cycle – Process of gaining funding and management approval prior to project
initiation.

Architecture – Imposes order and makes interconnections possible. Generally defined as an
intermediate step between initial requirements and business functional specifications during
which the entire complex of hardware, software, and design considerations are viewed as a
whole. Refers to a blueprint for evolving a technical infrastructure.

Assessment – A general term for the formal management review of a process.

Audit - A formal and detailed examination of the progress, costs, operations, results, or some
other aspect of a project or system performed by an independent party.

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        22
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
Availability – The portion of time that a system that is scheduled to operate actually can be
used as expected.

Glossary of Terms* (continued)

                                                         B

Backbone – A high-speed computer network designed to interconnect lower-speed networks or
clusters of dispersed user devices.

Baseline – A specification, or product, that has been formally agreed upon which serves as the
starting point against which progress will be judged.

Baseline Plan - The initial approved plan to which deviations will be compared as the project
proceeds. A work product that has been formally approved and that can be changed only
through formal change control procedures.

Batch – A term describing a method of operating computers. This method takes groups of
transactions, executes them, and returns the results, all without human intervention.

Bench Mark – A standard figure of merit which measurements or comparisons may be made.

Bridge – Devices that connect two separate networks. Once bridging is accomplished, the
bridge makes interconnected networks look like a single network.

Budget – A planned sequence of expenditures over time with costs assigned to specific tasks
and activities.

                                                         C

CASE – Computer Aided Software Engineering - Systems that attempt to automate some or
all of the tasks involved in managing, designing, developing, and maintaining software systems.

Change Management – The formal process of recording, analyzing, estimating, tracking and
reporting of changes to the project baseline business functional requirements.

Checkpoint – A point in the development process at which project state, status, and results are
checked, recorded, and measured.

Client/Server System – Primarily a relationship between processes running on separate
machines. A client initiates the dialog by sending requests to the server asking for information
or action.

Confidence Level - A level of confidence, stated as a percentage, for a budget or schedule
estimate. The higher the confidence level, the lower the risk.
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        23
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

Configuration Management – Methodical storage and recording of all software components
and deliverables during development.

Connectivity – Refers to the ability to send and receive information between locations,
devices, and business services.


Glossary of Terms* (continued)


Contingency Plan - An alternative for action if the project does not proceed according to plan
or if the expected results are not achieved.

Control - A process for assuring that reality, or actual performance, meets expectations or
plans.

Cooperative Processing – Computing that requires two or more distinct processors to
complete a single transaction.

Cost / Benefit Analysis – A formal study in which the development, execution, and
maintenance costs for a project are matched against the anticipated value of the product.

Critical Activity - A task, activity, or event that, if delayed, will delay another important event -
probably the completion of the project or a major milestone in the project.

Critical Path – Derived from the PERT method, this term implies the set of activities that must
be completed in sequence and on time if the entire project is to be completed on time. A missed
task on the critical path will cause a product delivery delay. This is the longest time for the
project from beginning to end.

Critical Path Method (CPM) - One of the two most common forms of networking systems.
CPM uses a one-time estimate for creating a project schedule.

Customer - The individual or organization that specifies and accepts the project deliverables.

                                                         D

Data – Describes the numbers, text, graphics, images, and voice stored in a form that can be
used by a computer.

Data Warehouse – Where you consolidate and store data from many sources.

Deliverable – A tangible, physical object that is the output of a software development task.

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        24
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
Dependency Diagram - Another name for a network or precedence diagram that shows the
dependencies among tasks.

Design – The tasks associated with specifying and sketching the features and functions of a
new application prior to coding.

Development Project – The sum of all tasks and activities necessary to build a software
product.

Document of Understanding – A formal agreement between two parties. A contract which is
sometimes referred to as a Statement of Work (SOW).

Glossary of Terms* (continued)

Documentation – The printed and displayed materials which explain an application to a user.

Duration - The period of time over which a task takes place. Duration establishes the schedule
for a project.

                                                         E

Effectiveness - A measure of the quality of attainment in meeting objectives.

Efficiency - A measure of the volume of output received for the input used.

Effort - The amount of work or labor (in hours or workdays) required to complete a task.

Environment – The set of tools and physical surroundings in which software is developed.

Estimate – A predicted total of expenditures required to complete a task, activity, or project.

Exit Criteria – The set of conditions that must be met prior to completing a project phase or
application.

                                                         F

Feasibility Project – A project designed to prove, or disprove, the appropriateness of the
technology solution under existing constraints (sometimes called “proof-of-concept” project).

Float - The amount of time for a task to be freely scheduled without affecting other tasks in the
project.

Function - An activity that spans the entire duration of a software project (e.g., status reporting,
quality assurance, verification and validation).


C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        25
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
                                                         G

Gantt Chart – A method of displaying overlapped and partially concurrent activities by using
horizontal lines to reflect the time required by each activity. The chart, named for Henry
Lawrence Gantt, consists of a table of project task information and a bar chart that graphically
displays the project schedule to be used in planning and tracking.

Gateway – Hardware or software that translates between two dissimilar protocols.

Granular – Describes the art of writing small modules of code and / or objects.

Graphical User Interface (GUI) – A manner of presentation that makes use of windows, icons,
menus, pointers, and scroll bards.


Glossary of Terms* (continued)

                                                         H

Hardcode – An informal term that describes a programming technique where data or
procedures are specifically written into the program instructions.

Hardware – Physical equipment used to process, store, or transmit computer program data.

                                                          I

Independent Review – A formal examination of a project conducted by an organization other
than the development organization.

Information – The meaningful interpretation of data.

IRMC – Information Resource Management Commission.

Integration – Describes the work, or device, required to connect two different systems that
were not originally designed to work together.

Integration Test – Testing in which software components, hardware components, or both are
combined and tested to evaluate the interaction between them.

Interface – A connection between two devices or systems.

Interoperability – The ability to have applications and computers from different vendors work
together on a network.

Intranet – An Internet network behind a firewall.
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        26
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

Issue – A problem to be solved or a decision that has not been made.

                                                         J

Joint Application Design (JAD) - The combined effort of client, program, and development
staff to define and elicit requirements for a system (JAR) or design a system (JAD).

                                                         K
                                                         L

Lag - The amount of time after one task is started or finished before the next task may be
started or finished.

Lead - The amount of time that precedes the start of work on another task.

Local Area Network (LAN) – A communications system confined to a limited area, typically a
building, occasionally a group, and linking computers together via cable.

Glossary of Terms* (continued)

                                                         M

Maintenance – Refers to the ongoing activity that keeps software functioning in a technical and
business environment (production).

Methodology – A set of formal protocols followed when performing a task.

Middleware – Software that hides the complexity of the networked computing environment
from the users and application programmers.

Milestone – A major checkpoint in the activities involved in a project. A clearly defined point in
a project that summarized the completion of a related set of tasks.

Model - A way of looking at reality, usually for the purpose of abstracting and simplifying it to
make it understandable in a particular context.

Modular Programming – Programming that has as its fundamental assumption that a large
piece of software should be separated into its constituent parts or modules thereby making for
easier and faster development and maintainability. Modules were traditionally called subroutines
or functions and now are often called objects.

                                                         N

Network – Describes the physical hardware and software connections between computers
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        27
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
allowing information to be shared and electronic communications to take place.

Network Diagram - The logical representation of tasks that defines the sequence of work in a
project.

N-tier Architecture – Describes a method for dividing an application into a series of distinct
layers to provide for ease of maintenance and flexibility.

                                                         O

Operating System – System software that controls data storage, input and output to and from
the keyboard, and the execution of applications written for it. It performs base services:
prioritizing work, scheduling, memory management, etc.

                                                         P

Package Acquisition – The purchase, or lease, of software from an outside source.

Padding - A standard project management tactic used to add extra time or money to estimates
to cover for the uncertainty and risk of predicting future project activities.

Path - A sequence of lines and nodes in a project network.

Glossary of Terms* (continued)

PERT – Project Evaluation and Review Technique - The PERT method uses the concepts of
milestones, activities, and slack time to calculate the critical path. The chart, which resembles a
flow chart, depicts a box to represent each project task and a line connecting two boxes to
represent the relationship between tasks.

Phases – The divisions of a software development life cycle into discrete stages (e.g.,
requirements, design, code, test, etc.).

Planning Project – A project intended to gather, or predict, the sequence of activities and
resources needed to complete a work effort.

Platform – The hardware and support software with which a program is intended to operate.

Precedence - When one task must be completed before another task can be started, the first
task is said to have precedence over the other.

Process – The step by step sequence of activities (systematic approach) that must be carried
out to complete a project.

Programming – The art of writing, in a computer understandable language, a set of
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        28
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
instructions that produces software.

Project – The combined resources (people, machines, materials), processes, and activities that
are dedicated to building and delivering a product to a customer.

Project Duration - The time it takes to complete the entire project.

Project Management - The combination of systems, techniques, and people required to
successfully complete a project on time and within budget.

Project Manager – The senior person responsible for the entire project.

Project Plan – A formal document that describes the technical and management approach to
be followed for a project.

Project Sponsor – The department “customer” who will authorize project initiation, and who will
receive, accept, and use the software product or service.

Protocol – A set of rules and specifications that describes how a piece of software will behave
and how other pieces of software must behave in order to work with the first piece of software.

                                                         Q

Quality (Product) - Conformance to business functional requirements with defect-free products.
Quality reflects both the completeness of software or system features and functions, and error-
free operation.
Glossary of Terms* (continued)

Quality (Process) – Verification and validation to established policies, standards, procedures
and guidelines for software development.

Quality Assurance – Within the State of North Carolina, the process tracking and oversight
function for monitoring project performance, adherence to commitments, and budget
requirements. Performed under the control of the Department of Commerce, Information
Resource Management staff.

                                                         R

Regression Test – Selective re-testing to detect errors or faults introduced during modification
of a system.

Relational Database – A collection of data that is organized into tables so that relationships
between and among data can be established.

Resource Leveling - The process of shifting resources to even out the workload of team
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        29
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
members.

RFP - Request for Proposal - Formal statement by a department that they are soliciting
enterprises to bid on a contract for a program, system or service.

Requirements – The statement of needs by a user that triggers the development of a program,
system, or project. May be called business functional requirements or requirement
specifications.

Research and Development Project – A definition of a project type essentially exploring
options for developing new systems or work products.

Risk – The probability that a project will experience undesirable events, which may create, cost
overruns, schedule delays, or project cancellation. The identification, mitigation, tracking, and
management of those elements creating the risk situation.

Risk Analysis - An evaluation of the feasibility or probability that the outcome of a project will
be the desired outcome.

                                                         S

Scalable – A term describing an architecture or software that can handle expansion in the use
as the need arises without adversely impacting systems management and operations.

Scope - The magnitude of the effort required to complete a project.

Server – A computer on a network that makes applications, print services, data, and
communications available.


Glossary of Terms* (continued)


SIPS – State Information Processing Services.

Slack - see float.

Software – Computer programs, systems, and the associated documentation that describes
them.

SDLC - Software Development Life Cycle – The period of time that begins with the decision
to develop a software product and ends when the software is delivered.

Software Development Process – The process by which user needs are translated into a
software product.
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        30
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

Software Project Management Plan - The controlling document for managing a software
project. The SPMP defines the technical and managerial project functions, activities, and tasks
necessary to satisfy the requirements of a software project.

Specifications – General term for the wide variety of paper-based descriptions of a program or
system.

Stakeholders - People who have a personal or agency interest in the end results of a project.

Standalone – Describes a computer workstation where the computer is not connected to any
other computer on a network.

Statement of Work (SOW) - An integrated set of task descriptions, goal descriptions, risks,
and assumptions that accompany the evolving master project plan during development.

Strategic Plan – The long range plan where the horizon is usually three to five years time
span.

Subcontract - Delegating tasks or sub-projects to contractors or other organizations.

System – A linked collection of programs, or components, that perform a generic business or
technical function.

System Test – The final stage of testing on a completed project (prior to client acceptance test)
when all hardware and software components are put together and tested as a whole.

SDLC - System Development Life Cycle - The complex of tasks and deliverables that are
organized toward developing software systems.


Glossary of Terms* (continued)

                                                         T

Tactical Plan – Specific improvements, or changes, that will be carried out in a fairly short time
span (usually twelve (12) months).

Task - A cohesive unit of work on a project (usually 40 to 80 hours of effort).

Task Description - A description that defines all the work required to complete a project task or
activity including input, output, expected results, and quality specifications.

Test Plan – A document that describes the scope, approach, resources, and schedule of
intended test activities.

C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        31
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

Testing – The set of defect removal tasks that include execution of all, or part, of an application
on a computer.

Topology – The map or plan of a network.


                                                         U

Unit Test - The testing carried out personally by individual programmers on their own code.


                                                         V

                                                         W


Wide Area Network (WAN) – A network where the computers are separated by significant
distances and telecommunications links are implemented.

Work Breakdown Structure (WBS) – A formal analysis of the activities, tasks, and sub-tasks
that must be accomplished to build a software project. A product or activity oriented hierarchy
tree depicting the elements of work that need to be accomplished in order to deliver a product.

Work Package - A specification for the work to be accomplished in completing an activity or
task.

Work Product - Any tangible item that results from a project function, activity, or task.

Workstation – Any machine with all of its installed storage, processing, and communications
that can be either standalone or networked.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        32
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan


Glossary of Terms* (continued)


                                                         X

                                                         Y

                                                          Z




* Definitions were extracted from Assessment and Control of Software Risks by Capers
Jones (1994); Managing Software Development Projects (Second edition) by Neal Whitten
(1995); IEEE Standards Collection: Software Engineering (1997 Edition); Best Practices in
IT Architecture Planning and Implementation by Larry DeBoever; Essential Client/Server
Survival Guide by Robert Orfali; and The Complete Idiot's Guide to Project Management by
Sunny and Kim Baker.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        33
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan




9. APPENDICES
    Appendices may be included, either directly or by reference, to provide supporting details
that could aid in the understanding of the Software Project Management Plan.



                            North Carolina State Government
                     Information Resource Management Commission
                             PROJECT PROPOSAL CHECKLIST
As approved by the IRMC: July 2, 1996                                                                  Revision Date: July 15, 1998




      Project Proposal Checklist Instructions

      Purpose

      The Project Proposal Checklist verifies that essential activities have been planned or performed to
      help ensure that proposed systems development or technology implementation projects are
      completed on time and within budget, and the expected benefits are realized.

      The checklist, responses, and supporting documentation will be validated in conjunction with the
      performance of the independent third-party quality assurance (QA) reviews throughout the project
      life cycle.


      Responsibility for Preparing Checklist

      The department proposing the project must prepare the checklist. All “No” responses must be
      explained.
      All “Yes” responses require the identification of the appropriate project documentation supporting the
      response.


      Projects Requiring a Checklist

      You must prepare a checklist if the project either:
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        34
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan

       results in total long-term expenditures over $500,000; OR                                                       Formatted: Bullets and Numbering

       is a Statewide strategic project, regardless of cost; OR
       is a major project, regardless of cost; OR
       has been designated a Priority 1 or 2 replacement effort by the Statewide Year 2000 Project
        Office.


      Statewide strategic projects are direction-setting projects that include multiple programs and / or
      Departments or Agencies. These projects may involve interfaces with other applications, provide
      data to or receive information from other applications or governmental programs or organizations.
      Statewide strategic projects impact state and local governments, private industry, citizens, and / or
      State employees beyond the Department / Agency.
      Major projects include projects that must be completed successfully (on time, within budget, and with
      the expected results and benefits) in order to avoid public embarrassment, shortcomings in the
      performance of business responsibilities or program operations, or detrimental deficiencies in the
      delivery of services. Major projects present unusual or high risks. These risks can be: technical (for
      example; implementing technology new to the department or state); business; organizational; or
      other areas (for example; system size; project duration; timetable flexibility; technical or business
      complexity; implementation challenges; importance to the operations of the state; and interrelations
      with other systems or departments).



      Timetable for Submitting Checklist

      1. Checklists for every systems development or technology implementation project must be                          Formatted: Bullets and Numbering
         submitted with your departmental biennial technology plan.
      2. Checklists for other projects must be provided to the IRM staff as early as possible in the
         planning process.
      3. Checklists should be updated and submitted to the IRM staff as the project progresses through
         the appropriate lifecycle phases or project milestone; i.e. - Requirements Definition, Design,
         Code, Systems Test, User Acceptance Test, Implementation, and Post-implementation support.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        35
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                           Software TestProject Management Plan

Activity                                                                             Yes         No1         Cross Reference 2


1.    Project Objective
     a) Are the project’s objectives and goals verifiable, defined, and                                                          Formatted: Bullets and Numbering
        stated?
     b) Is this project strategically aligned with departmental missions,                                                        Formatted: Bullets and Numbering
        goals, and objectives?
     c) Have or will business or program practices and procedures be re-                                                         Formatted: Bullets and Numbering
        engineered before or as part of the implementation of the system
        or technology?




2. Project Departmental Sponsorship
     a) Has departmental senior management approved this project?                                                                Formatted: Bullets and Numbering

     b) Will departmental senior managers be involved with this project on                                                       Formatted: Bullets and Numbering
        a regular basis?
     c) Has the project sponsor from the business or program area been                                                           Formatted: Bullets and Numbering
        identified?
     d) Will the project sponsor from the business or program area                                                               Formatted: Bullets and Numbering
        participate in this project on a regular and ongoing basis?
     e) Has the sponsoring business or program area participated in the                                                          Formatted: Bullets and Numbering
        development of the project management and organization
        documentation, including the work plan?


3. Project Cost / Benefit Analysis
     a) Are expected benefits (including improved or new services and                                                            Formatted: Bullets and Numbering
        cost savings) verifiable?
     b) Have the expected benefits been identified, documented, and                                                              Formatted: Bullets and Numbering
        quantified?
     c) Have all relevant costs been identified, documented, and                                                                 Formatted: Bullets and Numbering
        estimated?
     d) Has a cost/benefit analysis (such as pay back period, internal rate                                                      Formatted: Bullets and Numbering
        of return, return on investment, etc.) been performed?
     e) Have project funding sources been identified and approved?                                                               Formatted: Bullets and Numbering

     f)    Have departmental senior management and the project                                                                   Formatted: Bullets and Numbering
           business/program sponsor approved the cost/benefit analysis?

      C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                                   20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                                   e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                                   VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                                   QA\QAPLAN\PROJPLAN.doc                        36
                                                   09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
Notes:
1. Explanations for all “No” responses must be attached.
2. All “Yes” responses require the identification of the appropriate project documentation supporting the
response.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        37
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                          Software TestProject Management Plan

Activity                                                                            Yes         No1         Cross Reference 2


4. Project Technology
    a) Has an application architecture been developed and documented?                                                           Formatted: Bullets and Numbering

    b) Does the technology make use of the state’s technical physical                                                           Formatted: Bullets and Numbering
       and applications development infrastructure?
    c) Does the technology conform to the state’s technical architecture?                                                       Formatted: Bullets and Numbering

    d) Has the proposed application architecture been reviewed and                                                              Formatted: Bullets and Numbering
       approved by the IRM Chief Technology Officer (CTO)?
           If YES, attach approval document indicating approval
                authority and date of approval.
           If NO, indicate planned date of submission for IRM /CTO
                approval.
    e) Has commercial off-the-shelf software (COTS), state transfers, or                                                        Formatted: Bullets and Numbering
       turnkey systems been considered as part of the business solution
       (package acquisition)?
    f)     Are common business applications services that are required by                                                       Formatted: Bullets and Numbering
           the system being provided by the state’s technical infrastructure?
    g) Are new business applications services being developed by this                                                           Formatted: Bullets and Numbering
       project that are common to other systems going to be added to the
       state’s technical infrastructure?


  5. Project Risk Profile
    a) Have major project risk factors been identified and documented?                                                          Formatted: Bullets and Numbering
       (Risk factors may include: size; organizational structure; number of
       parties involved; availability of adequate funds; technical
       complexity; length of schedule; knowledge of technology being
       used; experience of project management team; skills of staff;
       volatility of business requirements; experience with tools being
       employed; data conversion and other implementation complexities;
       flexibility in schedule; number of interfaces within and outside of
       project team control; etc.).
    b) Has each major risk factor been analyzed to determine its potential                                                      Formatted: Bullets and Numbering
       adverse impact on the project and probability of occurrence?
    c) Have steps or factors for mitigating the risks been identified,                                                          Formatted: Bullets and Numbering
       documented, and incorporated in project plans and activities?
    d) Has a formal risk identification, tracking, and mitigation process                                                       Formatted: Bullets and Numbering
       been identified?
    e) Have procedures been developed to monitor continuously the                                                               Formatted: Bullets and Numbering
       major risk factors, so they can be managed as the project

     C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                                  20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                                  e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                                  VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                                  QA\QAPLAN\PROJPLAN.doc                        38
                                                  09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
   progresses?

Notes:
1. Explanations for all “No” responses must be attached.
2. All “Yes” responses require the identification of the appropriate project documentation.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        39
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                          Software TestProject Management Plan

Activity                                                                            Yes         No1         Cross Reference 2


6. Project Management and Organization
    a) Will an experienced project manager be assigned to this project                                                          Formatted: Bullets and Numbering
       who has completed the state's project management education
       program or received equivalent training?
    b) Will the project adhere to a formal systems development life cycle                                                       Formatted: Bullets and Numbering
       methodology (SDLC)?
    c) Does the project have a budget, supporting schedule, work plan,                                                          Formatted: Bullets and Numbering
       and work packages incorporating major phases, tasks, due dates,
       responsibilities, deliverables, and time and effort estimates?
    d) Have Gantt, PERT, and Critical Path charts been prepared so that                                                         Formatted: Bullets and Numbering
       interdependent activities and essential timetables are known?
    e) Has a formal project organization structure and management                                                               Formatted: Bullets and Numbering
       process (including regular progress reporting and communication
       among team members, sponsors, and all oversight bodies) been
       developed?
    f)     Have clear responsibilities and reporting relations been indicated                                                   Formatted: Bullets and Numbering
           on the project organization chart in the work plan?
    g) Have personnel resource needs been determined by identifying                                                             Formatted: Bullets and Numbering
       skill and experience requirements and work effort estimates?
    h) Are the necessary skills and experiences available or are training                                                       Formatted: Bullets and Numbering
       times included in the project work plan?

    i)     Has a change management process been developed and agreed                                                            Formatted: Bullets and Numbering
           upon by all participants?
    s) Does the project work plan include provisions and time for data                                                          Formatted: Bullets and Numbering
       conversion, user training, and system documentation preparation?
    k) Are representatives from the business and program areas included                                                         Formatted: Bullets and Numbering
       included in the project work plan, including personnel that will use
       the system when it is installed?

    l)     Does the project work plan include the development of a                                                              Formatted: Bullets and Numbering
           maintenance plan?
    m) Does the project work plan include the development of resource                                                           Formatted: Bullets and Numbering
       requirements provided by SIPS, such as computing, data storage,
       and communications needs?
    n) Have formal documents of understanding with SIPS been                                                                    Formatted: Bullets and Numbering
       documented, reviewed, and agreed to by SIPS?

    o) Have estimates been developed for project work efforts and costs?                                                        Formatted: Bullets and Numbering

    p) Have department staff members assigned to the project completed                                                          Formatted: Bullets and Numbering

     C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                                  20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                                  e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                                  VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                                  QA\QAPLAN\PROJPLAN.doc                        40
                                                  09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
   applicable portions of the state's education program for the
   statewide technical architecture?

1. Explanations for all “No” responses must be attached.
2. All “Yes” responses require the identification of the appropriate project documentation.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        41
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                          Software TestProject Management Plan

Activity                                                                            Yes         No1         Cross Reference 2


Project Training
    a) Is there a formal education and training plan or does the project                                                        Formatted: Bullets and Numbering
       work plan include the time and resources for the development of
       this plan?
    b) Does the formal education and training plan identify the curricula,                                                      Formatted: Bullets and Numbering
       delivery mechanisms, and audiences (e.g., senior management,
       departmental executives, project staff, and end users), or are there
       tasks in the project work plan to address these?

    c) Are automated aids and resources being used to support training                                                          Formatted: Bullets and Numbering
       needs for project staff and users?



8. Project Support and Logistics
    a) Have tools (including project management, configuration                                                                  Formatted: Bullets and Numbering
       management, change management, version control, productivity,
       CASE, testing, etc.) for managing and performing the project been
       identified?
    b) Have time and effort been allocated in the project work plan for                                                         Formatted: Bullets and Numbering
       acquiring, configuring, and learning the support tools?
    c) Has the project work plan been adjusted for staff training time for                                                      Formatted: Bullets and Numbering
       time for the support tools?

    d) Have the needs for subject matter experts been identified, and are                                                       Formatted: Bullets and Numbering
       those requirements reflected in the project work plan?
    e) Have the needs for other logistical items (such as workspace,                                                            Formatted: Bullets and Numbering
       workstations, LAN support, telephones, development and testing
       environments, etc.) been determined?
    f)     Does the project work plan accommodate the time required to                                                          Formatted: Bullets and Numbering
           acquire, install, and become competent with the necessary
           logistical items?
    g) Will automated aides be used for supporting data conversion, user                                                        Formatted: Bullets and Numbering
       training, and system documentation preparation?
    h) Does the project work plan include time and work efforts for                                                             Formatted: Bullets and Numbering
       coordinating with organizations providing shared services (e.g.,
       SIPS) and other departments involved in the system or
       technology?
    i)     Does the project work plan include participation of the                                                              Formatted: Bullets and Numbering
           departmental staff so that the department will be able to maintain
           the system after installation?

     C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                                  20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                                  e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                                  VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                                  QA\QAPLAN\PROJPLAN.doc                        42
                                                  09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
Notes:
1. Explanations for all “No” responses must be attached.
2. All “Yes” responses require the identification of the appropriate project documentation supporting the
response.




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        43
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                           Software TestProject Management Plan


Activity                                                                             Yes         No1         Cross Reference 2


9.    Project Tracking and Oversight
     a) Have standards, conventions and documentation requirements                                                               Formatted: Bullets and Numbering
        been developed for major activities (for example: requirements’
        analysis, program specifications, coding, etc.)?
     b) Will formal procedures and processes (such as JAD, etc.) be                                                              Formatted: Bullets and Numbering
        employed to ensure adequate participation by business and
        program personnel?
     c) Has a formal quality plan identifying quality goals and defect                                                           Formatted: Bullets and Numbering
        prevention activities been developed?
     d) Have detailed practices and techniques (such as design reviews,                                                          Formatted: Bullets and Numbering
        code inspections, etc.) been determined for identifying and
        correcting defects as early as possible in the implementation
        process?
     e) Have checkpoints for formal independent quality assurance                                                                Formatted: Bullets and Numbering
        reviews been identified?
     f)    Have the scopes and focuses of each quality assurance review                                                          Formatted: Bullets and Numbering
           been determined?
     g) Has the appropriate funding been allocated to support the                                                                Formatted: Bullets and Numbering
        performance of third-party independent QA reviews (minimum
        (minimum guidelines are 5% of total development budget through
        the first year in production)?

     h) Is the department’s internal quality assurance function involved in                                                      Formatted: Bullets and Numbering
        the project?


10. Project Testing
     a) Are all business and technical requirements testable?                                                                    Formatted: Bullets and Numbering

     b) Will all business functional requirements be tested?                                                                     Formatted: Bullets and Numbering

     c) Will all test cases be traceable to business functional                                                                  Formatted: Bullets and Numbering
        requirements?
     d) Has a formal project test plan (including unit, integration, system,                                                     Formatted: Bullets and Numbering
        performance, regression, and user acceptance tests) been
        developed?
     e) Will historical data files be converted?                                                                                 Formatted: Bullets and Numbering

     f)    Has a project test matrix been developed?                                                                             Formatted: Bullets and Numbering

     g) Will the testing process (including test cases) be automated?                                                            Formatted: Bullets and Numbering


      C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                                   20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                                   e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                                   VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                                   QA\QAPLAN\PROJPLAN.doc                        44
                                                   09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                      Software TestProject Management Plan
h) Have acceptance criteria been established?                                                                            Formatted: Bullets and Numbering

 Notes:
 1. Explanations for all “No” responses must be attached.
 2. All “Yes” responses require the identification of the appropriate project documentation supporting the
 response.
                                            State of North Carolina
                                   Information Resource Management Commission

                          Project Status Report
          Report Dates From: ____________ To: ______________
                 Report Submission Date: _____________

 I.        Project Information:                                                                                          Formatted: Bullets and Numbering

 Department / Agency:
 Project Name:

 Project Sponsor:                                       Telephone Number:
 Preparer’s Name:                                       Fax Number:
 Plan Start Date:                                       Actual Start Date:
 Plan End Date:                                         # of Plan Revisions:


 II.       Project Current Phase Information:

 SDLC:                                                  Plan Start:
 Phase:                                                 Plan Complete:
 % Complete:                                            Actual Start:



 III a.    Project Report Information: As of date: ______________

  Project Cost          Month         Month Plan          Project to Date         Project to Date Plan
                        Actual                                Actual
       Hours
       Dollars



 III b.    Year 2000 Reporting:

       System       Plan          Actual      Plan        Actual      Original      Spent      Est. to        %
       Phase        Start         Start       End          End        Estimate                Complete       Comp

 C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                              20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                              e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                              VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                              QA\QAPLAN\PROJPLAN.doc                        45
                                              09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
     Design
      Modify
        Test




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        46
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                       Software TestProject Management Plan
III c.     Project Projected Cost Information:

   Units            (A)            (B)                 (C)                    (D)               (E)
                  Actual       Estimate to        Total Project          Total Original       Variance
                 Project to
                                Complete         Estimated Cost             Project
                   Date
                                 Project             (A + B)                Budget
                                                                                              Percen
                                                                                                 t
                                                                                               (100 – C /
                                                                                                  D)
Hours
Dollars


III d.     Hour Projections:

             Cumulative Hours
                        10000                                                                           p
                         9000                                                                    p
                         8000                                                            p
                         7000                                                     p
                         6000                                             p
                         5000                                     p
                         4000                              p
                         3000                      p
                         2000               p
                         1000       p
 Lapsed Time - Months               2       4      6       8      10      12     14      16     18      20

Note:      “p” = Planned Hours, “r” = Revised Planned Hours, “A” = Actual Hours


III e. Cost Projections:
              Cumulative Costs
                       $10000                                                                           p
                        $9000                                                                    p
                        $8000                                                            p
                        $7000                                                     p
                        $6000                                             p
                        $5000                                     p
                        $4000                              p
                        $3000                      p
                        $2000               p
                        $1000       p
 Lapsed Time - Months               2       4      6       8      10      12     14      16     18      20

Note:      “p” = Planned Costs, “r” = Revised Planned Costs, “A” = Actual Costs
C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        47
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan



IV.      Progress Report Summary:

Highlight very succinctly the overall status of the project, particularly with respect to its completion on-time, on-
budget and delivering the expected results and benefits. The following milestone chart should be completed
indicating key project checkpoints and deliverables or major deliverables or milestones with the planned versus the
actual completion dates. Key project deliverables would include the project plan, requirements document, high level
design, detail design, program specifications, coding, unit testing, system testing, regression testing, client
acceptance testing, training, implementation. Attach a one page high-level GANTT Chart indicating project status
and critical path. The GANTT Chart must follow the prescribed format including the definition of actual hours
versus planned, estimates to complete in hours, and variance by major task or segment and for the total project. The
planned and actual position of each major task or segment on the critical path should be depicted graphically by
time.

     Milestone or Key Project                 Status              Planned                Actual
           Deliverable                                         Completion Date         Completion
                                                                                          Date




V.       Accomplishments This Period:

Provide a bullet point summary of key accomplishments for the month organized by active work
plan segment.

                                                                                                                       Formatted: Bullets and Numbering








         VI.      Plans for Next Period:


C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        48
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                     Software TestProject Management Plan
       Provide a bullet point summary of significant activities planned for the next period
organized by active work plan segment.

                                                                                                                       Formatted: Bullets and Numbering







         VII.     Issues Requiring Attention or Action:

       Provide a bullet point summary of each significant issue that has arisen and its
conclusion / resolution. Each project is required to have a formal, documented issues log.
Issues should be organized by order of importance. Each of the issues should be carefully
considered to determine the possible impact on the project as a whole, particularly the
impact on completing the project on-time, on-budget, and delivering the expected results
and benefits.

                                                                                                                       Formatted: Bullets and Numbering






         VIII. Risk Management / Mitigation

       Provide a bullet point summary of each significant risk that may jeopardize project
success (schedule, fiscal, and function). The project must have a formal, documented risk
profile organized by potential impact to the project. Each of the risks should be carefully
considered to determine the possible impact on the project as a whole, particularly the
impact on completing the project on-time, on-budget, and delivering the expected results
and benefits.


                                                                                                                       Formatted: Bullets and Numbering





IX.      Independent Quality Assurance Review Summary


C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        49
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM
                                                                      Software TestProject Management Plan

Provide the dates of the last and next third party quality management review.

                                                               Date

Last IRM Third Party QA Review Performed:

Next IRM Third Party QA Review Scheduled:




X.       Major QA Issues and Development Action Taken:


Provide a brief summary of each significant issue reported during the QA review process. QA
Issue “Status” is “Open”, “In-process” or “Closed”. Open QA issues require a proposed solution
and a planned resolution date.


QA Issue              Status        Proposed Resolution                    Planned          Actual
                                                                           Resolution       Resolution
                                                                           Date             Date




C:\Docstoc\Working\pdf\519a09af-c1fe-4e31-8133-
                                             20f0a2f37e8a.docE:\courses\spring2003\reading\Software_Test_Plan_Templat
                                             e.docQ:\IRM\PRIVATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRI
                                             VATE\INITIATI\QA\QAPLAN\TESTPLAN.docQ:\IRM\PRIVATE\INITIATI\
                                             QA\QAPLAN\PROJPLAN.doc                        50
                                             09/10/1203/03/0408/10/0008/06/9902/05/99 11:27 AM8:41 AM

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:9/11/2012
language:Unknown
pages:53