Project Charter: "Star Supermarket" Business Service Database Management System

“Star Supermarket”
Business Service
Database Management
System
Project Charter
Project Design and Architecture:
DATA
Database Analysis Team Associates
Business Service Database Management System Project
“Data Analysis Team Associates”
Table of Contents
Type chapter title (level 1) ...................................................................1
Type chapter title (level 2) ................................................................2
Type chapter title (level 3).............................................................3
Type chapter title (level 1) ...................................................................4
Type chapter title (level 2) ................................................................5
Type chapter title (level 3).............................................................6
Wednesday, March 23, 2016 Version: 1.0 Page 1

of 21
PROJECT
CHARTER
Project Name:
Date: 26/007/2010
Version Draft: 0.1
Point of Contact:
Project Manager: Yong

Lek
Database Analysis Team Associates Project Leader:
Document Purpose
This Project Charter document is issued for the purposes of the project initiator and sponsor “Star
Supermarket” (which shall hereinafter be referred to as “the Client”) that formally authorizes the
existence of this project, and provides the Database Analysis Team Associates (which shall
hereinafter be referred to as “DATA”) and its Project Manager with the authority to apply DATA
organizational resources to project activities.
The purpose of the charter is to obtain formal approval on the general parameters and structure of the
proposed project, including the following:
 the project objectives and outcomes, benefits, scope, and risks;
 the project deliverables, schedule, milestones and estimated costs

of 21
Section 1. Charter Introduction
1.1 Document change control

This section serves to control the development and distribution of revisions to the project charter. It
should be used together with a change management process and a document management system. It is
recommended that changes to the charter be documented only by adding appendices to the original
project charter. This will keep an accurate history of the original document that was first approved
Revision
Date of Issue Author(s) Brief Description of Change
Number
Sydney Institute St.

1.0 26/07/2010 Creation of the document.
George College
Initial Draft of Project Charter for

2.0 Draft 1 03/08/2010 Goran Krstevski
team review
1.2 Executive summary

Star Supermarket first Australian store opened its doors in January 1995. Now with 30 stores
successfully operating across New South Wales, ACT, Queensland and Victoria, Star Supermarket
has become one of the leading supermarket retailers in Australia. One of the main company objectives
is to provide quality products and services in a cost effective manner to excel in serving their
customers.
In the last five years, the company has been steadily expending, however it has become apparent that
there are some inefficiencies and inadequacies within their IT department has not been able to meet
their business needs in areas like: database storage and management system, inventory management
system, accounting system and billing and report system.
Star Supermarkets have recognized that these issues are affecting their business routine and looking
for a solution that will assist and resolve their issues.
Star Supermarket approached DATA to investigate the current system, and to propose, plan, design
and to implement a viable solution.
After analysing the organisational strategy and performing gap analysis of the company needs, DATA
proposed solution to the company’s requirements will be ‘Business Service Database Management
System’. This innovative DBMS is new software application solution designed for Star Supermarket
that will help enhance the Star Supermarket Company IT efficiency, increase uptime of critical
systems, enabling higher quality decision-making with effective use of data analysis for enhancing
Business Intelligence. This application will give the client necessary tools to manage their complex

of 21
pricing strategies, streamline inventory management processes, improve warehouse efficiencies, and
execute consistently across the enterprise
Goals and Objectives

The outcome of the Project is a DBMS which is a fully functional, flexible and scalable working
application.
The goal of this project is to enhance the Star Supermarket’s primary database management system
and its functions. The enhancements will be achieved primarily through the implementation of the
DATA proposed solution.
This Business Service Database Management System will help the company achieve the following
specific objectives including:
Improved system for controlling inventory
 Shorten product delivery time duration
 Decreased cost of system maintenance
 Automate ordering and supplying of stock
Simplifying processes by:

 Eliminating unnecessary paperwork, and duplication of efforts.
