14. Define the required information and argumentation mechanisms allowing well-balanced and risk-informed arguments with various levels of formality for acceptance decision making,
18. The GM-VV Volume 3: Reference ManualThe GenericMethodology for Verification & Validation Is introduced and defined in Provides guidance on implementation and use of Provides technical and referentialbackground information for Learns the basics of GM-VV from the GM-VV Vol 1. Introduction and overview M&S/VVAOrganizations and Personnel GM-VV Vol 2. Implementation guide Apply GM-VV by using the GM-VV Vol 3. Reference Manual Obtain VV&A and relatedbackground information on and for usewithin GM-VV from the
34. Member of a sponsoring organization or corporatehttp://www.sisostds.org ”SISO’s mission is to provide an open forum that promotes the interoperability and reuse of models and simulations through the exchange of ideas, the examination of technologies, and the development of standards.”
35. Standardization process Overview of the SISO standardization process Maturation of concept Sponsor Organization Study Group Standing Study Group Product Nomination Development of standard Product Development Group Balloted Standard Product Support Group
36. Standardization process Preliminary Ballot Group SISO Balloting process PDG vote to go to balloting Ballot Pool Membership rules Interme-diate Ballot Group Final drafted product to SAC for approval SISO Members Ballot Group Balance guidelines Other interested people SAC announce Ballot Product approval SAC announce Ballot Balloting Comment resolution
37. Ballot balancing rules Membership rules: Balance guidelines: Apply for membership and pay fee Committing to conduct thorough review and completing in required time Representation: Commercial, Government, Academic Interest: User, Developer, General Interest No representation should exceed 75% and each category >10% No organization >25% No interest >50%
39. Pilot Case Study Introduction Rationale Objectives Technology readiness level is 4 (Component and/or Breadboard Validated in Laboratory Environment Setting) Test the method in a real environment (improve, involve, strengthen) Correctness and utility of the document set* Practical applicability of GM-VV: knowledge & experience Educational material development (tutorials) Tools (evaluation, requirements)
40. Pilot Case Study Scenario: FileProof Rijkswaterstaat(2006-2008) aimed at: Immediate reduction of traffic jams by means of smart, innovative and practical approaches About 60 projects in 3 main categories: Projects aimed at reduction of regular and incidental traffic jams Projects tempting people to think and act differently
41. Pilot Case Study Scenario: FileProof Our Focus: Flashing lights off On site Why Flashing Lights Reduction of speed Not to draw attention to an accident Directive First vehicle (fend off car) lights ON Other cars (rescue workers) lights OFF Compliance in practice? Falls short of expectations
42. What are the effects of showing one or multiple flashing lights on: The safety of rescue workers on site, and Traffic flow Effect of light color (blue or amber / yellow)? Effect of time of day (daylight / evening)? Effect of position accident (own lane or other direction)? Pilot Case Study Scenario: FileProof
43. Introduction Pilot Case Study Scenario: FileProof Approach Deliverables 5 workshops, 4 nations (FR, NL, DE, SE) Focus on Technical Processes & Products Spiral Development (iterative & incremental) White Paper Authoritative & Educational Illustration Benefits, Limitations & Improvements Introductory Tutorial Presentation Dissemination for M&S Community Illustration & Guidance Application
44. The Case Study The content of the document has a steep learning curve with a high entry level Wording is long, fuzzy, vague and pressumes a lot Misleading titles creating false expectations No leading document driving the reader Weak cross-document proof reading There is no document that specifies THE methodology Bits & bytes scattered among the 3 documents HB perspective not clearly communicated Multiple objectives set Overlapping information & inconsistencies Incompatible to SISO product nomination More cases Pilot Case Study Scenario: Findings
Ballot announcement goes out to all SISO membersMembership rules:Apply for membership and pay feeCommiting to conduct thorough review and completing in required timeRepresentation: Commercial, Government, AcademicInterest: User, Developer, General InterestBalance guidelines:No representation should exceed 75% and each category >10%No organization >25%No interest >50%SAC approve compositionFirst ballot period 30-60 daysFormulate comments, suggest resolustion, determine whether to accept or reject the productComments, General, Editorial, Technical>75% of the ballots must be returned for a valid ballotIf >30% abstain, ballot invalidProducts which have a successful product ballot and have had no comments submitted shall proceed on tothe next step in the Balloted Products Development Process (Product Approval). Products which havecomments submitted by ballot group members shall have the comments resolved prior to product approval. Balloted products that do not have a successful product ballot shall go through the comment resolution and product ballot re-circulation.In the case where a consensus product is achieved, the PDG continues the product development process for accomplishing the final product approval and circulation.In the case where the process is halted, the community is advised. If proponents wish to attempt toresolve issues within the community and start the process again at a later time, they may.