Using Telelogic DOORS and Microsoft Visio to Model and Visualize

Home , IDEF, Telelogic

Using DOORS & Visio to Model and Visualize Complex Business Processes

Bob Sherman - [email protected] [email protected]

1 © Telelogic AB Agenda

• The Unmet Need

• The Solution

– Strategy: Business Driven Application Lifecycle

– Tactics: Business Modeling via DOORS & VISIO

– Tactics: DOORS/VISIO Integration

• Case Study Results

2 © Telelogic AB Chronic IT Project Problems

Top IT Project Problems • User/Stakeholder Engagement Outages • Unclear Objectives • Incomplete or Changing Requirements

*Standish Group Chaos Studies

3 © Telelogic AB Chronic IT Project Problems

Rework • 35-65% of project budget

*Standish Group spent on rework. • ~50% of rework is due to requirements errors

* IEEE & University of Southern California

4 © Telelogic AB Today’s Popular Methods Are Not Helping

CURRENT SITUATION WHAT IS NEEDED

• Focus is on the • Business focus software/system

• Emphasis on documentation • Rapid acquisition, vetting and ceremony and syntax exploitation of knowledge

• Standardization on methods • Innovative modeling and that have not yet solved the analysis techniques most critical IT project problems

5 © Telelogic AB It Won’t Fix Itself

• The method gurus rose to prominence in an era of small systems – gurus no longer on the front lines of the enterprise – gurus are pushing for standardization… slowing required evolution (or revolution) • Developers are in charge of method evolution – continued system vs. business centered focus – continued movement towards starting coding ASAP – increasing method/cultural emphasis on “embracing change” vs. getting it right the first time

6 © Telelogic AB If not addressed… the situation will worsen

• Foundational role of information systems in today’s business processes

• Increasing emphasis on the enterprise vs. the user

• Increasing number & complexity of technologies

• Shrinking the software project ROI window

7 © Telelogic AB Agenda

• The Unmet Need

• The Solution

– Strategy: Business Driven Application Lifecycle

– Tactics: Business Modeling via DOORS & VISIO

– Tactics: DOORS/VISIO Integration

• Case Study Results

8 © Telelogic AB We Have the Skills to Improve

AAMMRR --JJaann 22000033…… ““WWhhiillee mmoosstt ooff IITT’’ss eeffffoorrtt ggooeess ttoo ddeelliivveerriinngg ssoopphhiissttiiccaatteedd aapppplliiccaattiioonnss ffoorr tthheeiirr LLOOBB ccoouunntteerrppaarrttss,, mmoosstt IITT oorrggaanniizzaattiioonnss nneevveerr llooookk ttoo iimmpplleemmeenntt ssiimmiillaarr tteecchhnnoollooggiieess ttoo ssuuppppoorrtt tthheeiirr oowwnn ooppeerraattiioonnss..””

9 © Telelogic AB Strategy vs. What’s Needed

WHAT IS NEEDED STRATEGY • Business focus • Establish a business modeling framework and trace system requirements to the business model • Rapid acquisition, vetting and exploitation • Choose clarity over of knowledge elegance

• Text vs. syntax heavy, visual modeling

• Innovative modeling • Tabular and graphical and analysis techniques analysis

10 © Telelogic AB Business Driven Application Lifecycle (BDAL)

STRATEGY DEVELOPMENT & DEPLOYMENT

PORTFOLIO MANAGEMENT

Business Model

Zachman Project Management Requirements Master Planning & e L m le Architecture M re gi U t A eX Solution

Testing

11 © Telelogic AB BDAL Framework

Strategy Development & Objectives Strategies Deployment Goals Measures

Business Business Project Model Model Business Change Scenarios Objectives Methods Goals

Work Policies Regulations Strategies Processes Measures Data Representations Roles Data Automation Elements Objectives

Requirements

12 Initiative Scenario © Telelogic AB Application vs. Business Perspective

BUSINESS …B……S…-…1….. …B……S……-2….. BS-3 WORK ………… ………… ……………….. ……….. ……….. ………… SCENARIOS ……… ……… ……….. PROCESSES ……… ……… ……… ………

BF1 ……………….. ………………………….. ………………………….. …………….…. ………….. ……….. ………………….. … ……… ………………….. ……… ………… ………

