Friday, July 16, 2010

Project Procurement Plan

Project Name: Trust Online Banking System

Prepared by: Lee Long Kiat

Date (DD/MMM/YYYY): 13/Jul/2010


Project Initiation Phase – This portion of the Procurement Plan document is used to provide the project selection team with general information about the possible purchase of goods and services. No approval signatures are required.



1. Procurement Statement


Describe, in general terms, what products or services are being considered for procurement:

Adobe Dreamweaver CS5

Dreamweaver is the one of the best web development tool otherwise it is also design system which are easy to learn and master it.

Netbean 6.0

One of the Java development systems that develop from Sun Java. It provide some of function to let them to create their java system easily.

Oracle Databases

The best databases system. It can provide high secure databases management is suitable to our project.

Microsoft Office

Microsoft office can help our organization to record and create our document and project plan easily.



2. Estimated Cost








3. Vendor Selection
We choose RFP as our approach of the project team to select a product or vendor as:

– Document used to solicit proposal from prospective sellers.

– Issues to potential vendors.

– Vendors proposed various hardware, software and etc.

 

Project Planning Phase – This portion of the Procurement Plan document provides detailed information about how vendors, products and services will be chosen, what kind(s) of contract(s) will be used, how vendors will be managed and who will be involved at each stage of the process. This document should be approved by appropriate individuals before the actual procurement process begins.

1. Procurement Definition
Procurement means acquiring goods and/or services form an outside source. The term is widely used in the government; many private companies use the term purchasing; and IT professionals use the term outsourcing. Suppliers, vendors, subcontractors, or sellers refer to organizations or individuals
Trust online banking system is high secure banking system in which help the bank to manage their client banking process in an online system. This system will need a high secure databases to run it to ensure the detail of their client will not easy been stolen by cracker. Furthermore a better software development tool will help to increase the efficiency in the system development process speed.


2. Selection Process & Criteria
Criteria:

a) Price : To ensure the procurement are not influence to our cost estimation or budget.

b) Time : To ensure that when we can receive or obtain the tool we want that not influence to our system delivery deadline.

c) Quality : Better quality better quality of system that we can produce.


3. Project Procurement Team


List all stakeholders who are involved in the Procurement Process, along with contact information and a description of their Procurement Role. Enter an [ X ] next to each project team member who is authorized to enter into contract agreements or purchase for the Team (insert rows as needed):

X here Name: Phone / email: Procurement Role: 

[ x ] Lee Long Kiat davidlee5137@hotmail.com
Procurement Officer

[ x ] Kasturi honeymelon231183@yahoo.com

Project Manager

[ x ] Jeyaprakash Jay2snoop@yahoo.com

Business Officer

[ x ] Mohd Farid Seldz87@gmail.com

Contract Administrator

 
4. Contract Type
Fixed price or lump sum contracts will be our chosen contract type as it involves a fixed total price for a well-defined product. Fixed price contracts may also include incentives for meeting or exceeding selected project objectives such as schedule targets.

 
5. Contract Standards

a) The entire vendor should include free technical service to their product.

b) The entire vendor should provide training to let our developer to familiar to their product.

c) Maintenance should frequently provide by the vendors.

 
6. Vendor Management
a) The development will recently to send their feedback to the vendors.

b) Request the vendors to provide maintenance for ensure the quality of their product.

c) Any problem for the product the vendors can change or repair in a short time.

 
7. Links to related planning documents
Vendor Payment Plan

For the payment plan we decide using credit transfer as our payment because it is safety and fastest way in transfer huge amount of money.


Work breakdown structure (WBS)

Meeting Agenda & Minutes

CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                                           
Just Cool
Meeting Agenda

Date: 10 Jun 2010
Date/ Time: Thursday, 3.00pm - 4.00pm
Type / Place: KJ Student Lounge
Reference ID: OTBSM01

1.        Concise & decide the project title.
2.       Establish the group member & they capability in this project
3.       Coarse ideas of team member’s accountability
4.        Interview with Stakeholder / Customer
5.       Collect the objective & goals of this project.
6.       Documentation format
7.       Meeting schedule
8.       Date, time & place of each every meeting


CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
Just Cool
Minutes Meeting
Date: 10 Jun 2010
Date/ Time: Thursday, 3.00pm - 4.00pm
Type / Place: KJ Student Lounge
Reference ID: OTBSM01
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:


No
Agenda
Action by
1.
Welcoming note
-          Welcoming address by our project leader.
-          Recheck whether member recheck the project agenda schedule one day before meeting.
-          Decide the main project title.

Kasturi & All Members
2.
Determine group member strength & capability
-          Needs feedback from all members on their strength & capabilities






All Members
3.
Coarse ideas of team member’s accountability
-          Collect  & list the ideas  from all the members

