Rational Requisite Pro Usage at NYSDOT BA CoP 10-20-2011

Rational Requisite Pro
Usage at NYSDOT
BA CoP
10-20-2011
Rational Product Overview
(Current DOT ITD implementation)
• ClearCase
Software Configuration
Management
• ClearQuest
Change Management, Defect
Tracking, Application and Project
Inventory
• SoDA
Project Management Reporting
• Requisite Pro
Requirements Management
• Test Manager
Maintains test plans and controls
execution of test plans
• Robot/ RFT
Testing tools
MS
Visio
ReqPro
Rational Tools
TestManager
Robot
RFT
ClearQuest
ClearCase
SoDA
TestManager maintains the test plan and is the control &
execution component
ClearQuest handles change & defect management
ClearCase handles the application development
components
ReqPro catalogs the requirements and interacts with other
components to facilitate and monitor planning
Microsoft Visio is utilized to depict the workflow visually
Robot & RFT are used for testing a developed application
SoDA is used for Project Management Reporting
Rational Tool Integrations & Project Disciplines
Requirements
Rational
RequisitePro
Project
Mgmt.
Generate
documentation
Rational
SoDA
Track
requirements
tests
Baseline requirements
Baseline test scripts
Rational
Robot
Automate
run-time
testing
Create test
inputs from
requirements
Create & execute test scripts
Testing /
Implementation
Rational
TestManager
Rational
ClearCase
Link
requirements
to change
requests
Rational
ClearQuest
(ClearCase)
Submit defects
Link code
changes
to activities
Configuration
& Change
Management
Deployment
ReqPro Features



Organizes requirements
Provides traceability and change management
throughout the project lifecycle
Requirements may be created in a document or
in a view

MS Word Integration

Requirements are stored in a database

Integrates with ClearQuest (Defect Tracking) and
Test Manager (Test Management) for defect and
change tracking across the lifecycle
ITD Requirement Types
Business Rules
(constraints and
data validation)
Applies to
Non-Functional
Specifications
Adheres To
Subject to
Needs and Features
Use Case Model
(Captures Stakeholder
needs and System
Features)
(Use Case Survey,
Use Case
specifications)
Manipulates
Automates
Logical data model
(defines the
required
information)
Visualizes
Manipulates
Visualizes
User Interface
(screens and
navigation)
Reports
Specification
(data grouping and
presentation)
Overview of SDLC and OIS Tools
Artifacts
Standard Tools
Diagramming Tools
Requirements Phase
Needs and Features




Business Assessment - As IS/To Be Business Model
Stakeholder Needs
Features
Release Planning
Use Case Model Survey



Actors
Use Case Descriptions
Use Case Diagram
Use Case Specification - Use Case Brief






Trigger
Actor
Pre conditions / Post conditions
Basic and Alternative Flows
Excludes/Includes
Activity Diagram




Page Elements and Behavior
Screen Mockups
Element Structure
Object Mapping
User Interface Specification - Use Case Detail
RequisitePro
RequisitePro
Rational Rose / Visio
RequisitePro
Rational Rose / Visio
RequisitePro
Visio /
Development Tools
Business Rules Specification
RequisitePro
Report Specification
RequisitePro




Global requirements
Report Elements
Report Interface
Report Mockup
Non-Functional Specifications









Security, Usability, Reliability, Performance
Current Technical Environment
Infrastructure, Implementation Requirements
System Support
Design Constraints
Purchased Components and Liscensing
Non-User Interfaces
Legal, Copyright and Other Notices
Applicable Standards
RequisitePro
Analysis & Design Phase
Protoype - View/Controller of MVC
Multiple Options (i.e. ICMS uses J-Developer)
Logical data model -
Erwin Data Modeler
Data Requirements and Relationships
Use Case Realization -
Rational Rose / Visio
Classes, Objects and Implementation Model
Implementation / Test / Deployment Phase
Performance Testing
Loadrunner
Attribute View of All Features
Traceability






