Industry Thought Leaders to Keynote at SEPG Asia-Pacific

The SEI is proud and excited to have some of the industry’s most influential thought leaders keynoting at the first SEPG Asia-Pacific conference, September 16 -18 in Osaka, Japan. The keynote speakers will share successes and lessons learned, tell their own unique stories about their own performance improvement journeys, and inspire us all to be leaders and innovators in our field.

Paul Nielsen, Software Engineering Institute

Nielsen will talk about the new approaches in process improvement that the SEI is developing and leveraging to work together with existing models. This exciting evolution includes a new SEI Resiliency Management Model (RMM), which provides a comprehensive roadmap that enables organizations of all sizes to establish, manage, and evaluate operational resiliency, and encompasses both security and business continuity. It also includes a new addition to the CMMI family: CMMI for Services (SVC). CMMI-SVC joins the SEI People Capability Maturity Model (P-CMM), the Team Software Process (TSP), and the other CMMI best practice models for Acquisition and Development. The SEI is also the steward of the Smart Grid Maturity Model. Originally developed by IBM, the SEI is developing and expanding the model which aims to use digital technology to modernize the power grid. Nielsen will discuss how these complementary models support the key idea that software must be developed with quality principles while using the appropriate process improvement practices to help increase business continuity, reduce risk, increase security, and deliver better products and services. Read his full abstract and bio.

Yoshiaki Kushiki, Panasonic Corporation

Kushiki will discuss the future of embedded software. Japan is one of the biggest embedded software industry countries. Embedded software is used in almost all of consumer electronics and automotive systems. The digital revolution changed embedded software in the 1990s, and the network revolution changed it again after 2000. Now, consumer electronics face the new big revolution of energy saving and resource saving. Kushiki advocates that the methodology for embedded software has to take into consideration not only CE inside requirements but the environment and regulations surrounding CE, such as CO2 reduction, universal design, safety and reliability, power and cost saving, personalization for each customer, and linking with heterogeneous networks. In the 21st century, the embedded software of CE should not be called "Embedded" but "Environmental." Read his full abstract and bio.

Mario Tokoro, Sony Computer Science Laboratories, Inc.

Tokoro will discuss dependability of a huge and complex software system. According to Tokoro, we are facing two kinds of complexities, which lead to uncertainty and unpredictability in huge and complex software systems. One is internal, such as that caused by programming errors and incomplete specifications resulting in inconsistency between the designer’s intention and specification of a system and between the specification and implementation of the system. The other is external, such as that caused by improper operations, unexpected use, and attacks across networks. When a system is distributed over networks, we cannot know the entire structure and behaviors of the system at any instant. Thus, we cannot take the external observers’ view, and therefore the reductionist approach, to a huge and complex software system. Instead, we need to treat such a system as an open system, to which we can only take the internal observers’ view. Read his full abstract and bio.

Natarajan Chandrasekaran, Tata Consultancy Services Limited

Natarajan Chandrasekaran (Chandra) will focus on a key question: “How can certainty be an element in the design of business, products, and IT?” Ritualizing of quality has led to a gap between quality of experience and quality of service. Customers judge the quality of our products and services using a more holistic set of parameters than the ones used in our internal systems. Designing for certainty means changing the way we build our systems for First Time Right and delivering the same to customers with high levels of customer satisfaction. Quality must also encompass the way we interact with our customers to deliver what we build. Read his full abstract and bio.