Software Architecture in Practice RiSE’s Seminars Bass’s book :: Chapter 15 Ana Paula Cavalcanti December 5, 2018

Summary CelsiusTech: A Case Study in Product Line Development (Chapter 15) Relationship to the Architecture Business Cycle Requirements and Quality Architectural Solution Conclusion December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle CelsiusTech:: Leading supplier of command-and-control systems Composed of: CelsiusTech Systems, CelsiusTech Eletronics, CelsiusTech IT The ship System 2000 Naval Product Line Integrated system that unifies all weapons, command-and-control and communications systems on warship Production of a wide variety of naval systems (surface and submarine) Economics of Product Lines December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle ships A B C D E F G   1986 1988 1990 1992 1994 1996 Shrinking schedules December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle Code Re-use Using Core assets to expand the Business Area Takes advantage of the architecture and other core assets A successful product line organization considers its business to be the care, nurturing, and growth of its software product line, singular, particularly its core asset base. An important point is what a successful product line organization can do, at the enterprise level, with this powerful capability. That is, an articulated definition of what systems are within the product line’s capability to build. December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle Motivation… Everything was new (time of high technology flux) Analysis of the business context Ownerships changes Necessity to change organization by circumstances:: award of 2 naval contracts Technology changes:: maturation {Increased the time required to create product line but up to 1/3 of its initial technology investment was spent building assets that can now be purchased commercially.} December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle CelsiusTech’s Organizational Structure 1980-1985 Family Manager Command and Control Tracking Communications Operator’s Console Base System Integration Functional Areas Each functional area was led by a project manager December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle Architecture Team Costumer Project Management Integration and CM Team Program Manager Marketing C3 HCI Weapons Fundamental Services CelsiusTech’s Organizational Structure 1987-1991 Product Line Software Development Teams December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle CelsiusTech’s Organizational Structure 1987-1991 Strong management team focused on product line The success of a product line hinged on a stable yet flexible architecture Architecture team was responsible for the initial development and continued ownership and control of the product line architecture Project staffing levels ranged from an initial 20 to 30 to a peak of more than 200. December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle CelsiusTech’s Organizational Structure 1992-1998 Research and Development Group Technical Steering Group System Definition Naval Business Unit Development C2 Weapons HCI Global resources to All Business Units Air Defense Business Unit December 5, 2018

Relationship to the Architecture Business Cycle CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Relationship to the Architecture Business Cycle CelsiusTech’s Organizational Structure 1992-1998 Emphasis increasingly shifted from the development of the architecture and product line elements to the composition of new customer systems from the product line. Increased the size and responsibilities of the customer project management group. Staffing  fewer designers, developers and integrators. December 5, 2018

Requirements and Quality CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Requirements and Quality For new products to be derived from an organizational repository, they must be structured so that they can share modules. There must be a standard set of modules. Primary purpose of an architecture: Achieve a system that meets its behavioral and quality requirements: Performance Modifiability Safety, reliability and availability Testability December 5, 2018

Architectural Solution CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Architectural Solution Process View How distribution was accomplished Layered View Discussing how Ship System 2000 achieves a separation of concerns Module Decomposition View Show assignment of responsibilities to different large-scale elements of the system December 5, 2018

CelsiusTech: A Case Study in Product Line Development :: Chapter 15 Conclusion CelsiusTech evolved from a defense contractor providing custom-engineered point solutions to essentially a vendor of commercial off-the-shelf naval systems Architecture served as the foundation of the approach {technically and culturally} and for a long-term development effort. Full support of project management Architectures team’s authority December 5, 2018

References BASS, L.; CLEMENTS, P.; KAZMAN, R. Software Architecture in Practice. Addison-Wesley, 2003. CLEMENTS, P.; NOTHROP, L. Software Product Lines – Practice and Patterns. Addison-Wesley, 2002. December 5, 2018