Understanding and Enhancing Programming Profitability.


76 views
Uploaded on:
Category: Business / Finance
Description
Understanding and Enhancing Programming Profitability. Walt Scacchi Establishment for Programming Research College of California, Irvine Irvine, CA 92697-3425 USA www.ics.uci.edu/~wscacchi 16 February 2005. Presentation. What influences programming profitability?
Transcripts
Slide 1

Understanding and Improving Software Productivity Walt Scacchi Institute for Software Research University of California, Irvine Irvine, CA 92697-3425 USA www.ics.uci.edu/~wscacchi 16 February 2005

Slide 2

Introduction What influences programming profitability? Programming profitability has been a standout amongst the most examined parts of programming designing Goal: audit test of experimental investigations of programming efficiency for expansive scale programming frameworks from the 1970\'s through the mid 2000\'s. How would we enhance programming efficiency? Thinking back (history) Looking forward (future)

Slide 3

Understanding and enhancing programming efficiency: Historic perspective

Slide 4

Preview of discoveries Most programming profitability studies are insufficient and misdirecting. How and what you measure decides the amount of profitability you see. Little scale programming efficiency has more than a request of extent variety crosswise over people and dialects We discover opposing discoveries and rehashed weaknesses in profitability estimation and information examination, among the couple of chunks of enhanced comprehension.

Slide 5

Basic programming efficiency issue What to quantify? Efficiency is typically communicated as a proportion Outputs/Inputs This expect we know what the units of yield and info are This accept that both are persistent and direct (like “real numbers”, not care for “weather temperatures”)

Slide 6

Software profitability predicament We try to comprehend what influences and how to enhance programming efficiency Measurement is a mission for sureness and control What part does estimation take in serving to enhance programming profitability? Estimation relies on upon instrumentation, so the relationship must be clear. Instrumentation decisions lead to exchange offs.

Slide 7

Measurement-instrumentation exchange offs Who/what ought to perform estimation? What sorts of estimations to utilize? How to perform the estimations? How to present results to minimize twisting? Most programming efficiency studies expect proportion estimation information is favored. On the other hand, ostensible, ordinal, or interim measures may be exceptionally helpful. Consequently, what sorts of measures are most suitable for comprehension programming profitability?

Slide 8

Why measure programming profitability? Build programming generation profitability or quality Develop more significant items for lower expenses Rationalize higher money to-staff speculations Streamline or scale back programming creation operations Identify creation bottlenecks or underutilized assets But exchange offs exist among these!

Slide 9

Who ought to quantify programming profitability? Software engineer self-report Project or group chief Outside experts or eyewitnesses Automated execution screens Trade-offs exist among these

Slide 10

What to quantify? Programming items Software generation procedures and structures Software creation setting

Slide 11

Software items Delivered source proclamations, capacity focuses, and reused/outer segments Software improvement investigations Documents and relics Application-area information Acquired programming advancement aptitudes with item or product offering

Slide 12

Software creation forms Requirements examination : recurrence and conveyance of prerequisites changes, and other instability measures. Determination : number and interconnection of computational items, properties, relations, and operations in target framework, and their instability. Engineering outline : plan many-sided quality; the structural planning\'s instability arrangement, rendition space, and configuration group creation; proportion of new to reused design parts. Unit plan : outline exertion; number of potential configuration imperfections distinguished and evacuated before coding. Coding : push to code outlined modules; proportion of irregularities found between module configuration and usage by coders. Testing : proportion of exertion allotted to spent on module, subsystem, or framework testing; thickness of known mistake sorts; degree of computerized components utilized to produce experiment information and assess experiment results.

Slide 13

Software generation setting Programming language(s) Application sort Computing stages Disparity in the middle of host and target stages Software improvement environment Personnel ability base Dependence on outside associations Extent of customer or end-client cooperation Frequency and history of mid-task stage overhauls Frequency and history of troublesome inconsistencies and oversights in earlier activities

Slide 14

Findings from programming profitability concentrates More than 30 experimental investigations of programming efficiency have been distributed Aerospace, information transfers, protection, keeping money, IT, and others Company examines, research facility thinks about, industry studies, field considers, global studies, and others A little specimen of studies ITT Advanced Technology Center (1984) USC System Factory (1990) IT and Productivity (1995)

