This document summarizes a workshop on application lifecycle management (ALM) and how it can be integrated with product lifecycle management (PLM). The workshop discusses challenges with current ALM solutions, proposes using a single PLM system for configuration management of both mechanical and software content. Key topics discussed include source code vaulting, integrating development tools, requirements management for different content types, and configuration management challenges with fast changing software. Next steps proposed include creating an ALM special interest group and developing Aras' ALM solution to address these challenges.

1. BEDIFFERENT ACE 2012 I NTERNATI O NAL
Copyright © 2012 Aras. All Rights Reserved. aras.com

2. ACE 2012
INTERNATIONAL
Application Lifecycle Management
Workshop
Peter Schroer
Aras Corp
Copyright © 2012 Aras. All Rights Reserved. aras.com

3. COFES – 2012
Marc Halpern (Gartner)
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?
Copyright © 2012 Aras. All Rights Reserved. Slide 3 aras.com

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
Copyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com

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….
Copyright © 2012 Aras. All Rights Reserved. Slide 5 aras.com

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
Copyright © 2012 Aras. All Rights Reserved. Slide 6 aras.com

7. 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 aras.com

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.
Copyright © 2012 Aras. All Rights Reserved. Slide 8 aras.com

9. ALM
Solution Functional Concept
 Requirements Management
 Workflow
 Lifecycles
Rules
 Configuration Management
Workflow
Permissions  Document and Specification Vaulting
Repository
 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 ?
Copyright © 2012 Aras. All Rights Reserved. Slide 9 aras.com

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

11. Discussion Topic
Source Code Vaulting
 Integrate
• Subversion
• CVS
• Git
•…
 Replace
• Use PLM Vault? Practical? Realistic?
 Work-in-Process versus Released file vaulting
Copyright © 2012 Aras. All Rights Reserved. Slide 11 aras.com

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?
Copyright © 2012 Aras. All Rights Reserved. Slide 12 aras.com

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?
Copyright © 2012 Aras. All Rights Reserved. Slide 13 aras.com

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?
Copyright © 2012 Aras. All Rights Reserved. Slide 14 aras.com

15. Summary
Next Steps?
 What’s Aras doing? (Next slide)
Do we create an ALM SIG?
Copyright © 2012 Aras. All Rights Reserved. Slide 15 aras.com

16. Aras ALM Solution Approach
Roadmap
Standard- Available Now
Visibility & Traceability (Dashboard & Report)
Community – Available Now
Subversion,
New in 2012
Release Planning & Requirement
Document Management Git,
Management Management
etc.
Change Project Source code
Management Management vaulting
Workflow Lifecycle IDE
Visual Studio
Specification version Test Case Eclipse
Issue Tracking
control Management
Configuration
Access Controls Agile Templates
Management
Collaboration Tools (threads, discussions, chat, wiki)
2012 -> Standard (Aras Managed) Modules:
 Requirements Management with Use Case and Test Case Traceability
 Collaboration Tools
2012 -> Community Solutions
 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 aras.com