SYSM 5630 Reflection Paper

Zafiro, Karina S. · 2026

Read SYSM 5630 Reflection Paper by Zafiro, Karina S. (2026) in the Tower of Babel, a free online library of public-domain works preserved in clean, searchable text. No sign-up. The full text is served as a plain-text file at a predictable URL, where text is present: https://antarctic-labs.com/tower-of-babel/doe-osti-3022997-sysm-5630-reflection-paper.txt.

Introduction

Karina Zafiro, writing from Lawrence Livermore National Laboratory, reflects on SYSM 5630, a systems engineering class taken through a partnership between Georgetown University and the lab. Her memo of August 11, 2025, addressed to Robert Pitso, is filed as report LLNL-TR-2011278. It is the third systems engineering class she has taken in the series.

One lesson she sat with is the split between verification and validation. Verification asks whether the system was built right, against its specifications. Validation asks whether the right system was built, against what stakeholders actually need. She notes that a fully verified system can still miss stakeholder expectations, and she ties the course's V diagram to cutting risk and rework.

Catalog record

CREATORZafiro, Karina S.
YEAR2026
COLLECTIONPAPERS
FORMATTXT
FILE SIZE6 KB
LICENSEPublic Domain
RIGHTSPUBLIC DOMAIN
SOURCEDOE OSTI

Source: https://www.osti.gov/biblio/3022997

Browse the full library · About the Tower of Babel

Full text

The opening of the work, from the library's hosted text:

LLNL-TR-2011278

SYSM 5630 Reflection Paper

K Zafiro

March 2026

This document was prepared as an account of work sponsored by an agency of the United States
government. Neither the United States government nor Lawrence Livermore National Security, LLC,
nor any of their employees makes any warranty, expressed or implied, or assumes any legal liability or
responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or
process disclosed, or represents that its use would not infringe privately owned rights. Reference herein
to any specific commercial product, process, or service by trade name, trademark, manufacturer, or
otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the
United States government or Lawrence Livermore National Security, LLC. The views and opinions of
authors expressed herein do not necessarily state or reflect those of the United States government or
Lawrence Livermore National Security, LLC, and shall not be used for advertising or product
endorsement purposes.

This work performed under the auspices of the U.S. Department of Energy by Lawrence Livermore
National Laboratory under Contract DE-AC52-07NA27344.

 UNCLASSIFIED

Memo
       Date:    August 11, 2025
 To: Robert Pitso
 From: Karina Zafiro
 Subject: SYSM 5630 Reflection Paper

Introduction
This is the third Systems Engineering (SE) class I have taken through the partnership between
Georgetown University and Lawrence Livermore National Laboratory (LLNL). In my previous jobs, I
had minimal exposure to SE and was intrigued about the methodical approach to completing
projects at LLNL.
The Fundamentals of Design Thinking and Systems Engineering class taught me how to identify and
understand stakeholder needs and to translate these needs into conceptual solutions. Most
importantly, this class taught me how to develop a system and verifiable requirements to address
stakeholder needs.
The System Architecting and Design class taught me how to define, model and communicate the
architecture and design of complex systems. In this class, I learned how to approach a system from
di-erent architectural viewpoints – operational, functional, physical, requirements and verification.
In this Systems Integration, Verification and Validation class, I learned about the entire system
development lifecycle and learned to fully appreciate the iterative process that is the application of
systems engineering tools and concepts.

Key Learnings & Insights
There are many versions of the Systems Engineering V model, my favorite version is shown on
Figure 1 on the next page. I am well-versed in the SRR-CDR-PDR-FDR progression of engineering
design so seeing these familiar design phases overlaid on the V helps me better understand system
development from start to finish. The arrows in the middle are a good reminder that one must
always look back and refer to the initial phases of the project to confirm we are still headed in the
right direction.
Verification and Validation, or V&V, are usually paired together but they serve di-erent purposes.
Verification asks, “Are we building the system right?”, while validation asks, “Are we building the
right system?” I had to sit with this for a little while to fully understand how each process plays a
role in minimizing risk, reducing rework and ensuring stakeholder expectations are met. Verification
meets engineering specifications, while validation meets stakeholder needs. It is entirely possible
to have a verified system that cannot meet the stakeholder expectations.

 UNCLASSIFIED

 Figure 1 The Systems Engineering V
(SRR = System Requirements Review, CDR = Conceptual Design Review, PDR = Preliminary Design Review, FDR = Final Design Review, IQ
 = Installation Qualification, OQ = Operational Qualification, PQ = Process Qualification, ATP = Acceptance Test Plan, CTP =
 Commissioning Test Plan, WAP = Work Authorization Procedure)

The hands-on portion of this class where a small group takes a case study through all aspects of a
project lifecycle was an e-ective way for me to really grasp the concepts. The iterative processes
allowed me to appreciate and get a more comprehensive understanding of previous concepts from
previous classes. Our team developed a requirements traceability matrix to map requirements to
design elements, test cases and validation methods and this drove in the power of traceability and
being accountable from start to finish.
Not all parts of a system require equal levels of scrutiny. Based on the assessed risk of failure,
resources can be allocated accordingly. Sub-systems with higher risk will require more robust
verification.

Future Implementation
This class has enhanced my technical skills significantly. I became more comfortable with making
comments during design reviews and meetings to discuss testing and commissioning plans. I have
noticed an improvement in my critical thinking skills, especially in analyzing failure modes and
questioning the basis used for writing system requirements.
This course transformed my perception of V&V from something that’s done at the end once the
design is completed to something that is included from the start.
I am part of a portfolio of projects in various development stages, and I have been lucky to have had
the opportunity to take what I had just learned in class and apply it to a project just a few days later!
I am looking forward to taking more advanced SE classes to keep growing my SE toolkit.

 2

 UNCLASSIFIED

For an added challenge, I wanted to see if I could overlay the SE V with the classic 5 phases of
Project Management: Initiation, Planning, Execution, Monitoring & Controlling, Closure. The first
draft is shown in Figure 2. I worked as a Project Manager for over a decade, so I know and
understand these phases well.

 Figure 2 MITRE Systems Engineering V-Model and Project Management

Notionally, the overlapping green ovals indicate interactions and iterations between each project
management phase with the coordinating SE life cycles. The purpose of this exercise is to help
explain what Systems Engineering is to someone who is more familiar with applying Project
Management Principles to a project.

Read the complete text