Software maturity levels can help improve software related processes

Ask Control Engineering: How can software maturity levels help improve software related processes?

By Mark T. Hoske December 28, 2014

Question for Control Engineering: Can software maturity levels help improve software-related processes?

Answer: Yes, and just because a software implementation has a low maturity level doesn’t mean that it is somehow inappropriate for an organization or a particular application. Not all software systems need to operate at the highest level. Maturity models help an organization understand how software development works and how sophisticated something needs to be for a particular use or application.

To use an analogy, not all bike rides require a high-performance racing bicycle with graphite frame and 100 psi racing tires; sometimes a coaster-brake single-speed bicycle will do.

A five-part Control Engineering article series from Corey Stefanczak, senior system architect, Leidos, explains how understanding software maturity models can help an organization can improve and increase efficiencies. The articles introduce the maturity model, look at how to take the first step, how to gain a competitive advantage, how to optimize resources, and how to develop a highly mature enterprise. Learn more and link to each article, below.

Part 1: Understand the maturity model to better manage, integrate plant floor, enterprise systems Control Engineering (CE), August issue, Inside Machines section, p. M1 

Part 2: Migrating toward enterprise information systems from Applied Automation (supplement to CE and Plant Engineering), October issue, p. A13 

Part 3: Gain a competitive advantage, meet the challenges of enterprise information systems CE Weekly News enewsletter, Nov. 25 

Part 4: Optimizing the climb up the enterprise information systems maturity model CE November issue, Technology Update, p. 34 

Part 5: Highly mature enterprise: Meet the challenges of enterprise information systems CE December issue, Inside Machine section, p. IM4.

– Mark T. Hoske, content manager, CFE Media, Control Engineering,

Author Bio: Mark Hoske has been Control Engineering editor/content manager since 1994 and in a leadership role since 1999, covering all major areas: control systems, networking and information systems, control equipment and energy, and system integration, everything that comprises or facilitates the control loop. He has been writing about technology since 1987, writing professionally since 1982, and has a Bachelor of Science in Journalism degree from UW-Madison.