List of components Type Number of Data Elements No.

of business rules
User Login - UI Form 2 2
User Login - BE Program 2 4
Deposit - UI Form 10 5
Deposit - BE Program 10 2
Autoloan payment Interface 2 2
Account monthly statement Report 4
Loan payment history Report 5
My ATM transaction Report 4 2

All software components can be classified under form or backend program or report or interface.
Data elements are the fields or parameters used in the component
Business rules include any if conditions and repetitions on the business logic
File or database operations must be conceptually understood for read or write or update or delete operations

Complexity must be assigned based on the data elements, business rules, file-db operations
We need to get organization baseline statistics to find whether a form or report falls under high or medium or low complexity
Example:
Form Low <= 3 biz rules
Medium 4 to 6 biz rules
High 6 + rules

The hours to complete the form must be used based on design hours + coding hours + testing hours, and not just coding hour
If organizational baseline does not exist, we must conduct an exercise in organization to arrive at these statistics

Risk percentage needs to be worked out with senior management and finance people
Management percentage hours need to be worked out based on the project
Total hours include engineering hours, risk hours and project management hours
 File or DB operations Complexity Hours
Low 2
1 Low 4
Medium 6
2 Medium 6
3 High 16
3 Low 2
4 Medium 3
2 High 4

Total hours 43 A
Risk % 15%
Risk Hours 6.45 B
Management % 10%
Management Hours 4.3 C
Total Hours 53.75 A + B + C

date or delete operations

under high or medium or low complexity

s + testing hours, and not just coding hours.

n to arrive at these statistics