18
IBM Software Group © 2002 IBM Corporation Using Business Scenarios in the Software Development Process Mike Starkey Business Scenario Architect IBM Canada Lab

Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group

© 2002 IBM Corporation

Using Business Scenarios in the Software Development Process

Mike StarkeyBusiness Scenario ArchitectIBM Canada Lab

Page 2: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation2

Agenda

§ Why Business Scenarios?§ What is a Business Scenario?§ Understanding who is doing what?§ What is a Technical Scenario?§ Influencing the Software Development Process§ Results

Page 3: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation3

Evolution of e-business

Access Enterprise Integration On Demand

Access | Publish | Transact | Integrate Internally | Integrate Externally | Adapt Dynamically

Optimize operations

Dynamically respond to the needs of customers,

employees, partners, and suppliers

Buying not browsing

Working not surfingGet on the Net

Page 4: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation4

Why Business Scenarios?

§ Provide the context of how the products will be used§ Reduce the complexity of what developers need to consider§ Focus on solutions to customer problems rather than the “nice to have”s

Page 5: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation5

Market DynamicsFrom management of transactions to horizontal integration for

e-business on demandBuild TransactionalApplications

Develop

IntegrateApplications

PersonalizeExperiences

AutomateProcesses

…efficiency and flexibilityCollaboration with partners, suppliers…

adapt to changestrengthen relationships…

…new business models

….mergers, consolidations, acquisitions

Page 6: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation6

Evolving Business Scenarios

§ Phase 1 – Identify scenarios based on business problemRepresentative of a large number of customer solutions

Representative of a small number of large customer solutions

Addresses a number of known customer issues§ Phase 2 – Validate that they are important strategically

Review with marketing

Review with architects§ Phase 3 – Identify architectural issues in products

Prototype enough of the scenario to drive out architectural issues

Identify line items for products§ Phase 4 – Ensure scenario can be implemented

Test scenario by implementing to ensure it works

Page 7: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation7

What is a Business Scenario

§ Business Scenario (revenue potential, customer profile, business pains, etc.)Business Use Cases

Steps (business role, duration, description)Technical Solution (architecture, technical issues, existing infrastructure, etc.)

Technical Scenarios (products, components, design, etc.)Technical Use Cases (views)

Steps (technical role, duration, description)Line Items

Page 8: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation8

Sample Business Scenarios

Private Exchange Scenario ObjectiveProvide a one-stop shopping exchange for a set of suppliers and buyers by making product information available to the exchange participants

Customer BenefitsReduce costs associated with multiple manual data entry processesImprove quality/accuracy of product informationReduce cycle time to get product information to the market -- including new products

Customer Loyalty Scenario Objective

Aggregate the customer view across the total portfolio to provide consistent support/serviceProvide customer access anywhere and anytime....clicks & mortar

Customer BenefitsImprove profitability by maintaining customer base & increasing number of servicesIncrease customer service & marketshare

Mergers & Acquisitions Scenario ObjectiveExpand market opportunity by acquiring a channel to the web. Must increase profitability by reducing infrastructure costs.

Customer Benefits:Create a single, complete view for each customer.Quickly converge administration processes of acquired companies.Minimize the impact of convergence and costs on IT infrastructure.

Experiencing the customer lifecycle

product install

solution development

solution test

production test

production deploymentsolution

management

solution migration

Page 9: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation9

Business Scenario

Customer Centre Direct channel Agent channel Other channels

Single Admin Process

Auto Home Building

LGI Products

Auto

DirectCom Products

LGI Customers DirectComCustomers

Claims Customer Policy Admin

Lord General Insurance (LGI) acquiring DirectCar for access to its successful web channel operations and for its relevant IT skills. LGI needs to quickly consolidate the customer records and policy information to enable a single face to the customer and improved target marketing

Page 10: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation10

Who is doing what

Claim System

Claims Payment

Claims Handling

Claim System

Claims Payment

Claims Handling

In-force

system

New Business system

Policy Admin System

Agent

Customer Call Centre

Direct

Customer contactService Provider

Service Provider

Admin

S/vice Providers Payment system

Billing/Payment System

Content Manager

Finance

Service Provider

Agent CustomerCustomer call centre

ClaimsHandler

Accountant

Policy Handler

Salesman

System Programmer

System Administrator

AD Developer

System Analyst

