Date: 22 October 2014

Issue: 21

In This Issue

Relating the Functional and Physical Architecture in COREsim

Ron Kratzke, Vitech Principal Systems Engineer

Recently I have been fielding a number of questions regarding the use of LINKs in behavior analysis when running COREsim.

As CORE users are well aware, the COREsim modeling capability allows the system engineer to analyze the behavior of the system.

COREsim has an added feature that allows the systems engineer to integrate the functions and physical architectures to provide unique insight into the overall system architecture. Read More.

The Hero No One Knows

Warren Smith, Vitech Principal Systems Engineer

About 20 years ago, I met a systems engineer (name long forgotten) who was already an old hand at developing systems.

As we talked shop, discussing systems engineering, documentation, and office politics, he relayed a story that has stuck with me through the years. As a young engineer, he landed a job working on the Space program: a choice position indeed during the 1960s and early ‘70s. By this point, the program was quite mature. Most of the system specifications and design documents had long since been completed and released before he joined the team. Read More.

Using the Verification and Validation Facility in CORE 9

Ron Kratzke, Vitech Principal Systems Engineer

CORE 9 has the ability to allow the systems engineering team to plan Test and Evaluation activities for the system design project. This capability resides in the Verification and Validation Facility and includes the “VerificationRequirement”, “VerificationEvent”, “TestProcedure”, “TestConfiguration”, and “Test Activity” classes.

In a system design each leaf-level Function and Requirement is meant to be verified. This verification is captured by relating a “VerificationRequirement” to each Function and Requirement using the “verifies” relation (a VerificationRequirement verifies a Requirement/Function). The engineer may design a single VerificationRequirement to verify multiple leaf-level Requirements and Functions. Read More.

Using CORE for Almost Everything - Even Marketing

Katie Thacker, Vitech Communications Manager

Every day, we are seeing more and more members of “non-traditional” markets become curious about systems engineering, particularly model-based systems engineering. They are downloading the MBSE Primer, watching webinars, and asking for advice about how software could possibly not only help them get organized in their projects, but see potential problems before they arise, improve processes and products, and save time by simplifying the complicated process of coordinating ideas. Read More. 

4 Steps to Start your Systems Journey

David Long, Vitech and INCOSE President 

As I took the first steps in my systems engineering career 25 years ago, there was only one recognized path towards systems engineering: earn a degree in engineering, physics, or possibly math; work in your discipline for 10+ years to build a depth of knowledge and experience; then transfer onto a systems engineering team as dictated by corporate needs and personal interests. If you were lucky, you had the chance to attend a brief commercial training course or maybe even pursue a Master’s Degree at one of a handful of universities. You worked side-by-side with systems engineers of varying expertise and your systems journey had begun. Read More.