Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
A Problem Description
A POS (Point-Of-Sale) system is a computer system typically used to manage the sales in retail
stores. It includes hardware components such as a computer, a bar code scanner, a printer and
also software to manage the operation of the store.
The most basic function of a POS system is to handle sales. When a customer arrives at a POS
counter with goods to purchase, the cashier will start a new sale transaction. When the barcode of
a good is read by the POS system, it will retrieve the name and price of this good from the
backend catalog system and interact with inventory system to deduce the stock amount of this
good.
When the sale transaction is over, the customer can pay in cash, credit card or even check. After
the payment is successful, a receipt will be printed. Note that for promotion, the store frequently
issue gift coupons. The customer can use the coupons for a better price when purchasing goods.
Another function of a POS system is to handle returns. [The details of which are not given
here]
A user must log in to use the POS. The users of a POS system are the employees of the store
including cashiers and the administrator. The administrator can access the system management
functions of the POS system including user management and security configuration that cashiers
cant do.
For the POS system mentioned above, identify the FP.
Consider the organization average productivity is 6.5 FP/p-m (person-month) and
Burdened Labor rate = 8000 $/p-m a. Estimate the effort for the POS system.
Estimate the cost for developing the POS system.
Measurement Parameter
Number of user inputs
Count
6
Weight Factor
Low: 4 * 3 = 12
Average: 1 * 4 = 4
High: 1 * 6 = 6
Low: 2 * 4 = 8
Low: 1 * 3 = 3
Low: 2 * 7 = 14
Low: 2 * 5 = 10
2
1
2
2
Total
Complexity Adjustment Factor
Function Points
AFPC
=
=
=
=
=
=
Total
22
8
3
14
10
57
1.08
62
Estimated Efforts
Cost per FP
Project Cost
62/6.5
9.54 p-m
10 p-m
8000/6.5
1231 $/FP
8000 * 10
$ 80000
Complexity Factor
Fi
Backup and recovery
Data communication
Distributed processing
functions
Is performance
critical?
Existing operating
environment
On-line data entry
Input transaction built
over multiple screen
Master files updated
on-line
Complexity of inputs,
outputs, files, inquires
Complexity
of
processing
Code design for re-use
Are
conversion/installation
included in design?
Multiple installations
Application designed
to facilitate change by
the user
5
4
0
1
1
2
4
1
1
3
0
1
1
Total
4
0
43
User inputs
Login: simple
User outputs
Inventory
deduction:
simple
Coupon: simple
User Inquires
Print Receipt:
simple
Files
Inventory:
simple
User: simple
External
Interfaces
Bar code:
simple
Card Reader:
simple
No of Elements
2
1
1
Total
Weight
1
2
2
Productivity:
high
25
Reused:
1 15/100
85% of 6
5.1
0.2 p.m
Person-Month:
5/25
Total
2
2
2
6
Q3. For a given use case model of an ATM system (Withdraw functionality) given in the below
link:
http://www.cs.fsu.edu/~baker/swe1/restricted/templates/rr631gv1_stuwrk_withdraw_cash_usecase_spec.pdf
Compute the estimated effort PM Person-months needed to develop the system, assuming the
productivity of the team is 20 UCP/p-m
Using Use case point (UCP) based estimation.
Using use case size point based estimation.
Use Case Points:
Actor
Simple
Average
Complex
Count
0
1
3
Total
=
=
=
=
=
Type: Complex
11 + 15
0.6 + (0.01*7)
1.4 + (-0.03*2.5)
26*0.67*(1.325)
23*20
Technical Factor
Distributed System
Response or
throughput
performance objective
End user efficiency
Complex internal
processing
Code must be reusable
Easy to install
Easy to use
Portable
Easy to change
Concurrent
Includes special
security features
Provide direct access
to third parties
Special user training
facilities are required
Weight
1
2
3
=
=
=
=
=
Total
0
2
9
11
Weight: 15
26
0.67
1.325
23.0815
461.63
=
=
23
462
Count
1
1
Weight
2
1
Total
2
1
0
1
1
1
0
1
0
1
1
0
0
1
1
1
0.5
0.5
2
1
1
1
0
0.5
0.5
0
0
1
1
Total
7
3
Environmental
factor
Familiar with RUP
Application
Experience
Object Oriented
Experience
Lead Analyst
capability
Motivation
Stable requirements
Part time workers
Difficult
Programming
language
Count
Weight
Total
0
1
1.5
0.5
0
0.5
0.5
0
1
0
0
1
2
-1
-1
0
2
0
0
Total
2.5
Simple
Simple
Simple
Simple
Total Weight
2
2
2
2
8
Pre-condition:
Complex
Post-condition:
Average
Main Scenario
Simple
Alternate Scenario
Very complex
Exception
Simple
Unadjusted Use Case Point (UUCP)
3
2
6
20
1
40
FTA
1.07
FAA
0.01 * 4
0.04
40 * (1.07 0.04)
41.02
41
Technical Factor
Data communication
Distributed Processing
Performance
Equipment utilization
Transaction Capacity
On-line input of data
User efficiency
On-line update
Code reuse
Complex processing
Easiness of deploy
Easiness operation
Many places
Facility to change
Environmental
factor
Formal development
process existence
Experience with the
application being
developed
Experience of the
team with the used
technologies
Presence on an
experienced analyst
Stable requirements
Count
1
1
1
1
1
1
1
1
0
1
0
1
1
0
Total
Weight
4
4
5
3
4
4
2
5
0
5
0
3
3
0
Total
4
4
5
3
4
4
2
5
0
5
0
3
3
0
42
Count
Weight
Total
1
Total
4
4
Q4. Can Function Points be mapped to Object Points? Explain and justify, why or why not?
Yes, because factors used in object points are present in function points also.
Q5. Develop a detailed Gantt chart for your project (IT-632: SEN). Each team member of a
group is expected to choose a different functionality to develop the Gantt chart.