BEDIFFERENT A C E 2 0 1 2 I N T E R N A T I O N A L

BEDIFFERENT A C E 2 0 1 2 I N T E R N A T I O N A L

ACE 2012 I N TERNATIONAL Application Lifecycle Management Workshop Peter Schroer Aras Corp

COFES 2012 Marc Halpern (Gartner) Copyright 2012 Aras. All Rights Reserved. Slide 3 ALM and PLM: BFF? The design of software to be embedded in smart products has become too interdependent with the design of the product for ALM and PLM to remain completely independent of one another. On the other hand, the two domains have each have special needs that don t easily fit within the context of the other. So for the foreseeable future, ALM and PLM will have to walk hand-in-hand. What are the challenges in making that effective and as we look to the future, where should we focus our efforts?

Slide 4 Workshop Format 6 slides background information I ve collected Open discussion / brainstorming session on 4 topics: Source Code Vaulting IDE Integration Requirements Management / Systems Engineering Configuration Management Introductions

Slide 5 ALM Application Lifecycle Management For Software that is the product or goes into the product Firmware Application software Embedded Mechatronics context Not the internal IT applications Although the solution may be the same.

Slide 6 Why is ALM Important Lockheed F-22 Raptor = 1.7 million lines of code Lockheed F-35 Joint Strike Fighter = 5.7 million lines of code Boeing 787 Dreamliner = 6.5 million lines Today s Luxury Automobile 30-50+ chips >100 million lines of code sources spectrum.ieee.org/green-tech/advanced-cars/this-car-runs-on-code

ALM Current Solutions & Approaches Microsoft IBM-Rational Rally Open Source solutions (Git, Subversion, Bugzilla, ) Approaches: Focus is source code vaulting with very few features for ALM process and configuration management Hard-coded systems for small teams that lack the flexibility to adapt easily to user requirements, lack integration tools, and are not scalable for large, distributed enterprise projects Suite of point applications, not integrated approaches Designed for pure software company use cases, not mechatronics Copyright 2012 Aras. All Rights Reserved. Slide 7

Slide 8 Workshop Proposal Assume that ALM inside of PLM is the direction Single Configuration Management schema, but different behaviors and use cases for Mechanical, Electrical and Software content We ll talk about the data model, the process model, and the use cases. AND what do we integrate to or replace.

ALM Solution Functional Concept Rules Workflow Permissions Repository Copyright 2012 Aras. All Rights Reserved. Requirements Management Workflow Lifecycles Configuration Management Document and Specification Vaulting User and Access Rights Controls Project and Task Management Issue Tracking Collaboration / Social tools Use Case Management Test Case and Test Results Traceability Release Planning Source Code Vaulting? what did I miss? Slide 9

ALM Software Development Process Map Copyright 2012 Aras. All Rights Reserved. 10 Web Collaboration (Discussions, HelpDesk, Threads, Chat, Wiki, etc.) Mobile Collaboration (Discussions, HelpDesk, Threads, Chat, Wiki, etc.) Requirements Requirements Requirements Discussion, Thread Mgmt. Wiki Contents Management Issues Issues Issues Downloads Specification Specification Specifications Builds License Management Documents Release Plans Activities & Milestones Source Code Test Cases Dashboard & Reports Projects Management

Slide 11 Discussion Topic Source Code Vaulting Integrate Subversion CVS Git Replace Use PLM Vault? Practical? Realistic? Work-in-Process versus Released file vaulting

Slide 12 Discussion Topic IDE (development/authoring applications) Eclipse Visual Studio Integrate or Replace? Do we integrate in a similar way as Mechanical CAD? What functions?

Slide 13 Discussion Topic Requirements Management Is there a difference in RM data or processes? Software Mechanical Electronic Cable/Harness Complete System Modeling - Systems Engineering? Model-based engineering and simulation impact?

Slide 14 Discussion Topic Configuration Management Configuration Identification does S/W get a part #? Is S/W on the BOM? Do we need a vehicle configuration that includes S/W? How to handle the differences in Rate of Change? How to handle form-fit-function tier-up when software becomes significant to end-user operation, but changes so often?

Slide 15 Summary Next Steps? What s Aras doing? (Next slide) Do we create an ALM SIG?

Aras ALM Solution Approach Roadmap Standard- Available Now Community Available Now New in 2012 Release Planning & Management Change Management Visibility & Traceability (Dashboard & Report) Requirement Management Project Management Document Management Source code vaulting Subversion, Git, etc. Workflow Issue Tracking Lifecycle Specification version control IDE Test Case Management Visual Studio Eclipse Configuration Management Access Controls Agile Templates 2012 -> Standard (Aras Managed) Modules: Requirements Management with Use Case and Test Case Traceability Collaboration Tools 2012 -> Community Solutions Collaboration Tools (threads, discussions, chat, wiki) Aras ALM modules: Release Planning, Issue Tracking Git or Subversion Integration for source code vaulting Workflow and lifecycle templates for Agile methodology Visual Studio and/or Eclipse IDE plug-ins Copyright 2012 Aras. All Rights Reserved. Slide 16