3.3.2 Polymorphic System Architecture
Jeff Bryson · INCOSE International Symposium · 2010
Abstract The complexity of tomorrows problems will be far greater then problems we face today. This complexity will only increase the importance of systems engineering and systems architecture activities. As the value of the activities rise, the cost of the activities must fall. Neither a Multi‐year analysis and development schedule nor a short term schedule with a high risk of failure will be acceptable solutions. The solution for solving these complex problems will be to move systems engineering and architecture artifacts from the Non‐Recurring Engineering cost over head to reusable company assets. A Polymorphic System Architecture (PSA) is one way of achieving this goal. Run‐Time polymorphism (RTP) has been used in the software community for over 20 years to satisfy dynamic reconfiguration, plug‐n‐play, extensibility, and system redundancy requirements. RTP is also used to construct software Systems of Systems. Systems engineers now have the same requirements applied to system architecture. A PSA utilizes the same software technology but applies it to the system architecture (Bryson 2009). The goals of using a PSA are: Reduce the complexity of the system architecture Satisfy functional requirements within the system architecture Define an architecture that has the potential to mature over time Move the system architecture from cost overhead artifacts to company assets Create an architecture library of reusable artifacts that can be reused to solve new problems