Table Of ContentSYSTEM
VERIFICATION
SYSTEM
VERIFICATION
Proving the Design
Solution Satisfies the
Requirements
Second edition
JEFFREY O. GRADY
AMSTERDAM (cid:129) BOSTON (cid:129) HEIDELBERG (cid:129) LONDON
NEW YORK (cid:129) OXFORD (cid:129) PARIS (cid:129) SAN DIEGO
SAN FRANCISCO (cid:129) SINGAPORE (cid:129) SYDNEY (cid:129) TOKYO
Academic Press is an imprint of Elsevier
AcademicPressisanimprintofElsevier
125LondonWall,LondonEC2Y5AS,UK
525BStreet,Suite1800,SanDiego,CA92101-4495,USA
50HampshireStreet,5thFloor,Cambridge,MA02139,USA
TheBoulevard,LangfordLane,Kidlington,OxfordOX51GB,UK
Copyright©2016,2007ElsevierInc.Allrightsreserved.
Nopartofthispublicationmaybereproducedortransmittedinanyformorbyanymeans,
electronicormechanical,includingphotocopying,recording,oranyinformationstorage
andretrievalsystem,withoutpermissioninwritingfromthepublisher.Detailsonhow
toseekpermission,furtherinformationaboutthePublisher’spermissionspoliciesand
ourarrangementswithorganizationssuchastheCopyrightClearanceCenterandthe
CopyrightLicensingAgency,canbefoundatourwebsite:www.elsevier.com/permissions.
Thisbookandtheindividualcontributionscontainedinitareprotectedunder
copyrightbythePublisher(otherthanasmaybenotedherein).
Notices
Knowledgeandbestpracticeinthisfieldareconstantlychanging.Asnewresearchand
experiencebroadenourunderstanding,changesinresearchmethods,professional
practices,ormedicaltreatmentmaybecomenecessary.
Practitionersandresearchersmustalwaysrelyontheirownexperienceandknowledge
inevaluatingandusinganyinformation,methods,compounds,orexperimentsdescribed
herein.Inusingsuchinformationormethodstheyshouldbemindfuloftheirownsafety
andthesafetyofothers,includingpartiesforwhomtheyhaveaprofessionalresponsibility.
Tothefullestextentofthelaw,neitherthePublishernortheauthors,contributors,
oreditors,assumeanyliabilityforanyinjuryand/ordamagetopersonsorpropertyas
amatterofproductsliability,negligenceorotherwise,orfromanyuseoroperation
ofanymethods,products,instructions,orideascontainedinthematerialherein.
LibraryofCongressCataloging-in-PublicationData
AcatalogrecordforthisbookisavailablefromtheLibraryofCongress
BritishLibraryCataloguinginPublicationData
AcataloguerecordforthisbookisavailablefromtheBritishLibrary
ISBN:978-0-12-804221-2
ForinformationonallAcademicPresspublications
visitourwebsiteatwww.elsevier.com
Publisher:JoeHayton
AcquisitionEditor:BrianGuerin
EditorialProjectManager:CarrieBolger
ProductionProjectManager:AnushaSambamoorthy
Designer:MatthewLimbert
TypesetbySpiGlobal,India
ABOUT THE AUTHOR
JeffreyO.GradyhasbeentheownerofJOGSystemEngineering,asystem
engineering consulting and training company, since 1993, based in San
Diego,California.Inthatcapacityhehasworkedwithawidearrayofcom-
panieswithabroadcrosssectionofproductlines.Priortothis,followingten
yearsintheU.S.Marines,heworkedfor30yearsinaerospacecompaniesas
a customer-training instructor at Librascope on Anti-Submarine Rocket
(ASROC)andSubmarineRocket(SUBROC)underwaterfirecontrolsys-
tems; field engineer, project engineer, and system engineer at Teledyne
RyanAeronauticalonunmanneddayandnightaswellasstrategicandtac-
ticalphotoreconnaissance,SIGINT,strike,EW,andtargetaircraftlaunched
from ground launchers,aircraft, andshipboard;system engineer atGeneral
Dynamics Convair on advanced cruise missile; and system development
departmentmanageratGeneralDynamicsSpaceSystemsDivisionsonspace
transport (Atlas) and energy systems.
Jeffhasauthored11publishedbooksandnumerouspapersinthesystems
engineering field. He holds a bachelor’s degree in mathematics from San
Diego State University, a master of science in system management with a
certificateininformationsystemfromtheUniversityofSouthernCalifornia,
and a systems engineering certificate from the University of California San
Diego.Jeffteachessystemengineeringcoursesaroundthecountryon-siteat
companies and universities including the University of California San
Diego. Heisan International Councilon SystemsEngineering (INCOSE)
fellow, founder, and expert system engineering professional (ESEP).
ix
PREFACE
The original work for this book began under the title System Validation and
VerificationpublishedbyCRCPressin1997.Itwasrewrittenin1998tosome
extentandcoordinatedwitharewriteofseveralotherbooksthatIhadwritten
toformVolume4ofafour-volumeseriestitledGrandSystemsDevelopmentfor
useastextmaterialinasystemengineeringanddevelopmentinstructionpro-
gramofferedbymyconsultingandtrainingcompany,JOGSystemEngineer-
ing.Theoriginalbookcoveredbothvalidationandverificationbutthebook
waspublishedbyAcademicPressfocusedonlyonverification.Thevalidation
materialwasmovedtothecompanionbookinthesameseriestitledSystems
Requirement Analysis also published by Academic Press.
ThisisasecondAcademicPresseditionpublishedin2012.Itextendsthe
sameprocessappliedtoproductverificationtoprocessverificationfollowing
the pattern of: define the problem, solve the problem, prove it. Fairly
recently, sound standards have evolved for system development, system
engineering,andsoftwareengineering.Thesestandardsactasprocessspec-
ifications for thecorrespondingprocesseswemust design. Sound standards
arealsomaturingforcapabilitymaturitymodelsforuseinassessingthequal-
ity of the process design providing a process verification mechanism.
What the author recognized while working on a program for a system
developmententerprisewasthathehadneverobservedaclearwayimplemen-
ted on aprogram to communicateto the person assignedresponsibility fora
verification task specifically what requirements that person was responsible
for producing verification evidence about nor had he observed an effective
method applied requiring that person responsible for a task to coordinate
thetaskevidencetothosesamerequirements.Thatis,aclearmeansforcap-
turing the traceability between product requirements, verification require-
ments, verification task, and the content of the report for that task was
nowheredescribed.Theauthorsetouttoincludethisinformationinthisbook.
Healsofinallyconcludedinthiseditionthattheintegratedverificationdocu-
mentationaddressedinthetwopriorversionshadtobereplacedbythecom-
monseparateseriesofdocumentsforeachtaskmostoftenseenonaprogram.
Jog
San Diego, California
February 10, 2016
xi
ACKNOWLEDGMENTS
This book remains dedicated to the memory of Mr. Max Wike, a retired
navalofficerandasystemengineerinthedepartmentImanagedatGeneral
DynamicsSpaceSystemsDivisioninthemid-1980s.Beforehepassedaway
long before his time, he and his wife to be, Ms. Debbie Matzek, had suc-
ceeded in beginning my education in requirements verification and I very
much appreciate that to this day.
ItneverfailsthatduringeveryclassonsystemrequirementsanalysisthatI
havetaughtforUniversityofCaliforniaSanDiego,UCIrvine,UCBerkeley,
through short course companies, and independently through my systems
engineering consulting and education firm at companies, students have
offeredmegreatinsightsandideasabouthowthisprocesscanbedonebetter.
Manyoftheseinputsfindtheirwayintofuturecoursesaswellasnewbooks
and, hopefully, revisions of others. Unfortunately, I have not shown due
diligence in keeping a list of these people by name and location so that I
canproperlythankthem.Thelistwouldbeverylong.Bythetimethisbook
is published it will likely include on the order of 1000 engineers.
A lady from Raytheon in Tuscon, AZ, Christine Rusch, attending the
International Council on Systems Engineering (INCOSE) Symposium
V&V tutorial I did in Brighton, England in 1999 suggested coverage of
the reverification situation adding content to the course and a chapter to
thetext.Agentlemanattendingasimilartutorialatthe2000INCOSESym-
posiuminMinneapolis,MNdiscoveredthatIhadnotcoveredthereporting
process adequately, causing the addition of chapters on that subject. Also,
at the same time while considering how that material should be added,
Inoticedthatsystemtestandevaluationwascoveredinamostcursoryfash-
ionandawholepartwasaddedtothetext.Itistruethatalecturerlearnsa
greatdealthroughteachingbecauseyouhavetheopportunityoftalkingto
some very bright people. I appreciate all of those suggestions.
IbenefitedagreatdealfromaUCSanDiegoSystemEngineeringCer-
tificateProgramcourseIattendedwhiletheideasforthisbookwereinitially
swarminginmymind.ThatcoursewastitledSystemVerificationtaughtby
a great guy and fine system engineer, Mr. James R. (JB) Hill, at the time a
vicepresidentatScientificApplicationsInternationalCorporation(SAIC)in
SanDiego,California.IverymuchappreciatethenewknowledgeIderived
from his course.
xiii
xiv Acknowledgments
Several people in industry provided much appreciated and valuable
insights into modern techniques for validation and verification on items
as small as integrated circuits and as large as a transport aircraft. Mr. David
Holmes, a system engineer at Interstate Electronics Corporation in
Anaheim,California,verygenerouslyarrangedademonstrationofhowthey
develop application specific integrated circuits (ASIC) during a certificate
program I presented for UC Irvine at their facility in 1995. Mr. David
B. Leib, a Test Engineer on the McDonnell Douglas C-17 Flight Control
SystemSimulator(IronBird),gavemeatourofthesimulatorattheirfacility
in Long Beach, California during a certificate program I presented at their
facility for UC Irvine in 1996 that was very useful in describing a typical
large-scale validation and verification instrument.
While I have benefited from the advice of those identified and many
others where I cannot recall the precise situation, they should not be held
accountable for any errors of commission, omission, or wrong-headed
thinking. They belong wholly to the author.
ACRONYMS AND ABBREVIATIONS
Acronym Meaning
AFSCM AirForce Systems Command Manual
ASROC anti-submarine rocket
ASW anti-submarine warfare
ATP acceptance test plan or procedure
BIT business integration team
BUFF big uglyfat fellow
CAD computer aided design
CBD Commerce Business Daily
CCD capability developmentdocument
CDR critical designreview
CDRL contract data requirementslist
CFD control flow diagram
CMM capability maturity model
CMMI capability maturity model integrated
CONOPS conceptof operations
CPM critical path model
C/SCS cost/schedulecontrol system
DER designated engineeringrepresentative
DID data item description
DFD data flow diagram
DoD Department of Defense
DODAF Department of Defense architecture framework
DTC designto cost
DT&E developmenttest and evaluation
EFFBD enhanced functional flow block diagram
EIA Electronics Industry Association
EIT enterprise integration team
EMI electromagnetic interference
FAA Federal Aviation Administration
FCA functional configuration audit
FMECA failure mode effects and criticalityanalysis
FOT&E follow-on operational test and evaluation
FRACAS failure reportingand corrective action system
FRAG fragment
GD General Dynamics
HLD higher level demote
IAT integration, assembly, and test
ICAM integrated computer aided manufacturing
xv
xvi AcronymsandAbbreviations
Acronym Meaning
ICBM intercontinental ballistic missile
ICD initial capabilities document
ICD interface control document
IDEF integrated definition
IEEE Institute of Electricaland Electronics Engineers
ID item demote
ID identification
IMP integrated master plan
IMS integrated master schedule
INCOSE International Council on Systems Engineering
IOC initial operatingcapability
IOT&E interim operational testand evaluation
IP item promote
IPPT integrated product and process team
IRAD independentresearch and development
ITP integrated testplan
ISO International Standards Organization
ITEP integrated testand evaluation plan
IVDR integrated verificationdata report
IVP integrated verificationplan
JCD joint capability document
LLP lower level promote
MID modelingidentification
MIL military
MK mark
MoD Ministry of Defence
MODAF Ministry of Defencearchitecture framework
MSA modernstructured analysis
NASA National Aeronautics and Space Administration
OOA object oriented analysis
ORD operational requirementsdocument
OT&E operational test and evaluation
PARA paragraph
PBT program business team
PCA physical configuration audit
PDR preliminarydesignreview
PDT product developmentteam
PERT program evaluation review technique
PID product identification
PIT program integration team
PMP parts, materials, and processes
AcronymsandAbbreviations xvii
Acronym Meaning
PRID product requirementidentification
PSARE process for system architecture and requirementsengineering
PT part
QA qualityassurance
RAM reliability, availability, and maintainability
RATO rocketassistedtake off
RPM revolutions perminute
REQ requirement
RFP request for proposal
RID requirement identification
SADT structured analysisand designtechnique
SAR system architecture report
SAR surfaceair rescue
SDR system design review
SOW statement of work
SQA software quality assurance
SRA system requirementsanalysis
SRR system requirementsreview
STD standard
STE special test equipment
STEP system testand evaluation plan
SysML system modelinglanguage
TEMP test and evaluation masterplan
TQM total qualitymanagement
UADF universal architecture descriptionframework
UHL ultra high frequency
UML unified modelinglanguage
UPDM unified processforDODAF/MODAF
USAF UnitedStates AirForce
USN UnitedStates Navy
USS UnitedStates ship
VCRM verification cross reference matrix
V/H the ratio of velocityover height above terrain
VRID verification requirementidentification
VTN verification task number
V&V validation and verification
WBS work breakdown structure
