Visure Solutions

Corporate Information

2

Visure Solutions, The Requirements Company

• Focused on the delivery of innovative requirements solutions since

1999

• Privately held, VC Backed (Bullnet Capital)

• Headquarters in Madrid, Spain

– Offices in San Francisco, California, USA

– European Sales Offices in UK, Germany and Sweden

– Commercial presence (direct or via channel) in 25 countries

• More than 180 man-years focused on delivering

requirements products and solutions

• certified

3

Visure Solutions, Main Customers

Automotive, Rail & Electronics

Aerospace & Defense

Finance

Telecommunications

Transport & Energy

4

What do analysts say about us?

“A surprise was Visure

Requirements, a

newcomer from Madrid,

Spain, which offered …

advances in specific

areas.”

“In Butler Group’s view, the solution has an impressive

set of integration capabilities, and can be adapted

easily to existing RDM process in organizations,

as well as the development methodology in use."

Best tool for Optimizing Business Alignment

on Requirements

5

Our View of the Market: Market Pains 1

• Key issues:

– Relative growth of software,

increase of 33% compared to

mechanics and electronics

– Complexity of product lines and

large-scale systems

• Examples:

– Aircraft carrier, 1,000,000

requirements

– Hospital information system:

90,000 requirements

– Train control system: 14,000

contract requirements

Growing Complexity of Software and Product Variants

2006 2007 2008 2009 2010 2011 2012

0

5

10

15

20

25

30

35

40

45

50

Calendar years M

illio

ns

lin

es

of

co

de

2006

2007

2008

2009

2010

2011

2012

•Ford Motor Company’s Prediction of Growth of Software Content in Automobile embedded software.

•CPDA, The Requirements Engineering Process - Panel Discussion of Critical Issues in

Requirements Management

•Nationale Roadmap Embedded Systems, ZVEI, www.zvei.org, 2010

•Requirements Engineering: A Roadmap, Bashar Nuseibeh & Steve Easterbrook, 2000

6

Our View of the Market: Market Pains 2

• Key issues:

– < ~52% of requirements go into product release

– 1% to 3% per month of requirements become obsolete

– RDM tools do not seamlessly connect upstream and downstream

activities

– Lack of communication and visualization of RDM features for scoping &

descoping incl. decision support

Missing Connection to Market Needs & Business Requirements

•Nationale Roadmap Embedded Systems, ZVEI, http://www.zvei.org/, 2010

•Systems Engineering Vision 2020

•Information Technology for European Advancement (ITEA) 2009 Roadmap, http://www.itea2.org, p.18, 3rd Edition

•M. Bone, R. Cloutier: The Current State of Model-Based Systems Engineering:

Results from the OMG SysML Request for Information 2009

7

Our View of the Market: Market Pains 3

• Key issues:

– ~ 60% of all software defects traceable back to poor RDM practices

Changing requirements: Lack of effective change process and tool

enforcement

Absent formal RDM approach, > 90% of companies use still use natural

language approach

No defined RDM process

80% of organizations do not use RDM tool at all

– Connecting adjoint development activities:

Testing

Design

Product risk management

Project management

Requirements Quality Essential Driver for Software Product Quality

•Institute for Experimental Software Engineering (IESE), Fraunhofer Gesellschaft, Survey on Root Causes of Software Defects in Medical Devices, 2007;

http://www.iese.fraunhofer.de/

•Information Technology for European Advancement 2009 Roadmap, http://www.itea2.org p.18, 3rd Edition

•Chaos Chronicles v 3.0, Standish Group International, 2003, http://www.standishgroup.com/

8

Our View of the Market: Visure’s Differentiated Approach

Organization with mature Requirements

Engineering PROCESSES are proven to

consistently produce better quality products on

time, and within budget

A COLLABORATIVE requirements platform has

proven to have a direct impact in the project

success bridging the gap between business and

IT, communicating distributed teams, integrating

clear information between the teams, and

establishing workflows

QUALITY needs to be introduced straight from

the beginning and at every stage of the

development, from writing good requirements,

keeping changes under control, to reusing high

quality assets

Process

Collaboration

Product quality

9

Our value proposition: Vision/Mission

Your Process,

Your Requirements.

Better Results.

Our vision

To be the preferred global provider of

requirements engineering solutions,

spanning the entire requirements

lifecycle and solving requirements

challenges and regulatory

requirements

Our mission

• To deliver innovative and flexible process-

based requirements engineering lifecycle

solutions

• Enable companies to support and streamline

their requirements processes, collaborate

more effectively, improve quality and reduce

risk

• Enable companies to better define and

validate business needs, reduce costs and

meet regulatory requirements

10

Our Value Proposition: Process

OUR SOLUTION SUPPORTS YOUR PROCESS - FROM AGILE TO WATERFALL

11

Our Value Proposition: Collaboration

OUR ROLE-BASED SOLUTION KEEPS ALL STAKEHOLDERS IN SYNC

12

Our Value Proposition: Quality

OUR SOLUTION HELPS AVOID PITFALLS AND MITIGATE RISK

