0
9.3kviews
Explain size oriented software engineering metrics.Find function points for an E-commerce application with the following data,

Number of user Inputs 50 Number of user Outputs 30 Number of user Inquiries 35 Number of user Files 06 Number of External Interfaces 04 Assume suitable complexity adjustment factors and weighting factors.

Mumbai University > Computer Engineering > Sem 6 > Software Engineering

Marks: 10 Marks

Year: Dec 2016

1 Answer
1
162views

Size‐oriented software metrics:

Size‐oriented software metrics are derived by normalizing quality and/or productivity measures by considering the size of the software that has been produced.

There are thousand lines of code (KLOC) which are often chosen as the normalization value

Metrics include

  • Errors per KLOC - Errors per person-month
  • Defects per KLOC - KLOC per person-month
  • Dollars per KLOC - Dollars per page of documentation
  • Pages of documentation per KLOC

This metric is not universally accepted as the best way to measure the software process

The opponents are the one that argue with KLOC measurements

  1. Are dependent on the programming language
  2. Penalize well-designed but short programs
  3. Cannot easily accommodate non-procedural languages
  4. Require a level of detail that may be difficult to achieve

Function - oriented metrics

This metric uses a measure of the functionality delivered by the application as a normalization value

The most widely used metric of this type is the function point:

FP = count total * [0.65 + 0.01 * sum (value adj. factors)]

Example: Given that

  1. Number of user input = 50

  2. Number of user output = 30

  3. Number of user enquiries = 35

  4. Number of files =06

  5. Number if external interfaces = 04

Let’s take complexity adjustment values and weighting factor are average

Sr No. Domain Characteristics Count X Average Value Total
1. No. of user input 50 X 4 200
2. No. of user output 30 X 5 150
3. No. of user enquiries 35 X 4 140
4. No. of files 06 X 10 60
5. No. of external interface 04 X 7 28
. . . . . 578

Software complexity can be computed by answering following questions. These are complexity adjustment values.

  1. Does the system need reliable backup and recovery?
  2. Are data communications required?
  3. Are there distributed processing functions?
  4. Is performance of the system critical?
  5. Will the system run in an existing, heavily utilized operational environment?
  6. Does the system require online data entry?
  7. Does the online data entry require the input transaction to be built over multiple screen or operation?
  8. Are the master file updated online?
  9. Are the input, output, file or inquiries complex?
  10. Is the internal processing complex?
  11. Is the code designed being reusable? Chap 5| Software Design Specification KT280 Solutions 25
  12. Are conversion and installation included in the design?
  13. Is the system design for multiple installation in different organization?
  14. Is the application designed to facilitate change and ease of use by the user?

Function Points (FP)

= Count Total * (0.65 + (0.01 * Sum(Fi)))

= 578 * (0.65 + (0.01 * 42))

= 578 * (0.65 + 0.42)

= 578 * 1.07

= 618.46

Function Point value is 618.46

Please log in to add an answer.