Treasury 05a v3 0

CHAPTER 1.
0 - PROJECT CHARTER
1.1 Project Background
Treasury the name for the center of financial operations within a
company. The treasury is responsible for such things as issuing new
securities.
Treasury the funds or revenue of a government, corporation, or
institution, It is responsible for budgeting for and controlling public
expenditure, management of debt. It covers cash management, corporate
finance and financial risks management.
Treasury is constantly evolving, it is about the planning and operations,
cash and liquidity management, funding and capital markets, financial risks
management, stakeholder relations, cash flow forecasting, tax planning
clear and quantifiable approach to the future. It is related to accounts
payable and accounts payable. It is about the place where the money of
business is kept. Treasury is the one who arrange the expenses of costing
in terms of cash handlings. They are also handling the cash of customers.
1.1.1
Problem/ Opportunity Description
Poor control cost

If the prices of product gets higher they cannot control it.
Merchandising- Treasury Module System
Prices of commodities
The prices during yesterday session remain within a fairly narrow range
but the direction was down very long.
Out of stocks of some items to be sold
Some customers ask a product and it is out of stock so the store cannot
provide product which is out of stock.
Variances from cash to product
When their giving a change to their customers sometimes it cannot avoid
to commit mistake like giving a change more than the exact change. By
product there are some cases that there is mistaken by giving number of
product.
1.1.2
Benefits
Secure Data Records.

The treasury is responsible to secure all the data records especially
contracts regarding to the money that taken in and paid out by the
business so the proponents create a system that can secure all the
data records. By that they can assure that all the records are secured.
Faster and Efficient process due to automated transactions.
The proponents create a system that can make it faster and efficient
the business process of the treasury so the workload of the employees
will be lessen and easier.
The company will gain income, they will give benefits to their
employees.
The proponents create systems that can faster the process of the
company so it can lead to innovate the business. By that they gain
more customer and the company will gain income because of the good
service they will give benefits to their employees.
The system can check if how many people who requested in a day
and how much the money have taken in and paid out in business.
The treasury will record all the request and earn in a day they are
responsible to manage the money. So the proponents create a system
that can easily check the number of people who requested in a day and
also the money that taken in and paid out by the business.
1.1.3
Goals
To make it easily monitor the money that taken in and

out by a business.
To secure and safe with that it will prevent
unauthorized access of records and transactions.
To reduce manual data entry.

Improves short and long-term liquidity through
automatic
update
of
treasury
worksheets
Provides
complete auditing and tracking
To maintain their principal capital.

To monitor the money that taken in and paid out by the
business.To avoid bankrupt in company.
To provides complete auditing.

By creating a system that can provide a complete
auditing so that it can helps the employees to audit all the
transaction.
1.1.4
Stakeholders/Clients
Stakeholders
Auditor
Description/Participation
The one who audit the money like all
the
expenses of company. Auditors
examine personal and organizational

financial
records
to
verify
their
accuracy, detect fraud, and identify

opportunities for improving financial
Manager
processes.
Their
specialized
experience
can
organizations
identify
often
help
and
correct
financial inefficiencies.
The one who give fund to the
company. He or she coordinate with
various
departments
and
monitor
various store setups and resets in

region.
Develop and execute various store
rotation
schedule
for
appropriate
region.
Manage and validate model store
program for assign area.
Develop and ensure compliance to
budget for all merchandising process.
Supervise and ensure effectiveness of
all merchant activities.
Monitor retail price for competitors
and maintain appropriate pricing for
products accordingly.
Manage multiple projects, monitor
and allocate appropriate resources to
various accounts.
Monitor
Treasurer
and
apply
various
merchandising met
The one who in charge of the money
that taken in and paid out by a
company
Accounting
People who keep the financial records

of a company. Accounting Financial
accounting generates some of the key
company documents, including profit
and loss statement or P&Ls. P&Ls

show
the
business
financial
over
details
specific
of
period
Financial accounting also produces

the balance sheet which provides a
snapshot
of
business's
asset/">assets, debts, and equity at a

specific moment in time.. Financial
accounting also helps the managers
in the business is to manage more
efficiently by providing them views of
financial
information
which
may
include monthly management reports

presenting costs and profits against
budgets, sales, or other key metrics.
Reporting can be customized for the
specific needs of the business.
Lead Programmer
He/she will need to be able to

communicate your ideas and vision to
the programming team.
The Lead programmer leads the
programming team responsible for
creating all the computer code which
runs and controls a game.
Project Manager
The Project Manager is the person

responsible for ensuring that the
project team completes the project.
The Project Manager develops the
project plan with the team and
manages the teams performance of
project task
. It also the responsibility o0f the
project
manager
too
secure
acceptance
and
approval
of
deliverables from the Project Sponsor
and Stakeholders.
System Analyst
System
processing
analysts
analyze
problems
and
data
make
recommendation to help computer

systems operate more effectively and
efficiently.
System
analysts
often
begin a project by determining the

objective of a system
. They meet with managers and other
stakeholders to understand what the
system needs to do.
Business Analyst
Business Analyst is used to identify

and articulate the need for change in
how
organizations
work,
and
to
facilitate that change.

As business analyst he or she identify
and define the solution that will
maximize they value delivered by an
organization to its stakeholders.
Document Specialist will document all
Documents Specialist
the information regarding to the

System. He or she will be analyze the
solution to be well understand the
project.
1.2 Project Scope
1.2.1
Objectives
Security Information
To secure all the confidential information regarding the
funds of business.
To create a system that can organize the records of
people requested for the budget of their needs.

To update the information file of the treasury if
somebody request things or etc of their needs in work like
example laptops. The treasury are the one who provides
their expenses.
To create a system that can manage the money that

taken in and paid out of the company.
After they give the request to the treasury, the treasury
will record the request to the system so the system will
update. by that they can easily manage it.
To create a System that can easily search files.

By adding search engine to the system the
treasury can easily find all the financial records, like people
who requested in this day and money that taken out daily.
To create a system that is accessible and well

integrated to other modules
By integrating to other connected subsystem so that it
can faster the process of the company and it can lead to
innovate the business.

To create a cost-efficient, understandable, reliable and
user
friendly
system
for
every
merchandising
company that needs it.

By creating a system that is accessible and well
integrated to other modules.
1.2.2
Deliverables
Objective 1: Security Information

Project Deliverable
Work Products/Description
User Account
Limited users can log in the system
Objective 2: To create a system that can organize the records of people
requested for the budget of their needs.
Project Deliverable
Add a functionality that arrange the The system can arrange
and
records of people that request for organize the records of people who
budget
requested for the budget in the

proposed system
Objective 3: To create a system that can manage the money that taken in
and paid out of the company..
Project Deliverable
Add a functionality that monitors The system will monitor the money
the taking in and taking out of being
money
taken
in
the
treasury
consequently, the money taken out

of the treasury.
Objective 4: To create a System that can easily search files.

Project Deliverable
Search engine
Add search engine to the system
that will search for files needed
depended
on
what
has
been
searched.
Objective 5: To create a system that is accessible and well integrated to

other modules
Project Deliverable
Add a functionality that can access The system can access to the other
to other subsystem
subsystem. so if the system need

information to another system it
can easily access at once
Objective 6:To create a cost-efficient, understandable, reliable and user

friendly system for every merchandising company that needs it.

Project Deliverable
User Friendly System
Create a user friendly system that
can easily understand the system
so that the user can easily use it.
1.2.3
Out of scope
Monitoring of Sales
Monitoring of sales it will be the scope of sales
monitoring only report of sales is needed to the proposed
module.
Transaction of products
Transaction of products it will be the scope of point of
sales in doing the project integration. Only report of
All the accounts for recording transactions

All the accounts for recording transactions relating to a
company's assets, liabilities, owners' equity, revenue, and
expenses it will be the scope of general ledger in doing
the project integration.
1.2.4
Approval of request
Approve and payments of the request it will be the
scope of accounts payable and receivable. a record of
transaction and providing expenses of request will be the
scope of proposed module.
Enterprise Information System Required Functionalities

The following requirements must be included in this section:
Free Format Query

Personalized Screen
Analytical Report
1.3 Project Plan

1.3.1
Approach and Methodology
1.3.1.1 Methodology
The proponents use SDLC) as their methodology in doing
this project.
1.3.1.2 Approach
Phases
Plan
Planning
The Proponents conducted

an interview and surveyed
the people who involve for
the said project,
to keep all the documentation.
The proponents conducted a

meeting
for
the
brain
storming of the group.
Analysis
The Proponents analyze the
problems to solve those problems

Design
in treasury
The
proponents
research
about the design of the system

that
can
be
solve
those
problems in treasury.
In this phase, the proponents

integrated different ideas on
how the proposed system will
be user-friendly and obtain the
objective of generating the
system.
Implementation
In this phase, the system

needs to be tested and
undergo in a system defense
wherein the proponents will
present it to a group of
panelist. The panelist will
analyze the system if it satisfies
the needs of the users and the
panelist will tell if there will be
any revision to the system. The
created system will only be
implemented if it will be
consistent and free from errors.
Maintenance
1.3.2
I D T a s
1
S p o r t
2
M o c k
3
D o c u m
4
P r e
f
5
S
p
o
6
7
8
9
1
1
1
1
1
1
1
0
1
2
3
4
5
6
In this phase, the system is

already implemented. It is
important to determine who will
maintain the operation of the
system
. The proponents will be

discussing the flow, the
content, the availability and
how the system will be
maintained.
Project Timeline
k
a m e
f e s t
( B S I T )
D e f e n s e
e n t R e v i s i o n
i n a l
E x a m
r
t
f
e
s
t
D
a
t
e
September 10,2014
September 11,2014
September 22,2014
September 24-27
September 29,30 & Oct 1,2014
D u r a t
1
D
1
D
1
D
3
D a
3
D a
i o
a
a
a
y s
y
n
y
y
y
M e e t i n g o n A d v i s e r
P a y m e n t
o f
E x a m
F i n a l
D e f e n s e
F i n a l
E x a m
Doing Configuration Management Plan
S
e
m
b
r
e
a
k
Doing Software Quality Assurance
S ys t e m S p e ci fi ca ti o n
Doing Software requirement specification
October 7,2014
October 13-16
October 18,2104
October 23-25,2014
October 27-31
Nov.1-4,2014
N o v . 1 0
N o v . 1 2 - 1 6
N o v . 2 4 - 2 5
D
e
c
.
3
D e c . 4 - 5
1
3
1
3
5
4
1
5
2
1
2
a
y
a
y
y
y
y
y
y
a
y
y
s
y
s
s
s
s
s
s
y
s
d
D
a
D
D
d
D
d
D
D
a
a
a
a
a
a
D
1
1
1
2
2
2
2
2
2
2
2
2
2
3
3
3
3
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
P r e l i m
P a y m e n t
P r e l i m
E x a m
S
e
m
b
r
e
a
k
Doing software design specification
M e e t i n g o n a d v i s e r
M i d t e r m
P a y m e n t
Doing Software Design Specification
M i d t e r m
E x a m
Doing Software Design Specification
Pa ym en t o f P re-Fi na l
D
e
f
e
n
s
e
P r e - f i n a l
E x a m
M e e t i n g o n a d v i s e r
T e s t S p e c i f i c a t i o n
P a y m e n t
o f
F i n a l
T e s t S p e c i f i c a t i o n
F i n a l
E x a m
1.3.3
D e c . 9 - 1 2
D e c . 1 8 - 1 9
D e c . 2 1 - 3 1
Jan. 5-13,2015
Ja n .1 4 ,10 1 4
J a n . 1 5 - 1 7
Jan.19-24,1015
Jan.22-3,1015
Feb.2-6,2015
Feb.16-18,2015
Feb.20,201 5
Feb.26-27,2015
March 2,2015
March 9-13,2015
March 16-18,201 5
March 23-27,2015
April 13-14,2015
4
2
1 1
9
1
3
6
2
5
3
1
2
1
6
3
6
2
D
D
a y
a y
D a y
D a y
D
a
D a y
D a y
D a y
D a y
D a y
D
a
D a y
D
a
D a y
D a y
D a y
D a y s
Success Criteria
The project is considered a success if the documents and
systems passed the standard implemented for the project.
The project is considered a success if the system is fully
functional and were able to cater transactions, generate
accurate reports.
The project is success if the system met the requirements
of the users. User is an important part of the system, thus
this project must conform to the needs of the user to be
considered a success.
The project is considered a success if the panel will
approved the system.
The project is considered a success if the team members
will pass all the requirements to the system.
1.3.4
Issues and Policy Implications
s
s
s
s
y
s
s
s
s
s
y
s
y
s
s
s
Issues
Disbursement
Policy Implications
Every request that they give to the
treasury it must be always have
request form as proof. Every money
that taken in it will be recorded.
When it comes in deposit it is about
Deposit
the collection of money of treasury

that came from cashier then it will be
deposit on bank
When you fork out of the money to
Reimbursement
buy a things needed in company it

must always have the attachment of
petty cash together with the receipt
and how much you fork out.
In Liquidation it is all about the money
Liquidation
that taken in and paid out by the

treasury. It is about the asset and
liabilities.
In withdrawal process, when the
Withdrawal
treasury
receive
request
from
department then it should be need a

large amount of money they will
withdraw the money that they request
or either issuance of cheque.
1.3.5
Risk factor
Risk Management Plan

Probability
Impact
Risk
management
Expenses of the H
action
Keep the money
project
to continuously
Availability
the project.
Arrive
early
of H
time
before
the
Availability
of H
team members
meeting started.
Set the meeting
before
on
the
date you set. so

the
team
members
System
error/lost
can
prepare that day.

Make sure that
the
team
members
must
know to operate
the system.
1.3.6
Service Transition
The importance of the service transition is to help regarding the technical

problem in the system.
The IT Support Center

