|
|
Developing the System Architecture
Reducing Cost and Risk Through Systems Engineering
System conceptualization
provides an easily understood overview of the system architecture.
Structured methods
make the allocation of requirements to the system, software, and hardware architectures a manageable and thorough process.
Collaboration with your staff
yields an accurate allocation of requirements and a practical system architecture.
Our goal
is to help your staff develop a practical system architecture and accurate allocation of requirements.
Our architecture development experience
covers a broad range of control systems, communications, and RF sensors.
|
Architecture Effort
|
Examples
|
Developed Concept System Architectures
|
- Cooperative engagement system
- High-gain electronic support concept
|
Performed Architecture Trade-off Studies
|
- Weapon systems with varying degrees of observable RF emissions
- Missile warning systems
- Electronic warfare system cost and weight, volume, and power consumption
- Antenna subsystem cost and weight vs. radar detection performance
- Radar monopulse processing
|
Created Hatley-Pirbhai Methodology1 (HPM) Architecture Models
|
- Multiple-unit parallel solid-state power conversion system
- 6 software project proposals
- Secondary radar system
- Cooperative engagement system
- Radar system upgrade
- Proposed electronic warfare systems
- Electronic support receiver
|
Allocated System Requirements
|
- Numerous radar tracking modes
- Electronically-scanned antenna
|
Estimated Software Sizing
|
- Numerous radar tracking modes
- Passive ranging with an electronic support receiver
|
Supported Architecture Development Process
|
- Developed electronic warfare system configuration database tracking components for pricing model, weight, volume, and power consumption
- See also the Requirements page for additional information on CASE methods, tools, and training
|
|
1 HPM is a set of structured methods for specifying system, software and hardware requirements.
|
|