We Will Show How IBM Rational Addresses JKE's Software Delivery

Rationalize Your Software Delivery

With IBM

Define, Manage, and Track your

Requirements and Designs

We Will Show How IBM Rational Addresses JKE’s Software Delivery Strategies

• Implement ALM with the whole team approach Break Down Barriers with the Jazz Platform, Improved Planning and Collaboration

• Improve requirements management

• Build better designs collaboratively

Define, Manage, and Track your Requirements and Designs

• Create an efficient development environment Integrated Change, Build and Deploy Is What Sets Us Apart

• Instill software quality across the lifecycle Quality Is Not Accidental

• Extend the lifecycle to include operations Bridge the Gap between Development and Operations

• Connect all software delivery capabilities together into an end to end open solution

Big Picture – See the Forest for the Trees

3 - Define, Manage, and Track your Requirements and Designs 2

Current Concerns

Owner information hard to find, organize, and understand

Models and artifacts exclusive to tool, unable to integrate or share data

Excessive, vague, and unread info drives poor planning and expectations

JKE Business Analyst is drowning in data, but starving for good information

Business Analyst: “This material just does not

connect.”

Project Manager: “How do we scope

this?”

Stakeholder: ”Here is a photograph of our

whiteboarding.”

JKE Has Had Difficulty Capturing And Organizing Requirements-Related Assets

The business analyst ends up with disparate, disjointed

and inconsistent data in a variety of formats

Stakeholder: ”Here is an email with my features, and

a link to our team wiki.”


4

A poor requirements management

process affects the success of the

entire organization!

Architect: "I can’t take these

requirements and create

meaningful models from

them.”

Stakeholder: “Did my critical

requirement make it into the

new release?”

Tester: "What requirements

am I testing against?”

Developer: “Are there any new

requirements I don’t know about?”

Requirements Management Process Lacks Control

And Application Lifecycle Traceability

All parties are unclear of timelines and expectations

Current Concerns

No consolidated hub of information

Requirements aren’t linked to development or testing activities

Cannot communicate requirements and manage change during execution

Business Analyst: “People don’t seem to be

on the same page.”


JKE Business Requirements Problems

Difficult to capture and organize requirements-related assets that come from dissimilar tools

• Create disparate, disjointed and inconsistent data

• Variety of formats are impossible to understand and organize

Requirements management process lacks control, application lifecycle traceability and repeatability

• Source code can’t be tied to requirements

• Key requirements often missed completely in code

• Requirements can’t be turned into an architectural design

Problems gathering business requirements and delivering

requisite capabilities can be grouped into two areas


Projects Rarely Rise Above The Quality Of Their Requirements

Engage stakeholders - early and often - in defining and validating

requirements improves likelihood that projects will meet customer need.

Regardless of:

Project methodology (waterfall, iterative or agile)

Requirements artifacts created (stories, use cases, process

diagrams, etc.)

Create artifacts of many types - to express requirements and related

context/constraints

Can be created in various tools and data formats

− Spreadsheets and presentations

− Whiteboard session snapshots

− Recordings from Web conferences

Need to bring "information islands" together

Have conversations around them

6 3 - Define, Manage, and Track your Requirements and Designs

In order to succeed in requirements definition, you need to:

Requirements Management Integration In Application Lifecycle

Tightly aligning development and test activities with

business requirements makes project success

probable

Alignment requires:

Integrated tools

Common information hub

Common views of requirements by all parties

Real-time collaboration between business analysts and

development team members

Projects that don’t link requirements management to the

rest of the application lifecycle are unlikely to succeed


Average on time performance increased 161%

Time overruns reduced 87%

Average on budget performance improved over 95%

Budget overruns reduced about 75%

Percentage of projects that deliver functionality needed by business rose by about 75%

Source: IAG Consulting, September 2009

Benefits To Customers With A Strong Requirements Management Process


http://www.iag.biz/resources/library/download-business-analysis-benchmark-2009.html

