The ERP Paradigm for ALM Environments

1
The ERP Paradigm for ALM Environments An
Experience Report Shai Koenig Comverse and The
Open University of Israel June 2008
2
The Challenge

• Development of large, long-life, complex,
  software-intensive products involves
• large numbers of knowledge workers,
  organizationally distributed and often
  geographically distributed
• performing a very large number of inter-related
  activities
• that create, store, organize, update, maintain
  and search large amounts of inter-related
  information of
• many information types
• over very long periods of time
• To do this more effectively we need our own
• industrial revolution tooling !!!

3
Terminology

• CASE Computer-Aided Software Engineering
• Tools
• used to support individual tasks
• Workbenches
• A collection of integrated tools that support a
  single software development activity or phase
• Environments IPSE, SEE, ALME
• provide highly integrated support for a
  wide-range of software development activities

from Fuggetta, A., A Classification of CASE
technology, IEEE Computer, December 1993.
4
Integration Dimensions
High
Organizational Integration
Low
Information, Functional Process Integration
High
5
Organizational Integration Dimension
But most existing tools are not enterprise
aware !
6
Information Dimension
3rd Party
Capabilities
Products and components
Requirements
Features
TestWare
Alarms
Releases
Defects
Development Requests
Limitations
Test Execution
Iterations
Encryption Schemes
Risks
Decisions
Customer Projects
Action Items
Events
Documents, Templates, URLs
Professional Services
Customers
Reviews Gates Meetings
7
Information Integration Needs
3rd Party
Capabilities
Requirements
Products and components
Features
Alarms
TestWare
Releases
Defects
Development Requests
Limitations
Test Execution
Iterations
Encryption Schemes
Risks
Decisions
Customer Projects
Action Items
Events
Documents, Templates, URLs
Professional Services
Customers
Reviews Gates Meetings
8
Mapping tools onto the integration matrix
.
.
High

• Where would you situate the following
• tools on the integration matrix?
• Tools
• Rational ClearQuest
• Rational Requisite Pro
• Rational TestManager
• Telelogic Synergy
• Telelogic Doors
• Borland Caliber
• Borland StarTeam
• UGS TeamCenter Systems Engineering
• Mercury Quality Center
• Action Base
• Documentum
• Live Link

.
.
Organizational Integration
.
.
.
Low
Information Functional Integration
High
9
Integration Matrix
.
.
High

• Where would you situate the following
• tools on the integration matrix?
• Tools
• Rational ClearQuest
• Rational Requisite Pro
• Rational TestManager
• Telelogic Synergy
• Telelogic Doors
• Borland Caliber
• Borland StarTeam
• UGS TeamCenter Systems Engineering
• Mercury Quality Center
• Action Base
• Documentum
• Live Link

We want to be here !!!
?
.
.
Organizational Integration
.
.
.
Low
Information Functional Integration
High
10
Is there a better way?
How do we get there ?
11
Alternatives
Solution Alternatives

• Individual tools
• Tower of Babel

12
Alternatives
Solution Alternatives

• Individual tools and tool-to-tool interfaces
• Ad-hoc, Still a Tower of Babel

13
Alternatives
Solution Alternatives

• Individual tools and tool-to-tool interfaces
• Tower of Babel
• Individual tools linked to an interfacing
  platform
• PCTE ISO/IEC and ECMA
• Eclipse Application Lifecycle Framework ALF
• Jazz IBM

14
Alternatives
Solution Alternatives

• Individual tools and tool-to-tool interfaces
• Ad-hoc, Tower of Babel
• Individual tools linked to an interfacing
  platform
• PCTE ISO/IEC and ECMA
• Eclipse Application Lifecycle Framework ALF
• Jazz IBM
• Integrated Knowledge Mgmt Environment The ERP
  Paradigm
• Single, information modl and repository
• Consistent presentation model
• Unified process workflows
• Standard information linking
• Multiple view support

15
Alternatives
Solution Alternatives
The ERP Paradigm for App Lifecycle Mgmt Envs

• Examples
• VSTS Visual Studio Team System MS
• Rally Software oriented to agile development
• Qpack Orcanus
• DiME proprietary system

DiME
16
DiME - integration of product definition,
development delivery processes and information!

• DiME is an evolving
• Integrated,
• Collaborative,
• Enterprise-wide
• environment for managing the
• Processes and
• Information
• of product
• Definition,
• Development and
• Delivery

• Integration
• Information
• Application
• Processes
• Organization
• User Interface

DiME
17
DiME User Communities
CFG Project Management
RD Project Management
Testing
DiME
Professional Services
Development
System Engineering
Customization Engineering
Product Management
Release Management
18
DiME Capabilities
DiME Capabilities

• Application Capabilities
• Product Tree management
• Release mgmt
• Iteration mgmt
• Limitations mgmt
• Security mgmt
• Alarm mgmt
• Gates Review mgmt
• Feature/Service mgmt
• Development management
• Document management
• Requirements management
• Test management
• Customer Project mgmt
• Professional Services mgmt
• Risk management
• Knowledge management

• Interfaces
• Business Intelligence
• Harvest / ClearCase
• ClearQuest / IDTS
• PRS-D
• Customer ERP
• Projects ERP
• Users Active Dir
• CQS
• Pipeline
• PDM
• CRM
• MS Project

• Generic Capabilities
• Workflow
• Notification
• Authorization
• Built-in Test
• Document Generation
• Queries and Reports
• Task-based UI
• Metrics
• Alerts and Reminders
• Attention Requests
• Favorites
• Audit History
• Off-line updates
• Importing data

19
DiME Production Environment Architecture
DiME Computing Architecture
User
DiME Terminal Server
DiME Web Server
DiME Terminal Server
DiME Web Server
DiME Web Server
DiME Terminal Server
20
Integration Matrix
.
.
High

• Where would you situate the following
• tools on the integration matrix?
• Tools
• Rational ClearQuest
• Rational Requisite Pro
• Rational TestManager
• Telelogic Synergy
• Telelogic Doors
• Borland Caliber
• Borland StarTeam
• UGS TeamCenter Systems Engineering
• Mercury Quality Center
• Action Base
• Documentum
• Live Link

DiME
.
.
Organizational Integration
.
.
.
Low
Information Functional Integration
High
21
Evolution of DiME

• DiME has been evolving within Comverse since
  2001
• It is based on SmarTeam of Dassault Systems
  which is used as a Fourth Generation Language
• It is widely used within Comverse
• It supports various usage patterns

22
Usage Statistics
23

• For a closer look join us later for a Demo
• Thank You !!!