FEATURED ARTICLES
FEATURED ARTICLES
Architecture Models as Enablers of Agility By Juan Navas
Architecture Models as Enablers of Agility by Juan Navas, Thales Corporate Engineering Email: juan.navas@thalesgroup.com Copyright ©2021 by Juan Navas. All rights reserved. Authored for PPI SyEN.
Based on the paper Models as enablers of agility in complex systems engineering presented at the INCOSE International Symposium 2020 by Juan Navas, Stephane Bonnet, Guillaume Journaux and Jean-Luc Voirin.
Abstract This series of articles follows the engineering teams of the PythaDrone project during their endeavor of developing a drone-based product that addresses multiple market segments. The focus is on the use of system architecture models as the basis for several technical, management and organizational activities, in a context in which a company implements agility in its engineering processes. Although the PythaDrone project and the Pythagoras company are fictive, the practices described here are those put in place in some of our projects and business units.
Episode 2 – Run! Previously on Episode 1 In Episode 1 of this series of articles, we introduced the fictive PythaDrone team in the also fictive Pythagoras company. The PythaDrone team is in charge of developing a lightweight drone-based product that will address different markets: agriculture, aircraft exterior inspection, and public security enforcement. The team is implementing both agility and MBSE practices in order to react faster to changes in the customers’ expectations and ensure the consistency of the design. We followed them through their initial “warm-up” activity, in which they built their engineering strategy and the first vision of their product. In this Episode 2 we will situate ourselves later in time, and we will focus on the Systems Architecture team while specifying a subset of the features to be developed in further iterations. Defining the scope of design for Iteration 3 The Architecture team has been releasing incremental versions of the product architecture at each product-level iteration (i.e. every 3 months). The project started 6 months ago and the team is preparing the third iteration at the product-level. Until now the design has been focused on the visualization capabilities of the product in order to get feedback on user experience (UX) as soon as possible from operators. The table below summarizes the progress status of design, development and test per capability.
12
[Contents]
PPI SyEN