The one who is responsible to solve the problems in the
system.They communicate incident status information to customers
IT Coordinator
They are responsible to assist in preparing technical and functional
documentations for operating systems.
1.3.7
Option Analysis
Strategic interventions
Alternative Options
In terms of system integration, the By cooperating all the project team to
project team will be on the guard for do any changes.
any adjustment and revision that will
be
needed
by
the
whole
Merchandising system.
In terms of the budget, the whole
There must be always have a budget
team will stick in the budget of the for the expenses of the system by
project
however
unexpected
if
there
necessities
for
are saving money of the project team.

the
project, the team will produce the

needed
money
to
support
the
necessities.
In terms of software that will be used it
should
be
licensed
and
for
It is needed to provide a laptop or
the own gadget at least 2 in one group to
technical support that team will have develop a project.

their own gadget or laptops that is
needed for the development.
1.4.0
Technical Features
NETBEANS
The proponents used NETBEANS IDE version 7.3.1.for implementing a
system because of the special features of the software NETBEANS is an

open source integrated development environment (IDE) for developing a
primarily with java, php, c++ and other programming languages that aims
to help developers build any type of application. NETBEANS is coded in
java and runs on most operating systems with a java virtual machine
(JVM), including Solaris, Mac OS, and Linux.
NETBEANS platform allows application to be developed from a set of
modular software components called modules. Application based on the
NETBEANS platform (including the NETBEANS IDE itself) can be extended by
third party developers.
Hardware Specification:
Processor
Minimum requirement is 2.6 GHz and recommended requirement is
3.3 GHz or higher
Memory
Minimum requirement of 1 to 2 GB and the recommended
requirements is 2GB or higher
Hard Drive
Minimum requirement is 80 to 250 GB and the recommended
requirement is 500 GB or higher.
Software Specification Use
Operating System
Windows 7 or higher serves as the environment for the
development of the system
MSSQL
The Proponents use MSSQL for database software because it is the
most powerful MSSQL manager and admin tool, combining the features
of MSSQL Administrator, phpMyAdmin and other Front Ends and
MSSQL GUI tools. MSSql is a relational database management
systems developed by Microsoft. As a database, it is a software product
whose primary function is to store and retrieve data as requested by
other software applications
1.5 PROJECT ORGANIZATIONS AND STAFFING

Role
Project Manager
Name
Francia. Angelica
Responsibilities
She is responsible of the
planning,
controlling,
facilitating,
decision
making, and all knowing
about
the
propose
system
Business Analyst
Globiogo. Jean Rose
He or she is responsible
in knowing the problems
pertaining
to
the
researches about the
proposed system.
System Analyst
Eria. Mega
She is responsible for

knowing the solutions of
the problems given by
the Business Analyst
throughout the system
making. She will be able
to give the flow of the
system
Lead Programmer
Alburo. Marichu
She is responsible in
creating the front end
and the back end of the
system by means of
programming.
Alcon. Merla
She is responsible in
documenting all what
has happened in the
system making.
Adviser
Mr. Constantino
He is responsible for
guiding and give some
helpful ideal tips to the
group.
1.6 Project Budget

B u d g e t
O
i t e m
1 5 0 0 . 0 0
F a r e ( S u r v e y )
1 0 0 . 0 0
O n g o i n g
F
C o s t
e
3 0 0 . 0 0
2 5 0 0 . 0 0
Broadband (load)
2 0 0 0 . 0 0
5 0 . 0 0
2 0 0 . 0 0
B o o k b i n d e r
1 5 0 . 0 0
D e f e n s e
F e e
5 0 0 0 . 0 0
3 0 0 . 0 0
R e n t
i n t e r n e t
4 0 . 0 0
P r i n t
r e s e a r c h
3 0 . 0 0
D e s c r i p t i o n Budget cost
r
t
B
r
r
n
F o o d
F
p a n e l
l
1 0 0 . 0 0
1 0 . 0 0
F a r e ( m e e t i n g )
3 0 0 . 0 0
Tot a l O u t g o i n g C o s t
13,380.00
CHAPTER 2.0 Related Studies

2.1 INTRODUCTION
This chapter tackles about the related studies of the proponents. It
serves as a guide for their studies and to help the proponents to better
understand and aid us in completing the development of the said project.
The Proponents chose
2.1 FOREIGN STUDIES
2.1.1
Chesapeakes Smart Treasury it represents as their
related studies for treasury process of the system goes like this,
Comprehensive treasury reports, Smart Treasury has all of the
functionality you need in a treasury workstation without the superfluous
features you dont need (and dont want to pay for). Updates and
enhancements to the system are driven by customer feedback and
requests. The implementation process is driven by close involvement
from Chesapeake, with continued assistance as required. Smart
Treasury offers the look and feel of Excel, but with the enhanced
database and filtering capabilities of a high-end treasury workstation.
Reduces manual data entry Improves short and long-term liquidity
through automatic update of treasury worksheets Provides complete
auditing and tracking Assures timely and consistent wire, ACH, and
SWIFT initiation across bank accounts Centralizes cash management,
debt and investment data Minimizes the opportunity for fraud.
http://www.chessys.com/products/smarttreasury/ And these are
the following foreign related studies.
2.1.2
Treasury Services
Structurally improves the bottom line of its clients by cutting their
costs and by improving their efficiency in finance. We create a

competitive advantage for our clients by implementing financial
excellence.
Treasury Services offers Treasury Consultancy & Advice, Treasury

Management Software, Treasury Training & Education, Financial
Engineering Solutions and Treasury Outsourcing Services. With these
building blocks we can create complete solutions in Treasury
Management, Cash Management, Risk Management, Corporate
Finance and Treasury Control.
On the right-hand side of this WEB site, under Solutions, you can read
how our expertise can be applied to add value for your organization.
Treasury Services has an international portfolio of corporate, financial
institutions and not-for-the-profit organizations as clients. You can find
examples
of
our
proven
track
record
under
Client
Cases.
http://www.treasuryservices.be/
2.1.3
Treasury
Treasury's mission highlights its role as the steward of U.S.
economic and financial systems, and as an influential participant in
the world economy.
The Treasury Department is the executive agency responsible for
promoting economic prosperity and ensuring the financial security of

the United States. The Department is responsible for a wide range of
activities such as advising the President on economic and financial
issues, encouraging sustainable economic growth, and fostering
improved governance in financial institutions. The Department of the
Treasury operates and maintains systems that are critical to the
nation's financial infrastructure, such as the production of coin and
currency, the disbursement of payments to the American public,
revenue collection, and the borrowing of funds necessary to run the
federal government. The Department works with other federal
agencies, foreign governments, and international financial institutions
to encourage global economic growth, raise standards of living, and to
the extent possible, predict and prevent economic and financial crises.
The Treasury Department also performs a critical and far-reaching role
in enhancing national security by implementing economic sanctions
against foreign threats to the U.S., identifying and targeting the
financial support networks of national security threats, and improving
the safeguards of our financial systems.
Organization
The Department of the Treasury is organized into two major components the
Departmental offices and the operating bureaus. The Departmental Offices are
primarily responsible for the formulation of policy and management of the
Department as a whole, while the operating bureaus carry out the specific
operations assigned to the Department. Our bureaus make up 98% of the
Treasury work force. The basic functions of the Department of the Treasury
include:
Managing Federal finances;
Collecting taxes, duties and monies paid to and due to the U.S. and
paying all bills of the U.S.;
Currency and coinage;
Managing Government accounts and the public debt;
Supervising national banks and thrift institutions;
Advising on domestic and international financial, monetary, economic,

trade and tax policy;
Enforcing Federal finance and tax laws;
Investigating and prosecuting tax evaders, counterfeiters, and forgers.
2.1.4
The Treasury vision and management objective
Our visionA world-class Treasury working for higher living standards for
New
ZealandersOur
management
objectives
(T-I-M-E)Our
four
management objectives summarize how were going to achieve our vision:

T Take the lead
Shape the economic agenda and proactively identify new areas of
opportunity.
Anticipate ministerial needs and issues for the future and position
ourselves to improve
advice on key Government priorities.
Respond
quickly
and
innovatively
to
changing
demands
and
circumstances.
I Invest in our organization and its people
Encourage and develop effective leadership.
Enhance the capability of our people, addressing any talent gaps to
support our outcome priorities.
Develop the systems, structures and processes required to become a
more flexible and

capable organization
http://www.treasury.govt.nz/
2.1.5
Tanzania
Currency risk management is a sensitive area the banking
business. In todays
increased volatility, there is tendency for commercial banks to
position currency
risk management function under the treasury stewardship. The
study indicates the case to be the same for Tanzania commercial
banks. In the study respondents indicated that there is a treasury
function in their organigram that is separated between front and
back office. (89%) of the respondents agreed that they have well
established treasury function in their banks, whose among other
roles, currency risk management is their major area of concern.
Out of them, 78% of the respondents indicated that treasury unit is
separated between back and front office. This is necessary for
prudent currency risk management where separation of roles and
responsibilities is not only a requirement, but inevitable. While 67%
of the respondents (most of them being multinational banks)
indicated that, they have had treasury functions separated before
the BOT risk management guideline requirement issued in 2005,
33% have indicated that the BOT risk management guideline has
played a major role towards facilitation in the establishment of the
structure.
Though separation of treasury is imperative for best practice and
prudent risk management in banks, these separate reporting lines
are as well necessary for ensuring real segregation of duties. In
this regard, treasury front office which is headed by the treasurer.
(67%) and (22%) responded that the treasury front office reports to
the CEO and Head (Director) of finance respectively, while (11%)
were not sure. On the other hand, treasury back office which is
responsible for risk monitoring and control is headed by the
Treasury Operations Manager who reports to the Head of Finance
(22%), Head of Operations (56%) and 22% were not sure. The
magnitude of treasury front offices role in relation to foreign
currency trading is mainly around currency trading, and marketmaking. Respondent agreed that treasury front office is regarded
as profit centre for their banks. As indicated above, back office is
responsible for risk monitoring, evaluation and control for what
treasury front office does. Hence treasury back office role is
specifically risk management related. Respondents reported that
settlement risk, confirmation risk, position management risk, and
the attached penalties for failure or late submission of the foreign
currency trading and position management of the bank to the BOT
are their major areas of concerned. Findings from the study also
uncovered that, before the introduction of the modern treasury
structure,
the
traditional
methodology
for
currency
risk
management was to assign risks among different departments in

the bank, mainly finance, operations and/or auditing.
. Treasury Capacity for Currency Risk Management
This study was designed to find out whether treasury management unit
(for commercial banks in Tanzania) possesses the necessary tools,
techniques and treasury management information system (TMIS)
necessary for currency risk management. The study revealed that lack
of the tools, techniques and TMIS is a major concerned for most
commercial banks in Tanzania especially for small local banks. 56% of

respondents agree that senior management have been affording the
necessary support in terms of allocation of appropriate resources to
enable the treasury function carry their risk management function
accordingly. Only 33% of the respondents disagree to experience lack
of resources problem in the currency trading and risk management in
their banks.The increased volatility of the international foreign
exchange market generates increased financial risk especially to
commercial banks. Exchange rate change is one of the financial risks
where the increased volatility is reflected to the greatest extent.
Therefore, if banks are to measure, price, and control currency risk,
they must establish an appropriate unit responsible for currency risk
management. This paper attempts to show that, commercial banks in
Tanzania have the necessary resources to curb risks associated to
currency risks. This paper briefly provide some highlights on the
research findings as regards to the role of treasury management in
currency risk management and then poses recommendations and
challenges on the magnitude of sustainability of the registered best
practice for currency risk management in commercial banks. The study
employed both primary and secondary data with a comparative case
study orientation. Published financial statements and other desk
materials were collected principally from selected banks. Interviews
were also conducted with responsible treasury managers. There are
various ways (economic, translation and transaction), that the bank
can utilize in analyzing and setting the exchange rate risk
management. In this study, transaction and translation exposure were
the chosen methods of analysis.
2.2 The local related studies of the proponents
2.2.1
NSW Government
The Proponents chose NSW Government it represents as
their local related studies for treasury process of the system
goes like this, Fiscal and Economic Group
The Fiscal and Economic Group provides policy advice to
the Treasurer and other government agencies on economic
conditions and microeconomic reform, the fiscal outlook, and
fiscal policy and credit rating issues.
The Group also provides advice on revenue and expenditure
strategies
and
policies,
taxation
and
intergovernmental
financial relations, public sector financial framework reforms

and accounting policy, and the management of debt,
superannuation, self-insurance and other liabilities.
The Fiscal and Economic Group coordinates preparation of the
State Budget, Half-Yearly Review and annual Total State
Sector Accounts.
Resource Allocation Group

The Resource Allocation Group contributes to a strong and
sustainable financial and economic environment in NSW by
supporting the implementation of the Governments fiscal strategy,
micro-economic reforms and other measures to manage expense
growth across the government sector.
The Group provides advice on the efficient and effective use of the
States resources in the areas of health, justice, family and
community services, education, transport, planning, trade and
investment, environment and government services. It improves
agency awareness of the states fiscal constraints to develop a
shared understanding of goals and challenges.
Commercial Group
The Commercial Group provides commercial policy advice,
oversights the
Government,
performance
of the
commercial
sector of
manages major Government transaction
and
structures arrangements for the private financing of public

infrastructure.
The Group undertakes shareholder monitoring of State Owned
Corporations and shareholder governance functions and identifies
areas for better management of the States commercial assets.
It also undertakes scoping studies for major transactions and their
relationship with public policy and regulation and manages the
execution of transactions.
The Commercial Group fosters private sector involvement in major
capital projects through innovative financing structures and
allocation of risk. It monitors the compliance of projects with major
Government risk and provides advice on opportunities to better
manage the State's assets and liabilities. It also advises on
property purchases and sales and other areas of commercial
asset management.
Industrial Relations
NSW Industrial Relations (NSW IR) works to ensure NSW private
sector businesses comply with their responsibilities under NSW
industrial relations laws, including NSW laws regulating long
service leave, the entertainment industry, transport and taxi
industry contract determinations, shop trading hours and public
holidays; and ensures compliance with the NSW Guidelines for
construction procurement. As part of its compliance activities NSW
IR provides a comprehensive education program, including
workshops and presentation, and has a dedicated unit to help
Aboriginal and Torres Strait Islanders in NSW understand their