Providing more effective management information by:
 Implementing a real-time processing environment
 Providing departments with direct and easy access to financial, budgeting, procurement, and
human resources data
 Enabling departments to produce their financial, budgeting, procurement, and human
resources reports in a variety of formats (i.e. Business Warehouse)
 Providing additional business functionalities such as Business Intelligence
 Establishing secure access and reliable system

of 21
1.3 Authorization
Signatures of key the stakeholders, indicating that they agree with their roles and the description of the
Business Service Database Management System Project as it appear in the Project Charter.
This project charter formally authorizes the existence of the project, Project Name, and provides the
project manager with the authority to apply organizational resources to the project activities described
herein. If there is a change in the project scope, the charter will be updated and submitted for re-
approval.
________________________________________ _______________________
Full name Date
Executive Sponsor
Position, client organization
________________________________________ _______________________
Full name Date
Project Sponsor
________________________________________ _______________________
Full name Date
Project Manager
________________________________________ _______________________
Full name Date
Title

of 21
Section 2. Project Overview
Project Approach
The project will be broken into stages, and risk will be minimized by approaching project
activities in a staged manner, adding successive complexity and detail to the project activities over the
project life cycle (see Stages section for more details).
2.1 Project summary

 This section summarizes the entire project charter, highlighting the significant points of interest to
the reader. It includes all of the information required for approval by the key stakeholders.
 The project summary should also include some background information on the project that
includes the reason or reasons for creating the project (e.g. a business need or a legal requirement)
and mention the key stakeholders who will benefit from the project results.
2.2 Project goals, business outcomes, and objectives

This section describes the project goals and links each of them to related measurable project
objectives. In addition, business outcomes to be derived from the project goals and objectives should
be presented as outlined in the business case. Measurement criteria, which will be used to confirm that
an objective and the outcome have been reached, must also be provided.
Keep in mind that goals are expressed as high-level statements of intention that are typically
intangible or abstract. Objectives are concrete measurement criteria that are used to confirm if an
objective has been met. Business outcomes are results expected at the end of the project. Outcomes
can be expressed in just a few words.
Add rows as required.
No. Goals Objectives Business Outcomes
1.  
2.  
3.  
2.3 Project scope
2.3.1 Scope definition

This is a high-level description of the features and functions that characterize the product, service, or
result to be delivered by the project.
2.3.2 Boundaries
This is where you expand on the scope definition and outline the major activities required to
successfully complete the project (e.g. develop module ABC, develop a requirements document, and

of 21
prepare presentation XYZ). Make sure to include content under “Activities Out of Scope” to reduce
ambiguity.
While the table provides a summary of the project boundaries, further explanation should be provided
in a narrative form.
Activities in Scope Activities out of Scope
1. 1.
2. 2.
3. 3.
Insert additional explanations for project boundaries here.
2.4 Milestones
Identify the significant points or events in the project (such as the phases, stages, decision gates, and
approval of a deliverable). This chart can also represent a high-level project schedule.
Expected
Project Milestone Description
Date
Allocation of roles and responsibilities,

1. Project Charter identifying risk, constraints, goals, business 6-Aug-2010
outcomes, objectives, project scope and budget.
Indentifying Project Scope, Time Schedule,

2. Project Management Plan Project Accountabilities, Communication Plan, 11-Aug-2010
Risk Management Plan, Project Control Plan.
Identifying functional and non-functional

3. Requirement Specification requirement, creating Event Table, Use Case
30-Aug-2010
Report Diagram, Fully Dressed Use Cases, Context
Diagram and Functional Hierarchy Diagram.
Creating Domain Model, ER Diagram, System

4. Design Report Sequence Diagram, Data Dictionary, Contracts, 17-Sep-2010
Database Schema, UI designs
5. Build the System & Build Database, Tables, Views, Triggers, Stored
19-Oct-2010
Database procedures, UI