Understand the source of requirements
Manage changes to requirements
Assess the project impact of a change in a
requirement
Assess the impact of a failure of a test on
requirements (i.e. if test fails the requirement
may not be satisfied)
Verify that all requirements of the system are
fulfilled by the implementation
Verify that the application does only what it was
intended to do
Traceability Tree
Stakeholder Need
(STN)
Trace to
Features
(FEAT)
Trace to
Use Case
(UC)
Trace to
Business Rule
(BR)
Trace to
Report
(RPT)
Trace to
Non-Functional
(NF)
Trace to
User Interface
(UI)













Security
Usability
Reliability
Performance
Current Technical Environment
Infrastructure Requirements
Implementation Requirements
System Support
Design Constraints
Purchased Components and
Licensing requirements
Non-User Interfaces
Legal, Copyright and Other
Notices
Applicable Standards
Traceability Matrix –
Stakeholder Needs to Features
NYSDOT Rational Tools
Implementation - 2004







Define Process-ITD Software Development
Evaluate Tools-Preliminary Evaluation of tools to implement
the SDLC. (Rational, Oracle)
Determine Scope - Define scope of initial tool purchase:
Requirements, Design, Configuration Management, Change
Management, Framework
Proof of Concept-Rational Selected for Proof of ConceptConcrete Inspection selected as POC project, bi-weekly tool
reviews
Implementation Approach-General Approach defined,
number of licenses determined
Purchase Decision - March 04
Detailed Implementation Plan
NYS DOT 2004
Rational Suite Implementation Plan

General Approach:




Provide Concept/Method training to Process Definers
Define/Adapt NYSDOT processes specific to the
phase
Configure the appropriate tool to support the
defined process
Provide Just-In-Time Training (tool & process) to
ITD Staff as project adoption occurs
Rational Optimization - 2008



An In-depth review and assessment of the
agency’s current use of Rational and related skills
The planning and implementation of an optimized
environment and usage model for Rational –
Upgrade to Version 7
Conduct enablement (e.g., workshops,
mentoring) of users of Rational products at
NYSDOT to provide knowledge transfer and selfsufficiency
• Establish a Center of Excellence for Rational
Review and Assessment of
Rational Tool Training

Survey 0f 65 staff members
• 54% Consultants
• 16% Business Analysts


100% Consultants
30% w/ formal training
• 67% Developers
• Percentages of staff w/formal training



Requisite Pro – 11%
ClearQuest – 19%
ClearCase – 14%
Current in house Tools Usage Chart
18
16
SPTIR
SNOW ICE MATERIALS
14
SITEMANAGER
SESAME
PROJECTWISE UPGRADE V8I
12
PPM SOFTWARE
Permits R03
10
PERMITS DIV LOAD RENEWAL
PCARD
8
NYSEMAIL
LATS
6
LARGE CULVERTS
ICMS
HWP
4
Ejward
Civil RTS
2
CARTEGRAPH ITS
CARS 511
0
Count of Rational
Requisite Pro
Count of Rational
ClearQuest
Count of Rational Test
Manager
Count of Rational
Functional Tester /
Robot
Count of Rational
ClearCase
Suggested Improvements in the
existing in-house Tools usage









Training and Awareness
Tool Usage should be standardized
Usage models should be developed
Create a usage model for business process modeling
No in-house expert on how to integrate all Rational Tools
Better integration of MS Project with ClearQuest
Rational ClearQuest should be configured to work better
with agile methodology
Need agile/scrum specific tools
Although Rational Rose was available earlier on in the
project for diagramming, there’s a need for a tool that
can replace the diagramming capabilities of Rational Rose
Center of Excellence for
Rational - 2009





Information and Tools
Skills Development and Mentoring
Consulting and Technical Assistance
Standards and Guidelines
Self Managing
Rational Jazz Platform - 2011





Majority of Rational Tool Set is rapidly
reaching end of support and end of life
Ability to accommodate agile development
Ability to provide true Collaboration
between developers, analysts and Project
Managers
Enhanced Project monitoring of schedules
and resources
Ability to easily generate customized
reports and dashboards