QL

Question 1

Existing Features:

Answer 1

• Login with numeric Passcode and Logout
• Account Summary for multiple accounts as viewed in OLB
• Mini Statement for all accounts as viewed and available in OLB
• Account to Account Transfers
• Bill Payments
• Third Party Payments
• Credit Card Payments
• Credit Card Summary Details
• P2P Payments (RBS / NatWest to any RBSG customer except Ulster RoI)
• Alerts
• Mobile Phone Top Up (MPTU)
• ATM and Bank Branch Locators (Near Me)
• More – Change Passcode, Help, FAQs

Question 2

Alliance P2P Specific Features

Answer 2

• Branded iPhone clients for RBS and NatWest.
• Branded Blackberry clients for RBS and NatWest.
• Branded Android clients for RBS and NatWest.
• Fresh Installation and Upgrade for QL clients on RBS and NW only.
• Set-Up includes new set of Terms and Conditions and Notice of Variation(NoV)
• RBS/NatWest app users can make P2P payments to any UK mobile number.
• MI Reports
• Copy Changes, Error Matrix for P2P

Question 3

agile methodology principles

Answer 3

• Deliver early - Working software produces tangible results the customer can ‘touch and feel’.
• Capture feedback – Get feedback fast and incorporate appropriate changes quickly.
• Incremental change – Put a stake in the ground and evolves the design over time.
• Embrace change - The business environment changes as a project progresses.
• Keep it simple - Keep the solution simple. Don’t depict features that are not required today.
• Keep an eye on the future - A solution should be robust to accommodate multiple options.
• Identify and remove waste - Eliminate wasteful activities that add little or no value.
• Create partnerships - Customers have a seat at our table. They are active participants.
• Travel light - Documentation is required but we are not artifact-driven.

Question 4

MLS

Answer 4

monitise® Location Server

Question 5

MFS

Answer 5

monitise® Feedback Server

Question 6

REF

Answer 6

Reference Environment

Question 7

UBN

Answer 7

Ulster Bank

Question 8

QL

Answer 8

Quantum Leap

Question 9

RBSG

Answer 9

RBS and Group

Question 10

• RBSG QL Customers

Answer 10

Recipient is a RBSG QL registered customer (Except the Ulster ROI brand).

Question 11

• Visa Personal Payments (VPP) registered customer

Answer 11

Recipient is a registered VPP customer with atleast one VISA card.

Question 12

• Non-VPP registered customer

Answer 12

The recipient is not VPP customer and has no RBSG mobile app registered.

Question 13

2.2 Features Out of Scope

Answer 13

• iPad specific clients for Alliance P2P are not in-scope. However, existing iPad clients (post upgrade) will continue to work as expected.
• Brands NWO, IOM, Ulster Bank North (UBN) and Ulster Bank RoI are being excluded as part of this release.
• Spending Trend Analysis
• Tiered Security for services
• Apple Push notification used as alert bearer
• Alert inbox (required as part of move to push notifications)
• Integration with RBS Messaging platform

Question 14

Test iteration

Answer 14

• Initial requirement analysis and walkthrough of the specification documents
• Generation of Test Plan document.
• Test Data Requirements
• Preparation of Test Scripts
• Test Execution (Server-side and Client-side)
• Defect validation and re-testing.
• Generation of test completion report

Question 15

these tests will be planned with following methodology

Answer 15

1. Focus on the User Interface being designed for the current phase of the release.
2. Identify the “critical” functionalities that could prevent the user from using the Alliance - P2P functionality if a bug was found. (This bug would be of high severity). Such critical functionality will be determined by close interactions within iteration team/ stake holders and our experiences from Quantum Leap and Payments application testing.
3. Design test coverage scenarios for the functionality in-scope.
4. Time box testing effort required to prioritising tests that would suit a given iteration and thereby execute these tests.
5. Any re-prioritized/ unscheduled tests can be planned during regression testing phase.

Question 16

3.1 Smoke/Sanity Testing

Answer 16

Sanity testing will be carried out on all new client builds, server releases that may be deployed on to the functional test environment.

Question 17

3.1 Smoke/Sanity Testing

Answer 17

This is an initial test to determine if the build is fit for further in-depth functional testing, by executing the main user flows of the application. If the sanity tests do not pass, the build will be rejected.

Question 18

3.2 Functional Testing

Answer 18

Test cases for functional testing are based on the use cases and user flows derived from the proposition document and product demo. This section would be updated if any further supporting documents are received which may help in designing/ updating test cases.
All tests will be executed manually within Quality Centre. A risk-based test approach may be adopted in keeping with the timelines for ST completion. This will involve prioritizing tests that are most important.
The Alliance P2P functionality will be built on QL, Payments, & P2P application principles and architecture; we may re-use some test scripts that were written for Quantum Leap, Payments, and P2P as may be deemed necessary.
Test cases once complete, will be reviewed, updated and prioritized to suit the testing requirements for the given iteration.

Question 19

3.5 System Integration Testing

Answer 19

monitise® functional test environment will be integrated with RBS UQ environment from the beginning of this test phase. There are new API’s developed as part of the Alliance P2P project.
Web services will be verified using SOAP UI scripts.

Question 20

3.8.1 Performance Testing

Answer 20

Performance testing may be undertaken by an independent Performance Test Team. This is not within the scope of system testing.

Question 21

3.8.2 Security and Penetration testing

Answer 21

