Cover Image
市場調查報告書

持續的系統工程及DevOps

Continuous Systems Engineering & DevOps

出版商 VDC Research Group, Inc. 商品編碼 324618
出版日期 內容資訊 英文 23 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
持續的系統工程及DevOps Continuous Systems Engineering & DevOps
出版日期: 2015年01月23日 內容資訊: 英文 23 Pages
簡介

本報告提供內建式及物聯網 (IoT) 市場上持續的系統工程及DevOps相關研究、市場概要及軟體開發的IoT的影響等分析。

摘要整理

  • 主要調查結果

全球市場概要、預測

  • 持續增多的內建式開發的課題
  • 協同軟體的開發
  • 十字網域整合及DevOps
  • 外部軟體編碼來源的利用增加,擴大品質、安全的疑慮
  • 持續的工程方法

軟體開發的IoT的影響

  • 影響IoT的商務計劃
  • 軟體功能性,促進開發成本及變化
  • 支付高級費用的客戶期待加值服務
  • IoT資料使服務擴大成為可能

附表

目錄

New engineering processes and preferences are emerging and evolving at an unprecedented rate in the embedded and Internet of Things (IoT) marketplace. Ecosystem participants are assessing these trends and adjusting product, marketing, and partnership strategies to avoid losing position in the rapidly shifting value chain. Many OEMs have begun adopting more collaborative approaches such as Agile and DevOps to accelerate time to market. They are now exploring productivity resources, like software code from third parties, and realigning their engineering organizations to promote collaboration and gain synergies across functional groups (i.e. software, mechanical, and electrical). As more devices become interconnected, these organizations must continue to adjust course, adapting their development processes to support the continual delivery of post-deployment content and services and to use information aggregated through the IoT to guide the formation of next-generation product strategies.

What questions are addressed ?

  • How should suppliers of software and systems lifecycle management (SSLM) tools respond to interest in continuous systems engineering?
  • How is the increased use of third-party code sources impacting the SSLM solutions market?
  • Will OEMs' interest in integrating across their engineering teams finally translate into substantial commercial spending?
  • How will systems engineering firms respond to security and IP concerns relating to third-party-sourced software code?
  • How is the growing use of third-party code sources impacting test tool use?
  • Which tool types are embedded engineers increasing adopting in support of their more collaborative engineering practices?

Executive Summary

Embedded engineering organizations' schedule and budget pressures continue to mount, challenging companies to more rapidly deliver innovative new products or services while still controlling costs. More collaborative practices such as Agile and integration across software, mechanical, and electrical engineering groups (i.e. cross-engineering domain integration) have gained broader acceptance as effective strategies to improve the pace and accuracy of software development in the embedded domain. After witnessing the benefits of the improved collaboration and communication that are central to iterative software development methodologies, many embedded engineering companies are trying to expand these principles to more of their organization and processes. DevOps is a more holistic approach to system lifecycle management that extends collaboration beyond development into QA and operations. DevOps provides engineering teams with insight into the actions and requirements of adjacent groups by broadening the principles of Agile and cross-engineering domain integration to include the full system design/test/deliver lifecycle. A continuous engineering approach further extends collaborative practices, integrating development, manufacturing, operations, and services - establishing full round-trip system lifecycle management capabilities

[Data available in full report.]

Key Findings

  • Embedded engineering organizations need to find new efficiencies, as expected code base growth (XX.X%) far outpaces the projected headcount growth of software engineers (X.X% CAGR through 2016).
  • Embedded engineers surveyed in 2014 reported XX.X% of their current code base was from third-party sources. Commercial and open-source third-party code will grow both in volume and in percentage of the overall embedded code bases as system complexity advances.
  • The growing use of software code from commercial third parties, which is sometimes delivered only in binary form, is expected to drive an increase in binary analysis testing tools such as those offered by Veracode, GrammaTech, and others.
  • The Internet of Things (IoT) is encouraging OEMs to deliver more services after product delivery. The investigation of business models with more service offerings should benefit tool suppliers, such as PTC, that include service delivery support within their portfolios of lifecycle management tools.
  • A trend toward a more continuously collaborative approach to systems development is accelerating demand for software and systems lifecycle management tools. A linked data architecture, such as outlined by the Open Service for Lifecycle Collaboration (OSLC), will be a critical enabler to help facilitate the data sharing needed for continuous engineering.

Global Market Overview

Exhibit 1:
Adoption of IoT/M2M Capability and Applications by Vertical Market
(Percent of Respondents)

Embedded Development Challenges Continue to Mount

Time-to-market and budget pressures continue to rise unabated across the embedded industries, making it more difficult for companies to rapidly deliver innovative new products or services while still controlling costs. Challenges commonly facing engineering organizations include complex hardware architectures, distributed development teams, highly integrated component functionality, and code bases that can exceed tens of millions of lines. Now, the advance of the Internet of Things (IoT) is driving requirements for a flood of new, intelligent devices that can provide ubiquitous connectivity and real-time contextual computation.

