[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> bib
|| [News] || [Research]

Bibliography Retrieval Engine(Beta)

Items in bibliography identified by a string matching MATURITY

Aberdour07
.Open Aberdour07
 Mark Aberdour 
 Achieving Quality in Open Source Software
 IEEE Software Magazine V24n1(Jan/Feb 2007)pp58-64     
 =SURVEY OSS RESEARCH OPEN SOURCE TECHNICAL QUALITY PEOPLE ONION   
 Table 1 compares open and closed source processes.
 Page 62: 3 open source maturity models.
 Good software engineering complements good people structure.
.Close

AikenAllenParkerMattia07
.Open AikenAllenParkerMattia07
 Peter Aiken & M David Allen & Burt Parker & Angela Mattia 
 Measuring Data Managment Practice Maturity: A Community's Self-Assessment
 IEEE Computer Magazine  V40n4(Apr 2007)pp42-50   
 =MODEL +POLL DATA PROCESS MATURITY IMPROVEMENT CMMI 
 Proposes a CMMI-like measure of the maturity of data managment.
 6 process areas: data program coordination, organizational data integration, data stewardship, data development, data support operations, and data asset use.
 The usual 5 levels: 1=initial, 2=repeatable, 3=defined, 4=managed, 5=optimizing.
 Questionaire with 20+ questions used intelephone interviews 2000-2005 with 107 companies.
 Results: most process areas are at the repeatable level.
.Close

Aoyama93
.Open Aoyama93
 Mikio Aoyama (Fujitsu)<mikio@miki.nakahara.fujitsu.co.jp>
 Concurrent-Development Process Model
 IEEE Software Magazine (May 1993)pp48-55
 =EXPERIENCE management maturity non-sequential YAC(Aoyamaetal89) becomes YPL
.Box
 To reduce development cycle (time for a release).
 10^6 lines of code 3 months/cycle.
 Higher risks and so more careful management
 helps expose problems in process
 Requires at least a repeatable process maturity.
 p50: "For the large-scale communication project, therefore, we described the entire development process up to the details of the invidual developer's task, and analysed them. We then restructured a conventional process model to support concurrent development and developped a process-management system"
 p50:"traditional models focus on a single sequence of [...]; concurrent[...] focusses on the concurrent execution of multiple processes"
 Uncovering interactions between parallel requirements+designs by intensive review and inspection + management focus on decoupling requirements
 Interactions between implementations use configuration management. + integration focussed testing
 Special team from teams: define process, manage products, co-ordinate, develop management technique, plan, specify, and develop software-engineering environments and coordinate with research.
.Close.Box
.Close

BaikBoehmSteece02
.Open BaikBoehmSteece02
 Jongmoon Baik & Barry Boehm & Bert M Steece 
 Disaggregating and Calibrating the CASE Tool Variable in COCOMO II
 IEEE Trans Software Engineering  V28n11(Nov 2003)pp1009-1022
 =EMPIRICAL Bayesian STATISTICAL MODEL COST TOOLS COCOMO CMM
 Proposes new rating scales for the quality of a CASE Tool and calibrates them on 15 projects.
 New measures improved model by about 70%.
 New scales: tool coverage(TCOV), Tool integration(TINT), tool maturity/user support(TMAT).
 All 3 new measures are important.
.Close

Bamberger97
.Open Bamberger97
 Judy Bamberger(bamberger@eaglet.rain.com)
 Essence of the Capability Maturity Model
 IEEE Computer magazine V30n8(Jun 1997)p112-114
 =REPORT IMPROVEMENT CMM
.Close

BamfordDeibler93
.Open BamfordDeibler93
 Robert C Bamford & William J Deibler II
 Comparing & contrasting ISO9000 and the SEI capability maturity model
 IEEE Computer magazine v26n10(Oct 1993)pp68-70
.Close

Card93
.Open Card93
 David Card (CSC)<dc@sei.cmu.edu>
 Defect-Causal-Analysis Drives Down Error Rates
 IEEE Software Magazine(July 1993)pp98-99
 SQA DCA
.Box
 DCA has a maturity-pull effect, 1% investment can give a 50% reduction in error rates.  60% action proposals are in method
.Close.Box
.Close

DavisA93b
.Open DavisA93b
 Alan M. Davis
 Software Lemmingineering
 IEEE Software Magazine V10n5(Sep 1993)pp79-81&84;correspondence V11n1 (Jan 1994) pp10+V11n4(Jul 1994)pp110-111+QV DavisA94a&b.
 =ARTICLE METHODS TOOLS FAIL
.Box
Fads and trends and following the crowd:
  Structured
  Object
  Maturity
  C
  Prototyping
  CASE
  Reuse
  Comquats (COMercial off-the-shelf QUAlity sofTware)

Tom Adams letter describes methodology life cycle
  good project with new idea
  idea reduced to a buzz phrase
  complex methodology based on just the buzz phrase
  many seminars
  many books
  Many many failed projects

Richard Wells
 I reuse and am careful in C.
  CASE does not address my problems.
.Close.Box
.Close

Dichter93
.Open Dichter93
 Carl Dichter
 Software Audits
 UNIX Review V11n10(Oct 1993)pp43-49
 =NEWS STANDARDS SQA QUALITY ISO SEI MATURITY
.Box
Introduction to where and what of process assessment and audit
	ISO9000
	SEI CMM
.Close.Box
.Close

FraserVaishnavi97
.Open FraserVaishnavi97
 Martin D Fraser & Vijay K Vaishnavi
 A Formal Specifications Maturity Model
 Commun ACM V40n12(Dec 1997)pp95-103
.Close

HolmbergMathiassen01
.Open HolmbergMathiassen01
 Lena Holmberg & Lars Mathiassen
 Survival Patterns in Fast-Moving Software Organizations
 IEEE Software Magazine V18n6(Nov/Dec 2001)pp51-55
 =HISTORY Linq IMPROVEMENT SPI LinQing Linq-Portal
 consulting vs product development.
 employer driven maturity and professionalism.
 Innovation is not  improvement.
 Improvement gave a good product but there was no market for it! "[...]the market had not evolved as predicted. "     Liquidated!
.Close

IriberriLeroy09 
.Open IriberriLeroy09 
 Alicia Iriberri & Gondy Leroy
 A life-cycle perspective on online community success
 ACM Computing Surveys V41n2(Feb 2009) a11 $CR 1008-0832
 =SURVEY WEB/NET PEOPLE COMMUNITIES MANAGEMENT SOCIOLOGY SOCIAL
 online_community::lifecycle= #(inception(need, vision); Creation(purpose, technology, people); Growth(rules, roles, identity) Maturity(regulations, subgroups, trust, relationships) ); (Inception; Creation; Growth; Death|).
 Death comes from lack of contributions, poor participation, transient membership, not enough quality content, etc..
.Close

JaspanEtAl09
.Open JaspanEtAl09
 Ciera Jaspan & Michael Keeling & Larry Maccherone & Gabriel L. Zenarosa & Mary Shaw 
 Software mythbusters explore formal methods
 IEEE Software Magazine V26n6(Nov/Dec 2009)pp60-63
 =REPORT DISCUSSION EXPERIENCE MYTHS FORMAL METHODS AGILE FSM LOGIC MATHEMATICS
 Reference a list
.See [Hall90]
of seven myths
 Formal methods are richer than in 1990.
 They are now used in requirements to get precision and understanding.  
They are embedded in tools and environments reducing the need for mathematical maturity. 
 They enable communication and evolution and so support agility. 
 An FSM model for understanding lead to better code. 
 Must match the method to the problem cost-effectively.
 Formal methods are being domesticated.   
.Close

JonesC95c
.Open JonesC95c
 Capers Jones(Software Productivity research)
 Gaps in SEI Programs
 Software Development Mag V3n3(Mar 1995)pp41-48
.Box
ADVERT MATURITY
Software Productivity Research(SPR) use mutlichoice questions, rates vs stats, bell-shaped curve.
.Close.Box
.Close

Joos94
.Open Joos94
 Rebecca L Joos
 Software Reuse at Motorola
 IEEE Software Magazine V11n5(Sep 1994)pp42-46
.Box
high initial costs and slow return can make it a tough sell.  Must sell to top and then middle management. Use pilot projects. Collect evidence.

Depends on the maturity of the organisation.
.Close.Box
.Close

Kandt09
.Open Kandt09
 Ronald Kirk Kandt 
 Experiences in Improving flight software development processes
 IEEE Software Magazine V26n3(May/Jun 2009)p58-64
 =EXPERIENCE JPL SPACEFLIGHT CONTROLLERS CMMI IMPROVEMENT MATURITY MODULES SQA  MSAP
 Very little quantitative evidence of benefits of the improvement process.
 Improvements had a wide impact.
.Close

KaramCasselman89
.Open KaramCasselman89
 Gerald M Karam & Ronald S Casselman
 A Cataloging Framework for Software Development Methods
 IEEE Computer Magazine V26n2(Feb 1993)pp34-46
 =SURVEY METHODS SDM
 "SDM authors are not very explicit about how their methods work" vague rules or hidden as an notation.
.Box
comparison method. example of Buhr and OMT
Technical
 lifecycle, domain, philosophy, products & notations, procedure, guidelines & criteria & measures, verification, formallity, maintainable products, reusable products, concurrent ystems, performance engineering, traceabillity, extension/specialization
Useage
 application areas, System Size, automated support, ease o instruction, maturity
Managerial
 organization, integration
.Close.Box
.Close

Keuffel95c
.Open Keuffel95c
 Warren Keuffel
 People-based Processes: a RADical Concept
 Software Development Magazine(Nov 1995)pp31+32+35+36..37 +letter Jan 1996 p13
 =IDEA MATURITY CMM RAD
 SEI.CMM is not the only process
 CMM process does not have to be sequential (but CMM tends to make you think sequentially!)
 RADical::=Plan;Build;Focus.
.Close

Keuffel99c
.Open Keuffel99c
 Warren Keuffel
 When There Are No Second Chances
 Software Development V7n10(Oct 1999)pp21-22
 =EXPERIENCE high RISKS requires high Maturity IMPROVEMENT Ogden Air Logistics Center, 
 TEAM Software Process
.Find TSP
is between 
.Find PSP
and 
.Find CMM
.Close

LeeLitecky97
.Open LeeLitecky97
 Nam-Yong Lee & Charles R Litecky
 An Empirical Study of Software Reuse with Special Attention to Ada
 IEEE Trans Soft Eng V23n9(Sep 1997)pp537-549
 =POLL 500 ADA professionals REUSE factors =ANALYSIS
 R near .8
 note: demographic data may be multimodal
 standards have no sig effect
 size and Ada maturity decreases reuse
 effort and OO increase reuse
.Close

LuqiZhangBerzinsQiao04
.Open LuqiZhangBerzinsQiao04
 Luqi & Lin Zhang & Valdis Berzins  & Ying Qiao
 Documentation driven development complex real-time systems
 IEEE Trans Software Engineering  V30n12(Dec 2004)pp936-952
 =DEMO TOOL CAPS-PC AUTOMATE DOCUMENTATION REQUIREMENTS DESIGN CODE TIMING FSA/STD CARA AGILE STAKEHOLDERS LATTICES METRICS
 DDD ::= "Documentation Driven Development".
 Central dynamic data base with automatic translation between requirements, architecture, and components plus translations and executable prototypes for stakeholders.
 Process management. Risk assessment. metrics: requirements volatility, organization efficiency, product complexity, technology maturity (temperature) , ...
 CARA blood pressure maintenance IV for army stretcher.
.Close

ManzoniPrice03
.Open ManzoniPrice03
 Lisandra V Manzoni & Robert T Price 
 Identifying Extensions Required by RUP (Rational Unified Process) to COmply with CMM(Capability Maturity Model) Levels 2 and 3
 IEEE Trans Software Engineering  V29n2(Feb 2003)pp181-192
 =ANALYSIS RUP UML vs CMM PROCESSES MANAGEMENT
 Gaps in managing resources, planning, and subcontract management.  Makes 2 proposals.
.Close

MargariaSteffen10
.Open MargariaSteffen10
 Tiziana Margaria & Bernhard Steffen
 Simplicity as a driver for agile innovation
 IEEE Computer Magazine V43n6(Jun 2010)90-92
 =HISTORY TECHNOLOGY MATURITY DAIMLER AUTOMOBILE ANALOGY IT KISS STANDARDS COMPONENTS INFRASTRUCTURE PROCESSES
 Bad roads, bespoke technology, no support structure, no standard parts, no standard interface. 
So early cars needed professional chauffeur to repair tires and maintain the engine.
Which limits the market. 
 Cost of updates.  
 Maturity leads to standards and simplicity. 
 Slogan: "IT simply works"
.Close

McConnel00
.Open McConnel00
 Steve McConnell(ed)
 The Best Influences on Software Engineering
 IEEE Software Magazine V17n11(Jan/Feb 2000)pp27-17
 =INTERVIEW+POLL
.Net
 reviews and inspections
.See [Fagan76]
 information hiding
.See [Parnas72b]
 incremental development
 user involvement
 automatic revision control
 development uing the Internet
 programming languages hall of fame: FORTRAN,COBOL, Turbo Pascal, Visual Basic
 capability maturity model for software
 object-oriented progrmming
 component-based development
 metrics and measurement
.Close.Net
.Close

OConnoretal94
.Open OConnoretal94
 James O'Connor & Catherine Mansour & Jerri Turner-Harris & Grady H Campbell Jr
 Reuse in Command-and-Control Systems
 IEEE Software Magazine V11n5(Sep 1994)pp70-79
 =ADVERT METHOD Synthesis object-oriented REUSE DOMAIN
.Box
`"Synthesis" is an approach based on domain-specific reuse, by which an organisation can standardize its perceptions of customers' needs and effective solutions`

 Families of similar systems
 product families
 communication with enginners using reusable products
 pilot

Domain::=Net{ narative: `2 pages`, glossary:dictionary, commonality, variability:assumptions, decisions:models.}.
...
Adaptable requirements components using wordperfect macros.

Conclusions:
.List
 Synthesis has immediate beefits....maturity
 management commitment at all levels
 payoff depends on a substantial commitment of effort
 adopting a discipline engineering process stimulates the adoption of disciplined engineering methods.
.Close.List
.Close.Box
.Close

Oman94
.Open Oman94
 Paul W Oman
 Good and bad news emerges from reliability engineering symposium (report on 4th International Symposium on software Reliability Engineering November 1993 Order #4010 CS Press)
 IEEE Computer Magazine V27n1(Jan 1994)pp97-98
 =REPORT tools statistics quality Shuttle
.Box
p97: models reqire more than descriptive statistics and correlations
Poisson and Wiebull distributions
"Everybody is shipping products with latent faults, because the effort to find and remove faults increases as the number of faults diminishes" - exponentially greater - Wiebull.
"Early defect removal is still the key to cost-effective software development and maintenance"

p99:SQA and metrics people are surviving while programmers (untrained software developers) are seemingly the prime targets for layoffs.

Ted Keller Shuttle project [ cf Billingsetal94]
50% defects found by inspections using failure mode static analysis. Only one in-flight failure has been logged since 1985.  Total number of failures logged in tests flights and simulations was 23 in 1987 version, 3 for current - including minor defets.  rootcause failure analysis - 12..15 year database of fault data.  operational profiles. level 5 maturity.  Takes 2..3 years to climb one level. safety certification based on adherence to process.  Known controlled and repeatable process leads to known quality.

Alfred Aho
"Even good software development practices result in approximately one defect per thousand lines of code".  Problems 25 years old but better management, proces, technology, reusability.  multifacetted view of software quality
Richard DeMillo(QV) research pre-occupied with modeling existing defect data.
Janne Druggan "structural-based test coverage, operational profiles, and criticallity analysis were all used as a matter of course during circuit design and test..."

Formal Methods noticably absent.  Lack of communication.

John Gallager:"The formal specification Languages in use today are not useful to those implementing the software."
.Close.Box
.Close

Paulk01
.Open Paulk01
 Mark C Paulk (SEI)
 Extreme Programming from a CMM Perspective
 IEEE Software Magazine V10n6(Nov/Dec 2001)pp19-26
 =ANALYSIS XP CMM IMPROVEMENT PROCESS
 XP satisfies most maturity Level 2 practices(repeatable) but few level 3(defined) and 4(managed).
.Close

Pfleeger93
.Open Pfleeger93
 Shari Lawrence Pfleeger
 Lessons Learned in Building a Corporate Metrics Program
 IEEE Software Magazine (May 1993)pp67-74
 =EXPERIENCES SADT MATURITY
 Nice set of 4 software processes using SADT showing differences between maturity levels in a software process.
.Close

Phillips96
.Open Phillips96
 Dwayne Phillips(Lagos Nigeria)
 Technocentrism
 IEEE Computer Magazine V29N5(May 1996)pp136(open channel)
 =ESSAY ETHICS
.Box
technocentism::=belief that one's own technical group is superior.
"They are nice worthy people but they just couldn't make it in our group".
Allows:
 not invented here
 dismiss other techs selectively
 ignore reasons for their existance

Causes;
 misdirected praise, immaturity, LOW self-esteem

Consequences:
 pride
 short-term gain and long-term pain or death
 inbreeding, stagnant, ineffective


.Close.Box
.Close

Pitterman00
.Open Pitterman00
 Bill Pitterman
 Telcordia Technologies: The Journey to High Maturity
 IEEE Software Magazine V17n3(Jul/Aug 2000)pp89-96
 =EXPERIENCE 1994-1999 PROCESS IMPROVEMENT QUALITY SQA CMM MANAGEMENT telecommunications
 Mindless bureaucracy is not enough for ISO9001.
Need management & employee motivation & quantitive data.
Field faults down, customer satisfaction up, more shipped on time.
.Close

Reifer03b
.Open Reifer03b
 Donald J Reifer  Is the Software engineering state of the Practice getting closer to the state of the art?
 IEEE Software Magazine V20n6(Nov/Dec 2003)pp78-83 $CR 0501-0049
 =ESSAY COMPARING 25 RESEARCH and  11 CERTIFICATION topics
 Willingness to try new. Need: maturity, evidence of success, good theory, published and accessible rules and knowledge, training and support available, and non-hype success stories.
.Close

SaiedianKuzara95
.Open SaiedianKuzara95
 Hosein Saiedian & Richard Kuzara
 SEI Capability Maturity Model's Impact on Contractors
 IEEE Computer V28n1(Jan 1995)pp16-26
 =EXPERIENCE CMM MATURITY
.Close

SommervilleRansom05
.Open SommervilleRansom05
 Ian Sommerville & Jane Ransom 
 An empirical study of industrial requirements engineering process assessment and improvement
 ACM TOSEM Trans Software Eng & Methodology V14n1(Jan 2005)pp85-117 
 =EXPERIENCE 9 Greek  IMPROVEMENT REQUIREMENTS ENGINEERING MATURITY TOOL IMPRESSION CMM CMMI REAIMS
 3 levels. Initial; repeatable; defined.
 66 good practice guidelines.  36 basic, 21 intermediate, 9 advanced. In 8 areas of requirements engineering. ....
 Scoring. never, discretionary, normal, standardized.
 Others studied business performance measurement.
 Greek companies, with English methodologists, so companies did not use techniques invented by the experimenters. 
 At first, all companies didn't have a repeatable process, but some used intermediate and advanced practices anyway.
 Experimenters suggested guidelines to be targeted.
 All companies improved RE levels.
 Also looked at business results: critical success factors (CSF), key performance  indicators (KPI).  All companies showed improvements.
 Company reps said it was worth doing.
 Companies did not know what improvements to make.
 Classification of guidelines is domain dependent.
 The tool was worth developing: saved data entry time etc.
.Close

Spinellis07a
.Open Spinellis07a
 Diomedis Spinellis 
 Silver Bullets and other Mysteries
 IEEE Software Magazine V24n3(May/Jun 2007)pp22-23 
 =ESSAY SUBOPTIMAL PROCESSES DEATHMARCH FADS LEGACY GAMES   
 Notes Alan Davies's explanation (NASSCOM 2006) of why developers and 
marketers agree on adding functions with impossible delivery dates.
 Reason: Machiavellian win-win after failure
.Set
 Developers blame the impossible schedule.
 Marketers blame the delay for missing the market window.
.Close.Set

 Similarly rather than developers admitting the low quality of a legacy 
system, they prefer to promote its replacement with one using the latest
`silver bullet` method/technology/process.  Managers earn points for vision
and proactivity. Vendors make money by selling the new ideas.  And if it 
fails, then both developers and managers can blame the immaturity of the 
new `silver bullet`.
.Close

Voas99b
.Open Voas99b
 Jeffrey Voas
 Software Quality's Eight Greatest Myths
 IEEE Software Magazine V16n5(Sep/Oct 1999)pp118-120
 =ESSAY QUALITY IMPROVEMENT
.List
 Maturity means quality software
 Formal methods solve any quality problem
 Problems go away when you change the language or paradigm
 Numbers about code tell you how good it is.
 Published standards can replace common sense.
 Testing can get any project out of any bind.
 Programming with a graphic schematic or pictorial language will make code better.
.Close.List
.Close

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

To see the complete bibliography (1Mb+) select:[Bibliography]