Business Functions (Verticals) BF2 ……………….. ………………………….. ………………………….. …………….…. ………….. ……….. ………………….. … ……… ………………….. ……… BBuussiinneessss iinniittiiaattiivvee ………… ……… TT yypp ee ##11 BF3 Business ……………….. ………………………….. ………………………….. …………….…. ………….. ……….. Function ………………….. … ……… ………………….. BBuussiinneessssIInniittiiaattiivvee ……… ………… TT yypp ee##22 Capabilities ……… BF4 ……………….. ………………………….. ………………………….. ……….…. ………….. ……………….. … ……………… ……………….. Business Initia tiv e …………….. Business Initia tiv e ……………… ………… TT yypp ee##22 ………

Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] return to schema 13 © Telelogic AB BDAL Framework (continued)

Business Model Data Work Process Policies Representations

Data Automation Roles Elements Objectives

Requirements Automation Automation Automation Automation Requirements Data Rep. Use Cases User Types

Solution Solution Concept Solution Solution Specification Use Cases User Types

Design Testing Tests Test Sets

14 © Telelogic AB Agenda

• The Unmet Need

• The Solution

– Strategy: Business Driven Application Lifecycle

– Tactics: Business Modeling via DOORS & VISIO

– Tactics: DOORS/VISIO Integration

• Case Study Results

15 © Telelogic AB Why DOORS for Business Modeling?

• Text requires less overhead than DOORS Symbolic/UML symbolic languages when documenting processes TThhee uusseerr sseelleeccttss tthhee ""UUpp"" oorr ""DDoowwnn"" bbuuttttoonn • Schema and visualization mmoouunntteedd nneeaarr tthhee options not limited by industry eelleevvaattoorr ddoooorr((ss)).. standards groups (e.g. UML) • Better support for traceability and impact analysis • More granular change management Business Model • Better support for concurrent access Requirements Master

Planning & Solution Architecture • You are already using DOORS to manage the requirements that must be mapped to the business model

16 © Telelogic AB Example: DOORS Business Analysis Capabilities • Business Process – ranked by execution frequency – ranked by percent of initiative duration – ranked by participating role count • Artifacts – ranked by number of times the artifact is touched – ranked by number of business functions that touch the artifact • Process & Artifacts – time ordered grid of processes & artifacts that join business roles

17 © Telelogic AB Example: DOORS Biz Model Drives Req. Mgmt

MMoosstt iimmppoorrttaanntt wwoorrkk pprroocceesssseess.. Work Process Use Case Requirements Design Code

HHiigghh PPrriioorriittyy!!

Implementor

18 © Telelogic AB Why VISIO?

• Flexibility – Supports existing standards (e.g. UML, IDEF, Yourdon, etc.) – Supports user defined visualizations • Ubiquitous availability (Microsoft presence) • Inexpensive • Easy of use minimizes training requirements

19 © Telelogic AB Example: Business Analysis Capabilities

VALUE CHAIN ANALYSIS

Rectangles: Information assets

Black Lines: “n” work process steps

Blue Lines: Critical performance metrics

Red Lines: Most Likely Critical Path

Shaded Regions: Work process boundaries

Horizontal Swim Lanes: Business function boundaries

Vertical Grey Bars: Initiative Stage Gates Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected]

20 © Telelogic AB Example: Business Analysis Capabilities

ARCHITECTURAL ANALYSIS

Rectangles: Information assets

Black Lines: “n” work process steps

Blue Lines: Critical performance metrics

Red Lines: Most Likely Critical Path

Shaded Regions: AWAppopprlkliic cpaarttoiioocnen s BBsoo buuonnuddnaadrriaieerssies Horizontal Swim Lanes: Business function boundaries

21 © Telelogic AB Agenda

• The Unmet Need

• The Solution

– Strategy: Business Driven Application Lifecycle

– Tactics: Business Modeling via DOORS & VISIO

– Tactics: DOORS/VISIO Integration

• Case Study Results

22 © Telelogic AB DOORS / Visio Interface (DVI)

• To automate Business Driven Application Lifecycle data exchange between DOORS and Visio, a DOORS / Visio Interface (DVI) application has been written. • The DVI is written in the DOORS Extension Language (DXL), and uses DOORS as a Microsoft automation client to control the Microsoft Visio application.

• Microsoft Component Object Model (COM) technology is then used to access Visio properties and methods. – This technology allows the DVI to perform the necessary data access and manipulation functions to manage Visio diagrams and satisfy the DVI application requirements.

23 © Telelogic AB DVI- Interface Concept

DOORS Objects Mapped to Visio Shapes DOORS Links Mapped to Visio Connectors

24 © Telelogic AB DVI – Object Mapping

• The DVI allows DOORS objects to be mapped to shapes on a Visio diagram.

