IoT工程師的見解
市場調查報告書
商品編碼
1128129

IoT工程師的見解

Voice of the IoT Engineer

出版日期: | 出版商: VDC Research Group, Inc. | 英文 30 Pages; 342 Exhibits | 商品交期: 最快1-2個工作天內

價格
簡介目錄

本報告提供700人以上的IoT、內嵌工程師和決策者、影響者為對象每年實施大規模的調查,分析劃時代的知識和見識。調查對象,是硬體設備的選擇,作業系統 (OS),內建式軟體堆疊,網路安全用硬體設備、軟體,軟體開發工具等。這個資料集中,包含各產業、各地區、各組織規模的區分,及主要人口統計、行動學特性的交叉表列。

目錄

摘要整理

調查受訪者的人口統計和概要

硬體設備的概要與趨勢

  • 所有種類的組織,籌措著各種硬體設備
  • 各種處理器的利用增加
  • IoT/內嵌及邊緣系統,與企業/IT以不同的方法更新
  • 邊緣閘道器廣泛使用,每產業的採購方法不同

軟體堆疊的概要與趨勢

  • 1個OS並不適合全部
  • 填補與開放原始碼的分歧

內嵌、IoT網路安全趨勢

  • 試驗IoT設備的網路安全的組織增加

開發工具的概要與趨勢

  • 試驗,試驗

連接性和IoT趨勢

  • 無線通訊的採用增加

附錄:市場定義

關於VDC Research

簡介目錄

This report analyzes breakthrough findings from our extensive annual survey of over 700 IoT and embedded engineers, decision makers, and influencers. Topics covered include hardware selection, operating systems, embedded software stacks, cybersecurity hardware and software, and software development tools. The dataset includes segmentations according to vertical market, geographic region, and organization size with cross-tabulations across major demographic and behavioral characteristics.

Table of Contents

Executive Summary

  • Key Findings

Survey Demographics & Overview

  • Respondent Qualifications and Demographics

Hardware Overview & Trends

  • All Types of Organizations Are Sourcing Many Types of Hardware
  • Different Processor Types Are Growing in Use
  • IoT/Embedded & Edge Systems Are Updated Differently than Enterprise/IT
  • Edge Gateways Are Used Broadly & Sourced Differently Across Industries

Software Stack Overview & Trends

  • One OS Does Not Fit All
  • Bridging the Gaps to Open-Source

Cybersecurity Trends for Embedded & IoT

  • More Organizations Testing Cybersecurity of IoT Devices

Development Tools Overview & Trends

  • Testing, Testing

Connectivity & IoT Trends

  • Increased Adoption of Wireless Communications

Appendix: Market Definitions

About VDC Research