rights
and
responsibilities
as
employees,
employers
and
managers.
NSW IR provides strategic policy and advice to the Government
on both private and public sector industrial relations issues and
actively participates as a partner in the Commonwealths national
workplace relations framework. It supports public sector agencies
on industrial relations matters and represents the Secretary of The
Treasury, as the employer, and the Minister for Industrial Relations
in proceedings before the NSW Industrial Relations Commission
and Fair Work Commission.
The Long Service Corporation administers long service leave
schemes for workers in both the building and construction, and
contract cleaning industries in NSW.
Corporate Group
The Corporate Group delivers services to Treasury across a range
of corporate areas including finance and administration, human
resources, information management and technology, executive
and ministerial services, communications, project management,
corporate planning and risk management.
The
Corporate
Group
provides
leadership
for
strategies,
structures and tools that promote a high performance culture and

a capable, change-ready workforce.
Treasury Circulars
The Treasury website is the main vehicle for the issue of Treasury
Circulars to NSW Government agencies. Agencies are advised by
email when a new Circular is issued and are provided with the link
to where it sits on the website. Agencies are responsible for
ensuring appropriate distribution of the Circular within their
organization. Treasury's policy is for Treasury Circulars older than

5 years to lapse as at 31 December each year, except for certain
specified Circulars.
NB: Refer to the withdrawn circulars list for any missing numbers
in the current list.
Current NSW Treasury Circulars

Treasury Circulars - 2014
Pre-2009 Treasury Circulars
Withdrawn Treasury Circulars

Treasury Circulars (no longer valid)
Treasury Circulars by Policy Area

Financial Reporting - Treasury Circulars
Annual Reporting - Treasury Circulars
Financial Reports
NSW Treasury issues a variety of financial reports on behalf of the
Government outlining the status of State finances. These are required by the
Public Finance and Audit Act 1983. Proper reports on the management of the
State's finances ensure the accountability of Government to its constituents.
Monthly Statements
Half-Yearly Review
Statement of Uncommitted Funds (2011 State Election)
Report on State Finances

Monthly Statements for the financial years:
2013-2014
2012-2013
2011-2012
2010-2011
2009-2010
2008-2009
2007-2008
2006-2007
2005-2006
2004-2005
2003-2004
2002-2003
2001-2002
2000-2001
1999-2000
1998-1999
Consolidated Financial Statements

NSW Total State Sector (Incorporating the NSW Public Accounts)20002001
NSW Total State Sector (Incorporating the Public Accounts)1997-1998
Consolidated Financial Statement of the NSW Public Sector 1996-97
(Incorporating
Public
Accounts)
NSW Budget Sector Consolidated Financial Statements: July December
1996
(Unaudited)
2.2.2
AvantGard Treasury
SunGard's AvantGard Treasury solutions include sophisticated
risk management, cash management, settlements, and managed

bank connectivity with an embedded SWIFT Service bureau. The
solutions can be deployed on premises, in a private hosted
environment or via SaaS delivery.
What we offer
Treasury Risk AnalysisSGN Short-Term Cash Management
SGN Short-Term Cash Management (STCM) portal is a global, multifund cash investment solution for institutional short-term liquidity
investors.
Utilized
by
treasury
and
investment
specialists
at
corporations, hedge funds, public utilities, governments, and colleges

and universities.
SGN STCM provides the ability to research, analyze and submit trades
as well as report on hundreds of money market funds and short-term
cash investments through a single connection.

Features Offers access to a centralized custody and settlement service
by establishing a brokerage account through a tier one clearing firm or
via direct access to the fund company with complete transparency
Provides investment risk analysis Automates the distribution and
coordination of settlement information Offers access to hundreds of
domestic and off-shore funds for greater diversification of holdings
Centralizes transaction and holding data for immediate audit retrieval
across the organization Allows you to set compliance rules,
concentration limits and fund ownership restrictions Provides multiple
levels of control on a trade for up to five approvals Benefits Helps to
increase operational efficiencies with consolidated wire transfers
through a custody model that has an established brokerage account
through a tier one clearing firm Identifies trading partners with a direct
model Helps mitigate risk by aggregating counterparty information,
using meaningful and timely fund analytics and holdings information
across
security
types
Integrates
with
multinational
treasury
management systems to help eliminate the need to re-key daily rate

and trade confirmations Provides one centralized, automated source to
buy and sell shares in institutional money market funds Streamlines
cash management with one-stop trading across multiple money fund
providers Supports variable NAV and accumulation NAV fund types
SunGards Fox River Execution Solutions and SGN brokerage services
offered within the United States and Canada are provided by SunGard
Brokerage & Securities Services LLC, Member NYSE, FINRA, SIPC.
SGN brokerage services offered throughout Europe, the Middle East,
Africa and Asia Pacific are provided by SunGard Global Execution
Services Limited which is authorized and regulated by the Financial
Conduct Authority, No. 469919 * Incorporated and registered in
England and Wales No. 3127109 * Registered Office: 25 Canada
Square, London E14 5LQ.
SunGard Global Execution Services Limited (ARBN No. 132 508 742)
is exempted from licensing under Australia Securities & Investments
Commission Class Order 03/1099 and is regulated by the Financial
Conduct Authority under UK laws, which differ from Australian laws.
Terms
of
Use / Privacy
Policy / Important
Disclosures / Business
Continuity Plan / Statement of Financial Condition / Index

Cash Management
Cash management is not a simple task. The typical treasury operation
has to manage daily or intraday cash positioning, bank communication,
reconciliation, cash forecasting, zero-balancing pooling and multilateral
netting to name a few.
Often times, these tasks can be challenging as data is scattered
across disparate sources and processes are manual due to the continued
use of spreadsheets. Having access to consolidated information from
multiple sources, and in real-time is critical.
SunGard's AvantGard Treasury is a comprehensive treasury, risk and
cash management solution that helps drive integration, automation,
visibility and collaboration. It improves decision making, reduces manual
processing, decreases operating costs and drives improved management
of liquidity and risk.
Features Cash positioning and forecasting Prior and intraday
reconciliation Bank communication and interfacing Payments processing
with lockbox support Cash pooling/sweeping/zero-balancing Tiered bank
account and interest structures
Benefits Gain real-time global visibility into daily cash Manage multiple
bank relationships from a central point Compliance with segregation of
dutiesEfficient utilization of available cash Maximize returns as decisions

are based on accurate and up-to-date information
Cash Forecasting
Accurate cash flow forecasting is vital to the growth and success of a
business. In order to ensure that a company can meet its financial
obligations, the treasurer needs an accurate view of the companys future
funding requirements.
For many companies still relying on spreadsheets and enterprise
resource planning (ERP) systems, cash forecasting is a challenge. In
many cases, forecast information derived from different business units and
regions is prone to wide variations and assumptions in the way it is
constructed. Data is often times unreliable and difficult to combine in a
coherent, consistent fashion.
SunGards AvantGard Cash Forecasting solution automates cash
forecasting for real-time, global visibility of cash and improved cash
management. By providing a way to collect, analyze and project forecasted
cash flows, the solution empowers corporate treasures to make informed,
accurate predictions.
Features Leverage actual transaction history to predict future cash
flows Identify unanticipated inventory changes Configurable model for
viewing historical trends Flexible reporting Track seasonal trends
Benefits Real-time global visibility of cash Improved cash management

Flexible options for modeling Improved decision making Maximize interest
earned and decrease interest expense Discern patterns using statistical
analysis of historical transactions
Deal and Trade Capture
The role of the treasury dealer is to generate trading profits and

optimize liquidity for the organization. To do this, the dealer needs a
system that can aid in pre-deal decision making while also helping to
reduce operational risk.
SunGard's AvantGard Treasury Dealing solution provides the dealer
with an integrated desk-top that provides all of the information required for
pre-deal decision making, such as up-to the minute position reporting,
pricing tools and pre-deal credit limit checking. The flexible user interface
is designed for fast recording of the transaction where it is done over the
phone or seamless straight-through processing (STP) where a portal is
used.
Features Pre-deal credit limit checking Pricing models Flexible user
interface Dealing blotters Foreign language, including Unicode Straightthrough processing (STP) with money market and FX portalsDetailed audit
trail Flexible automated workflow Benefits Improves decision making
Reduces operational risk Increases operational efficiency
Settlement
Global organizations typically execute a large amount of inter-company
transactions, and in a multitude of currencies. This naturally escalates
costs as payment volumes and cross border transactions increase as do
transaction fees and bank charges. Without active management,
significant foreign exchange exposures can build up and considerably
increase risk to earnings.
SunGard's
AvantGard
Netting
provides
comprehensive
multilateral netting solution that allows a global organization to

efficiently manage inter-company transactions and to settle them
internally, reducing the number of external payments, cross border
flows and foreign exchange deals. The operational efficiencies realized
through netting inter-company invoices translate directly into reduced

bank fees, bank balances and currency conversion costs.
Features
Seamless
processing
of
external
cash
settlement
transactions In-house bank transactions, inter-company loans and foreign

exchange deals User-defined netting cycles and currencies Foreign
exchange dealing sheet Netting statements and confirmation letters
Benefits Decreases or eliminates cross border flows at the business unit
level Reduces or eliminates inter-company payment volumes Reduces
bank fees and charges Establishes clear settlement timeframes for intercompany transactions
Accounting/Hedge Accounting
Most CFOs recognize the value of hedge accounting as a way to
reduce
corporate
documentation,
earnings
ongoing
volatility. However, the
monitoring
and
reporting
burden
of
of
hedge
effectiveness, high costs, and the need to maintain compliance with

hedge accounting standards has many struggling with and even
foregoing this important activity.
SunGard's AvantGard Treasury Hedge Accounting is a fully integrated
solution that helps automate hedge accounting management. It
reduces manual intervention as, well as operational risk and provides
greater control and transparency over hedge accounting processes.
Flexible valuation models and comprehensive reporting functionality
help ensure compliance with hedge accounting standards such as IAS
39 and FAS 133.
Features
Complete
solution
(recording,
analysis,
reporting,
accounting)"One-step posting and recording of results Full valuation

throughout the life of the hedge Hedge documentation from inception
Flexible valuation models Credit/non-performance risk models Benefits
Helps you achieve compliance Keeps you up-to-date with the latest
accounting standards Offers short-cut or long-haul accounting methods

Increases operational efficiency
In-House Banking
Operating in a global economy often means that cash is deposited in
disparate bank accounts around the world and the structure of these
bank accounts is sometimes necessarily complex. Failure to manage
the operational risks relating to these accounts can lead to loss of
funds or the misreporting of financial statements. It is essential for
treasurers to put effective controls in place and to have complete
visibility to cash. Failure to do so can result in significant losses for a
corporation.
SunGard's AvantGard Bank Account Compliance solution can help
treasurers to put into place the appropriate procedures that will help
them to maintain tight control over their bank accounts. As an
extension to existing treasury system functionality, this solution
supports and simplifies the certification process and audit requests
each quarter, making it part of the standard bank relationship
management process within the treasury.
Features Manages and tracks bank accounts in a centralized
repository Maintains accounts, contacts and signatories, all in a single
location Performs bank fee analysis Systematically tracks all
enterprise-wide bank accounts Maintains rank relationship structures
and the corresponding bank contacts Keeps complete records of
qualified
corporate
signers
and
their
applied
limits
Tracks
compensation analysis to perform service and fee analysis Benefits

Provides a single source for all banking communication Enhances
security and
controls Increases operational
efficiency through
automated mandate maintenance Reduces costs through bank fee

analysis
Bank Communication
30 percent of companies state that they operate with 25 or more cash
management banks. Managed bank connectivity can help reduce
operational costs and mitigate risk.
Treasury and payments solutions require secure and reliable
connections to banking partners. Historically, these connections were
made via proprietary one-off links to each individual bank. The
challenges that arise are often due to inflexible and proprietary
connections between corporations and their banks which force
corporations to pay higher connectivity development and maintenance
costs while also making it difficult to achieve true bank independence.
SunGard offers a hub and spoke approach with embedded SWIFT
connectivity for easier, more efficient, and less costly bank connectivity.
Corporations can benefit from a single connection that sends and receives
all confirmations, trades, payment instructions, account statements and
more from worldwide treasury operations. SunGard's ECHOS platform
manages all integration with your treasury, payments, and enterprise
resource planning (ERP) systems, along with data transformations and
bank messaging.
This is a managed service, which means that SunGard manages the
platform, all connectivity and transmissions, including your SWIFT
relationship.
SunGard is a global SWIFT partner and has both technical and serviceoriented SWIFT certifications.
AvantGard Treasury SunGard Financial Systems
http://financialsystems.sungard.com/solutions/corporate-liquidity/treasuryrisk-management/products
2.2.3
Finpacific treasury system

Corporate Treasury Solution Overhaul: GDF Suez
GDF Suez is the worlds largest global utility company, with
218,350 employees in nearly 70 countries and a turnover of
84.5 billion Euros in 2010. The company was formed after a
merger between Gaz De France and the Suez Company in
July 2008. As part of the merger process, they conducted a
review of their business critical systems to ensure the
appropriate tools were in place to manage the new
organization and ensure that all possible synergies would be
achieved.
The business challenge
The main priority for GDF Suez was to ensure they had
sufficiently robust financial systems and processes in place to
support communication and growth, whilst both minimizing
costs and maintaining shareholder and regulatory confidence.
As a result of the scale of GDF Suezs operations, the
complexity of their treasury function is similar to that of a
medium-sized bank. The primary challenge for the treasurer
was determining how to empower subsidiaries, while ensuring
they had enough transparency and control to benefit from
group synergies and shared services. They needed an efficient
cash management system that would support communication
between the center and the regions, making sure that sufficient
funds are available in the right locations, at the right time and
in the right currency. Most of all, they wanted to be sure that
money was not being borrowed from the market if there were
surpluses in other parts of the company.
The merger between the two companies had dramatically

