You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.
The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.
For the reports in this repository we specifically note that
By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.
If you are in doubt, feel free to contact email@example.com
From enterprise systems to embedded systems, software is the key enabling force of today’s businesses. Although this fact is recognized by the current business and technology managers, the complexities that come along with software and tackling the related problems are hardly understood. This is mostly because software is “invisible” and the professional skills that are required to deal with complex software are generally unknown to the management. For this reason, software system development is largely considered as a bunch of coding activity plus some nasty process management. The businesses that are willing to apply the maturity models such as CMMI mainly focus on the processes without being conscious about the depth of the required solution techniques. The increased emphasis on architectures is mostly limited to considering the enabling technologies in system realization. On the other hand, the language of the researchers in computer science are unintelligible to the managers.
To address these challenges, we will first identify the so-called key quality and technology domains. Then we will introduce the concept of technology maturity models. A technology maturity model identifies the advancements an organization may master in due time within a key technology domain through adoption of increasingly more advanced and beneficial state-of-the-art and/or research-driven methods, techniques and tools. Technology maturity models are derived from the actual business needs through application of problem solving techniques. In this talk, we will give several examples in applying this approach to large industrial organizations.