Eagle6

Eagle6: Modeling & Simulation for 3 Primary Problems in Systems Engineering

Eagle6 is a first of its kind new modeling application that tests all possible system states within the test scope limits.

Question: “I have a great idea, but what happens if I change my system architecture?”

Answer: Test BEFORE you invest.

New technological solutions work great in the lab. The unknown is how the system will behave once it has been integrated into the enterprise. Worse yet, how will the new system affect the existing systems in the enterprise? Because enterprise components share everything from data to network bandwidth, anticipating the effects of change to an enterprise can be extremely difficult for larger, more complex enterprise systems. Tackling the Challenge of Systems Architecture Challenge 1: Changes to System Architecture May Cause Unintended System Behavior Challenge 2: New Technologies and Legacy Systems May Not be Compatible Challenge 3: Existing Organization Constraints May Not Support New Business Process Designs

Eagle6 is powered by Monterey Phoenix, a revolutionary modeling language developed by the Naval Postgraduate School.

Click HERE to learn more about how Eagle6 can save time, money, and risk by testing architectural designs before they are implemented. 

Challenge 1: Changes to System Architecture May Cause Unintended System Behavior

Problem: Traditional system testing techniques are not designed to identify architectural designs that result in UNINTENDED system behavior. Solution: Eagle6 tests all possible system states within the test scope limits. This mathematical approach to testing all possible scenarios within scope allows for system architects to identify architectural flaws with proposed designs BEFORE starting the building process. System architecture verification and validation saves time and money while preventing risk of system architectural design failures. Test BEFORE you invest!

REDUCE RISK OF UNINTENDED SYSTEM BEHAVIOR

System Architects struggle with the issue of maintaining the validity of system requirements. Unified Modeling Language (UML) diagrams are the traditional tool of choice for most architects, but testing UML diagrams in a Rapid Application Development (RAD) environment is cumbersome and inefficient. Our modeling software allows architects to quickly model system designs in such a way that they can be tested against the original requirements. Since our modeling methodology uses a single model from concept through execution, testing changes to system design in a RAD environment is no problem with Eagle6.

Making architectural changes to an enterprise requires a thorough analysis of how proposed changes may affect business processes and IT infrastructure. Our technology enables your organization to model and test alternative design ideas without having to experiment on a real system, which may be prohibitively costly, time-consuming, or simply impractical. It allows you to ask "what if?" questions about a system design without having to experiment on the physical system, and hence incur the costs of field tests.

Challenge 2: New Technologies and Legacy Systems May Not be Compatible

Problem: Legacy systems contain hardware, software, databases, and data structures that are largely dependent upon the legacy design. Newer technologies may contain hardware/software integration requirements that are not compatible in a legacy environment. Worse yet, the stress of placing a new system that does not “flow” with the legacy architecture may cause related systems to fail.

Solution: Eagle6 is a modeling and simulation tool that is capable of predicting system behavior. For example, Figure 1 represents the results of a model that was designed to test a Navy Gunship system’s ability to sustain multiple target tracking after a new radar system has been installed. The goal of the test is to test the radar within the constraints of the legacy environment. The new radar system works great in the lab, but the real question is “Can the legacy Command and Control, Gun Computer, and system network handle the new radar data stream?”

Bottom Line: Architectural verification and validation saves time, money, and risk of system architectural design failures.

Challenge 3: Business Constraints May Not Support New Business Process Designs

Problem: Changing the process in which an organization executes their business plan often results in reduced productivity, increased stress within the workforce, and unforeseen stress placed on systems that were not designed to support the new business processes.

Solution: Unlike any other modeling software, Eagle6 has the capability to model the system AND the environment. With Eagle6, an Architect can model the business process, human process, and system process in a single model, and test for violations of system or organizational constraints. Modeling a BPR effort limits the risks associated with changing an organization’s business process.

Changing the way your agency does business may result in UNINTENDED consequences that can be avoided by modeling potential architectural designs.  Test BEFORE you invest!