The project will have essential

business requirements from

many stakeholders. How do we

make sure they are all captured,

defined and managed?

Business Requirements For The “Money That Matters” Solution

Analyst

Rational Requirements

Composer can provide that,

as well as integrating with

your software development

activities across

requirements, development,

build and test.

IBM


Rational Requirements Composer Defines, Visualizes, Manages And Analyzes Requirements

Rational Software

Architect Design Manager

Designs

Models

Diagrams

…

Rational Team Concert

Release Plans

Iterations

Work Items

Source Code

…

Rational Quality Manager

Test plans

Test cases

Test scripts

Test executions

…

Jazz Team Server

RTC RRC RQM

Core OSLC REST Services: Discovery, Query, Storage, Presentation, Data Warehousing,

Administration, Reporting, etc…

RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Visualize:

Business Process

Models, Storyboards,

Use Case Modeling

Define

Rich Text Editor,

Seamless integration

with Rational

RequisitePro and

DOORS

Analysis:

Lifecycle traceability,

Impact and Coverage

Analysis, Dynamic

Dashboards

Manage:

Glossaries, Reuse,

Business Process,

Templates, Baseline and

Scope Management

RRC Client: Web browser

RSA DM REST

Services: Design

Management


Traceability

using ad hoc

spreadsheets

Collaboration using

ad hoc documents

JKE Struggled With Collaboration On Requirements And Requirements Traceability

Challenges

• Lack of integrated view of all requirements

• Costly to synchronize “islands” of information


Rational Requirements Composer

Glossaries

Rich-Text Docs

Process Diagrams

Use Case Models

RRC Stores All Requirements In A Central Hub With Full Lifecycle Traceability


Outline flows with Process Diagrams

Use whiteboard snapshots and other Informal Documentation

Many Options To Capture Requirements

The analyst can define and validate requirements using many techniques

Group related scenarios, describe actors, system boundaries and user goals with Use Cases

Visualize scenarios with Storyboards and Screen Flows

Describe flows and capture requirements in Rich-text Documents

Define and reuse common terms in Glossaries


Many Requirements Artifact Types Can Be Defined

Including (w/templates) but not limited to:

Business Goal

Business Process Diagram

Business Rule

Feature

Glossary

Role

Sketch

Use Case Diagram

User Story Elaboration

Non Functional Requirement

Security

Performance

Availability

This gives great flexibility in grouping objects with a similar function


Business Analyst Can See Linked Assets From Rational Team Concert And Rational Quality Manager

Information from RTC and RQM is visible in RRC

Widgets provide lifecycle status

This integration uses links to break down information

silos


Developers Can See Linked Requirements Assets From Rational Requirements Composer

Developers in RTC have insight into requirements from RRC

RTC Dashboard


The Requirements Management Process Is Now Under Control

17

By using RRC

All parties have meaningful conversations on requirements

Team can adapt to new requirements in middle of the project

Requirements are integrated into lifecycle for traceability and reusability

Faster informed decisions and team guidance avoids delays and derailment

Business Analyst: “This iterative process of continual validation

works fast.”

Developer: ”Traceable requirements and change

management help us avoid guesswork and rework.”

Project Manager: "Validation on scope was done earlier

and more precisely.”

Stakeholder: "I know how, when and where my inputs were used.”

Development Manager: “Process guidance helps us adopt new

techniques without disruption.”

Requirements are integrated into the application lifecycle. The Project

Manager can do better estimation and tracking


DEMO 1: Rational Requirements Composer

1) Stakeholders have provided

some feedback in a user story

in RTC

2) Business analyst creates

requirements artifacts to

support new requirement in

RRC:

a) User story elaboration

b) Storyboard

3) Artifacts are linked to the

original request

4) Changes are reviewed by

developer implementing the

functionality

5) Finally, requirements artifacts

are linked to the tracking Task

in RTC

User Story

Elaboration

Storyboard

Review