List of Exhibits

  • Exhibit 1: Primary Country of Residence
  • Exhibit 2: Type of Most Current or Recent Project
  • Exhibit 3: Personally Involved with Engineering of Embedded Technology
  • Exhibit 4: Type of Purchase by Respondent's Organization
  • Exhibit 5: Primary Industry Classification of Project
  • Exhibit 6: Type of Aerospace & Defense Application for Most Recent Project
  • Exhibit 7: Type of Automotive In-Vehicle Application for Most Recent Project
  • Exhibit 8: Type of Communications & Networking Application for Most Recent Project
  • Exhibit 9: Type of Consumer Electronics Application for Most Recent Project
  • Exhibit 10: Type of Digital Security Application for Most Recent Project
  • Exhibit 11: Type of Digital Signage Application for Most Recent Project
  • Exhibit 12: Type of Energy and Utilities Application for Most Recent Project
  • Exhibit 13: Type of Gaming Application for Most Recent Project
  • Exhibit 14: Type of Industrial Automation Application for Most Recent Project
  • Exhibit 15: Type of Media & Broadcasting Application for Most Recent Project
  • Exhibit 16: Type of Medical Device Application for Most Current Project
  • Exhibit 17: Type of Mobile Phone
  • Exhibit 18: Type of Office/Business Automation Application for Most Recent Project
  • Exhibit 19: Type of Transportation Application for Most Recent Project
  • Exhibit 20: Type of Retail Automation Application for Most Recent Project
  • Exhibit 21: Type of Non-Manufacturing/Services Application for Most Recent Project
  • Exhibit 22: Certification/Approval Standards Required for Current Project
  • Exhibit 23: Highest Design/Development Assurance Levels (DAL) Required for Project Software (Aerospace)
  • Exhibit 24: Highest Software Integrity Levels (SIL) Certification Required for Project Software
  • Exhibit 25: Highest Automotive Software Integrity Levels for Project Software
  • Exhibit 26: Capabilities/Features of Current Project
  • Exhibit 27: Capabilities/Features Expected in a Project Three Years From Now
  • Exhibit 28: Type of Real-Time Deadlines for Current Project
  • Exhibit 29: Application's Shortest Response Deadline to a Time-Critical Input or Event
  • Exhibit 30: Estimated Length for Current Project (In Months)
  • Exhibit 31: Current Project's Schedule
  • Exhibit 32: Estimated Number of Years Current Project will be Manufactured Once Complete
  • Exhibit 33: Estimated Number of Years of Useful Life for Product Once Deployed
  • Exhibit 34: Attributions of Delays to Project
  • Exhibit 35: Engineering Tasks Personally Involved
  • Exhibit 36: Estimated Percent of Time Spent on Engineering Tasks
  • Exhibit 37: Does Organization Have Formal Policies and Procedures for Testing the Security of IoT Devices?
  • Exhibit 38: Personnel Testing the Security of IoT Devices
  • Exhibit 39: Estimated Number of Full-Time Staff on Current Project
  • Exhibit 40: Engineering and Development Work Outsourced to Third-Party Engineering Services
  • Exhibit 41: Percent of Entire Engineering/Development Effort in Each Task that was Outsourced for Current Project
  • Exhibit 42: Estimate of Number of Full-Time Engineers or Developers Employed by Organization
  • Exhibit 43: Estimated Percent of Organization's Full-Time Engineers/Developers Working in Specific Roles
  • Exhibit 44: Estimated Total Cost of Development for Current Project
  • Exhibit 45: Estimated Bill of Materials for Current Project
  • Exhibit 46: Estimated Units to be Shipped Per Year of Current Project
  • Exhibit 47: Estimated Percent of Engineering Tasks/Domains Development Costs Spent on Specific Tasks
  • Exhibit 48: Estimated Percent of Engineering Tasks/Domains Development Costs Expected to be Spent on Specific Tasks for a Similar Project Three Years From Now
  • Exhibit 49: Estimate of Fully-Loaded Labor Costs for a Typical Engineer Involved with IT/Enterprise/Embedded Systems
  • Exhibit 50: Estimation of Number of Defects Reported and/or Software Patches Required by Customer Per Year for Most Current Project
  • Exhibit 51: Estimated Total Combined Man-Hours of IT and Engineering Time Required for Each Patch or Defect Remediation
  • Exhibit 52: Estimated Percentage of Devices that Will Become Inoperable Each Year
  • Exhibit 53: Primary Method for Updating Devices Once Deployed in Field
  • Exhibit 54: Biggest Obstacle to the Development and Growth of the Connected Vehicle Industry
  • Exhibit 55: Level of Automation of Respondent's Current Vehicle/Component Work
  • Exhibit 56: Biggest Obstacle to the Development and Growth of the Autonomous Vehicle Industry
  • Exhibit 57: Current Major Competition to the Connected/Autonomous Car Space
  • Exhibit 58: Expected Major Competition Three Years From Now
  • Exhibit 59: Technologies Respondent's Organization is Most Interest in Investing In and/or Building for Future Customers
  • Exhibit 60: Types of Computer System Components or Sub-Systems Purchased by Respondent's Organization
  • Exhibit 61: Processing Unit(s) Used on Current Project
  • Exhibit 62: Processing Unit(s) Expected to Use on a Project Three Years From Now
  • Exhibit 63: Primary/Application Processor Used in Current Project
  • Exhibit 64: Processor Family/Architecture of Primary/Application Processor in Current Project
  • Exhibit 65: Other Processor Family/Architecture Considered for Current or Similar Project
  • Exhibit 66: Bit-Width of the Architecture Used by the Primary Application Processor Within Current Project
  • Exhibit 67: Bit-Width of the Architecture Used by the First Additional Processor Within Current Project
  • Exhibit 68: Bit-Width of the Architecture Used by the Second Additional Processor Within Current Project
  • Exhibit 69: Bit-Width of the Architecture Used by the Third Additional Processor Within Current Project
  • Exhibit 70: Most Important Characteristics When Choosing an Embedded Processor
  • Exhibit 71: CPU/MCU Suppliers for Current Project
  • Exhibit 72: MCU Suppliers for Current Project
  • Exhibit 73: SoC Suppliers for Current Project
  • Exhibit 74: ASIC Suppliers for Current Project
  • Exhibit 75: ASSP Suppliers for Current Project
  • Exhibit 76: FPGA/PLD Suppliers for Current Project
  • Exhibit 77: Rating of Experience with Embedded Processor Supplier
  • Exhibit 78: Likelihood of Using the Same Embedded Processor Vendor on a Similar Project Three Years From Now
  • Exhibit 79: Most Important Characteristics When Selecting the CPU Boards, Blades, and/or Modules in Organization's Product
  • Exhibit 80: Board/Module Architectures Currently Used by Respondent's Organization
  • Exhibit 81: Board/Module Architecture Expected to be Used by Respondent's Organization Three Years from Now
  • Exhibit 82: COM Form Factors Currently Used by Respondent's Organization
  • Exhibit 83: COM Form Factors Expected to be Used by Respondent's Organization Three Years From Now
  • Exhibit 84: Embedded Board and Module Vendors Being Used for Current Project
  • Exhibit 85: Level of Satisfaction with Embedded Board/Module Supplier
  • Exhibit 86: Likelihood of Using the Same Embedded Board/Module Vendor on a Similar Project Three Years From Now
  • Exhibit 87: Most Important Product Selection Criteria when Purchasing or Specifying Embedded Computing and/or Storage Systems, Aside From Cost
  • Exhibit 88: Architectures or Form Factors Currently Used in Embedded Computing Systems Purchased or Specified by Respondent's Organization
  • Exhibit 89: Architectures or Form Factors Expected to be Purchased by Respondent's Organization Three Years From Now
  • Exhibit 90: Motherboard Form Factor Class(es) Currently Used
  • Exhibit 91: Motherboard Form Factor Class(es) Expected to be Used Three Years From Now
  • Exhibit 92: Industrial Computer/PC (IPC) Form Factor(s) Currently Used
  • Exhibit 93: Industrial Computer/PC (IPC) Form Factor(s) Expected to be Used Three Years From Now
  • Exhibit 94: COM Form Factor(s) Currently Used
  • Exhibit 95: COM Form Factor(s) Expected to be Used Three Years From Now
  • Exhibit 96: Percentage of Total Third Party Platform Purchases Represented by Standard and Custom Suppliers
  • Exhibit 97: Embedded System Vendors Currently Purchasing From for Current Project
  • Exhibit 98: Embedded System Vendors That Have Been Considered/Evaluated for Current Project
  • Exhibit 99: Embedded System Vendors That Were Not Considered for Current Project
  • Exhibit 100: Satisfaction with Current Embedded System Supplier
  • Exhibit 101: Likelihood of Using the Same Embedded System on a Similar Project Three Years From Now
  • Exhibit 102: Wired Connections In Use or Expected from Products Built by Organization for Current Project
  • Exhibit 103: Wired Connections In Use or Expected from Products Built by Organization Three Years From Now
  • Exhibit 104: Wireless Connections In Use or Expected From Products Built by Company in Current Project
  • Exhibit 105: Wireless Connections In Use or Expected From Products Built by Company Three Years From Now
  • Exhibit 106: Current Low-Power Wide-Area-Network Protocols/Networks Used in Products Built by Organization
  • Exhibit 107: Low-Power Wide-Area-Network Protocols/Networks Expected to Be Used in Products Built by Organization Three Years From Now
  • Exhibit 108: Estimation of Data Gathered by Organization's Product Systems Each Day Per Unit/Device
  • Exhibit 109: Estimation of Data Gathered by Organization's Product Systems Each Day Per Unit/Device Three Years from Now
  • Exhibit 110: Communication Protocol(s) Used in Most Recent Project
  • Exhibit 111: Types of Devices/Systems to Which Current/Upcoming Project Will Connect
  • Exhibit 112: Percent of Overall Computation Being Done by Location of Computation
  • Exhibit 113: Primary Operating System Used on Current Project
  • Exhibit 114: Primary Operating System Used on Previous Project
  • Exhibit 115: Primary Operating System Expected to be Used in Three Years
  • Exhibit 116: Commercially Obtained, Non Open Source Operating System Used on Current Project
  • Exhibit 117: Commercially or Consortia Obtained Open Source Operating System Used on Current Project
  • Exhibit 118: Freely and/or Publicly Available, Open Source Operating System Used on Most Current Project
  • Exhibit 119: Chip/Board Vendor-Supplied Operating System Used on Current Project
  • Exhibit 120: Most Important Characteristics When Selecting the Primary Embedded Operating System for Current Project
  • Exhibit 121: Likelihood of Using the Same Operating System on a Similar Project Three Years From Now
  • Exhibit 122: Embedded Software Stack Components Required on Current/Most Recent Project, Other than the Operating System
  • Exhibit 123: Expectation of Embedded Software Stack Components Required on a Project Three Years From Now
  • Exhibit 124: Vendor Used for On-Device Analytics in Current Project
  • Exhibit 125: Vendor(s) or Technologies Used for Virtualization/Hypervisors In Current Project
  • Exhibit 126: Vendor(s) or Technologies Used for Containers/Orchestration In Current Project
  • Exhibit 127: Factors Driving Organization to Adopt Virtualization/Hypervisor Technology in Current Project
  • Exhibit 128: Factors Driving Organization to Adopt Container Technology in Current Project
  • Exhibit 129: Guest Operating System Used with Virtualization/Hypervisor in Current Project
  • Exhibit 130: Importance of Security to Current Project
  • Exhibit 131: Actions Respondent's Organization Has Taken in Response to Security Requirements
  • Exhibit 132: How Well Respondent's Organization has Addressed Security Requirements on Current Project
  • Exhibit 133: Most Important Reason Why Security is Not More Important to Respondent's Project
  • Exhibit 134: Does Respondent's Organization Offer a Program to Facilitate Reporting of Security Vulnerabilities Discovered by External Security Researchers (e.g. Bug Bounty)
  • Exhibit 135: Have Vulnerabilities or Security Failures Within Respondent's Organization Been Exposed or Identified Externally
  • Exhibit 136: Were Any Exposed Vulnerabilities Disclosed to Respondent's Organization's Customers
  • Exhibit 137: Effects of Exposed Vulnerabilities
  • Exhibit 138: Business Implications of Exposed Vulnerabilities
  • Exhibit 139: Commercial Embedded Security Solution Vendors Being Used on Current Project
  • Exhibit 140: Types of Embedded Security Software Solutions Included in Current/Most Recent Project
  • Exhibit 141: Types of Embedded Security Hardware Solutions Included in Current/Most Recent Project
  • Exhibit 142: Types of Embedded Security Hardware Solutions Expected to be Included in Project Three Years From Now
  • Exhibit 143: Does Current Project Use Any Local Network-Based Security Software or Products
  • Exhibit 144: Does Current Project Use Any Cloud-Based Security Services
  • Exhibit 145: Do Devices in Respondent's Current Project Contain Digital Certificates, Encryption Keys, or Encrypted Device IDs
  • Exhibit 146: Functions of Digital Certificates/Encryption Keys/Encrypted Device IDs
  • Exhibit 147: Where Digital Certificates/Encryption Keys/Encrypted Device IDs are Stored
  • Exhibit 148: How Digital Certificates are Provisioned
  • Exhibit 149: Certificate Authority (CA) Primarily Used to Issue Digital Certificates
  • Exhibit 150: Estimate of Cost of Digital Certificates Per Device
  • Exhibit 151: Types of Devices Currently Connected to Respondent's Organization's IT Network
  • Exhibit 152: Types of Devices Expected to be Connected to Respondent's Organization's IT Network Three Years From Now
  • Exhibit 153: Do Respondent's Organization's Current IT Security Policies Cover Smartphones
  • Exhibit 154: Do Respondent's Organization's Current IT Security Policies Cover Tablets
  • Exhibit 155: Do Respondent's Organization's Current IT Security Policies Cover HVAC Sensors, Controls, and/or Thermostats
  • Exhibit 156: Do Respondent's Organization's Current IT Security Policies Cover Lighting Control Systems
  • Exhibit 157: Do Respondent's Organization's Current IT Security Policies Cover Medical Monitoring Devices
  • Exhibit 158: Do Respondent's Organization's Current IT Security Policies Cover Medical Imaging Devices
  • Exhibit 159: Do Respondent's Organization's Current IT Security Policies Cover Security Systems
  • Exhibit 160: Do Respondent's Organization's Current IT Security Policies Cover Point-of-Sale Terminals
  • Exhibit 161: Do Respondent's Organization's Current IT Security Policies Cover Information Kiosks
  • Exhibit 162: Do Respondent's Organization's Current IT Security Policies Cover Set Top Boxes for Cable/Satellite TV
  • Exhibit 163: Do Respondent's Organization's Current IT Security Policies Cover Televisions
  • Exhibit 164: Do Respondent's Organization's Current IT Security Policies Cover Factory or Industrial Automation Equipment
  • Exhibit 165: Do Respondent's Organization's Current IT Security Policies Cover Asset Location Trackers
  • Exhibit 166: Do Respondent's Organization's Current IT Security Policies Cover Fleet Vehicles or Trucks
  • Exhibit 167: Do Respondent's Organization's Current IT Security Policies Cover Additional Devices other than Laptops, PCs, or Servers
  • Exhibit 168: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Smartphones
  • Exhibit 169: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Tablets
  • Exhibit 170: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover HVAC Sensors, Controls, and/or Thermostats
  • Exhibit 171: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Lighting Control Systems
  • Exhibit 172: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Medical Monitoring Devices
  • Exhibit 173: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Medical Imaging Devices
  • Exhibit 174: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Security Systems
  • Exhibit 175: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Point-of-Sale Terminals
  • Exhibit 176: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Information Kiosks
  • Exhibit 177: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Set Top Boxes for Cable/Satellite TV
  • Exhibit 178: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Televisions
  • Exhibit 179: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Factory or Industrial Automation Equipment
  • Exhibit 180: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Asset Location Trackers
  • Exhibit 181: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Cover Fleet Vehicles or Trucks
  • Exhibit 182: Has Respondent's Organization Enacted IT Security Policies Specifically Designed to Additional Devices other than Laptops, PCs, or Servers
  • Exhibit 183: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Smartphones Within the Next Three Years
  • Exhibit 184: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Tablets Within the Next Three Years
  • Exhibit 185: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover HVAC Sensors, Controls, and/or Thermostats Within the Next Three Years
  • Exhibit 186: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Lighting Control Systems Within the Next Three Years
  • Exhibit 187: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Medical Monitoring Devices Within the Next Three Years
  • Exhibit 188: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Medical Imaging Devices Within the Next Three Years
  • Exhibit 189: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Security Systems Within the Next Three Years
  • Exhibit 190: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Point-of-Sales Terminals Within the Next Three Years
  • Exhibit 191: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed Cover to Information Kiosks Within the Next Three Years
  • Exhibit 192: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed Cover to Set Top Boxes for Cable/Satellite TV Within the Next Three Years
  • Exhibit 193: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Televisions Within the Next Three Years
  • Exhibit 194: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Factory or Industrial Automation Equipment Within the Next Three Years
  • Exhibit 195: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Asset Location Trackers Within the Next Three Years
  • Exhibit 196: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Fleet Vehicles or Trucks Within the Next Three Years
  • Exhibit 197: Does Respondent Expect Organization Will Enact IT Security Policies Specifically Designed to Cover Additional Devices other than Laptops, PCs, or Servers Within the Next Three Years
  • Exhibit 198: Extent to Which Respondent's Organization Expect IT Security Vendors Will Provide Security Solutions for IoT Devices
  • Exhibit 199: Security Threats, other than Laptops/PCs and Servers, Respondent's are Concerned about for IoT Devices Connected to Organization's Network
  • Exhibit 200: IoT Devices Currently Create Security Risks for My Organization
  • Exhibit 201: IoT Devices Are Likely to Create Security Risks for My Organization Within the Next Three Years
  • Exhibit 202: My Organization Has Control Over What Specific IoT Devices Connect to Its Network
  • Exhibit 203: My Organization is Prepared to Manage Many Different Types of Connected IoT Devices
  • Exhibit 204: An IoT Device Security Failure Has Already Cost My Organization Money
  • Exhibit 205: Security Solutions Used to Protect IoT Devices Connected to Respondent's Organization's Network
  • Exhibit 206: Security Solutions Respondent Would Like to See Used to Protect IoT Devices Connected to Respondent's Organization's Network Three Years From Now
  • Exhibit 207: Vendors Supplying Commercial IT Security Products
  • Exhibit 208: Use of Security Solutions from IoT Specialists Vendors
  • Exhibit 209: Percent of Organization IT Budget Related to Security
  • Exhibit 210: Percent of Organization's IT Security Budget Attributed to Commercial Security Software/Services
  • Exhibit 211: Percent of Organization's IT Security Budget Expected to be Related to Security Three Years From Now
  • Exhibit 212: Person(s) Within Respondent's Organization Responsible for the Selection and Purchase of Enterprise Security Solutions
  • Exhibit 213: Types of Tools Used in Current/Most Recently Completed Project
  • Exhibit 214: Types of Tools Expected to be Used in Similar Project Three Years From Now
  • Exhibit 215: Most Important Characteristics When Selecting the Compiler Used on Current or Most Recent Project
  • Exhibit 216: Does Respondent's Engineering Organization Purchase Cross or Native Compliers
  • Exhibit 217: Type of Compilation Tool(s) Currently Used by Respondent
  • Exhibit 218: Type of Static Analysis or SAST Being Used on Current Project
  • Exhibit 219: Most Important Factors in Selection of Static Analysis or SAST Tools Being Used in Current Project
  • Exhibit 220: Typical Decision Maker for Purchase of Static Analysis or SAST Tools Used by Respondent and Engineering Team
  • Exhibit 221: Dynamic Testing or DAST Tools Being Used on Current Project
  • Exhibit 222: Most Important Factors in Selection of Dynamic Testing Tools Being Used in Current Project
  • Exhibit 223: Typical Decision Maker for Purchase of Dynamic Testing Tools Used by Respondent and Engineering Team
  • Exhibit 224: Requirements Management/Definition Tools Being Used on Current Project
  • Exhibit 225: Most Important Factors in Selection of Requirements Management/Definition Tools Being Used in Current Project
  • Exhibit 226: Typical Decision Maker for Purchase of Requirements Management/Definition Tools Used by Respondent and Engineering Team
  • Exhibit 227: Standard Language-Based Modeling Tools Being Used on Current Project
  • Exhibit 228: Most Important Factors in Selection of Standard Language-Based Modeling Tools Being Used in Current Project
  • Exhibit 229: Typical Decision Maker for Purchase of Standard Language-Based Testing Tools Used by Respondent and Engineering Team
  • Exhibit 230: Proprietary Language-Based Modeling Tools Being Used on Current Project
  • Exhibit 231: Most Important Factors in Selection of Proprietary Language-Based Modeling Tools Being Used in Current Project
  • Exhibit 232: Typical Decision Maker for Purchase of Proprietary Language-Based Software/System Modeling Tools Used by Respondent and Engineering Team
  • Exhibit 233: Release Management/Continuous Deployment Tools Being Used on Current Project
  • Exhibit 234: Most Important Factors in Selection of Release Management/Continuous Deployment Tools Being Used in Current Project
  • Exhibit 235: Typical Decision Maker for Purchase of Release Management/Continuous Deployment Tools Used by Respondent and Engineering Team
  • Exhibit 236: Software Composition Analysis (SCA)/IP Compliance Tools Being Used on Current Project
  • Exhibit 237: Most Important Factors in Selection of Software Composition Analysis (SCA)/IP Compliance Tools Being Used in Current Project
  • Exhibit 238: Typical Decision Maker for Purchase of Software Composition Analysis (SCA)/IP Compliance Tools Used by Respondent and Engineering Team
  • Exhibit 239: Organization's Linking System Requirements in Respondent's Current Project
  • Exhibit 240: Method and Time Respondent Validates Requirements - Peer reviews/Visual inspection
  • Exhibit 241: Method and Time Respondent Validates Requirements - Development of Use Cases
  • Exhibit 242: Method and Time Respondent Validates Requirements - Trade Studies
  • Exhibit 243: Method and Time Respondent Validates Requirements - Simulation
  • Exhibit 244: Method and Time Respondent Validates Requirements - Optimization
  • Exhibit 245: Method and Time Respondent Validates Requirements - Roll-up Analysis (e.g., size, weight, power)
  • Exhibit 246: Method and Time Respondent Validates Requirements - Formal methods (consistency, completeness, and correcteness)
  • Exhibit 247: Method and Time Respondent Validates Requirements - Other
  • Exhibit 248: Respondent's Description of Organization's Requirement Engineering
  • Exhibit 249: Has Respondent's Organization Investigated or Implemented Ways to Enhance Cross-Engineering Domain Integration Between Software/System Development (ALM), Mechanical Engineering/Product Lifecycle Management (PLM), and/or Electrical Engineering/Electronic Design Automation (EDA)
  • Exhibit 250: Greatest Advantages/Benefits of Cross-Engineering Domain Integrations
  • Exhibit 251: Has Respondent's Organization Investigated or Implemented Ways to Enhance the Delivery of Continuous Post-Deployment Content and Service Support
  • Exhibit 252: Budget for Development Tools Being Used on Current or Most Recent Project
  • Exhibit 253: Types of Prototyping Solutions on Current Project
  • Exhibit 254: Use of Own Prototyping Board or Commercial Solution on Most Recent Project
  • Exhibit 255: ASIC Gate Count of What Was Prototyped (ASIC Equivalent Gates)
  • Exhibit 256: FPGAs Used in Most Recent Prototype
  • Exhibit 257: FPGA Vendor(s) Used for Prototype Hardware on Most Recent Project
  • Exhibit 258: Rating of FPGA-Based Prototyping Challenges
  • Exhibit 259: FPGA-Based/Physical Prototyping Solution Currently Used
  • Exhibit 260: Type of Tasks in Which Virtual Prototyping Solutions are Used
  • Exhibit 261: Virtual Prototyping Solution(s) Currently Using
  • Exhibit 262: Most Important Characteristics When Selecting Virtual Prototyping Solution
  • Exhibit 263: Location of Vertical Prototype Creation
  • Exhibit 264: Language(s) Used to Develop Software for Previous Projects
  • Exhibit 265: Language(s) Used to Develop Software for Current Project
  • Exhibit 266: Language(s) Expected to be Used to Develop Software for a Similar Project in Three Years
  • Exhibit 267: Estimate of Total Source Lines of Code Required on Current or Most Recent Project
  • Exhibit 268: Percent of Total Software Code in Final Design of Current Project Coming From Various Origins
  • Exhibit 269: Expected Change to Amount of Software Content/Lines of Code on the Next Commercial Third-Party Software Project
  • Exhibit 270: Expected Change to Amount of Software Content/Lines of Code on the Next Open Source Third-Party Software Project
  • Exhibit 271: Expected Change to Amount of Software Content/Lines of Code on the Next In-House Developed Code Project
  • Exhibit 272: Expectation of the Percentage Increase of Software Content/Lines of Code for Commercial Third-Party Software
  • Exhibit 273: Expectation of the Percentage Increase of Software Content/Lines of Code for Open Source Third-Party Software
  • Exhibit 274: Expectation of the Percentage Increase of Software Content/Lines of Code for In-House Developed Code
  • Exhibit 275: Expectation of the Percentage Decrease of Software Content/Lines of Code for Commercial Third-Party Software
  • Exhibit 276: Expectation of the Percentage Decrease of Software Content/Lines of Code for Open Source Third-Party Software
  • Exhibit 277: Expectation of the Percentage Decrease of Software Content/Lines of Code for In-House Developed Code
  • Exhibit 278: Estimated Percent of In-House Developed Software Code for Current Project, by Origin
  • Exhibit 279: Software Design Methodologies Used on Current Project
  • Exhibit 280: Software Design Methodologies Expected to Use on Similar Project Three Years From Now
  • Exhibit 281: Adherence to CERT C Coding Standard in Current Project
  • Exhibit 282: Adherence to CERT C++ Coding Standard in Current Project
  • Exhibit 283: Adherence to CWE Coding Standard in Current Project
  • Exhibit 284: Adherence to HIC++ Coding Standard in Current Project
  • Exhibit 285: Adherence to MISRA C Coding Standard in Current Project
  • Exhibit 286: Adherence to MISRA C++ Coding Standard in Current Project
  • Exhibit 287: Adherence to JSF AV++ Coding Standard in Current Project
  • Exhibit 288: Adherence to In House/Internal Coding Standard Coding Standard in Current Project
  • Exhibit 289: Plans to Use IoT/Cloud Services to Build Projects
  • Exhibit 290: Use of Any IoT/Cloud Services to Connect, Manage, or Analyze Any of the IoT Devices on Networks Owned or Managed by Respondent's Organization
  • Exhibit 291: Ways IoT Most Impacts Respondent's Organization's Business Prospect. IoT Enables Organization to...
  • Exhibit 292: Primary Factor Driving Organization Towards Utilizing and/or Providing IoT Solutions
  • Exhibit 293: Biggest Overall Challenge in Developing IoT Solutions
  • Exhibit 294: Most Important Elements When Considering Suppliers for IoT Components and/or Entire Solutions
  • Exhibit 295: Types of IoT/Cloud Services Being Used to Support Customers on Current Project
  • Exhibit 296: Types of IoT/Cloud Services Planned to Use to Support Customers on a Project Three Years From Now
  • Exhibit 297: Estimated Total Annual Cost of Current IoT Connectivity Services to Respondents' Organization
  • Exhibit 298: Estimated Total Annual Cost of Current IoT Remote Monitoring and Control Services to Respondents' Organization
  • Exhibit 299: Estimated Total Annual Cost of Current IoT Data Collection and Storage Services to Respondents' Organization
  • Exhibit 300: Estimated Total Annual Cost of Data Analytics Services to Respondents' Organization
  • Exhibit 301: Estimated Total Annual Cost of Other Current IoT Services to Respondents' Organization
  • Exhibit 302: Types of Cloud Analytics Used to Analyze IoT Data on Current Project
  • Exhibit 303: Is Respondent's Organization Selling, or Planning to Resell Any Connectivity Services as a Value-Added Service to End Customers
  • Exhibit 304: Is Respondent's Organization Selling, or Planning to Resell Any Remote Monitoring and Control Services as a Value-Added Service to End Customers
  • Exhibit 305: Is Respondent's Organization Selling, or Planning to Resell Any Data Collection and Storage Services as a Value-Added Service to End Customers
  • Exhibit 306: Is Respondent's Organization Selling, or Planning to Resell Any Data Analytics Services as a Value-Added Service to End Customers
  • Exhibit 307: Is Respondent's Organization Selling, or Planning to Resell Any Other IoT/Cloud Services as a Value-Added Service to End Customers
  • Exhibit 308: IoT Cloud Platforms-as-a-Service (PaaS) Being Used on Current or Most Recent Project
  • Exhibit 309: IoT Cloud Platforms-as-a-Service (PaaS) Expected to Be Used on a Similar Project Three Years From Now
  • Exhibit 310: Cloud Services Used as a Part of IoT Cloud Platforms Currently Being Used in Project
  • Exhibit 311: Cloud Services Expected to be Used as a Part of IoT Cloud Platforms in a Similar Project Three Years From Now
  • Exhibit 312: Does Respondent's Company Currently Purchase or Create/Integrate Embedded Computer Hardware Products Considered to be Edge Gateway Devices?
  • Exhibit 313: Does Respondent's Company Plan to Purchase or Create/Integrate New or Additional Embedded Computer Hardware Products They Would Consider to be Edge Gateways in the Future?
  • Exhibit 314: How Respondent's Company Expects to Source its Gateway Technology
  • Exhibit 315: Approximate Number of Endpoints/Devices That Will Be Connected to the Edge Gateways Purchased/Used/Integrated by Respondent's Company
  • Exhibit 316: Most Important Product Requirements In Selecting Embedded Computer Products That Would Provide Connectivity at the Edge Gateway in the Equipment Used/Built/Integrated by Respondent's Company
  • Exhibit 317: Vendors Used for Analytics Solutions on Gateway Devices
  • Exhibit 318: Edge Gateway Hardware Suppliers Used with Current or Most Recent Project
  • Exhibit 319: Edge Gateway Hardware Suppliers Expected to be Used Three Years From Now
  • Exhibit 320: Use of Machine Learning/Neural Networks on Current and Future Projects
  • Exhibit 321: Source of Machine Learning Technology Used on Current Project
  • Exhibit 322: Source of Machine Learning Technology Expected Three Years From Now
  • Exhibit 323: Types of Machine Learning Currently Used
  • Exhibit 324: Types of Machine Learning Expected to be Used Three Years from Now
  • Exhibit 325: Where Current Machine Learning Models are Trained
  • Exhibit 326: Where Current Machine Learning Models are Expected to be Trained in Future Projects
  • Exhibit 327: Target Architecture(s) Used for Inferencing In Current Project
  • Exhibit 328: Target Architecture(s) Expected to be Used for Inferencing In Future Projects
  • Exhibit 329: Machine Learning Software/Analytics Vendor(s) Currently Used
  • Exhibit 330: Machine Learning Software/Analytics Vendor(s) Expected to be Used Three Years From Now
  • Exhibit 331: Most Important Elements When Considering ML Vendors/Integrators
  • Exhibit 332: Involvement in Machine Vision Software Development
  • Exhibit 333: Imaging System Type for Current Project with Machine Vision
  • Exhibit 334: AI/ML/Deep Learning Processing Requiremeent on Current Project with Machine Vision
  • Exhibit 335: Machine Vision Software Development Solutions Vendor(s) Currently Used
  • Exhibit 336: Likelihood of Using the Same Machine Vision Software Development Solutions Source on a Similar Project Three Years From Now
  • Exhibit 337: Most Important Characteristics When Choosing Machine Vision Software Development Solutions
  • Exhibit 338: Machine Vision Use Case(s)
  • Exhibit 339: Components of Imaging Process Addressed in Current Project
  • Exhibit 340: Primary Role Within Company/Organization
  • Exhibit 341: Respondent's Organization's Primary Industry
  • Exhibit 342: Total Number of Employees at Respondent's Organization