Software Test Plan for Secret Simulation: Abstract Data Type (ADT) Functionality Evaluation

Preview (6 of 18 Pages)

100%

Purchase to unlock

Loading page image...

Software Test Plan for Secret Simulation: Abstract Data Type (ADT) FunctionalityEvaluationSoftware Test PlanforToDo ListProgramming Assignment XMonday, July 6, 2015Prepared ByDomicia Herringdnh@uah.eduPrepared ForDr. Rick Coleman, InstructorCS 221, Data Structures in C++Computer Science DepartmentUniversity of Alabama in HuntsvilleBased on the provided Software Test Plan for the Secret Simulation system, explain how the testprocedures ensure the effectiveness and robustness of the system in terms of functionality,reliability, and performance. In your response, analyze the testing strategies mentioned, such asintegration testing, regression testing, and system testing, and discuss how each approachcontributes to the identification of potential issues in the software.Word Count Requirement:400-500 words.

Loading page image...

Table of Contents1.0SystemOverview............................12.0ReferencedDocuments.......................13.0TestProcedures............................1AppendicesA.TestPlanForms............................8

Loading page image...

Software Test PlanSecret Simulation1.0System OverviewA secret government agency has need of a special Abstract Data Type (ADT) for usein a Basically Secret Simulation (BSS). The ADT may be thought of abstractly asthree queues (3Qs). The 3Qs each can hold the same type of data structure.Commands at regular time intervals (CARTI) will be sent to this portion of the BSS.Command one (C1) will be to dynamically create a data structure (DCDS), place intothe data structure information to be supplied (TBS), and enqueue it into the first queue(Queue A). Command two and three (C2 and C3) will be to dequeue a structure fromQueue A and immediately enqueue it into Queue B (C2) or Queue C (C3). Commandfour and five (C4 and C5) will be to dequeue and destroy a structure from eitherQueue B (C4) or Queue C (C5). Details of this functionality are given in section 2.0.As usual should you or any of your programming team divulge even the smallest bitof information about this BSS we will have to shoot you.2.0 Referenced DocumentsProgrammingAssignment X Statement of Work.Dale, Nell and Teague, David,C++ Plus Data Structures2nd ed. 2001.“Programming Assignment 2 Hints”web page,http://cs.uah.edu/~rcoleman/CS221/ProgAssign/cs221Prog2Hints.htmlSoftware Design Document for the Secret Simulationprogram.3.0 Test ProceduresThe following tests will be performed on the software before its release.

Loading page image...

Tablef1fdefinesfthefscopefoffthefDefencefIntegrationfandfSystemfTestfeffort.ISTfTestingfforfDefence…IS…ISFNOT…PositivefandfnegativeffunctionalityLoad,fcapacity,fandfvolumeReliabilityfandfstabilityErrorfhandlingfandfrecoveryCompetitivefinferiorityfcomparisonOperationsfandfmaintenanceUsabilityDatafqualityPerformanceLocalizationCompatibilitySecurityfandfprivacyInstallationfandfmigrationDocumentationInterfacesDistributedf(outsourcefusabilityfandflocalizationftesting)Black-box/behavioralftesting3.xfregressionftesting3.1fregressionftestingf(acrossfincrements)DatefandftimefhandlingStandardsfandfregulatoryfcomplianceCodefcoveragefverificationSet-usefpairforfdatafflowfverificationDatabaseftablefoverflowferrorfhandlingUserfinterfacefoffensivenessUserfinterfacefperformancefunderfmaximumfloadOfficeArrowfintegrationMigrationfandfmediafloadffine-tuningLegacyfbrowsers,fclient,forfserverfcompatibilityOSfloginfidentityfoverrideLegacyf(pref3.0)fmigrationUnitforfcomponentftestingf(exceptfsupportingfdevelopmentfteam)White-box/structuralftestingTablef1:fISTfforfDefencefIS/ISfNOTf(Scope)

Loading page image...

DefinitionsTablef2fdefinesfsomeftestftermsfandfotherftermsffoundfinfthisfdocument.TermMeaningBlackfBoxfTestingTestingfbasedfonfthefpurposesfafprogramfserves;fi.e.,fbehavioralftesting.BugSomefaspectfoffthefsystemfunderftestfthatfcausesfitftoffailftofmeetfreasonablefexpectations.f“Reasonable”fisfdefinedfbyfiterativefconsensusfiffitfisfnotfobvious.fBuildAfcollectionfoffsoftwarefobjectsfoffknownfrevisionflevelsfcompiledfintofoneforfmorefsoftwarefexecutablesfforfinstallationfonfthefsystemfunderftest.TestfReleaseConfirmationfTestAfselectedfsetfofftestsfdesignedftoffindfwaysfinfwhichfafbugffixffailedftofaddressfthefreportedfproblemffully.EntryfCriteriaThefparametersfthatfdeterminefwhetherfonefisfreadyfandfableftofenter,fcontinue,forfexitfafparticularftestfphase.fContinuationfCriteriaExitfCriteriaIntegrationfTestAfsetfofftestsfdesignedftoffindfbugsfinfthefinterfacesf(controlfandfdatafflows)fbetweenftestedfcomponentsfoffthefsystem.QualityfRiskThefpossibilityfoffafspecificfsystemffailurefmode,feitherflocalized,fcausedfbyfsubsystemfinteractions,forfafrepercussionfeffectfoffafremotefsystemffailure,fthatfadverselyfaffectsfthefsystem’sfuser.ReferencefPlatformAf“knownfcorrect”fsystemfagainstfwhichfonefcanfcomparefthefresultsfandfbehaviorsfoffthefsystemfunderftest.fServerfClusterAfsetfoffserversfconfiguredftofperformfafparticularfrolefinftermsfoffdevelopment,ftesting,forfproduction.RegressionfTestAfsetfofftestsfrunftoffindfnewffailures,forfregressions,fthatfchangesfhavefcausedfinfcomponent,finterface,forfsystemffunctionality.SmokefTestAflimitedfsetfoffregressionftestsfdesignedftofdetermine,fthoughfafrandomfsamplefoffcriticalffunctions,fwhetherfafgivenfbuildfisfreadyfforftesting.

Preview Mode

This document has 18 pages. Sign in to access the full document!

Report

Study Now!

Document Details

Related Documents

DevOps and Its Importance Study Notes

Veeam Certified Engineer VMCE-V12

Modules 1 - 3 Basic Network Connectivity and Commu

Notes CCNA

CCNA 200-301 Portable Command Guide 5th Edition 20

CCNA 200-301 Portable Command Guide 5th Edition 22

CCNA 200-301 Portable Command Guide 5th Edition 36

Foundations of Novell Networking Section 26

Modulo 7 DHCPv4

Build and troubleshooting Integration Challenge

Company

Explore

Study Tools