OEMs are increasingly turning to the software domain to address their market challenges and to serve as the primary vehicle for embedded device differentiation.

Consequently, software is also becoming a leading labor cost center for many embedded engineering organizations. In VDC's 2014 Software and System Development Survey, embedded engineers reported software delivered an average of XX.X% of end product value and accounted for XX.X% of their project's development budget.

Despite the increased focus and expenditures devoted to software, embedded engineering teams are still struggling with on-time project completion. In 2014, XX.X% of embedded engineers reported their current projects were behind schedule. To help improve on-time schedule performance and meet their growing software content creation demands, engineering organizations are modifying their staffing practices. The pace of software engineer hiring has accelerated and is projected to increase at a compound annual growth rate (CAGR) of X.X% through 2016. This expansion is expected to outpace the overall growth of the embedded engineering population (X.X% CAGR through 2016). However, VDC's research indicates the strain on software development resources will continue to intensify.

The demand for new software engineers could outstrip market supply and result in a financial premium being placed on the limited software engineer resources. Furthermore, the accelerated rate of software engineer hiring still trails the expected code base growth. Embedded engineers surveyed by VDC in 2014 expect a code base increase of XX.X% on their next project. Interest in developing products for the Internet of Things (IoT) and the related requirement for increased device connectivity adds further challenges. As a consequence, embedded firms need to reassess current practices and resource utilization plans to find new ways to improve the accuracy and efficiency of existing engineering teams.

Revised staffing strategies and the adoption of newer development practices offer some potential for lessening the gulf between embedded engineering organizations' software design demands and their production capabilities. However, the pace at which software-driven device functionality is growing necessitates that the contributions from all software sources accelerate. A resultant rise in associated development costs and persistent schedule challenges reinforce the need for embedded organizations to find new efficiencies.

It is becoming increasingly clear that embedded development teams cannot keep up with the accelerated pace of change by continuing to make incremental process improvements. Their necessary, fundamental changes will augment the demand for commercial development tools and additional services from suppliers of lifecycle management solutions.

Collaborative Software Development

The use of software development practices that incorporate more collaboration is among the primary strategies engineering teams are now exploring for improving the velocity and quality of software design. Many embedded organizations have determined serial software development practices, such as waterfall and the traditional V-model, are overly rigid, inefficient, and cannot scale to meet their needs. These organizations are increasingly turning to iterative methodologies; in 2014, XX.X% of embedded engineers reported practicing some form of Agile development on their current project.

XX Commercial in Confidence.

Table of Contents

Executive Summary

  • Key Findings

Global Market Overview

  • Exhibit 1: Adoption of IoT/M2M Capability and Applications by Vertical Market (Percent of Respondents)
  • Embedded Development Challenges Continue to Mount
  • Collaborative Software Development
    • Exhibit 2: Embedded Schedule Performance by Use of Agile
    • Exhibit 3: Distribution of Embedded End Product/Project Value by Domain
  • Cross-Domain Integration and DevOps
    • Exhibit 4: Biggest Advantages of Cross-Domain Integration
    • Exhibit 5: Level of Cross-Engineering Domain Integration by Vertical Market
    • Exhibit 6: SSLM Tool Use in Embedded, by Level of Cross-Domain Engineering Integration
  • Increased Use of Outside Software Code Sources Raises Quality and Security Concerns
    • Exhibit 7: Importance of Security on Current Project
    • Exhibit 8: Distribution of Software Code on Current Project, by Origin
  • Continuous Engineering Approach
    • Exhibit 9: SSLM Tool Use in Embedded, by Level of Post-Deployment Delivery of Content/Services

IoT Impacts on Software Development

  • Business Plan Impact of the IoT
    • Exhibit 10: Biggest Impact of IoT/M2M on Business Models
  • Software is Driving Functionality, Development Costs, and Change
    • Exhibit 11: Distribution of Embedded End Product/Project Value by Domain, Segmented by Vertical
  • Customers Paying a Premium Price Expect a Premium Service
    • Exhibit 12: Investigation of Continuous Post-Deployment Content Delivery and Services Support
    • Exhibit 13: Entity Most Responsible for Firmware/Software Updates to Deployed Services
  • IoT Data Enables Services Expansion

Additional Exhibits

  • Exhibit 14: Importance to Organization of IoT/Cloud Data Gathered for Product Development Improvement (Percent of Respondents)
  • Exhibit 15: Tool Use Rates, by Investigation of Cross-Domain Engineering Integration (Percent of Respondents)
  • Exhibit 16: Tool Use Rates, by Investigation of Post-Deployment Delivery of Content/Services (Percent of Respondents)
  • Exhibit 17: Biggest Impact of IoT/M2M on Business Models, by Vertical Market (Percent of Respondents)
Back to Top