of 21
Expected
Project Milestone Description
Date
6. Testing Plan In-house testing, System testing, UAT 1-Nov-2010
7. Implementation Plan Disaster Recovery Plan 9-Nov-2010
8.Project Due Hard and Soft Copy of the project 12-Nov-2010
9.Post Implementation Review Review the whole project 19-Nov-2010
10.Internal Presentation Technical Presentation 24-Nov-2010
11.External presentation Non-Technical Presentation 29-Nov-2010
2.5 Deliverables
Acceptance Criteria:
The acceptance criteria for below deliverables are:
Document has been reviewed and approved by: Prioritized scope and high level requirements have
been reviewed by the Design Team, which consists of stakeholders from the Business Sponsor
organization in addition to key members of the project team.
Note: Acceptance of this document is completed by signing off on Request For Acceptance form.
Milestones Deliverables Deliverables Due date

Project Charter Project Charter 6-Aug-2010
Project Management Plan Project Management Report 11-Aug-2010
Requirement Specification Event Table 30-Aug-2010
Report
Requirement Specification Use Case Diagrams 30-Aug-2010
Report
Requirement Specification Fully Dressed Use Cases 30-Aug-2010
Report
Requirement Specification Context Diagram 30-Aug-2010
Report
Requirement Specification Functional Hierarchy Diagram 30-Aug-2010
Report
Design Report Domain Model 17-Sep-2010
Design Report ER Diagram 17-Sep-2010
Design Report System Sequence Diagram 17-Sep-2010
Design Report Data Dictionary 17-Sep-2010
Design Report Contracts 17-Sep-2010
Design Report Database Schema 17-Sep-2010
Design Report UI designs 17-Sep-2010
Testing Plan Testing Reports 1-Nov-2010
Implementation Plan Disaster Recovery Plan 9-Nov-2010
Project Due Hard & Soft Copy 12-Nov-2010
Post Implementation Review Post Implementation Review 19-Nov-2010

of 21
Internal Presentation Technical Presentation 24-Nov-2010
External Presentation Non-Technical Presentation 29-Nov-2010
The deliverables section can be used to build the top levels of a project’s work breakdown structure,
which divides the big deliverables for a project into smaller, more manageable parts.
2.6 Project cost estimate and sources of funding
2.6.1 Project cost estimate

This is where you record a summary of cost estimates for all of the resources (human, material, and
financial) required to produce the deliverables and meet the objectives established for the project. For
input and to make sure the full project scope is covered, refer to the items listed in the initial work
breakdown structure and the project effort estimates. Don’t forget to include one-time as well as
ongoing costs. For example, the estimated cost to sustain the product(s) or service(s) of the project
should be provided. Modify the table as required.
The business case for the project should contain cost estimates that can be used as the basis for this
summary.
Project Phase
Estimated Cost Estimated Cost Estimated Cost Estimated Cost
Deliverable or
FY (1) FY (2) FY (3) FY (4)
Cost Category
(Phase 1/
Deliverable)
Salary
O&M
Professional
services
Capital
Other (e.g.
revenue)
Subtotals
(Phase 2/
Deliverable)
Salary
O&M
Professional
services
Capital

of 21
Other (e.g.
revenue)
Subtotals
TOTAL
2.6.2 Sources of funding

State the various sources of funding that will be used to support the project. It should be clear to the
project sponsor and the project manager where the funds come from and the level of resources
committed to this project.
2.7 Dependencies
This is where you list dependencies for the project such as the following:
 A predecessor or successor relationship exists with another project (such as through a
memorandum of understanding or partnerships);
 A related project expects a deliverable from your project;
 Your project expects a deliverable from a related project; or
 Your project delivers a product, service, or result that will be or that needs to be released with