Security and Penetration tests are out of scope for monitise® system test team; they may be planned by 3rd parties identified by monitise® / RBS.

Question 22

3.9 User acceptance Tests (UAT)

Answer 22

User acceptance tests will be planned and conducted by external / RBS test team. UAT approach and plans may be provided by RBS UAT team.
monitise® Quality Centre Access will be provided to the UAT team and they can raise and manage defects within QC as part of UAT test phase. There must be agreement between RBS and their chosen UAT partner to align defect states, priorities with those configured in QC.

Question 23

6.1 System Test Environments

Answer 23

monitise® will test the Alliance P2P application on the Functional Test environment FT15 / FT47 and MLS Server (FT18) for system testing.
monitise® reference environments will be used for Regression and UAT related tests.
The Alliance P2P functional test environment(s) will be integrated with RBS UQ environment (RBS e-banking system). The VISA Enterprise (VE) system may not be connected to the FT environments. This may be stubbed out on FT.

Question 24

6.1.1 Test Environment configuration

Answer 24

Operator Access Vodafone, O2, T-Mobile, Orange
Handset Manufacturers sampled Apple
Natasha Latest version
MBlox Connection MBlox SMS and Billing System (SMPP or XML connection)
Simulator Internal Test Simi (for developers) and Lexcel Simi (for testers)
Test Secure URL (FT15)
Test Secure URL (FT47)
Test Secure URL (FT18) http://test02.monitise.eu/

Question 25

4.5.2 Test Completion Report

Answer 25

* Overall test execution summary for every round of testing * Metrics on functionality based execution * Defect progress status * Active Defect progress by date * Total defects * Defects to be carried forward in the next iteration.

Question 26

monitise® test environment

Answer 26

(FT15 / FT47).

Question 27

the severity levels

Answer 27

``` 0 – Showstopper 1 - Customer Facing 1 – Critical 2 – Serious 3 – High 4 – Cosmetic 5 – Query ```

Question 28

0 – Showstopper

Answer 28

Major impact on the security or functionality of the product. Outage. Product cannot be released.

Question 29

1 - Customer Facing

Answer 29

Impact on the customer experience of the product. System may be functioning correctly, however, areas have a negative effect on customer perception of the product’s quality Product cannot be released. The following are examples of customer facing defects: 1- Spelling or grammatical errors 2- Incorrect error messages 3- Incorrect branding 4- Special characters not encoded properly 5- Missing banners 6- Code elements line null appearing in messages 7- Duplicate / missing words 8- Lack of region specific verbiage

Question 30

1 – Critical

Answer 30

Impact on major functionality; other areas work. Partially functional system. Product cannot be released.

Question 31

2 – Serious

Answer 31

Impact on major functionality. Workarounds exist to allow user to perform desired action. Impact on minor functions. Product can be released.

Question 32

3 – High

Answer 32

Impact on minor functionality. Impact on non-customer facing functions, with workarounds. Product can be released.

Question 33

4 – Cosmetic

Answer 33

Cosmetic defects not affecting functionality or security. | Product can be released.

Question 34

5 – Query

Answer 34

Queries on documentation and/or functionality.

Question 35

Test approach

Answer 35

3. 1 Smoke/Sanity Testing 11 3. 2 Functional Testing 12 3. 2.1 Out of scope for functional testing: 12 3. 3 Web Browser Compatibility Testing 13 3. 4 GUI Testing 13 3. 5 System Integration Testing 13 3. 6 Operator Compatibility Testing 13 3. 6 Device Compatibility Testing 13 3. 7.1 iOS Device Test List 14 3. 8 Non functional testing 14 3. 8.1 Performance Testing 14 3. 8.2 Security and Penetration testing 14 3. 9 User acceptance Tests (UAT) 14

Question 36

getRSAPublicKey

Answer 36

``` getRequestMethod getRequestQueryString isResponseValid offlineModeResponse parseResponse ```

Question 37

MRSAPIOperationSettings

Answer 37

serviceURL

Question 38

Environment | EnvironmentManager_Shared

Answer 38

*serverHost; *userAgent; *apiVersion; timeoutInterval; secureEnvironment; *mlsServerHost; *feedbackServiceHost; *authenticationType;

Question 39

local variable

Answer 39

Make sure the local variable name describes the value that it holds.

Question 40

param

Answer 40

It’s good to start the internal part of the parameter name with the word “param”.

Question 41

MRS_LIBRARY_OFFLINE_MODE

Answer 41

GCC_PREPROCESSOR_DEFINITIONS

Question 42

LoadingScreen_iPhone

Answer 42

+ (void) showWithText:(NSString *)paramText; | + (void) hideIfShown;

Question 43

MRSAPIManagerDelegate

Answer 43

optional Finished:(BOOL) paramSuccess withError:(MRSError *) paramError;

Question 44

quantum

Answer 44

the minimum amount of any physical entity involved in an interaction

Question 45

VISA

Answer 45

It facilitates electronic funds transfers throughout the world, most commonly through Visa-branded credit card and debit cards.[2] Visa does not issue cards, extend credit or set rates and fees for consumers; rather, Visa provides financial institutions with Visa-branded payment products that they then use to offer credit, debit, prepaid and cash-access programs to their customers

Question 46

security/session

Answer 46

security/session

Question 47

FT environment

Answer 47

test01.monitise.eu

Question 48

internationalCode

Answer 48

enrollmentManager