13

Our value proposition: Market Served

• Visure Focuses on Customers with:

– Portfolio of products with increasing complexity

– Defined business needs and requirements

– Formalized software engineering practices and standards

– Process Improvement and process maturity initiatives

– Distributed stakeholders, teams, partners and/or vendors

– Compliance needs

• Special expertise and experience in sectors like:

– Aerospace and defense

– Automotive

– Energy, transportation and utilities

– Renewable energies

– Finance, banking

– Telecommunications

14

Visure Requirements our Enterprise Solution

Visure Requirements INTEGRATES

PROCESS, QUALITY & COLLABORATION IN A SINGLE PLATFORM

15

Visure Requirements our Flagship Product

• With Visure Requirements, you can:

– Establish and support a requirements engineering process that

everyone can follow

– Prioritize capabilities and identify gaps and conflicts in the process

– Ensure your platform supports and enforces your process

– Avoid pitfalls and mitigate risk every step of the way

– Improve quality through more effective change management and reuse

– Achieve effective collaboration between stakeholders using different

tools

16

Process-Driven Requirements Engineering

Visure Requirements BECOMES THE PROCESS BACKBONE

REPRESENTING ALL REQUIREMENT-RELATED ARTEFACTS

• Agile, IT software development, automotive, pharmaceutical, aerospace and

many other can be represented through the Process Meta Models

• The interactive Meta Models allow representing different element types and

subtypes, including Requirements, Change Requests, Use Cases, Test

Cases, Defects, Glossaries of terms, etc. and the relationships between

them

17

Visure Requirements: Role-based Collaboration

• Users will have specific User Interface and Capabilities completely based on

their roles that will help them follow the process, and focus on their daily work

• All roles share a Centralized Information Repository (CIR), with access to parts

of it and with specific access rights, where they will share the information

• Access to the CIR is guaranteed to distributed teams independent from their

location

Visure Requirements BECOMES A TAILORED TOOL FOR EACH ROLE

WITH SPECIFIC VIEWS OF THE SAME CENTRALIZED INFORMATION

18

Visure Requirements: Collaboration

• Visure Requirements is capable of exchanging information with tools in other

disciplines and allow users keep using their own tools, while keeping

everything inside a CIR

CHANGE

MANAGEMENT AND

BUG TRACKING - JIRA

- Bugzilla

TEST

MANAGEMENT - HP QC

- LDRA

DESIGN - SPARX EA

- RSM/RSA

MS OFFICE AND

OTHER RM TOOLS - MS WORD, MS Excel

-IBM/Rational DOORS

- Caliber BorlandRM

- XML Requirements Interchange

REQUIREMENT-RELATED ARTEFACTS MAY COME FROM OTHER TOOLS AND

ROUND TRIPS MAY BE ESTABLISHED TO COMMUNICATE WITH TEAMS

19

Visure Requirements: Product Quality

• The end-to-end traceability in Visure Requirements allows controlling

the complete specification and change impact, identifying missed

customer requests, affected software requirements and use cases,

unfulfilled system requirements. These elements may come from third

party companies

Visure Requirements BECOMES A TRACEABILITY CENTER

OF THE COMPLETE REQUIREMENTS LIFECYCLE

20

Visure Requirements: Product Quality

• Requirements semantic analysis

• Ensure quality of individual requirements avoiding ambiguos terms,

conditional sentences, design terms, etc.

• Ensure specification quality, avoiding overlapping requirements,

contradictions, or inconsistent use of units or terms

QUALITY REQUIREMENTS BASED ON RIGHT THE FIRST TIME PREMISE

21

Visure Requirements: Product Quality

• Requirements Simulation

• Prototyping of low (mock ups) to high fidelity interfaces

• Supports user validation earlier in the phase reducing rework

PROTOTYPING & SIMULATION OF USER INTERFACES

22

Product Quality: Requirements Traceability

• Reusability allows defining catalogues

of “components” (Requirements, Uses

Cases, Test and Traceability), which

can be reused in projects

• The catalogues can be used for simple

reusability of elements (non- functional

Requirements, tests, etc.), in order to

reduce rework, reuse, high quality

assets

• Reusability in Visure Requirements

supports product families and variants

to help build similar systems with small

variations of it e.g. cars, cell phones,

software products, etc…

Requirement 1

Service 1

Test 1

Requirement 2

Requirement 3

Test 2

Test 3

Service 2

Service 3

Requirement 1Test 1

Service 1

Project 1

Component A

Requirement 1

Test 1

Requirement 2

Test 2

Service 1

Service 2

Component B

Requirement 1 Test 1

Component C

Project X

Requirement 1

v1

Test 1 v1

Service 1

v1Component A v1

Requirement 1Test 1

Service 1

Requirement 1 v2Test 1 v3

Component A v2

Test 4 v2

Service 1 v2

Project Y

Requirement 1

v2

Test 1 v3

Test 4 v2

Service 1

v2

Component A v1

Component A v2

Visure Requirements BECOMES THE REUSABILITY CENTER

OF COMPANY ASSETS