another new product, service, or result.
Dependency Description Critical Date Contact
2.8 Project risks, assumptions, and constraints
2.8.1 Risks
This initial risk assessment does not replace the full risk assessment conducted during the planning
phase and documented within the project plan—both are activities that come after the project charter
is established.
This is where risks are identified at the start of a project. Decide how important they are and indicate
the plan to mitigate the risks.
 Identify and describe in the table below the key strategic risks involved in the project.
 For each risk, list both the level of impact and the degree of probability (high, medium, low). This
tells the reader how significant each risk is.
 Identify the possible mitigation actions needed during the project to lessen the impact or lower the
probability of the risk involved, and assign the person or team responsible for resolution.
Probability Impact
No. Risk Description Planned Mitigation
(H/M/L) (H/M/L)
1.

of 21
Probability Impact
No. Risk Description Planned Mitigation
(H/M/L) (H/M/L)
2.
3.
2.8.2 Assumptions
State all factors that are, for planning purposes, considered to be true, real, or certain but without
including proof. These assumptions will be validated during the planning process. If any are
inaccurate, inconsistent, or incomplete, they will result in project risks. Add rows as required.
The following table lists the items that cannot be proven or demonstrated when this project charter
was prepared, but they are taken into account to stabilize the project approach or planning.
No. The following is assumed:
1.
2.
3.
2.8.3 Constraints
Identify the specific constraints or restrictions that limit or place conditions on the project, especially
those associated with the project scope (e.g. a hard deadline, a predetermined budget, a set milestone,
contract provisions, and privacy or security considerations). It will help to categorize the constraints if
there are several. Add rows as required.

of 21
The following table lists the conditional factors the project must respect:
No. Category Constraints
1.
2.
3.
Section 3. Project Organization
3.1 Project governance

 This is where you show how your project is governed and the corporate governance bodies that
may be involved in the approval process. In other words, it shows how decisions are made and
who makes which decisions.
 A diagram should be used.
 If committees are shown in the diagram, include a description of these committees in the “Roles
and responsibilities” section.
3.2 Project team structure
Project Role Assigned to
Project Leader Goran Krstevski
Deputy Leader Preeti Biradar
Recording Secretary Preeti Biradar
Security Co-ordinator Adinigara
Lead Builder Shobana Rajendran
Lead Designer Adinigara
Standards Co-ordinator Alexis Medina
Quality Assurance Co-ordinator Shobana Rajendran
Hardware Management
Network Administrator
Testing Co-ordinator Alexis Medina
Implementation Co-ordinator Goran Krstevski
Presentation Co-ordinator Shobana Rajendran

of 21
 Use an organizational chart to show the structure of the project team as well as the relationships
between team members
 You should also show how the team interacts with or relates to the governance structure for the
project.
 For small projects, the names of the team members can be included; for larger projects, the
organizational chart should name the groups or entities that form the project teams.
3.3 Roles and responsibilities

Table below gives the intended reader the overview picture of the roles and responsibilities assigned
to each member of the project team as well as those of the BMDMS project stakeholders and working
groups that have a significant influence on the this project.
Project Role Responsibilities Assigned to
 Accountable for the project. Select, or at least

approve, the project manager.
 Acquire funding for the project from the Board of
Directors, or whoever it is that authorises funds for
projects.
 Own the project's business case.
 Accountable for realising benefits once the project is
delivered..
 Give the project manager the go or no go at the start
of each project stage.
 State the project's objectives and have the vision for
Project Sponsor project deliverables
 Resolve issues the project manager can't.
 Ensure only needed function is delivered and that
money isn't wasted on unnecessary functionality and
features.
 Accountable for legal compliance of the finished
product.
 Chair project steering committee.
 Empower project manager to manage the project.
 Commission post implementation business case
review.
Management representatives from Star Supermarket

involved in the project oversight and control, Responsible
for approving project deliverables, help resolve issues and
policy decisions, approve scope changes, and provide
Steering Committee
direction and guidance to the project. The steering
committee can also be involved in providing resources,
assist in securing funding and act as liaisons between
project team and sponsor.

of 21
Monitor project scope and review and asses project

