Solutions Design - where systems become components

1
Solutions Design - where systems become
components

• Presented by Alan Gauld
• BT Exact

2
Solution Design

• Business Problems
• Product Launch
• Regulatory Requirements
• Operational difficulties
• Systems Solutions
• End to end view of product or scenario
• Feasibility, architecture and infrastructure
• Design authority safeguarding the strategy

3
What are the Qualifications?

• Understand the business and its needs
• strategy, market position, regulation
• Understand the existing systems
• Legacy COBOL/DB2 Mainframe VAX/VMS
• Understand whats possible now
• XP, UNIX, Linux, Web, PDAs, SOA, ESB
• Understand the glue
• CORBA, J2EE, .NET, SOAP, XML, ftp, Robots

4
A Case Study - Commitment Plus

• Aimed at medium-large corporate customers
• Customer agrees to spend amount X over a range of
  products
• Discount proportional to X is applied to all
  products in the range
• If X not spent penalties are applied

5
Primary Tools

• BT use UML supplemented with DFDs and ERDs.
• Primary diagram is Use Case diagram
• Identifies system scope and functions
• Static design uses Component Diagrams
• shows the structure of the solution
• Dynamic uses Sequence Diagrams
• supplemented by extended OOSE notation (see
  later)
• Finally need Deployment diagram
• Need Production, Fail-over, Training and
  Develop/Test
• Supplemented as necessary
• Activity and State charts, DFD/ERD for legacy
• Occasionally Class and Object diagrams

6
The Use Case Diagram
Marketing
Swift
Product Manager
Sales
Salesman
CSS
Fulfilment
Bill
Customer
CFB
Billing Clerk
Maintain
Cease
Measure
Bonussing
7
Enhanced Sequence Diagram(I)
8
Enhanced Sequence Diagram(II)
Actor, either other system or human user
performing a role
Timer. Used to initiate batch jobs or data
transfers
9
Enhanced Sequence Diagram(III)
Monthly
Monitor
Web
Salesman
Customer
10
C-Plus Deployment Design
Swift
CPWS
PC
CPAS
CSS
CPMIS
CFB
Bonussing
11
Solutions Design

• A different perspective on systems
• Success measured on least change
• Can involve very large systems
• Mix of business and technical knowledge
• Ability to communicate and influence
• One mans Design is anothers Requirement

12
And a final warning.

• Theres always something to trip you up!