System Requirements Traceability And System Verification .
15th Annual Systems Engineering ConferenceHyatt Regency Mission BaySan Diego, California22-25 October 2012ISAASIndividual Semi-AutomaticAirburst SystemSystem RequirementsTraceability andSystem VerificationRigor and PlanningJoel FeigumChief EngineerATK Advanced WeaponsApproved for Public Release, PA 675-12, dated 24 August 2012ISAASIndividual Semi-AutomaticAirburst System1XM7 SpiderAnti-Personnel Force ProtectionPGKPrecision Guidance Kit120mm Tank AmmunitionM395 APMIAccelerated Precision Mortar InitiativeApprovedVolcano for Public Release, PAO #675-12,24 AugustAnti-Tank2012Mine
AgendaProblem StatementProgram SummaryProcessImplementation DetailsConclusions2Approved for Public Release, PAO #675-12,24 August 2012
Problem StatementProgram SummaryProcessImplementation DetailsConclusions3Approved for Public Release, PAO #675-12,24 August 2012
Problem Statement (The Perfect Storm) Aggressive schedules Limited funding Increased requirement complexity Performance, Environment and Testing Increased rigor in testing Increased testing complexity 4 Multiple requirements 1 Test Multiple test 1 requirementMultifaceted program TD FOA-1 TD EMD EMD FOA-2Milestone C DecisionApproved for Public Release, PAO #675-12,24 August, 2012
Problem StatementProgram SummaryProcessImplementation DetailsConclusions5Approved for Public Release, PAO #675-12,24 August 2012
ISAAS SystemTA/FCBatteryWeaponHigh ExplosiveAir Training** Current Development** Future DevelopmentApproved for Public Release, PAO #675-12,24 August 2012
ISAAS Con-Ops7Approved for Public Release, PAO #675-12,24 August 2012
Program Schedule500 Series Ammo Test600 Series System Test300 Series Ammo Test400 Series System Test8Approved for Public Release, PAO #675-12,24 August 2012
ISAAS is in Theater”Forward Operational Assessment (FOA) running in parallel with EMD program9Approved for Public Release, PAO #675-12,24 August 2012
Problem StatementProgram SummaryProcessImplementation DetailsConclusions10Approved for Public Release, PAO #675-12,24 August 2012
Structured RequirementsCapability DevelopmentDocument (CDD)Rev. 2.826 Oct 2010CARDS #02092Approved29 January 2011Supporting IL-F-13926MIL-PRF-71226 ···MIL-STD-1474DMIL-STD-2105FED-STD-595STANAG 4439MIL-HDBK-759, Notice 2MIL-HDBK-454AITOP 4-2-602TOP 1-2-511TOP 3-2-045Customer Requirement DocumentsSystem Requirement DocumentsSystem PerformanceSpecification (SPS)2807727111TA/FC / Weapon M-ICD28082615System Electrical ICD28083249Weapon / Ammo M-ICD28083592User Interface ICD28083250TA/FC / Battery M-ICD28077025Messaging IRS28083356TA/FC PerformanceSpecificationWeapon PerformanceSpecificationAmmunition PerformanceSpecificationBattery 084210TA/FC Software RequirementsSpec32419Ammunition SoftwareRequirements Spec28080041TA/FC Software DesignDescription32420Ammunition Software DesignDescription28082950Approved for Public Release, PAO #675-12,24 August, 2012
Requirement Decomposition Understanding user requirements decomposition key to verification planning Focused test planning Customer/User focusKPP / �sKPP 1 - System Effectiveness1729516KPP 2 – Operational Availability2761KSA 1 – Target Acquisition2400KSA 2 - Reliability3321KSA 3 – Degraded Operation3120KSA 4 – Dispersion1022KSA 5 – Engagement Time1027614KSA 6 – Zero Retention/Repeatability334012Approved for Public Release, PAO #675-12,24 August, 2012
Early Test Planning is Critical Process demonstrates the key activities required to verify requirements Requirements management tool used to tie the testing and requirements Test planning driven by SE tools and team Early involvement of the customer and government test facilities Harvest data from FOA activitiesCustomerRequirementsDocumentConduct Voice ofthe Customer(VOC)System Spec / ICDDevelopmentConduct SystemSRR/SFRSubsystem Spec /ICD DevelopmentPreliminary DesignConduct PDRDevelop InitialTest PlansIdentify TestObjectives andTRD’sReviewPreliminary RVMDesign EvaluationTestingDevelop DetailedTest PlansContractorQualificationTestingUpdate ContractorQual TestObjectives andTRD’s13Conduct CDRContractor Proveout tomerQualificationPRR / SVRTestPerformance /RVM ReviewMilestone CApproved for Public Release, PAO #675-12,24 August, 2012
Problem StatementProgram SummaryProcessImplementation DetailsConclusions14Approved for Public Release, PAO #675-12,24 August 2012
SE Tools SupportsTest objectiveslinked to testsRequirements linked totest objectives andconfiguration item15Approved for Public Release, PAO #675-12,24 August 2012
Verification Identification 16Early identification of the “how to” during the verification process is critical toensuring program success Test planning Test objectives Success criteriaApproved for Public Release, PAO #675-12,24 August 2012
CDD 917XXTest XXXXXXXXReliability AnalysisRecognition AnalysisProbability of Incapacitation AnalysisPhysical InspectionOperational Availability AnalysisNuclear Event AnalysisMaintenance AnalysisLogistics InspectionTransportation AnalysisXTactical Transportation Shock AnalysisXLogistics AnalysisHuman Engineering AnalysisGovernment Arena TestingEMQRB ResultsDrawing InspectionCleaning DemonstrationChemical AnalysisTest 425Test 424Test 423Test 422Test 420Test 412Test 410Test 400XTest 370Test 350Test 330Test 310Test 300User Focused Verification Event SummaryXXXXXXApproved for Public Release, PAO #675-12,24 August 2012
Test Planning18Approved for Public Release, PAO #675-12,24 August 2012
Sample SE Tool Output19Approved for Public Release, PAO #675-12,24 August 2012
Problem StatementProgram SummaryProcessImplementation DetailsConclusions20Approved for Public Release, PAO #675-12,24 August 2012
Manage / Identify V&V Issues21 SE tool utilized to monitor V&V process and issues V&V updated immediately upon test completion Review results as appropriateApproved for Public Release, PAO #675-12,24 August 2012
Verification Metrics 22Constant monitoring of verification activities against plans is critical toensuring successApproved for Public Release, PAO #675-12,24 August 2012
Planned vs. Actual Objectives450400Gap due to analysis effortsand endurance testingNumber of Objectives350300250200150Planned (Cumulative)100Actual (Cumulative)Actual Passed (Cumulative)500Verification Events Sorted by Scheduled Completion Date23Approved for Public Release, PAO #675-12,24 August 2012
Conclusions Emphasis of System Engineering discipline throughout program life cycle Early collaboration and involvement of the test engineering System Engineering involvement in test planning and execution Early and constant monitoring of requirement V&V 24Metrics identification and trackingSE Tool usage is critical to tying it all together.Approved for Public Release, PAO #675-12,24 August 2012
AcknowledgementsSpecial thanks to PM-IW: Rob Greenfield – SE LEAD Andy Cline – Product DirectorTest support:25 Peter Ollis – ATC Test Lead Don Kukowski – ATK Test LeadApproved for Public Release, PAO #675-12,24 August 2012
Contact information: Name: Phone Number: Company:Abstract ID Number:26Joel Feigum763-744-5127ATK Advanced Weapons14764Approved for Public Release, PAO #675-12,24 August 2012
x MIL-STD-889 x MIL-STD-1168 x MIL-STD-1316 x MIL-STD-1472 x MIL-STD-1474D x MIL-STD-2105 x FED-STD-595 x STANAG 4439 x MIL-HDBK-759, Notice 2 x MIL-HDBK-454A x ITOP 4-2-602 x TOP 1-2-511 x TOP 3-2-045 Customer Requirement Documents System Requirement
Post-traceability Traceability class concerned with those aspects of a require-ment's life that result from its inclusion in the requirements document [10]. Pre-traceability Traceability class concerned with those aspects of a require-ment's life that are prior to its inclusion in the requirements document [10]. Requirements analysis and
The majority of literature relating to food traceability focuses on using instruments and potential advantages of adopting a traceability system. There is a paucity of research related to the traceability of food served within a cruise ships' foodservice operations. Therefore, the purpose of this study is to explore food safety traceability
back to the raw material sources. Eliminating Traceability Gaps Eliminating traceability gaps requires the seamless integration of quality management and traceability data with process automation and ERP into a single enterprise-wide solution. Meeting today's quality, traceability and food safety challenges demands a previously unprecedented .
food supply chain traceability (e.g. Chen et al., 2008; Kelepouris, 2007; Peets et al., 2009). However, a recent review of food traceability trends and advances by Badia-Melis et al. (2015) suggests that current traceability systems in practice do not capture, link and share the food traceability data accurately and effectively. Notwithstanding the
introduction to RFID technology, overview the concept of traceability, and present several typical RFID traceability applications as powerful motivations for our work. In Sect. 3, we introduce a generic reference framework for traceability networks and examine fundamental traceability queries. In Sect. 4, we identify a set of essential
ISO 22005 is a specific standard for traceability in the food and feed chain. ISO 22005 adds that “Terms such as document traceability, computer traceability, or commercial traceability should be avoided.” For all these ISO definitions (ISO 8402, ISO 9000, ISO 22005), there
the national traceability vision that links specific goals and strategies with performance indicators Owning execution of traceability implementation plan deliverables including, but not limited to, market assessments, regulation execution, traceability model selection Validating that traceability strategy implementation is
4 Metrological traceability: The international definition 13 5 International system of quantities and units (SI) 13 6 Establishing traceability 15 6.1 Essential activities in establishing traceability 15 6.2 Specifying the measurand and required uncertainty 15 6.3 Choosing a suitable procedure 16 6.4 Validation 17
