Your SlideShare is downloading. ×
0
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Adelaide Bank
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adelaide Bank

471

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
471
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Analysis – with Solution Designer – QA can get involved (making recommendations), depending on project. This is where QA would start thinking about how we are going to test. Development – developer makes necessary changes and unit tests Testing – QA test system changes – UAT ensures changes meet business requirements
  • Sign off for developer is needed for CAB Hard copies are kept for letter changes, etc.
  • All used for mainframe development, however: QUAL – Q9 used for loan testing – which involves Tower software amongst others (Fast Track, etc.) USER – U4 dedicated for OLB (programming outsourced to Sandstone) USER – U9 dedicated to UAT for Loan Software Applications (when moved from Q9)
  • Request for Change - logged on CAB site by change owner Change Advisory Board
  • Transcript

    • 1. Adelaide Bank IT Solution Delivery Presentation to Adelaide University Computer Science Students August 2007
    • 2. Agenda <ul><li>Overview of Adelaide Bank </li></ul><ul><li>Structure of IS and Projects Office </li></ul><ul><li>ABL Systems and Technologies </li></ul><ul><li>Overview of ABL Project Methodology / SDLC </li></ul><ul><li>Business Analysis </li></ul><ul><li>Solution Design </li></ul><ul><li>Development </li></ul><ul><li>Testing </li></ul><ul><li>Questions </li></ul>
    • 3.  
    • 4. Division: Information Services Department: Information Services General Manager Information Services Senior Manager Infrastructure & Services <ul><li>Service Desk </li></ul><ul><li>Service Support </li></ul><ul><li>Computer Operations </li></ul><ul><li>Capacity & Availability Planning </li></ul><ul><li>Networks </li></ul><ul><li>Windows </li></ul><ul><li>Mainframe </li></ul><ul><li>Planning & Architecture </li></ul><ul><li>IS Finance & Asset Management </li></ul><ul><li>IS HR </li></ul><ul><li>Executive Assistant </li></ul><ul><li>Quality Assurance </li></ul><ul><li>Technical QA </li></ul><ul><li>Server Development </li></ul><ul><li>Mainframe Development </li></ul><ul><li>Application Support (pool) </li></ul><ul><li>Margin Lending Development </li></ul><ul><li>Solution Design </li></ul>Senior Manager Solution Delivery Senior Manager IS Governance and Security Office of General Manager <ul><li>Information Security </li></ul><ul><li>IS Governance </li></ul><ul><li>Audit Liaison </li></ul><ul><li>IS BCP & Service Continuity </li></ul><ul><li>Risk Management </li></ul><ul><li>Regulatory Compliance </li></ul><ul><li>Continuous Improvement & Reporting </li></ul><ul><li>Policies & procedures </li></ul>FTE: Owner: Rob McKeon Vesion:1 Date:09/05 /07
    • 5. Senior Manager Solution Delivery Business Lending & Wealth - Solution Delivery Manager Design and Infrastructure Lead Server and Mocom Lead Test Lead Mortgage – Solution Delivery Manager Retail – Solution Delivery Manager Corporate - Solution Delivery Manager Application Support Lead <ul><li>Designers </li></ul><ul><li>Solution Architect </li></ul><ul><li>Systems Analyst </li></ul>Mainframe Developers Analyst Programmer & Programmer <ul><li>Testing </li></ul><ul><li>Test Designer </li></ul><ul><li>Testing Analyst </li></ul>Infrastructure Server Developers Analyst Programmer & Programmer Mainframe Lead
    • 6. Division: Group Strategy Department: Business Transformation General Manager Business Transformation Manager – Project Managers <ul><li>Senior Project Managers </li></ul><ul><li>Project Managers </li></ul><ul><li>Senior Business Analysts </li></ul><ul><li>Business Analysts </li></ul><ul><li>Business Transformation Managers </li></ul>Business Strategy Manager – Business Analysts FTE: Owner: Rob McKeon Vesion:1 Date:09/05 /07
    • 7. ABL Technology <ul><li>Mainframe </li></ul><ul><li>Windows Servers </li></ul><ul><li>Windows PCs/Laptops </li></ul><ul><li>Databases </li></ul><ul><ul><li>Datacom, SQL Server, Access </li></ul></ul><ul><li>Programming Languages </li></ul><ul><ul><li>.Net , CICS/Cobol, Microfocus Cobol </li></ul></ul><ul><li>Applications </li></ul><ul><ul><li>In-house, third party developed, COTS, hybrid </li></ul></ul>
    • 8. ABL Applications mapped to Business Capabilities
    • 9. ABL Applications
    • 10. Project Document Checklist (PDC) Adelaide Bank Project Methodology / Systems Development Lifecycle (SDLC) Business Case (BC) Project Statement (PS) Risk & Issue Register (RIR), Project Change Request (PCR) Program &/or Project Status Report (PSR), Meeting Agenda (MA), Meeting Minutes (MM) Estimation Worksheet Functional Specification Document (FSD) Start-Up Analysis Development Closure Implementation Concept Concept Estimate +100%, -50% Planning Estimate +50%, -25% Detailed Estimate +20%, -10% Concept Brief (CB) Admin Key Project Documents IS Documents Business Requirements Document (BRD) Business Implementation Plan (BIP) Post Imp’n Review (PIR) UAT Testing UAT Test Scripts (UATS) & SAT Scripts Closing Report (CR) Appendix – Post Imp’n Issue Register Production Acceptance Document (PAD) QA Test Plan QA Final Report Training & Comms Plan (TCP) Project Release Doc (PRD) SAT Testing IS Implementation Plan (feeds into BIP) UAT Test Plan (UATP) QA Problem Register Filename: App E_Project Document Flow_1.1.ppt Confidential to Adelaide Bank Ltd. Realised Benefits Review (BIR) PCR (to CAB with Production Status) High Level Solution Design Project Schedule (Sched) Production Acceptance Checklist
    • 11.  
    • 12. Any Questions???
    • 13. Business Analysis Heather Fitch (Senior Business Analyst)
    • 14. WHAT DOES A BUSINESS ANALYST DO? <ul><li>Understand existing process / technologies </li></ul><ul><li>Create Current State and Future State Process Maps </li></ul><ul><li>Process Re-engineering </li></ul><ul><li>Gather and Document Business Requirements </li></ul><ul><li>Liaise with developers and QA </li></ul><ul><li>UAT Plans and Scripts </li></ul><ul><li>Support UAT Testing </li></ul><ul><li>Training and Communication </li></ul><ul><li>Implementation Support </li></ul><ul><li>Site Acceptance Testing </li></ul><ul><li>Stakeholder Management (managing expectations) </li></ul><ul><li>Peer Reviews </li></ul><ul><li>Input to Project Schedule </li></ul>
    • 15. BUSINESS ANALYSIS PHASES: <ul><li>Initiation / Conceptualise (15%) </li></ul><ul><ul><li>Concept Brief / Business Case </li></ul></ul><ul><ul><li>Executive Sponsor / Scope / Case for Action / Voice of the customer </li></ul></ul><ul><li>As Is / Orient (20%) </li></ul><ul><ul><li>Understanding current business practice </li></ul></ul><ul><li>To Be / Organise (35%) </li></ul><ul><ul><li>BRD / Functional Spec </li></ul></ul><ul><li>Transformation / Convert (30%) </li></ul><ul><ul><li>Implementation / Post implementation support </li></ul></ul><ul><ul><li>Institutionalise the new way </li></ul></ul>
    • 16. BA TECHNIQUES <ul><ul><li>Benchmarking existing processes </li></ul></ul><ul><ul><li>Observe the task being completed </li></ul></ul><ul><ul><li>Interviews </li></ul></ul><ul><ul><li>Facilitation </li></ul></ul><ul><ul><ul><li>Team discussion to help those taking part to think about a particular aspect of their work and consider their experience as well as the practice of others </li></ul></ul></ul><ul><ul><li>Setting up / running workshops </li></ul></ul><ul><ul><ul><li>ensure the right participants </li></ul></ul></ul><ul><ul><ul><li>define the aim </li></ul></ul></ul><ul><ul><ul><li>take charge </li></ul></ul></ul><ul><ul><ul><li>provide an agenda (and stick to it) </li></ul></ul></ul><ul><ul><ul><li>environment – is the room conducive to meeting needs; too hot / cold; comfortable seating, white boards, brown paper, markers, post it notes, layout of room etc…. </li></ul></ul></ul>
    • 17. BA TECHNIQUES CONT…. <ul><ul><li>Informal coffee sessions </li></ul></ul><ul><ul><li>Brainstorming techniques – promotes creative, non-lateral thinking in a safe, non-judgemental environment </li></ul></ul><ul><ul><li>Listening – be interested, inquire, stay focussed, paraphrase, evaluate message </li></ul></ul><ul><ul><li>What, why, when, where, who and how </li></ul></ul><ul><ul><ul><li>What and Why clarify “As Is” </li></ul></ul></ul><ul><ul><ul><li>When, Where, Who & How are used for the “To Be” </li></ul></ul></ul>
    • 18. Requirements <ul><li>A GOOD BUSINESS REQUIREMENTS NEED TO BE: </li></ul><ul><ul><li>Verifiable </li></ul></ul><ul><ul><li>Ranked for importance and stability </li></ul></ul><ul><ul><li>Modifiable </li></ul></ul><ul><ul><li>Traceable </li></ul></ul><ul><ul><li>Understandable </li></ul></ul><ul><ul><li>Accurate </li></ul></ul><ul><ul><li>Complete </li></ul></ul><ul><ul><li>Consistent </li></ul></ul><ul><ul><li>Clear </li></ul></ul><ul><li>NEED TO CONSIDER NON-FUNCTIONAL REQUIREMENTS: </li></ul><ul><ul><li>Usability – “look and feel”, consistency, supporting documentation </li></ul></ul><ul><ul><li>Reliability – Frequency / severity of failure, recoverability and audit </li></ul></ul><ul><ul><li>standards </li></ul></ul><ul><ul><li>Performance – speed, efficiency and No. of users </li></ul></ul><ul><ul><li>Supportability – is the system configurable? Maintainable? </li></ul></ul>
    • 19. BA DELIVERABLES <ul><li>Process Maps </li></ul><ul><li>Business Requirement Document </li></ul><ul><li>Functional Specification </li></ul><ul><li>Procedure Manuals </li></ul><ul><li>Training Material </li></ul><ul><li>UAT Test Plans </li></ul><ul><li>UAT Test Scripts </li></ul><ul><li>Site Acceptance Test Scripts </li></ul>
    • 20. Any Questions???
    • 21. Solution Design Chris Owen (Solution Design Manager)
    • 22. Solution Design <ul><li>High Level Solution Design </li></ul><ul><ul><li>Input to business case (costs) </li></ul></ul><ul><ul><li>Framework for rest of design </li></ul></ul><ul><ul><li>Stakeholders are business, development, test, infratsructure, production services, enterprise architects, security, etc </li></ul></ul><ul><li>Functional Specification </li></ul><ul><ul><li>Describes functionally how the system will work. (Screen designs, flow diagrams, business rules) </li></ul></ul><ul><li>Technical Specifications </li></ul><ul><ul><li>Detailed designs of infrastructure, application components, messaging etc. </li></ul></ul>
    • 23. Any Questions???
    • 24. Development Mark Lockwood (Server Development Manager)
    • 25. Development <ul><li>Process </li></ul><ul><li>Environments </li></ul><ul><li>Technology </li></ul><ul><li>Resourcing </li></ul><ul><li>Application Support </li></ul>
    • 26. Development <ul><li>Process </li></ul><ul><li>What is Development? </li></ul><ul><li>Development takes ‘outputs’ from Analysis/Design phase and creates ‘outputs’ ready to be tested. </li></ul>
    • 27. Development <ul><li>Environments </li></ul><ul><li>(also known as Regions) </li></ul><ul><li>Development </li></ul><ul><ul><li>Development </li></ul></ul><ul><ul><li>Unit Testing </li></ul></ul><ul><li>Quality Assurance </li></ul><ul><ul><li>Integration Testing </li></ul></ul><ul><li>User Acceptance </li></ul><ul><ul><li>Regression Testing </li></ul></ul><ul><li>Production </li></ul><ul><ul><li>‘ Live’ system </li></ul></ul>
    • 28. Development <ul><li>Environments </li></ul><ul><li>Developers involvement (in principle) should end once code leaves the Development environment. </li></ul><ul><li>Developers are responsible for establishing scripts to migrate code (executables) as well Database changes between environments. </li></ul><ul><li>Developers will assist with the final implementation (to production). </li></ul>
    • 29. Development <ul><li>Technology </li></ul><ul><li>Server </li></ul><ul><ul><li>Microsoft core technologies </li></ul></ul><ul><li>Mainframe </li></ul><ul><ul><li>CICS </li></ul></ul><ul><ul><li>COBOL </li></ul></ul>
    • 30. Development <ul><li>Technology (Server) </li></ul><ul><li>Past </li></ul><ul><ul><li>Visual Basic 6.0 </li></ul></ul><ul><ul><li>Visual Interdev </li></ul></ul><ul><ul><ul><li>ASP (Active Server Pages) </li></ul></ul></ul><ul><ul><li>.Net Framework 1.0, 1.1 </li></ul></ul><ul><ul><li>Microsoft Access (97,2000) </li></ul></ul><ul><ul><li>Cold Fusion </li></ul></ul><ul><ul><li>Ingress </li></ul></ul><ul><li>Current </li></ul><ul><ul><li>Visual Studio 2005 </li></ul></ul><ul><ul><ul><li>.Net Framework 2.0 </li></ul></ul></ul><ul><ul><ul><li>VB.Net, ASP.Net </li></ul></ul></ul><ul><ul><li>SQL Server 2000 and 2005 </li></ul></ul><ul><ul><li>Biztalk Server 2004 </li></ul></ul>
    • 31. Development <ul><li>Technology (Server) </li></ul><ul><li>Future </li></ul><ul><ul><li>Visual Studio 2008 (Orcas) </li></ul></ul><ul><ul><ul><li>.Net Framework 3.5 </li></ul></ul></ul><ul><ul><ul><ul><li>WPF (Windows Presentation Foundation) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>WWF (Windows Workflow Foundation) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>WCF (Windows Communication Foundation) </li></ul></ul></ul></ul><ul><ul><ul><li>VB.Net, ASP.Net </li></ul></ul></ul><ul><ul><li>SQL Server 2005 and 2008 </li></ul></ul><ul><ul><li>Biztalk Server 2006 R2 </li></ul></ul>
    • 32. Development <ul><li>Resourcing </li></ul><ul><li>Factors to consider; </li></ul><ul><li>Skills Training </li></ul><ul><ul><li>Specialist (Guru) Vs Generalist (Jack of all trades, master of none) </li></ul></ul><ul><ul><li>Past (for Application Support), Current and Future Technlogies </li></ul></ul><ul><li>Key-man risk reduction </li></ul>
    • 33. Development <ul><li>Application Support </li></ul><ul><li>Support of ‘live’ code is critical to ongoing business success. </li></ul><ul><li>Facts of life; </li></ul><ul><ul><li>Death </li></ul></ul><ul><ul><li>Taxes </li></ul></ul><ul><ul><li>Application Support </li></ul></ul><ul><li>Support ‘burden’ has significant implications on Application Lifecycle . </li></ul>
    • 34. Any Questions???
    • 35. Testing Anne-marie Marchioro (QA officer)
    • 36. SOLUTION DELIVERY STAGES <ul><li>Analysis </li></ul><ul><li>Development </li></ul><ul><li>Testing </li></ul><ul><li>Implementation </li></ul><ul><li>Closure </li></ul>
    • 37. USER ACCEPTANCE TESTING <ul><li>Ensure user has appropriate access to USER environment </li></ul><ul><li>Assist user with any queries relating to the system or changes </li></ul><ul><li>Manipulate dates for data output </li></ul>
    • 38. PRODUCTION SUPPORT <ul><li>Existing problems that arise in PROD are forwarded to QA: </li></ul><ul><li>Ability to copy the customer into USE4 </li></ul><ul><li>Knowledge base </li></ul><ul><li>Testing experience </li></ul>
    • 39. IMPLEMENTATION <ul><li>Promote to PROD on Wednesday - between 2am and 5am </li></ul><ul><li>Reduces customer impact: </li></ul><ul><li>Low usage of ABL facilities </li></ul><ul><li>Branches open at 10am Wednesday </li></ul>
    • 40. CLOSURE <ul><li>Record and store results appropriately (either hard copies or QA Director) </li></ul><ul><li>Ensure business unit are happy with testing and receive their sign off </li></ul><ul><li>Provide sign off to developer </li></ul>
    • 41. TESTING ENVIRONMENTS <ul><li>DEV – 4 environments – used by developers for coding </li></ul><ul><li>TEST – 2 environments – used by developers for unit testing </li></ul><ul><li>QUAL – 10 environments – used by QA </li></ul><ul><li>USER – 6 environments – used for UAT </li></ul>
    • 42. ENVIRONMENTS <ul><li>QA are responsible for all QUAL and USER testing environments. This involves: </li></ul><ul><li>Ensuring they are refreshed regularly to reflect the existing PROD coding </li></ul><ul><li>Ensuring there is sufficient customer records to perform testing </li></ul><ul><li>Ensuring QUAL and USER environments contain the changed software that will replace PROD </li></ul>
    • 43. TOOLS <ul><li>Compuware QA Director </li></ul><ul><li>Information Technology Infrastructure Library (ITIL) </li></ul><ul><li>ISTQB certification </li></ul><ul><li>IEEE standards </li></ul>
    • 44. COMPUWARE QA DIRECTOR <ul><li>Allows for manual or automated testing. </li></ul><ul><li>Automated testing is particularly useful for: </li></ul><ul><li>Online Banking (regression testing) </li></ul><ul><li>Loan Centre Applications </li></ul><ul><li>Service Recovery Testing </li></ul>
    • 45. CAB PROCESS <ul><li>Request for Change - due Friday noon </li></ul><ul><li>Status changed to ready to assess </li></ul><ul><li>Reviewed by CAB members </li></ul><ul><li>CAB meeting to discuss - Tues </li></ul><ul><li>Result - approved / declined </li></ul>
    • 46. FREEZES <ul><li>ABL have a policy that enables IS to make a decision to stop all changes being promoted to PROD when: </li></ul><ul><li>There is an extended holiday </li></ul><ul><li>Major changes have been made in other applications that may affect promotes </li></ul><ul><li>End of financial year </li></ul>
    • 47. Any Questions???

    ×