White Papers

White Papers

Meet and deliver the results that today’s business environment demands

Vitech is dedicated to advancing the practice of systems engineering. We believe that systems thinking is key to solving worldwide challenges, and by improving the practice of systems engineering, we can improve the world we live in. To complement our more technical products, Vitech has recently undertaken a series of white papers to increase awareness and expand the effective application of systems engineering. Intended for technical and business levels alike, these white papers address fundamental needs, capabilities, and the value proposition for effective systems engineering. They offer insight into domain challenges, approaches, and benefits, helping project teams meet and deliver the results that today’s business environment demands of the systems engineering process.

One Model, Many Interests, Many Views

One Model, Many Interests, Many Views

In this white paper, Zane Scott and David Long lay out the many ways model-based systems engineering is capable of representing information contained in a model, or repository. Each diagram communicates a specific dimension of information, providing insight and best connecting with a particular audience.

The language that we use to depict the solutions under design consists of a set of views. These may be graphical or word-based, but in any case, they represent a subset of information from or about the model arranged for presentation according to a set of rules prescribed for constructing that view. Views are (or should be) constructed by querying the model for the needed information and then assembling the information into an agreed-upon format.

This paper discusses that language and its building blocks. We will examine various systems engineering views in some detail, paying particular attention to the information they convey, the format they use to convey it, and the intended audience they are designed to reach. The intent is not to provide an exhaustive treatise on the detailed notation (a purpose better served by guides, textbooks, and formal specifications), but instead an overview of many views, the information that underpins them, their interrelationships, and their effective use.

The Systems Perspective

The Systems Perspective

This paper by Zane Scott addresses the power that the systems perspective and systems thinking bring to the systems engineering practice. A topic regarded as esoteric by its very practitioners is reframed to deliver practical benefit.

The system perspective expressed in systems thinking both sets systems engineering apart from the other engineering disciplines and constitutes the substance of its relationship with other systems disciplines. This engineering distinctive and systems common ground is the central concept for systems engineering. It carries power and leverage yet is understood only in a superficial way by most practitioners.

9 Laws of Systems Engineering

9 Laws of Systems Engineering

Systems engineering is increasingly important in today’s business world. Even in businesses and industries where the term “systems engineering” is unknown, the need to guide the overall design and maintenance of business products and processes is apparent. Business cannot afford to develop products that won’t meet their customers’ needs or implement processes that will not “plug into” their enterprise frameworks.

For the manager seeking project success, the design team seeking to deliver a solution, and the customer seeking an answer to their needs, systems engineering is critical. It is through the application of sound systems engineering practices that the ultimate solution can be crafted to hit the mark while minimizing or eliminating unintended consequences. It is the systems engineer who maintains the systems perspective on the underlying needs and value proposition throughout the quest for a solution. It is the systems engineer who tracks the interaction of the system with its environment and works to prevent any unplanned, detrimental interactions that might result from the system design choices made along the way.

Without this systems perspective, solutions can go seriously awry. Unintended consequences can make the “cure” quite literally worse than the “disease.” Design choices can cause the solution to veer away from the customer needs that called for the solution in the first place. Sound systems engineering approaches stand against these possibilities.

Model-Based service volume engineering development using CORE software

Model-Based Service Volume Engineering Development Using CORE Software

Automatic Dependent Surveillance-Broadcast (ADS-B) system is considered the cornerstone of the Next Generation Air Transportation (NextGen) System that would transform today’s aviation and ensure increased safety and capacity in our NAS.

One of the most important design aspects of the ADS-B system is the design of the terrestrial radio station infrastructure throughout United States. Service Volume Engineering (SVE) is responsible for the technical design of such infrastructure that would meet all system requirements. This paper presents the model-based engineering approach adopted to support the majority of SVE design activities culminating with the development of a complex Geospatial / Radio Frequency entity-relationship engineering model. CORE software environment was selected for the development of such model based engineering environment.