increased
transaction
volumes,
operations
significantly more
making
complex.
their
Small
treasury
exception
management processes in existing tools had become costly,

with previously minor exposures to risk becoming sizeable.
The challenge for GDF Suez was how to effectively manage
this increased risk at both a regional and global level. As part
of a re-evaluation of GDF Suezs finance capabilities, the
company wanted to bring the treasury function closer to the
business. They wanted to establish a full payment value chain
across the organization from the capture of payments,
processing through central treasury and on to the swift network
directly to the bank. They also needed to ensure they were
fully IFRS compliant at both a central and regional level. The
final requirement for GDF Suez was to find a partner who
understood their business process and logic. They wanted to
form a partnership with a supplier that had a strong local
presence and would be able to advise them on business
processes as well as technical requirements.
The solution
GDF Suez was looking for a solution that would ensure the solvency of
the group one that could manage all business workflows, FX risk and
debt. After evaluating a number of systems they decided to invest
in Misys Corporate Treasury management system; Fusion Banking
Treasury Suite. They chose Fusion Banking Treasury Suite because of
the breadth of the offering, the flexibility and robustness of the product
and because it is supported by a team of specialists who instinctively
understand the challenges they face. GDF Suez is using Fusion
Banking Treasury Suite for the following:
Cash Management including Treasury centralization, reconciliation,
cash pooling, netting Deal management including investment
funding, debt management, IR and FX Risk, counterparty risk and swift
messaging Regional coordination using the web portal including,
cash management, funding/investment, FX Risk and Reporting

The results
GDF Suez now benefits from a single communication channel, as well as a
consolidated view of all subsidiary activities for cash management
purposes. The treasury can monitor activities centrally, creating reports
and services for the regions as required. The company ensures it gains
maximum value from the system with this service-based approach to
treasury operations. By increasing visibility for subsidiaries, duplication of
data and unnecessary costs are reduced, allowing the group to make more
informed and better decisions.
The group can now manage their total risk position much more
effectively thanks to this increased visibility. Because Fusion Banking
Treasury Suite is flexible enough to reflect specific company processes
and workflows, the central treasury function can delegate or retain the
rights to conduct specific operations and responsibilities, as required to
meet company policies and business unit capabilities.
The company is fully IFRS compliant and can prove to both auditors and
shareholders that the hedging of its operational cash flows is efficient.
Vendeville added, The groups IFRS postings are automatically produced
and are available through the Fusion Banking Treasury Suite Web. A full
straight-through-processing is now in place ensuring that once a deal is
initiated in the front office, all processes are automated right through to
generation of local and IFRS GAAPS. This allows us to avoid any
redundant captures.
Today, GDF Suez has better control of the payment value chain for the
group. They now have the tools in place to independently manage and
initiate payments with banks and partners at a variety of levels. This allows
the business to achieve a greater degree of accuracy and efficiency in the
way it manages the risks and needs of the organization. In addition, GDF
Suez experienced the following benefits:

Reduced operational risks reduced costs Improved reporting Better
management of capital to ensure the company remains solvent Regulatory
compliance
Conclusion
Working together with Misys, GDF Suez has used the implementation
of Fusion
Banking
Treasury
Suite as
an
opportunity
to
drive
efficiencies and growth. A combination of market-leading technology and

shared best practice has allowed GDF Suez to focus on the areas of its
business that provide a competitive difference ensuring their treasury is
ready to support business and finance requirements in the most effective
means possible.
Elisabeth Vendeville Global Project Manager at GDF Suez
"We needed to put in place a global solution to manage cash positions
resulting from the recording of financial flow, financial transactions and
cash pools; as well as to follow the management of risks hedged by
derivative products. Fusion Banking Treasury Suite was the perfect fit. The
solution also feeds our accounting systems and facilitates group reporting
which eases monthly closures."
"The whole groups reporting will be mapped onto the system with
valuation calculations, IFRS effectiveness tests and postings as well as the
management of remote subsidiaries input, all done through Fusion
Banking Treasury Suite web".
Fin facific treasury system
Source: http://www.finpacific.com/case-studies.html
2.2.4
M-HYPERMART JPMAS POS DESIGNER SOFTWARE
According to JPMA POS Designer Software, the entire display

interface is web based and can easily be modified. You may even want
to add your own Java, Macromedia Flash, PHP, ASP or ActiveX
components! This allows you to create a more dynamic display that
can include movies, sound-FX or speech.
CBI allows for the most adaptable POS interface to date. With little
time your POS can have any interface you want. Your POS display can
change monthly, daily, for the holidays, or whenever you feel like
switching things up.
Anyone with minimal web development skills can create any POS
interface imaginable. Check out some of the screenshots of just some
of the CBI interfaces created.
Our retail experts have worked with some of the worlds largest (and
smallest) retailers from the early stages of POS selection through
implementation and roll out and every step in between. Every retailer,
large and small has unique requirements. Our implementation team
will perform a detailed analysis of your current operations to provide as
seamless a transition as possible while implementing the new system
to meet your future requirements.
Supermarket Retailing
POS Designer is installed in hypermarkets in the Philippines with over
220 lanes in a single store with throughput of over 70,000 customers in
a single day. We understand demanding environments and have a
robust, proven architecture that can handle just about anything in
the demanding grocery retail environment.
All data flow throughout POS Designer in real-time, so you know your
prices at checkout are accurate and sales data at host and in the
stores are current and correct. If something interrupts the flow
server maintenance, network issues, etc. checkout continue to
operate seamlessly until
the
missing
link
is
restored.
Our guaranteed data delivery mechanisms automatically recover and

ensures the data gets where it needs to go.
Secure Electronic Payments
POS Designer is fully integrated with both MTXEPS and Mercury
Payment Systems for electronic payments. This ensures a PCI and
PA-DSS compliant payment platform with support for dozens of

payment devices and several payment processors.
Audit and Profile Based Security
POS Designers auditing system captures every move made on the
system. Detailed tracking information is available about who made
changes, what they changed it to and what they changed it from.
Employee security profiles allow the retailer to define each employee
type and what features are available to them at the front and back end.
Manager intervention can be configured for any front-end feature.
Back office employees will never see options they do not have access
to.
Simplifying the checkout experience
Second only to ensured delivery of data is a simple end user
experience. Graphical tools make customizing the screen by POS
grouping a breeze. Electronic Flip Charts point and shoot void, and
centralized returns make POS Designer one of the simplest and most
intuitive points of sale systems for cashiers to operate.
POS Designers grocery-driven tools streamline daily operations for
managers and file maintenance personnel. Promotions templates and
our wizard-based Batch Maker simplify daunting maintenance tasks.
Graphical cashier balancing tools, safe management and powerful
reports show our retailers exactly where the money is or isnt.
Source: http://www.jpma.com/
http://www.jpma.com/hp-tab-point-of-sale/grocery/
2.2.5
PUREGOLD PRICE CLUB- TPLINUX POS SYSTEM

According to Jun Auza (April 2009), Puregold is one of the
leading retailers here in the Philippines is set to deploy a Linuxbased point-of-sale system (POS) to cut down operating costs. It
has
reportedly
ordered
more
than
2,000
licenses
of TP
Linux software, which will be installed to Puregolds network of

stores.
TP Linux is owned by Wincor Nixdorf, a German corporation that
provides retail and retail banking hardware, software, and services.
TP Linux has the capability to run on other vendors hardware as

well as Wincor Nixdorfs own systems. Puregold is the first Filipino
company that will utilize the German firms open source-based
software.
Puregold is looking to cut overall licensing costs in terms of
security while standardizing on an open-source platform, covering
both
current
and
future
store
openings.
In an interview by Lawrence Casiraya of Inquirer.net, according to

RuelMagat, the company's IT Manager said, We wanted to cut the
cost of buying anti-virus licenses and save on the cost of the
license of (Microsoft) Windows per POS. Christian Charlton,
Wincor Nixdorfs Asia Pacific head of retail solutions, added that
Puregold also intends to use the open source-based software to
boost its customer-related initiatives such as promos and
discounts.
In these tough economic times, I hope more and more companies
here will follow what Puregold has done and will somewhat realize
the true value of open source software.
TPLinux is one of the most flexible Linux-based store solutions
available on the global market. Coupled with its versatility of use,
outstanding integration mechanisms and the experience gained
with over 50,000 TPLinux installations worldwide, TPLinux is ideal
both for modernizing store IT and for migrating and using
established POS hardware platforms.
TPLinux is owned by WincorNixdorf, a German corporation that
provides retail and retail banking hardware, software, and services.
TPLinux has the capability to run on other vendors hardware as
well as Wincor Nixdorfs own systems. Puregold is the first Filipino
company that will utilize the German firms open sourcedbasedsoftware.
Source:
http://www.junauza.com/2009/04/one-of-philippines-
leading-retailers-to.html
http://infotemajorproject.blogspot.com/2009/06/puregoldMerchandising- Treasury Module System
price-club-tplinux-pos-system.html
2.3 Synthesis of Foreign related literature
This chapter tackles about the foreign related studies of
the proponents. It serves as a guide for their studies and to
help the proponents to better understand and aid us in
completing the development of the said project. it represents
as their related studies for treasury process of the system goes
like this, . Smart Treasury offers the look and feel of Excel, but
with the enhanced database and filtering capabilities of a highend treasury workstation. Reduces manual data entry
Improves short and long-term liquidity through automatic
update of treasury worksheets Provides complete auditing and
tracking Assures timely and consistent wire, ACH, and SWIFT
initiation across bank accounts Centralizes cash management,
debt and investment data Minimizes the opportunity for fraud.
The US Treasury the Treasury operates and maintains
systems that are critical to the nation's financial infrastructure,
such as the production of coin and currency, the disbursement
of payments to the American public, revenue collection, and
the borrowing of funds necessary to run the federal
government. The Treasury Develop the systems, structures
and processes required to become a more flexible and capable
organization. Tanzania there is a treasury function in their
organigram that is separated between front and back office.
They have well established treasury function in their banks.
Treasury Services structurally improves the bottom line of its
clients by cutting their costs and by improving their efficiency in
finance. We create a competitive advantage for our clients by
implementing financial excellence. After the proponents
studied all the features of their related studies they decided to
implement a system that can lead the treasury to innovation.
So the proponents got all the features of the related
studies and hopefully it will be added to their implementing
system.
Matrix Diagram
System Description and Features
Automatically Update the treasury
R e l a t e d
L i t e r a t u r e s
Chesapeakes Smart Treasury Us Treasury The Treasury Tanzania Treasury Services NSW Government AvantGard Treasury Finpacif c treasury system M-HYPERMART PUREGOLD Proposed module
Pc Based System
Treasury report
Implementing Financial Excellence
It can run in operating system
Speed Process
operates and maintains systems that are crit cal to the nation's
financial infrastructure
Develop the systems, structures and proces es to become a
more flexible and capable

Could manage al busines workflows, risk and debt
Applicable in android mobile application
Can monitor activit es central y, creating reports and services for

the regions as required
Facility for mobile apps
Treasury report
Database: Ms sql
Immediate update treasury
Table No. 14: Matrix Diagram of Studies and the proposed module
Synthesis of Local Literature

After the proponents conducted an interview some of the companies are
have speeded their process except one. according to RuelMagat, the
company's IT Manager said, We wanted to cut the cost of buying anti-virus
licenses and save on the cost of the license of (Microsoft) Windows. Christian
Charlton, Wincor Nixdorfs Asia Pacific head of retail solutions, added that
Puregold also intends to use the open source-based software to boost its
customer-related initiatives such as promos and discounts. The finpacific
treasury system The main priority for GDF Suez was to ensure they had
sufficiently robust financial systems and processes in place to support
communication and growth, whilst both minimizing costs and maintaining
shareholder and regulatory confidence. The M-Hypermarket the entire display
interface is web based and can easily be modified. You may even want to add
your own Java, Macromedia Flash, PHP, ASP or ActiveX components! This
allows you to create a more dynamic display that can include movies, soundFX or speech. The NSW Government NSW Treasury issues a variety of
financial reports on behalf of the Government outlining the status of State
finances. These are required by the Public Finance and Audit Act 1983. Proper
reports on the management of the State's finances ensure the accountability of
Government to its constituent. After all features and process are explained.
The proponents have an idea that can added to their system and it can lead to
innovation.
CHAPTER 3 - EIS PROJECT MANAGEMENT AND DEVELOPMENT

3.1 RISK MITIGATION, MONITORING AND MANAGEMENT PLAN
3.1.1INTRODUCTION
This section gives the general overview of the Risk Mitigation,
Monitoring Management Plan for the Treasury Management System.
RMMM contains all the possible risks that may encounter to the
development of the system. RMMM also contains the possible solutions to
the difficulties might be a possible risk in the development of the system..
3.1.1.1 Scope and intent of RMMM activities
The proponents want the software to be free of any defects or errors, to
be safe. So the proponents would like to have a risk management plan to
counter any difficulties that may impact the development or the creation of
the software .The goal of the proponents is to assist the project team in
developing a strategy to deal with any risk. For this the proponents will
take a look at thepossible risks, how to monitor them and how to manage
the risk.
For software development to avoid any risk both the developer and
client have to work together. Client has to spent time with the developer in
the beginning phase of the software development. If client decides to
change the software, meaning if client wants to add some more functions
into the software or to change the requirement, this will have major effect
on the development of the software.
3.1.1.2 Risk Management organizational role.

The proponents have their responsibilities to manage all the possible risk
that may encounter while doing third proposed project.
System development can avoid having risk by double-checking the
record of money, estimates regarding costs of the development etc.

The manager helps the proponents got valuable details about the
system.
System development team can avoid risk by getting all the details of
the equipment that are provided or are accessible to them.