4.
Interview with Customer/ Stakeholder
-          Collect all the information & needs from customer/ stakeholder.
-          Determine the goals, purpose of the system.
5
Documentation project
-          Determine all the information, research & assign the duties according to member’s strength & capability.
6.
Meeting schedule
-          Assign and decision the next meeting
-          Decide the location and timing.
---------------------------------------------------------

CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                       
Just Cool
2nd Meeting Agenda

Date: 17 Jun 2010
Date/ Time: Thursday, 3.00pm - 4.00pm
Type / Place: KJ Library Discussion Room
Reference ID: OTBSM02

1.       Review last meeting summary
2.       Confirmation all tasks last meeting
3.       Requirement review
4.       SDLC Methodology Select
5.       Documentation Project
6.       Meeting Schedule.
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
Just Cool
Minutes Meeting
Date: 17 Jun 2010
Date/ Time: Thursday, 3.00pm - 4.00pm
Type / Place: KJ Library Discussion Room
Reference ID: OTBSM02
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:


No
Agenda
Action by
1.
Review last meeting summary
-          Review all the detail that had been discussed in last meeting.
Kasturi & All Members
2.
Confirmation all tasks last meeting
-          To check whether all the tasks had been given to the team member are complete or not.






All Members
3.
Requirement review
-          Check requirements which elicited from stakeholder are conflict or not.
-          Seek for best solution to solve the conflict or unrealistic requirements.
4.
SDLC Methodology Select
-          Bases on the stakeholder requirement to select the development methodology that suit to our team members.
5
Documentation project
-          Determine all the information, research & assign the duties according to member’s strength & capability.
6.
Meeting schedule
-          Assign and decision the next meeting
-          Decide the location and timing.
--------------------------------------------------------------------
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
Just Cool
Meeting Agenda
Date: 24 Jun 2010
Date/Time: Thursday, 3.00 - 4.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM03


1.      Review Last Meeting Minutes
2.      Confirmation all tasks from Last Meeting
3.      Requirement Change
4.      Programming Language Selection
5.      System Design Analysis
6.      Documentation Project
7.      Assign Tasks/Meeting Schedule

ONLINE TRUST BANKING SYSTEM
PROJECT
Just Cool Third Meeting
Minutes Meeting
Date: 24 Jun 2010
Date/Time: Thursday, 3.00 - 4.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM03
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:
-

No
Agenda
Action by
1.
Review Last Meeting Minutes
-          Review all the detail that had been discussed in last meeting.
Kasturi (Read last meeting minutes)
2.
Confirmation all Tasks from Last Meeting
-          To check whether all the tasks had been given to the team member are complete or not.
All Members
3.
Requirement Change
-          Farid report thatThe stakeholder has requested for the online banking system should include a customer feedback section.  
-          All members are agreeing to the request from the stakeholder.
4.
Programming language selection
-          Lee Long Kiat has decided using PHP as our project programming language because all our group members are familiar.
-          Kasturi request Lee to do the research whether PHP can link to the bank database as they are using Oracle database
5.
System Design Analysis
-          Farid and Jeya have completed the simple logical design (pseudocode).
-          All members will take part to review again the system design.

6.
Documentation Project
-          Kasturi received a message from one of the stakeholder that they are not very satisfied with the project charter.
-          Jeya suggest checking the format of the project charter and add-on more detail in the project charter.
7.
Assign Tasks / Meeting Schedule
-          Jeya edit the project charter
-          Lee research that PHP is compatible with Oracle database and how to link it
-          Assign and decision the next meeting
-          Decide the location and timing.

---------------------------------------------------------------
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                       
Just Cool
Meeting Agenda
Date: 01 July 2010
Date/Time: Thursday, 3.00 - 4.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM04

1.       Review Last Meeting Minutes
2.       Confirmation all Tasks Last Meeting
3.       System Design Review
4.       Code Implementation
5.       Test Plan and Determine System Test
6.       Meeting Schedule and Assign Task
Just Cool Fourth Meeting
Minutes Meeting
Date: 01 July 2010
Date/Time: Thursday, 3.00 - 4.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM04
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:
-

No
Agenda
Action by
1.
Review Last Meeting Minutes
-          Review all the detail that had been discussed in last meeting.

All Members
2.
Confirmation all Tasks Last Meeting
-          To check whether all the tasks had been given to the team member are complete or not.
-          Lee has confirmed that PHP can compatible to Oracle databases and also found the related technique for linking the databases.
-          Jeya has amended the project charter and submit to the stakeholder.

3.
System Design Review
-          All the group members have already review the design of the system and fix the defect in the design.
-          The code implementation will be handling by Lee.
4.
Code Implementation
-          Lee report that he will choose Dreamweaver coding.
-          Jeya and Kasturi will assist Lee in coding.
5.
Test Plan and Determine System Testing
-          All members will be involved to do the test plan.
-          The system testing will include unit testing, white box testing, black box testing, and user acceptance testing.


