Enhancing Collaborative IV&V through Content and Context: Insights from Patrick Olguin at NASA Workshop
Discover insights shared by Patrick Olguin at the NASA IV&V Annual Workshop in 2012 focusing on content and context-based collaborative IV&V. Olguin, with extensive experience in aerospace and commercial software development, emphasizes real-time peer review, the importance of delivering content in the right context, and the drawbacks of using PowerPoint in dynamic and interactive discussions. Join the journey of exploring new possibilities and interactions in IV&V.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Toward Content & Context- based, Collaborative IV&V IV&V Facility Welcome Stay Awake for 30 More Minutes! Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 1
Who is this Guy? IV&V Facility Hi, I m Patrick Olguin and I m from the government I m here to help you 29 years in aerospace and commercial software development Still upset I am no longer the college wiz-kid Taught C++ for 4 years Software Manager still recovering 4 years JPL Deep Space Network Ground Systems A very obscure, but impressive-sounding tech brief 11 years NASA IV&V MER, MRO, Phoenix, Kepler, GRAIL, Cx/ESMDI, JWST A pure software guy, living the dream of working with spacecraft flight software Our new acronym for Content&Context-based Collaborative IV&V C3I (darn that one s taken.. C3IV2 works) BTW Power Point is Evil Edward Tufte, 2003 Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 2
Goals IV&V Facility Interact with you and hopefully provoke you a little ok, a lot I m a teacher. You are forewarned Make some of you shout for joy at the possibilities we explore today Make some of you wish the workshop were over - NOW Cause you to think about how we work and interact With the workstation, tools and intranet environment With our information (artifacts, products, guidelines, work instructions, tasks) With one another (customers, colleagues, projects) Tell me how awesome/horrible I am: patrick.m.olguin@nasa.gov Agree with Ed and me on the evil of Power Point Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 3
Assertions IV&V Facility Searching is a waste of time Content delivered in the right context is everything Collaboration is real-time peer review Power Point is still Evil Edward Tufte Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 4
Ok, Why is Power Point Evil? IV&V Facility Stifles creative thought, for the most part Enforces outlined presentation and decomposition, which is not how all of us think and/or communicate Great for pictures, diagrams, real visual aids I have some of those! Not really conducive to this incredibly dynamic and interactive subject! Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 5
Searching is a Waste of Time IV&V Facility Searching violates 100-year old assembly-line theory The human should never wait for the machine/system I know what I need to do; the task management system knows what I need to do, so give me what I need to get my job done! What do we do with distributed systems? 200ms response isn t always possible. Do what everyone else does: Indexing Ranking Context-based suggested links We already have a rich assortment of pre-loaded queries Run them ahead of time instead of browse-and-run Search is a last resort Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 6
What Industry is Doing IV&V Facility Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 7
What We Could Be Doing IV&V Facility Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 8
Dynamically Built Environment In Other Words How Everyone Else Does it how about? Clickable, dynamically linked document tree Enables bridging of documents-as-built by projects and documents-as- required by IV&V for analysis Contract document # Project # Developer # Links and click-thrus are dynamic Based on simple rules reinforced by relevancy-ranking There are many free resources all over the net on how to develop these Unused/Unpopular links are eventually hidden They never go away Never out-of-date IV&V Facility Integrated Environment that learns what you need, for instance, Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 9
Content - What About Artifacts? Artifacts are everything We have to instantly/easily be able to identify what the document is, despite the wildly varying nomenclature across projects It s in the language (their requirements) with which they are most familiar CM is just the tip of the iceberg Intake of artifacts is where you make your money The purpose is to DELIVER CONTENT TO YOUR ANALYSTS How many times have you gotten this email? Hey, I just uploaded the $#@%!!-FSW Spec to the server, here s the link:<insert insanely long link>. Please update your TIMs. IV&V Facility Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 10
Real-time Content Delivery to the Rescue! IV&V Facility Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 11
What is the Magic Behind Content Delivery? IV&V Facility Artifacts are ingested into several frameworks Visible framework is a dynamically-built, clickable project document tree/site map Addresses the age-old problem of documents known by many names across developers Analysts that are new to the project can navigate the document hierarchy with ease. Facilitates adding resources to analysis tasks quickly by reducing spin-up time wasted in searching-out documents Document tree is a familiar metaphor of the system hierarchy, common to project and IV&V Old dogs can learn new tricks! Invisible framework links each artifact to: Project Document tree (the navigation aid) Previous version (if applicable) Parent and children documents Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 12
What is the Magic Behind Content Delivery? (continued) IV&V Facility Artifacts are LINKED to Issues (this is the payoff!) Updated artifacts automatically trigger notifications to analysts that issues require updating NOT AN EMAIL! The notification comes in the form of a complete task in the task-tracking database, which is a shrink-wrapped record containing links to: Open Issues Updated artifact Previous worksheets Related artifacts (and of course links to the ever-helpful document tree) Selected Methods from Catalog Requires the Issues be linked to artifacts (multiple artifacts ok) Current IV&V Facility issue database supports this Removes ambiguity/uncertainty Have we checked all of our issues related to this update? Data-driven vs. State/Metric-driven Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 13
Collaboration IV&V Facility IV&V can be a lonely experience What if being able to see what others are working on were as simple as scrolling through my list of on-line colleagues? Secure Chat client? Cut and paste of questions Real-time feedback with your colleague Has been used on previous projects Stay connected without necessarily interrupting one another Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 14
Is There Anybody Out There? IV&V Facility Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 15
Collaborate! IV&V Facility Skills Database We have one, at least. Put it to use! Experts in the domain/project/CSCI/language/project you re working are filtered and populate (or at least categorize) your chat list. No more searching! Analysts are pre-wired to help one another Coworkers/Customer status is in your newsfeed and their page (duh!) Augments formal communication paths Real-time peer-review with colleagues Raise your hand if you are loathe to use MKS/Orbit as a peer- review tool Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 16
Going off Script/Questions IV&V Facility Other context-sensitive features? How many times have you written a duplicate issue? As you re working on an issue, the system should be able to identify most duplicates before they re written, given information such as section, paragraph, quoted requirement/code Think of the Microsoft Word assistant that says, It appears you re writing a letter, would you like to use the template? What if the system could find/suggest issue relationships without them being explicitly created? Hello this looks like an issue against an unrelated document, but a similar design pattern would you like to see it? Word360 web-enabled MS Word. Why not edit rich-formatted text with one tool? We are only scratching the surface. Patrick Olguin - 2012 NASA IV&V Annual Workshop 9/13/2024 17
