Professional Documents
Culture Documents
0 - PROJECT CHARTER
1.1
PROJECT BACKGROUND
POS, abbreviation for Point- of- Sale is a comprehensive definition that
can include merchandising benefits, displays and the procedures used to
facilitate transactions. A POS system is a computer software and hardware
system that archives sales as they occur; it solves diverse problems of
operations and record-keeping.
POS systems are designed to record any and all sales. Not only does
that mean timely and precise sales tracking, but it also lets you freely classify
inventory levels, particularly when there is a mismatch of figures in the system
with actual available stock.
POS system not only lets you regulate your transactions, but it also
puts a wealth of information. Imagine being able to compare years of sales
data with just a few mouse-clicks. A POS system can also track inventory,
even modifying quantities for seasonal demands. In a nutshell, a POS system
aids to keep a constant eye on bottom line.
POS is used primarily for managing retail goods. It is used for stores,
restaurants, hospitals and other forms of business that transact the goods or
products purchased by a customer or consumer from a cashier. Maybe the
most traditional use is in the stores, focusing on merchandising.
A check-out counter is at the aisle where people place items that they
have chosen to purchase from a store, such as supermarket or department
store. The cashier rings up each item on the cash register and obtains the
total. The items are placed in bags and the customer can take them after
paying. POS system calculates the total cost of purchased products or goods
by means of scanners, weighing scales, electronic and manual cash registers,
touch screens and other wide variety of hardware and software available that
is used in POS. At the end of every transaction, a receipt will be generated,
having the purchase report. Sales report is also produced to monitor and
manage business. The system provides the capabilities to carry out
transactions and conduct daily store activities such as scanning items,
applying price adjustments, tendering, and printing receipts.
Scoping with Price Management, it is used in dealing with monitoring of
the overall price of products, creating product price, updating price, printing
tags, and implementing it. The management will be the one to decide the
prices of the products. Price Management defined as the process of
integrating all perspectives and information necessary, to arrive consistently at
optimal pricing decisions.
1.1.1 Problem/ Opportunity Description
the
that
use
automated
POS
systems
Transaction enabled
The cashier who is about to use the proposed Point- ofSales with Price Management Module can be able to create
automated transactions with the products being purchased by
the customers with faster and more efficient process than the
manual process.
Reports
The cashier and its supervisor who are using the
proposed module can be able to generate Sales Reports,
Terminal Reports of the proposed module to secure the
business and avoid cash and inventory shortages.
Price Viewing
The user of the proposed module can look up the
price of products using the proposed module. It is essential
for the users to view first the amount of the products they
Manage Price
The user of the proposed module can create the price of
the products accordingly. The user can also manage the price
of products and apply discounts. The user shall be benefited
from the proposed module because it will be automatically be
updated once the command of the user is given in managing
price. Additional is the security of data records.
Produce Outputs
The users of the proposed module have the ability to
produce receipts and price tags accordingly. Unlike the old
way, the proposed module shall be convenient not just in
doing transactions, but also in producing valuable outputs that
the company and the customer needs. The user of the
proposed module shall have convenience in their job for they
will just click and the system will do the other jobs.
Good Image
The end users of the proposed module will be having a
good image from the customers theyre serving. The
proposed module can give good customer service for
transactions will be made on time. The data being processed
will be accurate and reliable to avoid any conflicts for both
parties.
Higher Profit
The company that will use the proposed module shall be
benefited by having a higher profit for the system can manage
fast transactions and can avoid data discrepancies because it
has accuracy of its processes.
1.1.3 Goals
Stakeholders
Cashier
Description/ Participation
He/she is the person who scans the goods
through a machine called a cash register that the
customer wishes to purchase at the store.
He/she is the recipient of a good, service,
Customer
Consumer
Checkout
Supervisor
business.
The
checkout
supervisor
gives
Lead
Programmer
Project
Manager reports
and
changes,
escalate
issues
and
mitigate risks.
He/she is an IT professional who specializes in
System Analyst
analyzing,
designing
information
systems.
and
Participate
implementing
in
project
Documents
information
products
traditionally
known
as
1.2
PROJECT SCOPE
1.2.1 Objectives
1.2.2 Deliverables
Objective no.1: Create an automated system
10
Project Deliverable
Transactions
payment
especially
in
stores
and
Credit
Card
Transactions
communicate
to
the
respective bank.
o
products.
Table No 1.3 Deliverables of Objective no. 2
12
Update Price
the
changes
had
done
to
price
management.
Discounts
Senior Citizen If requirements are met,
accumulated
of
P650.00
will
be
of
the
card.
Members
that
13
transaction
as
proof
of
purchase.
Good
Price tags
receipts
are
from
normal
transactions
White Tags (Normal Price Tags),
Orange, Yellow and Red Tags can be
produced accordingly.
Table No 1.5 Deliverables of Objective no. 4
Objective no. 5: Manage special conditions in transaction processes
Project Deliverable
Voiding
14
Mobile Apps
Free Format Query
15
1.3
Personalized Screen
Import Export
Analytical Reports
PROJECT PLAN
Methodology
The proponents used System Development Life
Cycle (SDLC) as the methodology in doing the proposed
module.
SDLC Chart (Waterfall Diagram)
Planning
16
Analysis
Design
Implementation
Maintenance
1.1.3.2
Approach
Phases
Planning
Plan
The proponents conducted a meeting
with the other groups about the
proposed main system.
The
proponents
conducted
a
brainstorming
about
the
subsystem/ proposed module.
The proponents conducted researches,
surveys and interviews about the
proposed module.
The proponents ask guidance to their
adviser about the proposed module.
The project manager divided the jobs
according to the ability of a single
group member.
17
Analysis
Design
Task Name
Group meeting
(Planning)
Overall meeting (4th yr
Start
06/24/14
06/28/201
4
Finish
06/24/2014
06/28/2014
Duration
2 hours
4 hours
18
3
4
5
6
7
8
9
BSIT)
Group meeting with
other groups
Group Meeting
(brain storming about
system)
Look/Search
for
Adviser
Adviser is selected
Group Meeting with
head PMs
Meeting with Adviser
PM divided the group
work for each member
10
Conduct a Research
11
Group Meeting
12
Conduct a Survey
13
Group Meeting
14
Conducted a Interview
15
16
Group Meeting
Group Meeting with
Adviser
17
Project Charter
18
19
Group Meeting
Chapter 2
20
Group Meeting
21
22
Chapter 3
Group Meeting with
Adviser
23
Mock Defense
24
Group Meeting
07/01/201
4
07/04/201
4
07/07/201
4
07/09/201
4
07/10/201
4
07/12/201
4
07/14/201
4
07/15/201
4
07/19/201
4
07/21/201
4
07/26/201
4
07/28/201
4
08/01/201
4
08/02/201
4
08/04/201
4
08/09/201
4
08/11/2014
08/16/201
4
08/18/201
4
09/05/201
4
09/08/201
4
09/13/201
4
07/01/2014
1 day
07/04/2014
1day
07/07/2014
1 day
07/09/2014
1 day
07/10/2014
1day
07/12/2014
1 day
07/14/2015
1day
07/18/2014
1 week
07/29/2014
1day
07/25/2014
1 week
07/26/2014
1day
07/31/2014
3 days
08/01/2014
1day
08/02/2014
1 day
08/08/2014
1 week
08/09/2014
08/15/2014
1 day
1 week
08/16/2014
1 day
09/05/2014
3 weeks
09/05/2014
1 day
09/12/2014
1 week
09/13/2014
1 day
19
25
Revision of Chapter 1
and 2
26
Group meeting
27
Revision of Chapter 3
Group Meeting with
Adviser
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
09/15/201
4
09/20/201
4
09/22/201
4
09/27/201
4
09/29/201
4
10/06/201
4
10/13/2014
09/19/2014
1 week
09/20/2014
1day
09/26/2014
1 week
09/27/2014
1 day
10/03/2014
1 week
10/10/2014
10/17/2014
1 week
1 week
11/03/2014
11/14/2014
2 weeks
11/17/2014
11/17/2014
1 day
11/18/2014
11/18/2014
1 day
11/22/2014
11/22/2014
1 day
11/24/2014
11/24/2014
1 day
11/25/2014
11/26/2014
12/01/201
4
12/06/201
4
12/08/201
4
12/09/201
4
12/15/201
4
12/20/201
4
11/25/2014
11/26/2014
1 day
1 day
12/05/2014
1 week
12/06/2014
1 day
12/08/2014
1 day
12/12/2014
1 week
12/19/2014
1 week
12/20/2014
1 day
01/09/2015
1 week
01/10/2015
1 day
01/05/201
5
01/10/201
5
20
47
Discussion of Chapter
5
48
Chapter 4
49
Group Meeting
50
Chapter 5
51
Group Meeting
Continuation
of
Creating
the
Proposed module
Group Meeting with
Adviser
Continuation
of
creating the proposed
module
52
53
54
55
58
Group Meeting
Continuation
of
Creating the proposed
module
Finished the proposed
module
and
Documents
Checking of proposed
module with Adviser
59
Final Defense
60
Group Meeting
61
Re-Defense
62
Group Meeting
Submission of Final
project
56
57
63
01/12/201
5
01/19/201
5
01/24/201
5
02/02/201
5
02/07/201
5
02/09/201
5
02/14/201
5
02/16/201
5
02/21/201
5
02/23/201
5
02/28/201
5
03/02/201
5
03/09/201
5
03/14/201
5
03/16/201
5
03/21/201
5
03/23/201
5
01/16/2015
1 week
01/23/2015
1 week
01/24/2015
1 day
02/06/2015
1 week
02/07/2015
1 day
02/13/2015
1 week
02/14/2015
1 day
02/20/2015
1 week
02/21/2015
1 day
02/27/2015
1 week
02/28/2015
1 day
03/02/2015
1 day
03/13/2015
1 week
03/14/2015
1 day
03/20/2015
1 week
03/21/2015
1 day
03/23/2015
1 day
21
22
Policy Implications
planning
about
scoping
becoming
and
sub-
out-
systems
groups
the
and
main system.
Issues of budget in doing
subproper
communication
proposed
is
being
implemented.
Auditor and Treasurer must
implement
to
misunderstanding
of
group members.
being
an
open
attain
to
Right
to
avoid
budget
issues.
Proper time management and
doing
project
Timeline.
Discipline
in
time
management
Issues
shortages.
Meeting with other groups,
about
the
Subsystems
proper
must
scoping
be
of
module.
Point- of- Sales with Price Management Module
23
of
the
proposed
already implemented
System Malfunction
call
the
system
administrator.
Table No 1.9 Issues and Policy Implications
1.3.5 Risk Management Plan
Risk Factor
Probability
(H-M-L)
H
power
Impact
Risk Management
(H-M-L)
Action
H
Always have a back- up
of
the
system
either
or
cloud
external
project.
Unexpected
in
setting
where
making.
24
Unexpected
expenses
Budgeting of Expenses,
save
making.
thrifty.
Shortage
of
money and
be
is
not
expectedly available in
and
project-
problems.
making.
The
tasks
to
avoid
assigned
to
complete it
The hardware and
gets malfunction.
25
Application Development
To make available applications and systems which
provide the required functionality for the proposed module. This
process includes the development and maintenance of custom
applications as well as the customization and implementing the
system.
Alternative Options
Research on libraries about the
knowing the process of the system project, also in the internet to minimize
similar to the proposed module.
26
the companies.
Required
Hardwares
in
Softwares
and
developing
proposed module.
the proposed modules scopes, and project team will be on the guard for
integrations
systems
with
and
other
revisions
The
teams
thoughts
about
the
27
Hardware Specification:
Processor
Minimum requirement is core i3 CPU or higher m350 @2.27 Ghz
Memory
Minimum requirement of 1 GB RAM and 2GB higher.
Hardware Peripheral:
Computer Monitor
Computer Monitor will be used as a screen to view the
interface of the proposed module.
Barcode Scanner
Barcode scanners are used to scan bar codes that are placed
at the products. Scanned items details will be seen on screens/
monitors.
Thermal (Printer)
Thermals are used to print hard copy of receipts, price tags
and SKUs.
Software Specification:
Operating System
28
Database
MSSQL is the back-end or the storage of the proposed
module.
1.5
Project Manager
Business Analyst
Marayag,
Vivian
Riodique,
Jayson
She
responsible
of
the
planning,
System Analyst
is
is
responsible
for
knowing
the
Elepana,
Mary
Joylyn
29
Sale,
Lead Programmer
RJay
Documents Specialist
Adviser
Decelo,
Angelo
Mr. Billy
Tierra
PEC
(Project Evaluation Committee)
PROJECT BUDGET
BUDGET ITEM
DESCRIPTION
BUDGETED COST
ONE-TIME
COSTS
Computer Monitor
Terminal (Card
Swiper)
Barcode Scanner
P1,750,000.00
30
Thermal (Printer)
P50, 000.00
P2,700,000.00
Broadband
P50.00 x 30 days =
(Internet Provider)
Electricity
Power source
P1,500.00
P2,500 x 30 days =
ONGOING
COSTS
Utility Expenses
P75,000.00
HR
Project Manager
P50,
Business
months = P500,000.00
P40,000 x 10 months =
000.00
10
Analyst
System Analyst
P400, 000.00
P40, 000 x 10 months
Documents
= P400, 000.00
P30, 000 x 10 months
Specialist
Lead
= P300, 000.00
P18,000.00 x 5 months
Programmer
TOTAL ONGOING COSTS
= P90,000.00
P1,766,500.00
31
FOREIGN STUDIES
32
speedily and
staff at restaurants to
2.1.2 McDonalds
McDonalds is very busy restaurant because many costumers goes
there, the first priority for McDonalds is to deliver best restaurant
experience for the customers, for that McDonalds used pos system
point of scale system to ensure fast accurate order because this
Point- of- Sales with Price Management Module
33
34
Multi-currency processing
35
SPAR POS offers many benefits that should significantly increase gross
profit through:
Improve price control
Faster replenishment of stock
Improved shelf discipline
Improved efficiency at the till
Improved stock control
Suggested ordering
Sales and gross profit reporting at the end of each week.
A credit card facility with chip and pin and ISDN authorizations
SPAR POS has a full stock control module that will put you in total
control of your stock.
36
37
impacts,
and
implement
new
prices.
Syncron
delivers
price
Execution
Optimization
Analytics
38
Provide well-defined price corridors to your sales team when they need
it most
2.2
LOCAL STUDIES
2.2.1 SHOPWISE-
CYWARES
RETAIL
(SIMPLE
RETAIL)
POS
SOFTWARE
According to CYWARE INCORPORATED (2009) a software
development firm specializes in retail and payment processing
Point- of- Sales with Price Management Module
39
http://infotemajorproject.blogspot.com/2009/06/shopwise-
cywares-retail-simple-retail.html
40
future
store
openings.
41
2.2.3 7-Eleven
At 7-ELEVEN stores, each swipe of a barcode represents a
piece of sales transaction being saved to the immense database of the
POS system, which collects information from the seven million
consumers who shop at 7-ELEVEN every day. Our powerful POS
system, which manages thousands of products, the processing of
orders from stores, and the collection and analysis of daily sales data,
is an essential tool which facilitates the operation of 7-ELEVEN.
To pinpoint consumer needs, PCSC introduced the secondgeneration POS (point of sales) system in 2003. The new system
updates immediate sales and inventory information hourly, publishes
weather forecasts four times a day, and transmits consolidated product
information for multi-media presentation. This system has enabled us to
manage
information
in
strategic
way
and
increase
our
competitiveness.
and
develops
new
products
accordingly, strengthens
42
Source:
http://www.7-11.com.tw/en/business/is.html
2.2.4 KFC
Before year 2000, KFC Philippines was using multiple IT
solutions to address their corporate requirements. Because of this, the
integrity of the reports became
had a hard time tracking down their stocks. The KFC management
could not react as quickly and as timely as they wanted to. The reason
behind
these
problems
was
evident:
the
systems
could
not
43
restructuring,
user
training/
re-training,
new
report
All the
44
development from the Kaisa team. Kaisas solution was to use the
readily available SAP-LES, and SAP Query functionality, and SAP
Business Warehousing (BW) for more complex reports.
Improved system controls without compromising the speed of
process flow.
KFC needed to improve controls in the system and in the
business process to eliminate pilferage and unnecessary losses. New
functionalities such as shelf-life expiration date check, the use of
delivery notes for stock transport, and a custom physical inventory
taking transaction among others were introduced to optimize the flow of
goods and to improve stock keeping. The main objective was to make
sure that stocks are delivered on time, of the right type, of the right
quantity, and are of the highest quality.
Improved forecasting
KFCs Accounting and Purchasing groups were concerned that
they might lose the data of past transactions since these were logged in
the old system. This historical data is used by both groups as reference
points for forecasting. Through SAP BW, Kaisa addressed these
concerns and incorporated the live data into the reports with historical
data. Through SAP BW, KFC was able to track price changes,
accounting balances, and other vital information and was able to
compare it with the current data in a seamless way.
Change drives efficiency and profitability.
It is inevitable that in every organization, users might be reluctant
to change since they might be well accustomed to their present system
already. However, with the ever evolving business landscape, it is
pertinent that companies upgrade continuously to be able to keep up
with the changing times so as to not get left behind.
45
In KFC, they did not expect that their cluttered business process
and bad practices were going to be replaced with a more controlled and
structured environment. With the new Enjoy transactions, enhanced
report generation tools, and with more controls in the system, the users
saw that the upgrade in the system made their load lighter and their
business work process more efficient. KFC was able to increase their
annual
upgraded system.
Source:
http://www.kaisa.com/wpcontent/themes/kaisa/pdf/KFC_Success_Story
.pdf
46
Low stock
Pending orders
Quick Checkouts
Touch screen and bar code scanner enabled
Shift Reports
Source:
http://posnation.com/meat-market-pos-system
2.3
SYNTHESIS AND
RELEVANCE
TO THE
STUDY (MATRIX-
COMPARATIVE ANALYSIS)
Synthesis of the study:
Point- of- Sales with Price Management Module
47
The special feature that the proponents would want to put on the
proposed module is the facility for mobile application that runs with android
application. In this generation where technology are reigning, the needs of
customers about the knowledge and accessibility of their necessities must be
given as easiest as possible as could be. Hence, a lot of people are already
using smart phones because it has a lot of features, and other phone brands
sells cheaper price of it. So the proponents would want to put the ease of
transactions in their palms by the use of their android phones. This will be
used as price guide for the customers and they could reserve the product and
just get and pay the purchased items at the store.
Based on the researches concluded by the proponents, all related
companies gathered have the ability to speed the process of their business.
Majority of those related companies automatically progress orders, process
rapid sales and can forecast products. Some are PC based, maybe others are
using touch screens. Few only create backups, few also can track rewards
points. Five out of five produce POS reports, can communicate pricing and
policy changes quickly and accurately that makes pricing easy. Some can
implement new prices while the others cant. All literatures of course runs in
an operating system. None of them are using ms sql as their back ends.
Finally, six out of ten immediately updates their sales.
Hence, in all features being stated, the proponents get all of the said
features and added it to the proposed module. The main feature also will be a
big help to the customers especially in choosing and knowing their desired
purchases. It is important because today, many want for a better convenience
and as possible as it could be, process of purchasing must be done as easy
as possible.
Matrix Diagram
System
Description
and Features
Related Literatures
Pizza Hut
McDonald
s
SPAR
Supermarket
JD Edwards
Point-ofsale
Syncrons
Global Price
Managemen
t
ShopwiseCywares
Retail(Simpl
e Retail)POS
Software
PUREGOL
D Price
Club
7eleven
KFC
Meat
Market
Point-ofSale
-TPLINUX
POS
48
Proposed
module
System
Speed the
business
process
Automatically
progress
orders
Rapid sales
Product
forecasting
PC based
system
Backups data
Reward
points
tracking
Standard
Communicati
ng
pricing
and
policy
changes
quickly
and
accurately
makes pricing
easy
implement
new prices
Facility
for
mobile apps
POS reports
Running in
operating
system
Database: Ms
sql
Immediate
update of
sales
49
50
3.1.1.2
51
System Analyst
The System Analyst manages the risks that occur
which may occur in the process of the proposed module
being planned. The System Analyst keeps the process of
the system clean and free from possible risks that may
occur.
Lead Programmer
The Lead Programmer manages the risks in doing
the syntaxes of the proposed modules. He keeps avoiding
the risks by keeping his codes right.
Documents Specialist
The Documents Specialists shall only document all
things connected in the proposed module. List all risks
and put right decisions on managing it.
RISK TABLE
The
following
table
describes
all
the
risks
52
Risks
Probability
Impact
Risk
Managemen
Hardware
and
Software
15%
t Action
Always have a
back- up of the
while
system
doing
Unexpected
the
project.
either
problems that
external or cloud
storage. Do the
project- making.
project
in
setting
where
problems
15%
a
can
possibly
evade
and will
avoid
distractions.
Budgeting
of
Expenses, save
money and be
comply
thrifty.
necessary
requirements
Ability of a group member is
14%
Choose
worthy
group members
doing
specific
project-
making.
outcome
greatly
task
of
the
depends
in
The
her
project
on
responsibilities
the
and
in
POS
gets
malfunction.
tasks
avoid problems.
14%
As often as can,
check
the
system, system
unit
to
and
53
hardwares used
in the proposed
module.
Table No 3.1 Risks Table
3.1.2.1.1
DESCRIPTION OF RISKS
Business Impact Risk:
This is the risk where concern is that
of the not being able to come up or produce
the product that has impact on the clients
business. If the software produced does not
achieve its goals or if it fails.
Customer Risk:
This is the risk where concern is
clients motivation or willingness in helping
the software development team. If the client
fails to attend meeting regularly and fails to
describe the real need of the business, the
information needed of the proponents will be
lacking.
Development Risks:
If the proponents itself, their sponsors
and clients failed to provide all necessary
equipment
for
the
development
and
54
experienced
application
enough
necessary
to
to
use
the
develop
the
Product Size:
55
of
the
project
is
risky if
the
3.1.2.1.2
56
Risks
Lack of training
Probability
15%
Impact
1
Customer Risk
and experience
Customer may
15%
fail to
Process Risks
participate
Low Product
14%
Product Size
Quality
Where size
14%
Development
could be wrong
Insufficient
14%
Risks
Technology Risk
Obsolete
14%
Business Impact
technology
Product may
14%
estimates
harm the
business
Table No 3.2 Risks Table (sorted)
Impact Values
Description
Catastrophic
Critical
Marginal
57
Negligible
section
describes
Risk
Mitigation,
Monitoring
and
Management for each possible risk in details. It will tackle about the
ways on how to avoid, monitor and to have ways to manage the risks.
3.1.3.1
this
section,
several
different
software
PRODUCT SIZE
In this risk, the size of the codes
inputted at the proposed module varies. The
proponents must estimate the duration time
in coding the functionalities of the proposed
58
BUSINESS IMPACT
In this risk, the quality of product will
be
concerned.
The
Proponents
shall
3.1.3.1.4
PROCESS RISKS
59
features,
get
useful
feature
and
TECHNOLOGY RISKS
This risk will be avoided if the
technology
used
in
developed
in
the
DEVELOPMENT RISKS
Effectiveness of tools in developing
the system must be met in this risk. This risk
includes
the
Hardware
and
Software
expenses
that
requires
in
60
3.1.3.1.7
risk
involves
each
of
the
Performing
tasks
and
doing
PRODUCT SIZE
The proponents shall monitor the
development of proposed module. Starting
from its database size, the database can be
imported
and
exported,
can
also
be
BUSINESS IMPACT
The proponents shall have a meeting
with the end user of the proposed module, s
and their checkout supervisor. End users
must be determinant in the system if it is
good already or lacking of features and
needs improvement. The proponents will be
then aware on what ways must be done and
61
about
the
development
of
the
proposed module.
3.1.3.2.4
PROCESS RISKS
Each proponents tasks must be seen
by other proponents to ensure the product
quality of the proposed module. Informing
other proponents about their duties must be
practiced if it meets the right standards in
system development.
3.1.3.2.5
TECHNOLOGY RISKS
Observing latest technologies and
applying it at the proposed module must be
observed
for
the
improvement
of
the
62
3.1.3.2.6
DEVELOPMENT RISKS
Proponents
must
observe
the
occur
while
doing
the
proposed
module.
3.1.3.2.7
their
duties
and
responsibilities.
63
3.1.3.3.1
PRODUCT SIZE
Time and manpower in doing the
project must be observed. If it lacks, double
time must be needed to meet the projects
objectives.
3.1.3.3.2
BUSINESS IMPACT
If problems occur, end users must be
willing
to
give
information
about
the
proponents
will
only
ask
proposed
module
to
make
time
essential.
3.1.3.3.4
PROCESS RISKS
If work is not done properly, other
proponent must take over to do the job to
meet the standards in developing the
proposed module.
3.1.3.3.5
TECHNOLOGY RISKS
The proponents shall keep in touch
with the latest trends of technology in the
market; new trends that could make the
process of the proposed module become
64
DEVELOPMENT RISKS
In developing the proposed module, if
problems occurred, as soon as possible,
these problems must be solved as early as
possible to resume in developing the
proposed module and must always be
informed about new changes.
3.1.3.3.7
is
having
hard
time
in
Login
Users of the proposed module shall depend on the
Human Resource Module. This module shall burdens the
risks that the Log- in may occur.
2.
65
3.2
66
3.2.1.2
67
listed
are
proposed
modules
SCM
68
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
During
the
system
Approve change
All of the proponents of the
group must be informed about the
changes to the software development
that was proposed by one of the
proponent. After being informed, the
proponents will decide if the change
will be approved or declined.
69
If
the
change
is
being
and
discrepancies
are
documenting
of
all
that
happened.
3.2.2.1.2
Identify change
Once change is identified, all
members/ proponents of the group
will be informed for the proposed
change to the system development.
Control change
Evaluation of the change is
being planned by the proponents if it
will be implemented or not. If granted,
it will be implemented. If not, it will be
declined.
70
3.2.2.2
CONFIGURATION CONTROL
3.2.2.2.1
Description
Changes
will
be
and
automated
Request change.
Lead
Programmer
will
necessary
change
4.
Apply SQA activities
5.
Check in items
6.
Apply testing activities
71
7.
8.
3.2.2.3
VERSION CONTROL
3.2.2.3.1
Description
As a result of changes,
the version number of various
modules
will
be
increased
be
using
universal
3.2.2.3.2
it
will
be
72
Bug fix
If
have
enough
been
bug
done
fixes
on
the
is
increased.
The
will
be
added
to
work,
the
number
minor
may
be
increase
the
version
number.
Major Update
Major update will be
done if the proposed module
will
be
upgraded
and
73
Documentation
Document control will
be made for the development
of the proposed module and
document there all of version
revisions.
3.2.2.4
(CSA)
Configuration
Status
Accounting
informed
from
changes
that
may
concern.
3.2.2.4.1
Description
Describes on how the
Configuration
Status
74
to
communicate
verbally.
Online Help Desk
This will be used by the
client
to
changes
request
in
the
some
developed
together
with
the
with
end-
users/
emails.
The
and
take
further
actions.
Social Networking Site
This tool is commonly
used to communicate online.
The client may announce the
changes
Also,
the
or
enhancements.
developers
can
75
Work
products
and
documentation
Verbal suggestions
Notes
of
end-
users
suggestions
Documentation of test
76
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
representation of software;
2.
To verify that the software under review meets its requirements;
3.
To ensure that the software has been represented according to
predefined standards;
4.
To achieve software that is developed in a uniform matter;
5.
To make projects more manageable.
3.2.3.1
Management Responsibility
Quality System
Contract Review
Design Control
Document and Data Control
Purchasing
Control of Customer Supplied Product
77
CONDUCTION A REVIEW
There are two kinds of reviews, review case with the enduser and review case with other proponents.
For the changes that will affect the end user when they
use the system, the proponents must consult the end- users first.
But first, every proponents of the group must have agreed with
the change and must have a good record of the project before
and after changes.
78
Project
M anager
D ocum ent
S pecialist
B usiness
A nalyst
Lead
Program
m er
S ystem
A nalyst
3.2.3.2
79
RMMM Review
RMMM is use to prevent, monitor and manage
the risk.
requirements
stated
the
data
requirement, specification.
80
Interface (GUI)
Up on the request of the client, the proponents
will design the interface from the previous version.
Code Review
Errors, bugs, glitches that were found will be
reviewed according to the codes being applied to fix
encountered problems.
81
3.2.3.2.2
3.2.3.2.3
RMMM REVIEW
RMMM,
Risk
Mitigation,
Monitoring
&
SPECIFICATIONS)
Software Requirements stated the data
requirement and specifications.
3.2.3.2.5
82
3.2.3.2.7
INTERFACE (GUI)
Interface is the design of the proposed
module and known as front- end of the system.
3.2.3.2.8
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
3.2.3.2.11
3.2.3.3
SQA AUDITS
83
performance for the past week. Any problems, questions regardless on the
performance of the proponents will be noted.
Members will write part of the help menu that related to their
design parts.
Any changes that will be done to the project making must inform
the co- proponents and their adviser before implementing the changes
throughout the process of the system
3.2.3.4
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 follow- up.
3.2.3.4.1
REPORTING MECHANISMS
In reporting mechanisms, the system will
give the reports of sales to the integrating system.
After every transaction and at the end of the day,
sales reports will automatically produce.
3.2.3.4.2
RESPONSIBILITIES
Below are listed the proponents name
corresponds with the position
84
Project
M anager
D ocum ent
S pecialist
B usiness
A nalyst
Lead
Program
m er
System
Analyst
3.2.3.4.3
properly
conduct
software
quality
proponents
conducted
researches,
3.3
85
and
the
changes made to it
All changes made while doing the proposed
86
3.3.1.2
are
listed
the
proponents
name
87
Project
M anager
D ocum ent
Specialist
Business
Analyst
Lead
Program
m er
S ystem
A nalyst
88
3.3.2.1
Task Overview
The tasks stated above will cover the quality
control of the project, the design that will be use
conforming on the implemented design of the system, the
time and cost for the project, minimizing the errors that
the connected modules will encounter, problem tracking
and data flow.
3.3.2.2
the
SQA Resources
89
module
To verify that the proposed module meets its requirements
To ensure that the proposed module meet the predefined
standards.
To achieve software that is developed in a uniform manner
Conducting a Review
The
proponents
will
be
having
reviews
in
90
3.3.3.1.2
are
listed
the
proponents
name
3.3.3.1.3
3.3.3.1.4
91
RMMM Review
RMMM is use to prevent, monitor and manage
the risk.
requirements
stated
the
data
requirement, specification.
92
Interface (GUI)
Up on the request of the client, the proponents
will design the interface from the previous version.
Code Review
Errors, bugs, glitches that were found will be
reviewed according to the codes being applied to fix
encountered problems.
3.3.3.1.5
SQA Audits
a.
93
b.
Reporting Mechanisms
It shows information about the procedure in producing
reports about quality assurance. The proponents shall make
sales, terminal and price reports.
3.3.4.2
Responsibilities
Below are listed the proponents name corresponds
with the position
94
3.3.4.3
3.3.4.4
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:
Using the Pareto principle (80% of the defects can be traced to 20% of
Once the vital few causes have been identified, move to correct the
Product
Point- of- Sales with Price Management Module
95
Business
Conditions
Customer
Characteristics
Process
People
3.3.5.1
Development
Environment
Technology
Field
Logic
%
Reason
3 None of the member has any experience on doing a project in this
0 size, or the experience on the project in this degree of difficulties.
96
Interface
Data
Handlin
g
Error
Checkin
g
2
5
1
5
1
0
HW /
SW
1
0
Standar
d
1
0
Table No 3.3
Up on the request of the client, the proponents will design the interface
from the previous version.
This project involved a lot of data accessing / storing, data flow
between each interfaces. It's not easy to keep track of them. And the
queries that the database used are pretty much outdated.
Since the member have a very close contact with the client, and have
done an exceptional work on research and study the old version, the
member can keep the field under 10%.
The proponents will also do integration and help desk for a period of
time. And do some database re-engineering for the clients database to
make it more efficient and suit for project need.
Since the member has no experience on such degree of project, so
other errors might be uncover, but the member must be optimist since
they did a pretty good research on the project, and spent many times
on designing phase before any actual coding.
Errors that must expect on this project.
3.3.5.2
are
listed
the
proponents
name
97
responsibilities,
procedures,
processes
and
resources
for
3.4
SYSTEM SPECIFICATIONS
3.4.1 INTRODUCTION
98
99
Security of information
To secure all the information including the records
of transactions, receipts of customers and sales of the
company pertaining to the point- of- sale by putting
security features to the proposed module.
100
updated
rapidly,
discrepancies.
Improve
accurately
pricing
and
will
accuracy,
avoid
identify
101
3.4.1.2
General Requirements
102
Interface
The proposed module will be
a user-friendly interface.
2.
Database
The proposed module shall
have a database so that data could
have a proper storage.
3.
Training
The users of the proposed
module shall have proper training
before using it.
4.
Mobile Apps
The proposed module will be
having a mobile application.
5.
can
modify
the
system
accordingly.
6.
Personalized Screen
Personalized
screens
Import Export
103
Analytical Reports
Reports
will
be
produced
SYSTEM CONTEXT
User-friendly
interface
for
an
business
intelligence
of
the
proposed module.
3.4.1.4
MAJOR CONSTRAINTS
The proponents specified the
constraints of the system in terms of
design
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
104
DATA DESCRIPTION
3.4.2.1
105
106
107
Invoice/Report
Sales Report
Terminal Report
Product Price Report
Proof List Report
Utilities
Configuration
Logout
Description for Components:
Checkout Supervisor
Cashier
Cashier Supervisor
Management
Pos and Price Management are different and theyre
individual systems.
Pos and Price Management have different users.
108
109
Login Screen
Main Menu
Record Purchased Product
Payment
Price Tagging
3.4.4.4 Interface Design Rules
Provide rules for the interface design of the system
1. Strive for consistency
2. Enable frequent users to use shortcuts
3. Offer informative feedback
4. Design dialog to yield closure
5. Offer simple error handling
6. Permit easy reversal of actions
7. Support internal locus of control
8. Reduce short-term memory load
3.4.4.5 Components Available
Below are the components that will be used in the
interface of the proposed module.
1. Basic Controls
2. Interactive Displays of Highly Formatted Information
3. Un-editable Information Display
4. General-Purpose Containers
110
5. Special-Purpose Containers
3.4.4.6 Intrinsic Controls
Below are the intrinsic controls that will be
used in the interface of the proposed module:
Text Box
Label
Line
Image
List Box
Scrollbars
Command Button
Menu
Combo Box
Check Box
Option Button
3.4.4.7 Active XControls
Below listed are the activeX controls that will be
used in the interface of the proposed module.
Data Repeater
Date Time Picker
MS Flex Grid
Tree View
Status Bar
Tool Bar
Common Dialog
the
Restriction,
Limitations,
and
System
Cashier can only Record Purchased Product and
Payment, Also to Issue Invoice/Receipt
111
112
3.5
company.
The proponents aim to create a system
where any merchandising companies can cope on with it
system.
The proponents aim to create a system
where it can pass and collect data with other connected
systems.
113
3.5.1.2
proposed
module
shall
record
Record Payment
The
proposed
module
shall
record
certificates.
Print Invoice/ Receipt, Reports and Price Tags
The proposed module shall print invoice/
receipt depending on the type of payment given by
a customer during transactions, daily Sales and
Terminal Reports and also Price Tags.
Price Tagging
The proposed module shall be able to
apply price and discounts on products.
3.5.1.2.1
General Requirements
The following general requirements
were laid out for the proposed module
named
Point
of
Sales
with
Price
Management Module:
System Functionality
The proposed module shall be 100%
at its full functionality means all of its
114
Interface
Interface is important in every system
because it guides the user according to
the functionalities the system have. It is
on
android
be
operating
system.
Free Format Query
The system can be flexible to its user.
Personalized Screen
Screens intended for a specific user
of the system.
Import Export
The system has a functionality where
database can be imported and also
exported.
Analytical Reports
Reports were made according to the
purpose and scopes of the system.
115
3.5.1.2.2
Extended Enhancement
Mobile App
The proponents will add an android
mobile application for the price viewing and
purchasing of products.
3.5.1.3
SYSTEM CONTEXT
When
the
system
is
already
implemented,
all
in
counting
sales,
products
cannot
116
be
3.5.1.4
MAJOR CONSTRAINTS
Time
The proponents only have limited time in doing the
project because of other matters. The proponents will
have to do a double time to fulfill the documentation.
Funding
Funds needed in hardware used in the proposed
module are a major constraint. The proponents would
want to ask help with the other groups in attaining these
needed hardwares.
Integration
Integration is important because the proposed
module cant have data without connecting with other
modules.
Developing Environment
Developing Environment is a high constraint
because it can affect the project that is being made,
whether it may become successful or a failure.
Compatibility
Compatibility is also important so hardwares and
softwares being used must be properly checked to
observe its compatibility if it fits with other units to avoid
problems.
USER- PROFILES
117
3.5.2.2
Checkout
Override)
Cashier (Transaction)
Price Clerk (Price Management)
Customer (Purchasing of Products)
Administrator (Full Accessibility of the system)
Supervisor
(POS
transaction,
System
USE- CASES
The following are the use cases of the proposed
Point- of- Sales with Price Management Module.
1. Login to the system
2. Record Purchased Product
3. Record Payment
4. Record Price Tagging
5. Generate Invoice/Receipt
6. Logout from system
3.5.2.3
118
3.5.2.4
3.5.2.5
3.5.2.6
Activity Diagrams
1. Login to the system
2. Record Purchased Product
3. Record Payment
4. Record Price Tagging
5. Generate Invoice/Receipt
6. Logout from system
119
Trans_No
unique
number
assigned
for
Transaction Number
Prod_BarCode
A
unique
number
assigned
for
Product Barcode
Punch_Prod_Qty A number
assigned
for
Product
Quantity
Purch_amount
amount
Time_Scan
Scanned Time
Barcodes
Return_Qty
return items
Return_Date
Remarks
Transactions
Terminal_ID
every Terminals
Emp_ID
every Employee
Trans_Date_Time Transaction Date and Time
Items_purchased Items that were purchased
Total_Amt
Total amount of transactions
Point- of- Sales with Price Management Module
120
Payment_type
types
Trans_Desc
transactions
Customer_name
unique
unique
identification
identification
for
given
to
customer
transactions
Mem_ID
members
Earned_Pts
Points earned
transactions
GC_No
Certificates
GC_Amt
GC_Exp
GC_Total_Amt
121
Trans_No
transactions
Total_Amt
Change
transactions
Card_No
card number
Card_Name
Card_BankName
Card_Pin
Card_Desc
Name of card
Name of Bank
Pin number of card
Description of card
transactions
Prod_Barcode
Barcodes
Item_qty
Quantity of items
VoidItem_Description
Description of void item
members
Mem_Lname
Mem_Fname
122
Mem_Mname
Mem_Age
Mem_Gender
Mem_Bday
Mem_Add
Date_Reg
Earned_Pts
transactions
Mem_ID
Gained_Pts
Price Management:
PM_Tag Data Object
Tag_Code
Code assigned for tags
Color_Code
Code assigned for colors
Promo_Discount Discounts for promos
Promo_Disc_Type
Type of discount
PM_Price_List Data Object
Price_Code
Code assigned for price
Prod_Code
Code assigned for products
Tag_Code
Code assigned for tags
P_vat
Price vat
P_price
Price
P_date_issue
Date where price issued
3.5.3.2
Relationships
The cashier makes up the transaction process by
getting the information of products and money tendered.
The cashier supervisor shall manage the restricted
features of pos that cashiers cannot access because of
security purposes.
123
The
price
clerk
shall
manage
the
price
Verify Password
(No)
Incorrect Password
(Yes)
Access Granted
124
3.5.4.1.1
Add price
(No)
(Yes)
Save Product
125
3.5.4.1.2
(No)
(Yes)
Edit record
Save record
126
3.5.4.1.3
Display Information
3.5.4.1.4
127
(No)
(Yes)
Sales Report
Display Report
View Report
(No)
(Yes)
Print Report
128
3.5.4.1.5
Log in to system
(No)
(Yes)
Select Thermal
3.5.4.1.6
129
3.5.4.2
HUMAN INTERFACE
Cashier
The
cashier
can
only manipulate
the
Merchandising System
2.
130
131
4. System should have windows dialog for warning, errors, success and
conformation for the users awareness in the system.
5. The system should follow the standards that have been approved by
the Merchandising System and by the client
6. The data that have been inputted in the system should be stored in
the database.
7. System interface should be organized and easily understandable by
the users of the system.
8. The system should be well integrated to the other module or system.
132
3.6
133
sources
Free reporting facility (user has the option what to
display)
134
Security of information
To secure all the information including the
records of transactions, receipts of customers and
sales of the company pertaining to the point- ofsale by putting security features to the proposed
module.
create
system
where
price
135
proponents
will
include
proper
in
136
General Requirements
The following general requirements
were laid out for the proposed Point of Sales
with Price Management System:
the
cashiers
and
checkout
137
3.6.1.3
SYSTEM CONTEXT
138
If
the
proposed
module
successfully
be
MAJOR CONSTRAINTS
Time
The proponents only have limited time in doing the
project because of other matters. The proponents will
have to do a double time to fulfill the documentation.
Funding
Funds needed in hardware used in the proposed
module are a major constraint. The proponents would
want to ask help with the other groups in attaining these
needed hardwares.
Database Description
Below are mentioned all tables, their corresponding
attributes and a small description of each.
POS:
Table Name: POS_Terminals
Attributes: Terminal_ID, Counter_No, Terminal_Desc
Description: Table used for assigning terminal
Table Name: POS_Purchased_Product
Attributes: Trans_No, Prod_BarCode, Purch_Prod_Qty,
Purch_amount, Time _Scan
Description: Table used for Purchased Products
Table Name: POS_Return
139
Attributes: Return_No,
Trans_No,
Prod_BarCode,
Emp_ID,
Items_Purchased,
Total_Amt,
Payment_type, Trans_Desc
Description: Table used for transactions
Table Name: POS_Pending
Attributes: Trans_No, Customer_name
Description: Table used for pending transactions
Table Name: POS_Mem
Attributes: Mem_ID,
Mem_Lname,
Mem_Fname,
Item_Qty,
VoidItem Description
Description: Table used for void items
Table Name: POS_Card_Transaction
Attributes: Trans_No,
Card_No,
Card_Name,
GC_No,
GC_Amt,
GC_Exp,
GC_Total_Amt
Description: Table used for Gift Check
Point- of- Sales with Price Management Module
140
Price Management:
Table Name: PM_Tag
Attributes: Tag_Code, Color_Code, Promo_Discount,
Promo_Disc_Type
Description: Table used for Tags
Table Name: PM_Price_Lists
Attributes: Price_Code, Prod_Code, Tag_Code, P_vat,
P_price, P_date_issue
Description: Table used for Price Lists
Price Clerk
Java
Netbeans
Point- of- Sales with Price Management Module
MS
SQL
141
3.6.3.1
Program Structure
3.6.3.1.1
Overall
Main Screen
System
Setup
Transaction
Query
Report
Utility
Menu Items:
The following shows the architecture of the main menu:
System Setup
Tags
Promo Type
Transaction
Product Pricing
Product Promotion
Tag Printing
F1- Re- Print Receipt
F2 Payment
F3 Modes of Payment
F4 Customer Card
142
List of Promos
Report
Sales Report
Terminal Report
Audit Trail
Configuration
Log- out
3.6.3.2
3.6.3.3
143
144
145
146
147
148
149
Login Screens
3.6.3.3.1.2 Objects and Actions
Menu Items
3.6.3.3.2
the
usability
of
an
150
Consistent
sequences
of
identical
terminology
should
be
employed
throughout.
2. Enable frequent users to use shortcuts
As
the
frequency
of
use
should
be
some
system
for
infrequent
and
major
feedback
at
the
151
error
and
comprehensible
offer
simple,
mechanisms
for
undone,
it
thus
encourages
operators
152
The
limitation
of
human
consolidated,
windows-motion
and
sequences
of
actions.
3.6.3.3.3
Components Available
Java
has
many
components
153
3.6.3.5
Testing Issues
3.6.3.5.1
Classes of Test
Test strategy and preliminary test
case specification are presented in this
section. The various tests to be conducted
are the following:
Login The first class of test is login which
will be done by authorized person for the
security and safety of all the records inside
the system. To access the system, the
specified user needs to enter the username
and password. The user cannot login with
incorrect username and password and error
message will be shown. Log in will be
observed when the integrated module which
is HR give the log- in screen to every
module.
Database connection This test class is
defined if the assigned database connection
has been successfully connected to the
database server.
Test System Configuration This test
class is used to test tags and promo types.
Test Transaction This test class is used
during POS. the process of transactions
worked properly if all of its functionalities are
applied and all working. Also, it tests product
pricing, product promotion and tag printing.
154
Performance Bounds
The proponents have setup certain
bounds or criteria for the proposed module
so that by following that criteria will be able
to maintain quality and user friendliness of
the proposed module
Response time of search function
Best Case Scenario -> Immediate
Worst Case Scenario -> Fail to create
transactions
Response time of browse function
Completing a transaction When the
cashier
successfully
completed
transaction.
Done with a short period of time depends on
the items being scanned.
User should be able to log on within 0.1
second
3.6.3.5.3
155
156