software measurement - opportunities and challenges … chemuturi_… · software measurement -...

https://isma13in.wordpress.com

Software Measurement -Opportunities and Challenges

The Joint 13th CSI/IFPUG International Software Measurement & Analysis (ISMA13) Conference

Mumbai (India) – March 6, 2017

Murali Chemuturi, Chemuturi Consultants

Insert here a picture

[

http://www.ifpug.org/

http://www.csi-india.org/


https://isma13in.wordpress.com/

http://www.csimumbai.org/

2ISMA 13 – March 6, 2017 https://isma13in.wordpress.com

Software Measurement -

Opportunities and Challenges

Goals of the presentation

G1. To put the term “measurement” in perspective

G2. Take stock of the current scenario in softwaremeasurement

G3. To explore the opportunities and challenges insoftware measurement




Come together, let us

Stay together, let us

Strive together, let us

Shine together, let us

Banish ill will, let us

- Rigveda

Software Measurement - Opportunities and Challenges




Measurement

Act of measuring some thing

We used to ay, “If we cannot measure, we cannot manage it” but, now, if we can measure it, we automate it!

Needs a unit of measure

Needs a repeatable process that can be performed by anyone with in an acceptable margin of error

Easily accomplished in tangible things like height, weight, length

Is everything measurable?





Measurement – can we measure these?

Love?

Complexity?

Quality?

Beauty?

Enjoyment/entertainment?

Creativity?

Ability?





Measurement - Software Measurement

Measurement basically deals with the “quantity” or “how much” of an entity

In software measurement we have two attributes to measure

Quantity

Quality





Software Measurement – why?

Quantity measurement of software is needed for

Agreeing on the price/cost of software being acquired

To determine the amount effort to be spent by people of different skills

To devise the schedules for various activities leading to delivery, installation and roll out

For cost and schedule control

For recognizing and rewarding the people’s on-the-job performance

For capacity building





Software Measurement – Unit

Customer and management viewpoint

Units of software delivered

Project Management standpoint

Units of software requirements established

Units of software designed

Units of software coded/programmed

Units of software tested






Function Points

IFPUG

UKSMA

NESMA

Boeing

Cosmic

Quick






LOC

Object Points

Feature Points

Internet Points

Use Case Points

Story Points

PSU (Project Sie Unit)

SSU (Software Size Unit)

Story Points





Software Measurement

“Complexity” – what is complexity?

We do not understand it

When there is limited room for maneuvering

When something is new and very few experts are available

When excessive volumes are to be handled

When there are advanced mathematical routines are involved

When the work piece is delicate and is liable to break/damaged if handled carelessly






Test Point

STU (Software Test Unit)





Software Measurement – Challenges Define a unit of measure, that is well defined

How many units?

Requirements

Design

Input Design

Output Design

Database Design

Security Design

Process Design

Coding

Testing

User Documentation and training materials

Training

Define a simple methodology to measure the Quantum of software





Software Measurement – Challenges

We refuse to learn from manufacturing sector

We never heard of disciplines Cost Accounting and Industrial Engineering

Our software artifacts do not have the same level of granularity as engineering drawings

Define a unit of measure, that is well defined

What should be the basis of measuring software quantity

Data

Transactions

Type of application

Artifacts – screens, reports, tables, inputs, outputs, processes, documentation, training materials





Software Measurement – Challenges

Productivity

Delivery rate

Productivity

Capacity

Standard time?

Time taken to accomplish a unit of work by a qualified person after acclimatization, in defined environment, using defined methods at a pace that can be maintained day after day without causing any harmful health effects

The crux is in defining a unit f work





Software Measurement – Opportunities

IFPUG is uniquely positioned

It has a global membership that is large

It has been nurturing the most popular unit of measure for software

CSI has a verrry large membership

CSI is rich

CSI has reach to vast amounts of data to analyze and draw inferences






CSI has access to large professional software development organizations to conduct research

IFPUG has expertise and experience in measuring software

CSI has expertise and experience in developing software






Why research? To dispel/confirm the myths of software development

Using a different programming language to achieve the same functionality takes different amounts of time or the productivity for different programming languages is different

Software development work is completely creative

Software cannot be measured






Which CSI?

Computer Society of India

Construction Specifications Institute of USA





Software Measurement - CSI of USA

1995 Format – still used

Division 01 — General Requirements

Division 02 — Site Construction

Division 03 — Concrete

Division 04 — Masonry

Division 05 — Metals

Division 06 — Wood and Plastics

Division 07 — Thermal and Moisture Protection

Division 08 — Doors and Windows

Division 09 — Finishes

Division 10 — Specialties

Division 11 — Equipment

Division 12 — Furnishings

Division 13 — Special Construction

Division 14 — Conveying Systems

Division 15 — Mechanical

Division 16 — Electrical






These 16 divisions were increased to 50 divisions in 2004

Procurement and Contracting - 1

General Requirements – 1

Facility Construction – 18

Facility Services – 10

Site and Infrastructure – 10

Process Equipment – 10

Total - 50





Software Measurement -

My divisions of software development work

1. Project Initiation 2. Project Planning

3. Requirements Establishment 4. System Design

5. Construction 6. Test Planning

7. Testing 8. Integration

9. Integration Testing 10. System Testing

11. Acceptance Testing 12. Documentation

13. User Training 14. Project Closure

Each has subdivisions






Can we, together, emulate CSI of USA?

IMHO, there is a definite requirement to streamline defining specifications for software

IMHO, IFPUG can become CSI for Software

CSI of India can collaborate with IFPUG






Thank you allMurali Chemuturi

[email protected]




mailto:[email protected]

software measurement - opportunities and challenges … chemuturi_… · software measurement -...

Documents