G1

• Design Synthesis


  Process of translating the functional architecture developed in the Functional Analysis and Allocation step into a Physical Architecture, which includes product, system, and software elements that fulfill system required functions
• Physical Architecture


  Tangible structure or arrangement of physical components in a system or product. Forms the basis for design definition documentation, such as, specifications, baselines, & work breakdown structures (WBS)
• Modular Design


  Involves creating an item out of smaller, interchangeable parts known as modules
• Design Loop

  1. Define Problem

  2. Research Analyze

  3. Brainstorm

  4. Design Solution

  5. Build Prototype

  6. Evaluate Solution

  7. Redesign Solution
• Functional/Physical Matrix


  Tool used in systems engineering to map functional requirements to physical components within a system architecture
• Synthesis Tools

  • Trade Studies
  • Requirements Allocation Sheets (RAS)
  • Concept Description Sheets (CDS)
  • Schematic Block Diagrams (SBD)
  • Computer-Aided Design (CAD)
  • Computer-Aided Engineering (CAE)
  • Computer-Aided SE (CASE)
• Modeling


  Creating simplified representations of system components and behaviors using such tools. Models act as virtual prototypes, allowing engineers to test how the system would perform under various conditions. Helps teams communicate and collaborate by providing a common framework for understanding system behavior
• Schematic Block Diagram

  Traditional logical prototyping tool for Design Synthesis. A visual representation of a system's components and interconnections, typically displayed as blocks representing functions or subsystems and lines indicating connections

  
• Verification Process


  Confirms that Design Synthesis has resulted in a physical architecture that satisfies the system requirements. Throughout a system's life cycle, design solutions at all levels of the physical architecture are verified to meet specifications
• Verification

  Quality control process that determines if a system meets its system-level requirements
• Validation


  Quality control process that determines if operational requirements are met for the overall system to meet Initial Capabilities Document (ICD) and Capability Development Document (CDD)
• Verification Phases in V-Model

  • Requirement Analysis
  • System Design
  • Architectural Design
  • Module Design
  • Code Implementation
• Verification checks whether a component (software) confirms a specification
• Validation checks whether a component (software) meets the requirements and expectations
• Benefits of Verification and Validation


  • Making sure the product works
  • Improving the quality of the product
  • Minimizing costs and risks
  • Meeting rules and standards
  • Improving customer satisfaction
  • Improving performance and efficiency
  • Helping with continuous improvement
  • Improving safety and reliability
• Verification Process Key Objectives

  • Quality Control
  • Meeting Design Requirements and Customer Needs
  • Time Savings
  • Defect Reduction
• Verification Activities

  • Analysis (use of mathematical modeling and analytical techniques)
  • Inspection (visual examination)
  • Demonstration (use of system, subsystem, or component operation)
  • Test (use of the system, subsystem, or component operation)
• Performance Verification


  Performance requirements must be objectively verifiable, ensuring measurability, with Technical Performance Measurements (TPM) and management metrics employed to gauge progress towards meeting goals
• Verification Process Steps


  1. Planning (Verification Method and Level Assignments, Verification Task Definition, Verification Configuration Definition, Verification Scheduling)

  2. Execution (performance of a given verification task with supporting resources)

  3. Reporting (reports the compiled results of the executed verification plan and verifies the materials employed in system solutions can be used in a safe and environmentally compliant manner)
• System Architecture


  Describes the entire system, including physical architecture and support elements. MIL-HDBK-881 provides reference models for tailored top-level architectures

  
• Specifications


  Document that clearly and accurately outlines the fundamental technical requirements for items, materials, or services, including the procedures for verifying that these requirements have been fulfilled
• Specification Types


  • System Spec (defines mission/technical performance req, allocates requirements to functional areas & defines interfaces)
  • Item Performance Spec (defines performance characteristics of CIs and CSCIs, details design req & w/ drawings & other documents form the Allocated Baseline)
  • Item Detail Spec (defines form, fit, function, performance, and test req for acceptance)
  • Process Spec (defines process performed during fabrication)
  • Material Spec (defines production of raw materials or semi-fabricated material used in fabrication)

  
• Requirements documents explain why development is necessary, specification documents detail what the system must do technically (functionality, performance, interface), and design documents outline how design requirements are met
• Baselines


  • Functional Baseline
  • Allocated Baseline
  • Product Baseline
  • End Product Baseline (cover system requirements, architecture, technical drawings, and traceability)
  • Enabling Product Baseline (encompass manufacturing plans, supportability, manuals, training, and deployment planning, with a focus on susceptibility to configuration changes)
  • Acquisition Program Baselines (embody only the most important cost, schedule, and performance objectives and thresholds)
• Configuration Baselines

  Identify and define an item's functional and physical characteristics. Functional Baseline – describes system level requirements, Allocated Baseline – describes design requirements for items below system level, Product Baseline – describes product physical detail

  
• Decision Database


  Serves as documentation for configuration solution decisions, encompassing various analyses such as: Trade Studies, Cost Effectiveness Evaluations, Quality Function Deployment (QFD) Analysis, Models, Simulations, and Other Relevant Data. Aids in understanding requirements, developing alternative solutions, and ultimately selecting the most suitable option
• DoD Basic Classifications of Specifications

  • Material Specifications (dev by DoD components)
  • Program-Unique Specifications
  • Non-DoD specifications

  
• DoD Policy is to develop performance specifications for procurement and acquisition, and gives preference to the use of commercial solutions to government requirements, rather than development of unique designs
• Performance Specifications

  Define products in terms of functions, performance, and interface requirements

  
• Detail Specifications


  A specification that contains both performance and detail requirements. Item – like a description or a list of what something should be like, Performance – precise standards by which a system must fulfill its intended purposes, Detail – provide comprehensive, frequently technical explanations of how the system should operate or be implemented
• IEEE/EIA 12207 standard describes the development of software specifications as one aspect of the software development process
• MIL-STD-961D establishes uniform practices for specification preparation, to ensure inclusion of essential requirements, to ensure Verification (qualification) methods are established for each requirement, and to aid in the use and analysis of specification content
• Standards

  Establish engineering and technical limitations & applications for items, materials, processes, methods, designs, and engineering practices. "Corporate knowledge" documents describing how to do some process or description of a body of knowledge
• DoD Policy applies to the imposition of both Military Specifications and Standards and, in addition, to the imposition of Commercial and Industry Standards. The preferred approach is to allow contractors to use industry, government, corporate, or company standards they have determined to be appropriate to meet government's needs
• DoD Index of Specifications and Standards (DoDISS)


  Lists all international, adopted industry standardization documents authorized for use by the military departments, federal and military specifications and standards
• Standards


  Establish engineering and technical limitations & applications for items, materials, processes, methods, designs, and engineering practices
• Specification Hierarchy


  Structured organization of requirements and specifications within a system
• DoD Policy (Standards)


  Applies to the imposition of both Military Specifications and Standards and, in addition, to the imposition of Commercial and Industry Standards
• System Analysis and Control

  • Connects all other Systems Engineering operations, provides guidance, and serves as a map of the process's journey
  • Activity that covers the duration of the program
• System Analysis

  Involves studying a system's components, interactions, & processes to better understand how it works and how it may be improved