milestones.
Project review Undertake regular reviews regarding the project status; ask
committee probing questions to ensure an accurate understanding.
Deliver regular feedback to the project team on
performance, deviations and expectations.
Responsible for successful business outcome of the

project. In charge of project staffing, acquiring resources
for the project, personnel issues, top level work
assignments, and stakeholder interaction.
Project Manager Yong Lek
Is the top decision maker on the project, but normally
defers technical decisions to the appropriate technical lead.
Resolves disputes between project participants.
Responsible for coordinating the activities
Excellent and in dept understanding of the operation and

objectives of the BSDMS project and its implementation.
Responsible for the overall project planning and progress
toward the implementation. Also responsible for
monitoring and managing project day to day activities,
maintaining and adjusting the project plan (based on the
input and deliverables of team members), providing
Goran
Project Leader implementation experienced leadership strategies to the
Krstevski
Executive Sponsor, and ensuring the effectiveness of the
application and consultants assigned to the project. Other
responsibilities include reviewing and assisting in issue
resolution, coordinating task dependencies, and
establishing milestone project goals that keep the project
on time and within budget, continually monitoring project
scope, time frame, budget and risk.

of 21
The role of the Deputy Leader is to:

-Assist and share the duties of the Project Leader as
required;
-Report to the Project Manager on matters relating to any
project deliverables and milestones defined within his or
Preeti
Deputy Leader her purview.
Biradar
Also responsible for assisting under the team leader
control in ensuring agreed-upon project tasks are
completed using pre-defined milestones set in the project
Gantt chart and within scope, time, budget and quality
constraints of the project.
Responsible for recording the team meetings discussions

and minutes in the DATA team created Log document.
Taking care for the brief but precise description of the
Preeti
Recording Secretary reason/s for the meeting, topics discussed, and
Biradar
conclusion/s agreed upon if any. Responsible for
organising and safekeeping of the Logs and their
distribution among all team members.
Determine and allocate appropriate user access to tables,

plans, and any other database objects used in the project in
accordance with the security guidelines.
Set up and maintenance of security rights and access
permissions.
Security Co-ordinator Adinigara
Manage data security
Understands client/server system thoroughly
Participates in disaster recovery measures
Maintains database integrity
Oversees system functions
Assists with Database maintenance

of 21
-Develop and enforce BSDMS building standards.

-Create instances and databases with appropriate
initialization parameters and database structures (i.e.,
datafiles, rollback segments, tablespaces, etc.)
-Manage physical database resources
-Develop database administration tools/utilities/operation Shobana
Lead Builder
procedures Rajendran
-Participating in database migration reviews
-Assisting in product installation & reviewing initial
installation options; for Oracle, the Central DBA will
assist in product installation and specify initial installation
options
Responsible for the BSDMS architecture and overseeing

design activities. Also responsible for the product detailed
design, its functionality, integrity and maintenance
Involved in various phases of Software Development Life
Cycle (SDLC) including Performance Tuning, Testing,
Design and Architecture.
Lead Designer As appropriate may assign sub-leads for functional areas Adinigara
of the product or for technical specialties such as database,
web design and graphics, distributed processing,
communications protocol, etc.
Developing & maintaining naming standards for database
objects such as tablespaces, tables, indexes & views
Interfaces with other systems already in place.
Main responsibility to ensure that all requirements of ISO

9001:2008 standards are applicable to the product
Standards Co- provided with this project. Alexis
ordinator Must ensure that product standards and requirements Medina
comply with the industry and regulations standards and
requirements

of 21
Ensures that appropriate quality checking activities are

