The Challenges of Integrating a System Based on Commercial Components Dalia Pongratz Motorola NM MIL May 2009 Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009.
Preview This presentation is based on the book Building Systems from Commercial Components by Wallnau, Hissam and Seacord, published by the SEI in 2002 (ISBN 0 -201 -70064 -6) The purpose of the presentation: • Describe the main advantages and challenges – that the MSG MIL organization encounters in its integration activities – due to the significant dependency on commercial components • What the organization does to resolve the issues Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 2
A Brave New World or This is the World As It Is Now: The S/W Component Market (1 of 2) • The software component revolution – Software components have penetrated almost any area of S/W development – They are already altering the practice of S/W engineering • From custom-developed components to existing commercial ones • Examples: Web browsers, HTTP servers, object request brokers, relational database management systems, messageoriented middleware, public key infrastructure, transaction monitors, geographic information systems – Control has passed from the “software factory” to the market regime • Designers have less control over the architecture Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 3
A Brave New World or This is the World As It Is Now: The S/W Component Market (2 of 2) • The software component revolution – Is there a standard and well established process for developing systems that are constructed predominantly from COTS (commercial off the shelf) components? • There are processes in place, but: • They still focus on design as a process of component specification • Whereas it is becoming more a process of component selection – Which means a new class of design constraints Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 4
The MSG MIL Example: Product Definition through Component Selection • The Motorola cellular NM (network Management) product is heavily based on commercial and well established components: – Sun servers, disk arrays and operating systems – HP product for network element and agent tracking – IBM product for collecting, processing and interpreting network element performance data (PM) – Web cloud computing applications – Security – authentication, authorization and access control products – Geographic map products • The AEMS product specification is built around these components and using their terminology Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 5
Our Main NM Product: The AEMS The Advanced Element Management System (AEMS) is Motorola's advanced cellular networks management product, designated for Motorola's international networks markets. The product is aimed to provide network management services, including remote network device configuration and fault management, monitoring and maintenance functions. It is incorporated in Motorola's CDMA networks and is designed to provide core functionality to support future enhancements to further wireless networks technologies. In 2007 all the development has been transferred and assigned to MSG MIL, following very good performance and results of the organization. The AEMS product is comprised of features (functional and standard), some of which are managed by local MSG Israel staff. Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 6
The New Opportunities and Expertise Areas • Develop components (infrastructure, applications) • Develop component sub-assemblies • Expertise in integration of popular components – The new challenges may become new opportunities Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 7
The Main Challenges of Product Definition & Design Based on COTS S/W Components • Incomplete and sometimes incorrect understanding of the features, interfaces and behavior of commercial components • Migration between equivalent components made by different (and competing) vendors • Migration between different versions of a specific component – The compulsion to accept new component releases independent of the project plan • Component vendors tend to innovate and differentiate rather than stabilize and standardize Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 8
MSG MIL Mitigation of these Risks • Preserving our engineers and knowledge, in particular extensive experience with our product’s S/W components – Bugs and workaround – Performance – Avoiding risks • Decisions about migration to new vendors of integrated components are made as part of the system version definition, and are relatively rare – Only if the migration is unavoidable or has significant advantage • Migration between component releases is addressed and included in our SCM and build plans • Thorough testing of the commercial component behavior, as part of the MIL system – all levels, both “white” and “black box” Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 9
Classes of S/W Components • Operating System based vs. Framework based – OS-based: • Components that are deployed directly onto a native OS • Should comply with the interfaces & conventions of that OS, only – Framework based: • Deployed into a higher level environment (the Framework) • Need to be integrated with both the OS, the application components and with the custom-developed system • Infrastructure vs. application components – The infrastructure components are not always standard and do not always have common behavior – They too need to be integrated Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 10
Process Impact (1 of 4( • It is highly recommended to start from a spiral development paradigm – Considering the partial knowledge of the component behavior, and how they will behave in an integrated system – Considering the component release schedule which is not coordinated with our project schedule – An example: The IBM Rational RUP + UML When an angry congressman insisted that any general would be better than the one Lincoln had appointed, Lincoln said that he could not appoint any general, he had to appoint some general. • The architecture development process must accommodate the constraints imposed by the S/W components – Performance, reliability and security aspects Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 11
Motorola NM Drop Process Scheme Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 12
Process Impact (2 of 4( • Design for change – Market vendors create pressure to accommodate changes in the component features, interfaces and behavior – Ongoing upgrade and integration • Design the Supply Chain – Integration of the suppliers (when suppliers of parts are linked to suppliers of subassemblies of parts) Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 13
Process Impact (3 of 4( • Design in the face of misfit – A process of achieving fitness for use by removing misfit – The democracy of requirements underlie the market regime: • Vendors develop for many systems, not just ours! • A tough trade-off between component availability, quality and cost and its applicability to our product A S/W developer called an infrastructure product vendor and complained, that after spawning 200 threads the performance degrades considerably. The vendor system engineer answered: I didn’t even know that we can support 200 threads! • Integration misfit causes: – Architectural misfits (due to mismatched vendor assumptions about how their components would be integrated) – Vendors use idiosyncratic integration approaches to “lock in” their customers – Vendors prefer innovation to stability of interfaces Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 14
Process Impact (4 of 4( • Design to your developers’ technology competence – Expertise with popular and specific components becomes a major desirable developer’s skill – S/W components are complex as well as feature-rich – The accumulated developer knowledge in the organization is an important consideration and constraint for the system architect – Components change with each release, so the engineer competence with specific components must be continuously retained • Design as exploration – Learning about the components during the design process – Reduces design risks Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 15
The MSG MIL Example: Joint System Engineers & Dev Teams • Combined teams develop the product specification together • Prototyping as part of the product and requirements definition phase • Time must be allocated for self study and on the job training Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 16
Summary: The Process “Black Hole” • The Process compression: – Detailed knowledge about component implementation must shape the requirements – Knowing what to integrate depends on the requirements – So we have to make the requirements specification and the system integration at the same time! • Spiral development may help to do that without losing control • Shorter life cycle intervals – Strung back-to-back over the entire development effort • New component versions introduce a random element into the design, even after the product has been released – In fact, we may need to do all the life cycle phases at the same time, all the time! Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 17
Some Questions to take Home • Do S/W engineers that develop component-based systems have to be more skilled, as skilled or less skilled than engineers who develop custom systems? • Do you believe that a commercial market in standard, interchangeable software components is possible? If it is possible, what form would it take? • What effect would a component marketplace have on software engineering practices? Motorola Inc. LTD. All rights reserved. No part of this presentation may be copied or used without explicit permission by Motorola inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2009. May 2009 Page 18
Скачать презентацию The Challenges of Integrating a System Based on
4f4613c2f9359918c06d792f25ff3673.ppt