The proponents client can avoid risk by making all necessary
business changes before initiating request for the software.
Project manager
The Project Manager is the leader of the group then, the Project Manager
shall decide how to manage all the possible
risks of the proposed module.
Business Analyst
The Business Analyst is responsible to analyze the problem regarding to
the business process in system.
System Analyst
The System Analyst will managesthe risks that may encounter during or
after of the proposed project they will analyze all the possible risk to make
a good decision.
Lead Programmer
The Lead Programmer manages the risks in doing the system he thinks
very well to avoid any risk by doing a user friendly system..
The Documents Specialists will document all the things related in the
proposed module. They will analyze all the risks to have a solution to all
the upcoming risk.
3.1.2 Risk Description

This section describes the risks that are likely to be encountered during this
project. The proponents identify the risks that are present in the said project.
This requires an open mind set that focuses on future scenarios that may
occur. Implementing a risk response is the activity that actually adds value to
the project. It prevents a threat occurring or minimize negative effects. The
other risks have helped to map, prioritize and understand risks. This will help
you to make a sound risk response plan that focuses on the big wins.
Avoiding risks means you organize your project in such a way that you
don't encounter a risk anymore. This could mean changing supplier or
adopting a different technology or, if you deal with a fatal risk,
terminating a project. Spending more money on a project. Identify
possible risks.
Reduce or allocate risks.
Provide a rational basis for better decision making in regards to all risks.
Plan.
3.1.2.1 Risk Table

The following table describes the risks associated with the project. The
appropriate categories of the risks are also given, as well as probability of each
risk and its impact on the development process.
Risk factor
Probability
I m p a c t Risk management action
Expenses of the project

Availability of time
H
H
H
H
Keep the money to continuously the project.

Arrive early before the meeting started.
L
H
Set the meeting before on the date you set. so the team members can prepare that day.
Make sure that the team members must know to operate the system.
Availability of team members H

System error/lost H
Table No. 15: Risks Table
3.1.2.1.1
DESCRIPTION OF RISKS
Business Impact Risk
This concern about not being able to come up or produce the
product that has an impact on clients business. If the software

does not achieve its goals, then it will be basically lead to failure.
Development Risk
This risk is dependent on the project itself, if there are any possible
errors on the development that cant be debugged easily.
Employee Risk
This risk is totally dependent on the ability, experience and
willingness of the software development team members to create
the working product. If the team members are not putting all their
efforts to finish the project, then it will lead to a project failure.
Employee risk is one of the major risk to consider while designing
the software.
Process Risk
This risk involves the quality. If the proposed module developed did
not meet the standards set by the end user or the development
team, then it is a failure. This is because of the end users failure to
describe the true business need or the failure of the development
team in understanding the project.
Technology Risks
This risk involves in using technology. This includes the hardware and
software failure, malwares, viruses, spam or scam and also human error.
3.1.2.1.2
PROBABILITY AND IMPACT FOR RISKS
3.1.2.1.2
PROBABILITY AND IMPACT FOR
RISKS
The following is the sorted version of the above table by
probability and impact:
C a t e g o r y R i s k s Probability I m p a c t
Employee Risks Lack of training and experience 1
5
%
2
Process Risks Low Product Quality 1
5
%
2
Development Risks Insufficient
1
5
%
2
Technology Risk Obsolete technology 1
5
%
2
Business Impact Product may harm the business 1
4
%
3
Table No. 12: Risks Table (sorted)
Impact Values
Description
Catastrophic
Critical
Marginal
Negligible
Above is the table that categorizes the risks involved in

software development. It gives brief description of the risk
in Risks column and also provides the probability of risk
occurring in percentages in Probability column and also
the impact of the risk in the Impact column.
The impact values assigned to the each risk are
described in the section below the risk table. It is very
convenient way to look at the risk and derive the
information of the risk.
3.1.3 Risk Mitigation, Monitoring and Management

This section in detail describes Risk Mitigation, Monitoring and
Management for each of the possible risks. It will talk about ways
to avoid, monitor and to have ways to manage the risks. Risks can
be foreseeable and unforeseeable. In both cases, project manager
prepare with some means of dealing with them. Many risk
management plans address only foreseeable risks and fail to
address the unforeseeable ones. For that reason, project planning

must include a degree of schedule, cost, and scope margin. The
challenge facing risk management teams knows where to begin
the process of risk identification. Typical risk sources that should
be examined are poorly defined product requirements, design drift,
exceeding
technical
capabilities,
accepting
an
unproven
technology , making too many changes to an existing product,

limited availability of needed skills, project deadlines and
budget/funding limits.
3.1.3.1 Risk Mitigation for Risk Management
In this section several different software development risks will be
identify, a plan will be created ti avoid these risks. The proponents will
think of the risks and of the way to keep the software development process
from encountering these risks. It is important to have mitigation plan ti
avoid risks once and for all. Goal is to attack the risks even before it comes
into existence. The plan will help in identifying the possible risks and to
monitor them. Risk is always to be analyzed by the probability of the event
occurring and the consequence if it does occur, and should focus on the
project schedule, costs, scope and quality.
3.1.3.1.Business Impact
In the risk category we are concerned about the quality of
the final product. As mitigation step the proponents will spend
more time with the users to understand their needs. This way
proponents can gather all the information necessary for the
project to be successful. The proponents will try to understand
Business environment and can try to provide the user with help
in defining software requirements. More the time team spends
with the user better the understanding team will have regarding
the software.The proponents has to make sure that the system
integration is justified, meaning that it really improves
inspection process.
3.1.3.1.2
Process Risk
The proponents want quality of the product to be as high
as possible to achieve. The proponents will set up guidelines to
be followed for each of the team members during all the
phases of the software development cycle. The standard will
be set and defined for all of the software development. This will
help the team in delivering the high quality product thus
increasing our reputation in the future . For example,
viewingreport, updated status, If usercan not get used to the
forms in the PC they may go back to using pen and paper
which is not good for the reputation of the team.
3.1.3.1.3
Technology Risks
To avoid risk of using technology that may become
obsolete in few years after the product have been
developed. The proponents will do excessive research on
what technology to use for software development and will
see the latest technology (programming languages etc.) to
void this risk. The proponents used Java as their software
and MSSqlyog as their database for monitoring all the
records and transactions.
3.1.3.1.4
Development Risks
If the necessary tools are not provided to all of the team
members, their work will lack quantity and quality, as
mitigation phase the proponents will make sure that the
budget includes cost for latest technology and tools
needed to achieve the desired product. For example if the
merchandising refused to do some important tools needed
inintegration part will be useless.
3.1.3.1.5
Employee Risks (Team member)

This risks concerns the knowledge and of the
employees and their willingness to help make the project
succeed. As mitigation step of this risks the proponents will

make sure that someone in all of the project development

phases knows exactly what to do and the tools to use to
achieve the goals. If the employees that have little
knowledge in the main software implementation language
fails to learn it, may cause big problems when coding part
begins.
3.1.3.2 Risk Monitoring for RiskManagement
In this section the proponents will identify the conditions to
monitor to determine whether risk m is becoming more or less
likely.
3.1.3.2.1
Business Impact
As monitoring step in this risk The Proponents will
setup user meetings to show them the work has been
completed and to get user input on the work. The group
members will have meetings every other week to present
the work that has been done from the time of the last
meeting. This will help team in saying in touch with the
customers and will also be every efficient way to derive
customers input on the progress made. It will also be a
way to get customer insight on the project, which will help
you to determine the changes that group may have to
make to the software upon customer request.
3.1.3.2.3
User Risks
To monitor this risks the proponents will monitor the
successes of the meeting by keeping track of people that
have attended meeting. If the outcome of the meeting is
low we can contact responsible person to help the
proponents overcome this problem. The proponents will
also have the login charts to show the customer who is
attending the meetings and who needs to be reminded to
start attending meetings.

3.1.3.2.4
Process Risks
To monitor the risks here the Proponents will review
each others work to find the problems and to help each
other in achieving better product quality. The proponents
have the general guidelines set for all the work to be
carried on for the software development. Software
development team will constantly check each others work;
will compare it with the set guidelines, and will inform a
team member who is failing to participate in following the
guidelines.
3.1.3.2.5
Technology risks
For monitoring phase during the development of the
software the proponents will keep eye on tools being used
and their effectiveness. This will help the team members to
keep up with new technology .Java NetBeans and MSSql.
Observing the tools and equipments used for developing
the system must be done for the effectiveness of its use in
developing the proposed module.
Hardware Computers used for developing the system
must at least meet high quality of specifications
- Must able to support the software being used to develop
the proposed module.
Software Software must not be obsolete and must be in
the latest trend of softwares.
- Front end and Back end used must not be obsolete.
3.1.3.2.6
Development risk
software The Proponents will keep eye on tools being used
and their effectiveness. This will help the team members to
keep up with new technology. Theteam members will also
look for the availability of the inexpensive equipment that
may provide help in completion of the said project.

3.1.3.2.7
Employee Risks (teammates)

Monitoring and managing of this risks will include
looking out for each other, that is if some team member is
having difficulties in performing some tasks or using
particular tool or technique other members of that team will
help in completion of the said project.
3.1.3.3
Risk Management for risks m

In this section the proponents will identify several
different software development risks and will try to create a
plan to manage those risks if they do occur.
3.1.3.3.1
BUSINESS IMPACT
If a mistake has been made, user input on the
completed work will provide us with information to fix or
improve the software. Te proponents have done very many
meeting with the end users and plan to do meeting every
two weeks; this should clear any misunderstanding
between the software development team and customers.
This is the best way to go at since the work that is done on
the project is revealed during the meetings and customer
gets chance to make adjustments necessary.
3.1.3.3.2
PROCESS RISKS
If the problem exists with the quality of the work, the
quality assurance plan will be revised in risk management
phase. Other team member will attempt to take over or
swap the work of the member whose work does not meet
the quality standards.

3.1.3.3.3
TECHNOLOGY RISKS
software we will keep eye on new technology. If they spot
new techniques that can be implement without major
changes in our project they will include such techniques in
the development of the project. Team members will also
keep a look out for major shifts in the technology and how
it affects the software that we are working on. If there is a
need change in the technology will be discussed among
team members and will be presented to the users. If users
agrees necessary changes will be made with the existing
technology.
3.1.3.3.4
DEVELOPMENT RISKS
In the management phase if the funding for the
technology and tools are not enough we will have to
reschedule the phase of software development cycle to
allow more time to coding phase .
3.1.3.3.5
EMPLOYEE RISKS (TEAM MATES)