Slide 15

ITT Advanced Technology Center Systematic information on programming profitability, quality, and expense was gathered from 44 ventures in 17 corporate backups in 9 nations, representing 2.3M LOC and 1500 man years of exertion. Discovering: item - related and process - related elements represent give or take the same sum (~33%) of profitability change. Discovering: you can recognize profitability figures that can be controlled (procedure related) from those that can\'t (item related).

Slide 16

Process - related components (all the more effortlessly controlled) stay away from equipment programming co-advancement improvement PC size (greater is better) Stable necessities and determination utilization of "modern programming practices” allot experienced work force to group Product - related elements (not effectively controlled) registering asset limitations (less is better) program many-sided quality (less is better) client cooperation (less is better) size of project item (littler is better) ITT profitability variables

Slide 17

USC System Factory Examined the impact of collaboration in creating both formal and casual programming details. Finding: watched variety in efficiency and determination quality could be best clarified as far as repeating cooperation structures. Six cooperation structures (examples of collaboration) were seen crosswise over five groups; groups as often as possible moved starting with one structure then onto the next. High efficiency and high item quality results could be followed back to recognizable examples of cooperation. Cooperation structures, cohesiveness, and moving examples of collaboration are remarkable profitability variables. See S. Bendifallah and W. Scacchi, Work Structures and Shifts: An Empirical Analysis of Software Specification Teamwork , Proc. eleventh. Assistant. Conf. Programming Engineering , Pittsburgh, PA, IEEE Computer Society, 260-270, May 1989.

Slide 19

IT and Productivity IT is characterized to incorporate programming frameworks for exchange handling, vital data frameworks, and different applications. Looks at studies drawn from various monetary segments in the US economy. Finding: obvious "productivity paradox" in the improvement and utilization of IT is because of: Mismeasurement of inputs and yields. Slacks because of adjustment and expectation to learn and adapt impacts. Redistribution of additions or benefits. Fumble of IT inside mechanical associations. Therefore, one critical reason for our powerlessness to comprehend programming efficiency is found in mismeasurement.

Slide 20

Summary: Software Productivity Drivers What influences programming efficiency? Programming advancement environment traits Software framework item qualities Project staff characteristics

Slide 21

Software advancement environment properties Provide generous (and quick!) registering asset foundation Use contemporary SE devices and strategies Employ improvement helps that help venture coordination Use "appropriate" (space particular) programming dialects Employ procedure focus advancement situations

Slide 22

Software framework item ascribes Develop little to-medium many-sided quality frameworks Reuse programming that as of now addresses the issue No ongoing or circulated programming to create Minimal imperatives for acceptance of precision, security, and simplicity of adjustment Stable necessities and details Short undertaking calendars to maintain a strategic distance from slippages

Slide 23

Project staff qualities Small, all around sorted out task groups Experienced advancement staff People who gather their own particular efficiency information Shifting examples of collaboration structures

Slide 24

How to enhance programming profitability (in this way) Get the best from all around oversaw individuals. Make improvement steps more productive and more compelling. Streamline, crumple, or dispose of advancement steps. Wipe out revamp. Manufacture less difficult items or item families. Reuse demonstrated items, procedures, and creation settings.

Slide 25

Summary of programming profitability estimation difficulties Understanding programming efficiency obliges a huge, complex arrangement of subjective and quantitative information from numerous sources. The number and differing qualities of variables show that product efficiency can\'t be seen just as a proportion source code/capacity focuses created per unit of time/spending plan. A more orderly comprehension of interrelationships, causality, and systemic outcomes is needed. We require a more powerful hypothetical structure, systematic strategy, and bolster devices to address these difficulties

Slide 26

Understanding and enhancing programming efficiency: Future perspective

Slide 27

An information administration way to deal with programming building Develop setting-particular speculations of programming creation Identify and develop neighborhood programming profitability drivers Develop learning based frameworks that model, mimic, re-establish, and overhaul programming advancement and use procedures Develop, convey, utilization, and persistently enhance a PC upheld agreeable authoritative learning environment

Recommended
View more...