最新SoftwareQualityAssurancePlanTemplate精品资料.docx

最新SoftwareQualityAssurancePlanTemplate精品资料.docx

《最新SoftwareQualityAssurancePlanTemplate精品资料.docx》由会员分享，可在线阅读，更多相关《最新SoftwareQualityAssurancePlanTemplate精品资料.docx（23页珍藏版）》请在冰豆网上搜索。

最新SoftwareQualityAssurancePlanTemplate精品资料

最新Software_Quality_Assurance_Plan_Template精品资料

SoftwareQualityAssurance（SQA）Plan

Date:

GeneralTailoringGuidelines

ThisdocumentisatemplateforaSoftwareQualityAssurancePlanintendedforusebyCode303,AssuranceManagementOffice（AMO）personnelasthebasisforamission-specificSoftwareQualityAssurancePlan.

Therearethreegeneraltypesoftextformat:

TextinBlack,TextinBluewith<>,

TextinBluewith[]andTextunderlinedinblue.

TextinBlack

∙Textinthisstyle,black,isusedfortextthatisequallyapplicabletoallSoftwareQualityAssurancePlansandwillbeincludedintheSoftwareQualityAssurancePlanwithoutmodification.Alldocumentsectionheadingsareinthesamecategory.

TextinBluewith<>

∙Textinthisstyle,,isusedtoindicatethatthetextneedstobeupdatedwithprojectspecificinformationsuchastheprojectname,personsname,personstitle,date,revision#,DocumentControlNumber,exc…

TextinBluewith[]

∙Textinthisstyle,[blue],isusedtoindicatethatthereisadditionalinstructionfortailoringtextinanyspecificsection.Deletethisstyle,[blue],textbeforethedocumentisfinalized.

TextunderlinedinBlue

∙Textinthisstyle,blue,isusedtoindicateactivelinks.Theselinksareusuallytoprojectorsoftwareassurancewebsites.Thetextcolormayverydependingoneachpersonspersonalcomputersettings/configuration.

Allcomponentsofthetableofcontentswillbeaddressed,butthelevelofdetailisleftuptothesoftwarequalitypersonnel.ThelengthandlevelofdetailoftheSoftwareQualityAssurancePlanshouldbecommensuratewiththescopeandcomplexityoftheproject.

Sectionheadingsmaybeaddedwherenecessary,butexistingheadingsshouldnotbemodifiedordeleted.IfaparticularsectionisnotapplicabletothespecificSoftwareQualityAssurancePlanunderproduction,thatfactshouldbenotedunderthesectionheading,togetherwithabriefexplanation.

Thefollowingdisclaimerappearsonallpages:

“PrintedcopiesofthisdocumentareforREFERENCEPURPOSESONLY!

Theonlycontrolledcopyofthisdocumentislocatedon-lineat

//xxxxxxxx>.ThisdisclaimershouldbemodifiedtocontaintheappropriateURL,butshouldnotberemoved.

Finally,intheSoftwareAssurancePlanTemplate,thisentiresection（“GeneralTailoringGuidelines”）willbedeleted.

Foreword

ThisdocumentisaProjectcontrolleddocumentandadherestoIEEE730-2002,theIEEEStandardforSoftwareQualityAssurancePlans.ChangestothisdocumentrequirepriorapprovaloftheProjectConfigurationControlBoard（CCB）.ProposedchangesshallbesubmittedtotheSystemsAssuranceManager（SAM）,alongwithsupportivematerialjustifyingtheproposedchange.

QuestionsorcommentsconcerningthisdocumentshouldbeaddressedtotheAssuranceManagementOffice:

,/Code303

BuildingRoom

MailStop

GoddardSpaceFlightCenter

Greenbelt,Maryland20771

（301）

SignaturePage

Preparedby:

_______

Reviewedby:

_______

_________

Approvedby:

_______

ProjectDocumentTitle

DOCUMENTCHANGERECORDSheet:

1of1

REV/VER

LEVEL

DESCRIPTIONOFCHANGE

APPROVED

BY

DATE

APPROVED

TableofContents

13.0Training17

16.0SQAPlanChangeProcedureandHistory20

ListOfTables

Table

1.0Purpose

ThepurposeofthisSoftwareQualityAssurance（SQA）Planistoestablishthegoals,processes,andresponsibilitiesrequiredtoimplementeffectivequalityassurancefunctionsfortheproject.

TheSoftwareQualityAssurancePlanprovidestheframeworknecessarytoensureaconsistentapproachtosoftwarequalityassurancethroughouttheprojectlifecycle.ItdefinestheapproachthatwillbeusedbytheSAMandSoftwareQuality（SQ）personneltomonitorandassesssoftwaredevelopmentprocessesandproductstoprovideobjectiveinsightintothematurityandqualityofthesoftware.Thesystematicmonitoringofproducts,processes,andserviceswillbeevaluatedtoensuretheymeetrequirementsandcomplywithNationalAeronauticsandSpaceAdministration（NASA）,GoddardSpaceFlightCenter（GSFC）,andpolicies,standards,andprocedures,aswellasapplicableInstituteofElectricalandElectronicEngineers（IEEE）standards.

1.1Scope