Install/confgi/PD

solution build/test

performance/trends

security/admin

generate customer Quotes/Policies/claims manage claim, service

providers, payment

generate /monitor sales campaign

manage policy, billing, risk

manage reserves,,billings, cash flow,

requests for servicemonitor service level

BusinessAnalyst

business flowdesign

Page 11: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation11

Business Use Case: Investigate Claim

Check 3rd party and Assessor report ( Assumed in Auto to be unstructured), although standard assessor reports could be sent via EDI

Claims Handler

4

Send externally for detailed Assessment of damage Claims Handler

3

Check previous claim history - > Alert-. Claims exceeding $30000 NOTE: other external 3rd party checks could include - A Medical Examination,- An Assessment for another vehicle in addition to the policy holders vehicle- A Legal document from a solicitor- If claimant stated police were involved , it may have been necessary to request a police reportAll checks should be completed before moving to the next activityl

Claims Handler

2

Claim Handler logs into the Business Process Management system and is presented with a view of claims in a ‘Valid Claim’ status. The Claim Handler selects a Claim and retrieves details for that Claim

Claims Handler

1

Step DescriptionRoleStep

The Claims Handler requests and collates various sources of information pertaining to the claim from internal and external sources

Page 12: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation12

Today’s Enterprise IT Environment

The role of modern middleware is to integrate and simplify

Intranets

ValueChainExtranets

Databases

Customers

Transactions

Internet

Networks

Legacy Systems and Applications

IT environments are becoming increasingly heterogeneous and complex.

Page 13: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation13

Technical Roles

Technical user roles:I. Business Analysis

Business AnalystII. Up & Running

Product InstallerIII. Solution Development & Deployment

Solution ArchitectSecurity ArchitectApplication DeveloperUser Interface DeveloperInformation DeveloperInternal Tools DeveloperSolution IntegratorSolution Tester Solution Deployer

IV. System Administration & OperationSystem Administrator

Page 14: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation14

Technical Use Case: Production Environment install

Install solutions/products on the production environmentSolution Deployer

4

Apply any urgent quickfixes and testSolution Deployer

5

Prepare to back out to previous level if problems occur Solution Deployer

6

Apply prereqs and testSolution Deployer

3

Review hardware and software levels across the entire productionenvironment

Systems Administrator, Solution Deployer

2

Back up existing software and dataSolution Deployer

1

Step DescriptionRoleStep

The production environment is sacred. Therefore the products need to be installed and backed out quickly if they cause any adverse impact on existing products or solutions

Page 15: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation15

Influencing the Software Development Process

§ Adding business use cases to the product “theme” documents § Adding use cases to the component design documents§ Building samples around business scenarios§ Building testcases around technical use cases

§ Product architects using business scenarios to make tactical decisions so that they fit with strategy

§ Use business scenarios to prototype new technologies

§ Use business scenarios to incrementally add new component features

Page 16: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation16

An Example of how it Helps Development

§ Business use caseOn every logon, the user’s information is displayed to the user. They can change it if

it is incorrect.

§ Technical use caseRetrieve the data for the customer from the “Customer” Entity EJB

§ Problem:Developer focussing on how to optimize ejbCreate implementation

However, scenario shows following usage pattern:

ejbCreate called 4% of the timeejbLoad called 70% of the timeejbStore called 25% of the timeejbDelete called 1% of the time

Therefore, based on scenario, developer should focus on optmization mechanism for ejbLoad rather than ejbCreate

Page 17: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation17

Results

§ Changing the development culture to focus on customer solutions§ Helping make the “is-it-nice” or “is-it-necessary” kind of decisions§ More general knowledge of what customers are trying to do with our

products

§ Interesting side-effectsCustomers interested in the process

Using business scenarios to build their own platformCustomers interested in how their scenarios map to the ones we are

addressing in development (ie. Coverage)

Page 18: Using Business Scenarios in the Software Development Process · 2003-02-11 · Influencing the Software Development Process §Adding business use cases to the product “theme”

IBM Software Group | WebSphere software

© 2002 IBM Corporation18

Providing e-business on-demand

Business Process Integration

Access On Demand

Employees

Customers Partners

SuppliersBusiness Portals

Application Connectivity

Open Services Infrastructure Enterprise Modernization

Host Environment

Developers

Open SourceCommunity

ApplicationDevelopment