Professional Documents
Culture Documents
Project Plan
- Amin Hidayat
- Cahyadi
- Deni Irawan
- Erwin Diantoro
- Idrus Alfian
- Indra Maulana
- M. Diva Bhakti Irawan
(2012141021)
(2012141281)
(2012141418)
(2012140716)
(2012140741)
(2012140710)
(2012140931)
Prepared By
Kelompok 6
01 Februari 2016
Version 1.0.1
Page: 2 of 12
Table of Contents
1
Introduction................................................................................3
1.1 Objective.............................................................................3
1.2 Ruang Lingkup...................................................................3
1.3 Reference...........................................................................4
Testing Methodology..................................................................6
5.1 Test Scope..........................................................................6
5.2 Testing Strategy..................................................................6
5.3 Testing Tools......................................................................7
Implementation Methodology....................................................7
6.1 Prerequisite........................................................................7
6.2 Data & Environment...........................................................8
Assumptions...............................................................................8
Appendices.................................................................................. 9
8.1 Appendix A : Signatures.....................................................9
8.2 Appendix B: Other Documents & Document History........10
Internet Banking
[1.0]
Project Plan
Version:
Page 3 of 12
Introduction
Objective
Menurut Bank Indonesia, Internet Banking merupakan salah satu layanan jasa
Bank yang memungkinkan nasabah untuk memperoleh informasi, melakukan
komunikasi dan melakukan transaksi perbankan melalui jaringan internet.
Secara konseptual, lembaga keuangan bank dalam menawarkan layanan
internet banking dilakukan melalui dua jalan, yaitu pertama, melalui bank
konvensional (an existing bank) dengan representasi kantor secara fisik menetapkan
suatu website dan menawarkan layanan internet banking pada nasabahnya dan hal
ini merupakan penyerahan secara tradisional. Kedua, suatu bank mungkin
mendirikan suatu "virtual "cabang," atau "internet" bank. didirikan suatu Virtual
bank dapat menawarkan kepada nasabahnya kemampuan untuk penyimpanan
deposito dan tagihan dana pada ATM atau bentuk lainnya yang dimiliki. Tujuan dari
sebuah project plan INTERNET BANKING adalah
Ruang Lingkup
Peran yang dicakup dalam project Internet Banking ini adalah Project
Manager, Bussinees Analyst, Database Administrator, Software Designer,
Software Tester, Software Engineer, dan Web Design.
Web Design memiliki tanggung jawab dan tugas dalam membuat tampilan
software diberbagai device.
Metode yang digunakan dalam project Internet Banking ini adalah Waterfall.
Waterfall merupakan sebuah contoh dari proses perencanaan, dimana semua proses
kegiatan harus terlebih dahulu direncanakan dan dijadwalkan sebelum dikerjakan.
Dengan menggunakan metode waterfall ini diharapkan dalam proses dokumentasi
tersortir dengan baik serta kualitas software yang baik dalam versi 1.0 serta pada
tahap awal tidak mengalami perubahan.
Internet Banking
Project Plan
Version: 1.0.1
Page 4 of 12
Reference
See Appendix B for Reference & Other related documents.
Name
Cahyadi
Role
Project Manager
Indra Maulana
Business Analyst
Amin Hidayat
Internet Banking
Database
Administrator
Responsibilities
Perform project
planning activities
Conduct kick off
meeting and communicate
the project's progress to all
relevant stakeholders
Motivate the project
team and have constant
personal drive to achieve
the project's goals
Perform project
evaluation
Send Deliverables to
Client
Get user acceptance &
feedback from client
Perform production test
run
Log and Analyze
Problem
Perform Problem
solving activities
Conduct External &
Internal closing meeting
Perform FP Count of
Delivered SW
Save all project Defect
Data to Defect Database
Managing Risk and
Issues
Working with Vendors
Benefit Realitation
Perform and/or Verify SW
Requirements Analysis
Perform requirement
gathering with client
Develop Software
Requirement Specification
document
Assessing the adequacy of
requirements
Develop Mini RVM
Perform Design & Test Script
Review
Perform UAT with client
Make a Schedule Backup
Perform Data Migration
Calculate mount point size
in Lpar
Deliverables
Project Schedule
Project Plan
Software Requirement
Specification
Review Report
Test Scenario/Test
Script/Checklist with
result
Migrated Data
Project Plan
Version: 1.0.1
Page 5 of 12
Deny Irawan
Software Designer
Idrus Alfian
Software Tester
Muhamad Diva
Bhakti Irawan
Software Engineer
Erwin Diantoro
Web Designer
Test Scenario
Review Report
Test Scenario/Test
Script/ Checklist with
result
Software Architecture
Design
Test Scenario
Test Script
Review Report
Test Scenario/Test
Script/Checklist with
result
Validation Report
Source Code
Unit Test Result
Scan Log Report
Test Scenario/Test
Script/Checklist with
result
Review Report
Date
Raised
Phase of the
Project
Random
Random
20 April
2016
Random
Internet Banking
Risks
Impact
Kecelakaan
Progress
pengerjaan
tertunda
Design Web
Munculnya device
web baru dengan
ukuran yang belum
pernah ada disaat
progress
Progress
pengerjaan
bertambah
All phase of
the Project
Keterlambatan
dalam penyelesaian
Poryek
Mitigation Actions
Pengalihan tugas
sementara, salah
satu member team
akan mengampu 2
tanggung jawab
sementara
Penambahan waktu
pengerjaan untuk
design sekitar 3
hari untuk
penambahan
ukuran 3-5 device
1. Sistem backup
data 24 jam
2. fleksibelitas
tempat proses
pengerjaan projectproject.
Project Plan
Version: 1.0.1
Page 6 of 12
Task
Pengerjaan project harian
a. Today's Activity
b. Tomorrow's To Do List
c. Deferred Items
d. Today's Issues
Frequency
Daily
Clients if necessary
Weekly
Daily
End of
Phase
Internet Banking
Stakeholder
PM, Team Members
Project Plan
Version: 1.0.1
Page 7 of 12
1.2
Project Schedule
Internet Banking
Project Plan
Version: 1.0.1
Page 8 of 12
1.3.1
Task
Project Schedule
Project Plan
Software Requirement
Specification
Review Report
Test Scenario/Test
Script/Checklist with result
Migrated Data
Test Scenario
Review Report
Test Scenario/Test Script/
Checklist with result
Software Architecture
Design
Test Scenario
Test Script
Review Report
Test Scenario/Test
Script/Checklist with result
Validation Report
Source Code
Unit Test Result
Scan Log Report
Test Scenario/Test
Script/Checklist with result
Review Report
PIC
Role
Cahyadi
PM
2 Minggu
Indra
Maulana
BA
1 Minggu
Amin
Hidayat
DBA
1 Minggu
Deny
Irawan
SD
3 Minggu
Idrus
Alfian
ST
1 Minggu
Muhamad
Diva Bhakti
Irawan
SE
3 minggu
WD
2 Minggu
Erwin
Diantoro
Milestone
Remarks
2 Testing Methodology
Tes dilakukan untuk melihat kekurangan dari sistem aplikasi dilihat dari design,
database & source code.
2.2
Testing Strategy
All written code will be reviewed and tested multiple times under different aspects.
This chapter explains the different testing approaches in more detail:
System Testing
Objective: To validate the system behavior against the requirements stated
in the SRS
Entry Criteria:
Testing will commence if there is a baselined release from the developers.
Technique: BlackBox / functional testing, using test cases; each test case
states some interaction and input, along with the expected result/output.
Internet Banking
Project Plan
Version: 1.0.1
Page 9 of 12
Unit Testing
Objective: To validate the technical of units (small pieces of the software up
until method level) against its detail design specification.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: White Box testing with up to method testing precision. May
also enhanced by GlassBox test cases, which consider the program logic;
typically to achieve coverage of all statements.
Completion / Exit Criteria:
o All test cases executed with no more errors.
No error means, that the actual and expected system behavior is
the same.
o All test cases have been signed off to QA.
o All Automated unit test code has passed execution.
Related document: Unit Test Script (optional), Unit Test Code
(developed and reviewed later, see overall planning).
Performance Testing
Objective: To validate the usability and stability of the application when
under heavy load / access from web.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: tool-assisted multiple access of selected application
functionality, using test cases.
Completion / Exit Criteria:
o Single Transaction/single user: Successful completion of the test
scripts without any failures and within the expected / required time
allocation (per transaction).
o Multiple transactions / multiple users: Successful completion of the
test scripts without any failures and within acceptable time
allocation..
Related document: Performance Test Script
(developed and reviewed later, see overall planning).
Integrating Testing
Objective: To take unit tested components and build a program structure
that has been dictated by design.
Entry Criteria:
o Unit testing must be integrate with another one
Technique: using anomaly test.
Completion / Exit Criteria:
o There is no hang & bug in application
o Related document: Build system test script
(developed and reviewed later, see overall planning).
Internet Banking
Project Plan
Version: 1.0.1
Page 10 of 12
Name Device
Internet Explorer
Browser
Task
Display
transactions
history
Error
Javascript
Error
Cause
Browser isnt
support for
javascript
Implementation Methodology
Prerequisite
1.
2.
3.
4.
5.
6.
Internet Banking
Project Plan
Version: 1.0.1
Page 11 of 12
Appendices
Appendix A : Signatures
This document has been reviewed and accepted by the undersigned. Therefore, this
document will be used as the basis for doing further processing. Any addition and/or
modification of this document will be subjected to approval by the undersigned.
Signature
Name
Title
Date
:
:
:
Signature
Name
Title
Date
:
:
:
Internet Banking
Cahyadi
Project Manager
22 Desember 2015
Kaido
Director of Kaido Bank
22 Desember 2015
Signature
Name
Title
Date
:
:
:
Signature
Name
Title
Date
:
:
:
Dofflaminggo
Vice Dir. Of Kaido Bank
22 Desember 2015
Project Plan
Version: 1.0.1
Page 12 of 12
Related documentation:
Document History:
Version
1.0.1
Date
22 Des 2015
Internet Banking
Change Reason
Initial Creation
Author
Project Manager
Project Plan
Version: 1.0.1