Monitoring and managing of this risk will include
looking out for each other, that is if some teammember is having difficulties in performing some task
or using particular tool or technique other members of
that team will help him out. This is where team
members may have to spend little time with each
learning or teaching what others know. If team member
lack ability to use certain programming language or
application, others team members will take some time
off to teach the team members basics related to that
application.
`3.1.4 Special Conditions

Special conditions that are associated with the software
are as follows.
1. Login
Since the proponents are using modular login .they need to
make sure that the person logged in will only have access
to certain part of the application, this depends on the rights
granted to the users. The proponents also need to make
sure that users with read only write understand why they
are unable to make changes to other users reports.
2. Use of proprietary software
Proponents must use legitimate softwares in
doing
the
proposed syste
3.2 SOFTWARE CONFIGURATION MANAGEMENT PLAN
3.2.1
INTRODUCTION
During the time of the software development the
proponents will have changes to the original plans. Software
Configuration Plan is developed so that the proponents can identify
the change, control the change, make sure the plan is
implemented correctly and to make sure that the proponents report
the change to others. Software configuration management plan
can determine what was changed and who changed it. If a
configuration is working well, SCM can determine how to replicate
it across many hosts. So the teamwork will facilitate team
interactions related to the process. Process management ensuring
adherence to the organizations development process. This
chapter helped defines software configuration management in
simple terms as the mechanism used to control the evolution of a
software project. The proponents specifically discuss software
development and how they are enabled by a good SCM system.
During the time of the software development the proponents will
have changes to the original plans. Software Configuration Plan is
developed so that the proponents can identify the change, control
the change, make sure the plan is implemented correctly and to
make sure that the proponents report the change to others.
Software configuration management plan can determine what was

changed and who changed it. If a configuration is working well,

SCM can determine how to replicate it across many hosts. So the
teamwork will facilitate team interactions related to the process.
Process management ensuring adherence to the organizations
development process.
3.2.1.1
SCOPE AND INTENT OF SCM ACTIVITIES

The main purpose of SCM is to make report and
track any changes made to the original software
development plan. It is applied throughout the
software development process and will help the
proponents to keep track of changes and also help
the proponents go through and make changes.
SCM procedures will give us a good map out of
the software so that if they are needed to make
more changes it will be relatively easy to do so.
SCM will maximize productivity by minimizing
mistakes. For SCM to be successful, all the
members of software production team will have to
take time to report the changes that they think are
necessary and/or to notify others of changes that
they may have made. This is sort of boring and
time-consuming work, but it is very important.
SCM activities are developed to
Identify change
Control change
Ensure that change is being properly implemented
Also have a way to document the change.
3.2.1.2 SCM ORGANIZATION ROLE

Since the proponents have rather small software
development
team,
each
member
of
the
proponents will accept responsibility for software

configuration management. This is necessary
since there are only three members in the team. If
one of the member reports changes remaining two
members have to take up a job of authorizing
change and to ensure that change is properly
implemented.
confusion
This
will
reduce
or
eliminate
between
the
proponents
regarding
changes with the software. Since all the members

participate in the SCM, they need to interact
change with other software engineering teams is
eliminated.
They will keep all the proponents on the
clients side informed of all the changes for
acceptance. The changes that do not really
affect users knowledge of the software will
be presented to a selected member on the
client side. These changes will be noted in
a specific section so that they can refer
back to them to know what the original plan
was and why the changes they made. If
the changes are made or suggested so
that they will affect the way user uses the
software, then those changes will be
discussed with entire team. Once a client
has decided to go with the change then
and
only
then
will
changes
be
implemented. They will also extensively

report or document all the changes so that
client will have access to it after the
software is packed and delivered.
Control Board-composed of technical and

administrative representatives
who recommend approval/disapproval of
changes
to
CI
or
baseline
(e.g.,
Configuration Control Board (CCB), Internal
Review Board (IRB)).

Configuration Manager-a
manager
is
configuration
responsible
for
the
Configuration Management process and

the Configuration Management Database
(CMDB). He or she has create, read,
update
and
configuration
delete
permissions
items
in
the
CMDB.
all
A
configuration manager is also a super user

for
all
accounts
in
multi-customer
environment.
Configuration Management Officer (CMO)Implements and maintains the CM system
according
to
the
projects
CM
Plan.
Coordinates, supports and performs CM

activities and reports those activities to the
PDL.
Configuration
Auditor-the
configuration
auditor can view, modify or cancel audit
schedules and clean up old audit output.

Person in a Role-a role is a user who has
been assigned to a role. The assignment of
a user to a role is done by modifying the Id
file in LDAP.
3.2.2 SCM TASKS

In this section the proponents will try to detail all-important SCM
tasks and will assign responsibilities for each. All of the SCM tasks will
be performed by three members of the software development team
members. The proponents will try to keep one-person from the clients
team informed of all the changes that do not affect user. All the
changes that affect the use of the software will be discussed with entire
team on the clients team during the meetings.
The tasks of the software(NETBEANS) that will be used of the
proponents is to Create database connection to make it easily save the
password, Import Schema from One DB to Another to get a big
schema to test with. Import Data from another database. Create and
Insert Test Data.
3.2.2.1 IDENTIFICATION
In this section the proponents will describe the way software
configuration items will be identified for the software configuration
management plan.
3.2.2.1.1 DESCRIPTION
Identify Change
If during the software development phase a team member suggests
a change in the software then we need to have the team work on
the suggestion and to figure out if the change is necessary and is
justified.
Approve Change
The proponents want to be able to have control over any change
within the software. The proponents can not afford to have one
member of software development team think of a change or and
implement it without telling any other member of the team. This can
create huge technical problems for the software. The proponents want
to develop rules so that no member of the team will think of and
implement change without permission of other members. The
proponents will be using the change request report form to suggest
changes in the software.
Ensure that change is being properly implemented.

The proponents want to have team members looking over the
change. Since all the proponents will be working separately, it is
possible ton have made mistake in implementing the change .to make
sure this doesnt happen, they want to set up times when team
members will look over the change that other proponents have
implemented and to finalized the change.
Document the change

Since change has to be documented from the time that a team
member suggests change to the time change is finalized, they
will end up extensive documents. They will be using the change
request form developed by Delta group to request change. To
approve a change they will be using change report form, which
will be submitted to change control panel (remaining member of
the software development team).
3.2.2.1.2 WORKS PRODUCTS AND DOCUMENTATION
Identify change
Once the change is identified a change request form will be produced
and will be send to all the members of the SCM team.
Control Change
After evaluator (SCM team member) got the change request form,
change report, report form will be generated.
Ensure the change is being properly Implemented
Document the change

Once the change is approved they will document the change in the
library. And they will change the software version number if it is
necessary.
3.2.2.2 CONFIGURATION CONTROL

3.2.2.2.1
Description
Describes the procedures and tools to be used in controlling the

changes
Bug Fix
3.2.2.3Version Control
3.2.2.3.1
DESCRIPTION
As a result of changes, the version number of various modules will be
increased accordingly. We will be using a universal version number
system for all modules. The proponents will also have a final version of
the entire product.
Here are the steps to be done if there is a request for change:
Request the change

A meeting will be held with all team participating.
Discussion of the requested change.
Approval of the requested change.
If approved, list the change to be implemented and check
if it still conform the standards.
3.2.2.3.2Increasing Version Number

When a change request is filed, a change report will be
created. After the change is finalized, it will be documented. The
proponents will be using a decimal point version number system:
<major update>.<minor update><bug fix>
Bug Fix
For the system, Bug fix numbers are to be incremented if the bug to be
fixed is visible. The more visible bug fixes have been made, the closer the
bug fix number will need to be incremented.
Minor update
If functionality is added to the product/module will increase the userfriendliness / performance but does not change the way a function / interface
work. The minor update number may be increased. Several of these changes
will warrant a version number change. Again, visible changes (interface) will
cause the version number to increase sooner.
Major update
The proponents do not foresee any change in major version number. The
product will be labelled as version 2.
3.2.2.3.3 WORKS PRODUCTS AND DOCUMENTATION
A single document titled Version Revision History will be used
to document all the version revisions. The bug report and tracking
system will also be used to monitor and document all the bug fixes
and enhancement request.
3.2.2.4 Configuration status accounting (CSA)
The proponents will be using different ways to communicate with
the team members and to inform others that changes may concern.
3.2.2.4.1
Description
Two ways or the three tools that the proponents will be
using to communicate with other members or the people

associated with software development.
Change request report:

The proponents will have two different forms that they will use as
tools to request a change or to report a change to the SCM team.
Verbal communication:
Since their software development team is small and all the team
members are in constant touch with each other it would be better to
communicate verbally.
Social Networking Site

This tool is commonly used to communicate online. The client may
announce the changes or enhancements. Also, the developers can
communicate with each other by this.
3.2.2.4.2
Work products and documentation
Change request report generator
3.2.3
E-mails and chats

Test errors will be documented electronically.
Notes of clients suggestions
All suggestion made during peer review will be noted.
Documentation of test
SOFTWARE QUALITY ASSURANCE OVERVIEW

For the description of the methods for software quality assurance
please refer to Software Quality Assurance Plan (SQA)
SQA will focus on the management issues and the process specific
activities that enable a software organization to ensure that it does "the
right things at the right time in the right way." SQA plan provides a road
map for instituting software quality assurance.
Scope and Intent of SQA Activities
The objectives of SQA are:
A quality management approach

To define the approach that will be used in quality management
Effective software engineering technology (methods and tools)
To describe the methods and tools or the software engineering
technology for the development and testing of the software
Formal technical reviews that are applied throughout the software
process
To know all the personnel that needs to be involved.
Control of software documentation and the changes made to it
Create a procedure to assure compliance with software development
standards when applicable

A procedure to assure compliance with software developments when
applicable
Measurement and reporting mechanisms
Reviews and Audits

A formal technical review (FTR) is a software quality assurance activity that is
performed by software engineers . The objectives of the FTR are:
1.
To uncover errors in function, logic, or implementation for any
representation of the software;

2. To verify that the software under review meets ita requirements;
3. To ensure that the software has been represented according to
predefined standards;
4. To achieve software that is developed in a uniform manner;
To make projects more manageable.
3.2.3.1 GENERIC REVIEW GUIDELINES
The following are the requirements delineated by them. And the
proponents try to follow them as their quality assurance plan.
-Management responsibility
-Quality System
-Contract Review
-Design Control
-Document and Data Control
-Product identification and trace ability.
-Process control
-Inspection and Testing
-Control of Inspection, Measuring, and Test Equipment
-Inspection and Test Status
-Control of non-conforming product
-Corrective and Preventive Action
-Handling, Storage, Packaging, Preservation, and delivery.
-Control of Quality Audits
- Training
- Servicing
- Statistical Techniques
Conduction a Review
There are two kinds of reviews that the proponents will do. Review
cases with the client, and review cases with other teammates.
For the changes that will affect the clients' performance when they
use the software, they have to consult them first. But before take the
cases to the client, the entire team member has to agree with the
change. And keep a good record of the project before and after
changes.
Roles and Responsibilities

As stated in 1.2, SQA Organizational Role, the rule of each team
member will be very confusing since they have a relatively small team.
Project Manager: Francia. Angelica

Business Analyst: Globiogo. Jean rose
System Analyst: Eria. Mega
Documents Specialist: Alcon. Merla
Lead Programmer: Alburo. Marichu
Review Work Product

For each period (weekly, in our case), they'll
generate a work report from each proponent. In the
work report, they will state each member's work for the
past week, problems that encounter, problem that can
be solved, any cautions to remind. This report will be
extremely helpful when comes to documentation and
writing the help menu.
When they meet with their client, they will have a
minute for the record. In the minute, they will have the
questions that they make before they go see the client,
answered got from the clients' request, opinions on the
current work self reminder, schedule for next meeting,
etc.
3.2.3.2 Formal Technical Reviews

Here are the FTR that they will conduct during the software process:
- walkthroughs
-Inspections
After each form (interface) they design, they'll do a test on the interface
using block box testing method. And for each week, when the team set
down come to a meeting, they will ask the team mates to do a inspection
on the interface, then hook up the other's work, do a walkthroughs of all
the interfaces.
Description of review Walkthroughs
This review mainly focus on the integrations of the parts that they design
(such as interfaces, form, database.) They will ask other team members to
do the walkthroughs with the presence of coder.
Description of Review Inspection

This review is mainly focus on the correctness of the parts that they
designed. Usually allow the other two team members to do a private test,
without the designer's interrupt. This idea is try to allow team members
bring out the test cases.
3.2.3.2.1
System Specification Review
System specification usually changed after each weekly

meeting, and after each meeting with their client. As for this
moment, most of the system have been settle down. And since we
are actually doing a "bug fixing" originally, so the system
specifications is pretty much there. Even they have expended the
project into a higher level, the basic mapping of the project is still
the same. For more information, please see the document titled
"System Specification".
3.2.3.2.2
Software Project Plan Review

The purpose of Software Project Plan is over look of the
whole project.
3.2.3.2.3
RMMM Review
RMMM, Risk Mitigation, Monitoring & Management, is use
to prevent, monitor, and manage the risk. For more
information , please see the document titled "RMMM".

3.2.3.2.4
Requirements Review (Models, Specification)

Software Requirements stated the data requirement,
specifications. For more information, please see the document

titled "Requirement Plan".
3.2.3.2.5
Data design Review

The Date Design document is about the data flow between
each form (interface), and forms to the database.
3.2.3.2.6
Architectural Design Review

The Architectural Design document is about the whole
project design, layout, and da

3.2.3.2.7
Interface (GUI)
Interface is the design of the proposed
3.2.3.2.8
Component Design Review
Beside of the Interface, components of the front end and

back end will be checked to make it more efficient and suit to
project needed.
3.2.3.2.9
Code Review
Reviewing of codes is done to check the errors and
prompt a solution to it.
3.2.3.2.10 Test Specification Review

Testing of systems specs will be done for compatibility
issues with other hardware that the system will be
installed.
3.2.3.2.11 Change Control Reviews and Audits

It is done to manage and control reviews and audits
properly.
3.2.3.3 SQA AUDITS
The proponents will have a weekly on their individual

performance for the past week. Any problems questions
regardless on the performance of other proponents will also
noted there.
Proponents will write part of the help menu that related to their
design parts. And they also share between members.

Any changes that will affect the project will consult with other
proponents before doing any changes. These are the change
that is minor or require little code change, but still different from
the original architectural design.
3.2.3.4 Problems Reporting and Corrective Action/ Follow up

This section will describe problem reporting mechanisms that
occur as a consequence of the FTRs that are conducted and the
means for corrective action and follow-up.
3.2.3.4.1
Reporting Mechanisms
In reporting mechanisms, the system will
give the reports of money that taken in and
paid out on business to the integrating
system.
3.2.3.4.2
RESPONSIBILITIES
Each proponents of the team will be

responsible for something . But they
are helping each other out. Since they
use the ego-less model, so they dont
select a team leader. But since Marichu
is the one who assign in software
development and has an experience
on the project, so shes the lead
programmer for the team. But as far as
decision making, no changes will be
make unless all five members agree on
it.
Below are listed the proponents name

corresponds with the position
o
o
o
o
o

Business Analyst: Globigo. JeanRose
3.2.3.4.3DATA COLLECTION AND VALUATION

To properly conduct software quality
assurance,
data
about
the
software
engineering process should be collected,

evaluated, and disseminated. Statistical
SQA helps to improve the quality of the
project and the software process itself.
During each meeting. They will present
a prototype of the project; Even during the
two weeks that between two meetings, if
they try to keep the client have the latest
and 1st hand knowledge on the process of
the project, so letting them exam the
process.
3.3
SOFTWARE ASSURANCE PLAN
3.3.1INTRODUCTION
This section gives a general overview of the
Software Quality Assurance Plan (SQA) for the Treasury Module
System.SQA will focus on the management issues and the process
specific activities that enable a software organization to ensure that it does
the right things at the right time in the right way.
3.3.1.1 SCOPE AND INTENT OF SQA ACTIVITIES
These objectives of SQA are:
A quality management approach

Effective software engineering technology
Formal technical reviews that are applied
throughout the process

A multi testing strategy is draw
Control of software documentation and the
changes made to it
A procedure to assure compliance with software
development standards when applicable

Measurement and reporting mechanisms
3.3.1.2 SQA ORGANIZATION ROLE
These are the lists of the proponents name

corresponds with the position
Business Analyst: Globiogo. Jean rose
Lead Programmer: Alburo.Marichu
3.3.2SQA TASKS
Here are the tasks they have for the
SQA
These are the following task that we have for
Software Quality Assurance:
-Voting system when it comes to decision
making about the system.
-Have a good communication and relationship
in the client.
-Create a system with an extensive and
detailed design.
-Researching about the process of the Vendor
Consignment and Contract by interviewing
different company.
3.3.2.1 TASKS OVERVIEW
Tasks that described above will cover the
product quality control, Saving Design Time&
Cost, Minimize Errors, Problem Tracking &
Data Flow.
3.3.2.2 STANDARD
PRODUCES
AND
CONVENTIONS(SPC)
Voting system
The proponents decided that they will
use the majority decision when it
comes
in
doing
this
project
implementation.
Have
good
communication
and
relationship in the client.

Create a system with an extensive and
detailed design.
3.3.2.3 SQA RESOURCES

Modules- The proponents search sample
modules related to the system to get some
idea or resources and for their guide in doing
this project.
Adviser- the proponents always consult
their project to their adviser to ask guidance so
that they will get some idea or helpful tips in
doing this project.
3.3.3
REVIEWS AND AUDITS

A formal technical review (FTR) is a
software quality assurance activity that is

performed by software engineers.
The objectives of the FTR are:
To uncover errors in functions, logic, or implementation for
any representation of the software;

To verify that the software under review meets its
requirements;
To ensure that the software has been represented
according to predefined standards;

To achieve software that is developed in uniform manners;
To make project more manageable.
3.3.3.1 GENERIC REVIEW GUIDELINES

3.3.3.1.3
Conducting a review
There are two kinds of review well do, review cases with
the client, and review cases with the teammates.

For the changes that will affect the client performance when
they use the software, we have to consult them first. But before
taking the cases to the client, the entire team members has to
agree with the change. And keep a good record of the project
before and after changes.

3.3.3.1.2
Roles and Responsibilities

These are the lists of the proponents
name corresponds with the position
3.3.3.1.3
Business Analyst: Globiogo. Jean Rose
Review Work Product

For each period (weekly, in our case), well generate o work
report from each member. In the work report, we will states each
member's work for the past week, problems encounter, problems
that can't be solved, and any cautions. This report will be extremely
helpful when comes to documentations and writing the help menu.
When we meet with our client, we will have minutes for the
record. In the minutes, we will have the questions that we make
before we go see the client, answer got from the clients, clients
request, opinions on the current work, self reminder, schedule for
next meeting, etc.
3.3.3.1.3
FORMAL TECHNICAL REVIEWS

Here are the FTR that we will conduct during the software
process:
- Walkthroughs
- Inspections
After each form (interfaces) they design, they'll do a test on
the interface using block box testing method. And each week,
we will ask the team to do a inspection on the interfaces, then
hook up the other's work, do a walkthroughs of all the
interfaces.
3.3.3.1.5
Software Project Plan Review

The purpose of Software Project Plan is
over look of the whole project

3.3.4
RMMM Review
RMMM, Risk 3.2.1 Description of review Walkthroughs
3.3.4.1 Description and Focus Review
This review mainly focuses on the integration of
the parts that they design (such as interfaces, form,
database) they will ask other team members to do the
walkthroughs with the presence of the coder.
3.3.4.2 Description of Review Inspection
3.3.4.3 Description and Focus of Review
The review mainly focuses on the
correctness of the part that we designed. Usually allow
the other two team-members to do a private test,
without the designer's interruption. The idea is try to
allow the team-members bring out the test cases.
3.3.4.4 System Specification Review
The system specification is usually
changed after each weekly meeting, and after each
meeting with our client. As of this moment, most of the
system
design have stabilized. And since we are
actually doing a "bug fixing originally, so the system

specification is pretty much there. Even though we
have extended the project into a higher level, the basic
mapping of the project is still the same. For more
information, please see the document titled "Software
Project Plan".
Mitigation,
Monitoring
&
Management, is use to prevent, monitor, and

manage the risk. For more information, please see
the document titled "RMMM".
3.3.5.1 Requirements Reviews (Models, Specification)
Software Requirements stated the data
requirements, specifications.
3.3.5.2 Data Design Review
The Data Design Document is about the
data flow between each form(interface), and forms to the
database. For Architectural Design, please see the
document titled "Architectural Design".
3.3.6
Architectural Design Review

The Architectural Design document is
about the whole project design, layout, and data flow. For
Architectural Design please see the document titled
"Architectural Design".
3.3.6.1 SQA AUDITS
Team members will have a weekly report on the
individual performance for the past week. Any problems,
question regardless on the performance of other team
members will also noted there.
Members will write part of the help menu that relates to their
design work. And they also share between members.

Any changes that will affect the project will be presented to
other team members before doing any changes. These are
the changes that are minor or require little code changes,
but still different from the original architectural design.

-The client should be notified of all changes made to the.
For minor changes, we will just notify a reprehensive from
the client instead of the whole team from the client. This
rules only applies to the minor changes or cosmetics
changes, or minor functional change will still require the
agreement from the whole team from the client side (two
inspectors and one division manager).
A change that will affect the project will be presented to
other team members before doing any changes. These are

the changes that are minor or require little code changes.
Any major functional change will still require the agreement
from the whole team from the client side (two inspector and
one division manager).
A changed version will also been carefully recorded. That
included the copy of the project before and after the

changes. And noted on the document that what kind of
change will be make on where and by who. A version
system always helpful.
3.3.7
Problem Reporting and Corrective Action/Follow-up

This section will describe problem reporting mechanisms that
occur as a consequence of the FTRs that conducted and the

means for corrective action and follow- up.
Reporting Mechanisms
The proponents can be contacted by the system
administrator through the use of emails and cellular
phones in case that there will be a problem in the system.
3.3.8
Responsibilities
These are the lists of the proponents name corresponds
with the position
Lead Programmer: AlburoMarichu
Collection and Valuation

To properly conduct software quality assurance, data about the
software engineering process should be collected, evaluated, and
disseminated. Statistical SQA helps to improve the quality of the project
and software process itself.
During each meeting, we will present a client a prototype of the project;
ask the client's opinion on the design, present different option for them to
choice in many cases. Even during the two weeks that between two
meetings, if they try to keep the client have the latest and 1st hand
knowledge on the process of the project, we occasionally posted online, so
letting them exam the process.
Statistical SQA
Statistical quality assurance reflects a growing trend throughout industry to
become more quantitative about quality. For software, statistical quality
assurance implies the following steps:
- Information about software defects is collected and categorized.
- An attempt is made to trace each defects to its underlying, cause (e.g.,
nonconformance to specification, design error, violation of standards, poor
communication with customer).
- Using the Pareto principle (80% of the defects can be traced to 20% of all
possible causes), isolate the 20% (the "vital few").
- Once the vital few causes have been identified, move to correct the
problems that have caused the defects.
Although hundreds of different errors can be uncovered, even for a "small
scale" project like this, all can be tracked to one (or more) of the following
causes:
- Incomplete or erroneous specification (IES)
- Misinterpretation of customer communication (MCC)
- Intentional deviation from specification (IDS)

- Violation of programming standards (VPS)
- Error in date representation (EDR)
- Inconsistent module interface (IMI)
- Inaccurate or incomplete documentation (IID)
- Error in programming language translation of design (PLT)
- Ambiguous or inconsistent human-computer interface (HCI)
- Miscellaneous (MIS)
SOFTWARE PROCESS IMPROVEMENT ACTIVITIES

Determinants
for
Software
Quality
and
Organizational
Effectiveness
Product
Business
Conditions
Customer
Characteristics
Process
People
Development
Environment
Technology
4.0 Goal and Object of SPI

Here are some of the goals of SPI
1. All errors are defects are categorized by origin (e.g. flaw in specification,
flaw in logic, nonconformance to standards).
2. Te cost to correct each errors and defects is recorded.
3. The number of errors are defects in each category are counted and ordered
in descending order.
4. The overall cost of errors and defects in each category is computed.
5. Resultant date are analyzed to uncover the categories that result in highest
cost to the organization.
6. Plan are developed to modify the process with the intent of eliminating (or
reducing the frequency of occurrence of) the class of errors and defects that is
most costly.
4.1SPI Tasks and Responsibilities

These are the lists of the proponents name corresponds
with the position
Lead Programmer: AlburoMarichu
4.1.1 Software Configuration Management and Overview

During the time of the software development we will be making
changes to our original plans. Software Configuration Management Plan is
developed so that we can identify the changes, control the changes,
making sure that the plan is implemented correctly and to making sure that
we report the change to other team members and the clients. For further
information on this topic, please go to the document titled "Software
Configuration Management Plan".
4.1.1.1 SQA Tools, Techniques , Methods
The Proponents have described a lot tools, methods for SQA.
Using voting system, close contact with the client, extensive detail
design, and research on the subject to minimize the errors.
Different tools had been use for SQA for this project. Using
software review, problem tracking, Wetry to follow the ISO 9001
Standard
as
our
organizational
structure,
responsibilities,
procedures, processes, and resources for implementing quality

management. But the truth is, limited by the time and the size of
the team; we are overlapping many of the functions to the same
team members.
3.4 SYSTEM SPECIFICATION
3.4.1
INTRODUCTION
This
section
gives
general
overview
of
Treasury
Management System.
3.4.1.1
Goals and Objectives

The main purpose of Treasury Management
System is to automate the entire process
The goals of treasury system are:

out by a business.

Improves
automatic
short
update
and
of
long-term
treasury
liquidity
worksheets
through
Provides

To provides complete auditing one tracking.

By creating a system that can provide a complete auditing in one
tracking.

funds of business.

their expenses.




user
friendly
system
for
every
merchandising


3.4.1.2
System Statement of Scope

In this section, the general requirements of the
proposed module will be discussed.
Deposits
When it comes to deposit first the treasury will record
the money before they deposit.
Withdrawals
Regarding in withdrawals the treasury will receive the
request then the treasury will give to accounts payable
to approve the request so treasury will withdraw the
money to give to accounts payable and receivable. Its
up to them to give the money to the one ho request.
Disbursements
The flow of disbursement in treasury is when
department give another request to the treasury
because the first request is not enough so the treasury
will approve the request.

Issuance of Invoice
These are the list or record of the transaction.
Example: the amount of request, the number of
request, date and time.
3.4.1.2.1
General Requirements
The following general requirements were
laid out for the proposed module named Treasury
Management System:
A way in which treasury system could add new facilities to
the database.
A way in which treasury system could generate electronic
checklist.
A search on all electronics checklist
A way in which they could generate report to be sent out to
facilities.
A way in which all financial records and checklist could be
stored electronically.
A way in which they could view data which was entered into
the database prior to their software.
3.4.1.3 System Context

If the proposed project successfully be implemented multiple
users will be using the proposed module simultaneously, Human
Resource, Accounts Payable and Receivable, Sales Monitoring
and system administrator.
3.4.1.4 Major Constraints
Compatibility
Software incompatibility the system which cannot
operate satisfactorily together on the same computer or
different computers linked by a computer network.
People ware
The proponent has limitation on time to test the product at
the client's facility. They have access to the facility only during
the regular office hours. They also have to set us schedule
around the available time of the inspector that is to help them,
so time schedule will be a major constraints when they talk
about testing at the side
3.4.2
FUNCTIONAL DATA DESCRIPTION

This section describes overall system function and the information
domain which it operates.
DATA DESCRIPTION
3.4.2.1 Major Data Objects

Treasury:
Accountant Data Object
Accounts payable and receivable Data Object

Point of sale Data Object
System Administrator Data Object
Request form Data Object
Transaction Data Object
Receipt Data Object
Report Data Object
3.4.3
Human Interface Description

Accountant
The accountant can only manipulate the proposed system. The
accountant can record all the transaction and print report.
System Administrator
The system administrator can manage the system, and
can manage the software and hardware configuration to make sure
that the process is alright.
3.5 Software Requirements Specification

3.5.1
Introduction
This section will describe the software requirements and
specifications of the proposed Treasury System.
3.5.1.1 Goals And Objectives

The goals of the proposed module are:
To make it easily monitor the money that taken in

and out by a business.

Improves
automatic
short
update
and
of
long-term
treasury
worksheets
liquidity
through
Provides

To provides complete auditing.

By creating a system that can provide a complete
auditing.
funds of business.

their expenses.




user
friendly
system
for
every
merchandising

3.4.1.2
SYSTEM STATEMENT OF SCOPE

In this section, the general requirements of the
proposed module will be discussed.
Deposits
Withdrawals
Disbursements

Issuance of Invoice
3.4.1.2.1
The following general requirements were
laid out for the proposed module named

Treasury System.
3.5.1.2.2
System Functionality
Interface
Database
Training
Mobile Apps
Free Format Query
Personalized Screen
Import Export
Analytical Reports
Extended Enhancement
The proponents will add an android mobile
application for the enhancement of the system.
3.5.1.3
SYSTEM CONTEXT
If
the
proposed
project
successfully
be
implemented multiple users will be using the proposed

module simultaneously, Accountant, Accounts Payable
and
Receivable,
Sales
Monitoring
and
system
administrator.
3.5.1.4 MAJOR CONSTRAINTS
Developing Environment
The use of Open Source Software and a Proprietary
Software is an advantage in the system. From the flexibility
of the open source and security of the proprietary produces
powerful system.
Compatibility
The system can be used in different environment and
will encounter minimal error.
People ware

about testing at the side
3.5.2Usage Scenario
3.5.2.1 USER- PROFILES
There will be three levels of users:
System Administrator (Full Control)
Accountant (Transaction)
3.5.2.2 Use- Cases
3.5.3
Data model And Description
3.5.3.1 Data Objects and Dictionary
Employee
They are the one who use this propose module.
Bank Officer
Bank officer is the one responsible to handle and
manage the money.
Deposits
Disbursements

Issuance of Invoice
Example: the amount of request, the number of request,
date and time
3.5.3.2 Relationships
TREASURY_ACCOUNT
TREASURY_BANK
PK Bank No:
Bank name:
Bank location:
Bank_Tel.No:
PK Acc._ID:
Position:
Username:
Password:
TREASURY_WITHDRAWAL
TREASURY_DISBURSEMENT
PK Dis_No:
FK Acct_ID:
Dis_Requested by:
Dis_Dept.name:
Dis_Position:
Dis_Purpose:
Dis_Amount:
Dis_Total:
Dis_Date:
Dis_Approval:
FK Bank_no:
FK With_no:
TREASURY_Invoice
PK Inv_no:
FK Dis_no:
FK With no:
MerchandisingInv_amount:
Inv_Date:
Inv_Time:
Inv_Dept:
Treasury
PK With no:
FK Bank_no:
Acct._no:
Acct_Date:
Acct_Time:
Acct_emname:
Acct_Savings:
Acct_Balance:
Acct_Teller:
With_Amount:
TREASURY_GLreport
PK Acct_Id:
Acc_Name:
GL_Date:
GL_Description:
FK Dep_no:
Module
System
FK With
no:
FK Dis_no:
FK Sales_no:
Sales_TotalAmount:
TREASURY_DEPOSIT
TREASURY_BANK OFFICER
CASH
PK PK
Off_DepCashno:
ID:
Off_Lname:
FK
Bank_No:
Off_Fname:
FK
Acc._ID:
Off_Mname:
Acc._
Name:
Off_Position:
Acc. _Position:
FK Bank name:
Dept._Amount:
FK Bank location:
Dept._Date:
Dept._Time:
Dept._Com. Name:
TREASURY_POSrep
FK
Sales_no:
User_ID:
TREASURY_DEPOSIT
Total_Date:
Total_Time:
Dep_no: CHECK
Sales_Amount:
PKTotal_Daily:
DepCheckno:
FKTotal_Weekly:
Bank_No:
Total_monthly:
Bank_Name:
Total_yearly:
Bank_Location:
FKGTotalAmount:
Acc._ID:
TREASURY_AccR/Prep
Bank_name:
Acc._
FK
FK
FK
Name:
Inv_no:
Acc. _Position:
Dis_no:
Dept._Amount:
WithDept._Date:
no:
Acct_amount:
Dept._Time:
Acc_Dep:
Dept._Com. Name:
Acc_Approval:
Acc_time:
Acct_Date:
TREASURY_Salesmonrep
TREASURY_DepRep
PK Dept_no:
Dept_Amount:
Acct_no:
Bank_name:
SUBSYSTEM
Dept_Date:
FK Dept_Time:
FK DepCashno:
DepCheckno:
TREASURY_Disbrep
FK Dis_no:
Dis_Amount:
Dis_Purpose:
Dis_Dept:
Dis_Date:
Dis_Time;
Dis_Approval:
TREASURY_POSrep
PK Acct_Id:
Acc_Name:
GL_Date:
GL_Description:
FK Dep_no:
FK With no:
FK Dis_no:
FK Sales_no:
Sales_TotalAmount:
PK Sales_no:
User_ID:
Dept_name:
Sales_Date:
Sales_Time:
Sales_daily:
Sales_weekly:
Sales_monthly:
Sales_yearly:
Sales_TotalAmount:
PK Sales_no:
User_ID:
TREASURY_WithRep
Dept_name:
Sales_Date:
FK With no:
Sales_Time:
With_Amount:
Sales_daily:
FK Bank_name:
Sales_weekly:
Acct_no:
Sales_monthly:
With_Date:
Sales_yearly:
With_Time:
Sales_TotalAmount:
With_Dept:
PK Sales_no:
User_ID:
Dept_name:
Sales_Date:
Sales_Time:
Sales_daily:
Sales_weekly:
Sales_monthly:
Sales_yearly:
Sales_TotalAmount:
TREASURY SUBSYSTEM
TREASURY_AccR/Prep
FK Inv_no:
FK Dis_no:
FK With no:
Acct_amount:
Acc_Dep:
Acc_Approval:
Acc_time:
Acct_Date:
3.5.4FUNCTIONAL MODEL AND DESCRIPTION

3.5.4.1 System Flow Diagrams
LOGIN
Deposit of Cash
USER
DEPARTMENT
HEADS
Withdrawal of Cash
Disbursement of Cash
Issuance of Cash
General ReportOWNER

LOGOUT
3.5.4.2 Subsystem Flow Diagrams
LOGIN
Deposit of Cash
USER
DEPARTMENT
HEADS
Withdrawal of Cash
Disbursement of Cash
Issuance of Cash
General ReportOWNER
LOGOUT
3.5.5RESTRICTIONS, LIMITATIONS AND CONSTRAINTS

The system shall be integrated with the other systems of the

Merchandising System
All server side code shall be written in JAVA.

Microsoft SQL Server will be the database server of the system.
Compatibility
Software incompatibility the system which cannot
operate satisfactorily together on the same computer or
different computers linked by a computer network.
People ware
about testing at the side.
3.5.6
VALIDATION CRITERIA
The proponents used NETBEANS for implementing a
system because of the special features of the software
NETBEANS platform allows application to be developed
from a set of modular software components called
modules. Application based on the NETBEANS platform
(including the NETBEANS IDE itself) can be extended by
third party developers.
The Proponents use SQLYOG for database
software because it is the most powerful MSSQL manager
and admin tool, combining the features of MSSQL
Administrator, phpMyAdmin and other Front Ends and
MSSQL GUI tools. MSSql is a relational database
management systems developed by Microsoft. As a
database,
The proponents will test the transaction processes that are
needed in the Treasury if should all be working and can

generate real time records.
The proponents will test Search engine on the Query
section should produce a real time data that is stored in the
database. The proponents will test if reports should be
informational and if the contents should be based on the
data that has been inputted in the system and stored in the
database.
3.6 SOFTWARE DESIGN SPECIFICATION

3.6.1Introduction
This section describes the design for the proposed
Treasury System.
3.6.1.1 Goals And Objectives
The goals of the proposed module are:

out by a business.

Improves
automatic
short
update
and
of
long-term
treasury
liquidity
worksheets
through
Provides

funds of business.

example laptops. The treasuries are the one who provides
their expenses.



user
friendly
system
for
every
merchandising

To provides complete auditing one tracking.

By creating a system that can provide a complete auditing in one
tracking.
To reduce difficulty
To have less cost
To be efficient
Provide a User Interface and Database Design that will follow the
standard of the Quality Assurance Team.

Provide a generic system that can be configured (ex. Logo) to cater any
hospital using the system.
3.6.1.2 SYSTEM STATEMENT OF SCOPE
Deposits
Withdrawals
Disbursements
Issuance of Invoice
3.6.1.2.1
The following general requirements were laid out for the project
named treasury system
A way in which treasury system could add new facilities
to the database.
A way in which treasury system could generate
electronic checklist.
Simple
or
layman
terms
are
required
for
easy
understanding of the system
Short but brief and organized explanation of words and

messages on every field
A way in which all financial records and checklist could
be stored electronically.
A way in which they could view data which was entered
into the database prior to their software.
3.6.1.3 System Context
User-friendly interface for an organized system
resulting to faster processing of transactions
Database Design structure following the business

intelligence of the system
3.6.1.4 Major Constraints

Developing Environment
The use of Open Source Software and a Proprietary
Software is an advantage in the system. From the flexibility
of the open source and security of the proprietary produces
powerful system.
Compatibility
The system can be used in different environment and
will encounter minimal error.
3.6.1.5 Database Description
Employee
They are the one who use this propose module.
Bank Officer
Bank officer is the one responsible to handle and
manage the money.
Deposits
Disbursements

Issuance of Invoice
Example: the amount of request, the number of request,
date and time
3.6.1.6 Architectural and Component Level Design

Architectural Diagram
Bank Officer Accountant Maintenance Self Test Employee Administrator
3.6.1.7 Program Structure
A diagram showing the program structure of the system in
terms of process and overall system.
System Setup
Bank
Bank Officer
Employee
Account
Disbursement
Deposit
Withdrawal
List of Bank
List of Withdrawals
List of Deposits
List of Disbursements
Deposit Report
Invoice
Withdrawal Report
Disbursement Report
Transaction
Queries
Reports
Utilities
Configuration
Logout
3.6.1.8 Description for Components

Specify the hierarchy of data used in each transaction by

providing diagrams
Must have the following
Administrator
Accountant
Bank Officer
Employee
Test specification
This chapter gives a general overview of the testspecification for the Treasury
Management System. In this chapter the proponents will discuss the test
scenarios.
Goals and objectives
The proponents first will test their propose modulebut before that the software
has to go through a series of tests before its final release. Error free software
is extremely difficult to achieve. After all, nothing is perfect. Especially for
software developed in a short time frame. But high quality can be achieved
with a detailed test specification. All (or least most) of the test case willbe
listed, the development team will follow it step by step,to test all the necessary
objects, data flows, limits, boundaries, and constraints of the software.
The proponents would like to have a test specification to counter any
difficulties that may impact the development and the future performance of the
software. The proponents goal is to assists the project team in developing a
strategy to deal with any errors. For this, the proponents will take a look at the
most common errors to some very uncommom errors as well.
Statement of the scope
This is an overall plan for integration of the proposed module and a description
of specific tests are documented in this section. Below are the differrent kinds
oftests that the team will take to ensure the quality of the proposedmodule.
Unit Testing
Desktop Application
Database
Unit test will be performed using testing methods.
Integration Testing
Desktop application
Database
Validation Testing
The proponents will test software as whole, so all the units of the software will
be included
Desktop application
Database
High-order Testing
The software will be tested for several test methods. Units to be tested are.
Desktop application
Database
Major Constraints
In this section the proponents will talk about the business, technical or
resource relatef constraint that may keep us from performing all tests
necessary.
1. The proponents has limitation on time to test the proposed module at
clients facility.so time schedule will be a major constraints when
proponents talk about testing at the site.
2. The proponents does not know any hacker that can help the proponents
test the security problems. So the proponents have to rely on our own
knowledge and have trust the software for the security.
3. the proponents also does not have large enough group to have many
people use the application at the same time to perform real stress
related testing. So they will not be able to test the proposed module for
the larger user base.
Testing plan
The proponents want the proposed module to be bug free. The proponents
want to make sure that there are no defects in the proposed module. So
proponents will be spending large amount of the total software development
time on the testing. Below is the description of the testing procedure.
Software (SCIs) to be tested
Interfaces
The test to be carried on these interface windows are described below.
Login Window
The proponents will make use of several different names to log in to the
system, so proponents will be testing login window. They will also test OK and
Cancel buttons on this window by performing test above.
Switch User:
The function of this is to switch between the users.
Exit:
The function is to exit out the user.
Create/Modify:
When click on this choice proponents will be presented.
Screen used to create or modify inspection.
File Results:
When they select this choice they will be presented with file result window.
Approval
When they select this choice they will be presented with Approval Window. The
proponents will test the button by clicking on it to go to Approval Window.
Print Report
When proponents select this choice they will be presented with Print Report
Window. Proponents will be able to go to print report window. They want to

make sure that the proper window is presented.
Approval:
This option is presented and works only for employees of treasury. Proponents
need to make sure that when selected by employees software will bring up
window containing queued list of letters waiting to be approved
Reports:
Print Deposit Report
When they select this choice they will be presented with Report Window.
Print Withdrawal Report
Print Disbursement Report
Print Reimbursement Report
Maintenance:
Request Letter
When they select this choice they will be presented with request letter window.
Users:
When they select this choice they will be presented with users window.
System Setup
Bank information
Exit
Transaction
Deposit
Withdrawal
Disbursement
Reimbursement
Request form
Invoice
Query
List of deposit
List of withdrawal
List of disbursement
List of reimbursement
Unit testing
In the unit test case the proponents will be testing the separate modules of
the software. Proponents willtesting each module or components of the
software is tested individually. They will test the components by passing data
through it and they will be monitoring data to find the errors.
The proponents will be looking for entry and exit conditions of the data. They
will make sure that all the components work without any troubles.
The test primarily be carried out by the programmer who designed and
implemented the module. Lead tester will than carry out test on the modules to
finalized the testing.
Integration Testing
In this method of testing they will implement the software at the users location
and will run it. So they will be testing the proposed module on clients network.
As part of testing, will be looking for any signs of the collision between our
software components and those of the clients. Proponents want to make sure
there is no confusion among the application on the network when they are
running simultaneously.
The proponents will install the software and will run it. Proponents will have
several different other application open as well. The proponents want to make
sure that all data is saved and there is no loss of data or database anomalies
in the system.
Validation Testing
In this method of the test the proponents will be working with the user to find
out if the software developed in valid for the clients. The proponents want to
make sure that the client is getting what he/she asked for. They will look at the
software requirement document in the case of conflict or misunderstanding
with client regarding software requirements.
The proponents will perform. The testing where the software is completed
and they test all the software components together.
High-order testing
High order test are combination of several different methods. They will be
performing tests. These tests will be performed at software developer facilities
and at clients using the hardware that are available to clients.
Recovery testing
In this test method the proponents concerned with the software's
ability to retrieve lost data or to make sure that software does not
lose any data during updating o the database. The proponents will
be mainly looking at transaction processing when proponents talk
about the recovery testing the software. In transaction protection
proponents will be testing the software to make sure that when it
saves anything it will serve all of it or none of it this is necessary to
avoid existence of corrupt data in database.

Treasury 05a v3 0

Uploaded by

Copyright:

Available Formats

You might also like

Treasury 05a v3 0

Uploaded by

Document Information

Original Description:

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

Treasury 05a v3 0

Uploaded by

Copyright:

Available Formats

CHAPTER 1.

Problem/ Opportunity Description

Poor control cost

Secure Data Records.

Merchandising- Treasury Module System

To make it easily monitor the money that taken in and

To reduce manual data entry.

complete auditing and tracking

To maintain their principal capital.

To provides complete auditing.

expenses of company. Auditors

examine personal and organizational

accuracy, detect fraud, and identify

various store setups and resets in

People who keep the financial records

Merchandising- Treasury Module System

and loss statement or P&Ls. P&Ls

Financial accounting also produces

asset/">assets, debts, and equity at a

include monthly management reports

He/she will need to be able to

The Project Manager is the person

Merchandising- Treasury Module System

recommendation to help computer

begin a project by determining the

Business Analyst is used to identify

facilitate that change.

the information regarding to the

To create a system that can organize the records of

Merchandising- Treasury Module System

people requested for the budget of their needs.

To create a system that can manage the money that

To create a System that can easily search files.

To create a system that is accessible and well

innovate the business.

company that needs it.

Objective 1: Security Information

requested for the budget in the

consequently, the money taken out

Objective 4: To create a System that can easily search files.

Objective 5: To create a system that is accessible and well integrated to

subsystem. so if the system need

Objective 6:To create a cost-efficient, understandable, reliable and user

friendly system for every merchandising company that needs it.

All the accounts for recording transactions

Enterprise Information System Required Functionalities

Free Format Query

1.3 Project Plan

Approach and Methodology

The Proponents conducted

to keep all the documentation.

The proponents conducted a

storming of the group.

The Proponents analyze the

problems to solve those problems

about the design of the system

In this phase, the proponents