[ Pobierz całość w formacie PDF ]
.Any change to that statement must be a management decisionbecause there are all kinds of legal ramifications.Fourth, when the physical and functional baseline has been established andthe requirements negotiated, they must be brought together.Usually, this re-quires changing the system.At this point, you can write (rewrite) the SystemTest with reasonable assurance it will be correct.Sometimes, at this point, thereare other changes the customer sees he wants.This time, keep up with thechanges in the System Test!60d (NO) The System Test was not performed under appropriateload(s).2The System Test was not performed under appropriate load(s) when theloads on the system are not the loads required by the specification.RECOVERYIf the specification does not stipulate loads, it is best to create   reasonable loads, as determined by engineering analyses, and perform the system testsunder those loads.Those loads and that fact must be documented and presentedto the customer/client prior to final acceptance.The best time to present theseissues is in the first Design Review.If the customer/client has an issue with theloads, it is a point for negotiation.60e (NO) The System Test was not performed using the same kind ofpersonnel that will be used by the customer.The System Test was not performed using the same kind of personnel thatwill be used by the customer with regard to training, education, experience, etc.,150 BLUEPRI NT FOR PROJECT RECOVERYor the personnel specified by the customer.To conduct a System Test withengineers instead of Level X technicians is an invalid test even when you followall the procedures in the test.If the specification does not stipulate operatingpersonnel level, it is best to assume reasonable operating levels, as determinedby engineering analyses, and perform the system tests using those personnel.Those operating levels must be documented and presented to the customer/client prior to final acceptance.The best time to present these issues is in thefirst Design Review.If the customer/client has an issue with the created loads,that is a point for negotiation.60f (NO) The System Test was not properly documented and did notincorporate the test results of all prior-level tests.The System Test was not properly documented and did not incorporate thetest results of all prior level tests when the results of the unit level tests and thesubsystem level tests are not clearly visible in the construct and conduct of thesystem test.RECOVERYAssumption: The Unit Tests were properly constructed, and each associatedgroup of units constituted an appropriate subsystem.Pull together all the subsystem tests:R' Check the traceability of each unit and unit test to the appropriate sub-system.R' Check the inputs and outputs of each subsystem.R' Check the interfaces and interface compatibility of each interfacing sub-system.R' Check the loads of each subsystem.R' Make changes as necessary.R' Modify the system test as necessary and recheck the traceability to therequirements.61 CONFIGURATION MANAGEMENT61a (NO) The Configuration Management Plan (CMP) is notthorough, complete, or authorized.The Configuration Management Plan (CMP) is not thorough, complete, orauthorized unless it follows the required format and maintains the requiredRECOVERI NG FROM TECHNI CAL PROBLEMS 151content as specified in customer or company configuration management policy.Further, the CMP is not authorized unless it is signed by an authority that isauthorized to sign such documents (usually the vice president or director ofengineering or an equivalent position).The Configuration Management process could easily be looked upon as theJanus process.Remember the Roman god Janus who looked both backwardand forward? That s what the configuration management process does.It looksbackward to the baseline, as established, and forward to the test process thatwill prove the viability of a change.RECOVERYIf you do not have a CMP, consider the following outline.The detail of whatshould be contained in each section can be found in Attachment 5.Modify theoutline as necessary for your purposes:1.Introduction2.Reference documents3.Organization4.Configuration management phasing and milestones5.Data management6.Configuration identification7.Interface management8.Configuration control9.Configuration status accounting10.Configuration audits11.Subcontractor/vendor controlConfiguration Management should be treated on at least at two levels.Thegenerally accepted levels are, appropriately enough, Class I and Class II.Class Ichanges are those that affect form, fit, or function while Class II changes arethose that affect only documentation.Class I changes require convening a fullConfiguration Management (or Control) Board, often called the CCB.Class IIchanges only require the concurrence of the head of the CCB.The Configuration Management Plan should be prepared for specific projectuse and generally follow the requirements of MIL-STD-973, MIL-STD-483,152 BLUEPRI NT FOR PROJECT RECOVERYMIL-STD-61, EIA-649, or ISO 10007, as determined by the requirements docu-ment (contract).The purpose of the Software Configuration Management (SCM) plan is toachieve the   Repeatable  level on the Software Engineering Institute s (SEI s)Capability Maturity Model (CMM) and meeting the ISO/IEC 12207/MIL-STD-498 and the additional MIL-STD-973 requirements.Additional Resources:The following may contribute to developing your plan:Data Item Descriptions (DIDs)DI-CMAN-81343DI-CMAN-80858A61b (NO) Change requests were not presented and approved by anappropriate level of the Review Board.Change requests were not presented and approved by an appropriate levelof the Review Board when the presentations and approvals did not follow theConfiguration Management Plan (CMP).RECOVERYYou should have a CMP (See Attachment 5) containing a ConfigurationControl Section.A Change Process should be part of the Configuration ControlSection.Additional Resources:The following may contribute to developing your plan:Data Item Descriptions (DIDs):DI-CMAN-81343DI-CMAN-80858ARECOVERI NG FROM TECHNI CAL PROBLEMS 153Standards:MIL-STD-973MIL-STD-483MIL-STD-61EIA-649ISO 10007ISO/IEC 12207MIL-STD-49861c (NO) Version controls are not in place and are not reflected on(in) the product.Version controls are not in place and are not reflected on (in) the productwhen the affected product is not appropriately marked with the version whichdescribes it in the Version Description Document (VDD) (see glossary) and towhich it has not been tested.RECOVERYCreate a version system and a Version Description Document where:The general convention for document versions is:X.YZWhere: X Major issue or re-issue containing fundamental changes.Y Minor change containing use changes or additional modules.Z Minor use changes or documentation clarifications [ Pobierz całość w formacie PDF ]