【正文】 able price for quality required. Subcontractor ManagementThis section is to describe the requirements for the management and control of subcontractors. The objective is to ensure subcontractors are managed appropriately.Consider the following: What methods are to be used for managing and monitoring subcontractors (eg agreements, contracts etc)? What are their reporting requirements? What documents, if any, will the subcontractor provide (eg project schedule, quality plan etc)? Consider confidentiality, intellectual property and training issues. Inspection and Testing of Purchased Goods amp。 ServicesThis section is to describe the requirements for the verification of purchased goods and services. The objective is to ensure goods and services are inspected or tested/assessed upon receipt to ensure conformance with the purchase specification.Consider the following:168。 Where are the verification requirements to be documented (eg purchase order, PEP, agreement etc)?168。 Where will verification occur, and by whom?168。 What inspection and testing is to be performed?168。 What is to be the method of release?168。 Is the performance of the supplier to be rated and documented? Records RequiredThis section is to describe the requirements for the maintenance of purchasing records.Records may include:168。 Purchase orders, agreements/contracts, supplier selection and performance documents, Requests for Information/Tender/Quotation, subcontractor records/documents etc.168。 Project records required may be addressed in one section of this PEP or within individual sections/plans. The approach will depend on the demands of the project.5 Development PlanDescribe the process to be undertaken in the design and development of the project’s outputs, as defined in the Quality Plan.Consider the approach for this section, either by describing the design and development activities for each output, or summarising the minimum activities required. Design and Development ActivitiesDescribe the process that will be used to design, develop, review, accept, distribute and change outputs. Will all outputs delivered by the project follow the same process? Describe by exception?Example documentation products include Functional Requirements Specification, Design Specifications, Test Specifications, User documentation, Maintenance documentation and Training material. Other outputs may include developed software/systems. Organisation and StaffingIf not already addressed within this document, ensure the following:168。 that the skills required for design activities are identified。168。 that the resources (eg staff) are identified and allocated for design activities。 and168。 that appropriate management of staff, clients and providers is defined (this may have been addressed in the Project Business Plan under Stakeholder Management Plan (Section 4). Design MethodologyDescribe the design methodology that activities will conform or reference to, if not already addressed in the Quality Plan. Design and development activities to be performed are to be listed in the project plan. Design InputDescribe any design input that will be used. Ensure input is reviewed for applicability before mencing any design or development. Be aware that the development of an output may be input into the design of another output.168。 examples of input may be project management documents (Project Business Case, Project Business Plan etc) or a Functional Requirements Specification. Design OutputDescribe any specific design output requirements (eg an iterative process will occur to produce a sequence of design specifications). Inspection and ReviewDescribe the responsibilities and processes required.Consider the following: Reviewing outputs, ensuring conformance to methodologies and standards. Review/inspect for content and pleteness. Process for defects, deficiencies, related issues, etc. If applicable, programming review strategy – linkage to Test Plan. Documentation requirements. Approval and AcceptanceDescribe the responsibilities and processes required.Consider the following: Approval of output (eg by Project Manager), and acceptance (and nonacceptance) of output (eg by Business Owner). Documentation requirements. Authorisation and DistributionDescribe the responsibilities and processes required.Consider the following: Authorisation (of output release) and distribution of output. Output management and maintenance requirements postacceptance. Documentation requirements. Updating and ChangingDescribe the responsibilities and processes required.Consider the following: Updating the output (eg future releases following project milestones). Changing the output (eg client change in functional requirements). Requesting change and method of rerelease. Documentation requirements.6 Test PlanIf the project deliverables are other than an information system, then this section will require significant change.Ensure appropriate linkages to Purchasing (. subcontract development) where development and/or testing is to be performed by subcontractors. IntroductionDescribe the testing strategy to be used.The project system deliverables shall be subject to the following testing:168。 unit testing。168。 system and integration testing。 and168。 acceptance testing.All testing shall show the version of the output being tested, the version of the test specifications being used and, for acceptance testing, the version of the design specification being tested against.Testing shall be conducted according to the Methodology. The activities to be performed are listed in the Project Plan for this phase (Refer Section X – Project Plan). Unit TestingThe programmer shall test each testable unit of programming for conformance to the design by applying tests, recording the tests applied and the results of testi