included in the project plan and that the team perform
these tasks properly.
Planning
-Prepare a project QA plan that identifies quality activities
and resource requirement
-Verify that plans are reviewed by all affected project
stakeholders.
Project Start-up
Quality Assurance -Verify that requirements are clear, verifiable and testable Shobana
Co-ordinator -Ensure that risks are properly identified and tracked Rajendran
Project Performance
-Verify that the sponsor and project policies are followed
-Collect and analyse project metric data
-Coordinate formal QA reviews and audits
-Observe testing and inspect product test reports
-verify deliverables for conformance to standards
Close-out
-Achieve project metric data
-Certify readiness of the final product ( BSDMS)
Responsible for ensuring that all hardware requirements

Hardware have been addressed and complied with, providing solid
Management ground for successful product development and integration
with the sponsor current system.
Monitor the overall health of the network, server

deployment, security, and ensuring that the network
Network
connectivity throughout a company's LAN/WAN
Administrator
infrastructure is on par with technical considerations at the
network level of an organization's hierarchy.
-Review performance, maintenance and utilities associated

with each structure of the BSDMS
-Review necessary storage media for the product
Testing Co-
-Review SQL performance and Tuning Alexis Medina
ordinator
-Reviewing application's access to the database structures
-Review and test backup & recovery strategies
-Evaluate and test new features/functionality

of 21
Role:
Implementation of Services into Data Centres.
Relocation of client IT & communications equipment
Audit, plan, build, relocate, document services for
handover to operational units.
Project manage Data Centre implementation activities.
Hands on role.
Implementation Responsibilities: Goran
Co-ordinator Co-ordinate all activities regarding implementation of Krstevski
the final project product (BSDMS) into the client working
environment
Carry out product implementation audits.

Co-ordinate service for product onsite delivery.
Installation of product services to established standards.
Work with project managers to meet product
implementation deadline.
Role includes but is not limited to organising and

executing the project deliverables in a form of a
Presentation Shobana
presentation in front of the audience at the end of the
Co-ordinator Rajendran
project. Responsible for the overall quality of project
presentation
3.4 Project facilities and resources

For the purposes of this project, it is expected that DATA will be able to use existing computer
equipment at premises in St. George TAFE in Kogarah, to conduct this project. Microsoft Software
applications such as SQL Database 2008 and Visual Studio 2008 will be required from the faculty and
they will be acquired with the assistance of Project Manager. As mentioned above, Jong Lek will be
responsible for coordinating the acquisition of required software as well as providing all other
resources necessary for the duration of the project.
This facility will also have the capacity and flexibility to be used for co-curricular project associated
activities that will be undertaken outside of timetabled class time. Allocation of any specific time
resources and facilities will be documented in the Project Team Daily Logs.

of 21
Section 4. Project References

Table below provide the intended reader with information concerning the project key deliverables.
It describe and identify the location of key documents that define and establish the BSDMS project.
Version Author and Location (link or

Document Title Date
No. Organization path)
P:\CIOB\Project
1. Project Charter 1.0 03/08/2010 DATA
Charter
2. Project Management
DATA
Plan
2.1 Schedule DATA
2.2 Human resources DATA
2.2.1 App. A – Standards DATA
2.2.2 App. B – Quality

DATA
Assurance
3. Requirements
DATA
Specification Report
4. Design Report DATA
4.1 System Design DATA
4.2 Database Design DATA
5. Build Solution
( Build the System and DATA

Database)
6. Testing
DATA
Documentation
6.1 In-house Testing DATA
6.2 System Testing DATA
7. Implementation Plan DATA

of 21
Version Author and Location (link or

Document Title Date
No. Organization path)
7.1 App. A – Disaster

DATA
Recovery Plan
Section 5. Glossary and Acronyms

The following is a listing of all terms and acronyms that are required to interpret the project charter
properly.
Term or Acronym Definition
Database Analysis Team Associates – Private System Application

DATA Development IT Company that consist of 5 members plus Project
Manager
Star Supermarket – Project initiator and sponsor that formally authorize

CLIENT the existence of this project, and provide the DATA Manager with the
authority to apply DATA organizational resources to project activities.
Database Management System – Computer software program that is