ThisplancoversSQAactivitiesthroughoutthephasesofthemission.[IndicatewhetherornotSQAactivitieswillcontinuethroughoperationsandmaintenanceofthesystem.]

[Enterabriefdescriptionoftheproject,thesuppliersofthesoftware,thesoftwareitemscoveredbytheplan,andtheirintendeduse.]

2.0

ReferenceDocuments

Thefollowingdocumentswereusedorreferencedinthedevelopmentofthisplan:

∙NASA-STD-8719.13,NASASoftwareSafetyStandard

∙NASA-STD-8739.8,NASASoftwareAssuranceStandard

∙NPR7150.2,NASASoftwareEngineeringRequirements

∙GPG5100.3,QualityAssuranceLetterofDelegation

∙GPG7120.4,RiskManagement

∙GPG8700.4,IntegratedIndependentReviews

∙GPG8700.6,EngineeringPeerReviews

∙

∙

∙

∙

∙

∙

∙IEEESTD730-2002,IEEEStandardforSoftwareQualityAssurancePlans

∙ProjectSurveillancePlan

∙ProjectPlan

∙SystemImplementationPlan（SIP）

∙SoftwareManagementPlan（orProductPlan）

∙StatementofWork（SOW）

∙ConfigurationManagementPlan（CMP）

[Updatethereferencedocumentlisttoincludealistofprojectdocumentsusedorreferencedinthedevelopmentofthisplan.Thisincludespolicies,standards,procedures,guidelines,andothersimilardocuments.Note:

thelast6documentslistedareexamplesofprojectplansthatyoumightinclude.Citethemonlyiftheyapplyand/oraddothersspecifictoyourproject.]

3.0

Management

Thissectiondescribesthemanagementorganizationalstructure,itsrolesandresponsibilities,andthesoftwarequalitytaskstobeperformed.

3.1ManagementOrganization

effortsaresupportedbynumerousentities,organizationsandpersonnel（seeinternalwebsiteforadetailedorganizationalchart）.Relevantentities/rolesthatareofinterestandapplicabletothisSQAPlanandthesoftwareassuranceeffortaredescribedatahighlevelbelow.

[Enteracopyoftheproject’smanagementorganizationalchartortheproject’swebsitewherethisinformationcanbefound.Thischartshouldreflecttheproject’sinterfacewithCode303.]

3.1.1ProjectOffice

TheProjectOfficeatNASAGSFCisresponsibleformanagementofprojectobjectiveswithintheguidelinesandcontrolsprescribedbyNASAHeadquarters,GSFCManagement,andtheProjectPlan.TheProjectManager（PM）fromGSFCCodeisspecificallyresponsibleforthesuccessoftheProject,includingbutnotlimitedtocost,schedule,andquality.

3.1.2AssuranceManagementOffice

TheSAMprovidesProjectManagementwithvisibilityintotheprocessesbeingusedbythesoftwaredevelopmentteamsandthequalityoftheproductsbeingbuilt.TheSAMismatrixedtotheprojectandmaintainsalevelofindependencefromtheprojectandthesoftwaredevelopers.Riskescalationbeginsattheprojectlevel,andextendstotheAMOandtheOfficeofSystemsSafetyandMissionAssurance（OSSMA）,Code300.

Insupportofsoftwarequalityassuranceactivities,theSAMhasassignedandsecuredSoftwareQualitypersonnelfromtheMissionAssuranceServicesContract（MASC）tocoordinateandconducttheSQactivitiesfortheprojectandidentifyanddocumentnoncomplianceissues.Inthefutureandonanasneededbasis,SQpersonnelsupportfromtheSupplierAssuranceContract（SAC）and/orDefenseContractManagementAgency（DCMA）maybeutilizedtosupporttheSQactivitiesatremote（non-GSFC）locations.

AdditionalsupportpersonnelmayalsoincludeOSSMASafetyandReliabilityandNASAIndependentVerificationandValidation（IV&V）personnelfromtheNASAIV&VFacilityinFairmont,WV.ForadditionaldetailsonIV&Vactivities,referencetheIV&VMemorandumofAgreement（MOA）and/ortheIV&VProjectPlan（IVVP）.[IdentifywhichIV&Vagreements/plansareapplicabletoyourproject.]

[Enteranyadditionalmanagementorganizationand/orsuppliersprovidingsupporttothisproject.SomeexamplesofothermanagementorganizationsincludetheObservatoryprovider,instrumentprovider,and/orgrounddatasystemproviders.]

3.2

Tasks

Thissectionsummarizesthetasks（productandprocessassessments）tobeperformedduringthedevelopment,operations,andmaintenanceofsoftware.Thesetasksareselectedbasedonthedeveloper’s

ReferencetheNASAGSFCSoftwareAssurancewebsite,toretrievesoftwarequalitychecklistsandforms.ThissiteisownedandmaintainedbytheNASAGSFCSoftwareAssuranceLead,locatedintheOSSMA.

3.2.1ProductAssessments

ThefollowingaretypicalproductassessmentsthatmaybeconductedbySQpersonnel.SeetheSQActivitySchedulefortheplannedassessments:

∙PeerReviewpackages

∙DocumentReviews（seeSection4,Documentation）

∙SoftwareDevelopmentFolders

∙SoftwareConfigurationManagement（e.g.,configurationbaselines,configurationchangerequests,andchan