TSS01G Case Study Exercise 2: Instructions

Learning Objective:
Be able to navigate through and apply the essential aspects of TeamSD: Activity: EXPLORE
Options and Approach

From the Method:

“The purpose of this pre-sale solution design EXPLORE Activity is to identify the key client requirements,
develop a vision of the solution and assess the probability of a successful project from a client and IBM
point of view. The team EXPLORES with the client the options that offer what the client wants and values
and recommends the best. The team demonstrates IBM unique value, showing how we go beyond the
competition to offer the value the client wants. The progress indicator for this activity is a qualified
opportunity.”
Actors
Terence Liu, Maple Bank VP of Architecture
Robert Albany, IBM CTA for Maple Bank. Robert has been trying to get the Bank to take a look at IBM’s
Mobile products and services for some time but a competitor was involved in the first mobile banking
solution.
Shelly Berg is the Mobile Architect who will do the detailed design for the solution. She has recently
completed a very successful Mobile App for AirNova which is a public reference. Shelly does not have
existing relationships at Maple Bank and will be teaming with Robert on the Solution Design.
Background
Since Exercise 1, the IBM Client team has validated the opportunity and confirmed that GBS will lead the
Proposal, with insight on technology directions in Mobile from Software and GTS teams.
Robert has already accompanied Terence Liu to two IBM conferences where the IBM Mobile platform and
development capabilities were discussed. But, Robert Client Technical Architect (CTA) has to address
Terence Liu’s scepticism about using IBM.
Activities to be performed in your teams
1. Read inputs to Exercise 2 – see Module 2 slides Intro to Exercise 2
• Inputs to Exercise 2
1. e-mail from IBM Client Technical Architect
2. Architecture Standards (ARC 310)
• ‘Model’ Solution to Exercise 1 – (the slides in the ppt following Student Presentation
section)
1. Project Definition (ENG 343) (including view of requirements)
701890695.docx Page 1 of 4
© Copyright IBM Corporation 2017
 2. Business Direction (BUS 411)
3. Opportunity Plan (ART 0612)
2. Prepare for the interview with Terence Liu, VP, Architecture, Maple Bank. Listen to Terence’s
concerns and consider the capabilities that IBM can bring to gain his support.
• (Or, if these are provided to you, read the notes from interview with Terence Liu)
3. Search for Assets to accelerate this Solution Design and prepare a Candidate Asset List
using:
• Solution Navigator on Lighthouse: https://w3-03.ibm.com/services/lighthouse/solution-
navigator
• Other sources
1. TeamSD – where to get help http://w3-03.ibm.com/support/tsdesign/help.html

2. Asset Job Aid for Architects: https://w3-connections.ibm.com/wikis/home?lang=en-

us#!/wiki/The%20Asset%20Module%20-%20Job%20Aid/page/Asset%20Module%20-%20Job
%20Aid

3. Solution Gateway
https://w3-03.sso.ibm.com/services/practitionerportal/assethub/production/
sacindex.jsp
4. Expert Councils http://ibm.biz/BdipmT
5. Global Solutions Architecture Repository:
https://w3.gsar.ibm.com/services/gsar/gsar.xhtml
4. Use the asset(s), the inputs to Exercise 2, your notes from Terence Liu interview and the
Team Solution Design method to help you to create the following Team Solution Design work
products:
1. Candidate Asset List (ENG 100)
2. Architecture Overview (ART 0512)
3. Opportunity Plan (ART 0612) - updated
4. Architectural Decisions (ART 0513) – two to three key decisions that you have made as a
team
5. System Context (APP 011) – first draft
5. Please share your team outputs by placing them in the Box folder for your corresponding
Team e.g. Breakout Session 1 = Team 1
6. Notes:

 Do not spend your time making the work products pretty.

 Do spend your time on understanding the TeamSD ‘process’.

 One team will be selected to present their new created Work Products at the start of the next
module

701890695.docx Page 2 of 4
© Copyright IBM Corporation 2017
Exercise Inputs
E-mail from IBM Client Technical Architect
Hi Shelly
As I think you have heard from Heather, we have an exciting and challenging mobile opportunity at Maple
Bank.
I’m meeting with Terence Liu in two days and we’d like you to join me for that discussion – so that you get
some direction sense of the client challenge and the issues they have encountered with their current mobile
platform.
I’d like you to share with Terence your experience in delivering the mobile app for AirNova: the delivery
approach, architecture and the resulting customer usage and feedback.
We need to make Terence comfortable with IBM as a mobile partner as he is such an important influence
to the CIO. We need him as an ally both for a successful proposal and for delivery.
Let’s meet to prepare. I’ll give you more background on Maple Bank’s architecture standards and we can
prepare the questions that we want to ask on the current technical environment for mobile: tools,
middleware, infrastructure and integration.
Rob

Project Definition
Project Description
 Business problem: Maple Bank wants to be regarded as the leading Mobile Banking
provider in its markets, but its current mobile banking app has poor reviews and usage.
 Functions Needed:
− Sign-in / User Authentication
− My Accounts and Transaction History
− Account Details
− Account Transfer
− Bill Payment
− EMT – Electronic Money Transfer
− Mobile Appointment Booking
− Alerts Setting
− Branch Locator
− Device support – specified OS levels on iPhone, Android, Blackberry

Project Approach:
 Based on UMF AD 2.0 plus introduce Incremental Delivery during Requirements, Design, Build
and DIT
 Phased Implementation based on Devices
− Roll-out iPhone  Mobile Web  Android  BlackBerry
Key Sponsors, Stakeholders and Success Criteria:
 Arvind Kumar: key decision maker, accountable for Maple Bank mobile channel solutions
 Paul Powell: Key approver
701890695.docx Page 3 of 4
© Copyright IBM Corporation 2017
  Terence Liu: Key influencer
Plan for Communications, Meetings:
 Prioritize Requirement Modules and conduct workshops with all key stakeholders
 Establish Design Counsel sessions for reviews, decisions and acceptance

Architecture Standards (ARC310) – Maple Bank

 Open Standards: HTML5, JavaScript, REST/JSON
 Dojo mobile framework for mobile app – to support responsive design
 Single code base to support mobile app and mobile web
 Application architecture should maximize reuse
 Client code should be modular and separate style sheets from templates/widgets and
controllers/data access
 Minimize use of native code
 Readiness of this application to support a multi-channel solution architecture that separates the UI
layer from services (e.g. mobile, tablet, web).

Client Requirements
Functional Requirements
 High Level view – from Project Definition – Project Description
 Sign-in / User Authentication
 My Accounts and Transaction History
 Account Details
 Account Transfer
 Bill Payment
 EMT – Electronic Money Transfer
 Mobile Appointment Booking
 Alerts Setting
 Branch Locator
 Device support – specified OS levels on iPhone, Android, Blackberry

Non-Functional Requirements
 Infrastructure sizing and deployment a client responsibility
 But see Architecture Decisions that are related to Availability and Maintainability
 And for a mobile solution, performance is always crucial

701890695.docx Page 4 of 4
© Copyright IBM Corporation 2017