IBM Rational DOORS For Systems Engineering-Specific Requirements

For systems engineering/embedded systems, DOORS is

used for requirements management and replaces RRC

Industry accelerators provide domain-specific, built-in

compliance and guidance

Electronic Design

Aerospace and Defense

Automotive Engineering

Medical Device

Same OSLC integrations to RTC and RQM

Integrates with Rhapsody and Rhapsody DM – Systems

Engineering-Specific Modeling tools


DOORS Comes In Two Editions: A Standalone Client And Jazz-based Product

DOORS 9.x Features DOORS NG Features

Benefits teams already using existing

DOORS infrastructure, which is likely to

stay in place as-is for a long time.

A single-server solution native to the

Jazz Team Server making it easier to

deploy a multi-product solution.

More mature capabilities are included

with DOORS 9.x:

• Electronic signatures

• Baseline comparisons

• Round trip data import/export

• Requirements change management

driven by a change management tool

Simplest on-ramp from MS Word and

Excel

• Built-in visual notations for

collaborating around requirements

• Built-in capabilities for task

management and planning

• A solution using a commercial off-the

shelf (COTS) database

Significant product customizations,

integrations, or automation based on

DOORS eXtension Language (DXL)

A web-based RM solution offering the

most up-to-date web UI experience (with

optional local rich client and

interoperability with DOORS 9.5)


Choose which DOORS Is Right For You

Use DOORS Next Generation if…

• Teams currently using documents and spreadsheets for requirements who are seeking more effective requirements management.

• Teams seeking a less formal, lighter-weight requirements process than those typically implemented with Rational DOORS.

• Teams seeking a Web-based requirements tool (with optional local rich client).

• Teams seeking a single-server solution for multi-disciplinary product development teams (requirements, design, development, test).

Use both DOORS and DOORS NG to…

• Jump-start new projects in Rational DOORS NG: use existing information in DOORS 9.5 using the requirements interchange format (ReqIF).

• Involve your supply chain: invite your suppliers to use DOORS NG for requirements collaboration. Merge their updates into your DOORS 9.5 repository.

• Reference existing information in DOORS 9.5: use OLSC links in module traceability columns.

• Generate documents: use Rational Publishing Engine to create document templates with DOORS 9.5 and DOORS NG data sources.

If using DOORS v9.5…

• If you have active subscription and support for Rational DOORS, you are entitled to use Rational DOORS Next Generation.

• To purchase Rational DOORS NG, buy Rational DOORS 9.5. 21 3 - Define, Manage, and Track your Requirements and Designs

HP, Atlassian and Microsoft

claim that their ALM products

can also provide Requirements

Management.

JKE Has Heard Sales Presentations About Competitive ALM Solutions

Business Analyst


Composer is a better offering

for capturing requirements

as well as allowing

traceability across the

complete lifecycle.

IBM


HP ALM Is Geared Towards Testing, Not Full Lifecycle Management

Focus is to solve problems for test engineers

Is a test-oriented tool first, requirements second

Everybody within JKE needs to work/add-to requirements, not

just testers

Has a pre-configured, fixed data model, assuming how data

is related

Can’t create customized traceability views

Requirements Management needs to fit JKE’s business, not

the other way around

Integrations to expand beyond testing are point-to-point and

offer little in terms of open services/standards beyond basic

REST


Atlassian Provides Little Support For Requirements Management

JIRA provides only Issues – Epic and Story issue types

Wiki markup is supported

Confluence provides Wiki spaces that can be linked to issues

With Gliffy (3rd-party plug-in), JIRA

5 (not JIRA 4) can host charts,

diagrams, and UI mock-ups

Gliffy requires an annual

subscription

Artifacts created by Gliffy are

primitive, not directly

actionable

− Example: You can draw

process diagrams or UI mock-

ups, but there are no tools to

implement them


Microsoft Visual Studio 2012 Lacks Specialized Tools For Requirements Definition And Tracking

Microsoft solution

