BIGLEVER NEWSLETTER: GearUP Announcement
Introducing Gears 7.4 with Selective Actuation
Greetings from Dr. Drew Stovall:
This month, BigLever Software is releasing Gears version 7.4. For all engineers working, every day, on engineering your product line's shared assets – this one is especially for you.
First, some background about Gears
In case you're not familiar with Gears... BigLever's Gears Product Line Engineering Tool and Lifecycle FrameworkTM allows you to define feature models for the products in your product line, bring in engineering assets for those products, and then actuate to automatically generate a product-specific set of those assets based on feature choices. Features are the distinguishing characteristics that set your products apart from each other. A feature profile describes a particular product by capturing the feature selections for that product. To generate a product, Gears uses that product's feature profile to configure the shared engineering assets you've hooked up to it -- such as requirements, design models, code, tests, documentation, plans, Bills of Materials, and so on. The result is a fully consistent set of asset instances configured to perfectly support the product to be produced, based on the feature profile you supplied.
The figure illustrates this, by showing four types of shared assets on the left, including requirements, design models, and so forth. (Click image to enlarge.) But, the possibilities go far beyond just those.
The shared assets on the left are "supersets," containing all of the information needed to support any product in the product line. Asset engineers – for example, requirements engineers, or coders, or testers – create and maintain the supersets. They build variation points (places where the shared asset needs to be different to support a particular feature), and write the Gears logic to exercise those variation points based on feature selections. Through Gears' many tool integrations, engineers work on the shared assets using the engineering lifecycle tool they're accustomed to – DOORS, for example, or Visual Studio, or Rational Quality Manager, or many more.
The Expanding Scale and Scope of Product Line Engineering
The capabilities in this new Gears release are motivated by the continually expanding scale and scope of product line engineering (PLE) that is now being adopted by customers in commercial practice. BigLever's PLE tools and methods are now being deployed broadly across the entire enterprise in some of the world's largest corporations, building some of the world's most complex products and systems.
In these settings, PLE is managing the complexity of crosscutting and interacting feature variations for as many as thousands of features, in hundreds of subsystems, for tools and assets in tens of different phases and organizations in the systems engineering lifecycle, comprising hundreds of thousands of variation points, supported by thousands of engineers, to produce product line portfolios with millions of products annually, often in safety critical domains.
For the individual engineers working in these mega-scale PLE environments, the ability to narrowly and clearly focus on a particular engineering task – isolated from the unrelated details from thousands of surrounding assets, tools, features, engineers, subsystems, and products – is key. Widely used systems engineering techniques for isolation, such as modularity and decomposition, apply equally well with PLE. However, the crosscutting nature of PLE requires special treatment, particularly in mega-scale PLE settings. For example, understanding and testing the implications of a single feature enhancement might involve variation points in requirements, architecture and design models, source code, build scripts, automated unit test scripts, parts bill-of-materials, integration and acceptance test cases, product documentation, manufacturing codes, sales configurator expressions, and more.
Individual engineers working on a particular engineering task are most efficient and effective when they have fine-grained control to focus on the PLE facets that interest them the most.
Now, there's Selective Actuation
Engineering a shared asset superset of any kind involves the edit-run-test cycle all engineers are familiar with. You add or modify variation points in the superset, write the logic for Gears to exercise them, ask Gears to produce a product-specific configuration, and validate the results.
In Gears 7.4, we've added Selective Actuation to keep this process as efficient as possible, particularly in mega-scale PLE settings. Selective Actuation lets you focus the Gears Actuator on specific assets. When you actuate a product, you can now select assets by type or by name, and Gears will actuate just those assets. Now you've got a focused, and faster, edit-run-test cycle geared exclusively to the shared assets you're working with.
Of course, it's your whole product line engineering team that is more focused. While you're working on, say, requirements… your colleagues are doing the same thing in code, testing, and user documentation, and enjoying the same kind of focus from Gears on what matters to them.
Selecting the Shared Assets
Let's take a closer look at Gears 7.4. The following screen shots provide a view into how Selective Activation works. (Click screenshots to enlarge.)
1: Actuate product dialog
2: Select by asset type
3: Select by asset name
4: Select by type and name
5: Select by type and production line
Selecting the shared assets to actuate is easy, and it's right there were you'd expect it – in the actuation dialog.
When selecting the product to actuate, just expand the options section to select the shared assets to actuate (1).
Asset types are listed on the left; specific assets and imported production lines are listed on the right. You can build your list by working on either side. For example, want to actuate just the DOORS data? You can select just the DOORS bridge on the left (2).
Want to actuate just your Code and Calibrations data? You can select just those assets on the right (3).
Want the DOORS modules and Code and Calibrations? No problem (4).
Want to actuate just the DOORS modules in just some of the imported production lines? Sure, you can do that too (5).
Want to actuate the same assets that you actuated last time? Gears will remember what you did last time and automatically selects those bridges and assets.
The reactuation capability in Gears has always provided quick updates to the projection of an asset for the latest product. Selective actuation complements reactuation to provide quick updates to the projection of any number of assets in any product. Quick updates means quicker testing and quicker results. The edit-run-test cycle has just sped up, you've just sped up, and that's a great thing.
If you would like more information about Gears 7.4, or to see a product demonstration, please contact us at firstname.lastname@example.org.
BigLever Software Vice President of Engineering
Don't miss your Newsletter!
Please help us make sure that you continue to receive the BigLever Newsletter by confirming your subscription with us. This ensures that future newsletters will be successfully delivered to your Inbox and not misplaced into your junk mail or spam folder. To confirm, simply click the "confirm" link in the white bar below. After confirming, you can unsubscribe from our newsletter distribution at any time.