• Each mapped DOORS object is associated with a Visio master shape, and each Visio master shape is associated with a set of DOORS attributes. • Mapped DOORS attributes are automatically represented on Visio shapes as editable Visio “Custom Properties”, so that attribute value changes can be made from either application.

• Each mapped DOORS object can be mapped to one or more pages in the Visio drawing, and one or more layers in each page.

• The DVI allows DOORS links to be mapped to connectors on Visio diagrams.

• If two DOORS objects are mapped, and are also connected by a link in DOORS, then the linkset from the link module that the link belongs to is presented for mapping.

• If the linkset is subsequently mapped by the user, the DOORS links will be represented by Visio connectors glued to the Visio shapes that represent the linked DOORS objects.

DOORS Objects mapped to Visio Shapes (Page/Layer(s))

DOORS Linksets mapped to Visio Connectors

• The DVI uses one surrogate module for each DOORS project to represent mapped objects and relationships.

• For each mapped DOORS object, a surrogate object is created in the surrogate module, and a DOORS link is made from the surrogate object to the mapped object. – This ensures mapped objects are not deleted unless they are first unmapped from the DVI application.

• Surrogate objects are also created for mapped Visio masters, DOORS attributes, and DOORS linksets.

• The DVI manages multiple Visio drawings for each DOORS project. • Visio drawings can be stored as a file on a file system, or embedded into a DOORS object. – Embedding has the distinct advantage of allowing DOORS access rights to be applied to the DOORS object containing the Visio drawing.

• Before the synchronization of DOORS and a Visio drawing, the user is presented with a pre-synchronization review.

• This review lists all changes that are necessary to synchronize DOORS and the Visio drawing, based on changes to both applications since the last synchronization.

• Mapped DOORS attributes are represented on Visio shapes as editable Visio custom properties, and attribute value changes can be made from either application.

• DOORS history functionality can be used to detect the exact time and content for any changes to attribute values.

• Visio does not have any corresponding history functionality, so Microsoft Visio Visual Basic for Applications (VBA) macros are inserted into each DVI managed Visio drawing.

• These macros manage “Last Modified On” (LMO) date/time stamps for the Visio custom properties representing mapped DOORS attributes.

• Given this situation that attribute value changes can be made from either application for mapped DOORS attributes, it is possible that a DOORS attribute value was updated for both the DOORS mapped object and the corresponding Visio shape(s) since the last synchronization.

• Such a case is considered a conflict, and must be resolved before synchronization.

• For such cases the user is presented with both changes in the pre-synchronization review, and is allowed to choose which change should prevail.

• Conflicts are presented, and the user selects the prevailing change for each conflict before synchronization. – For such cases the user is presented with both changes in the pre-synchronization review, and is allowed to choose which change should prevail.

• DOORS Object Mapping to Visio Shape/Page/Layer • DOORS Link Mapping to Visio Connectors • DOORS Attribute Value Synchronization • DOORS/Visio editing and conflict resolution

• Final development of the DOORS/Visio Interface (DVI) v1.0 will be completed in 2005, and the application is expected to be widely deployed at Proctor & Gamble in 2006.

• The DVI application will also be made available as a commercial offering from Galactic Solutions Group (http://galactic-solutions.com) in 2006. – Pricing for the DVI application has not yet been determined.

• In addition, the DOORS/Visio integration technologies built to implement the DVI will be leveraged to create additional commercial products to visualize and manipulate DOORS database schema elements (Modules, Link Mappings, Links, etc.)

• DOORS Modules Mapped to Visio Shapes

• DOORS Attribute Definitions Mapped to Visio Custom Properties

• DOORS Linksets Mapped to Visio Connectors

• The Unmet Need

• The Solution

– Strategy: Business Driven Application Lifecycle

– Tactics: Business Modeling via DOORS & VISIO

– Tactics: DOORS/VISIO Integration

• Case Study Results

• Start of Project Context – First application of PLM in the target domain – No supplier or IT experience in target domain – Target domain under a new organizational model – No documented processes or data mgmt strategy • Project Results – Business process improvements implemented before delivering the system – Project 65% under-budget & order of magnitude reduction in industry average defects for similarly sized applications – Stakeholders and users expressed appreciation for their degree of involvement and for the transparency of the method

• Start of Project Context – Two entrenched camps created by one year of prior debate – Positions: $24MM savings vs. “it won’t work” – “Advocacy” displacing “inquiry” • Results – Two camps aligned on business process performance metrics as the decision criteria – Quantified business impacts of software solution options – Consensus on final decision (to stay with current supplier) – New insights on strategic value of the technology (irrespective of supplier)