5 Systems Engineering Principles to Managing Your Organizational System
By Sara Sumner
Posted on August 20, 2015
Throughout my professional career, I have worked at three different companies, each specializing in systems engineering. Ironically, I have found that even though systems has been the focus of each company, I didn’t find a true “systems” emphasis until I joined Vitech. As the VP of Professional Services (and my boss), Zane Scott, likes to put it, that requires a “focus on understanding systems and working from the perspective of that understanding.” A company true to the “systems” in “systems engineering” will manage the organization as a system itself, being deliberate and tactical regarding the management of the organization, and applying systems engineering principles ensuring organizational success. Below are five of the many systems engineering practices key to successfully engineering an organizational system:
1)Identify Your Mission
2)Keep the Systems Perspective
3)Manage Your Interfaces
4)Design for Redundancy
5)Verify and Validate
MBSE: Aligning Systems Engineering with Verification and Validation
By Mark Simons
Posted on November 21, 2019
In model-based systems engineering, we tend to focus on requirements and design, but how many MBSE implementations consider aligning design with verification and validation (V&V)? The Vitech systems metamodel is especially capable of supporting V&V activities throughout the development lifecycle on either side of the “V.” Let’s take a look.
The typical “V,” illustrated in the following figure, depicts verification planning activities on the left side of the V, and verification execution activities on the right side of the “V.” In reality, verification and validation activities are also conducted on the left side of the “V” in conjunction with system development activities. Left side verification and validation typically consists of verification by analysis using simulation to validate the evolving system design, while right side V&V consists of the traditional unit, integration, system, and operational testing of the system as it is integrated and field tested.
Figure 1. The Engineering Model
If V&V is in reality aligned with system development, what metamodel can be defined to guide these activities? The world of verification and validation tends to vary more from organization to organization than typical systems engineering. Typically, systems engineers speak about requirements, behavior, and system design. V&V, on the other hand, is implemented in many different ways depending on your engineering domain, organization, or field. Despite this variability, the Vitech systems metamodel provides a means to formalize V&V methodologies and connect V&V with systems engineering. An excerpt of the Vitech systems metamodel, included in the following figure, depicts four unique classes specific to V&V, and describes the relationships among these classes, and with other classes in the systems metamodel.