6.
Meeting Schedule and Assign Task
-          Lee. Jeya, and Farid will complete the system coding before next meeting.
-          Assign and decision the next meeting
-          Decide the location and timing.
-------------------------------------------------------
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                       
Just Cool
Meeting Agenda
Date: 08 July 2010
Date/Time: Thursday, 3.00 - 4.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM05

1.       Review Last Meeting Minutes
2.       Confirmation all Tasks Last Meeting
3.       System Design
4.       Implementation Requirement
5.       Software Testing
6.       Meeting Schedule and Assign Task

Just Cool Fourth Meeting
Minutes Meeting
Date: 8 July 2010
Date/Time: Thursday, 3.00pm-04.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM05
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:
-

No
Agenda
Action by
1.
Review Last Meeting Minutes
-          Review all the detail that had been discussed in last meeting.

All Members
2.
Confirmation all Tasks Last Meeting
-          To check whether all the tasks had been given to the team member are complete or not.
-          Lee has confirmed that database had created and well function with Oracle and PHP.
-          Changes in project charter review and update to the stakeholder.

3.
System Design
-          All the group members apply testing design to system and fix the defect in the usability testing.
-          Hardware & software requirement.
-          Recheck back code implementation.
4.
Implementation Requirement
-          Dreamweaver coding is compatible.
-          Lee complete done with coding.
5.
Software Testing
-          All members will be involved to do the last testing procedure.
-          Testing had been taken to check functional system and acceptance.
6.
Meeting Schedule and Assign Task
-          All members agreed the complete the system.
-          Next meeting will be assign 14 July 2010 type of communication Yahoo Messenger at 8pm till 10pm
----------------------------------------------------------------
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                       
Just Cool
Meeting Agenda
Date: 14 July 2010
Date/Time: Wednesday, 8.00 - 10.00pm
Type/Place: KJ Library Discussion Room
Reference ID: OTBSM06

1.       Review Last Meeting Minutes
2.       Confirmation all Tasks Last Meeting
3.       Stakeholder Report
4.       Backup Maintenance
5.       Update
6.       Meeting Schedule and Assign Task

Just Cool Fourth Meeting
Minutes Meeting
Date: 14 July 2010
Date/Time: Wednesday, 8.00 - 10.00pm
Type/Place: Yahoo Messenger
 Reference ID: OTBSM06
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:
-

No
Agenda
Action by
1.
Review Last Meeting Minutes
-          Review all the detail that had been discussed in last meeting.

All Members
2.
Confirmation all Tasks Last Meeting
-          To check whether all the tasks had been given to the team member are complete or not.
-          Lee has confirmed and tested the implementation phase complete with no broken link.
-          Complete project charter had been presented to stakeholder

3.
Stakeholder report
-          The stakeholder agreed to the design that done by all group member.
-          Stakeholder Recheck and debug coding.
4.
Backup and Maintenance
-          All group members are backing up the system original system to hard drive array.
5.
Update
-          Stakeholder agreed with complete system and request additional updates.
6.
Meeting Schedule and Assign Task
-          All members agreed the complete the system.
-          Next meeting will be assign 16 July 2010 type of communication KJ Library Discussion Room at 8pm till 10pm

----------------------------------------------------------------------
CEB2003
ONLINE TRUST BANKING SYSTEM
PROJECT
Instructor: Norlini Ramli
                                                                       
Just Cool
Meeting Agenda
Date: 16 July 2010
Date/Time: Friday, 8.00 - 10.00pm

Type/Place: KJ Library Discussion Room
Reference ID: OTBSM07

1.       Review Last Meeting Minutes
2.       Confirmation all Tasks Last Meeting
3.       Update
4.       Meeting

Just Cool Fourth Meeting
Minutes Meeting
Date: 16 July 2010
Date/Time: Friday, 8.00pm-10.00pm
Type/Place: KJ Library Discussion Room
 Reference ID: OTBSM07
Attendees:
Kasturi, Farid, JeyaPrakash, Lee Leong Kiat
Not Attending:
-

No
Agenda
Action by
1.
Review Last Meeting Minutes
-          Review all the detail that had been discussed in last meeting.

All Members
2.
Confirmation all Tasks Last Meeting
-          To check whether all the tasks had been given to the team member are complete or not.
-          Full report presented to stakeholder with complete updates.

4.
Update
-          Check entire complete system and schedule maintenance twice a week in a month.
-          2 copy of the complete system transfer to array.
5.
Meeting
-          This is the last meeting for the group member.
-          There been a good workforce and cooperation.
-          Thanking all the members in group.