Presentation: The Benefits of a Requirements Verification Architecture Model
In-Person Event (with remote option)!
Please join us on Wednesday, 21 Sept 2022, at Filippis restaurant in San Diego for a HYBRID presentation (in-person and webcast) by Mr. Charley Patton, CSEP, where he will discuss the concept and present examples of a Requirements Verification Architecture Model (RVAM) as practiced on his current program with Northrop Grumman.
Date: Wednesday, 21 September 2022. 5:30-7pm (presentation begins at 6pm) Pacific Time
Location: Filippi’s restaurant in Kearny Mesa, San Diego, CA. 5353 Kearny Villa Rd, San Diego, CA 92123 (Google Maps)
Cost: Free! There will also be an optional buffet (Italian food) for $5 for INCOSE members, $15 non-INCOSE members starting about 5:30pm – please join us!
Format: This live presentation will also be webcast!
Dial-In: +1 669 900 6833
Meeting ID: 833 9927 3933
IF you were asked to develop your system’s requirements model or architecture model, you’d probably have a fair idea how to start and what those models would look like. What about your system’s verification model? The right side of the lifecycle V-model tends to get short shrift when it comes to developing models more descriptive than meer traceability matrices. Charley Patton, CSEP, will discuss the concept and present examples of a Requirements Verification Architecture Model (RVAM) as practiced on his current program with Northrop Grumman. A complete RVAM brings together requirements, architecture entities, and verification cases in a suite of diagrams that provide an important development team coordination tool.
Presenter: Mr. Charley Patton, Northrop-Grumman Corporation (NGC)
Charley Patton, CSEP, is a systems engineering lead for Northrop Grumman, which he joined in 2004. He has a B.S. in Electrical Engineering and Computer Science from the University of Colorado, Boulder, an M.S. in Business Management from SDSU, and several certificates, including a Systems Engineering certificate from UCSD and a Model-Based Systems Engineering certificate from Caltech. Mr. Patton transitioned from software engineering to systems engineering the old-fashioned way – his boss directed him to derive the system requirements because he was the most experienced member of the project team. From this first excursion into systems engineering, he learned increasingly disciplined methods for determining and documenting requirements and architectures; planned and executed system test and deployment activities; eventually joined the ranks of functional management leading a group of mostly software, integration, and test engineers; and even managed a hardware development team for a year. Today he splits his time performing systems engineering lead functions, responding to proposals, executing technical systems engineering tasks, and trying to get his dachshund to understand the value of properly documented ConOps.