Requirements Across the Software Development Lifecycle Joel Pech, jlpechus'ibm'com

1
Requirements Across the Software Development
LifecycleJoel Pech, jlpech_at_us.ibm.com
2
The challenge Poor visibility, lack of cohesion
across business and technology domains
Business View

• Poor visibility and governanceover IT
  investments
• Lack of actionable information
• Blind decision-making

ApplicationDevelopment View
OperationsView
BusinessAnalysts

• Overwhelming complexity
• Relentless time-to-market pressure
• Uncontrolled change

• Inadequate service levels
• Inability to rapidly deploy applications
• Complex, multi-tier operating environments

ApplicationDevelopers
Operations
3
The solution Breaking down the silosA shared
view of the development lifecycle
Business View

• Clear view of technology ROI
• Top-down and bottom-up visibility into technology
  projects
• Objective decision-making support

ApplicationDevelopment View
OperationsView
BusinessAnalysts

• Rapid application development and deployment
• Improved collaboration
• Asset reuse

• Improved service and quality compliance
• Predictable deployments
• Accelerated diagnosis and repair

ApplicationDevelopers
Operations
4
IBM Software Development Platform
Analyst
Architect
Developer
Tester
Deployment Manager
Model, simulate, assemble,and monitor
processes. Manage requirements
Rapidly construct, transform, integrateand
generate code
Provision, configure, tune and troubleshoot
applications
Design, create, and execute tests
Visuallymodel applications and data

• Follow a common process
• Manage and measure projects and portfolios
• Manage requirements

• Manage changeand assets
• Manage quality

Project Manager

• Align investments with business objectives
• Analyze and monitor project portfolios

Executive
5
Requirements Things The Dev Team Needs to Know
Requirements
Marketing
Users
Dev Team
Legal
System
Architects
Customer/business
Businessrules
Designers
The system
Constraints
Developers
Interfaces
Testers
Data
Business processes
Technicaldetails
Gov't
6
Requirements Errors Cost A Lot
200
50
Relative Cost to Repair
20
10
5
1-2
0
Acceptance Test
Unit Test
Coding
Design
Analysis
Maintenance
Stage in which Requirements Error Is Discovered
7
The Software Development Lifecycle
8
The Business and Technology Chasm Still Exists
Business Needs
Application of Technology

• Understanding the business identifies
  opportunities and requirements for systems
• Without business modeling you might pick the
  wrong piece of the business to automate
• The business model helps you identify system use
  cases

9
Business Modeling Workflow in RUP

• Workflow details
• Assess business status
• Describe current business
• Identify Business processes
• Refine Business process definitions
• Design business process realizations
• Refine Roles and responsibilities
• Explore process automation
• Develop a domain model

10
Business Modeling Identifies Software Requirements

• Explore Process Automation
• Outputs are sketches of
• System use case model
• Supplementary specification
• Analysis model

11
What is a Business Model?

• One or more diagrams of a business or
  organization showing
• Business processes
• Tasks
• Resources
• Services
• Entities
• Business models can be static or dynamic

12
Value of Business Modeling for Software
Development

• Ensure stakeholders have a common understanding
  of how the business works
• Knowledge doesnt walk out the door when staff
  leaves
• Understand current problems in the business and
  identify improvement potentials 
• Derive the business requirements needed to
  justify improvements
• Ensure software teams pay more than superficial
  attention to business needs

13
Two Business Modeling Techniques
RSA/RSM (UML)
WBI Modeler (BPMN)
Architecture/ Execution Model
Process/Operation Model
UML Business Model
UML Use Case Model
Business Process Model
UML Class Model
Business Object
UML Data, XML, SQL Model
Business Data
Business Services
UML Interface/Service Model
14
Introducing WebSphere Business Integration Modeler

• Realistic visual representations and analysis of
  the way your organization works
• Fully Integrated
• Integrated with the entire WBI development
  tooling
• Animated Simulations
• Identify bottlenecks and watch what-if scenarios
• Powerful Analysis
• Understand detailed time/cost metrics of the
  process 
• Built-in Reporting
• Display information for different purposes and
  audience
• Eclipse based UI

15
WebSphere Business Integration Modeler
Business process diagram
Model explorer
16
Rational Software Architect/Modeler UML Business
Modeling (and more)
Business use case diagram
Model explorer
17
Mapping Between WBI Modeler and RSA/RSM
18
Process Diagrams lt--gt Activity Diagrams
RSA
Actions
Tasks
The actions are candidate system use cases
Workflow
WBI Modeler
19
Tasks lt--gt Business Worker Operations
WBI Modeler
RSA
Tasks
The operations of the business worker are
candidate system use cases
20
The Software Development Lifecycle
21
Requirements in RUP
Problem Space
Needs
Solution Space
Features
Software Requirements (Use Cases)
22
Business Models and Requirements
Entities
Tasks
Business processes
Design
23
Requirements in RUP - Another View
Vision Document - Needs and Features
Requirements Attributes
Supplementary Specification Non-functional
Requirements
Use Cases Functional Requirements
24
What is a Use Case?

• Use cases are shown in UML diagrams

• Use cases are described in text

25
Use Case Diagram - The Big Picture
26
Introducing IBM Rational RequisitePro

• A software tool for
• Managing lists of requirements
• Use cases
• Other types of requirements
• Keeping information about the requirements -
  attributes
• Cross referencing the requirements to each other
  - traceability
• Making sure the requirements are secure
• Finding the requirements once you have them in
  the tool
• Formatting and presenting the requirements to
  others

27
Managing Requirements with Rational RequisitePro

• Keep your team on track

Microsoft Word
Web

• 3 interfaces - work the way you want
• Document-centric or database-centric - your choice

28
RequisitePro - Word Interface and Windows Client
Word interface to Rational RequisitePro
Client interface to Rational RequisitePro
29
IBM Rational Software Architect/Modeler (RSA/RSM)
Use case diagrams are managed in RSA/RSM
30
RSA/RSM and RequisitePro Are Integrated
RequisitePro requirements explorer
RequisitePro View
31
Requirements Across the Lifecycle
Yoursystem
Business Models
Test Cases
Use Cases and supplementary requirements
32
For More Information - IBM developerWorks
http//www.ibm.com/developerworks/rational/
33

• Thank You
• Questions?