Systems Engineering %%%%

Category: Systems Engineering

30 Apr 2019

Visit Adaptive at Booth #893 at the International Microwave Symposium

June 2-7
Boston Convention & Exhibition Center

Visit us at booth #893.

Join us in Boston for the IEEE MTT International Microwave Symposium covering all aspects of microwave theory and practice.  Adaptive will be demonstrating the power of SIMULIA on the 3DEXPERIENCE Platform.  SIMULIA is a portfolio of simulation tools to help optimize the complex design of parts and boards for electronic and microwave components, materials analysis and more.  Applications in the SIMULIA portfolio enable engineers to test performance, reliability, and safety of materials and products while still in the virtual environment, saving time and money by reducing or eliminating physical prototypes.  

Our specialty toolset for microwave electronics applications includes two new product offerings on the 3DEXPERIENCE platform:

CST Studio Suite®, a high-performance 3D electromagnetic (EM) analysis software package, meets design, analysis, and optimization needs for EM components and systems. EM analysis is commonly used to examine questions such as electro-mechanical effects in motors and generators, thermal effects in high-power devices, exposure of the human body to EM fields, and electromagnetic compatibility and interference (EMC/EMI), among other uses.

Wave 6 – The next-generation vibro- and aero-vibro-acoustic simulation tool which offers a wide variety of industry application simulations and unique analysis methods that efficiently and accurately simulate noise and vibration across the audible frequency range.

About the Conference

The week-long conference includes technical paper presentations, workshops, tutorials as well as social events and networking opportunities. 

Some of this year’s highlights include:

  • IMS Three Minute Thesis (#MT) Competition
  • a 5G Summit showcasing next-generation wireless technologies
  • RF Boot Camp – a three-day course on RL/microwave
  • Industry workshops including:
    • Microwave Materials: Enabling the Future of Wireless Communication
    • 5G mm-Wave to sub-THz Circuit and System Techniques
    • Quantum Computing for RFIC Engineers: Concepts, Devices, Systems, and Opportunities
    • Fundamental of mm-wave IC design in CMOS
    • State-of-the-art RF Receivers: Leading Edge Industrial Architectures and New Systems on the Horizon
  • Networking events
  • Student Design, Student Paper, Industry Paper, and Advanced Practice Paper Competitions
  • Project Connect for under-represented minority engineering students, and the PHD Student Initiative for new PhD students

The Plenary session on Monday, June 3, features Dr. William Chappell, Director of the Microsystems Technology Office (MTO), Defense Advanced Research Projects Agency (DARPA) who will speak on “The Mind and Body of Intelligent RF.”

Find out more and register today


31 Jul 2018

Getting Started with Systems Engineering

With the ever-increasing adoption of “smart,” mechatronic products requiring a combination of a mechanical, electronics, and computer engineering, the discipline of systems engineering has never been more important.  Given the complexity of modern products, systems engineering’s methodical approach for product definition and realization is being done by most companies whether they realize it or not.

The systems engineering process flow is often represented as a “V” diagram and as with any process there are many variations of it (to get a quick sample do a Web image search of “systems engineering”).  Rather than presenting yet another “V” diagram to gain an understanding of how to better manage a systems engineering process, it is simpler to just focus on the two main aspects of systems engineering and its main sub-processes:

Product Definition

  • Requirements development
  • Functional breakdown and logical analysis
  • Product design

Product Realization

  • Sub-system integration
  • Verification that requirements are met
  • Validation of product behavior

As mentioned, most companies developing mechatronic products do perform systems engineering sub-processes – some more formally than others.  For instance:

  • With software, it is very common to see solutions that manage detailed requirements and their associated test cases for verification. Teams developing mechanical and electronics hardware, the need still exists, but adoption of formal tools has not been as common.
  • Many companies organize their bills-of-material based on a functional breakdown to facilitate the eventual sub-system integration from various engineering disciplines as designs are completed. Unfortunately, this approach fails to properly capture the logical relationship between sub-systems and how they interact.

Another common issue is that companies rely too much on costly physical prototypes, or even worse, early production runs, to validate if the final user/consumer will accept the product.  Companies are not taking advantage of modern simulation and product behavior modeling software to validate product performance enough early in the product development process as the system functional breakdown and product design occurs.

Lastly, even if every one of these sub-processes are pursued, it is often with unique tools and systems that do not allow for the easy flow and exchange of information between product development participants.

Considering the status quo and the issue highlighted above, what is really needed for effective systems engineering is:

  1. Capture requirements for hardware and software.
  2. Define test cases to verify that requirements are fulfilled.
  3. Model a product’s sub-systems based on function and their logical relationship to one another.
  4. Virtually model product behavior to validate that a system meets end user expectation.
  5. Perform product design with kinematics and/or virtual simulation to further validate and verify system performance.
  6. Ideally perform #s 1-5 with tools that provide easy data exchange and traceability between the various stakeholders from requirements through product design, verification, and validation.

The traditional “V” diagram falls short in properly conveying how this systems engineering flow should be executed because most do not convey feedback loops and parallel activities.  So, rather than being constrained by the “V” shape just because “verification” and “validation” are the goals, the following can be used to convey a systems engineering target.

Pursuing the full scope of systems engineering processes may seem daunting, but the Dassault Systèmes 3DEXPERIENCE solution provides capabilities for each of these systems engineering needs with increasing levels of capabilities so companies can improve their systems engineering process over time while still having a unified approach.  The following table summarizes the key systems engineering capabilities offered with 3DEXPERIENCE:




Engineer (SNK)
and pre-requisites

Engineer (SQK)
and pre-requisites

Specialist (MCK)
and pre-requisites

and Test Case

Functional and
Logical Sub-
System Definition


Product Design


To learn more about the 3DEXPERIENCE systems engineering solution, refer to