leverages documents for

requirements definition:

SharePoint documents

library – requirements

office documents

Team Foundation Server

- requirements work

items

Results:

Ineffective collaboration

on requirements

definition across team

roles

Unreliable traceability -

easily broken links

between work items and

requirements documents

VS IDE

Team

Explorer

TFS

Repository

TFS

Server

SharePoint

Project

Portal

& Reports

Developer

Stakeholder

Work

items

tracking

Product Owner

Team Web

Access

ASP .NET

Web app

Project Manager .mpp .mpp Office

docs

Links between requirements-

related work items and

requirement documents 3 - Define, Manage, and Track your Requirements and Designs 25

IBM

Project Manager

Translating Requirements Into A Design

Even with good requirements,

we have had trouble creating an

actionable architecture.

Rational Software Architect with

Design Manager can turn your

requirements into an architectural

design and provide collaboration

on design artifacts, life cycle

traceability and documentation to

stakeholders and development

team.


Rational Software Architect Design Manager Integrates Design Into The Lifecycle

3 - Define, Manage, and Track

your Requirements and Designs

27

Jazz Team Server

RTC RRC RQM

Core OSLC REST Services: Discovery, Query, Storage, Presentation, Data Warehousing,

Administration, Reporting, etc…

RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Collaborate:

Threaded comments,

design mark-up,

automated design

reviews, sketches

Design in context

Integrate with RSA to

work on web or in client,

work seamlessly with

team

Publish:

Design documents,

automated reports and

documents using

Rational Publishing

Engine

Manage:

Reuse, Templates,

Search designs, Link

designs to artifacts

across the lifecycle

RSA DM Client: RSA and Web browser


Composer

Collections

Requirements

Storyboards

Use cases

…

RSA DM REST

Services: Design

Management

Rational Team Concert

Release Plans

Iterations

Work Items

Source Code

…

Rational Quality

Manager

Test plans

Test cases

Test scripts

Test executions

…

Rational Software Architect Design Manager (RSA DM)

Integrating Designs and Jazz

• URL addressable design elements

• Enterprise-wide design repository for searching, analysis, and reuse

• Links designs to requirements, change requests, test plans, and other designs

• Navigate and visualize relationships

Stakeholder Collaboration

• Broader access to designs through web client

• In-context design collaboration with commenting and visual mark-up

• Automate design review tasks

Document Generation

• Satisfy auditing and regulatory demands with multi-discipline documents generation

• Include designs, comments, and links to other lifecycle data

IBM Collaborative

Design Management

Architect

Engineer Developer

Requirements Analyst

Deployment Engineer

“We are excited about the capabilities in

Collaborative Design Management …. We see it

playing a significant role in our development process

because it allows us to transition away from our

home grown solutions in that area to standardized

Rational products."

Hans-Peter Berger, Department Head, Application

Development Infrastructure, GAD


Rational Software Architect

Design Manager

RSA DM Can Link Design Artifacts To Requirements And Development


DEMO 2: Rational Software Architect Design Manager

Collaborative annotations can be captured for any diagram in RSA DM

Relationships between requirement artifacts and design artifacts keep the design team “in-the-know”

JKE’s Design team can connect to RRC, link artifacts, and create more concrete design artifacts in an automated fashion


Rational Rhapsody and Rhapsody Design Manager For Systems Engineering-Specific Designs

Rational Rhapsody and Rhapsody Design Manager replace

RSA and RSA DM for systems engineering/embedded

systems

Rational Rhapsody Architect for Software

Rational Rhapsody Architect for Systems Engineers

Rational Rhapsody Design Manager

Rational Rhapsody Designer for Systems Engineers

Rational Rhapsody Developer

Rhapsody DM provides OSLC integrations across lifecycle


Microsoft Visual Studio 2012 Offers Little Architecture And Modeling Capabilities Compared To RSA

Only 5 UML diagrams and 2 architecture diagrams are supported and

only in Ultimate edition of Visual Studio