DBMS designed as the means of managing all databases that are currently
installed on a system hard drive or network.
Business Service Database Management System – Software Application

Solution Designed for Star Supermarket that computerise the company
BSDMS whole IT infrastructure and automate client complex pricing strategies,
streamline inventory management processes, improve warehouse
efficiencies, and execute consistently across the enterprise
Project Manager – outside affiliate to DATA Responsible for developing,

in conjunction with the Project Sponsor the definition of the project and
PM responsible for managing the work of the team members, allocating and
utilising resources in an efficient manner and maintaining a co-operative,
motivated and successful team.

of 21
Any person or group that has an active interest in the project outcome or
process.
Project stakeholders are those entities within or outside an organization
which have interest in the project. In this project they are:
STAKEHOLDER – Star Supermarket – sponsor of the project
– Project leader, project team members, sponsor management team –
people that have or a gain upon successful completion of the project
– Project sponsor customers and user groups – people that have a positive
or negative influence in the project completion.

of 21

Project Charter: "Star Supermarket" Business Service Database Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Charter: "Star Supermarket" Business Service Database Management System

Uploaded by

Copyright:

Available Formats

“Star Supermarket”

Wednesday, March 23, 2016 Version: 1.0 Page 1

Version Draft: 0.1

Project Manager: Yong

Database Analysis Team Associates Project Leader:

 the project deliverables, schedule, milestones and estimated costs

Wednesday, March 23, 2016 Version: 1.0 Page 2

Section 1. Charter Introduction

1.1 Document change control

Sydney Institute St.

Initial Draft of Project Charter for

1.2 Executive summary

Wednesday, March 23, 2016 Version: 1.0 Page 3

Goals and Objectives

Simplifying processes by:

Wednesday, March 23, 2016 Version: 1.0 Page 4

Wednesday, March 23, 2016 Version: 1.0 Page 5

Section 2. Project Overview

2.1 Project summary

2.2 Project goals, business outcomes, and objectives

2.3 Project scope

2.3.1 Scope definition

Wednesday, March 23, 2016 Version: 1.0 Page 6

Activities in Scope Activities out of Scope

Insert additional explanations for project boundaries here.

Allocation of roles and responsibilities,

Indentifying Project Scope, Time Schedule,

Identifying functional and non-functional

Creating Domain Model, ER Diagram, System

Wednesday, March 23, 2016 Version: 1.0 Page 7

6. Testing Plan In-house testing, System testing, UAT 1-Nov-2010

7. Implementation Plan Disaster Recovery Plan 9-Nov-2010

8.Project Due Hard and Soft Copy of the project 12-Nov-2010

9.Post Implementation Review Review the whole project 19-Nov-2010

10.Internal Presentation Technical Presentation 24-Nov-2010

11.External presentation Non-Technical Presentation 29-Nov-2010

Milestones Deliverables Deliverables Due date

Wednesday, March 23, 2016 Version: 1.0 Page 8

2.6 Project cost estimate and sources of funding

2.6.1 Project cost estimate

Wednesday, March 23, 2016 Version: 1.0 Page 9

2.6.2 Sources of funding

 A related project expects a deliverable from your project;

 Your project expects a deliverable from a related project; or

Dependency Description Critical Date Contact

2.8 Project risks, assumptions, and constraints

Wednesday, March 23, 2016 Version: 1.0 Page 10

No. The following is assumed:

Wednesday, March 23, 2016 Version: 1.0 Page 11

No. Category Constraints

Section 3. Project Organization

3.1 Project governance

 A diagram should be used.

3.2 Project team structure

Project Role Assigned to

Project Leader Goran Krstevski

Deputy Leader Preeti Biradar

Recording Secretary Preeti Biradar

Security Co-ordinator Adinigara

Lead Builder Shobana Rajendran

Lead Designer Adinigara

Standards Co-ordinator Alexis Medina

Quality Assurance Co-ordinator Shobana Rajendran