5 UML Diagrams:

Class

Sequence

Use Case

Activity

Component

2 Arch. Diagrams:

Layer

Directed Graph


Microsoft Architecture And Modeling Solution Inadequate For Many Enterprise Scenarios

Even supported diagrams are not UML standard compliant

Only .NET languages and C/C++ Windows supported

Non-.NET developers would get input from the architect either as:

− XMI or

− Pictures

No non-Windows platform support

Many scenarios supported by RSA are completely missing from VS

2012 Ultimate, including but not limited to:

Modeling deployment topologies

Architecture Frameworks with UML models for creating complex

architectures

Business process modeling with BPMN

Modeling services and service-oriented architectures

Microsoft solution for architecture and modeling does not suit

heterogeneous teams and enterprise application development


We need an end-to-end security

solution starting from

requirements and extending

through all lifecycles

JKE Has Very Strict Security Requirements…

Product Owner


Composer has templates for

non-functional requirements

including security

requirements. Rational

AppScan completes the

solution…

IBM


REQUIREMENTS CODE BUILD SECURITY PRODUCTION QA

AppScan

Standard AppScan Source AppScan

Tester

Security

Requirements

Definition

AppScan

onDemand

(SaaS)

AppScan Enterprise / Reporting Console

(enterprise-wide scanning and reporting)

Security /

compliance

testing

incorporated into

testing

Security

requirements

defined before

design &

implementation

Outsourced

testing for

security audits

& production

site monitoring

Security /

Compliance

oversight,

control,

policy, audits

Build security

testing into

the IDE

Application Security Best Practices

Automate

Security /

Compliance

testing in

Build Process

Web site Compliance:

Policy Tester Privacy

Policy Tester Accessibility

Policy Tester Quality

Policy Tester onDemand

Security Requirements template provided in RRC

IBM Security AppScan Supports Application Security In Jazz

From Security Requirements in RRC to Code and Application Runtime Analysis

with IBM Security AppScan


AppScan Source Edition Gives Developers An Expert Advice To Improve Security

Security / compliance testing during software development

Scans source code looking for security vulnerabilities

• When writing the code

• When building the app

Identifies and provides expert advice on fixes to code

Integrates with other Rational Tools

Secure Code

Code Build

Scan


AppScan Source Edition Benefits Cross-Platform Teams

Including teams building z/OS applications: easily scan

COBOL, Java, JavaScript, JSP, ColdFusion, C, C++

Microsoft .NET languages, JScript, VBScript, PHP, Perl, VB 6

Integrates with

Rational Application Developer and its supersets

Eclipse IDEs

Microsoft Visual Studio

Defect tracking with

Rational Team Concert and Rational ClearQuest

HP Quality Center, MS Team Foundation Server

Deploys with AppScan Enterprise for automated correlation

of static and dynamic analysis results


Summary Rational Requirements Composer addresses JKE’s requirements needs:

• Capture/organize/access requirements from all stakeholders in a centralized hub of requirement artifacts

• Transparently integrate requirements management process with entire application development lifecycle

• Define and manage all types of requirements based on provided templates

• Includes non-functional requirements, e.g., Security

Rational Software Architect Design Manager:

• In addition to support of standards-based modeling, extends CLM to design activities

• Provides higher productivity through integration and collaboration

• Improves quality and lowers costs through and life cycle traceability

RRC + AppScan security provide end-to-end security solution for application lifecycle

Competitors don’t deliver full lifecycle capabilities:

• Lack of pre-defined out-of-the-box requirements templates for projects

• Usability geared to testers, not business analysts

• No single hub for requirements definition

• Architecture and modeling solution incomplete and not well-suited for heterogeneous platform teams


© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

www.ibm.com/software/rational


http://www.ibm.com/software/rational

We Will Show How IBM Rational Addresses JKE's Software Delivery

Documents

Transcript of We Will Show How IBM Rational Addresses JKE's Software Delivery