[Text Version] newbib Wed May 9 10:59:47 PDT 2012

Opening the PDF files on this page may require you to download Adobe Reader or an equivalent viewer (GhostScript).

Opening Microsoft files (winzip, word, excel, powerpoint) on this page may require you to download a special viewer. Or you can download and save the files and use your preferred office applications to view and edit them.

Bibliography

Richard J Botting
A Bibliography of software development
1984..2005 [ newbib.html ]
=BIBLIOGRAPHY SOFTWARE DEVELOPMENT
Goal:= To document most useful theories and the most reliable information about current and past practice.
Example: What really happened when IPT was tried at the New York Times? [McNurlin77]
Example: for how long have people been writing about replacing the Software Development Live Cycle? [Gladden82]
New items are described in my Weblog [ blog.mth ] when the citation is posted here.

Aaen03

Ivan Aaen
Software Process Improvement: Blueprints versus Recipes
IEEE Software Magazine V20n5(Sep/Oct 2003)pp86-93
=ADVOCATES AGILE IMPROVEMENT SPI PEOPLE vs PROCEDURE
Lists the risks of having a separate SPI team working out a blueprint/structure/standards.
Promotes the facilitation of improvisation plus reflection within existing teams

AalstWeijtersMaruster04

Wil van der Aalst & Ton Weijters & Laura Maruster
Workflow mining: discovering process models from event logs
IEEE Trans Knowledge and Data Engineering V16n9(Nov 2004)pp1128-1142 CR 0512-1362
=THEORY =APPLIED 2 SYSTEM nonsequential PETRI SWF-net workflow-net α-algorithm TOOLS EMiT Little Thumb WORKFLOW
Start with logs of real work-flows.
Gives α-algorithm to convert logs into nets. Work-nets are specialized petri P/T nets with certain structures forbidden.
Tested on system for patients in hospital and had to ignore rare events/activi ties.
Tested on 130,136 cases of fine collection for a justice system.

AalstWeske05

Wil M van der Aalst & Mathias Weske
Case Handling: A new paradigm for business process support
Data & Knowledge Engineering V53n2(May 2005)pp129-162 CR 0605-0527
=UNREAD =IDEA WORKFLOW DESIGN UML METAMODEL [click here if you can fill this hole]

AbadiLamport90

Martin Abadi & Leslie Lamport
Composing Specifications
Digital Sys Res Center(Oct 10 1990) CR9405-0309 F.3.1 [AbadiLamport93]
=MATHEMATICAL SPECIFICATION LOGIC
Has a ref to Cliff Jones's Oxford PhD Thesis in the early 80s! p9: "Composition is conjunction" cf Zave & Jackson.

AbadiLamport92

Martin Abadi & Leslie Lamport
An Old-fashioned Recipe for Real Time
Digital Sys Res Center TR#91(Oct 12 1992) [AbadiLamport94]
=MATHEMATICAL TIMING LOGIC

AbadiLamport93

Martin Abadi & Leslie Lamport
Composing Specifications
ACM TOPLAS V15n1(Jan 1993)pp73-132
=MATHEMATICAL SPECIFICATION LOGIC
Reviewed CR9405-0309 F.3.1
similar to AbadiLamport90 Based on Lamport91

AbadiLamport94

Martin Abadi & Leslie Lamport
An Old-fashioned recipe for Real Time
ACM TOPLAS V16n5(Sep 1994)pp1543-1571 See [AbadiLamport92]
=MATHEMATICAL TIMING LOGIC
Review CR9507-0506 F.3.1: uses TLA as a base
can reason separately about function and timing(by var now:real). Two problems: now can get stuck (Zeno-ness) or two requirements can conflict. ->> detect and correct spec to avoid. (not in A&L 1992?)

AbadiLamport95

Martin Abadi & Leslie Lamport
Conjoining Specifications
ACM Ttrans Prog Lang Sys V17n3(May 1995)pp507-535 CR9605-0369 CR9608-0610(...cumbersome notation....) F.3.1
=MATHEMATICAL SPECIFICATION LOGIC TLA
conjunction implies parallel combination

Abbotetal93

Ben Abbott & Ted Bapty & Csaba Biegl & Gabor Karsai & Janos Sztipanovits
Model Based Software Synthesis
IEEE Software Magazine (May 1993) pp42-52
=ADVERT METHOD

Abbott83

?? Abbott
Program Design by Informal English Descriptions
Commun ACM Vol 26 No 11(Nov 1983)pp882-894
=IDEA ADTs REALITY THEORY Informal algorithm->model->code
Start with an informal algorithm and extract and object-oriented model.
Leads to Grady Booch's methods but is later critiscized because getting the algorithm is difficult. [Booch83] [Booch86]

Abdel-Hamid96

Tarek K Abdel-Hamid
The Slippery Path to Productivity Improvement
IEEE Software Magazine VSE13N4(Jul 1996)pp43-54
=SIMULATION TOOLS PEOPLE
simulation rediscovers Brookes's Law. Also raw historical data can trigger a brookes crisis. Work reffered to in [Brooks95]

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.

Abiteboul00

Serge Abiteboul & Peter Buneman & Dan Suciu
Data on the Web: from relations to semistructured data and XML
Morgan Kaufman SF CA 2000 ISBN 1-55860-622-X CR 0105-0161 QA76.9.D3 A258
=MONOGRAPH DATA NET/WWW LOGIC XML XSL-QL DTD ACeDB OEM Lore Strudel

AbowdDix93

Gregory D Abowd & Alan J Dix
Integrating status and event phenomena in formal specifictions of interactive systems
SIGSOFT'94 Proc 2nd ACM SIGSOFT Symp on Foundations of Software Engineering & ACM SIGSOFT Software Engineering Notes V19n5(Dec 1994)pp44-52. See [ZaveJackson94]
=MATHEMATICAL HCI/USER SPECIFICATION

Abowdetal93

Gregory D Abowd & Robert Allen & David Garlan
Using Style to Understand Descriptions of Software Architecture
In [Notkin93] pp9-20
=THEORY MATHEMATICAL ARCHITECTURE
Z Pipe-filter and Event System styles
partial functions Syntax<>->Semantics to describe constraints on syntax

Abowdetal95

Gregory D Abowd & Robert Allen & David Garlan
Formalizing Style to Understand Descriptions of Software Architecture
ACM Trans Softw Eng Methodol V4n4(Oct 1995)pp319-365
=THEORY MATHEMATICAL ARCHITECTURE
expanded version of 1994 SIGSOFT paper (or is it : AbowdAllenGarlan93?)

AbramowitzStegun6465

Milton Abramowitz & Irene Stegun (National Bureau of Standards)
Handbook of Mathematical Functions
NIST hard back edition 1964 & Dover paper back edition NY NY 1965 [ Abramowitz_and_stegun ]
=HANDBOOK MATH FUNCTIONS TABLES FORMULAE
Electronic copies: [ http://people.math.sfu.ca/~cbm/aands/ ] at Simon Fraser University and [ AMS55.asp ] at ConvertIt.com.
Update [OlverEtal10]

Abramson73

?? Abramson
Theory & Practice of a Bottom-up Syntax Directed Translator
NY Ac Press 1973
=HOWTO COMPILER DDD REALITY SYSTEM

AbramsonDahl89

Harvey Abramson & Veronica Dahl
Logic Grammars
Springer Verlag 1989
=HOWTO GRAMMAR DDD PROLOG REALITY

Abrial89

J Abrial
A Formal Approach to Large Software Construction
In Mathematics of Program construction J L A Van de Snepscheut(ed) Springer NY NY 1989 pp 1-20. See [LafontaneLedruSchobbens91]
=ADVERT LOGIC TOOL Z VDM B
B theorem prover LOGIC TOOL used by Z and VDM groups

Abrial09

Jean-Raymond Abrial
Faultless Systems: Yes we can
IEEE Computer Magazine V42n9(Sep 2009)pp30-36
=ADVERT FORMAL SYSTEMS REQUIREMENTS B Event-B CORRECTNESS MODEL PROOF SIMULATION REFINEMENT PATTERNS MATHEMATICS TOOL Rodin
assumes waterfall is necessary.
process=requirements; model; code.
requirements are a mixture of informal explanations and form definitions and proofs etc.
Use coupled discrete state transition systems. And animation. Prove invariants.
Need tools to prove thousands of changing propositions.
Validate the problem as a system in an environment not just the software.
Problem with not enough discrete mathematics in education.
Problem with technology transfer.
Link [ http://www.event-b.org ]

AbrilPlant07

Patricia S Abril & Robert Plant
The patent holder's dilemma: buy, sell, or troll?
Commun ACM V50n1(Jan 2007)pp37-44
=SURVEY PATENTS LEGAL INTELECTUAL PROPERTY
Complex business models involving trading, holding, and combining software patents -- and they don't all work.

Abualsamid01

Ahmad Abualsamid
PHP & Hosted Applications
Dr. Dobbs #320(Jan 2001)pp56+58+60-63
=ADVERT WWW/NET SERVER SCRIPTING LANGUAGE EXAMPLE
PHP has syntax like UNIX shell.

Aceto92

Luca Aceto
Action Refinements in Process Algebras
Cambridge University press 1992 ISBN 0-521-43111-5
=THEORY NONSEQUENTIAL MATHEMATICAL ALGEBRA
CR9312-0920(non-sequential for experts; distinguished thesis; poor printing "tractable notion of semantic equivalence of process algebras that do not equate parallelism with sequential nondeterminism and support operators for refining actions.")

Ackerman03

Jody Ackerman
Uniting with only a few random links
Newswise [ ?id=RANDOM.RPI ]
=ARTICLE NONSEQUENTIAL NET PARALLEL COMPUTATION
Use a small world network to keep processes synchronized with minimal overhead.
Regular communication with a few neighbors + a few connections with random distant processes.
Research by Korniss at Rensslaer (RPI)

AcunaJuristo04

Silvia T Acuna & Natalia Juristo
Assigning people to roles in software projects Software - Practice & Experience V34n7(Jun 2004)pp675-696 CR Nov2004
=EXPERIMENT PEOPLE PROCESS
Document person-role-capabilities relationship before seeking optimal assignments in a project.
Worked better than a random assignment!
Leads to [AcunaJuristo06]

AcunaJuristo05

S Acuna S & N Juristo (Eds)
Software process modeling
Springer-Verlag New York, Inc., Secaucus, NJ, 2005. (the kluwer international series in software engineering) CR 0607-0694
=SURVEY =PAPERS PROCESS MODELLING MATHEMATICS PEOPLE UML MANAGEMENT JAD IMPROVEMENT CMM PSPS STIN SPEM
Reccommends focussing process research on the people in the process and the needs of the organization. [AcunaJuristo04] [AcunaJuristo06]

AcunaJuristoMoreno06

Silvia T Acuna & Natalia Juristo & Ana M Moreno
Emphasizing Human Capabilities in Software development
IEEE Software Magazine V23n2(Mar/Apr 2006)pp94-101
=EXPERIMENT PEOPLE Cattell 16PF ROLLS CF
Matching personality to role seems associated with fewer defects and higher productivity. [AcunaJuristo04].

ACM86

Editted by Robert L Ashenhurst & Susan Graham
ACM Turing Award Lectures: The First Twenty Years 1966-1985
ACM Press 1987 ( Addison-Wesley)
=HISTORY SURVEY PRIZE winners

ACMCALGO

Various
The ACM Collected Algorithms
Association for Computing Machinery 1960-
=HANDBOOK TECHNICAL

Adamatzky10

Anrew Adamatzky (Ed)
Game of Life cellular automats
Springer NY NY (2010) ISBN 1849962162 CR 1108-0789
=PAPERS =HISTORY CA Cellular Automata Conway Game of Life 2D 3D
TBD [click here Adamatzky10 if you can fill this hole]

AdamicHuberman01

Lada A Adamic & Bernardo A Huberman
The Web's Hidden Order
Commun ACM V44n9(Sep 2001)pp55-59
=ANALYSIS NET/WEB WWW COMPLEXITY SMALL-WORLD POWER-LAW DYNAMIC MODEL ECONOMICS
power_law(β)::= Net{ for some constant c, frequency = c /(size**β). }.
WWW shows exponential growth.
number of pages per site, number of users, number of outlinks, and number of inlinks all have close to a 1/n**2 distribution.
This can be accounted for by two random growth models. stochastic rate of growth proportional to size. Either starting at different times, or with different growth rates.
Usage is an 80-20 phenomenon.
Implication: any site gets a few visitors each day, few get large numbers...
winner take all markets.
small worlds effect because some sites have lots of links. diameter between sites is about 4 clicks. between pages about18 clicks.

Adams91

Illustrated by Scott Adams
Build a better life by stealing office supplies: Dogbert's big book of business
Andrews & McMeel, Kansas City, Missouri, 1991, ISBN 0-8362-1757-8
=JOKE PEOPLE MANAGEMENT

Adams97

Scott Adams
Seven Years of Highly Defective People
Andrews McMeel Publishing, 1997, Kansas City, Missouri, ISBN 0-8362-3668-8
=JOKE PEOPLE cartoons on engineering, life, and mis-management

Adams96

Tom Adams
Total Variance Approach to Software Reliability Estimation
IEEE Trans on Software Eng VSE-22n9(Sep 1996)pp687-688
=MATHEMATICS QUALITY TEST RELIABILITY
Operational Profiles do not admit that they are uncertain predictions and so reliability is underestimated

AdamsE84

E Adams
Optimizing preventive service of software products
IBM Research J., V28n1(?? 1984)pp2-14
=EMPIRICAL QUALITY vs RELIABILITY
Quoted by [FentonOhlsson00]

AdamsJ06

Joel C Adams
OOP and the Janus Principle
ITICSE ACM SIGCSE Bulletin V38n1(Mar 2006)pp359-363
=DEMO TEACHING PEDAGOGY JANUS OBJECT-ORIENTED MODULES MVC DAYTIME JAVA CSCI375
Janus::=following
The old Parnas rule:"Separate concerns". [Parnas72b]
Presents a modified MVC with View+Controller in one class plus separate Model class.
Nice example: Program to get and display current time from servers with multiple user interfaces: command line & menu-driven & GUI: [ http://www.calvin.edu/~adams/software/janus/ ]

AdamsEtAl11

Michael Adams & Arthur H M ter Hofstede & Marcello La Rosa
Open source software for workflow management: the case of YAWL
IEEE Software Magazine V28n3(May/Jun 2011)pp16-19
=ADVERT =HISTORY 2008-2010 OPEN SOURCE WORKFLOW SYSTEM LANGUAGE YAWL JAVA Sourceforge: [ http://sourceforge.net/projects/yawl/ ]

AdcockEtAl07

Bruce Adcock & Paolo Bucci & Wayne D Heym & Joseph E Hollingsworth & Timothy Long
Which Pointer Errors do Students Make?
ACM SIGCSE Bulletin V39n1(Mar 2007) & proc SIGCSE'07 pp9-13
=ADVERT TOOL C++ Java PEDAGOGY
Proposes finite state models for pointers in C++ and in Java.
Java_pointer_model::=following
Table
Old\New Alive Null Out of scope
Alive * new NULL }
Null new NULL *X }
Out of scope 0 0 declare

(Close Table)
(X = unsafe)
C++Pointer_model::=following
Table
Old\New Alive Null Out of scope Dead
Alive * new Z NULL Z } Z delete ε
Null new NULL *X delete } 0
Out of scope 0 0 0 declare
Dead new NULL } * X delete X

(Close Table)
(Z=dangerous, X=unsafe, ε=spontaneous)

Old\New	Alive	Null	Out of scope
Alive	* new	NULL	}
Null	new	NULL *X	}
Out of scope	0	0	declare

Old\New	Alive	Null	Out of scope	Dead
Alive	* new Z	NULL Z	} Z	delete ε
Null	new	NULL *X delete	}	0
Out of scope	0	0	0	declare
Dead	new	NULL	}	* X delete X

Adhikari95a

Richard Adhikari
BringingMethodology to Client/Server Madness
Software Magazine (Mar 1995)pp35-49
=SURVEY METHODS WEB/NET
Fig p40: 13 different methods in use/planned to be used

Adhikari95b

Richard Adhikara
Code Recycling saves resources
Software magazine (July 1995)pp31-37
=EXPERIENCE TECHNICAL REUSE
6 experiences of technical (code) reuse technology paying off. Across several platforms & industries: mainly large projects. Some object-oriented but some were not. Example of a simulation have code componentes that were later reused for non-simulation.

Adler88

Mike Adler
An Algebra for DFD Process decomposition
IEEE trans on Soft Eng vSE-14n2(Feb 1988)pp169-183
=MATH ALGEBRA IO MATRICES DESIGN DFD TECHNICAL

AdlerR95

Richard M Adler<radler@tiac.net>
Emerging Standards for Component Software
IEEE Computer Magazine V28n3(Mar 1995)pp68-76
=STANDARDS CORBA OMG+ OLE COM+OpenDoc+DCE/RPC+SOM+...

Adolf96

W Stephen Adolph
Cash Cow in the Tar Pit: Reengineering a Legacy system
IEEE Software Magazine V13N3(May 1996)pp41-47
=EXPERIENCE REENGINEERING RISK SYSTEM 20 year old assembly language for obsolete computers
need to provide tools to aid the reading of the legacy code and capturing key algorithms
2 weeks training in Hatley/Pirbhai SAD and PC CASE lead to designs that had to be thrown away
key objective: no feature of legacy system to be "improved" unless it reduced the cost of implementing the new system. domain experts must train sosftwrae specialists
need to manage CASE tools.

Adolph99

Steve Adolph =?= W Stephen Adolph
Whatever Happened to Reuse?
Software Development Magazine V7n11(Nov 1999)pp40-43
=ESSAY REUSE vs salvage COST ECONOMICS short-term needs vs long term value

Adolph00

Steve Adolph
four-wheel drive, garbage trucks and objects
Software Development Magazine V8n6(Jun 2000)pp52-55
=ESSAY OBJECT-ORIENTED DESIGN MODULE MAINTENANCE REFACTORING
OO + expediency can encourage loss of cohesion and high coupling: blobs, mudballs, or garbage barges
example - add salaried employee to employee

Adolf00b

Steve Adolph
Getting Out of the Software Mud Pit
Software Development Magazine V8n12(Dec 2000)pp41-44
=HOWTO =HISTORY REFACTOR MAINTENANCE TECHNICAL QUALITY
Big balls of mud are messy but systematic refactoring can help.
refactor::=apply behavior-preserving transformations that improve code quality.
Refers to William Opdyke's 1992 Doctoral thesis "Refactoring Object-oriented Frameworks" U of Illinois at Urbana-Champaign
Example: Fixing Feature Envy. A piece of code in method in class A refers to several class B methods only. Therefore Replace-Code-Segment-With-Function-Call AKA Extract Method(110) and then Move-Member-Function AKA Move Method(142)

Adve10

Datura Adve
Data races are evil with no exceptions
Commun ACM V53n11(Nov 2010)p84 [ 1839676.189697 ]
=ESSAY NONSEQUENTIAL SHARED MEMORY HAZARDS DETECTION EXCEPTIONS
Punning introduction to [ElmasQadeerTasiran10] and [FlanaganFreund10]

AgarwalREtal00

Ritu Agarwal & Prabuddha De & Atish P Singh & Mohan Tanniru
On the Usability of OO Representations
Commun ACM V43n10(Oct 2000)pp83-89
=EXPERIMENT FUNCTIONAL vs DATABASED MODELS of new SYSTEM POLL
Easiest to match type of model to the type of task.

AgarwalLago95

Rakesh Agarwal &Patricia Lago
PATHOS - A Paradigmatic Approach To High-level Object-oriented Software Development
ACM SIGSOFT Software Engineering Notes V20n2(Apr 1995)pp36-41
=ADVERT METHOD OBJECT-ORIENTED
1. confused
2. technical activities: find classes, find methods and behavior, define classes and methods
3. Technical control activities: logical design, detailed design
4. ...Early consideration of reuse and quality in design

AgarwalRahaGhosh00

Rakesh Agarwal & Arup Ratan & Raha Bhaskar Ghosh
Our experience and learning in ERP implementation
ACM SIGSOFT Software Engineering notes V25n2(Mar 2000)pp31-34
=EXPERIENCE MRP-II
gap_analysis:=comparing existing software behavior with the client budiness needs.
need tounderstand client's business
use informal discussion to gather data.

AgarwalSinha03

Ritu Agarwal & Atish P. Sinha
Object-oriented modeling with UML: a study of developers' perceptions
Communications of the ACM V46n9 (Sep 2003)pp 248-256 Virtual extension Retrieved Sep 3rd 2003 from [ 903893.903944 ]
=EXPERIMENT NOVICES UML GRAPHICS use case state charts
p252: "both use case diagrams and state diagrams were perceived as being easier to use than class and interaction diagrams."
p253: "developers with more experience in OO analysis and design techniques perceived class diagrams and interaction diagrams as being easier to use than those with less experience."
p253: "greater experience in process-oriented analysis and design techniques resulted in more positive perceptions of the usability of UML diagrams, overall."
p253-4: use case document real world problems BUT how much detail?, Class diagrams notations are liked but defining operations is difficult. State diagrams are simple and easy but how to identify states?, Interaction diagrams provoke strong +ve and -ve comments. Use cases are the best.

Agha90

Gul Agha
Concurrent Object-oriented Programming
Commun ACM V33n9(Sep 1990)pp125-141
=DEMO GRAPHIC OBJECT_ORIENTED NONSEQUENTIAL DESIGN
Actor-Event diagrams History dependent

Aghaetal89

Gul Aghar & Peter Wegner & Akinori Yonezawa(Ed)
Proceedings of the ACM SIGPLAN Workshop on Object-Based Concurrent Programming
SIGPLAN Notes V24n4(Apr 1989)
=PROCEEDINGS DYNAMICS OBJECT-ORIENTED COROUTINES

Aghaetal93

Gul Agha & Peter Wegner & Akinori Yonezawa(Ed)
Research Directions in Concurrent Object-Oriented Programming
MIT Press Cambridge MA 1993 ISBN 0-262-01139-5 CR9502-0058
=PROCEEDINGS DYNAMICS OBJECT-ORIENTED COROUTINES

Agosta95

Louis Agosta
Comparative Review(CR9502-0058)
Computing Reviews V36n2(Feb 1995)pp88-93
=HISTORY OBJECT-ORIENTED METHODS Three waves of OO methods:

Agre95

Philip A Agre
My Top 10 Email Hassles
Commun ACM V38n7(Jul 1995)pp122
=ARTICLES RISKS EMAIL

AgrestiEvanco92

William W Agresti & William M Avanco
Projecting Software Defects From Analysing Ada Designs
IEEE Trans on Software Eng VSE-18n11(Nov 1992) pp988-997
=EXPERIMENT METRIC
Evidence that "with" coupling is correlated with defect density.

AhoUllman7273

Aho & Ullman
The Theory of Parsing Translating & Compiling
2 Vols Prentice Hall International 1972 & 1973
=TEXTBOOK =REFERENCE SURVEY DDD TECHNICAL

AhujaCarrieroGelernter86

Sudhir Ahuja & Nicholas Carriero & David Gelernter
Lynda and Friends
IEEE Computer Magazine V19n8(Aug 1986)pp26-34
=ADVERT Lynda NONSEQUENTIAL

AielloEtAl07

Marco Aiello & Ian E Pratt-Hartman & Johan F van Bentham (Eds)
Handbook of spatial Logics
Springer Verlag NY Secaucus NJ 207 ISBN 1402055862 CR 0811-1045
=UNREAD =REFERENCE FORMAL MODAL LOGIC SPACE

AikenMuntzRichards94

Peter Aiken & Alice Muntz & Russ Richards
DoD Legacy Systems: Reverse Engineering Data Requirements
Comm ACM V37n5(May 1994)pp26-41
=EXPERIENCE REVERSE ENGINEERING DATA
1. LDM has 468 entities and 1994 data elements
  1993: LDM has 362 entities and 1318 data elements

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.

AichernigKainhofer04

Bernhard K. Aichernig & Reinhold Kainhofer Comments: Presented at LfM2000, published in the proceedings In C.Michael Holloway, editor, Lfm2000, Fifth NASA Langley Formal Methods Workshop, Williamsburg, Virginia, June 2000, number CP-2000-210100, pages 35-46. NA SA, June 2000
=DEMO VALIDATION VDM-SL Mathematica Hybrid SAFER graphic animation
Computer algebra systems can express VDM specifications and extend them to handle continuous(analog) components and behavior.

AissiMaluSrinivasan02

Selim Aissi & Pallavi Malu & Krishnamerthy Srinivasan
E-Business Process Modeling:The Next Big step
IEEE Computer Magazine V35n5(May 2002)pp55-62
=DEMO WEB/NET STANDARD WEB SERVICES XML
PCF::="Process Coordination Framework", groups standards for e-business.
PCF = security & ( service description and transaction binding end point description, public collaborative, private process; contracts and agreements).
WSDL::="Web service description Language". [ wsdl ] provides information needed to use a service over the web.
WSCL::="web services Conversation Language", [ http://www.w3.org/TR/wscl10/ ] defines conversations between service providers.
ebXML::= See http://www.ebxml.org/specs/ebBPSS.doc, UN and OASIS choreographs collaborations/transactions.
CPP::= See http://www.ebxml.org/specs/ebCPP.doc, Collaboration Protocol Profile.
WSFL::= See http:://www4.ibm.com/software/solutions/webservices/pdf/WSFL.pdf, Web services Flow Language.
XLANG::http://www.gotdotnet.com/team/xml_wsspecs/xlang-c/default.htm, describes executable internal business processes.
BPML::= See http://ww.bpmi.org/bpml.esp, describes internal business processes using transactional finite state machines.

Akera07

Atsushi Akera
Edmund Berkeley and the Origins of ACM
Commun ACM V50n5(May 2007)pp31-35
=HISTORY 1940s ANALYSIS Study Contract
Need to sell managment on the use of computers to do paper-work. "Methods Analysis".

AlagarVenkatesan01

Sridhar Alagar & Subbarayan Venkatesan
Techniques to Tackle state explosion in a Global Predicate Detection
IEEE Trans Software Engineering V27n8(Aug 2001)pp704-714
=THEORY LOGIC MODEL CHECKING

AlanenPorres03

Marcus Alanen & Ivan Porres
Difference and Union of Models
LNCS 2863 <<UML>> 2003 -- The Unified Modeling Language, Oct 2003, pp2-17
=ALGORITHMS on MODEL VERSIONS UML MOF CMS
If + is merge and - is difference then union of M1 and M2 based on M0 is M0+(M1-M0)+(M2-M0)

Alavi86

Maryam Alavi
An Assessment of the Prototyping Approach to Information Systems Development
Comm ACM V27n6(Jun 1986)pp556-563
=EXPERIMENT PROTOTYPING REQUIREMENTS TOOLS
concludes PROTOTYPING needs expertise support TOOLS and control but handles unclear and ambiguous REQUIREMENTS

AlaviWetherbe91

Maryam Alavi & James C Wetherbe
Mixing Prototyping and Data Modeling for Information-System Design
IEEE Software V8n3 (May 1991)p86-91.
=ADVERT DATA PROTOTYPING

Albizuri-Romero00

Miren Begona Albizuri-Romero
A retrospective view of CASE tools adoption
ACM SIGSOFT Software Engineering notes V25n2(Mar 2000)pp46-51
=SURVEY pre1990 papers on STRUCTURED TOOLS

AlencarCowanLucenaNova95

Paulo S C Alencar & Donald D Cowan & Carlos J P Lucena & L C M Nova
Formal specification of Reusable Interface Objects [SamadzadehZand95] pp88-96
=DEMO ADV/ADO ADTs REUSE

Albrecht04

Conan C Albrecht
How Clean is the future of SOAP
Commun ACM V47n2(Feb 2004)pp66-68
=THEORY SOAP TCP port 80 HTTP XML SECURITY vs CONVENIENCE
SOAP::protocol="Simple Object Access Protocol", uses port 80 and HTTP to access objects + XML to encode operation and response.
content type: text/xml-SOAP.
Web server passes SOAP to routing engine and response back to caller.
Currently not filtered. Security problems would change this.

AlencarCowanLucena02

Paulo S C Alencar & Donald D Cowan & Carlos J P Lucena
A Logical Theory of Interfaces and Objects
IEEE Trans Software Engineering V28n6(Jun 2002)pp548-575
=THEORY FORMAL LOGIC CATEGORY OBJECTS INTERFACES ADV ADO
ADV::= "Abstract Design Views", interfaces.
ADO::= "Abstract Design Objects".
views_a::@(ADV, ADO).
cf [AlencarCowanLucenaNova95]

Alexander79

Chistopher Alexander
A Pattern Language
Oxford U Press UK 1979
=THEORY ARCHITECTURE Buildings, towns, regions.

Alexander00

Christopher Alexander
The Nature of Order
Book to be published in 2000
=THEORY
living structures generated smoothly by structure preserving unfoldings.
normal 20C construction can not do this!

Alexander92

Tom Alexander
How to Stop Fearing and Start Loving the Parallel Computer
NSF MOSAIC V23n1(spring 1992)pp2-11
=ARTICLE NONSEQUENTIAL TECHNICAL

AlexanderCoplien99

Christopher Alexander & James O Coplien(introduction)
The Origins of Pattern Theory
IEEE Software Magazine V16n5(Sep/Oct 1999)pp71-82
=SPEECH OOPSLA'96 PATTERN THEORY
patterns were generative( ala Chomski ), included a moral component, must lead to morphological coherence - a life promoting structure, a good environment
15 geometric properties underlying original patterns -> profundity
80..90%agreement for "Do you feel more whole/alive in the presence of this or that object?". Correlates with certain features/structures & profound functionallity!
centers:=field-like structures recursively underlying all wholeness& more or less living things. See [Alexander00]
Can/will software designers help people generate a life enhancing world?

AlexanderH88

Heather Alexander
Comments on "Formal Specification of User Interfaces: A comparison and Evaluation of Four Axiomatic Approaches"
IEEE Trans Soft Eng VSE-14n4(Apr 1988)pp438-439
=DEMO need SQA on Z SPECIFICATIONs as well as code

AlexanderH03

Ian Alexander
Misuse Cases: Use Cases with Hostile Intent
IEEE Software Magazine V20n1(Jan/Feb 2003)pp58-66
=IDEA NEGATIVE USECASES SCENARIO PURPOSES QUALITIES ANTI-STORIES
Need to promote use-cases while stopping misuse cases.
Normal relations: includes, has exception.
New relations: misuse threatens use, use mitigates misuse.

Alexander11

Ian Alexander
GORE, SORE, or what
IEEE Software Magazine V27n6(Jan/Feb 2011)pp8-10
=COMPARISON REQUIREMENTS METHODS GOALS GORE i* KAOS STAKEHOLDER SORE SCENARIO SCORE USE CASES PRIORITY PORE COST-BENEFIT TRIAGE CONTEXT EVENT CORE
Informal use of a single approach over-simplifies situations.
Example: a scenario does not expose all threats that must be mitigated.
Analyzing goals (i*, KAOS) can expose unconscious intentions and assumptions and so threats and so mitigations.
Context models show what enters and leaves the system. So uncovering the events that must be handled.
Table 1 compares approaches.
Need to compare models from a many approaches that fit the particular situation.

AlexanderKong01

Perry Alexander & Cindy Kong
Rosetta: Semantic Support for Model-Centered Systems-Level design
IEEE Computer Magazine V34n11(Nov 2001)pp64-70
=DEMO TOOL ROSETTA MODEL SYSTEM PROPERTIES Category outputs Matlab TESTS
Sidebar on p69 describes rivals: Adept, DEVS, Ptolemy, aspects, viewpoints, HyTech, SAL Kestrel, SpecWare
Able to define, compose, project and explore the interactions of models of different types.
facet := a special model within a domain of models. Facets are combined vertically(all true at one time) and horizontally )interacting components).
domains: continuous and discrete times, finite and infinite state systems and tests, .... mechanical, hydraulic, power constraints

AlexanderRobertson04

Ian Alexander & Suzanne Robertson
Understanding Project Sociology by Modeling Stakeholders.
IEEE Software Magazine V21n1(Jan/Feb 2004)pp23-27
=IDEA REQUIREMENTS ANALYSIS STAKEHOLDERS Onion Model
Fig 3 p26: Large matrix of stakeholder types vs classes of knowledge.
Distinguishes 3 layers f stake holders centering on our product/the kit.
Many systems the role of users is split between the normal operator close to the product, and the functional beneficiary.
Onion.layers:=(our_product, our_system, containing_system, wider_environment).
our_system:={ normal_operator, maintenance_operator, ...}.
containing_system:={ functional_beneficiary, purchaser, interfacing_system,...}.
wider_environment:={political_beneficiary, financial_beneficiary, negative_stakeholder, regulator, developer, ...}

AlexanderRBiemanViega00

Roger T Alexander & James M Bieman & John Viega
Coping with Java Programming Stress
IEEE Computer Magazine V33n4(Apr 2000)pp30-38
=DEMO JAVA TECHNICAL traps
default/protected access easily broken
subclasses can steal methods called in superclass constructors
containers+no templates means ineffective type checking
extend only for subclassin/is-a
finalizers wai for garbage collection and may never happen
no const methods or assertions so document very carefully
avoid confusing (unlabelled) instance initialization blocks.

Alhir98

Sinan Si Alhir
UML in a Nutshell
O'Reilly, Cambridge, Mass, 1998 ISBN 1-56592-448-7
=REFERENCE to UML1.1 (OMG UML1.0) CR9908-0596
Comprehensive and with very few errors! Reference not readable.
Errata and comments on the UML on the WWW [ ~salhir ]

AllenA94

Arnold O Allen
Introduction to Computer Performance Analysis with Mathematica
CS&SciComp Acad Press 1994 ISBN 0-12-051070-7 Review p492 AMM May 1994
=TEXTBOOK with disk TECHNIQUE->QUALITY

AllenB94

Bradley P Allen
Case-Based Reasoning: Business Applications
Comm ACM V37n3(Mar 1994)(AI issue)pp40-44
=ARTICLE AI

AllenCD95

C Dennis Allen
Succeeding as a Clandestine Change Agent
Commun ACM V38n5(May 1995)pp81-86
=HISTORY USER PEOPLE SYSTEMS
The Water Torture Method
p82: "I discovered that automating a manual process can break the customer's work practice."

Allman90

Eric Allman
By the pricking of my thumbs(article)
UNIX Review V9n2(Feb 1991)pp66-69. History of FORTRAN and C
=HISTORY C FORTRAN LANGUAGES

Alonzo03

Omar Alonzo
Generating Text Search Applications for DataBases
IEEE Software Magazine V20n3(May/Jun 2003)pp98-105
=DEMO DOMAIN XML GENERATE Java Web/Net SQL TEXT SEARCH Oracle DARE-Web YASEC
XSLT less useful than DOM and SAX.

AlfaroHenzinger01

Luca de Alfaro & Thomas A Henzinger
Interface Automata
ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp109-120
=THEORY SPECIFICATION MODULE FSM/AUTOMATA INTERFACE NONSEQUENTIAL

AlijazzarLeue10

Husain Alijazzar & Stefan Leue
Directed Explicit state-space search in the generation of Counter examples for Stochastic Model Checking
IEEE Trans Software Engineering V36n1(Jan/Feb 2010)pp37-60
=DEMO MODEL CHECKING PROBABILITY PCTL CSL PRISM MARKOV CHAINS
Given a model as a Markov chain and a property, finds paths that are probable but don't match the property.
Can handle both discrete and continuous Markov chains.

AlmeidaJrEtal03

Jorge Rady de Almeida Jr & Joao Batista Camargo Jr & Bruno Abrantes Basseto & Sergio Miranda Paz
Best Practices in Code Inspections for Safety-Critical Software
IEEE Software Magazine V20n3(May/Jun 2003)pp56-63
=EXPERIENCE RISKS QUALITIES SQA CODE INSPECTION
Developed a useful checklist of defect types to find unsafe code.
For example: Check that a constant has the same value in different modules even when in different languages!

Almendros-JimenezIribarne10

Jesus M Almendros-Jimenez & Luis Iribarne
Describing Use-Case Relationships with Sequence Diagrams
Computer Journal V50n1(Jan 2007)pp116-128 [ bxl053 ]
=DEMO UML SEQUENCE USECASE
Shows that use case relations (includes, extends, generalizes) are not clearly defined or well understood.
Shows ways of deducing them from sequence diagrams of the scenarios in the use case.

AlmeringEtAl07

Vincent Almering & Michiel van Genuchten & Ger Cloudt & Peter J M Sonnemans
Using Software Reliability Growth Models in Practice
IEEE Software Magazine V24n6(Nov/Dec 2007)pp82-88
=EXPERIENCE 5 MODELS TVs
The models got better as more data was fitted.
λ(t) :=failure intensity function.
(GO): λ(t) =a*b*exp(-b*t).
(delayed S): λ(t) =a*b^2*t*exp(-b*t).
(log power): λ(t) = α*β*ln^(b-1)(1+t)/(1+t).
(log Poisson): λ(t) = λ[0] / (λ[0] * θ * t + 1).

Alsaadi04

Ahmad Alsaadi
A Performance analysis approach based on the UML Class diagram
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp254-260
=EXAMPLe PERFORMANCE NORMALIZATION UML
Can get speed by denormalizing physical data.
Very like SSADM physical design control.

AlshayebLi03

Mohammad Alshayeb & Wei Li
An Empirical Validation of Object-Oriented Metrics in Two Different Iterative Software Processes
IEEE Trans Software Engineering V29n11(Nov 2003)pp1043-1049
=EMPIRICAL Object-Oriented METRICS AGILE XP client-server stories vs JDK 1.[0-4] EVOLUTION PROCESSES JAVA EDITS
metrics={WMC, DIT, LCOM, NLM, CTA, CTM}.
analyses short-cycle vs long-cycle.
The metrics with multi-linear regression predict the amount of change (and effort) well in the later cycles of an XP process.
Not so useful in the JDK long-cycle evolution.
|-" prediction is impossible at the beginning of the " [XP] " process because there is very little substantive design structure in the system".
Idea: critical mass of classes needed to define metrics that predict XP effort.

AltendorfHohmanZabicki02

Eric Altendorf & Moses Hohman & Roman Zabicki
Using J2EE on a large, Web-Based Project
IEEE Software Magazine V19n2(Mar/Apr 2002)pp81-89
=EXPERIENCE WEB/NET MODULE COMPONENT JAVA J2EE

AlurDill94

R Alur & D L Dill
A Theory of Timed Automata
Theoretical Computer Science V126 pp183-235 1994
=THEORY AUTOMATA TIMING

AlurEtessamiYannakakis03

Rajeev Alur & Kousha Etessami & Mihallis Yannakakis
Inference of Massage Sequence Charts
IEEE Trans Software Engineering V29n7(Jul 2003)pp623-633
=THEORY MESSAGE SEQUENCE CHARTS MSC AUTOMATA FSM non-SEQUENTIAL
When do a set of MSCs describe a possible system with no surprising behaviors allowed?
MSC define partial orders on sequences of messages.
Realize as a set of parallel communicating FSM automata.
Communication between automata is not FIFO (data flow) but via Bags.
To get tractable algorithms must not consider sets of automata that can deadlock.

Aluretal93

R Alur & C Courcoubetis & D L Dill
Model checking in dense real time
Information and Computation V104 pp2-34(1993)
=DEMO TIMING MODEL

AlvarezDiazLlopisPimentalTroya04

J M Alvarez & M Diaz & L Llopis & E Pimental & J M Troya
An Object-Oriented methodology for embedded real-time systems
Computer Journal V46n2( 2003)pp121-145
=EXAMPLE Object-Oriented TIMING RMA SDL UML OOM-ERT

AmblerBurnett89

Alan L Ambler & Margaret M Burnett
Influence of Visual Technology on the Evolution of Language Environments
IEEE Computer v22 n10 (Oct 1989)pp9-22
=HISTORY GRAPHIC LANGUAGE

Ambleretal92

Alan L Ambler & Margaret M Burnett & Betsy A Zimmerman
Operational Versus Definitional: A Perspective on Programming Paradigms
IEEE Computer v25n9(Sep 1992)pp28-43
=DEFINITION TECHNICAL LANGUAGES

AmblerS95

Scott Ambler
Reduce Development Costs with Use-Case Scenario Testing
Software Development Magazine(Jul 1995)pp 53-61
=DEMO USE-CASE SCENARIO TEST

AmblerS95a

Scott Ambler
Mapping Objects to Relational Databases
Software Development Magazine(Oct 1995)pp63+64+67+68+70+72+letter(Jan 1996)p13
=DEMO DATA ERDs OBJECT-ORIENTED
reply to letter "why no OODBMS": (1) security (2)no track record (3) no efficient support for SQL/reporting tools (3) one thing at a time

AmblerS96

Scott Ambler
An Ounce of Prevention: Class Type Architectures
Software Development Magazine(Mar 1996)pp 40??45-61
=DEMO WWW/NET ARCHITECTURE OBJECTs DATA MVC PERSISTENCE TECHNICAL SYSTEM INFORMATION HIDING
Compare with UML Boundary vs Control vs Entity
1. 0. No connection
2. 1. restricted flow
3. 2. Feedback: callbacks, dispatched objects
4. OOCRUD=OO create read update delete.
  system & persistence: wrap well defined technical features, so mostly code and debug
  Business: analysis, understand first
  Interface: prototyping... coding trivial


User	X	0	0	0
X	Interface	1	0	rare
0	0	0	Business	OOCRUD	some
0	0	0	0	Persistence	often
0	2	2	2	2	System

AmblerS96a

Scott Ambler
Object-Relational Mapping
Software Development Magazine V4n10(Oct 1996)pp47-50
=DEMO DATA OBJECT-ORIENTED
wrap db; encapsulate;classes drive data; obj IDs as keys only; joins of keys only; arbitrary obj keys; use a data dictionary; do not map to a legacy data base(unless it is in 3NF)

AmblerS97a

Scott Ambler
Normalizing Classes
Software Development V5n4(Apr 1997)pp69-72
=DEMO DATA OBJECT-ORIENTED
increasing cohesion and coupling by redesign but result is not in even 1NF in Codd terms.
Adds a repeating group of enrollments to seminar.
Better: Seminar<-<Enrollment>->Student and new Enrollment(seminar student) handles enrollments responsibillities for connecting seminars and students.
Note: ends up with SSADM composite logical design!

AmblerS97b

Scott Ambler
Implementing Pick Lists of Object
Software Development Magazine V5n6(Jun 1997)pp73-76
=DEMO USER DATA Flyweight?
ways to handle stable identified/enumerated objects without involving overheads of persistent storage. Example: The days of the week and the states in the USA. Class stores data on all instances and is different for each subclass.

AmblerS97c

Scott Ambler
The State Diagram
Software Development Magazine V5n5(May 1997)pp83-88
=DEMO STD/FSM GRAPHIC
accidentally illustrates RISKS of STDs by showing STD that allows an overdrawn account to become nonoverdrawn when a query is made and vice versa. Also requires a single deposit to finish overdrawn status.

AmblerS97d

Scott Ambler
The Various Uses for Use Cases
Software Development magazine V5n11(Nov 1997)pp69-71
SCENARIOS glossary(p70) <<uses>> <extends>>

AmblerS98

Scott Ambler
Evolving Class Diagrams
Software Development Magazine V6n5(May 1998)pp69-72
=DEMO LIFECYCLE OOA/OOD UML
need three linked class diagrams (1) behavior and names of business objects; (2) normalized data and design patterns; (3)implementation using Gang-of-four patterns

AmblerS99

Scott Ambler
Engineering Object-Oriented Requirements
Software Development Magazines V7n3(Mar 1999)pp55-56+58
=SURVEY of MODELs
CRC+User Interface+Use-Case+Business Rules+Activity+Deployment+Supplementary
Also: Interface-Flow++Physical Data+Sequence+Collaboration+State Chart+Technical

AmblerS99b

Scott Ambler
Architecting for Change
Software Development Magazine V7n5(May 1999)pp56-58
=DEMO DOCUMENTATION UML EVOLUTION
defines the <<Change Case>> stereotype to describe new potential requirements and modifications to existing requirements.

AmblerS99c

Scott Ambler
Distributed Object Design
Software Development Magazine V7n6(Jun 1999)pp34-36+38-40
=DEMO DOCUMENTATION UML WEB/NET
9_steps::=(add_non_business_classes; contracts; simplify; collobating_clusters; contracts; simplify_interfaces; map_onto_physical)

AmblerS99d

Scott Ambler
Persistence Modeling in the UML
Software Development Magazine V7n8(Aug 1999)pp54-57
=ADVERT proposal for DOCUMENTATION UML profile DATA MODEL
stereotypes include table, entity, view, primary index, secondary index, candidate key, oid, trigger
Why doesn't he use Qualifiers to indicate keys and indexes?

AmblerS99e

Scott W Ambler
Enterprise-Ready Object IDs
Software Development Magazine V7n12(Dec1999)pp56-57
=IDEA PERFORMANCE OBJECT-ORIENTED DISTRIBUTED TECHNICAL
HIGH-LOW Strategy: server allocates contiguous groups of IDs to processes that create persistent objects by sending high-order bits to processes while process assign low-order bits.
Letter: V8n2(Feb 2000)p12 from Jeff Senn corrects misunderstanding caused by Ambler looking at non-compliant code. Standard UUID (MS GUID) works at least as well.

AmblerS99f

Scott W Ambler
More process patterns: delivering large-scale systems using object technology
Cambridge U Press NY NY 1999 ISBN 0-521-65262-6
=HANDBOOK UML RUP PROCESS PATTERNS

AmblerS00

Scott W Ambler
new year's resolutions
Software Development Magazine V7n1 (Jan 2000)pp50-51
=ESSAY ETHICS
no harm, reuse, requirements, model, justifiable, no mantras, multiple views, more than performance, respect&work with users, realistic plans, communication skills, habitual learning, test everything, document everything, more to software than tech..

AmblerS00b

Scott W Ambler
Reuse Patterns and Antipatterns
Software Development V8n2(Feb 2000)pp26-27
=SURVEY tabulates and evaluates various EXPERIENCE REUSE PROCESS PATTERNS

AmblerS00c

Scott W Ambler
Crossing the Object-Data Divide: Parts 1 and 2
Software Development Magazine V8n3(Nov/Dec 2000)pp69-70 and V8n4(Apr 2000)pp66-69
=ESSAY PEOPLE OBJECT vs DATA

Ambler00d

Scott W Amber
The Unified Process Elaboration Phase
R&D Books 2000
=TEXTBOOK RUP

Ambler00e

Scott W Amber
Requirements Engineering Patterns
Software Development Magazine V8n5(May 2000)pp58-60
=ADVERT [Ambler00d]
Requirements first, Requirements as a stick, Requirements as a shield.

Ambler00f

Scott W Ambler
Enterprise JavaBean Persistence 101
Software Development Magazine V8n8(Aug 2000)pp51-52+54
=ADVERT TECHNICAL JAVA DATA PATTERN EJB
see [Pour00] [Larman00]
primary key is an object (with id and methods etc not just data) that identifies complete object.

Ambler00g

Scott Ambler
XML in the real world
Software Development Magazine V8n9(Sep 2000)pp59-60+62
=IDEA XML XSL SOAP SEMANTICS
Lack of semantics will be a problem. Needs experience and process to design DTDs.

Ambler00h

Scott Ambler
Enterprise Java-Bean Persistence 201
Software Development Magazine V8n9(Oct 2000)pp53-55
=TUTORIAL EJB 2.0 OBJECTS DATA

Ambler00i

Scott W Ambler
Extreme Modeling
Software Development Magazine V8n11(Nov 2000)pp61-62+64
=IDEA MODEL artefacts
p64. sidebar of XP resorces.

Ambler00j

Scott W Ambler
Reuse Through Internal Open Source
Software Development Magazine V8n12(Dec 2000)pp57+59
=ADVERT Osage =HOWTO
Resources [ http://www.opensource.org ] [ http://www.collab.net ] [ http://sourceforge.net ]
Osage::= See http://osage.opensource.org.
Internal open source focus on encouraging programmers to simply cooperate on producing high quality shared modules with minimal process but careful over-sight.

Ambler01a

scott W Ambler
Object Concurrency Control 101
Software Development Magazine V9n1(Jan 2001)pp57-58
=TUTORIAL SIMPLE NONSEQUENTIAL OBJECT DATA
None | optimistic | pessimistic.
pessimstic locks data. optimistic marks it to find out if another process has updated the data. collison resolution.

Ambler01b

Scott W Ambler
Designing Web-Based User Interfaces
Software Development Magazine V9n3(Mar 2001)pp61-63
=HOWTO WWW/NET USER COLOR LAYOUT HTML FORM
"Functional not flashy!"
Indicate what must be done, and what is optional on a form.

Ambler01c

Scott W Ambler
Debunking Modeling Myths
Software Development Magazine V9n8(Aug 2001)pp51-53 + letters V9n9(Sep 2001)p12
=ESSAY MODELING
Models are not documentation.
You can't think everything thru first.
Modeling can be light/agile
You don't have to freeze requirements.
Designs don't have to be cast in stone.
You don't need a CASE tool. Simple low tech do most models.
Modeling can improve productivity.
Models don't all revolve around data.
It takes time to learn how to model.

Ambler01d

Scott W Ambler
The Secret Life of Systems Operations
Software Development Magazine V9n10(Oct 2001)pp49-51
=REMINDER SYSTEM ADMIN

Ambler02

Scott Ambler
Easy Does it
Software Development Magazine V10n3(Mar 2002)pp53-55
=EXPERIENCE MODEL AGILE
Use the simplest tool.
Example: Develop on white board; take a digital snapshot, pass through image improving software through to OCR!
Whiteboard_Photo::gadget= See http://www.pixid.com.

Ambler02b

Scott W Ambler
Tools and Evidence
Software Development Magazine V10n5(May 2002)pp65-66
=IDEA AGILE MODEL CODE DOCUMENTATION LIFECYCLE UML
Need to rapidly record ideas. and some ideas need to be preserved.
Has a class diagram: source code contains comments that are a type of documentation. source code is modeled by models. Some models are in documents. Documents are a type of documentation.
Has a state chart showing the transitions between Ideas(I), temporary models(T), and permanent models(P) : Start--->I--abandon->end, I--model-->T--keep->P--discard->end, T--update->T, P--update->P, P--version->P, T--discard->end, P--make temporary->T.

Ambler02c

Scott W Ambler
Lessons in Agility from Internet-Based development
IEEE Software Magazine V19n2(Mar/Apr 2002)pp66-73
=EXPERIENCE AGILE MODEL WEB/NET PROCESS UML RUP HTML PEOPLE
Comparison of two companies. Finding the right amount of documentation and the right kind of model for a particular situation.
Tabulates principles and where they fitted experience. Lessons
2. People matter.
3. You don't need as much documentation as you think.
4. Communication is critical.
5. Modeling tools are not as useful as you think.
6. You need a wide variety of intellectual models.
7. Big up-front design was not needed.
8. Reuse the wheel. Don't reinvent it.

Ambler02d

Scott W Ambler
The Fragile Manifesto
Software Development Magazine V10n8(Aug 2002)pp50-51
=JOKE AGILE PROCESSES PEOPLE DOCUMENTATION USER TEAM
Ironic and twisted summary of [Ambler02c]

Ambler03

Scott W Ambler
Ten Steps to a Robust DB
Software Development Magazine V11n2(Feb 2003)pp42-43
=EXAMPLE DATA ERD EVOLUTION REFACTORING UML
Process:=verify need; choose best; data cleansing; write unit tests; deprecate old schema; implement change; update DBMS scripts; run tests; document; version control.
See list of ways to refactor a data base (like Replace Column,...) [ catalog.html ]
Example of UML documentation of changes({removal date=...} and <<trigger>>s

Ambler03b

Scott W Ambler
Agility 2013
Software Development Magazine V11n4(Apr 2003)pp46-47
=FORECAST AGILE XP CRAFT SKETCHES VISUAL IDEs COBOL

AmblerS04

Scott W Ambler
Agile Database Techniques: Effective Strategies for the Agile Software Developer
John Wiley & Sons 2004 ISBN 0-471-20283-5
=UNREAD AGILE DATA
Basis on the web at [ http://www.agiledata.org/ ]
(dick)|-how long does it take to add a new data item to an entity in a large existing database?

AmblerS04a

Scott W Ambler
Are Your Models Normal?
Software Development Magazine, Agile Modelling Newsletter (Dec 2004)
=IDEA DOCUMENTATION MODEL NORMALIZATION DRY
"record information as few times as possible, ideally only once."
artifact:="any item created during a software development project including code, model, document, plan, etc".
artifact_normalization::="placing information about systems in the best single artifact".
Generate views. Cross reference, links, and inclusions.
DITA::="Darwin Information Typing Architecture", XML based technical documentation, Parallel to single_sourced technical documentation, normalized data bases, and coherent modularization.
(dick)|-"Are there cross cutting concerns? Compare with Aspect oriented programming".
(dick)|- (meta-data): "Documentation is data about a system and should be treated as data".
Compare with POLL [LethbridgeSingerForward03]

Ambler03

Scott Ambler
Agile database techniques: effective strategies for the agile software developer
John Wiley NY NY 2003 ISBN 0471202835 CR 0502-0163
=HOWTO AGILE DATA REFACTOR NORMALIZE Object-Oriented
From [Amblers04] and [Amblers03]

Ambler05

Scott W Ambler
The Elements of UML2.0 Style
Cambridge UP 2005
=ADVERT UML AGILE STYLE
Nice book but Not always standard and sometimes apposed by standard

Ambler07

Scott Ambler
Calculating Documentation Cruft
Dr. Dobb's Agile Newsletter (27 Jul 2007)
=IDEA DOCUMENTATION METRIC CRUFT
CRUFT::percent= 100 - C * R * U * F * T where
- C:=The percentage of the document that is correct,
- R:=The chance that the document will read by the intended audience,
- U:=The percentage of the document that will be understood,
- F:=The chance that the material contained in the document will be followed,
- T:=The chance that the document will be trusted.
(dick)|-perhaps we could use Shannon Communication Theory to measure the capacity, equivocation, etc of a document in bits?

AmbriolaNotkin88

V ambriola & D Notkin
Reasoning About Interactive Systems
IEEE Trans Softw Eng SE-V14n2(Feb 1988)pp272-276
=THEORY LOGIC PROOF formal non-sequential

AmericaRutten91

P H M America & J J M M Rutten
A Parallel Object-Oriented Language: Design and Semantic Foundations
CWI(Centrum voor Wiskunde en Informatica) Tract V81 Centre for mathematics & computer science Amsterdam the Netherlands(Stichting Mathematisch Centrum) 1991
ISBN 90-6196-402-4 CR9310-0751 QA3.A583 no.81
=ADVERT LANGUAGE POOL
cf Frits W Vaandrager in [Baetan90]

Amsterdam02

Jonathon Amsterdam
Java's new Considered Harmful
Dr. Dobbs #335(Apr 2002)pp19-20+22+24+26
=PATTERNS creational JAVA factory methods and objects

AnandalingamLucas05

G Anandalingam & Henry C Lucas Jr
The Winners Curse in High Tech
IEEE Computer Magazine V38n3(Mar 2005)pp96-97
=ADVERT BOOK HISTORY TECHNOLOGY ECONOMICS
Companies often bid too much for a technology and get burned.
Advertyises OUP 2004 book "Beware the Winner's Curse: Victories that can sink you and your company".

Ananthaswamy11

Anil Ananthaswamy
I, algorithm
New Scientist V209n2797 (Jan 29 2011)pp28-31
=ADVERT =HISTORY AI LOGIC NEURAL NETS MARKOV BAYES PROBABILISTIC PROGRAMMING INFERENCE ENGINE LEARNING LANGUAGES BLOG Church
BLOG::language="Bayesian logic".
Demos of models with thousands of variables.
General algorithms are inefficient.
Applications: test ban treaty, PhysiScore(babies), QMR-DT
Ref [Pearl88]

AndasSjoberg05

Bente Anda & Dag I Sjoberg
Investigating the role of use cases in the construction of class diagrams
Empirical Software Engineering V10n3(Jul 2005)pp285-309 CR 0807-0688
=EXPERIMENT HOWTO DESIGN CLASS DIAGRAM USE CASE DOMAIN MODEL UML TOOLS Rose Tau
Experimented with students and then with professionals.
Compares two methods for going from usecases to design class diagrams: derivations vs validation.
derivation:= use_case_text->domain_model; sequence_diagrams; design_class_diagram.
validation:= use_case_text-> initial_class_diagram; sequence_diagrams; do( validate; extend).
Measured time, completeness, and quality (coupling and cohesion).
Tools didn't add to diagram quality with either students or professionals.
Tools slowed down students but not professionals.
Students got more complete design classes using validation rather than derivation.
Students got better quality designs with the derivation method.
Professionals -- no significant differences found.

AndaSjobergMockus09

Bente C D Anda & Dag I K Sjoberg & Audris Mockus
variability and reproducibility in software engineering: a study of four companies that developed the same system
IEEE Trans Software Engineering V35n3(May/Jun 2009)pp407-429
=EXPERIMENT COMPARISON QUALITIES OUTSOURCED USER CODE MAINTENANCE RELIABILITY COST ESTIMATES TIME PROCESS
Sent out call for bids -- 34 responses, 4 selected -- to develop a web application in Scandinavia. Prices range from 2k Euros to 70k Euros!
Many variables, no trustworthy hypotheses to test. Exploration.
Concluded that only the usability was similar between 4 competing projects. The reliability, time to produce, size, and maintainability all varied between companies. There was evidence of a trade off between price and quality.

Anderson94

Bruce Anderson<bruce@essex.ac.uk>
OOPSLA'93 Workshop Report Patterns: Building Blocks for Object-Oriented Architectures(27th sept 1993)
ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)pp47-49 [Alexander79]
=DEMO PATTERN Ticked Objects [Anderson94] [Johnson94] [Lea94]

Anderson95

Bruce Anderson<bruce@essex.ac.uk>
OOPSLA'94 Workshop Report Patterns: Building Organisational Competence in Software Architecture

Anderson99

Ross J Anderson
The Formal Verification of a Payment System
In [HincheyBowen99] pp43-52
=EXPERIENCE LOGIC BAN VERIFYING PROTOCOL BANKING PAYMENT SMARTCARD
Used BAN_logic with new rule:
If A believes that A and B share key K and A sees the K encrypts X then A will believe that B used K.
Colored proof covering several white boards.
System successful for several years with problems.
Concludes the it better to have a simple logic with few rules and no tool than a complex (buggy?) logic with a tool.

AndersonFleekGarityDrake01

Jean Anderson & Francis Fleek & Kathi Garity & Fred Drake
Integrating Usability Techniques into Software Development
IEEE Software Magazine V18n1(Jan/Feb 2000)pp46-53
=EXPERIENCE SIEMENS HEALTH USER PEOPLE RUP workflow iteration
Early user improves quality and eliminates rework.
Organizational and cultural change is the important challenge. [ConstantineLockwood99]

Andersonetal96

Richard J Anderson & Paul Beame & Steve Burns & William Chaan & Francesmary Modugno & David Notkin & Jon D Reese
Model Checking Large Software Specifications
Proc 4th ACM SIGSOFT 1996 Symp on the Foundns of Software Eng: ACM SIGSEN V21n6(Nov 1996)pp156-166
=DEMO V&V SPECIFICATIONS TOOL use Binary Decision Diagrams(BDDs) 200Mgbs!

AndersonGouda91

James H Anderson & Mohamed G Gouda
A new explanation of the glitch phenomena
Acta Informatica V28f4(Apr 1991)pp287-310
=THEORY NONSEQUENTIAL all arbiters have both infinite delays and multiple changes in the values of outputs.

AndersonHansenLowrySummers06

Bonnie Brinton Anderson & James V Hansen & Paul Benjamin Lowry & Scott L Summers
The application of model checking for secure E-commerce transactions
Commun ACM V49n6(Jun 2006)pp97-101
=EXAMPLE V&V ECOMMERCE PROTOCOLS MODEL CHECKING RISKS
Given the complexity of ECommerce systems and protocols plus the risks of failure, the protocols should be checked prior to implementation.

AndersonRepsTeitelbaum03

Paul Anderson & Thomas Reps & Tim Teitelbaum
Design and implementation of a fine-grained software inspection tool
IEEE Trans Software Engineering V29n8(Aug 2003)pp721-733
=ADVERT V&V CODE INSPECTION C TOOL CodeSurfer(TM) TECHNICAL SLICES CHOPS HYPERTEXT VIEWS

AndersonShapiro89

RH Anderson & NZ Shapiro
Beyond User Friendly: Easy To...
EDUCOM Review v24 n3(Fall 1989) p50-54
=ESSAY USER

AnderssonGreenspunGrumet06

Eve Andersson & Philip Greenspun & Andrew Grumet
Software Engineering for Internet Applications
MIT Press Cambridge MA 2006 ISBN 0262511916 CR 0712-1164

AnderssonRuneson07

Carina Andersson & Per Runeson
A replicated quantitative analysis of Fault distributions is complex software systems
IEEE Trans Software Engineering V33n5(May 2007)pp273-286
=EXPERIENCES ANALYSIS SIZE MODULES RELIABILITY
Repeats [FentonOhlsson00].
Few modules contain most faults - pre & post release.
Fault densities are similar in similar environments.

Andexer01

Jens Andexer
Design Guidelines and Documentation Paradigms for Object Oriented Programs
SERG Report 397 (Sep 2001)P422,, McMasters [ serg.publications.html ]
=SURVEY EVOLUTION OBJECT_ORIENTED

AndleighGretzinger92

Prabhat K Andleigh & Michael R Gretzinger
Distributed Object-oriented Data-systems Design
Prentice Hall Englewood Cliffs NJ 1992 ISBN 0-13-174913-7 CR9309-0658
=SURVEY METHODS OBEJCT-ORIENTED DATA DESIGN
Review: Frame-object analysis combines features of earlier systems analysis methods with the newer object-oriented concepts. survey 5 well known (but not Coad)...

Andreetal81

Andre & Banatre & Routeau
A Multi-processing Approach to Compile-Time Symbol Resolution
ACM TOPLAS v3n1(Jan 1981)pp11-23
=DEMO DDD Clash

Andrews93

James H Andrews
Logic Programming: Operational Semantics & Proof Theory
Cambridge University Press NY NY 1993 ISBN 0-521-43219-7 CR9503-0142
=THEORY LANGUAGES

AndrewsP03

Pater B Andrews
Introduction to Mathematical Logic and Type Theory: to truth through proof
Kluwer Acad Pub Norwell MA 2002 ISBN 1402007639 CR 0305-0427
=THEORY LOGIC TYPES LAMBDA PEANO

AndrewsLeventhal93

Dorine C Andrews & Namoi S Leventhal
FUSION: Integrating IE, CASE and JAD: a handbook for reengineering the systems organisation
Prentice Hall Englewood Cliffs NJ 1993 ISBN 0-13-325333-3 CR9308-0568
=HANDBOOK CASE USER

AndrewsZhang03

James Andrews & Yinqjun Zhang
General Test Result Checking with Log File Analysis
IEEE Trans Software Engineering V29n7(Jul 2003)pp634-648
=EXPERIMENT RANDOM TESTING LOG TIMED FSM LFA lift language LFAL Prolog dictionary ADT
SUT::="Software Under Test".
LFA::="Log file analysis"..

Andriole94

Steve Andriole
Fast Cheap Requirements: Prototype or Else
IEEE Software magazine v11n2(Mar 1994)pp85-87
=ADVERT PROTOTYPE REQUIREMENTs

Andriole95

Stephen J Andriole(CIGNA)
Debatable Developent: What should we believe?
IEEE Software Magazine V12n4(Jun 1995)pp13-18
=ESSAY THEORY vs PRACTICE METHODS
p13: "There is an enormous disconnection between what academicians and consultants think will revolutionize development and what actually works in the trenches. We have much to learn about what really works
what works a little
and what does not work at all." [AndrioleMonsanto95]

AndrioleMonsanto95

Stephen J Andriole(<andriole@cigna.e-mail.com> & Charlton A Monsanto<mnsanca@duvm.ocs.drexel.edu>
Interactive Collaborative Requirements Management
Software Development(Sep 1995)pp35-40
=DEMO Do-It-Yourself TOOL REQUIREMENTS VISUALBASIC
Requirements: Its easier and cheaper to use a set of simple tools and templates (flowcharters databases ... prototypers) under the control of a Visual Basic workbench than even Integrated CASE tools

Anguela09

Andrew Anguelo
Software Methodology Wars (Viewpoint)
IEEE Computer Society Career Watch Mailing list (Mar 2009) [ vp4 ]
=ESSAY PROCESS METHODS DEVELOPMENT vs ENGINEERING ONE-SIZE ECONOMICS SHORT-TERM vs LONG_TERM
Quote
Net
(End of Net)
(dick)|-Ignores the claim that refactoring software can maintain the quality of software.

AniRedmiles09

Ban Al-Ani & David Redmiles
Trust in distributed teams: support through continuous coordination
IEEE Software Magazine V26n6(Nov/Dec 2009)pp35-40
=SURVEY TEAMS TRUST =ADVERT Palantir Ariadne World View Workspace Activity Viewer
Finds that leadership and time promote trust but diversity, size, and project type have a negative effect.
Argues that tools that make other peoples work visible to the team should promote trust.

Anon(HOS)84

Product brochure
Building Systems with USE.IT
Higher Order Software Inc. 1984 (2067 Massuchusetts Ave Cambridges MA 02140)
=ADVERT TOOL METHOD

Anon90

Anonymous but verified letter
IEEE Software Magazine V7n1(Mar 1990)p4
=LETTER whistleblowing engineering RISKS

Anon10

Anonymous Reporter
No Catastrophes Please, It's Software Modelling
ICT Results (01/28/10) [ index.cfm?section=news&tpl=article&ID=91135 ]
=ADVERT TRT MDE TOOL MODEPLEX MODEL Driven Engineering
Thales Research and Technology (TRT) researchers have created a development platform that enables applications to tackle the increasing complexity of modern computer systems.
MDE::=Model driven engineering.
lifecycle of development, including interoperability, substitutability, and traceability.
required functions related to the industry-specific domain.
design refers to real-world functions rather than algorithms...

ANSI/IEEE87

IEEE Computer Society
ANSI/IEEE Software Engineering Standards
IEEE/John Wiley 1987
=STANDARD lifecycle Technical

ANSI/IEEE90

IEEE Computer Society
IEEE Standard Glossary of Software Engineering Engineering Terminology(ANSI/IEEE Std. 610.12-1990)
IEEE Piscataway NJ
=STANDARD GLOSSARY
software_engineering::="The application of systematic, disciplined, quantifiable approach to the development, operation and maintenance of software; that is the application of engineering to software."

ANSI83ADA

ANSI
American National Standard for the programming language ADA
Washington DC Jan/Feb 1983
=STANDARD Ada LRM LANGUAGE

Anthes11

Gary Anthes
Nonlinear systems made easier
Commun ACM V54n1(Jan 2011)pp17-19 [ 1866739.1866745 ]
=ADVERT MATHEMATICS PROOFS NONLINEAR SYSTEMS CONVEXITY SEMIDEFINITE SUM-OF-SQUARES SOS Schor
Pablo Parrilo's method bounds nonlinear systems.
Used by Intel to prove design of floating point hardware.
Refs on page 19.
PariloSturmfels 2001 [ 0103170 ] Better method for finding minimal values/lower bounds for polynomial functions.

AntonPotts03

Annie I Anton & Colin Potts
Functional Paleontology: The evolution of User-Visible System services
IEEE Trans Software Engineering V29n2(Feb 2003)pp151-166
=EMPIRICAL HISTORY PURPOSE QUALITY REALITY EVOLUTION 50-years domestic telephones
Lehman's theory of E-systems that co-evolve with there environment implies that understanding environment change should proceed architectural design.
Systems vs services. Systems provide both benefits and burdens. A dialectic process.
Functional_Morphology::=profile of benefits and burdens at a given point.
Analyzed 1950-1999 adverts in Atlanta Telephone directories.
Evidence of punctuated evolution, expansion followed by retrenchment, growth from core outward, caller benefits first, object-level precedes meta-level.

AntoniolCanforaCasazzaLuciaMerlo02

Giuliano Antoniol & Gerardo Canfora & Gerardo Casazza & Andrea De Lucia & Ettore Merlo
Recovering Traceability Links between Code and Documentation
IEEE Trans Software Engineering V28n10(Oct 2002)pp970-983
=CASESTUDY IR PROBABILITY VECTOR-SPACE TRACEABILITY LIFE-CYCLE
2 methods: one uses Bayes and frequencies. the other a vector space with distance/similarity formula/metric.
Both are better than grep. Both can achieve 100% recall of all relevant.
Probability based figures help teams trace code back to documentation.
Probability gets better when 100% recall is needed.. Vector calculations are easier.

AntoniolEtal04

Giulano Antoniol & Aniello Cimitile & Guisepe A Di Lucca & Massimliano Di Penta
Assessing Staffing Needs for a Software Maintenance Project through Queuing simulation
IEEE Trans Software Engineering V30n1(Jan 2004)pp43-58
=EXPERIENCE PROCESS ESTIMATION QUEUES SIMULATION EVOLUTION PEOPLE COBOL/JCL Y2K QUEUEING THEORY
Assumed that Brooks law did not hold for Y2K. Future: conversion to euro, new euro-phone numbers.
QUEUE:Stochastic_System=Net{ interarrival, service:Distribution, number_of_servers:Nat=1, capacity:Nat=oo, discipline:Discipline=FIFO}.
Distribution:={Markovian, Deterministic, Erlang[k], General}.
Erlang[1]:=exponential.
Case study used QUEUE(M,G,m) model.
Lessons earned: simulating queuing models helped predict staffing needs and do what-ifs for team size and rework rates.
But need daily figures (not weekly!).
Not steady state: start up and close down phase are 30%of whole.
Queuing simulation tends to overestimate needs and so minimizes risk of over run.

AntoniolGueheneuc06

Giuliano Antoniol & Yann-Gael Gueheneuc
Feature Identification: an epidemiological metaphor
IEEE Trans Software Engineering V32n9(Sep 2006)pp625-641
=DEMO MAINTENANCE TECHNICALREVERSE ENGINEERING TOOL CODE MODULE ANALYSIS
A way to find out, by executing software the parts used to implement a feature.

Antoniou99

Grigoris Antoniou
A Tutorial on Default Logics
ACM ACM Computing Surveys V31n4(Dec 1999) pp337-359 CR0006-0401
=TUTORIAL FORMAL LOGIC DEFAULT INFERENCE EXCEPTIONS
default :=if Prereq : Justifications then Consequent, if Prereq then Consequent unless Justifications is known to be false where no free variables in parts.
default schema has free variables - stands for all substitutions.
normal: if P : J then J
closed world : if true : not A then not A
Not just inferences but also extensions of sets known facts by applying defaults that don't lead to contradictions

AntoyGannon94

Sergio Antoy & John Gannon
Using Term Rewriting to Verify Software
IEEE Trans on Software Eng VSE-20n4(Apr 1994)pp259-274
=THEORY MATHEMATICAL PROOF PROGRAM
1. p263: Ada - lack of means to annotate and verify semantic properties of elements in a package. Uaing the idea of a monoid of program functions.
2. p264: Specifying a C++ class by relationships between its operations member functions) and showing their completeness.
3. p265: Definition of subtyping (cf Liskov) includes annotated properties... but no representation function. TermRewritingSystems, Confluence Church-Rosser. Termination/Noetherian. Both gives cannonical or convergent or complete TRS. (see Wechler 1992) Ask specifiers to specs as a cannonical TRS.
4. hence overspecification(superposition algorithm Leavens 1991)and underspecification(another algorithm...)
5. pp266..267:Cannot compute confluence and termination. Hence strategies for ensuring them.
6. pp267..: Proving theorems: difficult, neeed tool to help.
7. p271 problems with module interconnections...

AntoyHamlet00

Sergio Antoy & Dick Hamlet
Automatically checking an implementation against its Formal Specification
IEEE Trans Software Eng V26n1(Jan 2000)pp55-69
=DEMO THEORY TEST SQA EXPERIMENT JAVA

AntoyHanus10

Sergio Antoy & Michael Hanus
Functional Logic Programming
Commun ACM V53n4(Apr 2010)pp74- 95 [ 1721654.1721675 ]
=ADVERT CURRY LANGUAGE FUNCTIONAL LOGIC PROGRAMMING
Combines ideas from functional programming (LISP, ML, Haskell) and Logic Programming (Prolog).
Given a definition of a function Curry can sometimes invert it, finding argument values to fit given results.

AnvikMurphy11

John Anvik & Gail C Murphy
Reducing the effort of bug report triage: recommenders for development-oriented decisions
ACM TOSEM Trans Software Eng & Methodology V20n3(Aug 2011)#10.1-35 [ 2000791.2000794 ] CR 12-3-0286
=TYPE BUGS ISSUES TRIAGE AI RECOMMENDERS BUGZILLA BUG TRACKING BUG REPOSITORY ISSUE TRACKING
Interesting statistics.
Regular expressions modeling triage scenarios/life histories.
AI tuned on open source projects. Shows a 75% accuracy.

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
1. To reduce development cycle (time for a release).
2. 10^6 lines of code 3 months/cycle.
3. Higher risks and so more careful management
4. helps expose problems in process
5. Requires at least a repeatable process maturity.
6. 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"
7. p50:"traditional models focus on a single sequence of [...]; concurrent[...] focusses on the concurrent execution of multiple processes"
8. Uncovering interactions between parallel requirements+designs by intensive review and inspection + management focus on decoupling requirements
9. Interactions between implementations use configuration management. + integration focussed testing
10. Special team from teams: define process, manage products, co-ordinate, develop management technique, plan, specify, and develop software-engineering environments and coordinate with research.

Aoyamaetal89

Mikio Aoyama & K Miyamoto & N Murakama & H Nagano & Y Oki
Design Specification in Japan: Tree Structured Charts
IEEE Software Magazine v6n2(Mar 1989)pp31-37
=ADVERT graphic YAC

ApelLeachSaake08

Sven Apel & Thomas Leach & Gunter Saake
Aspectual Feature Modules
IEEE Trans Software Engineering V34n2(Mar/Apr 2008)pp162-180
=DEMO FEATURES FOP + ASPECTS AOP ITERATION PRODUCT LINES AFM
AFM::="Aspectual Feature Module", combines iterative Feature Oriented Programming (FOP) with Aspect Oriented Programming(AOP).

AppelbeAbowd95

Bill Appelbe <bill@cc.gatech.edu> & Gregory Abowd<abowd@cc.gatech.edu>
Beyond Objects: A Response
ACM SIGSOFT Software Engineering Notes V20n3(Jul 1995)pp
=ESSAY

Apt88

Krzysztof R Apt
Proving Correctness of Concurrent Programs: A Quick Introduction
Chapter 7 (pp305-345) of Borger88
=THEORY NONSEQUENTIAL CORRECTNESS PROOF

Aptetal80

Krzysztof R Apt & Francez & De Roever
A Proof System for Communicating Sequential Processes
ACM TOPLAS V2n3(Jul 1980)pp359-385
=THEORY LOGIC CSP formal

ApvrilleEtal04

Ludovic Apvrille & Jean-PIere Courtat & Christophe Lohr & Pierre de Saqui-Sannes
TURTLE: A Real-Time UML Profile Supported by a Formal Validation Tool
IEEE Trans Software Engineering V30n7(Jul 2004)pp473-487
=TYPE REALTIME MODEL V&V UML1.5 PROFILE TCLASSES TTOOL RT-LOTOS RTL
Notes

Arango95

Guillermo Arango(arango@austin.sar.slb.com)
Software reusability and the Internet [SamadzadehZand95] pp22-23

Arangoetal86

Guillermo Arango & Ira Baxter & Peter Freeman & Christopher Pidgeon(all at UCI)
TMM: Software Maintenance by Transformation
IEEE Software Magazine V3n3(May 1986)pp27-39
=ADVERT for Draco based: make abstraction before porting using domain specific thingies

Aranow89

Eric Aranow
Full Lifecycle CASE: Views from the Tower of Babel
System Builder (Oct/Nov 1989)
=REPORT CASE tools process
Pictures of three different life cycles: "waterfall", "Rapid Iterative Prototyping", "Iterative redefinition and redesign".
Does not describe the idea of implementing part of the system first to refine and elicit requirements.

Aranow92

Eric Aranow
Object Technology Means Object-Oriented Thinking
Software Magazine (Mar 1992)
The baggage of the structured techniques - concentrate on the up-front analysis to get our class hierarchies properly defined

ArbaughFithenMcHugh00

William A Arbaugh & William L Fithen & John McHugh
Windows of Vulnerability: A Case study Analysis
IEEE Computer Magazine V33n12(Dec 2000)pp52-5
=ANALYSIS CERT Exploits IMAP phf BIND 1996-1999
Three buffer-overflow magnitude and one miss-out mistake.
Automating a vulnerability (not disclosing it) allows many more intrusions.
Systems are not being managed well: Nearly all intrusions could have been halted if known precautions installed.

Arbib64

Michael Arbib
Brains Machines & Mathematics
USA McGraw Hill 1964
=TEXT cybernetics theory FSM Finite State Machines neural networks information theory Turing Machines Regular expressions

Arbib68

Michael A. Arbib (ed) & K Krohn & J L. Rhodes
Algebraic Theory of Machines Languages & Semigroups
Academic Press New York 1968
=TEXT topology

ArblasterSimeGreen

?? Arblaster & ?? Sime && ?? Green
Jumping to Some Purpose
Comp Jnl v22 n2 (May 1979) pp105-109
=EXPERIEMNT sequential Technical

ArdagnaPernici07

Danilo Ardagna & Barbara Pernici
Adaptive Service Composition in Flexible Processes
IEEE Trans Software Engineering V33n6(Jun 2007)pp369-384
=EXPERIMENT ANNOTATED MODEL SERVICE QUALITIES PERFORMANCE OPTIMIZATION QoS MAIS BPEL UML XML MILP
Given a process that has many steps and includes loops and branches, and each elementary step can be carried out by several rival "concrete" services.... what is the optimum selection of services to complete task?
Given the same process that is partly complete.... what is the optimum way to complete the process.
If the optimal solution is not good enough... how to negotiate a better one.
MAIS::="MultiChannel Information Systems" project, [ http://www.mais-project.it ]
MILP::model="Mixed Integer Linear Programming".
Qualities = { Price, Reputation, Execution_time, availability, data_quality}.
Experiments suggest the algorithms work and are feasible.
See [ArdagnaEtAl11]

ArdagnaEtAl11

Danilo Ardagna & Luciano Baresi & Sara Comai & Barbara Pernici & Marco Comuzzi
A service-based framework for flexible business processes
IEEE Software Magazine V27n6(Mar/Apr 2011)pp61-67
=ADVERT LANGUAGE TOOL SERVICE ORIENTED QUALITIES WEB/NET BUSINESS PROCESS BPMN CASE UDDI QoS Discorso
ALso see [ArdagnaPernici07]

Ardisetal96

Mark A Ardis & John A Chaves & Lalita Jategaonker Jagadeesan & Peter Mataga & Carlos Puchol & Mark G StasKauskas & James Von Olnhausen
A Framework for Evaluating Specification Methods for Reactive Systems: Experience Report
IEEE Trans Softw Eng VSE22N6(Jun 1996)pp378-389 revised from ICSE-17 1995
=COMPARISON Modechart VFSM Esterel LOTOS Z SDL C telecommunications; SDL and Esterel scored well
methods uncovered dangerous ambiguity in an informally stated standard

ArdisMataga99

Mark Ardis & Pete Mataga
Formal Methods Through Domain engineering
In [HincheyBowen99] pp315-328
=EXPERIENCE FAST PROCESS DOMAIN technology transfer 5ESS Lucent
Recommends an evolutionary, incremental, introduction of formal methods, that follows informal Domain analysis to identify useful abstractions.
FAST::Process="Family-Oriented Abstraction, Specification, and Translation".

Arjomandietal83

Arjomandi & Fischer & Lynch
Efficiency of Synchronous Versus Asynchronous Distributed Systems
Jnl ACM V30n3(Jul 1983)pp449-456
=THEORY non-sequential optimization

Arnold94

Robert S Arnold
Software ReEngineering: A Quick History
Comm ACM V37n5(May 1994)pp13-14
=HISTORY maintenance

ArnoldK94

Ken Arnold
Class Design for Inheritance
UNIX Review V12n7(Jul 1994)pp67-72
=ARTICLE DESIGN OBJECT-ORIENTED
1. Liskov, Anything possible to/true of a B is possible to/true of an A as well
  A is_a_kind_of B that does V in a special way
2. class B...{ virtual... V (....)=0 }
3. class A: public B{..virtual... V (....){...}..}
  A has_a B class A:... { ... B name; ...} A refers_to_a B class A:...{ B* name; ...} A implemented_using B class A: private B {....} Don't!
4. class A: protected B{....} Don't!
  A is_like_a B For some C, A and B come from a template C

ArnoldTFuson94

Thomas R Arnold & William A Fuson
Testing "In A Perfect World"
Commun ACM V37n9(Sep 1994)pp78-86(in Binder94)
=ESSAY NONSEQUENTIAL OBJECTS SQA

ArnoutMeyer03

Karine Arnout & Bertrand Meyer
Uncovering Hidden Contracts: The .NET Example
IEEE Computer Magazine V36n11(Nov 2003)pp48-
=CASE-STUDY CONTRACTS ASSERTIONS ..NET LIBRARY META-DATA TOOL
In ARRAY_LIST 62% of routines have implicit contracts hidden in the meta-data.

AroraGouda93

Anish Arora & Mohamed Gouda
Closure and Convergence: A Foundation for Fault-Tolerant Computing
IEEE Trans on Software Eng VSE-19n11(Nov 1993)pp1015-1027
=THEORY guarded commands formal reliability

Arce02

Ivan Arce
Bug Hunting: The Seven Ways of the Security Samurai
IEEE Computer Magazine Security & Privacy supplement V35(Mar/Apr 2002)pp11-15
=EXPERIENCE BUGS SECURITY QUALITY RISKS
Lists security bug myths in a sidebar p12. Bug hunting takes time and understanding all the implications takes longer.
Lists samples of security bugs in a sidebar p13
The seven ways: audit, debuggers and disassemble, network traffic analysis, blackbox tests, brute force, top-down analysis, such the Internet.
Methods: lone ranger, timeboxed peer audit, assembly line, rotating teams.

Argent-KatwalaBradleyDingle04

Ashok Argent-Katwala & Jeremy T Bradley & Nicholas J Dingle
Expressing Performance Requirements using Regular Expressions to specify stochastic probes over process algebra models
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp49-58
=DEMO Performance Regular Expressions stochastic process algebra PEPA TOOL ipc/DNAmaca

Ariely09

Dan Ariely
Predictably Irrational: The Hidden Forces That Shape Our Decisions
Harper Collins NY NY 2009
=POPULARIZATION =EXPERIMENTS PEOPLE PSYCHOLOGY FALLACIES MARKETING BEHAVIORAL ECONOMICS
Web site [ http://www.predictablyirrational.com/ ]
We are all a lot less rational than standard economics assumes.
Online Outline [ Predictably-Irrational ]
Examples
1. A third option can makes us choose the worse alternative. cf Arrow's Theorem.
2. Price is often determined by habit not supply and demand. By thinking about a price we start to select a price.
3. The word "Free" helps us spend more money.
4. We will buy things or do things because of others not just money -- social norms.
5. Social norms can get more work done than money -- Open Source.
6. Arousal changes things. More than we expect.
7. Procrastination -- teachers should impose deadlines.
8. We overprice what we have -- cognitive dissonance strikes again.
9. We will waste time and money to keep our options open.
10. Expectations color our perceptions. Stereotypes!
11. Higher cost makes medicine etc. work better. Placebo effect.
12. We don't like to cheat but still cheat a little bit. We are more honest about cash than things.
13. Making public choices can make you choose differently (in the USA) or in conformity(Hong Kong).
(dick)|-Maslow!

AriesEtal02

James A Aries & Subhankar Bannerjee & Marc S Brittan & Eric Dillion & Janusz S Kowalik & John P Lixvar
Capacity and Performance Analysis of Distributed Enterprise Systems
Commun ACM V45n6(Jun 2002)pp100-105
=EXPERIENCE Boeing RE-ENGINEERING TUNING PERFORMANCE large scaling client-server net SIMULATION
Need to monitor what is going on. Need model of workload characteristics. Load testing. Need model of system.
Mathematical and analytical models. Trading off time to solve vs accuracy of predictions.

ArinzeAnandarajan03

Bay Arinze & Murugan Anandarajan
A Framework for Using Object-Oriented mapping methods to rapidly configure ERP Systems
Commun ACM V46n2(Feb 2003)pp61-65
=ADVERT EOM Object-Oriented ERP
EOM::="Enterprise Object Model".

ArisholmBriandFoyen04

Erik Arisholm & Lionel C Briand & Auden Fvyen
Dynamic Coupling Measurement for Object-Oriented Software
IEEE Trans Software Engineering V30n8(Aug 2004)pp491-506
=CASESTUDY DYNAMIC RUNTIME Java COUPLING METRICS TOOL JDissect Notes interaction of inheritance and message passing: the object-level coupling is determined at runtime but class-level is static (and different).
Figure 2, p494 is UML Metamodel of classes, methods, objects, etc.. Studied Velocity open source in Apache Jakarta Project. 17 versions 408 class es, 17KLOC, 65 inheritance relation, 149 methods overridden.
Average dynamic import and export couplings are always equal. Principle components confirm that dynamic coupling is not correlated with stat ic metrics.
Regression of change proneness on SLOC and each proposed metric.
|-the dynamic export coupling metrics predict change proneness.
Similar to work done on Smalltalk.
Export coupling occurs when one method is called by another one.
Changes come from calls

ArisholmBriandHoveLabiche06

Erik Arisholm & Lionel C Briand & Siw Elisabeth Hove & Yvan Labiche
The impact of UML Documentation on Software Maintenance: an Experimental Evaluation
IEEE Trans Software Engineering V32n6(Jun 2006)pp365-381
=EXPERIMENT UML MAINTENANCE DOCUMENTATION TOOLS TAO Visio Java Oslo Ottawa
UML documentation helps students to correctly make complex changes in code.
It helps students make complex changers faster but the total time (including updating the diagrams was longer.
Some students who had no UML docs drew their own on difficult tasks.
Some students given UML ignored it on some tasks.
Students without the UML docs where more likely to say that they were out of practice with Java and had problems grasping the whole picture.
Previous experiment [ ArisholmSjoberg04 ]

ArisholmSjoberg04

Erik Arisholm & Dag I J Sjoberg
Evaluating the Effect of a delegate versus centralized Control Style on the maintainability of Object-Oriented Software
IEEE Trans Software Engineering V30n8(Aug 2004)pp521-534
=EXPERIMENT EVOLUTION MAINTENANCE Object-Oriented MODULES Expert REALITY vs novice Java SESE RDD Responsibility GLM ANOVA
Comparison of the correctness and effort for maintaining two OO designs for the Coffee-Machine problem from OOPSLA'97 OO. Compared consultants(3 levels: junior, intermediate, senior) and Students(Ugrad vs Grad).
Two designs: one centralizes most of the responsibilities into a FrontPanel object. The decentralized design models ideas like product, ingredient, recipe and spreads the functionality over 12 modules.
Overall correctness on 4 tasks: 59%, correctness increases with expertise, centralized(69%) done correctly more often than decentralized(50%)!
Effort drops with expertise for students, but for consultants the effort on decentralized design drops with expertise and increases for the centralized.

ArisholmEtAl07

Erik Arisholm & Hans Gallis & Tore Dyba & Dag I K Sjoberg
Evaluating Pair Programming with respect to System Complexity and Progrmmer Expertise
IEEE Trans Software Engineering V33n2(Jan 2007)pp65-86
=EXPERIMENT TECHNICAL MAINTENANCE PAIR PROGRAMMING EXPERTISE STYLE Java
Well designed experiment testes whether pairs are more productive than programmers working alone.
Based on previously used experimental code [ ArisholmSjoberg04 ]
On average there is a slight bdecrease in the time and an increase in the likelihood of a correct fix -- but the effort(2 people vs 1person) is 80% higher.
With less experienced programmers pairs are 70%more likely to produce correct code it takes them a little longer.
Intermediate programmers get the best reduction in time 30%.
Experience programmers produce less correct code but do bit a little faster.
All these effects are moderated as the code switches style from a centralized control design to a distributed control Object-Oriented design.

ArlowNeustadt04

J Arlow & I Neustadt
Enterprise patterns and MDA: Building Better Software with Archetype Patterns and UML
Addison Wesley Longman Publishing Co, Inc., Redwood City, CA, 2003. CR 0412-1461.
=HANDBOOK COMMERCIAL ORGANISATION LITERATE UML MODELS MDA PCL archetype pleomorph
MDA::OMG="Model Driven Architecture", using tools to convert models directly to code.
PCL::=" Pattern Configuration Language".
archetype::= "a class, attribute, operation, or relationship that appears in many applications"
ArlowNeustadt04_pattern::= "A collection of collaborating archetypes", optional parts shown by the <<o>> stereotype. Names: Party, Party relationship, Customer Relations Management(CRM), Product, Inventory, Order, Quantity, Money, Rule.
pleomorph::= " distinct patterns of archetypes in different enterprises".

Armour00

Phillip G Armour
The Case for a new business model
Commun ACM V43n8(Aug 2000)pp11-22
=IDEA software is a medium for storing DATA
5_media:=(DNA, brains, hardware/tools, books, software).
We need paraphrenalia to allow us to embed knowledge in software so that it can be changed and used.
workplace and process should help acquire knowledge.
1. domain knowledge, 2. how to acquire knowledge, 3. how to structure it for embedding in software. Most developers will not need knowledge of software itself.
failure also leads to knowledge
account for knowledge as an asset

Armour00b

Phillip G Armour
The Five Orders of Ignorance
Commun ACM V43n10(Oct 2000)pp17-20
=ESSAY TECHNICAL CODE contains KNOWLEDGE PROCESSES METHODS
Tight hacked code does not contain disproven ex-knowlege.
For n:0..4, n.OI := n.th Order Ignorance.
0.OI = demonstrable knowledge.
1.OI = Know that I don't know.
2.OI = I don't Know that I don't know.
3.OI = I don't know how to uncover 2.OI.
4.OI = I don't know about the OI.
Methods and processes give usxquestions not answers.

Armour01

Phillip G Armour
The Laws of Software Process
Commun ACM V44n1(Jan 2001)pp15-
=ESSAY PROCESSES CMM IGNORANCE
5 orders of ignorance [Armour00b]
Why developing processes is difficult.
One size doesn't fit all. Fit process to situation. Experimental lab areas. Term limits. Measure value.

Armour01b

Phillip G Armour
Matching Process to Types of Teams
Commun ACM V44n7(Jul 2001)pp21-23
=ESSAY ONESIZE PROCESS TEAM PEOPLE
One size does not fit all -- a creative team does not want a repeatable product!
Four kinds of team:=( tactical, problem-solving, creative, Learning).
Use "orders of Ignorance".. [Armour00b]

Armour02

Phillip G Armour
The Spiritual Life of Projects
Commun ACM V45n1(Jan 2002)pp11-14
=ESSAY PEOPLE MANAGEMENT TEAM
(FatherJim)|-4 components of humanity: physical, intellectual, emotional and spiritual.
need: explicit or implicit code of conduct, higher purpose, contributing values to someone's life, morale, mutual support, leadership by creating an environment where people do their best, caring for weaker members of the team.

Armour02b

Phillip G Armour
Ten Unmyths of Project estimation
Commun ACM V45n11(Nov 2002)pp15-18
=ESSAY ESTIMATION QUALITIES
|-What we don't know is a major source of error in estimation and defects in code.
|-Sometimes we don't even know that we are missing knowledge.
|-Estimates are inaccurate.
|-don't estimate dates: estimate the probability of an event by that date.
|-estimates are not commitments.
|-time is only roughly defendant on size.
|-Historical data may be the best data, but it is not good enough to predict productivity.
|-Productivity works for buildings and things but not for knowledge.
|-LOC/FP does not measure knowledge we don't have.
|-Brook's Law.
|-No amount of resources can guarantee absence of defects.

Armour04

Phillip Armour
When Executives Code
Commun ACM V47n1(Jan 2004)pp19-22
=EXPERIENCE PEOPLE vs PRACTICE MANAGEMENT
Executives on a 3 day course behave like amateur programmers on a programming project and emerge sadder but wiser.
The course project included unexpected system failure, unrealistic deadlines, and deliberately intrusive management.
Executives lost track of the goals of the project in the joys of hacking code!
Never produced working system.

Armour04a

Phillip G Armour
Not-Defect: the Mature Discipline of Testing
Commun ACM V47n10(Oct 2004)pp15-18
=ESSAY TESTING IGNORANCE
Testing is about discovering what we don't know.

Armour03

Phillip G Armour
The laws of Software Process: A New model for the production and management of software
Auerbach Boston MA 2003 ISBN 0849314895 CR 0502-0217
=THEORY IGNORANCE PEOPLE METHODS
Software development as a process of discovering and recording knowledge.
Based on .Lookup Armour

Armour06

Phillip G Armour
Counting Boulders and Measuring Mountains
Commun ACM V49n1(Jan 2006)pp17-20
=ANALOGY ESTIMATION PLANNING Project Management WBS COCOMO SLIM-Estimate Everest
Argues that you don't get a good estimate of the size of a mountain by estimating the rocks that make it up and adding up the numbers.
WBS::="Work Breakdown Structure", count the rocks in the mountain.
Executives then ask for a better estimate/plan.
Scope-based implementation is more like using surveying tools and techniques to measure the mountain.
Use the scope of the project to estimate final system size.
Time depends on a power of system size.
Since scope is uncertain and the estimates of size based on a given scope add uncertainty, one generates effort estimates that have a range of values.
Quantify the uncertainties!
No discussion of the agile approach (start climbing the mountain first, and change your estimates as you climb, etc.)

Armour06b

Phillip G Armour
Software: hard data
Commun ACM V49n9(Sep 2006)pp15-17
=EXPERIENCES statistics Information technology projects
Software enacts knowledge about many domains with no commonality.
Quotes data from "QSM".
Small teams succeed more than large ones.
Typical projects have fewer than 7 people, last < 8 months, use COBOL, 9KLOC.
More projects overlap phases these days.
Best projects are good accross the board: effort, estimate, duration,...
Big LOC projects are more productive but why?

Armour07

Phillip G Armour
Agile . . . And Offshore
Commun ACM V50n1(Jan 2007)pp13-14
=INTERVIEW AGILE DISTRIBUTED PEOPLE ECONOMICS TOOLS WEB/NET GeneerAginity Ukraine Mantis Subversion Cruise control Ncover simian
Agile Geneer misjudged .com crash 2000-2002 & bank foreclosed.
Aginity offshore development (Evanston+Kiev) based on personal contact, shared achitecture, patterns, frameworks, language, & vocabulary.
Stories, iterations, risk provocation.
Open source groupware tools generate management data via web spaces.

Armour07a

Phillip G Armour
Mortallity Play
Commun ACM V50n3(Map 2007)pp-
=ANECDOTE INSURANCE SOFTWARE ESTIMATION
Insurance depends on estimating precisely the chances of bad things happening...
But this (anon) company had failed to figure out the chance of four projects failing.
Armour figured each had a 1/5 chance, so all four at about 1/200 for the complete set.
They used classic project planning with task breakdown etc...
Conclusion: don't just ask how long a project will take, ask what is the chanace that it will be complete by the deadline.

Armour07b

Philip G Armour
Twenty Percent
Commun ACM V50n6(Jun 2007)pp21-23
=IDEA ESTIMATION OPTIMISTIC RISKS DEATHMARCH
A good 50% estimate -- allowing for reasonable problems -- is negotiated down to one that has a 20% of being met, by ignoring the risks.
Optimism reduces the resources requested at the price of increasing the probability of running out of resources.
See [Spinellis07a] and [DEATHMARCH]

Armour08

Phillip G Armour
The inaccurate conception
Commun ACM V51n3(Mar 2008)pp13-16
=ESSAY ESTIMATION UNCERTAINTY LIFECYCLE
Cone_of_uncertainty::=map[t:time]([1/f(t) .. f(t)]* actual ), for some decreasing function f. "Describes how estimates get more accurate as a project proceeds". At that start of new product estimates are between [0.25 .. 4.0] times the actual value. Tightens as uncertainties are removed.
Express estimates as a distribution mapping qualities to probability of success. S shaped curve.
commitment is not an estimate.

Armour09

Phillip G Armour
The Business of Software: The Ontology of Paper
Commun ACM V52n1(Jan 2009)pp23-24 [ 1435417.1435427 ]
=ESSAY DOCUMENTATION PAPER vs
Claims that the industrial revolution did not occur until steam engines were used to create steam engines.
Claims that current software technology tends to reproduce the defects of paper-based artifacts.
Describes the properties of paper artifacts: difficult to link artifacts, not executable, not easily verifiable, serial access, imposes a hierarchical structure, places information within a linear context, inherently single-tasking, ...
Even hypertext does not relax these constraints.
Claims that older systems fitted the paper model well.
New systems need the external linkages and executability of software.

Armour09a

Phillip G Armour
the business of software: the cliche defence
Commun ACM V52n7(Jul 2009)pp34-36 [ 1538788.1538802 ]
=ESSAY PEOPLE MANAGERS BUZZ PHRASES
Do it right the first time. But.... Quote: "much of the business of software involves the discovery of what we are supposed to be doing".
Work smarter not harder.
Quality is the most important thing. But.... Which quality?
Our customers are the most important thing. But.... Which customers? What about future extensions and the people who work on them?
Our people are the most important thing. But... are they supported?

Armour09b

Phillip G Armour
Contagious craziness, spread sanity
Commun ACM V52n10(Oct 2009)pp19-20 [ 1562764.1562774 ]
=ANECDOTAL PEOPLE ESTIMATION TEAMS cognitive dissonance rationalization groupthink
Newton's first law of behavior: every behavior will continue until acted upon by another behavior.

Armour10

Phillip G Armour
Return at Risk
Commun ACM V53n9(Sep 2010)pp23-25 [ 1810891.1810902 ]
=POLEMIC ESTIMATION ROI RISK COST VALUE DISTRIBUTION
ROI::acronym="Return on Investment"
Argues that the traditional straight line formula
ROI=(value-cost)/cost, is not valid if there is any risk of the cost or value being wrong.
Need cost and value profiles. Probability distributions.
Notes that cost' tends to be skewed toward overruns and value` towards zero.
Calculating a better likely or average ROI is not simple and may need Monte Carlo methods. There exist tools.
Are cost and value independent?

Armour11

Phillip G Armour
The Business of Software: Don't Bring me a good idea
Commun ACM V54n1(Jan 2011)pp- [ 1866739.1866748 ]
=HOW TO SELL BUSINESS CHANGES IDEAS SYSTEMS MAKE MONEY
Good ideas -- ho-hum,
Cost reduction -- limited value,
Revenue growth gives and keeps on giving.

Armour11a

Phillip G Armour
etyltS edoC detisiveR (letter)
IEEE Software Magazine V28n4(Jul/Aug 2011)pp7-8
=ESSAY CODE STYLE THOUGHT
Coding is thinking and learning.
Reply to [Spinellis11]

Arms01

Willian Y Arms
Uniform Resource Names: Handles, PURLs, and Digital Object Identifiers
Commun ACM V44n5(May 2001)p68
=HISTORY WEB/NET URL RFC1737 URN CNRI DOI IDF
PURL::= "Persistent URL".

Armstrong06

Deborah J. Armstrong
The Quarks of Object-Oriented Development
Commun ACM V49n2(Feb 2006)pp123-128
=SURVEY OBJECTS TECHNICAL ONTOLOGY GLOSSARY TAXONOMY
Two "constructs": Structure and Behavior.
Under Structure: Abstraction, Class, Encapsulation, Inheritance, Object.
Under Behavior: Message Passing, Method, Polymorphism.
Table 3 includes definitions of the concepts.

Armstrong01

Rob Armstrong
Seven Steps to Optimizing Data Warehouse Performance
IEEE Computer Magazine V34n12(Dec 2001)pp76-79
=ADVERT PERFORMANCE OLAP DATA WAREHOUSE
Good for OLTP is bad for OLAP. Cf SSADM Physical design control in 1980's.
steps: use relational OLTP data, implement special views via SQL, add indices, store more summaries, denormalize, denormalize irrationally, export data.
Cycle: define requirement, understand benefits, determine needed data, find lowest step to get performance, calculate costs, implement or redefine requirements.

Armstrong10

Joe Armstrong
Erlang
Commun ACM V53n9(Sep 2010)pp68-75 [ 181091.1810902 ]
=ADVERT LANGUAGE Erlang NON-SEQUENTIAL FUNCTIONAL PROCESSES EXCEPTIONS QUEUING Ericsson
Message passing is good. Sharing is bad.
"let it crash" and another process tidies up the mess -- separates the main line code from the special cases. Many small modules.
First class functions/process allow easy upgrades inside running code.
Also see [Larson09]

ArrechederaMatteo00

Hector Arrechedera & Alfredo Matteo
How to get started with Design Patterns
Proc SCI/ISAS2000 VII pp47-52 [SCI00]
=EXPERIENCE EDUCATION OBJECT-ORIENTED PATTERNS

ArthorneLaffra04

John Arthorne & Chris Laffra
Official Eclipse 3.0 FAQs
Addison Wesley Pro BostonMA 2004 ISBN 0321268385 CR 0605-0450 [ http://www.eclipse.org ]
=UNREAD =MANUAL Eclipse PLUGIN Java IDE SWT [click here if you can fill this hole]

Arthur92

Lowell Jay Arthur
Rapid Evolutionary development: requirements, prototyping and software creation
John Wiley& Son NYNY 1992 ISBN 0-471-53633 CR 9211-0860 QA76.76.D47A78
=HANDBOOK EVOLUTION REQUIREMENTS PROTOTYPES

Arthur97

Lowell Jay Arthur
Quantum Improvements in Software Quality
Commun ACM V40n6(Jun 1997)pp46-52
=EXPERIENCE PEOPLE PROCES QUALITY MODULES METRIC CYCLOMATIC PARETO
focus on particular results and people. Give practical "accelerated" training(story+demonstrations+discuss application).
Laws: 20% of the code has 80% of the errors. 20% of the code requires 80% of the mods. Keep cyclomatic complexity of modules between 5 and 15.

ArthurGronerHayhurstHolloway99

James D Arthur & Markus D Gr"oner & Kelly J Hayhurst & C Michael Holloway
Evaluating the effectiveness of independent verification and validation
IEEE Computer Magazine V32n10(Oct 1999)pp79-83
=EXPERIMENT V&V SEES MER TAPs QUALITY
IV&V beneficial: cost of errors reduced

ArtziEtAl10

Shay Artzi & Adam Kiezun & Julian Dolby & Frank Tip & Danny Dig & Amit Paradkar & Michael D Ernst
Finding bugs in web applications using dynamic test generation an explicit-state model checking
IEEE Trans Software Engineering V36n4(Jul/Aug 2010)pp474-494
=CASESTUDY TOOL Apollo TEST PROOF CHECK VALIDATE VERIFY HTML PHP MySQL
Apollo found 100s of faults in real web applications.

Asaravala03

Amit Asaravala
All by themselves
Software Development Magazine V11n3(Mar 2003)pp38-41
=HISTORY AGENTS AI Clippy metadata semantic web XML RDF ontology DAML+OIL LOGIC
Agents (minimally) observe an environment and react to changes by interacting with the environment -- and other agents.
Agents either need a shared ontology or a way to share ontologies and metadata.
RDF::XML_DTD="Resource Description Framework", indicates relationships between subjects, predicates and objects.

Asaravala04

Amit Asaravala
Project Management, Evo Style
Software Development -- People and Projects newsletter(Nov 2004)
=ARTICLE AGILE EVOLUTIONARY PROJECT MANAGEMENT 1960s ITERATIVE Evo PDCA
Many small cycles each with Planning, Checking, Doing, and Acting -- -- --(PDCA)
Acting changes the plans...
See also "Evolutionary Project Management Methods," by Niels Malotaux [ http://click.sd.email-publisher.com/maacOZiabbnXPbdngFsb/ ] [pdf] and "How Quality Is Assured by Evolutionary Methods," by Niels Malotaux [ http://click.sd.email-publisher.com/maacOZiabbnXQbdngFsb/ ] [pdf].

AsarinCaspiMaler02

Eugene Asarin & Paul Caspi & Oded Maler
Timed Regular Expressions
J. ACM V49n2(Mar 2002)pp172-206
=THEORY TIMING REGULAR EXPRESSIONS STRINGS FSM LANGUAGES KLEENE BUCHI NONSEQUENTIAL
When time is important as well as sequence, then timed automata recognize languages defined by extended regular expressions: Intersection and relabelling have to be added to union/sequence/closure.
Definition is via the free merge of a Time monoid and an Event monoid.

Ashman00

H L Ashman <hla@cs.nott.ac.uk>
Relations Modeling Sets of Hypermedia Links and Navigation
Computer Journal V43n5( 2000)pp345-363
=THEORY WWW/NET HYPERTEXT

AslesonSchutta05

Ryan Asleson & Nathaniel T Schutta
Foundations of Ajax (foundation)
Apress Berkeley CA 2005 ISBN 159059823 CR 0611-1104
=UNREAD Web/NET Javascript XML Ajax
Compare with rival Atlas [SmithK06] from Microsoft.

Aslett91

M J Aslett(Ed)(GEC Marconi UK)
A knowledge based approach to Software development: ESPRIT project ASPIS
North-Holland Amsterdam Netherlands 1991 ISBN 0-444-88886-1 CR9310-0740
=UNREAD KNOWLEDGE ASPIS

AstesianoReggioRicca08

Egidio Astesiano & Gianna Reggio & Filippo Ricca
Modeling Business with a UML-based Rigorous Software Development Approach
Montanari Festschrift pp261-277 [DeganoEtAl08]
=DEMO UML BUSINESS MODELING MARS SOA REALITIES SYSTEMS ORGANIZATION OCL
BM::discipline="Business Modeling".
Use multiple UML2 views of business: Static + Organization + Business Process + Data.
Model business processes in the context of other business processes.
Model business entities and organization.
Model activities precisely.
Proposes stereotypes: <<A>> for autonomous acts, <<bw>> for business worker, <<bo>> for business objects, <<ext>> external entities, <<ou>> organizational units. <<bp>> business process "use case". <<large>> high level cases.

AstleySturmanAghar01

Mark Astley & Daniel Sturman & Gul Aghar
Customizable middleware for modular distributed software
Commun ACM V44n5(May 2001)pp99-107
=DEMO MODULES ARCHITECTURE WWW/NET NONSEQUENTIAL QUALITIES REFLECTION LANGUAGE ACTORS
separate concerns of application (PURPOSES) from nonfunctional requirements (policies) like security and atomicity.
Express policies(requirements) explicitly in the software.
Policies are to protocols as interfaces are to implementations.
DIL::= "Distributed Interaction Language", describes a protocol in terms of roles and their responses to events. Roles are formal parameters.
Multiple policies achieved by stacking protocols with one object playing one or more roles in several protocols.
?? Aliasing ?

Astrachan91

Owen Astrachan
Pictures as Invariants
SIGCSE Bulletin V23n1(Mar 1991)pp112-118
=DEMO LOGIC TECHNICAL GRAPHIC

Asuaga01

Ana Asuaga
Enginering a New society
IEEE Computer Magazine V34n6(Jun 2001)pp104+102-103-
=ESSAY SYSTEMS ENGINEERING ETHICS
Need for collaboration and listening in engineering and in society.

AthanasSilverman93

Peter M Athanas & Harvey F Silverman
Processor Reconfiguration Through Instruction-Set Metamorphosis
IEEE Computer Magazine V26n3(Mar 1993)pp11-20
=DEMO DFDs HARDWARE
DFDs on pages 15-16 are called DFGs

AtkinsBallGravesMockus02

David L Atkins & Thomas Ball & Todd L Graves & Audris Mockus
Using Version Control Data to evaluate the Impact of Software Tools: A Case Study of the Version editor(VE)
IEEE Trans Software Engineering V28n7(Jul 2002)pp625-637
=EMPIRICAL TECHNICAL TOOL EVALUATION
|-(1) : tools help developers determine and/or carry out modifications in existing documents.
|-(2) : The change history of such documents can be used to estimate the effort.
(1, 2)|-record tools used and relate to monitored data.
Tool designed to hide C++ #ifdefs etc had a significant and good effect on productivity.

AtkinsonKuhne03

Colin Atkinson & Thomas K"uhne
Aspect-Oriented Development with Stratified Frameworks
IEEE Software Magazine V20n1(Jan/Feb 2003)pp81-89
=IDEA DESIGN ASPECTS AOP HIERARCHY ARCHITECTURE PATTERNS
Refine labelled interactions to collaborations of objects. Labels name concerns and indicate the collaboration and/or more detailed concerns.
Concerns include coordination, distribution, persistence, security, recovery, undo, paradigms

AtleeBuckley96

Joanne M Atlee & Michael A Buckley
A logic-Model Semantics for SCR Software Requirements
Proc 1996 Int Symposium on Software Testing & Analysis(ISSTA) & ACM SIGSOFT SENotes V21n3(May 1996)pp280-292
=IDEA LOGIC SCR REQUIREMENTS TABULAR
SCR::="Software Cost Reduction"
SCR Statecharts RSML all share conditioned-event-driven reactive systems. demos analytical requirements temporal logic model and tool SMV::="Symbolic Model Verifier". CTL::=Computational Tree Logic
See CORE [WilliamsL94] [HeimdahlLeveson96]

Atwood07

Jeff Atwood
The coming Software Patent Apocalpse
Coding Horror (Jul ?? 2007) [ 000902.html ]
=ESSAY LEGAL PATENT ARMS RACE Microsoft Knuth

Atwood08

Jeff Atwood
Coding: It's just writing
coding horror nov10th [ 001184.html ]
=ESSAY CODING STYLE STRUNK LITERATE KNUTH

Atwood09?

Jeff Atwood
software engineering dead?
coding horror blog (jul 18 2007) [ 001288.html ]
=ESSAY CONTROL PLANNING ENGINEERING CRAFT
surprised by [DeMarco09]
Quote

Atwood09b

Jeff Atwood
COBOL: Everywhere and Nowhere
Coding Horror (Aug 9 2009) [ 001294.html ]
=BLOG COBOL COBOL.NET EXAMPLE

Atwood10

Jeff Atwood
Coding Horror Jun 1st 2010 [ the-vast-and-endless-sea.html ]
=ESSAY PEOPLE ECONOMICS SOCIOLOGY MOTIVATION Stack Overflow vs Stack Exchange FOSS
More money does not encourage better programming. [Pink09]

Atwood11

Jeff Atwood
The infinite version
Coding Horror (23 May 2011) [ the-infinite-version.html ]
=BLOG UPDATES INCREMENTAL FLUIDITY Chrome bsdiff Courgette WordPress Google Docs
Quote

AueBreu94

Alfred Aue & Michael Breu
Distributed Information Systems: An Advanced Methodology
IEEE trans on Soft Eng vSE-20n8(Aug 1994)pp594-605
=ADVERT BOS(Bull + Olivetti & Siemens-Nixdorf) ENGINEERING method REQUIREMENTS LIFECYCLE ERD
Based on Merise/Omega
MOis
GRAPES. Relaxed water fall model. Documents can be drafted
approved and then baseline. The draft versions "look ahead" to the future options.

AugustinePayneSencindiverWoodcock05

Sanjiv Augustine & Bob Payne & Fred Sencindiver & Susan Woodcock
Agile Project Management: Steering from the edges.
Commun ACM V48n12(Dec 2005)pp85-89
=ADVERT AGILE PROJECT MANAGEMENT APM COMPLEXITY XP
APM::= "Agile Project Management".
Agile methods rescue a medium sized project in 2002. Lists: 6 practices, 7 changes, 6 new activities, 6 innovations, 7 difficulties.
sidebar p87 describes complex adaptive systems ( CAS ).

Austin99

Robert D Austin
The Phantom Menace
IEEE Software Magazine V16n5(Sep/Oct 1999)pp15-18
=EXPERIENCE PROCESSES MANAGEMENT
superstars, dynamic requirements, parallelism, theatre

AustinDevin03

Rob Austin & Lee Devin
Beyond Requirements: software Making as Art
IEEE Software Magazine V20n1(Jan/Feb 2003)pp93-95
=ESSAY REQUIREMENTS FORMAL vs AGILE PURPOSES QUALITIES EVOLUTION ITERATION
Analogy with producing a play. The requirements are like a script. But a great performance goes beyond the script by iteration, creation, and improvisation. So great software will go beyond the predicted requirements using creativity, iteration, and improvisation.

Autebert99

Jean-Michel Autebert
Some Results about Centralized PC grammar systems
Theor Comput Sci V215n1/2(Feb 28 1999)pp383-398
=THEORY NONSEQUENTIAL GRAMMAR LANGUAGES THEORY
PC:= Parallel communicating context free.
Grammars generate query symbols that is a non-terminal in another grammar.
Centralised:@PC=only one grammar inserts queries.

AvisonFitzgerald03

David E Avison & Guy Fitzgerald
Where Now for development methodologies
Commun ACM V46n1(Jan 2003)pp79-
=HISTORY METHODS NONE SDLC ONE-SIZE -> DIVERSITY
methods became mixtures of ( structured, data-oriented, prototyping, Object-Oriented, participative, strategic, Systems) methods.
Most were local to the organization even if based on another one.
web related return to 1960's ad hocism?

AvisonGregorWilson06

David Avison & Shirley Gregor & David Wilson
Managerial IT Unconsciousness
Commun ACM V49n7(Jul 2006)pp89-93
=EXPERIENCES RISKS 3 AUSTRALIAN FAILURES PEOPLE RMIT ERP PeopleSoft Sidney Water One.Tel
All three we catastrophic (or near catastrophes) for stake holders. One bankruptcy.
3 different types of business: university, utility, .com telephones
Risk factors
1. Over-complex/ambitious or over-integrated systems.
2. Clueless management -- Poor governance -- no checks on progress and quality.
3. Inexperienced or powerless experts with no clout -- warnings ignored.
4. Ignoring the critical importance of getting money in: billing systems!

AvisonYoung07

David Avison & Terry Young
Time to rethink health care and ICT
Commun ACM V50n6(Jun 2007)pp69-74
=SURVEY UK HEALTH RISKS PEOPLE CULTURE FACE-TO-FACE VS ERP NPfIT RISP CSCI372
Describes and analyses the history of health systems not meeting their goals and/or failing to serve the stake holders
NPiFT::UK.NHS="The National Program for Information Technology".
Notes that best practices include understanding and supporting the culture of the organization.
Notes that health system rely on complex face-to-face communication.
Claims this is being ignored in NPfIT.

AvizienisBall87

Algirdas Avizienis & Danforth E Ball
On the Achievement of a Dependable and Fault-Tolerant Air Traffic Control System
IEEE Computer Magazine V20n2 (Feb 1987)pp63-71
=EXPERIENCE FAA AAS minimize RISKS
Compare with the later TCAS.

Avram10

Abel Avram
Lessons Learned from Skype's Outage
InfoQ (Dec 30 2010) [ Lessons-from-Skype-Outage ]
=ANALYSIS EXPREIENCE BUG UPDATES FEEDBACK NETWORK FAILURE SUPERNODES OVERLOADED
Most users don't upgrade unless they are forced to.

Avruninetal91

George S Avrunin & Ugo A. Buy & James C Corbett & Laura K Dillon and Jack C Wileden
Automated Analysis of Concurrent Systems With the Constrained Expression Toolset
IEEE SE-V17n11(Nov 1991)pp1204-1222 CR9303-0149
=DEMO TOOL NONSEQUENTIAL PREDICTION PROOF
regular expressions plus interleaving to predict behaviors and problems

AycockHorspool01

John Aycock & R Nigel Horspool
Schroedinger's Token
Software - Practice & Experience V31n8(10 Jul 2001)pp803-814
=IDEA LEXICAL PARSING LANGUAGES NONDETERMINISM
During lexical analysis a token can be left in a superposition of several types until the parser looks into the token and resolves it.
IF IF = THEN THEN THEN =IF
dummy token type: SCHRODINGER

AyewahEtAl08

Nathaniel Ayewah & William Pugh & David Hovemeyer & J David Morgenthaler & John Penix
Using Static Analysis to Find Bugs
IEEE Software Magazine V25n5(Sep/Oct 2008)pp22-29
=EXPERIENCE Google =SURVEY OPEN SOURCE TOOL FindBugs Java TECHNICAL QUALITY Mondrian
A free static analysis tool finds real defects in real code ... Plus some false positives -- but misses some bugs.
Survey of users shows it to be useful.

BaaderNipkow98

Franz Baader & Tobias Nipkow
Term rewriting and all that
Cambridge U Press NY NY 1998 ISBN 0-521-77920-0 CR0002-0072
=THEORY MATH

Baber82

Robert Laurence Baber
Software Reflected: the socially responsible programming of our computers
North Holland NY NY 1982 QA76.6.B26
=TEXTBOOK USER

Baber85

Robert L Baber
I/O Statements in Higher Programming Languages: Unnecessary & Undesirable(Open Channel)
IEEE Computer Magazine V18n6(Jun 1985)p112
=HARMFUL input/output LANGUAGES
harmful to split secondary from primary memory

BabarGorton09

Muhammad Ali Babar & Ian Gorton
Software Architecture Review: The State of Practice
IEEE Computer Magazine V42n7(Jul 2009)pp27-32
=POLL 235 ENTERPRISES SQA ARCHITECTURE MODELS INSPECTION WALKTHROUGH
Excellent summary of ways of ensuring design quality and addressing architectural concerns -- not all of them popular.
Common techniques: Scenarios, Experience, and prototyping. Less common: check lists, metrics, simulation, questionaires, mathematics
Documenting architectures: modeling notations, views, features, assumptions and constraints, ...
Inputs: (commonest first) requirements, descriptions, business drivers, standards, ...
Stakeholders -- various

Babinetal91

Gilbert Babin & Francois Lustman & Peretz Shoval
Specification and Design of Transactions in Informations Systems: A Formal Approach
IEEE SE-V17n8(Aug 1991)pp815-829
CR9303-0181
QV Lustman94
dataflows vs control_data_flows & FSM

Bach95

James Bach
Enough about process: What we need are heroes
IEEE Software Magazine V12n2(Mar 1995)pp96-98+replies IEEE Software Magazine V12n3(May 1995)p5-7 [Bach9?]

Bach97

James Bach
Good Enough Quality: Beyond the Buzzword
IEEE Computer Magazine V30n8(Aug 1997)pp96-98
=ESSAY QUALITY ECONMICS MS-PROCESS
rational choices of what to fix now
GEQ::="Good Enough Quality"

Bach9?

James Bach
Process Evolution in a Mad World
Borland International Internal Report (100 Borland Way Scots Valley CA 96066) [Bach95]
1. (riskbased1): absolutely necessary - to handle perceived risk
2. (riskbased2): make it tolerant
3. (riskbased3): small informal experiments first
4. (riskbased4): frequent evaluation
5. (riskbased5): find a champion
6. (riskbased6): work with the team
7. (riskbased7): mentor, not a manuaal
8. (riskbased8): "formalize" only when necessary
9. Example Bug reviews. 50..100 bugs per day. 30 bugs an hour.

BachleKirchberg07

Michael Bachle & Pauk Kirchberg
Ruby on Rails
IEEE Software Magazine V24n6(Nov/Dec 2007)pp105-108
=DEMO RUBY ROR TECHNICAL WEB PLATFORM RAPID PROTOTYPING MVC
Also compares with Apache Struts, Tapestry, Cocoon, and ASP.NET

Bachman69

Charles Bachman
Data Structure Diagrams
Data Base Journal ACM SIGDBP v1 n2 (?? 1969)pp4-10
=DEMO GRAPHIC DATA Reality

Bachman73

Charles Bachman
The Programmer as Navigator
Commun ACM v16 n11 Nov73 pp653-658
=ESSAY data

Bachman92

Charlie Bachman
New Apps Must be Model-Driven:Business Needs Steer Changes to Tech Model
Software Magazine Debate (Mar 1992)p52

Backhouseetal89

Roland Backhouse & Paul Chisholm & Grant Malcolm & Erik Saaman
Do-it-yourself Type Theory
Formal Aspects Comput V1n1 (Jan-Mar 1989)pp19-84
=theory structures Reality

BaclawskiIndurkhya94

Kenneth Baclawski & Bipin Indurkhya
The Notion of Inheritance in object-oriented programming(Letter)
Commun ACM V37n9(Sep 1994)pp118-119
[Grosberg93] [ArnoldK94] (C++ advice)
1. Abrahams's 91 letter "Subject: Objectivism"
2. Lalonde & Pugh JOOP 91 "subclassing <> subtyping <> is-a"
3. Tesler's 91 CACM letter
4. Wegner 80 pages in 90 OOPS messenger
5. Winkler 92 letter refers to POV vs COV in Winkler's letter Quotes Wegner 90
6. POV = Physical & COV = Conceptual Piaget: Child constructs idea of object permanence from its own actions on the objects.
  Class of objects without actions<>class of objects with some actions.
  Failure to find epistomological foundations of the IS-A link - six different generic-generic and four kinds of generic-individual relation
  "The point here is that the concepts in the real world, which programs attempt to model, do not come in neatly packaged hierarchies." (cf GoldsteinAlger92)
  "There are no standard conceptual hierachies. Given a domain and a specific PURPOSE, certain concept hierarchies would be clearly preferable than others, but such policy decisions are best left to the USER of the programming language[...] What a PL provides is a set of mechanisms [...] restrict what can be implemented[but] they do not themselves validate some view of inheritance or other[...]" these are also just implemented concepts and do not not have a universal objective meaning....upto the designers to choose suitable mechanisms.

BackusEtAl63

Backus, J. W. & Bauer, F. L. & Green, J. & Katz, C. & McCarthy, J. & Perlis, A. J. & Rutishauser, H. & Samelson, K. & Vauquois, B. & Wegstein, J. H. & van Wijngaarden, A. & Woodger, M Pete Naur(ed)
Revised report on the algorithm language ALGOL 60
Commun ACM V6n1(Jan 1963)pp1-17 [ 366193.366201 ]
=CLASSIC =DEFINITION ALGOL 60 LANGUAGE BNF SYNTAX SEMANTICS TECHNICAL

BaeckerMarcus90

R M Baeker & A Marcus
Human Factors and typography for More Readable Programs
ACM Press 1990
Readability QUALITY Readability Technical

Baetan90

J C M Baetan(Ed)
Applications of Process Algebra
Cambridge U Press Cambridge UK & NY NY 1990
=Theory nonsequential algebra CSP CCS ACP
1. problem with informal semantics in POOL pp172-236(Frits W Vaandrager)
2. fairness and liveness [p13 of Baetan90 by J A Bergstra &J W Kop]
3. ultrametric [p9 of Baetan90 by J A Bergstra &J W Kop] :. all guarded recursion equations without abstraction have a unique solution.
4. process creation can be simulated. pp81-88 of Baetan90 by J A Bergstra )
5. Process Algebra is a better model than CSP/CCS for concurrency.
6. Relations are a basic process algebra pp1-22(J A Bergstra &J W Kop) but without <*>

Baetan08

Joe C M Baetan
Calculating with Automata
Montanari Festschrift [DeganoEtAl08] pp746-756
=EDUCATION THEORY ALGEBRA EQUATIONS AUTOMATA GRAMMARS KLEENE REGULAR EXPRESSIONS
Demonstrates that most of standard theory can be taught using equations.

Baggi05

Denis L Baggi
An IEEE Standard for Symbolic Music
IEEE Computer Magazine V38n11(Nov 2005)pp100-102
=REPORT MUSIC STANDARD P1599 XML MEI RM0
P1599::= See http://www.computer.org/portal/pages/ieeecs/communities/standards/1599/par.html
MusicXML::= See http://www.recordare.com/xml.html

BaggiHaus09

Denis Baggi & Goffredo Haus
IEEE 1599: Music encoding and interaction
IEEE Computer Magazine V42n3pp84-87
=ADVERT =STANDARD IEEE-1599 MUSIC AUDIO VISUAL NOTATION GAME JAZZ Blues XML
IEEE1599::DTD= See http://standards.ieee.org/downloads/1599/1599-208/
Example: <clef type="G" staff_step="2" event_ref="c1"/>
Previous report [Baggi05]

Bagrodia89

Rajive Bagrodia
Synchronisation of Asynchronous Processes in CSP
ACM Trans Prog Lang Syst V11n4(Oct 1989) pp585-597
=THEORY Technical non-sequential

BahsounMerzServieres93

Jean Paul Bahsoun & Stephan Merz & Corinne Servieres<all@irit.fr>
A Framework for Programming and Formalizing Concurrent Objects [Notkin93] pp 126-137
=THEORY non-sequential objects TLA
1. messages::=${ sender, destination::agent, mode::modes, type::message_types, parameters::vector, ...}.
  Two modes: asynchronous- after sending the sender does not wait, semi-synchronous - the sender will not send a message of the same type to the same receiver before the first message has been acknowledged by the receiver.
  Assumes arbitrary delays and that messages can get out of order.
  TLA formalization via send[a](M)::=net:| a><M.... Conclusions Now need to investigate inheritance. must spec both components and protocols...

BaierHaverkortHermansKatoen03

Christel Baier & Boudewijn Haverkort & Holger Hermans & Joost-Pieter Katoen
Model-checking algorithms for continuous-time Markov Chains
IEEE Trans Software Engineering V29n6(Jun 2003)pp524-541
=THEORY MATHEMATICS MODEL CHECKING CTMC CSL RELIABILITY CTL
CSL:="Continuous Stochastic Logic". Steady state + path probabilities in time intervals. Modes P[event] <=> p. Nested. Generalizes CTL.
CTMC::="continuous time Markov chains". P(i -> j fires after t) = c*exp( -rate*t) iff it is first.

BaierEtAl07

Christel Baier & Lucia Cloth & Boudewijn R Haverkort & Mathias Kuntz & Markus Siegle
Model Checking Markov Chains with Actions and State Labels
IEEE Trans Software Engineering V33n4(Apr 2007)pp209-224
=THEORY MODEL CHECKING REAL TIME MARKOV CHAINS PROBABILITY LOGIC asCSL
Logic + model design for verifying requirements that a given pattern of actions and states (and time limits) has a given range of probabilities.
Example requirement: the probabillity of entering a full state via a number of arrive actions within 5 time units must be greater than or equal to 99%.
Defines products of chains.
Cellular phone hand over model.
experiment with tool.

BaierKatoen08

Christel Baier & Joost Katoen
Principles of Model Checking
The MIT Press Cambridge MA (2008) ISBN 026202649X CR 0912-1115
=TEXT =THEORY MODEL CHECKING MODAL LOGICS FSM LTL CTL CTL* TCTL BISIMULAION OBDT MARKOV PCTL PCTL*
Excellent and thorough text book suitable for graduate Computer scientists or some final year undergraduates
A large in depth reference to the theory of the most successful formal methods - so far.
Does not use the normal syntax for modes but uses ∀ and ∃. So doesn't fit some tools.
Does not use standard terminology.
Does include newer topics and types of models.

BaierHaverkortHermansKatoen10

Christel Baier & Boudewign R Haverkort & Holger Hermans & Joost-Pieter Katoen
Performance Evaluation and Model Checking Join Forces
Commun ACM V53n9(Sep 2010)pp76-85 [ 1810891.1810912 ]
=HISTORY MODEL CHECKING PERFORMANCE MODAL PROBABILLITY LOGIC CTL LTL PCTL DTMC ADVERT TOOLS PRISM EXAMPLES
Excellent diagram of history starting with Markov Chains in 1900 and ending with advanced algorithms and applications.
Figure 3: IPv4 zeroconf protocol
Example -- able to show that Firewire root contention protocol is faster when biased "coin tossing" is used.

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.

Bailin89

SC Bailin
An Object-Oriented Requirements Specification Method
Commun ACM v32n5(May 1989)pp608-623 [ 63485.63491 ]
=IDEA OBJECTS ERD DFD Reality PURPOSE TECHNICAL SRS

Baines98

Robin Baines
Across Disciplines: Risk, Design, Method, Process, and Tools
IEEE Software magazine V15n4(Jul/Aug 1998)pp61-64
=EXPERIENCE PEOPLE ENGINEERING
Compare your software people's activities with other engineers in your company

Baker93ab

Steven Baker
Net Worth Column
Unix Review (Jun 1993)pp23-37 & (Jul 1993)pp25-34
=HISTORY STANDARDS MIME EMail Multimedia SGML richtext RTF

Baker97

Richard A Baker Jr
Code Reviews Enhance Software QUALITY [ICSE'97]
When technical managers reveiw their subordinates code errors drop by 40% at a cost of <2%. Like by those being reviewed - manager cares and knows our work.

BakerB07

Brenda S Baker
Finding clones with Dup: Analysis ofan experiment
IEEE Trans Software Engineering V33n9(Sep 2007)pp608-621
=EXPERIMENT TOOLS COPYPASTE DRY SOURCE Dup
Also see [BellonEtAl07]

BakerHoekOssherPetre12

Alex Baker & Andres van der Hoek & Harold Ossher & Marian Petre
Studying Professional Software Design
IEEE Software Magazine V29n1(Jan/Feb 2012)pp28-33
=HISTORY REPORT WORKSHOP DESIGNERS WORKING
Bibliography [ MS.2011.155 ]
Quotes known observations:
1. Little exploration of alternatives.
2. Their is no linear process and no design phase.
3. Whiteboards and other transient media are prevalent in design work.
4. Notations are informal but not unlike the formal ones.
5. Experts tend to start by studying the problem and understand how to decompose problems and select the next subproblem to work on.
6. Designers have strategies but make provisional decisions to allow future options.
7. Designers try different topics vs the problem.
8. Experts tend to use local planning and gather feedback rather than analysing requirements.
9. Process emerges opportunistically not preplanned. But is a mixture of depth and breadth first solution development.
10. The more familiar the problem, the fewer options are considered.
Introduces results of the workshop:- [NakakojiYamamotoMatsubaraShirai12] [DimaghaniDibble12] (Oracle) [Shaw12] [RooksbyIkeya12]

BakerLevin83

Stephen Baker & Arnie Levin
I hate Meetings
Macmillan NY 1983 ISBN0-02-506370-7
= JOKES PEOPLE MANAGEMENT MEETINGS
Good explanation why people hate meetings.
Confirms purpose of meetings: too spread the blame/responsibility widely.
Chapter 8: good field guide to problem people from the chair's point of view: Speech maker, Yawner, Bottom liner, Devil's advocate, Early leaver, late-comer.

BalakrishnanFitzmaurice Kurtenbac.h01

Ravin Balakrishnan & George W Fitzmaurice & Gordon Kurtenbac.h
user interfaces for volumetric displays
IEEE Computer Magazine V34n3(Mar 2001)pp37-45
=ARTICLE NEW HCI 3D GRAPHIC hardware
pinch, twist, slice, & crush that display!

Balasubramanianetal95

V Balasubramanian & Bang Min Ma & Joonhee Yoo
A Systematic Approach to Designing a WWW Application
Commun ACM V38n8(Aug 1995)pp47-48
RMD::=Relational Managemnt Data (diagram) with slicing

BalasubramianEtal06

Krishnakuma Balasubramian & Aniruddh Gokhale & Gabor Karsai & Janos Sztipanovits & Sandeep Neema
Developing applications using model-driven design environments
IEEE Computer Magazine V39n2(Feb 2006)pp33-40 =DEMO MDD not MDA GME PICML ECSL DOMAIN MODEL LANGUAGES DSML
DSML::="Domain-Specific Modeling Language".
MIC::="Model-Integrated Computing".
Models replace programming languages, and each application domain has customized modeling languages.
GME:="Generic modeling environment", Vanderbilt University [ gme ]
PICML::="Platform independent component modeling language".

Baldwin92

Doug Baldwin
Using Scientific Experiemnts in Early Computer Science Laboratories
ACM 23rd SIGCSE technial Symposium SIGCSE Bulletin V24n1(Mar 1992)pp102-106

BaldwinChung95

Reid A Baldwin & Moon Jung Chung
A Formal Approach to Managing Design Processes
IEEE Coputer Magazine V28n2(Feb 1995)pp54-63
Process Flow Graph.... DFD like but with alternate refinements.

BaldwinHenderson02

Doug Baldwin & Peter B Henderson
The Importance of Mathematics to the Software Practitioner
IEEE Software Magazine V19n2(Mar/Apr 2002)pp112+110-111
=ESSAY MATH
Response to article by Robert Glass 2000.
Good School math correlates with good scores in freshman programming even tho' there was little explicit math in the programming classes.
Although programmers do not find much use for the calculus [Lethbridge00] , modest use of simple math combined with other good practices reduces defects [LarsonFitzgeralBrooks96] and/or bugs [PfleegerHatton97].
For more see [ relevance.html ]

BallCrawford99

Steve Ball & John Miller Crawford
Are Java Applets Independent Programs?
Dr. Dobb's n298(Apr 1999)pp101-104+105
=DEMO TECHNICAL JAVA RISK
Classwide fields are shared between all applets of a given type. Shows how to have one field per applet.

Ballanceetal90

Robert A Ballance & Susan L Graham & Michael L Van De Vanter
The Pan Language-Based Editing System for Integrated Development Environments
SIGSOFT'90 pp77-93
p85 Logic programming

BallEick96

Thomas Ball(mailto:tjball@bell-labs.com) & Stephen G Eick(mailto:eick@bell-labs.com)
Software Visualization in the Large
IEEE Computer Magazine V29N4(Apr 1996)pp33-43
=DEMO colored graphic technical source code

BallLarus00

Thomas Ball(microsoft) & James R Larus(microsoft)
Using paths to measure, explain, and enhance program behavior
IEEE Computer Magazine V33n7(Jul 2000)pp57-65
=SURVEY TECHNICAL GRAPH PERFORMANCE CORRECTNESS
maximal acyclic control paths. hot paths.

BalsamoMarcoInveradiSimeoni04

Simonetta Balsamo & Antinisca Di Marco & Paola Inveradi & Marta Simeoni
Model-Based Performance Prediction in Software Development: A Survey
IEEE Trans Software Engineering V30n5(May 2004)pp295-310 CR 0504-0464
=SURVEY MODEL QUALITIES PERFORMANCE 15 METHODS UML ALGEBRA QN Petri
Nearly all methods us UML and QN
QN::=Queuing Networks.
Most are highly automated and focus on software architecture and software design.

Balsters03

Hermann Balsters
Modeling database views with derived classes in the UML/OCL-framework
LNCS 2863 <<UML>> 2003 -- The Unified Modeling Language Oct 2003, pp295-309
=IDEA MODEL DATA VIEWS RELATIONAL DB RDB OCL
Introduces derived classes with names like /Emp2

Bamberger97

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

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

BamfordDeibler03

Robert Bamford & William J Deibler
ISO 9001;2000:for software and systems providers: an engineering approach
CRC Press Boca Raton FL 2003 ISBN 0849320631 CR 0511-1193
=REFERENCE ENGINEERING QUALITY STANDARD

BanatreLeMetayer93

Jean-Pierre Banatre & Daniel Le Metayer
Programming by Multiset Transformation
Comm ACM V36n1(Jan 1993)pp98-111
Concurrent nondeterministic repeated local operations
GAMMA=General Abstract Model for Multiset mAnipulation
1. For Type T, n:Nat, x:T^n, bag(x)::= +(bag o x).
2. For Type T, B:bag(T), B:@T::={t:T||B(t)>0}. For T:Type, n:Nat, X:=T^n, reaction:=(@^X)><(T^X), RA:finite_set(reaction), S:variable(bag(T)),
3. Γ(RA)::=
4. do with(x:T^n, (R,A) :RA) (
5. x in R&S and S'=S-bag(x)+bag(A(x))
6. ).

Bandinelietal95

sergio Bandineli & Alfonso Fuggetts & Luigi Lavazza & Maurizio & Gain Pietro Picco
Modeling and improving an Industrial Software Process
IEEE Trans Software Engineering V21n5(May 1995)pp440-453
=EXPERIENCE PROCESS MODEL
when improving a process you need to check the official process against the reality. Also the official process may be described in terms that are ambiguous. FSMs and Petrie nets can be used to uncover ambiguities and iaccuracies in the official process. Further they can lead to the discovery of simple and effective improvements in the process.

BandiVaishnaviTurk03

Rajendra K Bandi & Vijay K Vaishnavi & Daniel E Turk
Predicting Maintenance Performance Using Object-Oriented Design complexity metrics
IEEE Trans Software Engineering V29n1(Jan 2003)pp77-87
=EXPERIMENT Object-Oriented METRICS MAINTENANCE EMPIRICAL ANOVA
Three metrics: interaction level (IL), Interface size (IS), and Operation Argument Complexity (OAC)
Two tasks, one perfective and the other corrective maintenance.
93 students 5 sections, GPA 3.5, 14 credits of CIS work.
tested for difference due to complexity, instructor and quarter.
Complexity had a significant effect on maintenance time.
Correlation indicates significant positive linear relations between each metric and maintenance time. But R^2 is only 12-25%

BaniassadEtal06

Elisa Baniassad & Paul C Clements & Joao Araujo & Ana Moreira & Awais Rashid & Bedir Tekinerdogan
Discovering Early Aspect
IEEE Software Magazine V23n1(Jan/Feb 2006)pp61-70
=IDEA ASPECTS REQUIREMENTS ARCHITECTURE
See [ http://www.early-aspects.net ]
An aspect is a property that cuts across the dominant decomposition.
In requirements, aspects constrain many scenarios.
In architecture, aspects cut across many views.

Bankeretal93

Rajiv D Banker & Srikani M Datar & Chris F Kemerer & Dani Zweig
Software Complexity and Maintenance Costs
Comm ACM V36n11(Nov 1993)pp81-94
Maintenance Time increased by larger modules & larger paragraphs & "bad" GOTOs

BankerKemerer89

Rajiv D Banker & Srikani M Datar & Chris F Kemerer
Scale Economies in New Software Development
IEEE Trans Soft Eng VSE-15n10(Oct 1989)pp1199-1205 [ TSE.1989.559768 ]
=THEORY ONESIZE
Argues work=a+size^b is false because b varies giving a "most productive scale size" that "varies widely accross different application environments"

BansiyaDavis02

Jagdish Bansiya & Carl G Davis
A Hierarchical Model for Object-Oriented Design Quality Assessment
IEEE Trans Software Engineering V28n1(Jan 2002)pp4-17
=EMPIRICAL QUALITIES METRIC OBJECT QMOOD C++ TOOL QMOOD++ MFC OWL MSWINDOWS FRAMEWORKS COOL
Evaluated a set of metrics of two frameworks (MFC, OWL) over several releases.
Ranked 13 COOL projects by hand and by QMOOD++ and found 0,4..0.9 correlation.

BanslerBoedker93

Jorgen P Bansler & Keld Boedker
A Reappraisal of Structured analysis: design in an organisational context
ACM Trans Inf Syst V11n2(Apr 93)pp165-193, CR9402-0096
=POLL THEORY VS PRACTICE SA/SD Yourdon DeMarco DFD
SA treats people as machines and so ignores errors creativity politics, assumes all problems have been stated, rational designer, separation of function from implementation
small survey interviewing successful SA/SD.
people use tools not the rules. DFDs and ERDs. prototypes, screen layout
Abstract:

Bar-David93

Tsvi Bar-David
Object-oriented design for C++
Prentice Hall Englewood Cliffs NJ 1993
CR9312-0913 D.1.5

Barber90

Thomas Walter Barber, engineer
The Engineer's Sketch-Book of mechanical movements, devices, appliances, contrivances, and Details
Spon London UK and NY NY 1890 (2nd edn) [ books?id=sExDAAAAIAAJ&printsec=frontcover&dq=%22Thomas+Walter+Barber%22&source=bl&ots=TO7N5WG9MV&sig=4LXrUsWlKGYmqQ84S6DUiPxjVHw&hl=en&ei=K0mRS8bAOoj8sgO6zf38Aw&sa=X&oi=book_result&ct=result&resnum=5&ved=0CBUQ6AEwBA#v=onepage&q=&f=false ]
=CLASSIC =HANDBOOK MECHANICAL ENINEERING PATTERNS
Extensive review and historicalresearch [ twb.html ]
Sample [ EngineersSketchBookP49.gif ] (Page 49).

BarbierEtal03

Franck Barbier & Brian Henderson-Sellers & Annig Le Parc-Lacarelle & Jean-Michele Bruel
Formalization of the Whole-Part Relationship in the Unified Modeling Language
IEEE Trans Software Engineering V29n5(May 2003)pp459-470 Reviewed CR 0409-1078 and 0409-1079
=PROPOSAL Object-Oriented MODEL STANDARD aggregation composition whole-part bibliography UML OCL MetaModel OML OPEN Diamonds
careful philosophical analysis of semantics of whole-part. some confused "common logic" and much OCL.
Defines a new dotted diamond whole-part Relationship with specialization of aggregation and composition.
Introduces new stereotypes to indicate OCL constraints on the UML MetaModel.
Will it make it into UML4.0?
Correspondence
1. IEEE Trans Software Engineering V29n11(Nov 2003)pp1054-1056
2. "On formalization of the whole-part relationship in the unified modeling Language" by Hee Beng Kuan Tan & Lun Hao & Yong Hang corrects discrepancies,
3. "Controversies about the Black and White Diamonds" by Frank Barbier & Brian Henderson-Sellers" responds by changing name of "antisymmetry", accepting new formula for "transitivity", and agreeing to minor correction in a proof. Regrets the absence of "scientific" review of UML specifications.

BarbosaCostaAlmeidaAlameida04

Marcello W Barbosa & Mellssa M Costa & Jussara M Almeida & Virgilio A P Alameida
Using Locality of reference to improve performance of peer-to-peer applications
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp216-227
=SIMULATION P2P NET PERFORMANCE DATA LOCATION QoS Freenet Gnutella
claims 20..30% decrease in latency with no added load on network by knowing which node might have the data.

BaresiOrsoPezze97

Luciano Baresi & Alessandro Orso & Mauro Pezze
Introducing Formal Specification Methods in Industrial Practice [ICSE'97]
need to develop special languages and notations fr each set of clients therefore a customizable system. Uses hypergraph grammars and kernel of petri nets

BaresiPezze98

Luciano Baresi & Mauro Pezze
Toward Formalizing Structured Analysis
ACM ToSEM V7n1(Jan 1998)pp80-107
=ANALYSIS STRUCTURED METHOD SA/RT
issues to be resolved before choosing a formal model for Hatley-Pirbhai SA for Real Time systems

Barjis08

Joseph Barjis
The importance of business process modeling in software systems design
Science of Computer Programming V71n1(Mar 2008)pp73-87 [ science $CR 0906-0558 ]
=ADVERT METHOD THEORY MODEL DEMO LANGUAGE-ACTION PETRI GRAPHIC ANALYSIS REQUIREMENTS SCENARIOS Keywords: Requirements specifications; Model checking; Business process modeling; Business process simulation;
DEMO::="Design & Engineering Methodology for Organizations", [ http://www.demo.nl/ ]
Special colored Petri nets show logic. Can be simulated to show clients what is possible.
Analyze business processes in terms of the language-action cycle as expressed as Transactions between parts.
Transaction::=Order; Execution; Result.
Order is a transition from initiator to executor. It sets up a contract for the executor to carry out.
Result is a transition from executor to initiator. It completes the contract.
Execution is executed by the executor and can initiate further transactions with others.

Barlas96

Stephen Barlas
Anatomy of a Runaway: What Grounded the AAS(Advanced Automation System)
IEEE Software Magazine V13n1(Jan 1996)pp104-106
Failure of a 10 year life-cycle at edge of technology at start with 99.99999% reliability and dynamic loose REQUIREMENTS [Barlas96a]

Barlas96a

Stephen Barlas
FAA Shifts Focus to Scaled-Back DSR
IEEE Software magazine V13n3(Mar 1996)pp110+114
[Hall96a]
[Barlas96]
[KlosterZellweger87]

BarnardPrice94

Jack Barnard & Art Price
Managing Code Inspection Information
IEEE Software magazine v11n2(Mar 1994)pp59-69
=EXPERIENCE QUALITY control of SQA

Barnesetal91

Bruce H Barnes & Terry H Bolinger
Making Reuse Cost-Effective
IEEE Software v6n1(Jan 1991)pp13-24

BarnettEtAl11

Mike Barnett & Manuel Fahndrich & K Rustin M Leino & Peter Muller & Wolfram Schulte & Herman Venter
Specification and Verification: the Spec# Experience
Commun ACM V54n6(Jun 2011)pp81-91 [ 1953122.1953145 ]
=ADVERT CONTRACTS MICROSOFT C# .NET IDE SPECIFICATION LANGUAGE Spec# TOOLS PRECONDITIONS POSTCONDITIONS INVARIANTS Boogie CCI Z3 PROOFS Spec#
Planned to hide the proofs from the programmers!
Contracts written in the programming language.
Display contract as a tool-tip on a call.
Treat static mismatched conditions as if they were syntax errors.
Distinguishes between pointers and guaranteed non-null pointers.
Provide static and dynamic checking of conditions.
Can supply many loop invariants automatically.
To be useful it must be integrated into a real language and IDE.

Barnhart95

Andy Barnhart
Let's Get Stupid
Software Development Mag V3n3(Mar 1995)pp63-67.
=ESSAY TECHNICAL
advantages for going for the obvious simple solution that works.
problems with inspired brilliant solutions.
The algorithm that suddenly starts to work when you are playing with it and you don't know why.
Documenting Magic.

Barnhart99

Andy Barnhart
Wrapping COBOL Business Logic in Java
Software Development Mag V7n10(Oct 1999)pp41-45.
=EXPERIENCE TECHNICAL COBOL JAVA GUI LEGACY
MARS UK RLSCOM Telco marketting cellular air time

Barrett87

Geof Barrett
Formal Methods Applied to a Floating Point Number System
Technical Monograph 58 PRG Oxford 1987
=EXPERIENCE PROOF Floating-point operations STANDARD

Barrett95

Geof Barrett
Model Checking in Practice: The T9000 Virtual Channel Processor
IEEE Trans on Software Eng VSE-21n2(Feb 1995)pp69-78
=EXPERIENCE SQA INSPECTIONS MODEL CHECKING FORMAL NOTATIONS STD CSP Z English
Sometime implementation was correct when the spec was wrong
Easier to show what can happen than to show that something can not happen
Problem with notation(CSP) - "completely alien" to people used to STDs.
Quote: "Must base our tools on familiar notations and understand the obstacles...this means that visual specifications have to be used as much as possible."
Using multiple notations. STDs+Z+English.
Using checker for finite sequences.
Need an unusual combination of engineering, mathematical and programming skills

BarryStanienda98

Douglas Barry Torsten Stanienda
Solving the Java Object Storage Problem
IEEE Computer magazine V31n11(Nov 1998)pp33-40
=DEMO TECHNICAL JAVA JDBC ODMG persistence SQL

Basili90

Victor R Basili
Viewing Maintenance as Reuse-oriented Software Development
IEEE Software V7n1(Jan 1990)pp19-25
System Technical

Basili95

Victor Basili(interviewed)
Finding an Experimental Basis for Software Engineering
IEEE Software Magazine V12n3(May 1995)pp92-93
=ADVERT EMPIRICAL GQM QUALITIES EXPERIMENTS PROCESS IMPROVEMENT EXPERIENCE
The Software Engineering Laboratory
Goal/Question/Metric paradigm
QUALITY Improvement Paradigm
A separate Experience Factory
"The process is a variable to be manipulated"
"You can't just hand developers a tool or a method and walk away[...]be there as a resource,[...]supply cost models[...]types of defects[...]uncovering that class of defects[...]"
ISERN::=International Software Engineering Research Network.
Also see [Basili95a]

Basili95a

Victor Basili
The Experience Factory and its Relationship to Other Quality Approaches
Advances in Computers V41(1995)pp66-82
=EMPIRICAL QUALITY IMPROVEMENT EF/QIP vs PDCA:=Plan_Do_Check_Act + TQM + SEI CMM
Also see [Basili95]

BasiliBriandMelo96

Victor R Basili & Lionel C Briand & Walcelio L Melo
How Reuse Influences Productivity in Object-Oriented Systems
Comm ACM V39n10(Oct 1996)pp104-116
=experiment OMT Gnu C++ OSF/Motif
significant benefits in defect density rework and productivity

BasiliDonzelliAsgari04

Victor Basili & Paolo Donzelli &Sima Asgari
A Unified Model of Dependability: Capturing Dependability in Context
IEEE Software Magazine V21n6(Nov /Dec 2004)pp19-25
=CASESTUDY UMD TOOL THEORY QUALITIES DEPENDABILITY TSAFE
Jargon! Students simulate stakeholders?

Basilietal95

Victor Basili & Frank McGarry & Jerry Page & Sharon Waligora & Rose Pajerski
SEL's Software Process-improvement Program
IEEE Software Magazine(Nov 1995)pp83-87
=ADVERT SPIN SEL IMPROVEMENT
20 years: 75% fewer defect+50% reduction in cost+25% reduction in cycle time while complexity increased
understand; Assess&Refine;Pakage
significant changes come from Cleanroom and SQA techniques not PDL/Ada/OO.

BasiliEtAl10

Victor R Basili & Mikael Lundvall & Myrna Regardie & Carolyn Seaman & Jens Heidrich & Jurgen Munch & Dieter Rombach & Adam Trendowicz
Linking software development and business strategy through measurement
IEEE Computer Magazine V43n4(Apr 2010)pp57-65
=ADVERT GOAL QUESTION METRIC GQM+STRATEGIES
GQM::= See http://en.wikipedia.org/wiki/GQM.
Formalizes link between business level goals and strategies to software development goals, questions, and metrics.
See previous items for Basili and GQM.

BasiliMcGarryPajerskiZelkowitz02

Victor Basili & Frank E McGarry & Rose Pajerski & Marvin V Zelkowitz
Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory
ICSE24(May 2002)pp69-79 CR 0406-0749
=UNREAD =HISTORY IMPROVEMENT NASA SEL
Need management & staff support + focus & data.

BasiliPerricone84

Victor R Basili & Barry T Perricone
Software Errors and Complexity: An Empirical Investigation
Commun ACM V27n1(Jan 1984)pp42-42 + Correspondence V28n3(Mar 1985)pp322-323 (with Richard J Botting, H Dieter Rombach & Richard W Selby)
=EMPIRICAL DEFECTS MODULE COMPLEXITY SIZE SEL CHANGES
New application means requirements change during the project.
New modules have different kinds of errors than changed modules.
Module size did not account for error proneness.
Intuition clashes with data.

BasiliRombach87

Victor R Basili & H Dieter Rombach
Implementing Quantitive SQA: A Practical Model: Guest Editor's Intro to theme articles
IEEE Software V4n5(Sep 1987)pp6-61
=EMPIRICAL QUALITY

BasinDoserLodderstedt06

David Basin & Jurgen Doser & Torsten Lodderstedt
Model driven security: from UML models to access control infrastructures
ACM TOSEM Trans Software Eng & Methodology V15n1(Jan 2006)pp39-91
=DEMO MDA MODEL SECURITY ASPECT RBAC SecureUML DIALECT Java JB2EE .NET
Extends RBAC using UML metamodeling.
RBAC::= Net{Users, Roles, Permissions: Sets. POSET(Roles, <=). UA:@(Users, Roles). PA:@(Roles, Permissions). AC:=UA o <= o PA.}.
A user u can execute action a iff u AC a.
Extend RBAC by adding a hierarchy of Actions.
Shows how to generate complex & secure code by translating a UML model with SecureUML profile.

Baskerville93

Richard Baskerville
Information Systems Security Design Methods: Implications for Information Systems Development
Comp Surveys V25n4(Dec 1993)pp375-414 (history of systems analysis ::=check lists; mechanical; abstraction)

BaskervilleEtal01

Richard Baskerville & Linda Levine & Jan Pries-Heje & Balasubramaniam Ramesh & Sandra Slaughter
How Software Companies Negotiate Quality
IEEE Computer Magazine V34n5(May 2001)pp51-57
=POLL MARKET TIME QUALITIES drive PROCESS ONE-SIZE
toad_code::= "working code that was developed hopping fast and is ugly"

BaskervilleEtAl03

Richard Baskerville & Balasubramaniam Ramesh & Linda Levine & Jan Pries-Heje & Sandra Slaughter
Is Internet-speed software development Different?
IEEE Software Magazine V20n6(Nov/Dec 2003)pp70-77
=COLLOQUIUM INTERNET WWW/net AGILE
Answer=YES!
Concurrent operation and development but no maintenance, fast releases, tools, customers in team, stable architecture, assemble and reuse components, evolve methodology, people!

GrafLormansToetenel03

Bas Graf & Marco Lormans & Hans Toetenel
Embedded Software Engineering: The State of the Practice
IEEE Software Magazine V20n6(Nov/Dec 2003)pp61-69
=POLL 36 INTERVIEWS EMBEDDED REQUIREMENTS ARCHITECTURE MOOSE ITEA UML
Hardware driven, top-down: system drives subsystem drives component. At each stage the previous architecture becomes a requirement in the next level.
Stakeholders ={manufacturing, maintenance, marketing(users/consumers)}.
Context = { Suppliers, standards, legacies, regulators }
Requirements expressed in text using word processors and templates. Informal diagrams. Use cases from the UML. Some sequence diagrams and domain models. Pre/post conditions in programming. Only one formal specification(in Z).
Managing changing requirements: spreadsheets.
Architecture: vs time-to-market. Creative.
Performance: design for maximum speed possible, hope, and test. UML popular with Visio and Rose. DFDs. ERDs. HatleyPirbhai.
Reuse: Ad hoc.
Memory, power and real time less prominent than expected.
Modern methods/technologies: vs legacy systems, are too immature and complex,

BassNordWoodZubrow06

Len Bass & Robert Nord & William Wood & David Zubrow
Risk Themes Discovered Through Architecture
=EXPERIENCE RISK ARCHITECTURE ATAM QUALITY
Tech Report CMU/SEU-2006-TR-012
ATAM::="Architecture Tradeoff Analysis Method".
Lists 15 Risk Theme Categories: Availability, Performance, security, modifiability, integration, process and tools, requirements, allocation, documentation, Big Picture, Unrecognized needs, product lines, awareness, scope, coordination.
Claims 99 risk themes.
Reference to Boeing experience with ATAM and Charette's failure causes.
Relation to business goals.
Importance of "Performance" .
No evidence that risks are independent of domain. One size does not fit all.
Risks of commission and Omission. Omission more common.
Odd fact: security was always a risk of omitting to do something.

Bassett94

Paul Bassett
Reusability: You Reap What You Sow
Software Magazine(Sep 1994)pp110-109
1. productivity, quality, flexibility, performance, portability, standards, hidden complexity, compatibility, reduced maintenance, evloution of common parts.

Bastanied93

Farokh Bastani
Special Issue on Software Reliability
IEEE Trans on Software Eng VSE-19n11(Nov 1993)pp1013-1118

BastenSunyaev11

Dirk Basten & Ali Sunyaev
Guidelines for software Development Effort estimation
IEEE Computer V44n10(Oct 2011)pp88-90
=SURVEY 50 EMPIRICAL PAPERS ACCURACY ESTIMATES 32 FACTORS ADVICE
Make sure that the estimator includes an estimate of accuracy
Collect as much information as possible -- especially similar projects
Include feedback in the estimation process.
Estimator must understand the technical and managerial issues.
Professional developers should do their own estimates.
Select estimators who can learn from feedback.
Exclude optimists
Make requirements precise
Avoid anchors
Split large classes into parts, estimate and combine
Communicate frequently with clients.
Get more diligence from client by staing the importance of the project.
Use expertise to support inexperienced clients to get better requirements.

BasterKonanaScott01

Greg Baster & Prabhudev Konana & Judy E Scott
Business Components: A Case Study of Bankers Trust Australia Limited
Commun ACM V44n5(May 2001)pp92-98
=CASESTUDY DOMAIN TECHNOLOGY USER COMPONENTS ARCHITECTURE MODULES Arcadia
B_T_gap::= "Business-Technology Gap", a clash of subcultures.
Important to get shared knowledge and resolve cultural values.
Give the business users the ability to assemble applications from a repository of components.
lessons learned:=following,
1. understand the gap.
2. understand usage patterns to minimize costly disruption.
3. leverage user skills.
4. Low profile and low hype.
5. involve the detail-oriented users and allow word-of-mouth diffusion.
6. long prototyping process.
7. Leverage technical skills vs use skills -- technical optimize, users work out script details.
8. Plan for reuse but not as a central focus. components evolve. user acceptance and buyin must come before reuse.

Batoryetal95

Don Batory(utexas) & Lou Coglianese & Mark Goodwin & Steve Shafer(Loral)
Creating Reference Architectures: An Example from Avionics
See [SamadzadehZand95]
pp27-37
=CASE-STUDY ADAGE REUSE GenVoca realms DOMAIN [BatorySighalSirkinThomas93] [BatorySighalThomasetal94] [ Batoryetal95.html ]
Gathering simple info was the most difficult aspect.
Twice the cost and effort of a single system.

BatoryEtal00

Don Batory & Gang Chen & Eric Robertson & Tao Wang
Design Wizards and Visual Programming Environments for GenVoca Generators
IEEE Trans Software Engineering V26n5(May 2000)pp441-452
=DEMO TOOL DSL ARCHITECTURE P3 DATA PERFORMANCE JAVA JTK
Containers and cursors, type equations, optimization NP-hard
[ schwartz ]

BatoryEtal02

Don Batory & Clay Johnson & Bob MacDonald & Dale Vov Heeder
Achieving Extensibility Through Product-lines and Domain-Specific Languages
ACM TOSEM Trans Software Eng & Methodology V11n2(Apr 2002)pp191-214
=CASESTUDY ASPECTS ARCHITECTURE GenVoca PLAs DSLS REUSE FSMs Java JavaSM
Features as first-class components that cross-cut across OO hierarchies

BatoryGeraci97

Don Batory & Bart J Geraci
Composition Validation and Subjectivity in GenVoca Generators
IEEE Trans Softw Eng V23n2(Feb 1997)pp67-82
how to verify composition rules and how to allow multiple interfaces to components

BatorySighalSirkinThomas93

Don Batory & Vivek Sighal & Marty Sirkin & Jeff Thomas<*@cs.utexas.edu>
Scalable Software Libraries [Notkin93] pp191-199
GenVoca [BatorySighalThomasetal94]

BatorySarvelaRauschmayer04

Don Batory & Jacob N Sarvela & Axel Rauschmayer
Scaling Step-Wise Refinement
IEEE Trans Software Engineering V30n6(Jun 2004)pp355-371 & ICSE 2003
=TOOL GENERATE CODE FEATURE REFINEMENT SWR AHEAD Gen Voca ATS JAX Java
AHEAD::= "Algebraic Hierarchical Equations for Application Design".
Refinements apply to many types of artifacts(eg. Java code, Makefile, ...) in a uniform way.
Artifacts treated as indexed collections (code=name<>->class, Makefile=target<>->action,...)
A product is described as a set of equations in terms of features and the code is generated automatically.
Two operations: A \dot B adds A to B. A \diamond B replaces items in B by matching A items.
meta-modelling: Options and product lines described as unindexed sets.
Origami::= Describe each concern in a separate equation.

BatorySighalThomasetal94

Don Batory<batory@cs.utexas.edu> & Vivek Sighal & Sankar Dasari & Jeff Thomas & Marty Sirkin
The GenVoca Model of Software-System Generators
IEEE Software Magazine V11n5(Sep 1994)pp89-94
1. Examples Genesis and Predator
2. P++ language on top of C++
3. abstraction encapsulation and parameterization
4. realms, components, parameters
5. components encapsulate classes etc
6. realms describe sets of components
7. components act as transformers of input classes into new outut classes
8. parameters for constants, types, realms, components,...
  Example: Data Structures in terms of containers, cursors, and links.

Batra09

Dinesh Batra
Modified agile practices for outsourced software projects
Commun ACM V52n9(Sep 2009)online [ 1562164.1562200 ]
=THEORY AGILE DISTRIBUTED
You have to modify agile methods when the team is not co-located.

BaudryEtal05

Benoit Baudry & Franck Fleurey & Jean-Marfc Jezequel & Yves Le Traon
Automatic Test Case Optimization: A Bacteriologic Algorithm
IEEE Software Magazine V22n2(Mar/Apr 2005)pp76-81
=IDEA C# PARSER BUILDER VISITOR TESTING MUTATION EVOLUTION FITNESS
Nice use of patterns in the sample Component Under Test (CUT) a C# parser.
Need 30 generations to produce a set of tests that could kill all 500 mutants.

Bauer92

Henry H Bauer
Scientific Literacy and the Myth of the Scientific Method
U of Illinois Press Urbana Ill. QA175.B25 1992 ISBN 0252018567
=SURVEY SCIENCE STS SOCIAL PROCESS
not method but diverse error-correcting social processes.
jigsaw puzzle filter:=(human, frontier science, primary literature, secondary literature, textbook science, ...)
proponents haven't been good testers.
scientific knowledge is more like a map than a collection of facts
prediction is not proof but helps, if theory useful fitting inteqesting
includes innovation vs conservative
needs explicit enforced ethics
Compare [Lakatos76] on mathematics.

Baxter92

Ira D Baxter
Design Maintenance Systems
Commun ACM V35n4(Apr 1992)pp73-89
=EXPERIENCE MAINTENANCE DESIGN vs CODE
design deltas analysed(function, performance,...) and lead to implementation deltas,
Transformation Control Language(TCL)
Author sent me EMail... Quote from bibtex entry:

Bayes1763

T Bayes
An essay towards solving a problem in the doctrine of chances
Phil Trans Royal Society V53(1763)pp370-418
=THEORY PROBABILITY BELIEF
Bayes approach to probability was to assume that the number represented the degree of belief a person had in the proposition.
He worked argued that a rational person would have to follow certain rules. For example is P(A|B) is the probability of A given that B is true, then
P(A&B) = P(A|B)*P(B).
He worked out rules for rationally reevaluating the beliefs as new data came in.
The heart of this is:
(Bayes)|- (Bayes_theorem): if H is a set of mutually exclusive events, and E some new evidence, then for h:H, P( h | E) =P( E |h )*P(h )/Σ[h:H](P( E | h )*P(h)).
The Wikipedia has a good discussion [ Bayes_theorem ] of this result.

BayrakDavis03

Coskun Bayrak & Chad Davis
The Relationship between Distributed Systems and Open Source development
Commun ACM V46n12(Dec2003)pp99-102
=ESSAY OPEN SOURCE NONSEQUENTIAL PERFORMANCE OSD WWW/NET MARX MicroSoft W3C
Analogy: Higher speeds in distributed computation come from NOT controlling and coordinating them but letting them loose. allowing a degree of inconsistency to develop is often a way to speed up the result.
Tension between capital and craft..Close

BCS/IEE89

British Computer Society & Institution of Electrical Engineers
A Report on Undergraduate Curricula For Software Engineering
BCS London UK 1989
=CURRICULUM

Beale07

Russell Beale
Slanty design
Commun ACM V50n1(Jan 2007)pp21-24
=IDEA USER FUNCTION DESIGN
Slanty_design::= reduce functionality or usability to make unwanted behavior difficult or impossible. Image: slanty tops to stop people putting things on them.

BeauvaisEtal01

J-R Beauvais & E Rutten & T Gautier & R Houdebine & P Le Guernic & Y-M Tang
Modeling Statecharts and Activitycharts as signal equations
ACM TOSEM Trans Software Engineering & Methodology V10n4(Oct 2001)pp397-451
=THEORY TRANSLATION FSM statecharts denotation semantics Signal DC+ TOOL Sacres
Signal::language.

BeauxisPalamidessiValencia08

Ramain Beauxis & Catuscia Palamidessi & Frank D Valencia
On the asynchronous Nature of Asynchronous π-Calculus
Montanari Festschrift [DeganoEtAl08] pp473-492
=THEORY NONSEQUENTIAL BAGS QUEUES STACKS PI-CALCULUS
Proves that to get behavior equivalent to π[a] (Asynchronous Pi Calculus) you need a normal π calculus where communication is through buffered channels that act as buffers. Queues and stacks can not simulate all π[a] behaviors.

Beck99

Kent Beck(First Class Software)
Embracing Change with Extreme Programming
IEEE Computer Magazine V32n10(Oct 1999)pp70-77
=ADVERT =EXPERIENCES =HISTORY OBJECT-ORIENTED PROCESS METHOD XP
See book [Beck99b]

Beck99b

Kent Beck(First Class Software)
Extreme Programming Explained: Embrace Change
Addison Wesley October 1999
=ADVERT XP OBJECT-ORIENTED PROCESS METHOD
XP::="Extreme Programming", continuous analysis, many tiny (Analysis;Design;Implementation;Test) iterations driven by feedback from previous iterations.
Planning game, small releases, put what the user needs on 3 by 5 cards called user stories, metaphor as a collection of user stories, simple design(say everything once and only once),
programmers are always testing, customers also provide tests, merciless refactoring,
pair programming, continuous integration(within hours), collective ownership of code,
on-site customer, 40.hour weeks, open worksapce, Just Rules.
See [Beck99] and WikiWiki Reviews: [ wiki?ExtremeProgrammingExplainedEmbraceChange ]

Beck00a

Kent Beck
Emergent Control in Extreme Programming
Cutter IT Journal V13n11(Nov 2000)pp22-25
=ADVERT TECHNICAL PROCESS XP
XP :={ test first, planning game, short release cycle, pair programming, onsite customer, opn workspace, yesterday's weather, refactoring, continuous integration, collectiveownrship, simple once-and-only-once design, sane hours }.
control can be in the rules rather than embodied in person.

Beck01

Kent Beck
Aim, Fire
IEEE Software Magazine V18n5(Sep/Oct 2001)pp87-89
=DEMO TESTING first is ANALYSIS DESIGN SPECIFICATION
"Never write a line of functional code without a broken test case".
Ward Cunningham: "Test-first coding is not a testing technique".
Writing tests helps you understand the problem: analysis.
Writing tests described the logic of the design.
Hard to write GUI tests.
Claim that creatively lazy test-first coding tends to be more cohesive and less coupled -- because the interfaces tend to be minimized to saving typing: "intense feedback substitutes for the ability to guess right"
Test cases expose misunderstandings in pair programming.
Test cases document the all important answer to "What was this idiot thinking when he wrote this?".

Beck02

Kent Beck
Test-driven development: by example
Addison-Wesley Longman Boston MA 2002 ISBN 0321146530 [CR] 0308-0733
=TUTORIAL TEST REFACTOR DESIGN JUnit xUnit Python

Beck06

Kent Beck
Implementation Patterns
Addison-Wesley Pro, Boston MA, 2006 ISBN 0321413091 CR 0903-0209 Safari [ 9780321413093 ]
=THEORY PATTERNS Class State Behavior Collections Frameworks Performance TECHNICAL CODE = EXPERIENCE JUnit HotDraw
Lots of detailed advice on object-oriented coding.

BeckCunningham89

Kent Beck & Ward Cunningham
A Laboratory for Teaching Object-Oriented Thinking
OOPSLA'89 conf Proceedings ACM SIGPLAN V24n10(Oct 1989)pp1-6
=IDEA OBJECT_ORIENTED cards CRC_CARD
[ paper.html ]
Refers to [Wirfs-BrockWilkerson89]
1. CRC_Card::physical=index_card(4.inch><6.inch), available, inexpensive, erasable.
2. CRC::abbreviation="Class, Responsibility, Collaboration".
3. CRC::=Net{C:=class:name_of_component, R:=responsible_for:%Responsibilities, C:=collaborators:%name_of_component}.
  Walking through a scenario: tracing an "application assigning each activity to some component". each CRC card held by a different member of the team Often a cycle of What/Who questions: #(what_next; who_does_it).

BeckR10

Roman Beck
Can IT lean against the wind?
Commun ACM V53n5(May 2010)pp38-40 [ 1735223.1735238 ]
=EXPERIENCE RISKS BANKING FINANCE STANDARDS
Financial systems had emergency backups that handled catestrophes like 2001/9/11 and 2005/7/7 well. Even with major servers down transactions continued to be cleared. They were not prepared to handle the task of evaluating complex credit risks at the speed needed to ameliorate the 2008 collapse. These required gathering data from many incompatible databases. In haste most assumed they were ok.
Then all transactions assumed risky and stopped. Liquidity dried up.
Transaction data are standardized but not evaluation data.

BeckerMottay01

Shirley A Becker & Florence E Mottay
A Global perspective on web site usability
IEEE Software Magazine V18n1(Jan/Feb 2000)pp54-61
=THEORY USER WEB/NET DESIGN international
usability on the web ==> layout + navigation + consistency + customer service + reliability + security + performance + visible content

Beckman12

Brian Beckman
Why LINQ matters: cloud composability Guaranteed
Commun ACM V55n4(Apr 2012)pp38-44 [ 2133806.2133820 ]
=ADVERT UNREADABLE MS LINQ FUNCTIONS LAMBDAS URI SQO
Language Integrated Query
Abstract trees of operators (SQOs) can be defined, transmitted, received and interpreted as queries on data structure and data bases.
REST::acronym="representational state transfer".
URI syntax for queries.
SQO::acronym="standard query operators"
Lambdas: variable => body. The body can be a predicate or a transformation.
Also see [Meijer11]

BeckmanEtAl10

Nels E Beckman & Aditya V Nori & Sriram K Rajamani & Robert J Simmins & Sai Deep Tetali & Adtya V Thakur
Proofs from tests
IEEE Trans Software Engineering V36n4(Jul/Aug 2010)pp495-508
=DEMO ALGORITHM DASH POINTERS SUBPROGRAMS SOUND ABSTRACTION SYMBOLIC EXECUTION ALIASES TOOL YOGI Microsoft PLUGIN SLAM EXE BLAST SYNERGY
Tests under-approximate and abstractions over-approximate the Programs behavior.
Try to find a symbolic test that reaches an error state or find a precise enough abstraction to prove that no path leads to an error state.

BeckwithEtal06

Laura Beckwith & Marget Burnet & Valenline Grigoreanu & Susan Wiedenbeck
Gender HCI: What about software?
IEEE Computer Magazine V39n11(Nov 2006)pp97-101
=EXPERIMENT USER GENDER HCI MALE FEMALE self-efficacy tinkering
Men & women use spreadsheet tools differently. Men like exploring features for fun but women with low self-efficacy want to use them to solve problems.
Do software development tools put girls off?

BedersonGrosjeanMeyer04

Benjamin B Bederson & Jesse Grosjean & Jon Meyer
Toolkit Design for Interactive Structured Graphics
IEEE Trans Software Engineering V30n8(Aug 2004)pp535-546
=COMPARISON Object-Oriented LIBRARY DESIGN INHERITANCE vs COMPOSITION Java Swing GRAPHICS Jazz
Piccolo Goal: an extensible structured graphics toolkit.
Have many shapes and can add new ones easily.
Jazz::= See http://www.cs.umd.edu/hcil/jazz/.
Piccolo::= See http://www.cs.umd.edu/hcil/piccolo/.
polylithic::design_styles="mainly using run-time composition to extend...". Many small classes, Easier to create but harder to use,
monolithic::design_styles="mainly using compile-time inheritance to extend...". Few large classes. Harder to create but easier to use.
(dick)|-Polylithic designs seem to use the GoF patterns.
(dick)|-perhaps use composition for explore the domain and then reify functionality into a stable product.

Bednarz11

Ann Bednarz
How IBM started Grading is developers' productivity
InfoWorld (Nov 07 2011) [ how-ibm-started-grading-its-developers-productivity-178302 ]
=REPORT IBM CODE METRICS TECHNICAL Cast OBJECTIVES QUALITIES
Used tool to develop community standards and scoring programmers -- giving feed back on quality of code.

Beebe99

TeX User Group bibliography archive
=BIBLIOGRAPHY of mathematics+computing journals+magazines
[ http://www.math.utah.edu/ftp/pub/tex/bib/toc/ ] Nelson H. F. Beebe Center for Scientific Computing University of Utah Department of Mathematics, 322 INSCC 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA beebe@math.utah.edu [ http://www.math.utah.edu/~beebe/ ]

Beer74

Stafford Beer
Designing freedom
London Wiley 1974
=ESSAYs RISKS Cybernetics NET/WWW

Beeson81

Michael J Beeson
Formalizing Constructive Mathematics: Why and How?
Constructive Mathematics Spring Verlag Lecture Notes in Mathemetics V873 pp146-190 1981
=THEORY FORMAL LOGIC
LPT::="Logic of Partial Terms"
Compare [Schock68] [Parnas93] [JonesCB95] and [PVS] LPF:=Logic of Partial Functions

BegayRauzy01

Diddier Begay and A. Rauzy
A realistic involvement of formal methods
Software - Practice & Experience V31n2(Feb 2001)pp191-208
=Type FORMAL HARDWARE VERIFICATION CTL SMV Aralia PVS

BehrendsStirewalt00

Reimer Behrends & R E Kurt Stirewalt
The Universe Model: An approach for Improving the Modularity an Reliability of Concurrent Programs [FSE8] pp20-29
=CASESTUDY NONSEQUENTIAL MODULES TECHNICAL OBJECT-ORIENTED
Problems with interleaving many threads through one piece of code. Hard to separate concurrency control from useful code, modularity damaged. multi-step synchronization uncheckable.
Objects in a universe and each universe can host at most one process at a time. No execution of code outside the process's universe.
realm constraints control movement of processes between universes.

BekkeringShim06

Ernst Bekkering & J P Shim
i2i trust in videoconferencing
Commun ACM V49n7(Jul 2006)pp103-107
=EXPERIMENTS VIDEO MEDIA USER PEOPLE RISKS
i2i::cummunication="individual to individual"
Videophones and videoconferences discourage trust because the camera is not directly behind the screen. If you look at the screen then you don't make eye contact with the person at the other end, and vice versa.
Result: people trust voicemail and E-mail more than video.
Cell phones and PDAs may not have this problem.
Solution: variation on the "Reagan sincerity machine" which lets you look directly at the camera while seeing an image on a screen (e.g. a script).

Bekkerman04

Anna Bekkerman
Conflict Resolution and Operator Priorities in Extended BNF
=IDEA =DEMO EBNF PARSING CFG GRAMMAR =TOOL Java JAMOOS
Ph.D. Thesis(Technion Israel July 2004) [ thesis_anna.pdf ]
Improve BNF by allowing the specification of priorities and removing other ambiguities.

Bekic70

H Beki\'c (IBM Lab Vienna)
On the Formal Definition of Programming Languages
International Computer Symposium 1970
=CASE-STUDY VDL/VDM PL/I formal

BelagerEtal06

France Belanger & Weiguo Fan & L Christian Schaupp & Anjala Krishen & Jeanine Everhart & David Poteet & Kent Nakamoto
Web site successMetrics: Addressing the duality of Goals
Commun ACM V49n12(Dec 2006)pp114-116
=ESSAY REQUIREMENTS TAXONOMY METRICS WEB/NET PURPOSES OWNERS vs USERS
Success defined by owner goals + target audience.
Table p115 has 11 distinct types of goal.
Choose 2 sets of metrics: Owner vs user perspectives.

BelinaHogrefeSarma91

F Belina & D Hogrefe & A Sarma
SDL with Applications from Protocol Specifications
Prentice Hall Upper Saddle River NJ 1991 ISBN 0-13-785890-6 BCS Practitioner Series
=TEXT-BOOK SDL SPECIFICATION
a gradual introduction to SDL concepts illustrated by real examples (including an approach to X.25) together with an appendix with complete rules for use of the language.

Bell04

Alex E Bell (+ comment by Grady Booch)
Death by UML Fever
ACM Queue V2n1(Mar 2004)pp72-81
=JOKE HARMFUL UML
Lists a couple of dozen abuses of UML, including a classic "Circle the wagons" Use Case.

Bell08

Alex E Bell
Software Development amidst the whiz of silver bullets
=JOKE FADS XML UML OO WEB SERVICES
Commun ACM V51n8(Aug 2008)pp22-24 [ 1378704.1378712 ]
Names some previous failed fads.
Describes current (200n) fads.
Fads sound good but do not solve the real problems of software development.

BellSchmidt99

Alex E Bell & Ryan W Schmidt
UMLoquent Expression of AWACS Software Design
Commun ACM V42n10(Oct 1999)pp55-61 in [Booch99]
=EXPERIENCE DEMO EVOLUTION UML Boeing NMT ARCHITECTURE CORBA Ada
Notes value of the UML and some weak areas in the UML and need to improvise

BelliGrosspietsch91

Fevzi Belli & Karl-E. Grosspietsch
Specification of Fault-Tolerant Systems Issues by Predicate/Transition Nets and Regular Expressions -- Approach and Case Study
IEEE Trans SE v17n6(Jun 1991)pp513-526
Bullet proofing Technical

BelliniFioravantiNesi99

Pierfrancesco Bellini & Fabrizio Fioravanti & Paolo Nesi
Managing Music in Orchestras
IEEE Computer Magazine V32n9(Sep 1999)pp26-34
=DEMO MUSIC OBJECT-ORIENTED MOODS NETWORKED LANGUAGES HCI

BelliniMattoliniNesi00

P Bellini & R Mattolini & P Nesi
Temporal Logics for Real-time system specification
ACM Computing Surveys V32n1(Mar 2000) pp12-42
=SURVEY LOGIC TIMING RTL RTIL RTTL
WWW link to ACM Digital Library: [ p12-bellini ]
From Abstract:
The specification of reactive and real-time systems must be supported by formal, mathematically-founded methods in order to be satisfactory and reliable. Temporal logics have been used to this end for several years. Temporal logics allow the specification of system behavior in terms of logical formulas, including temporal constraints, events, and the relationships between the two. In the last ten years, temporal logics have reached a high degree of expressiveness. Most of the temporal logics proposed in the last few years can be used for specifying reactive systems, although not all are suitable for specifying real-time systems. In this paper we present a series of criteria for assessing the capabilities of temporal logics for the specification, validation, and verification of real-time systems. Among the criteria are the logic's expressiveness, the logic's order, presence of a metric for time, the type of temporal operators, the fundamental time entity, and the structure of time. We examine a selection of temporal logics proposed in the literature. To make the comparison clearer, a set of typical specifications is identified and used with most of the temporal logics considered, thus presenting the reader with a number of real examples.

BellinSimone97

David Bellin & Susan Suchman Simone
The CRC Card Book
Addison Wesley 1997 ISBN 0-201-89535-8 QA76.64 b437 1997
=HOWTO CRC Object-Oriented ANALYSIS PURPOSE SCENARIO CRC DESIGN CARD ROLE-PLAY TECHNICAL Smalltalk C++ Java UML MANAGEMENT

BellinzonaEtal95

Roberto Bellinzona & Maria Grazia Fugini<fugini@ipmel1.polimi.it> & Barbara Parnici<pernici@elet.polimi.it>
Reusing Specifications in OO Applications
IEEE Software Magazine V12n2(Mar 1995)pp65-75
1. IOOM::=Ithaca OO methodology.
2. F-ORM::=Functionallity in Objects with Roles Model. object--<view>--role-->FS.ELH
  Basic problm is identifying matching components.
3. Fuzzy matching against: verb-object, thesauri or semantic network ...., structures pairs Telos organizes knowledge in levels
  "Final document contains the set of graphical representations, the component documentation, and a trace of the steps."

BellLabs83

Unix Programmer's Manual
NY NY Holt Rinehart & Winston (2 Vols)
=handbook non-sequential tools pipe

BellNewell70

C Gordon Bell & Allen Newell
The PMS and ISP descriptive systems for computer structure
Proc AFIPS Spring Joint Comp Conf (??? 1970)pp351-374 [ PMS%20and%20ISP%20Descriptive%20Systems%201970%20c.pdf ] (PDF)
=IDEA HARDWARE DESCRIPTION PMS Processor-Memory-Switch ISP Instruction-Set-Processor
Also see [BellNewell71] for details and examples of ISP and PMS.

BellNewell71

C Gordon Bell & Allen Newell
Computer structures: Readings and examples
McGraw-Hill computer science series circa 1971 ISBN 0070043574 TK7888.3.B37
=EXAMPLES 1960s =SURVEY HARDWARE DESCRIPTIONS Burroughs CDC DEC PDP Deuce KDF9 IBM SDS UNIVAC

BellSiewiorek11

Gordon Bell & Daniel P Siewiorek
The Book "Computer Structures": Thoughts after 40 years
IEEE Annals V33n2(Apr-Jun 2011) [ MAHC.2011.47 ]
=HISTORY DOCUMENTING ANALYSING COMPUTER SYSTEMS HARDWARE
Anecdotes and examples from [BellNewell70] and [BellNewell71]

BellonEtAl07

Stefan Bellon & Rainer Koschke & Giuliano Antoniol & Jens Krinke & Ettore Merlo
Comparison and Evaluation of clone detection tools
IEEE Trans Software Engineering V33n9(Sep 2007)pp577-591
=EXPERIMENT TOOLS COPYPASTE DRY SOURCE Dup CloneDR CCFinder Duplix CLAN Duploc
Also see [BakerB07]

Ben-AbdallahEtal97

Hanene BenAbdallah & Insup Lee & Young Si Kim
The Integrated Specification and Analysis of Functional, Temporal, and Resource Requirements [RE'97] pp198-209
=DEMO TOOLS REQUIREMENTS LANGUAGE
GCSR::language="Graphical communicating Shared Resources".

Ben-AbdallahLeue97

Hanene BenAbdallah & S Leue
Timing Constraints in Message Sequence Chart Specifications
See [ tr97-04 in msc ]
=REPORT SCENARIO TIMING MSC SPECIFICATIONS
MSC::="Message Sequence Charts"

Ben-Ari10

Mordechai (Moti) Ben-Ari
A Primer on Model checking
ACM Inroads V1n1(Mar 2010)pp40-47
=ADVERT =EXAMPLES MODEL CHECKING EDUCATION Spin VN Erigone NDFA NON_SEQUENTIAL VERIFICATION MODAL LOGIC Promela IDE
The formula if not p then if p then q can be proved true by axiomatic methods but it is simpler and easier to check that it is true by trying out all 4 cases in a truth table.
Similarly, proving that a parallele non-deterministic program has a property is usually time consuming but there exist tools that will find counter examples in a reasonable time. Spin works in industry but can be wrapped in an IDE that works well with students.

Ben-Ari10a

Mordechai Ben-Ari
Objects Never? Well, Hardly Ever!
Commun ACM V53n9(Sep 2010)pp32-35 [ 1810891.1810905 ] Discussion V54n1(Jan 2011)p7
.See http://doi.acm.org/10.1145/1866739.1866741
=POLEMIC OOP PARADIGMS EXPERIENCE REUSE ONE SIZE
Match the paradigm to the problem.
Provide students with more than one paradigm!
Need published examples of OOP success and failure.
But
1. Ruby Quicksort
2. OOP or SP first?
(Close But )

Ben-ShaulHolderLavva01

Israel Ben-Shaul & Ophir Holder & Boris Lavva
Dynamic Adaptation and Deployment of Distributed Components in Hadas
IEEE Trans Software Engineering V27n9(Sep 2001)pp769-787
=DEMO TECHNICAL DISTRIBUTED DYNAMIC MODULE HADAS JAVA
Ways and means of allowing software components to be changed, moved, and remotely administrated.
Component interfaces have a fixed and a dynamic part.
Using reflection and introspection so that components can find out about each other -- but purpose and qualities are only described informally.

BenamatiLederer01

John Benamati & Albert L Lederer
Coping with rapid changes in IT
Commun ACM V44n8(Aug 2001)pp83-88
=POLL TECHNICAL CHANGE MANAGEMENT
Change is constant and is the most effective coping strategies are not applied.
Low cost learning is preferred.
Popular but ineffective: self education and bullying the vendor for support.
Unpopular but effective: consider new technology that is compatible with current, incentives to keep staff who know the new stuff, choose specific customized training not general informal education.
Review, think, plan, do, review, ....

Benbunnan-Fich02

Raquel Benbunnan-Fich
Improving Education and Training with IT
Commun ACM V45n6(Jun 2002)pp94-99
=SURVEY EDUCATION IDEA GRID
Education location><pedagogy><synchronocity.
location:= proximate..disperesed.
synchronocity:= synchronous..Asynchroonous
Pedagogy:=objectivist..Constructivist
Computer aided discussion etc makes no difference to mastery of topic(grades) but can effect what students feel.

BendraouEtAl10

Reda Bendraou & Jean-Marc Jezequel & Marie-Pierre Gervais & Xavier Blanc
A comparison of six UML-based languages for software process modeling
IEEE Trans Software Engineering V36n5(Sep/Oct 2010)pp662-675
=ADVERT UML4SPM PROCESS MODELING SPEM1.1 SPEM2.0 Di Nitto Promenade Chou
Languages are not formal enough and have few tools.
(dick)|-later process modeling languages use UML notation as is.

BenlarbiMelo99

Sa"ida Benlarbi & Walcelio L Melo
Polymorphism Measures for Early Risk Detection
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp334-344
=EMPIRICAL METRIC LALO Logistic Regression
relates measures of polymorphism with other metrics and fault proneness.
Polymorphism may increase fault proneness but not significantly. Static and dynamic polymorphism are similar. Both correlated to numbers of methods but not LOC.
See [BriandEtal99]

Bennett92

William S Bennett
Visualising Software: A graphical notation for analysis design and discussion
Marcel Dekker NY NY 1992

Benson93

David B Benson
Comparative Review of books on Category Theory for Computer Science
Computing Reviews V34n11(Nov 1993)pp577-579 (CR9311-0833)
=SURVEY CATEGORY Sets out a reading program.

Bentley84

J Bentley
Programming Pearls:Code Tuning
Commun ACM v27 n2 (Feb 1984) pp91-96
=CLASSIC BOOK optimization PERFORMANCE Technical

Bentley86

J Bentley
Programming Pearls
Addison Wesley Reading MA 1986
=CLASSIC BOOK case-study Technical
Also Knuth92

Bentley87

Jon Bentley
More Programming Pearls: Confessions of a Coder
Addison Wesley ma 1987
=case-study Technical

Bentley93

Jon Bentley
Do-It-Yourself Caching
UNIX Review V11n10(Oct 1993)pp95-104
=CAST-STUDY data performance case-study Technical

Berard89

Edward V Berard <sei!ajpo!eberard@pt.cs.cmu.edu>
Re: Attempts to connect SAD and OOPS
Software-Engineering-Digest/comp.soft.eng V6n37 & n40 & n42 Usenet/Internet 1989 + Personal communication(course notes 1989)
=CORRESPONDENCE object-oriented SAD Technical Semantic nets+STD+Petrie Nets

Berard93

Edward V Berard (Berard Software Engineering)
Essays on Object-oriented software engineering (vol 1)
Prentice Hall Englewood Cliffs NJ 1993
ISBN0-13-288895-5 CR9502-0058(comparative)

BergClineGirou95

William Berg & Marshall Cline & Mike Girou
Lessons Learned from the OS/400 OO Project
Commun ACM V38n10(Oct 1995)pp54-64
=EXPERIENCE REQRITE OBJECT_ORIENTED OPERATING SYSTEM SOFTWARE

BerczukLv10

Steve Berczuk & Yi Lv
We're all in this together
IEEE Software Magazine V27n6(Nov/Dec 2010)pp12-15
=ANECDOTE SCRUM INTRODUCTION AGILE MANAGEMENT
Certified Scrum Masters.
Scrum masters shouldn't be self selected at first. Lead and coach
Line managers command and control so at first shouldn't be scrum masters for their team.
Reorganized management or left.
Self planning teams & managers facilitate.
People have to change.

BerenbachBroy09

Brian Berenbach & Manfred Broy
Professional and Ethical Dilemmas in Software Engineering
IEEE Computer Magazine V42n1(Jan 2008)pp74-80
=ESSAY ETHICS NAMEs DILEMMAS MITIGATION IEEE ACM
Named dilemmas
1. Mission impossible
2. Mea Culpa
3. Rush Job
4. Not My Problem
5. Red lies
6. Fictionware versus vaporware
7. non-diligence
8. Cancelled vacation
9. Sweep it under the rug
Proposes mitigation strategies.
Failures of the ACM and IEEE Codes of Professional Behavior.
Notes likely criminal behaviors: Negligent homicide, reckless endangerment, depraved indifference.
Ethical dilemmas tend to be yoked, chained, or coupled.... and this magnifies the damage.

Berghel01

Hal Berghel
The Code Red Worm
Commun ACM V44n12(Dec 2001)pp15-19
=ARTICLE RISK TECHNICAL CODE buffer overflow Microsoft IIS web-server DLL

Berghel05

Hal Berghel
The Two Sides of ROI: Return on investment vs Risk of incarceration
Commun ACM V48n4(Apr 2005)pp15-20
=ESSAY RISK PRIVACY SECURITY ETHICS PROFESSION LEGISLATION HIPPAA GLB SOX New 2000 legislation puts CIOs and CEOs at risk of prosecution for not making
systems secure. GLB::="Gramm-Leach-Bliley Act of 1999", privacy and security of nonpublic pers onal info .
SOX::="Sarbanes-Oxley Act of 2002", accountability
Also good description of [HIPAA]

Berghel06

Hal Berghel
Fungible Credentials and Next-Generation Fraud
Commun ACM V49n12(Dec 2006)pp15-19
=EXAMPLES FRAUD CREDENTIALS
Fungible: interchangeable and universal.
Better computers and printers allow the creation of a hard to doubt credential that can be used to get legitimate (but false) credentials.
Figure 2 lists some anti-counterfeiting technology.

Bergin01

Joseph Bergin <jbergin@pace.edu>
A Pattern Language for Initial course design
ACM SIGCSE Bulletin V33n1(Mar 2001) & 32nd SIGCSE Tech Symp on Cop Sci Education (Feb 21-25 2001)pp282-286
=PATTERNS EDUCATION PLAN
Abandon Systems all ye that enter here.
Need to Know
Early Bird: identify important topics early.
Spiral
Lazy Professor

Bergland81

Glenn D Bergland
A Guided Tour of Program Design Methodologies
IEEE Computer v14(Oct 1981)pp13-37 (reprint in Chow(Ed)84)
=survey Compares FD JSP DFD and Dijkstra Gries
Page 241 of Chou
Figs 43 and 44: Where is the Magic in the methods?

BerglandGordon81

Glenn D Bergland & ?? Gordon(Eds)
Software Design Strategies(2nd Edition)
IEEE Computer Soc Tutorial IEEE Cat No. EH0184-2 Los Angeles CA 1981
=survey methods DDD SAD

BerglandZave86

Glen D Bergland & Pamela Zave
Special Issue on Software Design Methods
IEEE Trans on Software Engineering SE-12n 2 (Feb 1986)
=survey object-oriented DAD JSD functional formal ADTs DFD

Berghel06

Hal Berghel
Fungible Credentials and Next-Generation Fraud
Commun ACM V49n12(Dec 2006)pp15-19
=EXAMPLES FRAUD CREDENTIALS
Fungible: interchangeable and universal.
Better computers and printers allow the creation of a hard to doubt credential that can be used to get legitimate (but false) credentials.
Figure 2 lists some anti-counterfeiting technology.

Berghel07

Hal Berghel
Better-Than-Nothing Security Practices
Commun ACM V50n8(Aug 2007)pp15-18
=ADVERT BTNSP SECURITY XP Browsers WiFi
BTNSP::= See http://www.berghel.net/btnsp/ Simple things that users can do to improve the security of their systems... Better than doing nothing.

BergmanMoorNelson90

Merrie Bergman & James Moor & Jack Nelson
The Logic Book (2nd edn)
McGrawHill (1990) ISBN 0-07-909524-0 LC# BC135.B435
=TEXT FORMAL LOGIC NATURAL DEDUCTION TREES SEMANTIC TABLEAUX

BergstraPonseSmolka01e

J A Bergstra& A Ponse & S A Smolka
Handbook of process algebra
Elsevier 2001 ISBN 0-444-82830-3, review Tucker Computer Journal V45n1(2002)pp68-69
=UNREAD =Handbook algebra nonsequential CCS TCSP ACP Petri

BergstraTucker07

J Bergstra & J Tucker
The rational numbers as an abstract data type
JACM V54n2(Apr 2007)#7pp? CR 0808-0783
=UNREAD =THEORY ADT ABSTRACT DATA CONDITIONAL EQUATIONAL SPECIFICATION Lagrange
Notes [click here if you can fill this hole]

BerlingRuneson03

Tomas Berling & Per Runeson Efficient Evaluation of Multifactor dependent System Performance using fractional Factorial Design
IEEE Trans Software Engineering V29n9(Sep 2003)pp769-781
=STATISTICS PERFORMANCE PROTOTYPE TESTING ACCURACY ANOVA Pareto Iterative Careful choice of a few test cases applied to a prototype allows the evaluation of the effects of many factors on the targeting performance of a radar system.

BernardLaffite99

Pascal Bernard & Guy Laffite
The French Population Census for 1990
In [HincheyBowen99] pp15-42
=EXPERIENCE MATH Z B METHOD REQUIREMENTS GEOGRAPHY CENSUS
It worked as a process and a product.

Berns84

Gerald M Berns
Assessing Software Maintainability
Commun ACM V27n1(Jan 1984) pp14-23
=EXPERIENCE QUALITY TECHNICAL FORTRAN EVOLUTION TOOL MAT

Bernstein80

Arthur Bernstein
Output Guards and Nondeterminism in "Communicating Sequential Processes"
ACM TOPLAS V2n2(Apr 1980)pp234-238
=THEORY CSP non-sequential NON-DETERMINISM

Bernstein93

Lawrence Bernstein(attmail!l.bernstein)
Get The Design Right!
IEEE Software Magazine V10n5(Sep 1993)pp61-63
1. p 61: "...focus first on the problem domain and then on the implementation domain"
2. controlled, evolving and validated requirements
3. prototypes
4. p62:
5. nimble
6. pay attention to detail
7. visit the user
8. Setup operational profiles of expected use for performance analysis and scenario testing
9. p63: Write the specification after the prototyping and use a formal spiral-development program
10. "no tool will replace the skill and talent of the professional software designer."

Bernstein10

Michael Bernstein
Clay Shirky: doing work or Doing Work
Commun ACM V53n8(Aug 2010)p9 [ 1787234.1787238 ] & blog@Acm [ fulltext ]
=BLOG USEFUL USABLE USER
In February Clay Shirky [ shirky in keynotes ] distinguished things we are paid to do (Work) from what we like doing (work).
We must design software to be useful (helping us do what we want) rather than just usable (we have to be paid to use it).

BernsteinFitzGeraldMacdonellConcepcion05

Marc Bernstein & Kelly M FitzGerald & James P Macdonell & Arturo I Concepcion
AlgorithmA Project: The ten-week Mock Software Company
ACM SIGCSE Tech Symp Proc (Feb 2005)pp142-146
=EXPERIENCE 14.years EDUCATION PROJECT MAINTENANCE PEOPLE MANAGEMENT CSUSB CSCI488 RMT UML IEEE SRS

Berry11

Daniel M Berry
Liability Issues in Software Engineering
Commun ACM V54n4(Apr 2011)p98 [ 1924421.1924443 ]
= INTRODUCTION MASS MARKET BESPOKE SOFTWARE CONTRACTS EULA
Introduces [MetayerEtAl11] and also distinguishes bespoke from mass-marketted software contracts.

BerryKamsties05

Daniel M Berry & Erik Kamsties
The syntactically dangerous ALL and Plural in Specifications
IEEE Software Magazine V22n1(Jan /Feb 2005)pp55-57
=IDEA AMBIGUITY LOGIC LANGUAGE SPECIFICATION CS565
Words to suspect: "only", "all", "also", "each".
Use "each" when describing a property of the individual members of a set.
Use "all" for shared properties across a set.
Can use simple logic to clarify an ambiguity.
All the lights in the room have a single on-off switch.
Net
1. Each light has its own switch.
2. For all y:lights_in_room, one x: switch (x is on_off_switch_for y).
3. All the lights share a common switch.
4. For one x: switch, all y:lights_in_room (x is on_off_switch_for y).
(End of Net)
Similarly for plurals: "Students enroll in six courses" vs "Students enroll in hundreds of courses".

BersoffDavis91

Edward H. Bersoff & Alan M. Davis
Impacts of Life Cycle Models on Software Configuration Management
Commun ACM V34n8(Aug 1991)pp104-117

Bertolazzietal95

Paola Bertolazzi & Giuseppe Di Battista & Giuseppe Liotta
Parametric Graph drawing
IEEE Trans on Software Eng VSE-21n8(Aug 1995)pp662-673
The Graph Server: digraphs not diagrams - no words or icons.

BertolinoMirandola04

Antonia Bertolino & Raffaela Mirandola
Software Performance Engineering of Component-based Systems
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp238-242
=IDEA QUALITY Performance MODULAR COMPONENT CB-SPE
Based on PTS RT-UML [OMG020302].

BertranAugeraud99

Frederic Bertran & Michel Augeraud
BDL: A Speicalized Language for Per-Object Reactive Control
[WileRaming99] pp347-362
=ADVERT LANGUAGE SYNTAX SEMANTOC OBJECT-ORIENTED NONSEQUENTIAL ESTEREL

BerzalCuberoMarinVila05

Fernando Berzal & Jean-Carlos Cubero & Nicolas Marin & Maria-Amparo Vila
Lazy Types: Automating Dynamic Strategy Selection
IEEE Software Magazine V22n5(Sep/Oct 2005)pp98-106
=DEMO TECHNICAL POLYMORPHIC TYPES C# .NET
Lazy types have a common interface plus varying attributes and strategies for handling the interface depending on what attributes are available.
Objects gain and loose attributes as the program executes, the methods adapt auto-magically to what attributes are present.
lazy_types_library::= See http://elvex.ugr.es/software/lazy/, -- proof of concept for .NET
Uses hidden factory pattern and strategy pattern.

BerzinsLuqi90

Valdis Berzins & Luqi[Sic]
An Introduction to the Specification Language Spec
IEEE Software V7n2 pp74-84 (Mar 1990)
formal

BerzinsLuqi91

Valdis Berzins & Luqi[Sic]
Software Engineering with Abstractions
Addison Wesley
Reading Mass.1991
CR9211-0842
(Spec & Ada)

BerzinsLuqiYehudai93

Valdis Berzins & Luqi[Sic] & Amiram Yehudai
Using Transformations in Specification-Based Prototyping
IEEE Trans on Software Eng VSE-19n5(May 1993)pp436-452 QUALITY PURPOSE function
1. Transformations of specifications during a project.
2. Spec+DFDs
3. pp442-443 Software Process
4. p446 encapsulated user interface in module
5. pp446-447 requirements evolve
6. distinguish spec changes from design and implementation changes
7. p447inheriting from older specifications
8. p450 Distinguishing (and delaying) optimization decisions from functional requirements.
  pp458-459 distinguishing extention, contraction, refining, abstracting, relaxing, constraining by comparing Vocabulary, Granularity and Behavior.
  pp447-448: The derivation Lattice/poset to explain designs -- configuration management for specs?
  [Snelting96] [KramerLuqiBerzins93]

Berztiss88

Alfs Berztiss
Programming with Generators
Software - Practice and Experience V18n1pp73-81(Jan88)
=IDEA non-sequential Technical
Each time a generator is called it produces the next result.

Berztiss89

Alfs Berztiss
Formal Specification Methods and Visualisations
In [Chang89] pp231-290
=SURVEY graphic DFDS ERDs(problems) JSD STD Petrie Nets Structure Diagrams

Berztiss90

Alfs Berztiss
Programming with Generators: An Introduction
Ellis Horwood Chichester UK 1990 ISBN 0-13-739087 CR 9211-0847
=MONOGRAPH Technical pseudo-concurrency

BesseyEtAl10

Al Bessey & Ken Block & Ben Chelf & Andy Chou & Bryan Fulton & Seth Hallem & Charles Henri-Gros & Asya Kamsky & Scott McPeak & Dawson Engler
A few billion lines of code later -- using static analysis to find bugs in the real world.
Commun ACM V53n2(Feb 2010)pp [ 1646353.1646364 ]
=EXPERIENCE COVERITY 700 CUSTOMERS ERRORS CODE BUG FINDING RESEARCH vs PRACTICE TECHNIQUE vs PEOPLE
Practical experience uncovered new problems not seen in experiments. "Weird is not good. Tools want expected".
Bugs found vs false positives.
In practice most users are not the developers.
Selling the tool by an onsite trial with engineer and salesperson.
rules
1. You can't check code you don't see.
2. Not everybody uses make or even command lines. Must adjust checkers to work in complex GUI build ecology. Typical overnight builds. You can not change a build process even if it is clearly broken.
3. You can't check code you can't parse. Compilers diverge from the standard and are old. Amazing code works. Must translate these away for each compiler. 100s of translations.
4. Programmers react to bug reports with disbelief, anger, denial, and bargaining. Always some Clueless people. Good people still do stunningly clueless things. Always present results to a group. Someone may be stupid or unmotivated but another can be smart and motivated.
5. Commonly code is shipped with bugs in it. Lots of bugs. So maintain a list of bugs that are known already.
6. Upgrades that find more bugs make managers and the checker look bad. Bugs in the tool that lead to missed bugs make tool look bad when upgrade fixes them.
7. Missing bugs is easier to sell than reporting nonbugs.
8. Churn is bad. Churn is unexpected changes in user output on an upgrade. (dick: Festina lenti).
9. Deeper, smarter analysis is not always good. Need explainable bug reports.
10. Vital to reduce false positives. Especially in the early runs.
11. Else: "this tool sucks".
Programmers are starting to accept static checking tools.
If the code is big enough and it compiles then you can find bugs in it.

Betz95

Mark Betz
Building a CORBA Object Server
Software Development Magazine(Oct 1995)pp53-61
=ARTICLE TECHNICAL OBJECT-ORIENTED C/C++
IDL::=Interface Definition Language
ORB::=Object Request Broker

BeugnardEtal99

Antoine Beugnard & Jean-Marc Jezequel & Noel Plouzeu & Damien Watkins
Making components contract aware
IEEE Computer Magazine V32n7(Jul 1999)pp38-45
=THEORY COMPONENTS RELIABILITY QUALITY
1:IDL=syntax, 2: pre/post=behavioral, 3:synchronization, 4:quality-of-service

BeyerHoltzblatt94

Hugh R Beyer & Karen Holtzblatz
Calling Down the Lightening
IEEE Software Magazine V11n5(Sep 1994)pp106-107+113
=History Bricklin spreadsheet requirements design users
roadblocks to creativity::= separating requirements gathering from system design | products = list of features | FEAR(engineers talking to customers | people working together| new ideas |"it can't work")

BeyerHoltzblatt95

Hugh R Beyer & Karen Holtzblatz
Apprenticing with the Customer
Commun ACM V38n5(May 1995)pp45-52
=EXPERIENCE REQUIREMENTS
1. "sit by Nelly" and then ask questions
2. reveals: what matters, details, structure
3. events lead to discussions
4. master can transfer years of experience quicker
5. Then designer works out structure
  1. articulate understanding
  2. is there to improve work
  3. must have a specific focus
6. Beware
  1. other relationships: interviewer, expert, friend
  2. being abstract: things that are unsaid...ASK!
  3. polite ways of saying "no, you are wrong": "Huh?", "Ummm...maybe", "Yes, but..."

BeyerNoackLewerentz05

Dirk Beyer & Andreas Noack & Claus Lewerentz
Efficient Relational Calculation for Software Analysis
IEEE Trans Software Engineering V31n2(Feb 2005)pp137-149
=TOOL RELATIONAL LOGIC RML BDD TECHNICAL PATTERN JAVA CrocoPat
Faster recognition of patterns in class structures tested faster on real code: JDK AWT, Eclipse,... Than Prolog and MySQL.

Bhansali93

P V Bhansali
Survey of software safety standards shows diversity
IEEE Computer Magazine V26n1(Jan 1993)pp88-89
=SURVEY STANDARDS RISKS
1. UK MoD: Int Def Stan 00-55 (Formal)
2. UK MoD: Int Def Stan 00-56 (Hazard Analysis)
3. Instrument Soc America SP84(draft)
4. US DoD: Mil-Std-882B(Notice 1)
5. IEEE CS: P1228(Draft) (Safety plan)
6. Radio Tech Comm Aero/DO-178A
7. Int Elect Comm(industrial: SC 65A/WG9... EIA: SEB 6-A UL: UL1998(Draft)
8. FDA: Control of medical devices
  General
9. Identify and classify systems hazards
10. Identify system function allocated to software
11. Identify hazards related to software
12. Design to reduce or eliminate hazards
13. (sw and credible hw)
14. Implement SW
15. Verify hazards at acc level and no new hazards
16. Config management and SQA throughout

BhatGuptaMurthy06

Jyoti M Bhat & Mayank Gupta & Santhosh N Murthy
Overcoming Requirements Challenges: Lessons from Offshore Outsourcing
IEEE Software Magazine V23n5(Sep/Oct 2006)pp38-44
=CASE STUDIES 9 + THEORY RE Requirements SHARING TRUST
Problems in case studies can be avoided by success factors and best practices.
Success factors: shared goals, culture, process, and responsibility. Plus trust.
Lists best practices for people, process, and technology.
No technology to promote trust!

BhattiBerinoGafoorJoshi04

Rafae Bhatti & Ellsa Berino & Arif Gafoor & James B D Joshi
XML-based specification for web services
IEEE Computer Magazine V37n4(Apr 2004)pp41-49
=IDEA WWW SECURITY XML RBAC XUS XRS
RBAC::= "role based access control".
XUS::= "XML user sheet", credentials.
XRS::= XML role sheet.
etc.

BianchiEtal03

Alessandro Bianchi & Danilo Caivino & Vittorio Marengo & Giuseppe Visaggio
Iterative re-engineering of Legacy Systems
IEEE Trans Software Engineering V29n3(Mar 2003)pp225-241
=EXPERIENCE MAINTENANCE COBOL REENGINEER REFACTOR DATA
Compare mean time to maintenance request to estimated time to reengineer module.
Fig 4 has incorrect UML

BiancuzziWarden09

Federico Biancuzzi & Shane Warden
Masterminds of Programming: Conversations with the Creators of Major Programming Languages
O'Reilly Media 2009 ISBN 0596515170
=UNREAD =INTERVIEWS PROGRAMMERS PEOPLE CODING TECHNICAL LANGUAGES CSCI320
Please send me your comments [ contribute.html ] to see them here.

BicarreguiRitchie95

Juan Bicarregui & Brian Ritchie
Invariants, frames and Postconditions: A comparison of the VDM & B Notations
IEEE Trans on Software Eng VSE-21n2(Feb 1995)pp79-89
=CASE-STUDY FORMAL LANGUAGES SPECIFICATION

BichlerLin06

Martin Bichler & Kwei-Jay Lin
Service Oriented Computing
IEEE Computer Magazine V39n3(Mar 2006)pp99-101
=ADVERT SERVICES NET/WEB WORKFLOW SEMANTICS QoS WSDL OWL-S ONTOLOGY SOC BSN BPEL BPML

Bidoitetal91

Michel Bidoit & Hans-Jorg Kreowski & Piere Lescanne & Fernando Orejas & Donals Sannella
Algebraic System Specification and Development
Springer Verlag NY NY 1991(Lecture Notes in CS V501)
=SURVEY =BIBLIOGRAPHY THEORY FORMAL ALGEBRA SPECIFICATION
Short!

BiemanKang95

James M Bieman(bieman@cs.colostate.edu) & Byung-Kyoo Kang
Cohesion and Reuse in an Object Oriented System [SamadzadehZand95] pp259-262
=EXPERIENCE OBJECT-ORIENTED REUSE C/C++ EXPERIENCE
New measure of cohesion for a class - degree to which methods use the same fields. Most classes a quite cohesive. Classes reused by inheritance most are clearly of lower cohesion.

BiemanKang98

James M Bieman & Byung-Kyoo Kang
Measuring Design-Level Cohesion
IEEE Trans Soft Eng V24n2(Feb 1998)pp111-124
=IDEA =EXPERIMENT DESIGN MODULE METRICS
DLC::="Design-Level Cohesion".
DFC::="Design-level Functional Cohesion".
IODG::="Input/output dependence graph".

BiemanOtt94

James M Bieman & Linda M Ott
Measuring Functional Cohesion
IEEE trans on Soft Eng vSE-20n8(Aug 1994)pp644-657
=THEORY METRICS MODULARIZATION COHESION

BiemanZhao95

James M Bieman(bieman@cs.colostate.edu) & Josephine Xia Zhao
Reuse Through Inheritance: A Quantitive study of C++ Software [SamadzadehZand95] pp47-52
Inheritance is used far less frequently than expected

BiemanJainYang01

James M Bieman & Dolly Jain & Helen J Yang
OO design patterns, design structures, and program changes: an industrial case study
17th IEEE International Conf on Sw Maintenance ICSM'01 ( 2001)pp580+ CR 0511+1249 [ ICSM.2001.972775 ]
=experience evolution object-oriented GoF patterns metrics
39 versions of evolving industrial OO software
Strong relationship -- larger classes were changed more frequently
Classes that participate in design patterns were the most change prone.
Classes that are reused the most through inheritance tend to be changed more often.

Biffl00

Stefan Biffl
Using Inspection Data for Defect Estimation
IEEE Software Magazine V17n6(Nov/Dec 2000)pp36-43
=EXPERIMENT DEFECTS INSPECTION ESTIMATION 200+students
Capture-Recapture model of number of defects vs number found by different numbers of inspectors.
Best to assume that different defects have different chances of being detected, but that inspectors are all equally likely.

Billingsetal94

C Billings & J Clifton & B Kolkhorst & E Lee & W B Wingert
Journey to a mature software process
IBM Systems Jnl V33n1(1994)pp46-61
=EXPERIENCE HISTORY IMPROVEMENT REQUIREMENTS QUALITY V&V PROCESS EVOLUTION
Shuttle Onboard Software System. See
[Oman94] [MaddenRhone84] [ Billingsetal94.html ]

BimboCampanaiNesi93

Alberto Del Bimbo & Maurizio Campanai & Paolo Nesi
A Three-Dimensional Iconic Environment for Image Database Querying
IEEE Trans on Software Eng VSE-19n10(Oct 1993)pp977-1011 Graphics
1. strictly_after, after_with_right_adjacency, after
2. is_included_by with left_adjacency, includes with right_adjacency
3. includes, spatial-coincidence, isinclude_by, includes with left adjacent
4. before, before with left adjacency, strictly_before

Binder94

Robert V Binder(guest Editor)
Object-Oriented Software Testing(Special edition)
Commun ACM V37n9(Sep 1994)pp28-101
=EDITORIAL OBJECTS SQA TESTING

Binder95

Robert V Binder(guest Editor)
Scenario-Basesd Testing for Client Server Systems
Software Development Magazine(Aug 1995)pp43-49
SQA SCENARIO
cf Operational Profiles in Musa93(CLEANROOM)

BinkleyEtal06

David Binkley & Mariano Ceccato & Mark Harman & Filippo Ricca & Paolo Tonella
Tools-Supported refactoring of existing Object-Oriented code into aspects
IEEE Trans Software Engineering V32n9(Sep 2006)pp698-717
=DEMO TOOL MAINTENANCE REFACTOR ASPECTS
Has a useful list of refactorings which may or may not be complete.
The extract repeated code into an aspect: DRY.

Binstock11

Andrew Binstock (Dr. Dobb's Editor in Chief)
Lax Language Tutorials
Dr. Dobbs Update (31 May 2011) [ MailView?ms=MzY2Njg4NzYS1&r=MjIxNTUzNzc4NAS2&j=MTAyODAzNzM3S0&mt=1&rt=0 ]
=EDITORIAL LRM vs LANGUAGE TUTORIALS Python C Ruby K&R Scala Java
Compares good and bad language tutorials... and proposes that
1. A good tutorial starts with a collection of complete simple but usable examples
2. It finishes with a detailed reference manual with all the nitty gritty details

Binstock11b

The Dismal Science of Code Metrics
Andrew Binstock (Dr. Dobb's Editor in Chief)
Dr. Dobbs Update (Sep 27 2011) [ 231602262?cid=DDJ_nl_upd_2011-09-27_h ]
Quote
Couldn't put it better myself.

Bird09

Cameron Bird
Wired (Dec 2009) [ st_goodsigns ]
=ADVERT NOTATION MATHEMATICS RELATIONS
Dr. Byron Cook (QMC & MS Cambridge) [ http://research.microsoft.com/en-us/people/bycook/ ] new notation for relational calculus

BirdEtAl09

Christian Bird & Nachiappan Nagappan & Premkumar Devanbu & Harald Gall & Brendan Murphy
Does Distributed Development Affect Software quality? An Empirical Case study of windows Vista
Commun ACM V52n8(Aug 2009)pp- [ 1536616.1536639 ]
=EMPIRICAL DISTRIBUTED PROCESS QUALITY MS Vista
Little evidence that having a team spread over two continents gives worse code than being in the same building.
Size of team does have an effect.
(dick)|-They did not check to see if the distributed team compensated for distance be special processes or tools.

BisbalEtal99

Jesus Bisbal & Deirdre Lawless & Bing Wu & Jane Grimson
Legacy Information Systems: Issuses and Directions
IEEE Software Magazine V16n5(Sep/Oct 1999)pp103-111
=DESCRIPTION EVOLUTION DATA LIS Chicken-Little and Chrysalys Strategies

Bishop90

Judy M Bishop
The Effect of Data Abstraction on Loop Programming Techniques
IEEE Trans SE-16n4pp389-402(Apr 1990)
ADTs non-sequential Technical

BishopP02

Pete G Bishop
Rescaling Reliability Bounds for a New Operational Profile
Proc ISSTA02 & ACM SIGSOFT Software Engineering Notes V27n4(Jul 2002)pp180-190
=THEORY PROBABILITY FAILURE TESTING
If faults are removed as they are found by a fixed operational profile without effecting other faults and probability of a faults is constant with time T then P(failure per test | test number=T) <=N/(e * T) if there are N faults.
Reason: errors that are probable are found quickly, less probable once are less likely to happen.
This formula can be adjusted to allow for changes in the operational profile.
Results fit PODS TRIPV testing.

BishopLittlewoodPovyakaloWright11

Peter Bishop & Bev Littlewood & Andray Povyakalo & David Wright
Toward a formalism for conservative claims about the dependability of software-based systems
IEEE Trans Software Engineering V37n5(Sep/Oct 2011)pp706-717
=THEORY MATHEMATICS CONFIDENCE BAYES PROBABILITY
How confident are you that 99.99% of the time the system will work correctly?
How would your confidence change if the system passes a test?

BishopWagner07

Matt Bishop & David Wagner
Risks of E-Voting
Commun ACM V50n11(Nov 2007)p120
=REPORT TECHNICAL SOURCE CODE REVIEW VIRAL RISKS SECURITY QUALITIES
The authors found buffer overruns, hard-coded encryption keys, dumb pseudo-encryption, dumb passwords etc. in all voting systems.
Federal tests did not disclose the flaws. Code review did.
Voting systems must be transparent.
Need for audits.

BitnerReingold75

James R Bitner & Edward M Reingold
Backtrack Programming Techniques
Commun ACM V18n11 pp651-656(Nov 1975)
=survey non-sequential optimization Technical

Bittner02

Kurt Bittner
Use Case Modeling
Addison-Wesley Longman Boston MA ISBN 0201709139 [CR] 0305-0414
=HANDBOOK USECASE USER REQUIREMENTS

BittnerSpence03

Kurt Bittner& Ian Spence
Use case modeling
Pearson Education Boston MA 2003
=HOWTO REQUIREMENTS USECASE
Synthesize understandable models of complex requirement details.
Communication, simplicity, stakeolders, write details, Good enough.
Dangers of relationships between use cases.
How to write abstract cases(with a "{hole}") and their specializations(with an "at{hole}").

BiZhao04

Henry H Bi & J Zhao
Applying propositional logic to workflow verification
Information Technology and ManagementV5n3-4(Jul wppr)pp293-318 CR 0605-0526
=UNREAD =THEORY WORKFLOW VERIFICATION LOGIC [click here if you can fill this hole]

Bjorkander00

Morgan Bjo"rkander
Graphical Programming Using UML and SDL
IEEE Computer Magazine V33n12(Dec 2000)pp30-35
=IDEA UML SDL DYNAMIC FSM/STD MODEL TECHNICAL GRAPHIC
p34:"Code is generally considered king, and the model as its poor country cousin."

BjorkanderKobryn03

Morgan Bjorkander & Cris Kobryn
Architecting Systems with UML 2,0
IEEE Software Magazine V20n4(Jul/Aug 2003)pp57-61
=ADVERT PORT INTERFACE ACTIONS EXECUTABLE MODELING UML2.0
Classes can have ports(square boxes on border). Ports have interfaces.
Ports can be behavioral.
Interfaces(lollipops) are either required (half circle) or provided interfaces(half circle).
Ports can be connected: required to provided interfaces.
Statemachines, interactions, and activities all can actions.
Actions can be given precise -- executable -- semantics.

Bjorner06

Dines Bjorner
Software Engineering 1, 2 and 3
Springer-Verlag NY Secaucus NJ ISBN 3540211497 CR 0802-0113
=UNREAD =ADVERT =EXAMPLES FORMAL DOMAIN MODEL REALITY RSL ABSTRACTION

BjornerGeorgePrehn99

Dines Bjorner & Chris George & Soren Prehn
Scheduling and Rescheduling Trains
In [HincheyBowen99] pp157-184 [ http://www.iist.unu.edu ]
=EXPERIENCE DEMO FORMAL SPECIFICATION PROTOTYPING PRaCoSy lightweight RAISE RSL C train dispatching

BjornerJones82

?? Bjorner & ?? Jones
Formal Specification & Software Development
Prentice Hall NJ 1982
=ADVERT VDM formal language Technical

Black95

George Black
British Government Puts New GUIs to the Test
Software Magazine (May 1995)pp82-84
=EXPERIENCE SSADM GRAPHIC USER GUI
UK Customs & Excise Dept.
SSADM (pre Vn4) not good for GUIs... using IEEE standards instead

Blaha04

Michael Blaha
A Copper Bullet for software Quality Improvement
IEEE Computer Magazine V37n2(Feb 2004)pp21-25
=EXPERIENCE 11 years DATA MODEL REVERSE ENGINEERING QUALITY SOFTWARE PRODUCTS
(1) how to grade a data base: ABCDF
(2) expects grade of data base to be related to overall quality of software.
(3) companies that do not allow there data base design to be reviewed automatically scores badly.
Give a good list of common data defects.
Figure 2 has a small UML error: switched multiplicities.

BlackEtAl09

Sue Black & Paul P Boca & Jonathan P Bowen & Jason Gorman & Mike Hinchey
Formal versus agile: Survival of the Fittest
IEEE Computer Magazine V42n9(Sep 2009)pp37-45 + Correspondence V42n11(Nov 2009)p6 by William Adams
=SURVEY RESEARCH AGILE FORMAL MODEL CHECKING Alloy X-Machines SMV CTL KeY
SEEFM2003::acronym="First South East Europe Workshop on formal methods", [ SEEFM03 ]
XFM::="eXtreme Formal Modeling", [ 1109118.1109120 ]
XFun::= See http://delab.csd.auth.gr/~bci1/SEEFM03/seefm03_03.pdf (PDF), Unified Process with X-Machines verified by model checking.
KeY::method= See http://i12www.iti.uni-karlsruhe.de/~key/keysymposium07/slides/haehnle-agile.pdf
Extend TDD by including static-analysis and theorem-proving tools to extend coverage. Example 97% of assertions checked automatically in SPARKAda toolset.
How do formal requirements handle creep?
Machine checked refactoring?
Parallelism: FDR and Coverity [ http://www.coverity.com/ ]
Speed and availability of tools: Rodin [ http://rodin.cs.ncl.ac.uk/ ]
and Deploy [ http://www.deploy-project.eu/ ] projects. Praxis [ http://www.praxis-his.com/ ] has SPARK toolset as open source.
Formal methods lite -- use math at the right times in a project.
Argues that the total cost (effort) for a project is less with up front work getting requirements etc. right.
Agility is not about speed but maneuverability. Producing the highest quality in each iteration/increment. Compared to RAD.
Controlling the technical debt.
No real conflict... given some mutual understanding.

BlahaPremerlaniShen94

Michael R. Blaha & William J Premerlani & Hwa Shen
Converting OO Models into RDBMS Schema
IEEE Software magazine v11n3(May 1994)pp28-39
=ADVERT OBJECT_ORIENTED OMT DATA
OMT is Figure A on pages 34-35 [Premerlanietal90] [PremerlaniBlaha94]

BlahaPremerlani98

Michael R. Blaha &William J Premerlani
Object-Orietented Modeling and Design for Database Applications
Prentice-Hall NJ 1997
=MANUAL OBJECT-ORIENTED OOA/OOD DATA UML BNF for Object Navigation Notation [BlahaPremerlaniShen94]

BlahaSmith02

Michael Blaha & Cheryl Smith
A Pattern for Softcoded Values
IEEE Computer Magazine V35n5(May 2002)pp28-34
=DEMO dynamic data types metamodel reflection
Moves in the opposite orientation to objects!
How to code an generalization hierarchy of attributes and values in data. : DescribedObjects and DescribedObjecTypes.
Data use to Model attributes, values, units, constraints, generalization, etc
Values include sources and dates: entry, effective, expiration.
Does not handle behavioral inheritance.
Each Value has a field for numeric datum AND string datum AND datetime datum. Constrained by ode so that only one is non-null!
All generalizations has a discriminator attribute.

BlairBencomoFrance09

Gordon Blair & Nelly Bencomo & Robert B France
Models@run.time
IEEE Computer Magazine V42n10(Oct 2009)pp22-27
=EDITORIAL IDEA EXECUTABLE REFLECTIVE MODEL
Introduces papers pp28-68 about the advantages of a running system including a model (abstraction) that the system can access and update.

Blank89

GD Blank
A Finite & Real-Time Processor for Natural Language
Commun ACM v32 n10(Oct 1989)
=DEMO DDD

Blaschek94

Gunther Blaschek
Object-oriented programming with prototypes
Springer-Verlag NY NY 1994 ISBN 0-387-56469-1 CR9502-0058
=DEMO Objects without classes! Omega for the Macintosh

BleisteinEtal87

Sandra Bleistein & Robert Goetge & Frank Petroski & Robert Wiseman
Capacity Management of Air Traffic Control Computer Systems.
IEEE Computer Magazine V20n2 (Feb 1987)pp73-83
=EXPERIENCE FAA AAS PERFORMANCE

Blikle77

Andrzej Blikle
Co-Routines and Networks of Parallel Processes
Proc IFIP 77 (North Holland Pub Co 1977) pp285-290. Also IRIA Raport de Recherche No 202 Nov 76
=THEORY LOGIC SEMANTICS REGULAR-EXPRESSIONS

Bliss42

Charles K Bliss
Semantography ( Blissymbolics) 2nd Edn
Semantography ( Blissymbolics), Sydney Australia 1942 [ http://www.semantography.com/ ]
=ADVERT GRAPHIC SYMBOLIC LANGUAGE GENERAL SEMANTICS RATIONALITY LOGIC
Explains BlissSymbolics.
Argues that Semantography helps spot crooked thinking and false arguments.
Bliss Symbols include all internationally agreeed symbols: Math, Chem, Music,...
Dictionary of symbols [ http://www.semantography.com/4/ ]

Blood04

Rebecca Blood
How Blogging Software reshapes the online community
Commun ACM V47n12(Dec 2004)pp53-55
=ANECDOTE SOFTWARE BLOG
Software tools change the way things are done and what words mean in powerful ways.

Bloom83

S L Bloom
Algebraic Solution of a System of Recursion Equations in Infinite Trees Other Contraction Theories
Journal of Computer & System Science 1983 pp225-255
=THEORY TOPOLOGY

BloomBEtal00

Bard Bloom & Jim Russell & John Vlissides & Mark Wegman
High-level Program Development
Dr. Dobbs Special Report (Dec 2000)pp17-2
=ADVERT TOOLs IBM DOMAIN MODEL WORKFLOW vs PERFORMANCE
Enterprise Builder, Hyper/J, Dynamic Application Partitioning (DAP)

BloomChengDsouza97

Bard Bloom & Allan Cheng & Ashvin Dsouza
Using a Protean Language to Enhance expresiveness in Specifications
IEEE Trans Softw Eng VSE23n4(Apr 1997)pp224-234
Using structural Operational semantics to construct and extend specification languages including CCS Z Petri nets. GSOS Simple BDD-based model checking. philosphers & lifts

BloomEsik93

Stephen L Bloom & Zoltan Esik
Iteration Theories: Equational Logic of Iterative Processes
EATCS monographs on Theoretical Computer Science Springer Verlag NY NY 1993 ISBN 0-387-56378-4 CR9505-0287 630 pages $109.00 Hardcover
=MATHEMATICAL LOGIC ALGEBRA SEMANTICS

BloomfieldFroome86

R E Bloomfield & P K D Froome
The Application of Formal Methods to the Assessment of High Integrity Software
IEEE Trans SE-12n9 (Sep 1986)pp988-993
=CASE-STUDY Prolog VDL QUALITY

Blum87

Bruce I Blum
A Paradigm for Developing Information Systems
IEEE Trans Soft Eng VSE-13n4(Apr 1987)pp432-439
=ADVERT DATA METHOD TEDIUM
TEDIUM: all info about application is in data base(ADB) and product is generated automatically from database(FAP)
Experiences: Used John Hopkins since 1980
Demo on COCOMO example shows strong productivity increase(time ten times less!)

Blum92

Bruce I Blum
Software Engineering: A Holistic View
Oxford University Press London UK 1992 ISBN 0-19-507159-X $50 pp588
Very positive reveiw by Dave Hurley(U Pittsburg) p113 IEEE Software Magazine July 1993 (RS100). Moderate review by Vaclav Rajlich(Wayne State U) p102 IEEE Computer Aug 1994

Blum94

Bruce I Blum
A Taxonomy of Software Development Methods
Commun ACM V37n11(Nov 1994)pp82-94 CR9602-0143
history(pp84-90) methods

Blum95

Bruce I Blum
Beyond Programming to a New Era of Design
Oxford University Press 1995
ISBN 0-19-509160 $40 CR9610-0771 reccommended in IEEE Software Mag July/Aug 1995
=IDEA POSTMODERN

Blythetal90

David Blyth & Cornella Boldyreff & Clive Ruggles & Nik Tetteh-Lartey
The Case for Formal Methods in Standards
IEEE Software V7n5(sep 1990)

Boasson93

Maarten Boasson<boasson@hgl.signaal.nl>(Thomson)
Exploding Complexity may be our own Fault(Insider Column)
IEEE Software(Mar 1993)p12.

Bochenski89

B Bochenski
Importance of Optimization
Software Magazine (Nov 1989) p79(Box)
=IDEA data QUALITY

Bochmann88

Gregor von Bochmann
Delay-Independent Design for Distributed Systems
IEEE Trans Soft Eng VSE-14n8(Aug 1988)pp1229-1237
=THEORY non-sequential STD/FSM timing theory
regularity::=removing delays leads to equivalent states

BochmannVerjus87

Gregor von Bochmann & J P Verjus
Some Comments on "Transition-Oriented" Versus "Structured" Specification of Distributed Algorithms and Protocols
IEEE Trans Soft Eng VSE-13n4(Apr 1987)pp501-505
=ESSAY reinvents JSP inversion in context of LOTOS SDL Estelle etc NONSEQUENTIAL

Bock03

Conrad Bock
UML without Pictures
IEEE Software Magazine V20n5(Sep/Oct 2003)pp33-
=DEMO MODEL REPOSITORY UML2.0 SEMANTICS COMPILATION ACTIVITY
Shows how a C++ function is represented by an activity diagram and by collection of objects (mini data base)that model the diagram -- a repository

Bock05

Conrad Bock
UML 2 Activity and Action Models Part 6: Structured Activities
JOT V4n3(May-Jun 2005) [ column4 ]
=HOWTO UML2.0 STRUCTURE ACTIVITY interrupts exceptions REPOSITORY MODEL

BockleClemensMcGregorMuthigSchmid04

G|nter Bvckle & Paul Clemens & John D McGregor & Dirk Muthig & Klaus Schmid
Calculating ROI for Software product lines
IEEE Software Magazine V21n3(May/Jun 2004)pp23-31
=DIALOG MATHEMATICS COSTS REUSE

Boddie87

John Boddie
Crunch Mode
Yourdon Press/Prentice Hall NJ 1987
=HANDBOOK lifecycle SAD PURPOSE QUALITY

BodinGordonLoeb05

Lawrence D Bodin & Lawrence A Gordon & Martin P Loeb
Evaluating information security using the analytic hierarchy process
Commun ACM V48n2(Feb 2005)pp79-83
=ADVERT AHP SECURITY QUALITIES TRADEOFFS COTS DECISIONS
AHP [Saaty80]

BodolfKingBen-Menachem05

David Bodolf & Patrick C K King & Mordechai Ben-Menachem
Web Metadata Standards: Observations and Prescriptions
IEEE Software Magazine V22n1(Jan /Feb 2005)pp78-85
=ESSAY WEB STANDARDS METADATA ONTOLOGIES AI Table 1 page 80: List of standards: ebXML, CPP, WSDL, UDDI, SOAP, WS-Security, P3P, DC, CIMI, OWL. Suggests
1. Don't ignore testing, SQA and other long standing problems.
2. Don't target a standard at too many purposes/uses.
3. To find things may need meta-meta-data. Need tools to support search and navigation through classifications and thesau rus hierarchies.
4. Don't add useless indexing. Don't work at too high a level and allow too much freedom at more concrete lev els. Conventional ontologies should be limited to narrow domains until more reliable methods to develop ontologies are developed.

Boegh08

Jorgen Boegh
A New Standard for Quality Requirements
IEEE Software Magazine V25n2(MAr/Apr 2008)pp60-
=STANDARD QUALITIES MANAGEMENT MODEL MEASUREMENT REQUIREMENTS EVALUATION ISO/IEC 25030 SQuaRE
ISO 9126 Quality model{ {External, Internal}><{Functionality, Reliability, Usability, Maintainability, Portability}, Quality in Use {Effectiveness, Productivity, Safety, satisfaction }}
Distinguish: computer system, mechanical part, Human process.
Computer system: hardware, software, and data -- all with qualities.
Stakeholder needs ->(definition)->Stakeholder requirements ->(Analysis)-> System Requirements.
Many more details...

Boehm80a

Barry Boehm
Software engineering - as it is
See FreemanLewis80 pp 149-179
=survey

Boehm80b

Barry Boehm
Software Engineering Economics
Prentice Hall International 1980
=TEXT QUALITY ENGINEERING costs

Boehm87

Barry Boehm
Industrial Software Metrics Top Ten List
IEEE Software V4n5(Sep 1987)pp84-85
=EXPEREINCE QUALITY

Boehm96

Barry Boehm(USC)
Helping students Learn Requirements Engineering(abstract)
Preliminary program conf on Softw Eng Education April 1996
=EDUCATION REQUIREMENTS
"Many software engineering courses (and methods) begin with an assumption that software requirements are presented to software engineers in a complete
consistent
feasible
testable
and traceable form
and that the software engineer's main job is to correctly transform the requirements into code. This is generally an unhealthy approach
as the requirements for virually alll significant software products are to some degree unknown
unknowable
or the results of compromises requiring the software engineer's participation and expertise."

Boehm99

Barry Boehm(USC)
Making RAD Work for Your Project
IEEE Computer V32n3(Mar 1999)pp113-114+117
=ESSAY Types of RAD: DRAD(Bumb RAD=deathmarch).. SAIV(Schedule as Independent Variable) etc etc. See USC-CSE-99-512 on [ electronicopy.html ] for PDF formatted extended version

Boehm00

Barry Boehm
Unifying Software Engineering and Systems Engineering
IEEE Computer Magazine V33n3(Mar 2000)pp114-116
=IDEA SYSTEMS QUALITY determine ARCHITECTURE + COST REQUIREMENTS should be part of SOFTWARE ENGINEERING

Boehm00

Barry Boehm
Requirements that handle IKIWISI, COTS, and rapid change
IEEE Computer Magazine V33n7(Jul 2000)pp99-102
=ESSAY REQUIREMENTS EVOLUTION INFORMATION HIDING INCREMENTAL
IKIWISI::=I'll know it when I see it.
p99: "requirements tend to emerge with continued use".
COTS, p99: "capailities determine the requirements".
WWW change "an impossible to win game of catch-up".
p100: "avoid one-size-fits-all approaches to requirements".
new kindsof requirements: value-driven, sared-vision, change-driven, and risk driven.
benefits vs schedule, business consequences and assumptions, require some room for likely changes like addin low priority needs, in orout? -- minimize the risk.

Boehm00a

Barry Boehm
Project Termination doesn't Equal Project Failure
IEEE Computer Magazine V33n9(Sep 2000)pp94-96
=ESSAY SURVEY PROCESS RISK
Competitive edge means risk. "You shouldn't expect all your risky projects to succed."
manage your products.
manage risk with incremental commitment.
use architecture reviews, feasibillty rationales.
monitor assumptions.
Standish Group reported in 1995 [ chaos.htm ] that 31.1% of projects get cancelled before completion .
Hayes97, computerworld nov 3 1997, managing user expectations.

Boehm00b

Barry Boehm
Safe and Simple software cost analysis
IEEE Software Magazine V17n5(Sep/Oct 2000)pp14-17
=ADVERT COCOMO II ESTIMATING COST
tables diagrams and examples. Pointers to tools.

Boehm02

Barry Boehm
Get Ready for Agile Methods, with Care
IEEE Computer Magazine V35n1(Jan 2002)pp64-69
=IDEA XP AGILE adaptive risk-driven plandriven CMM
Presents a spectrum of processes from Hacking to Inch-pebble ironbound contract. XP is the limit of th CMM range.
Agile processes must have involved clientele. Plan-driven must have stable requirements.
There exist requirements that break architectures.
Shows graphs of risk exposure vs amount of planning for different losses that have to be traded-off at a sweet spot.
For L:loss, risk_exposure(l)::=P[L] * size(L).

Boehm08

Barry Boehm
Making a Difference in the Software Century
IEEE Computer Magazine V41n3(Mar 2008)pp32-38
=ESSAY IDEAS ACRONYMIC CATCHPHRASES ONESIZE OSUFA BITAR IKIWISI DAVAS SISOS TANIA
Rapid change vs
THWADI::="Thats How We've Always Done It".
Uncertainty and Emergence. Cone of Uncertainty. [Armour08]
BITAR::="Buy Information To Avoid Risk", Do extra things to reduce uncertainty. Tackle risks early.
IKIWISI::="I'll know it when I see it". So Iterate.
Dependability
DAVAS::="Dependability As Value Assured to Stakeholders". Example of conflicting values in a well known failed project.
Diversity.
OSUFA::="One Size Fits All". Culture makes a difference in the adoption of process standards.
SISOS::="Software Intensive Systems of Systems". OSUFA leads to failure
Interdependence.
TANIA::="There Are No Islands Anymore". No part of a system or of a process is isolated.
Figure 5, p36: Activities >< Phases >-> Level_of_activity, CF RUP.
SISOS need more time for Architecture and Risks.

BoehmAdve12

Hans-J. Boehm & Sarita V Adve
You don't know Jack about shared variables or memory models
Commun ACM V55n3(Feb 2012)48-54 [ 20764506.2076465 ]
=DEMO RISKY BUGGY CODE SHARED VARIABLES DATA RACES MPI Pthreads Mutex synchronization
Defines a data race as when two threads can access the same memory locations and one at least is a write and the instructions can execute at the same time.
Demonstrates that data races are evil.

BoehmBasili00

Barry Boehm & Victor R Basili
Gaining intellectual control of Software Development
IEEE Computer Magazine V33n5(May 2000)pp27-33
=ESSAY RESEARCH PLANNING PITAC NSF AESOP COTS PEOPLE SCIENCE ENGINEERING
President's information technology advisory committee
Report on two workshops.
great software depends on more than good engineering or just good technology.
need to study rea,l projects and compare successes and failures.
confusing table mapping dependencies of key challenges on software eng technologies and these technologies on underlying science.
need for domain science!

BoehmBhuta08

Barry Boehm & Jesal Bhuta
Balancing Opportunities and Risks in Component-based software development
IEEE Software Magazine V25n6(Nov/Dec 2008)pp56-63
=IDEA =EXAMPLE JPL PROCESS INCREMENTAL COMMITMENT ITERATION RISKs STAKEHOLDERS
ICM::acronym="Incremental Commitment Model",
ICM::lifecycle=exploration; valuation; foundations; develeopment & foundations; do(Operations & Development & Foundations ).
Mentions example of an architectural mismatch leading to a 4 times over-run, taking 5 person-years rather than 1.

Boehmetal97

Barry Boehm & Alex Egyed & Julie Kwan & Ray Madachy
Developing Multimedia Applications with the WinWin Spiral Model
[JazayeriSchauer97] pp20-39
=DEMO PROCESS TOOLs
students develop multimedia systems for USC library in 11 weeks
key milestones=life_cycle_objectives life_cycle_architecture initial_operational_capability.

BoehmHuang03

Barry Boehm & Li Guo Huang
Value-Based Software Engineering: A case Study
IEEE Computer Magazine V36n3(Mar 2003)pp33-41
=CASESTUDY ECONOMIC REQUIREMENTS PROCESS ESTIMATING AGILE FEEDBACK
Software can/does fail because of business non-technical value errors. See [ http://www.standishgroup.com/ ] CHAOS report.
Need to track the business value of all tasks performed and needed and use this to adjust plans.
initiative #(->cause_effect) ->assumptions
EDSER::="Economics-Driven Software Engineering Research", [ http://www.edser.org ]

BoehmHuangJainMadachy04

Barry Boehm & LiGuo Huang & Apurva Jain & Ray Madachy
The ROI of Software Dependability: The iDAVE Model
IEEE Software Magazine V21n3(May/Jun 2004)pp54-61
=CASESTUDY COCMO RELIABILITY ECONOMICS COQUALMO MTBF NASA OrderProcessing
iDAVE::="information Dependability Attribute Value Estimation".
Estimates the rate of introduction and removal of defects and the effect on the MTBF.
MTBF::="Meantime before Failure",
MTTR::="Meantime to Repair".
MTBF and MTTR leads to Availability.
Availability changes Benefit.
Hence ROI.
Does not quantify risks such as loss of life and reputation.

BoehmIn96

Barry Boehm & Hoh In(USC)
Identifying Quality-Requirement Conflicts
IEEE Software magazine V13n3(Mar 1996)pp25-35
=ADVERT TOOL QUALITY conflicts
QARCC Knowledge-based groupware tool WinWin Stakeholders--<quality attributes<>-<>Techniques

BoehmPapaccio88

Barry W Boehm & Philip N Papaccio
Understanding and Controlling Software Costs
IEEE Trans Soft Eng VSE-14n10(Oct 1988)pp1462-1477
=IDEA spiral model+value chain+oportunity tree COST
Conclude: important & contolling cost means controlling quality & less new code by best people with little rework and integrated support environment

BoehmPortAl-Said00

Barry Boehm & Dan Port & Mohammed Al-Said
Avoiding the Software Model-Clash Spider-web
IEEE Computer Magazine V33n11(Nov 2000)pp120-122
=IDEA SUCCESS MODELS PQRST Mbase stake holders Master Net
Stakeholder := user | acquirer | developer | maintainer | ... | public.
Each stake holder has a different model of what is needed.
Each model is a set of assumptions.
Classified as process, product, property, and success.
Could use purpose, qualities, techniques, team, etc .
Clashes can occur between and within different stakeholder models.
Has been used two diagnose problems quickly in large and small projects.
interesting spider-web diagram on p121.
Mbase::= See http://sunset.usc.edu/research/MBASE.

BoehmTurner03a

Barry Boehm & Richard Turner
Using Risk to Balance Agile and Plan-Driven Methods
IEEE Computer Magazine V36n6(Jun 2003)pp57-66
=ADVERT one-size situation risk process agile vs planned anchor mbase rup xp spiral modules
Based on book by same authors... [BoehmTurner03b].
Sidebar pp58-59: defines home grounds for agile and plan-based processes plus five critical factors: size, criticality, dynamism, personnel, and culture. Kiviat style polar chart.
sidebar p60:misquotes Cockburn03. 3 levels of skill.
figure 1 p60. idea: if situation does not fit either agile or planned then architect the project into agile and planned parts.
p63: can focus testing on the high-risk parts.
fig 4 p65: 3 kinds of risk: environmental, agile, plan-driven. ranges: minimal..showstopper.

BoehmTurner03

Barry Boehm & Richard Turner
Balancing agility and Discipline: A guide for the perplexed
Addison-Wesley Longman Boston MA 2003 ISBN 0321186125
=UNREAD =SYNTHESIS AGILE ONESIZE CR 0410-1130
Avertized in [BoehmTurner03a].

BoehmTurner05

Barry Boehm & Richard Turner
Management Challenges to Implementing Agile Processes in Traditional Development Organizations
IEEE Software Magazine V22n5(Sep/Oct 2005)pp30-39 =REPORT WORKSHOP Management Agile vs Traditional People Organizations Culture
p34. Sidebar lists 8 nonproblems + 10problems due to size/scope + 18 significant issues.
Authors make suggestions.

BoerFarenhorst08

Remco C de Boer & Rik Farenhorst
In search of 'Architectural Knowledge`
ICSE 2008, 3rd I workshop on Sharing and reusing architectural knowledge (2008) pp71-78 [ 1370062.1370080 ]
=SURVEY 115 ARCHITECTURE SEMANTICS
Number of relevant papers increasing exponentially.
Out of 115 papers, 14 give a clear definition. 7 in 2007 alone.
Abstract

BoerVliet08

Remco C de Boer & Hans van Vliet
On the similarity between requirements and architecture
Journal of Systems and Software V82n3(Mar 2009)pp544-550
=ESSAY REQUIREMENTS = DECISIONS ARCHITECTURAL KNOWLEDGE
Abstract

Bogart91

Kenneth P Bogart
An Obvious Proof of Burnside's Lemma
American Math Monthly V98n12(Dec 1991)pp927-928
"a function f from set S to a set T defines a multiset of size |S| chosen from T in which the multiplicity of t ∈ T is the number of s ∈ S with f(s)=t" =map[t:T]|/f(t)| = /f; Card= Card o /f. +(Card o /f)=Card o dom(f).

Bohlen02

Boris Bohlen & Dirk Jager & Ansgar schleicher
UPGRADE: building interactive tools for visual languages
[SCI2002] V1(Jul 2002)
=EXPERIENCE VISUAL GRAPHIC TOOLS

BohmJacopini66

Corrado Bohm & Giuseppe Jacopini
Flow Diagrams, Turing Machines, and Languages with only Two Formation Rules
Commun ACM V9n5(May 1966)pp366-71 [ 355592.365646 ]
=THEORY Structured programming technical sequential proof
The key paper that allowed structured programming to take off.
(BohmJacopini)|-All programs can be reprogrammed using sequence, selection, and iteration and no other structures.

BojicEtal04

Dragan Bojic & Thomas Eisenbarth & Rainer Koschke & Daniel Simon & Dusan Velasevic
Addendum to "Locating Features in Source Code"
IEEE Trans Software Engineering V30n2(Feb 2004)p140
=SURVEY CONCEPT ANALYSIS
Ball: tests vs parts of programs to help testing.
BojicVelaseic: usecase vs parts of programs refactoring in UML.
EisenbarthKosckeSimon: scenarios vs functional blocks to aid traceability

BojicVelasevic00

Dragan Bojic & Dusan Velasevic
Reverse Engineering of Use Case Realizations in U ML
ACM SIGSOFT Software Engineering notes V25n4(Jul 2000)pp56-61
=IDEA VisualC++ TEST profiling LOGIC DA-C
use concept analysis to convert profiles of test executions into lattices of use-cases

Bokowski99

Boris Bokowski
CoffeeStrainer: Statically-checked Constraints on the Definition and use of Types in Java
ESEC/FSE'99 SIGFOFT SE Notes V24n6(Nov 1999)pp355-374
=TOOL JAVA V&V CORRECTNESS TYPES CONSTRAINTS

BollellaGosling00

Greg Bollella & James Gosling
The Real-time specfication for java
IEEE Computer Magazine V33n6(Jun 2000)pp47-54
=HISTORY OBJECT-ORIENTED NET PERFORMANCE RTSJ RTJEG NIST STANDARD

Bollinger95

Terry Bolinger(DSC Communications)
What can Happen when Metrics Make a Call
IEEE Software Magazine V12n1(Jan 1995)pp15
Distinguish feature metrics from derived metrics. derivation: equation supposed to show progress towards goal
Dangers of Bogus metrics (eg lines of code). pressures practitioners into doing bad things almost inevitable
need to listen to developers very carefully: can give a good metrics program & get some serious buy-in as well

Bollinger00

Terry Bollinger
Visual Basic: Taming the woolly mamoth
IEEE Software Magazine V17n3(May/Jun 2000)pp16-17
=ESSAY COBOL BASIC THEORY vs PRACTICE
why two very popular languages have so few papers written about them?

BollingerBeckman99

Terry Bollinger & Peter Beckman
Linux on the Move
IEEE Software Magazine V16n1(Jan/Feb 1999)pp30-35
=HISTORY open-source development TECHNICAL
only use honest unmanaged of code peer review

Bolloju04

Narasimha Bolloju
Improving the quality of business object models using Collaboration patterns
Commun ACM V47n7(Jul 2004)pp81-86
=EXPERIMENT MODEL REALITIES PATTERN UML COMPOSITION
Based on Coad and Fowler lists 12 simple patters that helped students improve their conceptual models in 13 different business application domains: spotting classes and connections, plus correcting errors.
Collaboration_patterns::#Pattern=following,
- E1: Role (1)-(0..*) Transaction
- E6: Transaction (1)-(0..*) FollowupTransaction E5: Specification (1)-(0..*) Transaction
- E3: CompositeTransaction (1)<*>-(0..*) LineItem
- E2: Place (1)-(0..*) Transaction
- R: Actor (1)-(0..*) Role
- T1: Item (1)-(0..*) SpecificItem
- T4: Group (1)<>-(0..*) Member
- E4: SpecificItem (1)-(0..*) Transaction
- T2: Assembly(1)<*>-(0..*) Part
- P: OuterPlace (1)-(0..*) Place
- T3: Container (1)<*>-(0..*) Content
Next [BollojuLeung06]

Bolloju09

Narasimha Bolloju
Conceptual Modeling of Systems Integration Requirements
IEEE Software Magazine V25n5(Sep/Oct 2000)pp66-74
=EXPERIMENT METHOD NOTATION SYSTEM REQUIREMENTS SERVICES
Graph: Nodes represent subsystems and transformations. Arcs labelled with conditions and messages.
Transformations: BATCH and SPLIT, AGGREGATE and DISTRIBUTE, X(translation).
Uses <....> to indicate refined subsystem.
Tested an 78 graduate students who found it usable.

BollojuLeung06

Narasimha Bolloju & Felix S K Leung
Assisting Novice Analysts in Developing Quality Conceptual models with UML
Commun ACM V49n6(Jun 2006)pp108-112
=EMPIRICAL 15 PROJECTS UML UseCase Domain ERD sequence diagram model V&V SQA REQUIREMENTS CSCI372 CSCI375

Table 3 lists the commonest errors by artifact
Table

Artifact	Syntax	Semantics	Pragmatics
Use Case Diagram	bad notation	bad extends	cases too small?
Use Case Description	mismatch name with diagram	MIssing and ambiguous steps, invalid extension	steps too small and implementation dependent
Class Diagrams	not listing operations in sequence diagram or listing implicit operations	wrong multiplicity, mislocated attributes and operations, unrealizable operation	Subclasses not distinguished, showing inherited attributes
Sequence Diagram	missing "found" signal, return to wrong object, class not on class diagram	missing parameters, parameters used before set, missing classes	Responsibility misallocated to wrong object [Larman05]

(Close Table)

Ref to [LindlandSundreSolvberg94] for qualities of conceptual models.
Also see [Bolloju04]

Bolognesi00

Tommaso Bolognesi
Toward Constraint-Object-Oriented Development
IEEE Trans Software Engineering V26n7(Jul 2000)pp594-616
=EXAMPLE OBJECT-ORIENTED SPECIFICATION DESIGN STYLE COO LOTOS CO-NOTATION Z GRAPHIC

BolognesiBrinkma95

T. Bolognesi & Ed Brinksma
Introduction to the ISO specification language LOTOS
Comput Network and ISDN Syst V14n1(1987)pp25-29

Bolognesietal95

T. Bolognesi & Jeroen van de Lagemaat (mailto:lagemaat@cs.utwente.nl) & C.A. Vissers (ed)
LOTOSphere: Software Development using LOTOS
Kluwer Academic Publishers 1995 ISBN 0-7923-9529-8
=ADVERT LOTOS TOOLS

Bolt84

?? BOLT
Human interfaces for managers
Computer World v16 (July 1984) pp In Depth/1..18
=ARTICLE USER

BoltaciJones95

L. Boltaci & J.Jones
Formal specification using Z: A modeling approach
International Thomson Publishing London 1995.
=DEMO MODEL Z SPECIFICATION FORMAL

Bond95

David Bond
Project-Level Archetypes
Software Development Magazine(Jul 1995)pp39-44+letter (Oct 1995)p11
=IDEA DOMAINs ECONOMICS one-size does not fit all
Suggests that different industries/situations have different "best practices". four models:
1. constrained
2. internal client
3. vertical market
4. mass market.
cf [Constantine95b]
Letter points out the additional complexity of producing software is the need to integrate the new into existing systems.

BondAnderson01

Mike Bond & Ross Anderson
API-Level Attacks on Embedded Systems
IEEE Computer Magazine V34n10(Oct 2001)pp67-75
=HISTORY DESIGN SECURE INTERFACE CRYPTOGRAPHY ATMS COMMERCIAL IBM Visa VSM
Using formal methods to calculate new attacks on ATMs!
How to split a key so that it can be transmitted to a device securely in shares and combined internally so that the right key is installed and nobody knows what it is -- even if < n people collude, even if shareholders lie about their shares to the device!

BondG05

Gregory W Bond
Software as Art
Commun ACM V48n8(Aug 2005)pp118-124
=ESSAY ART
Knuth

BonifattiEtal01

Angela Bonifatti & Fabiano Cattaneo & stafano Ceri & Alfonso Fuggetta & Stefano Paraboschi
Designing Data Marts for Data Warehouses
ACM TOSEM Trans Software Engineering & Methodology V10n4(Oct 2001)pp452-483
=CASESTUDY DATA OLAP REQUIREMENTS GQM Star ERD C-Graph snowFlake

BontempsHeymansSchobbens05

Yves Bontemps & Patrick Heymans & Pierre-Yves Schobbens
From Live Sequence Charts to State Machines and Back: A Guided Tour
IEEE Trans Software Engineering V31n12(Dec 2005)pp999-1014
=THEORY REQUIREMENTS SCENARIOS SSDs MSC Message Sequence diagrams LSC Live sequence charts FSM/STD STATE CHARTS
Proves that most problems linking message sequence charts to state based models are intractable -- efficient automation may be impossible. [Harel01]

Booch83

G Booch
Software Engineering with Ada
Benjamin Cummings 1983
=HOWTO object-oriented graphic text Reality Technical

Booch86

Grady Booch
Object Oriented Development
IEEE Trans Soft Eng vSE-12n2(Feb 1986)pp211-221 (in BerglandZave86)
=HOWTO Ada graphic Reality object

Booch91

Grady Booch
Object Oriented Design with applications
Benjamin Cummins Redwood City CA 1991 ISBN 0-8053-0091-0 CR9105-0322 & CR 9209-0690 & CR9404-0198
=HOWTO [Booch94a instead]

Booch94a

Grady Booch(Rational)
Object Oriented Analysis and Design with applications(2nd Edn)
Benjamin Cummins Redwood City CA 1994
ISBN 0-8053-5340-2 CR9502-0135"Marked improvement over the first edition while retaining the outstanding features of the original"(T H Tse)

Booch94b

Grady Booch
Coming of Age in an Object-Oriented World
IEEE Software Magazine V11n6(Nov 1994)pp33-41
1. off the shelf
2. Codifies a specific and well understood horizontal domain
3. large market
4. driven to higher technical sophistication by the market
5. beomes a commodity item
6. Custom
7. Vertical business line
8. includes off the shelf components
9. must be as complex as the domain
10. domain is not well understood and is complex.
11. OO::=Net{Abstraction, Encapsulation, Inheritance, Polymorphism}.
  OO{programming, methods, infrastructure}
  Increasing focus on architectures rather than just classes
  Includes RDBMSs as OO.

Booch99

Grady Booch(guest editor)
UML in action
Commun ACM V42n10(Oct 1999)pp26-70
See [Kobryn99] [Larsen99] [Selic99] [BellSchmidt99] [Conallen99]

Booch01

Grady Booch
The Illusion of Simplicity
Software Development Magazine V9n1(Jan 2001)pp57-59
=ARTICLE PQRST MODEL MODULE
Forces on software development: cost/schedule, functionality, compatibility, reliability/availability, security, failsafe/fault-tolerance, Resilience, technology churn, scalability, capacity, Performance
help: abstractions: Object-Oriented , patterns, modeling
balance and mitigating conflicting forces.

Booch01b

Grady Booch
Developing the Future
Commun ACM V44n3(Mar 2001)pp119-121
=POLL OPINION PEOPLE SWEBOK XP Opensource
Future: split betwen high and low ceremony processes leading to some reconciliation.
More user-programmers vs a more mature profession.

Booch06

Grady Booch
The Accidental Architecture
IEEE Software Magazine V23n3(May/Jun 2006)pp9-11
=ESSAY ARCHITECTURE =HISTORY WWW/NET PATTERNS
Notes that we don't have a comprehensive list of architectures for software.
... unlike buildings: Babylonian, Greek, ...
Refers to Henry Petroski.
Describes a history of the WWW architectural styles: Plain HTML, Eye-Candy, simple scripting, middleware, simple frameworks, rich-client | service-oriented architecture.
Argues that architectural patterns emerge from a experience.

Booch06a

Grady Booch
Goodness of fit
IEEE Computer Magazine V39n10(Oct 2006)pp14-15
=ESSAY ARCHITECTURE STYLE PATTERNS FORTRAN COMPILER
Bachus's original pipe-and-filter architecture for FORTRAN compilation remains good for recent languages....with some small tweaks.
Does not mention [Jackson75]'s use of pipe+filter in Data Processing and McIlory's pipes in UNIX.
For a given set of forces there is a better architecture. The forces in a given domain are pretty constant.

Booch07

Grady Booch
Object-oriented analysis and Design with Applications
Addison Wesley Longman Redwood City CA 2007 ISBN 020189551X CR 0808-0732
=UNREAD =HOWTO ANALYSIS DESIGN OBJECTS
Notes [click here Booch07 if you can fill this hole]

Booch10

Grady Booch
Enterprise Architecture and Technical Architecture
IEEE Software Magazine V27n2(Mar/Apr 2010)pp96+95
=ESSAY TECHNICAL vs SYSTEM
Enterprise Architecture and Technical Architecture speak about different things mostly, so keep the notations etc. separate.
One is about the organisation and the other about the software.
Many more frameworks for doing enterprise architecture than technical architecture.

Booch10a

Grady Booch
Architecture Reviews
IEEE Software Magazine V27n3(May/Jun 2010)pp96+95
=EXPERIENCE ARCHITECTURE REVIEWS CONFIDENCE QUALITIES ALTERNATIVES TRIAGE ASSUMPTIONS REALITIES
Constructive Conflict. A review that just involves people nodding as artifacts are presented is a waste of time.
Focus on the forces that shape the system.
ATAM::="Architecture Tradeoff Analysis Method", [ http://www.sei.cmu.edu/architecture/start/glossary/ ]
Name significant design decisions.
Looking for a good enough plan to proceed. There is no single right answer.
Deciding whether to fix or to replace?

Booch10b

Grady Booch
An architectural oxymoron
IEEE Software Magazine V27n5(Sep/Oct 2010)pp96+95
=ADVERT AGILE ARCHITECTURE REQUIREMENTS DESIGN DECISIONS
Pointers to pages: Ambler, Wikiwiki, Coplien, Krutchen, ...
Need to socialize important design decisions and their rationale.

Booch10c

Grady Booch
The elephant and the blind programmers
IEEE Software Magazine V27n6(Nov/Dec 2010)pp88+87
=FABLE ENTERPRISE ARCHITECTURE VIEWPOINTS POV RASHOMON
so what do you think "the enterprise" is?

Booch12

Grady Booch
The Professional Architecture
IEEE Software Magazine V29n1(Jan/Feb 2012)pp12-13
=ESSAY ARCHITECTURE TECHNICAL SOCIAL
Complex balance between technology and needs,
Tension between discovery, invention, and implementation, ...

Boogie09

Microsoft Research
Boogie -- The World's Best Program Verification System
Web site Aug 27th 2009 [ http://boogie.codeplex.com/ ]
=ADVERT OPEN SOURCE VERIFIER SQA PROOF NONSEQUENTIAL TOOL #
"Boogie is a program verification system that produces verification conditions for programs written in an intermediate languagec (also named Boogie). The intermediate language is easy to target from source languages such as Spec#, C#, or even C."

BoralvStalmarck99

Arne Boralv & Gunnar Stalmarck
Formal Verification in Railways
In [HincheyBowen99] pp329-350
=EXPERIENCE RISKS SPECIFICATION STD/FSM LOGIC TPA vs DESIGN V&V TOOL Prover Delphi for ADtranz CVT Swedish Sternol
Prover is a Company specializing in the industrialization of formal methods. Stalmarck has patented the proof algorithm!
Can we make a formal tool that is as transparent to use as a word processor? Some parts need a formal methods expert, but some parts can be made more useful to railway interlocking engineers.
Need to trade-off expressive power of logic with the performance of the tool.
Claims that ONLY domain/application knowledge is needed to use the tools.

Borger88

Egon Bo"rger(Ed)
Trends in Theoretical Computer Science
Computer Science Press Rockville Maryland 1988
=Series: Principles of Computer science series
[Gurevich88]

BorgerSchulte00

Egon Bo"rger & Wolfram Schulte
A Practical Method for Specification and Analysis of Exception Handling -- A Java/JVM Case Study
IEEE Trans Software Engineering V26n9(Sep 2000)pp872-887
=CASESTUDY LOGIC SPECIFICATION SEMANTICS JAVA COMPILER JVM PROOF

Borgida85

Alexander Borgida
Features of Languages for the Development of Information Systems at the Conceptual Level
IEEE Software V2n1(Jan 1985)pp63-72
=SURVEY data concepual modeling

Borgidaetal95

Alex Borgida & John Mylopoulos & Raymond Reiter
The frame problem in procedure specifications
IEEE Trans on Software Eng VSE-SE-21n10(Oct 1995)pp785-798
=CRITIQUE LOGIC Set Theory SPECIFICATION METHODS circumscription [BorgidaMylopoulosReiter93] JacksonD9 [McCarthy87] [Delgrande98]

BorgidaGreenspanMylopoulos85

Alexander Borgida & Sol Greenspan & John Mylopoulos
Knowledge Representation as the Basis for Requirements Specifications
IEEE Computer MAgazine V18N4(Apr 1985)pp82-91 [ MC.1985.1662870 ]
=ESSAY MODEL REALITY PURPOSE Object-Oriented AI ONTOLOGY parts IS-A TIMES RML
Also see what happened [BorgidaGreenspanMylopoulos94]

BorgidaGreenspanMylopoulos94

Alexander Borgida & Sol Greenspan & John Mylopoulos
On formal requirements modeling languages: RML revisited
SIGSOFT Proceedings of the 16th international conference on Software engineering pp135-147 .See
=HISTORY RML MODEL REALITY PURPOSE Object-Oriented ONTOLOGY GIST KAOS
Also see [BorgidaGreenspanMylopoulos85]
Need QUALITIES -- non-functional requirements NFRs.

BorgidaJarke92

Alex Borgida & Mathias Jarke
Knowledge and Representation in Software Engineering(Editorial on special issue)
IEEE Trans SE-18n6(Jun 1992)pp449-450 CR9307-0467
domain logic ... relation to formal methods ... power vs performance ... empirical results

BorgidaMylopoulosReiter93

A Borgida & J Mylopoulos & R Reiter
"And Nothing Else Changes":The frame problem in procedure specifications
In Proc of the 15th Int Conf on Software Engineering
IEEE Computer Society(May 1993)pp303-314
Ref from ZaveJackson93 [Borgidaetal95] [BicarreguiRitchie95]

BorsoiBecerra08

Beatriz Terezinha Borsoi & Jorge Luis Risco Becerra
Definition and modeling of process using object orientation
ACM SIGSOFT Software Engineering Notes archive V33n3 (May 2008) Article No. 2
=IDEA PROCESS MODEL OBJECT-ORIENTED
Compare to earlier proposal [JaccheriPiccoLago99] E^3 OO process language.
But
1. OMG_SPEM::="Software Process Engineering MetaModel", [ modeling_spec_catalog.htm ]
(Close But )

BosakEtAl62

Robert Bosak & Richard F Clippinger & Carey Dobbs & Roy Goldfinger & Renee B Jasper & William Keating & George Kendrick & Jean E Sammet
An information algebra: phase 1 report - language structure group of the CODASYL development committee
Commun ACM V5n4(Apr 1962)pp190-204 [ citation.cfm?doid=366920.366935 ]
=THEORY DATA GEOMETRY ALGEBRA SETS GLUMPS
An early attempt to at a unified theory of data -- using geometric metaphors.

Bosak98

Jon Bosak(Sun)
Mediaindependent Publishing: Four Myths about XML
IEEE Computer Magazine V31n10(Oct 1998)pp120-122
=ADVERT XML
1. XML is a not MS conspiracy -- many others are involved.
2. XML is not an extension of HTML -- both come from SGML.
3. XML can not drive a web browser without style rules: DSSL and XSL [ WD-xsl ]
4. XML is not just for data -- it can convey any kind of structured data but it can also make any kind of information independent of platform/vendor/media/nationallity
Compare XML with YAML and JSON.

BossomaierGreen01

Terry R J Bossomaier & David G Green (Editors)
Complex Systems
Cambridge University Press 2000 ISBN 0-521-46245-2 Q172.5.C45C64
=SURVEY MATHEMATICS Alife GRAPH Theory Criticality fractals theory nets chaos

Boswell95

Anthony Boswell
Specification and Validation of a Security Policy Model
IEEE Trans on Software Eng VSE-21n2(Feb 1995)pp63-68
=ADVERT TOOL FORMALIZER and Z

Botting75

Richard J Botting
Letter on Comments and Methods
Computing Europe, Oct 30th, p8.
=LETTER ASSERTIONS CODE TECHNICAL
Don't want comments that tell you that i++ adds one to i.
You want comments that state what is necessarily true at that point in the program.

Botting77

RJ Botting
Efficient Storage for Amorphous Data
Software -Practice and Experience V7pp201-203
=DEMO Technical data structure

Botting78a

Richard J Botting
Loglan -- a more flexible language
=ADVERT Loglan Mathematics Logic ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) n598 (Feb 16 1978)letters
Response to [Kelly78]
Argues that Loglan fits Kelly's criteria better.

Botting78b

Richard J Botting
Languages at the Crossroads
=ADVERT Loglan Mathematics Esperanto ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) n598 (April 27 1978)p4
Response to [Love78]
Calls for "an Intermediate Text Language that benefits language translation and not use computers to help Esperanto"
Need to examine many alternative solutions to a problem.

Botting84a

RJ Botting
Fred - a Friendly Editor
Proc Western Educational Computing Conference Nov 1984 Western Periodicals Co N Hollywood CA.
=DEMO USER DAD System Technical [ papers/rjb84a.FRED.html ]
DAD::="Dynamic Analysis and Design", uses BNF style descriptions of entity life histories to determine the code of the software that keeps track of them.
Evolution of FRED is further tracked in [Botting84b]

Botting84b

RJ Botting
Generalization - An Alternative to Error Messages
Proc Western Educational Computing Conference Nov 1984( pp98-99) Western Periodicals Co N Hollywood CA. [ papers/rjb84b.Generalization.html ]
=DEMO USER non-sequential System PROTOTYPING EVOLUTIONARY AGILE
History of a simple technology strapped but successful piece of software.
Error messages show the lack of imagination of programmers.
Software can be evolved.

Botting85a

RJ Botting
On Prototypes vs Mockups vs Breadboards (letter)
ACM SIGSOFT Software Engineering Notes v10n1(Jan 1985)p18
=LETTER WORDS PROTOTYPING

Botting85b

RJ Botting
An Eclectic Approach to Software Engineering
pp25-29 Proc Third Int'l Workshop on Software Specification & Design(IWSSD3) Aug 1985
=survey PQRST PURPOSES QUALITIES REALITIES SYSTEMS TECHNOLOGIES DFD PROTOTYPES NOTATIONS
Names 28 processes available to a software developer and describes how they are connected. The processes are found in 31 different references.

Botting85c

RJ Botting
Evolution of Software for a Faculty Workstation
pp120-124 Western Educational Computing Conference1985
=demo evolution prototypes tools System AGILE
You can not reduce paperwork in an office by using a document driven software process in that office.
Abstract

Botting85d

RJ Botting
IO Statements in Higher Programming Languages(letter)
IEEE Computer v18n8(Aug 1985)p95
=harmful Technical

Botting86a

RJ Botting
Into the Fourth Dimension: An Introduction to Dynamic Analysis & Design
SE Notes v11 n2 pp36-48 Apr 1986 ACM SIG Software Engineering
=THEORY DAD graphic logic Reality

Botting86b

RJ Botting
Novel Security Techniques for Online Systems
(Pracnique) Commun ACM Vol 29 No 5 (May 1986)
=DEMO DAD SECURITY HCI

Botting87a

RJ Botting
A Critique of Pure Functionalism
pp148-153 Proc. Fourth Int'l Workshop on Software Specification & Design(IWSSD4) April 1987 IEEE Catalog No. TH0181-8 LA CA
=DEMO formal DAD DFD ERD DDD data lift

Botting87b

RJ Botting
Regular Expressions Relations & Software: Part I - Practice & Part II - Theory
Western Educational Computing Conference Nov 1987 Western Periodicals Co. N Hollywood CA.
=THEORY DDD JSP theory languages logic formal

Botting88

RJ Botting
Data Structures Classes Can Mislead
Western Educational Computing Conference Nov 1988 Western Periodicals Co N Hollywood CA.
=THEORY DISK DATA OPTIMIZATION PERFORMANCE QUALITIES
Assumes [PechuraShoefler83] 's formula for disk access: time delay is linearly dependent on distance between data.
Proves that for large data structures common O(...) formulas are wrong.
Example: a binary search of n items in a large disk file takes O(n) not O(log(n)).

Botting89a

RJ Botting
Comments on Tripp's Graphical Notations
ACM SIGSOFT Software Engineering Notes V14n1 (Jan 1989)p83
=LETTER Dimensional charts graphic

Botting89b

RJ Botting
Abstract of Research
Proc ACM CSC Conf 1989
=survey PQRST

Botting93

RJ Botting
Would you like your program in a glass?
IEEE Computer Magazine V26n10(Oct 1993)p104
=JOKE PROCESS
vaporware, liquidware, software, soggyware, firmware, hardware

Botting94

Richard J Botting
When More is Expected of Programmers(Letter)
IEEE Software Magazine V11n5(Sep 1994)p9
=LETTER PEOPLE

Botting95a

Richard J Botting
On the Relational Semantics of Programming Languages
Faculty seminar CSci CSUSB Spring 1995 [ rjb95a.Relations.vs.Programs.html ]
=THEORY SEMANTICS RELATIONS

Botting95b

Richard J Botting
Can One Size Fit All?
Faculty seminar CSci CSUSB Fall 1995 [ rjb95b.one.size.html ] [Botting97a]
=IDEA ECONOMICS CULTURE ONE-SIZE

Botting97a

Richard J Botting
On the Economics of Mass-Marketed Software
pages 465-470 of Proceedings of [ICSE'97]
=IDEA ECONOMICS SUNK externallities CULTURE ONE-SIZE
why one product becomes dominant and then is eclipsed by a later one. network effects. Sunk Costs. cultural assumptions [Botting95b] [CusumanoYoffie98]

Botting99

Richard J Botting
On the application of a popular notation to semantics
ACM SIGPLAN Notices V34n6(Jun 1999)pp82-83
=IDEA Why not use the UML and OCL to express Programming LANGUAGE SEMANTICS OBECT-ORIENTED
Uses TABULAR presentation of polymorphic functions.
Proposes a fixed point operator for the OCL

Botting99a

Richard J Botting
The MATHS Manifesto
URL [ 10_manifesto.html ]
=ADVERT DEFINES MATHS
MATHS::="Multi-purpose Abstractions, Terminology, Heuristics and Symbols".

Botting00a

Richard J Botting
Designing the Real World
IEEE Software Magazine (Letters) V17n2(Mar/Apr 2000)pp8-9
=ESSAY REALITY OOA/D NONSEQUENTIAL
See [Kaindl99]

BottingJuristo00

Richard J Botting
Natural Language dispute (Letter)
IEEE Software Magazine V17n5(Sep/Oct 2000)p11
=DISCUSSION POLYMORPHISM MODEL ANALYSIS vs DESIGN OBJECT-ORIENTED GRASP
Discussion of [JuristoMorenoLopez00]

Botting02

Richard J Botting
Some Stochastic Models of Software Evolution
[SCI2002] V1(Jul 2002)pp23-27
=THEORY DEBUGGING EVOLUTION SOFTWARE
Abstract:
Outline [ papers/rjb02.evolve.txt ] (TXT file).
Conclusions
1. One size does not fit all
2. Keep your n small and your α high!
3. A million monkeys will beat a blind watch maker.

Botting05

Richard J Botting
Teaching and Learning Ethics in Computer Science: Walking the Walk
ACM SIGCSE Tech Symp Proc (Feb 2005)pp342-346, SIGCSE Bulletin "Inroads" V37n1 (Mar 2005) pp342-346.
=ANECDOTE EDUCATION ETHICS SECURITY Identity Theft

Botting05a

Richard J Botting
On the co-evolution of SSADM and the UML
Chapter V in [Yang05] pp134-151
=IDEA UML2.0 SSADM

Botting05b

Richard Botting
Small Errors in "Toward formalizing domain modeling semantics in language syntax"
IEEE Trans Software Engineering V31n10(Oct 2005)pp911
=Correction Statecharts fork vs decision

Botting06

Richard J Botting
Use Case Diagrams
IEEE Computer Magazine V39n8(Sep 2006)pp5 [ MC.2006.317 ]
=LETTER DFD USE CASES UML2.0 information flows
See [DedekeLieberman06] for an non-standard way to document use case data flows.
Refers to [Botting05b] and [ http://cse.csusb.edu/dick/papers/rjb04bDFDs/ ]

BottingRoss

R J Botting & Paul Ross
Software Engineering for Computer Scientists
Unpublished Manuscript for a text book used in early 1980s.
=text formal data DDD method co-routines nonsequential nondeterministic design technical assemblers loaders editors
AKA Engineered Systems Software

BourdeauCheng95

Robert H Bourdeau & Betty H C Cheng
A Formal Semantics for Object Model Diagrams
IEEE Trans on Software Eng VSE-SE-21n10(Oct 1995)pp799-821
OMT in Larch LSL GRAPHIC FORMAL OBJECT-ORIENTED [ serg.html ]
Does not permit OMT subclasses to contain attributes found in superclass (fig 39..41 eqn 24)

BourqueEtal99

Pierre Bourque & Robert Dupuis & Alain Abran & James W Moore & Leonard Tripp
A Guide to the Software Engineering Body of knowledge
IEEE Software Magazine V16n6(Nov/Dec 1999)pp35-41
=ADVERT SWEBOK PLAN ENGINEERING

BoussinotSimone96

Frederic Boussinot & Robert de Simone
The SL Synchronous Language
IEEE Trans Softw Eng VSE22n4(Apr 1996)pp256-266
"as soon as signal hypotheses are allowed incorrect programs may be written". Incorrect meaning non-causal and unpredictable: "when S then t1 else t2" suspends if S is not present and then enters t2....

Boute81

R T Boute
"Towards System Specification Languages"
4th International conference on Software Engineering for Telecommunications Switching Systems University of Warwick(Conventry UK)
Inst of Electrical and Radio Engineers London UK July 1981 pp31-37
=SURVEY SRS LANGUAGES
1. Used p397 of DavisA90
2. Condemns STDs/FSMs
3. (1) not abstract, (2) not powerful enough (3) not structured Davis: "proposes using non-deterministic multistring dialogue grammars".

Boute92

Raymond T Boute
The Euclidean definition of the functions div and mod
ACM TOPLAS V14n2(April 1992)pp127-144
CR9211-0871
Semantics mathematics

Boute00

Raymond T Boute
Supertotal function definition in Mathematics and Software Engineering
IEEE Trans Software Engineering V26n7(Jul 2000)pp662-672
=IDEA FORMAL LOGIC FUNCTIONAL MATHEMATICS calculational
Refers to FunMath [PVS]
[Parnas93]
Compare: [LPT]
Question: How to calculated easily with partial functions?
Idea: Functions defined by a domain and an expression can be treated as total by extension to an arbitrary value in calculating with suitably guarded formulae

BouyerFahrenbergLarsenMarkey11

Patricia Bouyer & Uli Fahrenberg & Kim G Larsen & Nicolas Markey
Quantitive Analysis of Real-Time Systems using Priced Timed Automata
Commun ACM V54n9(Sep 2011)pp78-87 [ 1995376.1995398 ]
=ADVERT MATHEMATICS AUTOMATA FSM TIMING PRICE PERFORMANCE ENERGY GAMES
Presents an extension to timed automata to included pricing and uncertainty.
Transitions change "clocks" and can supply constraints. States have prices.
Example constraints have form x-y<=c where x & y are variables and c is a constant.
Can calculate minimum price, minimum times, whether feasible, etc.
Many tools exist to analyze these automata.

BowdigeGriswold98

Robert W Bowidge & William G Griswold
Supporting the Restructuring of Data Abstractionns through Manipulation of a Program Visulaization
ACM TOSEM V7n2(Apr 1998)pp109-157
=TOOL TECHNICAL GRAPHIC ADT REENGINEER

Jonathon Bowen
The Ethics of Safety-Critical systems
Commun ACM V43n4 (Apr 2000)91-97
=ESSAY RISKS METHODS Aristotle LOGIC
7 sins: epideictic, hyperole, pistic, oligarchy, ephemeral, epexegesis , maiandos
principles
modes of thought: scientific, technical, prudence, inntelligence/intuition, wisdom
p93: "most theorems are correct, but most hand proofs are wrong"

Bowen01

Jonathon P Bowen
Experience Teaching Z with TOOL and Web Support
ACM SIGSOFT Software Engineering Notes V26n2(Mar 2001)pp69-75
=REPORT UK TEACHING MATHEMATICAL LOGICAL SPECIFICATION REFINEMENT TOOLS ZTC ZANS
Diagnostic quizzes leading to makeup tutorials help handle wide ranges of math skills.

BowenHinchey94

Jonathan P Bowen & Michael G Hinchey
Formal Methods andSafety Critical Standards
IEEE Computer Magazine V27n8(Aug 1994)pp68-71

BowenHinchey95a

Jonathan P Bowen & Michael G Hinchey
Ten Commandments of Formal Methods
IEEE Computer Magazine V28 n 4(Apr 1995)pp56-63
1. I. Thou shalt Choose an Appropriate Notation
2. II. Thou shalt Formalize but not Overformalize
3. III. Thou shalt Estimate Costs
4. IV. They shalt have a Formal Methods Guru On Call
5. V. Thou shalt not Abandon Traditional ethods
6. VI. Thou shalt Document Sufficiently
7. VII. Thou shalt not Compromise thy QUALITY Standards
8. VIII. Thou shalt not be Dogmatic
9. IX Thou shalt Test, Test, and Test again
10. X. Thou Shalt Reuse

BowenHinchey95b

Jonathan P Bowen & Michael G Hinchey
Seven More Myths of Formal Methods
IEEE Software Magazine V12n4(Jul 1995)pp34-40
1. 8. FM delay the development process
2. 9. FM lack tools
3. 10. FM replace traditional engineering design methods
4. 11. FM only apply to software
5. 12. FM are unnecessary
6. 13. FM are not supportted
7. 14. FM people always use FM
8. p40: "system development should be as formal as necessary, but not more formal."
  Notes problems:
9. sidebar, p37: defining FM, IEEE glossary has two.
10. notation
  p38: Notes resources: internet forums for Z, VDM, Larch, OBJ. FTP archives, Periodicals. Courses.
  p40: Quotes BBC Interview: "If you want to build systems with ultra-high reliability whcih provide complaxe functionallity and you want to guarantee that they are going to work with very high reliability...you can't do it"

BowenHinchey96

Jonathan P Bowen & Michael G Hinchey
To Formalize or Not to Formalize
IEEE Computer Magazine V29N4(Apr 1996}pp18-19
=EXPERIENCE FORMAL MATHEMATICS

BowenHinchey99

Jonathan P Bowen & Michael G Hinchey It's Greek to Me: Method in the Madness
In [HincheyBowen99] pp1-4
=ESSAY METHODS PHILOSOPHY ETHICS ARISTOTLE
describes sins that can destroy a project that uses formal methods.
Describes useful frames of mind

BowenHinchey06

Jonathan P Bowen & Michael G Hinchey
Ten Commandments of Formal Methods ... Ten years later
IEEE Computer Magazine V39n1(Jan 2006)pp40-48
=HISTORY FORMAL Z TLA
See also "The Ten Commandments revisited: a ten-year perspective on Industrial application of formal methods" Proc 10th Int'l Workshop on formal methods for industrial Critical Systems, ACM Press 2005 pp8-16

CF [BowenHinchey95a]
Table

Then	Now
I. Thou shalt Choose an Appropriate Notation.	More now. Hybrids.
II. Thou shalt Formalize but not Overformalize.	3 levels: specs, Proofs, machine checked.
III. Thou shalt Estimate Costs.
IV. They shalt have a Formal Methods Guru On Call.	Plus a domain expert early on.
V. Thou shalt not Abandon Traditional methods.
VI. Thou shalt Document Sufficiently.	Iterative. Including why & when decided.
VII. Thou shalt not Compromise thy QUALITY Standards.	Notation & method.
VIII. Thou shalt not be Dogmatic.	Gap between analysis & specification.
IX Thou shalt Test, Test, and Test again.
X. Thou Shalt Reuse.

(Close Table)

BowenHinchey11

Jonathan P Bowen & Michael G Hinchey
Ten Commandments of Formal Methods, a Decade Later
FM 2011: 17th International Symposium of Formal Methods
=HISTORY FORMAL METHODS COMMANDMENTS
Slides [ ten-commandments-of-formal-methods-a-decade-later ]
See older [BowenHinchey06] with same list but more commentary.

BowenReeves11

Jonathan P. Bowen & Steve Reeves
From a Community of Practice to a Body of Knowledge: A Case Study of the Formal Methods Community,
In Michael Butler and Wolfram Schulte (eds.), FM 2011: 17th International Symposium of Formal Methods. Springer-Verlag, LNCS, V6664(2011) pp308-322 [ fm2011 ]
=DEMO PROCESS COMMUNITY FORMAL METHODS Z BOK KNOWLEDGE Abstract.
The slides for the presentation are under: [ fm-2011-symposium-slides ]
Translation of formal portion of slides (in Z) into MATHS: [ samples/BoK.html ]

Bowles90

Adrian J. Bowles
A note on the Yourdon Structured Method(Announcement)
ACM SIGSOFT SEN V15n2(Apr 1990)p27
=HISTORY METHOD YSM evolution
YSM::="Yourdon Method".

Bowles95

Adrian J. Bowles
Object methods Emerging and Converging
Software Magazine (May 1995)pp96

BowmanBriandLabiche10

Michael Bowman & Lionel C Briand & Yvan Labiche
Solving the class responsibility assignment problem in object-oriented analysis with multiple-objective genetic algorithms
IEEE Trans Software Engineering V36n6(Nov/Dec 2010)pp817-837
=DEMO SEARCH MOGA OOAD CLASSES UML COUPLING COHESION EVOLUTION SPEA2
Demonstrates that multiple-objective evolution can, at some expense, undo damage done to an expert's design class diagram.
Compares work with other algorithms. SPEA2 is better.
Assumes that design is a detailed form of analysis. Shows domain or analysis models that include methods.

BowmanHoltBrewster99

Ivan T Bowman & Richard C Holt & Neil V Brewster
Linux as a Case Study: Its Extracted Software Architecture
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp555-563
=EMPIRICAL reverse-engineering extracts dependencies between modules.
More connections than predicted between subsystems.

BoyerYu96

Robert S Boyer & Yuan Yu
Automated Proofs of Object Code for a Widely Used Microprocessor
JACM V43n1(Jan 1996) pp166-192 CR9710-0117
=EXPERIENCE PROOF

BoyleReslerWinter99

James M Boyle & R Daniel Resler & Victor L Winter
Do You Trust Your Compiler?
IEEE Computer Magazine V32n5(May 1999)pp65-72 + letters V32n10(Oct 99)pp5-7
=ADVERT TAMPR DDD PROOF sound code transformations
Same ideas as McCarthy in the early 1960's
Letters point out errors in paper and reccommend peer review/inspection

BrachiLockermann78

?? Brachi & ?? Lockermann
Information systems Methodology
Springer Verlag lecture notes in Comp Sci #65
=survey SAD PQRST

BradacPerryVotta94

Mark G Bradac & Dewayne E Perry & Lawrence G Votta
Prototyping a Process Monitoring Experiment
IEEE Trans on Software Eng VSE-20n10(Oct 1994)pp774-784
CR1995-0106(by RJB)

Bradfield92

Julian C Bradfield
Verifying Temporal Properties of Systems
Birkhauser Boston Inc Cambridge MA 1992
ISBN 0-817603625 CR9209-0661(F.3.1)
=THEORY CORRECTNESS Petri nets

BradyDeMarco94

Sheila Brady & Tom DeMarco
Management Aided Software Engineering
IEEE Software Magazine V11n6(Nov 1994)pp25-32
Interview re management best of practice in software development at Apple. [ BradyDeMarco94.html ]

BraekHaugen94

R Braek & O Haugen
Engineering Real Time Systems
Prentice Hall Upper Saddle River NJ 1994 BCS Practitioner Series ISBN 0-13-034448-6

BraffortHirschberg63

Braffort & Hirschberg(Eds)
Computer Programming & Formal Systems
North Holland 1963
=THEORY formal LISP languages

BraheSchmidt07

Seen Brahe & Kjeld Schmidt
The Story of a Working Workflow Management System
ACM Proc GROUP'07 (Nov 2007) pp249-258 CR 0811-1106 ACM DOI [ 1316624.1316661 ]
=EXPERIENCE SYSTEMS WORKFLOW BPEL XML SOA SERVICE LEGACY WFM PEOPLE DANISH BANK 2003-2007 ORCHESTRATION PORTAL TASK vs CASE
CSCW::="Computer Supported Cooperative Work".
WFM::="Workflow Management".
SOA::="Service Oriented Architecture".
Early attempts to program office procedures failed because exceptions to the procedures were common. How to make the result adaptable? How to fit in with the continuing creation and adaption of procedures/workflows. How to integrate existing (legacy) systems.
Integrate systems by using SOA... encapsulate legacy code as a service. Workflow as glue.
(dick)|-Workflow sytems/languages seems to be like scripting.
Develop a workflow system iteratively.
Get the developers and the users closely involved.
Business's analyst's can get it wrong!
Development followed Babbage's model: craft; division of labor; stepwise automation; more or less complete automation.
Need to avoid fragmented tasks. People prefer complete cases to individual tasks. First task in process should assign remaining tasks in the case to same person. "We do not want to be a factory". Not task-centric, but case-centric. "It does not feel right " not to know the context of tasks.
Another early task in each workflow is to determine if the task is simple enough to be automated or needs human discretion and guidance.
Describing exceptions if difficult and time consuming. Better to bounce them to a human... and think about how to automate in a later iteration.
Automating more kinds of processes is an optimization. Tweaking and Twisting the automated processes.
Nearly a 20% gain in speed. 80-90% automated.
No need to re-enter data into each application.
People like to monitor automated processes.
Tell the users when the system is becoming unstable. Tell them about bugs. Tell them about performance problems.
Workflows integrated legacy systems into exiting processes -- so the old system could not be replaced until the workflow was redesigned, tested, and running with the new service provider. Increased coupling and dependency between systems.
Application niche is a very regular system -- unlike, say -- medicine.

BrandtEtAl09

Joel Brandt & Philip J Guo & Joel Lewenstein & Scott R Klemmer & Mira Dontcheva
Opportunistic Programming: Writing code to prototype, ideat, and discover
IEEE Software Magazine V25n5(Sep/Oct 2000)pp18-24
=EXPERIMENT BRICOLLAGE POSTMODERN PROTOTYPING GLUE WWW/NET d.mix
Principles for rapid prototyping
1. Glue together existing high-level components.
2. Add functionality via Copy-paste from the web.
3. Iterate rapidly.
4. Consider code to be impermanent.
5. Expect and prepare for debugging.
6. Use many languages.
7. Don't expect good code.
8. Need different version control.

BrandKlintVerhoef97

M G J van den Brand & P Klint & C Verhoef
Reverse Engineering and System Renovation -- an Annotated Bibliography
ACM SIGSOFT Software Engineering Notes V22n1(Jan 1997)pp56-68 [ citation.cfm?doid=251759.251849 ]
=BIBLIOGRAPHY REVERSE ENGINEERING RENOVATION REUSE REFACTOR 110 items

BrandtUden03

D Scot Brandt & Lorna Uden
Insight into Mental Models of Novice Internet Searchers Commun ACM V46n7(Jul 2003)pp133-136
=ADVERT TKS KAT ACTA HCI USER PEOPLE WEB/NET
Distinguishes mental models of tasks from conceptual models of systems.
TKS::theory="Task Knowledge Structure", can express what people know about a task in a structured way.
ACTA::technique="Applied Cognitive Task Analysis", interview ->outline; audit knowledge(cues+difficulties); simulate scenario giving cognitive processes, tabulate cognitive demands.
KAT::technique="Knowledge Analysis of Tasks", break down ( objects, actions, goals, subgoals); identify central and generic properties; pseudocode procedures and taxonomy of terms use, add task knowledge needed to pseudocode.
Novices may need more cues and structure to use search engines effectively.

BratthallWohlin02

Lars Bratthall & Claes Wohlin
Is it possible to decorate graphical Software design and architecture models with qualitative information? -- and Experiment
IEEE Trans Software Engineering V28n12(Dec 2003)pp1181-1193
=POLL 35 STUDENTS GRAPHIC COMPONENT METRICS RELATIONSHIPS
How to show: A controls B, A is bigger than B, A is internally more complex than B, and A is harder to use then B.
Rough consensus: control shown by position, size by area, complexity by darkening the inside or boundary.
Demo for a car controller.

BrayHess95

Olin Bray & Michael M Hess(both Sandia)
Re-engineering a Configuration Management System
IEEE Software Magazine V12n1(Jan 1995)pp55-63
=DEMO NIAM
1. NIAM::=Natural Language Information-Analysis Methodology.
2. NIAM::=Net{entity types. types of facts. interactions between types} verbal or graphic presentation deep-structure sentence tables of examples and counter examples of facts
  reinvention of LDST

BremleyHolmes00

Jesse L Bremley & Donald Holmes
Advanced Computer Topics for Precollege Students
Proc SCI/ISAS2000 VI pp468-494 [SCI00]
=EXPERIENCE EDUCATION AI
How inner-city (Washington DC) children can do literature searches in AI and implement the results in programs.

Brender02

Ronald F. Brender
The BLISS programming language: a history
Software - Practice & ExperienceV32n10(Aug 2002)pp955-981
=HISTORY SYSTEMS LANGUAGE

BreretonBudgetHamilton98

Pearl Brereton & David Budgen & Geof Hamilton
Hypertext: The next Maintenance Mountain
IEEE Computer Magazine V31n12(Dec 1998)pp49-55
=IDEA EVOLUTION WWW

BrewkaEiterTruszczynski11

Gerard Brewka & Thomas Eiter & Miroslav Truszczynski
Answer set programming at a glance
Commun ACM V54n12(Dec 2011)93-103 [ 2043174.2043195 ]
=ADVERT DEFEASIBLE LOGIC DECLARATIVE PROGRAMMING ASP GROUNDERS SATISFY SAT SEMANTICS TOOLS APPLICATIONS ABBREVIATIONS
a <- b1,...,bm, not c1, ..., not cm. where a,b,c... are "predicates'.
Answer set is a set of predicates that can be derived if we assume certain predicates are true/false and is not contradicted by the derivable predicates.
Able to express if-then-else and constraints easily and a number of other formulas that appear in practice.
Can handle predicates that contain variables by reducing them.

BriandBunseDaly01

Lionel C Briand & Christian Bunse & John W Daly
A controlled Experiment for Evaluating Quality Guidelines on The Maintainability of Object-Oriented Designs
IEEE Trans Software Engineering V27n6(Jun 2001)pp513-530
=EXPERIMENT MODULE DESIGN MAINTAINABILITY QUALITIES Coad Yourdon
33 students attempt to understand two different designs -- one set up to be bad and the other good. The students did bette r on the good.
Good had low coupling, high cohesion, higher clarity/lower fuzziness/simplicity, more realistic inheritance.

BriandDalyWust99

Lionel C Briand & John W Daly & J"urgen K W"ust
A Unified Framework for Coupling Measurement in Object-Oriented Systems
IEEE Trans SoftEng V25n1(Jan/Feb 1999)pp91-121
=THEORY METRICS

BriandDebanbuMelo97

Lionel C Briand & P Devanbu & W Melo
An Investigation into Coupling Measures for C++
[ICSE'97]
=EXPERIMENT OBJECT-ORIENTED METRIC

BriandEtal99a

Lionel C Briand & J"urgen W"ust & John W Daly
A Unified framework for coupling measurement in Object-Oriented Systems
IEEE Trans Softw Eng VSE-25n1(Jan/Feb 1999)pp91-121 CR9910-0775
=SURVEY EMPIRICAL TECHNICAL QUALITY OBJECT-ORIENETED METRIC COUPLING MODULE

BriandEtal99b

Lionel C Briand & J"urgen W"ust & Stefan V Ikonomovski & Hakim Lounis
Investigating Quality Factors in Object-Oriented Designs: an Industrial Case Study
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp345-354
=EMPIRICAL QUALITY OBJECT-ORIENETD METRIC
LALO and UMD Principal Components Logistic Regression
Better than [BenlarbiMelo99]
Only 7 principal components account for variation in all the 30+metrics.
The metrics are related to fault proneness...
High numbers of method calls indicates fault prone classes.
Differences between LALO and UMD -- friends not found in UMD. UMD more experienced pALO and UMD -- friends not found in UMD. UMD more experienced people.

BriandMorascaBasili99

Lionel C Briand & Sandro Morasca & Victor R Basili
Ddefining and Validating Measures or Object-Based High-Level Design
IEEE Trans Soft Eng V25n5(Sep/Oct 1999)pp722-743
=EMPIRICAL DESIGN METRICS GQM OBJECT-BASED ADA FAULT-PRONE
NASA Goddard 3 projects
declared high-level links in package interfaces
is_component_of, uses, data declaration interaction(dependency), data subroutine interaction, generics?
->cohesion, coupling
change requests -> faults and modules
logistic regression using maximum likelihood
avg-depth +number imported parts+low cohesion has some effect increasing chance of a fault being reported

BriandMaloWust02

Lionel C Briand & Walcelio L Malo & J"urgen W"urst
Assessing the Applicability of Fault-Proneness Models Across Object-Oriented Software Projects
IEEE Trans Software Engineering V28n7(Jul 2002)pp706-720
=EXPERIMENT METRICS Object-Oriented ERRORS MARS logistic JAVA
MARS::="Multivariate Adaptive Regression Splines".
Can predictions that work well on one project be used on a different one? In this case: yes. Same team and language with different managers and projects.
Inheritance trees where short in both projects.

BriandMorascaBasili02

Lionel Briand & Sandro Morasca & Victor R Basili
An Operational process for goal-driven definition of Measures
IEEE Trans Software Engineering V28n12(Dec 2003)pp1106-1125
=EXPERIENCE GQM/MEDEA METRIC DEFINITION QUALITIES DFDs UML TRIO+

BriandWust01

Lionel C Briand & J"urgen W"urst
Modeling Development Effort in Object-Oriented Systems using Design Properties
IEEE Trans Software Engineering V27n11(Nov 2001)pp963-986
=ANALYSIS EXPERIENCE EFFORT SIZE C++ METRICS LIOO
Interface sizes (NMIMP, NMINH, NA, NM) are a good predictor of the effort needed to implement a class.
Used regression trees and poisson regression work well.
Measures of coupling and cohesion do not increase accuracy of estimates.
?? inherited methods and few implemented methods lower effort.

BriandEtal05

Lionel C Briand & Yvan Labiche & Massimiliano Di Penta & Han (Daphne) Yan-Bondoc
An experimental investigation of formality in UML-based Development
IEEE Trans Software Engineering V31n10(Oct 2005)pp833-849
=EXPERIMENT OCL UML COMPREHENSION INSPECTION EVOLUTION MAINTENANCE
OCL improves comprehension, defect detection, maitenance of UML models of software by small ammounts depending on the OCL experience of the students.

BriandLabicheLeduc06

Lionel C Briand & Yvan Labiche & Johanne Leduc
Toward the Reverse Engineering of UML Sequence Diagrams for distributed Java Software
IEEE Trans Software Engineering V32n9(Sep 2006)pp642-663
=DEMO MAINTENANCE DYNAMIC TOOL NONSEQUENTIAL REVERSE JAVA UML
Uses aspects to instrument distributed software and so log the calls between objects.
Recognises conditions and so one sideof alt constructions (only).

Briggs93

Albert W Briggs Jr
Mathematics for Liberal Arts Students
American Math Monthly V100n2(Feb 1993)pp162-166
education analysis skills proof
1. "1. to raise questions and make conjectures[...]
2. 2. to test those conjectures
3. 3. to settle definitely those questions and conjectures, or at least make progress toward such a settlement,
4. 4. to raise more questions as a result of this process,
5. 5. to read with enough precision to understand the questions and investigations of others,
6. 6. to write with enough precision to communicate their investigations to others."
7. "[...] students take to forming guesses and testing them with examples like ducks to water. But getting them to prove their guesses, or to deduce things from their guesses[...]is killingly hard. It is so hard that I have to wonder whether deduction[...] is as natural a human tendency as we[mathematicians] suppose."

Brin98

David Brin
The Transparent Society...
Addison-Wesley1998 ISBN 0-201-32802-X
=HISTORY =ESSAY SOCIETY ETHICS PRIVACY RISKS NET/WWW CRYPTOGRAPHY SSN VIDEO
Argues that often more information is better than less.
Adding a reverse flow is a way to solve a problem with an assymetric flow.
Most solutions are partial.
Secrecy that decreases accountability is bad for a society. Security, safety, & ideas can be improved by open information flows and criticism.
Drops many names. Discusses opposing positions.
Notes confusion between passwords and IDs. Example: SSN is an ID used by many systems as a password.

BrinchHansen81

Per Brinch-Hansen
The EDISON Papers
Software - Practice and Experience V11n4 (Apr 1981) QV [BrinchHansen83]
=DEMO DDD data languages optimization non-sequential EDISON BNF

BrinchHansen83

Per Brinch-Hansen
Programming a Personal Computer
Prentice Hall International 1983 QV [BrinchHansen81]
=DEMO DDD data languages optimization non-sequential EDISON BNF

BrinchHansen85

Per Brinch-Hansen
On Pascal Compilers
Prentice Hall International
=SURVEY DDD

BrinchHansen99

Per Brinch Hansen
Java's Insecure Parallelism
ACM SIGPLAN Notes V34n4(Apr 1999)pp38-45
=ESSAY JAVA TECHNICAL NON_SEQUENTIAL RISKS
Need to have all variables are private and all public methods synchronized to get predicatable parallelism.
Note. Also see [Hartley99]

Britcher96

Bob Britcher
A Few (proposed) fundamental laws of programming
IEEE Computer Magazine V29N3(Mar 1996)p136(Open channel)
1. In programming major changes in the product can occur in an instant
2. vs time to change plant or physical products
  The Law of Fallibility
3. The most careful reasoning about a simple sentence can lead to a wrong conclusion about the real world
4. Programmers have to reduce big "word-problems" to logic.
  The Law of Intellectual Gravity
5. Programs can be as massive(in there own way) as physical objcts.
  The Law of Permannence
6. Programs do not become extinct. They are not discarded, they are piled up, combined, absorbed, breeding and spreading.

Brittan80

Design for a Changing Environment
Comp Jnl v23 n1 pp13-19
=DEMO maintenance formal ENGINEERING lifecycle

BrockHunt99

Bishop C Brock & Warren A Hunt Jr
Formal Analysis of the Motorola CAP DSP
In [HincheyBowen99] pp-
=EXPERIENCE HARDWARE DESIGN V&V VERIFICATION FORMAL LOGIC TOOL ACL2

Brodaetal94

Broda & Eisenbach & Khoshnevisan & Steve Vickers<sjv@doc.ic.ac.uk>
Reasoned Programming
Prentice Hall Englewood Cliffs NJ 1994 $40 ISBN 0-13-098831-6 CR9607-0469:
=TEXT Formal miranda modular-2

Brodine06

Dick Brodine
Mathematical Server Sizing
IEEE Computer Magazine V39n7(Jul 2006)pp91-93
=ADVERT MATH QUEUING THEORY WEB/NET Trivedi
Quotes a useful formulas modeling server performance.
TRIVEDI::=following
Net
1. Kishor S Trivedi's model for M clients at rate λ to a server that handles them at rate μ -- both with exponential distributions.
2. E[Response_time] = M/E[T] - 1/λ),
3. E[T]=μ *(1-p0),
4. p0:=P[0 requestss in system],
5. p0=1/(+[n:0..M]((λ/μ)^n)*(fact(M)/fact(M-n)))
(End of Net)
Shows a screen short of a Java application that helps.

BrolundElnestam11

Daniel Brolund & Ola Ellnestam
Code Pick-up Sticks
IEEE Software Magazine V28n4(Jul/Aug 2011)pp11-14
=ANECDOTE EVOLUTION REFACTORING MAINTENANCE
How to change a large badly structured code base?
1. Document problems on a whiteboard.
2. Pick an independent piece.
3. Change and try to compile.
4. If fails revert and record what you have learned. Try a different change.
5. Repeat.

Brooks77

Frederick P Brooks Jr
The Computer "Scientist" as Toolsmith -- Studies in Interactive Computer Graphics
Proc IFIP 77 (North Holland Pub Co 1977) pp625-634 (Invited Paper)
=EXPERIENCE 10years USER ENGINEERING REQUIREMENTS
p634:

Brooks82

Frederick P Brooks Jr
The Mythical Man-Month - essays on software engineering
Addison-Wesley Ma and CA USA 1982
=survey costs PEOPLE

Brooks87

Frederick P Brooks Jr
No Silver Bullets
IEEE Computer Magazine V20n4(April 1987) IEEE Press.
=survey costs
Predicts no great reduction in the costs of developing software.
But
1. See [Cox90a] [Harel92] [FraserManci08]
(Close But )

Brooks95

Frederick P Brooks Jr
The Mythical Man-Month: Anniversary Edition
Addison-Wesley Publishing Co Inc 1995
Parts from Chapter 19 in pp57-60 IEEE Software Magazine (Sep 1995)
Also speech at the ICSE 17
=HISTORY PEOPLE COSTS MS-PROCESS
[Keuffel95b]
1. waterfall process is wrong. Early functinal prototype and incremental build are ways to GROW software -
2. better to be wrong than vague. User distributions.
3. design for evolution/family of products from the start(Parnas)
4. peopleware empowerment. "the power of giving up power" in IBM and in MS
  [McCarthyJ95a] MS Process: Jim McCarthy of Microsoft power of teams owning a set of features and controlling define+biuld+ship. 4..5 specialities: testing, writing, building. Settle own squabbles. Effect not reported.
5. encapsulation is OK - I was wrong and Parnas right
6. Brooks law: Boehm, Abdel-Hamid Madnick [Abdel-Hamid96]
7. Computers brought Fluidity to ...drawings, plans, ...texts, ...spreadsheets
8. Metaprogramming: hypercard... pre-VBX!

Brooks96

Frederick P Brooks Jr
The Computer scientist as Toolsmith II
Comm ACM V39n3(Mar 1996)pp61-68
science & Engineering

Brooks10

Frederick P Brooks Jr
The Design of Design: Essays from a computer scientist
Addison-Wesley Prof. Boston MA 2010 ISBN 02011362988 CR 1103-0278
=UNREAD =ESSAYS DESIGN

BrooksD08

David A brooks
An Introduction to HTML and JavaScript for Scientists and Engineers
Springer-Verlag Secaucus NJ ISBN 1846386565 CR 0810-0929
=UNREAD =TEXT =REFERENCE INTRODUCTION HTML JAVASCRIPT CSS
Notes [click here if you can fill this hole]

Brown83

?? Brown
Error Messages: The neglected area of the man-machine interface?
Commun ACM 26 4 pp246-249
=IDEA USER ERRORS

Brough01

Mike Brough
The History of YSM
[ ysmhist.pdf ]
=HISTORY METHODS YSM Yourdon

Brownbridge90

David Brownbridge(drb@paxis.co.uk)
Using Z to Develop a CASE Toolset
pp142-149 in Nicholls90
=EXPERIENCE SSADM Z CASE
340 pages of Z -> 37KLOC object-oriented in 11 months
no need of refinement
needed for typechecker
formal specification reviews are needed
needed roadmap of hierarchy

BrownChervanyReinicke07

Susan A Brown & Norman L Chervany & Bryan A Reinicke
What matters when introducing new information technology
Commun ACM V50n9(Sep 2007)pp91-96
=SURVEY IMPLEMENTATION ISSUES =EXPERIENCE
Surveyed the literature and made list of 5 areas: Commitment, Knowledge, Communication, Planning, Infrastructure.
Took 5 projects and looked for occurences of "disconnects": Commitment(59), Knowledge(18), Communication(53), Planning(25), Infrastructure(30).
Figure 2 show relative frequency accross 4 phases: Initiation(Knowledge), Adoption(Communications), Adaption(Infrastructure), Acceptance(Infrastructure+Commitment).
Table 3 lists 6 problems, identifies a area and suggests solutions. For example: If you can't identify the best new technology you have a Knowledge problem -- invest in employee education and create a central repository for sharing tech information.

BrownEarlMcDermid92

Alan W Brown & Anthony N Earl & John A McDermid
Software Engineering Environments: Automated Support for Software Engineering
McGraw-Hill NY NY 1992 ISBN 0-07-707432-7 CR9409-0606
=ADVERTS CASE TOOLS

BrownMalveauMcCormickMowbray98

William J Brown & & R C Malveau & Hays W McCormick III & T J Mowbray
AntiPattern: refactoring software, architectures, and projects in crisis
John Wiley & Sons, New York NY(1999) ISBN 0-471-32929-0 CR9908-0593
=PATTERNS ARCHITECTURE DESIGN REFACTOR EVOLUTION
BallOfMud := "one class becomes responsible for everything that doesn't fit elsewhere."

BrownMcCormickThomas99

William J Brown & Hays W McCormick III & Scott H Thomas
AntiPattern and Patterns in Software configuration management
John Wiley & Sons, New York NY(1999) ISBN 0-471-32929-0 CR9908-0593
=PATTERNS SCM

BrowneMenon04

Glen J Browne & Nirup M Menon
Network Effects & social dilemmas in Technology Industries
IEEE Software Magazine V21n5(Sep /Oct 2004)pp44-50
=Theory Markets Economics

BrowneMoore97

Shirley V Browne & James W Moore
Reuse Library Interoperability
[Harandi97] pp182-189
=ADVERT RIG WEB/NET REUSE URNs DATA MODEL RIG=http://www.rig.org.

BrownN96

Norm Brown
Industrial-Strength Management Strategies
IEEE Software Magazine VSE13N4(Jul 1996)pp94-103
=SURVEY people DoD managers list
9 best practices::=risk management & agreeed interfaces & formal inspections(not reviews) & metics & defect tracking & quality gates on tiny steps & configuration management & visible control panel & people aware accountability

BrownP91

Patrick Brown
Integrated hypertext and program understanding tools
IBM Syst J V30n3(1991)pp363-392
=TOOL TECHNICAL
CR 9211-0872(N Zvegintov)
1. TRAILS::= prototype hypertext tool
  linking program data - HIPO | lexical afinity |Data model attributes
  p389: "Lost in Hyperspace" - "loosing track of what they are looking at or how they got there"

BrownShipmanVetter07

Jeff Brown & Bill Shipman & Ron Vetter
SMS: The Short Messaging Service
IEEE Computer Magazine V40n12(Dec 2007)pp106-110
=STANDARD SMS PROTOCOL CELL MOBILE PHONE Shortcodes WAP EMAIL
SMS::protocol="Short Message Service", not just for teenagers, also connects to the web and EMail.

BrownswordOberndorfSledge00

Lisa Brownsword & Tricia Oberndorf & Carol A Sledge (SEI)
Developing new processes for COTS bases systems
IEEE Software Magazine V17n3(Jul/Aug 2000)pp48-55
=IDEA PROCESS COMPONENTS COTS
CBS:="COTS based system", COTS:="commercial off the shelf".
Requirements, marketplce, and architecture/design are defined and tradedog at once. cf [Boehm00?]
engineering+business+project areas.
architecture is only assett youown and so is strategic and must beflexible.

Broy93

Manfred Broy
Functional Specifications of time-sensitive Communicating systems
ACM Trans Softw Eng Methodol V2n1(Jan 1993)pp1-46 CR9311-0858
=THEORY PURPOSE NON_SEQUENTIAL
(dick)|-Contacted Manfred by Email about a typo. Archive on Wiley. Copy in Office.

Broy01

Manfred Broy
Toward a Mathematical Foundation of software engineering Methods
IEEE Trans Software Engineering V27n11(Jan 2001)pp42-57 CR0102-0065
=THEORY METHODS ALGEBRA DIGRAPH FSM/STD DFDs ADT ERD SEQUENCE DATA
Not object oriented.

Broy11

Manfred Broy
Can Practitioners neglect theory and theoreticians Neglect practice?
IEEE Computer V44n10(Oct 2011)pp19-24
=ESSAY GAP THEORY ENGINEERING
Theory should help establish terminology, techniques, and measurements. Practicioners have provided good ideas but where is the scientific tests of these theories?
Craft, Science, or Engineering?
Theory should help organize knowledge -- both domain and technical knowledge
A method/methodology may not have an explicit theory and probably: does not scle, is too difficult, not well designed, and not cost-effective.
Theory should be part of a software enginmeers education: operating systems, data bases, protocols, formal languages, semantics,... informatics, sociology,...
Theory in research: based on empirical data, isolated, vs ad hoc methods.
We do not need beautiful theories -- we need to solve particular problems.
Other forms of engineering a based on separate sciences... software engineering depends on logics and theories of information and computation.

BroyNelson89

Manfred Broy & Greg Nelson
Can fair choice be added to Dijkstra's calculus
Report 38 (Feb 1989) from Digital Equipment Corpn Systems Research Center Palo Alto CA 94301
=THEORY guarded-commands
see BroyNelson94

BroyNelson94

Manfred Broy & Greg Nelson
Adding fair choice to Dijkstra's calculus
ACM Trans Program Lang Syst V16n3(May 1994)pp924-938 CR9508-0601
=THEORY guarded-commands
see BroyNelson89

Brun-ColtonWall95

Francoise Brun-Colton & Patricia Wall
Using Video to Re-Present the User
Commun ACM V38n5(May 1995)pp61-71
=EXPERIENCE USER VIDEO DOCUMENTATION

BrunsChandra03

Glenn Bruns & Satish Chandra
Searching for Points-To Analysis
IEEE Trans Software Engineering V29n10(Oct 2003)pp883-897
=ALGORITHMS POINTERS CODE DATA LTS CFG SEMANTICS REACHABILITY

Brunner75

John Brunner
The Shockwave Rider
Harper & Row 1975 ISBN 0-060-10559-3
=NOVEL SF NETWORK WORMS PREDICTION MARKETS TARNOVER TOFFLER
Wikipedia [ The_Shockwave_Rider ]
Review 1976 [ 1095302.1095305 ]

BruntinkDeursenEngelenTourwe05

Magiel Bruntink & Arie van Deursen & Remco van Engelen & Tom Tourwh One the use of clone detection for identifying crosscutting concern code
IEEE Trans Software Engineering V31n10(Oct 2005)pp801-818
=CASE STUDY CODE C ASPECTS TOOLS Clone ccdiml CCFinder Komondor's PDG-DUP
Tools can find many examples of duplicated code for common tasks (eg. testing for NULL).
But if set to find more they become imprecise and retrieve irrelevant code.
Humans do better.
Only Concerns relevant to weaknesses in C considered. Memory, null pointers, r ange checking, error handling, & tracing calls.

Bryant90

Tony Bryant
Structured methodologies and formal notations: Developing a framework for synthesis and investigation
pp229-241 in Nicholls90
=THEORY Z SSADM DEF STAN 0055

BrylowPalsberg04

Dennis Brylow & Jens Palsberg
Deadline Analysis of Interrupt-Driven Software
IEEE Trans Software Engineering V30n10(Sep 2004)pp634-655
=DEMO Formal TIMING Z86 Interrupt Handling TEST

Buccietal94

Paolo Bucci & Joseph E Holingsworth & Joan Krone & Bruce W Weide
Implementing Components in RESOLVE
ACM SIGSOFT Software Engineering Notes V19n4(Oct 1994)pp29-39 See Sitaraman94
=IDEA ARCHITECTURE RESOLVE

BucciHeymLongWeide02

Paolo Bucci & Wayne Heym & Timothy J Long & Bruce W Weide
Algorithms and Object-Oriented Programming: Bridging the Gap
SIGCSE'02 Proceeding & ACM SIGCSE Bulletin V34n1(Mar 2002)pp302-306
=EXAMPLE ALGORITHM SORTING MACHINES Object-Oriented DESIGN
describe principles: hide data representation, hide implementation, hide when things are done, expose mathematical state abstraction (lies), expose precise pre/post conditions for operations in interface.
A sorting machine has a phase and a bag of items it can insert objects, change phase and then remove objects in a different order.
Table with 6 implementations: insertion, selection, quick. merge, heap, tree.

Buchanan11

Mark Buchanan
The Cassandra Factor
New Scientist V209n2797 (Jan 29 2011)pp36-39
=ADVERT =EXAMPLES DYNAMIC SYSTEM MODEL ODEs SLOW RECOVERY CRITICAL POINT TIPPING POINT PHASE CHANGE
Long before a system is about to change phase it starts to recover more slowly from disturbances.

Buchi02

J R Buchi
On a Decision Method in Restricted second-order arithmetics
Proc Int'l Conf. Logic, Methods and philosophy of science (1962) pp1-12
=THEORY AUTOMATA omega-automata Buchi-automata
Given a standard finite state automata with accepting states its language is defines a set of infinite strings that are acceptable: they can return an infinite number of times to at least on of the accepting states.

BuchsGuelfi00

Didier Buchs & Nicolas Guelfi
A Formal Specification Framework for Object-Oriented Distributed Systems
IEEE Trans Software Engineering V26n7(Jul 2000)pp630-652
=DEMO FORMAL SPECIFICATION DISTRIBUTED OBJECT_ORIENTED PETRI-NETS CO-OPN/2 based on COOPN COIL
transit node TNode example

Bucken93

Mike Bucken
Field Report: OO Methods Vie for Recognition
Software Magazine(May 1993) pp25-26
=REPORT Methods Object-oriented CASE
7 competing methods
none complete(object class relationship attributes messages inheritance) but evolving to include
CASE vendors doubtful

Buckley93

Fletcher F Buckley<f.buckley@compmail.com>
Defining Software Engineering as a Profession
IEEE Computer Magazine(Aug 1993) pp76-78

BuckleySilberschatz83

An Effective Implementation for the Generalized Input-Output Construct of CSP
ACM TOPLAS V5n2(April 1983)pp223-235
=DEMO optimization non-sequential

Budd87

Timothy Budd<budd@fog.cs.orst.edu>
A Little Smalltalk
Addison Wesley 1987
=TOOL
Source code: anonymous FTP to cs.orst.edu
get pub/budd/small.v3

Budd94

Timothy A. Budd<budd@cs.orst.edu>
Classic Data Structures in C++
ISBN 0-201-50889-3 QA76.73.C153B83(1994) BNB 93-21664 Dewey 005.7'3
=TEXT source code <mail :almanac@cs.orst.edu>
1. pronnounceable, words visible, few meanings, no digits, Booleans should identify the true condition, take care with infrequent and/or costly reuse via composition and inheritance
  Top down SWR:
  1. sequence, selection, parts
  2. find common

Budgen94

David Budgen<db@cs.keele.ac.uk>
Software Design
Addison-Wesley Publishing Company 1995 ISBN 0-201-54403-2
=TEXT =SURVEY METHODS

Budgen99

David Budgen
Software Design Methods: Life Belt or Leg Iron?
IEEE Software Magazine V16n5(Sep/Oct 1999)pp136+134-135
=ESSAY DESIGN METHODS
Real designers are oportunistic and modify the methods they are taught.

BudgenRigby07

David Budgen & Michael Rigby & Pearl Brereton & Mark Turner
A Data Integration Broker for Healthcar Systems
IEEE Computer Magazine V40n4(Apr 2007)pp34-41
=ADVERT SERVICE DATA HEALTHCARE IBHIS ONTOLOGY SEMANTICS UK

Buhr95

Peter A Buhr
Are Safe Concurrancy Libraries Possible?
Commun ACM V38n2(Feb 1995)pp117-120
=EXPERIENCE NONSEQUENTIAL RISKS of adding libraries to sequential LANGUAGES

Buhr98

R J A Buhr
Use Case Maps as Architectural Enitites for Complex Systems
IEEE Trans SE V24n12(Dec 1998)pp1131-1155 CR9908-0630
=DEMO GRAPHIC [UCM]
Collaborations as path thru responsibillities of components: forks and joins, and/or, rendezvous, time, stubs, plugins, component stacks, dynamic stub, movements
UCM::graphic_noatation="Use Case Map". Syntax at [ agents ]

BuhrCasselman96

R J Buhr & R S Casselman
Use Case Maps for Object-oriented Systems
Prentice Hall Int NJ 1996 ISBN 0-13-456542-8 [CR] 9705-0315 D.1.5
=TEXT GRAPHIC [UCM]
Structured prose descriptions of interactions: scenarios between a system to be designed and the users of the system

BuhrFortierCoffin95

Peter A Buhr & Michel Fortier & Michael H Coffin
Monitor Classification
ACM Computing Surveys V27n1(Mar 1995)pp64-107
=SURVEY nonsequential

Bullard92

L Bullard
Applying frame based SGML to enterprise engineering
<TAG> V5n7(Jul 1992)
=DEMO SGML

Burge91

T Burge
Truth and Singular Terms
in Philosophical Applications of Free Logic Oxford Univ Press 1991 pp 189-204
=THEORY FORMAL LOGIC
See [LPT]
and [LPV]

BurgeBrown07

Janet E Burge & David C Brown
Software Engineering Using RATionale
Journal of Systems and Software V81n3(2008)pp 395-413 CR 0906-0559
=EXPERIMENT =DEMO TOOL REQUIREMENTS DESIGN RATIONALE IDE SEURAT Eclipse Java RATspeak inference
Faster maintenance for nonexperts (only)
Who were the subjects?
What is cost of capturing the rationale?

Burgess91

Angela Burgess (Ed)
Phone Outages Blamed on Switching Software
IEEE Software V8n5(Sept 1991)pp100-101
=EXPERIENCE RISKS

Burns00

David Burns
The Mental Game of Debugging
Software Development Magazine V8n3(Nov/Dec 2000)pp44-48
=ESSAY ANECDOTE DEBUGGING GOOD
boast, relax, know the territory, if obscure start at the beginning, know what you don't know, seek the right tool, patient, eyes open, know what it should have been(specs can be wrong), don't patch it: fix it!

Burnsten07

Sidney L Burnsten
To map a process, first find its swimlane
Commun ACM V50n10(Oct 2007)p14
=ANECDOTE IBM SLB GRAPHIC ANALYSIS DESIGN METHOD DesignFlow
SLB::="Swim Lane Based".
Draw both "as is" and "to be" diagrams.
Involve users and stakeholders.
Each actor has a swimlane. Show activities & decisions in lanes. include information.
Claims many years of successful use.
Claims better than DFDs or Usecases.
Sounds like it is compatible with UML2.0 Activity diagrams.

BurrowsAbadiNeedham89

M Burrows & M Abadi & R M Needham
A Logic of Authentication
Proc Royal Society of London A V426(1989)pp233-271
=THEORY FORMAL LOGIC
BAN_logic::Logic, logic of authentication -- who can believe what about whom? [ BAN.html ]
See also [BurrowsAbadiNeedham90]

BurrowsAbadiNeedham90

Michael Burrows & Martin Abadi & Roger M Needham
A Logic of Authentication
ACM Transactions on Computer Systems V8n1(Feb 1990)pp18-36 [ 77648.77649 ]
=THEORY =DEMO LOGIC PROTOCOL PROOF V&V BAN KERBEROS CRYPTO
See also [BurrowsAbadiNeedham89]
Defines the [BAN_logic] of beliefs and messages.

Burridge99

Trevor Burridge
Certification in the united kingdom
IEEE Software Magazine V16n6(Nov/Dec 1999)pp46
=SIDEBAR ENGINEERING UK
UK has certified software engineers via IEE+BCS for years, no adverts for software engineers [ http://www.iee.org ] [ http://www.bcs.org.uk ] [ http://www.jobserve.com/ ]

BuschmannHenney10

Feank Buschmann & Kevlin Henney
Five Considerations for software architecture, part 2
IEEE Software Magazine V27n4(Jul/Aug 2010)pp12-14
=DEMO PATTERN IMPROVEMENT FACTORY SYMMETRY creator EMERGENCE non-sequential
Symmetry suggests that creators (for example factories) should also be responsible for destroying the objects they create.
(dick)|-why not life history objects as in JSP/JSD? [Sanden09] [Sanden03]
Emergence suggests the use of Pipes and Filters to handle work flows rather than a shared repository with hardwired transactions.
(dick)|-Pipes and filters goes back to Doug McIlroy and compiler technology and Michael A Jackson's methods for Data Processing.

BuseWeimer10

Raymond P L Buse & Westley R Weiner
Learning a metric for code readability
IEEE Trans Software Engineering V36n4(Jul/Aug 2010)pp546-558
=EXPERIMENT READABILITY 120 ANNOTATORS FIT FEATURES METRICS CHANGES DEFECTS CODE QUALITIES sourceforge
Annotators were students at U o Virginia.
Can construct a metric that predict readability with 80% reliability.
Same metric predicts the number of defect reports, changes, & defect log messages.
Two dozen factors. High scoring metrics: avg number of identifiers, avg line length, avg number of parentheses, number of periods, avg indenting, etc.
The number of comments, blank lines have a negative effect.

Bussler07

Chistoph Bussler
The Fractal Nature of Web Services
IEEE Computer Magazine V40n3(Mar 2007)pp93-95
=HARMFUL NAIVE SERVICE SOA PERFORMANCE QUEUES
A new silver bullet: Service-oriented Architecture.
If everything is a service and can be called by any other service then performance will be unstable.
Example: Simple request and reply leads 14 messages, 24 remote invocations, and 4 distributed transactions.
Need to think about what should be offered as a service....

BustardWinstanley94

David W Bustard & Adam C Winstanley
Making changes to Formal Specifications: Requirements and an Example
IEEE trans on Soft Eng vSE-20n8(Aug 1994)pp562-568
=DEMO SCAFFOLD FORMAL MAINTENANCE LOTOS Dynamics

ButlerEspositoHebron99

Keith A Butler & Chris Esposito & Ron Hebron
Connecting the Design of Software to the Design of Work
Commun ACM V42n1(Jan 1999)pp38-46
=ADVERT SYSTEM USER should drive design

ButlerHope02

Samantha Butler & Sian Hope
Software Process Evaluation using remote monitoring methods
[SCI2002] V1(Jul 2002)pp
=EXPERIENCE IMPROVEMENT MEASUREMENT metrics

Butov05

Andrey Butov
XML-Binary optimized packaging
Dr. Dobbs #379(Dec 2005)pp53-55
=ESSAY CODE Binary XML XOP
How to embed binary data in XML?

CACM25

Reprints
Special 25th Anniversary Issue
Commun ACM V26 n1 (Jan 1983)
history

CR

Various reviewers
Computer Reviews
ACM Press NY NY,
see [ home.cfm ]
=COLLECTION REVIEWS HISTORY
=JOURNAL REVIEWS
Each review is numbered YYMM-nnnn where YY indicates the year, MM the month, and nn is a serial number.
[CR] also provides a classification of subjects for each item -- CCS. For example D.2.1 is for Requirements/Specifications

CWE10

Steve Christie (Ed) [ cwe@mitre.com ]
CWE - 2010 CWE/SANS Top 25 Most Dangerous Programming Errors
MITRE/SANS [ http://cwe.mitre.org/top25/ ]
=POLL ERRORS SECURITY WEB/NET
Several categorized lists of error types: Cross-site scripting. SQL injection, Classic Buffer overflow, ...

CabotOliveTeniente03

Jordi Cabot & Antoni Olive & Ernest Teniente
Representing Temporal Information in the UML
LNCS 2863 <<UML>> 2003 -- The Unified Modeling Language Oct 2003, pp44-59
=IDEA UML/OCL TEMPORAL ER MODEL TOOL XML XMI XSL
Ls:=life span of the system.
E(e,t) :=e is an instance of type E at time t.
R(e1,e2,...,t) :=(e1,e2,...) participate in relation R at time t
Ci(e,E) :=all classification intervals of e in E
Intervals have properties like BelongsTo, endsAt, ...
Classification by frequency and durability. Therefore temporal stereotypes.
Historical entities/relations hold the history of entities via <<timestamp>>

Cahoon06

Jeff Cahoon
Faster Development Through Modeling
Dr. Dobb's Journal (Oct 05, 2006) Link: [ 193104822 ]
=TYPE MODEL RAPID PROTOTYPE GENERATION MDA
"Jeff describes a modeling technique that uses free tools and Model-Driven Architecture processes to speed up development."
Method
1. Create a model of the application.
2. Write a miniapplication that implements the first instance of the repeated set of steps.
3. Pull apart the miniapplication into template files replacing the named parts in the repeated set of steps with recognizable strings for substitution.
4. Write code that can rebuild the miniapplication from the templates and the model.
5. Generate all the code for the whole application.
(dick)|-model=horrible diagram.

Caietal91

Jiazhen Cai & P Facon & F Henglein & Robert Paige & E Schonberg
Type Analysis and Data Structure Selection
in Constructing Programs from Specifications B. Moeller ed. North_Holland 1991

CaiPaige93

Jiazhen Cai & Robert Paige
Towards Increased Productivity of Algorithm Implementation [Notkin93] pp 71-77
=DEMO SETL2 Data Engineering
Claims a 5 to 9 fold improvement in productivity by repetedly refining SETL2->SQ2->C. Giving 1.5 faster code than FORTRAN.
States that SETL optimizations were never very effective because of the hardwired hash table implementations of data structures.

Calan89

Frank Calan
The Quality System: A Source Book for Management and Engineers (2nd Edn)
Chilton Book Co. Radnor PA 1989
=TEXT QUALITY

CalcagnoOHearnBornat03

C Calcagno & P OHearn & R Bornat
Program logic and equivalence in the presence of garbage collection
Theoretical Computer Science V298n3(??? 2003)pp557-581
=THEORY FORMAL LOGIC HOARE Garbage Collection (D.4.2) VERIFICATION
What do we mean when we say that a particular object "exists" on the heap? To preserve Hoare's assignment axiom in the presence of garbage collection, the existence of garbage becomes "virtual".
The wise program prover should use a language with proved automatic garbage collection, and avoid assertions that refer to garbage!
Includes a formal model of garbage collection.

Calchera95

Gini Calchera(DFAS)
Assessing a System Before Re-engineering it: What a Novel Idea
IEEE Reverse Engineering Newsletter n8(Winter 1995)pp6-9

Caldieraetal91

Gianluigi Caldiera & Victor R. Basili
Identifying and Qualifying Reusable Software Components
IEEE Computer V24n2(Feb 1991)
Parallel SW process.

CallaghanHirschmuller98

Michael Callaghan & Heiko Hirschm"uller
3-D Visualisation of Design Patterns and Java Programs in Computer Science Education
ACM SICSE Conf Proc 6th Annual Conf on the Teching of Computing SIGCSE Bulletin V30n3(Sep 1998)pp37-40
=DEMO GRAPHIC 3D VRML TOOL JAVA WWW SVL VISP
See [ ~kira ] but compare with [FiejsJong98]

Callison95

H Rebecca Callison(mailto:callison@research.cs.orst.edu)
A Time-sensitive Object Model for Real-time Systems
ACM Trans Softw Eng Methodol V4n3(Jul 1995)pp287-317
TSO::=Time Sensitive Object.

CalloniBagert94

Ben A Calloni<BGBAC@TTACSI.TTU.EDU> & Donald J Bagert<BEDJB@TTACSI.TTU.EDU>
Iconic Programming in BACCI Vs Textual Programming: Which is a Better Learning Environment?
ACM 25th Technical Symposium on Computer Science Education SIGCSE Bulletin V26n1(Mar 1994)pp

CalvettiSomersalo2007

Daniela Calvetti & Erkki Somersalo
Introduction to Baresian Scientific Computing: Ten lectures on subjective computing
Springer-Verlag NY Secaucus NY 2005 ISBN 0387733930 CR 0811-1048
=UNREAD LECTURES BAYES PROBABILITY THEORY PHILOSOPHY

Cameron84

John R Cameron
JSP & JSD: The Jackson Approach to Software Development
IEEE Tutorial Cat No EH0206-3 IEEE Computer Society LA Order No 516
=HOWTO METHODS DDD DAD Reality System

Cameron86

John R Cameron
An overview of JSD
See [BerglandZave86] pp222-240
=ADVERT METHODS DAD Reality

Cameron89

John R Cameron
JSP and JSD: The Jackson Approach to Software development(2nd Edn)
IEEE Comp Society Press CA 1989
=HOWTO METHODS DDD DAD Reality System

Cameron02

John Cameron
Configurable Development Processes
Commun ACM V45n2(Mar 2002)pp72-77
=ADVERT WPD PROCESS PRODUCT DESCRIPTION META IBM EXPERIENCE
WPD::="Work Product Description".
About 100 WPDs plus dependency diagrams, work breakdown structures (rough plans/checkpoints), Roles/skill-sets linked to products and parts of plans, details of complex techniques.
Easier to describe products rather than processes.
Capturing intellectual capital.
Rigid processes do not work when applied uniformly. They always fail. However work products can be transplanted with success.
Configuration: selecting products using spreadsheet ad advice from WPDs. If a product is adopted then the WPD contains or refers to information for producing and using the product.
Products evolve over time to a finished from.

CameronR93

Robert D Cameron
Extending contect free grammers with permutation phreases
ACM Lett Program Lang Syst V2n1-4(March-Dec 1993)pp85-94
CR9412-0877

Camilleri90

Albert John Camilleri
Mechanizing CSP Trace Theory in Higher Order Logic
IEEE Trans Software Engineering SE-V16n9(Sep 1990)

Camp01

L Jean Camp
An atomicity-Generating Protocol for anonymous Currencies
IEEE Trans Software Engineering V27n3(Mar 2001)pp272-278
=EXAMPLE THEORY ECommerce NONSEQUENTIAL

Campbell-Kelly03

Martin Campbell-Kelly
From Airline reservations to Sonic the Hedgehog: A History of the Software Industry
MIT Press ISBN 0-262-03303-8 $29.95,
Review IEEE Computer Magazine V36n6(Jun 2003)pp78- [CR] 0308-0762
=HISTORY SOFTWARE ECONOMICS
Three main sectors: contractors, makers of corporate software, producers for the mass market.
Many diverse products and markets.

Campbell-Kelly08

Martin Campbell-Kelly
Historical Reflections -- Will the future of software be open source
Commun ACM V51n10(Oct 2008)pp21-23 [ 1400181.1400189 ]
=HISTORY 1950s-2000s OPEN SOURCE F/OSS
Initially source code was distributed with the executables and libraries.
Unsuspected technologies have and will disrupt predictions.

Campbell-Kelly10

Martin Campbell-Kelly
Be careful what you wish for
Commun ACM V53n4(Apr 2010)pp25-26 [ 1721654.1721666 ]
=HISTORY TABLES Napier Briggs Babbage Mauchly Eckert
the history of mathematical tables.
Babbage got into computing devices to print tables so the whole of Information and Computer Technology is an unintended side-effect of a limited initial project.
Later the computer made the mass production of accurate and useful tables possible just when computers started to make mathematicsl tables obsolete.

Campbell-Kelly10b

Martin Campbell-Kelly
Historical Reflections: Victorian Data Processing
Commun ACM V53n10(Oct 2010)pp19-21 [ 1831407.1831417 ]
=HISTORY DATA PROCESSING LOGICAL vs PHYSICAL BABBAGE CLEARING CHECKS USA CHEQUES UK
Shows an efficient solution to a problem in the form of a multi-agent procedure.
Traces the evolution of Bank Clearing Houses in the UK (as documented by Babbage) and then in the USA.
Argues that similar algorithms are still used in modern information technology.

CampbellHaberman74

R H Campbell & A N Haberman
The specification of Process Synchronisation by Path Expressions
Lecture Notes in Computer Science n16 (Apr 1974)
=THEORY REGULAR NONSEQUENTIAL
Path expressions, ref in ACM SIGSOFT Software Engineering Notes V17n4 (Oct 1992)p49&52

CamposNunes07

Pedro Campos & Nuno Jardin Nunes
Practitioner Tools and Workstyles for User-Interface Design
IEEE Software Magazine V24n1(Jan/Feb 2007)pp73-80
=POLL 300 USER INTERFACE DESIGNERS =DEMO CanonSketch MXML macromedia
Email surveys + interviews to establish how user interface designers work.
Most use manual tools: paper, pencil, whiteboards, Post-It notes.
Common transitions: problem->solution, refinement, ...
Problem->solution was perceived as the most costly one.
Examples of tools to support transitions -- drag and drop between synchronized views.
TaskSketch::= See http://dme.uma.pt/tasksketch (Mac OSX)
CannonSketch::= See http://dme.uma.pt/canonsketch

CanalEtal03

Carlos Canal & Lidia Fuentes & Ernesto Pimentel & Jose M Troya & Antonio Vallecillo
Adding Roles to CORBA Objects
IEEE Trans Software Engineering V29n3(Mar 2003)pp242-260
=CASESTUDY CORBA IDL PROTOCOL DYNAMIC SPECIFICATION π-calculus GRAMMAR ROLE TESTING MWB Java Orbix
role name( formal_arguments)= ... role_name( actual_arguments ) ...

CanevetGilmoreHillstonKloulStevens04

C Canevet & Stephen Gilmore & Jane Hillston & Leila Kloul & P Stevens
Analyzing UML2.0 activity diagrams in the Software performance engineering process
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp74-78
=DEMO TOOL performance PETRI ALGEBRA PEPA UML2 [GilmoreHillstonKloulRibaudo04]

Canforaetal92

Gerardo Canfora & Anielo Cimitile & Ugo de Carlini
A Logic-Based Approach to Reverse Engineering Tools Production
IEEE Trans on Software Eng VSE-18n12(Dec 1992)pp1053-1064

CanforaPentaCerulo11

Gerardo Canfora & Massimiliano Di Penta & Luigi Cerulo
Achievements and challenges in software reverse engineering
Comm ACM V54n4(Apr 2011)pp142-151 [ 1924421.1924451 $CR ]
=SURVEY 2000-2010 REVERSE ENGINEERING TOOLS TECHNIQUES GUI PLUGINS
Good lists and bad graphics!

CangussuDeCarloMathur02

Joao W Cangussu & Raymond A DeCarlo & Aditya P Mathur
A Formal model of the software test Process
IEEE Trans Software Engineering V28n8(Aug 2002)pp782-796
=MATH PREDICTING SOFTWARE TESTING
Splits testing into phases. Models each phase in turn.
Suggests an linear 2nd order ordinary differential equation to model the number of errors in a piece of software. Complexity is analogous to inertia, test effort is proportional to the number of errors (Volterra predator-prey model!), and that working quickly tends too slow the process(viscosity).
Derives typical curves (some of two exponential decays) and a matrix version.
Presets extreme cases and ways to estimate parameters.
Case study of Τ_ΕΧ in a Purdue Tech report.
Razorfish porting 4MLoc COBOL to SAP/R3program.

CangussuDeCarloMathur03

Joao W Cangussu & Raymond A DeCarlo & Aditya P Mathur
Monitoring the software test process using statistical process control: a Logarithmic approach
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp158-167
=THEORY STATISTICS TESTING QUALITY CONTROL
Before applying quality control to the number of defects fixed it is best to first lake logarithms to fit an exponential curve to form the expected value vs time.

Cann93

Ronnie Canne
Formal Semantics: An Introduction
Cambridge University Press New York NY 1993 ISBN 0-521-37610-6
CR9411-0776
(CR)|-Semantics of natural language, set theoretical, Lambda abstraction, generalized quantifiers, advanced text

CaoRamesh08

Lan Cao & Balasubramaniam Ramesh
Agile requirements engineering practices: an empirical study
IEEE Software Magazine V25n1(Jan/Feb 2008)pp60-
=INTERVIEWS 16 FIRMS AGILE REQUIREMENTS BENEFITS CHALLENGES PURPOSES TESTS QUALITIES
Identified 7 practices each with benefits & challenges.
1. Face-to-face communication not documents.
2. Iterating (requirements, priorities, planning, reviews, & acceptance tests).
3. Prototypes.
4. Test driven development(TDD).
challenges: forgotten qualities, wrong architecture, lack experience of TDD...

CaplanHarandi95

Joshua E Caplan & Mehdi T Harandi(*@cs.uiuc.edu)
A Logical Framework for Software Proof Reuse [SamadzadehZand95] pp106-113
=THEORY DEMO PROOF REUSE
Hoare triples do not have referential transparency!
1. for_vars x( {P(t=>x[m])} x[m]:= t {P} ). Declaration axiom:
2. for_vars x({ P and x[m]=e} C{Q})
3. ---------------------------------------------------where x=y,x[m],z.
4. for_vars y,z( {P} new x[m]:=e ; C {Q} )

CaplatSourrouille05

Guy Caplat & Jean-Louis Sourrouille
Model Mapping Using Formalism Extensions
IEEE Software Magazine V22n2(Mar/Apr 2005)pp44-51
=EXAMPLE THEORY METAMODEL TRANSLATION + EXTENSIONS MOF UML PROFILES MDA ARTO C++ PIM PSM CODE Sherlock Constraint Checker
The real problem in MDA is mapping between formalisms/languages.
Translating between different modeling formalisms is complicated because they have extensions.
Extensions are needed because translations can not be made between formalisms .
Extensions become UML profiles.
Constraint Checker is a tool that tests if a model conforms to a profile and u ses the language Sherlock.

Capperetal94

N P Capper & R J Colgate & J C Hunter & M F James
The Impact of object-oriented Technology on Software Quality: Three case histories
IBM Systems Jnl V33n1(1994)pp131-157
=CASESTUDY OBJECT-ORIENTED TECHNICAL QUALITY

Capra04

Licia Capra
Engineering Human Trust in Mobile System Collaborations
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp107-116
=THEORY MATHEMATICS TRUST AGENTS hTrust TMF
TMF::="Trust Management Framework".
Models the formation, dissemination and evolution of trust between agents.
trust_data::=Net{who_trusts, opinion, trusted, level, subject, direct_experiences, credentials, recommendations }.
Notes

CapraFrancalanciMerio08

Eugenio Capra & Chiara Francalanci & Francesco Merio
An Empirical study on the relationship among Software Design Quality, Development Effort, and Governance in Open Source Projects
IEEE Trans Software Engineering (Nov/Dec 2008)pp765-782
=EMPIRICAL ANALYSIS 75 OPEN SOURCE PROJECTS METRICS EFFORT PROCESS MANAGEMENT
In open source there is a continuum of governance practices.
Conclusion: Better quality code permits looser governance but that in turn takes effort to coordinate loosely governed people.
(dick)|-results are unlikely to happen by chance but the causality may be reversed.

CapretzAhmed01

Luiz Fernando Capretz and Faheem Ahmed Making Sense of Software Development and Personality Types IEEE IT Professional (Jan/Feb 2010)pp6-13 [ T_IT_MakingSense.pdf ]
=THEORY PERSONALITY MYERS-BRIGGS MBTI TRAITS PEOPLE PROCESS SKILLS DISCIPLINES LIFE CYCLE
Theory Different personallities are most useful at different times/jobs.
MBTI::="Myers-Briggs Type Indicator", [ reference.html#MBTI ]

Which types fits four disciplines/phases: Table 2 "The personality types with the strongest impact on the software life cycle."
Table

Personality types	System analysis	Software design	Programming	Testing	Maintenance
Extroversion (E)	x
Introversion (I)			x
Sensing (S)			x	x	x
Intuition (N)		x
Thinking (T)		x	x
Feeling (F)	x
Judging (J)				x
Perceiving (P)					x

(Close Table)

Carasiketal90

RP Carasik & SM Johnson & DA Patterson & George A Von Glahn
Towards a Domain Description Grammar: An Application of Linguistic Semantics
ACM SIGSOFT SEN V15n5(Oct 1990)pp28-43
conceptual model not ERA

Card93

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

CardComer94

Dave Card & Ed Comer
Why do So Many Reuse Programs Fail?
IEEE Software Magazine V11n5(Sep 1994)pp114-115
1. economics: setting up an internal marketplace between producers and consumers
2. culture: traing, incentives, measuremtn, management
3. Process: strong configuration management and quality assurance(level 2 CMM).

CardDN95

David N Card<dnc@sps.con>
Is Timing Really Everything?(Guest Editors Introduction)
IEEE Software Magazine V12n5(Sep 1995)pp19-22

Cardenas-GarciaZelkowitz91

Sergio Cardenas-Garcia & Marvin V Zelkowitz
A Management Tool for Evaluation of Software Designs
IEEE Trans SE-16 n9(Sep 1991)p961-971. QUALITY+PURPOSE risk analysis
viabillity::=correct+weighted attributes

Cardetal87

David Card & Frank E McGary & Gerald T Page
Evaluating Software Engineering Technology
IEEE Trans on Software Eng VSE-13n7(Jul 1987)pp845-851
=STATISTICS PRODUCTIVITY QUALITIES
concludes: using experienced+SQA+documentation improves reliability without effecting productivity. SP and top-down reduced productivity and made small +ve difference to reliability. Perhaps cleanroom testing? Weakness:
Let
(Close Let )
[SelbyBasiliBaker87]

CardMoranNewell83

Stuart K Card & Thomas P Moran & Allen Newell
The Psychology of Human-Computer Interaction
CRC Press 1983
=UNREAD USER INTERACTION HCI GOMS PEOPLE
GOMS::=${Goals, Operators, Methods, Selection_rules}.
Provides caculations to evaluate scenarios.
TBD [click here if you can fill this hole]

CardZubrow01

David Card & David Zubrow
benchmarking software organizations
IEEE Software Magazine V18n4(July/Aug 2001)pp16-17
=EDITORIAL BENCHMARKING PROCESSES CMM
Difficult: define clear objectives, plan carefully, and interpret cautiously.
For more see pages18-56

CareyCarlson02

James Carey & Brent Carlson
Lessons learned becoming a framework developer
Software - Practice & ExperienceV32n8(10 July 2002)pp789-800
=EXPERIENCE FRAMEWORKS PATTERNS Object-Oriented
You are not producing a product.
You must work on and with the framework's customer's teams.

CareyDeWittNaughton94

?? Carey & ?? DeWitt & ?? Naughton
The OO7 Benchmark
University of Wisconsin Technical Report April 1993 revised Jan 1994
=EXPERIENCE OBJECT-ORIENTED DATA PERFORMANCE
See [MartinSwaran97]

Carlson01

Dave Carlson
Modeling XML Applications with UML: Practical E-Business applications
Addison-Wesley 2001
=HOW-TO XML UML BUSINESS
Advert in Software Development Magazine V10n2(Feb 2002)pp44-47
Also see [Carlson02b] and [Carlson02c]

Carlson02b

David Carlson
Modeling XML Applications
Software Development Magazine V10n4(Apr 2002)pp48-50
=ADVERT UML XML xCBL
transforming UML models for specific platforms.
Use UML profile (stereotypes and tagged values) to model XML designs.
Extract from [Carlson01]
Also see [Carlson02c] and [Carlson02d]

Carlson02c

David Carlson
Modeling XML Applications Part 3
Software Development Magazine V10n5(May 2002)pp45-48
=IDEA UML XML XMI OMG MOF
Demos standard mapping from class diagram to XML schema with and without stereotypes indicating the XML mapping.
Shows how a schema can define the XML Scheme version of generalization: <xs: element name=... type=.... substitutionGroup="generalization"/>
Also see [Carlson02b] and [Carlson01].

Carlson02d

David Carlson
Modeling XML Applications Part 4
Software Development Magazine V10n6(Jun 2002)pp38-41
=ADVERT UDDI in UML WEB services SOAP XML schema
UDDI::="Universal Description, Discovery, and Integration", specifies XML documents for business data like contacts, services,etc. [ http://www.uddi.org ]
Also see [Carlson02b]
[Carlson02c] and [Carlson01]

CarmelWhitakerGeorge93

Erran Carmel & Randall D Whitaker & Joey F George
PD and Joint Application Design: A transatlantic Comparison
Comm ACM V36n6(Jun 1993)pp40-48
=HISTORY JAD PD USER DESIGN PROTOTYPING REQUIREMENTS
PD:="Participatory Design".
JAD:="Joint Application Design".
Reports claimed benefits of JAD (Table 1).
Typical drawing or typical JAD room of the time.
JAD moved from documentation to using CASE tools.
Many prescriptions and recipes for running meetings.

CarmelAbbot07

Erran Carmel & Pamela Abbot
Why 'nearshore' means that distance matters
Commun ACM V50n10(Oct 2007)pp40-46
=SURVEY 150 ARTICLES DISTRIBUTED PROCESS LOCATION OUTSOURCE OFFSHORE SHORING SOURCING
nearshore::= low geographical temporal cultural linguistic political economic historical distance to lower wage software development.
Some places are both exporters and importers of software work.

CarneyLong00

David Carney & Fred Long
What do you mean by COTS?
IEEE Software Magazine V17n2(Mar/Apr 2000)pp83-86
=ESSAY COMPONENTS
Don't use acronyms! Specify the type of source plus the modifiability of the component

Caromel93

Denis Caromel
Toward a Method of Object-oriented Concurrent Programming
Comm ACM V36n9(Sep 1993)pp90-116

Carpenter95

Paul Carpenter(mailto:paul@pcserv.demon.co.uk)
Never mide the Functionallity: Look at the graphics
IEEE Computer MagaZine V28n9(Sep 1995)p112

CarrellSkeen92

?? Carrell & ?? Skeen
Object Operations Benchmark
ACM Trans DBS
V17n1(Mar 1992)PP??-??
=EXPERIENCE OBJECT-ORIENTED DATA PERFORMANCE
See [MartinSwaran97]

Carrieroetal95

Nicholas Carriero & Eric Freeman & David Gelernter(all Yale) &David Kaminsky(IBM)
Adaptive Parallelism and Piranha
IEEE Computer V28n1(Jan 1995)pp40-49
1. Linda, coordination language, feeder, master-worker parallelism
2. tuple::=#data
3. tuplespace::=Bag(tuple)

CarrieroGelernter89

N Carriero & David Gelernter
Linda in Context
Comm ACM V32n4(Apr 1989)pp444-458
=ADVERT Technical Concurrency Tuples

CarringtonDukeHayesWelsh93

David Carrington<davec@cs.uq.oz.au> & David Duke<duke@minster.york.ac.uk> & Ian Hayes<ianh@cs.uq.oz.au> & Jim Welsh<jom@cs.uq.oz.au>
Deriving Modular Designs from From Specifications [Notkin93] pp 89-98
=CASE-STUDY FORMAL Design Z

Carroll82

John M Carrol
The Adventure of Getting to Know a Computer
Computer IEEE (Nov 1982) pp49-58
=EXPERIMENT USER System
Using a command line interface is very like trying to play a command line game like Adventure: disorienting, illusive, empy, mystery messages, slippery, side effects, clashes with experience, no help for acheiving goals.

Carroll91

John M Carroll
Making Errors; Making sense; Making Use
pp154-167 in FloydCetal91
=ESSAY USER

Carroll94

John M Carroll<carroll@cs.vt.edu>
Making Use a Design Representation
Commun ACM V37n12(Dec 1994)pp29-35
=EXPERIENCE USER scenario use-case

Carroll95

John M Carroll(ed)
Scenario-based Design: envisioning work and technology in system development
John Wiley & Sons Inc NY NY 1995 $44.95 ISBN 0-471-07659-7 CR9607-0458
=TEXTBOOK USER SCENARIO REQUIREMENTS REUSE Use-case CASESTUDY

Carrol01

John M Carroll
Making use: scenario-Based Design of Human-Computer Interactions,
MIT Press Cambridge MA ISBN 0-262-03279-1 QA76.9 H85 C37 review IEEE Computer Mag Apr 2000 p96
=HOWTO SCENARIOS USER ANALYSIS REQUIREMENTS

CarrollCarrithers84

John M Carroll & ?? Carrithers
Training Wheels in a User Interface
Commun ACM V27n8(Aug 1984)pp800-806
=EXPERIENCE prototypes System iterative process
Compare [Kelley84]

CarrollE05

Edward R Carroll
Estimating Software based on use case points
Companion to 20th ACM SIGPLAN OOPSLA (Oct 2005)pp257-265 CR 0611-1155
=EXPERIENCES THEORY ESTIMATION UCP COCOMO RUP
UCP tested at a CMM Level-5 organization! 95% of estimates are within 9% or actual.
Actors classified as simple(API), average(alpha), or complex (GUI).
Scenarios classified by number of transactions.
13 Technical factors (T1=must be distributed, ... T13=needs special user training).
8 Experience factors.
. . .
Feedback and tuning. Change process, management, technique, ...

CarrollL77

Lewis Carroll (ed. William W Bartley III)
Symbolic Logic Pts I & II
Harvester Press 1977 Hassocks Sussex England
=MONOGRAPH LOGIC syllogisms SORITES EXAMPLES
Pt II uses something like resolution and semantic tableaux!

CarrollRossonChinKoenemann98

John M Carroll & Mary Beth Rosson & George Chin & J"urgen Koenemann
Requirements Development in Scenario-Based Design
IEEE Trans SE V24n12(Dec 1998)pp1156-1170 CR9906-0433
=CASESTUDY USER SCENARIO participatory design.
SRS to SCENARIOS + observations ->- analysis->-activity, pragmatics

CartwrightShepperd00

Michael Cartwright & Martin Shepperd
An empirical investigation of an object-oriented software system
IEEE Trans Software Engineering V26n8(Aug 2000)pp786-796
=EXPERIENCES ANALYSIS Large testing system QUALITIES Shlaer-Mellor C++
Project_Technology::= See http:/www.projtech.com/, Shlaer_Mellor.
32 classes 133k LOC 1year of use part of 10 year old multimillon LOC telecommunication system. 2k developers ISO9000 accredited. 1993-1994. not OOT experienced.
one header had 2988 LOC! LOC = count semicolons.
depth of inheritance ranged 0..2.
defect/class stats (range=> 0..47, mean =>8, median =>2).
number of events and states in a class predict the size and the number of defects. size and inheriting increase the number of defects.

CarvalloFranchQuer07

Juan Pablo Carvallo & Xavier Franch & Carme Quer
Determining Criteria for selecting Software Components: Lessons Learned
IEEE Software Magazine V24n3(May/Jun 2007)pp84-94
=EXPERIENCE STANDRADS COTS COMPONENTS SELECTION QUALITIES PURPOSES Criteria Catalog ISO/IEC9126-1 METRICS EVOLUTION REALITIES DOMAIN TAXONOMY
"Adopt a balanced Criteria Catalog"
Three level hierachy extending one in the standard.
Built for a particular "scope": domain or category of similar domains.
"Recognize the importance of nontechnical criteria"
"Precisely Define your selection framework"
UML model. KitchenhamHughesLinkman01. Criteria can be linked: synergy, conflict, ... Tool [ http://www.lsi.upc.edu/~gessi/DesCOTS/ ]
"Consider the Criteria Catelogs final pupose". Catalogs can be reused between similar scopes.
"Organize software scopes herarchically". Build a taxonomyof scopes (Figure 5).... Based a known hierarchy of business Applications.
Describes 4 or 5 ways the experience can be used.
The specific evolved catalogs and taxonomies are less important than the idea of evolving, iteratively, incrementally precise catalogs and taxonomies suited to your projects.

CarverNagappanPage08

Jeffrey C Carver & Nachiappan Nagappan & Alan Page
The impact of educational background on the effectiveness of Requirements Inspections: an empirical study
IEEE Trans Software Engineering V34n6(Nov/Dec 2008)pp800-812
=EXPERIMENT PEOPLE INSPECTIONS REQUIREMENTS
Provides good evidence of a couple of useful facts:
1. People who have written requirements are better at finding defects than people who have not written them.
2. People with Computer or Software Engineering degrees are worse at find requirements defects than those who have other degrees.

CasatiEtal00

Fabio Casati & Silvana Castano & Mariagrazia Fugini & Isabelle Mirbel & Barbara Pernici
Using patterns to design rules in workflows
IEEE Trans Software Engineering V26n8(Aug 2000)pp760-785
=EXPERIENCE DESIGN RULEBASED EXCEPTIONS TOOL
pp773-779: Interesting catalog of templates that handle exceptions in workflows.
Templates related by refinement, enrichment, and instantition -based specialization

Caspi92

?? Caspi
Clocks in Dataflow Languages
Theor Comput Sci V95n1(Mar 23 1992)pp125-140
CR9304-0231
=THEORY CONCURRENT

Castagna95

Giusepe Castagna
Covariance and Contravariance: Conflict without Cause
ACM Trans Prog Lang Syst V17n2(May 1995)pp431-447 CR9608-0612
Objects theory genericity

Castagna97

Giusepe Castagna
Object-Oriented Programming: A Unified Foundation
Birkhauser 1997
IEEE Software Mag Review#907046

CastelloMiliTollis02

Rodolfo Castello & Rym Mili & Ioannis G Tollis
Automatic layout of statecharts
Software - Practice & Experience V32n1(Jan 2002)pp25-55
=DEMO TOOL GRAPHIC STATECHART FSM/STD LAYOUT

Casti92a

John L Casti
Reality Rules: I -- Picturing the world in Mathematics -- The Fundamentals
Wiley NY NY 1992
=MATHEMATICS MODELS CATESTROPHES CELULAR AUTOMATA CHAOS FRACTALS
Also see Volume II [Casti92b]

Casti92b

John L Casti
Reality Rules: II -- Picturing the world in Mathematics -- The Frontier
Wiley NY NY 1992
=MATHEMATICS GAMES EVOLUTION SYSTEMS CYBERNETICS COMPLEXES COMPUTATION BELIEF
Also see Volume 1 [Casti92a]

Cattell91

R G G Cattell(Guest Editor)
Next-Generation DataBase Systems
Commun ACM V34n10(Oct 1991)pp31-33
convergence of OO with DBMS remedies defects in RDBMS...

CavalcantiNaumann00

Ana Cavalcanti & Daviv A Naumann
A Weakest Precondition Semantics for refinement of object-oriented programs
IEEE Trans Software Engineering V26n8(Aug 2000)pp713-728
=THEORY SEMANTICS OBJECTS ROOL
Study C C Morgan first!

CavanoLaMonica87

Joseph P Cavano & Frank S LaMonica
QUALITY Assurance in Future Development Environments
IEEE Software V4n5(Sep 1987)pp26-34
=THEORY SQA QUALITY

CavusogluMishraRaghunathan04

Huseyin Cavusoglu & Birendra Mishra & Srinivasan Raghunathan
A Model for Evaluating IT Security Investments
Commun ACM V47n7(Jul 2004)pp87-92
=THEORY MATHEMATICS COST SECURITY ROI BAYES

CegielskiHall06

Casey G Cegielski & Dianne J Hall
What makes a Good Programmer?
Commun ACM V49n10(Oct 2006)pp-
=EXPERIMENT 139 undergraduates PSYCHOLOGY Object-Oriented PROGRAMMER Allport-Lindzey-Vernon ETS etc
theoretical_value_belief::@People= desire structure and proof, highly objective, highly focused, look for reason and validation, loners, no interest or consideration of the untested and unproven.
Cognitive ability and personality type both associated with programming skill.
theoretical_value_belief associated with cognitive ability and personality.

Cerietal88

Stefano Ceri & Stefano Crespi-Reghizzi & Andrea Di Maio & Luigi A Lavazza
Software Prototyping by Relational Techniques: Experiences with Program Construction Systems
IEEE Trans Soft Eng VSE-14n11(Nov 1988)pp1597-1609
=Experiences =Demo relational data Ada code

CerpaVerner09

Narciso Cerpa & June M Verner
Why did your project fail?
Communications of the ACM V52n12 (Dec 2009) Virtual extension pp130-134 [ 1610252.1610286 ]
=POLL 235 PROJECTS SUCCESS FAILURE PROJECT INSOURCE OUTSOURCE ESTIMATION DEVELOPMENT TIME QUALITY WORK PEOPLE MANAGEMENT
Delivery date, estimates, and other management issues are the commonest reasons for failure.
No time for reviews and reassessing risks, and so, no learning.
Figure 1 page132. 18 top reasons -- Worth the price of the PDF download from ACM.
inhouse not equal to outsourced.
Need inhouse postmortems.

CerroGasquet02

Luis Farnias Del Cerro & Olivier Gasquet
A General Framework for Pattern-Driven Modal Tableaux
L J of the IGPL V10n1(2002)pp51-83
=THEORY PROVING MODAL LOGIC SEMANTIC TABLEAUX RELATIONS
Proves completeness and soundness for a set of rules for proving formula in many different modal logics by combining Kripke semantics, semantic Tableaux, and relational calculus.
p58 rule <>: If <>A,S @ p then add node q: <>A,S@p ---A@q.
rule K: if []A,S@p----S1@q then []A,S@p----A,S1@q.
Lotrec::tool= See http://www.itit.fr/ACTIVITIES/LILaC/Lotrec/, written in Java

Cervanto00

Iliano Cervanto
Logical Framework: Why not just classical logic?
CSLI Lecture notes V91, Stanford U(2000)pp87-104 in "Formalizing the dynamics of information" ed. Martina Faller & Stefan C Kaufmann & Marc Pauly ISBN 1-57586-239-5 Q360
=ESSAY LOGIC LAMBDA cf Z SCHEMA
(dick)|-Parallels my thinking in creating MATHS.

CesareEtAl10

Sergio de Cesare & Mark Lycett & Chaitali Patel &Ray Paul
Examining perceptions of agility in software development practice
Commun ACM V53n6(Jun 2010)pp126-130 (Virtual extension) [ 1743546.1743549 ]
=POLL SENIOR PEOPLE HISTORY AGILITY
Organizations have an explicit and tailored but flexible and iterative/incremental development process for example RUP DSDM XP.
Strong belief in continuous delivery of working software, face-to-face communication, developers and business working together.
No agreement on working software measures progress or allowing late changes in requirements.
Postmortems/reflection used.
Change is controlled but iteration rules (most 3 months ).
Emergent design not well understood.

CeschiEtal05

Martina Ceschi & Alberto Sillitti & Giancarlo Succi & Stefano De Panfilis
Project Management in plan based and agile companies
IEEE Software Magazine V22n3(May/Jun 2005)pp21-27
=POLL 20 MANAGERS PROCESS SATISFACTION AGILE
All use some form of incremental delivery and face similar problems with deadlines and changing requirements,
Some nonsignificant evidence that Agile companies tend to be more satisfied with project planning and customer relationships.
50% of both want developers that can work in a group.

Chaaretal93

Jarir K Chaar & Michael Halliday & Inderpal S Bhandari & Ram Chillarege
In-Process Evaluation for Software Inspection and test
IEEE Trans Softw Eng VSE19n11(Nov 1993) pp1055-1070

ChaEtAl09

Hoon S Cha & David E Pingry & Matt E Thatcher
What Determines IT Spending Priorities
Commun ACM V52n8(Aug 2009)pp105-110 [ 1536616.1536644 ] (Virtual Extension)
=POLL 2006 IT SPENDING ECONOMICS PROJECT REASONS CS372
Abstract
1. "Based on survey results from 1,495 business leaders we have derived some important insights into how factors such as industry type, firm size, state location, and past IT performance affect a firm's allocation of IT expenditures across business functions. Specifically, the survey data shows that the highest IT spending priorities of the respondents are in the areas of administration and production and distribution while the lowest priorities are in the areas of R&D and security."

ChakrbortyLei04

Dipanjan Chakrborty & Hui Lei
Extending the Reach of Business Processes
IEEE Computer Magazine V37n4(Apr 2004)pp78-80
=IDEA BUSINESS PROCESS WORKFLOW WEBSERVICES SMS Email BPEL xBPEL WSDL
BPEL::= "Business Process Execution Language".
Use data+calendar+... to find route to people.

ChaeKwonBae00

Heung Seock Chae & Yong Rae Kwon & Doo Hwan Bae
A cohesion Measure for Object-Oriented classes
Software - Practice & Experience V30n12(Oct 2000)pp-
=CASESTUDY Object-Oriented METRIC cohesion C++ TOOL HYSS

Chaitin05

Gregory Chaitin
Meta Math
Pantheon Books NY NY 2005
=ESSAY MATH 42 GOEDEL TURING LIEBNITZ INFORMATION
Argues that we need to stress creativity and imagination rather than formallity(Hilbert)

Chalin10

Patrice Chalin
Engineering a sound assertion semantics for the verifying compiler
IEEE Trans Software Engineering V36n2(Mar/Apr 2010)pp275-287
=TYPE USER V&V SQA FORMAL METHOD TOOL VC VERIFICATION COMPILER
A verifying compiler should spot when assertions will go wrong.
The logic of the verifying compiler should allow for expressions being undefined.
Must handle arithmetic errors like 1/0 correctly. Even in assertions!
Stresses the need to talk to the users of the compiler before deciding its semantics!
Introduces a definedness predicate.
Formal Methods shouldn't have imposed an elegant but unsound logic on software.

Champeaux02

Dennis de Champeaux
Software Engineering Considered Harmful
Commun ACM V45n11(Nov 2002)pp102-104
=ESSAY ENGINEERING SCIENCE LOGIC PRACTICE C++UML VALIDATION
Quotes Denning on the state of current software systems and being hired to fix messes that should not have occurred.
Need for extensions to Hoare Logic to pointers and parallel processes.
Seems to ignore work by Hoare, Lamport and others.

Champauxetal93

Dennis Champeaux & Doug Lea & Penelope Faure
Object-oriented System Development
Addison-Wesley Redwood City CA 1993
532pp $48.50 ISBN 0-201-56355-X CR9408-0496

ChampauxFaure92

Dennis Champeaux & Penelope Faure
A comparative study of object-oriented analysis methods
Journal of Object-oriented Programming (Mar-Apr 1992)pp21-33.
=COMPARISON OBJECT-ORIENTED METHODS

ChanEtal01

William Chan & Richard J Anderson & Paul Beame & David H Jones & David Notkin & William E Warner
Optimizing symbolic Model checking for Statecharts
IEEE Trans Software Engineering V27n2(Feb 2001)pp170-190, also in ICSE'99
=EXPERIMENTS FORMAL VERIFICATION REQUIREMENTS STATECHARTS GRAPHIC LOGIC OPTIMIZATION RSML TCAS II BDD
Electrical power distribution system
order of magnitude improvements.

ChandraGuptaHennessy94

Rohit Chandra & Anoop Gupta & John L Hennessy
COOL: An Object-based Language for Parallel Programming
IEEE Computer Magazine V27n8(Aug 1994)pp13-25
=IDEA LANGUAGE COOL OBJECT-ORIENTED
extends C++
declare functions to be parallel
shared objects controlled by declaring functions 'mutex' or non-mutex
synchronization by monitors + condition variables and signals...
benefits of data abstraction

Chandrasekaran97

Periannan Chandrasekaran
How use case modeling policies have affected the success of various projects (or how to improve use case modeling)
OOPSLA'97 & ACM SIGPLAN notices V??n?(??? 1997)pp6-9 [ 274567.274569 ]
=ANECDOTE USE CASE REQUIREMENTS OOSE Jacobson
Tells conclusion from several large projects that used OOSE.
Problems
1. need details of all changes in system as use case proceeds
2. Need comprehensive list of use cases involving users, a comprehensive and clean model of the human actors, and robust domain model.
3. Include algorithms(business rules?) as regular requirements
4. Use cases must capture all interfaces with external systems even if not human.
5. The GUI is not the use case. One screen can trigger different use cases that are independent of each other.
6. Keep the use case and domain model synchronized. Common well defined terminology.
7. Use abstract use cases for algorithms.
An abstract use case is one that is not initiated by an actor and contains common steps abstracted from other use cases. Example: calculate discounts on sale. Notes that people expressed common algorithms and procedures as "business rules" (possibly in an attempt to fit them to SQL and AI style Rule Engines). Claims they should be expressed as (abstract) use cases. (dick)|-may be better to restrict business rules to invariants only??

ChandyMisra88

K Mani Chandy & Jayadev Misra
Parallel Program Design: A Foundation
Addison-Wesley Redwood City CA 1988
=DEMO UNITY NONSEQUENTIAL COMPOSITIONAL
cited in [Staskauskas93] [LamShankar94a] [KayReed93] [Jonsson94] [CreveuilRoman94]

Chang89

Shi-Kuo Chang(ed)
Principles of Visual Programming Languages
Prentice Hall Int. Englewood Cliffs NY 1989.
=TUTORIAL graphic informal

ChangC93

Carl K Chang
Is Existing Software Engineering Obsolete?(editorial)
IEEE Software Magazine V10n5(Sep 1993)pp4-5
=EDITORIAL ENGINEERING

ChangCChristensen99

Carl K Chang & Mark Christensen
A net practice for softwar project management
IEEE Software Magazine V16n6(Nov/Dec 1999)pp80-88
=DEMO TOOL GRAPHIC SCHEDULE PLAN PROCESS PETRI PM-Net
Better than hundreds of comercially available project management tools
Petri nets with products decisions & constraints

ChangEtal01

Carl K Chang & Jane Cleland-Huang & Shiyan Hua & Annie Kuntzmann-Combelles
Function-class decomposition: a Hybrid Software Engineering Method
IEEE Computer Magazine V34n12(Dec 2001)pp87-93 + letter from Dave Leigh IEEE Computer Magazine V35n3(Mar 2002)p6
=ADVERT METHOD FCD PURPOSE MODULE Object-Oriented UML Use-Case-map scenario M-Net =EXPERIENCE
Handles reported problem of having too many types of objects

ChangS-Ketal95

Shi-Kuo Chang & Gennaro Costagliola & Giulano Pacini & Genoveffa Tortora & Bing Yu & Jing-Sheng Yu
Visual-language System for User Interfaces
IEEE Software Magazine V12n2(Mar 1995)pp22-44
=IDEA LANGUAGE GRAMMAR for GRAPHICS GUI
1. Positional grammars and positional rules
2. S:= File Hor Arrow Hor OB
3. relational grammar.

ChangWeissHinchey11

Carl K Chang & David M Weiss & Mike Hinchey
Where Software Engineering meets ...
IEEE Computer V44n10(Oct 2011)pp17-18
=EDITORIAL
Introduces special feature: [Broy11] , [Fitzgerald11] , [Harman11] , ..., and [Parnas11]
Argues that Software Engineering can be imporved when we juxtapose it close to other disciplines.

Chaochenetal91

Zhou Chaochen & C. A. R. Hoare & A. P. Ravn
A calculus of durations
Information Processing Letters V40( 1991)pp269-276
=MATHEMATICAL model of Time

Chapelle07

Gregory Chapelle
Comment on Risks to the Public May 1007, F-22
ACM SIGSOFT Software Engineering notes V32n4(Jul 2007)pp6-7
=LETTER RISKS FAILURE REQUIREMNTS TESTS DATELINE Jighter Jet
Postmortem explanation of how an obvious test case (crossing the international date lien) was not noticed and so not tested for.
Notes how scheduling pressure contributes to this kind of blindness. -- the need to be able to step back and see the whole picture.

Chapman90

Gary Chapman
Bugs in the Program
"Viewpoint" Commun ACM (pp 251-252 ) Mar 1990
=IDEA RISKS

[Chapman06]

In Search of Stupidity: Over twenty years od high tech marketing disasters (2nd Edn)
APress, Berkeley CA 2006 ISBN 1590597214 CR 0801-0047
=UNREAD =EXPERIENCE MARKETTING SARCASM IBM Microsoft Apple MicroPro etc.

Charette95

Robert N Charette
How to Create a Successful Failure
Commun ACM V38n5(May 1995)pp122(Inside RISKS)
=HISTORY RISKS DISASTERS FAILURES COSTS PROCESS
1. Never Plan,
2. Exhibit extreme confidence,
3. Take the most expedient solutions,
4. Be simple Minded,
5. Spawn situations with subtly interlinked decisions,
6. Change decisions frequently,
7. Practice Foolish inconsistency.

Charette05

Robert N Charette
Why Software Fails IEEE Spectrum Magazine (Sep 2005)pp-
=ADVERT RISK MANAGEMENT DISASTERS COSTS
p44. Hall of Shame 1992..2005
Side boxes describe case studies
Rounds up the usual [Charette95] suspects:
1. Bad goals
2. Bad estimates of needed resources
3. Bad systems Requirement
4. Poor project control and/or planning
5. Bad communication ...
6. Politics
7. Commercial pressures

ChariSeshadri04

Kaushal Chari & Saravanan Seshadri
Demystifying Integration
Commun ACM V47n7(Jul 2004)pp59-63
=TAXONOMY STANDARDS BUSINESS
(industry domain (independent | dependent ))><((data | business | presentation ) logic)><(( transport | data format | process ) level)

Charles96

John Charles
DoD Standards Go Global and Commercial
IEEE Software Magazine V13N3(May 1996)pp98-99
Mil-Std498->-ANSI Trial Use Standard J-Std-016
=REPORT STANDARDS ONESIZE AGILE
IEEE/EIA is adapting ISI/IEC 12207 Software Life Cycle Processes->- US Commercial S L C P standard US 12207
trends: several lifecycles(waterfall|incremental|evolutionary)+ less paper documentation and formal review+clearer distinction between true requirements and design choices
Perry DeWeese: "A lot of the things that happen in Software development have there genesis before the sofware-development process starts"

Charles08

F Charles (ed)
The gift of time: the work of Gerald M Weinberg
Dorset House Pub 2008
=SURVEY RESEARCH PEOPLE
Help! [click here Charles08 if you can fill this hole]

ChatterjeeRyderLandi01

Ramkrishna Chatterjee & Barbara G Ryder & William A Landi
Complexity of Points-to Analysis of Java in the Presence of Exceptions
IEEE Trans Software Engineering V27n6(Jun 2001)pp481-512
=THEORY JAVA COMPLEXITY

Chaterjee10

Sutap Chatergee
The Waterfall that won't go away
ACM SIGSOFT Software Engineering Notes V33n1(Jan 2010)pp9-10 [ http://www.acm.org/sigsoft/SEN/ ]
=EXAMPLE MAINTAINENCE LEGACY AGILE Waterfall
Frontend experts must treat the backend developers as stakeholders.
Need to transition from an agile process to a more ceremonial one as software moves from deployment to maintenance.

Chatzigeorgiou03

Alexander Chatzigeorgiou
Mathematical Assessment of Object-Oriented design quality
IEEE Trans Software Engineering V29n11(Nov 2003)pp1050-1053
=THEORY QUALITY COLLABORATION METRICS DIGRAPH eigenvalues authority hub HITS
example of two designs for a microwave oven.

ChauChen03

Michael Chau & Hsichun Chen
Comparison of three vertical search spiders
IEEE Computer Magazine V36n5(May 2003)pp56-62
=SIMULATION NET/WEB NEURAL HITS BFS PageRank Hopfield
Compared 3 algorithms on simulated 100K page subset of the web to see how well relevant medical pages could be found.
PageRank formula had bad performance and relevance. Hubs and authorities may not be about medical things -- Adobe's page for example is an authority to define PDF!
Breadth-first+priorities worked as well as a simulated Hopfield neural net at spotting relevant web sites.

Chauvet95

Jean-Marie Chauvet
Efficient use and reuse of object-oriented technology
Software Development Magazine(Aug 1995)pp35-38
=EXPERIENCE REUSE PQRST ARCHITECTURE DOCUMENTATION TOOLS NOTATIONS
1. Reuse and standards are not automatic results of OOT
2. Architecture:
  - Separate the data base (T) from the the GUI (T)
  - the objects and rules of the Business Process Model (R)
3. Need for business savvy programmers.
4. Need to have indexed and linked model, design specs and code.
5. Common notation: description, indexed and exposed designs etc
6. Agreed non-waterfall but disciplined process
7. supportive tools.

Chavez00

Tom Chavez
A Decision-analytic Stopping Rule for Valdiation of Commercial Software Systems
IEEE Trans Software Engineering V26n9(Sep 2000)pp907-918
=MATHEMATICS BAYES STATITICS THEORY ECONOMICS RELIABILITY TESTS

ChechikDevereuxEasterbrookGurfinkel04

Marsha Chechik & Benet Devereux & Steve Easterbrook & Arie Gurfinkel
Multi-Valued Symbolic Model-Checking
ACM TOSEM Trans Software Eng & Methodology V12n4(Oct 2003)pp371-408
=IDEA TOOL MODEL CHECKING CTL FSM Kripke Multi-valued LOGIC Quasi-Boolean Lattice Χ\_CTL Χ\_Check Χ\_Kripke
Extends classical {False, True} reasoning to {False, Maybe, True} values. Good for incomplete models found during analysis.
Able to have multi-valued variables in: state of FSM, Transitions between states, satisfaction.
meaning(EX(p)) := backward_image(RR)(meaning(p)).
backward_image(RR)(TT) := map[s:S](multivalued_union[t:T](TT(t) multivalued_intersection RR(s,t) )).
Implementation described in 2002 CSRG Tech Report 446, University of Toronto

ChechikGannon01

Marsha Chechik & John Gannon
Automatic analysis of consistency between Requirements and Designs
IEEE Trans Software Engineering V27n7(Jul 2001)pp651-672 CR0203-0314
=CASESTUDY SCR REQUIREMENTS V&V DESIGN TOOL CORD ALGORITHM LANGUAGE LIGHTWIEGHT FORMAL

Checkland81

??? Checkland
Systems Theory; Systems Practice
John Wiley & Sons 1981
=monograph cybernetics USER System softsystems

Cheek95

Martin Cheek
Using Feedback to Improve Software Development
IEEE Software Magazine V12n3(May 1995)pp89-90
=REPORT FEAST EVOLUTION PEOPLE SYSTEMS

ChelfEbert09

Ben Chelf & Christof Ebert
Ensuring the integrity of embedded software with static code analysis
IEEE Software Magazine V26n3(May/Jun 2009)p96-99
=ADVERT RISKS =HISTORY TOOLS lint
p97 Links to resources in sidebar.
Six_detectable_defect_classes:= division by zero + memory leak + null pointer dereference + uninitialized variable + buffer overflow or underflow +inappropriate cast.

Chen80

Peter Pin-Shan Chen(Ed)
Entity Relationship approach to Systems Analysis and Design
North Holland 1980
=TEXT ERD SAD data

Chen04

Jing-Chao Chen
Building a new sort function for a C library
Software - Practice & Experience V34n8(10 Jul 2004)pp777-795
=ALGORITHM quicksort psort qsort C
Psort is O(n log n) in worst and average cases. It includes some the optimizations in qsort developed by Jim Bentley and Doug McIlroy.
Source: [ Psort.htm ]

ChenChuangTsai01

Ding-Yi Chen & Tyng-Ruey Chuang & Shi-Chun Tsai
JGAP: A Java-based graph algorithms platform
Software - Practice & Experience V31n7(Jun 2001)pp615-635
=DEMO GRAPH TOOL Java
Source and docs at [ JGAP.html ]

ChenDiosMiliWuWang05

Yaofei Chen & Rose Dios & Ali Mili & Lan Wu & Kefei Wang
An Empirical Study of Programming Language Trends
IEEE Software Magazine V22n3(May/Jun 2005)pp72-79
=POLL =HISTORY PROGRAMMING LANGUAGES
Gathered data on what developers used, schools taught, and the primary language in companies. Dates: 1993, 1998, 2003
Java is becoming the top language.
Developers appear to value machine independence and extensibility mosts, and dislike simplicity and ease of implementation.

ChenGansnerKutsofios98

Yih-Farn Chen & Emden R Gansner & Eleftherios Koutsofios
A C++ Data Model Suppoerting Reachability Analysis and Dead Code Detection
IEEE Trans on Software Eng VSE-24n9(Sep 1998)pp682-694
=DEMO TOOL TECHNICAL CIAO EDG Acacia [ Acacia ]

ChenR08

Raymond Chen
The New Old Thing: practical development throughout the evolution of Windows
Addison-Wesley Upper Saddle River NJ 2006 ISBN 0321440307 CR 0807-0639
=UNREAD =ANECDOTES MICROSOFT PROCESS DESIGN WHY
Reviewer: the essence of design is an compromise between competing forces in the presence of pressure and uncertainty. [click here Chen08 if you can fill this hole]

Cheng93

Jingwen Cheng<jim@bruce.cs.monash.edu.au>
Parameterized Specifications for Software Reuse
ACM SIGSOFT Software Engineering Notes V17n4 (Oct 1992)pp53-59
=IDEA generic polymorphic ADT specifications

ChengHeimdahl97

Betty H C Cheng & Mats P E Heimdahl
Bridging the Gap between Informal and Formal Approaches to Software Development
ACM SIGSOFT SEN V22n5(Sep 1997)pp83-84
=IDEA OMT+LARCH
plan to provide OMT with Larch formalizations...

ChengWang02

Betty H C Cheng & Enoch Y Wang
Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling
IEEE Trans Software Engineering V28n8(Aug 2002)pp747-762
=EXAMPLE Object-Oriented model OMT DYNAMICS semantics LOTOS
For UML see McUmberCheng01

ChenFuchsChung01

Shyh-Kwei Chen & Kent Fuchs & Jen-Yao Chung
Reversible Debugging Using Program Instrumentation
IEEE Trans Software Engineering V27n8(Aug 2001)pp715-727
=EXPERIMENT DEBUGGING TOOL C TECHNICAL
wraparound history buffer.

ChenJ97

Jen-Yen Jason Chen
CSPL: An Ada95-like UNIX-based Process Environment
IEEE Trans software Engineering VSE23n3(Mar 1997)pp171-184
=IDEA ADA ENVIRONMENT UNIX

ChenNishimotoetal90

Y-F Chen & M Y Nishimoto & CV Ramamoorthy
The C Information Abstraction System
IEEE Trans SE-16n3 pp325-334
=DEMO language ENGINEERING data

ChenPaul01

Chaomei Chen & Ray J Paul <@brunel.ac.uk>
Visualizing a Knowledge Domain's Intellectual Structure
IEEE Computer Magazine V34n3(Mar 2001)pp65-71
=SURVEY GRAPHIC 3D MODEL CITATIONS
ACA := "Author Cocitation Analysis".
SCI := "Science Citation Analysis".
MDS := "Multidimensional Scaling".
MSP := "Minimum Spaning Trees"..
Landscape tools: Spire themescape, VxInsight, PathFinder
PathFinder steps:= citation structure; essential connections; intellectual groups; citation history impact.
(dick)|-why isn't time a dimension?.

ChenTseZhou02

Tsing Yueh Chen & T H Tse & Zhi Quan Zhou
Semi-Proving: an Integrated Method Based on Global Symbolic Evaluation and Metamorphic Testing
Proc ISSTA02 & ACM SIGSOFT Software Engineering Notes V27n4(Jul 2002)pp190-195 & IEEE Trans Software Engineering V37n1(Jan/Fed 2011)pp109-125
=EXAMPLE SYMBOLIC TESTING INVARIANT PROPERTIES TOOL METAMORPHIC RELATION PATHS
Symbolically execute all paths to verify invariant results under changes of input.
Example1: all permutations of 3 numbers have the same median.
A mutated program will not satisfy the same test.
Note: the IEEE Trans paper is extended and has title "Semi-proving: an integrated method for program proving, testing, and debugging".

CheonLeavens94

Yoonsik Cheon & Gary T Leavens
The Larch/Smalltalk Specification Language
TOSEM V3n3(Jul 1994)pp221-249
=DEFINITION LARCH SPECIFICATION MODULES Smalltalk OO
1. First Larch Spec language with both subtyping and inheritance.
2. Description of LSL etc..
3. *Separate conceptual types from implemented classes.
4. Type inference
5. interface spec
```
 Header
```
```
   returns
```
```
   requires
```
```
   modifies
```
```
   ensures
```
```
 Trait specs
```
```
   includes
```
```
   introduces
```
```
 Asserts
```
```
   ... generated by ...
```
```
   ... partitioned by ....
```
```
     Axioms
```

Cherry92a

George W Cherry
Graphic Formalisims Should Integrate Communication, Control, and Data Flow
ACM SIGSOFT Software EngineeringNotes V17n2(Apr 1992)pp64-69
=ADVERT GRAPHIC writing is not ENGINEERING [Cherry92b]

Cherry92b

George W Cherry
Software Construction by Object-Oriented Pictures: Specifying Reactive & Interactive Systems
Thought**Tools Inc. dist Dorset House Publishing New Your NY 10014-9982 ISBN 0-9625003-0-5
=TEXT

ChesnevarMaguitmanLoui00

Logical models of argument
ACM Computing Surveys V32n4(Dec 2000)pp337-383
=HISTORY 1950-99 FORMAL DIALECTIC DEFEASIBLE CONSISTENCY REASON ARGUMENT PLAUSIBLE AGENTS AI LAW NONMONOTONIC
Formal logic is reasoning that can not be defeated. Normal reasoning is not like this.
Detailed, difficult and hard to read.
No ref to work on inconsistent requirements. Small comment on OO inheritance.

Chetali98

Boutheina Chetali
Formal Verification of Concurrent Programs Using the Larch Prover
IEEE Trans Soft Eng V24n1(Jan 1998)pp46-62
=EXPERIENCE UNITY LARCH SQA NONSEQUENTIAL SAFETY LIVENESS

CheyneRitter01

Tanya L Cheyne & Frank E Ritter
Targeting Audiences on the Internet
Commun ACM V44n4(Apr 2001)pp94-98
=EXPERIENCE WEB/NET Usenet polls
1 in 10K respond from Usenet. 8% complain (all from UK). More like a focus group.
Banner adds with incentive is fruitful.
Search engines are promising.
Problem: anonymity, dishonesty, and multiple submissions.

CheungKramer94

Shing Chi Cheung & Jeff Kramer
Tractable Dataflow analysis for Distributed Systems
IEEE trans on Soft Eng vSE-20n8(Aug 1994)pp579-593
=PAPER STD/FSM CORRECTNESS NONSEQUENTIAL

ChidamberKemerer94

S R Chidamber & C F Kemerer
A Metrics Suite for Object-Oriented Design
IEEE Trans SE V2?n?(??? 1994)pp467-493
=IDEA METRICS OBJECT-ORIENTED

Chikofsky(ed)88

Various authors
Special Issue on the emergence of CASE
IEEE Software v5n2(Mar 1988)
=MAGAZINE tools graphic DFD ERD Technical

ChikofskyCross90

Elliot J Chikofsky & Lames H Cross II
Reverse Engineering and Design recovery: A Taxonomy
IEEE Software V7n1(Jan 1991)pp13-17
=DEFINITIONS REVERSE ENGINEERING

ChinEtAl06

George Chin Jr & Eric C Stephen & Debbie K Gracio & Olga A Kuchar & Paul D Whitney & Karen L Schuchardt
Developing concept-based user interfaces for scientific computing
IEEE Computer Magazine V39n8(Sep 2006)pp26-34
=DEMO HCI VISUALIZATION EXPLICIT GRAPHIC ONTOLOGIES MINDMAPS WORKFLOWS SCENARIOS VMWEB RCM-PSE SKFAM
Intereting and useful: visual front end to a data base.
In the 1980's FileVision on the Mac let you associate graphics with data input as forms into a data base....
Now add useful tools: libraries of processes for a workflow as an example.

ChirouzeClearyMitchell05

Olivier Chirouze & David Cleary & George G. Mitchell
A software methodology for applied research: eXtreme Researching
Software - Practice & Experience V35n15 (Dec 2005) pp1441-1454
=EXPERIENCE DISTRIBUTED XP Erickson

Chisholm94a

John Chisholm
The Art of Software Design Part II
UNIX Review V12n4(Apr 1994)pp17-20
=ESSAY PROCESS
1. Investigate: use all resources to gather all possible data users, problem, technology
2. Taxonomy: user's goals, all aspects name, hierarchy
3. Organisation: user goals parallel congruent to program functions
4. Epiphany (Aha!): creative thinking ---> unified vision (metaphors)
5. Dramatization: Scenarios based on goals
6. Iteration: Repeat until USER goals match requirements

Chisholm94b

John Chisholm
Mail-enabled Applications: Part I
UNIX Review V12n6(Jun 1994)
=ARTICLE EMAIL UNIX
See [Chisholm94c]

Chisholm94c

John Chisholm
Mail-enabled Applications: Part II
UNIX Review V12n7(July 1994)
=ARTICLE EMAIL UNIX
See Part I [Chisholm94b]

Chittaro06

Luca Chittaro
Visualizing information on Mobile Devices
IEEE Computer Magazine V39n3(Mar 2006)pp40-45
=DEMO MOBILE USER INTERFACE DATA DISPLAY HCI HALOS Relevance
Need to create new ways to display data on mobile device.

Chmuraetal90

L J Chmura & A F Norcio & T J Wicinski
Evaluating Software Design Processes by Analyzing Change Over Time
IEEE Trans SE-16n7(Jul 1990)pp729-740
=case-study lifecycle

ChoiZeller02

Jong-Deock Choi & Andreas Zeller
Isolating Failure-Inducing Thread Schedules
Proc ISSTA02 & ACM SIGSOFT Software Engineering Notes V27n4(Jul 2002)pp210-220
=DEMO TOOL TECHNIQUE TESTING Delta-Debugging NONSEQUENTIAL DEJAVU JAVA Jalapeno
Tool found smallest difference in schedules that caused an error to occur.
Based on .Seeee ZellerHildebrandt02

ChomskiSchutzenberger63

Naom Chomski & ?? Schutzenberger
The Algebraic Theory of Context-free Languages
pp 118-161 in Braffort Hirschberg 63
=theory languages topology SEMINAL

Choobinehetal92

Joobin Choobineh & Michael V Mannino & Veronica P Tseng
A Form Based Approach for Database Analysis and Design
Commun ACM V35n2(Feb 1992)pp108-120 CR9305-0337
=DEMO DDD DATA EXPERT cardinallities to determine structure EDDS ERA NORMALISATION System Reality

Chorost05

Michael Chorost
Rebuilt: How becoming part computer made me more human
Houghton Mifflin NY NY 2005 ISBN 0-618-37829-4
=ESSAY COCHLEAR IMPLANT HUMANITY GEEK CYBORG DEAFNESS
How do you feel when what you hear depends on a program written in C and you can read the source code?
Excellent discussion of science fictional treatments of cyborg's, androids, and the Butlerian Jihad in Dune.
Much more...

Chow(Ed)84

Software Quality Assurance
IEEE Computer Society Tutorial
=TUTORIAL SQA QUALITies V&V DESIGN

Christensen94

Mark J Christensen(Northrop ESDiv)
Would you do this to your customer?
IEEE Software magazine v11n1(Jan 1994)pp12

ChristensenCM97

Clayton M Christensen
The Inovator's Dilemma: When new Technologies cause Great Firms to Fail
Harvard Business School Press Boston MA 1997 ISBN 0-87584-585-1 CR9802-0061
=HISTORY =THEORY ECONOMICS of INNOVATION
Applied to software development in pp180-182 [Highsmith99]
Doing the right things (research, listening to customers, finding improvements and profits) helps an organization fail to develop new makets/values that ultimately eclipses the normal.
new_technology = sustaining_technology | disruptive_technology.
Disruptive technology re-creates the market with new values and metrics and initially shows comparatively low profits, performance, and market.
Historical examples: disk drives, mechanical shovels, motor bikes, Quicken, ...
Sustaining tech fits given customers but disruptive tech discovers new customers that fit the given tech.
New customers who need less performance at a lower price, higher convenience, and/or higher reliability. Disruptive is down-market.
There are more reasons and profit to move up-market than down-market.
Disruptive technology undermines the old market. It starts with a tiny unpredictable new one. Agnostic marketing!
Survival: create small separated suborganisation with room to fail and learn. Don't ask the customer; watch them. K.I.S.S.!
Uses trajectory maps showing performance (supply and demand) vs time.
cf. Kuhn's paradigm shift in science. Thom's Catastrophe theory. Koestler's matrix shift. Toynbee's David and Goliath.

ChristensenChang96

Mark J Christensen(Northrop ESDiv) & Carl Chang
Blueprint for the Ideal Requirements Engineer
IEEE Software magazine V13n3(Mar 1996)p12
=ESSAY SYSTEM REQUIREMENTS
RE continues thruout the life cycle embracing end-to-end responsibillity and allowing only smooth and controlled evolution based on understanding the concrete application domain
RE language needs to be formal with both text and graphical notations.

ChristosPoniPalaiolgou10

Ioannis T Christou & Stavros T Ponis & Eleni Palaiogou
Using the agile unified process in banking
IEEE Software Magazine V27n3(May/Jun 2010)pp72-79 CR 1106-0674(Jun 2011)p383
=EXPERIENCE AGILE AUP RUP PROCESS UML SERVICES SOA GREEK BANKS INTEGRATED DESKTOP
Describes phases and iterations in the AUP --agile unified process -- as tailored to a project.
Collision between BDUF and emergent design of data base.
Tools: simple -- whiteboards, sticky notes, index cards, flip charts, ...
Produced too much documentation.
Use cases also need
business rules, HCI requirements, constraints, and nonfunctional requirements.
Need more than the UML.
Which artifacts do you really need?
Managers like rigid but developers like flexible.
Work on many artifacts at once.
Simple just good enough artifacts.
People must be able to both model and code.
Honest open communication. Publish models.

Christy09

Peter Christy
Commentary: A Trip without a Roadmap
ACM Queue V7n1(Mar 2009) [ detail.cfm?id=1515746 ]
=CASE STUDY REVIEW TECHNOLOGY REQUIREMENTS RIA FITNESS PERFORMANCE USER
Review of [Norwalk09]
No user requirements -- straight to technological solution. Performance an afterthought.
Quote

Chroust86

G Chroust(IBM Vienna)
Backtracking in Software Process Models
p64-68 in [Dowson86].
=case-study non-sequential lifecycle

Chu-Carroll11

Mark Chu-Carroll
Things Everyone Should Do: Code Review
Good math, bad math blog(Jul 6 2011)
.See http://scientopia.org/blogs/goodmath/2011/07/06/things-everyone-should-do-code-review/
=BLOG CODE TECHNICAL QUALITY CONTROL

ChungNixonYuMylopoulos99

Lawrence Chung & Brian A Nixon & Eric Yu & John Mylopoulos
Non-functional Requirements in software engineering
Kluwer Acad Norwell MA 2000 ISBN 0-7923-8666-3 QA76.758 .N65 1999
=THEORY+CASESTUDYs FORMAL NFR SOFTGOALS SIGs GRAPHICS TABLES LOGIC QUALITIES REALITIES SYSTEMS TECHNIQUES
Accuracy, security, performance,
SIG:= "Softgoal Independency Graph", pp17+48+85
presenting arguments connecting statements independently of their (boolean) value: "dialectical style of reasoning".
refinements and correlations
{BREAK, HURT, UNKNOWN, HELP, MAKE}, AND, OR, EQUAL.
denied, undecided, satisficed.
Consolidates and summarizes: [MylopoulosChungNixon92] [BorgidaMylopoulosReiter93] [ChungNixonYuMylopoulos99] [MylopoulosChungYu99] [MylopoulosChungLiaoWangYu01] also see [Nixon00]

Church56

Alonzo Church
Introduction to mathematical logic: Volume I
Princeton Univ Press 1956 No17 in Princeton mathematical series
=TEXT LOGIC
Skolem normal form in section 42 &43

ChurchillBly99

Elizabeth F Churchill & Sara Bly
Virtual Environments at Work: ongoing use of MUDs in the WOrkplace
ACM SIGSOFT SE Notes V24n2(Mar 1999)pp99-107 (Proceedingd of WACC'99)
=EXPERIENCE using MUDs to aid software development
Supports: maintaining relationships+coordination+reduces time for som interaction

Chusho93

Takeshi Chusho
What makes Software Tools successful?
IEEE Software Magazine V10n5(Sep 1993)pp63-65

CiancariniFranzeMascolo00

P Ciancarini & F Franze & C Mascolo
Using a Coordination Language to Specify and Analyze Systems Containing Mobile Components
ACM TOSEM Trans Software Engineering & Methodology V9n2(Apr 2000)pp167-198
=IDEA LANGUAGE MOBILE PoliS MODEL-CHECKING TUPLE-SPACES vs CHAM UNITY

CiapessoniEtal99

Emanuelle Ciapessoni & Alberto Coen-Porisini & Ernani Crivelli & Dino Mandrioli & Piergiorgio Mirandola & Engelo Morzenti
From Formal Models to Formally Based Methods: An Industrial Experience
ACM TOSEM V8n1(Jan 1999)pp79-113 CR9906-0432
=EXPERIENCE TRIO FUNCTIONAL NONFUNCTIONAL PERFORMANCE Make haste slowly. EVOLUTION Adding formalism to existing

CicaleseRotenstreich99

Cynthia Della Torre Cicalese & Shmuel Rotenstreich
Behavioral specification of distributed component interfaces
IEEE Computer Magazine V32n7(Jul 1999)pp46-53
=THEORY COMPONENTS RELIABILITY IDL CORBA JAVA RMI
BISCOTTI::=Java+contracts

CiolkowskiLaitenbergerBiffl03

Marcus Ciolkowski & Oliver Laitenberger & Stefan Biffl
Software Reviews: The State of the Practice
IEEE Software Magazine V20n6(Nov/Dec 2003)pp46-51
=POLL 226 SQA WALKTHROUGHS INSPECTIONS ISERN IESE VISEK
- Why: to improve quality and enforce standards.
- When: 40% requirements and design, 30% code. 20..40% have regular reviews.
- What: 20% have no formal procedure for selecting what is reviewed. Individual preparation: only 40%. using checklists, ad hoc, simulation and other t echniques.
- Meeting: 40%
- Followup: 35%
- Monitor and optimize: 25% ( data collected 60%)
- Effectiveness estimate: varies from 0 to 100%. 50% in 21..60%.

ClabenHartmutWolz93

Ingo Claben & Ehrig Hartmut & Dietmar Wolz
Algebraic Specification techniques and tools for software development: The ACT approach
World Sci Pub Co River Edge NJ $38 ISBN 981-02-1227-5

Clark73

R. Lawrence Clark
A Linguistic Contribution to GOTO-less Programming
Datamation, December 1973. Reprinted in Comm ACM, April 1984
=JOKE LANGUAGES COMEFROM
proposed the comefrom statement.

ClarkB00

Bradford K Clark
Quantifying the effects of Process Improvement on Effort
IEEE Software Magazine V17n6(Nov/Dec 2000)pp65-70
=POLL ESTIMATION CMM
161 projects, ... 1 CMM level can reduce effort by 4%..11%

ClarkD00

David Clark
Are Too Many Programmers Too Narrowly Trained?
IEEE Computer Magazine V33n6(Jun 2000)pp12-15
=INTERVIEWS EDUCATION
quotes norman matloff(UCD), les hatton, constantine, davis, & roger Pressman
narrow ==> cheap&fast to hire==> inefficient&bad work
Confuses training progammers with educating computer scientists.

ClarkeEmersonSifakis09

Edmund M Clarke & E Allen Emerson & Joseph Sifakis
Model Checking: algorithmic verification and debugging
Commun ACM V52n11(Nov 2009)pp75-84 [ 1592761.1592781 ]
=HISTORY MODEL CHECKING LTL CTL CTL* MODAL LOGICS PROOF TOOLS
2007 Turing Prize Article

ClarkeGrumbergPeled99

Edmund M Clarke Jr & Orna Grumberg & Doron A Peled
Model Checking
MIT Press 1999 ISBN 0-262-03270-8 QA 76.76 V47 C553 1999
=MONOGRAPH FORMAL LOGIC CTL MODEL CHECKING SMV SPIN OBDDS KRIPKE SYMMETRY GROUPS
CSUSB cs565/656

ClarkeRosenblum06

Lori A Clarke & David S Rosenblum
A Historical perspective on runtime assertion checking in Software Development
ACM SIGSOFT Software Engineering Notes V31n3(May 2006)pp25-37
=HISTORY ASSERTIONS LOGIC PROVING DEBUGGING Ada Eiffel Anna C++ Euclid Turing
Excellent bibliography on pages 34-37

ClarkeWing96

Edmund M. Clarke & Jeannette M. Wing
Formal Methods: State of the Art and Future Directions
ACM Computing Surveys V28n4(Dec 1996)pp625-643
=SURVEY

Cleaveland79/80

James C Cleaveland
Mathematical Specification
SIGPLAN v??n??(1979 or1980) p31-41 [click here if you can fill this hole]
=DEMO formal

CleavelandParrowSteffen93

Rance Cleaveland & Joachim Parrow & Bernhard Steffen
The Concurrency Workbench: A Semantics-Based Tool for the Verification of Concurrent Systems
ACM ToPLAS V15n1(Jan 1993)pp36-72 CR (C.2.2)
Tool analysing non-sequential CCS Mu-calculus using Standard ML

CleavelandSmolkaEtal96

Rance Cleaveland & Scott A Smolka et al
Strategic Directions in Concurrency Research
ACM Computing Surveys V28n4(Dec 1996)pp607-625
=SURVEY NONSEQUENTIAL concurrency@cwi.nl

Cleland-HuangChangChristensen03

Jane Cleland-Huang & Carl K Chang & Mark Christensen
Event-Based Traceability for Managing Evolutionary Change
IEEE Trans Software Engineering V29n9(Sep 2003)pp796-810
=DEMO REQUIREMENTS PUBLISH CHANGES ARTIFACTS SUBSCRIBE DOORS Event-Notifier EBT
See [ http://re.cti.depaul.edu/ebt/ ]

Cleland-HuangEtAl07

Jane Cleland-Huang & Raffaella Settimi & Eli Romanova & Brian Berenbach & Stephen Clark
Best Practices for automated traceability
IEEE Computer Magazine V40n6(Jun 2007)pp27-35
=ADVERT POIROT REQUIREMENTS TRACEABILITY TOOL =HOWTO IMPROVE DOCUMENTATION
Detailed technical description of a tool that extracts links between documents in a software project.
Describes a model of requirements and other artifacts: from Business Goals to Feature, Business use case, system use case, component, concrete ability, release, and product.
Advice: create traceable artifacts
- Use a project glossary
- Write good requirements: correct, unambiguous, complete, prioritized, verifiable, understandable, identifiable, etc.
- Structure the documents: headlines and sections.
- Uncover/create synonyms across domains.
- Create rich content: document the domain properties that link system requirements to user requirements.
- (dick)|-this is a special case of M A Jackson's recent thinking. -- [Jackson0] [Vickers07]
Plan and introduce automatic tools/processes to maintain and/or expose traces.

Cleland-HuangMarreroBerenbach08

Jane Cleland-Huang & Will Marrero & Brian Berenbach
Goal-Centric Traceability: Using Virtual Plumblines to maintain critical Systemic qualities
IEEE Trans Software Engineering V34n5(Sep/Oct 2008)pp685-699
=CASESTUDIES REGRESSION TESTING QUALITIES KAOS QAM SIG SOFTGOALS i* ATAM GCT
GCT::acronym="Goal Centric Traceability".
Put tests for qualities into regression testing and derive tests from goals.
Tests can be done statically or by running code. But are automatically traced to impacts on quality goals.
QAM::acronym="Quality Assessment Methods", These may be manual or automatic.
They can be: executable models(simulations), Manually evaluated models, Runtime monitors, or test cases.
Develops from [Cleland-HuangEtAl07]

Cleland-HuangEtAL09

Jane Cleland-Huang & Horatiu Dumitru & Chuan Duan & Carlos Castro-Hrrera
Automated Support for managing feature requests in open forums
Commun ACM V52n10(Oct 2009)pp19-20 [ 1562764.1562784 ]
=EXPERIMENT TOOL CLUSTERING TOPICS USERS REQUESTS
Evidence that an algorithm can analyse and classify issues better than the subjects provided by submitters.

Clemenconetal96

Christian Clemencon & Bodhisattwa Mukherjee & Karsten Schan
Distributed Shared Abstractions(DSA) on Multiprocessors
IEEE Trans Soft Eng VSE22n2(Feb 1996)pp132-152
=DEMO NET NONSEQUENTIAL DATA ABSTRACTION HARDWARE

ClementBesselaar93

Andrew Clement & Peter Van den Besselaar
A retrospective look at PD Projects
Comm ACM V36n6(Jun 1993)pp29-37
=POLL EXPERIENCE Participatory DESIGN JAD USER STAKEHOLDER PD REQUIREMENTS
PD:="Participatory Design".
Took 25 published (at IFIP) projects and got 15 response to questionaire. Selected 10 most substantive.
Claims there had been hundreds of PD projects.
Results include temporary empowerment, technologists thinking outside of the box, mostly accurate requirements -- but not necessarily in the market.
PD is a complex process with far reaching implications to an organization and so involves juggling many competing forces.
Need to address immediate needs and have an insider.
All goals, plans, and rationales have to be continuously discussed and revized.
Politics!

ClementsEtal02

Paul Clements & David Garlan & Len Bass & Judith Stafford & Robert Nord & James Ivers & Reed Little
Documenting Software Architectures: Views and beyond
Pearson Education, Upper Saddle River NJ 2002 ISBN 0201703726 CR 0411-1291
=UNREAD ARCHITECTURE VIEWS STYLES UML
Notes [click here if you can fill this hole]

ClementsJonesNorthropMcGrego05

Paul G Clements & Lawrence G Jones & Linda M Northrop & John D McGregor
Project Management in a Software Product Line Organization
IEEE Software Magazine V22n5(Sep/Oct 2005)pp54-62
=CASE STUDY PRODUCT LINE DOMAIN MANAGEMENT ASSETS VARIATIONS EVOLUTION REUSE
Though similar maintaining and extending a product line requires some changes in traditional approaches.
Lists similarities and differences.
Adding a product to an existing line is based on the assembly of existing assets.
Choosing the correct new product involves assessing both the existing assets and products as well as the traditional analysis.

Cline96

Marshall P Cline
The Pros and Cons of Adopting and Applying Design Patterns in the Real World
Comm ACM V39n10(Oct 1996)pp47-49
Objects allow hinges and patterns resolve dilemmas in nonfunctional requirements

Cloyd01

Molly Hammar Cloyd
Designing User-Centered Web applications in web time
IEEE Software Magazine V18n1(Jan/Feb 2000)pp62-69
=EXPERIENCE FAST WEB B2B APPLICATIONS USER
How to introduce human factors methods into a reluctant development organization.
Usability and first-time-to-market are now "must have" qualities.
1: user, 2: low tech prototypes prove concept, 3: storyboard, 4: module = use case+screen mockups, 5: others develop modules.

Coad88

P Coad Jr
Design Approaches & DoD-STD-2167
ACM SIGSOFT Software Engineering Notes v12n1 (Jan 1987)p50
=ESSAY lifecycle

Coad90

Peter Coad
Object Oriented Analysis
Object Int & Ed Yourdon Press Prentice Hall NJ
=HANDBOOK object-oriented SAD DFD ERD STD

Coad92

Peter Coad
Object-Oriented Patterns
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp152-159

Coadetal95

Peter Coad with David North & Mark Mayfield
Object Models: Strategies & Patterns & Applications
Prentice Hall 1995 $49 ISBN 0-13-108614-6
CR9607-0462:"based on talks?" ref in Software Development Magazine(Jul 1995)p35 [Coadetal95a]
with disk

Coadetal95a

Peter Coad(mailto: coad@oi.com) with David North(dnorth@aig.com) & Mark Mayfield(mayfield@oi.com)
title
Software Development Magazine(Oct 1995)pp39-50 [Coadetal95]
DEMO OBJECT-ORIENTED MODELS SCENARIOS strategies tactics

CoadLefebvre99

Peter Coad & Eric Lefebvre
Modeling in Color
Software Development Magazine V7n3(Mar 1999)pp39-140
=THEORY use Color for common analysis class stereotypes: role, time, thing, description

CoadMayfield97

Peter Coad & Mark Mayfield
Designing with Interfaces for Java
Software Development V5n4(Apr 1997)pp47-48+50+52+54

CoadNorthMayfield97

Peter Coad & David North & Mark Mayfield
Object Models: Strategies, Patterns, and Applications
Yourdon Press(Prentice Hall Int) 1997 ISBN 0-13-840117 $48
=TEXT OO MODELS OMT UML PATTERNS
reviewed ACM SIGSOFT Software Eng Notes V23n3(May 1998)pp123-126 "cute style"
148 strategies + 31 design patterns
Playground::= See http://ww.oi.com/playground.htm

CoadNicola93

Peter Coad & Jill Nicola
Object-oriented Programming
Yourdon Press Englewood Cliffs NJ 1993 ISBN 0-13-032616-X CR9502-0058
=ADVERT

CoadYourdon91

Peter Coad & Edward Yourdon
Object Oriented Design
Yourdon Press Prentice Hall NJ 1991
=HANDBOOK object-oriented coupling and cohesion
problem domain+HCI+task management+data management
Review: Alejandro Teruel IEEE Computer Magazine V25n3(Mar 1992)p125
CR9404-0198

CoadyKiczalesFeeleySmolyn01

Yvonne Coady & Gregor Kiczales & Mike Feeley & Greg Smolyn (UBC)
Using AspectC to improve Modularity of Path-Specific Customization in Operating System Code
ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp88-98
=CASESTUDY ASPECTS MODULARITY FreeBSD C
Layered architectures work well with OS's but some decisions can not be confined to a single layer but drill down through many layers. Aspects let this be handled in a modular way by encapsulating cross-cutting concerns.

CobbEtal98

Maria A Cobb & Harold Foley III & Ruth Wilson & Miyi Chung & Kevin B Shaw
An OO Database Migrates to the Web
IEEE Software magazine V15n3(May/Jun 1998)pp22-30
=EXPERIENCE OBJECT-ORIENTED Geographic DATA CORBA JAVA SMALLTALK IDL NET/WEB

CobleighAvruninClarke08

Jamieson M Cobleigh & Gregory Avrunin & Lori A Clarke
Breaking up is Hard to do: An Evaluation of Automated Assume-Guarantee Reasoning
=EXPERIMENT TOOL AUTOMATED VERIFICATION NONSEQUENTIAL Ada Code FLAVERS LTSA
ACM TOSEM Trans Software Eng & Methodology V17n2(Apr 2008)#7pp1-52
Given a system with two or parallel subsystems can we compute the necessary and sufficient conditions for the whole to perform as specified.
FSF::="Finite State Verification".
Using the L* algorithm to find assume-guarantee conditions can slow the process but doesn't waste memory.
Some assume-guarantee conditions discovered where large: 250 states. Not known if this is the best one.

Cockburn96

Alistair Cockburn
The 3 Rings of Object Technology
Object Magazine (Nov 1996) pp20-22
DATA MODEL vs OBJECT-ORIENTED: structure vs changes. Modeling data on disk vs data in organization
conceptual+logical+physical. Date model quicker. SCENARIOS:channel effort
test completeness and variations. [CRC] encourages creativity.

Cockburn00

Alistair Cockburn [ arc@acm.org ]
Characterizing People as Non-Linear, First-Order Components in Software Development
Humans & Technology, HAY Technical Report 1999.03(Oct 21 1999) and Proc SCI/ISAS2000 VI pp728-736 [SCI00]
=EXPERIENCE 20 projects PEOPLE AGILITY ONESIZE
A commonly observed pattern by methodologists and tool smiths
1. The people on the projects were not interested in learning our system.
2. They were successfully able to ignore us, and were still delivering software, anyway.
3. Almost any methodology can be made to work on some project.
4. Any methodology can manage to fail on some project.
5. Heavy processes can be successful.
6. Light processes are more often successful, and more importantly, the people on those projects credit the success to the lightness of the methodology.
7. people are
  1. are communicating beings, doing best face-to-face, in person, with real-time question and answer.
  2. have trouble acting consistently over time.
  3. are highly variable, varying from day to day and place to place.
  4. generally want to be good citizens, are good at looking around, taking initiative, and doing "whatever is needed"
  5. need both think time and communicating opportunities.
  6. work well from examples.
  7. prefer to fail conservatively than to risk succeeding differently
  8. prefer to invent than to research
  9. can only keep a small amount in their heads, and do make mistakes
  10. find it hard to change their habits.
8. Individual personalities easily dominate a project.
9. A person's personality profile strongly affects their ability to perform specific assignments.
10. paper documentation is the least effective communication medium available.

Cockburn 00b

Alistair Cockburn
selecting a project's methodoloist
IEEE Software Magazine V17n3(Jul/Aug 2000)pp64-71
=IDEA PEOPLE before MEHODS
size and criticallity(fear) drives need for bigger methods.
nonlinear method->cost, d cost/d method is large.
consider priorities and reconsider them later.
face-to-face communicates better than paprr

Cockburn00c

Alistair Cockburn
Balancing Lightness with Sufficiency
Cutter IT Journal V13n11(Nov 2000)pp26-33
=ARTICLE METHODS PROCESSES PROJECT
p26. "software development can be thought of as a cooperative game of invention and communication with limited resources." [ game ]
Start with closest fitting methods. Need to tune and prune procedures to fit particular projects needs as they evolve. Hunting for sweet spots. No substitute for rapid feedback.
technology >< team size >< damage potential >< culture. See [Cockburn00?]
What is sufficient for now may be insufficient when the team is gone.
A team has an insufficient methodology when it does not communicate often or well enough for its members to carry out their work.
Crystal_Clear::= See http://members.aol.com/humansandt/crystal/clear

Cockburn02

Alistair Cockburn
Games Progremmers Play
Software Development Magazine V10n2(Feb 2002)pp28-32
=IDEA PROCESS GAME THEORY
Software development considered as a game of invention and communication.
Primary goal: deliver software that fits problem space.
Secondary goal: leave tracks to make the next game easier to win.

Cockburn02b

Alistair Cockburn
Use Cases, ten years later
STQE Magazine (Mar/Apr 2002) [ Use+cases,+ten+years+later ]
=HISTORY =HOWTO USE CASES FORMALLITY Brief Casual Fully dressed STAKEHOLDERS GOALS Theory
- Use cases about one type of user and their goals -- the Prime Actor.
- Use cases are about the user's goals and the ways they try to fulfill these. Steps in scenarios achieve small goals on the way to a big goal. And Goals have different scopes/levels/sizes.
- Because there are actions that are invisible to the Prime Actor there must be other stakeholders involved with different interests. The Prime Actor want to get candy but the owner of the candy machine wants to get money for the candy... So there are contracts that the system must follow.
- There is more value in thinking out the alternative scenarios than the main success scenario.
How people reacted to use cases...
Some peole like formal structured use cases but others dislike them.
Advice: Keep them simple. Keep them essential/logical. Use multiple formats: Brief, Casual, Fully Dressed.
Mistakes: too many physical details, main use case too long and detailed.

Cockburn03

Alistair Cockburn
Agile Software Development
Addison-Wesley Boston MA 2001 ISBN 0-201-69969-9 US$34.99
Reviewed IEEE Software Magazine V20n1(Jan/Feb 2003)pp97-98 and [CR] 0305-0454 [CR] 0307-0652
=HANDBOOK IDEAS PROCESS AGILE
Communication+collaboration+insight+study+practice+experimentation

CockburnHighsmith01

Alistair Cockburn & Jim Highsmith
what
IEEE Computer Magazine V34n11(Nov 2001)pp131-133
=ADVERT AGILE PEOPLE trump Process

CODASYL71

CODASYL Database Task Group
CODASYL Database Task Group report
ACM NY NY 1971
=STANDARD data logic ENTITIES SETS(FUNCTIONS)

Codd70

?? Codd
A Relational Model for Large Shared Data Banks
Commun ACM 13 6 (Jun 1970) pp 377-387 (also CACM25)
=DEMO data structures System

Codd82

?? Codd
Relational Databases: a practical foundation for productivity
Commun ACM v25 n2 Feb82 pp109-117
=DEMO data structures

Codenieetal97

Wim Codenie & Koen De Hodt & Patrick Steyaert & Arlette Vercammen
From Custom Applications to Domain-Specific Frameworks
Comm ACM V10n10(Oct 1997)pp71-77
=EXPERIENCE REUSE GENERIC
need more than fill-in-the-blanks (hotspots); must document how-to+effort of reuse as a contract

Codephirst07

Colin Codephirst (alias) & Nail Maiden (ed)
From the horse's mouth
IEEE Software Magazine V24n6(Nov/Dec 2007)pp21-23
=JOKE REQUIREMENTS SPECIFICATION WORST PRACTICES

Codephirst09

Colin Codephirst (alias) & Nail Maiden (ed)
Where have all the stencils gone?
IEEE Software Magazine V26n4(Jul/Aug 2009)pp
=HISTORY STENCILS FLOWCHARTS =JOKE REQUIREMENTS
Technique was easy and fun to use, impressed the stakeholders, and contributed little to understanding the problem.
Compare [Codephirst07]

Coen-Porisinietal91

Alberto Coen-Porisini & Flavio De Paoli & Carlo Ghezzi & Dino Mandrioli
Software Specialization Via Symbolic Execution
IEEE Trans SE-17 n9 (Sep 1991)pp884-899 CR9302-0092
=DEMO logic symbolic execution re-engineering specialization

Coen-Porisinietal94

Alberto Coen-Porisini &Richard A Kemerer & Carlo Ghezzi & Dino Mandrioli
A Formal Framework for ASTRAL Intralevel Proof Obligations
IEEE Trans on Soft Eng vSE-20n8(Aug 1994)pp548-561
=MATHEMATICAL PROOF FORMAL TIMING FSMS

Coen-Porisinietal97

Alberto Coen-Porisini & Carlo Ghezzi & Richard A Kemerer
Specification of Realtime Systems using ASTRAL
IEEE Trans on Soft Eng vSE-20n8(Aug 1994)pp548-561
=ADVERT SPECIFICATION TIMING LANGUAGE [Coen-Porisinietal94]

Cohen79

?? Cohen
Non-Deterministic Algorithms
ACM Comp Surveys 11 2 (Jun 1979) pp79-94
=SURVEY non-sequential optimization

Cohen90

Jacqes Cohen
Constraint Logic Programming Languages
Commun ACM V33n7(Jul 1990)pp52-68
=DEMO CLP non-sequential AI

Cohen04

Jaques Cohen
Bioinformatics: an Introduction for computer Scientists
ACM Comput Surveys V36n2(Jun 2004)pp122-158 [ 1031120.1031122 ]
=SURVEY BIOINFORMATICS BIOLOGY

CohenBirkinGarfieldWebb04

Cynthia F Cohen & Stanley J Birkin & Monica J Garfield & Harold W Webb
Managing Conflict in Software Testing
Commun ACM V47n1(Jan 2004)pp76-81
=INTERVIEWS 10 TESTERS PEOPLE MANAGEMENT PROCESS
Uncovered (obvious) sources of conflict and proposes resolutions.
Example: Time is scarce. So: Plan for overruns, manage schedule changes, learn from experience.
p79: Managers matter: "The developers fired the manager".

CohenCampbell93

Donald Cohen & Neil Campbell
Automating Relational Operations on Data Structures
IEEE Software Magazine(May 1993)pp53-59 Example: topological sort on page 54
1. do( x' in graph & no y in graph(y before x);
2. out:!x; graph:~x;
3. )

Cohenetal97

Don Cohen & Martin S Feather & K Narayanaswamy & Stephen S Fickas
Automatic Monitoring of Software Requirements [ICSE'97]
=IDEA FLEA AMOS

CohenFeldman04

Yossi Cohen & Yishai A Feldman Automatic High-Quality Reengineering of Database Programs by abstraction, Transformation and Reimplementation
ACM TOSEM Trans Software Eng & Methodology V12n3(Jul 2003)pp285-316
=EXPERIENCE TOOL MIDAS REENGINEER network to RELATIONAL DATAbase COBOL SQL PERFO RMANCE
simple translation of procedural code to relational/SQL leads to slow data base response. Need to abstract the plan for the legacy code. Used Plan Calculus with Query graphs.

CohenHarwoodJackson86

B Cohen & W T Harwood & M I Jackson
The specification of Complex cystems
Addison Wesley Wokingham UK 1986
UCR Rivera QA76.9.s88 1986
=theory nonsequential specification VDM

Cohn04

Mike Cohn
User Stories Applied: for agile software development
Addison-Wesley 2004 ISBN 0-321-20568-5
=UNREAD USER REQUIREMENTS AGILE XP

CohnFord03

Mike Cohn & Doris Ford
Introducing an agile Process to an Organization
IEEE Computer Magazine V36n6(Jun 2003)pp74-78
=EXPERIENCE AGILE PROCESS PEOPLE RISKS Scrum programmer:
1. initially need a balance of scepticism and enthusiasm. Need top talent.
2. Can initially classify Scrum sprints as "prototyping","requirements capture, ... "stabilization".
3. Do not use a distributed development team initially.... especially after a merger. culture clash.
4. Some initially see agile as micromanagment.
Testers: don't let them program! If they want to then hire them as programmers! Testing is up front and managers get involved.
Manager problems: promise customers what? What progress now? How does it effect xyz? When is the end of the project?
Involve Human Resources! Performance reviews without predicted deliverables?

CoistagliolaEtal06

Gennaro Coistagliola & Vincenzo Deufemia & Filomena Ferrucci & Carmine Gravino
Constructing Meta-CASE workbenches by exploiting visual language generators
IEEE Trans Software Engineering V32n3(Mar 2006)pp156-175
=DEMO GRAPHIC TOOLS for PROCESSES CASE UML GXL MEG WoG
GXL::XML="Graph eXchange Language".
MEG::Tool="Modeling Environment Generator".
WoG::Tool="WOrkbench Generator".
VLDesk::="Visual Language Desk"
Figure 1 shows Cannallen's UML icon's for web components.
Uses analysis/robustness diagrams with entity+interface+control classes.
Examples of UML models of tools: meta-CASE.
In usecase diagram replaces include by INCLUDED and extends by EXTENDED.
Adds artifacts to activity diagrams and adds a dashed arrow indicating a constraints between artifacts.

ColbergThomborson02

Christian S Colberg & Clark Thomborson
Watermarking, Tamper-proofing, and Obfuscation -- tools for Software Protection
IEEE Trans Software Engineering V28n8(Aug 2002)pp735-746
=IDEA SECURITY RISKS ETHICS TECHNICAL Intellectual Property
Security has has long been about protecting host systems from attacks by mobile code. This articles looks at protecting mobile code from abuse by its host!

Colbert02

Ed Colbert
Avionics architecture Description Language ( AADL )
IEEE Los Angeles Chapter Bulletin (Jan 2002) p6
=ABSTRACT DESIGN LANGUAGE UML MetaH TOOLS STANDARD SAE Automotive avionic
Full paper presented at chapter meeting 8pm Jan 9th 2002, Los Angeles.

Coleman79

Derek Coleman
A Structured Programming Approach to Data
Springer Verlag NY 1979
=DEMO sequential DDD language data

Colemanetal94

Derek Coleman & Patrick Arnold & Stephanie Bodoff & Helena Gilchrist & Fiona Hayes & Paul Jeremaes
Object-oriented development: the FUSION Method
Prentice Hall Englewood Cliffs NJ 1994 ISBN 0-13-338823-9 CR9502-0058
=HOWTO OBJECT_ORIENTED MODEL FORMAL CRC BOOCH REGULAR ERD OMT COLLABORATION HP
Combination of OMT Booch CRC and some formal methods.
Prefigures UML and RUP, Subsumed in OPEN. Uses regular expressions to express dynamics.
Unusually precise definitions!

ColemanHayesBear92

Derek Coleman & Fiona Hayes & Stephen Bear
Introducing ObjectCharts or How to Use Statecharts in Object-Oriented Design
IEEE Trans SE-18n1(Jan 1992)pp9-18 CR9301-0026
=IDEA ObjectCharts OBJECT GRAPHIC STD STATECHART Harel

CollierDeMarcoFearey96

Bonnie Collier & Tom DeMarco & Peter Fearey
A Defined Process for Project Postmortem Review
IEEE Software Magazine VSE13N4(Jul 1996)pp65-72
How to do a Postmortem::= anonymous survey; collect objective data; debriefing; project history day; publish; act [ postmortems.html ]

Collins02

Rosann Webb Collins
Software localization for Internet software: Issues and methods.
IEEE Software Magazine V19n2(Mar/Apr 2002)pp74-80
=EXPERIENCE PROBLEMS INTERNATIONAL WEB/NET
examples: date formats, one graphic: meaningful, meaningless, holy, or even obscene!

CollinsBicknell98

Tony Collins & David Bicknell
Crash: learning from the world's worst computer disasters
Simon and Schuster London Uk 1998 ISBN 0-684-81687-3
=ANECDOTE RISK COST PQRST HISTORY 1830-1998 UK USA ...
Simplify and standardize before you computerise.
Cost is three times bigger than your most meticulous estimate.
Big systems fail. Disastors happen when techies have control. Especially if they have power.
Make sure you have a Plan B for when a new system fails -- even if all the tests and diligence seem to make failure impossible. Run old in parallel with old. Do one piece at a time.
A computerized system that depends on its users acting perfectly or differently will fail. Plan for human errors and shortcuts.
Cancel software development that will have no tangible benefits within 6.months .. 1.year. Instead buy COTS and change the organisation to fit it.
Customers must be experts and sceptics. Know what is needed here and what has been done elsewhere.
Better to do it yourself than use consultants or even local MIS.
Avoid big-bangs. Go incremental.
Normally a project fails and neither the customers nor the suppliers are to blame - they say. Lawyers profit.
Don't set or accept artificially tight deadlines.
Ten deadly sins: overambition, pride, presumption, credulity, consultancy, modification, concealment, buck-passing, lawyers.
Suggestions:
1. CEO must remain in control and be reay to terminate project.
2. First tune existing system to 80% of capacity and simplify business procedures to 2 sides of A4 paper.
3. Proceed warily. Put business ahead of technology. Look for a system that needs no changes and is minimally proprietary. Choose Lowest level technology: ( PCs < workstations/minis < mainframes )
4. Get a complete list of all consultant's clients.
5. Demand clear explanations - no meaningless jargon.
6. Technical designers should work as or with end-users for a week/month/year before designing a new system.
7. Freeze design before developing new software. Suppliers will still misundertand it. Further features or users will be added after system has succeeded and not before.
8. Fixed price contract with consultant: We won't pay until it works to our satisfaction. Two stages: up to a complete frozen written spec., and after spec. if it beneficial in < 6 months.
9. Have evidence system can handle expected loads/demands.
10. Include data design and setup costs. Look for cheap but reliable ways to populate any databases
11. Go live in small steps.
12. No miracles! Instead the new system will be worse than the old, but slowly some benefits will appear.
13. Big systems fail. Keep It Simple. No more than one year at a time. Best if less than 6 months. Computerize one bit at a time.
14. Expect to throw the first attempt away.

Collinsetal94

W Robert Collins Keith W Miller & Bethany J Spielman & Phillip Wheery
How Good is Good Enough? An Ethical Analysis of Software Construction and Use
Commun ACM V37n3(Jan 1994)pp81-91

CollofelloBuck87

James S Collofello & Jeffrey J Buck
Software Quality Assurance for Maintenance
IEEE Software V4n5(Sep 1987)pp46-51
=REPORT SQA QUALITY

Colmerauer90

Alain Colmerauer
An Introduction to Prolog III
Commun ACM V33n7(Jul 1990)pp68-90
=LRM logic-programming non-sequential AI

Colonna93

Jean-Francois Colonna
The Subjectivity of Computers(Letter)
Commun ACM V36n8(Aug 1993)pp15-18
= ESSAY RISKS

Colwell02

Bob Colwell
Near Misses: Murphy's Law Is Wrong
IEEE Computer Magazine V35n4(Apr 2002)pp9-12
=ESSAY EXPERIENCE RISKS ENGINEERING vs SCIENCE
Learning from mistakes. eg. Challenger. Hubble. Mars Climate Orbiter etc.
Engineers often can not afford a replicated scientific experiment -- especially testing something to destruction!
"To engineer is human" -- Petroski85: never make the same mistake twice.
"Failure is not an option" -- Gene Kranz 2000: NASA pushing the envelope means design mistakes so need test pilots.
Erroneous sqrt vs 1.5 safety factor in aircraft wing design.
Engineers must do two different things: design to achieve perfection and design as though errors are going to be made.
A pattern: major failure occurs in unusual circumstances: three mile island & Chernobyl. Often as a result of humans in the loop.
Perrow 1999: Normal accidents: Living with High-Risk Technologies: Coupling and interactions make systems harder to control and understand.
James Chiles 2001: Inviting Disasters: Lessons from the Edge of Technology: Murphy is wrong -- things can fail to go wrong many times before a big disaster happens in the same way. "Near misses are nature's way of telling us something's wrong, and we'd better fix it fast."
However: repeatedly getting away with something makes us feel that it is safe. The near disaster becomes the norm. Hence the requirements a bent a bit.
Disasters are averted by deep understanding of the system and all its quirks plus the ability to keep ones head when all else are losing their's. Example lightening hitting Apollo 12.
Emotional stress effects judgment.
Beware management manipulation: "do you want your boss to know how stupid you are?", "We go with or without you"(sign off and they will blame you). "Take off your engineering hat and think like a manager..", "Ships are not supposed to be docked safely in the harbor all the time".
User friendly designs can hide how close to disaster the user is/was.

Colwell03

Bob Colwell
Design Reviews
IEEE Computer Magazine V36n10(Oct 2003)pp8-10 + letter V36n12(Dec 2003)p6-7
=ANECDOTES PEOPLE DESIGN QUALITY INSPECTION SQA
Article describes some disastrous design reviews.
Jesse N Alexander's letter gives some rules:
1. Reviews (informal high level discussion) are not inspections(formal and detailed error hunt).
2. No Managers allowed.
3. Meeting metrics must measure the process not the people.
4. Define the Roles.
5. Criticize the design not the designer.
6. No design allowed.
Colwell04
1. Bob Colwell
2. Brainstorming, influence, and icebergs
3. IEEE Computer Magazine V37n4(Apr 2004)pp9-12
4. =EXPERIENCE PEOPLE MEETINGS

Colwell04b

Bob Colwell
Interface Quotas and Internet-Derived Value
IEEE Computer Magazine V37n12(Dec 2004)pp10-11
=ESSAY USER SAFETY SIMPLICITY WEB/NET
Keep user interfaces similar to old & thouqht-free.
Use internet to simplify & unify user interfaces.

Comaford95

Christine Comaford
What's Wrong with Software Development?
Software Development Magazine(Nov 1995)pp27..28
9 RISKS problems and solutions
1. 1. understand your business better
2. 2. understand your users better
3. 3. manage developers better
4. 4. better infrastructure for applications
5. 5. understand the real mening of RAD
6. 6. more reliable estimation for client/server development
7. 7. control prototypes
8. 8. better architectures
9. 9. better testing

CommonerHoltEvenPnueli71

F Commoner & ?? Holt & ?? Even & ?? Pnueli
Marked Directed Graphs
Jnl Computer and Systems Sciences V5pp511-523
=THEORY formal graphic petri nets non-sequential
My reduction of this work is in [ Marked%20Directed%20Graphs in math_76_Concurency ]

ComputerworldStaff05

Computerworld Staff
Computerworld Development Survey gives nod to C#
Computerworld (Mar 28 2005) [ 0,4814,100542,00.html ]
=POLL LANGUAGES C# JAVA VB JavaScript C++ API .Net IDE Linux Open Source
Summary by ACM TechNews [ item8 in 0404m ]
50% use some open source code.
72% C#, 66% Java, 62% Visual Basic, 54% C++, 50% JavaScript...
58% Web Services being developed

Conallen98

Jim Conallen
Modeling Web Application Design with UML
Rational [ dynamic.jtmpl?doc_key=100462 ]
new stereotypes: server, client, xml, form, target, ...

Conallen99

Jim Conallen(jconalle@Rational.com)
Modeling web application architectures with UML
Commun ACM V42n10(Oct 1999)pp63-70 in [Booch99]
=ESSAY WWW/NET DESIGN UML stereotypes vs [RMM]
Also see [Conallen98] on the WWW
web application implement business logic and when accessed changes the state of the business. Separate business ADM from presentation UI.
ADM:=Analysis/Design model
classes: separate client side pages from server side pages. serverside builds clientside.
components: Iconic stereotypes
stereotypes for: server pages, client pages, links,builds, form, parts of forms, frame, target, applets, javascript, activex,...
Details to be announced [ http://www.rational.com/ ]

Conallen01

Jim Conallen
Modeling Web-Tie Components
Software Development Magazine V9n1(Jan 2001)pp49-55
=ADVERT WAE MODEL WWW UML
WAE := Web Application Extension.
Proposes new sereotype: <<virtual root>>, <dynamic page>>, <<HTMLpage>>, <<active Server page>>, <<Java Server Page>, <Servlet>>, <<client page>>, <<server page>>, <<link>, <<build>>, <<submit>>, <<redirect>>
Note: uses dependency arrows backwards and associations for behaviorial dependencies.
Compare with [Conallen99]

Conallen02

Jim Conallen
Building Web Applications with UML (2nd edn.).
Addison-Wesley Pearson Boston MA 2002 ISBN 0-201-73038-3 [CR] 0305-0332
=TEXT WEB/NET HTML UML USER UX PQRST XML workflows process JavaScript Java ActiveX/COM RMI/IIOP DCOM UDDI SOAP WSDL
A thorough coverage of web site development using UML based on authors own practice and experience.
WAE::="Web Application Extension", not OMG standard but Rational Profile.
Uses statecharts to map out transitions between web pages.
UX::="User experience".
Uses the Objectory icons for Interface, Control, and Entity objects.
Describes development Processes using UML but does not use OMG SoftProc Modelling02-11-14.pdf but Rational's 27070_BusinessModeling.pdf
See [Conallen01] [Conallen00] [Conallen99] [Conallen98]

ConboyCoyleWang11

Kieran Conboy & Sharon Coyle & Xiaofeng Wang
People over Process: key challenges in agile development
IEEE Software Magazine V28n4(Jul/Aug 2011)pp48-57
=POLL 27 PROJECTS AGILE PROBLEMS PRACTICES
Good table defining agility.
Transparency causes fear: provide alternative feedback, provide mentors, pairing.
(dick)|-Also control big mouths!
Every body must master all trades: pairing and rotation, allow self-assignment for learning, perhaps reintroduce specialist roles when it would help team.
More social skills: training using own examples, add documentation to communication.
Lack of business/domain knowledge: enterprise training+interactive niche training modules, hire tech+business skills.
Need to adopt agile values and principles as well as practices: many get trained or go to conference, coaching and championing, cross-team observation, assess values not practice.
Motivation: include motivated in each team, collect and share success stories.
Devolved decision-making: sharing and learning, democratic voting, manager as facilitator.
Need agile compliant performance evaluation: bredth not depth, 360 degree evaluation.
Recruitment: special processes, team recruiting, put new graduates on agile projects to learn hands-on.

ConboyFitzgerald11

Kieran Conboy & Brian Fitzgerald
Method and Developer characteristics for agile method tailoring: a study of XP expert opinion
ACM TOSEM Trans Software Eng & Methodology V20n1(Jan 2011)#2.1-30 [ 1767751.1767753 ]
=INTERVIEWS 16 XP EXPERTS 16 PRACTITIONERS AGILE TAILORING
XP is a rigid process that is never completely adopted.
Tailoring proceeds ad hoc and backwards -- adding practices as desired.
Table II. Research needed to clarify when XP is good, what parts are dependent, develop a rationale for each practice, ...
Table III. Advice to those about to adopt a process/method
1. Formally analyze your situation, before the project starts, to see if the method fits.
2. Involve all the stakeholders.
3. What are the organizational limits on adopting the process?
4. Train before you try it out. Accept/reject a practice after trying it.
5. Include practical training before tailoring.
RUP is not mentioned. But comes with tailoring instructions.

ConcasEtAl11

Giulio Concas & Michele Marchesi & Alessandro Murgia & Roberto Tonelli & Ivana Turnu
On the distribution of bugs in the Eclipse system
IEEE Trans Software Engineering V37n6(Nov/Dec 2011)pp872-877
=EMPIRICAL BUG FIX STATISTICS DEFECTS MODELS ECLIPSE Yule-Simon
Reports on attempts to match bug fix stats to 4 statitical models. One fits very well.
Apparently bugs like company -- fixes tend to be in modules that have fixed more often before. The Yule-Simon model.
This means that the Yule Simon distribution fits the number of bugs per module very well indeed.
p(x)=p0 * Β(x+c, α) / Β(h0+c, α),
Β(a,b)::= Γ(a)*Γ(b) / Γ(a+b).
Compare [ConcasEtAl07] on other OO Metrics.

ConcasEtAl07

Giulio Concas & Michele Marchesi & Sandro Pinna & Nicola Serra
Power-laws in a large Object-Oriented Software System
IEEE Trans Software Engineering V33n10(Oct 2007)pp687-708
=EMPIRICAL STATISTICS OBJECT-ORIENTED METRICS Pareto Log-normal Yule Power-law POWER LAWs
Measured metrics on three large OO development tools to determine distributions of properties. Found patterns: most metrics have a log-normal or Pareto distribution.
Quoted theories for these distributions.
Noted that for these distributions extreme values are more likely than the normal/chi-square/t family of distributions. The mean value is not a good estimated of position.
Basic process: number of entities have a numeric property. Entities are picked at random and the chosen entities property is increased. How many entities will have a given range of properties?
If the each entity has the same chance and the same change is made the resulting distribution is binomial.
If the size of the increase depends on the value of the property the distribution is log-normal.
(Yule process): If the increase is fixed but the chance if the entity being chosen depends on the property value then the distribution is Pareto.
(log-normal): p(x) = if(x<0, 0, (1/sqrt(2*π))*exp(-(ln(x)-μ)**2/(2*σ**2))).
Example metrics: #methods/class, #all instance variables/class, #LOC/class, class out-degree (see note below).
(Pareto): p(x) = if(x<xmin, 0, (α*(x/xmin)**(-α)/xmin)).
Example Metrics: #Inst vars/class, #subclasses, inst variable names, method names and calls, LOC/method, class in-degree.
Refers to H Simon Biometrica V42 pp425-440 1955 and Newman Cont Physics V46 pp323-351 2005.
Notes that the class outdegree is correlated with the class LOC and so outdegree/LOC has a Gamma distribution.
More see [LouridasSpinellisVlachos08] [ConcasEtAl11]

ConcepcionBottingScroggins00

Arturo I Concepcion & Richard J Botting & Darryl D Scroggins
ROOT Project: An Integration of an OOA/D Methodology in the Computer Science Curriculum
Proc SCI/ISAS2000 V2 pp401-405 [SCI00]
=EXPERIENCE OBJECT-ORIENTED EDUCATION

ConcepcionLinSimon99

Arturo I Concepcion & Sunny Lin Scott J Simon
The RMT(Recursive Multi-Threded) Tool: A Computer Aided Software Engineering Tool for Monitoring and Predicting Software Development Progress
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp660-663
=DEMO TOOL PROCESS MANAGEMENT

ConcepcionZeigler87

Arturo I Concepcion & Bernard P Zeigler
DEVS Formalism: A Framework for Hierarchical Model Development
IEEE Trans Soft Eng VSE-14n2(Feb 1988)pp228-241
=DEMO hardware performance top-down simulation formal graphics

Cone06

Edward Cone
Scott Rosenberg: What Makes Software So Hard
CIO Insight (Jan 8th 2007) Zipf-Davis URL [ 0,1540,2079462,00.asp ]
=REVIEW EXPERIENCE Salon ITERATIVE
Book: Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software (Crown, 2007)
"people have succeeded in creating amazing software systems that do work, and do serve people's needs....So it's doable. But when you pick up the rock and look underneath the surface of every one of those systems, you find stories of delay and difficulty and problems. "

Conklin96

Peter F Conklin
Enrollment Management: Managing the Alpha AXP Program
IEEE Software Magazine VSE13N4(Jul 1996)pp53-64
=EXPERIENCE PEOPLE MANAGEMENT MOTIVATION
motivate by
- shared vision & complete committed delegation
- inspect and provide positive feedback
- acknowledge all progress(public & personal) and learning

ConklinJ06

Jeff Conklin
Dialogue mapping: Building shared understanding of wiked problems
John Wiley NY NY 2006 ISBN 047017686 CR 0811-1059
=UNREAD =ADVERT =MANUAL IBIS Compendium STAKEHOLDERS
Compare [DenningYaholkovsky08]

ConnellShafer95

John Connel & Linda J Shafer
Object-oriented rapid prototyping
Yourdon Press NJ $39.40 ISBN 0-13-629643-2 CR9603-0154
=HANDBOOK Object-oriented RAD

ConnollyBegg04

Thomas Connolly & Carolyn Begg
Database Systems(4th edn)
Pearson Education Harlow Essex UK 2005
=TEXT DATA PQRST
Comprehensive & detailed

Conrad06a

Paul Jefferson Conrad
Analysis of PSP-Like Processes for Software Engineering
CSUSB CSci Masters Thesis Spring 2006
=SURVEY =POLL PSP STUDENT PROCESS TOOLS
How can Watts Humphrey's Personal Software Processes be used at in the computer science department at CSUSB?
1. Abstract
2. The PSP, Personal Software Process, is introduced to Computer Science graduate students in Software Engineering (CS655). The purpose of introducing PSP to Computer Science students is to allow students to enhance their coding skills and documentation. PSP is the leading approach for software developers to improve their own software development skills. However, the PSP data collection process is a time consuming task and error prone. The purpose of this thesis is to provide the California State University, San Bernardino Department of Computer Science with an analysis and recommended solution to improving the software development process of graduating Computer Science students.

Conrad06b

Paul Jefferson Conrad
What
CSUSB CSci Technical Report #1 Spring 2006 [ cs690/20060519PaulConrad.html ]
=IDEA PSP STUDENT PROCESS TOOLS Eclipse
Using an integrated development environments with a PSP plugin can improve the education of Computer Science students.

ConradiDyba01

Reidar Conradi & Tore Dyba
An Empirical study on the utility of formal routines to transfer knowledge and experience
ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp268-276
=POLL PEOPLE PROCESS IMPROVEMENT MANAGEMENT vs DEVELOPERS
Written process is doubted by developers BUT trusted by technical managers.
Social processes are more effective than written manuals at transferring knowledge.
Written processes are without schedule revision and update procedures.
Involvement leads to belief in the efficiency of a training/learning medium.

ConradiDybaEtAl06

Reidar Conradi & Tore Dyba & Dag L Sjoberg & Tor Ulsund
Software Process Improvement: Reulsts and Experience from the field
Springer-Verlag NY Secaucus NY 2006 ISBN 3540321780 CR 0712-1162
=UNREAD CONFERENCE SPI IMPROVEMENT EMPIRICAL SCANDINAVIAN

ConradiWesfechtel98

Reidar Conradi & Bernhard Westfechtel
Version Models for Software Configuration Management
ACM Comp Surveys V30n2(Jun 1998)pp232-282
+THEORY =SURVEY TOOLS [SCM]

Constantine90

Larry L Constantine
Comments "On Criteria for Module Interfaces"
IEEE Trans SE-16 n12(Dec 1990)p1440

Constantine94

Larry Constantine
Essentially Speaking
Software Development V2n1(Nov 1994)pp96+95
1. p96 "Data Flow diagrams were intended as a nonprocedural model o computation, separating the essence of what the computer was to do from how it was to be accomplished through any particular algorithm or procedure[...] In practice, designers often turned DFDs into flowcharts with funny figures, a corruption encouraged by enhancements taht implicitly invited procedural thinking." ref to McMenaminPalmer86, Stephen P McMenamin & John Palmer, Essential Systems Analysis, Yourdon Press 1986
2. p95 Essential use-case modeling: S-T
3. p95"If we don't design to the ideal, we can't see where technology or technical assumptions are limiting us, and we may miss completely the opportunity for alternative approaches."

Constantine95

Larry Constantine
Essential modeling: use cases for user interfaces
interactions V2n2(Apr 1995)pp34-46
CR9607-0521 USER SCENARIO

Constantine95a

Larry Constantine
Software Objectives
Software Magazine (Jun 1995)pp88-87

Constantine95b

Larry Constantine
Embedded with the Best
Software Development Magazine(Jul 1995)pp88&87+letter(Oct 1995)p11

Constantine95c

Larry Constantine
Under Pressure
Software Development Magazine(Oct 1995)pp112+111
=EXPERIENCES
reports on competition to produce a complex system in under one day in Australia
Concludes that design time pays off but configuration management is vital when under pressure.

Constantine99

Larry Constantine
Modeling for the long term
Software Development Magazine V7n11(Nov 1999)pp40-43
=EXPERIENCE USER MODEL ECONOMICS REUSE
Models clarify needs and designs early.
Persistent models have an extra pay off later.
=ADVERT [ConstantineLockwood99]

Constantine00

Larry Constantine
Cutting Corners
Software Development V8n2(Feb 2000)pp72+70-71
=EXPERIENCE Crunch mode TANSTAAFL PROTOTYPING MODELING
Face-time can be traded for user modeling.
A real user is a better model of the user than any model!

Constantine00b

Larry Constantine(ed) with Sylvain Hamel & Jim Highsmith
Optimize -- or Adapt
Software Development Magazine V8n4(Apr 2000)pp80+78-79
=DEBATE PROCESS PEOPLE

Constantine01

Larry Constantine
Managing Creative Input
Software Development Magazine V9n1(Jan 2001)pp70-72
=IDEA VISION REQUIREMENTS
managers and marketers speak a different language to designers and developers - and this not a bad thing.
Input is fantasy not SRS. Compile, sort, compare, combine, weigh.
user roles.
To bridge the gap use a role_support_matrix:
role_support_matrix := ( ( capability | page) >< user_role ) -> importance.
importance := -2 .. +2, prohibited .. necessary.
Use cases are not features, but specific desired ways to use features and functions

Constantine01b

Larry L Constantine
Back to the Future
Commun ACM V44n3(Mar 2001)pp126+128-129
=ESSAY HISTORY QUALITY SOFTWARE
Increased hardware power has permitted software to be developed without being engineered
The result is that it doesn't work well and gives little extra value.

ConstantineLockwood99

Larry L Constantine & Lucy A Lockwood
Software for use: a practical guide to the models and methods of usage-centered design
ACM Press/Addison-Wesley 1999 ISBN 0-201-92478-1 QA76.76.A65 C665 1999 CR9906-0400
=HANDBOOK USER PURPOSES DESIGN METHOD MODEL CARDS SCENARIOS DOCUMENTATION HCI ERGONOMICS GRAPHICS PROTOTYPES
models: {user role maps, essential use cases, use case map, focal use cases, low tech model, navigation map}
5 rules of usability:= {access, efficacy, progression, support. context }
6 principles of usability:= {structure, simplicity, visibility, feedback, tolerance, reuse }.

ConstantineLockwood02

Larry L Constantine & Lucy A D Lockwood
Usage-Centered Engineering for Web Applications
IEEE Software Magazine V19n2(Mar/Apr 2002)pp42-50
=EXPERIENCE =DEMO AGILE WWW/NET USECASE METHOD PROCESS CARDS
Usage-centered design differs from user-centered design in using models(role, task, content), engineering to provide tools supporting user tasks.
Process involves exploration and iteration.
task cases: technology free essential abstract description of user's intentions and system's responsibilities.
Content model aka abstract prototype based on several canonical forms: [ cannonical.pdf ]
Navigation map connects interaction contexts.

ContedeLeonAlves-Foss06

Daniel Conte de Leon & Jim Alves-Foss
Hidden implementation dependencies in high assurance and critical computing systems
IEEE Trans Software Engineering V32n10(Oct 2006)pp790-811
=CASE STUDY FORMAL HA&CCS ARTIFACTS RELATIONS LOGIC PROLOG GRAPHIC IMPLEMENTATION ABSTRACTION GUAM DO-178B
Pedantic theory leads to tool that found problems in software from traceability relations on "work product sections" (artifacts).
Translation into MATHS
Net
1. artifact:Sets.
2. implements: @(artifact,artifact) =given, indicates traceability between artifacts.
3. |-STRICT_ORDER(strict_relation=>implements, artifact).
4. l: artifact>->level =given, assigns a level to each artifact.
5. <: @(level, level) =given.
6. |-STRICT_ORDER(strict_relation=>(<), level).
7. dependency: @(artifact, artifact) =goal.
8. d := dependency.
9. |- (conceptual_completeness): for x, y, z: artifact((if (x implements y and z) and l(x)<l(y)<l(z) then y d z) and (if (x and y implements z) and l(x)<l(y)<l(z) then x d y))
10. STRICT_ORDER::= See http://csci.csusb.edu/dick/maths/math_21_Order.html#STRICT_ORDER
(End of Net)

Conway63

Malcolm E Conway
Design of a Separable Transition Diagram Compiler
Commun ACM V6n7(Jul 1963)pp396-408)
=DEMO graphic non-sequential CO-ROUTINES
Source for the 2 stars-> uparrow and cards to lines problem of Hoare.
ChandyMisra88 pp185-190 (design without processes and channels by added them later)
Knuth (V1.4.5 p226) writes that M E Conway invented co-routines in 1958.

Cook10

Mary Rose Cook
Creative Requirements Conversations
IEEE Software Magazine V27n2(Mar/Apr 2010)pp90-91
=ADVERT USER REQUIREMENTS ELICITATION ALTERNATIVE CODESIGN Uscreates
Gathering requirements should be a creative conversation and so needs special environments and techniques.
The Touring Cafe Caravan -- mobile space to collect requirements. Free refreshments...
Speed modeling: 3d brainstorming, plasticine, ...
Compare [Gottesdiener99] requirements workshops.

CookDaniels94

S Cook & J Daniels
Designing Object Systems
Prentice Hall Upper Saddle River NJ 1994
Syntropy

CookWolf98

Jonathon E Cook & Alexander L Wolf
Discovering Models of Software Processes from Event-Based Data
ACM TOSEM V7n3(Jul 1998)pp215-249
=ANALYSIS EXPERIENCE data mining neural nets DaGamma GRAMMAR FSM Markov

CookWolf99

Jonathon E Cook & Alexander L Wolf
Software Process Validation: Quantitive Measuring the Correspondence of a process to a model
ACM TOSEM V8n2(Apr 1999)pp147-176
=EXPERIENCE PROCESS vs SYSTEM Balboa Petri Net FSM/STD TOOL

Cooke06

John Cooke
Constructing Correct software(2nd edn)
Springer 2005 QA76.76 ISBN 1-85233-820-2
=INTRODUCTION MATHEMATICS LOGIC PROOF CORRECTNESS PROGRAMMING TECHNICAL
compare with Bo Sandin's stuff in the 1980's and Huth & Ryan (textbook).

CookPodelskiRybalchenko11

Byron Cook & Andreas Podelski & Andrey Rybalchenko
Proving program termination
Commun ACM V54n5(May 2011)pp88-98 [ 1941487.1941509 ]
=DEMO MATHEMATICS TERMINATION LOGIC DISJUNCTIVE
Instead of proving that the transition relation R is a sub-relation of a well-founded relation T:
R==>T, One can try to prove that
R^(1..*) ==> | [i:1..n] T[i], where each T[i] is well-founded.
Claims that "Ramsey's Theorem" implies that only a finite collection of T's need be considered.
Adding extra statements and assertions to the code can express termination as invariants. For example, to verify that a variable is decreasing but positive:
```
    assert( oldx > x && x > 0 );
```
```
    oldx:=x;
```
Tools can then verify the invariants.
Compare Andreas Blass and Yuri Gurevich. ACM Trans Comp Logic (Dec 2006) pp1-25 [ download?doi=10.1.1.146.4485&rep=rep1&type=pdf ]

CookeRushton09

Daniel E Cooke & J Nelson Rushton
Taking Parnas's Principles to the Next Level: Declarative Design
IEEE Computer Magazine V42n9(Sep 2009)pp56-63
=ADVERT SequenceL FUNCTIONAL LANGUAGE SERIAL PARALLEL
Rediscovers APL and Lucid.
(dick)|-almost like executable MATHS. For example, Σ( 1/((0..n)!) ) in MATHS looks like this
```
  sum(1/fact( [0,...,N]))
```
in SequenceL.
Compare [Holmes09]

CoomberChilds90

CJ Coomber & RE Childs
A Graphical Tool for the Prototyping of Real-Time Systems
ACM SIGSOFT SEN V15n2(Apr 1990)pp70-82 DFDs prototyping STDs

CoombsRenearDeRose87

James H Coombs & llen H Renear & Steven J DeRose
Markup Systems and the Future of Scholarly Text Processing
Commun ACM V30n11(Nov 1987)pp933-947
=SURVEY MARKUP LANGUAGES
SGML markup_forms::=none | presentational | procedural | descripitive | metamarkup |punctuational.

Cooper95

Alan Cooper
about face: the essentials of user interface design
idg book foster city ca 1995 isbn1-56884-322-4 qa76.9 u83 c6 1995
=MANUAL USER GUI

Cooper99

Allen Cooper
The Inmates are Running the Asylum
Sams 1999, ISBN 0-672-31649-8
=EXPERIENCE PEOPLE PROCESS ECONOMICS REQUIREMENTS =ADVERT interaction design USER PURPOSE QUALITY Scenarios
goals persona cognitive friction thinking [ Cooper99.html ] [ persona in Cooper99 ]

CooperP07

Peter Cooper
Beginning Ruby: From Novice to Professional
Apress Berkeley CA 2007 ISBN 1-59059-4 QA76.64 C667
=TEXT Ruby LANGUAGE =REFERENCE

Coplien97

James O Coplien
Idioms and Patterns as Architectural Literature
IEEE Software Magazine V14n1(Jan/Feb 1997)pp36-42
=HISTORY

Coplien99

James O Coplien
Multi-paradigm Design for C++
Addison Wesley Longman Reading MA 1999 ISBN 0-201-82467-1 CR9905-0317 CR9906-0404
=DEMO DESIGN C++ METHODS OBJECT-ORIENTED DATA INHERITANCE

Coplien99d

James O Coplien
Reevaluating the Architectural Metaphor: Toward Piecemeal Growth
IEEE Software Magazine V16n5(Sep/Oct 1999)pp 40-44
=HISTORY ARCHITECTURE OBJECTS PATTERNS PEOPLE
Growing systems piecewise in teams, uncovering architecture by growing system

CoplienDevos00

James O. Coplien & Martine Devos
Architecture as Metaphor
Proc SCI/ISAS2000 VI pp737-??? [SCI00]
=SURVEY ARCHITECTURE meeting grounded theory
concepts: Change, Role Interaction, Structure, Economics, Constraints, Process, Professionalism
Sample insites
1. In buildings the clienbt is a slave to fashion but in software it is the architect.
2. In buildings the architect shows the user interface to prospective clients and delegates the internals, in software the architect focusses on the internals and delegates the user interface!

CoplienSchmidt96

J O Coplien & D C Schmidt
Pattern Languages of Program Design
Addison-Wesley Redwood City CA 1995(paperback) $39.76 ISBN 0-201-60734-4
based on PLoP94 [ index.html ]

Corbato91

Fernando J Corbato
On Building Systems that Will Fail(Turing Award lecture)
Commun ACM V34n9(Sep 1991)pp72-81
CR9209-0696
The questions to ask about ambitious systems are "what will go wrong" and what happens "when it does go wrong"
p80 "Worse yet
There is no way to simply 'look' at a system and determine what the privacy and security implications".

CorbettAvrunin94

James C Corbett & George S Avrunin
Towards Scalable Compositional Analysis
SIGSOFT'94 Proc 2nd ACM SIGSOFT Symp on Foundations of Software Engineering & ACM SIGSOFT Software Engineering Notes V19n5(Dec 1994)pp53-61
=THEORY =DEMO NONSEQUENTIAL MODEL CHECKING

Cordesetal91

David Cordes & Marcus Brown
The Literate-Programming Paradigm
IEEE Computer V24n6(Jun 1991)pp52-61
=ADVERT LITERATE

Cordova99

Jose L Cordova
Matheatical Proofs as Graph Search Problems in Theory Courses
ACM SIGCSE Bulletin -- Inroads V31n1(Mar 1999)pp110-113
=EXPERIENCE Teaching ANALYSIS

CormodeMuthukrishnan12

Graham Cormode &S Muthukrishnan
Approximating data with the count-min sketch
IEEE Software Magazine V29n1(Jan/Feb 2012)pp64-69
=ADVERT APPROXIMATE DATA STRUCTURE SKETCH count-min
Can use a fixed number of fixed hash tables to store enough data to retrieve good approximate answers. to problem of the minimum counts. see also Bloom filter and AMS sketch...

CornelHorstmann98

Gary Cornell & Cay Horstman
Taking the Right Approach
Software Development Magazine V6n6(Jun 1998)pp34-36+38+40-41
=ARTICLE TECHNICAL Java RMI vs CORBA IDL
Java smaller simpler and less general.

CorriganGurry94

Peter Corrigan & Mark Gurry
ORACLE Performance Tuning
O'Reilly & Assoc 1993 ISBN 1-56592-048-1 Review p492 AMM May 1994
=MANUAL data ENGINEERING database technique->quality

Cortellessa01

V. Cortellessa & A. D'Ambrogio & G. Iazeolla
Automatic derivation of software performance models from CASE documents
Performance Evaluation V45n2-3 (Jul 2001) pp81-105 [ http://www.elsevier.com/ ] [CR] 0201-0025
=DEMO QUALITY PERFORMANCE MODEL SCENARIO CASE UML Flowgraphs QUEUES LQN
LQN::="Layered Queuing Network".
(dick)|-sounds like modern version of SSADM physical design control.

Costagliolaetal95

Genaro Costagliola & Genoveffa Tortora & Sergio Orefice & Andreas De Lucia
Automatic Generation of Viusal Programming Environments
IEEE Computer Magazine V28n3(Mar 1995)pp56-66
=TOOL GRAPHIC PROGRAMMING
1. positional grammars
2. HOR and VER
3. bibliography...
4. Positional LR model
5. Positional context free grammars

CortellessaPompei04

Vittorio Cortellessa & Antonio Pompei
Towards a UML profile for QoS:a contribution in the reliability
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp197-206
=IDEA QUALITY reliability SPECIFICATION UML profile =EXAMPLE elevator.
Gives rules mapping model into formulae for calculating reliability.

CortellessaEtal05

Vittorio Cortellessa & Katerina Goseva-Postojanova & Kalaivani Appukkutty & Ajith R Guedin & Ahmed Hassan & Rania Alnaggar & Walid Abdelmoez & Hany H Ammar
Model-Based Performance Analysis
IEEE Trans Software Engineering V31n1(Jan 2005)pp3-20
=DEMO REQUIREMENTS DESIGN QUALITY PERFORMANCE TIMING RISK PROBABILITY LOAD UML1.5 MODEL
How to estimate the probability that a performance requirement will fail.
For each scenario:
1. assign demand vectors(CPU,Disk,network,...) to steps in sequence diagram; map to software execution model (=~= Activity diagram)
2. Add hardware info to deployment diagram
3. Devise workload parameters, map to execution model, contention analysis, est. Probability of violating timing
4. Severity analysis
5. Risk=severity * probability; identify high risk components.
Estimate probability of failure at workload w, P(w) by linear interpolation from upper and lower bounds on throughput (l(w).. u(w)) and objective t. Assume l & u are monotonic increasing.
If u(w0)=t then P(<=w0)= 0 and if l(w1) = t then P(>=w1) =1.
For w: [w0..w1], P(w)= (u(w)-t)/(u(w)- l(w)).
Research continued in [CortellessaPieriniRossi07]

CortellessaPieriniRossi07

Vittorio Cortellessa & Pierluigi Pierini & Daniele Rossi
Integrating software models and platform models for performance Analysis
IEEE Trans Software Engineering V33n6(Jun 2007)pp385-401
=DEMOs MODEL PERFORMANCE QUALITY TIMING UML-RT ANNOTATIONS RRT REAL TIME
Shows how to model design + platform so that the system can be simulated.
RRT::= "IBM-Rational Rose RealTime tool set", includes simulation.
Simulations appear to fit actual system loads well.
Note. Diagrams may be UML-RT but they are not UML1.* or UML 2.0. They use a non-standard conditional node.
Continues [CortellessaEtal05]

CostagliolaEtal97

Gennaro Costagliola & Andrea De Lucia & Sergio Orefice & Genoveffa Tortora
A Parsing Methodology for the implementation of Visual Systems
IEEE Trans SE V23n12(Dec 1997)pp777-799)
=THEORY pLR GRAMMAR =DEMO TOOL VLCC compiler-compiler for graphic languages

CostagliolaDeufemiaPolese04

Gennaro Costagliola & Vincenzo Deufemia & Giuseppe Polese
A Framework for Modeling and Implementing Visual Notations with Applications to Software Engineering
ACM TOSEM Trans Software Eng & Methodology V13n4(Oct 2004)pp431-487
=DEMO THEORY GRAPHICS LANGUAGE GRAMMAR PARSING METACASE VLDesk XPG XpLR UML Statecharts
XPG::="eXtended Positional Grammar", syntactic description of visual notations in terms of visual symbols (vsymbols), plus spatial relations generating visual sentences.
Ontology of spatial relations:
Net
1. Relation = Connection | Geometric
2. Plex ==>Graph==>Connection,
3. String ==>Iconic==>Box==>Geometric.
(End of Net)
XpLR::=parsing method associated with XPG.
VLDesk::tool, provides a "desk" where methodologists can develop CASE tools.

CostagliolaEtal05

Gennaro Costagliola & Filomena Ferruci & Genoveffa Tortara & Giuliana Vitiello
Class Point: an approach for the size estimation of Object-Oriented systems
IEEE Trans Software Engineering V31n1(Jan 2005)pp53-74
=EXPERIMENT ESTIMATION CODE SIZE LoC EFFORT FP IFPUG TUCP METRICS NEM NSR
CP1::level= "Class Point 1", based on NEM and NSR (Methods and services requested).
level::= (low, average, high).
CP2::level= "Class Point 2", based on NEM, NSR, and NOA(attributes).
TUCP::= "Totally Unadjusted Class Point",based on CP1 and CP2.
|-TUCP=Sum [class_type c, level l]( weight[c, l] * number classes[c, l]).
class_type::= problem_domain | human_interaction | data_management | task_management.
CP::= "Class Point", based on TUCP and 18 technical factors.
p71. fig 6. Form
Significant correlation between CP1 and CP2

CostelloLiu95

Rita J. Costello & Dar-Biau Liu
Metrics for Requirement Engineering
Journal of Systems and Software V29n1 (Apr 1995) pp39-63. Elsevier Science Inc. 655 Avenue of the Americas New York NY 10010.
=ADVERT REQUIREMENTS METRICS

CougerZawacki01

D J Couger & R A Zawacki
Motivating and Managing Computer Personel
John Wiley 1980
=POLL THEORY PEOPLE

CoulourisThimbleby93

George Coulouris & Harold Thimbleby
HyperProgramming: building interactive programs with HyperCard
Addison-Wesley Reading MA 1993 ISBN 0-201-56886-1 CR9402-0062
=TEXT APPLE HYPERTALK HYPERCARD VISUAL GRAPHIC PROGRAMMING

CounsellSwiftCrampton06

Steve Counsell & Stephen Swift & Jason Crampton
The Interpretation and utitlity of three cohesion metrics for Object-Oriented Design
ACM TOSEM Trans Software Eng & Methodology V15n2(Apr 2006)pp123-149
=THEORY Object-Oriented METRICS COHESION QUALITIES LCOM CAMC NHD SNHD
Notes the lack of definition of OO cohesion comparedto Constantine and Myers definition for "structured" code in 1979.
CAMC, NHD, and SNHD measure the extent that all methods in a class have similar signatures.
(dick)|-does not refer to Larman's description and use of High Cohesion as a design pattern/principle using sequence diagrams [Larman04b].

CourageBaxter05

Catherine Courage & Kathy Baxter
Understanding your user: a practical guide to user requirements
Morgan Kaufman SF CA 2005 ISBN 1-55860-935-0 QA76.9H85C69
=HANDBOOK USER REQUIREMENTS
comprehensive

Cousot90

Patrick Cousot
Methods and Logics for Proving Programs
Chapter 15 (pp841..993) of Leeuwen90
=THEORY Operational and relational semantics

Courte07

Jill E Courte
Comparing Student Acceptance and Performance of Online Activities to Classroom Activities
Proceedings of the 8th ACM SIGITE conference on Information technology education (2007)pp185-190 [ 1324302.1324341 ]
=EXPERIMENT ONLINE vs FACE-TO-FACE TEACHING EDUCATION JavaScript
The average grades may be the same.... but the online students lose interest in the topic.

CowanDEtal02

Robert D Cowan & Ali Mili & Hany Ammar & Alan McKendall Jr & Lin Yang & dapeng Chen & Terry Spencer
Software Engineering Technology Watch
IEEE Software Magazine V19n4(Jul/Aug 2002)pp123-129
=THEORY TECHNOLOGY
Distinguishes 3 kinds of research: Analytical, Empirical and Experimental.
Many questions and theories but no results yet.

Cowanetal80

Cowan & Graham & Welsh & Lucena
A Data Directed Approach to Program Construction
Software Practice & Experience V10 pp355-372
=DEMO DDD graphic sequential

Cowanetal95

Donald D Cowan & Carlos J P Lucena
Abstract Data Views: An Interface specification Concept to enhance Design for Reuse
IEEE Trans on Software Eng VSE-21n3(Mar 1995)pp229-243 CR9602-0126
=DEMO ADO ADV OBJECT-ORIENTED REUSE ARCHITECTURE

Cox90a

Brad C Cox
There is a Silver Bullet
BYTE V15n10(Oct 1990) pp209-218
=HYPE Objected-Oriented

Cox90b

Brad C Cox
Planning the Software Industrial Revolution: The Impact of Object-Oriented Technologies
IEEE Trans SE-15n11(Nov 1990)
=HYPE Objected-Oriented

Cox01

Brad J Cox
Object-Oriented programming: an evolutionary approach
Addison-Wesley 1987 QA76.9.S88C69 ISBN 0-201-10393-1
=DEMOS MODULES UNIX C++ OBJECTIVEC

CoxA98

Alan Cox
Cathedrals, Bazaars and the Town Council
Slashdot Features (0ct 1998)98/10/13 [ 1423253.shtml ]
=EXPERIENCE OPEN SOURCE PROCESS 8086 Linux
Why talk without code can be a problem with open source development
Quote: Beware "We should", extend a hand to "How do I"...

CoxD01

David Cox
Parsing XML
Dr. Dobbs #320(Jan 2001)pp96+98+100
=DEMO XML PARSE TREE C++
parsing a subset of UML in C++.

Craigenetal93

Dan Craigen(dan@ora.on.ca) & Susan Gerhart(pl0183@mail.psi.net) & Ted Ralston(ralston@cli.com)
An International Survey of Industrial Applications of Formal Methods
2 Vols National Technical Information Service Springfield Virginia 22161 1993 ( NIST GCR 93/626-V1 -V2 order PB93-178556/AS+PB93-178564/AS Microfiche: A02 $12.50+ A03/$12.50)
=SURVEY FORMAL METHODS EXPERIENCE
Long survey of twelve case studies of the use of formal methods in industrial projects. Volume 1 describes the purpose, approach, analysis, and conclusions of the survey; Volume 2 describes the case studies.
CSR Gypsy B Statecharts Z*5 Cleanroom RAISE FDM HP-SL(VDM+??)

Craigenetal95

Dan Craigen<dan@ora.on.ca> & Susan Gerhart<pl0183@psilink.com> & Ted Ralston
Formal Methods Reality Check: Industrial Applications
IEEE Trans SE-20n2(Feb 1995)pp90-98 CR9601-0215
=EXPERIENCES FORMAL METHODS [GerhartCraigenRalston94]

CraigenMeiselsSaaltink99

Dan Craigen & Irwin Meisels & Mark Saaltink
Analyzing Z specifications with Z/EVES
In [HincheyBowen99] pp255-283
=DEMO SQA Z SPECIFICATION PROOF TOOL Z/EVES SWP
demo on Sliding Window Protocol and a simple password/user system.
Short and simple introduction to Z.

Crameretal94

Joachim Cramer & Ernst-Erich Doberkat & Michael Goedicke
Formal methods
Schaferetal94 pp 79-111
=THEORY REUSE FORMAL ALGEBRA SPECIFICATIONS
Describes hierarchy of semantic models for algebraic specification, cf Lin93.

Cramm10

Susan Cramm
IT and Business Leaders: Getting Along Is Not Enough
Harvard Business Review (Mar 3 2010) blog [ it-and-business-leaders-getting-along.html ]
=POLL UNDERSTANDING INFORMATION TECHNOLOGY vs BUSINESS
Thought that business does not understand IT well enough and IT doesn't understand business as well

Crawford90

Diane Crawford
National Software Needs: A Matter of Priorities
"from Washington" Commun ACM V33n3 (Mar 1990)pp272-273
=NEWS USA SOFTWARE

Creel99

Chris Creel
Requirements by Pattern
Software Development Magazine V7n12(Dec1999)pp44-46
=EXPERIENCE PATTERN REQUIREMENTS
avoid overspecification by using: present|display, specify|locate, prioritize|sort, ...

CreveuilRoman94

Christian Creveuil & Gruia-Catalin Roman
Formal Specification and Design of a Message Router
ACM Trans Softw Eng Methodol V3n4(Oct 1994)pp271-307 CR9512-0963
=CASE-STUDY UNITY FORMAL NONSEQUENTIAL CASESTUDY
Router problem studied in the 6th International Workshop on Software Specification and Design p304-305, Conclusions
1. "It is better to specify and reason about a closed system - i.e. a system and its environment -- rather than an open one" ...
  "[A] critical element is the formulation of the top-level specification[...] focussing on I/O properties[...]selecting the "right" notation. [..] One does not stumble upon appropriate notation. Experience, exploration, and some looking ahead can provide the required insight. [...] True design, however, never makes such pretense[of being mechanistic]. Looking ahead and back-tracking are a part of the method. [...] selection of auxilary variables was one of the key decisions."
  "[...]small refinements proved helpful."
  "It was relatively easy to separate the formal treatment of the proofs from the refinement process itself. [... many trial refinements,...final design proved]. [...] design and verification can actually be carried out by different people."

Crispin06

Lisa Crispin
Driving software quality: how test-driven development impacts software quality
IEEE Computer Magazine V39n10(Oct 2006)pp70-71
=ADVERT TDD
Quotes experience & pubs showing that writing tests first have many good effects on a project.

CRL

See web site [ serg.publications.html ]
Reports from theCommunications Research Laboratory of the Telecommunications Research Institute of Ontario(TRIO) McMaster University Hamilton Ontario Canada
includes [Parnas92] + [Wang95] + [Janicki97]

CrnkovicSentillesVulgarakisChaudron11

Ivica Crnkovic & Severine Sentilles & Aneta Vulgarakis & Michel R V Chaudron
A classification framework for software component models
IEEE Trans Software Engineering V37n5(Sep/Oct 2011)pp593-615
=SURVEY TAXONOMY COMPONENT MODELS MODULES LIFE-CYCLE AUTOSAR BIP BlueArX CCM COMFES CompoNETS EJB Fractal Koala KobeA IEC 61131 IEC 61499 JavaBeans MS-COM OpenCOM OSGI Palladio PECOS Pin ProCom ROBOCOP RUBUS SaveCCM SOFA 2.0
extra-functional-properties::=quality requirements.

CrowstonHowison06

Kevin Crowston & James Howison
Assessing the Health of Open Source Communities
IEEE Computer Magazine V39n5(May 2006)pp89-91
=EXPERIENCE =SURVEY OPEN SOURCE FLOSS SOCIOGRAM
Assess the stage in the life cycle, the size, and the shape of the community.
10 is about the mode for size.
Mature groups are structured in shells like an onion.
Growing community means more time spent synchronizing -- many projects don't make it past the "one developer=user" stage.
Has the community survived the transition in the leadership -- e.g. founders becoming inactive?
Who provides the infrastructure (a necessary but boring function)?

CrowVito98

Judith Crow & Ben Di Vito
Formalizing Space Shuttle Software Requirements: Four CASE Studies
ACM TOSEM V7n3(Jul 1998)pp215-249
=ANALYSIS EXPERIENCE [PVS] GPS RAPID FORMAL LOGIC TABLE MATH MurΦ
1. Where do states come from, shared variables used as input/output.
2. Large number of errors discovered (early) just by formalizing requirements without checking!
3. Need for readymade math theories: eg properties of mappings!
4. Failed proofs are more help than successful ones.
5. Specification is iterative.
6. Need to specify constraints found in the problem domain.
7. Can simplify model: remove continuous values and time and remove costraints. Therefore check some impossible states
8. Tailor formal methods to the situation.

CSSyllabus92

Computer Science Syllabus
Summer 1992
Syllabus Press Sunnyvale California<syllabus@applelink.aplle.com>
=HISTORY Kay Object-Oriented education

CSTB'89

National Research Council's Computer Science and Technology Board
Scaling Up: A Research Agenda for Software Engineering
Excerpts -Commun ACM V33n3(Mar 1990)pp281-293 & Full Report - National Acad Press Wa. D.C.
=handbook harmful RISKS

CubranicMurphySingerBooth05

Davor Cubranic & Gail C Murphy & Janice Singer & Kellog S Booth
Hipikat: A Project memory for Software Development
IEEE Trans Software Engineering V31n6(Jun 2005)pp429-526
=ADVERT TOOL EVOLUTION DOCUMENTATION WWW EMAIL CVS BUGZILLA Hipikat tool analyzes artifacts gathered in Eclipse development and provides readings to newcomers with maintenance tasks.

CugolaNitoEtal96

Giampaolo Cugola & Elizabetta di Nitto & Alfonso Fuggetta & Carlo Ghezzi
A Framework for Formalizing Inconsistencies and Deviations in Human-centred Systems
ACM TOSEM V5n3(Jul 1996)pp191-230
=THEORY USER REQUIREMNTS FORMAL Z: REALITY vs SYSTEM PETRIE GRAPHICS

CugolaDiNottiFuggetta01

Gianpaolo Cugola & Elisabetta Di Notti & Alfonso Fuggetta
The JEDI Event-Based Infrastructure and its application to the development of the OPSS WFMS
IEEE Trans Software Engineering V27n9(Sep 2001)pp827-850
=DEMO ARCHITECTURE NET JAVA JEDI OPSS WORKFLOW lifecycle regular expressions ORCHESTRA TWIST IETF TIMING latency =SURVEY
JEDI_architecture::=decouple objects by passing events to a centralized or distributed dispatcher that notifies subscribed objects using a hierarchical strategy.
stateServer -- handles FSMs that define admissible sequences of events.

Cukic05

Bojan Cukic
The virtues of assessing reliability early
IEEE Software Magazine V22n3(May/Jun 2005)pp51-53
=ADVERT COMPONENTS QUALITIES RELIABILITY PREDICTION UML MODEL USE CASES SEQUENCE DEPLOYMENT TOOL beta-distribution Monte Carlo ECRA
ECRA::= "extended component-based reliability assessment".
See cukic@csee.wvu.edu.

CunhaGreathead07

Alessandra Devito Da Cunha & David Greathead
Does Personality Matter? An Analysis of code-review ability
Commun ACM V50n5(May 2007)pp109-112
=EXPERIMENT 64 PEOPLE INSPECTION CODE TECHNICAL MBTI DEBUGGING
Used the Myers-Briggs Type Indicator (MBTI) to classify students vs their skill at finding bugs in code.
iNtuitive+Thinking people do significantly better at finding bugs in code than iNtuitive+Feeling, Sensing+Thinking, and Sensing+Thinking types.

Curtis01

Tex(Bill) Curtis
So you Wanna Be a cowboy
IEEE Software Magazine V18n2(Mar/Apr 2000)pp122+110-111
=ARTICLE PEOPLE
cowboys: work long hours alone, never admit uncertainty, ignores bureaucracy, no time for family, takes on any challenge.
death marches and cattle drives,
Unique skills
branding irons and copyrighting code.
projects and cattle drives.
But cowboys need discipline and teamwork - think stampede. Call the rowdy programmer a maverick!

CurtisKellnerOver92

Bill Curtis & Marc I Kellner & Jim Over
Process Modeling
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp75-90
=SURVEY MODEL PROCESS

CurtisKrasnerIscoe88

B Curtis & H Krasner & N Iscoe
A Field Study of the software design process for large systems
Commun ACM V31n11(Nov 1988)pp1268-1287
=POLL EXPERIENCE 17 LARGE PROJECTS DESIGN
Problems: not enough domain knowledge, fluctuating and conflicting requirements, and Communication.
"Writing code isn't the problem, understanding the problem is the problem."
"Planned is probably a generous term . . . . an englightenment occurs as they move forward."

Cusumano04

Michael A Cusumano
Who is Liable for Bugs and Security Flaws in Software
Commun ACM V47n3(Mar 2004)pp25-27
=NEWS =ARTICLE SECURITY RISKS LEGAL Microsoft
Oct 2003: NYTimes reports lawsuit in California vs Microsoft.
Software companies are liable for flaws. Some are better than others at detecting and fixing defects. None are 100% successful.
Most if not all networked software have had security flaws. What is acceptable?
So why was Microsoft sued?

Cusumano07

Michael A Cusmano
What Road Ahead for Microsoft the Company
Commun ACM V50n2(Feb 2007)pp15-18
=ARTICLE ECONOMICS Microsoft vs OPEN SOURCE WEB/NET
Rivals use new business model: use fee but pay for support and enhancements. Rather than pay for licence and upgrades.
Challenge of breaking up monolythic code.
Challenges of changing top management.

Cusumano07b

Michael A Cusumano
The Changing Labyrinth of software pricing
Commun ACM V50n7(Jul 2007)pp19-22
=NEWS ECONOMICS PRICES
Notes a shakeout in software producers in last 10 years.

Reports his students MS work (S Nayak, Pricing and licensing of software products and services: A study of industry trends", MIT MS Thesis Sys Des & Man Program MIT, May 2006)

software_pricing::=
Net{
1. Licence_options::=individual | group | concurrent | enterprse | site.
2. Licence_term::= 0..1.year | annual | 3 years | perpetual.
3. Installation_types::= designated computer | standalon named user | network named user | concurrent user.
4. Payment_methods::= up_front | pay_as_you_go | financed.
5. Terms_and_compliance::=shrink_wrap | contract | dongled | activation.
6. Flexibility::= product specific | product agnostic | remix.
Also variations on free software: free razor + paid_for_blades, free software + paid_for_services, free software + advertizing.

Cusmano07c

Michael A Cusumano
Extreme Programming compared with Microsoft-Style Iterative Development
Commun ACM V50n10(Oct 2007)pp15-18
=ESSAY XP Microsoft ITERATION HP WATERFALL
Useful comparison

Cusumano08

Michael Cusumano
Technology Strategy & Managment: The Puzzle of Apple
Commun ACM V51n9(Sep 2008)pp- [ 1378727.1378736 ]
=ESSAY ECONOMICS PRODUCTS vs PLATFORMS
MS tends to create platforms that encourage other businesses to get involved.
Apple prefers a closed but higher quality (and higher priced) product.
Comparison with Betamax vs VHS.

CusumanoMaccormackKemererCrandall03

Michael Cusumano & Alan Maccormack & Chris F Kemerer & Bill Crandall
Software Development worldwide: The State of the practice.
IEEE Software Magazine V20n6(Nov/Dec 2003)pp28-34
=POLL 104 PROJECTS INTERNATIONAL PRACTICES ONESIZE
LOC productivity about the same as 10 years ago. lowest = India <US < Europe etc < Japan = most.
Defect rates have improved. worst US > India > Europe etc > Japan.
Certain clusters of practices work better than others: for example, iterative development with beta testing works as well as waterfall with complete specification.
See [CusumanoMaccormackKemererCrandall03]

CusumanoMaccormackKemererCrandall09

Michael A Cusumano & Alan MacCormack & Chris F Kemerer & William Crandall
Critical Decisions in Software Development: Updating the State of the Practice
IEEE Software Magazine V25n5(Sep/Oct 2000)pp84-87
=SURVEY PROCESS MANAGEMENT waterfall vs agile ONESIZE QUALITIES
Revisits [CusumanoMaccormackKemererCrandall03] showing a wide range of processes and qualities.
One size does not fit all.
Must choose a process to fit the situation.
Distributed development gives rise to a more modular structure and needs special learning to pay off.
A rigid process can give higher quality but at risk of loosing innovative products.

CusumanoSelby95

Michael Cusumano & Rick Selby
Microsoft's Secrets: How the world's most powerful software company creates technology& shapes markets & and manages people
Simon & Schuster September 1995
=REPORT MICROSOFT PROCESS PEOPLE MS-PROCESS AGILE
See also [Keuffel95b] , [Bond95] , [MyersW95] , and an extract in [CusumanoSelby97]
For a view of the later Microsoft proceesses, see [ Cusumano06 ]
Key observations:
1. Process::= Planning;Development;Stabilization,
2. Planning::=Vision;Spec;Organize,
3. Development::=(vision&spec&design&tests evolve and grow in parallel)&(first1/n; second1/n; third1/n; ...),
4. n in {3,4}. each_1/n::=code&test&stabilise_features; integrate&test&debug;BUFFER time.
5. Frequent synch/daily build.
6. Stabilization::=Internal test; external test; Prepare for release.
7. Fixed dates and multiple releases
8. Continuous customer feedback
9. Aim: large teams work like small ones.
  Focus on the production of code (not design vs documentation). Minimal optional high level architectures. Some implementation decisions (data structures) may be documented. "One document. One. It's the Source code."
  Costs:1 tester for each developer PLUS >1 customer-support engineer per developer
Also Warren Keuffel's notes [ notes/Keuffel95b.html ] on Cusmano's talk at ICSE 1995.

CusumanoSelby97

Michael A Cusumano & Richard W Shelby
How Microsoft Builds Software
Commun ACM V40n6(Jun 1997)pp53-61 CR9711-0916
=ADVERT [CusumanoSelby95]

CusumanoYoffie98

Michael A Cusumano & David B Yoffie
Competing on Internet Time
Free Press (Simon & Shuster) NY NY 1998 ISBN0-684-85319-1 HD9696.65.U64N473
=EXPERIENCE ECONOMICS PEOPLE PROCESS Netscape
1. Part in Commun ACM V42n10(Oct 1999)pp??-??
2. Note: Confirming instance of theories in [Botting97a]
3. Internet implied a changing situation but Internet time does not last for ever!
4. Andreesen claims his processes are based on rejecting processes he had seen bog down while an intern in IBM: trying to finish a perfect product before delivering anything.
5. Initially stressed innovation and time to market, later needed to add reliability and architecture to enter corporate market.
6. Netscape and MS avoid researching new technologies "Rocket science" in favor of exploiting other people's inventions.
7. Many at Netscape Equated SQA with testing! To increase quality, hire more testers!
8. As with MS, avoid checkout;lock;checkin delays by frequent builds to detect incompatibilities. Synchronize and Stabilize also IEEE Computer Magazine V32n10(Oct 1999)pp60-69.
9. Parallel development of several releases at one time.
10. Dynamic specifications, time-boxed milestones, and multiple Betas.

Cutkoskyetal96

Mark R Cutkosky & Jay M Tenenbaum & Jay Glicksman
Madefast: Collaborative Engineering over the Internet
Commun ACM V39n9(Sep 1996)pp78-87
=TOOL DISTANCE ENGINEERING
Engineering Web: problems to solve security+standards+interactivity+organising site+people [ ACM_paper.html ]
ENGINEERING documents are a mixture of formal and informal information

Cutts88

Geof Cutts
Structured Systems Analysis and Design Methodology
Van Nostrand Reinhold NY NY 1988
=TEXT SAD ERD(cow format) DFD DAD(using std not ELH) SSADM PQRST

CybulskiReed92

Jacob L Cybulski & Karl Reed
A Hypertext Based Software Engineering Environment
IEEE Software V9n2(Mar 1992)pp62-68
=ADVERT HyperCASE

CysneirosLeite04

Luiz Marcio Cysneiros & Julio Cesar Sampaio do Prado Leite
Nonfunctional Requirements: from elicitation to Conceptual models
IEEE Trans Software Engineering V30n5(May 2004)pp328-350
=CASESTUDY operational QUALITIES REQUIREMENTS NFR UML LEL CR 0504-0459
NFR::="Nonfunctional Requirement".
LEL::= "Language Extended Lexicon", project glossary.
NFR_graph::lattice, mapped to class diagrams etc..
Figures have spelling mistakes & they ignore UML stereotypes & tags.
Can not handle Qs like maintainability that "do not demand actions to be performed by the system".

D'Souza93

Desmond F D'Souza
A Comparison of Object-Oriented Analysis and Design Methods and Application Domains
OOPSLA 1993 Tutorial Notes # 2 ACM PRESS
=SURVEY METHODS OBJECT-ORIENTED

D'Souza98

Desmond D'Souza
Interface-Centric Design
Software Development Magazine V6n6(Jun 1998)pp43-44+46-47
=ADVERT for UML book [D'SouzaWills98]
type models describe vocabulary
collaborations via interfaces
patterns

D'SouzaWills98

Desmond D'Souza & Alan Willis
Objects, Components, and Frameworks with UML: the CATALYSIS approach
AddisonWesleyLongman Reading MA 1999 ISBN 0-201-31012-0 CR9903-0146
=EXAMPLES OOA/D UML CATALYSIS

DAmbrosLanzaLungu09

Marc D'Ambrose & Michele Lanza & Mircea Lungu
Visualizing co-change information with the evolution radar
IEEE Trans Software Engineering V35n5(Sep/Oct 2009)pp720-735
=TOOL GRAPHIC EVOLUTION MODULE CHANGE CVS Java PACKAGES FILES
The image shows a central module and all the other modules surrounding it.
A Module is a slice of the pie and contains files.
The files are shown as circles with size proportional to the degree of change.
Their angle of a file is determined by their name with in each module.
Their distance depends on the degree that they are changed at the same time as the central module.
Relies on a revision /configuration control system that records all changes in time.
Tested on one maintenance project.

DaCapo08

Stephen M Blackburn & Kathryn S McKinley & Robin Garner & Chris Hoffman & Asjad M Khan & Rotem Bentzur & Amer Diwan & Daniel Feinberg & Daniel Frampton & Samuel Z Guyer & Martin Hirzel & Antony Hosking & Han Lee & J Eliot & B Moss & Aashish Phansalkar & Darko Stefanovic & Thoms VanDrunen & Daniel von Dineklage & Ben Wiedemann
Wake Up and Smell the Coffee: Evaluation methodology for the 21st century
=ADVERT JAVA BENCHMARKs PERFORMANCE METRICS
Commun ACM V51n8(Aug 2008)pp83-89 [ 1378704.1378723 ]
Developing a useful benchmark is time consuming.
Using them needs understanding of relevant workloads, good experimental design, and rigorous analysis.
Benchmark research is underfunded.

DagRegnellGervasiBrinkkemper05

Johan Natt och Dag & Bjorn Regnell & Vincenzo Gervasi & Sjaak Brinkkemper
A Linguistic-Engineering Approach to Large-scale requirements Management
IEEE Software Magazine V22n1(Jan /Feb 2005)pp32-39
=IDEA LANGUAGE SIMILARITY DOCUMENTATION RETRIEVAL REQUIREMENTS Map documents into vector space and use cos(angle) to measure matches when ret rieving. Use log functions to scale the frequency of occurrence of words (formula is su spect)
Applied to matching market requirements to business requirements.

DahlbomMathiassen97

Bo Dahlbom & Lars Mathiassen
The Future of Our Profession
Commun ACM V40n6(Jun 1997)pp80-89
=SURVEY of literature re ENGINEER: artifact(build) vs Culture(help/evolve) vs Power(change). Machanistic vs Romantic. Leads to a new curriculum stressing what RJB calls ANALYSIS POSTMODERN

Dahletal72

O Dahl & E W Dijkstra & C A R Hoare
Structured Programming
Ac Press NY NY 1972
=TEXT sequential non-sequential PURPOSE Technical
Once called "The Old Testament".

DaiXieLongNg07

Yuan-Shun Dai & Min Xie & Quan Long & Szu-Hui Ng
Uncertainty Analysis in Software Reliability modelling by Bayesian Approach with Maximum-Entropy Principle
IEEE Trans Software Engineering V33n11(Nov 2007)pp781-795
=THEORY PROBABILITY RELIABILITY PREDICTION
Problems: few tests fail, inorporating prior information, allowing uncertainty in modelling to reduce reliability.
MEP::= "Maximum-Entropy Principle", choose an a prior distribution to maximize the entropy given the known data.
For distribution p, entropy(p):= E(-ln(p(_))).
Use Bayesian a postiori formula to encorporate data from tests.
Use simulation and analysis to predict relibilities of whole system.
Gives examples.
Refers to texts for calculations of MEP.

DalaKamathKolarikSivaraman04

Nikuni P Dala & Manjunath Kamath & WilliamJ Kolarik & Eswar Sivaraman
Toward an Integrated Framework for Modeling Enterprise Process
Commun ACM V47n3(Mar 2004)pp83-86
=ADVERT BUSINESS PROCESS MODELLING IMPROVEMENT ERP EPML XML Petri Analysis TED
Need to model/implement distributed.
Need for process semantics.
Need to link business and enginering.
Graphic front-end(EPML) <->XML<-> formal Back-end. Analise back end.
NSF Scalable Enterprise Systems Initiative.
EPML::="Enterprise Process Modelling Language".
Graphic showing: activities (Human, Computer, Machine), logic and decision logic, data icons, control flows , (input, output)><( material, data), timing triggers.
TED::="Task Execution Diagram". Analysis petri nets: design (termination, deadlock, safety) + performance (resource assignment, simulation, timing, success vs time statistics)

DalalMcIntosh94

Siddhartha R Dalal & Allen A McIntosh
When to stop Testing for Large Software Systems with Changing Code
IEEE Trans SE-30n4(Apr 1994)pp318-323
=THEORY ECONOMIC TEST MAINTENANCE

DamasLambeauDupontLamsweerde05

Christophe Damas & Bernard Lambeau & Pierre Dupont & Axel van Lamsweerde
Generating Annotate Behavior Models from End-User Scenarios
IEEE Trans Software Engineering V31n12(Dec 2005)pp1056-1073
=DEMO INTERACTIVE TOOL SCENARIOS MODEL MSC LTS FLUENTS use-cases
Given positive and negtive scenarios (sequence charts) the system asks questions in the form of scenarios.
It then generates a state-based model to fit all the scenarios. It uses fluents and grammar induction to create a Labeled Transition System (LTS) that fits the scenarios and annotates each state with fluents. The fluents provide a meaningful interpretation of the state.
Fluents have a name, start and end events, and an initial value. Booleans. Example: doorOpen. [GiannakopoulouMagee03]

DamianChesan06

Daniela Damian & James Chesan
An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management
IEEE Trans Software Engineering V32n7(Jul 2006)pp433-453
=EXPERIENCE REQUIREMENTS PROCESS IMPROVEMENT ACUS
Evidence that collaborative and iterative analysis and negotiation of requirements into testable scenarios improves estimates and quality.
Evidence that change management reduces requirements creep.
Important contributions from forming cross-functional teams, group-analysis, traceability, and decomposition.

DamianEberleinShawGaines00

Daniela E Herlea Damian & Armin Eberlein & Mildred L G Shaw & Brian R Gaines
Using different communications media in requirements negotiation
IEEE Software Magazine V17n3(May/Jun 2000)pp28-36
=EXPERIMENT REQUIREMENTS PEOPLE ORGANISATION
2 conflicting customers + 1 systems analyst + 1facilitator
face to face is not the best!
don't put all your customers in one room.

DamianiEtal06

Ernesto Damiani & Brian Fitzgerald & Walt Scacchi & Marco Scotto & GianCarlo Succi
Open source systems: IFIP Working Group 2.13 Foundation Conference on Open Source Software, June 8-10, 2006, Como, Italy (IFIP International Federation for Information Processing)
Springer-Verlag New York, Inc., Secaucus, NJ, 2006.
=PROCEEDINGS HISTORY OPEN SOURCE F/OSS PROCESS PSYCHOLOGY ECONOMICS SOCIOLOGY USAGE CR 0802-0110
Academic.
F/OSS projects are not chaotic but self organizing. A mature project is a collection of groups of people who work together. Face-to-face friendships influence the makeup of groups. The 'onion' model: a permanent, small, elite core of developers with recognizable subgroups.
Outer layers of a project are transient debugging groups that stay together as they move from project to project.
Prestige comes from sharing information like in scientific research.

DamianiFuginiBelletini99

E Damiani & M G Fugini & C Belletini
A Hierarchy-Aware Approach to Faceted Classification of Object-Oriented Components
ACM TOSEM V8n3(Jul 1999)pp215-262 + Corrigenda V8n4(Oct 1999)pp425-472
=TOOL REUSE COMPONENT FRAMEWORK OBJECT-ORIENTED Isa MFC C++ Borland Delphi Facetted descriptors

DamonJacksonJha96

Craig A Damon & Daniel Jackson & Somesh Jha
Checking Relational Specifications With Binary Descision Diagrams
Proc 4th ACM SIGSOFT 96 Symp on the Foundns of Software Eng: ACM SIGSEN V21n6(Nov 1996)pp70-80
=DEMO MODEL CHECKING BDDs
Z-like specs checked via testrolog-type diagrams
BDDs::=Binary Decision Diagrams

Daneva04

Maya Daneva
ERP Requirements Engineering Practice: Lessons Learned
IEEE Software Magazine V21n2(Mar/Apr 2004)pp26-33 +CR 0705-0527
=EXPERIENCE REQUIREMENTS reuse ASAP ERP
13 lessons learned mainly reinforcing known results!
cooperation win-win team communication learning are good
reuse needs management: query assumptions, analyze risks, plan, do, measure...
need data modeling
lookout for unofficial requirements leaking into project.

DanforthTomlinson88

S Danforth & C Tomlinson
Type Theories and Object Oriented Programming
Comp Surveys V20n1 (pp29-72)Mar 1988
=THEORY object-oriented logic Reality

DangleLarsenShawZelkowitz05

Kathleen Coleman Dangle & Patricia Larsen & Michele Shaw & Marvin V Zelkowitz
Software Process Improvement in Small Organizations: A Case Study
IEEE Software Magazine V22n5(Nov/Dec 2005)pp68-75
=CASE STUDY DSCS CMM
(dick)|-when does software process improvement merge into business process reengineering?
(dick)|-Rediscovers some trad systems analysis and design ideas.
Discoveries:
- Processes and process improvement should address business goals not just CMM dogma,
- Choose the sequence of improvements to support needs not CMM KPAs.
- TANSTAAFL: Improvement needs resources.
- Test proposed improvements on selected projects and change them before expanding enterprise-wide.
- Ongoing activities should drive the plans for introducing new processes.
- Start formal reviews immediately to provide feedback to stakeholders.
- Divide improvements up and delegate.
- Assess experience with software processes and SP improvement.

Daniels02

John Daniels
Modeling with a sense of Purpose
IEEE Software Magazine V19n1(Jan/Feb 2002)pp8-10
=ESSAY MODELs REALITY SPECIFICATION TECHNICAL UML
Three types of model: World/conceptual, Specification, Implementation
Maps UML notations to types of model (eg UseCase-> spec)
Proposes using three UML stereotypes: <<concept>>, <<type>>, <<class>>

DanoBriandBarbier97

Benedicte Dano & Henri Briand & Frank Barbier
An Approach Based on the Concept of Use Case to Produce Dynamic Object-Oriented Specifications [RE'97] p54-64
petri-nets

DarcyKemerer05

David P Darcy & Chris F Kemerer
OO metrics in Practice
IEEE Software Magazine V22n5(Nov/Dec 2005)pp17-19
=ADVERT =SURVEY CK METRICS Object-Oriented

Dasgupta89

Subrata Dasgupta
The Structure of Design Processes
pp1-62 of Yovitz(ed)89
=THEORY ENGINEERING lifecycle=scientific discovery

Darwiche10

Adnan Darwiche
Bayesian Networks
Commun ACM V53n12(Dec 2010)pp80-90 [ 1859204.1859227 ]
=ADVERT BAYES PROBABILITY NETWORK CAUSALITY BBN HMM HIDDEN MARKOV
Good description of the theory, practice, and possibilities of Bayesian models.
Source [Pearl88]

Dasgupta91

Subrata Dasgupta
Design Theory and Computer Science: Processes and Methodology of Computer Systems Design
Cambridge U Press NY NY 1991(Tracts in theoretical Comp Sci)
=THEORY ENGINEERING methodology
Reviews: CR9207-0475
Am Math Monthly V100n4(Apr 1993) page 423
1. plausibility::={undetermined, assumed, validates, refuted}.

Dashboard08

Project Dashboard Initiative
Project Dashboard
Sourceforge [ http://processdash.sourceforge.net/ ]
=UNTESTED =TOOL PSP TSP GRAPHIC MANAGEMENT DEFECTS QUALITITES ESTIMATION
Notes [click here if you can fill this hole]

Date00

Christopher J Date
What not how: the business rules approach to application development
Addison-Wesley Longman Boston MA 2000 pp131 $24.95 ISBN 0-201-70850-7 CR0011-0557 H.2.0 qa76.76 a65 d375 2000
=ADVERT RULES SQL LOGIC LPC TABLES

DateDarwen06

Christopher J Date & Hugh Darwen
Databases, Types, and the Relational model
Addison Wesley Longman Publishing Co, Inc., Redwood City, CA, 2007
=THEORY DATA Rejects SQL. Back to Codd.

DateFagin92

C J Date & Ronald Fagin
Simple conditions for guaranteeing higher normal forms in relational databases
ACM Trans Database Systems V17n3(Sept 1992)pp465-476
=THEORY DATA NORMALIZATION 5NF 4NF PJ/NF(Projection-join)

DatteroGallup04

Ronald Dattero & Stuart D Gallup
Programing Language and Gender
Commun ACM V47n1(Jan 2004)pp99-102
=POLL 37398 PEOPLE LANGUAGES GENDER COBOL Java C++ SQL HTML
Roughly 80/20 male/female split.
Experience:= distribution (..1.yr +> 11%, 1..2.yr+>16%, 3..5+>33%, 6..10+>20%, 11..14+>8%, 15.yr.. +>12%)
Languages:=(HTML+>36%, SQL+>29%, VB+>23, JavaScript+>23%, Java+>18%, C +>17%, "C++"+>16%, Oracle+>13%, ASP+.13%, Perl+>11%, ActiveX+>10%, Basic+>9%, "VisualC++"+>9%, OOP+>8%, COBOL+>7%, ...).
Most have 2 languages.

DavanbuStubblebine02

Premkumar T Davanbu & Stuart G Stubblebine
Stack and Queue Integrity on a Hostile Platforms
IEEE Trans Software Engineering V28n1(Jan 2002)pp100-108
=THEORY ADTs without trust

Davidson88

Colin M Davidson
Quicksort Revisited
IEEE Trans Soft Eng VSE-14n10(Oct 1988)pp1480-1481
=DEMO METHOD new Quicksort with no recursion [MillsLinger86]
inspired new way to derive quicksort: put unsorted segments into a set and so no stack and no recursion.

DaviesDavies97

Byron Davies & Victoria Bryan Davies
Patching onto the Web: Common LISP Hypermedia for the Intranet
Comm ACM V40n5(May 1995)pp66-69
ADVERT LISP WEB/NET CL-HTTP
CL-HTTP to put large factory database onto the WWW

DaviesJ94

Jim Davies
Specification and proof in real-time CSP
Cambridge Univ Press NY NY ISBN 0-521-45055-1(distinguished dissertation) CR9407-0395 AMM Review: timed denotational semantics
=THEORY SEMANTICS TIMING SPECIFICATION PROOF

DavisA90

Alan M. Davis
Software Requirements: Analysis and Specification
Prentice Hall Englewood Cliffs NJ 1990 ISBN 0-13-824673-4 BNB89-16392 QA76.76 D47 D38 1990
=TEXT SADT DFD DATA Coad bibliography
Reviews: IEEE Software magazine v11n2(Mar 1994) CR9112-0915.
Revised as DavisA93a

DavisA92

Alan M. Davis
Operational Prototyping: A New Development Approach
IEEE Software Magazine V9n5(Sep 1992)pp70-78
lifecycles
1. Throwaway vs evolutionary prototyping
2. Operational= Throwaway+evolutionary
3. Implement a high quality solution for understodd functions. In the field prototypers tryout ideas and then deletes them. When well understood and worthwhile the prototyper submits a change request. Periodically a new baseline is released.

DavisA93a

Alan M Davis
Software requirements: objects & functions and states
Prentice Hall Englewood Cliffs NJ 1993
=TEXT SADT DFD DATA Coad bibliography

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
1. Structured
2. Object
3. Maturity
4. C
5. Prototyping
6. CASE
7. Reuse
8. Comquats (COMercial off-the-shelf QUAlity sofTware)
  Tom Adams letter describes methodology life cycle
9. good project with new idea
10. idea reduced to a buzz phrase
11. complex methodology based on just the buzz phrase
12. many seminars
13. many books
14. Many many failed projects
  Richard Wells
15. I reuse and am careful in C.
16. CASE does not address my problems.

DavisA94a

Alan M. Davis
Counterpoint: There are no bad guys and no one has the "Truth"(Side bar in Glass94a)
IEEE Software magazine v11n3(May 1994)pp92
=DEBATE

DavisA94b

Alan M. Davis
Rewards of Taking the Path Less Traveled
IEEE Software magazine v11n4(Jul 1994)pp100-101+102
=ESSAY IMPROVEMENT CUSTOMER PROTOTYPES FORMAL SQA REUSE
1. Get the Big Picture or - little risk, little cost, proven to give some benefit, fuddy-duddy
2. Talk to your customers
3. Build Prototypes
4. Do Trade-Off Analysis
5. Play with Formal methods
6. Review, Walkthrough, inspect
7. Salvage

DavisA94c

Alan M. Davis(ed)
Fifteen Principles of Software Engineering
IEEE Software Magazine V11n6(Nov 1994)pp94-96&101
=ADVERT and Excerpt from [DavisA95]
1. 1. Make Quality Number 1
2. 2. High-Quality Software is Possible
3. 3. Give Products to Customers Early
4. 4. Determine the Problem before Writing the Requirements
5. 5. Evaluate Design Alternatives
6. 6. Use an Appropriate Process Model
7. 7. Use Different Languages for Different Phases
8. 8. Minimize Interlectual Distance
9. 9. Put Technique before Tools
10. 10. Get it Right Brefore You Make it Faster
11. 11. Inspect Code
12. 12. Good Management is more importatn than Good Technology
13. 13. People are the Key to Success
14. 14. Follow with Care
15. 15. Take Responsibillity
16. -------- -- --(Table page 95)
17. 16. Understand the Customers Priorities
18. 17. The more they see the more they want
19. 18. Plan to through one away
20. 19. Design for Change
21. 20. Design without documentation is not design
22. 21. Use tools, but be realistic
23. 22. Avoid tricks
24. 23. Encapsulate
25. 24. Use Coupling and cohesion
26. 25. Use McCabe Complexity Measure
27. 26. Don't Test your own Software
28. 27. Analyze Causes for Errors
29. 28. Realize that Software's Entropy Increases
30. 29. People and Time are not Interchangeable
31. 30. Expect Excellence

DavisA95

Alan M Davis
201 Principles of Software Engineering
McGrawHill NY NY 1995 $24.95 ISBN 0-07-015840-1 CR9512-0926(Praise by Tom DeMarco)
=HANDBOOK [DavisA94c]

DavisA95a

Alan M Davis
Software Prototyping
Advances in Computers V40(1995)pp39-63
=EXPERIENCES PROTOTYPING COST QUALITY
Is not instantly cheaper! Choose throwaway or evolutionary.
Evolution demands good QUALITY from the beginning and maintained for ever.

DavisA00

Alan M Davis
The Software Company Machine
IEEE Software Magazine V17n2(Mar/Apr 2000)pp14-15
=THEORY ORGANISATION
(R&D + Financial + Marketting& Sales) engines

DavisA03

Alan M Davis
The Art of Requirements Triage
IEEE Computer Magazine V36n3(Mar 2003)pp42-49
=CASESTUDY REQUIREMENTS vs SCHEDULING ESTIMATION PROBABILITY vs FIRST-TO-MARKET
1. Keep a simple hierarchical list of requirements.
2. Record dependencies.
3. Add effort needed, importances to different stake holders.
4. Importance of super-requirement > max sub-requirements.
5. Involve customers, developers and financial representatives in triage.
6. Foster teamwork between all stake holders.
7. Nothing is absolute, think in terms of probabilities in a given time.
8. Base probabilities on previous projects.
9. You can do triage by paring down the optimistic plan or expanding the pessimistic plan.
10. Plan multiple releases but re-plan before every new release.
11. Don't be intimidated into accepting schedules that are either technically impossible or too late to market. Look for a creative compromise that gives a high probability of both.
12. Better 90% now than 95% in sic months.
Partition requirements into (must have + must not have + may or may not have) in this release. Use priorities to schedule the third group.
Use schedule probability graphs: map dates>->probability of completion by that date.
When there 100s of requirements group them into features/"super-requirements" capable of unified implementation and sale.
Refers to A Davis03? "Just enough Requirements Management", Prentice Hall Int 2003.

Davis03a

Alan M Davis
System Phenotypes
IEEE Software Magazine V20n4(Jul/Aug 2003)pp54-56
=IDEA REQUIREMENTS PHENOTYPE vs DESIGN CODE GENOTYPE
The difference between requirements and design is not a matter of detail or refinement.
Examining a fly in detail under a microscope shows you the phenotype not the genetic. Genetics is not always expressed. Phenotype is observable.
Requirements are observable even if highly detailed. They constrain the internal structure (genotype).
Requirements expressed(spoken, drawn,..) in the customers language not technical jargon.

Davis05

Alan M Davis
Just enough Requirments management: where software development meets marketting
Dorset House NY NY 2005, 240 pages, ISBN 0932633641 CR 0712-1159
=UNREAD EXPERIENCES REQUIREMENTS ELICITATION TRIAGE SPECIFICATION
May also have been published in 2003. See [DavisA03] above

Davisetal88

Alan M. Davis & Edward H Bersoff & Edward R Comer
A Strategy for Comparing Alternative software Development Life Cycle Models
IEEE Trans Soft Eng VSE-14n10(Oct 1988)pp1453-1461
=THEORY METHODS PROCESS USER vs TIME
plot USER needs and functionallity supplied against time

Davisetal91

Alan M. Davis & Peter A Freeman
Requirements Engineering (Guest Editors Introduction)
IEEE Trans SE-17 n3(Mar 1991)pp210-211
=EDITORIAL REQUIREMENTS RESEARCH

Davisetal94

Alan M. Davis & Pradip Sitaram
A Concurrent Process Model of Software Development
ACM SIGSOFT Software Eng Notes V19n2(Apr 1994)pp38-51
=THEORY non-sequential process statechart ...

DavisM11

Michael Davis
Computer ethics: will software engineering ever be engineering?
Commun ACM V54n11(Nov 2011)pp32-34 [ 2018396.2018407 ] Rebuttal GM Samaras V55n1(Jan 2012)p6 [ 2063176.2063168 ]
=ESSAY ENGINEERING KNOWLEDGE
SWEBOK omits knowledge (eg chemistry) found in engineering. Also misdefines engineering.
Software engineering has its own methods.
But engineering is starting to look like software engineering!

DavisMorgan93

John Davis<74155.416@compuserve.com> & Tom Morgan
Object-Oriented Development at Brooklyn Union Gas
Special Theme "Making OO Work" IEEE Software V10n1(Jan 1993)pp67-74
=EXPERIENCE OBJECT-ORIENTED OOA/OOD PL/I CICS
1. p74 "Developers shouldn't try to specify the system more than a few steps into its life cycle"
2. pp72-73:Reuse during maintenance - 2K lines added but 40K lines used to support them
3. pp70: "The largest single source of technical program erors [...no] real garbage collector."
4. pp68: 3 layers{Interface, Process, Busness-Object}

DavisMS00

Mathew S Davis
an object-oriented approach to constructing recursive descent parsers
ACM SIGPLAN notices V35n2(Feb 2000)pp46-51
=DEMO TECHNICAL SMALLTALK DDD

DavisR07

Randall Davis
Magic Paper: Sketch-understanding Research
IEEE Computer Magazine V40n9(Sep 2007)pp34-41
=DEMO TABLET SKETCH GRAPHICS CASE Rose USER
Tantalysing glimpse of a tool that front-ends Rational Rose to turn a rough sketch of a class diagram into Java Code.
Discusses issues in recognizing and parsing roughly hand drawn graphics.

DavisRetal96

Randall Davis & Pamela Samuelson & Mitchell Kapor & Jerome Reichman
A new View of Intellectual Property and Software
Commun ACM V39n3(Mar 1996)pp21-30
=IDEA ETHICS PROPERTY

DavisTE00

Thomas E Davis
Object-Oriented Design in Procedural Environments
Dr. Dobbs Journal #313(Jun 2000)pp68+70-72
=DEMO
Reinvents techniques used in FORTRAN and C!

Dean96

Neville Dean
The Essence of Discrete Mathematics
Prentice Hall Hemel Hempstead UK 1996
=TEXT DISCRETE MATHEMATICS
part of the "Essence of Computing" series 1996. See DeanHinchey95

DeanCordy95

Thomas R Dean & James R Cordy
A Syntactic Theory of Software Architecture
IEEE Trans on Software Eng VSE-21n4(Apr 1995)pp301-314 CR9602-0119 D.2.0
=THEORY ARCHITECTURE DFDs GRAMMAR

DeanGhemawat08

Jeffrey Dean & Sanjay Ghemawat
MapReduce: Simplified Data Processing on Large Clusters
Commun ACM V51n1(Jan 2008)pp107-113
=EXPERIENCE FUNCTIONAL PROGRAMMING Google DATA C++ LIBRARY FP NONSEQUENTIAL PIPE
Very large numbers of problems have been programmed to run on large clusters. Each is written as two (2) functions:
map: Key><Value><Data -> List(Key>< Value),
reduce: (Key->List(Value)) ->List( Value).
Also, implicitly the system has a sort function:
sort: List(Key><Value) -> (Key->List(Value).
System applies map to some data, sorts data by key and passes it to reduce.
map; sort; reduce
All the concurrency, distribution, fault tolerance etc. is provided by the system not the programmer.
Note: the idea using functions was in LISP and FP(Jim Bachus). Similar techniques used in UNIX/Linux Shell scripts, but dates back to the COBOL SORT verb! Part of MATHS.
For an attempt to express this in Haskell see [Lammel08]

DeanGhemawat10

Jeffrey Dean & Sanjay Ghemawat
MapReduce: A Flexible Data Processing Tool
Commun ACM V53n1(Jan 2010)pp72-77 [ 1629175.1629197 ]
=ADVERT =EXPERIENCE GOOGLE TOOLS MapReduce Hadoop FORMATS Protocol Buffer
Reply to [StonebrakerEtAl10]
Has some conclusions (p77) for speeding up MapReduce processes.

DeanHinchey95

Neville Dean & Michael G Hinchey
Introducing Formal Methods Through Role-playing
Papers of the 26th SIGCSE Technical Symposium on Computer science Education: ACM SIGCSE Bulletin V27n1(Mar 1995)pp302-36
=EDUCATION FORMAL Z

DeAntonellisZonta90

Valeria De De Antonellis & Bruta Zonta
A Disciplined Approach to Office Analysis
IEEE Trans SE-16n8(Aug 1990)pp822-828
=DEMO System Reality

DeBakker75

J W de Bakker
Flow of Control in the Proof of Sequential Programs
Proc 16th Ann Symposium on the Fundamentals of Computer Science Berkeley California(pp29-33) IEEE Computer Society 1975
=THEORY regular logic

DeBakker96

Jaco de Bakker
Control Flow Semantics
MIT Press Cambridge MA 1996 ISBN0-262-04154 $50 CR9709-0654(F.3.2)
=MATHEMATICAL 27 LANGUAGES MATHEMATICS TOPOLOGY Complete Metric spaces

Deck01

Michael Deck
Managing Process Diversity while Improving your Practice
IEEE Software Magazine V18n3(May/June 2001)pp21-27
=EXPERIENCE IMPROVEMENT EVOLUTION CLEANROOM PEOPLE RISKS INCREMENTS ONE-SIZE CMM
Even in one project "one size does not fit all" parts of the project. For example inspection do not help you test a prototype algorithm for adequate performance. Remotely executed software must be derived in the most rigorous zero-defect approach but locally executed software does not need this.
People -- especially new ones -- are a prime risk factor.
Diversity plan distinguishes three levels for each part of a process: Foundation, standard and advanced.
A practice can be required, recommended, or optional.

DedekeLiberman06

Adenekan (Nick) Dedeke & Benjamin Liberman
Qualifying Use Case Diagram Associations
IEEE Computer Magazine V39n6(Jun 2006)pp23-29
=DEMO UML USE CASE DOMAIN MODEL DATA FLOWS DFDs
Analyzing data needed for a use case and linking it to a conceptual domain model leads to better use cases.
Extension to UML2.0 use case diagrams.
(dick)|-why not use a DFD? [ papers/rjb04bDFDs/ ]

DedeneSnoeck94

G Dedene & M Snoeck<fdbaa30@cc1.kuleuven.ac.be>
MERODE: A Model-Driven Entity-Relationship Object-oriented DEvelopment method
ACM SIGSOFT Software Engineering Notes V19n3(Jul 1994)pp51-61
=ADVERT METHOD DAD REGULAR-EXPRESSION NONSEQUENTIAL ERD
1. object_type::="<" @Events "," RegularExpression(Elements=>Events) ">", Restriction
```
  RE\S
```
  more deterministic Parallel composition of object types. They use "||" for interleaving type semantics
For an improved method see [SnoeckDedene98]

DeekMcHugh07

Fadi P Deek & James A M McHugh
Open source: technology and policy
Cambridge UP NY NY 2008 ISBN 0-521-88L03-X
=TEXT Open source

DeGraceStahl90

Peter DeGrace & Leslie H Stahl
Wicked Problems and Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms
Yourdon Press NY NY 1990 QA76.758.D44 1990 CR9208-0538
=POLEMIC METHODS vs PROBLEMS
many DFDs of methods.
wicked_problem::=The solution is part of the problem & no stopping rules & not true/false. [rittel & webber 73: dilemmas in a genl theory o planning policy sciences v4pp155-169].
handcuffs and hacking.
(dick)|-possible confusions: COBOL=DP. top-down=waterfall. [Cardetal87]

DeGraceStahl93

Peter DeGrace & Leslie H Stahl
The Olduvai imperative: CASE and the state of software engineering practice
Yourdon Press NY NY 1993 ISBN 0-13-161100-3 CR9401-0006
=ESSAY METHODS
1. CR by RL Glass: Folksy sophisticated, pragmatic yet intellectual, call-a-spade-a-spade, Two different cultures - Roman and Greek. will be cheered by practitioneers and disliked by academics and managers.
2. Greek::=individual brilliance, informal methods, problem-focussed people, empirical/inductive.
3. Roman::= group, formal, management, analytic/deductive.
4. QV: Gods of Management...

DeganoEtAl08

Pierpaolo Degano & Rocco De Nicola & Jose Meseguer (eds)
Concurrency, Graphs and Models: Essays dedicated to Ugo Montanari on his 65th Birthday
LNCS 5065 Springer Verlag Berlin Heidelberg (2008) CR 0909-0812
=FESTSHRIFT MATHEMATICS GRAPH THEORY CONCURRENCY NON-SEQUENTIAL CATEGORIES SEMIRINGS TOOLS HISTORY
Includes [AstesianoReggioRicca08] UML BUSINESS ... [Baetan08] ALGEBRA EQUATIONS AUTOMATA ... [BeauxisPalamidessiValencia08] NONSEQUENTIAL BAGS... [HermenegildoEtAl08] LANGUAGE Ciao ... [Quaglia08] BIOLOGICAL CELLULAR SYSTEMS...

deJong07

Jennifer deJong
It's Lean, But Is It Agile? Iterative methods are closely aligned
SD Times (15 Jun 2007) [ story-20070615-04.html ]
=ARTICLE AGILE = LEAN XP Crystal Beck Cockburn

deGuzman0jedaValverdes95

I P de Guzman & M Ojeda & A Valverdes
A formal identifiaction between tuples and lists with application to list-arithmetic categories
Acta Inf V32n1(1995)pp61-78 CR9602-0125 D.3.1
=THEORY DATA STRUCTURES

DelamaroMaldonadoMathur01

Macio E Delamaro & Jose c Maldonado & Aditya P Mathur
Interface Mutation: An Approach for Integration Testing
IEEE Trans Software Engineering V27n3(Mar 2001)pp228-247
=DEMO TESTING MODULES

Delany76

Samuel R Delany
Triton: Some Informal Remarks Toward the Modular Calculus Part One
Corgi Edn. 1977 Transworld London UK
=FICTION =SEMINAR language SEMANTICS theory structure

DelatteHeitzMuller93

B Delatte & M Heitz & J F Muller
HOOD: Reference Manual 3.1
Prentice Hall International(UK) Mason Paris France 1993 ISBN 0-13-396243-1 CR9411-0756
=HANDBOOK Object-oriented method

DelenDalaBenjamin05

Dursun Delen & Nikunj P Dala & Perakath C Benjamin
Integrated Modeling: The key to Holistic understanding of the enterprise
Commun ACM V48n4(Apr 2005)pp107-112
=ADVERT ERP MODELING TOOL PROCESS FUNCTION DATA COST ONTOLOGY PQRST GERAM IDEF CPM MODELMOSAIC REPOSITORY
GERAM::= See http://www.cit.gu.edu.au/~bernus/taskforce/

Delgrande98

James P Delgrande(Simon Fraser U, Burnaby, BC, Canada)<jim@cs.sfu.ca>
On first-order conditional logics
Artif Intell V105n1-2(Oct 1998)pp105-137 CR9903-0211
=THEORY defeasible LOGIC possible worlds Kripke
1. Proposes replacing for all x( P implies_if_normal Q) by P implies_for_all_normal[x] Q
2. Examples: all birds fly, penguins are birds, penguins don't fly.
3. All elephants like their keepers, unless the keeper is mean like Fred in which case they don't like him, unless the elephant is Clide who likes all the keepers.

DeLine01

Robert DeLine
Avoiding Packaging Mismatch with Flexible Packaging
IEEE Trans Software Engineering V27n2(Feb 2001)pp124-143 in ICSE'99 + Correction IEEE Trans Software Engineering V27n6(Jun 2001)p576
=DEMO MODULE ARCHITECTURE ware+packager NONSEQUENTIAL
Allows one piece of logic to be mapped into spreadsheet, CGI, yacc, ....
Stresses use of coroutines as more flexible than procedural code.

DeLineVenoliaRowan10

Robert DeLine & Gina Venolia & Kael Rowan (Microsoft Research)
Software Development with Code Maps
ACM Queue(Jul 4 2010) [ detail.cfm?id=1831329 ] & Commun ACM V53n8(Aug 2010)pp48-62 (Better pictures) [ 1787234.1787250 ]
=ADVERT TOOL GRAPHIC TECHNICAL CODE VISUALIZATION HCI CODE MAP VISUAL STUDIO CODE CANVAS
Another tool that generate graphic zoomable and editable images of code. But a tool based on what programmers already did!
A rare example of applying systems analysis to software engineering.

DeLineZelesnikShaw97

Robert DeLine & Gregory Zelesnik & Mary Shaw
Lessons on Converting Batch Systems to Support Interactions [ICSE'97]
=Experience architecture evolution
8 rules on page 203
no ref to Jackson's work in 1975.

DelisleGarlan90

Norman Delisle & David Garlan
A Formal Specification of an Oscilloscope
IEEE Software V7n5(sep 1990)
=DEMO FORMAL SPECIFICATION HARDWARE

DeLoachHartrum00

Scott A DeLoach & Thomas C Hartrum
A Theory-based representation for object-oriented domaon models
IEEE Trans Software Engineering V26n6(Jun 2000)pp500-517
=DEMO CATEGORY THEORY fits OMT O-SLANG
classes events sorts atttributes axioms

DeMarco79

Tom De Marco
Structured Analysis & Systems Specification
Prentice Hall 1979
=TEXT SAD DFD PURPOSE System

DeMarco80

Tom De Marco
Structured Analysis & System Specification
Yourdon Press NY NY
=HANDBOOK SAD DFD ERD PURPOSE System Reality

DeMarco88

Tom de Marco
Interview
IEEE Software v6n2(Mar 1988)pp92-93
=INTERVIEW object-oriented non-sequential

DeMarco95

Tom DeMarco
Why Does Software Cost So Much? And Other Puzzles of the Information Age
Dorset house 1995 CR9702-0104 rev IEEE Software Magazine VSE13N4(Jul 1996)pp134-135(Alan M Davis)
=ESSAYs PEOPLE COST

DeMarco03

Tom DeMarco
The McCarthy Protocols
Commun ACM V46n6(Jun 2003)pp24-25
=ADVERT TEAM PEOPLE MEETING CEREMONY PATTERN
Describes Jim and Michele's patterns for meetings, see
TeamorX::= See http://www.mccarthytech.com, and [McCarthyMcCarthy02]

DeMarco09

Tom DeMarco
software engineering: an idea whose time has come and gone
IEEE Software Magazine V26n4(Jul/Aug 2009)pp96+95 =ESSAY PROCESS CONTROL METRIC ESTMATING PLANNING
1982 book tried to control too much.
Only marginal projects need tight control.
Better to ask for incremental growth to better and better systems until time runs out.

DeMarco11

Tom DeMarco
All late projects are the same
IEEE Software Magazine V28n6(Nov/Dec 2011)pp104+103 [ lateprojects ] with discussion V29n1(Jan/Feb 2012)pp8-11
=ESSAY ESTIMATION COST LATE PROJECTS
Late projects start too late.
Either trying to catch a competitor, or to save money, or discovered need too late!
Discussions look at other possible reasons for failure.

DeMarcoBoehm02

Tom DeMarco & Barry Boehm
The Agile Methods Fray
IEEE Computer Magazine V35n6(Jun 2002)pp90-92
=DEBATE AGILE METHODS
Previous [Boehm02]
Individual skills or organizational rules?
Also see "Duking it out" in Software Development Magazine V10n7(Jul 2002)pp53-55

DeMarcoHruschkaEtAl08

Tom Demarco & Peter Hruschka & Tim Lister & Suzanne Robertson & James Robertson & McManamin
Adrenaline Junkies and Template Zombies: Understanding patterns of project behavior
Dorset House, NY NY 2008 pp248 ISBN 0932633676
=UNREAD PEOPLE PATTERNS PROJECTS PROCESSES
Contributions needed -- [click here DeMarcoHruschkaEtAl08 if you can fill this hole]

DeMarcoLister87

Tom DeMarco & T Lister
Peopleware: Productive Projects and Teams
Dorset House NYNY 1987
=TEXT PROCESS PEOPLE TEAM
from [Brooks95]

DeMarcoLister03

Tom DeMarco & Tim Lister
Risk Management during Requirements
IEEE Software Magazine V20n5(Sep/Oct 2003)pp99-101
=EXPERIENCE RISKS REQUIREMENTS PEOPLE POLITICS
Continuous public identification of risks to a project.
examples: arbitrary schedule, stakeholder conflict, scope creep, personnel loss, productivity variation.
Assign ranks to all requirements and express all outcomes in probabilities. Show growth of probability of delivering requirement as a graph. Risks of using vague requirements to hide non-agreement (non-concurrence)
Diagnose non-agreement/politics by precisely documenting data flows in and out of system.

DeMelo06

Darrion DeMelo
ReMoTe: A Complete tool to support software process management
CSUSB MS Presentation (Feb 24 2006)
=DEMO TOOL MANAGEMENT PROCESS RMT CHAT MESSAGES GANT BAR CVS BUGZILLA

DeMilloLiptonPerlis79

Richard DeMillo & Richard Lipton & Alan Perlis
Social processes and Proofs of Theorems and Programs
Commun ACM V22n5(May 1979) pp271-280, letters V22n11pp621-630
=ESSAY EXAMPLES MATHEMATICS PROOF LOGIC
p272: "There is simply no way to describe the history of mathematical ideas without describing the successive social processes at work on proofs."
See [Lakatos76] [Bauer92]
(DeMilloLiptonPerlis79)|-rigorous software development will also depend on social processes

DeMouraBjorner11

Leonardo de Moura & Nikolaj BjC8rner
Satisfiability modulo theories: introduction and applications
Commun ACM V54n9(Sep 2011)pp69-77 [ 1995376.1995394 ]
=ADVERT LOGIC FORMAL MATHEMATICS PROBLEM SOLVING TOOLS SMT SAT
SMT solve problems within specialized mathematical theories.
Example theory: difference arithmetic where every formula has form x-y<=c where x & y are variables and c is a constant.
SMT work with SAT solvers.
Several solvers for different theories can be combined.
Many problems about programs can be expressed in the theories with tractable solvers.

Demers81

Richard A. Demers
System Design for Usability
Commun ACM V24n8 (Aug 1981) pp494-501
=DEMO USER IBM System/38

DemirersGencel09

Onur Demirors & Cigdem Gencel
Conceptual Association of Functional Size Measurement Methods
IEEE Software Magazine V26n3(May/Jun 2009)pp71-78
=CASESTUDIES ESTIMATION FPA FSM UM

DempseyWeissJoneGreenberg02

Bert J Dempsey & Debra Weiss & Paul Jone & Jane Greenberg
Who is an Open Source Software developer
Commun ACM V45n2(Feb 2002)pp67-72
=HISTORY OPEN SOURCE LINUX ARCHIVE 4k contributions MetaLab LSM ibiblio.org
more European than US, more com than edu, more single submissions than many, some maintenance, mix of apps+utilities+games+system+etc
LSM::="Linux Software Map", defines data about a contribution, Net{ Title, Version, Entered=date, description, Primary-site: fields, ...}.
Archive at [ http://www.ibiblio.org ]

DemskyRinard06

Brian Demsky & Martin C Rinard
Goal-Directed Reasoning for specification-based Data Structure Repair
ICSE'05 & IEEE Computer Magazine V39n12(Dec 2006)pp931-951
=DEMO DATA SPECIFICATION SETS RELATIONS ABSTRACTION INVARIANTS CONSTRAINTS REPAIR FAULT AbiWorld CTAS Freeciv File System
In some cases it is better to repair a broken data structure incorrectly and continue running rather than crash and stop running.
Data structures can be repaired by using formal abstract specification in terms of Sets and Relationships.
Comparison with bespoke/domain specific fsck and chkdsk.
Fix each broken constraint in turn and use a Repair Dependence Graph to avoid infinite loops of repairs.
Lists actions to repair data structure.
Focuses on internal consistency rather than "REALITY" and as a consequence the whole application may work incorrectly.
Compare [KuncakLamZeeRinard06] that uses a similar abstraction/specification but includes domain constraints to model bot internal data structure consistency and external domain constraints.

DeneckerBruynooghe02

Marc Denecker & Maurice Bruynooghe
Logic Programming Revisited: Logic Programs as Inductive Definitions
ACM Trans Computational Logic V2n4(Oct 2001)pp623-654
=THEORY LOGIC Prolog INDUCTION

DenneCleland-Huang04

Mark Denne & Jane Cleland-Huang
The incremental funding method: Data-driven Software Development
IEEE Software Magazine V21n3(May/Jun 2004)pp39-47
=EXAMPLES ECONOMICS ROI COST-BENEFIT INCREMENTAL
Include value of each delivered increment as benefit with costs.

Denning90

Peter Denning
Human Error and the Search for Blame(editorial)
Commun ACM V33n1(Jan 1990)pp6-7
=EDITORIAL RISKS

Denning93

Peter J Denning
Educating a New Engineer
Comm ACM V35n12(Dec 1992)pp83-97
=EDUCATION ENGINEER

Denning94

Peter J Denning
Designing a Discipline of Software Design
Keynote address at the 7th SEI Conference on Software Engineering Education "Putting the 'Engineering' into Software Engineering" January 5-7 1994 San Antonio Texas USA
=IDEA REALITY ONTOLOGY [WandWeber90] cf [WiederholdWegnerCeri93] cf
?? S-->RPQ->T (ontological mapping)

Denning02

Peter J Denning
Flatlined
Commun ACM V45n6(Jun 2002)pp15-19
=ESSAY THINKING GRIDs 2dimensional GRAPH TABLE Science
Rather than set up a false P vs Q dichotomy, map out in two dimensions (low P..high P)><(low Q.. high Q). Thus 4 quadrants.
Example: science: understanding >< utility.
Example: software industry: technical excellence >< customer satisfaction.
Example: professions: technical skills >< value skills

Dennning03

Peter J Denning
Accomplishment
Commun ACM V46n7(Jul 2003)pp19-23
=ADVERT Language-action PHILOSOPHY PEOPLE SYSTEMS COORDINATION USER AI
People use language to make more or less explicit contracts for action. Trust comes from a promised action satisfying expectations.
action_loop::=#( a.request; b.promise; b.deliver; a.accept).
Watch out for miscommunication. Exposed by action.
Loss of market can come from lack of satisfaction in above loop between producer and consumer.
Used as a basis for Email client.
Management depends on handling action_loops.
There are protocols for inventing possibilities.
disclosure: Implicit awareness of signals about other's thoughts & feelings (but distorted). Need to consciously listen; react; adjust interpretation. [DenningDunham03]

Denning04

Peter J Denning
The Social Life of Innovation
Commun ACM V47n4(Apr 2004)pp15-19
=SURVEY INNOVATION ENGINEERING WEB
|-invention != innovation.
Innovation has a strong social component because it leads to change. Refers to [Drucker85] and adds a new kind of opportunity "marginal practices" from Spinoza % Dreyfus &Flores: "Disclosing New Worlds", MIT Press 1997 Adds a table of practice for innovation: Awareness, Focus+persistence, Listening+Blending, declarations, destiny, Offers, Networks+Institutions, Learning. Cognitive blindness: not seeing something and not knowing you didn't see it. applies theory to Tim Berners-Lee and the WWW.

Denning04b

Peter J Denning
The Field of Programmers Myth
Commun ACM V47n7(Jul 2004)pp1-20
=HISTORY EDUCATION programming vs computer science
(public)|- (myth_cs_is_p): computer science = programming != science.
Separate and link programming practice with algorithmic thinking/abstraction. "ladder of competence".
Teach error detection and correction

Denning04c

Peter J Denning
Network Laws
Commun ACM V47n11(Nov 2004)pp15-20
=SURVEY MATHEMATICS NETWORKS RANDOM GRAPHS POWER LAWS SMALL WORLDS
Clique: highly connected subset with few connections outside the clique.
Hubs: nodes with many links.
Broker: the only connection between a pair of cliques.
Bridge: connected to several cliques In many real networks the Pr[k links at a node] = (1/k)**p, "power law".
Accounted for by new nodes being created at random and connecting to nodes wit h larger numbers of links.
Hubs are key for securing and using a network.
Command a network by communicating intent and delegating decision making.

Denning05

Peter J Denning
Is Computer Science Science?
Commun ACM V48n4(Apr 2005)pp27-31
=HISTORY =SURVEY SCIENCE ENGINEERING TECHNOLOGY ART
Simulated dialog with a skeptic.
Notes internal doubts and discussion. Notes the credibility problem of research claims that were not tested before publication, and practical predictions that did not pan out.

Denning05b

Peter J Denning
The Locality Principle
Commun ACM V48n7(Jul 2005)pp19-24
=SURVEY =HISTORY LOCALITY

Denning07

Peter J Denning
Mastering the Mess
Commun ACM V50n4(Apr 2007)pp31-25
=ESSAY PROBLEMS INNOVATION THINKING
mess: disorder, no problem statement, controversy, doubtful causality, fixes don't work, ... "Normal"...
4 levels of mess and actions.
6 stratagems: declare, learn, question, many views, lead, disguise

Denning07a

Peter J Denning
Computing is a natural science
Commun ACM V50n7(Jul 2007)pp13-18
=ESSAY COMPUTING SCIENCE ARTIFICIAL
Refutes Herbert Simon's claim the that we study the "Science of the Artificial". [Simon69]
Claims that computation is found inside all other natural sciences -- not just as a tool but as a model of processes in their topic area.

Denning07b

Peter J Denning
The Choice Uncertainty Principle
Commun ACM V50n11(Nov 2007)pp9-14
=ESSAY RACE HAZARDS ARBITRATION SYNCHONISATION NON-SEQUENTIAL METASTABLE STATE flipflop Buridan
CUP::= "No choice between near-simultaneous events can be made unambiguously within a preset deadline".
9 refs. Many examples: hardware, software, and mundane.

Denning11

Peter J Denning
The profession of IT: The Grounding Practice
Commun ACM V54n12(Dec 2011)pp36-40 [ 2043174.2043188 ]
=IDEA CLAIMS EVIDENCE ARGUMENTS DATA cf TOULMIN
Grounded_claim::=a claim accompanied by sufficient relevant supporting evidence.
Objective vs subjective evidence.
Also: plausibility, balance, commitment.
Need to provide more than objective evidence when an innovation may change the culture.
Some claims depend on community opinions. But beware truthiness.
p40: Table describes the anatomy of a grounded claim.
Get into the habit of noticing what kind of grounds are presented when people present claims.

DenningDunham03

Peter J Denning & Robert Dunham
The Missing Customer
Commun ACM V46n3(Mar 2003)pp19-23
=FLAME CUSTOMER USER VALUE SATISFACTION TRUST ACADEMIC EDUCATION
argues that IT professionals, academics, and companies can focus on technical excellence rather than the impressions that a customer gets of the profession/company.
Four basic truths:=following
Net
1. Customers buy because of perceived future value but buy again because of remembered past satisfaction.
2. customer: Actor.
3. performer: Actor.
4. something: Thing.
5. performer provides something.
6. something satisfies customer.
7. customer trusts performer to provide something.
8. performer trusts the customer will be satisfied by something.
9. Note. money is not a required as part of this relationship.
(End of Net)

DenningDunham06

Peter J Denning & Robert Dunham
Innovation as Language Action
Commun ACM V49n5(May 2006)pp47-52
=ADVERT INVENTION INNOVATION PEOPLE
Based on the Language-Action Perspective [Dennning03]
Innovation is more than invention: innovation changes what people do.
Most innovation is a normal process.
Some innovations are bad and are|should be abandoned.
Innovation size is measured by the number of people involved: 4..4M
Innovation takes time.
Most Innovations are incremental not radical.
(dick)|-Viral innovation is effortless.
Stresses the need to observe what is going on and listen to criticism during development.
Claims there are seven skill areas or practices that can be learned that are needed: Sensing, Envisioning, Offering, Executing, Adopting, Sustaining + Leadership.
Non-verbal communication ( body language, tone of voice, ...) are the most important part of these skills.
Gives examples, tables, and references.
(dick)|-the 7 practices fit perfectly into the classic SDLC(Software Development Life Cycle).
Does not mention subversive innovations as in "The Inventors Dilemma".
Used in my CSCI372 course 2006

Denningetal89a

P J Denning & D E Comer & D Gries & M C Mulder & A Tucker & A J Turner & P R Young
Computing as a Discipline
Commun ACM V32n1(Jan 1989)pp9-23
=CURRICULUM education science ENGINEERING

Denningetal89b

Peter Denning (ed)
A Debate on Teaching Computing Science
Commun ACM V32n12 pp1397-1414(Dec 1989)
=DEBATE education
Dijkstra89 plus replies by 7 others also letters V33n3p264-271(Mar 1990) and V33n6pp628-630&633(Jun 1990)

DenningEtAl08

Peter J. Denning & Chris Gunderson & Rick Hayes-Roth
The Profesion of IT: Evolutionary System Development
Commun ACM V51n12(Dec 2008)pp- [ 1490360.1409371 ]
=REPORT EVOLUTION PROCESS AGILE USA GOVERNMENT LTEs RISKS FITNESS
Important to understand how fast a situation is changing and make sure that software is developed and delivered before the requirements change.
USA procurement rules allow LTE -- Limited Procurement Experiments -- that don't follow the BDUF waterfall.
Reports that the W2COG was able to deliver in 18 months an 80% complete version of software using LTE ($100K) and evolution while a parallel BDUF project delived only a concept document ($1.5M).

DenningFloresLuzmore10

Peter J Denning & Fernando Flores & Peter Luzmore
The Profession of IT -- Orchestrating Coordination in Pluralistic Networks
Commun ACM V53n3(Mar 2010)pp30-32 + Correspondence V53n6(Jun 2010)p6 + letter Ronnie Ward V53n2(Jun 2010)p6
=ANECDOTE WoW SIMULATE TRAINING TEAMS CULTURES PEOPLE
Claims that there is a need for effective multicultural distributed teams.
Claims that certain values/activities help and can be learned in multiplayer style game environment like World of Warcraft.
Values/activities
1. Proficient in a practice essential to the team.
2. Able to articulate vision of teams worth that others embrace.
3. Make commitments and fulfill them.
4. Spot and eliminate waste.
5. Share assessments+moods+emotions to build & maIntain trust.
6. Observe own history and link it to other's history.
7. Able to Blend: dynamically align to own intentions+actions of others.
Ronnie ward states the obvious that Email does not do enough to inspire teamwork.

DenningFreeman09

Peter J Denning & Peter A Freeman
The Profesion of IT: computing's paradigm
Commun ACM V52n12(Dec 2009)pp28-30 [ 1610252.1610256 ] +Letters V53n4(Apr 2010)pp6-7 [ Fulltext in citation ]
=ESSAY SCIENCE MATHEMATICS ENGINEERING COMPUTING
shared_paradigm::=initiation; conceptualization; realization; evaluation; action.
(dick)|-Ignores analysis, maintenance, iterations, updating, and social processes.

DenningHorning0202

Peter J Denning & James J Horning
Inside RISKS: Risks of Linear Thinking
Commun ACM V45n2(Mar 2002)p120
=ESSAY USER vs TECHNIQUE
Quotes Donald Stokes (Pasteur's quadrant: basic science and technological innovation, Brooking's institute, 1997). 2><2: inspired by use >< quest for fundamental understanding. Pasteur(Y,Y), Bohr (N,Y), Edison(Y,N), and unnamed(N,N).
Argues that software development is similar: focus on the user and focus on the technical aspects.

DenningRiehle09

Peter J Denning & Richard D Riehle
The Profession of IT: Is Software Engineering Engineering
Commun ACM V52n3(Mar 2009)pp24-26 [ 1467247.1467257 ]
=POLEMIC ENGINEERS
Things we do worse than engineers do:
1. The Principle of least surprise.
2. Design metrics -- including design to tolerances.
3. Separating design from implementation.
4. Reconciling conflicting forces and constraints.
5. Adapting to changing environments
Roles (one person plays many roles in a team) --
software { architect, engineer, programmer, manager } | O(systems engineer).
Need for Systems Thinking: From the hardware.... to the user environment.
Need for better tools, education, adoption of effective practices.

DenningYaholkovsky08

Peter J Denning & Peter Yaholkovsky
Getting to "We"
Commun ACM V51n4(Apr 2008)pp19-24
=ESSAY TOOLS PEOPLE TEAM WICKED PROBLEMS SYNERGY DESIGN Charettes
Collaboration is when people create synergistic solutions|strategies
Notes that tools support communication, coordination and cooperation rather than collaboration.

Dent96

Alan Dent(dent@highway1.com.au)
Solo Software Engineering
Software Development Magazine(Apr 1996)pp41+42+44-45
=EXPERIENCE SOLO
interuptions mean need for documentation
recommends diarys: project diary+random thoughts diady+design decisions diary+code change diary
User testing via self-hypnosis
Version control system [ adsoftware ]

Dern11

Daniel P. Dern
Lost programming skills: What today's coders don't know and why it matters
ITWorld(Aug 5 2011) [ lost-programming-skills ]
=POLL MANAGERS TECHNICAL LOST CODING

DershowitzJouannaud90

Nachum Dershowitz & Jean-Pierre Jouannaud
Rewrite Systems
Chapter 6 (pp243-320) of Leeuwen90.
=THEORY STRINGS GRAMMARS

DesaiEtal05

Nirmit Desai & Ashok U Mallya & Amit K Chopra & Munindar P Singh
Interaction protocols as design abstractions for business processes
IEEE Trans Software Engineering V31n12(Dec 2005)pp1015-1027
=THEORY MODEL BUSINESS PROCESS COMMITMENTS SCENARIOS OWL-P AGENTS ROLES π-CALCULUS
Proposes a logic of commitments between agents.
Uses sequence charts containing commitments to describe protocols.
Implies that activity diagrams are a bad way to describe business processes. Entangles the internal logic of different agents with each other. So unstable.
(dick)|-take home message: don't use control flows to model work flow.

DesaiChopraSingh09

Nirmilt Desai & Amit K Chopra & Munindar P Singh
Amoeba: A methodology for modeling and evolving cross-organizational business processes
ACM Transactions on Software Engineering and Methodology V19n2(Oct 2009)pp6.1-45
=ADVERT 2 CASE STUDIES Amoeba REQUIREMENTS METHOD LOGIC COMMITMENTS SCENARIOS SEQUENCE CHARTS AXIOMS EVOLUTION AGENTS SERVICES ORCHESTRATION CHOREOGRAPHY
Amoeba::Method= iterate( roles and interactions; contractual relationships -> Commitments; message meanings->create and manipulate commitments; Constraints; compose protocols -> process model).
Uses the idea of business protocols as modules. These have messages and resulting changes in the commitments between components. For example CC(VENDOR, BUYER, pay(price), ship(goods)) would result from a VENDOR sending a quotation(price, goods) message to a BUYER.
Theory [DesaiEtal05]

DeselEtAl04

Jorg Desel & Wolfgang Reisig & Grzegorz Rozenberg (Eds)
Lectures on Concurrency and Petri nets: Advances in Petri Nets (LectureNotes in CSci 3098)
SpringerVerlag NY NY 2004 ISBN 3540222618 CR 0511-1194
=UNREAD =PAPERS NONSEQUENTIAL MODELS Petri TIMED AUTOMATA algebra TCP

Desfray94

Phillippe Desfray(SOFTEAM)
Object Engineering: the Fourth Dimension
Addison-Wesley Redwood City CA 1994 $36.95 ISBN 0-201-42288-3 CR9511-0834
=TEXT OBJECT-ORIENTED [Desfray96]

Desfray94

Phillippe Desfray(SOFTEAM)
title
IEEE Computer Magazine V29N2(Feb 1996)pp62-66
=CASE-STUDY Hypergenericity client-server
see [Desfray94] for details
1. Adds a method with processing etc to an existing class.
2. "for each attribute..."

DesharnaisEtal98

Jules Desharnais & Marc frappier & Ridha Khedri & Ali Mili
Integration of Sequential Scenarios
IEEE Trans SE V24n9(Sep 1998)pp695-678 CR9906-0431
=THEORY RELATIONS Z SCENARIOS If pre(R)&pre(Q)=pre(R&Q) then demonic_meet(R,Q) ::= R&Q | Q~(pre(R)><post(Q)) | R~(pre(Q)><post(R)).
Scenario as a digraph labelled by two kinds of relations: those describing environment actions and those defining system actions.
Integration defined by union of environment actions and demonic meet of system actions.
"the simple fact of formalizing a specification or a scenario is a step towards a better understanding of the system under consideration"

Desilets08

Alain Desilets
Tell Me a Story
IEEE Software Magazine V25n2(MAr/Apr 2008)pp14-15
=EXPERIENCE USER REQUIREMENTS STORIES
Express user goals as simple, specific, and concrete stories about particular people getting valuable things.

Desouza03

Kevin C Desouza
Barriers to effective use of Knowledge Management systems in software engineering
Commun ACM V46n1(Jan 2003)pp99-100
=SURVEY REPOSITORY KNOWLEDGE EXPERTISE PEOPLE
Software engineers do not like being categorized as experts since it may type-cast them.
Knowledge about software is hard to capture and categorize on a computer data base.
Alternative (Human) systems may work better.
Measure communication not just use of repository use.

Desouza03b

Kevin C Desouza
Facilitating Tacit Knowledge exchange
Commun ACM V46n6(Jun 2003)pp85-88
=EXPERIENCE TEAM KNOWLEDGE
People needed encouraging to use a game room on company time.
Managers expected job-related knowledge to be shared in the room.
Lotus notes was used fro sharing knowledge later and both game room and project oriented knowledge started to be posted.

DesouzaAwazuTiwana06

Kevin C Desouza & Yukika Awazu & Amrit Tiwana
Four Dynamics for bringing use back into software reuse
Commun ACM V49n1(Jan 2006)pp97-100
=POLL 100 REUSE PEOPLE
Traditional reuse of published artifacts works better among novice and transient developers.
Uncovered evidence of three "knowledge spaces": private, public, and quasi-private.
A knowledge space is a collection of artifacts that may be more or less reusable. Examples repositories, code libraries, ..., and CASE tools.
Developers prefer to reuse stuff in their private space rather than the public space,
Expert: if it isn't in my private space, it probably doesn't exist.
Experts understand the interconnections better than novices and so tend to work with them rather than refactor into modules.
Novices and rookies are risk averse and don't have a wide knowledge space so they tend to reuse public artifacts.
Modularity encourages reuse.
Reuse tends to occur within groups rather than across team boundaries. The teams have tacit shared knowledge that makes reuse more valuable.
Transient teams tend to reuse public artifacts more than permanent ones. Repeated interaction between members of teams over a long time develops shared searching strategies.
Notes application of theories to open source projects.

DetlefsNelsonSax05

David Detlefs & Greg Nelson & James B Sax
Simplify: A theorem prover for program checking
J ACM V52n3(May 2005)pp365-473 CR 0605-0494
=UNREAD =DEMO TOOL PROGRAM PROVING V&V Simplify [click here if you can fill this hole]

Deursen01

Arie van Deursen
Customer Involvement in Extreme Programming -- XP2001 Workshop Report
ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp70-73 & [ http://www.cwi.nk/~arie/wci2001/ ]
=CONFERENCE XP USER CUSTOMER SQA
Customer representatives are a vital role (not a person) in XP, they re responsible for the right system being built and may need training and support.
Ask customers to add a "...so that..." clause to their User Stories that refers to the higher level goal.

DeursenKlintVisser00

Arie van Deursen & Paul Klint & Joost Visser
Domain-Specific Languages: An Annotated Bibliography
ACM SIGPLAN notices V35n6(Jun 2000)pp26-36
=BIBLIOGRAPHY DOMAIN LANGUAGES DSL
Project [ dsl ]

DeursenKuipers99

Arie van Deursen & Tobias Kuipers
Identifying Objects using Cluster and Concept Analysis
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp246-255
=EXPERIMENT Concept analysis beats cluster analysis [Snelting??]

Deville90

Yves Deville
Logic Programming: Systematic Program Development
Addison Wesley 1990 QA76.63.D48 CR9204-0201 & CR9102-0042
=TEXT LOGIC PROGRAMMING

Devlin01

Keith Devlin
The Real Reason why Software Engineers need Math
Commun ACM V44n10(Oct 2001)pp21-22
=ADVERT MATH
Learning of specific mathematical skills is not important -- they may never be used in practice.
Software practice demands abstract thinking.
Repetitive practice in mathematics makes thinking about abstractions a familiar and so easier process.
Evidence of rigorous algebra improving all scores!

DevlinEtal03

Keith Devlin (ed)
Why Universities require computer science students to take math (special section)
Commun ACM V46n9(Sep 2003)pp37-55
=ESSAYS MATH
Devlin: "Being smart is about doing, not knowing"... need to open up (train) abstr act ways of thinking. Bruce et al give examples of how math helps develop good software.
Henderson argues for math in software engineering because need precise abstract th inking.
Almstrum reports a survey of 500 computer professionals on why they were attracted to computing: 1:benefit, 2:Science and math, 3:experimenting, 4:being in the Vangu ard

DevlinRosenberg96

Keith Devlin & Duska Rosenberg(Brunel)
Language at Work: analyzing communication breakdown in the workplace to inform systems design
CSLI/Stanford Standford CA 1996 ISBN 1-57586-05101
=EXPERIENCE SYSTEM MATHEMATICS: Situation theory
LFZ::="Layered formalism and zooming".

Dewan05

Presan Dewan
Teaching inter-object design patterns to freshman
ACM SIGCSE Tech Symp Proc (Feb 2005)pp482-486
=DEMO small Object-Oriented PATTERNS iterator MVC observer facade composite factory Java

DewanRiedl93

Prasun Dewan & John Riedl
Toward Computer-Supported Concurrent Software Engineering
IEEE Computer Magazine V26n1(Jan 1993)pp17-28
=DEMO Flecse TECHNICAL TOOLS Concepts LIFECYCLE integration sharing NONSEQUENTIAL

DharJarke88

Dependency Directed Reasoning and learning in Systems Maintenance Support
IEEE Trans Soft Eng VSE-14n2(Feb 1988)pp211-227
=EXPERIENCE OBJECT-ORIENTED MAINTAINCE AI ONTOLOGY WHY
maintenance aided by storing justification for existence of parts of the design in terms of other parts(including external parts). object hierarchy AI analogy generalization

DiamondJ03

Jared Diamond
Guns, Germs, and Steel: The Fates of Human Societies
Norton NY NY(2003) ISBN 0-393-31755-2
=HISTORY PEOPLE CONNECTIONS COMPLEXITY INNOVATION GEOGRAPHY MIME TICS
The differences between societies -- and who conquers who -- appear to depend on geography not genetics.
Innovation happens most when there are large numbers of communicating and competing parts.
The technologies of farming flow east-west more than North-South.
Catalogs crops and domesticated animals by geography.
The 2003 edition relates the theories to software development at Microsoft vs IBM etc.

Diaz-Herrera93

Jorge L Diaz-Herrera(SEI-CMU)
The Importance of Static Structures in Software Construction
IEEE Software Magazine(May 1993)pp75-87
=IDEA GRAPHIC MODULAR HMD
Hierarchical Modular Diagrams(HMD) GRAPHIC

DiazSligo97

Michael Diaz & Joseph Sligo
How Software Process Improvement Helped Motorola
IEEE Software Magazine V14n5(Sep 1997)pp75-81
=EXPERIENCE IMPROVEMENT CMM
increased quality and lowered cycle time
process defined by task leaders and preactitioners
CMM lower levels pay off in higher levels

DisneyJohnson98

Anne M Disney & Phillip M Johnson
Investigating Data QUALITY Problems in the PSP
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp143-152 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=ANALYSIS CASE-STUDY 10 students...
[JohnsonDisney98]

DistefanoScarpaPuliafito11

Salvatore Distefano & Marco Scarpa & Antonio Puliafito
From UML to Petrie Nets: the PCM-based Methodology
IEEE Trans Software Engineering V37n1(Jan/Feb 2011)pp65-79
=DEMO METHOD ESTIMATE PERFORMANCE UML NON-MARKOVIAN PETRIE NETS PCM

Dichter93

Carl Dichter
Software Audits
UNIX Review V11n10(Oct 1993)pp43-49
=NEWS STANDARDS SQA QUALITY ISO SEI MATURITY
1. ISO9000
2. SEI CMM

Dick05

Jeremy Dick
Design traceability
IEEE Software Magazine V22n5(Nov/Dec 2005)pp14-16
=ESSAY traceability REQUIREMENTS DESIGN
Value in knowing why something is needed or how a need is met.
Defines implicit traceability and rich traceability.
Review. Sufficient design? Necessary design?

DickKrauseCozens90

A J J Dick & P J Krause & J Cozens
Computer Aided Transformations of Z into Prolog
pp71-85 in Nicholls90
=DEMO TOOL Z SPECIFICATION PROLOG PROTOTYPE
prototype
animation tool
finds unintended non-determinism in Z specification

Diehl07

Stephan Diehl
Software Visualization: Visualizing the structure, behavior, and evolution of sofware
Springer Verlag NY NY 2007 ISBN 3540465049 CR 0809-0828 & 0810-0932
=UNREAD =TEXT GRAPHIC CODE TECHNICAL [click here if you can fill this hole]

DiesteJuristo11

Oscar Dieste & Natalia Juristo
Systematic review and aggregation of empirical studies on elucidating techniques
IEEE Trans Software Engineering V37n2(Mar/Apr 2011)pp283-304
=SURVEY 30 EMPIRICAL REQUIREMENTS ELICITATION
Covers until 2005.
Guidelines
1. Unstructured interviews(and perhaps structured interviews) are more effective than introspection and sorting
2. And give more complete information
3. But are less efficient.
4. Introspection is worst!
5. Laddering is preferable to sorting and introspection.

DiesteJuristoShull08

Oscar Dieste & Natalie Juristo & Forrest Shull
Understanding the customer: What do we know about Requirements Elicitation
IEEE Software Magazine V25n2(MAr/Apr 2008)pp11-13
=SURVEY USER REQUIREMENTS ELICITATION
Many techniques and results, see [ s2voe.html ]
Summary:
Plan interviews in advance! Plan a Structure.
Include general question when new to a domain.
Introspective techniques are less useful.
Sorting techniques not as useful as interviews but sometimes quicker.

Dietz06

Jan L G Dietz
The deep Structure of Business Processes
Commun ACM V49n5(May 2006)pp59-64
=EXPERIENCE INTERACTION DESIGN LANGUAGE-ACTION PEOPLE REALITIES SYSTEMS
Used the language action perspective to analyze and design interactions.
Sample diagrams and jargon not well defined.
Distinguishes language acts from performing acts.
Mentions communication facts and performance facts... but not defined.
Goal to extract the essential map of a process as a basis for discovering opportunities and designs.

Digre98

Tom Digre<tomd@dataaccess.com>
Business Object Component Architecture
IEEE Software Magazine V18n5(Sep/Oct 1998)pp60-69
=THEORY DOMAIN ARCHITECTURE
Boca::="Business Object Component Architecture", pseudoC.

Dijkstra68a

Edsger W Dijkstra
Co-operating Sequential Processes
"Programming Languages" Academic Press 1968
=DEMO TECHNICAL non-sequential

Dijkstra68b

Edsger W Dijkstra
GOTO statement considered harmful
Letter Commun ACM 11 3 pp147-148 (Mar 1968)
=EXPERIENCE =HARMFUL sequential

Dijkstra68c

Edsger W Dijkstra
The structure of the "THE"-Multiprogramming System
Commun ACM 11 5 pp341-346 (May 1968)
=DEMO non-sequential formal analysis virtual machine

Dijkstra72

Edsger W Dijkstra
The Humble Programmer - ACM Turing Award Lecture 1972
see ACM86
=HISTORY science

Dijkstra74

Edsger W Dijkstra
Self-Stabilising systems in spite of distributed control
Comm ACM V17n11(Nov 1974)pp643-644
=THEORY TECHNICAL NONSEQUENTIAL
Ref by letter from Xavier A Bebest(Hochhheim Germany) Comm ACM V38n2(Feb 1995)pp115-117

Dijkstra76

Edsger W Dijkstra
A Discipline of Programming
Prentice Hall Inc Englewood Cliffs NJ
=TEXT guarded-commands sequential non-sequential formal logic structures

Dijkstra89

Edsger W Dijkstra
On the Cruelty of Really Teaching Computer Science
Talk at ACM Computer Science Conference Louisville Feb 1989(See [Denning89b] )
=TALK formal logic education

Dijkstra90

Edsger W Dijkstra(Editor)
Formal Development: programs and proofs
Addison-Wesley 1990(U Texas Year of Programming Series)
=MONOGRAPH FORMAL PROOFS

Dijkstra01

Edsgar W Dijkstra
The End of Computing science?
Commun ACM V44n3(Mar 2001)p92
=IDEA COMPLEXITY SCIENCE
|-Research is about what we don't know how to do.
(above)|-we need to study intricacy and simplicity.
"The average customer [...] expects his system to crash all the time."

DilligDilligAiken10

Isil Dillig & Thomas Dillig & Alex Aiken
Reasoning about the unknown in static analysis
Commun ACM V53n8(Aug 2010)pp116-123 [ 1787234.1787259 ]
=DEMO LOGIC MATHEMATICS MODEL CHECKING C Linux may/must SOUNDNESS

Dillon90

Laura K Dillon
Verifying General Safety Properties of Ada Tasking Programs
IEEE Trans SE-16n1pp51-63(Jan 1990)
=EXPERIENCE formal QUALITY non-sequential

Dillonetal86

Laura K Dillon & G S Avrunin & J C Wileden
Constrained Expressions: Toward Broad Applicability of Analysis Methods for Distributed Software Systems
COINS Tech Report 86-15 Univ of Amherst MA
=THEORY PREDICTING regular DAD formal

Dillonetal94

Laura K Dillon & G Kutty & L E Moser & P M Melliar-Smith && Y S Ramakrishna
A Graphical Interval Logic for Specifying Concurrent Systems
ACM Trans Softw Eng Methodol V3n2(Apr 1994)pp131-165 [ 33145.html ] [ citation.cfm?id=192218.192226&coll=portal&dl=ACM&idx=J790&part=transaction&WantType=transaction&title=ACM%20Transactions%20on%20Software%20Engineering%20and%20Methodology%20%28TOSEM%29&CFID=1643654&CFTOKEN=8691090 ]
=ADVERT NOTATION MODAL TEMPORAL LOGIC FORMAL GIL TOOL GILED
GIL::="Graphic Interval Logic".
Later see [RTGIL] -- real time GIL

DillRushby96

David L Dill(Stanford) & John Rushby(SRI International)
Acceptance of Formal methods: Lessona from Hardware Design
IEEE Computer Magazine V29N4(Apr 1996)pp23-24
=HISTORY HARDWARE vs SOFTWARE TOOLS
1. Cost needs to be justified
2. Hardware has a small number of design elements.
3. Formal treatment can pay off accross many applications
4. Mechanize formal calculations to reduce cost
5. A tool to find bugs (not all, but some) at a small cost per bug would make a clear payoff.
6. Prime need: effective, pragmatic tools.

DimaghaniDibble12

Ania Dimaghani & Jim Dibble (Oracle Corp)
Strategies for Early-Stage Collaborative Design
IEEE Software Magazine V29n1(Jan/Feb 2012)pp39-45
=ADVERT EXPERIENCE COLLABORATION DESIGN SUCCESS VISEO RECORD
Good things to do
1. Agree on and agenda and goals.
2. Determine the target Users.
3. Reframe requirements around users.
4. Sketch the problem Domain.
5. Drive to a solution.
6. Foster communication -- may be, perhaps, it might, what do you think
7. Evaluate as you go vs users and their needs.
8. Mine disagreements -- learn the opposing viewpoint as well as your own.
9. Don't sweat the details -- yet.
10. Capture Decisions.
Part of workshop [BakerHoekOssherPetre12]

DimitrovSchietendorfDumke02

Evgeni Dimitrov & Andreas Schietendorf & Reiner Dumke
UML-based Performance Engineering Possibilities and Techniques
IEEE Software Magazine V19n1(Jan/Feb 2002)pp74-83
=ESSAY UML QUALITY PERFORMANCE OCL CONSTRAINTS STEREOTYPES TAGGEDVALUES STATECHARTS

DingMateti90

Chen Ding & Prabhaker Mateti
A Framework for the Automated Drawing of Data Structure Diagrams
IEEE Trans SE-V16 n5 pp543-557(May 1990) CR9207-0512
=THEORY graphic ERD

DingelGarlanJhaNotkin98

J Dingel & D Garlan & S Jha & DNotkin
Reasoning about Implicit Invocation
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp209-221 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=DEMO =THEORY PROOF ARCHITECTURE MODULARITY

DingelLiang04

Juergen Dingel & Hongzhi Liang
Automating comprehensive safety analysis of concurrent programs using VeriSoft and TXL
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp13-22
=DEMO SQA AUTOMATED MODEL CHECKING TOOL ViP TXL plLTL Verisoft

Dinh-TrongBieman05

Trung T Dinh-Trong & James M Bieman
The FreeBSD Project: A Replication Case Study of Open Source Development
IEEE Trans Software Engineering V31n6(Jun 2005)pp481-494
=POLL OPEN SOURCE PROCESS FreeBSD GNATS
Replicates [MockusFieldingHerbsled02]
FreeBSD has been developing for 10 years.
A small group of up to 15 developers controlled the code base.
No more than 50 top developers contributed most of the functionality.
Some ceremony was needed to coordinate work but it is neither imposed nor veri fied.
A larger group repairs defects fed by an even larger group of developers who r eport problems,
A mechanism for separating stable from unstable code means that stable code will have a lower defect density than commercial feature tested code.
The developers were users.

dick

Richard J Botting
Comments on Item in this bibliography
Various item in this bibliography [ newbib.html ] source code [ newbib.mth ]
=METAINFORMATION
I use the MATHS assertion syntax to add my annotations to items:
```
 		(dick)|-comment
```
Direct quotations from original items are in double-quoted strings like this
```
 		page-number:"..."
```

diSessaAbelson86

Andrea diSessa & Harold Abelson
Boxer: A Reconstructable Computational Medium
Commun ACM V29n9(Sep 1986)pp859-868
=ADVERT graphic nested boxes/text + sprites as objects+LOGO-like

DittoMunakata95

William Ditto & Toshinori Munakata
Principles and Applications of Chaotic Systems
Commun ACM V38n11(Nov 1995)pp96-107
=THEORY CHAOS COMPLEXITY

DittrichVaucouleurGiff09

Yvonne Dittrich & Sebastien Vaucouleur & Stephen Giff
ERP customization as software engineering: knowledge sharing and cooperation
IEEE Software Magazine V26n6(Nov/Dec 2009)pp41-47
=EMPIRICAL VIDEOS DEVELOPERS INTERVIEWS DOCUMENTATION ADDON ENHANCE COMPLEX CODE
Understanding the ERP is the main challenge. Communication. Apprenticeship. Studying code.
Need more than user documentation to customize ERP.
Separate new code from old code.
A feature can effect tables , forms, code, etc. Crosscutting:.aspects?! Multilevel.
(dick)|-more like maintenance than green field development.

Dixmier84

Jacques Dixmier
General Topology
Springer Verlag Undergraduate Texts in Maths 1984
=MATHEMATICS

DjuricDevedzic10

Dragan Djuric & Vladan Devedzic
Magic Potion: incorporating new development paradigms through metaprogramming
IEEE Software Magazine V27n5(Sep/Oct 2010)pp38-44
=ADVERT JAVA LISP JVM Modeling Spaces XML RDF/OWL DSL DOMAIN MODEL LOGIC ONTOLOGY UML MDA
Clojure::= See http://clojure.org, Dialect of LISP that runs in the Java Virtual Machine.

DladodHarmanOteroHu03

J J Dladod & M Harman & M C Otero & L Hu
An Empirical investigation of the influence of a s type of side effects on program comprehension
IEEE Trans Software Engineering V29n7(Jul 2003)pp665-670
=EXPERIMENT CODE TECHNICAL SIDEEFEECTS UNDERSTANDING C
Compared answers of students to questions about C code with and without side effects (x++).
Side effects make code harder to read.

DobingParsons06

Brian Dobing & Jeffrey Parsons
How UML is Used
Commun ACM V49n5(May 2006)pp109-113 + letterV49n8(Aug 2006)pp11-13 + CR 0705-0477
=POLL GRAPHIC UML PRACTICE
Frequency of diagrams/narratives use varies a lot between teams/projects.
At least Half the projects are not use case driven --- more class diagram usage.
Clients are involved in most diagram types.
Use case narratives are used >70% by analysts and programmers.
Use case naratives do not capture all requirements.
UML is complex and could be understood better.

DobricaNiemela02

Liliana Dobrica & Eila Niemela
A Survey on Software Architecture Analysis Methods
IEEE Trans Software Engineering V28n7(Jul 2002)pp638-653
=SURVEY 8 METHODS Architecture Qualities SAAM SAAMCS ESAAMI SAAMER ATAM SBAR ALPSM SAEM scenarios metrics

Doernhoefer00

Mark Doernhoefer(ed)
Large vs Small. More on Programming in Small Teams
ACM SIGSOFT Software Engineering notes V25n4(Jul 2000)pp13-18
=DISCUSSION ONE-SIZE PROCESS
What to do when you are successful small project engineer faced by a manager who expects lsrge scale processes.
Methods and processes for small teams.

Doernhoefer01

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Free Software
ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp19-28
=ADVERT OPEN SOURCE WWW/NET GNU Linux FreeBSD Apache PHP MySQL OSDN Slashdot SourceForge OpenSource.org W3C

Doernhoefer03a

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: GUI Building
ACM SIGSOFT Software Engineering Notes V28n3(May 2003)pp13-21 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 773126.773134 ]
=SURVEY GRAPHIC USER GUI
Dozen good WWW sites

Doernhoefer03b

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Database Design
ACM SIGSOFT Software Engineering Notes V28n4(Jul 2003)pp11-20 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ ??? ]
=SURVEY DATA DESIGN KNOWLEDGE
17 good WWW sites

Doernhoefer04

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: XML
ACM SIGSOFT Software Engineering Notes V29n3(May 2004)pp15-24 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 986710.986718 ]
=SURVEY XML MARKUP LANGUAGES
Dozen or more good WWW sites related to the eXtensible Markup Language.

Doernhoefer05

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: service oriented architecture
ACM SIGSOFT Software Engineering Notes V30n6(Nov 2005)pp5-13 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 1102107.1102116 ]
=SURVEY WEB SERVICES SOA XML Sun BEA IBM ESB .NET CBD OASIS TOGAF ADM OWASP WS-I W3C Notes.Close
Another excellent collection of web sites on a new topic/hype-fest.

Doernhoefer06

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Software Process Improvement
ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)pp5-13 [ http://www.acm.org/sigsoft/SEN/ ] [ 1108768.1108783 ]
=SURVEY PROCESS IMPROVEMENT CMM-I SEI SPICE PSP SWPI SEPO USNAVY SWEBOK

Doernhoefer06a

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Requirements Management
ACM SIGSOFT Software Engineering Notes V31n2(Mar 2006)pp17-25 [ 1118537.1118553 ]
=SURVEY NET REQUIREMENTS
Excellent survey of resources on the web [ http://www.jiludwig.com/ ] [ requirements_management.htm ] [ index.php ] [ reqtracing.html ] [ AgileArticlesCatSearch?category=Requirements ] [ read.php ] (tools) [ p2_req.htm ] [ life_cycle_management.jsp ] [ Methodology ] [ reqanalysis.html ] [ http://www.telelogic.com/ ] [ reqfrm.htm ] plus lots more...

Doernhoefer06b

Mark Doernhoefer
Surfing the net for software engineering notes: The semantic Web
ACM SIGSOFT Software Engineering Notes V31n3(May 2006)pp8-16
=SURVEY SEMANTIC WEB ONTOLOGY URI OWL RDF DAML SPARQL Jena pOWL Protege SWOOP
Links [ sw ] [ swintro ] [ uri-schemes.html ] [ RDF ] [ owl-features ] [ http://www.daml.org ] [ rdf-sparql-query ] [ j-sparql ] [ index.html ] [ j-jena ] [ http://powl.sourceforge.net ] [ http://protege.stanford.edu ] [ SWOOP ] (editors) [ http://dublincore.org ] (DCMI) [ home ] [ URI ] (URIs must be static.... Tips)

Doernhoefer07

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Database Technology
ACM SIGSOFT Software Engineering notes V32n4(Jul 2007)pp10-19 [ surfing.html ]
=REVIEW WEB/NET DATA

Doernhoefer07a

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: User Interface Design
ACM SIGSOFT Software Engineering notes V32n5(Sep 2007)pp7-16 [ surfing.html ]
=REVIEW WEB/NET USER SIGCHI HCI MVC FOX Webby Suck

Doernhoefer08

Mark Doernhoefer
Surfing the Net for Software Engineering Notes: Requirements
=REVIEW WEB/NET REQUIREMENTS
ACM SIGSOFT Software Engineering Notes V33n3(May 2008)pp7-16 [ 1360602.1360606 ]
Includes
- The Atlantic Systems Guild [ index.html ]
- Joel Spolsky's Blog [ http://www.joelonsoftware.com/ ]
- Techrepublic [ 5100-3513-6146544.html ]
- Functional Specification Tutorial [ tutorial ]
- Cal Poly on Non-Functional Requirements [ nonfunctional.html ]
- Undreamt Requirements [ undreamtrequirements.html ]
- IDEF [ idef0.html ]

Doernhoefer08b

Mark Doernhoefer
Surfing the net for software engineering notes: Computer People
ACM SIGSOFT SEN V33n4(Jul 2008)p7-16 [ 1384139.1384149 ]
=SURVEY WEB BIOGRAPHIES PEOPLE
Allan Turing, John von Neumann, John W Mauchly, J Presper Eckert, C A R Hoare, Edsger Dijkstra, David Parnas, Grace Murray Hopper, Barry Boehm, Frederick Brooks, Brian Kernighan, Dennis Ritchie, Ken Thompson, Alan Perlis, Niclaus Wirth, Donald Knuth, Richard Hamming, Edgar Frank Codd, Gordon Bell, Gary Kildall, ...

Doernhoefer09

Mark Doernhoefer
Surfing the net for software engineering notes: Tool Time
ACM SIGSOFT SEN V34n1(Jan 2009)pp7-16 [ 1457516.1457519 ]
=SURVEY TOOLS Eclipse NetBeans MySQL PostGresSQL Apache Tomcat JBoss Caucho Resin ArgoUML C# .Net Subversion CVS FindBugs PMD Pentaho W3C VALIDATION LINK CHECKER

Doernhoefer09a

Mark Doernhoefer
Surfing the net for software Engineering notes -- Software and System Reliability
ACM SIGSOFT Software Engineering Notes V34n3(May 209)pp6-15 [ 1527202.1527204 ] (PDF)
=SURVEY =LINKS RELIABILITY
Handbook [ http://www.cse.cuhk.edu.hk/~lyu/book/reliability/ ]
The Reliability Information Analysis Center [ http://www.theriac.org/ ]
The Data and Analysis Center for Software [ https://www.thedacs.com/databases/url/key/2/ ]
Relex Reliability Dictionary [ ReliabilityDictionary.asp ]
Weibull.com [ http://www.weibull.com/ ]
NASA Software Assurance Technology Center [ http://satc.gsfc.nasa.gov ]
IEEE Reliability Society [ index.jsp?&pName=relsoc_home ]
City University Centre for Software Reliability [ http://www.csr.city.ac.uk ]
Reliability Engineering Tools [ tools.htm ]
...
IEEE Transactions on Software Engineering(1993) [ toc.cfm?id=173802&type=issue&coll=GUIDE&dl=GUIDE&CFID=29760540&CFTOKEN=27889279 ]
Dependable Embedded Systems [ http://www.ece.cmu.edu/~koopman/des_s99/sw_reliability/ ]
...
Reliability Calculators [ AvailabilityTranslator.htm ] [ reliability_calculator ]

Doernhoefer09b

Mark Doernhoefer
Surfing the net for software Engineering notes -- Empirical Software Engineering
ACM SIGSOFT Software Engineering Notes V34n3(Jul 2009)pp4-16 [ 1543405.1543409 ] (PDF)
=SURVEY =LINKS EMPIRICAL EXPERIMENTAL EXPERIENCE POLLS SURVEYS
LInks to Journals, Groups, Courses, Conferences all concerned with gathering data and fitting theories to software development.

Doernhoefer09c

Mark Doernhoefer
Surfing the net for software engineering notes: computer science
ACM SIGSOFT SEN V34n5(Sep 2009)pp8-17 [ 1598732.1598752 ]
=SURVEY SWEBOK SigACT ALGORITHMS CALGO NUMERICAL NIST GAMS DATA STRUCTURES THEORY HARDWARE TM OS IMBOK FUZZY LOGIC PROGRAMMING LANGUAGES

Dolado00

Jose Javier Dolado
A Validation of the Component-Based Method for Software Size Estimation
IEEE Trans Software Engineering V26n9(Sep 2000)pp1006-1021
=EXPERIMENT 46 SIMULATED BUSINESS Informix-4GL ESTIMATE LOC CBM FPs
component := menu | input | report_and_enquiry.
stats: regression, neural nets, genetic programming.
NOC::= number of components.
example: LOC = 116 + 75 *inputs + 73 *menus + 68 * reports.
NOC increases with LOC. NOC/LOC decreases with LOC from 0.03 to 0.005. Type of components matter.
[VernerTate92]

Dolev00

Shlomi Dolev
Self-Stabilization
MIT press 2000 $40 ISBN 0-262-04178-2 CR0006-0360
=MONOGRAPH THEORY NONSEQUENTIAL RELIABILITY

DongYangZhang07

Jing Dong & Sheng Yang & Kang Zhang
Visualizing Design Patterns in Their Applications and Compositions
IEEE Trans Software Engineering V33n7(Jul 2007)pp433-453
=DEMO TOOL VisDP UML PROFILE PATTERNS GRAPHICS WEB SERVICE XMI J2EE java.awt
Need to show how one object/class plays many roles depending on the patterns.
Defines an UML profile to show how classes/attributes/operations take part in design patterns.
Demonstartes the clutter that appears with different ways of displaying this information.
Demonstrates a tool that will make design paterns visible as requested by the user.

DonnellanEtal05

Brian Donnellan & Brian Fitzgerald & Brian Lake & John Sturdy
Implementing an Open Source Knowledge Base
IEEE Software Magazine V22n5(Nov/Dec 2005)pp92-95
=COMPARISON TOOLS KB OPEN SOURCE COSPA MetaData DSpace LAMP Data Centric KMS Lotus Notes
KB::="Knowledge Base", part of an expert system, the body of knowledge available for the inference engine to use.
Dublin_Core::standard= See http://dublincore.org.
(Open archives initiative Protocol for Metadata Harvesting): framework [ http://www.openarchives.org ]
Only works well when it evolves with the needs of the users.

Donnelly00

Daniel Donnelly
In your Face Too!
Rockport Pubs Inc., Gloucester MA, 2000 ISBN 156496-677-1
=EXAMPLES interactive interfaces CD-ROM DVD web/net kiosks user HCI

Donzelli 06

Paulo Donzelli
A Decision Support System for Software Project Management
IEEE Software Magazine V23n4(Jul/Aug 2006)pp67-75
=DEMO SIMULATION QUEUING NONSEQUENTIAL PROCESS ESTIMATION STAFFING + COCOMO REQUIREMENTS QNAP2 NASA SEL
Two level model: artifacts circulate around workstations, work station parameters determined by COCOMO.
Predicts staffing requirements -- completely ignoring Brooke's Law.
Changing requirements add more work later in the project and extend time to complete by about 30%
Comparable with staffing profile from SEL project with high instability.
For a survey of other process models see [AcunaJuristo05].

Doolan92

E P Doolan
Experience with Fagan's Inspection Method
Software - Practice & Experience V22n2(Feb 1992)pp173-182
=EXPERIENCE QUALITY V&V INSPECTIONS REQUIREMENTS
Each personel-hour of inspection saved cost of 30 personel-hours of fixing

DoppkeEtal98

John C Doppke & Dennis Heimbigner & Alexander L Wolf
Software Process Modeling and execution within Virtual Environments
ACM ToSEM V7n1(Jan 1998)pp1-40
=DEMO PROCESS can be described game(MUD/MOO) using lambdaMOO

Dorfman99

Merlin Dorfman
Commercial vs Aerospace Worlds: comparing software engineering cultures
IEEE Software Magazine V16n6(Nov/Dec 1999)pp97-100
=ESSAY EXPERIENCE
one size does not fit all
comercial: - smaller projects +Time to market -new methods - new tools - funding + hope - time accounting - costing - estimating

Dori08

Dov Dori
Words from Pictures for Dual-Channel Processing
=DEMO TOOL GRAPHIC NATURAL LANGUAGE SYSTEM DESIGN MODELLING OPM OPD OPL OPCAT FSM
Commun ACM V51n5(May 2008)#7pp47-52
Claims that automatically linking diagrams to text makes process more intuitive. [MillerJ02]

Doublait97

Stephane Doublait
Standard Reuse Practices: Many Myths vs a Reality
ACM StandView V5n5(Sep 1997)pp84-91
=EXPERIENCES at Sodalia(ISO9001& CMM=2)

Douglass99

Bruce Powel Douglass
Components: Logical, Physical Models
Software Development Magazine V7n12(Dec 1999)pp52-54
=ADVERT OBJECT-ORIENTED METHOD UML ROPES COMPONENTS
Components are runtime plugin Binaries not objects .Note UML components include data files, web pages, source code, etc etc.

Douglass99b

Bruce Powel Douglass
Doing Hard Time: developing real-time systems with UML, Objects frameworks, and patterns
Addison Wesley, Longman 1999 ISBN 0-201-49837-5 QA46.6 D655 1999 includes CDROM
=TEXTBOOK ADVERT UML Rhapsody TMING NONSEQUENTIAL ROPES Object-Oriented
special stereotypes pp48-52
5 safety patterns pp116-124
Mechanistic design
12 state-behavioral-patterns, table pp 590-591.
Many patterns recur in different parts.
RMA:: theory = Rate Monotonic Algorithm, requires sum [i : 1..n](worst [i ] / period [i ] ) < n*( 2**(1/ n )-1).
has some UML errors:
1. multiplicity "1" when should be "0,1" or "2",
2. Collaboration diagrams show classes rather than objects,
3. composition put in collaboration diagrams and mis-defined,
4. some activity diagrams are flowvharts, etc..

Douglass04

Bruce Powell Douglass
Real Time UML (3rd edn): Advances in the UML for Real-Time Systems
Pearson Education Boston MA 2004 ISBN 0-321-16076-2 (Addison-Wesley Object Technology Series)
=TEXT QUALITIES PURPOSE PERFORMANCE TIMING RELIABILITY UML ROPES PATTERNS
No mention of OCL and some diagrams have non-standard UML notations.
Introduction to and examples of PTS profile and RT-UML [OMG020302].
ROPES::="Rapid Object-Oriented Process for Embedded Systems".
Quotes (misquotes?) the Rate Monotone Analysis bound.
Older and subtly different [Douglass99b].

DowdyFoster82

Comparative Models of the File Assignment Problem
ACM Comp Surveys V14 n2 (Jun 1982) pp287-313 see also V15 n1 pp87-89
data optimization Technical

DownsA00

Andrew Downs
From Engineer to Technical Lead
Software Development Magazine V8n4(Apr 2000)pp72-74
=EXPERIENCE PEOPLE code reviews

DownsClareCoe8792

Ed Downs & Peter Clare & Ian Coe
Structured Systems Analysis and Design Method
Prentice Hall International (UK) Herts UK 1988(1st edn) & 1992(2nd Edn) CR9305-0292
=TEXT SSADM management COMPACT
COMPACT for Office systems
2nd Edn has Combined viewpoint diagrams(CCTA 1990) : two parts control+Process

Dowson86

M Dowson(ed)
Iteration in the Software Process
Proc of the 3rd Int Software Process Workshop (Nov 1986)
=PROCEEDINGS non-sequential lifecycle PROCESS ITERATION AGILE

Drake96

Thomas Drake
Measuring Software Quality: A Case Study
IEEE Computer Magazine V29n11(Nov 1996)pp78-87
NSA SEATC(Software Engineering Applied Technology Center)
=EXPERIENCE TECHNICAL QUALITY
25MLoC benefits Kiviat Diagrams profile many Qualities of code

Dribin96

Lawrence S Driben
Defining Design Terminology(letter)
IEEE Software Magazine V13N3(May 1996)p8
external design vs internal design: which is the true architecture?

DrobkaNoftzRaghu04

Jerry Drobka & David Noftz & Rekha Raghu
Piloting XP on four mission-critical projects
IEEE Software Magazine V21n6(Nov /Dec 2004)pp70-75
=EXPERIENCE XP AGILE 4 Motorola Projects
Gained a minimum of 260% productivity vs waterfall (incremental was 162%) with 70-90% test coverage, and with a 51..75% improvement in quality (defects at system test/KAELOC)
High morale and confidence, training easier.
Challenges: fitting with non-XP projects and managers. Need thorough training and coaching.
Did an initial "blitz" software architecture rather like Unified Process.

Dromey88

RG Dromey
Systematic Program Development
IEEE Trans Soft Eng SE-V14n1(Jan 1988)pp12-29
formal

Dromey90

Geof Dromey
Program derivation: the development of programs from specifications
Addison-Wesley Reading MA 1990 TEXT FORMAL METHOD

DromeyChorvat90

RG Dromey & TA Chorvat
Structure clashes -- an alternative to program inversion
Comput J V33n2(Apr 1990)pp126-132
JSP

Drucker85

Peter Drucker
Innovation and Entrepreneurship
Harper Business 1993, Harper Perennial 1985
=EXPERIENCES INNOVATIONS ENGINEERING BUSINESS ANALYSIS
Innovation includes: searching for opportunity & analysis & listening & Focus & leadership. Opportunities include: unexpected events, incongruities, process need, change of industry structure, demographics, change of mood or perception, and new knowledge.

DuJingLiu12

J Du J & S Jing & J Liu
Creating shared design thinking process for collaborative design
Journal of Network and Computer Applications V35n1(2012)pp111-120
=DEMO ENGINEERING RATIONALE TOOL TEAMTHINK S-DTPM cf COMPENDIUM IBIS TOULMIN
Ideas about designs are issues, options, solutions, rules, criteria, and annotations.
There are operations for sharing perspectives: Argument, evolution, association, fusion.
Very weak evidence: one demo/case-study with 2 people.

DubocRosenblumLetier10

Leticia Duboc & David S Rosenblum & Emmanuel Letier
Death, Taxes, & Scalability
IEEE Software Magazine V27n4(Jul/Aug 2010)pp20-21
=ADVERT REQUIREMENTS KAOS QUALITY REALITY SCALABILITY LAS HMRC
Scalability is not just about performance but impacts other qualities and even functionality.
Scalability is not defined well in most projects. Examples: LAS (London Ambulance System) & HMRC (UK Revenue and Customs).
Scalability requirements can be stated in such away that they can not be met by a finite system. This has to be spotted and fixed. All scalability requirements need to be critiqued.
Scalability is always relative to the reality and the system surrounding the software. These must be defined as assumptions. They must then be challenged.
Analyzing how a system will fail to scale leads to better systems -- for example adding emergency procedures and back up processing power.

DucasseLanza05

Stephane Ducasse & Michele Lanza
The Class Blueprint: visually supporting the understanding of classes
IEEE Trans Software Engineering V31n1(Jan 2005)pp79-90
=EXPERIMENTAL GRAPHIC Object-Oriented code metrics structure smalltalk
Classifies attributes and methods into layers: initialization, interface, internal implementation, accessors, attributes.
Attributes and methods shown as boxes. Metrics mapped to height and width. Type to color.
Caller-callee link goes from bottom of caller box to top of called.
Tested on real code. and by a dozen students (all found it helpful).

DueckCormack90

G D P Dueck & G V Cormack
Modular Attribute Grammars
Computer Jnl V33n2(Feb 1992)pp164-173

DuenasEtAl07

Juan C Duenas & Hugo A Prada G & Felix Cuado & Manuel Santillan & Jose L Ruiz
Apache and Eclipse: Comparing open source project incubators
IEEE Software Magazine V24n6(Nov/Dec 2007)pp90-98
=EMPIRICAL COMPARISON 2 F/OSS PROCESSES PROJECT INITIATION LIFE CYCLE ANALYSIS
Incubation is the process of developing and defining new project/subprojects to be further developed and integrated into a the current (evolving) system.
Apache and Eclipse have well defined processes and share many features (Table 1 page 97)

DugganByrneLyons04

Jim Duggan & Jason Byrne & Gerard J Lyons
A task allocation optimizer for Software Construction
IEEE Software Magazine V21n3(May/Jun 2004)pp76-82
=DEMO PEOPLE PROCESS PLAN ALGORITHM MOEA
Allocating people to tasks has many objectives: time & defects.
Multiobjective optimizer computes Pareto-optimal set using elitist genetic algorithm.
Human picks one.
dominates::@(solution, solution), x dominates y iff for all f:objectives(f(x)better_than f(y).
Pareto_optimal_set::@(solution)= {x. for no y(y dominates x)}.

DumasParsons95

Joseph Dumas & Paige Parsons
Discovering the Way Programmers Think about New Programming Environments
Commun ACM V38n6(Jun 1995)pp45-56
Dylan USER PROTOTYPE
OODL::=OBJECT-ORIENTED with automated memory management & dynamic linking & incremental development & self-identifying objects
Dumay04
1. Mark Dumay
2. Business Processes: the theoretical impact of process thinking on information development
3. arXive.org e-print archive Sun, 19 Sep 2004 09:56:24 GMT [ 0409037 ]
4. =ESSAY POSTMODERN SYSTEMS PEOPLE SOCIOLOGY BPR RISKS PROCESS vs FUNCTIONS TECHNOCRACY =SURVEY SOCIOLOGY
5. Argues that Business Process Reengineering tends to fail because they expect & require people to fit the process not vice versa.
6. Business Process ReEngineering deliberately uses information technology to impose a process view on an organization... ignoring the existing culture, structure, management, etc.
Duncan79
1. Fraser Duncan
2. Microprocessor Programming & Software Development
3. Prentice Hall International
4. =harmful Technical =MANUAL highlevel assembler
DunlopBasili82
1. DD Dunlop & VP Basili
2. Comparative Analysis of Functional Correctness
3. Comp Surveys v14n2(Jun 1982)pp229-244
4. theory SQA
Dunne95
1. Alex Dunne
2. The Office Environment's Trickle-Down Effect(Editorial)
3. Software Development Magazine(Oct 1995)pp7-8
4. POLL more readers(26%) need better communication at all levels than anything else. Then more time and a clear view of requirements and a more defined process.
Dunn03
1. William R Dunn
2. What
3. IEEE Computer Magazine V36n11(Nov 2003)pp40-46
4. =ESSAY RISKS COST MITIGATION HAZARD MISHAP
5. What is an acceptable risk? How to achieve it?
DunsmoreRoperWood03a
1. Alastair Dunsmore & Marc Roper & Murray Wood
2. The Development and Evaluation of Three diverse techniques for object-oriented code inspection
3. IEEE Trans Software Engineering V29n8(Aug 2003)pp673-686
4. =EXPERIMENT V&V SQA CODE TECHNICAL INSPECTIONs Object-Oriented Java delocalization use-case checklists abstraction
5. 69 SoftEng. students U Strathclyde. 200 LoC 2 classes extending known software 90 minutes 14 defects.
6. 3 reading techniques: (abstraction, checklist, use case)-based.
7. abstraction: write specification for methods...
8. Possibly significant differences between detection rates: means: checklist>abstraction>use case. all ranges from 2-11 out of 14.
9. None good at spotting omissions.
10. None found a subtle misuse of a class library.
11. (dick)|-some evidence that the chance of detecting a defect is independent of the reading method.
12. More readable with more examples [DunsmoreRoperWood03b]
DunsmoreRoperWood03b
1. Alastair Dunsmore & Marc Roper & Murray Wood
2. Practical code inspection techniques for Object-Oriented systems: and experimental comparison
3. IEEE Software Magazine V20n4(Jul/Aug 2003)pp21-29
4. =ADVERT V&V SQA CODE TECHNICAL INSPECTIONs Object-Oriented Java delocalization use-case checklists abstraction
5. Static and dynamic views.
6. Results and stats in [DunsmoreRoperWood03a]
Durfee01
1. Edmund H Durfee
2. Scaling Up Agent Coordination Strategies
3. IEEE Computer Magazine V34n7(Jul 2001)pp39-46
4. =SURVEY AGENTS PROBLEMS STRATEGIES
DutertreStavidou97
1. Bruno Dutertre & Victoria Stavidou
2. Formal Requirements Analysis of an Avionics Control System
3. IEEE Trans Softw Eng VSE23n5(May 1997)pp267-278
4. =DEMO V&V REQUIREMENTS LOGIC TOOLS TIMING RISKS REALITY PVS [PVS]
5. model of time and clocks
6. exposed some unstated assumptions about REALITY and one defect
Dutton93
1. James E. Dutton<dutton@parcplace.com>
2. Commonsense Approach to Process Modeling
3. IEEE Software Magazine(July 1993)pp56-64
4. =IDEA PROCESS MODELING DFDs
5. ProSLCES VPML::= DFDs+StructuredText
DuvalHodgins06
1. Erik Duval & Wayne Hodgins
2. Standardized Uniqueness: Oxymoron or Vision of the Future
3. IEEE Computer Magazine V39n3(Mar 2006)pp96-98
4. =STANDARD EDUCATIONAL OBJECTS METADATA LOM IEEE1484 LTSC XML
5. The IEEE1484 standard specifies the information to be recorded about "Learning Objects": artifacts that help you learn.
6. The standard is MODULAR separating logical structure from physical bindings.
7. The standard defines many data elements in a hierarchical data model but every part is optional.
8. How to make the metadata invisible?
Dvorak94
1. Joseph Dvorak<dvorak@ast.dsd.northrop.com>
2. Conceptual Entropy and its effect on Class Hierarchies
3. IEEE Computer Magazine V27n6(Jun 1994)pp59-63
Dwelly00
1. Andrew Dwelly
2. XML, Reflective pattern matching, and Java
3. Dr. Dobbs Journal #313(Jun 2000)pp46+50-51+54
4. =DEMO TECHNICAL Marius DDD HARMFUL
Dwyer81
1. Barry Dwyer
2. A User-friendly Algorithm
3. Commun ACM V24n9(Sep 1981)pp556-561 [ 358746.358751 ]
4. =EXPERIENCE USER BEHAVIORISM PEOPLE HCI BEHAVIOR MODIFICATION
5. Correspondence [McMahon82] Critiquing this approach -- skinnerian -- with Dwyer's rebuttal.
DwyerM92
1. Michael Dwyer(IBM Corp)
2. The Cleanroom approach to quality software development
3. John Wiley& Son NYNY 1992
4. ISBN 0-471-54823-5
5. CR9211-0861 Review [Humphrey93]
Dyadkin94
1. Lev J Dyadkin<ldyad@lahey.com>
2. Multibox Parsers
3. ACM SIGSOFT Software Engineering Notes V19n3(Jul 1994)pp23-26
4. DDD FORTRAN
Dyadkin95
1. Lev J Dyadkin<ldyad@lahey.com>
2. Multibox Parsers: No More Handwritten Lexical Analyzers
3. IEEE Software Magazine V12n5(Sep 1995)pp61-67 & see Dyadkin94
  1. FORTRAN 90 needs 8 boxes to lex parse it.
  2. Most code generated automatically from generic boxes.
  3. 96% of the lexer automatically generated!
  4. Easily ported to other platforms.
  5. Use fast LL(1) processes.
  6. Does not run slower than another FORTRAN 90 compiler(Salford).
Dyba00
1. Tore Dyb'a
2. Improvisation in small Software Organizations
3. IEEE Software Magazine V17n5(Sep/Oct 2000)pp82-87
4. =SURVEY 120 managers in 55 Norwegian companies. PROCESS One-SIZE CMM
5. Larger organizations reduce exploration in turbulent environments but small ones increase it.
6. In a turbulent environment success requires mix exploiting known and predictable skills with exploring unpredictable new ideas.
7. Theory: Variance helps survival. Failure is inherent in seeking to succeed in dynamic situations.
8. Compare with [Highsmith99b] and [Highsmith99]
Dyba03
1. Tore Dyba
2. Factors of Software process improvement success in small and large organizations in a Scandinavian context
3. FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp148-157
4. =EMPIRICAL IMPROVEMENT ORGANIZATION SIZE
5. Small and large can do equally well but must involve people more and explore new knowledge. See [Dyba00].
Dyba05
1. Tore Dyba
2. An Empirical investigation of the Key Factors for success in Software Process Improvement
3. IEEE Trans Software Engineering V31n5(May 2005)pp341-424
4. =POLL 120 ORGANIZATIONS IMPROVEMENT SPI STATISTICS
5. p421: "organizational issues are at least as important in SPI as technology, if not more so."
6. Results suggest the following,
  1. Align improvement goals with business. Share knowledge between business and software experts.
  2. Management provides resources not leadership in SPI.
  3. Involve the developers/workers in creating the proposed changes and metrics.
  4. Focus on the measurement of success.
  5. Look for existing knowledge to exploit and/or explore for new knowledge
  6. Encourage workers/developers to explore new ideas because this involves them in the process.
DybaDingyrMoe04
1. Tore Dyba & Torgeir Dingyr & Nils Brede Moe
2. Process improvement in practice: a handbook for IT companies
3. Kluwer Academic, Norwell MA 2004 ISBN 1402078692 CR 0511-1197
4. =HANDBOOK SOFTWARE PROCESS IMPROVEMENT SPI
DybaDingsoyr09
1. Tore Dyba & Torgeir Dingspoyr
2. What do we know about agile software development
3. IEEE Software Magazine V26n5(Sep/Oct 2009)pp6-9 + Correspondence V26n6(Nov/Dec 2009)p8
4. =SURVEY EMPIRICAL RESEARCH AGILE XP
5. Agile processes can improve customer satisfaction, productivity and job satisfaction.
6. They can be difficult to introduce into a large organization.
7. Being the onsite customer is stressful and hard to sustain.
8. A Team needs a strong focus on both the interpersonal and the team goals.
9. Skill and experience helps.
10. May not be the best approach for large projects.
11. Need more research.
12. (William Adams)|-fads, bullets, need to match situation to method/process.
DybaEtAl07
1. Tore Dyba & Erik Arisholm & Dag I K Sjoberg & Jo E Hannay & Forrest Shull
2. Are two heads better than one? On the effectiveness of pair programming
3. IEEE Software Magazine V24n6(Nov/Dec 2007)pp12-15 CR 0902-0169
4. =META-ANALYSIS EXPERIMENTS PAIR-Programming QUALITY COST
5. Quality tends to be a little better and the time to complete the project is better. The effort (people * time) is slightly worse.
DybaKitchenhamJorgensen05
1. Tom Dyba & Barbara A Kitchenham & Magne Jorgensen
2. EVIDENCE-BASED Software Engineering for Practitioners
3. IEEE Software Magazine V22n1(Jan /Feb 2005)pp58-65
4. =IDEA PRACTICES LITERATURE SURVEY EBSE META-ANALYSIS
5. How to select technologies, methods, processes to put into a project?
6. EBSE::acronym="EVIDENCE-BASED Software Engineering", and following
  1. Convert problem/information into answerable question.
  2. Search the literature for best evidence.
  3. Critically appraise evidence: valid? Impact?, Applicable?
  4. Apply the evidence that fits current project: experience, values, circumstances.
  5. Evaluate performance and seek to improve.
7. Resources page 61
  - IEEE Xplore [ http://ieeexplore.ieee.org/ ]
  - IEEE Digital Library [ http://www.computer.org/publications/dlib/ ]
  - ACM Digital library [ http://www.acm.org/dl/ ]
  - ISI Web of Science [ http://www.isinet.com/products/citation/wos/ ]
  - EBSCOhost Electronic Journals Service [ http://ejournals.ebsco.com/ ]
  - CiteSeer [ http://citeseer.nj.nec.com/ ]
  - Google Scholar [ http://scholar.google.com/ ]
8. Checklist page 62.
9. Example page 64: Chaos report does not fit with other surveys and does not include data to evaluate the accuracy of its evidence.
DzidekEtAl08
1. Wojciech James Dzidek & Erik Arisholm & Lionel C Briand
2. Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance
3. =EXPERIMENT UML MAINTENTANCE EFFECTIVENESS VALUE Oslo Java Eclipse BESTWeb
4. IEEE Trans Software Engineering V34n2(May/Jun 2008)pp407-432
5. Use 20 real developers to maintain real software!
6. BESTweb:=Internal bibliographic data base on software cost and effort estimation. Realistic (1..2 weeks) tasks. Half had UML diagrams.
7. Replicates on [Arisholm06BriandHoveLabiche06]
8. UML improves quality significantly with only a 14% worse time.
Eaddy01
1. Marc Eaddy
2. C# Versus Java
3. Dr. Dobbs #321(Feb 2001)pp74+76+78+80+82
4. =HISTORY JAVA C++
EaddyEtAl08
1. Marc Eaddy & Thomas Zimmermann & Kaitlin D Sherwood & Vibhav Garg & Gail C Murphy & Nachiappan Nagappan & Alfred V Aho
2. Do Crosscutting Concerns Cause Defects
3. IEEE Trans Software Engineering V34n4(Jul/Aug 2008)pp497-515
4. =EMPIRICAL ASPECTS REQUIREMENTS CONCERNS CROSS-cutting CODE QUALITY BUGS
5. Requirements mapped into concerns.
6. Reverse engineered concern->code map and the bug->code mapping and deduce concern->bug relationship in corpus of Java code.
7. Defects tend to be associated more with wide-spread concerns than with total amount of code implementing a concerns.
EasterbrookCallahan97
1. Steve Easterbrook & John Callahan
2. Formal Methods for V&V of Partial Specifications: An Experience Report [RE'97] pp160-168
3. Value of formalizing english specs is in finding ambiguities incompleteness and contradictions
4. AND/OR and SCR TABULAR
EasterbrookEtal98
1. Steve Easterbrook & Robyn Lutz & Richard Covington & Yoko Ampo & David Hamilton
2. Experiences Using Lightweight Formal Methods for Requirements Modeling
3. IEEE Trans Soft Eng V24n1(Jan 1998)pp4-14
4. =EXPERIENCES FORMAL SQA complement trad METHODS: SCR And/Or TABULAR [PVS] OMT
5. results of using a formal model is useful after the model is out-of-date
6. great deal of domain knowledge needed to distinguish strange but possible cases from impossible cases
Easton78
1. Frank M Easton
2. Esperanto Success
3. =ADVERT Esperanto ITL UNIVERSAL LANGUAGES
4. Computer Weekly (UK) (Mar 23 1978)p19
5. Rebuts Botting78a "Loglan unheard of".
Ebert06
1. Chistof Ebert
2. Understanding the Product Life Cycle: Four Key Requirements engineering Techniques
3. IEEE Software Magazine V23n3(May/Jun 2006)pp19-25
4. =STATISTICS ? PROJECTS OVERRUN vs REQUIREMENTS ALCATEL
5. 4 technique associated with finishing embedded or application software products with less overrun.
6. portfolio::= "depicts all products in the organization together with their market and investment etc.".
7. Techniques
  1. Install an empowered core team for each release at its start.
  2. Focus life cycle on the early gate-reviews using portfolio as guide.
  3. Evaluate requirements from various perspectives.
  4. Assure dependable portfolio visibility and release implementation.
8. project size/length not associated with higher %overrun.
EbnerKaindl02
1. Gerald Ebner & Hermann Kaindl
2. Tracing All Around in Reengineering
3. IEEE Software Magazine V19n3(May/Jun 2002)pp70-77
4. =CASESTUDY REENGINEERING RETH HYPERTEXT DOCUMENTATION
5. RETH::="Requirements Engineering Through Hypertext".
6. Erroneous UML metamodel (roles at wrong end of association )! Requirements justify Design Decision, new Requirements replace old Requirements.
Ebrahimi97
1. Nader B Ebrahimi
2. On the statistical analysis of the number of errors remaining in a software design document after inspection
3. IEEE rans Se V23n8(Aug 1997)pp529-532
4. SQA =THEORY not capture/recapture allows non-independent reviews but requires independent issues
Ebrahimi99
1. Nadar B Ebrahimi
2. How to Improve the Calibrartion of Cost Models
3. IEEE Trans SE V25n1(Jan/Feb 1999)pp136-140 CR9906-0435
4. =THEORY STATISTICS ESTIMATION COSTS proxy variable for size beats COCOMO
EbringerThorneZheng00
1. Tim Ebringer & Peter Thorne & Yuliang Zheng
2. Parasitic Authentication to Protecting Your E-Wallet
3. IEEE Computer Magazine V33n10(Oct 2000)pp54-60
4. =IDEA USER SECURITY
Eckstein99
1. Robert Eckstsein
2. XML pocket reference
3. O'Reilly 1999 ISBN 1-56592-709-5 $8.95
4. =MANUAL XML
Eco85
1. Umberto Eco
2. Travels in hyperreality
3. Harcourt brace etc 1985 0-15-1911079-0 PQ4865.c6t7
4. =ESSAY modern etc culture
5. p178: In scientific publishing photocopying meant price up, number down, and less to authors
Eco94
1. Umberto Eco
2. The Search for the Perfect Language
3. Blackwell Oxford UK & Cambridge USA 1995 ISBN 0-631-17465-6 P106.E2813
4. =HISTORY semiotic artificial languages in europe
5. "[...] it is only necessary to make one simple assumption: the perfect language exists, and it is identical to one's own tongue. Once this assumption is made, the choice of the metalanguage follows[...]"
Edel88
1. Mark Edell
2. The Tinkertoy Graphical Programing Environment
3. IEEE Trans Soft Eng VSE-14n8(Aug 1988)pp1110-1115
4. Graphical Functional LISP: problems with PROG sequential iterative structures
EditorU08
1. Unknown Editor
2. Special Issue on Formal Proof
3. Notices of the American Mathematical Society V55n11 (Dec 2008) [ http://www.ams.org/notices/200811/ ]
4. =EXAMPLES FORMAL PROOFS MATHEMATICS
5. Includes [Hales08] [Gonthier08] [Wiedijk08]
Editors00
1. Contributing Editors
2. Tales of Terror
3. Software Development Magazine V8n9(Oct 2000)pp41-80 + Letters V8n12(Dec 2000)p11
4. =ANECDOTES FAILURE METRICS ETHICS MARKETING PLANNING TESTING DIRECTORIES ALGORITHM META-BUREAUCRATIC DENIALS CLUELESS DATA SIZING LEGACY TESTING
Editors01
1. Many contributors
2. Pick a Language any Language
3. Software Development Magazine V9n3(Mar 2001)pp44-47
4. =OPINION LANGUAGES VB SmallTalk MVC C++ STL Prolog Java Perl
5. "What ever I get paid for is best".
6. "the one I designed and built myself".
Edmond92
1. David Edmond
2. Information Modeling: Specification and Implementation
3. Prentice Hall Englewood Cliffs NJ 1992
4. $51 ISBN 0-13-457748-5 CR9501-0017
Edwards94
1. Stephen H Edwards
2. Annotated Bibliography of RESOLVE Research
3. ACM SIGSOFT Software Engineering Notes V19n4(Oct 1994)pp65-67 [Sitaraman94]
Edwards97
1. Stephen H Edwards
2. Representation Inheritance: A Safe Form of "White Box" Code Inheritance
3. IEEE Trans Softw Eng V23n2(Feb 1997)pp83-92
4. =IDEAS object-oriented
Edwards09
1. Kathryn Edwards
2. The A-Z of Programming Languages: MATLAB
3. Computerworld Australia (Dec 09 2009) [ -z_programming_languages_matlab ]
4. =INTERVIEW =HISTORY 25 years MATLAB LANGUAGE MATHEMATICS ENGINEERING Cleve Moler
5. Surprise success of a tool develop for students... favourite feature
  1. It's the mathematics. The thing that I enjoy as a mathematician is finding out how mathematics underlies so many different disciplines. We didn't intend to do automobiles, anti-lock brakes or human genome or pricing of derivatives in the finance market. We never set out to do any of that originaly, but mathematics is common to all of these. I really enjoy talking about how these different fields are unified by the underlying mathematics.
Edwardsetal94
1. Stephen H Edwards & Wayne D Heym & Timothy J Long & Murali Sitaraman & Bruce W Weide
2. Specifying Components in RESOLVE
3. ACM SIGSOFT Software Engineering Notes V19n4(Oct 1994)pp23-28
4. See Sitaraman94
EdwardsEtal04
1. Stephen H Edwards & Murali Sitaraman & Bruce W Weide & Joseph Hollingsworth
2. Contract-check Wrappers for C++ Classes
3. IEEE Trans Software Engineering V30n11(Nov 2004)pp794-810
4. =DEMO WRAPPERS CONTRACT ASSERTIONS TECHNICAL C++ V&V SQA FACTORY
5. Instead of inline code checking assertions, can provide optional compiled wrappers that contain assertions.
EdwardsJacksonTorlak04
1. Jonathan Edwards & Daniel Jackson & Emina Torlak
2. A Type System for Object Models
3. Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp189-199
4. =IDEA LOGIC RELATIONAL TYPES Alloy 2.0
5. Defines an improved type system for Alloy with subtypes, relations, etc.
6. Compares with UML OCL.
7. Precisely defines two types for formulas: bounding type and relevance type.
8. An empty relevance type indicates an error.
EfromHarelCohen05
1. Sol Efrom & David Harel & Irun R Cohen
2. Reactive Animation: Realistic modeling of complex dynamic systems
3. IEEE Computer Magazine V38n1(Jan 2005)pp38-47
4. =ADVERT Flash TCP/IP Rhapsody state chart MODEL CELL Thymus bioinformatics MVC
Egyed02
1. Alexander Egyed
2. Automated abstraction of Class Diagrams
3. ACM TOSEM Trans Software Eng & Methodology V11n4(Oct 2002)pp449-491
4. =ADVERT THEORY TOOL ABSTRACTION UML/analyzer
EgyedGrunbacher04
1. Alexander Egyed & Paul Grunbacher
2. Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability can help
3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp50-58
4. =THEORY AUTOMATED REQUIREMENTS TRADE-OFFS PURPOSES QUALITIES DEMO VOD Video-on-demand
5. Express all requirements as tests and run them tracing which ones execute the overlapping pieces of code.
6. Classify requirements in terms of type.
7. Types indicate likely cooperation and conflict in a semantic web.
8. Hence able to express trade-off situations.
EgyhazyEyestoneMartino01
1. Csaba Egyhazy & Scott Eyestone & Janet Martino
2. Defining Team Processes using OO Metaphors
3. IEEE Software Magazine V18n3(May/June 2001)pp74-83
4. =EXPERIENCE Object-Oriented PROCESS
5. Object based ideas of classes, responsibillites, and collaborations can be used to define a software development process.
EgyhazyMukherji04
1. Csaba Egyhazy & Raj Mukherji
2. Interoperability architecture using RM-ODP
3. Commun ACM V47n2(Feb 2004)pp93-97 =EXPERIENCE GCPR GOVERNMENT MILITARY MEDICAL RECORDS ARCHITECTURE INTEROPERABILITY
4. RM-ODP CORBA
5. RM-ODP::="Reference Model for Open Distributed Processing", [Putnam01].|-Need to address policies and procedures (especially security and authentication ) not just interfaces, data, design, and programming.
6. Viewpoints::={enterprise, information, computational, engineering, technology}.
7. Alphabet soup! Class diagrams, IDL, sequence diagrams, tables of metadata, usecases, deployment d iagrams.
8. |-No commercial tools were up to the job.
9. |-UML could not be used for RM-ODP.
EhrigMahr8589
1. H. Ehrig and B. Mahr
2. Fundamentals of Algebraic Specification Vols I and II
3. Springer Verlag Berlin 1985 & 1989 ADTs
EickEtal01
1. Stephen G Eick & Todd L Graves & Alan F Karr & J S Marron & Audris Mockus
2. Does code Decay? Assessing the Evidence from change Management data
3. IEEE Trans Software Engineering V27n1(Jan 2001)pp1-12
4. =EXPERIENCE EVOLUTION MAINTENANCE COST MODULE
5. 16 years 100MLOC C/C++ 50 subsystems 5K modules. describes maintenance process and data collection.
6. Each module is a directory full of files.
7. Analysis of 100 modules 2,500 file 130k deltas 500 login ids to find that costs increased, faults increased, and if changes start to span more modules. Large span meant larger effort.
8. changes := adaptive | corrective | perfective.
9. causes of decay: wrong architecture, changes in reality, imprecise requirements, time, tools, organizations, programmers, bad process.
10. symptoms: bloat, frequent changes, frequent faults, dispersed changes, kludges, numerous interfaces.
11. risk factors: size, age, inherent complexity, churn, porting and reuse, requirements load, inexperience.
EickEtal02
1. Stephen G Eick & Todd L Graves & Alan F Karr & Audria Mockus & Paul Schuster
2. Visualizing Software Change
3. IEEE Trans Software Engineering V28n4(Apr 2002)pp396-412
4. =EXPERIENCE TOOL GRAPHIC CODE TECHNICAL DELTAS EVOLUTION IMR
5. IMR::= "Initial Modification Request".
6. How to understand changes in 20M lines of code in 5000 modules across 15 years.
7. views: matrix, cityscape, bar and pie charts. filtering. perspectives.
8. For N[i,j]:= number of IMRs effecting both i and j, N[i] number effecting i, strength_of_linkage[i.j] := N[i,j]/sqrt(N[i]*N[j])).
EickelmenAnant03
1. Nancy Eickelmen & Animesh Anant
2. Statistical Process Control: What you don't measure can hurt you
3. IEEE Software Magazine V20n2(Feb/Mar 2003)pp49-51
4. =HISTORY STATISTICS PROCESS QUALITIES QC Kiviat σ INSPECTION SQA
Eilenberg74
1. S Eilenberg
2. Automata Languages & Machines
3. Volume A Academic Press 1974
4. =theory languages
Eischen02
1. Kyle Eischen
2. Software Development: and Outsiders View
3. IEEE Computer Magazine V35n5(May 2002)pp36-44
4. =HISTORY SOCIOLOGY ECONOMICS CRAFT RATIONALIZATION
5. The fact that software is still produced without using the rationalized/managed/defined processes indicates a fundamental schism between rationalized manufacturing and craftsman-like design in software.
6. requirements and design are difficult and involve knowledge and translation of non-software domains -- cultures.
7. Software benefits from peer review.
8. Much s already working.
9. Competition is essential to get both innovation and accurate evaluation of process and product.
10. Need build and borrow tools that evaluate and translate domain knowledges.
11. Design is inherently buggy and difficult -- in all areas.
12. Education should include: human skills, cross disciplinary work and research.
13. Sidebar: 3 analogies: university, Hollywood, and construction.
EisenbarthKosckeSimon03
1. Thomas Eisenbarth & Rainer Koscke & Daniel Simon
2. Locating Features in Source Code
3. IEEE Trans Software Engineering V29n3(Mar 2003)pp210-224
4. =DEMO TEST SCENARIO TRACE CODE MODULES CONCEPT MAINTENANCE
5. Proposes a technique to isolate parts of code involved in particular features.
6. Select scenarios with and without features of interest; list features as set in each scenario; run them and trace; record set of modules executed for each.
7. Describes formal concept analysis [GanterWille99]
8. Defines a context @(Features><Modules)
9. Do concept analysis on this context to generate lattice of @Features >< @Modules.
10. Categorize the lattice nodes relevant to features: for feature f, nodes >== specific | relevant | conditionally_specific | shared | irrelevant.
11. Combine with static dependency analysis to develop a map of where each feature is implemented (or at least involved).
12. Shows how to iteratively grow lattice by adding features.
Eisenstadt97
1. Marc Eisenstadt
2. My Hairiest Bug War Stories
3. Comm ACM V40n4(Apr 1997)pp30-37 CR9711-0918
4. =POLL RISKS QUALITIES DEBUGGING
5. Very interesting.
6. Internet POLL for bugs classified for difficulties(long cause-effect chain and hampered tools being commonest) + how found(gathered data and ispeculation leading) + root cause(memory, vendor, design,logic, initialization ...) +interaction(use data gathering when cause-effect chain is likely to be long or the tools are hampered)
Eisner05
1. Howard Eisner
2. Managing Complex Systems: Thinking Ouside the Box
3. Wiley Hoboken NJ 2005 TA168.E387 ISBN-13 978-0-471-69006-1 ISBN-10 0-471-69006-6
4. =HANDBOOK MANAGEMENT THINKING
5. Many interesting ideas and pointers to details but a little thin in places.
El-FakihYevtushenkoBochmann04
1. Khaled El-Fakih & Nina Yevtushenko & Grego v Bochmann
2. FSM-Based Incremental Conformance Testing Methods
3. IEEE Trans Software Engineering V30n7(Jul 2004)pp425-436
4. =THEORY =EXPERIMENT FSM/STD SPECIFICATION EVOLUTION TEST
ElEmamLaitenberger01
1. Khaled El Emam & Oliver Laitenberger
2. Evaluating capture-recapture models with two inspectors
3. IEEE Trans Software Engineering V27n9(Sep 2001)pp851-864
4. =SIMULATION MODEL QUALITIES V&V INSPECTION ERRORS STATISTICS CAPTURE-RECAPTURE
Elfatatry07
1. Achmed Elfatatry
2. Dealing with change: components versus services
3. Commun ACM V50n8(Aug 2007)pp35-39
4. =ESSAY components services EVOLUTION RISKS EFFICIENCY
5. Components selected before run but services are selected during the run. So services are easier to change but less efficient and less trustworthy.
6. (dick)|-Sounds like a hacker can offer an evil service and get it accepted
SimEtAl12
1. Susan Elliott Sim & Medha Umarji & Sukanya Ratanotayanon & Cristina V Lopes
2. How well do search engines support code retrieval on the web?
3. ACM TOSEM Trans Software Eng & Methodology V21n1(Jan 2012)#4.1-25 [ 2063239.2063243 ]
4. =POLL =EXPERIMENT COMPARE CODE SEARCH ENGINES TECHNICAL REUSE REFERENCE
5. Nice piece of work observing and doing statistics on programmers searching for code samples.
6. People search for code for two reasons: to reuse and as a reference.
7. Tested 4 code search engines:=following,
8. It was easier to find references than reusable examples.
9. Google beats the others.
10. Google does a much better job at finding small pieces and Koders and Krugle better at big chunks (systems).
11. Order of trying different engines does not matter.
12. There is room for improvement in all of them.
EllisJ94
1. John R Ellis
2. Objectifying Real-Time Systems
3. SIGS Publications NY 1994 $44
4. review IEEE Software magazine V13n3(Mar 1996)p123: down to earth and based on WardMellor RTSA with DFDs ERDs etc
Ellison95
1. Karen S Ellison
2. Developing real-time embedded software in a market driven company
3. John Wiley & Sons NY NY 1994 $39.95 ISBN 0-471-59459-8 CR9511-0829
EllisStroustrup90
1. Margaret A Ellis & Bjarne Stroustrup
2. The Annotated C++ Reference Manual (ARM)
3. Addison-Wesley Redwood City CA 1990 (Copyright AT&T Bell Labs 1990) LC 90-33932 ISBN 0-201-51459-1
ElmasQadeerTasiran10
1. Tayfun Elmas & Shaz Qadeer & Serdar Tasiran
2. Goldilocks: a race-aware Java Runtime
3. Commun ACM V53n11(Nov 2010)pp85-92 [ 1839676.189698 ]
4. =DEMO JAVA NONSEQUENTIAL SHARED MEMORY HAZARDS DETECTION EXCEPTIONS
5. See also [Adve10] and [FlanaganFreund10]
ElshoffMarcotty82
1. ?? Elshoff & ?? Marcotty
2. Improving Computer Program Readability to Aid Modification
3. Commun ACM V25 n8( pp512-521)
4. =THEORY STRUCTURED CODE QUALITY
Emam05
1. Khaled El Emam
2. The ROI from Software Quality
3. Auerbach Pub, Boston MA, 2005 ISBN 0849332982 CR 0612-1195
4. =UNREAD HOWTO MEASURE VALUE QUALITY IMPROVEMENT
EmamBenlarbiGoelRai01
1. Khaled El Emam & Saida Benlarbi & Mishith Goel & Shesh N Rai
2. The Confounding Effect of class size on the Validity of Object-Oriented Metrics
3. IEEE Trans Software Engineering V27n7(Jul 2001)pp630-650
4. =CASESTUDY METRICS OO SIZE
5. Size accounts for fault proneness as well as more common metrics: chidamberKemerer o LorenzKidd
EmamBirk00
1. Khaled El Emam & Andreas Birk
2. Validating the ISO/IEC 15504 measures of software requirements analysis process capabillity
3. IEEE Trans Software Engineering V26n6(Jun 2000)pp541-566
4. =STATISTICS IMPROVEMENT MEASURES PRODUCTIVITY
5. In large organisations controling requirements llinked to higher productivity
EmamEtal02
1. Khaled El Emam & Saida Benlarbi & Nishith Goel & walcelio Melo & Hakim Lounis & Shesh N Rai
2. Th Optimal Class size for Object-Oriented Software
3. IEEE Trans Software Engineering V28n5(May 2002)pp494-509
4. =CASESTUDY STATISTICS C++ Java CODE Object-Oriented METRIC
5. size measured by statements, LoC, #methods and #attributes.logistic Logistic function: Pr[class size S=s has a fault] =1/(1+exp(-(β0+β1*size)))
6. vs Threshold model:....
7. Both size and faults were skewed toward 0.
8. The theory that small pieces are more faulty was previously shown to be an artifact of the data!
9. There is no empirical evidence in this experiment that large classes have more faults either.
EmamGoldenson00
1. Khaled El Emam & Dennis R Goldenson
2. An Empirical Review of Software Process Assessments
3. Advances in Computers V53(2000)pp320-423
4. =SURVEY CMM SPA effectiveness ISO/IEC15504 SPI IMPROVEMENT
5. SPA Sponsors expect SPA to be useful.
6. Organizations have too high expectations for SPA.
7. Evidence that SPA results are consistent.
8. Ample evidence that higher levels are linked to improved performance.
EmamKoru08
1. Khaled El Emam & A Gunes Koru
2. A Replicated survey of IT Software Project Failures
3. IEEE Software Magazine V25n5(Sep/Oct 2008)pp84-90
4. =POLL 2006 2007 PROJECTS SUCESS FAILURE SIZE LENGTH STATISTICS
5. Published work overestimates failure rate.
6. In this poll about 16% were cancelled in 2005 and 12% were cancelled in 2007.
7. Reasons given: uninvolved senior management, requirements/scope changes, lack of management skills, over budget, lack of technical skills, system not needed afterall, etc..
Embleyetal92
1. David W Embley & Barry D Kurtz & Scott N Woodfield
2. Object-Oriented Systems Analysis: A Model-driven Approach
3. Prentice Hall Englewood Cliffs NJ 1992
4. OSA
5. Reviewed Am Math Monthly V99n8(Oct 1992)p807 CR 9202-0686(K.6.1)
6. CR9404-0198
Embleyetal95
1. David W Embley<embley@cs.byu.edu> & Robert B Jackson & Scott N Woodfield(BYU)
2. Object-Oriented Systems Analysis: Is it or isn't it
3. IEEE Software Magazine V12n4(July 1995)pp19-33 + correspondence with Shlaer & Mellor IEEE Software Magazine V12n5(Sep 1995)pp8+10
  1. OOS-L::=Object-oriented Specification Language::= formal, also natural versions
  2. IPOST::=Interaction Prototyping Object-oriented Specification Tool
    Comparison of features of several methods: subjective.
    p25: "All systems are embedded, either in the way we normally think about embedded computer systems or are in an organisation such as a business[so] the larger environment should always be considered, especially for analysis, which emphasizes the comprehension and documentation of entire systems."
    p32: Goal: "A software-engineering environment based on a single formal model.
EmbleyNagy81
1. ?? Embley & ?? Nagy
2. Behavioral aspects of text editors
3. ACM Computer Surveys 13 1 (Mar 1981) pp33-70
4. =SURVEY USER EDITOR
Emery69
1. F E Emery (ed)
2. Systems thinking: selected reading
3. Penguin books, Harmondsworth Middx UK, Baltimore Md USA1969
4. =READINGS SYSTEM CYBERNETICS
5. Of historical value... but [Weinber75] largely supersedes it.
EmeryTrist60
1. F E Emery & E L Trist
2. Socio-technical Systems
3. Management Science, Models and techniques, V2(?? 1960)pp83-97
4. =ESSAY SYSTEMS PEOPLE TEAM
5. Similar observations in British coal mining and Indian textile mills: a composite group/team oriented organization with complex roles and interaction outperforms a rigid hierarchical organization. Also less rigid form ad less symptoms of stress (illness, accidents, etc).
6. Managers should manage interactions between teams rather than micro-manage the internal structures of teams.
7. (dick)|-probably applies to agile vs rigid processes.
EmmerichAoyamaSventek08
1. Wolfgang Emmerich & Mikio Aoyama & Joe Sventek
2. The Impact of Research on the Development of Middleware Technology
3. ACM TOSEM Trans Software Eng & Methodology V17n4(Apr 2008)#19pp1-48 [ 13487689.13487692 ]
4. =SURVEY HISTORY MIDDLEWARE J2EE CORBA IBM BEW Oracle Nicrosoft Tibco Websohere RMI .NET etc RESEARCH PhDs
5. 20 year lag between academic research and large mainstream market.
6. PhD. Theses are important!
EmmerichEtal99
1. Wolfgang Emmerich & Anthony Finkelstein & Carlo Montangero & Stefano Antonelli & Stephen Armitage & Richard Stevens
2. Managing Standards Compliance
3. IEEE Trans Software Engineering V25n6(Nov/Dec 1999)pp836-837
4. =THEORY MODEL LOGIC FLEA TOOL DOORS DXL STANDARDS in PROCESS
5. uses STATECHART UML~OCL+1st_order_logic PETRI Net LISP (AP5)
6. FLEA::="Formal Language for Expressing Assumptions".
Endres93
1. Albert Endres
2. Lessons Learned in an Industristrial Software Lab
3. IEEE Software Magazine V10n5(Sep 1993)pp58-61
Engelsetal92
1. G Engels & C Lewerentz & M Nagl & W Schafer & A Schurr
2. Building Integrated S Development Environments Part 1: Tool Specification
3. ACM Trans Softw Eng Methodol V1n2(Apr 1992)pp135-167
Engel99
1. Gerald L Engel
2. Program Critrria for Software engineering Accreditation Programs
3. IEEE Software Magazine V16n6(Nov/Dec 1999)pp31-34
4. =ADVERT SWEEP ENGINEERING EDUCATION
EnrightWilkens93
1. Aaron G Enright & Linda M Wilkens
2. Engineering the Transition to Better Software
3. ACM SIGSOFT Software Engineering Notes V18n3(Jul 1993)ppA47-49
4. Notes the fallacies and problems of using a faulty process model (rush to code) to the improvement of the software process. pA47 col2 "Why not just engineer the transition"
EomHollingsworth01
1. Hyeonsang Eom & Jeffrey K Hollingsworth
2. A Tool to Help Tune where Computation is Performed
3. IEEE Trans Software Engineering V27n7(Jul 2001)pp618-629
4. =CASESTUDY Net DISTRIBUTE PERFORMANCE LBF
5. LBF::="Load Balancing Factor".
Epstein94
1. Richard L Epstein
2. The Semantic Foundations of Logic: Predicate Logic
3. Oxford U Press Inc NY NY ISBN 0-19-508760-7 CR9601-0018
4. philosophical translation of Natural language into various predicate calculi
Epstein01a
1. Richard L Epstein
2. Predicate logic: The semantic foundation of Logic
3. Wadsworth Belmont CA 2001 ISBN 0-534-55846-1 BC181.E67 2001 $40.95 pp412 CR0011-0555 F.4.1
4. =TEXT =REFERENCE LOGIC PC MODAL
5. x is a dog notation!
6. CSUSB CS556/656 [Epstein94]
Epstein01b
1. Richard L Epstein
2. Propositional logic: The semantic foundation of Logic
3. Wadsworth Belmont CA 2001 ISBN 0-534-55846-1 BC181.E67 2001b
4. =TEXT =REFERENCE LOGIC PC MODAL
5. CSUSB CS556/656
Epstein06
1. Richard L Epstein
2. Classical mathematical logic: The semantic foundation of Logic
3. Princeton UP Princeton NJ 2006 ISBN 0691123004 CR 0803-0245
4. =UNREAD =TEXT =REFERENCE LOGIC
5. Compare [Epstein01b] [Epstein01a] [Epstein94]
EpsteinJAxtell96
1. Joshua M Epstein & Robert Axtell
2. Growing Artificial Societies: Social Science from the Botom up
3. The Brooking Inst Washington DC 1996
4. CR9710-0776
Erdogmus05
1. Hakan Erdogmus
2. The Economic Impact of learning and flexibility on Process decisions
3. IEEE Software Magazine V22n5(Nov/Dec 2005)pp76-83
4. =ESSAY MATH ONESIZE Economics PROCESS ITERATIVE vs SEQUENTIAL COST-BENEFIT
5. Calculated values of projects.
6. Iteration & learning can make a project profitable in an uncertain situation.
Erdogmus07
1. Hakan Erdogmus
2. Novelty in sameness
3. IEEE Software Magazine V24n3(May/Jun 2007)pp5-7
4. =EDITORIAL IID ITERATIVE INCREMENTAL EVOLUTION Royce70
5. Notes the difficulty of understanding and using new ideas.
6. Good definition & discussion of iteration and increments.
7. Compare with [Meyer97] (Quality First), [JacobsonBoochRumbaugh98] (RUP), [Larman04] (Evo, ...).
Erdogmus08
1. Hakan Erdogmus
2. Must software research stand divided
3. IEEE Software Magazine V25n5(Sep/Oct 2008)pp4-6
4. =ESSAY EMPIRICIST VS CONSTRUCTIONIST RESEARCH
5. Gives a good description of the two types of research into software development.
Erdogmas09
Erdogmus09
1. Hakan Erdogmas
2. A process that is not
3. IEEE Software Magazine V26n6(Nov/Dec 2009)pp4-7
4. =EDITORIAL Tiki COLLABORATION TOOL OPEN SOURCE ANTIPROCESS F/OSS BAZAAR
5. An example of an unusually open project. No onion....
6. Tiki::= See http://tikiwiki.org/
Erdogmus10
1. Hakan Erdogmas
2. Can all sequential processed grow up to be iterative and incremental
3. IEEE Software Magazine V27n4(Jul/Aug 2010)pp2-5
4. =ESSAY NONSEQUENTIAL PROCESSES Kanban scrumban LEAN stage-gate v-model
5. Refers to [Beck99] Break process down into parts and apply sequence to parts many times.
6. Refers to [Ladas08] (Scrumban).
7. Divisibility of work. Unravelling principles: ( pipelining, workflow-schedule independence).
8. Split up, make parallel, add buffers, and add integration steps.
9. Compare with "Pipe and Filter" architecture and Jackson's methods in the 1970s and 1980s.
ErdogmusJohnston91
1. M Hakam Erdogmus & Robert Johnston
2. On the Specification and Synthesis of Communicating Processes
3. IEEE Trans SE-16 n12(Dec 1990)pp1412-1432
ErdogmasMorisioTorchiano05
1. Spelling mistake for [ErdogmusMorisioTorchiano05]
ErdogmusMorisioTorchiano05
1. Hakan Erdogmus & Maurizio Morisio & Marco Torchiano
2. On the Effectiveness of the Test-First Approach to Programming
3. IEEE Trans Software Engineering V31n3(Mar 2005)pp226-237
4. =EXPERIMENT TESTING AGILE TFD TDD
5. Summarizes previous studies: test-first makes no difference or improves quality and may or may not improve productivity.
6. This paper has a controlled experiment comparing test-first with test-last development of a series of user stories.
7. Test-first programmers broke stories into a series of tests and added one test and then added code to make program pass test. Test last coded complete story and then carried out all tests.
8. Experiment: 40PCs Java JUnit ECLIPSE CVS, 35 3rd year volunteer students, 11 dropped out.
9. Quality measure via hidden acceptance tests.
10. Productivity in terms of number of stories per unit time.
11. Theories: Test-first may tend to increase the number of tests, the quality, and productivity. However more tests anyway may increase quality and productivity.
12. My translation of their statistics results:
  1. quality >= 0.55 + tests/10. NOTE: not a linear equation but an inequality.
  2. More tests increase the minimum number of tests passed in the acceptance testing.
  3. Other factors can improve quality as well as tests.
  4. productivity= 0.255 + 0.659 tests.
  5. Test-first programmers did more tests on average.
  6. Test-first programmers where more productive and produced the same quality code.
  7. 30% dropped out -- "morbidity"
Erickson94
1. Martin Erickson
2. An Introduction to Combinatorial Existence Theorems
3. Mathematics Magazine V67n2(Apri 1994)pp118-123 Math Assoc of America
Erickson96
1. Thomas Erickson
2. Design as Storytelling
3. ACM interactions V3n4(Jul/Aug 1996) pp30-35
4. CR9703-0195: USER tell stories of unpredicatable computer systems
EricksonA09
1. Aaron Erickson
2. The Nomadic Developer: Surviving and Thriving in the World of Technology Consulting
3. Addison-Wesley Professional; 1 edition (May 15, 2009) ISBN 0321606396 [ 0321606396 ]
4. =UNREAD CONSULTING IT ICT TECHNOLOGY PEOPLE ECONOMICS
5. Help [click here EricksonA09 if you can fill this hole]
EricksonMcDonald08
1. Thomas Erickson & David W McDonald (Eds)
2. HCI Remixed -- Essays on Works that have influenced the HCI Community
3. The MIT Press Caambridge MA 2008 QA76.9.H85H4125 ISBN 978-0-262-05088-3
4. =HISTORY =ESSAYS USERS Human Computer Interfaces HCI
5. (dick)|-Any book with an essay on Ted Nelson's Computer Lib/Dream Machines must be good!
EricksonSiau07
1. John Erickson & Keng Siau
2. Theoretical and practical complexity of modeling methods
3. Commun ACM V50n8(Aug 2007)pp47-51
4. =POLL UML DIAGRAM USAGE COMPLEXITY
5. People use only some parts of the UML: class statechart, sequence, use case,...
6. Subset scores only 40% of complete complexity.
EriksonBorstlerBorg06
1. Magnus Erikson & Jurgen Borstler & Kjell Borg
2. Software Product Line modelling made practical
3. Commun ACM V49n12(Dec 2006)pp49-53
4. =CASESTUDY SWEDISH PRODUCT LINE MODEL FEATURE USECASE PLUSS
5. PLUSS::="Product Line Use case modelling for Systems and Software engineering".
6. Hierarchy of features. Features map to use cases and steps in use case.
7. Need moreformalism to model a complete product line.
8. Threat of losing of ownership of individual existing products can lead to resistance.
9. Notes
ErnstBadrosNotkin02
1. Michael D Ernst & Greg J Badros & David Notkin
2. an empirical Analysis of C Preprocessor Use
3. IEEE Trans Software Engineering V28n12(Dec 2003)pp1148-1170
4. =EMPIRICAL TECHNICAL STATISTICS C PREPROCESSOR MACROS
ErnstHookwayOgden94
1. George W Ernst & Raymond J Hookway & William F Ogden
2. Modular Verification of Data Abstractions with Shared Realizations
3. IEEE Trans SE-30n4(Apr 1994)pp288-307
EscuderoNegroSatriani01
1. Marina Blanco Escudero & Pedro Gutierrez Negro & Giuseppe Satriani
2. SPI Patterns: Learning from Experience
3. IEEE Software Magazine V18n3(May/June 2001)pp28-35
4. =EXPERIENCES IMPROVEMENT WWW STATISTICS PATTERNS CMM PIE Vasie
5. PIE::=Process Improvement Experiment", a project that aims to demonstrate the benefits of of improvement by experiment.
6. Vasie::= See http://www.esi.es/vasie, a repository of more than 250 European PIEs.
7. impact analysis: one year later. Quality can be improved - especially by mature organizations.
8. Technical goals are more likely to be achieved than business goals.
9. There are many paths to improvement.
Eshuis06
1. Rik Eshuis
2. Symbolic Model Checking of UML Activity Diagrams
3. ACM TOSEM Trans Software Eng & Methodology V15n1(Jan 2006)pp1-38
4. =DEMO V&V SQA Model checking UML1.5 activity diagrams NuSMV PLTL-X
5. Page 8 describes the shift in semantics from UML1.5 to HML2.0 but not the state machine vs activity diagram ambiguity in UML2.0.
6. Describes two translations into hypergraphs using WAIT states --activity machines.
7. Hypergraph:=Net{Node:Set, Hyper_Edge:Set, source:Hyper_edge->@Node~{{}}, target:Hyper_edge->@Node~{{}} }.
8. Defines two semantics: maximal parallel instantaneous unqueued actions vs queued single-event steps-take-time.
9. Shows these equivalent in special cases.
10. Claims to derive CRUD constraints from activity+class diagrams. Evidence is weak.
11. Tool shows that the queued single-event semantics does not scale. 19 activities is too many.
EtzioniGoldenWeld97
1. Oren Etzioni & Kieth Golden & Daniel S Weld
2. Sound and Efficient closed-world reasoning for Planning
3. Arif Intell V89n1-2Z(Jan 1997)pp113-148
4. when the data base is complete it is ok to use the closed world assumption about that "local" database
5. a sound efficient but incomplete system of reasoning
EugsterGuerroaui04
1. Patrick T Eugster & Rachid Guerroaui
2. Distributed programming with typed events
3. IEEE Software Magazine V21n2(Mar/Apr 2004)pp-
4. =DEMO NET DATAFLOW TYPED PUBLISH/SUBSCRIBE TPS GDACs Generic Java rpc lynda
5. decouple processes in time, space, & flow.
Evans82
1. ?? Evans
2. Software Engineering for the COBOL environment
3. Commun ACM v25 n12 (Dec 1982)
4. sequential
Evans01
1. Gary K Evans
2. Palm-sized Process: Point-of-sale gets agile
3. Software Development Magazine V9n9(Sep 2001)pp28-32
4. =CASESTUDY AGILE POS ITERATIVE EVOLUTION Java PEOPLE LITE RUP UML Modeling LEGACY SYSTEM
5. Unexpected complexity. 14 deliveries, one per 4 weeks, small team, good manager, cubicles+war-room w white boards.
6. (above)|-next project will reduce modeling further.
Evans03
1. Gary K Evans
2. UML2.0 Primer
3. Software Development Magazine V11n4(Apr 2003)pp36
4. =SIDEBAR UML Parts Ports Connectors
5. UML2_0::= See http://www.u2-partners.org/.
6. A part is a set of objects contained within another object called the owner. Owners are composed of parts.
7. Parts have ports (small squares). Ports can be connected by connectors. Ports can have interfaces: provided to others, required from others.
8. A Connector is an association indicating communication between parts and/or thru ports. Connectors can be assembly or delegation connectors
EvansGuttagHorningTan94
1. David Evans & John Guttag & Jame Horning & Yang Meng Tan
2. LCLint: A Tool for Using Specifications to Check Code
3. SIGSOFT'94 Proc 2nd ACM SIGSOFT Symp on Foundations of Software Engineering & ACM SIGSOFT Software Engineering Notes V19n5(Dec 1994)pp
Evanco03
1. William M Evanco
2. Comments on "The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics"
3. IEEE Trans Software Engineering V29n7(Jul 2003)pp670-672
4. =CRITIQUE STATISTICS QUALITY CODE SIZE OBJECT-ORIENTED METRICS
5. (1) Need studies of how several metrics effect quality.
6. (2) Select variables with a view to causality (as shown by timing) even if there is a correlation.
7. Example: LoC correlates with Number of Methods. But Number of Methods drives size of Code rather than Vice versa.
EvansEtal03
1. Gary Evans & Allen Vander Meulen & Donna L Davis & Scott Meyers & Name Withheld
2. Curse of the Living Code: Five Bone Chilling Tales of IT
3. Software Development Magazine V11n10(Oct 2003)pp29-31
4. =ANECDOTEs AGILE REQUIREMENTS USER RISKS COMMENTS EVOLUTION
5. Agile development meets big design up front - of a database. Godzilla meets Bambi? Management may require agile development but force a complete set of requirements first!
6. Programmer removes comments placed by colleague to preserve job security.
7. User interface has 11 or more different ways to close a window.
8. When a programmer chooses a bad user interface, the user and organization pays, not the programmer.
9. There is no such thing as a one-off solutions.... "not only did it survive, it mutated into a two-headed beast".
EvansLarochelle02
1. David Evans & David Larochelle
2. Improving Security Using Extensible Lightweight Static Analysis
3. IEEE Software Magazine V19n1(Jan/Feb 2002)pp42-51
4. =CASESTUDY C gets TOOL Splint was LCLint taint
5. Common and detectable defects lead to exploitable security holes.
6. defect stats: buffer overflow 19%, malformed input 16%, memory leaks, format bugs 6%, ...
7. Splint::GPL ::= See http://www.splint.org.
8. C source code + annotations /*@,,,@*/ static checked assertions.
EvansSammutEtal05
1. A Unified Superstructure for UML
2. Andy Evans & Paul Sammut & James S. Willans & Alan Moore & Girish Maskeri
3. Journal of Object Technology Vn1(Jan 2005) [ article6 ]
4. =DEMO UML SYNTAX vs SEMANTICS
5. Proposes providing a common abstract syntax for all structural diagrams and a different one for all behaviorial diagrams.
EvaristoDesouzaHollister05
1. J Roberto Evaristo & Kevin C Desouza & Kevin Hollister
2. Centralization momentum: the pendulum swings back again
3. Commun ACM V48n2(Feb 2005)pp67-71
4. =HISTORY DECENTRALIZATION
5. Notes
EveleensVerhoerf10
1. J Laurenz Eveleens & Chris Verhoef
2. The rise and fall of the Chaos Report figures
3. IEEE Software Magazine V27n1(Jan/Feb 2010)pp30-36
4. =CRITIQUE STATISTICS PROJECT SUCCESS CHALLENGED ESTIMATION
5. Provides evidence that the process used by the Standish group to measure the percentage of projects that succeed is actually measuring the accuracy of the estimates at the start of the project not the real success of the project.
6. Problems with a closed data set.
7. Tendency to sensationalize results when advocating new methods.
EvermannWand05
1. Joerg Evermann & Yair Wand
2. Toward formalizing domain modeling semantics in language syntax
3. IEEE Trans Software Engineering V31n1(Jan 2005)pp21-37
4. =IDEA REALITY DOMAIN Bunge ONTOLOGY LANGUAGES MODEL UML STATE CHART METAMODEL
5. Map ontology of the real domain into constraints on modeling languages to minimize "impedance mismatch" between analysis and design.
FaegriHanssen07
1. Tor Erlend Faegri & Geir Kjetil Hanssen
2. Collaboration, Process Control, and Fragility in Evolutionary Product Development
3. IEEE Software Magazine V24n3(May/Jun 2007)pp96-104
4. =EXPERIENCE Evo GILB EVOLUTION METRICS IMPROVEMENT
5. Reports on a two-year process of introducing and adapting Tom Gilb's Evo (1981) Process.
6. Evo has a strict weekly schedule, defines increments in terms of measurable stakeholder needs.
7. It needs efficient tools to support the rapid weekly cycle of adding requirements and testing solutions.
8. May need to add "Green weeks" where system is tested without new functions being added. May need to have some 2 week iterations.
9. Evo depends on the presence of the stakeholders.
10. Evo improves customer satisfaction.
11. (dick)|-for a good comparison of Evo with other agile methods see [Larman04]
Fafchamps94
1. Danielle Fafchamps(HP labs)
2. Organizational Factors & Reuse
3. IEEE Software Magazine V11n5(Sep 1994)pp31-41
Fagan76
1. M E Fagan
2. Design & Code Inspections to Reduce Errors in Program Development
3. IBM Sys J. V15N3(1976) pp 182-211( IBM Reprint Order No. G32)
4. =EXPERIENCE SQA QUALITY
5. Compare [Fagan76]
Fagan99
1. M E Fagan
2. Design & Code Inspections to Reduce Errors in Program Development
3. IBM Sys J. V38N2(1999)pp182-211 [ scholar?hl=en&lr=&cluster=1567005265693599201 ]
4. =EXPERIENCE SQA QUALITY
5. Compare [Fagan76]
6. A precisely defined and proven method of examining code to find out the defects within it.
Fairbairn87
1. Making Form follow Function: An Experiment in Functional Programming Style
2. Software - Practice and Experience V17n6(Jun 1987)pp379-386
3. design PURPOSE
FairleyWilshire05
1. Richard E (Dick) Fairley & Mary Jane Wilshire
2. Iterative Rework: The Good, the Bad, and the Ugly
3. IEEE Computer Magazine V38n9(Sep 2005)pp34-41 =ESSAY PROCESS STATISTICS QUALITY CONTROL CHARTS REWORK EVOLUTION ITERATION RE FACTORING REWORK AGILE ITERATIVE Too much (>20%) or too little rework(<10%) means something is wrong. So track % rework on a statistical control chart (Shewart 1920s) with upper and lower control levels. Trends, spikes, and random walks over the same limit trigger ro ot cause analysis and improvement.
4. All types of rework can be good, bad, or ugly!
5. Rework= Evolutionary_rework | Avoidable_rework.
6. Evolutionary_rework::=response to changing world.
7. Avoidable_rework::=Retrospective_rework | Corrective rework.
8. Retrospective_rework::= work that could have been before.
9. Corrective rework::= work the fixes defects in current or previous versions Distinctions are not very objective but good enough to suggest process improvements.
FangSoKreindler96
1. F W(Walter) Fang & Andrew C So & R Jordan Kreindler
2. The Visual Modeling Technique(VMT) : An Introduction and Overview
3. JOOP (Jul-Aug 1996)pp48-57+73
4. VMT::=OMT+Use cases+RDD+CRC+object types(entity|interface|control)+event traces+pre/post-conditions. [CRC]
FarenhorstVliet08
1. Rik Farenhorst & Hans van Vliet
2. Experiences with a Wiki to Support Architectural Knowledge Sharing
3. 3rd Workshop on Wikis for Software Engineering (Sep 2008) .See http://farenhorst.eu/publications/Farenhorst-vanVliet-Wikis4SE2008-CRC.pdf (download November 24th 209).
4. =EXPERIENCE WIKI ARCHITECTURAL DECISIONS NPK
5. How to make it easy for a team to store, retrieve and develop architectural decisions and their rationales using a Wiki.
6. Knowledge = Decisions + Design.
7. Concern=Net{Description, #Alternative, Ranking Criteria, O(Decision)}
8. Decision=Net{Id, Status, #Relationship, Rationale}.
9. Do start small.
10. Do allow and stimulate all types of knowledge.
11. Do strive for integration.
12. Don't impose too much structure.
13. Don't restrict access
Farquhar05
1. Cynthia Patrice Farquhar
2. An Empirical Study: usage of the Unified Modeling Language in the Bachelor of Science and Master of Science Degree Programs at California State University, San Bernardino
3. CSUSB CSci Masters Thesis March 2005
4. =EMPIRICAL CSUSB STUDENT UML USAGE PEDAGOGY
5. All undergraduates and most(96%) of graduate students know what the UML is.
6. Was the UML used as a blueprint, sketch, programming language, or required documentation? [Martin Fowler 2003]
  Table
  Usage % of time
  Required 83%
  Sketch 78%
  Blueprint 76%
  Language 38%
  
  (Close Table)
Farley01
1. Jim Farley
2. Picking a Winner: .NET vs J2EE
3. Software Development Magazine V9n3(Mar 2001)pp36-42
4. =COMPARISON PLATFORM Microsoft XML C# CLR Sun Java Beans JVM
5. J2EE::="Java 2 Enterprise Edition".
6. "Surprisingly similar".
7. J2EE works with Windows+Linux and Solaris, .NET works with windows only.
8. J2EE needs Java code, .NET accepts C++, VB, and C#.
9. XML is central to .NET and peripheral to J2EE.
Farmer03
1. William M Farmer
2. A Basic Extended Simple Type Theory
3. McMaster University Hamilton Ontario CA (29 Sep 2003)
4. =IDEA LOGIC TYPES
5. BESTT::= CSTT with HOL, sets, lists, & tuples.
6. CSTT::= Church's Simple Type Theory.
Farmer06
1. Eugene Farmer
2. The Gatekeeper's Guide,or How to Kill a Tool
3. IEEE Computer Magazine V39n10(Oct 2006)pp12-13
4. =JOKE TOOLS FAILURE
5. proposes 10 ways to stop a tool being adopted
  1. Make it Optional.
  2. Economize on Training -- a lecture with 50 Powerpoiont slides and no workshops, handson experience, or real examplesof use.
  3. Don't use a real project.
  4. Never integrate the tool into the workflow or with other tools.
  5. Use it sporadically.
  6. Call it a "quality initiative"
  7. Marginalize the champion.
  8. Capitalize on early misteps.
  9. Make only a small investment
  10. Exploit fear, uncertainty, doubt, laziness, and inertia.
FarmerMohrenschildt00
1. William M. Farmer and Martin v. Mohrenschildt
2. Transformers for Symbolic Computation and Formal Deduction
3. Presented at a Workshop on the Role of Automated Deduction in Mathematics, CADE-17, Carnegie Mellon University, Pittsburgh, Pennsylvania, June 2000 [ transformers.pdf ]
4. =IDEA LOGIC DEDUCTION COMPUTATION TERM TRANSFORMERS
5. STTM::="von-Neumann-Bernays-Goedel set theory". This has terms and formulas. Terms may be undefined, but formulas are always defined and are either true or false.
6. Transformers are total functions which may or may not preserve meaning or logistic properties like being (provably) true or false.
Farrell95
1. Joseph Farrell
2. Arguments for Weaker Intellectual Property Protection in Network Industries
3. StandardView V3n2(Jun 1995)pp46-49
Farrow84
1. Rodney Farrow
2. Generating a Production Compiler from an Attribute Grammar
3. IEEE Software Magazine (Oct 1984) pp77-93
4. DDD
Faulketal92
1. Stuart Faulk & John Brackett & Paul ward & James Kirby Jr
2. The CORE Method for Real-Time Requirements
3. IEEE Software magazine V9n6(Sep 1992)pp22-33
  [SPC93]
  1. CORE::=Consortium Requirements Engineering Paul Ward's CASE + David Parnas
  2. CASE::= Ward+Mellor Parnas - four variables: monitored, controlled, input and output constraints Nat: from nature and Req from required Relations
    Objects encapsulate design decisions
    Context, ERD, STD, forms for objects, Independent of any format, standard or notation.
FaulkHietmeyer97
1. Rigorous Requirements for Real-Time Systems: Evolution and Application of the SCR method
2. Tutorial [ICSE'97]
3. Derived from CORE
FavaroPfleeger98
1. John Favaro & Shari Lawrence Pfleeger<s.pfleeger@ieee.org>
2. Making Software Development investment Decisions
3. ACM SIGSOFT Software Engineering Notes V23n5(Sep 1998)pp69-74
4. =THEORY COSTS IMPROVEMENT
5. Making decisons: "Customer satisfaction alone is inadequate", "Market leadership alone is inappropriate".
6. Compares rules used in SE litereature for estimating the value of an investment: Net Present Value, Payback, Average return on Book value, Internal rate of return, Profitability index. Reccommends first.
7. NPV::= sum[t:Time]discounted(benefit(t), t) - initial_investment.
Fayad02
1. Mohamed Fayad
2. Accomplishing Software Stability
3. Commun ACM V45n1(Jan 2002)pp111-115+ letters V45n5(May 2002)pp11-12
4. =EXAMPLE (kitchen) REALITY Object-Oriented ARCHITECTURE EBTs enduring BUSINESS THEMES BUSINESS OBJECTS
5. In a kitchen there are certain enduring business themes (EBT) : food storage and preservation, cooking, cuisine, livability. Livability includes cleanliness, light, and convenience. Light is a class of business objects. Cuisine has Recipes as business objects.
6. These themes are expressed by changeable industrial objects: cabinet, refrigerator, range, cook-top, sink, window, shelf, etc etc
7. Themes are intangible, objects are not. Business is stable and implicit.
8. See previous [FayadAltman01]
FayadAltman01
1. Mohamed E Fayad & Adam Altman
2. An Introduction to software stability
3. Commun ACM V44n9(Sep 2001)pp95-98
4. =THEORY Object-Oriented DESIGN REALITY UML =CASESTUDY loans
5. Another example: [Fayad02]
6. stable designs fit the stable aspects of the environment well. More than cursory analysis needed.
7. Stable designs need EBTs and BOs modeled by classes (not functions).
8. EBT::concepts-"Enduring business Themes", examples: "friendship", "Finance", "solvency".
9. BO::things="Business Objects", -- examples:"friend", "loan", "expenses".
10. Proposes adding {enduring} and {business} "stereotype" to the UML.
11. (dick)|-UML ERROR: should be <<enduring>> and <<business>>.
12. (dick)|-perhaps some EBTs are better treated as ASPECTS.
Fayadetal93
1. Mohamed E Fayad & Louis J Hawn & Mark A Roberts & Jerry R Klatt (Macdonnel Douglas Corp)
2. Using the Shlaer-Mellor Object-Oriented Analysis Method
3. IEEE Software Magazine V10n2 (Mar 1993)pp43-52 + Correspondence V10n5(Sep 1993)pp6-7
4. OBJECT-ORIENTED METHOD OOA review
  1. p43. consistently produced better abstract objects than other OOMethods
  2. p44. Best applied to information systems or to re-engineering; when the data objects are defined.
    **disputed in correspondence** Colberts ws succssful, but SAD not defined map from analysis to design, or use of Ada Packages. S-M: 2 months for ERA, rules:uniformit, more than name, no Ors, more than a list. Tangibles|roles|incidents|interactions|specifications
  3. p47 CASE tool:=Teamwork
  4. pp48-49 ->> Object selection(ERA) is sound TNF rules Get a complete information model first, Need more than names and few lowlevel object classes defined. Good in the RT area States -> the wicked problem (Ramamoorthy). Weak in the PQ and S area.
  5. p50. Data and process analysis linked, can express constraints, but DFDs become cluttered needed a data and process dictionary. State models can list duplicate processes. Need more views of objects. Semantics difficult: Just choosing descriptive words.
  6. p51 Interaction insufficiently documented. DFD not much help (*disputed*)with update/retrieval but resulting processes are cohesive. TWO MONTHS.
Fayadetal94
1. Mohamed E Fayad & Wei-Tek Tsai & Mark A Roberts & Louis J Hawn & Jay W Schooley
2. Adapting an Object-Oriented Development Method
3. IEEE Software magazine v11n3(May 1994)pp68-76
4. =SURVEY METHODS Colbert OOSD MAINTENANCE
Fayadetal95
1. Mohamed E Fayad & Wei-Tek Tsai
2. Object-Oriented Experiences
3. Commun ACM V38n10(Oct 1995)pp51-53
4. recommends software ENGINEERING+training: 40 hours training over 10 weeks+metrics+process+plan+SQA
Fayadetal96
1. Mohamed E Fayad & Wei-Tek Tsai & Milton L Fulgrum
2. Transitions to Object-Oriented software Development
3. Commun ACM V39n2(Feb 1996)pp108-121
4. =EXPERIENCE EDUCATION PEOPLE
5. chaos to OO process takes a year independently of project team and techniques
  [Racko95d]
6. : "first step is to get process and then add OO"
FayadLaitinenWard00
1. Mohamed Fayad & Mauri Laitinen & Robert P Ward
2. Software Engineering in the Small
3. Commun ACM V43n3(Mar 2000)pp115-118 CR0102-0079
  =ESSAY Census data|-manysmall sooftware development companies
4. Small companies and start ups need scaled down procedures that are faster and co-evolve requirements along with the code.
5. Compare [Botting97a]
  [Botting95b]
Feather98
1. Martin S Feather
2. Rapid Application of Lightweight Formal Methods for Consistency Analysis
3. IEEE Trans SE V24n11(Nov 1998)pp949-959
4. =EXPERIENCE NASA DATABASE LISP
5. Wanted: moderate results extremely rapidly. Discover implicit causal loops.
FeatherLamsweerde94
1. Martin S Feather & Axel van Lamsweerde(eds)
2. Succeedings of the seventh International Workshop on Specifiction and Design(IWSSD7)
3. ACM SIGSOFT Software Engineering Notes V19n3(Jul 1994)pp18-20
Feijs93
1. Loe Feijs(Philips Reearch Laboratories Eindvoven)
2. A Formalization of Design Methods: A λ-calculus Approach to Systems Design with an Application to Text Editing
3. Ellis Horwood Chichester West Sussex UK 1993
4. ISBN 0-13-106113-5
5. Reviews CR9408-0498 IEEE Software magazine V11n5(Sep 1994)p130 by Anthony Hall(Praxis)
FeijsJonkers92
1. Loe M G Feijs & H B M Jonkers
2. Formal Specification and Design
3. Cambridge University Press (Cambridge UK & New York NY) 1992
4. $48 ISBN0-521-43457-2
5. Reviewed IEEE Software magazine v11n3(May 1994) & AMM Mar 1993 p296 & CR9412-0849
FeijsJong98
1. Loe Feijs & Roel de Jong
2. 3D Visualization of Software Architectures
3. Commun ACM V41n12(Dec 1998)pp73-78
4. =DEMO GRAPHIC 3D TOOL VRML RELATIONS LEGO GUCS
5. Compare [CallaghanHirschmuller98]
FeijsJonkers94
1. Loe M G Feijs & H B M Jonkers & Cornellis A Middelburg
2. Notations for Software Design
3. Springer Verlag 1994
4. =SURVEY COLD-1 FORMAL MATHEMATICS PICTORIAL
Fekete93a
1. Alan Fekete
2. Reasoning about Programs: Integrating Verification and Analysis of Algorithms Into The Introductory Programming Course
3. ACM SIGCSE Bulletin V25n1(Mar 1993) 24th Technical Symposium on Computer Science Education pp198-202
Fekete93b
1. Alan Fekete
2. Formal Models of Communication Services: A Case Study
3. IEEE Computer Magazine(Aug 1993)pp 37-47
FelberGuerraouiFayad99
1. Pascal Felber & Rachid Guerraoui & Mohamed E Fayad
2. Putting OO Distributed programming to Work
3. Commun ACM V42n11(Nov 1999)pp97-101
4. =ESSAY OBJECT-ORIENTED DISTRIBUTED TECHNICAL RELIABILITY
5. failure as a 1stclass abstraction, push & pull techniques
Felderetal94a
1. Miguel Felder & Dino Mandroli & Angelo Morzenti
2. Proving Properties of Real-Time Systems Through Logical Specifications and Petri Nets
3. IEEE Trans SE V20n2(Feb 1994)pp127-141
4. =FORMAL TIMING Temporal TRIO
  1. Dist( P, d )::=P is true d time units from (_),
  2. model of timed petrie nets
  3. proof that dining philosphers TPN is deterministic and every body eats every 7 units of time!
    compare with MATHS manual on Modal Logic
    Question: They prove a liveness property of the philosophers by proving a liveness property for one fork. Is this circular?
Felderetal94b
1. Miguel Felder & Angelo Morzenti
2. Validating Real-Time systems by History-Checking TRIO Specifications
3. Trans Softw Eng Methodol V9n4(Oct 1994)pp308-339
4. =EXPERIENCE TIMING TRIO LOGIC SPECIFICATION PROOF
  1. Futr(A,t)::=A(_+t), Past(A,t) ::=A(_-t)
  2. Table 1, p316 defines:
  3. AlwF, AlwP, Alw, SomF, SomP, Som,Lats,Lasted, since, Since[w], WithinP, Until, Until[w], UpToNow, FirstTimeF
FelderPezze02
1. Miguel Felder & Mauro Pezze
2. A Formal design Notation for Real-Time systems
3. ACM TOSEM Trans Software Eng & Methodology V11n2(Apr 2002)pp149-190
4. =EXPERIENCE GRAPHIC TIMING NOTATION SEMANTICS PETRI SA/RT ward-Mellor STATECHARTS Model-checking Cabernet
FellerFitzgeraldHoek01
1. Joseph Feller & Brian Fitzgerald & Adre van der Hoek
2. Making Sense of the Bazaar: 1st Workshop on Open source Software Engineering
3. ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp51-52 & IEEE Proceedings -- Software V149n1 & [ http://opensource.ucc.ie/icse2001/ ]
4. =CONFERENCE OPEN SOURCE
FeltyNamjoshi03
1. Amy P Felty & Kedar S Namjoshi
2. Feature Specification and automated Conflict Detection
3. ACM TOSEM Trans Software Eng & Methodology V12n1(Jan 2003)pp3-27
4. =CASESTUDY telecommunications SPECIFICATION FEATURES LOGIC LTL FSM Buchi MODEL Checking TOOL FIX COSPAN
5. Features expressed in sugared LTL: pre/post conditions. including until/unless discharge requirements.
6. Complex/careful definition of what it means for two features to conflict.
7. FIX use LTL approximation to find witnesses for conflicts.
FengEtAl11
1. Xin Feng & David Lorge Parnas & T H Tse & Tony O'Callaghan
2. A Comparison of Tabular expression-based testing strategies
3. IEEE Trans Software Engineering V37n5(Sep/Oct 2011)pp616-634
4. =THEORY =EXPERIMENT =ADVERT TABULAR EXPRESSIONS TESTING SUBSUMPTION
5. Tables are already useful for writing specifications perhaps they tables can be used to derive test cases?
6. Example based on western calendar.
7. Strategies: partition, decision tables, basic meaningful impact, fault-based
Fenton91
1. Norman Fenton
2. Software Metrics - A Rigorous Approach
3. Chapman & Hall London UK 1991
4. See Fenton94
Fenton94
1. Norman Fenton
2. Software Measurement: A Necessary Scientific Basis
3. IEEE Trans SE V20n3(Mar 1994)pp199-206
4. =THEORY METRICS COCOMO Function points
5. Notes [ Fenton94.mth ]
6. Compare with Matson, Barrett and Mellichamp SE-V20n4(Apr 1994) ->>p285:"The key point is that improved results may be achieved by unbundling the function point variable into its constituent components."
Fentonetal94
1. Norman Fenton & Shari Lawrence Pfleeger & Robert L Glass
2. Science and Substance: A Challenge to Software Engineers
3. IEEE Software magazine v11n3(July 1994)pp86-95+ Correspondence V11n5pp6+8 CR9509-0737
4. =ESSAY critiscizing computer science's contribution to software engineering and lack of empirical data testing theories.
5. Notes: [ Fentonetal94.mth ]
6. Good communication and management count more than technology
7. p 90:"Inspections are the cheapest and most effective testing techniques for finding faults"
8. p93: Software Engineering Lab: 8 major projects using OO/Ada.. reuse rises dramatically (20%..80%) but OO/Ada requires significant domain analyisis and project tailoring
FentonKrauseNeil02
1. Norman Fenton & Paul Krause & Martin Neil
2. Software Measurement: Uncertainty and Causal Modeling
3. IEEE Software Magazine V19n4(Jul/Aug 2002)pp116-122
4. =EXAMPLE STATISTICAL MODELS PROCESS PRODUCT Bayesian networks
5. regression does not predict errors well in practice. A positive correlation overall can become negative when another factor is taken into consideration (Simpson's paradox 1899).
6. (Bayes_theorem_simple): P(event given condition) = P(condition given event)*P(event)/p(condition).
7. Causality modeled by graph(node=>events, arrows=>causes), cause mean that p(one given other) is non zero.
8. Note: For a Bayesian Belief Network the formula is P(event given set of causes) not a set of P(event given one cause). [ maths/math_22_graphs.html#BAYESIAN_NETWORK ]
9. Shows how a distribution of defects depends on complexity and on the number of defects found and fixed in unit testing.
FentonNeil98
1. Norman E Fenton & Martin Neil
2. A Strategy for Improving Safety Related Software Engineering Standards
3. IEEE Trans SE V24n11(Nov 1998)pp1002-1013
4. =SURVEY STANDARDS RISKS
5. Conformance vs risk assessment, product vs process vs resource standards
6. Need for many ministandards not one big standard for all industries, software projects, and project phases
FentonNeil99
1. Norman E Fenton & Martin Neil
2. A Critique of Software Defect Prediction Models
3. IEEE Trans Soft Eng V25n5(Sep/Oct 1999)pp675-689
4. =SURVEY SQA METRIC QUALITY RELIABILITY DEFECT PREDICTION
5. problems:=following,
  1. how do defects relate to failures?
  2. weak statistical work
  3. Goldilock's Conjecture:=defect rate of large modules less than for very small ones.
6. BBN:=Bayesian Belief Network.
FentonOhlsson00
1. Norman E Fenton & Niclas Ohlsson
2. Quantitive Analysis of Faults and Failures in a complex software system
3. IEEE Trans Software Engineering V26n8(Aug 2000)pp797-814
4. =EXPERIENCES ANALYSIS SIZE METRICS RELIABILITY
5. Hatton and others: empirical data opposes theory of modular programming that large modules have proportionally more errors.
6. See [Adams84] most faults in use come from a few of defects.
7. Pareto analysis of sizes, faults, testing failures, and failures in 1st year of use.
  two releases.
8. 20% of modules account for 60% of the pre-release faults but only 30% of the size.
9. 10% of modules account for 80..100% of the operational failures. But they were in the smaller modules mainly.
10. Many pre-release faults predict fewer operational faults!
11. faults/LOC don't correlate with any f(LOC) or complexity metrics.
12. evidence that fault density does not change with time or release.
13. 10 times as many found in testing as in operation.
14. p812: There are no unbreakable laws of software engineering.
FergusonHumphreyEtal97
1. Pat Ferguson & Watts S Humphrey & Soheil Khajenoori & Susan Macke & Annettes Matvya
2. Results of Applying the Personal Software Process
3. IEEE Computer magazine V30n5May 1997)(pp24-31
4. =EXPERIENCES with PSP IMPROVEMENT
FerreJuristoWindlConstantine01
1. Xavier Ferre & Natalia Juristo & Helmut Windl & Larry Constantine
2. Usability Basics for Software Developers
3. IEEE Software Magazine V18n1(Jan/Feb 2000)pp22-29
4. =ADVERT USER QUALITIES
5. usability >== { learn-ability, efficiency, user retention over time, error rate, satisfaction }.
6. Must be analyses first, designed in at the front and tested for at the end with real users.
7. Many reviews before design. Benchmarks.
8. Conceptual design and visual design.
9. specifications : Table = attribute><instrument><values><current><worst acceptable><planed target><best possible><observed.
10. (Like Gilb!)
11. Prototypes: paper, wizard of Oz, scenarios, storyboards, snapshots.
FernandezRamsey97
1. Mary Fernandez & Norman Ramsey
2. Automatic Checking of Instuction Specifications
3. TOOL SLED fields opcodes...assembler idioms checker [ toolkit ]
FerrariGnesiMontanariPistore03
1. Gian-Luigi Ferrari & Stefania Gnesi & Ugo Montanari & Marco Pistore
2. A Model-Checking Verification Environment for mobile Processes
3. ACM TOSEM Trans Software Eng & Methodology V12n4(Oct 2003)pp440-473
4. =DEMO TOOL MODEL CHECKING MOBILE π-calculus FSM HD-Automata HAL π-logic ACTL
FerrisFarrell03
1. Christopher Ferris & Joel Farrell
2. What are Web Service
3. Commun ACM V46n6(Jun 2003)p31
4. =SIDEBAR WEB/NET SERVICES W3C URI XML WSDL SOAP
5. An application identified by a URI with interface and bindings defined described and discovered via XML.
6. See
7. Web_Services_Architecture_Draft::= See http://www.w3.org/TR/WD-wsa-xxx.
8. Finding, publishing and working with services provided over the web.
9. WSDL::="Web services description Language"
Fetzer88
1. J H Fetzer
2. Program Verification: The Very Idea
3. Communications ACM V31n9(Sep 1988)pp1048-1063
4. algorithms can be proved but programs can not be. Used in Dasgupta91
FeysFitch69
1. RObert Feys & Frederic B Fitch
2. Dictionary of Symbols of Mathematical Logic
3. Amsterdam North-holland Pub Co 1969
4. =DICTIONARY LOGIC SYMBOLISM LANGUAGE
FiadeiroMaibaum95
1. Jose Luiz Fiadeiro(Ilf@di.fc.ul.pt) & Tom Maibaum(tsem@doc.ic.ac.uk)
2. Interconnecting Formalisms: Supporting Modularity& Reuse and Incrementality [Kaiser95]
FichmanKemerer92
1. Robert G Fichman & Chris F Kemerer
2. Object-Oriented and Conventional Analysis and Design Methodologies
3. (Special Issue: Object-Oriented Computing) IEEE Computer Magazine V25n10(Oct 1992)pp22-39
FichmanKemerer97
1. Robert G Fichman & Chris F Kemerer
2. Object Technology and Reuse: Lessons from Early Adopters
3. IEEE Computer Magazine V30n10(Oct 1998)pp47-59
4. =EXPERIENCES OBJECT-ORIENTED REUSE
5. authors visited 4 companies:steep OO learning curve+immature tools+reuse<OO vision
6. lessons: Money for learning+complete architecture first+reuse is separate+adopting OO is R&D
FickasHelm92
1. Stephen Fickas & B Robert Helm
2. Knowledge Representation and Reasoning in the Design of Composite Systems
3. IEEE Trans SE-18n6(Jun 1992)pp470-482
4. Composite::=hard+soft+human
5. lift problem - difficult to evaluate our design
6. Critter
7. design states::= generative infrastructure and constraints
8. CR9307-0467
Fidge96
1. Colin Fidge
2. Fundamentals of Distributed System Observation
3. IEEE Software Magazine V13n6(Nov 1996)pp77-83
FidgeKearneyUtting97
1. Colin Fidge & Peter Kearney & Mark Utting
2. A Formal Method for Building Concurrent Real-Time Software
3. IEEE Software magazine V14n2(Mar/Apr 1997)pp99-106
4. Quartz DEMO nonsequential performance method. Does it resolve Parnas's Problem?
FieldRamalingam99
1. John Field & G Ramalinga
2. Identifying Procedural Structure in COBOL Programs
3. PASTE'99 & ACM SIGSOFT Software Engineering Notes V24n5(Sep 1999)pp1-10
4. =ADVERT IBM VisualAge STRUCTURE LEGACY MAINTENANCE
Fielding99
1. Roy T Fielding
2. Shared Leadership in the Apache Project
3. Commun ACM V41n4(Apr 1999)pp42-43
4. =EXPERIENCE PEOPLE PROCESS
FieldsElvang-Goranson92
1. Bob Fields & Morten Elvang-Goranson
2. A VDM Case Study in Mural
3. IEEE Trans SE-18n4(Apr 1992)pp279-295
4. VDM Mural specification and proof system using LPF Manchester and Rutherford Labs UK
5. slow
6. unfriendly
7. tedious time consuming
8. no library..
FilipenkoMorris92
1. I Filipenko & F L Morris
2. Domains for Logic Programming
3. Theor Comput Sci V94n1(Mar 1992)pp63-99
4. CR9304-0239"Original and sound"
FilmanEtal02
1. Robert E Filman & Stuart Barrett & Dianna D Lee & Ted Linden
2. Inserting Ilities by Controlling Communications
3. Commun ACM V45n1(Jan 2002)pp116-122
4. =IDEA OIF Object-Oriented WEB/NET QUALITIES TOOL Pragma = EXPERIENCE CORBA/Java cf ASPECT
5. OIF::="Object Infrastructure Framework",
6. Theory:= iities can be injected as objects that act on communications between functional objects.
7. Pragma maps high level properties into a suitable injector initializations.
8. Annotations allow the object that implement ilities to share meta-data.
FindlerLatendresseFelleisen01
1. Robert Bruce Findler & Mario Latendresse & Mathias Felleisen
2. Behavioral Contracts and Behavioral Subtyping
3. ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp229-236
4. =THEORY REUSE RUNTIME V&V TOOLS Object-Oriented MODULES JAVA
5. Assigning blame for errors to the caller, the called,or the hierarchy.
6. Tools should report hierarchy errors as well as pre/post condition mismatches.
7. Notation: method m in class C has precondition pC and postcondition qC expressed as sets of argument values. A call C.m(x) is correct if x in pC and is executed correctly if x in qC afterwards.
8. If D is derived from C(D extends C), m is a method in D and C then( ( pC ==> pD)and (qD ==> qC).
9. Most tools presume these conditions hold and replace pD by pD & pC, qD by qC | qD. --- this is wrong.
Finkelsteinetal94
1. Anthony C W Finckelstein & Dov Gavey & Anthony Hunter & Jeff Kramer & Bashar Nuseibeh
2. Inconsistency Handling in Multiperspective Specifications
3. IEEE trans on Soft Eng vSE-20n8(Aug 1994)pp569-578
4. =IDEA REQUIREMENTS LOGIC SPECIFICATION See Nuseibehetal94
  1. VeiwPoint::=Net{Style, Work_Plan, Domain, Specification, Work_Record}.
FinkHouse89
1. C Fink & K House
2. Expert Systems Development: The Next Generation
3. System Builder (Oct/Nov 1989)pp14-26
4. AI Reality
Finney96
1. Kate Finney
2. Mathematical Notitation in Formal Specifications: Too Difficult for the Masses?
3. IEEE trans on Soft Eng vSE V22(Feb 1996)pp158-9
4. readable
FioravantiNesi01
1. Fabrizio Fioravanti & Paolo Nesi
2. Estimation and Prediction Metrics for Adaptive Maintenance Effort of Object-Oriented Systems
3. IEEE Trans Software Engineering V27n12(Dec 2001)pp1062-1084
4. =ANALYSIS EXPERIENCE METRICS ESTIMATE MAINTENANCE Object-Oriented EVOLUTION MUSIC
5. proposes tests and recommends a complex measure for predicting maintenance effort.
6. Methods are more important for estimation than attributes. Complex interfaces are important.
Firesmith90
1. Donald G. Firesmith
2. "OOD and Ada Bibliography"
3. Ada Letters VXn6(July/Aug 1990)pp114-128
4. (SIGADA) ACM Press
Firesmith93
1. Donald G. Firesmith
2. Object-oriented Requirements analysis and logical design: A software engineering approach
3. John Wiley & sons NY NY 1993 ISBN 0-471-57807-X CR9502-0058
Firesmith05
1. Donald G Firesmith
2. Quality Requirements Checklist
3. JOT V4n9(Nov-Dec 2005)pp31-38 [ column4 ]
4. =HOWTO QUALITIES MODEL V&V
5. Stresses the importance of specifying (1) the conditions when the requirement applies, (2) a measurement, and (3) the minimum threshold value.
6. Quality_Requirement::= Net{conditions, criteria: Quality_subfactor, threshold: Quality_metric }.
FiresmithEykholt95
1. Donald G. Firesmith & Edward M Eykholt
2. Dictionary of Object technology: the Definitive Desk Reference
3. SIGS publications Inc NY NY 1995 $55 ISBN 1-884842-09-7 CR9506-0386
Fishburne00
1. William Fishburne
2. Margination and Project Gutenberg
3. Dr. Dobbs #312(May 2000)pp52+54-56
4. =ALGORITHM ASCII optimal linebreaks word wrap
5. Example of problems with informal specifications.
6. For all lines l, if l.length>0 then 55<= l.length <=75.
7. optimal lines l, l.length=65.
8. ??aim for mean of 65 with standard deviation 5.
9. more aesthetic=>Τ_ΕΧ, simple word wrap=> 'br'
FislerKrishnamurth01
1. Kathi Fisler & Shiram Krishnamurthi
2. Modular Verification of Collaboration-Based Software Designs
3. ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp152-163
4. =THEORY NONSEQUENTIAL CTL MODULE VERIFICATION FSM/AUTOMATA CROSSCUTTING FSATS
FittingMendelsohn98
1. Melvin C. Fitting and Richard Mendelsohn
2. First-Order Modal Logic
3. Kluwer 1998 paperback 1999
4. =TEXT FORMAL LOGIC MODAL THEORY
5. Modal predicate logic
Fitzgerald03
1. Michael Fitzgerald
2. Trash your desktop
3. MIT Technology Review V106n9(Nov 2003)pp42-46
4. =IDEA EMAIL ORGANIZER PIM Chandler
5. Mitch Kapor(Lotus 123), Andy Hertzfield(MacPaint, HyperCard, Magic OS)
Fitzgerald04
1. Brian Fitzgerald
2. A Critical Look at Open Source
3. IEEE Computer Magazine V37n7(Jul 2004)pp92-94
4. =ESSAY OPEN SOURCE F/OSS
5. Lists reasons why F/OSS is "doomed to fail": lack of talent, maintaining quality, coupling between modules, doing mundane tasks, little support, no standards.
6. However: F/OSS developers are professional. Collaboration is high. Costs are lower. Code is highly modular. Quality control is in place.
Fitzgerald11
1. Brian Fitzgerald
2. Open source software: lessons from and for software engineering
3. IEEE Computer V44n10(Oct 2011)pp25-30
4. =SURVEY F/OSS ENGINEERING MODULARITY CM PEER REVIEW EMAIL ONION CONTINUOUS RELEASE
5. Evidence for value of version control, modularity, configuration management, peer review, status, iteration, etc.
FitzgeraldEtal05
1. John Fitzgerald & Peter Gorm Larsen & Paul Mukherjee & Nico Platt & Marcel Verhoef
2. Validated designs for Object-Orients Systems
3. Springer-Verlag NYNY 2005 ISBN 1852338814 CR 0605-0447 [ http://www.vdmbook.com/ ]
4. =UNREAD =MANUAL VDM++
5. Notes [click here if you can fill this hole]
FitzgeraldOKane99
1. Brian Fitzgerald & Tom O'Kane
2. A Longitudinal Study of Software Process Improvement
3. IEEE Software Magazine V16n3(May/Jun 1999)pp37-45
4. =EXPERIENCE CMM level 4 for Motorola cellular phone software Ireland
5. CMM must be tailored, CSF (Critical Success Factors) help.
6. Prompt process notation
FitzgeraldRussoOKane03
1. Brian Fitzgerald & Nancy Russo & Tom O'Kane
2. Software development Method Tailoring at Motorola
3. Commun ACM V46n4(Apr 2003)pp65-70
4. =EXPERIENCE ENGINEERING ONESIZE PROCESS IEEE1074 V-SDLC CMM
5. Tailoring methods takes part at the industry, organization, division and project level.
6. Follows from [FitzgeraldOKane99]
FlanaganFreund10
1. Cormac Flanagan & Stephen N Freund
2. FastTrack: efficient and precise dynamic race detection
3. Commun ACM V53n11(Nov 2010)pp93-101 [ 1839676.1896939 ]
4. =DEMO SHARED MEMORY HAZARDS VECTOR CLOCKS FAST PERFORMANCE
5. See also [Adve10] and [ElmasQadeerTasiran10]
FlanaganFreundQadeer05
1. Cormac Flanagan & Stephen N Freund & Shaz Qadeer
2. Exploiting Purity for Atomicity
3. IEEE Trans Software Engineering V31n4(Apr 2005)pp275-291
4. =THEORY NONSEQUENTIAL PURE ATOMIC REDUCTION
Flatt12
1. Mathew Flatt
2. Creating languages in Racket
3. Commun ACM V55n1(Jan 2012)48-56 [ 2043176.2063195 ]
4. =DEMO ADVENTURE GAME RACKET LISP EXTENSION LANGUAGES
Flor06
1. Nick Flor
2. Globally distributed software development and pair programming
3. Commun ACM V49n10(Oct 2006)pp57-58
4. =IDEA DISTRIBUTED PAIR PROGRAMMING
5. Refers back to earlier theories of how side-by-side pair programming generates better solutions...
6. Need to develop an environment that not only lets two people see and discuss a common artifact, but also lets the programmers see and hear each other's "gestures and mumbles".
FloracCarletonBarnard00
1. William A Florac & Anita D Carleton & Julie R Barnard
2. Statistical Process Control: Analyzing a Space Shuttle Onboard Software Process
3. IEEE Software Magazine V17n3(Jul/Aug 2000)pp97-106
4. =EXPERIENCE SQA/V&V PROCESS SPC SEPG
5. control charts, variations are predictable | abnormal
6. know the process and its data
Floyd67a
1. Robert W Floyd
2. Assigning Meaning to Programs
3. pp19-32 of Proceedings of Symposia in Applied Mathematics Vol XIX
4. formal logic PROOF
Floyd67b
1. Robert W Floyd
2. Non-deterministic Algorithms
3. J ACM V14n4 pp636-644(Oct67)
4. =CLASSIC non-sequential non-determinism
FloydC91
1. Christiane Floyd
2. Software Development as Reality Construction
3. pp86-100 in [FloydCetal91]
4. =THEORY PEOPLE STAKEHOLDERS VIEWS REALITIES EVOLUTION USER POSTMODERN
5. multiple perspectives
6. evolution and integrating production with use
7. involving people "a web of design decisions"
FloydCetal91
1. Christiane Floyd & Heinz Zu"llighoven & Reinhard Budde & Reinhard Kiel-Sawic (Eds)
2. Software Development & Reality Construction
3. Springer Verlag NY NY 1992
4. ISBN 0-387-54349-X QA76.76D47S633
5. Post-modern
FloydUllman82
1. Robert W Floyd & Jeffery D Ullman
2. The Compilation of Regular Expressions into Integrated Circuits
3. J ACM (Jul 1982)
4. regular non-sequential Technical
FluriEtAl07
1. Beat Fluri & Michael Wursch & Martin Pinzger & Harald C Gall
2. Change Distilling: Tree Differencing for Fine-Grained Source Code Change Extraction
3. IEEE Trans Software Engineering V33n11(Nov 2007)pp725-743
4. =DEMO ALGORITHM TOOL Eclipse plugin AST STRING MATCHING
FlynnHoverdBrazier90
1. Mike Flynn & Tim Hoverd & David Brazier
2. Formaliser - an Interactive Support Tool for Z
3. pp128-141 in Nicholls90
4. PC/AT WYSIWYG windows to LATEX with parsing smalltalk and type checking
FocardiMarchesiSucci01
1. Sergio Focardi & Michele Marchesi & Giancarlo Succi
2. A stochastic Model of Software Maintenance and its Implications on extreme Programming Processes
3. In [SucciMarchesi01] pp191-206
4. =THEORY RANDOM GRAPH MODEL SOFTWARE MAINTENANCE CONTAGION
Fogel03
1. David Fogel
2. Evolutionary Entertainment with Intelligent Agent
3. IEEE Computer Magazine V36n6(Jun 2003)pp106-108
4. =EXPERIENCE AI GAMES PERSONA EXPERT EVOLUTION AGENT NEURAL WEB/NET CHECKERS DRAUGHTS Blondie24
5. =ADVERT book product
6. After 840 generations moved to top 500 of 120,000 players on www.zone.com
7. Needed to adopt a female persona to stop opponents swearing at the neural network.
Fokkink07
1. Wan Fokkink
2. Modelling distributed systems
3. Springer 2007 ISBN 978-3-540-73937-1 QA76.58 F65
4. =TEXT NONSEQUENTIAL FORMAL microCRL ACP DATA TOOLS μ_CRL ALGEBRA
FoleyDumigan01
1. Simon N Foley & Robert Dumigan
2. Are Hand-held viruses a significant threat
3. Commun ACM V44n1(Jan 2001)pp105-107
4. =DEMO RISKs PALM TECHNICAL
FongCameron01
1. Philip W L Fong & Robert D Cameron
2. Proof Linking: Modular verification of Mobile Programs in the Presence of Lazy, Dynamic Linking
3. ACM TOSEM Trans Software Engineering & Methodology V9n4(Oct 2000)pp379-409 CR0105-01777
4. =THEORY MODULE PROOF of LINKING NET/WWW bytecode verification DEMO Java
Foo87
1. Norman Y Foo
2. Algebraic Specifications as Solutions of Implementaion Equations
3. IEEE Trans Soft Eng VSE-13n12(Dec 1987)pp1364-1369
4. if finite algebraic spec exists than can derive it from an implementation by algebra using equivalence relations. works with initial and final algebras. method fails when no finite spec. unsolvable problem: whether algebra is free(no equations)+how many eqns needed
Foo93
1. Norman Y Foo
2. Comments on "Defining Software by Continuous Smooth Functions"
3. IEEE Trans SE 19 n3(Mar 1993)pp307-309
  1. sensitivity(T)::= sup[x:design_parameters~{0}](norm(T(x))/norm(x))
    refs to: R A De Millo R J Lipton, Defining Software by Continuous Smooth Functions, IEEE Trans SE 17 n4(Apr 1991)pp383-384.
Ford91
1. Gary Ford
2. The SEI Undergraduate Curriculum in Software Engineering
3. SIGCSE Bulletin V23n1(Mar 1991)pp375-385
Ford04
1. Bryan Ford
2. Parsing expression grammars: a recognition-based syntactic foundation
3. ACM 31st SIGPLAN-SIGACT symposium on Principles of programming languages(2004)pp111-122 [ 964001.964011 ]
4. =IDEA PRIORITIZED CHOICE reduces AMBIGUITY PARSING CFG GRAMMAR
5. PEG::="Parsing Expression Grammar", [ Parsing_expression_grammar ]
6. Use "/" instead of "|" to express an "or" where the left hand parsing is taken whenever possible
7. Other techniques to handle "and" and "or".
FormicaMissikoff02
1. Anna Formica & Michele Missikoff
2. An extended XML approach to ontology engineering
  [SCI2002] V1(Jul 2002)
3. =IDEA DATA XML ONTOLOGY OPAL
Forte97
1. Gene Forte
2. Managing change for Rapid Development
3. IEEE Software magazine V14n2(Mar/Apr 1997)pp120-122
4. control/communicate/feedback change+timebox+plan/design for change
Fortnow09
1. Lance Fortnow
2. The status of the P versus NP problem.
3. Commun ACM V52n9(Sep 2009)pp78-86 [ 1562164.1562186 ]
4. =SURVEY THEORY PERFORMANCE COMPLEXITY NP NP-HARD NP-COMPLETE P=NP?
5. "What we would gain from P = NP will make the whole Internet look like a footnote in history."
6. "Since all the NP-complete optimization problems become easy, everything will be much more efficient. Transportation of all forms will be scheduled optimally to move people and goods around quicker and cheaper. Manufacturers can improve their production to increase speed and create less waste."
7. probably P<>NP. But no proof yet.
8. Quantum computers probably won't do it.
9. For practice see [MalikZhang09]
Foster77
1. M A Foster
2. The Game Players of Zan
3. DAW books no. 236, Donald A. Wollheim New York NY 1977
4. =FICTION cellular automata life
FossStensrudKitchenhamMyrtveit03
1. Tron Foss & Erik Stensrud & Barbara Kitchenham & Ingunn Myrtveit
2. A Simulation Study of the Model evaluation Criterion MMRE
3. IEEE Trans Software Engineering V29n11(Nov 2003)pp985-996
4. =SIMULATION EMPIRICAL STATISTICS MMRE HARMFUL
5. Provides evidence that software engineers should use traditional goodness of fit statistics rather than inventing their own measures.
Fosteretal91
1. I Foster & C Kesselman & S Taylor
2. Concurrency: Simple Concepts and Powerful Tools
3. Comput Jnl V33n6(Dec 1990)pp501-507. monotonic variables (single assignment)+interleaving+choice+encapsulated sequences => "permit the design of powerful programming tools"
Fouts00
1. Jason W Fouts
2. An "Out-Of-Box" Experience
3. Commun ACM V43n11(Nov 2000)pp28-29
4. =ANECDOTE USER
5. developers shoud take users goals and environment into account, including other software that may
6. be running.
7. Ref to alan cooper
Fowler97
1. Martin Fowler
2. Analysis Patterns: Reusable objects models
3. Addison Wesley Longman MA 1997
4. PATTERNS SYSTEM REALITY OBJECT-ORIENTED
Fowler98
1. Martin Fowler with Kendall Scott...
2. UML Distilled: Applying the standard Object Modeling Language
3. Addison Wesley Longman Inc (9th printing) 1998 ISBN 0-201-32563-2 [ 0-201-32563-2 ]
4. Introduction to UML and OOA/D. Omits much. Adds much. See [Alhir98].
Fowler99
1. Martin Fowler
2. Refactoring
3. Addison-Wesley Longman 1999 ISBN 0-201-48567-2 CR0301-0021
4. =REFERENCE Object-Oriented CODE EVOLUTION
Fowler00
1. Martin Fowler
2. Put Your Process on a Diet
3. Software Development Magazine V8n12(Dec 2000)pp32-36
4. =SURVEY LIGHT METHODS
5. p34: side-bar -- resources -- Crystal, Open source, AD, Scrum, FDD( Feature Driven Development).
6. New methods tend to be adaptive and people-oriented, and minimize the production of untested artifacts.
7. Iterative development handles changing and unknown requirements.
8. New methods may not apply to larger teams.
Fowler01
1. Martin fowler
2. Avoiding Repetition
3. IEEE Software Magazine V18n1(Jan/Feb 2000)pp97-99
4. =EXAMPLE THEORY DESIGN Object-Oriented CODE
5. DRY::="Don't repeat Yourself".
6. (XP)|-"Once and Only Once".
7. "A simple principle that leads to good design".
Fowler01b
1. Martin Fowler
2. Is design... dead?
3. Software Development Magazine V9n4(Apr 2001)pp42-46
4. =ESSAY XP UML
5. Continuous integration, testing, and refactoring enable evolutionary design.
6. documentation is another User Story.
7. UML diagrams as posters when useful.
Fowler01c
1. Martin Fowler
2. Separating User Interface code
3. IEEE Software Magazine V18n2(Mar/Apr 2000)pp96-97
4. =ESSAY MODULES USER REALITY XML SQL HTML
5. p.96: Separate presentation code from domain code.
6. increases maintainability, portability, testing.
7. Problems: VB, Delphi,... don't do this. WEB server pages that contain business logic.
8. HTML vs XML.
Fowler01d
1. Martin Fowler
2. Separating User Interface Code
3. IEEE Software Magazine V18n2(Mar/Apr 2000)pp96-97
4. =ESSAY MODULES USER vs DOMAIN HTML vs XML vs WIMP
Fowler02
1. Martin Fowler
2. Public vs Published Interfaces
3. IEEE Software Magazine V19n2(Mar/Apr 2002)pp18-19
4. =ESSAY INFORMATION HIDING MODULES TECHNICAL
5. Published information has to be frozen because it allows intermodule dependencies.
6. Minimize published.
7. Add rather than change or remove.
8. Strong code ownership in a team creates published interfaces inside the team and inflexible structure.
Fowler03
1. Martin Fowler
2. When to Make a Type
3. IEEE Software Magazine V20n1(Jan/Feb 2003)pp12-13
4. =ESSAY DATA TYPES DESIGN REFACTOR
5. Useful but normally missing types include money, range, dimensions, dates, ... but where to stop.
6. Create a type when it has special behavior, when it communicates intention clearer, when other types have unwanted operations, when the data can be used in many places.
Fowler03b
1. Martin Fowler
2. Errant Architectures
3. Software Development Magazine V11n4(Apr 2003)pp38-41
4. =DEMO NET DISTRIBUTED COMPONENTS PERFORMANCE LATENCY QUALITIES
5. Remote calls take time, traffic, etc.
6. Instead distributing classes, cluster the objects into applications and distribute multiple copies across servers.
7. Use the Remote Facade pattern to hide unneeded remote service calls behind coarse grained classes and objects.
8. Using web services (OAP over XML over HTTP for example) is handy and handle incompatible encoding but is heavy-weight. OO RPC is lightweight and ok when no code translation will be needed.
Fowler03c
1. Martin Fowler
2. Who needs an Architect?
3. IEEE Software Magazine V20n5(Sep/Oct 2003)pp11-13
4. =ESSAY AGILE ARCHITECTURE
5. So what is architecture any way? Things you want to get right early in a project because they are hard to change later.
Fowler03d
1. Martin Fowler
2. Data Access Routines
3. IEEE Software Magazine V20n6(Nov/Dec 2003)pp96-98
4. =DEMO MODULES HIDING ENCAPSULATION getters setters C# Java Ruby In C# can declare a public variable with attached get and set functions that w ork in expressions and assignments.
5. In Java, do not return a collection, return a clone.
6. Or Return a casted version of the data.
7. Or Provide an iterator to avoid exposing a collection of data.
8. Avoid writing accessors to parts of a collection or structure.
9. (dick)|-forgot to mention the Law of Demeter: Don't talk to strangers!
Fowler03e
1. Martin Fowler
2. UML Distilled: A brief Guide to the standard object modeling language
3. Addison-Wesley Longman, Boston MA 2003 ISBN 0321193687 CR 0408-0893
4. =REFERENCE UML2.0
5. Second edition updated to UML 2.0, Previous edn by Fowler and Scott.
Fowler04
1. Martin Fowler
2. Module Assembly
3. IEEE Software Magazine V21n2(Mar/Apr 2004)pp65-67 + Correspendence V21n4(May/Jun 2004)pp8-9
4. =HOWTO MODULES LINKERS DLL dependency injection Object-Oriented
5. 3 ways to select an implementation for a needed module.
  1. use a linker.
  2. dependency_injection::= clients declare dependency and assembler module loads implementation, like? Factories(GoF).
  3. Object-Oriented polymorphism (GoF)
FowlerHighsmith01
1. Martin Fowler & Jim Highsmith
2. The Agile Manifesto
3. Software Development Magazine V9n8(Aug 2001)pp28-32 + letters V9n9(Sep 2001)p12 + V9n10(Oct 2001)pp13+16 + V9n11(Nov 2001)pp13+17
4. =ADVERT PEOPLE > PROCESS & METHODS AGILITY XP SCRUM Crystal
5. manifesto in sidebar on p30 signed by: kent beck, mike bedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C Martin, steve Mellor, Ken Schwaber, Jeff sutherland, & Dave Thomas.
6. "Helpers not tellers"
7. "delivery is not release"
8. Long term agility relies on maintaining technical excellence and good design.
9. "Maximize what is not done"
10. agile_alliance::= See http://www.agileAlliance.org.
11. Agile_Manifesto::paraphrase=following,
  Net
  1. Value individuals and interactions more than process and tools.
  2. Value Working software more than comprehensive documentation.
  3. Value customer collaboration over contract negotiation.
  4. Value responding to change over following a plan.
  5. But -- some value to lesser items above.
  6. Highest priority early, continuous, and long term delivery of currently valuable software.
  7. teamwork, review, support, interaction....
  8. ...
  (End of Net)
FowlerKobryn02
1. Martin Fowler & Cris Kobryn
2. Customizing UML for Fun and Profit
3. Software Development Magazine V10n7(Jul 2002)pp-
4. =DEMO UML TABULAR stereotype metaclass tags constraints
5. A Stereotype is defined as <<stereotype>>ing a <<metaclass>> in the UML meta-model.
6. A Stereotype has a name, zero or more tags (attribute) and zero or more constraints.
7. Use UML class diagram. Use generalization for special kinds of previous stereotypes.
8. Can Use table to list the stereotype, base class, parent, tags, constraints and description.
9. Can use a table to specify tags by stereotype, type, multiplicity and description.
Fox66
1. Fox(Ed)
2. Advances in Programming & Non-Numerical Computation
3. Pergamon Press Oxford UK
4. =SURVEY formal logic
FoxR00
1. Robert Fox
2. Paper Still King
3. Commun ACM V43n11(Nov 2000)p10
4. =NOTE EXPERIMENT PEOPLE READABILITY
5. reading and writing on a computer each and together reduces the comprehension of text. Ohio State U.
FoxFrakes97
1. Christopher Fox & William Frakes
2. The Quality Approach: Is It Delivering
3. Commun ACM V40n6(Jun 1997)pp25-29
4. editorial introduction definitions bibliography and links. QUALITY
Frailey94
1. Dennis J Frailey<frailey@mkcase1.desg.ti.com>
2. Apparent Contradictions in Transfering Technology
3. IEEE Software Engineering Technology Transfer Newsletter V2n3(Winter 1995)pp2-3
  1. similar objectives: customer satisfaction, efficiency, quality, predicatability
  2. means: clear boundaries but not micromanagement
  3. assumptions: educated preactitioners
  4. practice:
  5. (1) extremes and over the edge
  6. (2) apply techniques not know assumptions
  7. Process: overspecify when faced by ignorance, committees to choose the one true method
  8. Empowerment: Freedom but forget the knowledge Conclussions: Few people actually accept their need to continuously learn about things outside the usual context and training.
  9. Arrogance and expertise vs continuous braod education
  10. Pity education is seen as an expensive overhead....
Frailey95
1. Dennis J Frailey<frailey@acm.org>
2. Proving Software Engineering's Legitimacy(Letter)
3. IEEE Software Magazine V12n1(Jan 1995)pp14
  1. journals, topics, organisations, sources of funding (also on Internet?)
Frailey00
1. Dennis J Frailey (ed Larry Constantine)
2. Reducing Cycle Time
3. Software Development Magazine V8n8(Aug 2000)pp80+78-79
4. =EXPERIENCE PROCESS bottlenecks systemic
5. reinvents O&M from 1950s!
6. WIP:="work in process".
7. |-average_cycle_time = WIP / throughput. Little's law?
8. cycles of learning := its faster to have many small iterations or increments because early iterations provide learning to speed later ones.
9. small batch principle: no economies of scale because of requirements creep.
10. smooth flow is more important than local optimization.
FrakesFox95
1. William B Frakes & Christopher J Fox
2. Sixteen questions about Software Reuse
3. Commun ACM V38n6(Jun 1995)pp75-87+112
FrakesFox96
1. William B Frakes & Christopher J Fox
2. Quality Improvement Using a Software Reuse Failure Modes Model
3. IEEE Trans Softw Eng VSE22n4(Apr 1996)pp274-279
4. =THEORY QUALITY IMPROVEMENT REUSE
5. Pareto analysis assuming successful_reuse(p)::=attempt; exists(p); available(p); found(p); understood(p); valid(p); integration(p). Many small chances to fail add up to a large overall chance of failure. SURVEY show mostly no attempt is made to reuse; next the part can not be integrated. encorporate into (plan;do;check;act).
FrakesIsoda94
1. William B Frakes & Sadahiro Isoda
2. Success Factors of Systematic Reuse
3. IEEE Software Magazine V11n5(Sep 1994)pp15-18 Bib p16
4. =EXPERIENCE REUSE
  1. *management
  2. *Measurement
  3. *Economics
  4. *Design for Reuse
  5. *Libraries
    p17: Insufficient reliable data on the benefits and costs of reuse
    p18: Japan's experience: critical factors: senior management, selection of domain, modules systematically derived from the domain, several years effort.
FrakesKang05
1. William B Frakes & Kyo Kang
2. Software Reuse Research: Status and Future
3. IEEE Trans Software Engineering V31n7(Jul 2005)pp529-536
4. =SURVEY =POLL =HISTORY REUSE
FrakesLea94
1. Bill Frakes<frakes@sarvis.cs.vt.edu> & Doug Lea<lea@sunyo.edu>
2. Design for Reuse and Object-Oriented Reuse Methods (Report on working group at WISR'93: 6th Ann Workshop on Sofware Reuse)
3. ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)pp55-56
  1. 3C::=Net{Concept, Content, Context} Key relationships: encapsulated, component, service, client, interface, helper, import spec or contract, Parameterized, generate. 50 design rules(WISR 5?) into taxonomy: 1. Component Structure
  2. identify and encapsulate comonality and variability, Separate interfaces and implementations, separete context and polict from functionallity, link documentation to code, link tests to code, use tools when language are inadequate
    2. Interfaces
  3. minimise |names per name space|, minimize implementation dependance, refine by extending and adding properties, optimize by specializing
    3. Composition
  4. Identify and min (import specs, interference between helpers), use layering, implement policy on top of mechanisim
    4. Parametrization
  5. Use to abstract away contextual variability, Use instanciation to generate components
FrakesTerry94
1. Bill Frakes<frakes@sarvis.cs.vt.edu> & Carol Terry
2. Software Reuse: Metrics and Models
3. ACM Computing Surveys V28n2(Jun 1996)pp415-435
FramlingEtAl07
1. Kary Framling & Timo Ala-Risku & Mikko Karkainen & Ian Holmstrom
2. Design Patterns for managing Product life cycle Information
3. Commun ACM V50n6(Jun 2007)pp75-79
4. =DEMO OBJECT-ORIENTED GoF PATTERNS OBSERVER COMPOSITE WEB/NET AGENTS SOAP JAVA HTML
5. Gof.Observer and GoF.Composite were useful for organizing networks of agents.
France92
1. Robert B France
2. Semantically Extended Data Flow Diagrams: A Formal Specification Tool
3. IEEE Trans SE-18n4(Apr 1992)pp329-346 DFD CR9308-0580(D.2.1)
FranceHorton95
1. Robert B France & Thomas B Horton
2. Applying Domain Analysis and Modeling: An Industrial Experience [SamadzadehZand95] pp206-214
3. =EXPERIENCE REUSE DOMAIN ARCHITECTURE DSSA pagers
Francez86
1. Nissim Francez
2. Fairness
3. Springer Verlag NY NY 1986(Texts & Monographs in Comp Sci). ISBN 0-387-96235-2
4. (UCR) QA76.6.F7226
5. ACM(D.1.3 D.2.4 D.3.1 D.4.1 F.1.2 F.3.1 F.3.3)
6. termination safety liveness temporal logic
FranchCarvallo03
1. Xavier Franch & Juan Pablo Carvallo
2. Using Quality Models in software Package selection
3. IEEE Software Magazine V20n1(Jan/Feb 2003)pp34-41
4. =ADVERT QUALITIES COTS PACKAGES ISO/IEC9126-1
5. Refine ISO/IEC qualities into metrics fro a particular need and evaluate rival packages.
6. Case study: Mail servers.
FrankelWinant97
1. Mike Frankel & Becky Winant
2. Domain Partitioning and Reuse Taxonomy
3. Object Magazine V7n1(Mar 1997)pp38+42-45
4. vocabulary shift indicates domain shift
5. real-world vs technology vs axiomatic
6. object dependancy hierarchy indicates boundaries of reusabillity.
FranceGhoshSongKim03
1. Robert France & Sudipto Ghosh & Eunjee Song & Dae-Kyoo Kim
2. A Meta-modeling approach to pattern-based model refactoring
3. IEEE Software Magazine V20n5(Sep/Oct 2003)pp52-58
4. =DEMO PATTERNS MODEL METAMODEL REFACTOR
5. examples: bridge, observer, abstract factory, GoF Maze Game
6. Metamodel defines a set of source models and target models and the transformation between them.
7. Tool with 2 user interfaces: pattern engineer(metamodel) and application engineer(model)
FranceKimGhoshSong04
1. Robert B France & Dae-Kyoo Kim & Sudipto Ghosh & Eunjee Song
2. A UML-Based Patterns Specification Technique
3. IEEE Trans Software Engineering V30n3(Mar 2004)pp193-206 CR 0503-0328
4. =DEMO SPECIFICATION PATTERN MODEL UML2.0 class sequence diagrams OCL METAMODEL SPS IPS Observer Visitor
5. SPS::="Structural Pattern Specification".
6. IPS::="Interaction Pattern Specification".
7. Patterns specialize the UML metamodel. Create special meta-models defined by UML diagrams. Patterns are used by presenting variants as conforming class diagrams.
8. Ignores UML parameterized collaborations.
9. Experience: used by graduate students, on top of Rational Rose, problem with missing OCL tools.
10. Students able to create specs after two lectures... uncontrolled.
11. Behaviors localized in methods (eg FactoryMethod) needs state machines.
12. UML2.0 sequence diagrams better than UML1.4 -| no need for recursion.
13. Explored domain model: library check-in/check-out
FranceEtal06
1. Robert B France & Sudipto Ghosh & Trung Dinh-Trong & Arnor Solberg
2. Model-Driven Development Using UML 2.0: Promises and Pitfalls
3. IEEE Computer Magazine V39n2(Feb 2006)pp59-66
4. =ESSAY MODELING MDD UML2.0 meta-models semantics
5. MDD::="Model-Driven Development", the next level of abstraction above 3rd generation programming languages.
6. Good survey of UML2.0
7. Interaction modeling hard to extract from the metamodel.
8. Semantics still too loose -- variation points.
9. Need metamodeling tools to enable MDD
Fraseretal91
1. Martin D Fraser & Kuldeep Kumar & Vijay K Vaishnavi
2. Informal and Formal Requirements Specification Languages: Bridging the Gap
3. IEEE Trans SE-V17n5(May 1991)pp454-466
4. synergy
5. acceptance VDM+DFD&SA need to relate discrete flows to VDM variables
Fraseretal94
1. Martin D Fraser & Kuldeep Kumar & Vijay K Vaishnavi
2. Strategies for Incorporating Formal Specifications in Software Develpment
3. Commun ACM V37n10(Oct 1994)pp74-86 CR9509-0705
  1. Page77: defines methods, lists 10: VDM, Z, Larch, FSM, Petri Nets, Temporal Logic, Transition Axioms, CSP, CCS, PAISLEY
  2. Page 78. Lists 9 strategies of use Table 2, page 79: informal vs semi-formal vs formal: definition and examples (JSD as semiformal) Morphological analysis Table 3: Formalization Processes (taxonomy= { direct, transitional={sequential, parallel}}) Table 4: Support: Unassistted vs Computer Assisted Table 5: Table 3 >< Table 4 -> references
    25 refs
FraserLeishmanMcLellan95
1. Steven Fraser & Deborah Leishman & Robert McLellan
2. Patterns, Teams and Domain engineering
3. In [SamadzadehZand95] pp222-224
4. =EXPERIENCE ARCHITECTUR EXPERIENCES
FraserManci08
1. Steven Fraser & Dennis Manci
2. No Silver Bullet: Software Engineering Reloaded
3. IEEE Software Magazine V25n1(Jan/Feb 2008)pp91-94
4. =REPORT OOPSLA PANEL HISTORY STATUS Brookes Werewolf
5. Fred Brookes + David Parnas + Linda Northrop + Aki Namioka + Dave Thomas + Ricardo Lopez + Martin Fowler.
6. Guess who turned into a werewolf!
7. Video on YouTube!
8. All because of [Brooks87]
9. Also see [Cox90a] [Harel92]
FraserVaishnavi97
1. Martin D Fraser & Vijay K Vaishnavi
2. A Formal Specifications Maturity Model
3. Commun ACM V40n12(Dec 1997)pp95-103
Frazier01
1. George F Frazier
2. Cross-Platform coroutine in C++
3. Dr. Dobbs #322(Mar 2001)pp72+74+76+78-80
4. =EXAMPLE NONSEQUENTIAL NT Solaris parsing
Freed95
1. Ken Freed
2. Client/Server Analysis and Design Patterns
3. Software Development Magazine(Jul 1995)pp35-37
4. =IDEAS PEOPLE PATTERNS
5. Refers to Ed Yourdon and others: The big picture nearly always turns on a few critical details: "itterate between the big picture and the implementation details". D A Deards's Lift Method C1972!
Freedman83
1. Roy S Freedman
2. The Common Sense of Object Oriented Languages
3. Computer Design pp111-118
4. structures object-oriented logic
Freeman75
1. Peter Freeman
2. Software Systems Principles - A survey
3. Chicago SRA 1975
Freeman87
1. Peter Freeman
2. A conceptual analysis of the Draco Approach to Constructing Softwre Systems
3. IEEE Trans Soft Eng VSE-13n7(Jul 1987)pp830-844
4. uses SADT to advertise on Nieghbors system and the philosophy of reuse via analyzing famlies of related software and generating specification languages and their tools for the family
Freeman07
1. Peter A Freeman
2. Risks are your Responsibility
3. Commun ACM V50n6(Jun 2007)p104
4. =SERMON RISKS MODELS INCOMPLETE Limited Calculation SIMULATION MODULES ARCHITECTURE
5. When working on a part need to be able to understand the whole -- and we don't have good tools for doing that with software.
FreemanGaudel91
1. Peter A Freeman & Marie-Claude Gaudel
2. Editorial:Building a Foundation for the Future of Software Engineering
3. Commun ACM V34n5(May 1991)pp32-33
FreemanHart04
1. Peter Freeman & David Hart
2. A Science of Design for Software-Intensive
3. Commun ACM V47n8(Aug 2004)pp19-21
4. =ADVERT NSF Science of Design
FreemanL03
1. Lee A. Freeman
2. A refresher in data flow diagramming: an effective aid for analysts
3. Communications of the ACM V46n9 (Sep 2003) pp147-151: Virtual extension
4. Full text Pdf (171JKB) Retrieved Sep 3rd 2003 from [ 903893.903932 ]
5. =EXPERIMENT REQUIREMENTS ANALYSIS DFDs
6. Review CR 0405-0558
7. Reminding novice analysts about the rules of DFDs increased simulated client's satisfaction and the accuracy (as judged by experts) of the DFDs produced
FreemanLewis80
1. ?? Freeman & ?? Lewis
2. Software Engineering
3. Academic Press NY NY 1980
4. =text
Frenkel93
1. Karen Frenkel
2. An Interview with Robin Milner
3. Comm ACM V36n1(Jan 1993)pp90-97
4. =HISTORY LCF ML Objects CCS LANGUAGES
FreimutBriandVollei05
1. Bernrd Freimut & Lionel C Briand & Ferdinand Vollei
2. Determining Inspection cost-effectiveness by combining project data and expert opinion
3. IEEE Trans Software Engineering V31n12(Dec 2005)pp1074-1092
4. =CASESTUDY INSPECTIONS SQA COST VALUE ECONOMICS
5. Inspecting early artifacts had a clear positive value but code inspections may not be as valuable.
6. Involving developers in the inspection tuning process was a good idea.
7. Proposes a complex formula based on Kusumoto's (cost saved - cost consumed)/potential cost of defects.
8. Describes an evaluation process using experts.
9. Interviews: need to evaluate questions in a pilot study.
Freudenbergeretal83
1. Stefan M. Freudenberger & Jacob T. Schwartz & Micha Sharir
2. Experience with the SETL Optimizer
3. ACM TOPLAS V5N1(Jan 1983)pp26-45
4. =EXPERIENCE data optimization Technical
FreyEtal02
1. Peter Frey & Radharamanan Radhakrishnan & Harold W Carter & Philip A Wilsey & Perry Alexander
2. A Formal Specification and Verification Framework for Time-Warp-Based Parallel Simulation
3. IEEE Trans Software Engineering V28n1(Jan 2002)pp58-78
4. =DEMO SPECIFICATION DESIGN VERIFICATION SIMULATIONS PVS
5. PVS: allows conservative extension of theories -- adding a new function and axiom preserves consistency. 67 axioms and 459 theorems spread over 9 theories.
FreydScedrov89
1. Pete J Freyd & Andre Scedrov
2. Categories& Allegories
3. Elsevier Amsterdam Netherlands ISBN0-444-70368-3 QA169.F73
4. allegories are abstracted from binary relations like categories abstracted from functions
5. notation for diagrams: noncommuting (+) + pullbacks + equalizers + products
6. quantification based on making visible the comments(quantiviers and logical connectives) made while drawing the diagram on a blackboard
FriasEtal05
1. Marcello F Frias & Carlos G Lopez Pombo & Gabriel A Baum & Nazareno M Aguirre & Thomas S E Maibaum
2. Reasoning about static and dynamic properties in Alloy: A Purely Relational Approach
3. ACM TOSEM Trans Software Eng & Methodology V14n4(Oct 2005)pp478-526
4. =THEORY EQUATION RELATIONAL LOGIC HOARE TRIPLES FORK ALGEBRA FRL
5. A fork algebra is based on a set that has a pairing operation (p) that is used to define a fork operation on relations:
6. fork::infix=map[R,S] rel[a,d](for some b,c (d=p(b,c) and a R b and a S c)).
FriasEtAl08
1. Marcello F Frias & Carlos G Lopez Pombo & Juan P Galeotti & Nazareno M Aguirre
2. Efficient analysis of DynAlloy Specifications
3. ACM TOSEM Trans Software Eng & Methodology V17n1(Dec 2007)#4pp1..34 CR 0902-0168
4. =DEMO SPEED DynAlloy vs Alloy SPECIFICATION MODEL CHECKING HOARE TRIPLES
5. Instead of traces defines {pre}action{post}.
6. Much faster than Alloy.
FrickEtal00
1. A Frick & G Goos & R Neuman & W Zimmerman
2. Construction of robust class hierarchies
3. Software - Practice & Experience V30n5(May 2000)pp481-543
4. =THEORY OBJECT-ORIENTED TECHNICAL MODULES INHERITANCE DESIGN
5. no one design is robust, flexible and efficient.
6. given priorities and specification then best hierarchy can be generated automatically.
FriedenthalMooreSteiner08
1. Sanford Friedenthal & Alan Moore & Rick Steiner
2. A Practical Guide to SysML: The Systems Modeling Language
3. Morgan Kaufmann(July 24, 2008) ISBN 0-12-374379-6 eISBN 0-08-055836-4 (eBook)
4. =MANUAL SysML SYSTEMS ENGINEERING UML REQUIREMENTS STRUCTURE PARAMETERS FORMULAS
FriedmanTranGoddard95
1. Michael A Friedman & Phong Y Tran & Peter L Goddard
2. Reliability of sofware intensive systems
3. Noyes Publications ParkRidge NJ 1995 $64 ISBN 0-8155-1361-5
4. =HANDBOOK RISKS ANALYSIS
FriesenJahnichenWeber97
1. Viktor Friesen & Stefan Jahnichen & Mathias Weber
2. Specification of Software Controlling a Discrete-Continuous Environment [ICSE'97]
3. REALITY OOA Z with continuous variables. statecharts
Frolund96
1. Svend Fr/olund
2. Coordination distributed objects: An actor-based approach to synchonisation
3. MIT Press Cambridge MA 19996
4. =ADVERT THEORY NON-SEQUENIAL
5. ISBN 0-262-06188-0 CR9803-0117
6. LOS::="Language with Objects and Synchronizers"
Frost07
1. Randall Frost
2. Jazz and the Eclipse Way of Collaboration
3. IEEE Software Magazine V24n6(Nov/Dec 2007)pp114-117
4. =ADVERT ENVIRONMENT TEAMWORK PROCESS BUG BUILD TRACKING
5. Jazz extends on Eclipse to coordinate many programmers.
Fry97
1. Christopher Fry
2. Programming on an Already Full Brain
3. Comm ACM V40n4(Apr 1997)pp55-64
4. graphics TECHNICAL =DEMO LISP
FuBultanSu04
1. Xiang Fu & Tevfic Bultan & Jianwen Su
2. Model Checking XML Manipulating Software
3. Proc ISSTA 2004 & ACM SIGSOFT Software Engineering Notes V29n4(Jun 2004)pp252-262
4. =DEMO SPIN MODEL CHECKER Promela XPath XML WSAT Web services
5. Gives algorithms for translating XML data and XPath expressions into Promela.
FuBultanSu05
1. Xiang Fu & Tevfik Bultan & Jianwen Su
2. Synchronizability of Conversations among Web Services
3. IEEE Trans Software Engineering V31n12(Dec 2005)pp1042-1043
4. =DEMO NONSEQUENTIAL WEB SERVICES VERIFICATION TOOL FSM BPEL LTL WSAT MSC
5. Theory of buffered communicating finite state machines.
6. Verification using Promela and SPIN of existing protocols expressed in BPEL
7. BPEL::XML_document="Business Process Execution Language"
8. (dick)|-`More evidence that businesses use buffered data flows not synchronous message passing`.
FuentesEtal03
1. Jose M Fuentes & Victor Quintana & Juan Llorens & Gonzalo Genova & Ruben Prieto-Diaz
2. Errors in the UML Metamodel?
3. ACM SIGSOFT Software Eng Notes V28n6(Nov 2003)p29 [ 966221.966236 ]
4. =CRITIQUE STANDARD UML METAMODEL SEMANTICS
FuggettaEtal99
1. Alfonso Fuggetta & Luigi Lavazza & Sandro Morasca & Stefano Cinti & Giandomenico Oldano & Elena Orazi
2. Applying GQM in an Industrial Softare Factory
3. ACM ToSEM V7n4(May 1999)pp411-448
4. =EXPERIENCE GQM Digital Italia TOOL Windows95 //ftp.cefriel.it/pub/Settore2/gqm-tool/
5. Cost of GQM is in the planning and was about one person-year.
6. Cost of operating the result was about 2% overhead.
7. Can reuse much of first GQM effort in second one.
8. Payoff: can reduce field testing: high cost low return.
Xxx??
1. Unknown Author
2. Unknown Title
3. Unknown source
4. =LOST
  1. Maintain derived data
  2. Enforce integrity constraints
  3. Triggering external operations
    Semantic primitives and describing what the USER wants to do, not how it will be done by the system.
    ECA: Event-Condition-Action style
    programming-by-invariants.
  4. Constraints::=MATHS(axiom)
  5. Derivation::=MATHS (definition)
    p36: Advantages::= clarity, uniformity, abstraction, data independence, deterministic, ....
  6. Temporal_data_base::= has a historical record
  7. proactive and retroactive processing
  8. state_elment::=value><temporal_extension,
  9. temporal_extension::=Net{commit, decision, valid:Times}
GENI06
1. GENI Planning Group
2. GENI Design Principles
3. IEEE Computer Magazine V39n8(Sep 2006)pp-
4. =ADVERT DESIGN NSF NETWORK RESEARCH SCIENCE
5. GENI::="Global Environment foir Network Innovations", [ http://www.geni.net ]
6. Do not confuse with Sun's Geni network!
Gabriel08
1. Richard P Gabriel
2. Designed as Designer
3. OOPSLA 2008 & SIGPLAN Notices V43n10(Oct 2008)pp617-632
4. =ESSAY DESIGN POETRY WRITING
5. Refs Brookes -- Conceptual Integrity comes from having a single designer.
6. Gives examples of design emerging from collaboration and help.
7. The importance of listening to what the product/design is saying.
8. Design is at least a dialog between Designer and the Designed.
9. Example: That dome in Florence, TS Elliot and E Pound, ...
10. Did not mention Umberto Ecco's "Foucalt's Pendulem" arguing the importance of editors.... (dick).
GalinAvrahami06
1. Daniel Galin & Motti Avrahami
2. Are CMM Program investements Beneficial? Analyzing past studies
3. IEEE Computer Magazine V39n10(Oct 2006)pp81-87
4. =SURVEY CMM EXPERIENCES ROI
5. Significant benefits -- example a 300% median ROI -- for each increase in CMM level.
6. Fewer errors, more predictable processes, less rework, and higher productivity.
Gall79
1. John Gall
2. Systemantics: How Systems work and especially how they fail
3. Fontana/Collins England 1979, NY Times Book Co 1977
4. =ESSAY SYSTEMS FAILURE GUP FLAW ANERGY AXIOM GARBAGE GOAL Goedel
5. Of the 32 intuitively true (or funny) Systems propositions (appendix I, pp85-92) here are some observatios that a relevant for computer people:
  - 5. The Generalized Uncertainty Principle -- (GUP) Systems Display Antics.
  - Proof -- corolary of Goedel's theorem.
  - ...
  - 16. A Complex System Designed From Scratch Never Works and Cannot be patched to make it work. You have to start over, beginning with a working simple system.
  - Programs never run the first time.
  - Complex Programs never run.
  - 15. A complex system that works is invariably found to have evolved from a simple system that works.
  - 13. A simple system, Designed from scratch, sometimes works.
  The Wikipedia entry [ Systemantics ] has a complete list and citation of a newer edition: General Systemantics Press/Liberty, 2003. ISBN 0-9618251-7-0.
Galloway97
1. Patricia Galloway
2. Software Patterns(Letter)
3. Comm ACM V40n1(Jan 1997)p23
4. =CORRESPONDENCE ARCHITECTURE PATTERN
5. Architectural pattern languages are either too vague or too dependent on ephemerra
GambinoJohnsonWilson
1. Gambino & Johnson & Wilson
2. The microcomputer User learning curves
3. Comp World May 31 pp35-42
4. =EXPERIENCE USER dynamics
Gammaetal94
1. Erich Gamma & Richard Helm & Ralph Johnson & John Vlissides
2. Design Patterns: Elements of Reusable Object-Oriented Software
3. Addison-Wesley Reading MA 1994 pp416 $38 ISBN 0-201-63361-2 BNB94-34264 QA76.64.D47 005.1 CR9509-0650
4. =IDEA REUSE OBJECT_ORIENTED
  1. why, solve what, what variants, effects of ignoring.
    
    Reviewed IEEE Softare Magazine by Tom Demarco (May 1995) CR: not casual reading 3 types of pattern: structural, behavorial & creational introduction, case study, catalog(3 chapters), conclusion. each pattern inludes sample code Inside covers have summaries and pointes, ER diagram(!)
Gancarz95
1. Mike Gancarz
2. The UNIX Philosophy
3. Digital Press Newton MA 1995 151 pp. $19.95 ISBN 1-55558-123-4 BNB94-25895 QA76.76.063G365 CR9511-0943
4. =ADVERT UNIX METHOD AGILE
  1. 1. Small is beautiful
  2. 2. Make each program do one thing well
  3. 3. Build a prototype as soon as possible
  4. 4. Choose portability over efficiency
  5. 5. Store numerical data in Flat ASCII files
  6. 6. Use software leverage to your advantage
  7. 7. Use Shell scripts to increase leverage and portabillity
  8. 8. Avoid Captive User Interfaes
  9. 9. Make every program a filter
  10. Plus ten lesser tenets
GaneSarson77
1. Chris Gane & Trish Sarson
2. Structured Systems Analysis
3. IST 1977
4. =HANDBOOK SAD DFD PURPOSE System
GaneSarson79
1. Chris Gane & Trish Sarson
2. Structured Systems Analysis: Tools & Techniques
3. Englewood Cliffs NJ Prentice Hall 1979
4. =HANDBOOK SAD DFD PURPOSE System
5. IRACIS::acronym="Increase Revenue, Avoid Costs, Improve Service".
Ganesan99
1. Ravi Ganesan
2. The messyware advantage
3. Commun ACM V42n11(Nov 1999)pp68-73
4. =ESSAY WWW/NET ECONOMICS Amazon.com
5. Middlemen provide added intangible values like reliabillity & information that are vitally important.
6. a library with 0 catalog& helpful librians is not a library!
Gannonetal87
1. John D Gannon & Richard C Hamlet & Harlan D Mills
2. Theory of Modules
3. IEEE Trans Soft Eng VSE-13n7(Jul 1987)pp820-829
4. =THEORY MODULES PURPOSE
5. denotational/functional semantics of sequential abstractions + trace tables proof
Gannonetal93
1. John D Gannon & Jim Purtilo & Marvin V Zelkovitz
2. Software Specification: A Comparison of Formal Methods
3. Vol 5 in the Computer-Based Information Systems in Organizations Series Ablex Pub Corp 355 Chestnut Street Norwood NJ(201-767-8450 1993/in preparation
Gansneretal88
1. Emden R Gansner & Stephen C North & Kiem-Phong Vo
2. DAG - A Program that draws directed graphs
3. Software - Practice and Experience V17n1( 1988)pp1047-1062
4. =ADVERT GRAPHIC PROGRAM DAG
Gansneretal93
1. Emden R Gansner & Eleftherios Koutsofios & Stephen C North & Kiem-Phong Vo(A T & T Bell Labs)
2. DAG - A Program that draws directed graphs
3. IEEE Trans SE-V19n3(Mar 1993)pp214-230
4. =ADVERT GRAPHIC PROGRAM DAG
  1. dot
  2. network simplex ranking; fewer crossings; position ports; join with spline curves
GanterWille99
1. Bernhard Ganter & Rudolf Wille R
2. Formal concept analysis: Mathematical foundations
3. Springer 1999 QA171.5 G3513 1999
4. =THEORY MATHEMATICAL FORMAL LOGIC LATTICE CONCEPT
5. Given a set of objects X, a set of attributes Y, and a relation R:@(X><Y), then (X,Y,R) is called a formal context. If A is a subset of X then define A'={y:Y. for all x:A(x R y)}. Similarly B'={x:X.for all y:B( x R y)}. A formal concept is a pair (A, B) where A'=B and B'=A, and A is the extent and B the intent of concept (A,B). The subconcept_superconcept relation:(A1,B1) <= (A2,B2) iff A1 is a subset of A2. This defines a lattice of formal concepts.
6. Leads to a diagram showing the underlying structure of the relation R.
7. Given a table X><Y<>-> Z and by defining a scaling Z into (true, false) then a context can be defined.
8. See [ logic_42_Properties_of_Relation.html ] for some rough notes on Concept analysis.
9. Note. Theory has been used to aid the maintenance of software:
  [BojicVelasevic00]
  [DeursenKuipers99]
  [LindigSnelting97]
  [SiffReps99]
  [Snelting96]
  [SneltingTip98]
GantiGehrkeRamakrishnan99
1. Uenkatesh Ganti & Johannes Gehrke & Raghu Ramakrishnan
2. Mining very large databases
3. IEEE Computer Magazine V32n8(Aug 1999)pp38-45
4. =SURVEY DATA mining ALGORITHMS apriori
GansnerNorth00
1. Emden R Gansner & Stephen C North
2. An Open Graph Visualization system and its applications to Software Engineering Software - Practice & Experience V30n11(Sep 2000)pp1203-1233
3. =ADVERT TOOL GRAPH GraphVis VISUAL [ http://www.research.att.com/sw/tools/graphviz/ ]
GaoChenToyoshimaLeung99
1. Jerry Z Gao & Cris Chen & YasuFumi Toyoshima & David K Leung
2. Engineering on the Internet for Global Software Production
3. IEEE Computer Magazine V32n5(May 1999)pp38-47
4. =ADVERT TECHNICAL PROCESS WEB/NET
GaoHayesCai05
1. Hong Tina Gao & Jane Huffman Hayes & Henry Cai
2. Integrating Biological Research through Web Services
3. IEEE Computer Magazine V38n3(Mar 2005)pp26-31
4. =DEMO WEB SERVICES BIOINFORMATICS Drug discovery
5. Combine many remote components to analyze data.
6. Need standards.
7. Helps if people split Model from View.
Garfield78
1. ?? Garfield
2. Essays of an Information Scientist
3. ISI press (2 vols)
4. =ESSAYs graphic
Garfield09
1. Bob Garfield
2. The Chaos Scenario -- Among the ruins of mass media, the choice for business is stark: Listen or Perish
3. Stielstra Publishing USA 2009 [ http://TheCahosScenarion.net ]
4. =BLOG =POLL =EXPERIENCE MASS MARKETING ADVERTISING LISTENING
5. The title says it all...
6. He claims that Top 10 lists are good for blogs and gives the reader the option to publish this list:
7. Listenomics::=following,
  1. Listen to the conversation
  2. Better yet, host the conversation
  3. Off that Community a stake in your enterprise
  4. Practice Jujitsu -- turn you attacker's strength against them
  5. Sneeze in Public
  6. Have a story to tell
  7. What's it in for us? Not you. US!
  8. Behave yourself
  9. Remember Siegfried and Roy. Especially Roy. -- Tigers)
  10. Pray for Serenity -- somethings you can not fix.
  Garber02
  1. Lee Farber(ed)
  2. Taking a Graphical Approach to the Password
  3. IEEE Computer Magazine V35n7(Jun 2002)p19
  4. =IDEAS SECURITY Passwords
  5. Use a sequence of clicks to identify uses: navigating a virtual world or complex scene.
  6. Research Adrian iority: 2 Completed: No Note: at UCB. Map authentication Scheme.
  7. companies: Microsoft, ber02, Real User.
  GarciaLucenaCowan04
  1. Alessandro F Garcia & Carlos J P de Lucena & Donald D Cowan
  2. Agents in Object-Oriented Software Engineering
  3. Software - Practice & Experience V34n5(10 Apr 2004)pp489-521
  4. =EXAMPLE AGENTS OBJECTS ASPECTS AOP
  5. Agents have many concerns: autonomy, adaption, interaction,..... That cut across OO designs and architectures. Therefore use Aspects to handle them.
  GarciaVizcainoEbery11
  1. Felix Garcia & Aurora Vizcaino & Christof Ebery
  2. Process management tools
  3. IEEE Software Magazine V27n6(Mar/Apr 2011)pp15-18
  4. =ADVERT TOOLS MODEL PROCESSES COLLABORATION AUTOMATION PEOPLE OMG SPEM BPMN Eclipse EPFC ARIS Appian BizAgi Intalio RUP UP RMC UMA
  GareyJohnson75
  1. Michael R Garey & David S Johnson
  2. Computers and Intractability: A Guide to the theory of NP-Completeness
  3. Bell Telephone Labs 1979
  4. =THEORY COMPLEXITY INTRACTABILIY PERFORMANCE ALGORITHMS NP-COMPLETE
  5. Includes a catalog of problems that are (probably) without efficient algorithmic solutions.
  Garfinkel05
  1. Simson Garfinkel
  2. Microsoft's Secret Bug Squasher
  3. Wired (Nov 10 2005) [ 0,2924,69375,00.html?tw=wn_tophead_3 ]
  4. =REPORT MS MODEL CHECKING DEVICE DRIVERS TOOL SLAM
  5. So called formal methods -- math & logic -- are used inside Microsoft!
  GarfinkelWeiseStrassman94
  1. Simson Garfinkel & Daniel Weise & Steven Strassmann
  2. The UNIX-Haters Handbook
  3. IDG Books World San Mateo CA 1994 ISBN 1-56884-203-1
  4. =ADVERT NON-UNIX
  5. Compare Gancarz95
  GargantiHeitmeyer99
  1. Angelo Garganti & Constance Heitmeyer
  2. Using Model checking to generate tests from requirements specifications
  3. ESEC/FSE'99 SIGFOFT SE Notes V24n6(Nov 1999)pp146-162
  4. =CASESTUDIES SCR -> TESTING
  GargantiniMorzenti01
  1. Angelo Gargantini & angelo Morzenti Automated Deductive Requirements analysis of Critical systems
  2. ACM TOSEM Trans Software Engineering & Methodology V10n3(Jul 2001)pp255-307
  3. =DEMO FORMAL REQUIREMENTS ANALYSIS SRA LOGIC [TRIO] TD TOOL PVS Non-Zeno
  4. TD:="Time dependent".
  5. TRIO -- see Federer
  6. DUC::="Device under Construction".
  7. events (point based predicates) : true at a single time and not immediately before or after.
  8. interval-Based predicates: if true then true in some before or after interval nearby and if false then false nearby..
  9. left and right closed interval-based predicates and variables. Left continuous interval based (lci) means that predicate has the same value at a given time as it had in a previous neighboring interval.
  10. non-Zeno predicates and variable. Named after Zeno's paradoxes. finite variability. physical meaningful. One can talk about the value immediately before or after the current time.
  11. non_Zeno(A)::=(UpToNow(not A) or UpToNow(A)) and (NowOn(not A) NowOn(A) ),
  12. UpToNow(A)::= t+>for some d1>0, all d2:(0..d1) ( A (t-d2)),
  13. NowOn(A)::= t+>for some d1>0, all d2:(0..d1) ( A (t+d2))
  GarlanChengKompanek02
  1. David Garlan & Shang Cheng & Andrew J Kompanek
  2. Reconciling the needs of architectural description with object-modeling notations
  3. Science of Computer Programming V44n1(Jul 2002)pp23-49
  4. =ESSAY? MODULES ARCHITECTURE UML REAL-TIME
  GarlandGuttagHorning90
  1. Stephen J Garland & John V Guttag & James J Horning
  2. Debugging Larch Shared Language Specifications
  3. IEEE Trans Software Engineering SE-V16n9(Sep 1990)
  4. =EXPERIENCE LARCH SPECIFICATION
  Garlanetal95
  1. Davis Garlan & Robert Allen & John Ockerbloom
  2. Architectual Mismatch: Why Reuse is so Hard
  3. IEEE Software Magazine(Nov 1995)pp17-26
  4. =EXPERIENCES ARCHITECTURE PERFORMANCE
  5. Performance problems and rewriting due to undocumented assumptions about control data and infrastructure
  GarlanPerry95
  1. David Garlan<garlan@cs.cmu.edu> & Dewayne E Perry
  2. (Introduction to the special Issue on Research Directions in) Software Architecture
  3. IEEE Trans on Software Eng VSE-21n4(Apr 1995)|ACM Computing Surveys V27n2(June 1995)pp257-261
  4. =EDITORIAL ARCHITECTURE
  5. Contains [GriswoldNotkin95] [DeanCordy95] [Shawetal95] [Luckhametal95] [Moriconietal95] [InverardiWolf95]
  GarmusHerron95
  1. David Garmus & David Herron
  2. Measuring the Software Process: A Practitcal Guide to Functional Measurement
  3. Prentice Hall PTR 1996 ISBN 0-13-349002-5 $41.00
  4. =HANDBOOK PROCESS METRICS Function Points
  5. reviewed ***1/2 Software Development Magazine (Jul 1996)pp67-68
  GarmusHerron96
  1. David Garmus & David Herron
  2. Effective Early Estimation
  3. Software Development Magazine (Jul 1996)pp57+58+59+60+62+65
  4. =ADVERT METRICS BOOK
  5. Metrics(function points+feature points+3D+Bang+MakII) advert for book [GarmusHerron95]
  GarotEtal87
  1. Jean-Marc Garot & Dlebert Weathers & Thomas Hawker
  2. Evaluating Proposed Architectures for the FAA's Advanced Automation System
  3. IEEE Computer Magazine V20n2 (Feb 1987)pp
  4. =EXPERIENCE FAA AAS ARCHITECTURE
  GarrettDanziger07
  1. R Kelly Garrett & James N Danziger
  2. IM = Interuption Management? Instant Messaging and disrutption in the workplace
  3. Journal of Computer-Mediated Communication, V13n1(2007)article 2. [ garrett.html ]
  4. =SURVEY USER SMS
  5. Evidence that IM leads to less interupted work than phone calls.
  GarzasPiatini05
  1. Javier Garzas & Mario Piatini
  2. An Ontology for Microarchitectural Design Knowledge
  3. IEEE Software Magazine V22n2(Mar/Apr 2005)pp28-33
  4. =IDEA ORGANIZE DESIGN KNOWLEDGE ONTOLOGY
  5. Distinguishes and relates rules: Principle, heuristic, best practice,bad smell, refactoring, and pattern.
  GarzottoPaoliniSchwabe93
  1. F Garzotto & P Paolini & D Schwabe
  2. HDM - A model Based Approach to Hypermedia Application Design
  3. ACM Trans Inf Sys V11n1(Jan 1993)pp1-26
  4. =ADVERT WEB HYPE HDM
  Gathier82
  1. Gathier
  2. Left Handed Functions
  3. SIGPLAN V17n3 (Mar 1982)pp12-13
  4. =IDEA non-sequential
  Gause05
  1. Donald G Gause
  2. Why Context Matters - and What can we do about it?
  3. IEEE Software Magazine V22n5(Sep/Oct 2005)pp13-15
  4. =ADVERT REQUIREMENTS Context Scope
  GauseWienberg89
  1. Donald C Gause and Gerald M Weinberg
  2. Exploring requirements: quality before design
  3. Dorset House Publishing 1989. ISBN 0-932633-13-7
  4. =HANDBOOK REQUIREMENTS
  GavalasEconomou11
  1. Damianos Gavalas & Daphne Economou
  2. Development platforms for mobile applications: status and trends
  3. IEEE Software Magazine V27n6(Jan/Feb 2011)pp77-86
  4. =CASE STUDY =POLL MOBILE PLATFORMS JAVA .NET VB CLR FLASH ANDROID DALVIK DEX
  5. Ignores Apple iOS iP* platform with Objective-C and Xcode.
  GayBaptyNeemaTuck01
  1. Jeff Gray & Ted Bapty & Sandeep Neema & James Tuck
  2. Handling crosscutting constraints in domain-specific modeling
  3. Commun ACM V44n10(Oct 2001)pp47-93 + letters Commun ACM V45n2(Mar 2002)pp11-12
  4. =EXPERIENCE DOMAIN ARCHITECTURE ASPECT ISIS OCL ECL XML TOOL weaving
  5. Expressing constraints as part of a domain model is complex and repetitive. Express them as separate aspects and provide a tool to distribute constraints to where they apply.
  Geer03
  1. David Geer
  2. Federated Approach expands Database-Access Technology
  3. IEEE Computer Magazine V36n5(May 2003)pp18-20
  4. =ADVERT LEGACY DATA INTEGRATION XML
  Geer03b
  1. David Geer
  2. Taking steps to secure web services
  3. IEEE Computer Magazine V36n10(Oct 2003)pp14-16
  4. =STANDARDS WEB/NET SECURITY SAML WS-SEC SSl TLS SOAP XML
  5. SAML::="Security assertion Markup Language", asserts rules for authentication, attributes, and authorization, [ http://www.oasis-open.org/ ] (OASIS).
  6. WS-SEC::="Web Services security protocol", encryption, signatures, etc. [ wss ] (IBM, Microsoft, Verisign).
  Geer06
  1. David Geer
  2. Will Software Developers Ride Ruby on Rails to success
  3. IEEE Computer Magazine V39n2(Feb 2006)pp18-20
  4. =ESSAY Ruby Rails MVC WWW DATA platform
  5. Ruby::scripting_language.
  6. Rails::framework=supports data base access and MVC GUIs, Define controllers, views, ...
  7. Uses the DRY: Don't Repeat Yourself principle.
  Geer08
  1. David Geer
  2. To Boost Adoption IPv6 Proponents Back Once-Shunned Technology
  3. IEEE Computer Magazine V41n10(Oct 2008)pp16-19
  4. =EXAMPLE TECHNOLOGY CHANGE IETF INTERNET PROTOCOL
  5. IPv6 (128 bit +authenticating and encrypted packets) may be better than IPv4 (32 bit). No need for DHCP with IPv6.
  6. But it is not being adopted.
  7. So standards body is allowing an new architecture using network-address Translation (NAT). Uses dual-stack routers.
  8. (dick)|-network externalities strike again. Converse of the inventors dilemma.
  Geer10
  1. David Geer
  2. Are companies actually using secure development life cycles
  3. IEEE Computer Magazine V43n6(Jun 2010)pp12-15
  4. =POLL SECURITY METHODS PROCESSES SDLs SDL-agile SAMM BSIMM SSDL CLASP
  5. Security has to be part of the development of software from the get go -- it can not be added later.
  6. Can use static analysis to catch holes in code. Most security holes are design holes. Commonly letting in unexpected attacks.
  7. Need to analyze and model threats.
  8. Survey by Errata.
  9. 81% were aware but only 39% are using a "formal methodology".
  10. Reasons not used include time, no need, cost, ...
  GeethaSubramanian90
  1. T V Geetha & R K Subramanian
  2. Representing Natural Language with Prolog
  3. IEEE Software V7n2 pp85-92
  4. =ADVERT DDD LOGIC PROLOG LANGUAGE NLP
  Geier96
  1. Jim Geier
  2. Don't get Mad: Get JAD
  3. Software Development Magazine(Mar 1996)pp53-55
  4. =ADVERT REQUIREMENTS USER PEOPLE stake-holders
  5. needs planning and good facilitator skills
  GelbardTeeniSadeh09
  1. Roy Gelbard & Dov Te'eni & Matti Sadeh
  2. Object-oriented Analysis -- is it just a theory
  3. IEEE Software Magazine V27n1(Jan/Feb 2010)p64-71
  4. =POLL 54 PROJECTS UML DFDs flowcharts OOA ANALYSIS DESIGN CODE
  5. Most classes are identified during design & code.
  6. diagram types: (most used) class(ERD), package, activity, flow, sequence, state, collaboration, DFD, use case(least used). Component& deployment not used.
  7. Text always used, mostly with diagram. Diagrams are not enough.
  8. 80% used one iteration.
  9. Clients do not get oo diagrams.
  10. CASE tools don't speed up understanding and explaining.
  11. Missing: user interface, business process, ... OO models.
  12. Suggest that less is more.
  13. Notes use of OOA depends on policy, costs, and benefits.
  14. Minimize Costs: focus on organisational relationships, interactions, data items, and user experiences.
  15. Maximize Benefits: use psychology and sociology to analyse needs.
  Gelernter91
  1. David Gelernter
  2. Mirror Worlds: or the day software puts the universe in a shoebox...how it will happen and what it will mean
  3. Oxford U Press Oxford UK & NY NY 1991 CR9306-0374 QA76.754 G45 ISBN 0-19-506812-2 BNB 91-19178 Dewey 005
  4. =IDEA REALITY NET
  Gelernter95
  1. David Gelernter
  2. The Muse in the Machine: Computerizing the Poetry of Human Thought
  3. FreePress NY NY 1993
  4. =IDEA
  GencelDemirrors08
  1. Cigdem Gencel & Onur Demirrors
  2. Functional Size Measurement Revisited
  3. ACM TOSEM Trans Software Eng & Methodology V17n3(Apr 2008)#15pp1-36 CR 0908-0763
  4. =EMPIRICAL PURPOSE METRIC SIZE ESTIMATE IMPROVEMENT FFP FUNCTION POINTS COSMIC
  5. Measuring and predicting size is important for project management...
  6. More work is needed.
  GennariAltmanMusen95
  1. John H Genari & Russ B Altmman & Mark A Musen
  2. Reuse with Protege-II: From Elevators to Ribosomes
    [SamadzadehZand95] pp72-80
  3. =EXPERIENCE REUSE
  GenuchtenEtal01
  1. Michiel van Genuchten & Cor van Dijk & Henk Scholten & Doug Vogel
  2. Using Group Support Systems for Software Inspections
  3. IEEE Software Magazine V18n3(May/June 2001)pp60-65
  4. =EXPERIENCE V&V SQA INSPECTION TOOL
  5. GSS::="Group Support System".
  6. GSS improves inspections as long as the process is maintained.
  Genuchten91
  1. Michiel van Genuchten
  2. Why is Software Late? An Empirical Study of Reasons For Delay in Software Development
  3. IEEE Trans SE v17n6(Jun 1991)pp582-590 CR9210-0796
  4. =EXPERIENCE PROCESS DELAYS
  Gerhart89
  1. Susan Gerhart
  2. Formal Methodists Warn of Software Disasters (report on Formal Methods 89 Conference)
  3. IEEE Software v6 n6(Nov 1989)p77&83
  4. =ADVERT RISKS vs FORMAL
  Gerhart90
  1. Susan L Gerhart(Guest Ed)
  2. Applications of Formal Methods: Developing Virtuoso Software
  3. IEEE Software V7n5(sep 1990)
  4. =ADVERT FORMAL
  GerhartCraigenRalston94
  1. Susan Gerhart & Dan Craigen & Ted Ralson
  2. Experience with Formal Methods in Critical Systems
  3. IEEE Software magazine v11n1(Jan 1994)pp21-28 CR9601-0044
  4. =EXPERIENCE FORMAL [Craigenetal95]
    1. Formal methods more useful at front than for code
    2. Tend to improve things
    3. refinement not cost effective
      p27:"Mathematics involved in most formal methods is elementary, so the greater challenge may lie in teaching users how to model systems properly and carry design through."
      p28: primarily used for
    4. Assurance, Domain Analysis, Communication, Evidence of best practice, Re-Engineering
  GermainRobillard05
  1. Eric Germain & Pierre N. Robillard
  2. Engineering-based processes and agile methodologies for software development: a comparative case study
  3. J. Systems & Software V75n1-2(15 Feb 2005)pp17-27 CR 0602-0171 [ science?_ob=JournalURL&_cdi=5651&_auth=y&_acct=C000059573&_version=1&_urlVersion=0&_userid=521812&md5=851cb8e7e96cf9a729dcab38f42f8044 ]
  4. =EXPERIMENT EFFORT COGNITIVE XP vs UPEDU RUP
  5. Total effort similar with a high ceremony and a low ceremony process.
  6. Teams drawing diagrams did said they didn't help.
  7. Drawing diagrams does not resolve risks of an unknown technology.
  8. Teams forced to code early learned new technology and taught the other teams whaen they needed it (later).
  GershonPage01
  1. Nahun Gershon & Ward Page
  2. What Storytelling can do for Information visualization
  3. Commun ACM V44n8(Aug 2001)pp31-37
  4. =DEMO =ESSAY THEORY DATA VISUALIZATION COMICS
  5. Demonstrates that a 3 sentence story implies 20 distinct probable facts.
  6. (above, dick)|-user stories are better than more traditional lists of requirements.
  7. p36: start presentations with a story not a bulletted list!
  GervasiNuseibeh02
  1. Vincenzo Gervasi & Bashar Nuseibeh
  2. Lightweight validation of natural language requirements
  3. Software - Practice & Experience V32n2(Feb 2002)pp113-133
  4. =CASESTUDY LITE FORMAL V&V REQUIREMENTS LOGIC NASA
  5. Shows how lightweight formalism can find errors in natural language specifications.
  6. This is easy and not expensive, and finds subtle errors.
  GhezziJazayeriMandrioli91
  1. Carlo Ghezzi & Mehdi Jazayeri & Dino Mandrioli
  2. Fundamentals of Software Engineering
  3. Prentice-Hall Inc Englewood Cliffs NJ 1991
  4. CR9207-0440
  5. =TEXTBOOK SOFTWARE ENGINEERING
  GiannakopoulouMagee03
  1. Dimitra Giannakopoulou & Jeff Magee
  2. Fluent Model Checking for Event-based systems
  3. FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp257-266
  4. =THEORY TOOL TEMPORAL LOGIC V&V LTS LTL FLUENT FLTL LTSA Buchi
  5. A fluent is a property of states defined by events at the start and end. Example TUNING starts when the tuner is turned on and ceases when the device is tuned in.
  6. Syntax: <start_set, end_set> initially (true|false).
  7. Define shorthand for fluents for single actions/sets of actions: <S, All~S>initially false.
  Gibbs06
  1. R Dennis Gibbs
  2. Project Management with the IBM Rational Unified Process: Lessons from the Trenches
  3. IBM Press 2006 CR 0712-1204
  4. =ADVERT RUP GLOBAL DISTRIBUTED OUTSOURCE
  5. Need for extra work on requirements and prototypes before committing to project.
  Gibbsetal90
  1. Simon Gibbs & Dennis Tsichritzis & Eduardo Casais & Oscar Nierstrasz & Xavier Pintado
  2. Class Management for Software Communities
  3. Commun ACM V33n9(Sep 1990)pp90-103.
  4. =TOOLS OBJECT-ORIENTED
  Giddings84
  1. R V Giddings
  2. Accommodating Uncertainty in Software Design
  3. Commun ACM v27n5(May 1984)p428
  4. =IDEA lifecycle non-sequential DOMAIN dependence
  5. Early example of process diversity and the One Size doesn't fit argument.
  GieseEtAl03
  1. Holger Giese & Mathias Tichy & Sven Burmester & Wilhelm Schafer & Stephen Flake
  2. Toward the Compositional Verification of Real-Time UML Designs
  3. FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp38-47
  4. =THEORY UML Patterns UML/RT statecharts fsm raven RT-OCL Assume/guarantee
  Gigler08
  1. Tom Gigler
  2. Moops: A Web Implementation of the Personal Software Process Reporting System
  3. =DEMO TOOL PSP AUTOMATION PROCESS WEB/NET OPEN SOURCE PHP/MySQL CSCI655
  4. CSUSB MS Project (May 2008)
  GilDeelmanEtAl07
  1. Yolanda Gil & Ewa Deelman & Marc Ellisman & Thomas Fahringer & Geoffrey Fox & Dennis Gannon & Carole Goble & Miron Livny & Luc Moreau & Jim Myers
  2. Examining the challenges of Scientific Workflows
  3. IEEE Computer Magazine V40n12(Dec 2007)pp24-32
  4. =REPORT CONFERENCE NSF DATA PROCESS DFD MODELS SCIENCE
  Gilb
  1. Tom Gilb
  2. Design by Objectives: a structured system Architecture Approach
  3. (unpublished manuscript (?))
  4. =IDEA QUALITY [ParikhZvintzov82] [Gilbert83]
  Gilb77
  1. Tom Gilb
  2. Software Metrics
  3. Winthrop 77
  4. =IDEA METRICS GOALS REQUIREMENTS ARCHITECTURE Mecca
  Gilb88
  1. Tom Gilb
  2. Principles of Software Engineeering Management
  3. Addison-Wesley Redwood City CA 1988
  4. =TEXT MANAGEMENT EVOLUTION
  Gilb96
  1. Tom Gilb(gilb@acm.org)
  2. Level 6: Why we Can't Get There From Here
  3. IEEE Software Magazine V13n1(Jan 1996)pp97-98+103
  4. =ADVERT QUALITY evolutionary delivery engineering Softcrafters
  Gilb05
  1. Tom Gilb
  2. Competitive Engineering
  3. Elsevier 2005 ISBN 0-7506-6507-6
  4. =UNREAD HANDBOOK EXPERIENCES REQUIREMENTS SPECIFICATION
  5. Reviewed (wonderful contribution) in
  6. ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)p28
  7. by Larry Bernstein
  GilbGraham93
  1. Tom Gilb & Dorothy Graham
  2. Software Inspections
  3. Addison-Wesley Redwood City CA 1993 ISBN 0-201-63181-4 [GilbGraham94]
  GilbGraham94
  1. Tom Gilb & Dorothy Graham
  2. Software Inspections
  3. Interviewed IEEE Software magazine v11n1(Jan 1994)pp104-105
  GilbWeinberg77
  1. Tom Gilb & Gerry Weinberg
  2. Humanized input
  3. Winthrop Inc Cambridge Ma 1977
  4. =EXPERIENCE USER
  Gilbert83
  1. ?? Gilbert
  2. Software design & development
  3. SRA Chicago 1983
  4. =text PURPOSE QUALITY
  Gillenson87
  1. Mark L Gillenson
  2. The Duality of database structures and design techniques
  3. Commun ACM V20n12(Dec 1987)pp1058-1065
  4. technical design data
  Gillibrand00
  1. David Gillibrand
  2. Essential Business Object Design
  3. Commun ACM V43n2(Feb 2000)pp117-119
  4. =EXAMPLE =ADVERT METHOD JSD ELH ERD DAD OBJECT-ORIENTED
  5. Delegate event to the most suitable class to handle the behavior
  6. May have to model ephemeral classes not needed in JSD
  GilmoreHillstonRibaudo01
  1. Stephen Gilmore & Jane Hillston & Marina Ribaudo
  2. An Efficient Algorithm for Aggregating PEPA Models
  3. IEEE Trans Software Engineering V27n5(May 2001)pp449-464
  4. =TYPE PERFORMANCE MODEL MATHEMATICS SYNTAX SEMANTICS
  5. PEPA::="Performance Evaluation Process Algebra". Kind of Markovian process algebra. CCS based on labelled exponentially distributed random processes.
  6. algebra use prefix, choice, cooperation, hiding and defined constants.
  GilmoreHillstonKloulRibaudo04
  1. Stephen Gilmore & Jane Hillston & Leila Kloul & Marina Ribaudo
  2. Software performance modelling using PEPA nets
  3. WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp13-23
  4. =DEMO TOOL performance PETRI ALGEBRA PEPA [CanevetGilmoreHillstonKloulStevens04]
  5. PEPA_net::=colored_Petri_net with tokens=PEPA_algebra.components.
  6. PEPA_algebra::stochastic_process_algebra, [Hillston95] [GilmoreHillstonRibaudo01].
  GilmoreTsiknis93
  1. Paul C Gilmore & George K Tsiknis(UBC)
  2. A Logic for Category Theory
  3. Theor Comput Sci V111n1-2(Apr 1993)pp211-252
  4. CR9409-0647
  Gilula9X
  1. Mikhail Gilula
  2. The Set Model for Database and Information Systems
  3. ACM Press 1994/5
  4. ACM Order#706942
  Ginac00
  1. Frank P Ginac
  2. Creating High Performance Software Development Teams
  3. Prentice Hall 2000
  4. =EXPERIENCE PEOPLE PROCESS
  Gladden82
  1. G R Gladden
  2. Stop the Life-Cycle: I Want to Get Off
  3. ACM SIGSOFT Software Engineering Notes V7n3(Apr 1982)pp35-39 [ 1005937.1005945 ]
  4. =HARMFUL SDLC Scenarios Agile Hollywood Prototypes Mockup
  5. Objectives first, mock ups second.
  6. System requirements and design obscure the real system!
  7. Fiascos occur mainly because of
    1. non-existant, vague, incomplete, ... requirements.
    2. Changing requirements effect everything and occur after sytem work is in progress.
    3. The traditional lifeccycle gives slow feedback from designers to stakeholders.
  GlaserFuTumelty04
  1. Alan Glaser & Snow Fu & Mark Tumelty
  2. Growing a participatory programing Environment
  3. Commun ACM V47n6(Jun 2004)pp27-29
  4. =ANECDOTE PEOPLE TEAMS Merck
  5. 3 good things: teamness, leadership, quality.
  6. Customized candid 2day workshop communicated to management, who fixed things.
  7. Small teams design solution to a special technical problem. Share & critique. 0 managers, please!
  GlaserHartelGarratt00
  1. Hugh Glaser & Pieter H Hartel & Paul W Garratt
  2. Programming by Numbers: A Programming Method for Novices
  3. Computer Journal V43n4( 2000)pp254-265
  4. =EXPERIMENT METHOD FUNCTIONAL PURPOSE ML JAVA
  5. strict sequential method for simple recursive functions and classes. Compare HOS? Use in CSUSB CSCI320?
  6. Programming_by_numbers::=( Name the function; write down its type; enumerate all cases; list the ingredients; deal with simple cases; deal with complex cases; Think about the result ).
  Glass94a
  1. Robert L Glass
  2. From Wonderland to the Real Problem
  3. IEEE Software magazine v11n3(May 1994)pp90-92
  Glass94b
  1. Robert L Glass
  2. The Software-Research Crisis
  3. IEEE Software Magazine V11n6(Nov 1994)pp42-47
    1. scientific, engineering, empirical, analytical.
      Inheritted from pure vs applied maths: a disdain for the practical. Costs of trying new ideas out by academics
      p46: "no one stepped back to reanalyse the field's approaches to it to see that a new model was needed."
      Praises the government sponsored consortium of academe and industry at the software engineering laboratory. Ignores similar project carried out earlier with Oxford, IBM and HMG UK on applying forml methods. p46: "A researcher working alongside a practitioner, being open to adjusting and improving ideas"
      Notes need to "...getting rid of the schedule-driven approach to building software..."
      "a new research idea would by analysed by researcher after researcher, advocated thoroughly, and never used in practice."
      p46-47: quotes Fentonetal94 attak on "Formal Methods". See also DavisA94a, Fentonetal94, Glass94a
  Glass95
  1. Robert L Glass(Computing Trends)
  2. In the Year 2020: In Search of Self-Belief: The "BOP" Phenomenon
  3. IEEE Computer V28n1(Jan 1995)pp3537
  Glass95b
  1. Robert L Glass(Computer Trends)
  2. Software Creativity
  3. Prentice Hall Upper Saddle River NJ 1905 $30.67 ISBN 0-13-147364-6 CR9511-0858
  4. reviewed IEEE Software Magazine V13N3(May 1996)p111
  Glass96
  1. Robert L Glass(Computer Trends)
  2. Formal methods are a surrogate for a more serious software concern
  3. IEEE Computer Magazine V29N4(Apr 1996}p19
  Glass98
  1. Robert L Glass
  2. Reuse: What's Wrong with this Picture
  3. IEEE Software Magazine V15n2(Mar/Apr 1998)pp57-59
  4. =HISTORY REUSE
  5. "Bending software is that difficult; modification can be harder than building anew"
  Glass98a
  1. Robert L Glass
  2. Success? Failure? or Both?
  3. IEEE Computer Magazine V31n5(May 1998)p103(Open Channel)
  4. SCR SCIENCE ENGINEERING
  5. SCR was successful science but failed engineering project because no finished product but some some new ideas
  Glass99
  1. Robert L Glass
  2. Computing Calamities: Lessons Learned from products, Projects, and companies that failed
  3. Prentice Hall PTR Upper Saddle River NJ 1999 ISBN 0-13-082862-9
  4. =AUTOPSES PEOPLE RISKS
  Glass99a
  1. Robert L Glass
  2. Realities of Software Technology Payoffs
  3. Commun ACM V42n2(Feb 1999)pp74-79
  4. =SURVEY looking for evaluations of benefits show no numbers for SP+OOP and wide ranges for 4GL+Case+CMM
  5. Rigorous inspection (CLEANROOM) has the most supporting data for a significant payoff
  Glass99b
  1. Robert L Glass
  2. A Snapshot of Systems Development Practice
  3. IEEE Software Magazine V16n3(May/Jun 1999)pp112+110-111
  4. =POLL 78 IS practioners (3% response rate)
  5. 78% 4GL, 67% start with feasibility, 64% prototyping, 62% code inspections/walkthroughs, 60% GUI builders, 60% project management tools, 58% postmortems, 58% life-cycle methodology
  6. Loss of interest in CASE, metrics, JAD.
  Glass99c
  1. Robert L Glass
  2. Evolving a new theory of Project success
  3. Commun ACM V42n11(Nov 1999)pp17-19
  4. =REFERS Kurt R Linberg00 Jnl o Sys&Software
  5. developers don't feel they've failed it management screws up a project!
  Glass00
  1. Robert L Glass
  2. Process Diversity and a computing old wives'/husbands' tale
  3. IEEE Software Magazine V17n3(Jul/Aug 2000)pp128+127
  4. =HISTORY MULTIPLE METHODS
  5. one size does not fit all. ad hoc. eclectic
  6. Factors: domain + size + criticality + innovativeness
  Glass01
  1. Robert L Glass
  2. An Embarrassing, Yet Rewarding, Ending to a Previous Column
  3. Commun ACM V44n1(Jan 2001)pp11-13
  4. =ANECDOTE QUALITY vs SCHEDULE PROCESS CMM
  5. Software Engineering Ideas increased code quality but it took personnel and time to do it. This can be reversed. See Glass (Dec 98).
  Glass01a
  1. Robert L Glass
  2. Of Model changeovers, style, and Fatware
  3. Commun ACM V44n9(Sep 2001)pp17-18
  4. =ARTICLE MASS-MARKET SOFTWARE driven by FASHION FEATURES
  Glass01b
  1. Robert L Glass
  2. A story about the Creativity Involved in software work
  3. IEEE Software Magazine V18n5(Sep/Oct 2001)pp96-97
  4. =ANECDOTE CLERICAL VS INTELLECTUAL
  5. 80% of activity in software development is intellectual (and difficult) and the rest clerical(and easy) -- based on analysing videotapes.
  6. Hard to distinguish creativity form non-creative activities. But 6..29% of tasks depend on creativity.
  Glass02a
  1. Robert L Glass
  2. In Search of Meaning (A tale of two Words)
  3. IEEE Software Magazine V19n4(Jul/Aug 2002)pp136+134-135
  4. =ESSAY SEMANTICS
  5. "ad hoc"::="fitting to this problem".
  6. heuristic::="a rule of thumb".
  7. Note: but we tend to confuse "ad hoc" with messy and "heuristic" with trial-and-error.
  Glass03a
  1. Robert L Glass
  2. Questioning the Software Engineering Unquestionables
  3. IEEE Software Magazine V20n3(May/Jun 2003)pp120+199
  4. =REVIEW XP ONE-SIZE METHODS TOOLS McBreen03
  5. The importance of negative criticism of new ideas in Software engineering methodology.
  6. One size does not fit all.
  Glass03b
  1. Robert Glass
  2. A socio-political look at Open source
  3. Commun ACM V46n11(Nov 2003)pp21-23
  4. =ANECDOTE PEOPLE OPEN SOURCE
  5. Hierarchy of open source developers: readers, contributors, product gurus, and methodology gurus.
  6. Continuing costs of forking: creating your own version of an open source product.
  7. Claims: open source best for systems programs -- programmers = users.
  8. Notes the Utopian fervor of unidentified advocates.
  9. Claims governments are being petitioned to (1) only allow open source, and (2) always forbid open source.
  Glass04a
  1. Robert Glass
  2. Matching Methodology to problem domain
  3. Commun ACM V47n5(May 2004)pp19-21 + Correspondence V47n8(Aug 2004)
  4. =ADVERT ONESIZE METHODS
  5. Correspondence notes that Glass doesn't mention MAJackson's work on matching methods to problems: JSP JSD Problem Frames.
  Glass04b
  1. Robert Glass
  2. The Mystery of Formal Methods Disuse
  3. Commun ACM V47n8(Aug 2004)pp15-17
  4. =POLEMIC FORMAL METHODS
  5. Criticizes [Wordsworth99] for threatening to sneak formal methods into practice.
  6. Agrees that formal methods are not taught or taken seriously.
  7. Suggests that customers don't want "vague" requirements so much as have a need to keep them flexible to cover "problem evolution".
  Glass04c
  1. Robert W Glass
  2. Is This a Revolutionary Idea, or Not?
  3. Commun ACM V47n11(Nov 2004)pp23-25
  4. =ADVERT Dromey IDEA REQUIREMENTS as COMPONENTS
  GlassVessey95
  1. Robert L Glass & Iris Vessey
  2. Contemporary application Domain Taxonomies
  3. IEEE Software Magazine V12n4(July 1995)pp63-76 [VesseyGlass98]
    1. Suggests we don't need theories for all possible problems (which will be weak) but strong ones for for particular domains.
    2. Argues for application tasonomies, as distinct from solution taxonomies.
    3. Survey and critique of several taxonomies. notes confusions.
    4. Provides a meta taxonomy.
    5. States it is going to take a lot of work.
    6. Ref to [Jackson95]
  Glass05
  1. Robert L Glass
  2. IT Failure Rates -- 79% or 10..15%
  3. IEEE Software Magazine V22n3(May/Jun 2005)pp112+110-111
  4. =SURVEY Standish considered harmful
  5. Evidence that the 70% failure rate is mythical. Invites Standish to respond.
  Glass05b
  1. Robert L Glass
  2. "Silver Bullet" milestones in Software History
  3. Commun ACM V48n8(Aug 2005)pp15-18
  4. =HISTORY LANGUAGES MODULES OPERATING SYSTEMS ACADEMIC METHODS CASE TOOLS Object-Oriented agile open source
  Glass06
  1. Robert L Glass
  2. Software Conflict 2.0: The art and science of Software Engineering
  3. Developer.* Books Atlanta GA 2006 ISBN 0977213307 CR 0804-0319
  4. =UNREAD =ESSAYs PRACTICE THEORY
  5. Notes [click here if you can fill this hole]
  Glass07
  1. Robert L Glass
  2. A Deja-Vu Look at Software EngineeringResearchers who care about Practice
  3. Commun ACM V50n8(Aug 2007)pp21-23
  4. =HISTORY RESEARCH MCC SEI SPC Fraunhofer NICTA Simula
  5. 3 labs used to do "practice-based research". MCC closed. SEI moved to advocacy for CMM etc.. SPC is now "Software and Systems Consortium".
  6. Fraunhofer has two centers: IESE and FC-MD focused on SE.
  7. NICTA (Australia) and Simula(Norway) have a group for empirical SE research.
  8. Glass compares missions, staffing, and techniques.
  9. All are looking at proceses, and 2/3 studying Risk, architecture, and measurement.
  10. NICTA includes measurement under process and risk under requirements. [ http://nicta.com.au/ ]
  11. Simula focusses on Object-Oriented AD and use cases in requirements, ... Estimating costs, ... [ http://simula.no/ ]
  12. Fraunhoffer: product lines under architecture, ... Clearing house [ http://iese.fraunhofer.de/ ]
  Glass07a
  1. Robert L Glass
  2. A Research project with important practitioner-oriented findings
  3. Commun ACM V50n11(Nov 2007)pp15-16
  4. =REPORT EXPERIMENT STANDARD ISO/IEC 9126 QUALITIES DESIGN METRICS
  5. H Al-Kilidar & K Cox & B Kitchenham, The use and usefulness of the ISO/IEC 9126 standard, Proc ISESE 2005 conference.
  6. The standard was ambiguous and not easy to use (by student teams).
  Glass08
  1. Robert L Glass
  2. On the impurity of the English language
  3. IEEE Software Magazine V25n2(Mar/Apr 2008)pp96+95
  4. =ESSAY ENGLISH LANGUAGE PHONETICS AMBIGUITY
  Glass08b
  1. Robert L Glass
  2. Software design and the Monkeys brain
  3. =ESSAY DESIGN ITERATION CREATION
  4. Commun ACM V51n6(Jun 2008)pp- 2008)pp21-22 + correspondence V51n11(Nov 2008)p9
  5. Research showed mental design process: understand problem; create solution; do(test; modify); tests OK.
  6. Tools & methods slow process down.
  7. Unless can record directly the designers brain!
  8. (Alexis Simonelis)|-"No one knows the one best way to build a mental model of a software solution".
  Glass08c
  1. Robert L Glass
  2. Two Mistakes and Error-Free Software: A Confession
  3. =ANECDOTE TEST COVERAGE vs ERRORS
  4. IEEE Software Magazine V25n4(Jul/Aug 2008)pp96+95
  5. In the 1970's Glass analysed testing data base and discovered that 35% of errors where omissions and 40% only appear if a combination of pieces of code were taken -- 75% of errors not found by testing every piece of code.
  6. In 1981 analysed errors that are uncovered after going live. 60% were omitted code, and 23% were failing to reset data.
  7. Conclusion: good testing does not expose most errors.
  Glass09
  1. Robert L Glass
  2. Making research more relevant while not diminishing its rigor
  3. IEEE Software Magazine V26n2(Mar/Apr 2009)pp96+95
  4. =SURVEY 2 PAPERS RESEARCH PROCEDURE
  5. Michael Rosemann and Iris Vessey propose that teams doin research in some area should show their plans and their results to practitioners who carry out a reality check.
  6. They proposed this in "Toward Improving the Relevance of Information Systems Research to practice: the role of applicability checks" [MIS Quarterly (Mar 2008) pp1-22] and in the 2005 "European Conference on Information Systems".
  Glass09a
  1. Robert L Glass
  2. Goodbye
  3. IEEE Software Magazine V26n6(Nov/Dec 2009)pp96+95
  4. =ESSAY ESTIMATION ONE SIZE METHOD RESEARCH = ADVOCACY
  5. Estimates are done by the wrong people and too early. No process to adjust estimates as process generates data. No agreeed method for estimates.
  6. Local loyalties lead to wasted controversy about software development.
  7. One size does not fit all. New methods need evaluation to match their best application.
  Glass09b
  1. Robert L Glass
  2. Frequently Forgotten Fundamental Facts about Software Engineering
  3. IEEECS Career Watch Newsletter (1 Dec 2009) [ fa035?utm_source=bronto&utm_medium=email&utm_term=Forgotten+Facts+About+Software+Engineering ] reprint of IEEE Software magazine V18n3(May/Jun 2001)pp112+110-111
  4. =SUMMARY EXPERIENCE COMPLEXITY PEOPLE TOOLS TECHNIQUES QUALITY RELIABILITY EFFICIENCY MAINTENANCE REQUIREMENTS DESIGN REVIEWS INSPECTIONS REUSE ESTIMATION RESEARCH
  GlasserGurevichVeanes04
  1. Uwe Glasser & Yuri Gurevich & Margus Veanes
  2. Abstract Communication Model fro Distributed Systems
  3. IEEE Trans Software Engineering V30n7(Jul 2004)pp458-472
  4. =THEORY COMMUNICATION MicroSoft Plug-and-Play UPnP XLANG AsmL
  5. AsmL::="Microsoft's abstract state machine language", compiles into .NET.
  6. ASM::="Abstract State Machine".
  7. Describes AsmL. Nondeterminstic Object-Oriented nonsequential language.
  8. Uses AsmL to define an Abstract Communication Model that generalizes UPnP XLANG (XML business processes), Model-Based testing and analysis etc.
  GlassRostMatook08
  1. Robert L Glass & Johann Rost & Matthias S Matook
  2. Lying on Software Projects
  3. IEEE Software Magazine V25n6(Nov/Dec 2008)pp90-95
  4. =POLL LIES ESTIMATION STATUS REPORTS ETHICS
  5. Lies observed: Estimation(commonest), Status Reporting, Politics, Hype(rarest).
  Glerum99
  1. Katrina Glerum
  2. The Harvard Educational Record System
  3. Software Development Magazine V7n1(Jan 1999)pp49-52+54-55
  4. =EXPERIENCE LEGACY WEB three-tier Java Oracle CORBA UML
  Go
  1. Google
  2. The Go Programming Language
  3. Web site [ http://golang.org/ ]
  4. =ADVERT TOOL LANGUAGE GO SYSTEMS PROGRAMMING FAST SAFE OPEN SOURCE CONCURRENT NONSEQUENTIAL CSP
  GoShiratori99
  1. Kentaro Go & Norio Shiratori
  2. A Decomposition of Formal Specifications: An Improved Constraint-Oriented method
  3. IEEE Trans Se V24n2(Mar/Apr 1999)pp258-273
  4. =THEORY LOTOS FSM TOP-DOWN LTS:="Labeled Transition Systems" applied to protocol in OSI reference model
  GlushkoMcGrath07
  1. Robert J Glushko & Tim McGrath
  2. Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services
  3. MIT Press 2008 $22 ISBN978-0-262-57245-3
  4. =UNREAD ANALYSIS DESIGN DATA XML DOCUMENTS WEB
  5. Notes [click here if you can fill this hole]
  Godartetal94
  1. C Godart & F Charoy(Authors) & Iain A Craig(Translator)
  2. Databases for Software Engineering
  3. Prentice Hall Englewood Cliffs NJ 1994 ISBN 0-13-030255-5 CR9508-0548(R L Glass)
  GodefroidPeleStaskauskas96
  1. Patrice Godefroid & Doron Peled & Mark Staskauskas
  2. Using Partial-Order Methods in the Formal Validation of Industrial Concurrent Programs
  3. IEEE Trans Soft Eng VSE-22n7(Jul 1996)pp496-507
  Gogollaetal91
  1. Martin Gogolla & Uwe Hohenstein
  2. Towards a Semantic View of an Extended Entity-Relationship Model
  3. ACM Trans Database Systems V16n3(Sep 1991)pp369-416
  4. CR9209-0713
  5. =MATHEMATICAL ER MODEL Queries Relational completeness and safety
  Goguen86
  1. Joseph A Goguen
  2. Reusing and Interconnecting Software Components
  3. IEEE Computer Magazine V19n2(Feb 1986)pp16-18
  4. LIL::Language=Library Interconnection Language. Theories+generics+packages+views+...Ada like. horizontal and vertical composition
  GokhaleLyu05
  1. Swapna S Gokhale & Michael Rung-Tsong Lyu
  2. A Simulation Approach to Structure-Based Software Reliability Analysis
  3. IEEE Trans Software Engineering V31n8(Aug 2005)pp643-656
  4. =SIMULATION RELIABILITY MODULES FAILURE REPAIR
  Golazetal90
  1. W H Golaz & JR Comer and TC Nute and JR Rinewalt and DJ Rodjak
  2. Academic Experiences in Software Project Management
  3. SIGCSE Bulletin V22n3(Sep 1990)pp47-53
  4. =EXPERIENCE Analysis needed
  GoldMohanLayzell05
  1. Nicholas E Gold & Andrew M Mohan & Paul J Layzell
  2. Spatial Complexity Metrics: An Investigation of Utility
  3. IEEE Trans Software Engineering V31n3(Mar 2005)pp203-212
  4. =EXPERIENCE METRICS 30 COBOL TECHNICAL LoC
  5. Spatial Complexity Metrics allow for the distance between references to identifiers.
  6. Two out of three such metrics are no better than Lines of Code at predicting complexity on this sample.
  7. Sample is of single file COBOL programs, many versions.
  8. A metric worth study: Douce Basic(1999). Sum[each call] (number of lines of code from call to definition)
  Goldberg87
  1. Adele Goldberg
  2. Programmer as Reader
  3. IEEE Software V4n5(Sep 1987)pp62-70
  4. object-oriented QUALITY Readability Technical
  GoldbergARubin95
  1. Adele Goldberg & Ken Rubin
  2. Succeeding with Objects
  3. Addison-Wesley Redwood City CA 1995 $49.54 ISBN 0-201-62878-3 CR9606-0424
  4. rev*** Software Development Magazine(Dec 1995)p42
  5. CR: OO implies Management and organizational change 39 projects 26 organizations "Decision frameworks"
  GoldbergD91
  1. David Goldberg
  2. What Every Computer scientist Should Know About Floating-Point Arithmetic
  3. ACM Computer Surveys V28n1(Mar 1991)pp5-48
  4. mathematics errors
  GoldbergD94
  1. David E Goldberg
  2. Genetic and Evolutionary Algorithms Comes of Age
  3. Comm ACM V37n3(Mar 1994)(AI issue)pp113-119
  GoldfedderRising96
  1. Brandon Goldfedder & Linda Rising
  2. A Training Experience with Patterns
  3. Comm ACM V39n10(Oct 1996)pp61-64
  4. Design Patterns book worthwhile but needs real-time embedded systems considerations
  5. classroom not enough
  6. students need convincing that the code is good
  7. students can be lead to discover some patterns
  8. students need exposure to range of platforms and projects
  9. makes them able to share and recognized problems and solutions
  Goldkuhl06
  1. Goran Goldkuhl
  2. Action and Media in interorganizational Interactions
  3. Commun ACM V49n5(May 2006)pp53-57
  4. =DEMO INTERACTION DESIGN LANGUAGE-ACTION WORKFLOW DEMO BAT Business model NET PEOPLE REALITIES SYSTEMS
  5. Stresses to two-way flow of values -- actual or future: e.g. payment and service.
  6. Restates 4 phase action workflow loop: preparation; negotiation; performance; acceptance.
  7. Focus on inter-business interactions/workflows.
  8. Information technology as a mediating.
  9. Who is in control of each phase?
  Goldschlag90
  1. David M Goldschlag
  2. Mechanically Verifying Concurrent Programs with the Boyer-Moore Prover
  3. IEEE Trans Software Engineering SE-V16n9(Sep 1990)
  Goldstein05
  1. Harry Goldstein
  2. Who killed the Virtual Case File
  3. IEEE Spectrum Magazine (Sep 2005)pp24-35
  4. =HISTORY VCF Trilogy FBI DISASTER FAILURE RISKS
  5. Demonstrates that bad management and bad process can lead to a lot of money being spent for nothing.
  6. Mistakes:
    1. Amateurism
    2. Changing goals in midstream
    3. Tightening the schedule
    4. No process or control
    5. No "system architecture"
    6. Changing bosses in midstream.
    7. Muzzling and ignoring critics.
    8. Giving very detailed requirements (position and color of buttons) but no vision or goals.
    9. Changed requirements flood in after first demo.
    10. Cost plus contract.
    11. NIH: no COTS bought in
  7. It may be cheaper to spend time writing good requirements using math and prototypes rather than hiring lawyers to wrangle over the ambiguities.
  GoldsteinAlger92
  1. Neal Goldstein & Jeff Alger
  2. Developing Object-oriented Software for the Macintosh: Analysis Design & Programming
  3. Addison-Wesley Redwood City CA 1992
  4. QA76.8 M3 G643 ISBN 0-201-57065-3 BNB 91-29046 Dewey 005.265
  Gomaa85
  1. Hassan Gomaa(hgomaa@isse.gmu.edu)
  2. Software development of real-time systems
  3. Commun ACM V29n7(Jul 1986)pp657-668
  4. DFD+queuesetc STD/FSM incremental development prototypes+event sequence diagrams
  Gomaa95
  1. Hassan Gomaa(hgomaa@isse.gmu.edu)
  2. Domain Modeling Methods and Environments [SamadzadehZand95] pp256-258
  3. Demo EDLC(Evolutionary Domain Life Cycle) eliminates development vs maintenance
  GomaaMenasceShin01
  1. Hassan Gomaa & Daniel A Menasce & Michael E Shin
  2. Reusable Component Interconnection Patterns for Distributed software Architectures
  3. ACM SIGSOFT Software Engineering Notes V26n3(May 2001)pp69-77
  4. =THEORY NONSEQUENTIAL NETWORK MODULE COUPLING
  5. Patterns for handling synchronous, asynchronous and broker ed communication expressed using the UML.
  GondranMinoux07
  1. M Gondran & M Minoux
  2. Dioids and Semirings: Links to fuzzy sets and other applications
  3. Fuzzy sets and Systems V158n12(Jun 2007)pp1273-1294 CR 0805-0505
  4. =UNREAD =HISTORY DIOIDS MATHEMATICS ALGEBRA THEORY APPLICATIONS
  5. A dioid is a semiring with idempotent addition.
  6. See my notes [ maths/math_41_Two_Operators.html#SEMIRING ] for the definitions of these terms.
  GonnetBaeza-Yates91
  1. G.H. Gonnet & R A Baeza Yates
  2. Handbook of Algorithms & their Data Structures(In Pascal & C)(2nd Edn)
  3. Addison Wesley Reading Ma. 1991
  4. =REFERENCE DATA ADTs ALGORITHMS
  Gonthier08
  1. Georges Gonthier
  2. Formal Proof -- The Four-color Theorem
  3. Notices of the American Mathematical Society V55n11 (Dec 2008) [ tx081101382p.pdf ]
  4. =EXAMPLE Coq 4COLOR FORMAL PROOFS MATHEMATICS TYPES
  5. This formal proof of the famous four-color theorem uses Combinatorial Hypermaps not Graphs!
  6. Coq and the calculus of Inductive Constructions (CiC).
  7. Inference subsumed into type inference?
  GonnetTompa
  1. G.H. Gonnet & ?? Tompa
  2. A Constructive Approach to the Design of Algorithms & their Data Structures
  3. Commun ACM 26 11 (Nov 1983) pp912-920
  4. =METHOD ADTs Reality PURPOSE
  Gonzales05
  1. Regina Gonzales
  2. Developing the Requirements Discipline: software vs systems
  3. IEEE Software Magazine V22n2(Mar/Apr 2005)pp59-61
  4. =HISTORY SYSTEMS ENGINEERING vs SOFTWARE ENGINEERING REQUIREMENTS
  5. Tendency to jump to solutions before understanding the problems. Systems engineers get the big picture(including people and politics) but don't understand software.
  6. Software engineers miss the big picture and focus on formalizable models.
  GoodeMachol57
  1. Harry H Goode & Robert E Machol
  2. System Engineering: An Introduction to the design of Large-scale systems
  3. McGraw-Hill NY NY (1957) LC Card# 56-11714 TA168
  4. =TEXT ANALYSIS DESIGN ENGINEERING MATHEMATICS CYBERNETICS PEOPLE MODELS EXPERIMENTS ECONOMICS PERFORMANCE PROCESS TEAM GRAPH THEORY
  5. Proposes a multi-phase process: initiation; Organization; Preliminary design; Principal Design; Prototype construction; Test Training and Evaluation
  6. Each phase has a complex block diagram.
  7. non-standard flow diagrams (digital and analog) implement mathematical models of computations on 2 0r 3 pages.
  8. Block diagrams are discussed in detail (pages305-314): functional, component, geographical, physical-layout, ...
  9. Distinguished information flow from material flow and hypothesizes that designs based on information flow are easily adjusted to include material flow.
  10. Ref to [Luce53] and [Leavitt51] on the effects of team structure (graph theory) on problem solving ability and attitudes. A wheel like structure with a central communicational hub tends to develop a leader and solve easier problems faster. A circular structure is better for some hard problems and people felt they had more fun but were not organized. (pages 390-393)
  11. Implies that structure of a system design team must not reflect the structure of the system they are designing because system design is typically a harder problem than running the solution system (page 392)
  GopalKrishnanEtAl02
  1. Anandasivam Gopal & M S Krishnan & Tridas Mukhopadhyay & Dennis R Goldenson
  2. Measurement Program in Software Development: Determinants of Success
  3. IEEE Trans Software Engineering V28n9(Sep 2002)pp863-875
  4. =SURVEY STATS METRICS PROCESS ORGANIZATION TECHNICAL
  5. What tends to increase the successful use of software metrics?
  6. Survey of 214 organizations under CMU SEI aegis.
  7. Suggests a dozen factors and questions to to estimate them using Likert 1..5 scales. Uses principal components to weight questions.
  8. Tries to fit to simultaneous equations for use_in_decision_making and Organizational_performance.
  9. Claims that usage depends significantly performance, analysis, and frequency with which measurements are recorded.
  10. Claims that performance depends significantly on the alignment of the metrics program with management.
  11. (dick)|-Results intuitive but methods not to be trusted.
  GopalMukhopadhyayKrishnan05
  1. Anandasivam Gopal & Tridas Mukhopadhyay & M S Krishnan
  2. The Impact of institutional forces on software metrics programs
  3. IEEE Trans Software Engineering V31n8(Aug 2005)pp679-694
  4. =SURVEY STATISTICS METRICS PROCESS MANAGEMENT CUSTOMERS RIVALS
  5. Applies Cooper and Zmud's innovation diffusion model(1990) :
  6. innovation_diffusion::= initiation; adoption; adaption; acceptance; routinization; infusion.
  7. Adaption is when the the normal processes are being changed to fit the innovation.
  8. Management, Customers, and rivals all influence whether a metrics program make it into/through adaption.
  9. See also [GopalKrishnanEtAl02].
  Gorden81
  1. Practical LCP
  2. McGraw-Hill UK
  3. DDD
  GordijnYuRaadt06
  1. Jaap Gordijn & Eric Yu & Bas van der Raadt
  2. e-service Design Using i* and e^3 value modeling
  3. IEEE Software Magazine V23n3(May/Jun 2006)pp26-33
  4. =DEMO BUSINESS MODEL GOALS + VALUES ECONOMICS REQUIREMENTS WEB/NET SERVICES softgoals
  5. Complex diagrams expressing important ideas.
  6. Values are always exchanged.
  7. Obligations are always paired.
  8. Map how tasks & goals are related.
  9. Look for chains of value exchanges.
  Gordon94
  1. Andrew D Gordon
  2. Functional Programming and input/output
  3. Cambridge Univ Press NY NY 1994 ISBN 0-521-47103-6
  4. CR9607-0470
  5. =THEORY FUNCTION DATA SEMANTICS DEMO
  GordonBieman95
  1. V scott Gordon & James M Bieman
  2. Rapid Prototyping: Lessons Learned
  3. IEEE Software Magazine V12n1(Jan 1995)pp85-95
  4. =EXPERIENCES PROTOTYPING EVOLUTION
  5. 39 case studies 33 successful+ most evolutionary not throwaway
  Gorecki93
  1. Andrzj Tomasz Gorecki
  2. Reliable Programs Must Not be Written...
  3. ACM SIGSOFT Software Engineering Notes V18n3(Jul 1993)ppA 44-46
  4. =ADVERT GRAPHIC CODE DIMENSIONS
    1. Reliable Programs Must Not be Written they must be drawn. Notes 4 dimensionel real world and 1 dimensional code
      Proposes 2 1/2 D flowcharts
  Gorlaetal90
  1. N Gorla &A C Benander & B A Benander
  2. Debugging Effort Estimation Using Software Metrics
  3. IEEE Trans SE-16n2pp223-231(Feb 1990)
  4. =THEORY quality METRICS EFFORT
  GorlaLam04
  1. Narasimhaiah Gorla & Yan Wah Lam
  2. Who should work with Whom?
  3. Commun ACM V47n6(Jun 2004)pp79-82
  4. =POLL PEOPLE TEAMS
  5. MBTI::= Net{social_interaction:{Introvert, Extrovert}, information_gathering: {Sensing, Intuitive}, decision_making: {Thinking, Feeling}, dealing_with_the_external_world: {Perceiving,Judging},
  6. short_form::("I"|''E") ("S"|"I") ("T"|"F") ("P"|"J").
  }=::MBTI.
8. Leaders of good teams Sensing<Intuitive & Thinking<Feeling.
9. Systems analysts in good teams tended to be Thinking>Feeling.
10. Programmers in good teams tended to be Introvert<Extrovert.
11. Good teams tended to have leaders who were more Intuitive +Extrovert than the members of the team.
12. Team size matters.
Gorlatch00
1. Sergei Gorlatch
2. Toward Formally-based design of message passing programs
3. IEEE Trans softw eng V26n3(Mar 2000)pp276-288
4. =MATHENMATICAL NONSEQUENTIAL PERFORMANCE
5. reductions hpmpmorphism theorem
Gorman00
1. Ian E Orman
2. Parsing Complex Text Structures
3. Dr. Dobbs Journal #313(Jun 2000)pp90+92-98
4. =ADVERT DEMO OmniMark TOOL REGULAR-EXPRESSIONS GRAMMAR
Gorschek06?
1. Tony Gorschek & Claes Wohlin & Per Garre & Stig Larsson
2. A Model for technology transfer in practice
3. IEEE Computer Magazine V39n10(Oct 2006)pp88-95
4. =EXPERIENCE PROCESS ACADEME vs INDUSTRY
5. Proposes a process that might be a model for all software development:
  1. Identify potetial improvement areas based on industry needs.
  2. Formulate research agenda.
  3. Formulate candidate solutions.
  4. Evoultionand transfer preparation via validation.
  5. Lab validation.
  6. Static Validation -- presentation and feedback.
  7. Dynamic validation -- pilot programs
  8. Release -- including tailoring the general model to particular companies, documentation, training, support, champion, measurements.
6. Has "Lessons Learned" for each step in process.
Gorton08
1. Ian Gorton
2. XML does Real Programmers a Service
3. IEEE Computer Magazine V41n9(Sep 2008)pp100+98-99
4. =JOKE HISTORY QUICHE SPECIFICATION vs CODE DCE Corba PROCESS EMPIRICAL AGILE XML SERVICES AGENTS AI
5. Real Programmers write code, late at night, just before the deadline.
6. Agile allows real programmers to do what they want and provide the stakeholders with what they want.
7. XP: "[...] every one prefers muffins and expresso to writing specifications."
GortonLiuBrebner03
1. Ian Gorton & Anna Liu & Paul Brebner
2. Rigorous Evaluation of COTS Middleware Technology
3. IEEE Computer Magazine V36n3(Mar 2003)pp50-55
4. =DEMO QUALITIES WEB/NET Java J2EE servers MTE WebSphere WebLogic ...
Goseva-PopstojanovaEtal03
1. Katerina Goseva-Popstojanova & Ahmed Hassan & Ajith Guedem & Walid Abdelmoez & Diaa Eldin M Nassar & Hany Ammar & Ali Mili
2. Architectural-level Risk Analysis Using UML
3. IEEE Trans Software Engineering V29n10(Oct 2003)pp946-960
4. =CASE-STUDY ARCHITECTURE RISK SCENARIO UML RoseRT Markov cardiac pace-maker USECASE
Goshawke78
1. Walter Goshawke
2. qadvantages of Number Language
3. =ADVERT NUMBERS ITL UNIVERSAL LANGUAGES
4. Computer Weekly (UK) (Mar 16 1978)p20
5. SLUNT::="Spoken Language Numeric Translation".
6. More details in Computer Weekly (UK) (Sep 1 1977)
Gotel06
1. Olly Gotel
2. In Search of the System Concept
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp102-103
4. =ADVERT REQUIREMENTS CONCEPT
5. The systems concept is a short vision statement.
6. It can be as short as a tag line or motto.
7. They have many uses and many advantages.
GotelMorris09
1. Olly Gotel & Stephen Morris
2. More than Just "Lost in Translation"
3. IEEE Software Magazine V26n2(Mar/Apr 2009)pp7-9
4. =IDEA MULTIMEDIA REQUIREMENTS TRACEABILITY
5. Need to elicit, record, analyze, and document requirements that include audiovisual records, videos, etc. These, in turn, have to be linked to design decisions and artifacts
Goth00
1. Greg Goth
2. New Air Traffic Control Software Takes an Incremental Approach
3. IEEE Software Magazine V17n3(Jul/Aug 2000)pp108-111
4. =EXPERIENCE FreeFlight FAA CTAS NASA USER EVOLUTION TRACON METRICS EVM
5. 1.4M LOC $600M C Sun Sparc -> C++ GUI
6. Incremental spiral, "build a little, test a little", constant communication and updates, start with algorithms to generate optima but back to get feasible programs and robust solutions. Optimize design code later if needed.
7. workload vs efficient light plans.
8. web based code and bug tracking.
Goth00b
1. Greg Goth
2. The Team Software Process: A Quiet quality Revolution
3. IEEE Software Magazine V17n6(Nov/Dec 2000)pp125-127
4. =EXPERIENCE TSP IMPROVEMENT CMM TEAM
5. needs better tools -- Visual basic is a hog.
6. hard to believe until you try it.
7. TSP:=following, [Humphrey9??]
Goth02
1. Greg Goth
2. Will the Cyber-UL Concept Take Hold?
3. IEEE Software Magazine V19n4(Jul/Aug 2002)pp12-15
4. =ARTICLE SECURITY STANDARD
5. Common Criteria for security. parallel to the Underwriters Laboratory seal of approval.
Goth02a
1. Greg Goth
2. Has Object-Oriented Programming Delivered?
3. IEEE Software Magazine V19n5(Sep/Oct 2002)pp104-107
4. =OPINIONS OBJECT-ORIENTED TECHNICAL C++
Goth04
1. Greg Goth
2. Source Code controversy not just about security
3. IEEE Software Magazine V21n4(Jul/Aug 2004)pp96-99
4. =NEWS SOURCE SECURITY ETHICS LEGAL INTELLECTUAL PROPERTY VOTING BSD Diebold Microsoft CISCO SCO AT&T IBM EFF
5. Example of loss of trade secret protection by failing to shutdown public FTP site.
6. Example of flawed source code not being fixed for five years.
7. Examples of "Dirty Hands" doctrine: you can't claim intellectual property for something that you may have stolen!
Goth09
1. Greg Goth
2. Betting on ideas
3. Commun ACM V52n3(Mar 2009)pp13-15 [ 1467247.1467252 ]
4. =ARTICLE PREDICTION MARKETS IOWA IEM PROBABILITY DELPHI
John F Schoch & Jon A Hupp
The "Worm" programs -- early experience with a distributed computation
Commun ACM V25n3(Mar 1982)pp172-180 [ 358453.358455 ]
=DEMO WORM NETWORK
Refers to [Brunner75] in a footnote and records the transition from a novelist's idea of a "Tape worm" to a practical technology.

Usage	% of time
Required	83%
Sketch	78%
Blueprint	76%
Language	38%

Gotterbarn93

Donald Gotterbarn
SEL 'Experience Factory' explored at software engineering workshop(Goddard Space Flight December 2nd-3rd 1992)
IEEE Computer Magazine V26n2(Feb 1993)pp117-118
=REPORT EMPRIRICAL SEL

Gotterbarn04

Don Gotterbarn
UML and Agile Methods: In Support of Irresponsible Development
ACM SIGCSE Bulletin V36n2(Jun 2004)pp11-13
=ESSAY RISKS AGILE UML RUP vs SYSTEM
Examples of how focusing on programming is risky.
A focus on programming can accidental damage the people effected by the software because we don't think outside the box.
Examples: cataract removal design did not include the patient.... program to open door and start car... web page ignores some of stake holders.
"One aspect of being a professional is developing systems that improve a situation rather than make it worse."
Need a way to express/think: "In some cases, if you develop software in this way, it might have this consequence."

GotterbarnMillerRogerson99

Don Gotterbarn & Keith Miller & Simon Rogerson
Software Engineering Code of Ethics and Professional Practice
Commun ACM V42n10(Oct 1999)pp1026-107 + IEEE Computer magazine V32n10(Oct 1999)pp84-88
=STANDARD RISKS USER PEOPLE ETHICS

Gottesdiener99

Ellen Gottesdiener
Decoding business needs
Software Development Magazine V7n12(Dec1999)pp28-32
=EXPERIENCE REQUIREMENTS USER
how to workshop
Advert [ about.php ]

Gottesdiener02

Ellen Gottesdiener
Requirements by collaboration: workshops for defining
Addison-Wesley Longman Publishing Co., Inc., Boston MA 2002. ISBN 0-201-78606-0 $44.99 [ http://www.ebgconsulting.com/ ]
=HANDBOOK USER CLIENT REQUIREMENTS WORKSHOPS

GottlobSchreflRock96

Georg Gottlob & Machael Schrefl & Brigitte Rock
Extending object-oriented systems with roles
ACM Trans Inf Syst V14n3(Jul 1996)pp268-296 CR9706-0451
=THEORY OBJECT-ORIENTED

Gouda02

Mohamed G Gouda
Multiphase Stabilization
IEEE Trans Software Engineering V28n2(Feb 2002)pp201-208
=THEORY STABILIZATION FAULTS ADAPTIVE
Assumes system is a collection of actions with fairness. An actions is a guarded command. Actions partitioned into numbered phases. Convergence to a property by a series of predicates and each is achieved by actions in that phase.
Simple yet useful generalization of standard fault recovery model.

GoudaHerman91

Mohamed G Gouda & Ted Herman
Adaptive Programming
IEEE Trans Software Engineering SE-16 n9(Sep 1991)p911-921.
=THEORY RELIABILITY STABILIZATION FAULTS ADAPTIVE
secures::= all sequences of states under given fixed input conditions ultimately enter particular set of states. axiomatic a la Hoare.

Gouldetal91

John D Gould & Stephen J Boies & Clayton Lewis
Making Usable useful productivity enhancing computer applications
Commun ACM v34n1(Jan 1991)pp74-85
=EXPERIENCE USER DESIGN

GouldLewis85

John D Gould & Clayton Lewis
Designing for Usability: Key Principles and What Designers Think
Commun ACM V28n2(Feb 1985)pp300-311
=EXPERIENCE USER DESIGN
early focus on USER+tasks & empirical measurement & iterative design

Grabiner95

Judith Grabiner(Pitzer college)
Descartes and Problem-Solving
Mathematics Magazine V68n2(Apr 1995)pp83-97
=HISTORY PROBLEM SOLVING MATHEMATICS ALGEBRA

Grado-CaffaroGrado-Caffaro01

Maria-Angles Grado-Caffaro & Martin Grado-Caffaro
The Challenges that XML Faces
IEEE Computer Magazine V34n10(Oct 2001)pp15-18
=REVIEW MARKUP LANGUAGE DTD
DTDs can not define numeric constraints on data. Schemas may map text data in XML docs into numeric data.
challenge1: diversity may imply incompatibility. Example: competing organizations proposing B2B standards: Oasis(ebXML) vs MicroSoft (BizTalk) vs RosettaNet
challenge2: security -- need encryption. content can be malicious so need ability to be sure that data is from trusted source.

Grady93

Robert B Grady
Practical Results From Measuring Software QUALITY
Comm ACM V36n11(Nov 1993)pp62-68
=EXPERIENCE METRIC QUALITY SQA

Graf89

Mike Graf
Building a Visual Designers Environment
pp291-325 of Chang89
=EXPERIENCE engineering language graphic

Graham94

Ian Graham (BIS App System)
Object-Oriented Methods(2nd edn)
Addison-Wesley Reading MA 1994 ISBN 0-201-59371-8 CR9503-0143
=SURVEY OBJECT-ORIENTED METHODS MODEL REALITY USER PROTOTYPING
SOMA(Semantic Object Modeling Approach)
ref in [Henderson-SellersGraham96]

Graham96

Ian Graham
Making Progress in Metrics
Object Magazine 6(9)(Oct 1996)pp68-73
=EXPERIENCE METRICS OBJECTS
critique of earlier attempts; task points; The International Object-Oriented Metrics Club(IOMeC)

Gras04

Jean-Jacques Gras
End-to-end Defect Modelling
IEEE Software Magazine V21n5(Sep /Oct 2004)pp98-100
=EXPERIENCE MOTOROLA DEFECTS SQA BN BAYES NETWORKS
Evidence for usefulness Bayesian Networks [FentonKrauseNeil02] [FentonNeil99] in predicting defects, and for adapting model to actual defect rates. Also BNs useful for eliciting, comparing and combining causal models

Gravell90

A M Gravell
Minimisation in Formal Specification and Design
pp32-45 in Nicholls90
=THEORY QUALITY TECHNICAL OPTIMISATION REFINEMENT

Graves86

Tom Graves
Towards a Magical Technology
USA Interbook Inc San Leandro CA, Gatway Books Bath UK, 1986 ISBN 0-946551-30-8
=THEORY SCIENCE ENGINEERING MAGIC
The engineer works in the swamp while the scientist builds a castle.
Nice pictures.
Science searches for the truth about what is "out there" but the engineer seeks for value.
The fool tries to make useful things in the swamp while looking at the scientific truth not the real world.
Based on an even weirder book.

GravesEtal00

Todd L Graves & Alan F Karr & J S Marron & Harvey Siy
Predicting Fault Incidence Using Software Change History
IEEE Trans Software Engineering V26n7(Jul 2000)pp653-661 CR0104-0133
=EXPERIENCE STATISTICS SQA METRICS
code decay
Number of changes was the best predictor of future need for change. Normal metrics did not predict as well.
p654: "We assume new faults are continuously being added to the system as changes are made."
best model: each delta has an exponentially decaying chance of generating a further fix!
Module Size does not matter!!

GraveKarrMarronSiy00

Todd L Graves & Alan F Karr & J S Marron & Harvey Siy
Predicting Fault Incidence Using Software Change History
IEEE Trans Software Engineering V26n7(Jul 2000)pp653-661
=EXPERIENCE STATISTICS SQA METRICS
code decay
Number of changes was the best predictor of future need for change. Normal metrics did not predict as well.
p654: "We assume new faults are continuously being added to the system as changes are made."
best model: each delta has an exponentially decaying chance of generating a further fix!

Gray88

David Gray
The Formal Specification of a Small Bookshop Information System
IEEE Trans on Soft Eng vSE-14n2(Feb 1988)pp263-272
=EXAMPLE PURPOSE Z

GrayN94

N A Gray
Programming with class: A practical introduction to object-oriented programming with C++
John Wiley & Sons Inc NY NY 1994 ISBN 0-471-94350-9 CR9509-0649
1. 1: why change to oo
2. 2: history of languages
3. 3: example introduces concepts
4. 4,5,6: C++
5. 7,8,9,10: libraries, tools, environments(ET++, MacApp)
6. 11: OOA/OOD
7. 12: newer C++ features(template funtions, multiple inheritance, exceptions)
8. 13: overview of Eiffell
  needs copyeditting and indexing properly. no exercises not enough syntactic/semantic C++ details

GrayPetal92

Peter M Gray & Krishnarao G Kulkarni & Norman W Paton
Object-oriented databases: a semantic data model approach
Prentice Hall Englewood Cliffs NJ 1992(ISBN 0-13-630203-3)
CR9306-0359(H.2.4)"Useful reference for reserchers
developers & grad students"
similar review IEEE Software Magazine V12n2(Mar 1995)pp118-119

GrayRWetal92

Robert W. Gray & Vincent P Heuring * Steven P Levi & Anthony M Sloane & William M Waite
Eli: A Complete
Flexible
Compiler Construction System
Commun ACM V33n2(Feb 1992)pp121-131
DDD

Green80

?? Green
Ifs & Thens: Is Nesting Just for the Birds?
Software Practice & Experience V10pp373-381
=harmful =EXPERIMENT Technical CODE NESTED
Presents experimental data that nested code is harder to understand.
Having different endings that match begginnings helps reduce errors.

GreenLedgard11

Robert Green & Henry Ledgard
Coding Guidelines: finding the art in the science
Commun ACM V54n12(Dec 2011)pp57-63 [ 2043174.2043191 ] + letters V55n3(Mar 2012)pp6-8 [ 2093548.2093550 ]
=ESSAY TECHNICAL CODING STYLE TABULAR MATHEMATICS
A must-read reminder for all coders, team leaders, CS Students, and some teachers.
Code is not natural language but tables and math!

.Close

GreenHevner00

Gina C Green & Alan R Hevner
The Successful Diffusion of Innovations: Guidance for Software Development Organizations
IEEE Software Magazine V17n6(Nov/Dec 2000)pp96-103
=SURVEY PSP usage and satisfaction by 70..80 developers
Satisfaction is linked to use.
Satisfaction is increased when developers have the choice to use a predefined process that increases the predictability of their work.

GregoriadesSutcliffe05

Andreas Gregoriades & Alexander Sutcliffe
Scenario-Based Assessment of Nonfunctional Requirements
IEEE Trans Software Engineering V31n5(May 2005)pp392-409
=DEMO TOOL SRA BAYES BN MODEL SYSTEM PERFORMANCE QUALITIES NFR REQUIREMENTS TESTING
Allows for human unreliability in system.
Bayesian network allows the back propagation of high failure rates to likely root causes.
Compare with NASA operational profiles.

Gregory84

?? Gregory
Letter
Software Engineering Notes V9 n9 p13 ACM SIGSOFT
prototypes System

GreiskampLepper00

Wolfgang Grieskamp & Markus Lepper
Using Use Cases in Executable Z
3rd IEEE Int'l Conf Formal Engineering Methods (Sep 2000)pp111-119
=DEMO FORMALIZE Black Box TEST USE CASES Executable Z Notation Lift ZAP ZETA
Shows how to express use cases/scenarios in an executable form of the Z notation.

Grier06

David Alan Grier
The Print of the Hand
IEEE Computer Magazine V39n7(Aug 2006)pp8-10
=ANECDOTES HISTORY WOMEN ENGINEERS SALESPEOPLE MANAGERS INVENTIVENESS
How to handle salesmen requesting incorrect performance figures.
The obscene operating system.
Business incubation.

Grier06a

David Alan Grier
The Empty Box
IEEE Computer Magazine V39n8(Sep 2006)pp9-11
=HISTORY SOFTWARE BUSINESS ADAPSO ISV IBM
What is the center of the universe -- Hardware or Software?
Hardware became invisible under a layer of system software, is systems software also disapearing under a layer of applications?

Grier06b

David Alan Grier
The Language of Bad Love
IEEE Computer Magazine V39n10(Oct 2006)pp7-9
=HISTORY LANGUAGES COBOL FORTRAN ALGOL JAVA OPEN SOURCE LOVE
Evidence of code (and language specs) being open in the days of mainframes.

Grier07

David Alan Grier
Dirty Electricity
IEEE Computer Magazine V40n2(Feb 2007)pp6-8
=HISTORY DEBUGGING
Edison commented on bugs in 1878.

Grier07c

David Alan Grier
Working Class Hero
IEEE Computer Magazine V40n5(May 2007)pp8-10
=HISTORY OPEN SOURCE 1955 SHARE CUBE LINUX
Argues that the Open/Free Source Code movement dates back to the free sharing of software in "user groups" in the 1950's.
Anecdote arguing that it takes a degree of oppression of the workers to keep a software product alive in competition.

Grier07a

David Alan Grier
The Boundaries of Time
IEEE Computer Magazine V40n7(Jul 2007)pp5-7
=History Clocks Y2K ENIAC SAGE 360

Grier07b

David Alan Grier
Annie and the boys
IEEE Computer Magazine V40n8(Aug 2007)pp6-9
=HISTORY SPREADSHEETS MASSMARKET VISICALC MICROSOFT MULTIPLAN LOTUS 1-2-3 QUATRO IBM COPYRIGHT INTELECTUAL PROPERTY

Grier08

David Alan Grier
Edward Elgar's Facebook Page
IEEE Computer Magazine V41n11(Nov 2008)pp6-8
=ESSAY SOCIAL NETWORKS SCIENCE invisible colleges Email cell-phones
How "Pomp and Circumstances" became the graduation song because of Elgar's social network.
invisible_colleges::="Concluded that loosely organized groups drive scientific research", Derek de Solla Price 1960s.
Connection can have different strengths. Weak connections can be important -- if they distribute a message widely or allow wide collection of data.
Maintaining an invisible college can take time and travel.

Grier08a

David Alan Grier
Evolutionary Fervor
IEEE Computer Magazine V41n12(Dec 2008)pp10-12
=EXAMPLES EVOLUTION
Unpredictable changes in communities, careers, Darwin, Business, software, languages, hardware, browsers, ...

Grier09

David Alan Grier
Scanning the Horizon
IEEE Computer Magazine V42n2(Feb 2009)pp8-10
=HISTORY RETAIL SYSTEM UPC BARCODE ECONOMICS SYSTEMS THINKING

Grier09a

David Alan Grier
Bad alignment
IEEE Computer Magazine V42n11(Nov 2009)pp-
=ESSAY STAKEHOLDERS REQUIREMENTS MARKETING PEOPLE Patterson Shewhart Cs372 aaccreditation
Patterson::=identify need; propose solution; demonstrate; close.
Shewhart::=(plan; do;check; analyse ).repeat.

Grier10

David Alan Grier
The Age of accountability
IEEE Computer Magazine V27n5(May 2010)pp6-8
=ESSAY AUTOMOTIVE TOYOTA AUTOSAR TRANSPARENCY ACCOUNTABILITY RISKS
Example of good people unable to solve problems because they did not communicate or cooperate.
There is now a need for transparency.
Automobile software needs software engineering. Hence AUTOSAR.

Grier10a

David Alan Grier
Utter Chaos
IEEE Computer Magazine V43n4(Apr 2010)pp6-9
=HISTORY SCIENCE XRAYS ROENTGEN
It takes time to form an organized and reliable theory.
A new observation often triggers a chaotic phase of theory making and experimentation.
Normally in journals and papers. Xrays discussed in newspapers.
Sometimes the observation is rejected -- cold fusion.
Similarly when learning a discipline.

Grier10b

David Alan Grier
Mental Discipline
IEEE Computer Magazine V43n8(Aug 2010)pp6-8
=ESSAY MATHEMATICS ENGINEERING BLACK-BOXES
What is the value of learning mathematics in a time when most common problems can be easily solved using a computer?
Because "it makes us special and sometimes can be used to discipline the minds of others".

Grier10c

David Alan Grier
The spirit of combination
IEEE Computer Magazine V43n7(Jul 2010)pp-
=HISTORY ENCYCLOPEDIA WIKIPEDIA DIDEROT HYPERLINKS WEB WIKIAATA WIKILACKEY EDUCATION ONTOLOGY

GrierJEtAl10

Jonathon Grier & MIchael Stonebraker & Daniel Abadi & David J DeWitt & Sam Madden & Erik Paulson & Andrew Pavio & Alexander Rasin
Hold the Accusations that limit Scientific Innovation (correspondence)
Commun ACM V53n4(Apr 2010)p7 [ 1721654.1721657 ]
=CORRESPONDENCE GOOGLE MapReduce DBMS
Reply to [StonebrakerEtAl10]
Google did not trample on the toes of others.
But Google's engineers seem to have ignored prior art when developing MapReduce.

Gries78

David Gries
Lecture
NATO Summer School Marktoberdorff 1978 (Germany)
=THEORY TECHNICAL guarded-commands

Gries81

David Gries
The Science of Computer Programming
Springer Verlag NY NY
=TEXT formal guarded-commands

Gries91

David Gries
Teaching Calculation and Discrimination: A More Effective Curriculum
Commun ACMV34n3(Nar 1991)pp44-54. Letters Commun ACM V34n9(Oct 1991)pp16-18 & 91-95 & Commun ACM V35n2(Feb 1992)pp22-26
=ESSAY FORMAL LOGIC MATH EDUCATION
1. p54"The main activity that is supposed to separate engineering from other fields is design: the actual activity of preparing a plans for some object[..] design of proofs[...]".
2. p54"Let us all learn more about calculational techniques and gain skill with them: and let us begin to teach computing using them."

Gries96

David Gries(mailto:gries@cs.cornell.edu)
The Need for Education in Useful Formal Logic
IEEE Computer Magazine V29N4(Apr 1996)pp29-30

GriesSchneider93

David Gries & Fred B Schneider
A Logical Approach to Discrete Mathematics
Springer Verlag NY NY 1993 ISBN 0 -387-94115-0
$44.95 textbook LOGIC calculations MATH CR9407-0412 IEEE Computer (Jul 1994)pp125-126

UCR Bookstore

Discussion on FASE EMail list -September 1994

Gries07

Correction --- see [Grier07c]

GriesSchneider95

David Gries & Fred B Schneider
Teaching Math More Effecively Through Calculational Proofs
Am Math Monthly V102n8(Oct 1995)pp691-697)
=ADVERT CALCULATIONAL LOGIC MATHEMATICS
Advert for [GriesSchneider93]
1. 15 axioms and 4 rules
2. = is transitive, can substitute a free variable,
3. equanimity:
4. if P and (P ≡ Q) then Q
5. and Liebnitz:
  1. E[v:=P]
  2. = <P=Q>
  3. E[v:=Q]
  Where P and Q are expressions and v some variable not found in P or Q and E[v:=P] some expression with every ovccurrence of v replaced by P and E[v:=Q] the same expression with every v replaced by Q.
  Also treats ≡ as an associative (serial) operator, and equals as a parallel operator.
  Unified notation for all quantification, summation, etc:
6. (op var | condition : expression)
  Formal notation is a repository of facts and a means of clarification. It provides rules for judging the soundness of inference and detecting and eliminating ambiguity.

Grenning01

James Grenning
Launching Extreme Programming at a Process-Intensive company
IEEE Software Magazine V18n6(Nov/Dec 2001)pp27-33
=EXPERIENCE SAFETY PROCESS XP vs DOCUMENTATION USECASES MockObjects
how to sell XP.
successful implemented XP but project mothballed!

Grimshaw93

Andrew S Grimshaw<grimshaw@virginia.edu>
Easy-to-use Object-oriented Parallel Processing with Mentat
IEEE Computer magazine V26n5(May 1993)pp39-51
1. p39: "the programmer understands the application domain and can make better data and computation partitioning decisions than the compiler...management of ten-of-thousands of assynchronous tasks, where timing-dependent errors are easy to make, is beyond the capacity of most programmers. Compilers on the other hand are very good at ensuring that events happen in the right order and can more readily and correctly manage communication and synchronisation..."

Grinzo96

Lou Grinzo
Here Be Pluggers
Software Development Magazine (Jul 1996)pp25+26+29+30
plug components together tools+non-programmer generates maintenance nightmares so trench programmers have to mentor the pluggers. The Bubble sort syndrome

Griss95

Martin Griss(moderator)
Panel: Systematic Software Reuse: Objects and Frameworks are not enough [SamadzadehZand95] pp17-18
p17. "Objects are neither necessary nor sufficient for effective reuse."
Chris Jette, Doug Lea, Ivar Jacobsen<ivar@os.se>, Bob Kessler

Griss00

Martin L Griss
My Agent wil call your Agent
Software Development V8n2(Feb 2000)pp43-46
=SURVEY XML HTML HTTP allow autonomous user representative programs to communicate.

GrissPour01

Martin L Griss & Gilda Pour
Accelerating Development with Agent Components
IEEE Computer Magazine V34n5(May 2001)pp37-43
=ADVERT HP AGENTS WEB/NET COMPONENTS MODULE ARCHITECTURE CBSE
Agents : KiviatGraph= mix (autonomous, collaborative, adaptable, knowledgeable, mobile, persistent)

GriswoldEtal06

William G Griswold & Macneil Shonle & Kevin Sullivan & Yuanyuan Song & Nishit Tewari & Yuanfang Cai & Hridesh Rajan
Modular Software Design with Crosscutting Interfaces
IEEE Software Magazine V23n1(Jan/Feb 2006)pp51- 60
=CASESTUDY ASPECTS INTERFACES CONTRACTS AspectJ
Claims that defining interfaces for aspects: what the provide and what they require, makes the design clearer and simpler.

GriswoldGriswold83

?? Griswold & ?? Griswold
The Icon Programming Language
Prentice Hall International 1983
=IDEA non-sequential LANGUAGE

GriswoldHansonKorb81

?? Griswold & Les Hanson & ?? Korb
Generators in ICON
ACM TOPLAS V3n2 (Apr 1981)pp144-61?
=IDEA non-sequential ICON

GriswoldNotkin95

William G Griswold & David Notkin
Architectural Tradeoffs for a Meaning-Preserving Program Restructuring Tool

Grosberg93

John A Grosberg
Comments on Considering "Class" Harmful (Letter )
Comm ACM V36n1(Jan 1993)pp113-114
=IDEA OBJECTS CLASSES abstraction object oriented
1. ref to letter from Winkler92 (aug 1992 pp128-130).
2. cf BaclarskiIndurkhya94
3. COV vs POV (Conceptual vs Programming View).
4. Distinguish abstract classes which have subclasses from concrete classes that have instances. An abstract class does not have instance. A concrete class may not have subclasses.
5. Example::=
  Net{
  1. abstract_complex>=={complex,abstract_real}
  2. abstract_real>=={real,abstract_rational}
  3. abstract_rational>=={rational,abstract_integer}
  4. abstract_integer>=={integer,natural}
  5. 1 ∈ natural ==>abstract_integer==>abstract_rational...
  6. 1+2j ∈ complex.
    }

Gross06

Christian Gross
Ajax Patterns and Best Practices
Apress Berkeley CA 2006 ISBN 1590596161
=UNREAD HANDBOOK AJAX NONSEQUENTIAL JAVASCRIPT WEB/NET

Grossman11

Lisa Grossman
Study: Math Skills Rely on Language, Not Just Logic
Wired Science (Feb 8 2011) [ http://www.wired.com/wiredscience/2011/02/homesigning-numbers/ ]
=REPORT EXPERIMENT SIGNERS NUMBERS COUNTING ARITHMETIC PEOPLE PSYCHOLOGY
This reports on a recent experiment in Nicuagua by Elizabet Spaepen. It shows that if you don't know the words for the numbers you can not communicate a number (as in the number of sheep) correctly.
Memorizing the mnemonic sequence (one,two, three, ...) provides pegs to hang observations on...

GrottkeTrivedi07

Michael Grottke & Kishor S Trivedi
Fighting Bugs: Remove, Retry, Replicate, and Rejuvenate
IEEE Computer Magazine V40n2(Feb 2007)pp107-109 + letter V40n5(May 2007)pp6-7
=SURVEY DEBUGGING
Different types of bugs need different strategies.
Bohrbugs: use testing to find and remove faults that consistently manifest bugs in well defined conditions.
Mandelbugs: No replication.fault->internal error-> error propagation-> platform interactions -> chaotic behavior. So can often avoid bug by retrying the software. Can try replicated software in different platforms.
Age-Related Bugs: Rejuvenate = restart. Same two type: Bohr and Mandel.
In letter, Lawrence Stabile, criticizes the "Rejuvenate" tactic as not an "engineering solution".

Gruman90

Galen Gruman (staff editor)
Bug Disrupts AT&T Service
IEEE Computer(Update) V23n3 p84(Mar 1990)
=EXAMPLE RISKS

Gruman91

Galen Gruman (staff editor)
Interview with Richard De Millo(NSF)
IEEE Software(In the News) V24n1 pp92-93(Jan 1991)
"need to find problems"

Grune77

?? Grune
A View of Coroutines
ACM SIGPLAN notices Jul 77 pp75-81
=THEORY non-sequential TECHNICAL

Grunske08

L Grunske
Specification patterns for probabilistic quality properties
ACM/IEEE 30th Conf ICSE'08 Software Engineering(May 2008)pp31-40
=THEORY =DEMO PROBABILISTIC VERIFICATION QUALITIES PCTL* CSL TEMPORAL LOGIC ProProST PATTERN LANGUAGE STRUCTURED ENGLISH GRAMMAR
English Subset [ samples/Grunske08.html ] grammar.

GruschkeJorgensen08

Tanja M Gruschke & Magne Jorgensen
The Role of Outcome Feedback in Improving the Uncertainty Assessment of Software Development Effort Estimates
ACM TOSEM Trans Software Eng & Methodology V17n4(Apr 2008)#20pp1-35 [ 13487689.13487693 ]
=EMPIRICAL ESTIMATION FEEDBACK
Letting programmers see their estimation errors does not help them improve their future estimates -- especially if they use intuitive prediction methods.

Gsoedl00

Jacob Gsoedl
Can You Implement COM Components Using Java
Dr. Dobbs Journal #313(Jun 2000)pp119-120+122+124+126
=DEMO TECHNICAL IDL ASP

GuaspariMarceauPolak90

David Guaspari & Carla Marceau & Wolfgang Polak
Formal Verification of Ada Programs
IEEE Trans Software Engineering SE-V16n9(Sep 1990)

Guerevich87

Yuri Guerevich
Logic and the Challenge of Computer Science
pp1-57 in Borger88

Guerra-FilhoAloimonos07

Gutenberg Guerra-Filho & Yannis Aloimonos
A Language for Human Action
IEEE Computer Magazine V40n5(May 2007)pp-
=IDEA PARALLEL GRAMMAR MODELS HUMAN MOTION
Use a parallel synchronous grammar system to describe the motions of linked limbs/joints.

GuerrauiFayad99

Rachid Guerraoui & Mohamed E Fayad
OO Distributed Programing Is Not Distributed OO Programming
Commun ACM V41n4(Apr 1999)pp101-104
=THEORY OBJECT-ORIENTED WEB
It is not possible or safe to hide the fact that an object is on a separate processor.

Guest95

Ronald A Guest(ron.guest@rss.dl.nec.com)
Blame It on the Market(letter)
IEEE Software Magazine(Nov 1995)pp4
[WilliamsD95] [JohnsonB95]

GuilfordRuggScott02

Sheila Guilford & Gordon Rugg & Niall Scott
Pleasure and Pain: Perceptual Bias and its Implications for Software Engineering
IEEE Software Magazine V19n3(May/Jun 2002)pp63-69
=EXPERIMENT PSYCHOLOGY PEOPLE USER
peak_end_effect::=" People's feelings about an unpleasant medical procedure tends to be based on a combination of the peak and ending pains. Not the averages!".
Software experiment 1, 10 students: dissatisfaction afterwards is best correlated with the average satisfaction in 5 students and with peak-end in 5 cases. Different!
software experiment 2, 14 students visual Lickert
Software experiment 3, 11 students.
Peak+end unpleasantness predict global in only 5 out of 25 cases the average is better in the rest!
Peak pleasant+end predicts 50% of the time better than average.
Note. Absence of standard statistical methods to analyze data; If you have two random predictors then 50% of the time one is better than the other -- as in this case. No scattergrams or correlations. However quick calculations show that peak, final and average are all correlated with the global unpleasantness and with each other, r=.0.7..0.8. Conclusion: there was a common user dependent factor driving all ratings: user skill, etc.

Gumb89

Raymond D Gumb
Programming Logics: An Introduction to Verification and Semantics
John Wiley & Sons NY NY 1989
natural deduction
introduction to hoare axioms and dentational semantics

Gunter92

Carl A Gunter
Semantics of Programming Languages:Structures and Techniques
The MIT press Cambridge MA 1992
Foundations of Computing Science Series
ISBN 0-262-07143-6
theory semantics languages types

Gunter00

Carl A Gunter
Abstracting Dependecies between Software Configuaration Items
ACM TOSEM V9n1(Jan 2000)pp94-131
=THEORY SCM make IDE
P-nets:=Petri_net with acyclic & unique_producer & nonempty_inputs & nonempty_outputs & places are inputs or ouputs to one or more events.

GunterGunterJacksonZave00

Carl A Gunter & Elsa L Gunter & Michael A Jackson & Pamela Zave
A Reference Model for Requirements and Specifications
IEEE Software Magazine V17n3(May/Jun 2000)pp37-43
=THEORY REQUIREMENTS SPECIFICATION REALITY WRSPM
W, R, S refer to the environment. S, P, M refer to the system.
Actual expression of descriptions can take many forms.
Designated terms -- typically designate states, events, and/or individuals. e -- controled by environment, s -- controled by system.
Shared terminology.
Three properties of adequacy and consistency define a contract between the buyer and seller of the software.
Similar, relative, properties constrain the specification and imply the three fundamental properties.
[ GunterGunterJacksonZave00.html ]
See also [ZaveJackson97b]

GunterMitchellNotkin96

Carl Gunter & John Mitchell & David Notkin
Strategic Directions in Software Engineering and Programming Languages
ACM Computing Surveys V28n4(Dec 1996)pp725-737
=SURVEY

Guptaetal96

Deepak Gupta & Pankaj Jalote & Gautam Barua
A Formal Framework for On-line Sofware Version Change
IEEE Trans Soft Eng VSE22n2(Feb 1996)
online MAINTENANCE THEORY

Gurevich88

Yuri Gurevich
Logic and The challenge of Computer Science
in [borger88]
=THEORY FORMAL LOGIC COMPUTING

GurfinkelDevereuxChechik02

Arie Gurfinkel & Benet Devereux & Marsha Chechik
Model Exploration with temporal logic query checking
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp139-148
=DEMO TOOL MODEL CHECKING CTL QUERIES
Given a finite state model enable the faster answering of questions like: what property is always true with p.
Cruise control example.
refers to Chan's original idea.
Developed to [GurfinkelChechikDevereux03]

GurfinkelChechikDevereux03

Arie Gurfinkel & Marsha Chechik & Benet Devereux
Temporal Logic Query Checking: A Tool for Model exploration
IEEE Trans Software Engineering V29n10(Oct 2003)pp898-914
Based on [GurfinkelDevereuxChechik02]
=IDEA MODAL TEMPORAL LOGIC CTL Placeholders DeMorgan Algebra TLQSolver χ\_Chek Cruise control SCR CSCI656
Instead of checking a CTL for truth/falsity: compute the formula that "fill in the blanks" in a CTL formula:
AG(?1) -- what is always and forever true?
AX(?1{p,q}) -- what formula on p and q (only) is always true in the next step?
AG(?1 /\ AX?2) -- what pair of formulas ...

GursaranRoy01

Gursuran & Gurdev Roy
On the Applicability of Weyuker Property 9 to Object-Oriented Structural Inheritance Complexity Metrics
IEEE Trans Software Engineering V27n4(Apr 2001)pp381-384
=THEORY Object-Oriented METRICS GRAPHS
Shows that graph based inheritance metrics may not increase by concatenation.

GuttagHorning91

John V Guttag & James J Horning
Introduction to LCL: A Larch/C Interface Language
Report 74 from Systems Research Center of Digital Equipment Corpn(24th Jul 1991)
=REPORT LARCH TOOL LANGUAGE
1. Specifications as firewalls between modules in C. requires r modifies m ensues e::=for all x(if r(x) then terminates and m(x,x') and e(x,x')). pointers! x^ x' pre and post values
  July 1993: LCLint is available on internet

GuttagHorning93

John V Guttag & James J Horning
LARCH: Languages and tools for formal specifications
Springer Verlag NY NY 1993 ISBN 0-387-94006-5 CR 9405-0262
=TEXT LARCH TOOL LANGUAGE

Guzdial95

Mark Guzdial<guzdial@cc.gatech.edu>
Centralized Mindset: A student Problem with Object-Oriented Programming
Papers of the 26th SIGCSE Tech Symposium on CS Ed SIGCSE Bulletin V27n1(Mar 1995)pp182-185
=EDUCATION PEOPLE OBJECT-ORIENTED vs FUNCTIONAL
Tendency for students to pack all the logic and structure into a single leader object rather than use communcation and shared responsibillity.
Claims result is less reusable.
Solutions: Motivate, evaluate alternatives, teach class library, provide experience

GyimothyFerencSiket05

Tibor Gyimothy & Rudolf Ferenc & Istvan Siket
Empirical Validation of Object-Oriented metrics in open source software for fault prediction
IEEE Trans Software Engineering V31n10(Oct 2005)pp897-910
=EXPERIENCE =STATISTICS Mozilla Bugzilla metrics defects coupling LOC
Larger classes (LOC) had more bugs, as did classes with couplings (CBO) to other classes.
Cohesive methods helped but not to identify bad classes.
Other metrics did not help predict fault proneness.

Haagetal96

Stephen Haag & M K Raja & L L Schkade
Quality Function Deployment usage in Software development
Comm ACM V39n1(Jan 1996)pp41-49
=IDEA QFD SURVEY QUALITY PURPOSE DESIGN

HadarLeron08

Irit Hadar & Uri Leron
How Intuitive is Object-Oriented Design
=EXPERIMENT STUDENTS LEARNING OO DESIGN
Commun ACM V51n5(May 2008)pp- 2008)#7pp41-46
Distinguishes two different modes of thought: S1 and S2.
S1: fast, automatic, effortless, unconcious, and inflexible.
S2: slow, concious, effortful, but relatively flexible.
S2 acts a s amonitor and critic of S1.
Inheritance is backward(S1).
Surface features (S1) lead to bad OODs.
Confusing abstract and concrete classes (S1).
Identifying coding with development (S1).
It is hard to replace S1 with S2.

Hager89

James A Hager
Software Cost Reduction Methods in Practice
IEEE Trans Soft Eng VSE-15n12(Dec 1989)pp1638-1644
=EXPERIENCE SCR maintanability by information hiding+living documents
not clear if feasible without tools
10% reduction in costs/time for upgrade

HaggeLappe05

Lars Hagge & Katherine Lappe
Sharing Requirements engineering experience using patterns
IEEE Software Magazine V22n1(Jan /Feb 2005)pp24-31
=Advert Requirements engineering people patterns Organize the specification to parallel the structure of the project. Teams appoint one member as an author. Authors coordinated by the requirements engineer. Help stakeholders write specifications by giving them guidelines based on the prefered process by analysts,
Record requirements on index cards and classify them.
Link components to requirements by checklists.
Fig6:UML model for pattern mining/database.

HalaszSchwartz90

Frank Halasz & Mayer Schwartz
The Dexter Hypertext Reference Model
Proceedings of the Hypertext Workshop NIST Gaithersburg Md Jan 16-18 1990
NIST Special Publication 500-178 March 1990 pp95-133
=EXPERIENCE FORMAL Dexter WWW/NET Z

HalaszSchwartz94

Frank Halasz & Mayer Schwartz
The Dexter Hypertext Reference Model
Comm ACM V37n2(Feb 1994)pp30-39
=ADVERT Dester WWW/NET
1. UID: Unique Identifiers - uniaue across entire univers of discourse
2. Links: From, To, Bi-directional, None
  Figure 5 p35. SGML interchange format

HalbertO'Brien87

Daniel C Halbert & Patrick D O'Brien
Using Types and Inheritance in Object-Oriented Programming
IEEE Software V4n5(Sep 1987)pp71-79
=DEMO structures OBJECT-ORIENTED TECHNICAL CODE

HaleParrishDixonSmith00

Joanne Hale & Allen Parrish & Brandon Dixon & Randy K Smith
Enhancing the COCOMO Estimation Models
IEEE Software Magazine V17n6(Nov/Dec 2000)pp45-49
=EXPERIMENT COCOMO PROCESS
The intensity, concurrency, and fragmentation of the tasks in a process significantly change the productivity.
High intensity -- one tight focussed task -- is good.
High concurrency -- many working on one task at a time -- is good.
Fragmentation over many tasks is bad.
Gives adjustments to COCOMO to allow for these factors.

Haley96

Thomas J Haley
Software Process Improvement at Raytheon
IEEE Software Magazine V13n6(Nov 1996)pp33-41
=EXPERIENCE IMPROVEMENT

Hales08

Thomas Hales
Formal Proof
Notices of the American Mathematical Society V55n11 (Dec 2008) [ tx081101370p.pdf ]
=EXAMPLES HOL Light FORMAL PROOFS MATHEMATICS ZFC TYPES
Good discussion of the philosophy of formal proofs and HOL Light in particular.
Difficult theorems can have 1728 pages for an informal proof and take decades to write.
Provide formalizations can take years.
DeBruijn_factor::=Length of a formal proof/Length of a conventional proof.
List of 12 "real" theorems that have got formal proofs.
Description of HOL_light.
Discussion of full automation and automated discovery of theorems.
Coq::proof_assistant= See http://coq.inria.fr/.
HOL_light::proof_assistant= See http://www.cl.cam.ac.uk/~jrh13/hol-light/.
Isabelle::proof_assistant= See http://isabelle.in.tum.de/.
Mizar::proof_assistant= See http://mizar.org/.
ProofWeb::proof_assistant= See http://prover.cs.ru.nl/login.php.
QED::manifesto= See http://www.cs.ru.nl/~freek/qed/qed.html.

HaleyLaneyMoffettNuseibeh08

Charles B Haley & Robert Laney & Jonathon Moffett & Bashar Nuseibeh
Security Requirements engineering: A Framework for Representation and Analysis
IEEE Trans Software Engineering V34n1(Jan/Feb 2008)pp133-153
=CASESTUDY SECURITY REQUIREMENTS METHOD
Describes a complex process and set of languages that work from security goals, to assets that are to be protected (compare [Stoneburner06] ), to requirements, thence to arguments for a particular system design satisfying the requirements, and so to the assumptions that can be rebutted, and the mitigation of the rebuttals and so forth.
Security requirements are non-functional requirements and are closely related to the context of the machine being designed.
Must expose assumptions about the machine and its context.
Arguments that the system satisfies the requirements lead to lists of assumptions that can be challenged (WHY?) and rebutted.
Rebuttals lead to mitigators that change the context and/or the requirments. In turn the mitigators can be rebutted, and so on.
Hence an iterative process making the design more secure.
Uses Jackson Problem Frames ( [Jackson95c] [Jackson01] ), simplified [Toulmin79] arguments, Propositional logic, and a causal logic based on
Event1 shall cause Event2.
Outer_argument::=Formal logic showing the design satisfies the requirement and exposing assumptions
Inner_argument::=Explores assumptions in terms of rebuttals and mitigators.
Process involves engineers and stakeholders in intense and fruitful discussion.
(dick)|-Compare [Lakatos76] model of the mathematical process. Also methods used to achieve safety.

HalfakerRiedl12

Aaron Halfaker & John Riedl
Bots and Cyborgs: Wikipedia's immune system
IEEE Computer Magazine V45n3(Mar 2012)pp79-82
=OBSERVATION Wikipedia TOOLS BOTS CYBORGS EVOLUTION
Clear evidence of software evolving rather than BDUF.

Hall81

John Hall
System Development Methodology
Learmonth & Burchet Management Systems Ltd London England Mar 1981
=BLURB SSADM PQRST

Hall90

Anthony Hall
Seven Myths of Formal Methods
IEEE Software V7n5(Sep 1990)pp11-19
=EXPERIENCE FORMAL MYTHS
1. FM:="Formal Methods".
2. 1. FM can guarantee that software is perfect
3. 2. FM are all about program proving
4. 3. FM are only usefule for safety critical systems
5. 4. FM require highly trained mathematicians
6. 5. FM increase the cost of development
7. 6. FM are unacceptable to users
8. 7. FM are not used on real, largescale software

Hall96

Anthony Hall(Praxis mailto:jav@praxis.co.uk)
What is the Formal methods debate about?
IEEE Computer Magazine V29N4(Apr 1996)pp22-23
=EXPERIENCE FORMAL QUALITY COST
1. 10 years practical use of FM
2. we used to argue that FM were an expensive but necessary part of getting correct software
3. Now we can say that they are the cheaper way to produce complex correct software
4. AirTraffic Control system, CDIS 150 user-level operations, 1000 pages of spec, 200KLOC, productivity as good or better than without - found errors early
  Lockheead avionics software C130J using Spark(Ada) Core(SPC) - added quality and saved testing money. SW correct by construction.
  Correct qn: What can FM do to improve quality and decrease cost.

Hall96a

Anthony Hall(Praxis mailto:jav@praxis.co.uk)
Using Formal Methods to develop an ATC Information System
IEEE Software magazine V13n3(Mar 1996)pp66-76 reprint in [HincheyBowen99] pp207-229
1989-1993 Air Traffic Control GUI display information system(CDIS) for the London Area 197KLOC(C) 15.5Kperson-days 13LOC/day 11 faults/LOC into testing 150 faults after delivery(0.75faults/KLOC)
=EXPERIENCE FORMAL ER DFD VDM VVSL CSP FSM CCS
HCI spec was weakest + needed more informal explanation diagrams etc + problem in gettting an overview [Barlas96]

Hall97

Anthony Hall
What's the Use of Requirements Engineering? [RE'97]
=KEYNOTE REALITY SYSTEM USER
Keynote speech stresses need to focus on the environment and talk with users and experts and learn their world
Trap of designing system structure or collections of objects in new system

HallChapman02

Anthony Hall & Roderick Chapman
Correctness by Construction: Developing a Commercial Secure System
IEEE Software Magazine V19n1(Jan/Feb 2002)pp18-25
=EXPERIENCE CORRECTNESS SECURITY FORMAL Z CSP MODEL PREDICTABLE PROCESS TOOLS COTS MXI Multos Spark Ada95 GUI C++ MSFC
CA:="Certification Authority", Certifying smart cards.
Process with 17 deliverables
Handled risks by trailblazing prototypes.
Rigorous static code checking: BoundsChecker and PC-Lint.
Avoided unit testing as expensive and ineffective.
Used incremental builds: many real tiny systems with tests derived from specification and automated (Rational Visual test)
Defects introduced mainly in spec and coding.
Coding Defects almost entirely removed in code reviews and developer testing.
Spec errors removed in all later phases, mainly in architecture and code.
In operation only 4 defects: 3 from coding and one from spec. Out of 100 KLoC.
Productivity: 28 lines of code per day. Work: requirements 2% specification+architecture 25%, code 14%, Test 34%, fault fixing 6%, management 10% training etc 9%.
achieved 0.04 defects per thousand line of delivered code.

HallEtAl08

Tracy Hall & Helen Sharp & Sarah Beecham & Nathan Baddoo & Hugh Robinson
What do we know about developer motivation
=SURVEY =METAANALYSIS MOTIVATION
IEEE Software Magazine V25n4(Jul/Aug 2008)pp92-94
Developers motivation is not a simple thing but complex and includes these specific ones: challenge, change, benefit, problem solving, team work, science, experiment, and best practices.

HallEtAl11

Tracy Hall & Sarah Beecham & David Gray & Steve Counsell
Developing fault-prediction models: what the research can show industry
IEEE Software Magazine V28n6(Nov/Dec 2011)pp96-99
=SURVEY 206 MODEL PREDICTING DEFECTIVE MODULES
70% accuracy possible. Some better, some worse.
Naive Bayesian and logistic regression seem to be best.
Combining code metrics, change data, data about developers.
LOC surprisingly good!
Pointers to best models.

Hale-Evans04

Ron Hale-Evans
Kennexions GBG Home Page
Link [ http://kennexions.ludism.org/ ] TBA
Also see
Ludism::= See http://ludism.org/ , the philosophical study of games
=IDEAS Glass Bead Game Wiki Kennexions Bliss Loglan

HallRapanottiJackson08

Jon G Hall & Lucia Rapanotti & Michael A Jackson
Problem Oriented Software Engineering: Solving the Package Router Control Problem
IEEE Trans Software Engineering V34n2(Mar/Apr 2008)pp226-241
=DEMO POSE METHOD ENGINEERING DESIGN ANALYSIS ARGUMENTS RATIONALE ITERATION PROCESS
POSE::="Problem Oriented Software Engineering", based on Jackson's Problem Frames [Jackson01] , using informal or formal satisfaction arguments that target stakeholders, refinement, iteration, backtracking, etc.,
Models a problem+solution as a set of Domains+Solution+Requirements
```
 	D[1],...D[2], S |- R
```
A Gentzen Sequent!
Domains have a name(N) and description(E) that mentions phenomena: controlled(c), observed(o), and unshared(p):
```
 	D(p)[o]^c = N : E
```
Solutions are a domain.
Requirements have a name and description that constrains(c) certain phenomena and refers (r) to other phenomena:
```
 	R[r]^c = N : E.
```
Progress is made by transforming problems (like inference rules in SOS or Natural Deduction). Each transformation has NAME and an adequacy argument.
Arguments have a Justification, Includes, Concerns, Phenomena, and Resulting Problems (if any).
Sample of Problem Transformations
1. CONTEXT INTERPRETATION Justify a new description of a domain.
2. REQUIREMENT INTERPRETATION Justify an expanded requirement
3. SOLUTION INTERPRETATION Justify the expansion of the solution. Example: nSep. Separation into independent parts. Example: applying the MVC pattern. Example: Using an analogic model.
4. SEPARABLE PROBLEM Explain how one problem becomes a set of independent problems
5. PROBLEM PROGRESSION Changes requirements
6. SOLUTION EXPANSION Moves known components into environment and generates a set of problems to be solved.
7. Backtracking. Justify the abandonment of a previous solution and replacement by a new one.
Has been tested in a safety critical system -- avionics -- using Alloy.
Development involves learning about the context of the problem as well as about the requirements and solutions.
Justifications must satisfy the stakeholders. Different stakeholders will need different justifications.
Development is an iterative activity. Concerns lead to backtracking.
HalleVillemaireCherkoui09
1. Sylvain Halle & Roger Villemaire & Omar Cherkaoui
2. Specifying and validating data-aware temporal web service properties
3. IEEE Trans Software Engineering V35n5(Sep/Oct 2009)pp669-683
4. =THEORY TOOL LANGUAGE TEMPORAL LOGIC DATA WEB SERVICES CTL-FO+ PSPACE-complete PROOF

HalpernParkes11

Joseph Halpern & David C Parkes
Journals for certification, conferences for rapid Disemination
Commun ACM V54n8(Aug 2011)pp36-38 [ 1978542.1978555 ]
=META CONFERENCES JOURNALS COMPUTER SCIENCE
In computer science, for many decades conference papers have been the place to look when doing research. Journals are less important. In Other fields journal publications are the sin qua non. Conference presentations and proceedings almost a form of advertising. The real sieving of the good from the bad is by publication in a top journal.
This paper proposes a way for CSE to change to fit normal form.

HalpernZuck92

Joseph Y Halpern & Lenore D Zuck
A Little Knowledge Goes a Long Way: Knowledge-Based Derivations and Correctness Proofs for a Family of Protocols
J. ACM V39n3(Jul 1992)pp449-478 [CR] (Oct 1993)
=THEORY PROVING REFINEMENT PROTOCOLS KNOWLEDGE MODAL LOGIC
Argues for the high level design of inefficient solutions that can be shown to be 100% correct and then their refinement into efficient solutions that implement th high level ones.
Derives the Alternating Bit Protocol and Stenning's protocol for the Sequence Transmission problem.
Defines data flow and how to implement it using unreliable communication. Safety: output sequence is prefix of input sequence. Liveness: all inputs are ultimately output (given fairness).

HalpinEtal

Terry Halpin and others
Object Relation Modeling [ http://www.orm.net/ ]
=SITE DATA CONCEPTUAL MODEL METHOD FACTS OBJECTS CONSTRAINTS Visio .NET ORM ERD RELATIONAL SCHEMA SQL

HamilPopstojanova09

Maggie Hamil & Katerina Goseva-Popstojanova
Common trends in fault and failure data
IEEE Trans Software Engineering V35n4(Jul/Aug 2009)pp484-496
=EMPIRICAL CASESTUDIES GCC NASA FAULTS = FIXES vs FAILURES
One failure is fixed by changes in more than one file 60% of the time. More than 2 files, 30% of the time.
Pareto principle: 20% of the files contain nearly 80% of the fixes in GCC. 47% of the files have 100% of the fixes.
NASA groups files into configuration items. 90% of failures lead to fixes within one item.
main reasons: 30% requirements, 25..30% coding, 15% data, ...
interactions cause problems.

Hamilton95

Scott Hamilton
Evolving the HPCCI(from NRC/CSTB 1995 Report)
IEEE Computer Magazine V28n6(Jun 1995)pp79-81
=ADVERT HPCCI

Hamilton01

Scott Hamilton
Formalizing Concept Maps
IEEE Computer Magazine V34n1(Jan 2001)pp66+68 (Figure and Side-bar)
=IDEA GRAPHIC LOGIC MODEL RKF USER vs FORMAL
RKF := Rapid Knowledge Formation.
Concept maps are informal concept graphs or semantic nets.

HamiltonZeldin76

M Hamilton & S Zeldin
Higher Order Software - A Methodology for Defining Software
IEEE Trans SE VSE2n1(Mar 1976)pp25-32
=DEMO METHOD HOS APOLLO CORRECTNESS FUNCTIONAL DECOMPOSITION
Quoted as Appendix II in [Martin85].
Compare with [HamiltonHackler08]

HamiltonHackler08

Margaret H Hamilton & William R Hackler
Universal Systems Language: Lessons Learned from Apollo
IEEE Computer Magazine V41n12(Dec 2008)pp34-43
=HISTORY CORRECT DESIGN EVOLUTION HOS USL FUNCTIONAL DECOMPOSITION
Apollo space mission 1961-1975.
Functions and maps decomposed using three structures: Join, Include, Or. (=~= ";", "&", "|" in MATHS).
Theories of correctness and tools to check such decomposition.
Still blindsided by events. Reality had unexpected properties.
The power of a global reset when an inconsistent state occurs.
Asynchronous process and asynchronous software,
(dick)|-further developed into language AXES, tool USE.IT and company HOS in the 1980's.

Hamlet94

Dick Hamlet
Foundations of Software Testing: Dependabillity Theory
SIGSOFT'94 Proc 2nd ACM SIGSOFT Symp on Foundations of Software Engineering & ACM SIGSOFT Software Engineering Notes V19n5(Dec 1994)pp128-139
=THEORY RISKS
1. dependability::=probable correctness::=the degree of confidence that some software is reliable under all circumstance and at any time.
2. reliability::=the probability of correct behavior under given operating conditions for a given time period.
  Nice to quantify the feeling that lots of passed tests somehow tell you the the software is good.
  p133: "A physical-system hazard rate is a function of time because the system changes. Software changes only if it is changed. Hence a time-dependant failure intensity is appropriate for describing the development process, or maintenance activities"
  using analyis vs operational profile to measure the likelihood of a fault showing up if it is present. Using other randomized tests to show that failure is actually unlikely in the same operational profile. Hence conclude that since faults are likely to cause the tests to fail and that the tests did not fail... conclude that the faults are 'not in hiding'

Hamlet98

Dick Hamlet
What can we learn by Testing a program
ACM SIGSOFT International Symposium on Software Testing and Analysis(ISSTA) 1998 Software Engineering Notes V23n2(Mar 1998)pp50-52
=SURVEY THEORY
relyabl::=a test set that will expose an error
relyabl_subdomains::=a set of subsets of the input space SS such that if behavior is not equal to spec then for some S:SS all inputs in S are discrepant
[Howden76]

Hamlet02

Dick Hamlet
Continuity in software systems
Proc ISSTA02 & ACM SIGSOFT Software Engineering Notes V27n4(Jul 2002)pp196-202
=THEORY CONTINUITY MATH CODE not SPECIFICATION
Compare [Hamlet98].
How small changes in input effect output.
If code computes a polynomial then a finite number of tests can prove that the code computes the correct polynomial.
Combine proof of properties of code (by symbolic execution/tracing) with testing to demonstrate correctness.

HandMonnilaSmyth02

David Hand & Haikki Mannila && Padhraic Smyth
Principles of data mining
MIT Press 2001 ISBN 0-262-08290-X QA76.9.D3343 H38 2001
=TEXT THEORY DATA MINING STATISTICS MATHS NEURAL

HanEtal00a

Yan Ha n & Xu Chun-gen & Zhang Gong-xuan & Liu Feng-yu
Constraint specification for object model of access coontrol based on role
ACM SIGSOFT Software Engineering notes V25n2(Mar 2000)pp60-64
=PATTERN FORMAL UML LOGIC
Dynamic roles form a hierarchy

HanEtal00b

Yan Han & Liu Fengyu & Zhang Hong
An object-oriented model of access coontrol based on role
ACM SIGSOFT Software Engineering notes V25n2(Mar 2000)pp64-68
=PATTERN UML

Hanks06

Brian Hanks
Student Attitudes toward Pair Programming
ACM SIGCSE Bulletin V38n3(Sep 2006) & proc ITiCSE 2006 pp113-
=POLL 115 STUDENTS 3 INSTRUCTORS PAIR-PROGRAMMING PEDAGOGY
1..7 point Lickert scale on 4 questions: "I like pair programming",... 7="strongly agree"
Median students agree (score =5 or 6).
Similar scores accross genders.
But one instructor had students who gave (on average) a lower score, especially if they were female -- 3 female graduate students in particular. But could be an observer effect (cognitive dissonance).

Hannaetal90

F. Keith Hanna & Neil Daeche & Mark Longley
Specification and Verification Using Dependent Types
IEEE Trans Software Engineering SE-V16n9(Sep 1990)
=THEORY SPECIFICATION TYPES V&V

HannaM93

Mary Hanna
Reengineering aims for Legacy Salvation
IEEE Software Magazine (Sep 1993)p41-48
=POLL ENGINEERING TOOLS REQUIREMENTS
1. 1. Capture data defintions
2. 2. Identify problem code
3. 3. Support Version Control
4. 4. Capture Data Models
5. 5. Analyze data flows and logic
6. 6. Capture process model
7. Usage(p42)
8. debug, Test, change management
9. pp44-45+47: Table of 79 vendors selling reeng tools!

HannaM95

Mary Hanna
Farewell to Waterfalls
IEEE Software Magazine (May 1995)pp38-46
=ESSAY NONSEQUENTIAL PROCESSES RAD TOOLS

HannayEtAl10

Jo E Hannay & Erik Arisholm & Harals Engvik & Dag I K Sjoberg
Effects of Personality on Pair Programming
IEEE Trans Software Engineering V36n1(Jan/Feb 2010)pp61-80
=EXPERIMENT PSYCHOLOGY PEOPLE PAIR PROGRAMMING PERSONALITY TECHNICAL SKILL KNOWLEDGE STATISTICS
Surveys models of personality. Selects the big 5 factors not MBTI.
Personallity is not as important as expertise for productivity when pair programming.

HannaySjobergDyba07

Jo E Hannay & Dag I K Sjoberg & Tore Dyba
A Systematic Review of Theory use in software Engineering Experiments
IEEE Trans Software Engineering V33n2(Jan 2007)pp87-107
=SURVEY SCIENCE?
103 papers. 25 use some theory. 40 theories.

Hansen94

Gregory A Hansen
Tools for Business-Process Reengineering
IEEE Software Magazine V11n5(Sep 1994)pp131-133
=ADVERT DFD SIMULATION TOOL

Hansen96

Gregory A Hansen(mailto:73024.542@compuserve.com)
Simulating Software Development Processes
IEEE Computer Magazine V29N1(Jan 1996)pp73-77
=SIMULATION PROCESS LIFE-CYCLE MANAGEMENT TOOL(Extend+BPR)

Hansen06

Kai T Hansen
Project Visualization for Software
IEEE Software Magazine V23n4(Jul/Aug 2006)pp84-92
=DEMO MANAGEMENT PROJECT COLOR GRAPHICS UML PROCESS STATUS BLUEPRINT
Idea: publish project status data using colored architecture diagrams.
Figure 8 is a good example of a bad use case diagram.

HansenRavnRischel91

Kirsten M Hansen & Anders P Ravn & Hans Rischel
Specifying and Verifying Requirements of Real Time Systems
ACM SIGSOFT'91 Conf on Software for Critical Systems: Software Eng Notes V16n5(Dec 1991)pp44-54
republished IEEE Trans SE-19n1(Jan 1993)pp41-55
=DEMO TIMING REALITY Requirements SYSTEM LOGIC
1. "1. An application domain system model of the equipment and its intended environment of use is defined. This is a dynamic system model, and defines the overall states of the system as functions of time. Requirements are constraints on this model." 2. control model 3. design model. Interval logic(predicates define durations of states) formal

Hanson96

David R Hanson
C interfaces and Implementations:techniques for creating reusable software
Addisson Wesley Longman 1996 ISBN0-201-49841 CR9709-0633 D.2.2
=TEXT information hiding in C

Haque95

Tani Haque<tani@sql.com>
Effective Parallel Development
Software Development(Sep 1995)pp43-48
=ARTICLE

Harandi97

Medhi Harandi(ed)
Proceeding of the 1997 Symposium on Software Reusability -- -- --(SSR'97)
ACM SIGSOFT Software Engineering Notes V22n3(May 1997)
=PROCEEDINGS REUSE

HardgraveArmstrong05

Bill C Hardgrave & Deborah J Armstrong
Software Process Improvement: It's a Journey, not a Destination
Commun ACM V48n11(Nov 2005)pp93-96 CR 0611-1154
=EXPERIENCE IMPROVEMENT vs CMM
It took 4 years to move from CMM Level 1 to level 2.
In the process installed a common methodology throughout the organization.
Measurable improvements:customer satisfaction, schedule deviations, budget deviations.
Lessons:=
1. Need management guidance and support from start to finish.
2. Engage the members.
3. Use well-respected team members to lead the process.
4. MEASURE from day 1
5. SPI is a project and needs resources.
6. Focus on continuous improvement rather than meeting the next level by a given deadline.
7. Fit the improvement to the organization.
Negative review by Phillip Laplante CR 0608-0838
Neutral review by C Bayrak CR 0609-0941

Harel79

David Harel
First Order Dynamic Logic
Springer Verlag 1979 (PhD Thesis MIT 78)
=THESIS regular logic structure

Harel86

David Harel
Statecharts: A Visual Approach to Complex Systems(revised)
Report CS86-02 Dept App Maths Weizman Inst Science Rehovot Israel March 1986
=THEORY STATECHART STD graphic formal dynamics statecharts Reality

Harel88

David Harel
On Visual Formalisms
Commun ACM v31n5(May 1988)pp514-530
=THEORY STATECHART STD graphic formal dynamics state-charts

Harel92

David Harel
Biting the Silver Bullet: Toward a Brighter Future for System Development
IEEE Computer Magazine V25n1(Jan 1992)pp8-20 CR9304-0261"Needs an example"
=ESSAY MODELING SIMULATION TOOL STATECHART
1. Reply to Brooks86: history,vanilla approach to modeling, reactive systems, model behavior, model data, visual, objects as an exotic flavor, analysis of model - execution, temporal verification, cose generation verifying consistency,

Harel95

David Harel
Will I be Pretty, Will I be Rich? Some Thoughts on Theory vs. Practice in Systems Engineering
[RE'97] pp184-185
=TALK SCIENCE ENGINEERING METATHEORY
Three types of theory: (1) foundations: deep robust general explanatory power, (2) pragmatic response to needs of an application, (3) Theory for the Sake of Theory: elegant difficult and CLEVER

Harel01

David Harel
From play-in scenarios to code: Achievable Dream
IEEE Computer Magazine V34n1(Jan 2001)pp53-60
=IDEAs USER REQUIREMENTS PURPOSE SAFETY LIVENESS MODEL DESIGN TEST REACTIVE TOOLS Rhapsody Statecharts MSC LSCs XUML
p54 Sidebar: HISTORY SA/SD
p55 Sidebar: HISTORY OOAD
See [HarelGery97] [Harel92] etc..
Also compare [UchitalKramerMagee02]
Users play with a system that models structure and teaches it the correct behaviors. These are represented internally by hidden formal models ( LSCs) and then super-compiled into the working code with links back to model and requirements.
Sequence charts model requirements but statecharts model the system..
play_in_scenario := simulated system with GUI that lets user play with scenarios and teach both good and bad ones.
anti_scenarios := Things that must not happen.
XUML := eXecutable UML, class diagrams+State charts.
MSC := Message Sequence Chart, telecommunications standard, states what might happen but does not state what must and what must not happen.
LSC::= Live Sequence charts, show possible and necessary sequences, can express both liveness and safety requirements, hot and cold elements.
hot_condition in LSC := when part of scenario is entered the condition has to be true, or the system has failed catastrophically.
cold_condition in LSC = when part of scenario is entered the condition has to be true, or the chart will terminate or exit to a higher level.
inter-object vs intra-object models.

Harel09

David Harel
Statecharts in the Making: A Personal Account
Commun ACM V52n3(Mar 2009)pp67-75 [ 1467247.1467265 ]
=HISTORY StateCharts GRAPHIC TOOL NOTATION FSM Hypergraphs SYNTAX SEMANTICS PRACTICE VISUAL FORMALISM Statemate Rhapsody
Originally an invited paper at the history of Programming Languages conference 207
How work on Avionics (1983) lead to a notation where diagrams define the system's behavior.
1983 Problem: clients understood the system but the information was not well-organized: "I had to pend a lot of the time asking questions"(p69).
Solution: "The pictures simply did a much better job of setting down on paper the systems' behavior[...]the mathematician in me found this difficult to accept".(p69)
"when designing a graphic language, topology should be used whenever possible"(p70).
"Executability was a basic[...] concern"(p70).
1984 Tools: Statemate -- GUI, executable, generate source code. Simulate circumstance -- similar to debugger.
Woes of Publication -- many rejections -- some successes. Technical report [Harel86] Commun ACM [Harel88] IEEE Trans Se [Hareletal90] ACM TOSEM [HarelKahanna92] [HarelNaamad96] IEEE Computer Magazine [Harel01]
Object-oriented StateCharts: [HarelGery97] [HarelKupferman02]
On Semantics: very important, but finding the right semantics took time.
Now used widely.
Conclusions
1. Lessons come from developing tools and real-world use.
2. Development in the lion's den -- not academic.
3. Getting a handle on the way clients think.
4. Should have published a book faster.
5. Should not have confused the problem of getting clear semantics with publicizing the chosen semantics.

Hareletal90

D Harel & H Lachover & A Naamad &A Pnueli & M Politi & R Sherman & A Ahtull-Trauring & M Trakhtenbrot
STATEMATE: A Working Environment for the Development of Complex Reactive systems
IEEE TRANS SE-16n4(Apr 1990)pp403-414
=ADVERT TOOL graphic STD statecharts

HarelGery97

David Harel & Eran Gery
Executable Object Modeling with Statecharts
IEEE Computer Magazine V30n7(Jul 1997)pp31-42
=DEMO OBJECT-ORIENTED STATECHART
Book [HarelPolitit??]

HarelKahanna92

David Harel & Chaim-Arie Kahanna
On Statecharts and Overlapping
ACM Trans Softw Eng Methodol V1n4(Oct 1992) pp399-422
=PAPER STATECHART STD syntax before semantics

HarelKozenTiuryn00

Dynamic Logic
MIT Press 2000 ISBN 0-262-08289-6 $50 QA76.9 L63 H37
=TEXT LOGIC TEMPORAL
for cs565/656

HarelKupferman02

David Harel & Orna Kupferman
On Object systems and Behavioral Inheritance
IEEE Trans Software Engineering V28n9(Sep 2002)pp889-903 correspondence V29n6(Jun 2003)p576
=DEFINITION Object-Oriented DYNAMIC INHERITANCE Liskov STATECHARTS
Defines with examples object-systems and linear and branching substitutability. These reflect trace containment(CSP?) and simulation (CCS).
Jinghong Cox Chen & Hewijin Christine Jiau note iand correct 4 typographical errors and raises a question about a missing assumption.

HarelNaamad96

David Harel & Amnon Naamad
The STATEMATE Semantics of Statecharts
ACM TOSEM V5n4(Oct 1996)pp293-333
=THEORY SEMANTICS STATECHARTS non-sequential
Problems of semantic drift between versions. Can changes in a step effect this step? No!

HarelPolitit??

D Harel & M Politi
Modeling Reactive Systems with Statecharts
McGrawHill NY 19??
=THEORY FSM/STD STATECHARTS MODELS REACTIVE

Hares90

John S Hares
SSADM for the Advanced Practitioner
John Wiley & Sons NY NY 1990
=TEXT SSADM Content
1. 1 Past and future
2. 2 strengths and weaknesses
3. 3. Pearls of PRactical Wisdom
4. 4 Distributed, Realtime, Conversational
5. 5 Expert Systems & Object Oriented Design
  1. OOD
  2. Normalize logic as well as attributes.
  3. access paths ---> responsibillity clusters
Hares94
1. John S Hares
2. SSADM version 4: the Advanced Practitioner
3. John Wiley & Sons NY NY 1994 ISBN 0-471-93564-6 CR9502-0077
4. =TEXT SSADM4
HaresSmart94
1. John S Hares & John D Smart
2. Object Orientation: Technology& Techniques& Management and Migration
3. John Wiley & Sones Inc NY NY 1994 $48.95 ISBN 0-471-94124-7 CR9511-0832
4. =TEXT extends SSADM to Objects
  [RobinsonBerrisford94]
Harman10
1. Mark Harman
2. Automated patching techniques: the fix is in
3. Commun ACM V53n5(May 2010)p108 [ 1735223.1735248 ]
4. =EDITORIAL CODE EVOLUTION SBSE GENETIC
5. Introduces [WeimerEtAl10]
6. SBSE::="Search Based Software Engineering".
7. See [Harman11] [HarmanJones01]
Harman11
1. Mark Harman
2. Software Engineering meets Evolutionary Computation
3. IEEE Computer V44n10(Oct 2011)pp31-37
4. =SURVEY SOFTWARE EVOLUTION ENGINEERING DESIGN GENETIC TESTING SEARCH-BASED SBSE
5. 71 references!
6. CF [Harman10]
7. Quotes the generic evolutionary programming algorithm, see [HarmanJones01]
HarmanJones01
1. Mark Harman & Bryan F Jones
2. The SEMINAL Workshop: Reformulating Software Engineering as a Metaheuristic Search problem
3. ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp62-66 & [ http://www.brunel.ac.uk/~csstmmh2/seminal2001/ ]
4. =CONFERENCE GENETIC ALGORITHMS ENGINEERING OPTIMIZATION SEARCH EVOLUTION GA
5. "Search based software engineering"
6. defines a generic evolutionary algorithm -- works with a population of candidate solutions P and applies recombination, mutation, evaluation, and selection to create the next set P'.
7. generic_evolutionary_algorithm::= with(P:@Solutions)(while(!goal(P) and !stop(P))(P'=select(evaluate(mutate(recombine(P)))))).
8. (above)|-generic_evolutionary_algorithm = do(not(goal or stop);recombine; mutate; evaluate; select ); (goal or stop).
9. simulated annealing: search for optima but may consider worse than the than current candidates in the early stages.
10. tabu search of discrete combinations: search by making moves but forbid certain moves at various times depending on recency and short and long term memory of previously unpromising moves.
Harmon11
1. Dion Harmon & Marcus A. M. de Aguiar & David D. Chinellato & Dan Braha & Irving R. Epstein & Yaneer Bar-Yam
2. Predicting economic market crises using measures of collective panic
3. arXiv:1102.2620v1 [q-fin.ST] (13 Feb 2011) [ 1102.2620 ]
4. =THEORY OBSERVATION ECONOMICS SOCIOLOGY GROUPTHINK COMOVEMENT PHASE CHANGE Abstract
  2. Predicting panic is of critical importance in many areas of human and animal behavior, notably in the context of economics. The recent financial crisis is a case in point. Panic may be due to a specific external threat, or self-generated nervousness. Here we show that the recent economic crisis and earlier large single-day panics were preceded by extended periods of high levels of market mimicry --- direct evidence of uncertainty and nervousness, and of the comparatively weak influence of external news. High levels of mimicry can be a quite general indicator of the potential for self-organized crises.
HarmonMorrissey96
1. Paul Harmon & William Morrissey
2. The Object Technology Casebook: Lessons from award-winning business applications
3. John Wiley & Sons NY NY 1996 ISBN0-471-14717-6 CR9709-0630(D.1.5)
4. =TEXT OBJECTS for managers and developers not programmers
HarmsWeide91
1. D E Harms & B W Weide
2. Copying and Swapping: Influences on the design of Reusable Software Components
3. IEEE Trans Soft Eng VSE17n5(May 1991)pp424-435
4. =ISEA RESOLVE philosophy of ADT design and implementation
HarrisAebischerKlaus07
1. Michael Harris & Kris Aebischer & Tim Klaus
2. The Whitewater Process: Software product development in Small IT Businesses
3. Commun ACM V50n5(May 2007)pp89-93
4. =STUDY 3 SMALL Florida Information Technology BUSINESSES PEOPLE PROCESS CUSTOMERS FEATURES TECHNOLOGY ITERATION INCREMENTAL MICRO-RELEASES EVOLUTION SMITB ONESIZE
5. Development is feature driven -- even the development platform and technology is changed when their is a market reason to change.
6. Small companies do not support multiple versions, multiple platforms, large marketing teams, trade shows, ...
7. Small companies tend to support a small number (=~= 100) non-IT customers using internet delivery.
8. Small teams. Modular architecture. Comparatively simple product.
9. Increment starts with inspiration and evaluation. Then iterative development: many micro-release shown to customers. Delivery is followed by high-touch support. Though out customers (current and potential) are shown the new features for feedback.
10. There are some cycles that involve major redesign and refactoring to add clashing features and/or resolve structural issues.
HarrisonCounsellNithi98
1. Rachel Harrison & Steve J Counsell & Reuben V Nithi
2. An Evaluation of the MOOD Set of Object-Oriented Software Metrics
3. IEEE Trans SE V24n6(Jun 1998)pp491-496
4. =THEORY =EXPERIENCES OO METRICs
Harrison04
1. Warren Harrison
2. Propaganda and software development
3. IEEE Software Magazine V21n5(Sep /Oct 2004)pp5-7 & V21n6(Nov /Dec 2004)pp9
4. =ESSAY PEOPLE CHANGE MOTIVATION
5. 3 Tricks. Bandwagon. Link old to enemy. Simplified ideas in unqualified positive statements.
Harrison05
1. Warren Harrison
2. Skinner wasn't a Software Engineer
3. IEEE Software Magazine V22n3(May/Jun 2005)pp5-7 + letters V22n5(Sep/Oct 2005)pp9-10
4. =EDITORIAL RESEARCH
5. Notes problems with experiments (on students) and field studies.
6. Describes single subject research designs.
7. design::=baseline #(treatment withdraw).
8. One subject implies no means. Looking for an observable change instead. therapeutic criterion
Harrison05a
1. Warren Harrison
2. What do Software Developers Need to know about Business?
3. IEEE Software Magazine V22n5(Sep/Oct 2005)pp5-7
4. =ESSAY BUSINESS CONTEXT ECONOMICS FINANCE EDUCATION
5. Need to learn about more than computing.
Harrison06
1. Warren Harrison
2. Content Mismanagement systems
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp5-8
4. =ESSAY REQUIREMENTS QUALITIES vs TECHNICAL CMSs URLs
5. Example of a technical constraint leading to a reduction in a quality.
6. CMS systems place database paths and keys into URLs making them long and incomprehensible -- unmailable.
7. Solutions? tinyurl.com, www.digbig.com, shorl.com, snipurl.com.
Harrison06a
1. Warren Harrison
2. Eating your own dog food
3. IEEE Software Magazine V23n3(May/Jun 2006)pp5-7
4. =ESSAY DOGFOODING
HarrisonAvgeriouZdun07
1. Neil B Harrison & Paris Avgeriou & U Zdun
2. Using Patterns to Capture Architectural Decisions
3. IEEE Software Magazine V25n5(Jul/Aug 2007)pp38-45
4. =ESSAY ARCHITECTURE PATTERNS QUALITIES TECHNIQUES REQUIREMENTS
5. Patterns provide a way of describing the trace from requirements to design.
6. p39: "Ideally, architecture documentation records decisions that architects made while designing the system"
HarrisonAvgeriou11
1. Neil B Harrison & Paris Avgeriou
2. Pattern-Based Architecture Reviews
3. IEEE Software Magazine V28n6(Nov/Dec 2011)pp66-71
4. =ADVERT CASESTUDIES PBAR ARCHITECTURE REVIEW PATTERNS REQUIREMENTS QUALITIES TECHNIQUES
5. Defines production focused projects that only value code.
6. Evidence for the value of reviewing the architecture of a project even when it is not documented.
7. Need one or two experts that can map the techniques in code back to the required qualities.
8. Review starts with reviewing the requirements and then looks at the code.
9. Do not need documented architecture -- but must have a walking skeleton implementation and some requirements.
10. Can be done the same day in a meeting with the team developing the software.
11. Teams found it of value.
12. PBAR::="Pattern-Based Architecture Review".
13. See also [HarrisonAvgeriouZdun07]
HarrisonSnook02
1. Rachel Harrison & Colin Snook
2. Practitioners Views on the Use of Formal Methods: An Industrial Survey by Structured Interview
3. Information & Software Technology 43(4) : 275-283 (2001) [ rharrison.pdf ]
4. =POLL EMPIRICAL UML Z B VDM CSP CCS in Marconi Prasix IBM Phillips
5. Using these methods typically needs trained customers. Most customers accept that software is error prone.
6. "Some customers do not want to be tied down to what they require,"[so that they don't]"take responsibility for the systems validity".
7. IBM and Praxis claim evidence of higher quality (eg fewer post-delivery failures).
8. Praxis notes you get more efficient code that does less!
9. No change in (traditional) life cycle but specification takes longer (and is most difficult) but reduces later effort.
10. size of system is not a problem. Understandability of the notation was not a problem. Finding useful abstractions is a problem.
11. Need style as well as formal notation. comments help. Making implicit changes explicit helps.
Hart95
1. Johnson M. Hart
2. Experience with Logical Code Analysis in Software Maintenance
3. Software Practice and Experience V25n11(Nov 1995)pp1243-1262
4. =DEMO EXPERIENCE PROOF
Hartley99
1. Stephen J Hartley
2. "Alfonse, Wait Here For My Signal!"
3. ACM SIGCSE Bulletin -- Inroads V31n1(Mar 1999)pp58-62
4. =EXAMPLE difficulties of JAVA NONSEQUENTIAL RISKS synchronize Thread rendezvous interupt
Hartmanis94a
1. Juris Harmanis
2. Turing Award Lecture: On computational complexity and the Nature of Computer science
3. Comm ACM V??n??(?? 1994)pp also Computer Surveys V27n1(Mar 1994)pp7-16(in [Hartmanis94b)]
4. =TALK SCIENCE ENGINEERING PARADIGMs
Hartmanis94b
1. Juris Harmanis(chair)
2. Computing Surveys Symposium on computational complexity and the Nature of Computer science
3. Computer Surveys V27n1(Mar 1994)pp1-61
4. =SURVEY SCIENCE ENGINEERING PARADIGMs
  1. Laszlo A Belady: Engineering info and CS is essential to all workers
  2. Gilles Brassard: Time for Another Paradigm Shift, quantum comps
  3. Peter Denning: data for machines, information for us :. subjective
  4. Peter A Freeman: Effective CS, involves other disiplines
  5. Michael C Loui: CS is a NEW Eng Discipline, consciencious competent...
  6. John Plaice: CS is an Experimental Science. Experiemnts are writing risky software! No idea of what tolls and methods will do...
  7. John Savage: Will CS become irrelevant? distinguishe roles of CS practitioner, research CS, experimental Cs and theoretical CS
  8. N F Stewart: Science and Cs: Popper
  9. Jeffrey D Ullamn: The Role of Theory Today: tendency to move away from real problem to reply to papers about papers...
  10. Peter Wegner: Interaction as a Basis for Empirical CS. beyond algorithms. p47: Corrrectness:( Type 1:Exists correct behavior in interactions, Type 2: No incorrect behavior in algorithm)
  11. Rick Weingartner: Government Funding & C research Priorities: no curiosity driven research.
  12. W A Wulf: Wulf94 and a response to the responses: [Hartmanis94c]
Hartmanis94c
1. Juris Hartmanis
2. Responses to essays "On computational complexity and the Nature of Computer science"
3. Computer Surveys V27n1(Mar 1994)pp59-61
4. =ESSAY FUTURES SCIENCE ENGINEERING
HassenzahlBeuBurmeister01
1. Marc Hassenzahl & Andreas Beu & Michael Burmeister
2. Engineering Joy
3. IEEE Software Magazine V18n1(Jan/Feb 2000)pp70-76
4. =IDEA USER
5. dangers of reductionism to usability, design, or market.
6. semantic differential!
7. RGT::="Repertory Grid Technique", by George Kelly!
8. Shira::= "structured hierarchical interviewing for requirements analysis"
Hasselberg99
1. On Defining Computer Science Terminology
2. Commun ACM V42n2(Feb 1999)pp88-91
3. =MODEL UML GRAPHIC OO Classification of Health Care Information Systems
Hassler05
1. Susan Hassler
2. Learning from Software Failure
3. IEEE Spectrum Magazine (Sep 2005)p8
4. =EDITORIAL COSTS RISKS FAILURE DISASTERS VCF
5. Good software can transform a business: Dell Walmart.
6. Notes that a future disaster may be when the USA digitizes and automates medical records.
7. Introduces [Charette05] [Ross05] [Goldstein05]
Hassler05a
1. Vesna Hassler
2. Open Source Libraries for Information Retrieval
3. IEEE Software Magazine V22n5(Sep/Oct 2005)pp78-82
4. =SURVEY 5 OPEN SOURCE LIBRARIES IR Xapian Apache Lucene ht://Dig Swish-e DataparkSearch
HassonCooper06
1. Patricia Hasson & Stephen Cooper
2. A Case Study Involving the Use of Z to Aid Requirements Specification in the Software Engineering Course
3. IEEE 17th conference on software engineering education and training CSEET'04 (2004)pp84-94 CR 0606-0664 CR 0607-0768 (In the IEEE Digital library at [ CSEE.2004.1276515 ] )
4. =EXPERIENCE EDUCATION Z SPECIFICATION
5. When students take previous projects, done by others, and express the specs in Z the discover errors.
6. Graphics and user interface details are not part of Z, tell students to omit them.
7. Need to add to the library of fundamental data types - decimals & text.
8. Students need LPC first.
9. (dick)|-Online copy has a non-Z font. Many symbols changed from Z Reference Manual. [Spivey01]
10. (dick)|-Z is the wrong language to express data formats: BNF, COBOL PICTURES, Finite state machines, etc should be used instead.
Hastings93
1. Reed Hastings<hastings@pure.com>
2. Improving Tests For Reliability
3. UNIX Review V11n10(Oct 1993)pp59-62
4. =EXPERIENCE SQA TEST RELIABILITY QUALITY
  1. When software breaks it because of a failure in a quality gate
  2. Bugs are in the gates!
  3. Fixing the gate is more important than fixing the code!
HastingsSajeev01
1. T E Hastings & A S M Sajeev
2. A Vector-Based Approach to Software Size Measurement and Effort Estimation
3. IEEE Trans Software Engineering V27n4(Apr 2001)pp337-350
4. =EXPERIMENT ADT METRIC vs FP COCOMO
5. VSM::= "Vector Size Measure".
6. VPM::= "Vector Prediction Model".
7. Applied to 8 MIS projects.
8. ADT has functions and rules. Rules predict complexity and Functions functionality. length is the sum. size is the functionality><complexity pair. Magnitude sqrt(functionality^2+complexity^2). gradient = complexity/functionality.
9. Effort is approximately proportional to magnitude * gradient!
HatleyPirbhai87
1. Derek J Hatley & Imtiaz A Pirbhai
2. Strategies for Real-Time Specification
3. Dorset House Publishing 1987
4. =METHOD Hibrid DFD/CFDs + STDs
Hatton95
1. Les Hatton
2. Programmiung Languages and Safety-Related Systems
3. Proc of the Safety-Critical Systems Symposium
4. Springer-Verlag New York NY 1995 pp48-64
5. =SURVEY EXPERIENCE FORMALITY RISKS
Hatton95a
1. Les Hatton
2. Safer C: Developing Software for High-integrity and Safety-critical Systems
3. McGraw Hill (UK) 1995 ISBN 0-07-707640-0
4. =TEXT RISKS C
Hatton97
1. Les Hatton
2. Reexamining the Fault density - component Size connection
3. IEEE Software magazine V14n2(Mar/Apr 1997)pp89-97
4. =EXPERIMENT METRIC QUALITYT MODULE SIZE DEFECTS STATISTICS
5. density::=faults/size. Is a Ushaped function of size.
6. |-|bugs| is_proportional_to log(size).
Hatton98
1. Les Hatton
2. Does OO Sync with how we Think
3. IEEE Software magazine V15n3(May/Jun 1998)pp46-54
4. =EXPERIENCE C DDD vs C++ OBJECT-ORIENTED TECHNICAL TOOLs =THEORY PEOPLE
5. defect density 25% > for C++
6. C fixes done quicker -- roughly 50% less time perhaps because of inheritance
7. similar degree of reuse
Hatton07
1. Les Hatton
2. How Accurately do Engineers predict Software Maintenance Tasks
3. IEEE Computer Magazine V40n2(Feb 2007)pp64-69
4. =EXPERIENCE STATISTICS MAINTENANCE CHANGE REQUESTS CR
5. Ratios of Corrective:Adaptive:Perfective vary with project. In these projects roughly 10:45:45.
6. 75% of changes took less than 5 hours.
7. Typically estimate was roughly 35% over the actual.
8. But overestimation was significantly less in the second half of the data vs the first half.
9. The variance of the overestimate drops as project progresses.
Hatton07a
1. Les Hatton
2. Emprirical Test Observations in Client-Server Systems
3. IEEE Computer Magazine V40n5(May 2007)pp24-29
4. =STATISTICS ERRORS TWO CLIENT-SERVER SYSTEMS
5. Worth continuing to monitor correctness of client and server system after delivery. Even for errors in the serverthat the user can not observe.
6. No evidence that a good GUI covers up errors.
7. Claims <= 1 defect per KSLOC.
Hatton07b
1. Les Hatton
2. The Chimera of Software Quality
3. IEEE Computer Magazine V40n8(Aug 2007)pp104+102-103
4. =POLEMIC QUALITY LOW OPEN SOURCE BETTER
5. Bewails lack of experimental data in methods.
6. Argues that the biggest contributor to quality code is the developer.
7. Notes bad quality of: scientific programs, off the shelf software, etc etc.
8. States the value of inspecting code.
9. Notes that open source code is better than closed source code.
Hatton08
1. Les Hatton
2. Testing the value of checklists in code inspections
3. =EXPERIMENT INSPECTIONS CHECKLISTS
4. IEEE Software Magazine V25n4(Jul/Aug 2008)pp-
5. No evidence that checklists decreased the number of undetected faults in a program.
6. Idea to use capture-recapture techniques.
7. Tried both allowing engineers to use checklists and mandatin that some used checklists.
8. Effectiveness : the best engineers found 10 times as many faults as the worst engineers.
9. Two person teams can increase per centage found from (average) 53% to 76%.
10. Raw Data [ Data_Inspections_05_06_2007 ]
Hatton09
1. Les Hatton
2. Power-law distributions of component size in general software systems
3. IEEE Trans Software Engineering V35n4(Jul/Aug 2009)pp566-572
4. =EMPIRICAL STATISTICS CODE PACKAGES METRIC QUALITY MODULE SIZE DEFECTS STATISTICS Pareto
5. Theory and data show that defect density(defects/line) in a stable software system is proportional to the logarithm of the number of lines of code in that module.
6. However see [Zhang08] that claims a Weibull distribution is better.
HattonRoberts94
1. Les Hatton & Andy Roberts
2. How Accurate Is Scientific Software
3. IEEE Trans SE-V20n10(Oct 1994)pp785-797 CR9601-0123 D.2.8
4. =EXPERIMENT RISKS SCIENTIFIC CALCULATION NUMERICAL ANALYSIS
  1. Not Very!
  2. Compared 9 commercial versions of a single program for geophysical analysis across the same large set of data. Add result of removing a bug from one version. Differences cluster in groups... more like DNA than anything. Not random, but nonrandom, equally reasonable but essentially different answers. More computation ..> bigger differences. Swapping components gives less assurance than replicating a new version.... but is commonly used to verify.
    Cumulative precision loss of 1% per 4KLOC(per 3KExecLOC)
HaumerPohlWeidenhaupt98
1. Peter Haumer & Klaus Pohl & Klaus Weidenhaupt
2. Requirements Elicitation and Validation with Real World Scenes
3. IEEE Trans SE V24n12(Dec 1998)pp101036-1054
4. =DEMO SYSTEM SCENARIOS recorded in multimedia linked to goal tree "CREWS"
Haungs01
1. Jim Haungs
2. Pair Programming on the C3 Project
3. IEEE Computer Magazine V34n2(Feb 2001)pp118-119
4. =EXPERIENCE XP C3 PERFORMANCE TESTING
5. C3::="Chrysler's Comprehensive Compensation project". Smalltalk on Gemstone object database + call COBOL for fast tax calculations.
6. develop in VisualWorks SmallTalk, then live in Gemstone. Profiling. Tuning. Testing with pair programming
Hausleretal90
1. Philip A Hausler & Mark G Pleszkoch & Richard C Linger & Alan R Hevner
2. Using Function Abstraction to Understand Program Behavior
3. IEEE Software V7n1(Jan 1990)pp55-63
4. =EXPERIENCE CLEANROOM! RE-ENGINEERING COBOL!
5. concurrent assignment and guards
Hausleretal94
1. Philip A Hausler & Richard C Linger & C J Trammell
2. Adopting Cleanroom software engineering with a phased approach
3. IBM Systems Jnl V33n1(1994)pp89-109
4. =EXPERIENCE CLEANROOM
5. Table with 17 projects 1987..1993, 3..350KLOC, several languages, error rates in testing 0..6.1/KLOC
6. 3 phases of introduction (intro, Full, Advanced) accross 8 technologies: Management&Team, CustomerInterction, Incremental development, System Specification, System Design & Implementationn, Correctness Verifiction, Statistical testing & Reliability certification, Process Improvement
Hawking06
1. David Hawking
2. Web search engines: part 2
3. IEEE Computer Magazine V39n7(Aug 2006)pp88-90 [ MC.2006.286 ]
4. =DEMO DATA STRUCTURES ALGORITHMS SEARCH ENGINE PERFORMANCE
HawryshRuprecht00
1. Stephen P Hawrysh & Jim Ruprecht
2. Light methodologies: it's like Deja Vu all Over Again
3. Cutter IT Journal V13n11(Nov 2000)pp4-12
4. =HISTORY METHODS
5. p9: "There is no one-size-fits-all software development model, and it is nuts to try and force one into place."
Hawryszkiewycz8491
1. ?? Hawryszkiewycz8491
2. Database Analysis & Design
3. Chicago IL SRA (1st Edn 1984 2nd 1991)
4. =TEXT DATA DBMS DESIGN
HavelunddLowryPenix01
1. Klaus Havelundd & Mike Lowry & John Penix
2. Formal analysis of a Space-Craft Controller using SPIN
3. IEEE Trans Software Engineering V27n8(Aug 2001)pp749-765
4. =CASESTUDY FORMAL MODEL CHECKING TOOL SPIN LISP LTLMODAL LOGIC ESL PROMELA
5. Deep Space 1.
6. Located a major design flaw.
7. found a bug that testing missed that caused problem 98M kilometers from Earth.
8. LTL::="Linear Temporal Logic", properties of traces using modes [] = always and <> meaning some.
9. Interviewed programmer about impact of work: found difficult mission-killing bugs -- thought formal meant program proving not finding bugs.
Havey05
1. Michael Havey
2. Essential Business Process Modeling
3. O'Reilly Media Sebastopol CA 2005 T 58.64 ISBN0-596-00843-0
4. =HANDBOOK workflow Business Process Modeling theory pi-calculus petri patterns languages STANDARDS XML BPM UML? YAWL P4
5. Standards include BPEL BPELJ BPMN BPML XPDL WAPI WfXML WS-CDL WSCI WSCL ... languages and diagrams for modeling business processes.
6. Useful list of business process patterns including 20 from P4 (M Dumas + A H M ter Hofstede + B Kiepuszewski + A P Barrios " Workflow Patterns" TR Eindhoven U of Technology 2003, Distributed and Parallel Databases V14n1(2003)pp5-51)
  1. Basic: Sequence, Parallel split & join, Exclusive choice/XOR and simple merge
  2. Advanced branch and join: multi-choice/or and synchronized merge or multimerge. Discriminastor and N-out-of-M Join
  3. Structural: Arbitary cycles/goto, implicit termination(branches need no end marker).
  4. Multiple instances: unsynchronized, synchronized (know how many at design time or at run time, or unknown number).
  5. State-based: defered choice (nondeterminism), interleaved parallel routing (unordered execution of each element once), Milestone (bracketted repetition)
  6. Cancelation: cancel activity, cancel case
7. More patterns:
  1. Human workflow: Prioritisation and escalation {delayed tasks become more important and may be taken over by anotherr person(boss)}, Roles compete for task (AND....1 out of 3)
  2. Communication: receive request, call parner, wait for response, unsolicited event, corelated response, dynamic partner
8. (dick)|-buffered vs unbuffered communication
HaxtehausenPelska00
1. Anne E Haxtehausen & Jan Pelska
2. Formal development and verification of a distributed railway control system
3. IEEE Trans Software Engineering V26n8(Aug 2000)pp687-701
4. =CASESTUDY RAISE DISTRIBUTED RADIO SYSTEM SAFETY REQUIREMENTS invent & verify SPECIFICATION
5. model reality and purpose separately. trains and switch-boxes.
6. Consultants to INSY GmbH Berlin RELIS 2000 and others.
HayAtlee00
1. Jonathan D hay & Joanne M Atlee
2. Composing Features and resolving Interactions
  [FSE8] pp110-119
3. =CASESTUDY FORMAL EVOLUTION CVF LOGIC Relations POTS
4. A way to add features to a complex system even when they conflict with the system and each other.
Hayes-RothBetal95
1. Barbara Hayes-Roth & Karl Pfleger & Phillipe Lalande & Hillipe Morignot & Marko Balabanovic
2. A Domain-specific sofware architecture for adaptive intelligent systems
3. IEEE Trans Software Eng V21n2n4(Apr 1995)pp288-301 CR9604-0272
4. =ADVERT DSSA AI REUSE BlackBoard
Hayes-RothJacobstein94
1. Frederick Hayes-Roth & Neil Jacobstein
2. The State of Knowledge-Based Systems
3. Comm ACM V37n3(Mar 1994)(AI issue)pp27-39
4. =REPORT
Hayes90
1. Ian Hayes
2. A Generalisation of Bags in Z
3. pp113-127 in Nicholls90
4. =EXAMPLE Z SPECIFICATION
5. physical units and bank accounts
6. For set X, bags(X)::=X<>->Integer.
Hayes93
1. Ian Hayes (ed)
2. Specification Case Studies(2nd Edition)
3. Prentice Hall Englewood Cliffs NJ 1993 (Series in Comp Sci)
4. ISBN0-13-8325444-8 BNB92-33735 QA76.6.S667 1993(csusb)
5. =TEXT SPECIFICATION Z Formal CICS Text
HayesB01
1. Brian Hayes
2. The Web of Words
3. American Scientist V87n2(Mar-Apr 1999)pp108-112
4. =ARTICLE SEMANTICS NATURAL LANGUAGES is-a has-a TOOL WordNet
5. Illustrates and defines
6. hypeynym-hyponym relation::= is-a (inheritance/generalization) hierarchy. @ for hypernym.
7. holonym_meronym::= has_a/composition/whole_part relationship. - for parts.
8. WordNet::= See http://www.cogsci.princeton.edu:80/~wn/main/ , also on a CD-ROM from MIT Press.
9. antonyms::= opposites. ! for opposites.
10. Examples: (dwelling, house) in hypeynym-hyponym and (dwelling, kitchen) in holonym_meronym.
HayesB02
1. Brian Hayes
2. The Easiest Hard Problem,
3. American Scientist V90n2(Mar-Apr 2002)pp113-117 and republished in [HayesB08]
4. =POPULARIZATION CHAOS COMPLEXITY THEORY ALGORITHMS NP-COMPLETE partition PHYSICS
5. Link between complexity physics and chaos??
6. NP-Hard problems can have regions where they are easy! There may be a phase transitions from areas that are easy to areas where they are hard.
7. Partitioning n numbers in range 1..2**m into to sets with equal totals is easy when m/n<1 and hard when m/n >1.
Hayes03
1. Brian Hayes
2. A Lucid Interval
3. American Scientist V91n6(Nov-Dec 2003)pp484-488
4. =SURVEY INTERVAL ARITHMETIC
Hayes06
1. Brian Hayes
2. Foolproof
3. American Scientist V95n1(Jan-Feb 2007)pp10-15
4. =HISTORY PROOFS UNDERSTANDING MATHEMATICS trisection Euclid Hobbes Wantzel DIALECTICS POSTMODERN
5. "[...]if proof is a magic wand that works only in the hands of wizards, what is it's utlity to the rest of us?"
6. Experimental mathematics using programs.
7. Compare [Lakatos76] and mathematics as a social process.
HayesB05
1. Brian Hayes
2. Naming Names
3. American Scientist V93 (Jan/Feb 2005) and republished in [HayesB08]
4. =ARTICLE CODING DATA
  1. Internet account IDs
  2. NY Stock Exchange Ticker Symbols -- up to 3 Uppercase letters -- 26+26**2+26**3 possible
  3. Universal Product Codes -- bar codes -- ( UPC )-- 12-digit until January 2005, and then 13-digits.
  4. Global Traded Item Numbers (GTIN)
  5. European Article Numbers (EAN)
  6. Biological Species -- Two Latin-like words
  7. The Chemical Elements -- One uppercase letter + option lower case letter. (I had to program these while working for ICI in the 1960's)
  8. Organic Chemicals -- Complex coding.
  9. Internet Assigned Number Authority IANA names for countries -- two ASCII letters
  10. Radio Call Signs -- 3..4 Capital letters -- KVCR, KFROG, ...
  11. Telephone numbers -- 10 digits (in the USA).
  12. Social Security Numbers -- 9 digits in the USA
  13. Airport codes (IATA) -- Three letters.
  14. Names of Horses -- 2..18 characters ( letters plus space, period, and apostrophe).
HayesB08
1. Brian Hayes
2. Group theory in the bedroom, and other mathematical diversions
3. Hill and Wang NY NY 2008 ISBN 0-8090-5219-9
4. =ARTICLES MATHEMATICS FUN CODING DATA INTRACTABILITY
5. Reprints
  1. Naming Names [HayesB05]
  2. and other good articles
Hayes09
1. Brian Hayes
2. Writing Math on the Web
3. American Scientist V97n2(Mar-Apr 2009)pp98-102
4. =ARTICLE HTML Τ_ΕΧ TeX MathML JsMath FONTS techexplorer
5. Problems with putting formulae onto web pages.
6. Where to render the formula: author, server, or client?
7. Client: Plugin(techexplorer), fonts, special script (JsMath). Rely on user having the plugins and fonts to work.
8. Server example -- Wikipedia uses texvc, MathTeX, MimeTeX. All make graphic images. reliable and ugly.
9. How to render: as a graphical image or using Fonts or Unicode?
10. Failure of MathML to become mainstream.
11. (dick)|-Failure of Τ_ΕΧ to express hypertext markup.
12. (dick)|-No formal syntax and semantics for proofs and logic in Τ_ΕΧ or MathML
13. (dick)|-Still like my MATHS language better.
Hayes09a
1. Brian Hayes
2. Everything is under control
3. American Scientist V97n3(May-Jun 2009)pp186-191
4. =DEMOS ECONOMIC MODELS SIMULATIONS HYDRAULIC MONIAC. CONTOL THEORY LAG
5. MONIAC::=hydraulic analog computer for the British economy 1949 by A WH Phillips.
6. Control theory suggests the need for proportional & integral & derivative feedback.
7. Need to reduces lags.
8. Example model [ main2.htm ] (127 equations Ray C Fair )
HayesJones89
1. I. J. Hayes & C. B. Jones
2. Specifications are not (necessarily) executable
3. IEE Software Engineering Journal V4n6(Nov 1989)pp320-338 ftp://ftp.cs.man.ac.uk/??UMCS??89-12-1
4. =IDEA SPECIFICATION
  1. author = "I. J. Hayes C. B. Jones",
  2. title = "Specifications are not (necessarily) executable",
  3. journal = "IEE Software Engineering Journal",
  4. volume = "4",
  5. number = "6",
  6. pages = "320--338",
  7. month = "November",
  8. year = "1989"
    }
  Which is available by ftp from ftp.cs.man.ac.uk as UMCS 89-12-1

HayesJonesNichols94

Ian Hayes<Ian.Hayes@cs.uq.oz.au> & Cliff B Jones<cbj@cs.man.ac.uk> & J E Nichols
Understanding the Differences between VDM and Z
ACM SIGSOFT Software Engineering Notes V19n3(Jul 1994)pp75-81
=HISTORY FORMAL METHODS Z vs VDM

Hazewinkel04

Michiel Hazewinkel
Mathematical Knowledge Management is Needed
Keynote speech at the November, 2003 MKM meeting at Herriott-Watt, Edinburgh, UK
=ESSAY MATHEMATICS
MKM::="Mathematical Knowledge Management", Handling the vast amount of published mathematics. In the 1970's 200,000 theorems where being published per year! MSCS::="Mathematical Subject Classification Scheme", tree structure with 5500 leaves

Hazzah90

Ali Hazzah
The ER Semantics of Enterprise Model[sic]
Software Magazine(Dec 1990)pp62-79
=IDEA ERD SEMANTICS

HeartyFentonMarquezNeil09

Peter Hearty & Norman Fenton & David Marquez & Martin Neil
Predicting Project Velocity in XP using a learning Dynamic Bayesian Network Model
IEEE Trans Software Engineering V35n1(Jan/Feb 2009)pp124-137
=EXPERIENCE XP ESTIMATION BAYES BN PV

HazzanDubinsky08

Orit Hazzan & Yael Dubinsky
Agile Software Engineering
Springer Pub NY NY(2008) ISBN 184001983 CR 0912-1151
=MANUAL PEOPLE AGILE TEAMS TESTS REFLECTION HUMAN ORGANIZATIONAL TECHNOLOGY
HOT::analysis=Human >< Organizational><Technological.
Describes a process that helps people learn what might be taught directly in other books.
Not clear if they are training students or teachers.
The treatment of refactoring is completely inadequate.

HazzanLeron10

Orit Hazzan & Uri Leron
Disciplined and free-spirited: "Time-out behavior" at the Agile Conference
Elsevier Journal of Systems and Software V83(2010)pp2363-2365 CR ????-????
=OBSERVATION ANTHROPOLOGY AGILE PEOPLE CONFERENCES INTERACTIONS COMPETITIONS PUB ETIQUETTE

HeckVervest07

Eric Van Heck & Peter Vervest
Smart Business Networks: How the network wins
Commun ACM V50n6(Jun 2007)pp29-37
=CASESTUDIES WEB/NET BUSINESS NETWORK EFFECTS ECONOMICS SERVICES COORDINATION ORCHESTRATION BOS Amazon eBay Multiasistecia Kenny's TheBigWord
BOS::="Business Operating System".
Businesses are starting to need the ability to create and operate flexible and ad hoc networks with partners.
Also see news item on page 14: Amazon's "Mechanical Turk" and ChaCha that farm out problems that require powerful AI to real intelligences.

Heckel82

Bruce? Heckel
The Elements of Friendly Software Design
NY NY Warner books 1982
=HANDBOOK USER

HeckermanEtAl95

David Heckerman & Abe Mamdani & Michael P Wellman
Real-World Applications of Bayesian Networks
Commun ACM V38n3(Mar 1995)pp24-57
=ISSUE BBN CONDITIONAL INDEPENDENCE GRAPHS PROBABILITY DEBUGGING DATA TROUBLESHOOTING
Good introduction: [HeckermanWellman95]

HeckermanWellman95

David Heckerman & Michael P Wellman
Bayesian Networks
Commun ACM V38n3(Mar 1995)pp27-30
=INTRODUCTION BBN CONDITIONAL INDEPENDENCE GRAPHS PROBABILITY TROUBLESHOOTING
More [ Bayesian Networks in math_22_graphs ]

HeerBostockOgievesky10

Jeffrey Heer & Michael Bostock & Vadim Ogievetsky
a tour throughout the visualization zoo
Commun ACM V53n6(Jun 2010)pp59-67 [ 1743546.1743567 ]
=DEMO GRAPHICS HCI CS489

Hehner84a

Eric C R Hehner
Predicative Programming Part I
Commun ACM V27N2 ( Feb 1984)pp134-151
=DEMO dynamic logic regular
Next part [Hehner84b]

Hehner84b

Eric C R Hehner
Predicative Programming Part II
Commun ACM V27n3( Mar 1984)
=DEMO dynamic logic regular non-sequential
Follows [Hehner84a]

Hehner93

Eric C R Hehner
A Practical Theory of Programming
Springer Verlag NY NY 1993 ISBN 0-387-9106-1 CR9405-0276 F.3.0
=TEXT FORMAL DDD Review
1. .Author F Aribaud Paris France
2. undergraduate text on theory that a PL is sublanguage of a specification language,
3. state and temporal variables,
4. dynamic predicates like,
5. Modus ponens becomes refinement,
6. fuzzy presentation of wffs - quantification over infinite domains so risk of inconsistency,
7. terse disussion of fixed points for recursion,
8. lightened the maths too much,
9. less formal and interesting
  recommended to instructors not beginners

Hehner94

Eric (Ric).C.R. Hehner
Abstractions of Time
chapter 12 in Roscoe94 (p.191-210)
=THEORY

HehnerSilverberg83

Eric C R Hehner & B A Silverberg
Programming with Grammars: An Exercise in Methodology-directed Language Design
Comp Jnl V26n3 pp277-281(Aug 1983)
=DEMO DDD non-sequential

Heiler95

Sandra Heiler(GTE Labs mailto:sheiler@gte.com)
Semantic Interoperability
ACM Computing Surveys V27n2(June 1995)pp271-273
=ESSAY SEMANIC SPECIFICATION MODULE

Heimdahl96

Mats P E Heimdahl
Experiences & Lessons from the Analysis of TCAS II
Proc 1996 Int Symposium on Software Testing & Analysis(ISSTA) & ACM SIGSOFT SENotes V21n3(May 1996)pp79-83
=EXPERIENCE REQUIREMENTS SQA RSML StateCharts And/Or Tables
"Identified problems in requirements specification[...]that had undergone extensive manual verification"
tends to find to many holes and ambiguities and inconsistencies that can be difficult to correct. Should allow extended entries and AND/OR tables perhaps.
See also [Levesonetal94]
[HeimdahlLeveson96]

HeimdahlKeenan97

Mats P E Heimdahl & David J Keenan
Generating Code from Hierarchical State-Based Requirements [RE'97] pp210-219
=EXPERIENCE RSML STATECHARTS TABULAR SEMANTICS C/C++

HeimdahlLeveson96

Mats P E Heimdahl & Nancy G Leveson
Completeness and Consistency in Hierarchical State-based Requirements
IEEE Trans Softw Eng VSE22N6(Jun 1996)pp revised from ICSE-17 1995 CR9707-0519 D.2.1
=EXPERIENCE TCAS experiences and formal definition of analysis
[Heimdahl96]
[Levesonetal94]

Heitmeyer02

Constance Heitmeyer
Software Cost Reduction
Center for High Assurance Computer Systems (CHACS) Publications 2002 [ 2002heitmeyer-encse.pdf ]
=HISTORY PARNAS NRL SCR IDEAS NOTATIONS TOOLS TABULAR LOGIC NAT IN OUT REQ A-7E TAME REQUIREMENTS DESIGN MODULES
@T(c)::=c becomes true,
@F(c)::=c becomes false.
SCR uses logic and tables to express very clearly what is expected of a new system.
Software that monitors certain inputs and controls certain outputs.
It uses a four variable model (NAT+REQ+IN+OUT) that distinguishes the assumed properties (NAT) from the requirements (REQ). IN and OUT specify tolerances.
Software has modes. Tables relate modes and events. Finite State model.
Human inspection for defects proved expensive and tools uncovered more defects afterwards.
Tools include SPIN, TAME, PVS, Salsa, an invariant generator, .
Usable subsets of requirements lead to the uses hierarchy, module guide, etc..
Methods and tools applied to real projects to discover problems.
Also see [HeitmeyerEtal98] [HeitmeyerKirbyLabaw97]

Heitmeyer02a

Constance Heitmeyer
Software Cost Reduction.
Article in [Marciniak02]
=UNREAD =HISTORY PARNAS NRL SCR IDEAS NOTATIONS TOOLS TABULAR LOGIC NAT IN OUT REQ A-7E TAME REQUIREMENTS DESIGN MODULES
Compare [Heitmeyer02] perhaps [click here Heitmeyer02a if you can fill this hole]

HeitmeyerEtal96

Constance L Heitmeyer & Ralph D Jeffords & Bruce G Labaw
Automated Consistency Checking of Requirements Specifications
ACM TOSEM V5n3(Jul 1996)pp231-261
SCR TABULAR CR9705-0365

HeitmeyerEtal98

Constance Heitmeyer & James Kirby Jr & Bruce Labaw & Myla Archer & Ramesh Bharadwaj
Using Abstraction and Model Checking to Detect Safety Violations in Requirements Secifications
IEEE Trans SE V24n11(Nov 1998)pp927-948
=EXPERIENCE RISKS automatic lightweight TOOL(sun) SCR TABULAR Spin Promela
In minutes found scenarios where weapons system could be risky - not meet invariants.
Uses nondeterministic state machines and homomorphisms to reduce state space.

HeitmeyerKirbyLabaw97

Constance Heitmeyer & James Kirby & Bruce Labaw
The SCR Method for Formally Specifying& Verifying& and Validating Requirements: Tool Support
[ICSE'97]
=EXPERIENCE TOOLS FORMAL SCR
Formal demonstration of tools mapping SCR tables into animated mockups scenario logs etc. Uncovered problems... especially in translating requirements into mathematics

HelanderZhaoOhlsson98

Mary E Helander & Ming Zhao & Niclas Ohlsson
Planning Models for Software Reliability and Cost
IEEE Trans SE V24n6(Jun 1998)pp420-434
=THEORY COST RELIABILITY
how to optimize reliability with fixed cost or optimize cost for a fixed reliability given hierarchy+operational profile+utilisation matrix

Helft11

Miguel Helft
The Class That Built Apps, and Fortunes
NY Times (May 7, 2011) [ 08class.html?_r=2&pagewanted=all ]
=EXPERIENCE 2007 PROCESS MARKET FACEBOOK apps EDUCATION ENTREPRENEURS
Process:
Market:

Hellenack97

Leslie J Hellenack
Object-Oriented Business Patterns
Object Magazine 6(11)(Jan 1997) pp23-30+70
=IDEA SYSTEM REALITY OBJECTS
SYSTEM+REALITY OBJECTS: adapts IBM's work in the 70's to OO
OMT-like model looks like LDSTs of SSADM courses 1982

HellersteinEtal99

Joseph M Hellerstein Ron Avnur & Andy Chou & Christian Hidber & Chris Olston & Vijayshakar Raman & Tali Roth & Peter J Haas
Interaetive data analysis: the Control project
IEEE Computer Magazine V32n8(Aug 1999)pp51-59
=ADVERT USER DATA mining
Control::="continuous output and navigation technolog with refinement online".
display growing random sample fitting query.
[ http://control.cs.berkeley.edu ]

Hellman99

Reed Hellman
A Semantic approach adds meaning to the web
IEEE Computer Magazine V32n12(Dec 1999)pp13-16
=ADVERT WEB RDF XHTML

Hemendinger90

David Hemendinger
Specifying Ada Server Tasks with Executable Formal Grammars
IEEE Trans SE-16n7(Jul 1990)pp741-754
=DEMO NONSEQUENTIAL GRAMMAR regular DAD

Henderson-Sellers96a

Brian Henderson-Sellers
The Mathematical Validity of Software Metrics
ACM SIGSOFT Software Engineering Notes V21n5(Sep 1996)pp89-94
=EXAMPLE METRIC ERRORS
examples of metrics with careless mathematics and stats

Henderson-Sellers96b

Brian Henderson-Sellers
The OPEN-MeNtOR Methodology
Object Magazine (Nov 1996)pp56-59
=ADVERT OPEN MENTOR OBJECT-ORIENTED METHOD
merger of methods from 20 experts with some input from UML

Henderson-Sellers00

Brian Henderson-Sellers
COBOL for the next millenium
IEEE Software Magazine V17n2(Mar/Apr 2000)pp53-58
=ADVERT OPEN OBJECT-ORINTED PROCESS NOTATION

Henderson-SellersEdwards90

Brian Henderson-Sellers & Julian E. Edwards
The Object-Oriented Systems Life Cycle
Commun ACM V33n9(Sep 1990)pp142-159
=SURVEY METHODS
1. Fig2: Problem Space vs Solution Space, Scale of 3 methodologies - Top-down Function vs JSD vs Object-oriented Decomposition, Parallel life cycles for clusters of objects, The Fountain Model, Object Structure Classes, O/C - Objects or Classes, Graphic Notation for Client-Server and inheritance, Effort vs time.

Henderson-SellersEdwards94

Brian Henderson-Sellers<brian@socs.uts.edu.au> & Julian E. Edwards
BOOKTWO of Object-Oriented Knowledge: The Working Object : Object-oriented software engineering: methods and management(MOSES)
Prentice Hall Englewood Cliffs NJ 1994 ISBN 0-13-093980-3 $48 CR9508-0550
=TEXT MOSES OBJECT-ORIENTED method+TOOL+NOTATION

Henderson-SellersFreeman92

B. Henderson-Sellers & C. Freeman
Cataloguing and Classification for Object Libraries
ACM SIGSOFT Software Engineering Notes V17n1(Jan 1992) pp62-64
=DEMO OBJECT-ORIENTED REUSE

Henderson-SellersGraham96

Brian Henderson-Sellers & Ian Graham
OPEN: Toward method convergence?
IEEE Computer Magazine V29N4(Apr 1996)pp86-89
=ADVERT OPEN =SURVEY METHODS OBJECT-ORIENTED
OPEN::=Object Oriented Process Environment and Notation
contract driven life cycle is flexible
CIRT::=class|intance|role|type
matrix mapping activity><task->mandatory|recommended|option|possible|forbidden
tasks completed by techniques
more than 100 echniques

Henderson86

P Henderson
Functional Programming Formal Specification & Rapid Prototyping
p241-250in BerglandZave86
=DEMO prototypes PURPOSE

Henderson90

Peter B Henderson
Discrete Mathematics as a Precursor to Programming
ACM SIGCSE V22n1pp17-21(Feb90)
=EDUCATION formal MATHEMATICS

Henderson10

Peter B Henderson
Math Counts -- Model Checking
ACM Inroads V1n1(Mar 2010)p33
=ADVERT MODEL CHECKING VERIFICATION EDUCATION
Encourages the use of model checking in teaching computer science.
Introduces [ Ben-Ari10 ]

Henderson-Sellers03

Brian Henderson-Sellers
Method engineering for OO Systems development
Commun ACM V46n10(Oct 2003)pp73-78
=ADVERT OPF METAMODEL METHODOLOGY OPEN
First, choose your process...
OPF::=" [OPEN] Process Framework".
OPEN::="Object-Oriented Process, environment and Notation".
A framework for selecting process components to fit a development situation.
define five major classes of components: work product, producer, work unit, language, stage,... For part of the framework supplies a set of component instances: examples: 30 activity instances, 160 task instances, ...
Task/activity matrix. Technique/task matrix.

HendrixCrossMaghsoodloo02

Dean Hendrix & James H Cross II & Saeed Maghsoodloo
The Effectiveness of Control Structure diagrams in source Code Comprehension Activities
IEEE Trans Software Engineering V28n5(May 2002)pp463-477
=EXPERIMENT TECHNICAL CODE READING CSD GRAPHIC VISUALIZATION TOOL Java Ada C C++
CSD::="Control Structure diagram". cf Robilard in the 1980s!
Responses to questions about code came quicker with CSD. Correct responses also quicker.
More correct responses with CSD.
Tendency for CSD to help with earlier questions.
In one case CSD mislead students because it did not make a one line loop visible.

HendrixSchneider02

T. Dean Hendrix & Michelle P. Schneider
NASA's TReK project: a case study in using the spiral model of software development
Commun ACM V45n4 (Apr 2002)pp 152-159 [ 505248.506004 ]
=EXPERIENCE PROCESS INCREMENTAL DELIVERY
It worked in a challenged project.

HenkelReichenbachDiwan08

Johannes Henkel & Christoph Reichenbach & Amer Diwan
Developing and Debugging Algebraic Specification for Java Classes
ACM TOSEM Trans Software Eng & Methodology V17n3(Apr 2008)#14pp1-37
=CASESTUDIES TOOL DEBUG SPECIFICATIONS vs JAVA CODE TECHNICAL
Formal specifications need debugging. A tool helps.

Hennessy88

?? Hennessy
Algebraic Theory of Processes
MIT Press MA 1988
=TEXT ALGEBRA MATH NONSEQUENTIAL logic

Henning08

Michi Henning
The Rise and Fall of CORBA
=HISTORY STANDARDS OMG MIDDLEWARE CORBA OBJECT-ORIENTED DISTRIBUTED NET NONSEQUENTIAL vs WEB DCOM SOAP XML
Commun ACM V51n8(Aug 2008)pp53-57 [ 1378704.1378718 ] CR 0909-0847
CORBA_history::=bleeding_edge_technology; popular_middleware; obscure_niche_technology, -- why?
Two technical issues: complexity and missing features,
Reasons endemic in a democratic open consortium of customers and vendors.
OMG_process::=customers generate a fuzzy and possible umimplementable RFP; vendors propose their own rival solutions with no implementation; solutions are merged with no reference implementation.
Process does not create high quality standards.
Proposals
1. Only standardize existing best practice.
2. No standard approved without a reference implementation.
3. No standard approved without being used on realistic projects.
Compare open source projects
1. Ideas developed as competing working solutions.
2. It is more important to say "No" than to say "Yes". A dictator or cabal is useful for saying "No" to bad RFPs Compare [Shirky03] [DenningYaholkovsky08] on problems with getting collaborative solutions.
(dick)|-UML is another OMG standard of growing complexity with no reference implementation...

Henning09

Michi Henning
API Design matters
Commun ACM V52n5(May 2009)pp46-56 [ 1506409.1506424 ]
=EXAMPLES BAD GOOD INTERFACES FUNCTION PROTOTYPE SPECIFICATION ABSTRACTION ADVICE USER
Bad is easier than good but has large long term unlimitted costs.
1. Provide sufficient functionality to the caller/client/user.
2. Smaller is better.
3. Understand the context.
4. General interfaces shouldn't set policy but specific ones should.
5. Design from the caller's/client's point of view and for their convenience not yours.
6. Don't pass the buck to the caller/user/client.
7. Document before you implement.
8. Ergonomics!
Need to change education and career paths.
(dick)|-no discussion of design by contract. Does it give better interfaces?

Henninger94

Scott Henninger
Using Iterative Refinement to Find Reusable Software
IEEE Software Magazine V11n5(Sep 1994)pp48-59
=DEMO REUSE TECHNICAL PROBLEM SEARCH
1. Dex, Helgon,...,Codefinder
2. When searching for related terms the results must be explicable to the user.

HenryBlasewitz92

Joel Henry & Bob Blasewitz
Process Definition: Theory and Reality
IEEE Software magazine V9n6(Nov 1992)pp103-105
=EXPERIENCE PROCESS

HenryFaller95

Emmannuel Henry & Benoit Faller
Large-scale Industrial Reuse to Reduce Cost and Cycle Time
IEEE Software Magazine V12n5(Sep 1995)pp47-53
=EXPERIENCE C++ TECHNICAL REUSE COST PROCESS

Henson10

Gary Henson
Schlock: from Web to iPhone
PLUS14 Website [ http://www.plus14.com/news/schlock-from-web-to-iphone/ ]
=EXPERIENCE APPLE iPhone iPad App WEB/NET GRAPHIC TOUCH COMIC SCHLOCK

Henzingeretal94

T. Henzinger & X. Nicollin & J. Sifakis & S. Yoviner
Symbolic model-checking for real-time systems
Information and Computation V111(1994)pp193-244
=UNKNOWN THEORY FORMAL MODEL VALIDATION

Hepworth90

Brian Hepworth
ZIP: a Unification Initiative for Z Standards Methods and Tools
poster pp253-260 in [Nicholls90]
=POSTER STANDARDS Z HISTORY forsite FUZZ ZED Genesis ZEBRA B

Herbertetal90

Andrew Herbert & William Lively & Sallie Sheppard
A Graphical Specification System for User-Interface Design
IEEE Software V7n4 (Jul 1990) p12-20
=IDEA graphic DFD STD USER

Herbsleb99

James D Herbsleb
Metaphorical Representation in Collaborative Software Engineering
ACM SIGSOFT SE Notes V24n2(Mar 1999)pp117-125 (Proceedingd of WACC'99)
=EXPERIENCE 70% of spoken descriptions are metaphors

HerbslebMockus03

James D Herbsleb & Audris Mockus
An Empirical study of speed and communication in Globally distributed software development
IEEE Trans Software Engineering V29n6(Jun 2003)pp481-494
=EXPERIENCE TEAM GLOBAL MAINTENENCE Lucent
Communication is an important part of software development.
The time to make a change is larger when it is a larger change effecting many modules and people are far apart and using Email and telephone instead of face-to-face.
Distance decreases communication significantly. The key distance apart is 30.meters!
Finding expert advice takes longer.
Possible tools: chat rooms, Instant messaging, summarize change management data to publically identify experts.

HerbsledMockus03b

James D Herbsled & Audris Mockus
Formulation and Preliminary Test of an empirical theory of coordination in software engineering
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp138-147
=THEORY =EMPIRICAL SCIENCE MODULES DECISIONS COORDINATION
Postulates a number of decisions which lead to a feasible or infeasible result.
f(x):{0,1}=feasibility of decisions x.
The feasible choices for a decision are those where there is at least one other set of decisions that make the result feasible.
FC(X i)={x:X(i). for some u:X(1..i-1), v:X(i+1..n) ( f(u!x!v) = 1 )}.
E(X i | X k = x) :=the effect of fixing X k on X i .
ME(X l| X k):=maximal effects of k on i.
Defines clumps of decisions and the Parnas effect as the number of other decisions that have no effect on this clump.
The Conway effect relate clumps associated with team structure.
7 other assumptions.
Observes the fate Modification Requests (MRs) in a real project.
Productivity goes down with the number of independent sources of MRs.
It takes longer to do an MR that effects many modules.

HerbslebMoitra01

James D Herbsleb & Deependra Moitra (Guest editors)
Global Software Development
IEEE Software Magazine V18n2(Mar/Apr 2000)pp16-86
=COLLECTION CULTURE TECHNOLOGY MODULES
Synching:= "making organizations congruent".

HermenegildoEtAl08

M V Hermenegildo & F Bueno & N Carro & P Lopez & J F Morales & G Puebla
An Overview of the Ciao Multiparadigm Language and Program Development Environment and its Design Philosophy
Montanari Festschrift pp208-237 [DeganoEtAl08]
=ADVERT LANGUAGE Ciao TOOL THEORY FUNCTIONAL OO LOGIC CONSTRAINT
Downloads [ http://www.ciaohome.org ] [ http://www.cliplab.org ] ciao@clip.dia.fi.upm.es
91 references

HerringKaplan00

Charles Herring & Simon Kaplan
The Viable System Model for Software
Proc SCI/ISAS2000 VVIIIII pp266-274 [SCI00]
=THEORY viable COMPONENT METHOD VSM ARCHITECTURE VSA Stafford Beer Algedonic feedback

Hersh95

Ruben Hersh
Fresh Breezes in the philosophy of Mathematics
American Math Monthly V102n7(aug-sep 1995)pp589-594
=HISTORY MATHEMATICAL LOGIC
Compare [Lakatos76].

Hersh05

Ruben Hersh (Ed)
18 unconventional essays on the nature of mathematics
Springer-Verlag NY Secaucus NY 2005 ISBN 0387257179 CR 0811-1046
=UNREAD ESSAYS MATHEMATICS
Compare [Hersh95]

Hesse43

Herman Hesse
The Glass Bead Game (Magister Ludi)
Publishers: Several. Try any good library or book store [ 080501246X ] (Amazon.com)
=CLASSIC NOVEL BILDUNGSROMAN LANGUAGES ACADEME MEDITATION EXISTENTIALLISM
For history, summary and clues see [ The_Glass_Bead_Game ] (Wikipedia)

Hevneretal92

Alan R Hevner & Shirley A Becker & Lenard B Pedowitz
Integrated CASE for Cleanroom Development
IEEE Software V9n2(Mar 1992)pp69-76
=ADVERT CLEANROOM
Formal+verified+object-oriented+Reliability statistics + CASE with a central repository and integrated tools
IBM cf Mills...
Black Box<-<State Box<-<clear box

HevnerMills93

A. R. Hevner & Harlan D Mills
Box-structured Methods for Systems Development with Objects
IBM Sys Journal V32n2(1993)pp232-251
=IDEA GRAPHIC TECHNICAL MODEL CLEANROOM
part of CLEANROOM METHOD
See Hevneretal92 for more detail
1. Black_Box::=Net{Stimulus, Response, Behavior},
2. Behaviour::=#Stimulus->Response,
3. State_Box::=Net{Common, Stimulus, Response, State, Behavior},
4. Clear_Box::=Net{Common, Stimulus, Response, State, Behavior::= Data><Process},

HevnerMarch03

Alan R Hevner & Salvatore T March
The Information systems Research Cycle
IEEE Computer Magazine V36n11(Nov 2003)pp111-113
=ESSAY RESEARCH IS BEHAVIORAL vs DESIGN PARADIGMS
Need to balance and connect the IS environment (people, organizations, technology) with the knowledge base (Foundations, methodologies).

Heyman07

Karen Heyman
A new virtual private network for today's mobile world
IEEE Computer Magazine V40n12(Dec 2007)pp17-19
=STANDARD SECURITY PROTOCOLS WWW/NET UDP IPsec TCP SSL VPN

Hidding97

Gezinus J Hidding
Reinventing Methodology: Who Reads it and why
Comm ACM V40n11(Nov 1997)pp102-109
=POLL estimate usage of method documentation by planners+sales+doers+managers
plaaners in Andersen Consulting use method docs most: avg 31.3 pages sd 26.5; 29% skimmed 54% read 17% studied; 72%applied
different types of practitioner need different kinds of method info
the format for presenting methods must change from a single path through a single collection of handbooks to a collective knowledge base allowing one-of-a-kind solations+collaborating disciplines+configurable process modules

HiemdahlWhalen97

Mats P E Heimdahl & Michael W Whalen
Reduction and slicing of Hierarchical State Machines
[JazayeriSchauer97] pp450-467
=DEMO RSML SPECIFICATION STATECHART TABULAR
calculate restricted transition mapping under conditions in given scenario

HieattMee02

Edward Hieatt & Robert Mee
Going Faster: Testing The Web application
IEEE Software Magazine V19n2(Mar/Apr 2002)pp60-65
=EXPERIENCE WEB/NET TESTFIRST CODE TECHNICAL

HigaMorrisonetal92

Kunihiko Higa & Mike Morrison & Joline Morrison & Olivia R Liu Sheng
Object-Oriented Methodology for Knowledge Base/Database Coupling
??
=??

Higgins83

David Higgins
Designing Structured Programs
EduCo Prentice Hall Denver Colorado 1983
=TEXT LCP text DDD

Higgins10

Kelly Jackson Higgins
Kaminsky Issues Developer Tool To Kill Injection Bugs
dark reading (Jun 14 2010) [ http://mobile.darkreading.com/9287/show/e17461923a943ee5a9ddab78d5a4f496/ ]
=RFC TOOLWEB/NET SECURITY FRAMEWORK CODE VS DATA SQL injection XSS CREDENTIALS Interpolique
Normal string interpolation is unsafe -- but attractively easy.
By distinguishing code from data, a new framework helps stop the user injecting there on (evil) code into your code.
Recursion_Ventures::= See http://recursion.com/index.html.
Iterpolique::= See http://recursion.com/interpolique.html.
(Dan Kaminsky)|-"Life is too short to defend broken code". Code breaks only when a website become popular,

Highsmith99

Jim Highsmith
Beyond optimizing
Software Development Magazine V7n9(Sep 1999)pp80+78-79
=HARMFUL CMM PROCESS command-control
adaptive chaordic(Hock) patterns leadership-collaboration

Highsmith99b

James Highsmith
Adaptive software development:A Collaborative Approach to Managing Complex Systems
Dorset House NY NY 2000 ISBN0-932633-40-4 CR0002-0090
=ADVERT PROCESS MANAGEMENT CYBERNETICS ASD PEOPLE Complex Systems Theory (erroneous)

Highsmith02

Jim Highsmith
Does Agility Work?
Software Development Magazine V10n6(Jun 2002)pp30+31-36
=ANECDOTES AGILITY SCRUM ASD Trimble IDX "feature driven" FDD Nebulon CPT?
Fit process to project.
Barely sufficient methodology, ...
Short term iteration. Making skilled people collaborate. Fight to avoid wasting time.
Turned around Singapore bank project bogged down in analysis: 50 people, 2000 features, 15 months, happy clients and CEO.
sidebar pp32-34 by Ken Schwaber on [Scrum] Send development terms to the customer.

HighsmithCockburn01

Jim Highsmith & Alistair Cockburn
Agile Software Development: The Business of Innovation
IEEE Computer Magazine V34n9(Sep 2001)pp120-122 + letters IEEE Computer Magazine V34n12(Dec 2001)p4
=MANIFESTO AGILITY PEOPLE not PROCESS ASD XP etc

HighsmithNix96

Jim Highsmith & Lynne Nix
Mission Possible
Software Development Magazine (Jul 1996)pp41-45
=ADVERT people Technical how to do a feasibility study

Higman67

Brian Higman
A Comparative Study of Programming Languages
NY NY Elsevier North Holland 1st edn 1967
=SURVEY language history

Higman77

Brian Higman
A Comparative Study of Programming Languages
Elsevier NY 1977 2nd edition
=SURVEY language history

HildebrandtZeller00

Ralf Hildebrandt & Andreas Zeller
Simplifying Failure-Inducing Input
Proc ISSTA 00 & ACM SIGSOFT Software Engineering Notes V25n5(Sep 2000)pp135-145
=DEMO DEBUGGING TOOL Mozilla Netscape
Given program and failure find simplest way to induce failure.

Hillston95

Jane Hillston
A Compositional Approach to Performance Modelling
Cambridge UP(1996) Google Books [ books?id=XhAhygkvxYIC&printsec=frontcover&dq=Hillston+Performance+Modelling&source=bl&ots=S08b3LYZfs&sig=GjGUoUi5AtWGVbdVAcJrIBMPqeQ&hl=en&ei=peSsTP8tiMKwA9ScpZcM&sa=X&oi=book_result&ct=result&resnum=1&ved=0CB4Q6AEwAA#v=onepage&q&f=false ] (Google Books),
Based the Thesis [ 43258476 ] (Abstract and pointer to archive) [ book.pdf ]
=TEXT PEPA ALGEBRA PERFORMANCE QUALITY MATHEMATICS
Expressions contain prefixes(.), choices (+), hiding(/), and cooperation (<L>) with shared actions.
Actions have a type and a rate:[0..1].
Structured Operational Semantics in terms of a transition relations: E-action->E'.
Most complex rule:
If E-(α,r1)->E' and F-(α,r2)->F' and α ∈ L and R=(r1/r[α](E))*(r2/r[α](F))*min(r[α](E),r[α](F)) then E<L>F -(α, R)-> E'<L>F' )
r[α](F):=the apparent rate of action type α in component F, with a compositional definition.

Hillston05

Jane Hillston
Fluid Flow Approximation of PEPA models
Second International Conference on the Quantitative Evaluation of Systems (QEST'05)(September 2005)pp. 33-43
=MATHEMATICS PEPA ALGEBRA NON-SEQUENTIAL COMPONENT LOADS ALGORITHM MATRIX ODEs
Demonstrates that a continuous approximation to the discrete system is easy to solve and makes adequate predictions.

HincheyBowen95

M. G. Hinchey and J. P. Bowen (eds.)
Applications of Formal Methods
Prentice-Hall International Series in Computer Science 1995
=EXPERIENCES - good news vs bad press and no extra profit

HincheyBowen99

Michael G Hinchey & Jonathan P Bowen (Eds)
Industrial-Strength Formal Methods in Practice
FACIT Series of Springer-Verlag 1999 SBN 1-8533-640-4 QA76.9 F67 I53
=EXPERIENCE FORMAL METHODS B BAN Z TABULAR ACL2 RAISE Z/EVES EVES V&V TOOL Cleanroom SSADM RSML
for cs556/656
Contains [BjornerGeorgePrehn99] [LevesonEtal99b] [KestenKleinPnueliRaanan99] [BrockHunt99] [LanoGoldsackSanchez99] [BurrowsAbadiNeedham89] [Anderson99] [BernardLaffite99] [BowenHinchey99] [LingerTrammell99] [BoralvStalmarck99] [ArdisMataga99] [MooreKlinkerMihelcic99] [CraigenMeiselsSaaltink99] [SemmensBryant99] [Jacky99]

HincheyEtAl08

MIke Hinchey & Michael A Jackson & Patrick Cousot & Byron Cook & Jonathen P Bowen & Tiziana
Software Engineering and Formal Methods
Commun ACM V51n9(Sep 2008)pp54-59 [ 1378727.1378742 ] CR 0908-0760
=SURVEY FORMAL MATHEMATICAL LOGICAL METHODS TOOLS QUALITIES RELIABLE COST
Summary of three key note speeches from ICSE&FM 2007.
Describes history: increasing dependability of hardware, more intensive use of software, more ubiquitous computing, no increase in software dependability.
Formal methods can increase dependability.
Jackson notes that good engineering stays within the normal design discipline associated with a given application domain. Radical design leaves the normal and always decreases the dependability of the result. Therefore the need to develop special purpose disciplines for each domain. Refers to [Vincenti90] on engineering. Compare with Henry Petrosky's work.
Patrick Cousot defines formal methods and the idea of abstraction. Mentions Astree.
Byron Cook notes the explosion of complexity when there is concurrency and the attempts to overcome it.
Conclusion reviews the history, describes method engineering and states that the quest continues...

Hirsh05

Barbara Hirsh
Positive Reinforcement as a Quality Tool
IEEE Software Magazine V22n2(Mar/Apr 2005)pp62-63
=EXPERIENCE CHANGE IMPROVEMENT QPM SQM CMM SQA V&V AUDIT After enterprise-wide training and several audited projects hold a competition for the "best X" where X is a desired change with meaningful prizes..
In this case 30 submissions, 20% peer review.

HirschmanLindblom62

A O Hirschman & C E Lindblom
Economic Development, Research and Development, Policy Making: Some Converging Views Behavioral Science V7(1962)pp211-222 & [Emery69] pp351-371
=SURVEY AGILE PROCESSES in ECONOMICS SOCIOLOGY POLITICS ORGANIZATION
Argues that complexity, uncertainty, and value conflicts are best handled incrementally with piecemeal unbalanced development that is driven by what happens.
"incremental meandering"
"adjusting the ends to fit the current means"

HirschheimNewman91

Rudy Hirschheim & Mike Newman
Symbolism and Information System Development: Myth, Metaphor, and magic
Information Systems Research V2n1(??? 1991) & [MyersAvisson02]
=SURVEY POSTMODERN PEOPLE SYSTEMS ANTHROPOLOGY CYBERCRUD
Ref to [Markus83]
Argues that information system development can not described as a rational endeavor and gives examples from 4 projects of myths, metaphors, and Magic (ritual).
Distinguishes believers(faith overrides events) from cynics( belief follows events)
6 myths: user involvement, resistence always happens and must be overcome, integration is good, system people know best, politics doesn't matter, top-down is good.
3 metaphors: it's a battle, the organization is divided into fiefdoms, people are machines.
3 magic rituals: involving the user, signing off, owning data.

Hirschi07

Ashwin Hirschi
Traveling Light, the Lua way
IEEE Software Magazine V24n5(Sep/Oct 2007)pp31-38 CR 0904-0362
=EXPERIENCE LUA C/C++ DYNAMIC TYPED SCRIPTING RAD Reflexis
Adds a dynamically typed stack to C++.
Lua::= See http://lua.org/.

HitzMontazeri96

Martin Hitz & Behzad Montazeri
Chidamber & Kermerer's Metrics Suite: A Measurement Theory Perspective
IEEE Trans Softw Eng VSE22n4(Apr 1996)pp267-271
=CRITIQUE improved METRICS for Object-Oriented code [ChidamberKemerer94]

Hoare69

C.A.R. Hoare
An Axiomatic Basis for Computer Programming
Commun ACM V12 n10 Oct 69
=THEORY logic formal structures

Hoare73

C.A.R. Hoare
Computer Programming as an Engineering Discipline
Electronics & Power v19 pt14 pp316-320
=ESSAY modules graphic

Hoare78

C.A.R. Hoare
Communicating Sequential Processes
Commun ACM v21 n8 pp666-677(Also book -See [Hoare85] )
=THEORY non-sequential logic CSP
Contrast [Milner80] CCS [Baetan90] ACP

Hoare79

C.A.R. Hoare
Final Panel Discussion
p274 of Proc Formal Design Methods Conference 1979 IFIP T2 Group
=SUMMARY non-sequential

Hoare81

C.A.R. Hoare
The Emperor's Old Cloths(ACM Turing Lecture)
Commun ACM v24 n2 Feb 1981 pp75-83
=SPEECH RISKS history

Hoare85

C.A.R. Hoare
Communicating Sequential Processes
Prentice Hall 1985
=IDEA CSP non-sequential formal logic structures
Developed from [Hoare78]
Contrast [Milner80] [Baetan90] ACP
Later edition(2006) online [ cspbook.pdf ] as PDF.

Hoare86

C.A.R. Hoare
Mathematics of Programming
Speech at the Boston Computer Museum reported in Byte Aug 1986(pp115-127)
=SPEECH RELATIONAL structures

Hoare87

C.A.R. Hoare
An Overview of Some Formal Methods for Program Design
IEEE Computer V20n9(Sep 1987)pp85-91
=SURVEY METHODS FORMAL optimization

Hoare93

C A R Hoare
Algebra and Models [Notkin93] pp 1-8
=IDEA ALGEBRA RELATIONS ?
Hoare01
1. C A R Hoare
2. Assertions: a personal perspective (Draft)
3. Microsoft Research Ltd., Cambridge, England (6 Jun 2001) .See http://research.microsoft.com/~thoare/6Jun_assertions_personal_perspective.htm
4. =HISTORY ESSAY CODE ASSERTIONS INVARIANTS ALGOL60 ELLIOTT CSP Z
5. Assertions as annotating designs.
6. Assertions and axioms defining semantics.
7. Assertions as an executable part of code.

Hoare09

C A Hoare
retrospective: an axiomatic basis for computer programming
Commun ACM V52n10(Oct 2009)pp30-32 [ 1562764.1562779 ]
=HISTORY VERIFICATION PROGRAMMING LOGIC PROOFS TESTS HACKERS SPECIFICATIONS COSTS
Looking back at [Hoare69] 40 years later. Compare [Hoare01]
Expected to retire before research was complete and industry adopted methods.
Surprised to find "assert" in C/C++.
Didn't expect the new logics/mathematics that have been developed.
Tests test the programmer not the program.
Hackers have got industry interested in verification -- finally.
Academic and industrial research should complement each other. One goes for the big ideals and the other for low hanging fruit.
Reply [ Humelsine10 ] (letter).

Hoareetal87

C.A.R. Hoare & IJ Hayes & HE Jifeng & CC Morgan &AW Roscoe & JW Sanders & IH Sorenson & JM Spivey & BA Sufrin
Laws of Programming
Commun ACM V30n8 (pp672-686)1987
=IDEA formal sequential logic
For practicing engineers mathematical laws are also more relevant than the elaborate models constructed in a study of foundations.
could define programs as relations that are total and with images that are either finite or else universal with fictitious "state at infinity" for non-termination.
finite texts have a normal form ignoring speed.

HoareBroySteinbruggen01

Tony Hoare & Manfred Broy & Ralf Steinbruggen
Engineering theories of Software Construction
IOS Press(2001) Amsterdam, The Netherlands ISBN 1586031724 CR 0304-0310
=WORKSHOP ENGINEERING MATH LOGIC MODELING PROBLEM-FRAMES REALITY REACTIVE Petri

HodgeGrayFiddian00

Leigh E Hodge & W Alex Gray & Nick J Fiddian
A Toolkit to Facilitate the Integration of Tabular Information in Textual Documents with Database Applications
Proc SCI/ISAS2000 VI pp35-41 [SCI00]
=ADVERT TOOL HTML TEXT LaTeX XML DATA Regular-expressions Perl Visual-Basic MS-Acess Excel

Hodges77

Wilfrid Hodges
Logic
Penguin Books Middlesex UK & NY NY 1977
=TEXT FORMAL LOGIC Semantic Tableaux TREEs
Describes an easy to learn and use method of proving/disproving results.
Compare with earlier [Jeffrey67] and next edition [Hodeges05]

Hodges05

Wilfred Hodges
An Introduction to Elementary Logic, Second Edition $20.00 Paperback | 5.07 x 7.79in | 304 pages | ISBN 9780141003146 | 28 Dec 2005 | Penguin UK
=TEXT FORMAL LOGIC Semantic Tableaux TREEs
Describes an easy to learn and use method of proving/disproving results.
Based on earlier [Jeffrey67]

HoepmanJacobs07

Jaap-Henk Hoepman & Bart Jacobs
Increased security through open source
Commun ACM V50n1(Jan 2007)pp79-83
=ESSAY OPEN SOURCE SECURITY
Argues that open source software may initially be more vulnerable but it ultimately will be more secure than closed source.

HoekstraKrocSloot10

Alfons G Hoekstra & Jiri Kroc & Peter M Sloot (Eds)
Simulating Complex Systems by cellular automats
Springer NY NY (2010) ISBN 3642122027 CR 1107-0694
=PAPERS CA Cellular Automata Complexity
TBD [click here HoekstraKrocSloot10 if you can fill this hole]

HoerrlAichernig00

Johan Hoerl & Bernhard K Aichernig
Validating voice communication Requirements using lightweight formal methods
IEEE Software Magazine V17n3(May/Jun 2000)pp21-27
=CASESTUDY INDUSTRY Frequentis VDM++ -> UML Rational Rose 98 TOOL for ATC PABX PSTN VCS3020s
lightweight:=formal specification without proofs
24000lines VDM++, 1000 fot test cases, found 64 issues (ambiguious/coontradictory/incomplete), 22 before VDM + 30 during + 12 during functionllity spec'n
writing a formal spec uncovered issues that will be missed by just reading a informal spec
formalized test cases
calculated coverage of test cases - 80%
VDM++ deficencies: Types inside a class are private. No method calls in expressions. All member variables private.|-can not access object state in expression!
presents time and effort figures.
next parallel development VDM with ongoing project

Hoffman90a

Daniel Hoffman
On Criteria for Module Interfaces
IEEE Trans SE-16n5(May 1990)pp537-542
=IDEA modules Technical

Hoffman90b

Daniel Hoffman
Author's reply to Contantine90
IEEE Trans SE-16 n12(Dec 1990)p1440
=REBUTTAL

Hoffman08a

Leah Hoffman
In Search of Dependable Design
=ESSAY RELIABILITY CORRECTNESS RISKS BUGS
Commun ACM V51n7(Jul 2008)pp14-16
History: Intel Pentium Bug, FBI virtual case file, IRS tax-processing
Impact of software on life and estimated costs of defects is increasing... NIST estimates $59.5 billion lost per year.
Daniel Jackson: Need for precise requirements.
Model checking [ Hoffman08b ]
Eiffel [Meyer90] [Meyer91]
Alloy [JacksonD06a]
Booch: human communication is critical, not coding.

Hoffman08b

Leah Hoffman
Talking Model-checking Technology
=INTERVIEW HISTORY MODEL CHECKING VERIFICATION FSM TEMPORAL LOGIC
Commun ACM V51n7(Jul 2008)pp112+110-111
Interview with Turing prize winners E Allen Emerson & Edmund M Clark & Joseph Sifakis
Painful birth: theoretically trivial and practically impossible!
Handle programs that do not stop. Avoid humans proving programs. Based on finite state abstractions of program+hardware and requirements specified in temporal logic. If property is not satisfied by abstraction then procedure gives a diagnostic trace of the bad behavior.
Problem: State Explosion: no of cases to consider can grow exponentially with the size of the model.
Benefits: precise specifications.
Limits: 10^100 states!
Microsoft has one used for device drivers!

Hoffmann09

Leah Hoffmann
Crowd Control
Commun ACM V52n3(Mar 2009)pp16-17 [ 1467247.1467254 ]
=ARTICLE CROWDSOURCING STATISTICS
Many minds make lite work.... wide band delphi

HoffmanLehner01

Hubert F Hoffman & Franz Lehner
Requirements Engineering as a Success Factor in Software Projects.
IEEE Software Magazine V18n4(July/Aug 2001)pp58-66
=POLL 15TEAMS REQUIREMENTS SUCCESS
Lists 10 best practices:involve users, identify and consult all sources, assign skilled project managers, allow 15-30% of project total to requirements, provide specification templates and examples, maintain good relations between stake holders, prioritize requirement, develop both models and prototypes, maintain traceability matrix, Use peer review, scenarios, and walkthrus.

HoffmanSnodgrass88

Daniel Hoffman & Richard Snodgrass
Trace Specifications: Methodology and Models
IEEE Trans Soft Eng VSE-14n9(Sep 1988)pp1243-1252
=IDEA ADTs formal specification and LISP prototypes
Heuristics: incrementally(normal form+prefixes+predicates+macros).

HoffmanWeiss01

Daniel M Hoffman & David M Weiss
Software fundamentals: Collected Papers by David L Parnas
Addison-Wesley 2001 CR0109-0914 ISBN 0-201-70369-6 QA76.754P36
=COLLECTION REQUIREMENTS MODULES DESIGN LOGIC TECHNICAL SCR TABULAR LANGUAGES METHODS SDI A7 ENGINEERING

Hogben37

Lancelot Hogben
Mathematics for the million
W W Norton 1937 NY NY
=TEXT MATHEMATICS HISTORY GEOMETRY ASTRONOMY ARITHMETIC TRIGONOMETRY ALGEBRA GRAPHS LOGARITHMS CALCULUS STATISTICS
Provides exercises for the serious.
Shows how practical matters drive the development of abstruse calculi.
Argues that mathematicians rely on diagrams and computation before the get to proving something.
An excellent description of the problem of "word problems" starting with p.304

Hohman97

Luke Hohman
Journey of the Software Professional: A Sociology of Software Development
Prentice Hall 1997
=HISTORY
Project notebooks
Ref in Warren Keuffel articl Software Development Magazine (Aug 1997)p26

Hohman03

Luke Hohman
The Difference between Marketecture and Tarchitecture
IEEE Software Magazine V20n4(Jul/Aug 2003)pp51-53
=EXPERIENCE MARKET REQUIREMENTS <> TECHNICAL ARCHITECTURE
THere is more to software than writing code.
Example of neat technical evolution that would have lost $5M dollars in revenue.
Example of marketing modules that were technically boolean flags.
example of an API that was technically convenient but never sold to application programmers!
Marketecture::="software as imagined by marketing and sold o customer".
tarchitecture::="software structure as imagined by developers".
Compare with Davis03 phenotype and genotype.

Hohpe02

Gregor Hohpe
XML abuse
Software Development Magazine V10n12(Dec 2002)pp38-39
=EXAMPLES XML how-not-to HARMFUL
(badXML1): XML configuration files may be readable but they are not writable.
(badXML2): XML configuration files tend to be verbose and monolithic.
(badXML3): XML-code arguments are loosely typed and so runtime errors are common.
(badXML4): XML does not provide semantic -- meaningful-- integration.
(badXML5): XML metadata is in the TD not the document so does not allow reflexion.
(badXML6): XML does not provide multiple data access pas and user interaction.

Hohpe03

Gregor Hohpe
An Asynchronous World
Software Development Magazine V11n7(Jul 2003)pp30-37
=DEMO TECHNICAL NONSEQUENTIAL WEB/NET JMS JAVA PIPE MESSAGING COUPLING
Describe how to send messages -- reliably across networks and surprising pitfalls.
Beware messages left undelivered from early runs/tests.
When responding to a stimulus include stimulus's ID (setJMSCorrelationID) in response.
When sending a stimulus and expecting a response check that the response is for the right stimulus via the stimulus's echoed ID.
Expect data that goes thru different paths to arrive out of sequence.

Hohpe05

Gregor Hohpe
Your coffee shop doesn't use two-phase commit
IEEE Software Magazine V22n2(Mar/Apr 2005)pp64-66 & letter V22n3(May/Jun 2005)pp8-9
=ARTICLE PATTERNS CONCURRENCY TRANSACTIONS ACID NONSEQUENTIAL
4 strategies: write-off, retry, compensate/undo, coordinate.
Compare 1970s SSADM/Jackson recognition problems.
Shorter version at [ 18-starbucks.html ]

HollandLieberherr96

Ian M Holland & Karl J Lieberherr
Object-Oriented design
Computing Surveys V29n1(Mar 1996)pp273-275
=SURVEY Object-Oriented design
identify objects classes relationships and behavior needed to implement software

Hollingsworthetal94

Joseph E Holingsworth & Sethu Sreerama & Bruce W Weide & Sergey Zhupanov
RESOLVE Components in Ada and C++
ACM SIGSOFT Software Engineering Notes V19n4(Oct 1994)pp40-63
=ADVERT Resolve OBJCT-ORIENTED COMPONENTS
See Sitaraman94

Holloway95

C Michael Hollowy<c.m.holloway@larc.nasa.gov>
Software Engineering epistomology
ACM SIGSOFT Software Engineering Notes V20n2(Apr 1995)pp20-21
=SURVEY LOGIC FALACIES PROCESS IMPROVEMENT How do we know that something is true:
1. Divine -> Absolute truth
2. Human -> Opinion
  Reason
3. Logic -> Conditional Absolute Truth
  Experience
4. Anedotal Experience -> Possible truth
5. Experimental Experience -> Probable truth
  Pronouncements with little logic or experiemne.
  Resistance to data collection in projects ....

HollowayButler96

C Michael Hollowy<c.m.holloway@larc.nasa.gov> & Ricky W Butler
Impediments to Industrial Use of Formal Methods
IEEE Computer Magazine V29N4(Apr 1996)pp25-26
=EXPERIENCE FORMAL METHODS
1. Tools: "Not only do the input languages use specialized notations from mathematical logic, but many tools have numerous bugs in them. Few things are more disconcerting..." need to improve quality of current not their power.
2. Examples are toy, interesting but irrelevnt
3. The first effort in a new domain requires far greater creativity than subsequent efforts.
  need to provide guidance for executives on matching method to applications. unbiased assessments.

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!

Holmes00a

Neville Holmes
Some Comments on the Coding of Programs
IEEE Computer Magazine V33n11(Nov 2000)pp128+126+127
=IDEA TECHNICAL CODE STYLE abbreviation punctuation layout
Code is not literature, even if comments should be!
Can systematically abbreviate later uses of identifiers.
Can line up parentheses and punctuation vertically. See p127 fig 5,

Holmes00b

Neville Holmes
Why Johnny Can't Program
IEEE Computer Magazine V33n12(Dec 2000)pp160+158-59
=EXAMPLES DESIGN DESIGN CODE READABILITY
ref to a column by Bertrand Meyer De 1999
Enumerate, illiterate, and overwhelmed.
split in-the-large system design from in-the-small programming craft
no proper training for either
possible bug in example code: does not eat initial spaces.

Holmes04

Neville Holmes
The usefulness of hindsight
IEEE Computer Magazine V37n11(Nov 2004)pp120+ 118-119
=ANECDOTE ANALYSIS USER DATA Ref [StrongVolkov04]

Holmes06

Neville Holmes
The Data Doughnut and the Software Hole
IEEE Computer Magazine V39n6(Jun 2006)pp100+98-99
=ESSAY MODULAR SYSTEMS ARCHITECTURE DATA vs INPUT vs OUTPUT INFORMATION IT DP ERP CSCI372
Claims that large systems fail because they are integrated rather than modular.
Best architecture has a central data base plus information processing programs around it.
(dick)|-These observations are still true even if they were first made 30 years ago.
(dick)|-However... there is a family of components that are neither input, output, or database. These are interactive interfaces for editing data. See Model-view-controler(MVC), Ambler on architecture, and so on back to SSADM and JSP.
Also see Gankarz for the Unix way of modularizing programs.

Holmes07

Neville Holmes
Binary ARithmetic
IEEE Computer Magazine V40n6(Jun 2007)pp90-93
=REFERENCE BINARY ARITHMETIC BITS ADDRESS INTEGER SCALED FLOATING POINT

Holmes08

Neville Holmes
The European Union and the Semantic web
=ADVERT UNIVERSAL LANGUAGES E-speranto ITL
IEEE Computer Magazine V41n8(Aug 2008)pp108+106-107 + Letter and rebuttal V41n10(Oct 2008)pp6-7
E-speranto::="a simplification of Esperanto".
Esperanto::="the most popular artificial universal language".
Letter from Patrick Durusau: People add ambiguity and idiosyncracies to any language they use -- including mathematics.
Reply -- Usage as an intermediate language should stop semantic drift and creative inconsistencies
Also see evidence of evolution/drift in invented languages -- [Okrent09]

Holmes09

Neville Holmes
Agility and respect
IEEE Computer Magazine V42n7(Jul 2009)pp100+98-99
=HISTORY ETHICS RESPECT PROGRAMMING vs ENGINEERING USER SERVICE NOT PROJECTS
Programming is a talent. Engineers should respect it. Programmming is a separate trade to engineering.
Development should focus on providing services to the enterprise not on projects.
A computer professional must be more than an expert on the technology.
Respect users by empowering them rather than programming them.
Also keynote at ASWEC2009 [ keynote-speakers ] (Link in article was broken).
(dick)|-Many programmers are craftspeople.
(dick)|-CASE tools did not change this, will model-driven tools?
Compare [Read03] and [WhittakerAtkin02] on programmers and coding.

Holmes09a

Neville Holmes
Truth and Breadth, Clarity and Depth in Algebra
IEEE Computer Magazine V42n11(Nov 2009)pp108+106-107
=ADVERT Formulator FUNCTIONAL TOOL SERIAL PARALLEL
Use APL/MATHS style operators to express complicated calculations in exact arithmetic.
Compare [CookeRushton09]

HolmesWalkerMurphy06

Reif Holmes & Robert J Walker & Gail C Murphy
Approximate Structural Context Matching: An Approach to Recommend Relevant Examples
ICSE'05 & IEEE Computer Magazine V39n12(Dec 2006)pp952-970
=DEMO TOOL TECHNICAL Eclipse HTTP JHotdraw Java FRAMEWORK USAGE REPOSITORY DATABASE Strathcona HEURISTIC SEARCH
Tools take an attempt at using a framework and look in existing libraries to find similar calls in a similar context: function, class, package.
Database contains 3M "structural facts": Database stores data on types, fields, methods, methods calling methods, accessing fields, and using types. Plus the type hierarchy.
Plausible claim: beats using grep!

Holt84

Richard C Holt
Turing (article)
Computerworld - InDepth pp1-6 May 14th 1984
=ADVERT language case-study

HoltCordy88

Richard Holt & Cordy
The Turing Programming Language
Commun ACM
v31n12(Dec 1988)pp1410-1423
=case-study formal TURING LANGUAGE

HoltCordyWortman82

?? Holt & James R Cordy & ?? Wortman
An Introduction to S/SL: Syntax/Semantic Language
ACM TOPLAS V4 n2 (Apr 1982) pp149-178
=ADVERT S/SL DDD language tools non-sequential

Holzmann97

Gerard J Holzmann
The Model Checker SPIN
IEEE Trans Softw Eng VSE23n5(May 1997)pp279-295
=ADVERT Buchi FSM/STD PROMELA HOL V&V PROOF
p290:"Most mature engineering disciplines include a methodology for constructing and analysing prototypes of designs"

Holzmann02

Gerard J. Holzmann
The Logic of Bugs
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp81-87
online at [ 587051.587064 ]
=Keynote BUGS V&V SQA MODEL CHECKING TOOLS NOTATIONS LOGIC GRAPHIC LTL SPIN TimeLineEditor
Human fallibility: abut 12 errors in 13800 sentences in a typical NYTimes. Careful programmers have similar error rates(?).
Argues that bugs evolve: the mutate and only some type survive.
The weakest point is where the bugs are to be found.
The weak point in model checking is the language used to specify requirements.
Suggests using a graphic notation instead of a temporal logic.

XieEngler02

Yichen Xie & Dawson Engler
Using Redundancies to Find Errors
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp51-60
=EXPERIMENT REDUNDANT CODE BUGS Linux
They found a very significant association between simple redundancies in code and bugs in the code.
redundancy::= idempotent operations + redundant assignments + dead code + redundant conditions - macros.
See .See [XieEngler03]

XieEngler03

Xichen Xie & Dawson Engler
Using Redundancies to Find Errors
IEEE Trans Software Engineering V29n10(Oct 2003)pp915-928
=DEMO REDUNDANT CODE ERRORS
See .See [XieEngler02]

XieYang03

Min Xie & Bo Yang
A Study of the Effect of Imperfect Debugging on software development cost
IEEE Trans Software Engineering V29n5(May 2003)pp471-473
=THEORY MINIMAL COST PROBABILISTIC STOCHASTIC ECONOMIC MODEL TESTING
Assumes effectiveness of testing effects cost.
Shows how to find optimal testing effectiveness and time to minimize total cost of testing, removing bugs while testing, and removing bugs in the field.

HolzmannSmith02

Gerard J. Holzmann & Margaret H. Smith
An automated verification method for distributed systems software based on model extraction
IEEE Transactions on Software Engineering V28n4(Apr 2002)pp364-377
=EXPERIENCE TOOLS FORMAL VERIFICATION SPIN/PROMELA C
CR review

Holzinger04

Andreas Holzinger
Usability Engineering methods for Software developers
Commun ACM V48n1(Dec 2005)pp71-74
=REFERENCE USER QUALITIES MEASURE TEST HCI SQA INSPECTION
usability::=(learnability, efficiency, memorability, low error rate, satisfaction).
usability_inspection_methods::= heuristic_evaluation + cognitive_walkthrough + action_analysis.
action_analysis =~= time_and_motion_analysis.
usability_test_methods::= thinking_aloud + field_observation + questionaires .
matrix on p 72.

Holzmann06

Gerard J Holzmann
The Power of 10: Rules for developing Safety-critical code
IEEE Computer Magazine V39n6(Jun 2006)pp95-97
=THEORY QUALITIES RELIABILITY RISKS TECHNIQUES LANGUAGE SAFE C CODE NASA/JPL
Given the aim is code that can be checked for risks... here are 10 rules.
My summary (with the first place I saw it)
1. Structured control flow. (Dijkstra 1960's)
2. All loops have a fixed upper bound on number of repetitions (Witty 1970's)
3. Don't allocate dynamic memory after initialization.
4. All functions less than one page and one line per declaration (UK Criminal records 1970's)
5. At least 2 assertions per function (IK Sturtevant in the 1970's)
6. Declare data objects in the smallest scope -- no globals! (1980's)
7. Check all input parameters inside each function and all returned values after each call.
8. Only simple preprocessing -- no ellipses or recursive macros.
9. Control pointers -- only one level of dereferencing, and never hidden in a macro/typedef. No function pointers.
10. Compile, from day 1, with all warnings on. Daily static analysis.
(dick)|-just use FORTRAN IV! The 9th rule means no object-oriented code, and rule 7 leads to an infinite regress of parameter checking. The above does nothing to control pointers and subscripts from going out of bounds.
See the venerable "Ten Commandments of C Programming" [ doc/C.commandments.txt ]

Hong05

Duan Hong
A Comparative Study of Pre/postcondition and Relational Approaches to Program Development
SQRL Report No. 23 McMaster U. 2005 [ sqrl_reports.html ] (PDF)
=UNREAD =THESIS CORRECTNESS RELATIONS vs CONTRACTS PRE/POST
Abstract

Honidenetal93

Shinichi Honiden & Nobuto Kotaka & Yoshinori Kishimoto
Formalizing Specification Modeling in OOA
Special Theme "Making OO Work" IEEE Software V10n1(Jan 1993)pp54-66
=ADVERT OBJECT-ORIENTED PROCESS NONSEQUENTIAL
1. software process analyzed as DFDs with backtracking; then into
2. substep::=Net{triggers, inputs, outputs, activities}
3. p62 "In essence, the object-oriented specification process is not sequential. Each step should be executed side by side.",
4. p63 "Our model does not take into account the know-how held by domain experts. This is a problem of how to extract information from a speciifcation written in a natural language."

Honidenetal94

Shinichi Honiden & Kazuhiko Nishimura & Naoshi Uchihira & Kiyoshi Itoh
An Application of Artificial Intelligence to Object-Oriented Performance Design (OOPD) for Real-Time Systems
IEEE Trans SE VSE-20n11(Nov 1994)pp849-867
=DEMO LOGIC NONDECLARATIVE OBJECT-ORIENTED PROLOG MENDEL
Automatic redesign of lift controler to avoid bottleneck

Hoomanetal92

J J Hooman & S Ramesh & W P de Roever
A Compositional axiomatization of Statecharts
Theor Comput Sci v101n2(20 July 1992)pp289-335 (Papers from BCS-FACS workshop on Semantics for Concurrency July 1990) CR9307-0468(D.2.1)
=THEORY SEMANTICS FSM STATECHARTS NONSEQUENTIAL

Hopgood03

Adrian A Hopgood
Artificial Intelligence: Hype or Reality?
IEEE Computer Magazine V36n5(May 2003)pp24-28
=HISTORY AI

Hopkins94

Mark Hopkins<mark@omnifest.uwm.edu>
"Re: 'Program Verification: The Very Idea' ..."
E Mail Aug 23..Aug 31 1994
=THEORY GRAMMAR CODE TECHNICAL STRUCTURE DIGRAPH NONSEQUENTIAL CFL
1. CCFL::=concurrent context free language.
  Finite intersections.
  "chipping away at the language block without driving a stake through its center is a characteristic of "[the 1970's]
  Automata - infinite state have a revealing structure: N dimensional!
  Context Free Expressions for nonCFLs!
  Interleaving is like processing concurrently.
  Liu and Wiener

Horch95

John W Horch
Review of "Object Lessons" by Tom Love
IEEE Software Magazine V12n2(Mar 1995)pp117-119
=REVIEW EXPERIENCE vs TEXT

Horning94

James J Horning(DEC SRC)
Computation Engineering: Foundations & Metaphors & Metrics
Abstract from Keynote Address SIGSOFT'94 Proc 2nd ACM SIGSOFT Symp on Foundations of Software Engineering & ACM SIGSOFT Software Engineering Notes V19n5(Dec 1994)p1
=KEYNOTE

Horowitz05

Alan S Horowitz
IT workers: You can't always guess what they want
Computerworld(Sep 12 2005)
=ARTICLE MANAGEMENT MOTIVATION PEOPLE
Confirms previous research: [CougerZawacki01] (1980) [RubinHernandez88] [Kanetal94] [ThomasHunt04b]
Money can cause dissatisfaction rather than motivation.
More important: a meaningful task, recognition, security, access to new stuff, humane work schedule, contributing value.
Perhaps three types: some want to continue as is, some want new technical challenges, and some want to become managers.
Perhaps two: interested in the business vs interested in the technology.
Managers need to open up upward channels of communication: surveys, meetings, chats, lunches, skip-level, ...
Given a choice of reward: 40% would choose flextime&telecommuting, 35% an 8% raise, 13% a week of paid vacation, 12% better benefits and health insurance.

Horrocks08

Ian Horrocks
Ontologies and the Semantic Web
Commun ACM V51n12(Dec 2008)pp58-67 [ 1490360.1409377 ]
=POPULARIZATION WEB ONTOLOGIES SEMANTICS LOGIC RULES RDF OWL
Figure 2:the Tree of Porphyry [ Tree_of_Porphyry ] (Wikipedia) and [ Stuff in logic_8_Natural_Language ] (MATHS)
RDF expresses labelled directed graphs: subject --(verb)--> Object. What we used to call semantic nets in the 1970s.

HouHoover06

Danqing Hou & H James Hoover
Using SCL to Specify and check Design Intent in Source Code
IEEE Trans Software Engineering V32n6(Jun 2006)pp404-423
=CASESTUDY TOOL V&V SQA STATIC CHECK TECHNICAL CODE Java C++ MVC
SCL::="Logic based language and tool that expresses and checks constraints on object-oriented code"
Typical constraint: In Java all classes derived from Object should define a public boolean equals(Object o) method, not one with another parameter type.
Lint for the 21st century.

Houghton83

?? Houghten
software development tools: a profile
Computing(IEEE) (May 1983) pp63-70
=SURVEY TOOLS

Houghton84

?? Houghton
Online Help Systems: A Conspectus
Commun ACM V27n2(Feb 1984) pp126-133
=SURVEY USER HELP

Houlding00

David Houlding
Publish and subscribe with CORBA Web Events
Dr. Dobbs #314(Jul 2000)pp88+90-96+97
=EXAMPLE chat TECHNICAL CORBA JAVASCRIPT WWW NONSEQUENTIAL UML
compare simpler [RouselleGreff00]

HoustonKing91

Iain Houston and Steve King
Experiences and results from the use of Z in IBM
CICS Project Report, pp. 588-595 in VDM Europe 91
=EXPERIENCE Formal maintenance Z IBM CICS

Hovenden00

Fiona Hovenden
A Meeting and A Whiteboard (describing the power to speak)
Proc SCI/ISAS2000 VI pp743-746 [SCI00]
=EXPERIENCE PEOPLE ETHNOGRAPHY
"This apparent alliance between speaker and whiteboard begins to raise some questions. What is it about proximity to, and use of the whiteboard, which facilitates, or even patrols, speaking in IT meetings? Is it possible for sustained discussion to occur in an IT meeting, without recourse to the whiteboard (or some other object/channel which carries the illustrative function)?"

Hovy03

Eduard Hovy
Using an Ontology to simplify data access
Commun ACM V46n1(Jan 2003)pp47-49
=DEMO ONTOLOGY DATA BROWSE SENSUS GAW EDC

Howden76

W E Howden
Reliability of the path analysis testing strategy
IEEE Trans SE V2(??? 76)pp208-215)
=THEORY TESTING

Howden82a

W E Howden
Contemporary Software Development Environments
Commun ACM 25 5 (May 1982)
=SURVEY IDE tools

Howden82b

WE Howden
Validation of Scientific Programs
Comp Surveys v14n2(Jun 1982)pp193-227
=SURVEY JSP SQA PURPOSE

HowdenWieand94

W E Howden & Bruce Wieand
QDA - A Method for Systematic Informal Program Analysis
IEEE Trans SE V20n6(Jun 1994)pp445-462
=DEMO QUALITY COMMENTS TECHNICAL SQA OBJECT-ORIENTED
1. {properties of X are P} X is Q {properties of X are P| Q}
2. {properties of X are P} X is and only is Q {properties of X are Q}

Hruby06

Pavel Hruby
Model-driven design using Business patterns
Springer-Verlag NY Secaucus NJ 2006 ISBN 3540301542 CR 0802-0114 & 0804-0322
=UNREAD =THEORY PATTERNS COMMERCIAL ANALYSIS REQUIREMENTS CAPTURE REA
REA::=Net{resources, events, agents}.
Notes [click here if you can fill this hole]

Hsia93

Pei Hsia
Learning to put Lessons in to Practice
IEEE Software Magazine V10n5(Sep 1993)pp14-17
=EDITORIAL EXPERIENCE ETHICS PROCESS QUALITY
Editor's introduction to special issue on the lessons learned in doing software engineering. Suggests that it is a moral issue - to make the documented process match the actual practice; to make quality more important than productivity.

Hsia96

Pei Hsia
Making Software Development Visible
IEEE Software Magazine V13n3(May 1996)pp13-1726
Editor's introduction to special issue on the lessons learned
[Hsia93]
=EDITORIAL MODEL SOFTWARE
Since we can only see software by seeing it run we must use incremental or evolutionary development. "It is the large to enormous projects that get away from us. Why not break a large project down into smaller ones"..."system decomposition"..."guided by the designer not by the user"[is the wrong way.

HsiaDavisKung93

Pei Hsia & Alan M Davis & David C Kung
Status Report: Requirements Engineering
IEEE Software magazine v10n6(Nov 1993)pp75-79 + Correspondence with (Edward LaBudde) IEEE Software magazine v11n2(Mar 1994)pp6&8
=FLAME METHODS

Hsiaetal94

Pei Hsia & Jayarajan Samuel & Jerry Gao & David C Kung & Yasufumi Toyoshima & Chris Chen
Formal Approach to Scenario Analysis
IEEE Software magazine v11n2(Mar 1994)pp33-41+ correspondence v11n4(Jul 1994)p5
=IDEA SCENARIO FORMAL Letter
1. Mark Ardis corrects errors in original:
2. scenarios have to be cross-validated for misnamed events
3. concurrent scenarios have to be checked for dead-locks
4. need event lists for checking
5. use simulator V1(Jul 2002)pp
6. =POLL WEB USER CULTURE PEOPLE DIFFERENCES
7. Preferences of web page styles in 3 cultures Japan,china, UK. Certain things a definitely bad in all cultures (eg: No title). some things a good in only 1 culture: china pinkpages.
8. Note: data confounds culture and gender.
Huff92
1. Clifford C Huff
2. Elements of a CASE Tool Adoption Budget
3. Commun ACM V35n4(Apr 1992)pp45-54
4. =EXPERIENCE CASE COSTS
5. Total 5yr costs/station=$40K
HughesBultan08
1. Graham Hughes & Tevlik Bultan
2. Interfaces Grammars for Modular Software Model Checking
3. IEEE Trans Software Engineering V34n5(Sep/Oct 2008)pp614-632
4. =DEMO GRAMMAR INTERFACE MODEL CHECKING EJB TOOL JPF
5. Uses nested context free grammars with semantic elements <<action>>.
6. Meaning as traces including calls and returns from methods using structural operational semantics -- derivation rules.
7. Interface grammar language....
8. Describes how EJB Persistance API is used.
9. Algorithms for model checking.
10. Experiments -- some executions took 13 seconds.
HughesPowell81
1. Janet Hughes & ?? Powell
2. Program Design
3. pp 63-73 of Proc. of Workshop on Program Specification & Design (Aug 1981) Ed Staunstrup Springer Verlag 1981
4. =DEMO DESIGN formal non-sequential DFD DDD
HuiChau02
1. Kai Lung Hui & Patrick Y K Chau
2. Classifying Digital Products
3. Commun ACM V45n6(Jun 2002)pp73-79
4. =IDEA GRID DIGITAL E-COMMERCE
5. Sets up 3D grid and finds examples of each..
6. Grid=delivery_mode><Granularity><trialability.
7. delivery_mode:={download, interactive}.
8. granularity:=low..high.
9. Trialability:=low..hight.
Hulletal91
1. M E C Hull & P G O'Donoghue & B J Hagan
2. Development Methods for Real-Time systems
3. Comput Jnl V34n2(Apr 1991)pp164-172 Review Chris Hallgren CR9203-0182
4. =SURVEY METHODS JSD MASCOT MOON HOOD
5. JSD+MASCOT 3 ==> MOON
6. HOOD
7. "the design methods all support diagramatic notations..."
HullJHart01
1. Jonathon J Hull & Peter E Hart
2. Toward Zero-Effort personal Document Management
3. IEEE Computer Magazine V34n3(Mar 2001)pp30-35
4. =ADVERT Save everything! Ricoh
5. IM^3 := "infinite memory multi-function machine".
6. copiers and printers save copy into store for indexing and retrieval.
HullKing87
1. R Hull & R King
2. Semantic Database Modeling: Survey, Application, and Research Issues
3. ACM Computing Surveys V??n??(Sep 1987)pp210-260
4. =SURVEY ERD
Humby73
1. E Humby
2. Programs from Desion Tables
3. Macdonald London UK & American Elsevier NY NY 1973 ISBN 0-356-04126-3 & 0-444-195969-6 respectively LCCard#72-90803
4. =HANDBOOK Tables SQA REQUIREMENTS QUALITY COMPLETENESS AMBIGUITY implementation COBOL
5. A Decision Table is an early non-procedural and non-language description of requirements and logic. They can be translated into code. Manually they where difficult to maintain.
6. They are a table with two parts. First come the conditions -- one per row and then come the actions.
7. Each condition can (in a simple decision table) have one of two values: T or F. The columns indicate T, F, and - (either). In the actions an X indicates an action to be done and a - one that is not done (we can also use A,B,C, ... in a column to indicate the sequence of actions.
8. Example Decision table from page 88
  Table
  Labels Rules 1 2 3 4
  C1 He knows N N Y Y
  C2 He knows C1 N Y N Y
  A1 Shun him X - - -
  A2 Teach him - X - -
  A3 Wake him - - X -
  A4 Follow him - - - X
  
  (Close Table)
Humelsine10
1. Jim Humelsine
2. Software still as much an art as science
3. Commun ACM V53n1(Jan 2010)p7 [ 1629175.1629176 ]
4. =ESSAY THEORY vs PRACTICE PROOF TESTS CLIENTS REQUIREMENTS UNCLEAR COMPLEX
5. Reply to [Hoare09]
6. Asserts I use program proving but clients can't give me a clear specification...
Humphrey89
1. Watts S Humphrey
2. Managing the Software Process
3. Addison-Wesley Reading Mass 1989
4. =TEXT PROCESS SCIENTIFIC MANAGEMENT
5. "The disciplined application of engineering scientific and mathematical principles methods and tools to the econmical production of quality software"
Humphrey93
1. Watts S Humphrey
2. Review of Dwyer92 "The Cleanroom Approach..."
3. IBM Sys Journal V32n2(1993)pp328-329
4. =REVIEW CLEANROOM
Humphrey94
1. Watts S Humphrey (SEI)
2. The Personal Software Process(PSP)
3. =ADVERT PSP
4. Presentation 3:30pm Aug 23rd (Maturing the Process) the 94th Software Engineering Symposium SEI 1994
Humphrey95a
1. Watts S Humphrey (SEI)
2. A Discipline for Software Engineering
3. Addison-Wesley Redwood City CA 1995 (SEI Series in software Engineering)
4. ISBN 0-201-54610-8 BNB 93-41673 QA76.758H857
5. =TEXT PSP IMPROVEMENT ESTIMATION METRICS
  1. (ac)|-Did not work well as CS455(Software Engineering) text.
    Includes logic and statistics! Goal-Question-Metric. Tables("Templates") in chapter 10 "software design".
    See [Humphrey95b] for quick summary.
    Reviewed by Tom DeMarco: revolutionary idea that individuals should be responsible for estimation and measurement, not institutions. Weakest in low-level design. IEEE Computing Magazine Oct 1995 pp82-83
    Follow ups: Textbook on PSP: [Humphrey97;] the Team Software Process( [TSP] ), introduction [Humphrey00]
Humphrey95b
1. Watts S Humphrey (SEI)
2. Making Process Improvement Personal
3. IEEE Software Magazine V12n5(Sep 1995)pp82-83
4. =ADVERT for [Humphrey95a]
  1. PSP::abreviation=Persona;l Software Process.
  2. PSP::=( PSP0; O(PSP0.1; O(PSP1; O(PSP1.1; O(PSP2; O(PSP2.1; O(PSP3) )))) ).
  3. PSP0::=learn to make and value simple measurements
  4. PSP0.1::=estimating and measuring program size
  5. PSP1::=historical data->linear_regression->estimator
  6. PSP1.1::=estimating and scheduling+eaarned value+progress of work to date
  7. PSP2::= design and code reviews & checklists & Pareto analysis & other methods of SQA
  8. PSP2.1::=design completenes and correctness(trace tables, execution tables, proofs); selecting methods of design and review
  9. PSP3::=scaling up to industrial sized projects; team work; project level work.
    Lots of good (but not new) advice
Humphrey96
1. Watts Humphrey
2. Using a Defined and Measured Personal Software Process
3. IEEE Software Magazine V13N3(May 1996)pp77-89
4. =advert for PSP
Humphey97
1. Watts S Humphrey
2. Introduction to the Personal Software Process
3. Addison-Wesley Longman Reading MA 1999 CR9711-0870
4. =TEXT PROCESS PEOPLE CMM PSP IMPROVEMENT PAPERWORK STANDARDS
Humphrey00
1. Watts S Humphrey
2. Introduction to the Team Software Process
3. Addison-Wesley Longman Essex UK 2000 ISBN 0-201-47719 CR9910-0765
4. =TEXT PROCESS PEOPLE TEAM CMM PSP IMPROVEMENT PAPERWORK MANAGEMENT
5. TSP::=Team Software Process
Humphrey00b0
1. Watts S Humphrey (Guest Editor)
2. The Personal Software Process: Status and Trends (Special section)
3. IEEE Software Magazine V17n6(Nov/Dec 2000)pp71-103
4. =EXPERIENCES PSP
5. Half a dozen papers on PSP in practice. [Morisio00]
Humphreyetal91
1. Watts Humphey & Terry R Snyder & Ronald R Willis
2. Software Process Improvement at Hughes Aircraft
3. IEEE Software V8n4(Jul 1991)pp11-23
4. =ADVERT IMPROVEMENT HUGHES
5. See also [WohlwendRosenbaum94]
HungerfordHevnerCollins04
1. Bruce C Hungerford & Alan R Hevner & Rosann W Collins
2. Reviewing Software Diagrams: A Case Study
3. IEEE Trans Software Engineering V30n2(Feb 2004)pp82-96
4. =EXPERIMENT V&V SQA INSPECTION DFD ERD
5. Most defects found by experienced developers who rapidly switch between DFDs and ERDs.
HuntbachRingwood95
1. Mathew M Huntbach & Graem A Ringwood
2. Programming in Concurrent Logic Languages
3. IEEE Software Magazine(Nov 1995)pp71-82
4. =PAPER TECHNICAL NONSEQUENTIAL vs NONDETERMINISM BACKTRACKING PERFORMANCE
5. adding paralelism efficiently means redefining nondeterminism and so abandoning backtracking with result that is not logic programming
HunterNuseibeh97
1. Anthony Hunter & Bashar Nuseibeh
2. Analysing Inconsistent Specifications [RE'97] pp78-86
3. =FORMAL REQUIREMENTS LOGIC
4. REQUIREMENTS LOGIC must not include ex falso quodlibet and should track all inferences from stated requirements to conclusions and so aid diagnosis of inconsistencies
5. QC::="Quasi Classical Logic"
HunterNuseibeh99
1. Anthony Hunter & Bashar Nuseibeh
2. Managing Inconsistent specifications: Reasoning, Analysis, and Action
3. ACM ToSEM V7n4(May 1999)pp335-367
4. =IDEA labelled QC Quine FORMAL LOGIC SPECIFICATION
5. Label requirements and record deductions so that you can back track when inconsistent ones emerge. [QC]
6. Compare with the way mathematicians handle inconsistencies in [Lakatos76].
7. (dick)|-my MATHS notation uses
```
 		(reason, reason, ...)|-(label): statement.
```
  to record such connections but does not allow the same freedom in abandonning and adjusting the logic.
HuntKloster87
1. Valerio R Hunt & Gregory V Kloster
2. The Federal Aviation Administration's Advance Automation Program
3. IEEE Computer Magazine V20n2 (Feb 1987)pp14-17
4. =ARTICLE FAA AAS
5. See [Barlas96]
  [Barlas96a]
  [KlosterZellweger87]
  [PhillipsMD87]
  [AvizienisBall87]
  [BleisteinEtal87]
  [GarotEtal87]
HuntThomas02
1. Andy Hunt & Dave Thomas
2. software Archeology
3. IEEE Software Magazine V19n2(Mar/Apr 2002)pp20-22
4. =ESSAY LEGACY EVOLUTION CODE JARGON
5. analogy: digging into ancient cultures.
6. first make an inventory and initial version control to protect the site.
7. Make maps: notes and diagrams and use tools to find things. Meticulous records.
8. Watch out for curses: misleading code, name, comments, etc. Build a rosetta stone.
9. Add tracing statements carefully (AspectJ!) and look out for Heisenbugs.
10. Aerial views with visualization and synopses. SignatureSource.
11. Respect the culture and learn its weaknesses and strengths.
12. Sidebar lists tools from workshop at OOPSLA 2001
13. leave clues, a map says where, a glossary explain language, comments say why, code says how.
HuntThomas02a
1. Andy Hunt & Dave Thomas
2. Zero-Tolerance Construction
3. IEEE Software Magazine V19n5(Sep/Oct 2002)pp100-102
4. =IDEA TECHNICAL QUALITY CODE MAINTENANCE EVOLUTION
5. Theory (based on urban decay) that even a small unfixed defect(broken window) encourages the development of serious defects and unmaintainable software.
6. So fix even the smallest problem -- or board it up and put up danger signs around it.
7. Quotes XP: don't let the sun set on bad code -- fix it or throw it out.
8. Quotes Scrum: have to produce a working subset in 30 days.
HuntThomas04b
1. Andy Hunt & Dave Thomas
2. Keep it DRY, Shy, and Tell the Other Guy
3. IEEE Software Magazine V21n3(May/Jun 2004)pp101-103
4. =ARTICLE Object-Oriented style
5. Funny but good.
6. DRY:="Don't Repeat Yourself",
7. Shy:="Don't talk to strangers and keep things to your self".
8. Don't call us we'll call you: it is better to send commands than get data.
9. Defines 4 couplings: static, dynamic, domain, temporal.
HuntThomas03
1. Andy Hunt & Dave Thomas
2. Preparing the Raw Material
3. IEEE Software Magazine V20n5(Sep/Oct 2003)pp97-98
4. =ESSAY GOOD PEOPLE
5. Software development is a mental activity. We are the raw materials. good people: pragmatic, take multiple views, take responsibility, communicate well , and learn.
6. (Confucius)|-"Hearken to [...] words and watch their deeds"
HuntThomas04
1. Andy Hunt & Dave Thomas
2. Three Legs, No Wobble
3. IEEE Software Magazine V21n1(Jan/Feb 2004)pp18-19+22
4. =ADVERT CODE PRACTICE TOOLS
5. Ruining code
  1. Never look back at your code.
  2. Never improve your code.
  3. What ever you do, avoid doing it the same way twice.
  vs Best practices
  - Version control.
  - Unit testing. using professional, automatic, independent, repeatable code.
  - Automation.
HuntThomas04c
1. Andy Hunt & Dave Thomas
2. Imaginate
3. IEEE Software Magazine V21n5(Sep /Oct 2004)pp96-97
4. =ANECDOTE USERS PRAGMATIC RAPID COBOL AGILE
5. By using old technology that works and gives the user what they want rapidly you can do what is impossible using the latest technology and methods.
6. imaginate::="to instantiate into reality by pure will of imagination".
HurnausPrahofer
1. D Hurnaus & H Prahofer
2. Programming assistance based on contracts and modular verification in the automation domain
3. Applied Computing, Sierre, Switzerland (Mar 22-26 2010)pp2544-2551
4. =CASE STUDIES TOOL IDE LANGUAGE GRAPHIC DSL MONACO MODULAR FLOWCHART CONTROL MODEL CHECKING AI BELIEF UPDATE
5. Two case-studies of a system that helps users construct correct industrial control programs by using hidden formal methods.
6. In a changing world, what beliefs should we abandon when a new truth is asserted?
Hursonetal93
1. A R Hurson & Simin H Pakzad & Jia-bing Cheng
2. Object-oriented Database Management Systems: Evolution and Performance Issues
3. IEEE Computer Magazine V26n2(Feb 1993)pp48-60
4. =SURVEY OBJECT-ORIENTED DATA OODBMS QUALITY SPEED MAINTENANCE
MunozDowekCarreno04
1. Cesar A Munoz & Gilles Dowek & Victor Carreno
2. Modeling and Verification of an Air Traffic Concept of Operations
3. Proc ISSTA 2004 & ACM SIGSOFT Software Engineering Notes V29n4(Jun 2004)pp175-182
4. =EXPERIENCE THEOREM PROVING PVS CONCEPT of OPERATIONS V&V REQUIREMENTS ATC Airport SATS-HVO
5. Concept_of_operations::="a collection of rules and procedures".
6. Uncovered 10 issues in proposed concept of operations that where accepted into a revised form.
7. The model also had to be revized...
8. Model checking could not handle the 213 boolean variables needed,
9. PVS allowed a more abstract expression of the concepts and the verification that it permitted only safe states.
10. Given no more than 4 planes at a time, depth first exploration discovered no more than 2811 reachable states. The algorithm (depth first) was written and proved using PVS. [ http:researcch.nianet.org/~munoz/Besc ]
Huth04
1. Michael Huth
2. Mathematics for the Exploration of Requirements
3. ACM SIGCSE Bulletin V36n2(Jun 2004)pp34-39
4. =EXAMPLE Uncertain Mathematical Specifications Alloy TOOL =CASESTUDY .NET cache
5. =ADVERT 2nd edition [HuthRyan00] [ http://www.cis.ksu.edu/~huth/lics/ ]
6. Checking Specifications for inconsistency and to see if they meet goals and objectives.
7. Shows that tools & languages for requirements drive discussions rather than solve problems. Some tools will generate spurious diagnostics.
HuthRyan00
1. Michael R Huth & Mark Ryan
2. Logic in Computer Science: Modeling and reasoning about systems
3. Cambridge U P 2000 ISBN 0 521 65200 6 (hardback) ISBN 0 521 65200 8 (paperback)
4. =TEXT FORMAL MODEL LPC MODAL LOGIC CTL OBDDs AGENTS VERIFICATION SMV CSUSB.CSCI556/656
Hutt94
1. Andrew T.F. Hutt
2. Object Analysis and Design: Description of Methods
3. (OMG/Object Management Group)Published by John Wiley and Sons Inc - QED Books. 1994 ISBN 0-471-62366-0 $58
4. =SURVEY OBJECT-ORIENTED METHODS OMG
Hutton95
1. Len Hutton ??
2. Safer C : Developing Software for High-integrity and Safety-critical Systems
3. McGraw-Hill 1995
4. =TEXT RISKS C
5. See [Hatton95a]
IacovouDexter05
1. Charalambos L Iacovou & Albert S Dexter
2. Surviving IT Project Cancellations
3. Commun ACM V48n4(Apr 2005)pp83-86
4. =SURVEY Delphi 36 IT CONSULTANTS
5. Gives list of the 18 top ranked actions for when a projects fail:
  1. prepare a communication plan to contain misinformation and rumor and so limit damage
  2. Perform a post mortem to determine causes of failure
  3. Form a contingency plan with sponsor
  4. Modify process to fit discoveries
  5. Reflect on your own role and responsibilities.
  6. ...
IacovouNakatsu08
1. Charalambos L Iacovou & Robbie Nakatsu
2. A Risk profile of offshore-Outsourced Development Projects
3. =SURVEY OFFSHORE DISTRIBUTED DEVELOPMENT
4. Commun ACM V51n6(Jun 2008)pp89-94
5. It sounds like the usual suspects: lack of management commitment, miscommunicated requirements, Inadequate user involvement, Failing to manage expectations, Poor change control, developers don't understand the business or the technology, unexpected costs.
IBM86
1. International Business Machines
2. Document Content Architecture: Revisable Form Text Reference(DCA-RFT)
3. IBM SC23-0758-1(1986)
4. =PROPOSAL DCA RFT
IBM88
1. International Business Machines
2. Architecture for Object Interchange
3. IBM GC24-3296-00(Nov 1988)
4. =PROPOSAL
ICP89
1. ICP million dollar awards
2. The people's choice awards(Special report)
3. System Builder v2n3(Jun/Jul 1989)pp27-34
4. =ADVERT
ICSE'97
1. ACM & IEEE CS
2. Proceedings of the 1997 International Conference on Software Engineering
3. May 17..23 Boston MA USA
4. ISBN 0-89791-914-9 ACM Order #592970 IEEE CS Order #0270-5257 also bound and on microfiche
5. =PROCEEDINGS ICSE
IEEEStd1044-1993
1. IEEE Standards
2. IEEE Standard Classification for Software Anomalies
3. IEEE Computer soc Press 1994(SH 16915 $38)
4. =STANDARD BUGS ERRORS DEFECTS
IEEESWMag03
1. Laurie Williams(Ed)
2. Special edition on XP
3. IEEE Software Magazine V20n3(May/Jun 2003)pp14-47
4. =ISSUE XP
5. Includes XP vs CMM [Reifer03], Introduction [Williams03], Introducing XP [Rasmusson03], XP and scientific programming [WoodKleb03], XP in europe Internet .See[MurruDeiasMugheddu03]
6. Debate: requirement planning(Annie I Anton) vs planning to solve wrong problem (don wells)
Iivari96
1. Juhani Iivara
2. Why are CASE Tools are Not Used
3. Comm ACM V39n10(Oct 1996)pp94-103
4. =ARTICLE CASE
5. CASE has a good effect but is not used
Ilgunetal95
1. Koral Ilgun & Richard A Kemmerer & Phillip A Porras
2. State Transition Analysis: A Rule-Based Intrusion Detection approach
3. IEEE Trans on Software Eng VSE-21n3(Mar 1995)pp181-199 CR9602-0130 D.4.6
4. =FORMAL FSM/STD RULES SECURITY
InKimYangBoehm06
1. Hoh Peter In & Sansoo Kim & Ye Yang & Barry Boehm
2. A Quality-based cost estimation model fro the product line life cycle
3. Commun ACM V49n12(Dec 2006)pp85-88
4. =THEORY COCOMO II COQUALMO COPLIMO qCOPLIMO -> QUALITY ROI
Ince88a
1. Darrel C Ince
2. An Introduction to Discrete Mathematics and Formal System Specification
3. Clarendon Press Oxford UK 1988
4. =TEXT Z MATH
5. Next edition reviewed [Ince93]
Ince88b
1. Darrel C Ince
2. Software Development: Fashioning the Baroque
3. Oxford U press UK 1988
4. =SURVEY RISKS
Ince92
1. Darrel C Ince
2. Review of "Foundations of Computer Science" by Aho and Ullman
3. Times Higher Education Supplement Page 30 September 25th 1992 TIMES/Mirror London UK
4. =REVIEW TEXT PROGRAM PROVING HARMFUL
Ince93
1. Darrel C Ince
2. An Introduction to Discrete Mathematics and Formal System Specification, and Z
3. Oxford Univ Press NY NY 1993 ISBN 0-19-853836-7 CR9508-0570
4. =TEXT Z MATH
  1. (CR9508-0570, Berztiss)|-errors in book - treating "only if" as "iff", loosing track of units(volts expecially).
Ingebretsen08
1. Mark Ingebretsen
2. Unconferences catch on with Developers
3. IEEE Software Magazine V25n6(Nov/Dec 2008)pp108-110
4. =REPORT SELF-ORGANIZING MEETINGS ORGANIZATION PEOPLE FOOcamps BarCamp DemoCamp Web2Open openspace meetings Eclipse Microsoft Canada
5. Tools for planning, problem solving, and product invention and development.
6. 1983 Harrison Owen: why not a conference made up of coffee breaks only ----> Open Space Technology. More done in two days than months done other ways.
7. Wiki [ http://www.barcamp.org ]
8. Several frameworks. Before: announce a real important goal. Initially participants list issues to meet goal. People select breakout sessions on issues. Breakout session activity is recorded. Records put on Wikis and/or blogs. Groups may report back in a plenary session.
9. "You need to have places where people can just bump into each other".
Ingevaldsson79
1. ?? Ingevaldsson
2. JSP: a Practical Method of Program Design
3. Studentlitteratur Sweden INPUT TWO-NINE UK
4. =TEXT DDD non-sequential
InverardiWolf95
1. Paola Inverardi & Alexander L Wolf
2. Formal Specification and Analysis of Software Architecture Using the Chemical Abstract Machine Model(CHAM)
3. IEEE Trans on Software Eng VSE-21n4(Apr 1995)pp373-386
4. =THEORY ARCHITECTURE THEORY GAMMA LANGUAGE NONSEQUENTIAL
IoannidisWong91
1. Yannis E Ioannidis & Eugene Wong
2. Towards an Algebraic Theory of Recursion
3. Journal ACM V38n2(Apr 1991)pp329-381 CR9206-0416
4. =MATHS RECURSION RELATIONAL KLEENE ALGEBRA
5. CR9206-0416:"They show that all relational algebra operators form a closed semiring and that an immediate linear recursive query is answered by solving an equation in an explicit form" - kleene and accelerated iterations. Multilinear rcursion->bilinear_recursion. Some bilinear recursions have unique solution
InverardiTivoli01
1. Paola Inverardi & Massimo Tivoli
2. Automatic Synthesis of deadlock free connectors for COM/DCOM
3. ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp121-131
4. =CASESTUDY NONSEQUENTIAL MODULE CCS C2 CBA ARCHITECTURE MICROSOFT
InveradiWolfYankelevich00
1. Paola Inveradi & Alexander L Wolf & Daniel Yankelevich
2. Static Checking of System Behaviors Using Derived Component assumptions
3. ACM TOSEM Trans Software Engineering & Methodology V9n3(Jul 2000)pp239-272
4. =ALGORITHM DYNAMIC MODULE ERRORS DEADLOCK CHAM
  1. Given specification of each component's interaction behavior
  2. Calculate actual behavior patterns and assumptions about external environment.
  3. Compare assumptions with actuals.
  4. Return True iff no dealocks
5. True means no deadlocks but false means may or may not be deadlocks
6. AC and AS Graphs.
7. state_space = O( nstates * ngraphs ).
8. complexity := O( nstates! * ngraph**2 * log( ngraph ) )
9. Applied to Compressing Proxy example from the ERN HTTP server with gzip. Architecture clash pipes vs function calls.
10. Inert states have no applicable transformation.
11. Specs give initial and final states.
12. Deadlock if there is an inert but nonfinal state.
IribaneTroyaVallecillo04
1. Luis Iribane & Jose M Troya & Antonio Vallecillo
2. A Trading Service for COTS Components Computer Journal V47n3( 2004)pp342-357
3. =EXAMPLE COTS WEB/NET COMPONENTS TRADING XML MODULE SPECIFICATION CORBA CBSD XML
4. includes functional, properties, packaging and marketing fields.
IriberriLeroy09
1. Alicia Iriberri & Gondy Leroy
2. A life-cycle perspective on online community success
3. ACM Computing Surveys V41n2(Feb 2009) a11 CR 1008-0832
4. =SURVEY WEB/NET PEOPLE COMMUNITIES MANAGEMENT SOCIOLOGY SOCIAL
5. online_community::lifecycle= #(inception(need, vision); Creation(purpose, technology, people); Growth(rules, roles, identity) Maturity(regulations, subgroups, trust, relationships) ); (Inception; Creation; Growth; Death|).
6. Death comes from lack of contributions, poor participation, transient membership, not enough quality content, etc..
Irons61
1. ?? Irons
2. A Syntax Directed Compiler for Algol 60
3. Commun ACM V4()pp51-55 (also CACM25)
4. =HISTORY DDD
Irons63
1. ?? Irons
2. The Structure & Use of the Syntax Directed Compiler
3. Ann Rev in Auto Proging v3 pp207-227
4. =HISTORY DDD history
Isakowitzetal95
1. Tomas Isakowitz & Edward A Stohr & P Balasubramanian
2. RMM: A Methodology for Structured Hypermedia Design
3. Commun ACM V38n8(Aug 1995)pp34-43
4. =ADVERT RMM METHOD ERD DESIGN HYPERTEXT DEMO NET/WWW GUI
  1. RMM::=Relationship Management Methodology.
  2. ERD->-RMDM(Relationship ManagementData Model)
  3. slices::=how the information selected from a set of entities is presented to users and how they can access it.
  4. access primitives( unidirectional & Bidirectional links, Groupings, condition indexes, conditional guided tour, conditional index/guided tour)
Isakowitzetal96
1. Tomas Isakowitz & Robert J Kauffman
2. Supporting Search for Reusable Software Objects
3. IEEE Trans Softw Eng VSE22N6(Jun 1996)pp407-423
4. =PAPER REUSABLE CODE
  [PoulinWerkman95]
5. Extensions to ICE rule driven VHL CASE
Isberg02
1. Wes Isberg etal(AspectJ team)
2. Get Test-Inoculated
3. Software Development Magazine V10n5(May 2002)pp40-43
4. =ADVERT AspectJ AOP TESTING
5. Can, for example, specify and action to be taken any time a private variable is changed outside a setter method.
Ishida02
1. Toru Ishida
2. Q: A scenario description Language for Interactive agents
3. IEEE Computer Magazine V35n11(Nov 2002)pp42-47
4. =DEMO LANGUAGE SCHEME Q AGENT DESCRIPTION SCENARIO GUARDED COMMANDS CSP-like interaction design
5. cue:=("?" name #argument).
6. action:=("!" name # argument).
7. Other functors: guard, defscenario, defagent, defavatar, defcrowd,...).
8. Excel front end -- interaction pattern card
Islam97
1. Nayeem Islam<mailto:nayeem@watson.ibm.com>
2. Customizing System Software using OO Frameworks
3. IEEE Computer magazine V30n2(Feb 1997)pp69-78
4. =EXPERIEMENT object-oriented control-flow graphs help automatic selection of concurency components to fit given qualities
IslamDevarakonda96
1. Nayeem Islam & Murthy Devarakonda
2. An Essential Design Pattern for Fault-Tolerant Distributed State Sharing
3. Comm ACM V39n10(Oct 1996)pp65-76
4. =ADVERT Recoverable Distributor Pattern ARCHITECTURE DISTRIBUTED NONSEQUENTIAL NET
Isner82
1. ?? Isner
2. A FORTRAN Methodology based on data abstraction
3. Commun ACM V25 n10 (Oct 1982) pp686-697
4. =DEMO ADTs FORTRAN
Isoda03
1. Sadahiro Isoda
2. A Critique of UML's Definition of the Use-Case Class
3. LNCS 2863 <<UML>> 2003 -- The Unified Modeling Language Oct 2003, pp280-294
4. =CRITIQUE UML OOSE USECASE MODEL
5. Surveys history and definitions of usecase, includes, extends, and generalization. "an Usecase instance is an execution of a usecase"
6. ACU conjecture: An actor calls use cases.
7. Proposal. Make an OO Model of how developers use usecases.
8. Hence: a usecase is associated with many scenarios that can be created by it! Usecases control and contain information about actors.
9. Diagram has a large oval contain the system and actors connected by roles!
Iwasaki02
1. Hideya Iwasaki
2. Developing a Lisp-based preprocessor for TEX documents
3. Software - Practice & ExperienceV32n14(25 Nov 2002)pp1345-1363
4. =TOOL LISP TeX Emacs MACROS Markup TEXT
IyerRamesh01
1. Sridhar Iyer & S Ramesh
2. Apportioning: A Technique for Efficient Reachability Analysis of Concurrent Object-Oriented Programs
3. IEEE Trans Software Engineering V27n11(Nov 2001)pp1037-1056
4. =DEMO FORMAL V&V Object-Oriented Concurrency DIGRAPH
5. Trade off analysis safety vs efficiency.
ISO/IEC10027
1. ISO/ITC
2. Information Technology - Information Resource Dictionary Systems(IRDSs) Framework
3. found: IEEE Software magazine V13n3(Mar 1996)p41
4. =STANDARD FRAMEWORK DATA DICTIONARY
ISO/IEC13817-1
1. P G Larsen & B S Hansen & H Brunn & N Plat & H Toetenel & D J Andrews & J Dawes & G Parkin & et al
2. Vienna Development Method -- Specification Language -- Part 1:Base Language
3. ISO Information Technology -- Programming languages, their environments and system software interfaces Number ISO/IEC 13817-1. December 1996.
4. =STANDARD VDM FORMAL SPECIFICATION
5. Thanks to Andrew Martin <apm@ecs.soton.ac.uk> for this citation

Labels	Rules	1	2	3	4
C1	He knows	N	N	Y	Y
C2	He knows C1	N	Y	N	Y
A1	Shun him	X	-	-	-
A2	Teach him	-	X	-	-
A3	Wake him	-	-	X	-
A4	Follow him	-	-	-	X

ISO8613

International Standards Organisation
Information Processing - Text and Office Systems - Office Document Architecture and Interchange Format (ODA ODIF)
[ISO8613] (July 1988)
=STANDARD DOCUMENT FORMAT OFFICE LANGUAGE

ISO8879

International Standards Organisation
Information Processing - Text and Office Systems - Standard Generalized Markup Language(SGML)
[ISO8879] (October 1986)
=STANDARD MARKUP LANGUAGE SGML

ISO9000

International Standards Organisation
Quality Management and Quality-Assurance Standards 1987
Global Engineering Documents //2805 McGaw Ave. //Irvine CA 92714// Phone:USA-(714)261-1455
=STANDARD QUALITY QA

ISO9126

International Standards Organisation
Information Technology/Software Evaluation - Quality Characteristics and Guidelines for the Use 1991
Global Engineering Documents 2805 McGaw Ave. Irvine CA 92714 Phone USA-(714)261-1455
=STANDARDs QUALITY DTR

ITU00

International Telecommunications Union
ITU Recommendation Z.100: Specification and Description Language (SDL)
International Telecommunications Union
=STANDARD SPECIFICATION NONSEQUENTIAL SDL MSC
SDL::="Specification and Description Language"

i-Technology05

i-Technology News Desk
Linus Torvalds Outburst Sparks Fierce Debate: Does Open Source Software Need Specs?
SYS-COM Magazines (Oct. 3, 2005 09:30 AM ) [ 136960.htm ]
=REPORT =HARMFUL SPECIFICATIONS OPEN SOURCE LKML Linux kernel
Original posting to LKML sep29 2005 12:57 PDT
Equated 'reality' with 'code'. "Specs are a basis for _talking_about_ things. But they are _not_ a basis for implementing software."

Jaaksi03

Ari Jaaksi
Assessing Software Projects -- Tools for Business Owners
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp15-18
=EXPERIENCE MANAGEMENT USE-CASES ARCHITECTURE TESTS INCREMENTS ERROR STATISTICS
Testing should be stringent enough to start accumulating open errors, but a project is not half complete until the number of open errors stabilizes and decreases.
Management by walking around: face-to-face interviews are vital.
Documents lie!
No project has been seen that successfully developed a complete support system before big-bang implementation of all use-cases.

JaccheriPiccoLago99

Maria L Jaccheri & Gian P Picco & Patricia Lago
Eliciting software Process Models with the E^3 Language
ACM ToSEM V7n4(May 1999)pp368-410
=DEMO TOOL OBJECT-ORIENTED LANGUAGE for PROCESS Modeling Language(PML)

Jackson75

M A Jackson
Principles of Program Design
Academic Press (NY)1975
=DEMO DDD non-sequential Reality System proto JSP

Jackson76

M A Jackson
Constructive Methods of Program Design
Lect Notes in C Sci vol 44 pp236-262 Springer Verlag Berlin 1976
=DEMO DDD Reality

Jackson78

M A Jackson
Information Systems: Modeling Sequencing and Transformation
pp72-81 in Proc. 3rd Interntl Conf on Software Engineering IEEE1978
=DEMO DAD Reality

Jackson80

M A Jackson
Conventional Programming Language
pp321-342 Human Interaction with Computers Acad Press London UK
=ESSAY non-sequential optimization

Jackson83

M A Jackson
System Development
Prentice-Hall International 1983
=TEXT DAD Reality

Jackson91

Michael A Jackson (101 Hamilton Terrace London NW8 9QX UK)
Description is our Business
pp1-8 in VDM Europe 91 (1991)
=ESSAY Reality
1. "effort devoted to describing a domain pays off by producing at least a partial description of the machine as a by-product" "Let us, sometimes at least, look outward. The point at which formalisms meet informal realities seems to be like the junction of two dissimilar metals: there is a difference of temperature, and an electromotive force is generated. I think this force could be a source of real intelectual energy"

Jackson94

Michael A Jackson
Problems & Methods and Specializations
IEEE Software Magazine V11n6(Nov 1994)pp57-62(advert p93)
See IEEE Software Engineering Journal 1994
=ESSAY PROBLEMS vs SOLUTIONS Engineering JSD Refs to Polya Parnas ADTs
1. "There are no casual builders of cars or bridges", "Many theorists and practitioners, even the most proffessional are naive." p58: "The prerequisites for a more mathematical approach are not yet in place...an automotive engineer [...]a repetoire of standard designs[...]the design space is very narrow." "Understanding the problem and structuring the solution is the primary need"[...]"general computational paradigms[DFDs, objects,...] gives a design space that is too wide for comfort."
  architectural styles, types of problem. focussing on the problem and not the technique. refers to Polya... Problems in context, understand problem::=mapped into set of frames, solutions within and to frames, recombined solutions.
  Need for specialisms within engineering.
  Three frames:
2. JSD, Workpiece->ADT, Controlled environment
3. JSD::=Net{Real_World, Information_outputs, Requests, System, Function}
4. Workpiece::=Net{Workpieces, Operation requests, Operations, machine}
5. Environmane-Effect::=Net{Environment, Connection, Machine, Requirement}
  ->>Engineering disciplines should not focus on a material so much as a network of connected sets of problems and solutions: Personal transport<net>automobiles. MassTransit<net>railway engines.
  See also session at ICSE95

Jackson95a

Michael Jackson(MAJ Consulting Ltd. London) <jackson@acm.org>
Multi-view Implementations(abstract of position paper at the Dagstuhl Workshop on Software Architecture)
ACM SIGSOFT Software Engineering Notes V20n3(Jul 1995)pp70
=ABSTRACT PROBLEMFRAMES

Jackson95b

Michael Jackson(MAJ Consulting Ltd. London) <jackson@acm.org>
Problem Frames
Proc of the 1st Int Workshop on Software architecture CMU-CS-TR-95-151<reports@cs.cmu.edu>
=ADVERT PROBLEMFRAMES
See [Jackson95c]

Jackson95c

Michael Jackson(MAJ Consulting Ltd. London) <jackson@acm.org>
Requirements & Specifications: a Lexicon of Software Practice Principles and Prejudice
Addison-Wesley Redwood City CA 1995 ISBN 0-201-87712-0 CR9607-0459 D.2.1
Excerpt IEEE Software Magazine V12n6(Nov 1995)pp103-104 and [Jackson94]
1. No one method.
2. Context diagrams/problem frames reality driven.
3. Predicates for precision, composition by "and".
4. Designations, definitions, assumptions.
5. Moods: indicative(NAT) vs optative(REQ).
6. Shared phenomena connect domains.
7. Individuals.
8. Danger of vagueness (especially at top level)
9. Describes some risks+limits of: JSP, Z, DFDs, ERDs, top-down, hierarchies, solutions not problems.
10. Ref to Phillip Kraft: "Deskilling".
11. Examples: Dekker, elevators, kohnigsberg, packages, ...
12. Aboricide
13. Importance of critical reading
14. Sent EMail July 23rd 1996

Jackson98

Michael Jackson<jackson@acm.org>
Will There ever be Software Engineering?
IEEE Software Magazine V15n1(Jan/Feb 1998)pp36-39
=ESSAY ECONOMICS ENGINEERING
1. rush to market + dollars for upgrades leave little reason for engineering
2. entrenched interest of practitioners in what they are doing
3. complexity: writing a macro vs no do-it-yourself kit for building suspension bridges
4. variety of products+projects: bridge engineers don't design ships
5. professors of unsolved problems?
6. specialization by product and requirement
7. we will get the software we deserve.

Jackson98a

Michael Jackson<jackson@acm.org>
Defining a Discipline of Description
=ESSAY
IEEE Software Magazine V18n5(Sep/Oct 1998)pp14-18
1. Formal computers in an informal world.
2. It is hard to make sense of a specification of an interface if their is no information about what is inside at least one side of the interface.
3. Designations vs Definitions, may have to bypass some "real" terms because too unclear
4. Must analyse the effects of designation errors: where the formal system can come adrift from reality.
5. Dangers of badly structured descriptions, for example confusing things that are true because of the system with things that are true without the new system.

Jackson99

Michael A Jackson
Specializing in Software Engineering
IEEE Software Magazine V16n6(Nov/Dec 1999)pp120-121+119
=ESSAY ENGINEERING
SPECIALITIES are good
1.more knowledge accumulates, 2 sound theories in standard practice, 3 know what is possible, 4 stronger sense of professional responsibilities
better learning from failures
necessary but not sufficient
one size does not fit all

Jackson01

Michael A Jackson
Problem Frames: Analyzing and structuring software development problems
Addison Wesley 2001 ISBN 0-201-59627-X QA76.76 D47 J32 2001
=ESSAY PROBLEM ANALYSIS REQUIREMENTS REALITIES SYSTEMS METHODS
An in depth attempt at deconfusing a critical part of software development: understanding the problems and planning how to tackle them. Includes detailed references to several methods and some classic examples from the literature,
Five basic problem frames Required Behavior, Commanded Behavior, Information Display, Simple Workpieces, Transformation.
Plus many variants and compositions,
Classification of domains: lexical(symbolic, formal, data like), causal (contolable), biddable( may not follow commands...)
Domains are collections of phenomena: events, entities, values.
Connected by shared phenomena.
Good discussion of the concerns that arise with different types of problems and domains. For example: Allowing for messages that don't make it through mail to the recipient.
Many examples. New Glossary, Careful definitions of what the diagrams mean,
Diagrams show domains, connections, and requirements.
Distinguishes: the machine, the parts of reality, the requirements, the existence of parts of reality that a symbolic descriptions, ...
Some advice for decomposing a problem into subproblems -- for example introducing a designed model of a part of reality and a machine to keep it synchronized, plus other machines to meet other requirements.
Notes problems of synchronizing the different machines that solve different subproblems.
Introduces the idea of a formal/lexical/symbolic domain which specifies requirements to be imposed on another domain by the machine.
Good discussion of problems caused by dome domains not being 100% under control and a suggestion of a special type of problem of auditing compliance.

Jackson03

Michael Jackson
Why writing programs is difficult and will remain so
Information Processing Letters V8n1-2(Oct 2003)pp13-25,CR 0406-0748
=ESSAY REALITY FEATURITIS
Notes

Jackson04

Michael A Jackson
Seeing More of the World
IEEE Software Magazine V21n6(Nov /Dec 2004)pp83-85
=ESSAY REALITY REQUIREMENTS
Requirements are about the problem world which interacts with the machine at the machine-world interface. Outer requirements describe the effects the stakeholders would like to experience in the problem world. Inner Requirements specify how the machine should behave at the machine-world interface to ensure the whole satisfies the outer requirements.
Stakeholders needs are nearly always met by a causal chain problem-wold properties separating inner from outer.
Sequence: outer; problem-world properties; inner.
How to find some faults before they emerge as failures in use. Some questions to ask:
- What if a use-case is abandoned in mid-execution?
- How do use-cases fit together in sequences?
- Consider any object's attribute, what happens if the real world attribute changes?
- Take any actor, what other things might it do/might happen to it (eg die) and what should the machine do about it?
- Start from an output, trace the chain of problem world events, what might happen? What might go wrong? What if things get delayed(crossed letters!)?
[Jackson01]

Jackson06

Michael Jackson
What can we expect from program verification
IEEE Computer Magazine V39n10(Oct 2006)pp65-71
=ESSAY REALITY vs SYSTEM MODELS
Notes on how (and why) to extend formal methods from models of the new system to models of the real world.
Example. Traffic light controler is separated from its requirements(on pedistrians, vehicles, drivers) by other parts: lights, buttons, sensors,road layout.
Three ways to model environment+software: NAT+REQ+IN+OUT, rely and guarantee, reality/ghost variables.
Ideas for splitting problems up into solvable parts and recombining solutions.
Compare [Jackson04]

JacksonD95a

Daniel Jackson(CMU)
Aspect: Detecting Bugs with abstract Dependencies
ACM TOSEM V4n2(Apr 1995)pp109-145
assert dependencies middel ground between type checking and program proving. Good for ommitted statements

JacksonD95b

Daniel Jackson <mailto:dnj@cs.cmu.edu><http://www.cs.cmu.edu/~dnj/>
Structuring Z specifications with Views
ACM TOSEM V4n4(Oct 1995)pp365-389
CR99611-0903
1. interlocking partial specifications(partial state+some ops) with shared ops+operations of whole are combinations of partial ops, conflicts with Z refinement model, needs (guard and if disclaimer then postcondition) synchronized ops plus intersecting invariants on states, one view ND other makes deterministic, good views are simple with complex connections, needs implicit spec and preconditions+ explicit framing and uniform types like Z, needs guards+ indexing+semantic actions not in Z,
  Not whole+part decomposition, no master representation, no need to reconcile multplie viewpoints/perspectives [ZaveJackson94]

JacksonD98

Daniel Jackson
An Intermediate Design Language and its Analysis
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp121-130 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=DEMO NP/Nitpick Language/Tool of RELATIONS
related to more complex Z.
model sets as relations with a singleton range Unit:={unit}. compar [Maddux99]
analysis by building model semantics

JacksonD00

Daniel Jackson
Automating first-Order Relational Logic
[FSE8] pp120-139
=THEORY LOGIC RELATIONS PREDICATE Z OCL =DEMO TOOL 50KLOC Java SAT Alloy Analyzer Nitpick UML COM Mobile IP
Shorter than SMV by 10 times.
Quantifiers make logic easier to use. Analysis s faster than Nitpick as well.
Describes syntax, type rules and semantics of the logic.
In place of composition of relations ( R; S = rel[x,z](some y, x R y S z)), defines navigation ( R . S = rel[x,z](some y, y R z and y S x))
scalar variables are replaced by singleton set variables.
analysis:= normalize and skolemize; boolean formula; conjunctive normal form; SAT solver; map back to relational.
Alloy_Analyzer::= See http://sdg.lcs.mit.edu/alloy
Proved UML meta-model is consistent in less than 20 seconds.
See also [JacksonDSullivan00]

JacksonD02

Daniel Jackson
Alloy: A Lightweight Object Modeling Notation
ACM TOSEM Trans Software Eng & Methodology V11n2(Apr 2002)pp256-290
=IDEA GRAPHIC FORMAL Object-Oriented NOTATION Alloy Z SEMANTICS LOGIC SETS RELATIONS FUNCTIONS

JacksonD06

Daniel Jackson
Dependable software by design
Sci american V294n6(Jun 2006)pp58-65
=SURVEY FORMAL V&V SQA CORRECTNESS MODEL CHECKING TOOLS Alloy .. Zing

JacksonD06a

Daniel Jackson
Software Abstractions: Logic, Language, and Analysis
The MIT Press Cambridge MA 2006 ISBN 0262101149 CR 0802-0116 0806-0536
=TEXT Alloy LIGHT FORMAL MODEL CHECKING METHODS TOOLS
A neat way of finding bugs in specifications and requirements.
Small_scope_hypothesis::=Most bugs have small counterexamples.
Notes the difficulty of creating consistent formal models that have the desired properties.
Alloy::language=a formal first order relational logic expressed in ASCII with tools in Java.
Alloy_examples::= See http://softwareabstractions.org.
Alloy_analyzer::= See http://alloy.mit.edu.

JacksonD09

Daniel Jackson
A Direct Path to Dependable Software
Commun ACM V52n4(Apr 2009)pp78-88 [ 1498765.1498787 ] [ publications.html ]
=ESSAY RISKS COSTS not PROCESSES CRITICAL PROPERTIES CLAIMS QUALITIES REQUIREMENTS
Based on a study done for NRC lead to Dependability Cases.
Lots of examples of RISKS and how they occurred and how the effect reasoning about the dependability od a system.
A dependability case provides evidence, in the form of claims, that certain critical properties will hold.
The analysis of the critical properties and the claims that support them starts on day one of a project, and guides architectural decisions. Well chosen architecture -- modular, decoupled, simple -- makes it cheaper to establish a dependability case.
Dependability cases should develop "hand-in-hand" with the product. The developers chose techniques and technology to support the claims.
Critical properties should be close to the user/client/real world.
All claims depend on assumptions about the client's world: an air traffic control system can not stop a pilot deliberately crashing into another aeroplane.
Claims connect the developing system, via assumptions, to the critical properties.
A dependability case must be auditable, complete, and sound.
A rigorous process can help establish a dependability case -- but need not be burdensome.
A risk-averse and meticulous culture will help.
Need robust platforms and tools -- language design.
The correctness of code is not the weakest link in the chain -- only 3% of the time...
Testing and analysis contribute as well.
Credible tools -- example of a broken proof: binary search when bounds > largest integer!
See also [JacksonD06] [Jackson01] [Jackson04] (Outer vs inner requirements)

JacksonDChapin00

Daniel Jackson & John Chapin
Redesigning Air Traffic Control: An Exercise in Software Design
IEEE Software Magazine V17n3(May/Jun 2000)pp63-70
=CASESTUDY DESIGN IMPROVEMENT CTAS REVERSE ENGINEERING Motif
CTAS := ground bases air traffic control system
Basic techniques taught in university courses reduced 80k C++ Communication Manager by 80% to extendable Java
data abstraction replaced functional decomposition and shared record structures.
queues to hide blocking IO
general message handler with table driven special cases replace hard-coded message handling
common interfaces
special language and compiler for message types( .h files)
example of Hoare's maxim.
Tools help.
Coding standards that fit tools help.
System-level model of assumptions and behavior was needed: for example can not id aircraft by call sign alone!
Satyanarayanan: bloat and bit-rot is the price of cost cutting up front.

JacksonDDamon96

Daniel Jackson (mailto:daniel.jackson@cs.cmu.edu) & Craig A Damon(mailto: craig.damon@cs.cnu.edu)
Elements of Style: Analyzing a Software Design Feature with a Counterexample Detector
Proc 1996 Int Symposium on Software Testing & Analysis(ISSTA) & ACM SIGSOFT SENotes V21n3(May 1996)pp239-249 & IEEE Trans Soft Eng VSE-22n7(Jul 1996)pp484-495
Jackson's home page [ http://www.cs.cmu.edu/~dnj/ ]

JacksonDJacksonM95

Daniel Jackson & Michael Jackson
Problem Decomposition for Reuse
Tech Rep CMU-CS-TR-95-108
School of Computer Science Carnegie Mellon University Pittsburgh PZ Jan
to appear in Software Engineering Journal

JacksonDShlyakhterSridharan01

Daniel Jackson & Ilya Shlyakhter & Manu Sridharan
A Micromodularity Mechanism
ACM SIGSOFT proc ESEC-8 FSE-9 Software Engineering Notes V26n5(Sep 2001)pp62-73
=IDEA MODULAR SPECIFICATIONS RELATIONS FORMAL NOTATION LOGIC EXTENSION TOOL? cf Z Alloy
On the WWW [ publications ]
|-A structure is a set of atoms and its fields are global relations that map atoms to other sets of atoms.
|-Structure extensions are just subsets.
sig name [parameters] extends parent[parameters]{ field: associate ...}{properties}: field is a relation between name and associate and name is a subset of parent.
fact { property }: makes assumptions, states constraints, can retrofit fields
assert{properties}: theorems -- properties that are intended to hold, and so need checking.
fun name(para:type...){property}: defines properties that may or may not be true. used to describe methods, abstraction.
Simpler and more focused than Z, VDM, or MATHS

JacksonDSullivan00

Daniel Jackson & Kevin Sullivan
COM Revisited: Toll-Assisted Modeling of an Architectural Framework
[FSE8] pp149-158
=CASESTUDY Alloy MODEL Microsoft COM SPECIFICATION
Uses Alloy Analyzer [JacksonD00]
Analysis contributes to modeling by validating simplifications and spotting typographical errors rapidly and interactively. Rapid analysis encourages more daring experimental models.
Astonished at how hard it was to preserve precise meanings when restructuring and at how useful the tool was
Z notation may have contributed to typographical errors in previous models.
paper+model is at [ publications ]

JacksonDWaingold99

Daniel Jackson & Allicon Waingold
Lightweght Extraction of Object Models from Bytecode
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp194-202
=DEMO Womble reverse engineers object-oriented model using Alloy from JAVA Bytecode
Not perfect but still useful to programmers, does not find n-ary relations.

JacksonDWaingold01

Daniel Jackson & Allison Waingold
Lightweight extraction of Object Models from Bytecode
IEEE Trans Software Engineering V27n2(Feb 2001)pp156-169 also in ICSE'99 [JacksonDWaingold99]
=DEMO TOOL TECHNICAL Java bytecode MODEL Alloy Womble Superwomble Rose
* := zero or more, ? := zero or one, ! := exactly one. ---|-> := static.
Womble::= See http://sdg.lcs.edu/womble.

JacksonDWing96

Daniel Jackson & Jeanette Wing
Lightweight Formal Methods
IEEE Computer Magazine V29N4(Apr 1996)pp21-22
more like a surgical lazer than a light bulb. Partial languages: models and analysis

JacksonJ05

Joab Jackson
Open-source bug hunt results posted
GCN V1n1(Mar 6) [ 40053-1.html ]
=REPORT OPEN SOURCE QUALITY Coverity Homelan Security
Only 1 bug per 2000 Lins of Code on avergae.
Different open source products have different bug rates.
Size doesn't matter -- usage does: Apache less than 1 in 4000 LoC.

JacksonK89

Ken Jackson
Providing for the Missing Steps
UNIX Review v6n11(Nov 1988) pp55-63
SAD DFD DDD DAD Mascot

JacksonKLavi93

Ken Jackson & Jonah Z Lavi
"CBSE Task Force seeks standard conceptual models for new discipline"
IEEE Computer magazine V26n5(May 1993)pp98-99
=CFP
CBSE::="Computer-Based Systems Engineering"

JacksonTwaddle97

Michael Jackson & Graham Twaddle
Business Process Implementation: Building Workflow Systems,
Addison Wesley ACM Press 199? ISBN 0-201-17768-4 3rd hd58.87.j32 1997
=EXPERIENCE SPECIFICATION MODEL OFFICE WORKFLOW PEOPLE DATA PROCESS FLEXIBLE vs BUSINESS RULES TABULAR GRAPHIC METADATA
workflow_problem_frame::= following,
Net
1. |- (minimal_workflow_frame): The machine supports an office that interacts with an outside world.
2. |-The prime business need is to keep track of long term commitments, contracts, and obligations.
3. |-There are rigid business rules and flexible activities.
4. |-activities are multitasked error correcting that proceed at a human pace.
5. |-not safety critical.
(End of Net)
theoretical_method:= data; process; tasks; workflow.
In practice incremental and iterative delivery is feasible.
data:=simple ERD, like SSADM.
task_types:=initiated performed content [task_details].
initiated:=X | T | P | I. X=eXternal, T=Time, P=follows Preceeding, I=Internally.
performed= A | M, A=Automatically, M=not A, Manually,
content:= E | K| U | D | O, E=dataEntry, K=checK, U=Update, D=Decision, O=Output.
Tasks involve entities.
LC:=" life cycle".
An entity life cycle is a defined sequence of stages but an entity may not progress thru the stages in such a simple way. Office work may backtrack, hang up, fail, or multitask parts of stages at one time. Stages may not be omitted. Backtracking (a setback) means handling side-effects: beneficent, neutral, and intolerable. cf [JSP].
In a stage contains a task that fails then the current life cycle fails and initiates a different one instead.
Stages determine states: State = ("In" | "Failed" | "Awaiting" | "Halted" ) stage.
Within a Stage many tasks can execute in parallel. some can spawn (one|many (inclusive | exclusive)) subtasks (sometimes). One subtask can be spawned by many tasks, and a subtasks can restart their parent tasks (in a loop).
Task states = null; start; (n/a | run | failed | passed). passed states do not spawn subtasks, run states must start their subtasks. Task states determine life-cycle states.
There are rules for assigning tasks to stages.
One life cycle can depend on another one. Changing stage depends on one(or all) other linked entities of a given type is|are past a certain stage. Tasks can start and halt other life cycles.
Entities are placed in classes. Classes form a heterarchy -- multiple inheritance. Also classification entities -- classes of objects each defining a class of object!
Entities play roles in entity life cycles. roles require only a subset of the attributes, Also several types of entity can play the part in a single role.
Datasets are structured navigation paths between entity types. from A access one B and many Cs. They are chosen to fit tasks.
Programs support tasks - within task context and using task content. actions include SET_RESULT, START_LC, SUSPEND_LC, RESUME_LC, CANCEL_LC, SETBACK_LC, WAIT..., SIMPLE_CHECK, COMPLEX_CHECK, SIMPLE_SET, APPLICABLE_WHEN. Some tasks must not be repeated, others may be repeated when backtracking.
Decision Tables!
Tasks and life cycle work mainly define wrong sequences. Work flows help get good things done. Work flows are about scheduling, options, menus, and efficiency. Work flows are based on a relational data base:
task_details:=
Net{
1. Each task is in a stage of a life cycle of an entity.
2. Each task has a task_type that has a program, data set, and a set of skills.
3. Tasks are related to users who can/should do them by Skills and by stages and departments for example.
  }.
Detailed reporting and so tuning of the workflows.
Life cycle definitions and the office workflow are also held in the data base. "Process representations become data". Process data is PLANs and FEATUREs.
The only purpose of documentation is understanding.... but if documentation is in a data base is also useful to the software.
dick:the office workflow frame fits agile software development process.

JacksonVaziri00

Daniel Jackson & Mandana Vaziri
Finding Bugs with a Constraint Solver
Proc ISSTA 00 & ACM SIGSOFT Software Engineering Notes V25n5(Sep 2000)pp14-25
=DEMO LOGIC Alloy disproving
find scope limited models of (Pre and Code and nou Post )
Programs with pointers often have errors exposed in seconds. Worst 6 minutes.

JacksonWDawsonWilson03

Thomas W Jackson & Ray Dawson & Darren Wilson
Understanding Email interaction increase organizational productivity
Commun ACM V46n8(Aug 2003)pp80-84
=EXPERIENCE EMAIL INTERRUPTION
"You've got mail".... response in 6 seconds. 64sec interruption.
Better: if only look at EMail every 45 minutes, reduce reply-to-all and mail-to-all, display only from+subject+3lines, train users to use rules.

Jacky95

Jonathon Jacky
Specifying a Safety-Critical Control System in Z
IEEE Trans on Software Eng VSE-21n2(Feb 1995)pp99-106 CR9605-0354 D.2.1
1. Safe_Op::= Dangerous_Op and Pre_Safe_Condition_for_Op.
2. Pre_Safe_Condition_for_Op::= for some State'( Dangerous_Op & Invariant(Sensors)).
3. For S, Invariant(S)::=(S'=S). Notice that Invariant(Sensors) do not appear directly in the Ops, only inconjunction with them, and then hidden in a quantifier.
  May need to add extra interlocks on transitions that are not in raw requirements.
  Did not need an OO version of Z. Defined classes of components all sharing a common schmer and separted by their identifiying names.
  Useful Idioms: promotion, multiple comp ops,

Jacky99

Jonathon Jacky
Lessons from the Formal Development of a radiation therapy machine control program
In [HincheyBowen99] pp185-205
=EXPERIENCE Z tools TABULAR CSR SMV TMC radiation therapy machine
formal methods can help create novel designs and original code not just post hoc.
A detailed informal specification checked by users and designers must come first.
Creating formal description requires design judgment.
All documentation require much revision: content, correctness, clarity, organization.
It is harder to do a useful formal description than a subset of the whole. educated developers can easily do small specifications.
Good implementation is not easy.
Inspection and paper-and-pencil can detect most but not all errors in large Z... if modularized.
Minor errors don't make a document useless.

Jacob91

Jeremy Jacob
A Uniform Presentation of Confidentiality Properties
IEEE SE-17n11(Nov 1991)pp1186-1194
quantifier notation and information flow

Jacobs09

Adam Jacobs
The pathologies of big data
Commun ACM V52n8(Aug 2009)pp36-44 [ 1536616.1536632 ]
=EXAMPLES DENORMALIZATION DATA OPTIMIZATION QUALITIES PERFORMANCE RDBMS
"It is easier to get data into a large database than get it out."
"To achieve acceptable performance[...] one must be willling to consider abandoning the purely relational database model."
"As dataset sizes grow, it becomes increasiingly important to exploit the efficiency of sequential acces[...]"
Problems with arbitrary limits.
Discusses distributed data bases.
Tradeoffs between fast access and duplicated data.

JacobsenJadud05

Christian L Jacobsen & Mathew C Jadud
Towards concrete concurrency: Occam-π on the LEGO Mindstorms
ACM SIGCSE Tech Symp Proc (Feb 2005)pp431-435
=DEMO CONCURRENCY EDUCATION LANGUAGE occam-π ROBOT LEGO Transterpreter

Jacobsen00

Allan Baktoft Jakobsen
Software Processes: Live and Let Die
IEEE Software Magazine V17n3(May/Jun 2000)pp71-75
=EXPERIENCE RE-ENGINEER 50000 LoC to CLEANROOM PEOPLE Adizes
people should choose there own process to fit the types of people on the team
productive process was closer to XP refactoring than a pure top-down cleanroom.
product was not defect free

Jacobson93

Ivar Jacobson
Is Object Technology Software's Industrial Platform

Special Theme "Making OO Work" IEEE Software V10n1(Jan 1993)pp24-30

p27:"A use case is simply a way to use a system" Usecases->interaction diagrams...

p29:"Describing Objects with text alone is ineffective. We make it difficult for ourselves because we are obliged to use text." p29

Jacobsen03

Ivar Jacobsen
The case for aspects
Software Development Magazine V11n10(Oct 2003)pp32-37
=EXPERIENCE 1979 USECASE EXTENSION COMPONENTS ASPECTS
Requirements often cut across components.
Example: One use case could not ignore another one.
Extension used to inject steps into one use case to support another one.
Use patching(1980s) or AOP(2000s) to implement use case extension!

Jacobsonetal92

Ivar Jacobson & Magnus Christenson & Patric Jonsson & Gunnar Overgaard
Object-oriented Software Engineering
ACM Press NY NY 1992 ISBN 0-201-54435-0 CR9306-0376(H.2.1 K.6.2)
=EXPERIENCE METHOD USE CASES SCENARIOS RESPONSIBILITY

JacobsonJacobson96

Ivar Jacobsen & Sten Jacobson
Use-Case Engineering: Unlocking the Power
Object Magazine V6n9(Oct 1996)pp96-95
objet-oriented. (analyse; design; test) use-cases
system border set by allocating responsibilities to actors or use-cases

JacobsonBoochRumbaugh98

Ivar Jacobson & Grady Booch & James Rumbaugh
The Unified Software Development Process
Addison Wesley Longman Reading MA 1999 ISBN 0-201-57169-2
=DEFINITION METHOD RUP (Rational Unified Process) USECASE OBJECT-ORIENTED FSM UML
1. Grow system through iterations driven by adding usecases.
2. Architecture (metaphor?) controls cost of changes.
3. phases:=Inception; elaboration; construction; transition.
4. phase:= iterate(requirements; analysis; design; implement; test).
5. The phases differ in the ammount of effort spent in the different parts of each iteration.
6. See also [Meyer96c] [JacobsonBoochRumbaugh99]

JacobsonBoochRumbaugh99

Ivar Jacobson & Grady Booch & James Rumbaugh
The Unified Process
IEEE Software Magazine V16n3(May/Jun 1999)pp96-104
=ADVERT METHOD USECASE OBJECT-ORIENTED for the book of the same name

Jacquet93

Jean-Marie Jacquet
Constructing Logic Programs
John Wiley & Sons NY NY 1993
ISBN 0-471-93789-4 CR9601-0007(D.1.6)
skeletons + links to OO

JagerSchleicherWestfechtel99

Dirk Jager & Awsger Schleicher & Bernhard Westfechtel
Using UML for Software Process Modeling
ESEC/FSE'99 SIGFOFT SE Notes V24n6(Nov 1999)pp91-107
=IDEA PROCESS MODEL UML MADAM PROGRES DYNAMITE

JahanianMok94

Farnam Jahanian & Aloysius K Mok
Modechart: A Specification Language for Real-Time Systems
IEEE Trans SE VSE-20n12(Dec 1994)pp933-947

Jahnichen92

Generating two-dimensional user interface out of graphical specifications
reported in TichyHabermannPrechelt93 p43

Jainetal96

Anil K Jain & Jianchang Mao & K M Mohiuddin
Artifical Neural Networks: A Tutorial
IEEE Computer Magazine V29N3(Mar 1996)pp31-54

Jaksic04

Mirjana Jaksic
Mapping of bibliographical standards into XML
Software: Practice and Experience V34n11(Sep 2004)pp1051-1064
=HOWTO XML BIBLIOGRAPHY MARC UNIMARC Java

JalicsHeines83

?? Jalics & ?? Heines
Transporting a Portable Operating System: UNIX to an IBM Minicomputer
Commun ACM V26 n12 (Dec 1983) pp1066-1072
=case-study Technical

JaloteSaxena02

Pankaj Jalote & Ashish Saxena
Optimum control limits for Employing Statistical Process Control in Software Process
IEEE Trans Software Engineering V28n12(Dec 2003)pp1126-1144
=MATHEMATICS STATISTICS METRIC SQA COSTs OPTIMAL
tool::= See http://www.cse.iitk.ac.in/research/software/.

JaloteMurphySharma08

Pankaj Jalote & Brendan Murphy & Vibhu Saujanya Sharma
Post-release reliability Growth in Software products
ACM TOSEM Trans Software Eng & Methodology V17n4(Apr 2008)#17pp1-20 [ 13487689.13487690 ] CR 1006-0592
=EXPERIENCE RELIABILITY USAGE
Users learn to work round the bugs.
Proposes and tests model based on
Failure_rate:=transient_failure_rate + steady_state_failure_rate.
transient_failure_rate:= λ * α**(-time_in_use).
Model fitting handles the time when the product is sold -- monthly sales.

Janicki97

Ryszard Janicki<janicki@mcmaster.ca>
On a Formal Semantics of Tabular Expressions
[CRL] Report 355 Telecommunications Research Institute of Ontario(TRIO) McMaster University Hamilton Ontario Canada 1997
earlier version [CRL] Report 264

Janik01

David Janik
Module Design Guidelines for Real-Time System
Dr. Dobbs #321(Feb 2001)pp108+110-113+117
=EXAMPLE MODULES C
Protected data, external functions, internal functions
single file or multifile.
passive(no need for realtime, use semaphor) vs active modules(need RTOS). active = repetitive tasks vs IO queues.

JanickiSekerinski01

Ryszard Janicki & Emil Sekerinski
Foundations of the Trace Assertion Method of Module Interface Specification
IEEE Trans Software Engineering V27n7(Jul 2001)pp577-598
=THEORY MODULE SPECIFICATION AUTOMATA TRACES RELATIONS TABULAR REFINEMENT NONDETERMINISM EXCEPTIONS
compares Algebraic & Mealy.
uses step traces. Input(e), output:e.

Jankowski94

David J Jankowski
The Feasibility of CASE Structured Analysis Methodology Support
ACM SIGSOFT Software Eng Notes V19n2(Apr 1994)pp72-82

JansenEtal08

Slinger Jansen & Sjaak Brinkkemper & Ivo Hunink & Cetin Demir
Pragmatic and opportunistic Reuse in Innovative start-up companies
IEEE Software Magazine V25n6(Nov/Dec 2008)pp42-49
=EXAMPLES 2 STARTUPs OSSD POSTMODERN ASSEMBLY MASHUP
Page 43 has a useful table and figures showing 8 different ways components can be connected.
how_to_mashup::=following,
1. Send object through filter.
2. Use method calls.
3. Write glue code.
4. Components share a data object or data base
5. Use a component bus like CORBA
6. Use a plugin architecture as in Java and Eclipse.
7. Use network and services -- MySQL, SOAP, ...
8. Enterpise service bus passes calls to best component to provide service.

JansenHermansKatoen03

David N Jansen & Holger Hermans & Joost-Pieter Katoen
A QoS-Oriented Extension of UML Statecharts
LNCS 2863 <<UML>> 2003 -- The Unified Modeling Language Oct 2003, pp76-91
=EXAMPLE PROBABILISTIC UML STATECHART MODEL QUALITY-of-service TIMING stochastic FSM StoCharts
StoCharts add probabilities and randomized delays to transitions.

JanzenSaiedian05

David Janzen & Hossein Saiedian
Test-Driven Development: Concepts,Taxonomy, and future directions.
IEEE Computer Magazine V38n9(Sep 2005)pp43-50
=SURVEY TEST-DRIVEN PROCESS TDD XP SCRUM AGILE EDUCATION
Well written survey of history and literature on test-driven development.
Predicts that TDD will not go away.
Refs [Beck01] [Reifer02] [ErdogmasMorisioTorchiano05]

JanzenSaidian08

David S Janzen & Hossein Saidian
Does Test-Driven Development Really Improve Software Design Quality?
IEEE Software Magazine V25n2(Mar/Apr 2008)pp77-84
=EXPERIMENT TEST TDD CODE TECHNICAL QUALITITIES
Evidence that TDD is associated with simpler and better tested modules.
Two myths: TDD means (1) write all tests first or (2) automate all the testing. [JanzenSaiedian05]
TDD::process=High-level design; TDD_design_and_code; test.
TDD_design_and_code::= unit_test; code; refactor; O(TDD_design_and_code).

JaouaMilietal91

A Jaoua & A Mili & N Boudriga & J L Durieux
Regularity of Relations: A Measure of Uniformity
Theoretical Comp Sci. V79n2(Feb 1991)pp323-339
CR904-0236
See Milietal89
1. |-for all R:@(X,Y), R==>R;/R;R.
2. Regular::={R || R;/R;R==> R}.
3. (-2, -1)|-Regular = {R || R;/R;R=R}.
4. kernel(R)::= {}<>s'.R==>s.R,
5. (kernel)|-kernel(R) in reflexive & transitive.
6. nucleus(R)::=R;/R,
7. (-1)|-nucleus(R) in reflexive & symmetric. (?????)
8. (Regular)|-If equivalence(R)then R in Regular.
9. (Regular)|-post(R)>=={u.R||u:pre(R)} iff Regular.
10. (Regular, nucleus, kernal)|-If Regular R then nucleus(R) = kernel(R) in reflexive & symmetric & transitive.
11. |-form(x'=f(x,...)) is regular. ...
12. |-For all Regular R, Functions f, f;R in Regular.
13. Rational::={R||for some X, f,g :dom(R)->X(R=f;/g)}.
14. |-Regular iff Rational. For all R, some f,g, R=/f;g.

Jarc93

Duane J Jarc<jarc@umuc.umd.edu>
??
ACM SIGCSE Bulletin V26n2(pp2-4+8)
=IDEA ADTs EDUCATION
1. Lists Trees Graphs
2. Sequential Linked
3. Bits and Addresses
  Notes that Trees and lists can be treated as special graphs.(!)
  Can not place sets of Hash Tables in hierarchy.

Jarke92

Mathias Jarke
Strategies for Integrating CASE Environments
IEEE Software V9n2(Mar 1992)pp54-61
=EXPERIENCE CASE REALITY+SYSTEM+TECHNICAL maintaining world model
conceptual models
database programs.

Jarke99

Marthe Jarke
Scenarios for Modeling
Commun ACM V42n1(Jan 1999)pp47-48
=HISTORY PURPOSE leads to scenario to model
Life-cycle of arien toos

JarkeKurki-Suonio99

Mathias Jarke & Reino Kurki-Suonio
Guest Editorial: Introduction to the Special Issue [on Scenario Management]
IEEE Trans SE V24n12(Dec 1998)pp1033-1035
=SURVEY SCENARIO life cycle
Also see [KaindlCarroll99]

JarviPowellLumsdaine03

Jaakko Jarvi & Gary Powell & Andrew Lumsdaine
The Lambda Library: unnamed functions in C++
Software - Practice & Experience V33n3(Mar 2003)pp259-291
=ADVERT C++ STL LIBRARY LAMBDA FUNCTIONAL LL

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 [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.

Jarzabek98

Stan Jarzabek
Design of Flexible Static Program Analyzers with PQL
IEEE Trans SE V24n3(Mar 1998)pp197-215
extended OMT OOA/OOD models of COBOL85 programs entered into knowledge base
PQL::="Program Query Language".

JazayeriSchauer97

Mehdi Jazayeri & Helmut Schauer (Eds)
Procedings 6th European Software Engineering Conference and 5th ACM SIGSOFT symposium on the Foundations of Software Engineering(ESEC/FSE'97) September 1997
ACM SIGSOFT Software Eng Notes V22n6(Nov 1997) Special Edition: [Rushby97]
[Boehmetal97]
[Maibaum97]
[LandSauerJeffery97]
[HiemdahlWhalen97]
[KarlssonTaxen97]
[PerryVotta97]

JeanStrohmeier90

Catherine Jean & Alfred Strohmeier
An experience in teaching OOD for Ada software
ACM SIGSOFT SEN V15n56(Oct 1990)pp44-49 (problems with "informal strategy" on page 49)

JeffordsHeitmeyer98

Ralph Jeffords & Constance Heitmeyer
Automatic Ceneration of State Invariants from Requirements Specifications
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp56-69 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=THEORY of TOOL SCR prototype TOOL tested on A-7 SRS
boolean encoding of states

JeffordsHeitmeyer03

Ralph D Jeffords & Constance L Heitmeyer A Strategy for efficiently verifying requirement specifications using composition and invariants
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp28-37
=DEMO TOOLS THEORY SCR LTS SMV SPIN Salsa Assume/guarantee
BCP::="Basic Compositional Proof".
MCP::="Modified Compositional Proof".

Jeffrey67

Richard C Jeffrey
Formal Logic: Its Scope and Limits
McGraw-Hill NY NY 1967
=TEXT FORMAL LOGIC semantic Tableaus TREES
An easy to use way of proving things.
Compare with the later [Hodges77] and [Jeffrey91]

Jeffrey91

Richard C Jeffrey (Princeton U)
Formal Logic: Its Scope and Limits
McGraw-Hill Higher Education NY NY 1991 ISBN 0-07-032357-7
=TEXT FORMAL LOGIC semantic Tableaus TREES
An easy to use way of proving things.
Improved edition of [Jeffrey67].
Compare with the earlier [Hodges77]

JeffreyVotta99

D R Jeffery & L G Votta (Guest Editors)
IEEE Trans Softw Eng V25n4(Jul/Aug 1999)pp435-583
=SURVEY EMPIRICAL techniques for studying software engineering

Jeffries00

Ron Jeffries (ed Larry Constantine)
Card Magic for Managers
Software Development Magazine V8n12(Dec 2000)pp61-62+64
=ADVERT CARDs for THINKING XP PLANNING
Cards force you to be concise and modular and allow rapid reorganization.
Good for planning.

JeffriesMelnik07

Ron Jeffries & Grigori Melnik (eds)
TDD: The Art of Fearless Programming
IEEE Software Magazine V24n3(May/Jun 2007)pp24-83
=SURVEY =ISSUE TEST DRIVEN DEVELOPMENT
Pages 24-29 defines TDD, surveys the research literature(TDD does work), introduces the following papers.
In TDD the system is in one of three states: Fail (Red), Pass(Green), and Refactor in the following cycle:
1. Design a test for one new capability.
2. state=Fail.
3. Implement just enough code to make all tests succeed.
4. state=Pass.
5. Improve design using tests to verify continued sucess.
6. state=Refactor.

Papers in special section
Table

Author	Title	Note/link
Robert C Martin	Professionalism and test-driven development
Scott W Ambler	Test-driven Development of Relational Databases	refactoring may temporally lead to duplicated fields and special synchronisation methods/triggers. [Ambler03]
Thomas Dohmke & Henrik Gollee	test_driven Devlopment of a PID Controller
Alex Ruiz & Yvonnee Wang Price	Test-Driven GUI development with testNG and Abbot
Jennitta Andrea	Envisioning the NExt Generation of Functional Testing tools
Johnson & Maximillien & Ho & Williams	Incorporating Performance testing in a Test-Driven Development
Bas Vodde & Lasse Koskela	Learning Test-Driven Development by Counting Lines	See [VoddeKoskela07]

(Close Table)

Jenkins06

Stephen B Jenkins
Musings of an "old-school" programmer
Commun ACM V49n5(May 2006)pp124-126 + letter V49n6(Jun 2006)pp11-12
=ESSAY TECHNICAL MINIMALISM agile multi-language TOOLS Vim/Emacs bash no debugger UML IDE
Projects that are small enough to be tackled by an individual do not need complex tools or extensive documentation -- just a vision and iterating towards that vision.
Like chopping a bike or crafting an essay,

Jenkins06b

Stephen Jenkins
Concerning interuptions
IEEE Computer Magazine V39n11(Nov 2006)pp116+114-115
=EXPERIENCE TECHNICAL FLOW vs INTERUPTIONS

Jerome00

Carlos Jerome
Building Better Business System with Scenario
Software Development Magazine V8n6(Jun 2000)pp56-60
=DEMO SCENARIOS USECASES PEOPLE
scenarios preferred by developers because they are more specific than usecases and explore situations.

JessupEckel99

Jennifer Jessup & Bruse Eckel
Patterns of Efficiency
Software Development Magazine V7n4(Apr 1999)pp77-79
=DEMO Singleton in JAVA

JetleyIyerJones06

Raoul Jetley & S Purushothaman Iyer & Paul L Jones
A Formal Methods Approach to Medical Device Review
IEEE Computer Magazine V39n4(Apr 2006)pp61-67
=CASE STUDY FDA MEDICAL MODEL CHECKING TESTING FORENSICS LTS FSM CDRH SLICING ABSTRACTION

JeyarajSauter07

Anand Jeyaraj & Vicki L Sauter
An Empirical Investigation of the Effectiveness of Systems Modeling and Verification Tools
Commun ACM V50n6(Jun 2007)pp63-67 + Correspondence Commun ACM V50n8(Aug 2007)p13-14
=EXPERIMENT DFD vs UCD USE CASE DATA FLOW GRAPHICS REQUIREMENTS MODEL
Compared the ability of people (novice and experienced) to extract a correct and complete narrative from either a DFD or a use case diagram.
DFDs better at exposing information about the system.
Before asking non-experts (clients, users, stake holders) to review requirements diagrams provide training.
Replicates [FreemanL03]

Jezequel99

Jean-Marc J'ez'equel
Reifying Variants in Configuration Management
ACM TOSEM V8n3(Jul 1999)pp284-295
=DEMO SCM OBJECT-ORIENTED TOOL

Ji00

Katrina Ji
ADAP: A Component-Based Model Using Design Patterns With Applications In E-Commerce
CSUSB MS Thesis (May 2000)
=THESIS DEMO METHOD TECHNICAL DESIGN PATTERNS Java MOBILE Aglet

JilaniDesharnaisMili01

Lamia Labed Jilani & Jules Desharnais & Ali Mili
Defining and Applying Measures of distance Between Specifications
IEEE Trans Software Engineering V27n8(Aug 2001)pp673-703
=THEORY METRICS RELATIONAL SPECIFICATIONS COTS COCOMO
Refinement Lattice; Refinement difference; Symmetric refinement Difference;
Possible applications: predicting integration costs, adaption costs

Jimenez-PerezBatory97

Guillermo Jimenez-Prez & Don Batory
Memory Simulators and Software Generators
[Harandi97] pp136-145
GenVoca P2 ARCHITECTURE PERFORMANCE generates faster code!

Jingetal95

Ying Jing & He Zhijun & Wu Zhaohui & Li Jiangyun & Fan Weicheng & Xu Zhaohui
A Methodology for High-level Software specification Construction(MHSC)
ACM SIGSOFT Software Engineering Notes V20n2(Apr 1995)pp48-54

JirotkaGoguen94

M.Jirotka & J.Goguen (eds)
Requirements Engineering: social and technical issues
Academic Press London UK 1994
=BOOK REQUIREMENTS PEOPLE TECHNICAL SYSTEM

JirotkaLuff06

Marina Jirotka & Paul Luff
Supporting Requirements with Video-Based Analysis
IEEE Software Magazine V23n3(May/Jun 2006)pp42-44
=EXPERIENCE SYSTEM VIDEO REQUIREMENTS ELICITATION ANALYSIS ethnography dealing rooms
Video recording exposed the (tacit) complexity and value of the current system.
Show video excerpts to designers!
Page 44. Sidebar gives guidelines for using audiovisual equipment and analyzing video recording.
Video recording raises ethical concerns: get consent, destroy sensitive segments, keep recording confidential, destroy when done.
Compare [JirotkaGoguen94]

Joannou07

Paul Joannou
Enterprise, Systems, and Software Engineering -- the need for Integration
IEEE Computer Magazine V40n5(May 2007)pp103-105
=IDEA ENTERPRISE ENGINEERING SYSTEMS SOFTWARE
Need to match software to system and systemto enterprise,

JohansenEtal02

Dag Johansen & Kere J. Lauvset & Robbert van Renesse & Fred B. Schneider & Nils P. Sudmann & Kjetil Jacobsen
A TACOMA retrospective
Software - Practice & ExperienceV32n6(May 2002)pp605-619
=EXPERIENCE MOBILE CODE NET TACOMA

Johnson89

Dan Johnson
Graphical Program Notations: On Tripp's Survey - the Past & The Future
ACM SIGSOFT Software Engineering Notes v14n5(Jul 1989) p78-79
box-charts graphic

Johnson94

Ralph E Johnson<johnson@cs.uiuc.edu>
Why a Conference on Pattern Languages?
ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)pp50-52

JohnsonB95

Bruce Johnson(johnson@xavier.xu.edu)
More Lessons From Civil Engineering(letter)
IEEE Software Magazine(Nov 1995)p6
[WilliamsD95]
Civil Engineers have learnt to not specify how a highway is constructed. Instead they specify the characteristics of a good highway and contractors determine the best ways to produce the desired outcome. "Designers must learn to think more deeply about the characteristics of a good system".

JohnsonRA00

Richard A Johnson
The ups and downs of Object-Oriented Systems Development
Commun ACM V43n10(Oct 2000)pp69-73
=POLL150 OOSD people
Compared trained and experienced with inexeperienced and untrained .
Experience beleive in advantages more but not stability, reuse, and user communication. Also reject disadvantages.
(dick)|-ignores cognitive dissonance.

JohnsonBrodman96

Donna I Johnson & Judith G Brodman
Realities and Rewards of Software Process Improvement
IEEE Software Magazine V13n6(Nov 1996)pp99-101
costly but profitable

JohnsonDisney98

Phillip M Johnson & Anne M Disney
The Personal Software Process: A Cautionary Case Study
IEEE Software Magazine V15n6(Nov/Dec 1998)pp85-88
=EXPERIENCE PSP IMPROVEMENT TOOL
It can teach Software engineering but many erors made by students recording PSP data on forms. AUtomate! [ http://www.cs.etsu.edu/softeng/psp/ ]

JohnsonS??

Steven D Johnson
Behavior Tables
=ADVERT TABULAR

JohnsonBrodman00

Donna L Johnson & Judith G Brodman
Applying CMM Project Planning Practices to Diverse Environments
IEEE Software Magazine V17n3(Jul/Aug 2000)pp40-47
=EXPERIENCE CMM MAINTENANCE
challenges: product_line, maintsnance, Service, database, cuztomization, small, schedule_driven.
Define a project as enough tasks to make CMM planning worthwhile. Smaller tasks only need a supplement.
" CMM practices state that individuals from the software group should participate in the project proposal effort."

JohnsonEtal05

Philip M Johnson & Hongbin Kou & Michael Palding & Qin Zhang & Aaron Kagawa & Takuya Yamashita
Improving Software development management through Software project Telemetry
IEEE Software Magazine V22n3(Jul/Aug 2005)pp76-85
=DEMO TOOL METRICS AUTOMATION DISPLAY Hackystat
Hackystat::= See http://hackystat.ics.hawaii.edu/.

JohnsonSanders90

Michael Johnson & Paul Sanders
From Z Specifications To Functional Implementations
pp86-112 in Nicholls90
Optimisation QUALITY Technical Miranda FD..FP

Johnston11

Casey Johnston
Content-Focused iPad Apps Value Form Over Function, Study Finds
Wired Online (May 29, 2011 ) [ http://www.wired.com/epicenter/2011/05/ipad-apps-form-over-function/ ]
=POLL USERS MOBILE WEB/NET APPLICATIONS
From Nielsen Norman Group report uncovers common problems with iPad applications.
Ambiguous implementation of navigation techniques
Provide hints when swiping works when not booklike.
Users didnb
Content-Focused iPad Apps Value Form Over Function, Study Finds
Wired Online (May 29, 2011 ) [ http://www.wired.com/epicenter/2011/05/ipad-apps-form-over-function/ ]
=POLL USERS MOBILE WEB/NET APPLICATIONS
From Nielsen Norman Group report uncovers common problems with iPad applications. [ http://www.nngroup.com/reports/mobile/ipad/ ]
Ambiguous implementation of navigation techniques.
If it doesn't look like a book you need to provide a visual cue to get people to swip.
User do not read the instructions and prefer to abandon the app.
Given a choice between a web site and a unobviously navigated app... the users go to the web site.
No way to go back to previously items without repeating a search.
Making interface less usable but prettier -- eg shrinking buttons.
No point in making a sub-optimal app, instead tune the website to be finger-friendly.

JohnstoneScott07

Adrian Johnstone & Elizabeth Scott
Proofs and pedagogy; science and systems: The grammar tool box
Science of Computer Programming V69n1-3(Dec 2007)pp76-85 CR 0902-0178 [ j.physletb.2003.10.071 ]
=UNREAD =ADVERT GTB PEDAGOY GRAMMARS

Jones81

Alwyn Jones
Need for 'graphicacy' should be underlined
Computer Weekly(Europe) p10 (May 28th 1981)
graphic

JonesC94a

Capers Jones
Software Management: The weakest link in the software engineering chain
IEEE Computer magazine v27n5(May 1994)pp
=SURVEY QUALITY USER PEOPLE
1. none: 15% > 12 months over
2. some: 5% > 12 months over
3. both: 1% > 12 months over
  QUALITY estimation linked to a 70% reduction in USER complaints
  Tools used in leaders: project planning, cost/size estimating, quality est, defect tracking, resource and milestone tracking, measurement & analysis

JonesC94b

Capers Jones
Geriatric Care for Legacy Systems
IEEE Computer Magazine V27n10(Oct 1994)p79
1. Maintenance assignment scope::= the yearly ammount of software that one person can keep active and operational. function points, or LOC
2. = size of portfolio/no. maintainers.
  Specialized industry that produces tools to help.
  Percentage of maintenance programmers varies from 67%(cobol) to 84%(Assembly).
  Software rot.

JonesC95a

Capers Jones(Software Productivity research)
How Office Space Affects Programming Productivity
IEEE Computer V28n1(Jan 1995)pp76-77

JonesC95b

Capers Jones(Software Productivity research)
Gaps in Programming Education
IEEE Computer V28n4(Apr 1995)pp70-71

JonesC95c

Capers Jones(Software Productivity research)
Gaps in SEI Programs
Software Development Mag V3n3(Mar 1995)pp41-48

JonesC96

Capers Jones(Software Productivity research)
The Economics of Sofware Process Improvement
IEEE Computer Magazine V29N1(Jan 1996)pp95-97

JonesC96a

Capers Jones(Software Productivity research)
Software Defect-Removal Efficiency
IEEE Computer Magazine V29N4(Apr 1996)pp94-95
1. informal design review: 25-40
2. formal design inspection: 45-55, median 60
3. informal code review:30-35
4. formal code inspection: 45-70, median 57
5. unit test: 15-50
6. new function test: 20-35
7. regression test: 15-30
8. integration test: 25-40
9. system test: 35-55
10. lowvolume beta(<10 clients) :29 to 40
11. highvolume beta(>1000) : 60 to 85
12. separate SQA dept: 32-55, median 45
13. trained testers:37-60, median 53

JonesC96b

Capers Jones(Software Productivity research)
Software Change Management
IEEE Computer Magazine V29N2(Feb 1996)pp80-82
=ADVERT PROCESS COSTS maintenance requirements bugs hypertext paperwork

JonesC96c

Capers Jones(Software Productivity research)
Activity-based Software Costing
IEEE Computer Magazine V29N5(May 1996)pp103-104
=DEMO METRICS COSTS PROCESS
1. function-points
2. interesting list of activities with sample costs and times/fp
3. requirements, prototyping, architecture, project plans, initial design, detailed design, design reviews, coding, reuse aquisition, package purchase, code inspection, independent V&V, configuration management, formal integration, user documentation, unit testing, function testing,, integration testing, system testing, field testing, acceptance testing, independent testing, quality assurance, installation & training, Project management.

JonesC96d

Capers Jones
Patterns of Software System Failure and Success
International Thomson Boston MA 1996
ref in IEEE Software magazine V13n3(Mar 1996)

JonesC03

Capers Jones
Variations in Software development Practices
IEEE Software Magazine V20n6(Nov/Dec 2003)pp22-27
=EMPIRICAL METRICS DOMAIN PRACTICES 18years
Larger projects use more activities and specialists.
Requirements, coding, reuse, and unit testing were used in all sizes of project.
End user projects use the least activities (prototyping, coding, reuse, unit testing) .. military projects all 25 activities.
Military projects have all except function-points people. Large projects have all types of specialists except globalization experts.
No method or language accounted for success/failure.
Good quality control indicates good projects.

JonesCB95

Cliff B Jones
Partial Functions and Logics: A Warning
IPL V54n2(??? 1995)pp65-67
=THEORY FORMAL LOGIC
See [LPT]
and [LPV]

JonesCB96

Cliff B Jones(U of Manchester mailto:cliff@cs.man.ac.uk)
A Rigorous Approach to Formal methods
IEEE Computer Magazine V29N4(Apr 1996)pp20-21

JonesD95

Do-While Jones<do_while@ridgequest.ca.us>
Repeatable Software developmen Part II: Configuration Management
Software Magazine (Jun 1995)pp55-57
1. requirements management
2. configuration management
  out of Level 2 CMM has half a dozen Key Process Areas (KPA).
3. Quality assurance
4. requirements management
5. configuration management
6. project planning
7. project tracking
8. subcontract management
9. CMM says what but not how. It requires a plan that is followed with: commitment + abillity + some observable results. ->- adequate funding stafing and resources.

JonesEtal05

Keith J Jones & Riachrd Bejtlich & Crtis W Rose
Real Digital Forensics: Computer Security and Incident Response
Addison-Wesley Pro Boston MA 2005 ISBN 0321240693 CR 0611-1087
=UNREAD FORENSICS RISKS ADMINISTRATION

JonesP01

Paul Jones
Open (Source)ing the Doors for contributor-run digital libraries
Commun ACM V44n5(May 2001)pp45-46
=EXPERIENCE Linux OPEN SOURCE CODE LIBRARY [ http://metalab.unc.edu/ ]
simple open FTP submission with small metadata form. 4.5% rejection rate.

JonesPE07

Peter Edward Jones
Do Programming Languages make Software too Soft
IEEE Software Magazine V24n3(May/Jun 2007)pp120+118-119
=EXAMPLE TECHNICAL leap year Java
Gives half-a-dozen variations of Java code for determining if a year is a leap year -- including 4 tests of divisibility.
Claims that languages should be harder so that only one or two solutions are possible!

JonesJones91

Peter C Jones & Paul E Jones Jr
Data Theory
Prentice Hall Int Englewood Cliffs NJ 1991 QA76.9.D3 CR9206-0367
=theory logic incomprehensible

JonesRPetal96

Rhys Price Jones<rhyspj@cs.oberlin.edu> & Fritz Ruehr & Richard Slater
Web-based Laboratories in the introductory curriculum enhance formal methods
Proc 27th SIGCSE Tech Symp on C Sci Education & SIGSCE Bulletin V28n1(Mar 1996)pp160-164
WWW H^tX Scheme Spec->coding->correctness

Jonsson94

Bengt Jonsson<bengt@sics.se
bengt@docs.uu.se>
Compositional Specification and Verification of Distributed Systems
ACM Trans Prog Lan & Sys V16n2(Mar 1994)pp259-303

Joos94

Rebecca L Joos
Software Reuse at Motorola
IEEE Software Magazine V11n5(Sep 1994)pp42-46

Jordahl91a

Gregory Jordahl(editor)
Patriot's Software Failure Let Missile Hit Troops
IEEE Software V8n4(Jul 1991)p97

Jordahl91b

Gregory Jordahl(editor)
ICSE 13 Shows Diversity - Using Formal Methods
IEEE Software V8n4(Jul 1991)p97-100

Jordan90

David Jordan
Implementation Benefits of the C++ Language Mechanism
Commun ACM V33n9(Sep 1990)pp61-67

Jorgenson04

Magne Jorgenson
Realism in assessment of effort estimation uncertainty: it matters how you ask
IEEE Trans Software Engineering V30n4(Apr 2004)pp209-278
=EXPERIMENT ESTIMATION PEOPLE PERT
PERT asks for min, mode(most likely), and max times.
Get better estimates by asking for mode + the chances that the real value is half & twice the mode.

Jorgensen05

Magne Jorgensen
Evidence-Based Guidelines for assessment of Software Development Cost Uncertainty
IEEE Trans Software Engineering V31n11(Nov 2005)pp942-954
=SURVEY DEVELOPMENT COST ESTIMATION
Uncovers evidence that software developers use intuition and expertise to predict costs and tend to underestimate them as a result.
Propose some guidelines based on on a very thorough literature survey.
Examples:
- Don't ask for 90% confidence intervals. Instead ask fro an interval and then ask what % of projects were outside the interval.
- Formal cost estimation are currently less efficient - intervals are unusable.
- Use a structured process with explicit reasons.
- Compare this project with previous projects to estimate errors.
- Perhaps use groups rather than formulas to combine estimates.
- Paying people if they are more accurate may or may not improve their accuracy.

Jorgensen09

Magnes Jorgensen
How to avoid selecting bids based on overoptimistic cost estimation
IEEE Software Magazine V26n3(May/Jun 2009)pp75-84
=THEORY ECONOMICS COSTS ESTIMATION BIDDING

JorgensenBoehm09

Magne Jorgensen & Barry Boehm
Software Development Estimation: Formal methods or expert judgement
IEEE Software Magazine V26n2(Mar/Apr 2009)pp14-19
=DEBATE ESTIMATION COCOMO

JorgensenBossen04

Jens Baek Jorgensen & Claus Bossen
Executable Use Cases: Requirements for a Pervasive Health Care System
IEEE Software Magazine V21n2(Mar/Apr 2004)pp34-41
=EXPERIENCE USE CASE PROTOTYPE MODEL REQUIREMENTS hospital Work Flows Colored Petri Nets CPN
A normal prototype models the software. An executable use case also models the environment.
Three tiers: 1: Prose, 2: formal, 3: animation.
The formal model is a colored petri net showing work flows.

JorgensenGrimsted11

Magne Jorgensen & Stein Grimsted
The impact of irrelevant and misleading information on software development estimates: a randomized controlled field experiment
IEEE Trans Software Engineering V37n5(Sep/Oct 2011)pp695-707
=EXPERIMENT ESTIMATION LABORATORY VS REALITY
Software development companies are less mislead by misinformation in specifications than people tested in a laboratory.

JorgensonMolokken-Ostvold04

Magne Jxrgenson & Kjetil Molxkken-Xstvold
Reasons for software estimation Error: Impact of Respondent Role, information collection approach, and data analysis method
IEEE Trans Software Engineering V30n12(Dec 2004)pp993-1007
=EMPIRICAL INTERVIEWS SURVEYS PEOPLE ESTIMATION ERRORS
People blame errors on things they don't control and take credit for things they do control.
Also see .Lookup Jorgenson

JorgensenShepperd07

Magne Jorgensen & Martin Shepperd
A Systematic Review of Software Development Cost Estimation Studies
IEEE Trans Software Engineering V33n1(Jan 2007)pp33-53
=SURVEY 304 PAPERS ESTIMATION COST EFFORT PREDICTION
Refs [ BESTweb ]
Search engines only find 60%of the relevant papers! Or else find 278,000 false drops.
lack of a standard terminology!
76 Journals have papers that are relevant.
Papers tend to be too focussed.
Data Sets may be out of date and not chosen well.
Lists the 10 journals having 66% of the references.

Joukhadar97

Kristina Joukhada
OMG Committee Meets on Object Analysis and Design Proposals
Object Magazine V7n1(Mar 1997)pp12-13
evidence of convergence and table of concepts and graphics for OPEN's OML and Rational's UML OOAD

JovanovicMrdalj93

Vladan Jovanovic & Stavan Mrdalj
A Structured Specification Technique for Hypermedia systems(Letter)
Comm ACM V36n11(Nov 1993)pp18-20
1. ---> pointer/links
2. object(operations
3. ( duration )

JuanTsaiMurataZhou01

Eric Y T Juan & Jeffery J P Tsai & Tadao Murata & Yi Zhou
Reduction METHODS for REAL-Time systems using delay time petri nets
IEEE Trans Software Engineering V27n5(May 2001)pp422-448
=THEORY PETRI GRAPHIC NONSEQUENTIAL MODEL =DEMO TOOL
DTPN::="Delay time Petri nets", have time ranges on arrows as well transitions.

Jullig93

Applying Formal Software Synthesis
IEEE Software Magazine (May 1993)pp11-93
=ADVERT FORMAL METHOD

Jung98

Ho-Won Jung
Optimizing Value and Cost in Requirements Analysis
IEEE Software magazine V15n4(Jul/Aug 1998)pp74--78
=THEORY =CASESTUDY REQUIREMENTS COST
use knapsack integer programming
find max value for given cost; then min cost to get max value

JungkShim04

Peder Jungk & Simon S Y Shim
Issues in High-Speed Internet Security
IEEE Computer Magazine V37n7(Jul 2004)pp36-42
=Type RISKS NET SPEED SECURITY Slammer CodeRed/NIMDA
SQL Slammer infected 75,000 systems in 31 minutes using a only 384 byte packet.
As networks speed up attacks like this will happen faster and will often be using newly invented techniques.
Argues that security demands speed+adaptability+power that can not be provided by traditional CPU or ASIC designs.
Shows how a Network Processor unit(NPU) with a field programmable gate array(FPGA) and Ternary Content Addressable Memory(T-CAM) could spot a slammer style packets or even handle Access Control Lists(ACL).
Suggests that adaptive software can spot and display statistics and patterns leading to new signatures.
(dick)|-Ignores the fact that malicious packets etc are the result of human errors in designing and coding the servers, protocols, etc.

JuricRozmanHerickoDomajnko00

Matjaz B Juric & Ivan Rozman & Marjan Hericko & Tomaz Domajnko
Integrating legacy systems in distributed object archtctures
ACM SIGSOFT Software Engineering notes V25n2(Mar 2000)pp35-39
=ADVERT EVOLUTION MATHEMATICAL METHOD selecting CORBA vs DCOM vs Java RMI

JuristoMoreno02

Natalia Juristo & Ana M Moreno
Reliable Knowledge for Software Development
IEEE Software Magazine V19n5(Sep/Oct 2002)pp98-99
=ESSAY SCIENCE VS QUACKERY
Refers to Latour & Woolgar 1986 "Laboratory Life: The Construction of Science Facts" Princeton UP for a life history of knowledge.
Refers to Vincenti's "What Engineers know and how they know it" Johns Hopkins UP 1990 to show how aeronautical engineering changed with more science being available.
Many other references.

JuristoMorenoLopez00

Natalia Juristo & Ana Maria Moreno & Marta Lopez
How to Use Linguistic Instruments for Object-Oriented Analysis
IEEE Software Magazine V17n3(May/Jun 2000)pp80-89
=DEMO METHOD OOA/D LANGUAGES BNF OMT
step by step way to map requirements via objectmodel (OM) plus behavior model (BM) to OO? design
Starts with informal requirements, but notes errors occur in them.
Splits into static vs dynamic. Translates into 1:special language; 2: OMT+martin
missing(p85) : using normalization to assign attributes to class.
missing(pp88-89) :ref to NIAM?
wrong(p87) : when a method operates on all the classes in a sub-hierarchy "the method will belong to the highest class". leads to anomolous classes with no behaviors plus highlevel classes with complex logic and so reduced maintainabillty. [BottingJuristo00]

JuristoMorenoSilva02

Natalia Juristo & Ana M Moreno & Adres Silva
Is the European Industry Moving toward Solving Requirements Engineering Problems?
IEEE Software Magazine V19n6(Nov/Dec2002)pp70-77
=POLL 150 European REQUIREMENTS ENGINEERING PRACTICE
Still a lag between theory and practice. Only simplest tools are in use. Some problems result.
page 76. Sidebar with 6 online resources:
1. Atlantic systems guild [/www.systemsguild.com/GuildSite/Guild/resources.html]
2. Chaos report series [ http://www.standishgroup.com/ ]
3. Lancaster university Good Practice Guide(GPG) [ http;//www.comp.lancs.ac.uk/computing/resources/re-gpg ]
4. ICRE/RE conferences [ http://www.re02.org ]
5. ICOSE -- systems engineering
6. http://www.icose.org
7. Karl Wiegers tools and templates [ http;//www.processimpact.com ]

JuristoMorenoSanchez-Segura07

Natalia Juristo & Ana Maria Moreno & Maria-Isabel Sanchez-Segura
Guidelines for Eliciting Usability Functionalities
IEEE Trans Software Engineering V33n11(Nov 2007)pp744-758
=SURVEY =EXPERIMENT USER PATTERNS FEATURES ISSUES HCI
Lists 9 techniques to improve usabillity:
Feedback, Undo/Cancel, Prevent/Correct errors, Wizards, User Profiles, Help, Command aggregation(record-replay), shortcuts, Reuse information
For each provides a description and a set of issues that need to be raised with the stakeholders.
See [ usability-elicitation-patterns ]

JuristoMorenoVegasSolari06

Natalia Juristo & Ana M Moreno & Sira Vegas & Martin Solari
In search of What we Experimentally know about unit testing
IEEE Computer Magazine V39n10(Oct 2006)pp72-80
=SURVEY UNIT TESTING EXPERIMENTS SWEBOK

Kahn92

Ken Kahn
A Braid of Research Threads(in The Fifth Generation Project)
Comm ACM V36n3(Mar 1993)pp77-82
=EXPERIENCE OBJECT-ORIENTED GRAPHIC DESIGN

KahnMacQueen77

G Kahn & DB MacQueen
Co-Routines and Networks of Parallel Processes
Proc IFIP 77 (North Holland Pub Co 1977) pp993-998. Also IRIA Raport de Recherche No 202 Nov 76
=THEORY timing non-sequential

KahnSaraswat92

Ken Kahn & V Saraswat
Complete visualisations of concurrent programs and their executions
in Proceedings of the Visual Language Workshop IEEE NY(Oct 1990)
=DEMO GRAPHIC NONSEQUENTIAL CODE EXECUTION

Kaindle93

Herman Kaindl<kaih@oop.geu.siemens.co.de>
The Missing Link in Requirements Engineering
ACM SIGSOFT Software Engineering Notes V18n2(Apr 1993)pp30-39
=IDEA REQUIREMENTS HYPERTEXT RETH FRAMES INHERITANCE
1. requirements_engineeering::=
  Net
  1. problem_analysis::=domain_analysis_modeling&requirements_formation
  2. requirements_definition;
  3. requirements_analysis;
  (End of Net)
  no good layout algorithm and graphic tools are not semantic

Kaindl99

Herman Kaindl
Difficulties in the Transition from OO Analysis to Design
IEEE Software Magazine V16n5(Sep/Oct 1999)pp94-102
=ESSAY OOA/D METHODS compared REALITY ANALYSIS DESIGN
Distinguish "real" entities from computer objects.
Should analysis model a world that contains the software being designed or the world without the software
Letter [Botting00]

KaindlCarroll99

Hermann Kaindl & John M Carroll (Guest Editors)
Symbolic Modeling in Practice
Commun ACM V42n1(Jan 1999)pp28-30
=SURVEY of special section page 31-63
See [MylopoulosChungYu99] & [ButlerEspositoHebron99] & [Jarke99] & [Rosson99] & [GainesShaw99]
Also see IEEE Trans Dec 1998 [JarkeKurki-Suonio99]

Kaiser95

Gail E Kaiser(ed)
SIGSOFT'95: Proceedings of the 3rd ACM SIGSOFT Symposium on the Foundations of Software Engineering
ACM SIGSOFT Software Engineering Notes V20n4(Oct 1995)
=PROCEEDINGS FSE

KallepalliTian01

Caitanya Kallepalli & Jeff Tian
Measuring and Modeling Usage and Reliability for Statistical Web Testing
IEEE Trans Software Engineering V27n11(Nov 2001)pp1023-1036
=THEORY =EXPERIENCE WWW/NET FAILURES TESTING Markov reliability

KalishMontague64

Donald Kalish & Richard Montague
Logic: Techniques of formal reasoning
Harcourt Brace & World Inc. NY NY 1964
=TEXT LOGIC
Natural deduction with boxes withn boxes.
Brilliant.

KamataYoshizawa00

Mayumi I. Kamata & Tadashi Yoshizawa
Key Factors for Managing Small Scale Software Projects : Empirical Studies on Japanese 35 Cases with a Groupware Package
Proc SCI/ISAS2000 VI pp47-52 [SCI00]
=EXPERIENCE STATISTICS Lotus-Notes REQUIREMENTS EVOLUTION PROTOTYPES
35 One-of-A-Kind small scale projects
Success by spending time on requirements, managing changes and using evolutionary prototyping

KambayashLedgard04

Yasuchi Kambayashi & Henry F Ledgard
The Separation Principle: A Programming Paradigm
IEEE Software Magazine V21n2(Mar/Apr 2004)pp- & V21n6(Nov /Dec 2004)pp9-11
=DEMO =EXPERIMENT =ADVERT separation TECHNICAL DESIGN DATA FUNCTION TOOL not Object-Oriented
Based on William S Cave, The Software Survivors, Predictions Systems, 1995
Separate data from functions. Use a graph to show what functions can access which data.
Experiment showed students could answer questions slightly faster and slightly more accurately with separation rather than Object-Oriented code. (90%+ significance? heteroskedadastic)

Kamp10

Poul-Henning Kamp
You're Doing It Wrong
ACM Queue (June 11 2010) [ detail.cfm?id=1814327 ]
=EMPIRICAL ALGORITHM PERFORMANCE VIRTUAL MEMORY B-HEAP
Proposes a new type of heap which performs 10 times better in a virtual memory system because it organizes successive accesses to be in the same page thus reducing page faults.
Compare [PechuraShoefler83] [Botting88] for other non-text-book results.

Kamp10a

Poul-Henning Kamp
Sir, Please step away from the AST-33
Commun ACM V53n11(Nov 2010)pp56-57 [ 1839676.189693 ]
=POLEMIC =HISTORY SYNTAX PROGRAMMING LANGUAGES GO JAVA C++ LIMIT ASCII ALGOL APL UNICODE GLYPHS PYTHON TCL
Why not use the full Unicode character set?
Why not use right-left positioning?
Why not use color?!
Need to escape from vi!
(dick)|-and we'll need a new keyboards for Unicode as well.

Kamp11

Poul-Henning Kamp
B.Y.O.C (1,342 times) and counting
Commun ACM V54n3(Mar 2011)pp56-58 [ 1897853.1897870 ]
=STATISTICS FOSS CRYPTOGRAPHIC CODE MD SHA AES STANDARDS C stdlibcrypto
BYOC::="Bring Your Own Code"
Found 1,300+ implementations of well known crypto algorithms in one unix distribution.
Pleads for a standard library of cryptographic routines.
Mentions own library libmd as a possible basis.

Kamp11a

Poul-Henning Kamp
The software industry is the problem
Commun ACM V54n11(Nov 2011)pp44-47 [ 2018396.2018412 ] + correspondence V55n2(Feb 2012)p6 [ 2076450.2076452 ]
=ADVOCATES LEGAL ETHICS SOFTWARE LIABILITY OPEN SOURCE VS MALWARE
Refs Thompson84 & Godel Escher Bach
Mr. Crab's record player metaphor for computer and malware.
Put not your trust in builders.
Clause 0: copied from criminal liability.
Clause 1: open source limits liability to a refund.
Clause 2: otherwise liable for damage caused by normal use.
Correspondent(Lawrence C Paulson) argues for a more draconian set of rules.

Kanaracus09

Chris Kanaracus
Study Shows improvements in quality of open source code
Info world (Sep 23 2009) [ study-shows-improvements-in-quality-open-source-code-950 ]
=REPORT QUALITY METRICS STATISTICS OPEN SOURCE
"In survey commissioned by Department of Homeland Security, Samba, tor, OpenPAM, and Ruby granted top-level status for resolving defects"
Data collected at [ about.html ]

KanBasiliShapiro94

S H Kan & V R Basili & L N Shapiro
Software quality: An overview from the perspective of total quality management(TQM)
IBM Systems Jnl V33n1(1994)pp2-19
=IDEA QUALITY USER SYSTEM CUPRIMDA FURPS CLEANROOM REUSE
1. p8: Plan-Do-Check-Act, QIP:Quality improvement Paradigm, EF: Experience Factory [Oivo&Basili93] GQM: Goal/Question/Metric
2. p11. Software inspections are distinctly diffeent from manufacturing inspections.
3. p12. cleanroom, "several oo projects...learning curve...increased productivity and quality"
4. p13: "Reuse should not be limmitted to code"

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.

KanerPels98

Cem Kaner & David Pels
Bad Software: What to do when Software Fails
Wiley New York NY 1998 QA76.76F34K36 ISBN 0-471-31826-4 Dewey 005
=TEXT RISKS QUALITY USER ECONOMICS
RISKS Why mass-marketted software has low QUALITY and how to get your money back
[ http://www.badsoftware.com/ ]

Kanetal94

S H Kan & S D Dull & D N Amundson & R J Lindner & R J Hedger
AS/400 Software Quality Management
IBM Systems Jnl V33n1(1994)pp62-88
=EXPERIENCE QUALITY PROCESS IMPROVEMENT

KangChiang06

David Kang & Roger Chiang
A Systematic approach in managing post-deployment system changes
Commun ACM V49n6(Jun 2006)pp91-95
=EXPERIENCE SUPPORT MAINTENANCE CSCI372
A system is rarely complete and without defects -- it will need changing.
Using a system generates new suggestions.
A bank went through 4 systems for handling changes.
Final system included:
1. A database of suggestions and issues
2. A user team that prioritised issues.
3. An Alpha development system.
4. A Gamma testing system with duplicate data.
5. A Production (Beta) system.

KangCheng04

Jeong A Kang & Albert Mo Kim Cheng
Shortening Matching Time in OPS5 Production Systems
IEEE Trans Software Engineering V30n7(Jul 2004)pp448-457
=EXPERIMENT RULE PERFORMANCE TIME QUALITIES OPS5 RETE
Compares speed of original and two improved algorithms for extracting rules from a rule base.

KangLeeKim00

Inhye Kang & Insup Lee & Young-Sui Kim
an efficient state space generation for the analysis of real-time systems
IEEE Trans Software Engineering V26n5(May 2000)pp453-476
=DEMO THEORY ALGORITHM TOOL TREAT SPECIFICATION TIMED FSM
continuois timed automata
History equivalence and transition bisimulation

Kant93

Elaine Kant
Synthesis of Mathematical-Modeling Software
IEEE Software magazine(May 1993)pp30-41
=DEMO MATHEMATICS MODEL

Kantetal90

Krishna Kant & A Ravichandran
Synthesizing robust data structures - an introduction
IEEE Trans Comput v39n2(Feb 1990)pp161-173
=PAPER QUALITY ROBUSTNESS DATA

KappelEtal01

G Kappel & S Rausch-Schott & W Retschitzegger & M Sakkinen Bottom-Up Design of Active Object-Oriented Data Bases
Commun ACM V44n4(Apr 2001)pp99-104
=DEMO REALITY UML MODEL to TECHNICAL OBJECT-ORIENTED DATA DESIGN TOOL Gemstone
AOODB::="Active Object-Oriented Databases".
ECA::rule="Event/Condition/Action".
Rule patterns are parameterized and composable. They allow rules that cut across applications. Usable in many domains.
(dick)|-??{ candidate for [AOP] or form of [AOP]
}

UML constraints indicate business rules
TriGS::= See http://www.ifs.unilinz.ac.at/ifs/research/publications/papers01.html.

Kaplan07

Dan Kaplan
Web2.0
CS Magazine for Security Professionals, (Feb 2007)pp25-26+28-29
=ARTICLE WEB2.0 RISKS Javascript AJAX MySpace RSS Outlook
Downloading and executing code is a bad idea that keeps on being reinvented, and then being abused.
Computer Proffessionals and Users need to work together.

KaptelinCzerwinski07

Victor Kaptelin & Mary Czerwinski (Eds)
Beyond the Desktop Metaphor -- Designing Integrated Digital Work Environments
The MIT Press Caambridge MA 2007 QA76.9.H85B539 ISBN 978-0-262-11304-5
=PAPERS USER HCI METAPHOR Lifestreams Haystack Task Gallery GroupBar Scalable Fabric Soylent

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.
1. lifecycle, domain, philosophy, products & notations, procedure, guidelines & criteria & measures, verification, formallity, maintainable products, reusable products, concurrent ystems, performance engineering, traceabillity, extension/specialization Useage
2. application areas, System Size, automated support, ease o instruction, maturity Managerial
3. organization, integration

KaramSanczykBond89

Gerald M Karam & CM Stanczyk & GW Bond
Critical Races in Ada Programs
IEEE Trans SE-15n11pp1471-1480(Nov 1989) & comments McNameeOlsonn90
=THEORY timing non-sequential

Karat98

Clare-Marie Karat
Guaranteeing Rights for the User
Commun ACM V41n12(Dec 1998)p29-31
=MANIFESTO declaring the USER's bill of rights

Karlsson95

Even-Andre Karlson
Software Reuse: A Holistic Approach
John Wiley & Sons inc NY NY 1995 $59.95 ISBN 0-471-95819 CR9606-0396
=MANUAL REUSE

KarlssonTaxen97

Even-Andre Karlsson & Lars Taxen
Incremental Development for AXE 10
[JazayeriSchauer97] pp519-520
=EXPERIENCE PROCESS EVOLUTION INCREMENTAL
increments paid off and became standard
increment::=well-defined testable independent functions in final system.

KarlstromRuneson05

Daniel Karlstrom & Per Runeson
Combining agile methods with Stage--Gate Project Management
IEEE Software Magazine V22n3(May/Jun 2005)pp43-49
=EXPERIENCES SD SDLC+XP AGILE PROCESS MANAGEMENT ABB Ericsson Vodafone
Engineers are ready for agile processes but managers fear them. Success needs both!
XP leads to better quality.
The SDLC documentation should be treated as another XP User Story.
Agile process handles the day-to-day process of development and lets managers concentrate on the overall progress.

KarniyaKusumotoInoue02

Toshihiro Karniya & Shinji Kusumoto & Katsuro Inoue
CCFinder: A Mutilinguistic Token-Based Code Clone Detection System for Large Scale Source Code
IEEE Trans Software Engineering V28n7(Jul 2002)pp654-670
=DEMO TECHNICAL TOOL CCFinder JDK BSD Linux
detecting duplicate code

KarpAH03

Alan H Karp
E-speak E-xplained
Commun ACM V46n7(Jul 2003)pp113-118 [ HPL-2000-101.html ]
=ADVERT e-speak WEB/NET e-service HP web service SOAP WSDL XML HTTP TCP/IP vs Jini Biztalk
40 year old idea: a networked environment where services are created, specified, advertised, discovered, accesses and executed -- from idea to market in 2 hours!
Get things done -- without having to say how. Just say what: "get me a printout of this here in color by 10am".
Billing, authentication, authorization, discovery, etc etc.
Protocol stacks etc.
espeak::=ftp://ftp.hp.com/linux/espeak/

KarpMiller66

Richard M Karp & Raymond E Miller
Properties of a Model for Parallel Computations: Determinancy, Termination, Queueing
SIAM J Ap Math V14n6(Nov 1966)pp1390-1411
=THEORY timing non-sequential DETERMINISTIC
computation_graph::=following,
Net
1. N::Finite=given, Nodes.
2. BRANCH::=Net{from, to: N}.
3. D::Finite($ BRANCH)=given, branches.
4. Each branch d:D has a FIFO queue of data words in it that are input to d.to and output from d.out.
5. Each node n:N inputs a fixed number of data words from each of the branches going to it, and outputs a fixed number of words into the queue leading from it that depend only on the data input.
6. A::D->Nat0=given,
7. For d:D, A(d)=number of words in d at start of the computation.
8. U::D->Nat0=given,
9. For d:D, U(d) = number of words output from d into d.from.
10. W::D->Nat0=given,
11. For d, W(d)=number of words removed from d and input into d.to.
12. T::D->Nat0=given,
13. For d, T(d) =the threshold of number of words needed in d for d.to to be initiated.
14. For all d:D, T(d)>=W(d).
15. S::=D->#Data, set of states.
16. A node n:N is eligible for initiation iff for all d:n./to (number of words in queue d >=T(d)).
17. For n:N, s:S, eligible(n,s)::@= for all d:n./to (s(d) >=T(d)).
18. No two performances of a node can be simultaneously initiated.
19. After n is initiated, W(d) words are removed from each d:n./to, and operation Op(n) is performed.
20. When Op(n) terminates, U(d) words are placed in each queue d : n./from.
21. Whole graph terminates when every node has at least on incoming edge that has too few words to let it initiate.
22. Note. A loop d:D such that d.from=d.to will act as a state for the node d.from as long as d.A=d.U=d.W.
23. |-the computation is determinate.
(End of Net)

KarvonenEtal01

Antti Karvonen & Arkki Rautama & Jorma Tarhio & Jan Turkia
Versatile Concept Map Viewing on the Web
ACM SIGCSE Bulletin V33n3(Dec 2001)pp105-108
=ADVERT CONCEPT MAPP GRAPHIC JAVA TOOL CML
Refers to CharGer, inspiration, CGWorld

KarypisHanKumar99

George Karypis & Eui-Hong(Sam) Han & Vipin Kumar
Chameleon: Hierarchical Clustering using Dynmaic Modeling
IEEE Computer Magazine V32n8(Aug 1999)pp68-75
=DEMO ALGORITHM DATA GRAPH cluster analysis

Katz90

Robert L Katz
Business/Enterprise Modeling
IBM Systems Journal V29n4(1990)pp509-525
=ADVERT MODEL DATA PROCESS
1. p510..511(Figures 1 &2) modeling across the life cycle(data,process, network)><scope, ERD,Logical, technology=design, detailed=implemented)

KatzenbergPiela93

Barbara Katzenberg & Peter Piela
Work Language analysis and the Naming Problem
Comm ACM V36n6(Jun 1993)pp86-92
=EXPERIENCE REALITY USER

KauffmannMoore97

Matt Kaufmann & J S Moore
An Industrial Strength Theorem Prover for a Logic Based on Common LISP
IEEE Trans Softw Eng VSE23n4(Apr 1997)pp204-213 [ http://www.cli.com/ ]
=EXPERIENCES PROOF LOGIC LISP ACL2 hardware CLI Nqthm

Kay77

Alan Kay
Microelectronics and the Personal Computer
Sci American(Sep77) also reprinted in Reading 11 (pp125-135) of "Microelectronics" Sci Am Readings Series
=ADVERT graphic smalltalk object-oriented

Kaye07

Richard W Kay
The Mathematics of logic: a guide to completeness theorems and the applications
Cambridge UP NY NY 2007 ISBN 052170877X CR 0902-0126
=UNREAD THEORY LOGIC MATHEMATICS SEMANTICS Zorn AC Posets TARSKI P=NP

KayReed93

Andrew Kay & Joy N Reed
A Rely and Guarantee Method for Timed CSP: A Specification and Design of a Telephone Exchange
IEEE Trans SE-V19n6(Jun 1993)pp625-639
=THEORY MODULES NONSEQUENTIAL SAFETY LIVENESS PROOF PERFORMANCE
1. TCSP::=Timed CSP traces with refusal sets - research/1 notes/kay&reed/... prevents, causes,
  rely and guarantee
  P O T S: Spec with 24 rely/guarantee pairs

KazmanChen90

Rick Kazman & Hong-Mei Chen
the metropolis model -- a new logic for development of crowdsourced systems
Commun ACM V52n7(Jul 2009)pp76-84 [ 1538788.1538808 ]
=ESSAY WEB/NET COMMONS F/OSS ONION SERVICES CROWDSOURCE JAD CBSS LIFECYCLE ANALYST DESIGN ECONOMICS ITERATION. DISTRIBUTED EVOLUTION PEOPLE COMMONS
CBSS::="community-based service systems", following
Net
1. not producing goods for consumption. Not centralized.
2. open teams.
3. Mashability -- reuse.
4. conflicting, unknowable requirements -- discover by doing, emergent. Continuous evolution.
5. Focus on operations. Start with a working system and aim for no downtime.
6. Sufficient correctness. Perpetual Beta.
7. Unstable resources -- many parallel prosumers.
8. prosumer::= produce & consumer.
9. Emergent behavior. Nondeterministic.
(End of Net)
metropolis_model::onion=kernel+periphery+masses.
principles:
1. crowd management>project management.
2. promotion through ranks, attracting developers, meritocracy.
3. split kernel services from peripheral services.
4. pernipheral work is done by crowdsourcing, kernel by higher ranked developers.
5. ubiquitous operations even as it evolves.
implications: no phases, align business to crowd, not control but lead, tutorials and examples, usability. Requirements come from the periphery, forums help but can be shortcircuited. Architecture vital core. Small modular kernel. Tools for Testing, bug reporting and tracking. Flexible delivery. High availability.

Kazmanetal96

Rick Kazman & Greogory Abowd & Len Bass & Paul Clements
Scenario-Based Analysis of Software Architecture
IEEE Software Magazine V13n6(Nov 1996)pp47-55
=ADVERT SCENARIO ARCHITECTURE ANALYSIS
SAAM::=Software Architecture Analysis Method

KeepenceMannion99

Using patterns to model. Uariability in product families
IEEE Software magazine V16n4(Jul/Aug 99)pp102-108
=ADVERT PATTERNS ARCHITECTURE realms

Kehoe93

Ray Kehoe
Applying Software Engineering
UNIX Review V11n10(Oct 1993)pp51-56
=HOWTO ENGINEERING SRS
Notes [ Kehoe93.html ]

Keidaral02

Idit Keidar & Roger Khazan & Nancy Lynch & Alex Shvartsman
An Inheritance-Based Technique for Building Simulation Proofs Incrementally
ACM TOSEM Trans Software Engineering & Methodology V11n1(Jan 2002)pp63-91
=EXPERIENCE THEORY Object-Oriented FSM
Given spec S' inherits from S and algorithm A' inherits from A, and A implements S then it is easy to show hat A' implements S'.

Keil-Slawik91

Reinhard Keil-Slawik
Artifacts in Software Design
pp168-188 in [FloydCetal91]
=THEORY POSTMODERN NONSEQUENTIAL PROCESS ECOLOGY

KeilCarmel95

Mark Keil & Erran Carmel
Customer-developer Links in Software development
Commun ACM V38n5(May 1995)pp33-44
=EXPERIENCE USER REQUIREMENTS PROTOTYPES
1. surrogates::={systems analysts, ecnical support, VARs, Intrnal consultants, external consultants, odd customers, supervisors, marketing, developers}
  Consider new types of links: each has a favorite that someone else does not use
  Custom vs package: Custom work has a real maintenance phase
  Customers as an extension of the development team

KeilEtal98

Mark Keil & Paul E Cule & Kalle Lyytinen & Roy C Schmidt
A Framework for Identifying Software project Risks
Commun ACM V41n11(Nov 1998)pp76-83
=SURVEY International Delphi 40+ managers =ANALYSIS
1. The only technical risk factor is that of new technology. Most of the factors are about people and requirements.
  Table
  Control seen as Low High
  Importance seen as
  High Customer Mandate Scope+Requirements
  Moderate Environment Execution
  
  (Close Table)

Control seen as	Low	High
Importance seen as
High	Customer Mandate	Scope+Requirements
Moderate	Environment	Execution

KeilRobey01

Mark Keil & Daniel robey
Blowing the Whistle on Troubled software Projects
Commun ACM V44n4(Apr 2001)pp87-93
=POLL 42 AUDITORS ETHICS
Some IS auditors report failing projects and some do not(mum). Those that do are frequently not heard(deaf) and may pay a high price.
Four quadrants: healthy, cover-up(mum), deaf-dumb-blind(mum & deaf), ostrich(deaf).

KeilTiwana05

Mark Keil & Amrit Tiwana
Beyond Cost: The Drivers of COTS Application Value
IEEE Software Magazine V22n3(May/Jun 2005)pp64-69
=POLL MARKET COMPONENTS PURPOSE QUALITIES COST CUSTOMIZATION USER
MIS Managers tend to treat functionality and reliability as more important than cost, ease of customization, and ease of use.

KelemenovKelemen86

Ed Kelemenov & Kelemen
Trends, Techniques, and Problems in Theoretical Computer Science
Springer Verlag 1986 (Lect Notes in Comp Sci 281)
=SURVEY theory

Keller86

Arthur M Keller
The Role of Semantics in Translating View Updates
IEEE Computer V19n1(Jan 1986)pp63-73
=DEMO data Reality

KellerR87

Robert Keller
Expert System Technology: Application and Development
Yourdon Press & Prentice-Hall Inc NJ 1987
=HANDBOOK YSM Prolog AI
[YSM] meets Prolog

KelleherPausch07

Caitlin Kelleher & Randy Pausch
Using storytelling to motivate prgramming
Commun ACM V50n7(Jul 2007)pp59-64 CR 0812-1193
=ADVERT Alice EDUCATION GENDER SCENARIOS GRAPHICS Stencils XP GAMES GIRLS

Kelley84

J F Kelley
An Iterative design methodology for user-friendly natural language office information applications
ACM TRans Office Information Systems V2n1(Mar 1984)pp25-41
=EXPERIENCE USER ITERATIVE DEVELOPMENT EVOLUTION OZ CALENDARING
"Pay no attention to the man behind the curtain"
Compare [CarrollCarrithers84]
Process
- Presented users with an incomplete working system.
- Developer could observe the users attempts to use it and intervene to make the system respond correctly.
- The interventions were stored and encoded in the next iteration.
The code defined the language used by the users... no need to design the language first.
Needed a generic structure and specific data: stored in dictionaries.

Kellog86

George Kellog
From Data Management to Knowledge Management
IEEE Computer V19n1(Jan 1986)pp74-84
=HISTORY DATA AI

Kelly78

Ian D K Kelly
How Esperanto can aid machine Translation
=ADVERT Esperanto ITL UNIVERSAL LANGUAGE
Computer Weekly (UK) (Jan 19 1978)p16
States six criteria: rich, computer text, precise, regular, humanized interface, existing corpus.
Argues that SLUNT is not proven rich enough, but Esperanto fits all criteria.

Kelly78a

Ian D K Kelly
Loglan -- a more flexible language
=ADVERT Esperanto ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) (Mar 16 1978)p20
Rebuts [Taylor78]
Argues that Sanscrit might fit the criteria best and has several centuries of formal syntax.

Kelly06

Diane Kelly
A Study of Design Characteristics in Evolving Software using stability as a criterion
IEEE Trans Software Engineering V32nt(May 2006)pp315-329
=STATISTICS SCIENTIFIC FORTRAN EVOLUTION COMMON BLOCKS MODULES METRICS REALITY
Argues tha stable properties of source code indicate good design patterns.
Studied software for aiding design of reactors started in 1975 and still successful and maintained in 200+.
Typical scientific application -- developed by scientists who are not software engineers.
Large piece of software: 15..61 kLOC. 116..295 modules. 55..119 common blocks. 5,000 variable names. 613..1625 variable names in common blocks.
One base-line version and 3 later versions.
Most measures of size increased.
Two kinds of variation: base vs evolved, plus difference between evolved versions.
Proposes formulae for estimating the variabilities of various measurements of code as it changes: distance and variation.
Indicates that meaningful domain-based names are stable and so probably a good idea.
Another pattern is the existence of blocks of dta that are essentially global -- accessed by most modules.
Did not study any of the standard metrics.
Did not apply Constantine and Myers scales of cohesion or coupling.

KellyCulleton99

Declan P Kelly & Bill Culleton (Silicon& Software Systems)
Process Improvement for Small Organizations
IEEE Computer Magazine V32n10(Oct 1999)pp41-46
=EXPERIENCE PROCESS IMPROVEMENT CMM ISO9001

KellyPohjonen09

Steven Kelly & Risto Pohjonen
Worst practices for domain-specific modeling
IEEE Software Magazine V26n4(Jul/Aug 2009)pp22-29 =EXPERIENCES 76 CASES DOMAIN MODELS LANGUAGES GRAPHICS DSL DSM
DSL::="Domain Specific Language".
DSM::="Domain Specific Model".
Everyone's first language is unlikely to be a masterpiece.
Involve stakeholders.
Understand the domain. Think about how people will use the language and/or model.
Suspect outside sources for concepts. Eg UML/3GL/code/library/tools.
Iterate. Nothing is perfect.
Balance specific and general concepts.
Don't Focus too strongly on one feature of the domain.
Choose a good notation: Symbols need to be visually different and not ugly.
Select graphic notation for relations between concepts with care.
Plan for reuse.
Understand the clients process.
Plan to train people. It is not obvous.
Plan to change after it is in use.

KellySherif92

J.C. Kelly and Y.S. Sherif
Comparison of four design methods for real-time software development
Journal of Information Technology V34n2(??)1992
=SURVEY METHODS REALTIME
Clipping from Iyer92 Ramu Iyer
>Methodologies comp.software-eng 27 Jul 1992

KellyWangLafortuneMahlke

Terence Kelly & Yin Wang & Stephane Lafortune & Scott Mahlke
Eliminating Concurrency bugs with control engineering
IEEE Computer Mag V42n12(Dec 2009)pp52-60
=DEMO TOOL Gadara NONSEQUENTIAL EFFICIENT DEADLOCK AVOIDANCE DCT PETRI siphons CONTROL THEORY
Compile time tool detects possible deadlocks and plants minimally invasive changes to code to avoid them.
DCT::="Discrete Control Theory", C G Casandras & Stephane LaFortune "Introduction to discrete Event Systems", 2nd Ednd Springer 2007

KelnerEtAl91

Marc I. Kellner & Peter H. Feiler, Anthony Finkelstein, Takuya Katayama, Leon J. Osterweil, Maria H. Penedo, and H. Dieter Rombach
ISPW-6 Software Process Example
ISPW-6 [ ispw6.html ]
=PROBLEM SOFTWARE PROCESS
Quote

KelseyEtal98

Richard Kelsey & William Clinger & Jonathin Rees(Editors)
Revised Report on the Algorithmic Language Scheme
ACM SIGPLAN Notices V33n9(Sep 1998)pp26-76
=LRM BNF SYNTAX denotational SEMANTICS

Kemmerer90

Richard A Kemmerer
Integrating Formal Methods into the Development Process
IEEE Software V7n5(sep 1990)
=ADVERT FORMAL MATHEMATICS

KennedyEberhart02

James Kennedy & Russell C Eberhart
Swarm Intelligence
Morgan Kaufman 2001 ISBN 1-55860-595-5 QA337.3 K45
=IDEA NON-ALGORITHMIC NONSEQUENTIAL OPTIMIZATION
In a swarm individuals tend to both move toward their topological neighbors, but also toward the individual that seems to be doing best.
Claims to be useful and effective.
Overgeneralized (?) to argue that intelligence is dependant on the interaction of individuals.
Useful survey of many years of experiments with systems made of interacting individuals.

Kenny84

?? Kenny
Co-routines
C User's Group Newsletter II 2 BDS C User's group Box 287 Yates Centre KS 66783
=HOWTO CODE C non-sequential

Kerner10

Sean Michael Kerner
Mozilla Firefox Gets More 'Agile' with Lorentz
developer.com (Jan 22 2010) [ Mozilla-Firefox-Gets-More-Agile-with-Lorentz.htm ]
=NEWS MOZILA AGILE LORENTZ RELEASES

Kernighan08

Brian Kernighan
Sometimes the Old Ways are best
IEEE Software Magazine V25n6(Nov/Dec 2008)pp18-19
=HISTORY PROGRAMMING
Old tools still good and useful: grep, diff, sort, wc, find, shell scripts
Good tools: do something better than manually, available everywhere, can be used creatively, not to specialized or intelligent.
Need for tools to ashare a uniform representation -- for example ASCII.
"I can often have the job done while experts are still waiting for the IDE to start up."

KernighanPike99

Brian W Kernighan & Rob Pike
Regular Expressions: Languages, and Software
Dr. Dobb's n298(Apr 1999)pp19-22
=ALGORITHMS TECHNICAL grep Matching

KernighanPlauger74

Brian E Kernighan & ?? Plauger
Elements of Programming Style
McGraw-Hill NJ 1974
=TEXT STYLE sequential technical RISKS
Quotes large amounts of erroneous text books.
"Make it right before you make it faster."
"Make it clear before you make it faster."

KernighanPlauger76

Brian E Kernighan & ?? Plauger
Software Tools
Addison Wesley Reading MA USA
=TEXT non-sequential

KernighanPlauger81

Brian E Kernighan & ?? Plauger
Software Tools in Pascal
Addison-Wesley Reading MA.
=TEXT non-sequential PASCAL

KernighanRitchie

Brian E Kernighan & Dennis Ritchie
The C Programming Language
Englewood Cliffs NJ Prentice Hall Int. 1978
=MANUAL C LANGUAGE case-study

KerthCunningham97

Norman L Kerth & Ward Cunningham
Using Patterns to Improve Our Architectural Vision
IEEE Software V14n1(Jan/Feb 1997)pp53-59
=ADVERT PATTERNS
Quotes Humpty Dumpty. mystical: quality-without-a-name.

Kesler00

Laurie A Williams & Robert R Kesler
All I really need to know about pair programming I learned in kindergarten
Commun ACM V43n5(May 2000)pp108-114
=ESSAY CODE TECHNICAL PEOPLE XP
One drives, one reviews, then switch at the keyboard, both are reponsible for results.
errors drop and productivity goes up!
14 rules from Fulghum

KestenKleinPnueliRaanan99

Yonit Kesten & Amit Klein & Amir Pnueli & Gil Raanan
Bridging the E-Business Gap Through Formal Verification
In [HincheyBowen99] pp118-137
=EXPERIENCE VERIFICATION DESIGN SECURITY MODULE SAFETY SPIN SPL SPL++ PROMELA STeP C++
How to formulate a C++ class in SPL++.
Proves a composition rule for safety channel properties.
Safety properties: once failed they are never again met.
Top-level design took nearly 7 hours to verify using SPIN/Linux on 333MHz Pentium-II.
Used manual verification for the detailed C++. Calls for deductive verification tools that can handle threaded C++.

Keuffel90

Warren Keuffel
House of Stucture(article)
UNIX Review V9n2(Feb 1991)pp28-36.
=History STRUCTURED DESIGN SD SA SAD OO
Box p30-31:Lary Constantine
Box p33 Methods and CASE

Keuffel95a

Warren Keuffel
The Launch Chasm
Software Development Magazine(Jul 1995)pp27-32
=EXPERIENCE MARKET HYPE CASE
1. (1) innovators "got to have it"
2. (2) Early Adopters
3. (3) Early Majority
4. (4) Late Majority
5. (5) Laggards and Luddites
  CASE was over hyped (James Martin),.... snake oil, crash. No agreed standard methods supported.
  CASE needed to find a niche that would get it across the chasm.
  p30: "A technology in search of an application rather than a toolset crafted to meet customers' known needs" p32:"we should sell no technology before its time"

Keuffel95b

Warren Keuffel
And Now the Microsoft Process
Software Development Magazine(Aug 1995)pp29-32+letters (Oct 1995)p11+reply(Nov 1995)pp31-33
=REPORT PROCESS MICROSOFT MS-PROCESS
1. Part 1: Cusumano's ICSE Talk: PEOPLE Daily smoke-test common style metrics milestones [ Keuffel95b.html ]
2. Part 2 Brooks's talk [Brooks95]
Keuffel95c
1. Warren Keuffel
2. People-based Processes: a RADical Concept
3. Software Development Magazine(Nov 1995)pp31+32+35+36..37 +letter Jan 1996 p13
4. =IDEA MATURITY CMM RAD
5. SEI.CMM is not the only process
6. CMM process does not have to be sequential (but CMM tends to make you think sequentially!)
7. RADical::=Plan;Build;Focus.
Keuffel96
1. Warren Keuffel
2. Smelling the Rose
3. Software Development Magazine(Apr 1996)pp35-38
4. =HISTORY Unified method OOA/OOD/OOAD rational TOOL
Keuffel96a
1. Warren Keuffel
2. Helping a Reader Out
3. Software Development Magazine (Jul 1996)pp35+36+38
4. =ADVERT REQUIREMENTS
5. State of the art? study groups: McConnell93 & DavisA95
Keufel96b
1. Warren Keuffel
2. Coad Comes of Age
3. Software Development Magazine V4n10(Oct 1996)pp31-32+34
4. =ADVET OO Design alternate notation to UML
Keuffel97a
1. Warren Keuffel
2. Stepwise Process Improvement at Hewlett Packard
3. Software Development magazine V5n10(Oct 1997)pp25-27
4. =EXPERIENCE plan-do-check-act spiral CMM
Keuffel97b
1. Warren Keuffel
2. Just Doing It
3. Software Development magazine V5n11(Nov 1997)pp31-32
4. =EXPERIENCE at Nike of enterprise-wide data model
5. ASD="adaptive Software development" Highsmith [Keuffel(Jul 1997)"Adapting Personal Processes"]
Keuffel98
1. Warren Keufffel
2. Apache: An Open-Source Software Succes Story
3. Software Development Magazine V6n6(Jun 1998)pp29-31
4. =EXPERIENCE PROCESS NET/WWW APACHE
5. A PAtCHy Server:-) APACHE
6. 48% of market
7. organic meritocracy(election to core group) fixing problems in their own use of the system [MockusFieldingHerbsleb00]
8. all changes require multiple peer approval giving inspected code
  voting:+1|0|-1 or yes|(no&explanation)
9. Roy Fielding:success in a worst-case situation [Fielding99]
10. Jim Highsmith: like my Adaptive Software Development process - not stable/optimizing but adapting
Keuffel99
1. Warren Keuffel
2. A Ten-fold Improvement?
3. Software Development V7n7(Jul 1999)pp25-27
4. =EXPERIENCE vertical market MIS projects with a tight fixed price ($0.1M) and time (6 months)contract TOOLS PROCESS ORACLE PROTOTYPE
Keuffel99b
1. Warren Keuffel
2. Novell's Novel Turnaround
3. Software Development V7n8(Aug 1999)pp25-26
4. =EXPERIENCE Start with techie top manager and focus on core market
5. NPI: New Product Idea pipieline, engineers own and develop new ideas, refresshing the R&D group
Keuffel99c
1. Warren Keuffel
2. When There Are No Second Chances
3. Software Development V7n10(Oct 1999)pp21-22
4. =EXPERIENCE high RISKS requires high Maturity IMPROVEMENT Ogden Air Logistics Center,
5. TEAM Software Process TSP is between PSP and CMM
Keuffel00a
1. Warren Keuffel
2. Extreme Programming
3. Software Development V8n2(Feb 2000)pp26-27
4. =SURVEY ASD XP ASD= [Highmith99)]
Keuffel00b
1. Warren Keuffel
2. A broader context for UML
3. Software Development magazine V8n5(May 2000)pp62-63
4. =ADVERT LIFECYCLE METHOD top-down user mission ERD hardware+software+operator objects
5. Odel:=object description language,
6. Tofs:=http://www.toolsforsystems.com,
7. O4S::=Objects for Systems, Ingmar Ogren, iog@romet.se [ http://www.romet.se ]
Keuffel00c
1. Warren Keuffel
2. Best practices actually applied
3. Software Development Magazine V8n7(Jul 2000)pp57-59
4. =EXPERIENCE WWW Cysive PROCESS UML UseCases OBJECT-ORIENTED REVIEWS INSPECTIONS IMPROVEMENT TECHNOLOGY
5. Traditional software engineering with objects and nonCMM process improvement.
6. Another project manager reviews each project each month and gives a written report to executive management and clients.
7. Uses small teams. Teams involved in selecting methods.
8. special activities to evaluate and learn new technologies in a pipeline.
Keuffel01
1. Warren Keuffel
2. No silver Bullets
3. Software Development Magazine V9n4(Apr 2001)p80
4. =HISTORY CASE Brooks PATTERNS ANALYSIS vs DESIGN
5. silver lining: Jackson01 Problem frames
Keuffel03
1. Warren Keuffel
2. The Matrix, Redux
3. Software Development Magazine V11n1(Jan 2003)p56
4. =REVIEW ARCHITECTURE Zachman DATA PURPOSES WEB/NET USER EUE Visual Vocabulary
5. Zachman::= See http://www.zifa.com/.
6. EUE::="The Elements of User Experience", .Seeee http://www.jjg.net/ia/elements.pdf
7. Visual_Vocabulary::= See http://www.jjg.net/ia/visvocab/.
Keuffel04
1. Warren Keuffel
2. Spinning the Semantic Web
3. Software Development Magazine, Web Services Newsletter (Nov 2004)
4. =Article Semantics Web/net ontology OWL RDF XML
5. Where to find meaning?
  1. Experts. Ontology Working group
  2. Users. Emergent Semantics. Sony Paris. Steffen Staab.
  3. Language. Computational semiotics. Alexander Maedche
Keyes92
1. Jessica Keyes
2. How Software is Developed Undergoing Basic Changes
3. Software Magazine(Jan 1992)pp38-55
4. =ADVERT Information Engineering
5. 001 method
6. Linc Systems Approach
7. CASE must include and enforce methods
8. Gane and sarson HyperAnalyst is an Expert System with 191 activities...The software development process is broken...a very piecemeal approach...
Khanna91
1. S Khanna
2. Logic Programming for Software Verification and testing
3. Comput Jnl V34n4(Aug 1991)pp350-357.
4. =DEMO LOGIC V&V TESTING
Khoury02
1. Carole Khoury
2. OO-AS-IS, an Object-Oriented Algebraic Specification formalism with Implicit State for Reactive systems
  [SCI2002] V1(Jul 2002)pp
3. =IDEA ECLECTIC FORMAL NOTATION
Kiczales96
1. Gregor Kiczales(Xerox PARC gregor@-arc.xerox.com)
2. Beyond the Black Box: Open the Implementation
3. IEEE Software Magazine V13n1(Jan 1996)pp8-10
4. =IDEA MODULE 2 INTERFACES DESIGN QUALITY
5. generic performance metaprogramming: primary interface plus a metainterface allowing a client to adjust the implementation strategy decisions [ oi ] [Kiczalesetal97]
Kiczalesetal97
1. Gregor Kiczales & John Lamping & Cristina Videira Lopes & Chris Maeda & Anurag Mendhekar & Gail Murphy
2. Open Implementation Design Guideline [ICSE'97]
3. =DEMO REUSE TECHNICAL DESIGN QUALITY INTERFACE
4. separate interfaces for function and quailty control eg add arguments to constructor to describe expected usage patterns or prefered implementation strategies or replacement strategies
  [Kiczales96]
KiczalesEtal01
1. Gregor Kiczales & Erik Hilsdlae & Jim Hugunin & Mik Kersten & Jeffrey Palm & Wiliam G Griswold
2. Getting Started with AspectJ
3. Commun ACM V44n10(Oct 2001)pp59-65+ letters Commun ACM V45n2(Mar 2002)pp11-12
4. =ADVERT AspectJ ASPECT AOP for JAVA TOOL
5. Distinguishes production aspects from development aspects.
Kienle01
1. Holger M Kienle
2. Exchange Format Bibliography
3. ACM SIGSOFT Software Engineering Notes V26n1(Jan 2001)pp56-60
4. =BIBLIOGRAPHY GRAPHS GDL GRL GML daVinci RSF TA DATA GXL RDF XML ATerms GEL CDIF ASN XDR ASDL SUIF Hoof AST SDE ANDF Schemas GraX TGraphs RAL UML MOF
5. "CDIF appears to be maintained no longer"
Kilov91
1. Haim Kilov<haim@haim@cc.bellcore.com>
2. Conventional and Convenient in Entity-Relationship Modeling
3. ACM SIGSOFT SENotes V16n2(Apr 1991)pp30-31
4. =IDEA ERD
Kilov94
1. Haim Kilov<haim@haim@cc.bellcore.com>
2. On Understanding Hypertext: Are Links Essential?
3. ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)p30
4. =IDEA RELATIONS vs HYPERTEXT
KilovRoss94
1. Haim Kilov<haim@cc.bellcore.com> & James Ross
2. Information modeling: an object-oriented approach
3. Prentice-Hall 1994 ISBN 0-13-083033-X reviewed SIGSOFT SEN V21n2(Mar 1996)pp91-92 "beneficial and entertaining"
4. =ADVERT IBM METHOD DATA OO
  1. separation of concerns between specifying business rules and implementing systems based on them "patterns of reasoning" in information modeling -- generic associations encountered in any application.
Kim97
1. K H (Kane) Kim
2. Object Structures for Real-time Systems and Simultators
3. IEEE Computer Magazine V30n8(Aug 1997)pp62-70
4. =ADVERT non-sequential object-oriented TIMING
5. object has name+collaborations+data+time-triggered and spontaneous methods+message-triggered methods
Kim00
1. K H (Kane) Kim
2. APIs for real-time distributed object programming
3. IEEE Computer Magazine V33n6(Jun 2000)pp72-80
4. =ADVERT RMMC BCC C++/JAVA SvM
5. TMO:="time-triggered, message triggered object".
Kim04 Hee-Woong Kim
1. A Process Model for Successful CRM System Development
2. IEEE Software Magazine V21n4(Jul/Aug 2004)pp22-28 =EXPERIENCE SUCCESS vs FAILURE CAUSE-and-EFFECT INFLUENCE MODEL PROCESS CRM ERP PQRST
3. CRM::="Customer Relations Management" Uses cause-and-effect graphs to trace how long term high level championship leads to an effective system, but loss of championing leads to a less effective system. Parts of a positive process: championship gives Management support and Resources.
4. Management support encourages user participation... Leads to a skillful project team and good requirements management. Hence good design and change management.
5. Requirements lead to a good strategy, process, and system design. Good systems integrate well with legacy and new systems. And good systems have better functionality. This improves system quality and user satisfaction,
6. Skillful teams lead to good change management.
7. Change management and quality systems lead to use.
8. The quality and process have a positive impact.
Kimball96
1. Ralph Kimball
2. The Data Warehouse Toolkit: Practical techniques for building dimensional data warehouses
3. John Wiley & Sons Inc NY NY 1996 $44.95 ISBN0-471-15337-0 CR9611-0868
4. =HANDBOOK TOOL DATA
KimLochovsky89
1. W Kim & FH Lochosky(eds)
2. Object-Oriented Concepts, Databases, and Applications
3. ACM Press NY 1989
4. =IDEA OBJECT-ORIENTED data
KimWhiteheadZhang08
1. Sunghun Kim & James Whitehead Jr & Yi Zhang
2. Clasifying software changes: Clean or Buggy
3. IEEE Trans Software Engineering V34n2(Mar/Apr 2008)pp181-196
4. =STATISTICS OPEN SOURCE CHANGES SVM
5. Has a definition of a buggy change -- a change that is later changed and described as a bug/fix etc.
6. Analyses a dozen open source projects.
7. Doesn't find a simple way to recognise a change that contains a bug vs a clean change.
King88
1. David King
2. Creating Effective Software: Computer Program Design Using the Jackson Method
3. Prentice Hall NJ 1988
4. =TEXT DDD JSP
King89
1. Roger King
2. My Cat is Object-Oriented
3. in [KimLochovsky89] p24
4. =ESSAY OBJECT-ORIENTED
KingHammondChapmanPryor00
1. Steve King & Jonathon Hammond & Rod Chapman & Andy Pryor
2. Is proof more cost-effective than testing?
3. IEEE Trans Software Engineering V26n8(Aug 2000)pp673-797
4. =EXPERIENCE FORMAL COST TEST Z SPARK Ada SHOLIS helicopter TOOLs
5. More faults fond per day trying to prove Z specs than by testing or inspections.
KingPardoe85
1. M.J. King & J.P. Pardoe
2. Program Design Using JSP: A Practical Introduction
3. (Paperback) J Wiley & Sons NY NY 1985
4. =TEXT DDD JSP
KingT07
1. Tom King
2. Dr. Dobbs Requirements Development n4(Apr 2007)p17 [ index.php ]
3. =POLL REQUIREMENTS USE CASES ACTIVITY DIAGRAMS
4. 50% adopted use cases, 25% activity diagrams, ... large companies adopt more than small ones.
5. Adoption patchy.
Kiniry02
1. Joseph R. Kiniry <kiniry@acm.org>
2. Semantic Component Composition
3. Submitted to GCSE/SAIG '02, arXiv.org e-Print archive Mon, 15 Apr 2002 [ 0204036and Ph.D. Thesis CalTech] .
4. =ADVERT THEORY MODULES CORRECTNESS CONTRACT REUSE COMPONENTS SEMANTICS Kind-theory LOGIC QUALITIES BON Jiki
5. author attempted to develop a way to describe components, calculate inter-operation, and to lead automatically generating adapters to connect components.
6. instance : kind
7. kinds: 2 inheritance relations, 2 inclusion relations, several equivalences, 2 realization relations, 3 composition operators, 2 interpreter mappings, a canonical operator [_]
8. Compare with many previous logistic systems going back to Aristotle.
9. semantic_ properties:=meta_information | dependencies | inheritance | contractual | concurrency | usage | pending_work | versioning | documentation | Miscellaneous.
10. meta_information:= author | bon | bug | copyright | description | history | license | title,
11. dependencies:= references | use.
12. inheritance:= hides | overrides | realizes,
13. contractual:=ensure | generate | invariant | modifies | require,
14. usage:= param | return | exception.
15. pending_work:= idea | review | todo.
16. versioning:= version | deprecated | since.
17. documentation:= design | equivalent | example | see.
18. Miscellaneous:= guard | values | time_complexity | space_complexity.
KiperLutzEtlinger92
1. James Kiper & Michael J Lutz<mjl@cs.rit.edu> & Henry A Etlinger
2. Undergraduate Software Engineering Laboratories: A Progress Report from Two Universities
3. ACM 23rd SIGCSE technial Symposium SIGCSE Bulletin V24n1(Mar 1992)pp57-62
4. =EXPERIENCE EDUCATION CASE labs
KirkegaardMollerSchartzbach04
1. Christian Kirkegaard & Anders Moller & Michael I Schartzbach
2. Static Analysis of XML Transformations in Java
3. IEEE Trans Software Engineering V30n3(Mar 2004)pp181-192
4. =DEMO XACT TOOL JAVA =FORMAL XML templates DTD XPATH summary graphs
5. Demonstrates tools and theories for expanding XML templates and DTDs and validating transformations.
6. Source code [ http://www.brics.dk/Xact/ ]
KirnerDavis95
1. Tereza G Kirner & Alan M Davis
2. Nonfunctional Requirements of Readl-Time Systems
3. Advances in Computers V42(1996)pp2-37
4. =THEORY TIMING QUALITY
Kirsch09
1. Russell A Kirsch
2. An undetected Error (letter)
3. IEEE Computer Magazine V42n4(Apr 2009)p53-59
4. =HISTORY SEAC ERRORS RELIABILITY
5. SEAC work 24/7 for four years with an undetected error! Discovered when moved.
6. Video [ videosearch?q=seac+history ]
7. The_Kirsch_Principle::="All computers are always, in some, sense 'broken'".
8. Reliability can occur in the presence of defects.
KishiNoda06
1. Tomoji Kishi & Natsuko Noda
2. Formal verification and software product lines
3. Commun ACM V49n12(Dec 2006)pp73-77
4. =ADVERT MODEL CHECKING ENVIRONMENT + PRODUCT VARIATIONS UML PROMELA SPIN TOOL ECLIPSE
5. Features map to variations in environment & product models.
6. Models include classes and state machines in UML, mapped into Promela.
7. Tools check scenarios...
Kishidaetal87
1. K Kishida & M Teramoto & K Torri & Y Urano
2. Quality-Assurance Technology in Japan
3. IEEE Software V4n5(Sep 1987)pp11-18
4. =ARTICLE SQA QUALITY
Kitchenham96
1. Barbara Ann Kitchenham(barbarak@ncc.co.uk)
2. Evaluating Software Engineering Methods and Tools: Part 1: The Evaluation Context and Evaluation Methods
3. ACM SIGSOFT Software Engineering Notes V21n1(Jan 1996)pp11-15
4. =SURVEY EXPERIMENT METHODS TOOLS
5. DESMET: (qualititive|Quantitive)(formal experiments | case studies | surveys) | Qualitive (screening|survey) | benchmarking
KitchenhamHughesLinkman01
1. Barbara A Kitchenham & Robert T Hughes & Stephen G Linkman
2. Modeling Software measurement data
3. IEEE Trans Software Engineering V27n9(Sep 2001)pp789-804
4. =EXPERIENCE ERRORS STATISTICS METRIC METADATA STANDARD ERA TOOL miniSQUID
5. Most measurement problems stem from: poor definitions of what is being measured, what type of data is produced,not providing suitably powerful data bases, and failing to match techniques to goals.
6. Need to establish standards for metric data across projects -- and tools for metaanalysis.
7. Some values need historical data and in others a new value overwrites the old one.
8. definition precise enough to allow comparison globally.
9. measurment_scales::= nominal | ordinal | interval | ratio | absolute.
10. ordinal::=restricted_ordinal | unrestricted_ordinal.
11. Nominal: finite set of values. ordinal: set of linearly ordered values. interval: linear order with a difference operation. ...
Kitchenhametal95
1. Barbara Ann Kitchenham(barbarak@ncc.co.uk) & Lesley Pickard & Shari Lawrence Pfleeger
2. Case studies for Method and Tool Evalutation
3. IEEE Software Magazine V12n4(July 1995)pp52-62
4. =ESSAY SCIENCE vs CASE-STUDY
5. Rejects results where project is a success with nothing to compare it with. [Pfleeger93] [ Kitchenhametal95.html ]
Kitchenhametal95a
1. Barbara Ann Kitchenham(barbarak@ncc.co.uk) & Shari Lawrence Pfleeger & Norman Fenton
2. Towards a Framework for Software Measurement Validation
3. IEEE Trans Softw Eng VSE21n12(Dec 1995)pp929-944
4. =SURVEY METRICS QUALITY ERD
5. ERDs of concepts of METRICS. Some errors? in ERDs but a good analysis of the situation.
Kitchenhametal96
1. Barbara Ann Kitchenham(barbarak@ncc.co.uk) & Shari Lawrence Pfleeger
2. Software Quality: The Elusive Target
3. IEEE Software Magazine V13n1(Jan 1996)pp12-21
4. =ESSAY QUALITY
  [ISO9126] on page 19
KitchenhamEtAl02
1. Barbara A Kitchenham & Shari Lawrence Pfleeger & Lesley M Pickard & Peter W Jones & David C Hoaglin & Khaled El Emam & Jarrrett Rosenberg
2. Preliminary Guidelines for Empirical Research in Software Engineering
3. IEEE Trans Software Engineering V28n8(Aug 2002)pp721-734
4. =STANDARD EMPIRICAL EXPERIMENT STATISTICS
5. Propose standards for doing, analyzing, and publishing empirical research.
6. Gives examples of papers that have failed to meet these standards.
7. Notes that medical research has similar problems.
KitchenhamJefferyConnaughton 07
1. Barbara Kitchenham & David Ross Jeffery & Colin Connaughton
2. Misleading Metrics and Unsound Analysis
3. IEEE Software Magazine V24n2(Mar/Apr 2007)pp73-78
4. =STATISTICS EXPERIENCES PROCESS STANDARD ISO/IEC 15393 METRICS PRODUCTIVITY Function points AMS
5. AMS of IBM Australia is CMM level 4 softare group and has statistical databases for all their projects.
6. Standard defines productivity = Lines_of_code / hours_of_effort.
7. This ratio was not normally distributed and had a large standard deviation accross all projects.
8. Classic statistical control charts don't make sense.
9. Aggregated values do not apply to particular projects
10. Scatter plots of Effort vs size in function points shows that a correlation model does not apply: nonhomoskedadistic for a start.
11. Should use similar projects, graphical displays of data, transform data before correlating effort vs size, avoid means and standard deviations, beware metrics that are ratios!
KitchenhamMendesTravassos07
1. Barbara A Kitchenham & Emilia Mendes & Guilherme H Travassos
2. Cross versus Within-Company Cost Estimation Studies: A Systematic Review
3. IEEE Trans Software Engineering V33n5(May 2007)pp316-329
4. =SURVEY ESTIMATE COSTS COCOMO
5. Can a company rely on data frm other companies to guide its cost-estimation methods?
6. Found the 10 empirical papers published on this topic. Evaluated and compared them. Drew conclusions:
7. A large company, similar applications, similar sizes, some large projects all indicat that estimtes can be made better using data from another company.
8. Small companies, specialized or small projects, or homogeneous internal data sets indicate that a company should only use its own data to calibrat its estimates.
KjaerMadsen95
1. Arne Kjaer & Kim Halskov Madsen
2. Participatory Analsis of Flexibillity
3. Commun ACM V38n5(May 1995)pp53-60 CR9609-0695
4. =EXPERIENCE USER REQUIREMENTS EXCEPTION postmodern
KlarlundSchwartzbach99
1. Nils Klarlund & Michael I Schartzbach
  [WileRaming99] pp378-386
2. =ADVERT REGULAR EXPRESSIONS FIDO for Sets and Trees M2l MONA
KlasNakaoElberzhagerMunch10
1. M Klas & H Nakao & F Elberzhager & J Munch
2. Support planning and controlling of early quality assurance by combining expert judgment and defect data--a case study
3. Empirical Software Engineering V15n4(?? 2010)pp423-454 CR
4. =EMPIRICAL ESTIMATION REQUIREMENTS OUTSOURCED QUALITY ASSURANCE EFFORT EXPERTS STATISTICS SQA
5. Shows that expert opinion improves predictions using history.
6. Case study only of requirements. But probably same hybrid method will work with other artifacts.
7. Models only apply to independent validation and verification.
8. (dick)|-Probably not needed with an agile process.
KlaweWhitneySimard09
1. Maria Klawe & Telle Whitney & Caroline Simard
2. Women in Computing -- take 2
3. Commun ACM V52n1(Jan 2009)pp68-76 [ 1461928.1401947 ]
4. =SURVEY GEBDER COMPUTING EDUCATION CAREERS
5. Excellent quote and interesting statistics.
6. Why has there been a decline in the representation of women since the 1980s?
7. Alice the programming language
Kleene56
1. S Kleene
2. Representation of Events in Nerve Nets & Finite Automata
3. in Shannon & McCarthy 56 pp 3-42
4. =THEORY REGULAR DYNAMICS FSM
Klein93
1. Mark Klein
2. Capturing Design Rationale in a Concurrent Engineering Teams
3. IEEE Computer Magazine V26n1(Jan 1993)pp39-47
4. =IDEA SEMANTIC NET REQUIREMENTS DECISIONS DRCS
  1. DRCS::=" Design Ratonale Capture System" Rationale connects decisions made in process Refinement generates constraints downward and between parts that are connected Uses semantic nets.
Kleinberg08
1. Jon Kleinberg
2. The Convergence of Social and Technological networks
3. Commun ACM V51n11(Nov 2008)pp66-72 [ 1400214.1400232 ]
4. =EMPIRICAL 6DEGREES SMALL WORLDS GRAPHS WEB/NET Milgram SOCIOLOGY CONTAGION MIMETICS IDEAS
5. Evidence that real social networks are "small worlds" as predicted.
6. Evidence that ideas spread in jagged trees through the network.
7. "Contagion as a Design Priciple"
KleinJiangTesch02
1. Gary Klein & JAmes J Jiang & Debbie B Tesch
2. Wanted: Project teams with a blend of IS professional Orientations
3. Commun ACM V45n6(Jun 2002)pp81-87
4. =POLL GRID PEOPLE TEAMWORK
5. 3 types of Information Systems orientations: technical, user, socio-political.
6. Successful teams have had a mix of these.
Kleiner91
1. Israel Kleiner
2. Rigor and Proof in Mathematics: A Historical Perspective
3. MAA Mathematics Magazine V64n5(Dec 1991)pp291-314
4. =HISTORY MATHEMATICS PROOF
5. themes: validity of a proof reflects the mathematical climate at the time, changes in rigor (up and down) occur because of good mathematical reasons, changes in rigor created problems with rigor.
6. Babylon, ..., computer

Kleppe08

Anneke Kleppe
Software Language Engineering: creating domain-specific languages using metamodels
Addison-Wesley Boston MA (2008) ISBN 0321553454
=UNREAD =DEMO LANGUAGE ASM CSM DSL Grasland
Notes: RFC [click here Kleppe08 if you can fill this hole]

KlepperBock95

Robert Klepper & Douglas Bock
Third and Forth Generation Language Productivity Differences
Commun ACM V38n2(Sep 1995)pp69-79
=EMPIRICAL MIS METRICS PRODUCTIVITY 4GL vs 3GL
study of empirical study of impact of 4GL on System devt vs 3GL
1. in complex MIS, mixed situations, FPoints, MDAIS using STRADIS archive selected all new business application systems 2 year period 1988 total labor hours...reuse, method, FPs, FP/hr, MISS(tendency to have missing data), %3GL,%4GL, N=40.,regression, remove outliers, N=37 Conclusions: 4GL gives higher FP/hr in design phase -- less than claimed but statistically significant. roughly 25% reduction in hours

KlineGirow00

Marshall Cline & Mike Girou
Enduring Business Themes
Commun ACM V43n5(May 2000)pp101-106
=EXPERIENCE THEORY MANAGEMENT SPECIFY ADAPTABLE OBJECT-ORIENTED BUSINESS SOFTWARE
EBT:=enduring business theme, -- specify and annalyse business,
EBF:=enduring business framework,
An EBF implements an EBT.
1. difficult to design classes with the right amount of generallity. they tend to be too thin (data mainly no glue).or too thick (many adjustable features).
2. first focus on glue code connecting objects since that dictates object detail.
3. ?collaboration?
4. themes are abstrations: city as market place with adaption of rational buying selling agents, not as dellicatesan-street-cashRegister objects.
5. enduring themes are better: objects modeling nouns or verbs?
6. insights not decomposition.
7. business: the structure of business sentences with blanks for the current objects.
8. business what not how.
9. Customer's viewpoint. Not railroad but transport.
10. think more about Future requirements than today's.
11. avoid cetralized command and control models.
12. an EBF is incomplete (abstract). Needs new-style industry objects implementing policy and timing.
13. possible to reverse engineer EBF from code. Better to think the EBT first.

KlosterZellweger87

Gregory V Kloster & Andres Zellweger
Engineering the Man-Machine Interface for Air Traffic Control
IEEE Computer Magazine V20n2 (Feb 1987)pp47-62
=EXPERIENCE USER REQUIREMENTS JAD GUI SREM SCENARIOS FAA AAS
FAA AAS rigorous USER REQUIREMENTS JAD workstudy SREM SCENARIOS focus on linguistic model of GUI

Kluger08

Jeffrey Kluger
Simplexity -- why simple things become complex (and how complex things can be made simple)
Hyperion NY NY(2008) ISBN 978-1-4013-0301-3
=ANECDOTES PLECTICS SYSTEMS COMPLEXITY PEOPLE MANAGEMENT BIOLOGY ART SANTA FE GELL-MANN
Chapter 9 on the complexity of technology is worth reading.
Theory: complexity appears near the middle of the range of systems from the unconstrained (perfect gas) to the overconstrained (rock).
Theory: mid-level jobs are simpler than top and bottom level jobs - and so easier to automate.
Reference to orbifolds modeling music.

Knaster28

B Knaster
Un Theoreme sur led fonctions d'ensembles
Ann. Soc. Polon. Math. V6(1928) pp133-134[ref Tarski 55]
=Mathematics semantics

Knee06

Michael Knee
Computer science and computing: a guide to the literature
Libraries Unlimited Westport CT 2006 ISBN 1-59158-160-5 Z5640.K56 QA78 Z6244
=SURVEY
A place for students to start a literature survey... where to look to find out what has been published on computing.

Knight09

Allan Knight
Facilitating the integration and impact measurement of technologies and media that augment learning environments
Thesis Defense CSci UCSB(Sep 8th 2009)
=THESIS WWW/NET EDUCATION TECHNOLOGY PEOPLE CULTURE DATA PERFORMANCE USER EVOLUTION
New devices, social media, and connectivity.
Turning up in classrooms. Opportunities or distractions in the classroom?
Stakeholders: teachers + students + researchers.
|-We can create computer systems that facilitate integration of the new into the learning as well as support research.
Four projects: DeCAF(event streams/producers/consumers), AutoCap(captioned audio), DataCafe(research data), PAIRwise(Plagiarism)
Lessons learned:
(DataCafe): relational database didn't scale. Flatter files fast enough. Interface difficult to use.
(PAIRwise): Evolved in purpose and implementation. Installation simplified. Initial version fragile.

KnightDai02

Alan Knight & Naci Dai
Objects and the Web
IEEE Software Magazine V19n2(Mar/Apr 2002)pp51-59
=DEMO Object-Oriented WEB/NET ARCHITECTURE PATTERN MVC
Proposes a modification of the model-view-controller architecture to web applications by introducing an application controller object connecting business objects to the input controller and view objects.

KnightMyers93

John C Knight & E Ann Myers
An Improved Inspection Technique
Comm ACM V36n11(Nov 1993)pp51-61
=EXPERIMENT SQA INSPECTION DEFECTS

Phase	Seeded	Found	Hours
3	12	24	9
4	10	31	13
5	7	8	5
6	12	32	21

Knuth69

Donald E Knuth
The Art of Computer Programming
Addison Wesley 1969-20??
=TEXT NONSEQUENTIAL DATA TECHNICAL MIX
Co-routines in section 1.4.5.2

Knuth74

Donald E Knuth
Structured Programming with GOTOs
Computer Surveys v5 n4 Dec 74 ( Republished in Yeh77 & Yourdon79 & Knuth92)
=HARMFUL REGULAR TECHNICAL

Knuth89

Donald E Knuth
The Errors of \TEX
Software - Practice and Experience
v19n7(Jul 1989)pp607-685 (republished in Knuth92)
=EXPERIENCES TECHNICAL QUALITY
Pay users to report errors. Increase value.

Knuth92

Donald E Knuth
Literate Programming
Center for Study of Lang. and Info. Stanford CA 1992 ISBN 0-9370-7389-6 CR9210-0746
=DEMO TECHNICAL LITERATE

Knuth98

Donald Knuth
The Art of Computer Programming (parts 1, 2, and 3)
Addison-Wesley 1998
=TEXT NONSEQUENTIAL DATA TECHNICAL MIX
[Knuth68]

KnuthBendix70

Donald E Knuth & P B Bendix
Simple word problems in Universal Algebras
J. Leech ed. Computational problems in Abstract algebra(pergamon Press Oxford 1970)pp263-297; reprinted in: Automation of Reasoning V2(Springer Berlin 1983)pp342-376
=MATHEMATICAL THEORY Knuth-Bendix ALGORITHM

Knuthetal89

Donald E. Knuth & Tracy Larrabee & Paul M Roberts
"Mathematical Writing"
The Mathematical Association of America: Notes n14 1989 ISBN 0-88385-063-X
=TEXT WRITING MATHEMATICS
[Knuth92]

KoMyers10

Andrew J Ko & Brad A Myers
Extracting and Answering Why and Why not questions about Java Program Output
ACM TOSEM Trans Software Eng & Methodology V20n2(JAug 2010)#4:1-36 [ 1824760.1824761 ]
=DEMO DEBUGGING IDE TOOL JAVA Whyline TRACE
When interrupted tool trace the path taken vs path not taken and generates lists of questions it can answer about the program. User can select a relevant question and see the part of the trace that explains what happened.
Questions like: why is the color of the line black?
Experiments show tool improved success rate and time vs traditional break-point debuggers.
Possibly derived from [KoMyersCoblenzAung06]

KoMyersCoblenzAung06

Andrew J Ko & Brad Myers & Micheal J Coblenz & Htet Htet Aung
An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks
ICSE'05 & IEEE Computer Magazine V39n12(Dec 2006)pp971-987
=EXPERIMENT SIMULATED MAINTENANCE INTERUPTIONS TECHNICAL Eclipse Java Swing Paint
Information_Foraging::=the BIBLIOGRAPHY(authors=>"P Pirolli &S K Card", title=>"Information Foraging", citation=>"Psychological Review V106n4 (1999)pp643-675").
Took video records of developers modifying and correcting bugs in apaint program.
Coded the actions into 9 types: Handling information(15%), reading code(12%), editing code, navigating dependencies, searching for names, testing, reading Java API, switching applications,reading task description(2%).
Early perceptions of bugs can lead to wasted time exploring irrelevant code.
Enhancements: developers had to search for a place to extend the existing framework and for examples to copy and modify.
Developers used "Find" dialog, Eclipse's multiple windows, What is relevant? When interupted developers always complete there current editting task before acknowledging the interuption, but sometimes forgot to save the edited file!
Three states: Search; Relate; Collect.
Need better ways to search for relevant code. Good names are vital! Perhaps use hovering to show header info on methods fro example.
Need less overhead in navigating and viewing code. EG highlight code to show dependencies of nearby code rather than menus.
Show many fragments of code in separate subwindows?
See [KoMyers10]

Kobryn99

Cris Kobryn [ ckobryn ]
UML 2001:A Standardization Odyssey
Commun ACM V42n10(Oct 1999)pp29-37, in [Booch99]
=HISTORY UML STANDARDS OMG ISO MOF XMI
4-layer metamodel
Revision Task Force [ http://uml.shl.com/ ]

Kobryn00

Chris Kobryn
Modeling components and frameworks with UML
Commun ACM V43n10(Oct 2000)pp31-38
=EXAMPLES UML COM EJB CORBA
UML components are not components in the Kobryn sense, yet(2000).

Kobryn00b

Chris Kobryn
UML Meets EJB and COM+
Software Development Magazine V8n12(Dec 2000)pp49-50+52+55
=ADVERT OMG UML 1.4 RTF COMPONENTS
Argues that UML does not allow component modeling in design diagrams and has too many ways to model EJB and COM+ components
p52. fig 3. shows a package with interface and implementation ( with fork symbol) and stereotype realization links. Realization is shown as a dependency inconsistent with UML1.3.

Kobryn01

Chris Kobryn
The road to UML2.0: Fast Track or Detour?
Software Development Magazine V9n4(Apr 2001)pp49-52
=REPORT STANDARD UML COMPONENTS EJB RTF
UML1.* winding down and u=UML2.0 ramping up for possible 2002 delivery.

Kobryn02

Chris Kobryn
Will UML 2.0 Be Agile or Awkward
Commun ACM V45n1(Jan 2002)pp107-110
=HISTORY UML 1.* =ESSAY on UML 2.0
Second system effect: [Brooks95]
UML2.0 will have 4 parts: infrastructure, superstructure, OCL, and Diagram Interchange
Resources [ uml ] [ http://www.uml-forum.com/ ] [ http://www.telelogic.com/publications/uml_models/ ]

KocherSchneier04

Paul Kocher & Bruce Schneier
Insider Risks in Elections
Commun ACM V47n7(Jul 2004)p104
=ESSAY VALUE ELECTION FRAUD RISK
Estimates amounts spent by candidates to get elected and so deduces the risk of insider fraud in election systems.

Kock00

Ned Kock
Benefits for virtual organizations from Distributed Groups
Commun ACM V43n11(Nov 2000)pp107-112
=EXPERIENCE 38 PROCESS IMPROVEMENT (PI) TEAMS NET BPR TQM
PI := conceptualPI; practicalPI.
conceptualPI :=identification; analysis; rededign.
practicalPI := implementation; routinization.
Brazil and New Zealand 1993-1996 conferencing messaging.
Iniative and leadership is bottom-up when incremental changes are made compared to face-to-face. radical change still needs high level leadership.
Messages are not just chat, they are part of the record.
Groups finish faster and meet more often than face-to-face.
Costs are reduced vs face-to-face.
Results are just as good if not better than face-to-face - you think more.

Kodaganallur04

Viswanathan Kodaganallur
Incoporating Language Processing into Java Applications: A JavaCC Tutorial
IEEE Software Magazine V21n4(Jul/Aug 2004)pp70-77
=TUTORIAL JavaCC GRAMMARS EBNF COMPILERS JAVA DDD
Assumes reader doesn't know EBNF etc. Presents an interpreter as a compiler. Ignorant of Jackson's methods.

Kogut95

Paul Kogut(kogut@vfi.paramax.com)
Design Reuse: Chemical Engineering vs. Software Engineering
ACM SIGSOFT Software Engineering Notes V20n5(Dec 1995)pp73-77
=ESSAY ENGINEERING REUSE DESIGN Figure 1 Design Knowledge Evolution Process
1. Design is mainly routine plus some innovation that evolves via a prototype to a fullscale implementation. Each design can produce some design knoledge that is captured & Organized & shared. Handbooks and published design diseminate the knowledge to the engineering community. Internally design knowledge becomes design standards for the product line in the organisation.
  Chemical engineers have Perry's Handbook: 100 authors, highlevel, principles and then guidelines. Not a textbook. Chemical engineers have a common language in mathematics and chemical formulae and graphical symbols for process flow charts. They have a shared ontology of objects problems and relations. Also licensable processes.
  Author recommends internal design standards plus (1) an online handbook on the internet, and (2) licensing for designs on the internet.

KohaviLongbotham07

Ron Kohavi & Roger Longbotham
Online Experiments: Lessons Learned
IEEE Computer Magazine V40n9(Sep 2007)pp103-105
=EXPERIENCE HOWTO WWW/NET EXPERIMENTAL FEATURE SELECTION
Good introduction to classic experimental design when used to evaluate features on web-based systems.
Details at [ hippo.aspx ]
Topics: control vs treatment, metric, randomisation, power, duration of test, analysis (EARLY)

KohEtAl07

Joon Koh & Young-Gul Kim & Brian Butler & Gee-Woo Bock
Encouraging Participation in Virtual Communities
Commun ACM V50n2(Feb 2007)pp69-73
=POLL USERS WEB/NET COMMUNITIES
Activity = Posting | Viewing.
Perceived usefulness improves viewing.
Offline interaction & quality of technology drives posting.
Larger communities have more posting and viewing.

Kohlhase06

Michael Kohlhase
OMDoc -- an open markup format for mathematical documents [ version 1.2 ]
Springer-Verlag NY Secausus NJ (Lecture notes in CS 4180) ISBN 3540378979 CR 0803-0261
=UNREAD =STANDARD MATHEMATICS FORMAL + INFORMAL THEORIES STATEMENTS FORMULAE

KokRuuten90

Joost N Kok & and Jan J Ruuten
Contractions in Comparing Concurrency semantics
Theoretical Comp Sci. V76n2&3(Nov 1990)pp179-222 CR 9108-0543
=THEORY MATHEMATICS SEMANTICS

Kokol87

Peter Kokol
Some Applications of Spreadsheet Programs in Software Engineering
ACM SIGSOFT Software Engineering Notes V12n3(Jul 1987)pp45-50
=DEMO TABULAR TOOLS (Visicalc) for COSTS (COCOMO) METRICs

KontioGettoLandes98

Jyrki Kontio & Gerhard Getto & Dieter Landes
Experiences in improving Risk management processes using the concepts of the Riskit method
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp163-174 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=DEMO RISKs
need to be both systematic and innovative+flexible in degree of detail

Koriem00

Samir M Koriem
A Fuzzy Petri Net Tool for Modeling and Verification of Knowledge-Bases Systems Computer Journal V43n3( 2000)pp206-223
=THEORY FUZZY PETRI KBS

Kornfeld82

William A Kornfeld
Combinatorial Implosive Algorithms
Commun ACM V25n10(Oct 1982)pp734-738
=THEORY OPTIMIZATION NONSEQUENTIAL

KorsonMcGregor90

Tim Korson & John D McGregor
Understanding Object-Oriented: A Unifying Paradigm
Commun ACM V33n9(Sep 1990)pp40-60
=ADVERT ERD STDs

KorsonVaishnavi92

Timothy D Korson<korson@cs.clemson.edu> & Vijay K Vaishnavi<ciskv@gsuvm1.gsu.edu>
Managing Emerging Software Technologies: A Technology Transer Framework
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp101-110
=THEORY MANAGEMENT TECHNIQUE

KoruTian04

A Gunes Koru & Jeff Tian
Defect Handling in Medium and Large Open Source Projects
IEEE Software Magazine V21n4(Jul/Aug 2004)pp54-61
=POLL 52 OPEN SOURCE DEFECTS
All projects keep a data base of defects and most use it for almost all defects.
The records tend to be complete and consistent.
Defects are recorded in source code, design documents, requirements documents. But KDE and Gnome are mainly source code defects.

KoruTian05

A Gunes Koru & Jeff (Jianhui) Tian
Comparing High-change modules and modules with the highest measurement values in two large-scale Open-Source Products
IEEE Trans Software Engineering V31n8(Aug 2005)pp625-642
=EXPERIENCE MINING OPEN SOURCE Mozilla OpenOffice EVOLUTION MODULES METRICS size cohesion coupling inheritance
Modules that have the most changes are not those with the worst metrics!
High change modules were not quite the highest.
Used Tree based models to correlate metrics and changeability.
Anecdotal: tough problems have highest measures but get the best programmers.
Open source projects are a good source of software engineering data.
Appendix describes the processes in Mozilla and OpenOffice.

KoruZhangEmamLiu09

A Guneg Koru & Dongsong Zhang & Khaled El Emam & Hongfang Liu
An Investigation into the Functional Form of the size-defect relationship for software modules
IEEE Trans Sofware Engineering V35n2(Mar/Apr 2009)p293-304
=EMPIRICAL STATISTICS OPEN SOURCE LOGS DEFECTS MODULE SIZE Cox
Problems with conventional analysis -- deleted modules, size changes, ...
Proposes and fits Cox proportional hazards models to CVS data from Mozilla, Cn3d, JBoss, and Eclipse
Discovers more changes are made to small modules than might be expected.

KoruEmam10

A Gunes Koru & Khaled El Emam
The Theory of Relative Dependency: Higher Coupling concentration in Smaller Models
IEEE Software Magazine V27n2(Mar/Apr 2010)pp81-89
=EMPIRICAL STATISTICS KDE Linux METRICS SIZE LoC COUPLING DIT CBO CONCENTRATION CURVE and INDEX
Measured dependencies between classes -- inheritance and couplings.
Number of dependencies is not proportional to size (LoC).
You are more likely to find a line that is dependent when the class has fewer lines of code.
Measures the effect of refactoring in one project -- makes classes smaller.
(dick)|-a small class has to be coupled to other classes to do anything useful.
Compare [KoruZhangEmamLiu09]

KotonyaLockeMariani11

Gerald Kotonya & Simon Locke & John Mariani
Scrapheap software development
IEEE Software Magazine V27n6(Mar/Apr 2011)pp68-74
=EXPERIMENT REUSE DEAD PROJECTS
Junk yard wars
Resources: bits of abandoned hardware and software, Not re-engineered but lots of glue (& duck tape), The Teams Knowledge, ...
Observations: bottom up development, experts become champions, efficiency is sacrificed, ..
Control Structures/Glue: scripts, pipes, exec calls, sockets, clipboards, ...
Advice
1. Consider all a components properties
2. Access to detailed knowledge about components is eseentail
3. Project knowledge is vital
4. What control structures/glue
5. How complex is the data translation to connect A to B
6. When was this component scrapped?
7. Why was this component scrapped?
8. Don't ignore residual functionality
9. Reflect on overall dependability

Kotov99

Alex Kotov
The Internet as a Medium for Software Engineering Experiments
ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp722-723
=ADVERT Doctoral thesis: how to increase sample sizes and representativeness to overcome noisy data.

Kotula98

Jeffey Kotula
Using Patterns to Create Component Documentation
IEEE Software Magazine V15n2(Mar/Apr 1998)pp84-92
=DEMO PATTERNS for TECHNICAL DOCUMENTATION
Catalog on pp90-91

Kotze98

Paula Kotz'e
Why the Hypermedia Model is inadequate for Computer-Based Instruction
ACM SICSE Conf Proc 6th Annual Conf on the Teching of Computing SIGCSE Bulletin V30n3(Sep 1998)pp148-152
=THEORY FORMAL Z WWw

KoutsofiosNorth92

Eleftherios Koutsofios & Stephen C North
Drawing graphs with dot
Tech Rep (available from AT&T Bell Labs Murray Hill NJ) 1992 [Gansneretal93]
=MANUAL GRAPHIC TOOL

KovedShneiderman86

Larry Koved & Ben Shneiderman
Embedded Menus: selecting Items by Context
Commun ACM V29n4(Apr 1986)pp312-318
=DEMO TIES touchtext USER HYPERTEXT-like viewing and selection are linked not separated

Kovitz99

Benjamin L Kovitz
Practical Software Requirements: A Manual of Content an Style
Manning Pub Co Greenwich CT 1999 ISBN 1-884777-59-7 CR99050314 also reviewed www.sdmagazine.com August 1999
=HOWTO REQUIREMENTS

Kowalik06

Janusz Kowalik
The applied mathematics and computer science schism
IEEE Computer Magazine V39n3(Mar 2006)pp104+102-103
=ESSAY EDUCATION COMPUTING vs MATHEMATICS
Computer scientists miss lots of good algorithms if they don't do applied mathematics.
Applied mathematicians miss lots of tools and technology if they don't study computer science.
Studying mathematics helps one to be a more rigorous thinker.
(dick)|-what do you mean by "rigorous thinker"?

Kowalski79

Robert Kowalski
Algorithm=Logic+Control
Commun ACM V22n7(Jul 1979)pp424-436
=DEMO logic-programming non-sequential prolog optimization

Kowalski79b

Robert Kowalski
Logic for Problem solving
Elsevier Science NY NY 1979 1983 ISBN 0-444-00365-7 QA76.K68
=TEXT LOGIC FORMAL PROLOG THINKING

Kozaczynski91

Wojtek Kozaczynski
A Suzuki Class in Software Re-engineering
IEEE Software v6n1(Jan 1991)pp97-98
=DEMO REENGINEERING

KraemerDedrickSharma09

Kenneth L Kraemer & Jason Dedrick & Prakul Sharma
One Laptop Per Child: Vision vs. Reality
Commun ACM V52n6(June 2009)pp66-73 [ 151646.1516063 ]
=EXPERIENCE TECHNOLOGY CULTURE SYSTEMS ECONOMICS EDUCATION MARKET
OLPC::acronym="One Laptop Per Child".
Project attempted to change the worlds educational system by giving cheap robust laptops to all children.
Teachers don't accept the new learning plan.
Lack of political will and diffusion of goals -- computers are abandoned in classrooms with no training....
Inspired existing companies to develop rival netbook Computers.
Good technical solution fails to meet objectives because of cultural mismatch.

Krakovsky11

Marina Krakovsky
Deus Ex Machina
Commun ACM V54n5(May 2011)p22 [ 1941487.1941496 ]
=ARTICLE PROOF ONTOLOGICAL EXISTENCE GOD PROVER9 LOGIC PROVER9
Authors Paul Oppenheimer and Edward Zalta: "A Computationally-Discovered Simplification of the Ontological Argument". Australasian Journal of Philosophy 89 (2): 333-349. 2011.
Details [ http://mally.stanford.edu/cm/ontological-argument/ ]
More at [ download?doi=10.1.1.151.7483&rep=rep&type=pdf ] (PDF).

Kramer93

Mitch Kramer(Sudbury Mass.)
Large App Development: A Job for OO A&D Tools(article)
Software Magazine Jan 1994 pp39-49
=DEMO Objects Analysis Design Code

KramerKaindl04

Stefan Kramer & Hermann Kaindl
Coupling and cohesion metrics for knowledge-based systems using frames and rules
ACM TOSEM Trans Software Eng & Methodology V13n3(Jul 2004)pp332-358
=IDEA METRIC RULES FRAMES GRAPH THEORY
Developers found tool using metrics helpful.
does not measure coupling between two frames but the average coupling with all other frames.

KramerLuqiBerzins93

Bernd Kramer & Luqi & Valdis Berzins
Compositional Semantics of a Real-Time Prototyping Language
IEEE Trans SE-V19n5(May 1993)pp453-477
=THEORY PSDL Specifications DFDs Petrie Nets Algebraic

KramerMaggeNg89

J Kramer & J Magee & K Ng
Graphical Configuration Programming
IEEE Computer v22 n10 (Oct 1989) pp53-65
=DEMO GRAPHIC OBJECT-ORIENTED NONSEQUENTIAL REALITY

KramerNoronhaVergo00

Joseph Kramer & Sunil Noronha & John Vergo
A User-centered design approach to personalization
Commun ACM V43n8(Aug 2000)pp45-48
=ESSAY USER > TOOLS
UCD:="User-Centered Design"

KramerWolf96

Jeff Kramer & Alexander L Wolf
Succeedings of the 8th International Workshop on Software Specification and Design
ACM SIGSOFT Software Engineering Notes V21n5(Sep 1996)pp21-35
=CASESTUDIES REQUIREMENTS SPECIFICATION
The London Ambulance System case study: need for QUALITIES + MAJackson's notions pointed up problems + modeling of environment><system
Daniel Jackson's group used sets in place of predicates

Krasneretal92

Herb Krasner & Jim Terrel & Adam Linehan & Paul Arnold & William H Ett
Lessons Learned from a Software Process Modeling System (SPMS)
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp91-100
=EXPERIENCE PROCESS MODEL CASE

KrautStreeter95

Robert E. Kraut<robert.kraut@cmu.edu> & Lynn A Streeter <lstreet@advtech.uswest.com>
Coordination in Software Development
Commun ACM V38n3(Mar 1995)pp69-81
=EXPERIENCES POLL LARGE PROJECTS AGILE
No single cause
Coordination problems increase as project size and uncertainty increase
Communication problems are very common [ KrautStreeter95.html ]
Provides evidence for agile values before the agile manifesto.

Krieg-BrukenerLuckman80

Bernd Krieg-Bruckner & David C Luckham
ANNA: towards a language for annotating Ada programs
Proceedings of the ACM-SIGPLAN symposium on Ada programming language 1980 pages 128-138 [ citation.cfm?id=948650 ]
=IDEA ADA PROOF ANNOTATION Floyd INVARIANT ASSERTION

Krick69

E V Krick
An Introduction to Engineering and Engineering Design (2nd Edn)
John Wiley&Sons NY 1969
=TEXT ENGINEERING

Krill06

Paul Krill
Agile programming has fallen short, conference told
Infoworld(13 Mar 2006) [ 76420_HNmcconnell_1.html ]
=REPORT McConnell BEST & WORST IDEAS Agile RISKS REQUIREMENTS ITERATION INCREMENTAL EVOLUTION REUSE ONESIZE
Importance of people, evolution, risk, estimation, management,...
One size does not fit all: different projects need different processes
Next [Krill10]

Krill10

Paul Krill
Agile programming 10 years on: Did it deliver?
Infoworld(Nov 2 2010) [ agile-programming-10-years-did-it-deliver-761 ]
=INTERVIEWS AGILE EXPERIENCE XP Scrum LEAN PROCESSES Kanban RUP DSDM
Agile depends on professional programming. It is no silver bullet.
Agile opened up this debate: is it better to document the requirement or to implement an approximation and iterate towards what is actually needed?
Compare [Krill06] "Agile programming has fallen short..."

KrishnamurthiFelleisen98

Shiram Krishnamuthi & Matthias Felleisen
Toward a Formal Theory of Extensible Software
ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp88-98 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
=THEORY extension of repertoires of programs
comparison of cut-and-paste extensions vs using the [GoF] Interpreter pattern
Advertise and adhere to interfaces.

KrishnamurthiFisler07

Shriram Krishnamurthi & Kathi Fisler
Foundations of Incremental Aspect model-checking
ACM TOSEM Trans Software Eng & Methodology V16n2(Apr 2007)pp1-39
=THEORY ASPECT MODULES EVOLUTION FSM CTL MODAL LOGIC
Models code as finite state machines with special (paired) transitions for entering and leaving subprograms.
Aspects are modeled as finite state machines that are place in before/after/arround the special transitions.
Aspects placed using regular expression on the state of the stack of calls.
CTL modal operators used to state required properties.

KrishnamurthyRoliaXu11

Diwaka Krishnamurthy & Jerry Rolia & Min Xu
WAM -- The weighted Average Method for predicting the performance of systems with bursts of customer sessions
IEEE Trans Software Engineering V37n5(Sep/Oct 2011)pp716-735
=DEMO PERFORMANCE QUEUING QNM MARKOV PROBABILITY STOCHASTIC SYSTEMS
WAM::="Weighted Average Method", predicts performance of a typical web-base system, By simulating a load and calculating mean rate of response with different numbers of active sessions.
Assumes that distribution at a given time is estimated by the distribution across time.
Results fit well.

KrishnanKellner99

M S Krishnan & Marc I Kellner
Measuring Process Consistency: Implications for Reducing Software Defects
IEEE Trans Software Engineering V25n6(Nov/Dec 1999)pp800-815
=EMPIRICAL IMPROVEMENT DEFECTS VS CMM KPA C
45 systems software projects in one company
small projects, highly capable people, and attention to CMM Key Process areas lead to fewer defects
Defects were repeatable customer problems in first 24 months after release

KrishnanLiSteler92

Ramayya Krishnan & Xiaoping Li & David Steler
A Knowledge-Based Mathematical Model Formulation System
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp138-146
=TOOL MATHEMATICAL MODEL KNOWLEDGE

Kristensen02

Jan Kristensen
Evolutionary Information Systems: Maintaining consistency when structural transformations force integrity rules to break
[SCI2002] V1(Jul 2002)pp
=EXPERIENCE EVOLUTION DATA MODEL
Since it is common that optimal data designs break after a long time,one should deliberately loosen up data base designs to handle changes.

KrizSandmayer80

? Kriz & ? Sandmayer
Extension of Pascal by Coroutines & its application to quasiparallel programming & simulation
Software Practice & Experience 10 p373-398
=IDEA non-sequential PASCAL

Krob91

Daniel Krob
Complete systems of \B-rational Identities
Theor Comput Sci 1989n2(Oct 28 1991)pp207-343 CR9304-0240
=THEORY
Completeness of some of Conway's Calculi

KrollKruchten05

Per Kroll & Phillippe Kruchten
The Rational Unified Process made easy: a practitioner's Guide to the RUP
Addison-Wesley 2003 ISBN 0321166094 QA67.76 D47K75
=HOWTO =ADVERT RUP PROCESS TOOLS TEMPLATES METHODS PEOPLE ONE-SIZE
The Spirit of RUP::=following,
- Attack major risks early and continuously or they will attack you.
- Ensure you deliver value to your customer.
- Stay focused on executable software.
- Accommodate change early in the project.
- Baseline an executable architecture early on.
- Build your system with components.
- Work together as one team (not annalists versus developers vs testers)(make architecture central).
- Make quality a way of life, not an after thought.
Gives examples of small,....large projects.

Krug00

Steve Krug
Don't Make me Think: A Common sense approach to web usability
New Riders 2000 TK5105.888 K78 ISBN 0-7897-2310-7
=GUIDE USER HCI WWW/NET PEOPLE TEAMS
"Advanced Common Sense"
Expert usability review != usability testing
(1) self evident | (2) self explanatory
Users scan pages, they don't read them. We guess. We muddle through.
Visual hierarchy and logic. Conventions. Break up into areas. Make clickabilty obvious. Minimize noise.
Omit words! Instructions and happy talk.
ask(search) or browse?
navigation info: site id, utilities( a way home, a way to search,...), contents(with drop down secondary navigation)
Page names on all pages, and match link text that refs them.
bread crumbs: You are here X>Y>Z>...
Tab dividers. Drawn right and front tab clearly in front.
home pages: all the above + tag line + ...+where to start
design team problems: wars of religion -> resolve by testing the particular case
How to do usability tests.....

Krueger92

Charles W Krueger
Software reuse
Computing Surveys V24n2(Jun 1992)pp131-184
=survey reuse

Krutchen95

Phillipe B Krutchen(Rational Software pjrutchen@rational.com)
The 4+1 View Model of Architecture
IEEE Software Magazine(Nov 1995)pp42-50
=ADVERT SCENARIOS METHOD
logical+process+physical+development centered on Scenarios
each view uses Elements+forms+rationale/constraints

Krutchen03

Phillippe Krutchen
The Rational Unified Process: an Introduction
Addison-Wesley Longman Boston MA 2003 ISBN 0321197704 CR 0411-1339
=UNREAD RUP PROCESS UML

Krutchen05

Philippe Krutchen
Casting software design in the Function-Behavior-Structure framework
IEEE Software Magazine V22n2(Mar/Apr 2005)pp52-58
=IDEA ENGINEERING Gero PROCESS WATERFALL RUP FBS
FBS::= following
Net
1. F:set(function).
2. S:structure.
3. Be: set(behavior), expected.
4. Bs: set(behavior), actual.
5. D:description.
6. formulation:F->Be.
7. synthesis:Be->S.
8. analysis:S->Bs.
9. evaluation:(Be,Bs)->acceptability.
10. documentation:S->D.
11. structural formulation:S->S.
12. behavioral formulation:S->Be.
13. functional formulation:S->F.
(End of Net)
Author maps above into RUP.
Software_engineering = SWEBOK.software_design+ requirements + coding + testing.
Formulating the problem is part of engineering design.
Lack of techniques for analyzing the behavior of structures, other than testing.
A piece of software is less expensive to change than a bridge. Hence, software developers can afford more reformulation on the way to an acceptable product.
Legacy systems: D to S to Be to F...
COTS: F to Be to S.
Patterns?
SwEng words mean different things to other engineers.

Kruchten08

Philipe Kruchten
The Biological Half-life of Software Engineering Ideas
IEEE Software Magazine V25n5(Sep/Oct 2008)pp10-11
=SURVEY IDEAS 1988..2008
Half_life(C)::=The time taken before 50% of a chemical C is removed from a body, example: Half_life(caffeine) =~= 3.5.hrs.
Out of 50 items in IEEE Software from 1988 no more than 3 are still important.
This implies a Half_life of about 5.years.
Professional organizations enforce continuing professional development.
More important to learn how to learn than learn the language/system of the day.
(dick)|-Compare the half life used to model radioactive decay.
(dick)|-Suggests exponential decay:
amount (t) = amount (t0) * 2 ** ((t0-t)/ half_life) ).
(dick)|-Which ideas are strong enough to survive?

Kruchten09

Philippe Kruchten
When Robert Rules
IEEE Software Magazine V26n1(Jan/Feb 2009)pp20-21
=PRINCIPLES MEETINGS GROUPS PEOPLE MANAGEMENT PROCESS
Source [ Robert%27s_Rules_of_Order ] (Henry M Robert, 1837-1923)
Principles
1. Scope the meeting: agreed and prioritized objectives.
2. Tackle one issue at a time. Focus on pro and con of one proposed idea.
3. Get Closure on issues. An agreed conclusion. (1) evolves (2) Ratified.
4. Be flexible. A way to modify a proposal.
5. Know when to stop or defer a decision.
6. Remember what was decided. Minutes or other artifacts.
7. Know how to undo a decision. Rescind.
8. Dealing with difficult situations. Need chair/facilitator. Points of order. Politeness, Address the topic not the people.

Kruchten09a

Phillippe Kruchten
You are what you read
IEEE Software Magazine V26n2(Mar/Apr 2009)pp10-11
=ESSAY READING RETAINING HOWTO
Software development knowledge has a half-life of about 5 years -- 50% of today's knowledge will not needed in 5 years time.
Value of reading -- not just Googling on the fly. Set aside time to read web, journals, and books of interest.
Value of writing reviews.
Need to take note and store the notes. Keep copies on hard-drive. Use file naming conventions.
Track where important books have been loaned. Prominent Labels.

Kugel05

Peter Kugel
It's time to think outside the computational box
Commun ACM V48n11(Nov 2005)pp33-37
=ESSAY PROGRAMMING BY EXAMPLE COMPUTE IN THE LIMIT
Allowing programs to be wrong a finite number of times before being correct allows them to (in the limit) produce the program that fits all the given examples.
(dick): most software development works like this anyway: testing, beta, alpha, ...

Kuhn97

D Richard Kuhn
Sources of Failure in the Public Switched Telephone Network
IEEE Computer Magazine V30n4(Apr 1997)pp31-36
=EXPERIENCE RISKS

KuhnWallaceGallo04

D Richard Kuhn & Dolores R Wallace & Albert M Gallo
Software fault Interactions and Implications for Software Testing
IEEE Trans Software Engineering V30n6(Jun 2004)pp418-421
=Theory TESTING DEBUGGING
Most bugs are dependent on only a few (1..6) parameters having special combinations of values.

KuichSalomaa86

W Kuich & A Salomaa
Semirings Automata Languages
Springer Verlag EATCS monographs Vol 51985
=THEORY LANGUAGE TOPOLOGY

KulakGuiney00

Daryl Kulak & Eamon Guiney
Use Cases: Requirements in Context
Addison-Wesley/ACM Press 2000 ISBN 0-201-65767-8 review SIGSOFT SEN V26n1 p101 lib congress: QA76.9 S88 K85 2000 CR0301-0016
=MANUAL REQUIREMENTS PURPOSES USECASES QUALITIES REALITY SCENARIOS UML TEAMS MANAGEMENT CASESTUDIES
Comprehensive and claimed experience-based description of how and why to use use cases to develop requirements. Including a sequence of iterative phases: (facade, filled, focused, finished) and common mistakes.
Describes many templates and filters to be used as tools.
Use_Case_template::=Net{ name, iteration, summary, basic_course_of_events, alternative_paths, exception_paths, extension_points, triggers, assumptions, preconditions, postconditions, related_business_rules, author, date: text}.
Usecases are good for inquiry-only systems, Raps, evaluating packages, and for non-object-oriented systems.

KulkarniReddy03

Vinay Kulkarni & Sreedhar Reddy
Separation of Concerns in Model-Driven Development
IEEE Software Magazine V20n5(Sep/Oct 2003)pp64-69
=DEMO METAMODEL TEMPLATE UML OCL
Layered architecture implies many similar transformations.
The Template meta-model can be instantiate to fit them all, including code generation of GUIs, functions, and databases.
MetaModel

KuncakLamZeeRinard06

Victor Kuncak & Patrick Lam & Karen Zee & Martin C Rinard
Modular Pluggable Analysis for Data Structure Consistency
IEEE Computer Magazine V39n12(Dec 2006)pp988-1005
=DEMO TOOL Hob MODULAR PROVING REALITY SETS RELATIONS ABSTRACTION PALE Bohn Isabelle flag ADTs Minesweeper httpd etc
Shows that the theories of ADTs from the 80s are the basis for a set of tools.
Modules have three parts: implementation, specification, and abstraction.
The code inside modules is proved to support certain assertions expressed in the language of set theory. The abstraction section defines higher level formulas using sets and the calculus of relations -- like Alloy.
Programs are proved using the higher-level properties.
Page 989. "One somewhat unusual feature of these abstract properties is that are outward looking: the capture important features of the system that are directly meaning ful to the users.

Kung89

C H Kung
Conceptual Modeling in the Context of Software Development
IEEE Trans Soft Eng vSE-15 n10(Oct 1989)pp1176-1187
=DEMO data ERD DFDs logic Petrie nets System

KunkleCooperman08

Daniel Kunkle & Gene Cooperman
Solving Rubik's Cube: Disk is the New RAM
Commun ACM V51n4(Apr 2008)pp31-33
=DEMO CLUSTER DISK PERFORMANCE QUALITIES BANDWIDTH LATENCY
Many disks give the same bandwidth as RAM when accessed by many CPUs.
But must avoid random access to disk. Use disk sorts + collation + RAM caches instead.

KuoKarimi88

F-Y Kuo & J Karimi
User Interface Design from a Real Time Perspective
Commun ACM V31n12(Dec 1988)pp1456-1466
=DEMO DFD STD USER

KupermanEtal05

Benjamin A Kuperman & Carla E Brodley & Hilmi Ozdoganoglu & T N Viyakuma & AnkitJalote
Detection and prevention of stack buffer overflow attacks
Commun ACM V48n11(Nov 2005)pp51-56
=REPORT TECHNICAL RISK ERROR STACK CODE V&V TOOLS
Concludes that training and review is one of the more effective techniques for getting rid of code that can be exploited. Bit code review is not perfect.
There are tools to spot potential security violations: ITS4, RATS, LCLint.
Dynamic protection (eg modify compiler to do bounds checking) can be costly but hardware may evolve to spot attacks fast.

KuperVardi93

Gabriel M Kuper & Moshe Y Vardi
The Logical Data Model (LDM)
ACM Trans Database Syst v18n3(Sep 1993)pp379-413 CR9407-0472
=THEORY DATA
theory for LDM
OO data model that generalizes the relational hierarchical and network
review of 7 other attempts
none provide both conceptual data and a well defined retrieval mechanism/query language
defines a DB schema as a digraph. leaves are dta, internal nodes are connections from objects with separate names and values.
sect 2 intro, sectn 3 math defs, sectn 4 logic og LDM, sectn 5 & 6 query languages
Strong theoretical foundation for future DBMSs

Kurki-Suonio94

Reino Kurki-Suonio<rks@cs.tut.fi>
Real-Time: Further Misconceptions (or Half-Truths)
IEEE Computer Magazine V27n6(Jun 1994)pp71-76
=ESSAY REAL TIME

Kurtz91

Barry L Kurtz
Laboratory Activities for Studying the Formal Semantics of Programming Languages
SIGCSE Bulletin v23N1(mAR 1991)PP162-168

Kurtzetal91

Barry L Kurtz & Richard L Oliver & Edward M Collins
The Design, Implementation, and Use of DSTutor: A Tutoring System For Denotational Semantics
SIGCSE Bulletin V23n1(Mar 1991)pp169-177
=EXPERIENCE PEDAGOGY DENOTATION SEMANTICS TOOL EQUATIONS
"Writing the semantics equation [...] is an important part of the learning process; however because of the symbolic notation of the denotational formalism this would be difficult using keyboard input[Hidden multiple choices] seemed to be a viable alternative to some laborious mechanism allowing students to type in the bugged semantic equation"

KwonAgha11

YoungMin Kwon & Gul Agha
Verifying the evolution of probability distributions governed by a DTMC
IEEE Trans Software Engineering V37n1(Jan/Fed 2011)pp126-141
=THEORY DEMO TOOL MODAL LOGIC MODEL CHECKING iLTL MARKOV DISCRETE TIME BUCHI
Model has both probabilities and qualities on transitions and so expected value on paths. Probabillitues and qualities used to give modes in the logic.

Kyng95

Morten Kyng
Making Representations Work
Commun ACM V38n2(Sep 1995)pp46-55
=EXPERIENCE USER PROTOTYPING REQUIREMENTS LOWTECH MOCKUP
Note External design
How to make images and models on the screen work to help the USER via low-tech and medium tech prototyping and USER involvement

Lachheb04

Tawfik Lachheb
A secure client/server java application programming interface
CSUSB CSCI Project 2004 QA76.9 .A25 L334 2004 OVERSIZE
=DEMO SECURITY CLIENT/SERVER WEB/NET Java ENCRYPTION
Proposes a transitive model of trust.

Ladas08

Corey Ladas
Scrumban - essays on kanban systems for lean system development
Modus operandi. 2008
=UNREAD =HANDBOOK LEAN KANBAN
sample? [ http://leansoftwareengineering.com/ksse/scrum-ban/ ] Scrumban.
Kanban::wikipedia= See http://en.wikipedia.org/wiki/Kanban.

LaddagaVeitch97

Robert Laddaga & James Veitch
Dynamic Object Technology
Comm ACM V40n5(May 1997)p37-38
=EXPERIENCE COST ECONOMIC
cost proportional to change by <polysyllabic> <buzz phrase>...

LaddRamming96

David A Ladd(ladd@research.att.com) & J Christopher Ramming(jcr@research.att.com)
A*: A Language for Implementing Language Processors
IEEE Trans Soft Eng VSE-21n11(Nov 1995)pp894-901
=EXPERIENCES DEMO BNF DDD well written
experimental extension of awk to be a compiler-interpreter

LafontaneLedruSchobbens91

Christine Lafontane & Yves Ledru & Pierre-Yves Schobbens
An Experiment in Formal Software Development: Using the B Theorem Prover on a VDM case Study
Commun ACM V45n5(May 1991)pp62-ff
=EXPERIMENT FORMAL VDM LOGIC
Review: CR 9204-0229

Lahman11

HS Lahman
Model-Based Development: applications
Addison-Wesley Pearson Boston MA (2011) ISBN 0-321-77407-8
=ADVERT HISTORY METHODS MODEL-BASED SHLAER-MELLOR DAD INVARIANTS OOA OOD OOP BAL Turing Blitz reviews
Disclaimer: I was sent a free copy of this book.
Chatty style and a strong method.
Detailed description of using domain plus executable models leads the development of maintainable software.
Strong on Class models and State machines but weak on use cases, quality requirements, the UML, and scenarios.
UML nit picks:
1. Figure 10-15 on p268: The association class C is not connected to the association by a dashed line. The reification has the wring multiplicities. Reifying C: A(*)-(*)B gives A(1)-(*)C(*)-(1)B.
2. Figure 15-9 0n page 404: is described as a state machine but is described as having activity diagram semantics.

Lai08

Charlie Lai
Java Insecurity: Accounting for subtleties that can compromise code
IEEE Software Magazine V25n1(Jan/Feb 2008)pp13-19
=DEMO TECHNICAL Java SECURITY
Example of sompromisable singleton pattern.

LaiHuang03

Richard Lai & Sun-Jen Huang
A Model for Estimating the size of a Formal communication Specification and its implementation
IEEE Trans Software Engineering V29n1(Jan 2003)pp46-62
=STATISTICS ESTELLE C ESTIMATION SIZE LOC 14 PROTOCOLS FSM
Specs vary from 225..8738 lines, implementation1899..37531lines.

Laird01

Cameron Laird
GUI construction with Perl
Dr. Dobbs #320(Jan 2001)pp80+82+84+86
=ADVERT Perl/Tk LANGUAGE MODULE TOOLKIT HCI

LaitenbergerEmamHarbitch01

Oliver Laitenberger & Khaled El Emam & Thomas G Harbitch
An Internally Replicated Quasi-experimental Comparison of checklist and Perspective Based Reading of Code Documents
IEEE Trans Software Engineering V27n5(May 2001)pp387-421
=EMPIRICAL SQA TECHNICAL INSPECTIONS COSTS Bosch Telecom.
PBR:= "Perspective based reading", a particular way of reading a piece of code based on a specific stake-holders point-of-view.
PBR_scenario::document = introduction # Instructions #question.
Theory: Specific focus gives less overlap and better reading.
Perspectives give more effective defect finding at a lower cost per defect than check-lists.

Laitinen96

Kari Laitinen
Estimating Understandability of Sofware Documents
ACM SIGSOFT Software Engineering Notes V21n4(Jul 1996)pp81-92
=TOOL CODE VOCABULARY STATISTICS
confuses vocabulary with language and uses size of vocabulary in document to measure understandability
shows that natural identifiers lead to a smaller vocabulary

LaitinenFayadWard00

Mauri Laitinen & Mohamed E Fayad & Robert P Ward
The Problem with Scalability
Commun ACM V43n9(Sep 2000)pp105-107
=ESSAY PROCESSES ONE-SIZE ECONOMICS
Not easy to change standard software engineering practice to work economically with small teams and projects. either some roles or procedures must be abandoned or some people have too many roles to play.

Lakatos76

Imre Lakatos (edited by John Worral and Elie Zahar)
Proofs and Refutations
Cambridge University Press 1976
=PHILOSOPHY MATHEMATICS PROOFS SOCIAL PROCESS
Describes an advanced seminar in mathematics where the students duplicate the key points in the history of a particularly elegant theorem in the theory of polyhedra.
He makes it clear that proofs are often refuted. Mathematics grows by a process of proof, refutation, and reproof.
The exception improves the rule more often than not.
The author wanted to decrease the dogmatism of mathematics, and in particular the dogma that mathematical knowledge grows by deducing truth from known truths.
He shows that actual mathematics develops in an illogical fashion because it grows by discovering the underlying assumptions as well as by working from these to prove conclusions.
The end result of years of exploration is an axiomatic structure like Euclid. But this structure is not how the field developed.
Lakatos tabulates specific ways of tackling facts that don't fit the theorem and its (putative) proof.
See [DeMilloLiptonPerlis79]

LamDingLiu08

Tak Cheung Lam & Jianxun Jason Ding & Jyh-Charn Liu
XML Document parsing
IEEE Computer Magazine V41n9(Sep 2008)pp30-37
=THEORY XML PARSING PERFORMANCE DOM SAX StAX VTD
Different parsing tools/models perform best on different tasks.
Sample: DOM good for data bases and SAX & StAX for streaming. VTD will need special hardware to perform quickly.

Lamb90

David Alex Lamb
Specification of Iterators
IEEE Trans SE-16 n12(Dec 1990)pp1352-1360 & correction IEEE Trans SE-17n9(Sep 1991)p982
=THEORY TECHNICAL SPECIFICATION ITERATORS

Lamb00

Charles Lamb
Jini: Net Intelligance at Your Command
Software Development V8n2(Feb 2000)pp30-35
=ADVERT JAVA JINI WWW/NET TECHNICAL RMI TRANSACTIONS Proxy objects
Extends polymorphism to allow an object to behave according to a remote class definition.

LamMcDermid97

W Lam & J A McDermid
A Summary of Domain Analysis Experience by way of Heuristics
[Harandi97] pp54-64
=EXPERIENCE REQUIREMENTS REUSE
unclear idea of a domain is: problem or solution?

LammelVerhoef01

Ralf Lammel & Chris Verhoef (free University of Amsterdam)
Cracking the 500-Language Problem
IEEE Software Magazine V18n6(Nov/Dec 2001)pp78-88
=EXPERIENCE GRAMMAR NF LRM LANGUAGES TOOLS
Value of grammars in writing tools.
Can rapidly (2 weeks) steal a grammar from 1: compiler code, 2: compiler BNF, 3: LRM rules, 4: RM examples
Only RPG did not provide syntax rules in its LRM.

Lammers86

Susan Lammers
Programmers at work(1st series)
Microsoft Press WA USA
=POLL TECHNICAL

Lammers89

Susan Lammers
Programmers at Work: Interviews With 19 Programmers Who Shaped the Computer Industry
Tempus Books 1989 ISBN 1556152116 [ 1556152116 ]
=UNREAD =INTERVIEWS PROGRAMMERS PEOPLE CODING TECHNICAL
Parts online at [ http://programmersatwork.wordpress.com/ ]
Please send me your comments [ contribute.html ] to see them here.

Lamport86a

Leslie Lamport
Control Predicates are Better than Dummy Variables for Reasoning About Program Control
Report 11 Systems Research Center Digital Equipment Corpn May 5th 1986
=THEORY NONSEQUENTIAL FORMAL

Lamport86b

Leslie Lamport
A Simple Approach To Specifying Concurrent Systems
Report 15 Systems Research Center Digital Equipment Corpn Dec 25th 1986
=THEORY non-sequential formal specification

Lamport87

Leslie Lamport
win and sin: Predicate Transformers for Concurrency
Report 17 Systems Research Center Digital Equipment Corpn May 1st 1987
=THEORY non-sequential formal

Lamport90a

Leslie Lamport
A Temporal Logic of Actions(TLA)
Report 57 from Systems Research Center Digital Equipment Corpn(1st Apr 1990) & Revised as Lamport91
=MATHEMATICAL non-sequential formal dynamic modal logic

Lamport91

Leslie Lamport
The Temporal Logic of Actions(TLA)
Report 79 from Systems Research Center Digital Equipment Corpn(25th Dec 1991)
=MATHEMATICAL non-sequential formal dynamic modal logic
Revision of Lamport90b

Lamport94b

Leslie Lamport
Processes are in the Eye of the Beholder
Report #132 from Systems Research Center Digital Equipment Corpn(25th Dec 1994)
=THEORY NONSEQUENTIAL LOGIC

Lamport94b

Leslie Lamport
Unknown
ACM TOPLAS (May 1994)pp872-923
=MATHEMATICAL non-sequential formal dynamic modal logic
Cannonical version of Lamport91 TLA Temporal Logic of Actions.

Lamport95

Leslie Lamport<lamport@src.dec.com>
How to Write a Proof
American Math Monthly V102n7(Aug-Sep 1995)pp600-608

=DEMO PROOFS FORMAL LOGIC

Q.E.D. is a step representing what needs to be proved:

 Theorem <statement>

 PROOF SKETCH: <english style proof scetch>

 ASSUME: <label>. <predicate> ...

 PROVE: <predicate>

 NumberedList( <number>. <step|predicate> )

   <number>. Q.E.D.

 LET: <definitions>

 Choose .... such that....

 CASE: statement of assumption

 ASSUME: Statemnt of assumption

 PROVE: Q.E.D.

Lamport95a

Leslie Lamport
TLA in Pictures
IEEE Trans SE VSE-21n9(Sep 1995)pp768-775
=THEORY TLA Formal Graphics temporal logic of actions
1. Δ:=for all nodes n, always(if P(n) then A(n) ) or
2. Δ_bar:=always(some nodes n(P(n) and A(n))).
3. (above)|-if Δ then Δ_bar
4. (above)|-if disjoint_predicates then (Δ iff Δ_bar)

LamShankar90

Simon S Lam & A Udaya Shankar
A Relational Notation for State Transition Systems
IEEE Trans SE-16n7(Jul 1990)pp755-775
=MATHEMATICAL regular dynamic formal non-sequential

LamShankar94a

Simon S Lam & A Udaya Shankar
A Theory of Interfaces and Modules I -- Composition Theorem
IEEE Trans SE V20n1(Jan 1994)pp55-71
=THEORY SAFETY LIVENESS MODULARITY PROOF COMPOSITION
See [Jonsson94]
[KayReed93]
[ChandyMisra88]
[AbadiLamport93]

LamSuKoganti88

Herman Lam & Stanley Y W Su & Nageshwar R Koganti
A Physical Database Design Evaluation System for CODASYL Databases
IEEE Trans Soft Eng VSE-14n7(Jul 1988)pp1010-1022
=DEMO DATA QUALITY VOLUME SPEED
not unlike SSADM physical design control.

LammaMelloRiguzzi04

Evelina Lamma & Paola Mello & Fabrizio Riguzzi
A System for Measuring Function Points from an ER-DFD Specification
Computer Journal V47n3( 2004)pp358-372
=CASESTUDY METRIC COST EFFORT DFD ERD ILF ER-DFD
ER-DFD::="Shows entities and relations plus the processes that effect them, and the external entities (actors) involved".

Lammel08

Ralf Lammel
Google's MapReduce programming Model -- revisited
Science of Computer Programming V70n1(Jan 2008)pp1-30 CR 0908-0758 doi:10.1016/j.scico.2007.07.001
=THEORY MapReduce Haskell vs NONSEQUENTIAL MATHEMATICS
See first [DeanGhemawat08]

LamsweerdeDarimontLetier98

Axel van Lamsweerde & Robert Darimont & Emmanuel Letier
Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Trans SE V24n11(Nov 1998)pp908-926
=THEORY PURPOSE KAOS LIGHTWEIGHT FORMAL temporal LOGIC views Some EXPERIENCE
find scenarios leading to divergences. Obstacles are scenarios that make it impossible to meet all the requirements

LamsweerdeLetier00

Axel van Lamsweerde & Emmanuel Letier
Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Trans Software Engineering V26n9(Sep 2000)pp978-1005
=CASESTUDY REQUIREMENTS REFINEMENT EXCEPTIONS TEMPORAL LOGIC KAOS
Requirements can assume too much reliability in parts of system.
Should calculate things that can go wrong and allow for them in their requirements.
p983: "an obstacle defines a set of undesirable behavior; a negative scenario produces a behavior in this set". Obstacles imply a goal is not met but obstacles must not be inconsistent with the domain - exists a scenario
Goals have form "at all times...." but obstacles have form : "at some time...." [KjaerMadsen95]
user anti-story!

LamsweerdeWillemet98

Axel van Lamsweered & Laurent Willemet
Inferring Declarative Requirements Specifications from Operational Scenarios
IEEE Trans SE V24n12(Dec 1998)pp1089-1114
=DEMO USER to PURPOSE TLA FORMAL LOGIC LANGUAGE KAOS WHY+WHO+WHEN+WHAT Lift
Stakeholders may have problems expresssing requirements in abstract but typical scenarios are easier to elicit.
SCENARIO as example of or counter-example to abstraction
Scenario=sequence diagram, Goal.types={achieve, Cease, maintain, avoid}.

LandCrnkovic11

Rikard Land & Ivica Crnkovic
Oh dear, we bought our competitor: integrating similar software systems
IEEE Software Magazine V27n6(Mar/Apr 2011)pp75-82
=EXPERIENCES MERGING CHOOSING SOFTWARE 7 ENTERPRISES 10 PROJECT PAIRS
Approaches: loose integration , merge, choose one, start from scratch, combinations.
Tabulates critical factors, costs, risks etc.

LandSauerJeffery97

Lesley Pek Wee & Chris Sauer & Ross Jeffery(all @unsw.edu.au)
Validating the defect detection performance advantage of group designs for software reviews: Report of a laboratory experiment using program code
[JazayeriSchauer97] pp294-309
=EXPERIMENT COBOL students review code independently and list defects; meet in random groups to prepare 2nd group list also calculate nominal group reports
Results: meetings better! Not because of synergy but because they better discriminate real from false defects.

LandauerGalottiHartwell83

?? Landauer & ?? Galotti & ?? Hartwell
Natural Command names & initial learning: A study of text-editing terms
Commun ACM 26 7 (Jul 1983) pp495-503
=EXPERIENCE USER System

LandayMyers01

James A Landay & Brad A Myers
Sketching Interfaces: Toward More Human Interface design
IEEE Computer Magazine V34n3(Mar 2001)pp56-64
=DEMO TOOL HCI DESIGN SILK
It is important for initial interface designs to look rough. They must be easy to create and edit.

Landwehretal94

Carl E. Landwehr & Alan R. Bull John P McDermott & William S Choi
A Taxonomy of Computer Program Security Flaws
ACM Computing Surveys V26n3(Sep 1994)pp211-254
=SURVEY QUALITY RISKS SECURITY

Lang93

Neil Lang(Project Technology Inc)
Shlaer-Mellor Object-Oriented Analysis Rules
ACM SIGSOFT Software Engineering Notes V18n1(Jan 1993)pp54-58
=REPORT OBJECT-ORIENTED METHOD RULES
72 rules that an analysis must satisfy - but not how to get there

LangFitzgerald05

Michael Lang & Brian Fitzgerald
Hypermedia Systems Development Practices: A Survey
IEEE Software Magazine V22n2(Mar/Apr 2005)pp68-75
=POLL 167 IRISH PROCESS WEB/NET MEDIA REQUIREMENTS MANAGEMENT PEOPLE
Mixture of people from software development and from graphic design. 41% people with equal background.
30% hit time targets and 47% hit cost target. However 17% had 50% timed over run, and 14% had a cost overrun.
Most of the problems where minor or moderate rather than major.
Project scope, feature creep, volatile and changing requirements tended to be more of a problem than estimation, time pressure, communication, or coordination.
Most had a clear process and written requirements specification(mostly 10..50 pages).
Wide range of methods including hybrid, custom, SSADM JSP, SDLC, RAD, XP, RUP plus tool focussed: PHP, Java, Flash, ASP, J2EE,UML. Pus FuseBox, WSDM, OOHDM, ...
No evidence that academic research has produced methods for hypermedia/web that developers are using.

Langdon03

Christoph S Langdon
The State of Web Services
IEEE Computer Magazine V36n7(Jul 2003)pp93-94
=NEWS WEB SERVICES XML URL SEMANTICS MAINTENANCE ECONOMICS INTRANET
service:= search; select; fulfill; pay.
Last not yet supported.
XML: syntax but not semantics.
Used within organizations more than between .

LangeChaudronMuskens06

Christian F J Lange & Michel R V Chaudron & Johan Muskens
In Practice: UML Software Architecture & Design Description
IEEE Software Magazine V23n2(Mar/Apr 2006)pp40-46
=POLL 80 Architects +14 CASE STUDIES UML QUANTITY QUALITY METRICS
80% used usecase & logical, 50% component & scenarios, 17% deployment.
Loose adherence to standard.
Survey presumed a "waterfall" process.
Problems mentioned in poll. scattered information, incompleteness, disproportion, inconsistency, diagram quality, informality, no conventions.
40%+ plan to use more UML metrics.
Defects in case studies: classes do not fit sequence diagrams, classes with no methods.
Experiment: most students & practitioners can't detect mismatches between class and sequence diagrams.
See "Effects of defects in UML models" in ICSE06 by Lange & Chaudron.

LangeNakamura97

Danny B Lange & Yuichi Nakamura
Object-Oriented Program Tracing and Visualization
IEEE Computer magazine V30n5(May 1997)pp63-70
=DEMO GRAPHIC OBJECT-ORIENTED
object interaction graph + class interaction graph + interaction chart + method slicing

Langr02

Jeff Langr
Enlightened Java Style
Software Development Magazine V10n3(Mar 2002)pp48-51
=ADVERT TECHNICAL CODING STYLE Java Comments COHESION
Advertises book: essential Java Style Prentice Hall 1999
"Code should speak."
Boils down all style rules to three patterns: Composed method, Intention-revealing Name, Comment.
composed method leads to cohesion. All parts of method are at the same level of abstraction/encapsulation.
Intention-revealing names ensure cohesion and the hide implementation behind purpose.
Comments are avoided: instead refactor and rename methods.
XP Virtues: simplicity and courage.
Encourage early method return.
discusses braces.

Langr02b

Jeff Langr
Connecting the Dots
Software Development Magazine V10n6(Jun 2002)pp42-46
=DEMO JAVA Test-first JUnit GAME "Boxes" MVP vs MVC
Tests are code that show how classes should be used.
So tests are documentation.

Langton02

Christopher G Langton (Ed.)
Artificial Life: proceedings of an interdisplinary Workshop [...]1987
Addison-Wesley 1989 V6 Santa Fe Inst Studies ISBN 0-201-09346-4
=PROCEEDINGS COMPLEXITY LIFE BIOLOGY

Lano77

R J Lano
The N^2 Chart
TRW report(Software Series) TRW-SS-77-04(Nov 1977) TRW Redondo Beach CA 90278 1977, Extract published as pp244-271 of ThayerDorfman90
=EXPERIENCE graphic engineering

LanoBreuer90

K Lano & P T Breuer
From Programs to Z Specifications
pp46-70 in Nicholls90
=THEORY REVERSE ENGINEER CODE Z

LanoGoldsackSanchez99

Kevin Lano & Stephen Goldsack & arturo Sanchez
specification of a Chemical Process Controller in B
In [HincheyBowen99] pp53-80
=EXPERIENCE fORMAL SPECIFICATION REACTIVE VALIDATION V&V B PCT FSM TEMPORAL LOGIC StateCharts TOOLS
Chemical process control synthesis.
Worked but would have liked to have temporal logic to specify dynamics

LanoHaughton94

Kevin Lano & Howard Haughton
Object-oriented specification case studies
Prentice Hall Englewood Cliffs NJ 1994 ISBN0-13-097015-8
=DEMOS FORMAL MooZ OOZE/FOOPS VDM++ Z++ Object-Z Fresco OOSD OMT SSADM

LanzaDucasse03

Michele Lanza & Stephane Ducasse
Polymetric Views -- A Lightweight Visual Approach to Reverse Engineering
IEEE Trans Software Engineering V29n9(Sep 2003)pp782-795
=DEMO GRAPHICS METRICS CODE REVERSE ENGINEERING TOOLS LANGUAGES Moose CodeCrawler FAMIX
For kinds of plots: tree, scatter, checker, stapled
Map selection of 18 module metrics into five graphic attributes of rectangles: X, Y, height, width, color.

Laplante07

Phillip A Laplante
What every engineer should know about software engineering
CRC Press Boca Raton FL 2007 ISBN 0849372283 CR 0810-0933
=UNREAD =INTRODUCTION SOFTWARE ENGINEERING
Notes [click here if you can fill this hole]

Laplante08

Phillip A. Laplante
Open Source: The Dark Horse of Software?
=SURVEY RESEARCH OPEN SOURCE
Computer Reviews (Jul 2008) [ hottopic_essay_09.cfm ]

LaporteAlexandreRenault08

Claude Y Laporte & Simon Alexandre & Alain Renault
Developing International Standards for Very Small Enterprises
IEEE Computer Magazine V41n3(Mar 2008)pp98-102
=STANDARDS SMALL ENTERPRISES VSE ONESIZE ISO/IEC WG24
Survey shows that small enterprises don't implement ISO standards because (1) no resources, (2) not required, & (3) standards are difficult bureucratic and don't fit small businesses.
Working Group 24 is developing special standard profiles and packages for small enterprises.
Some enterprises will try out the new standards -- real soon now.
See [ index.html ] [ indexEN.php3 ]
(dick)|-This might fix the problems recently reported with ISO/IEC standards [Glass07a]

Larman98

Craig Larman
Applying UML and patterns : an introduction to object-oriented analysis and design
Prentice Hall PTR, c1998. Upper Saddle River, N.J. ISBN 0137488807 QA76.9 .O35 L37 1998
=TEXT OBJECT_ORIENTED PATTERNS UML OOA/D
GRASP::=General Responisbility Assignement Software Patterns
Example: Expert:=assign responsibillity to class that knows about the data.

Larman00

Craig Larman
Enterprise JavaBeans 201: Aggregate entity pattern
Software Development Magazine V8n4(Apr 2000)pp46-52
=ADVERT DESIGN DATA OBJECTS PERFORMANCE EJB COMPONENT PATTERN
Provide a unified efficient remote interface to sets of dependent persistent objects

Larman01

Craig Larman
Protected Variation: The Importance of Being Closed
IEEE Software Magazine V18n3(May/June 2001)pp89-91
=HISTORY MODULES THEORY
refers to [Parnas72] , [Meyer88] and [Cockburn96] as variations of a common principle.
OCP:="Open closed Principle" -- Meyer, Open to extension and adaption but closed to changes that effect clients.
PV:="Protected Variation" -- cockburn.

Larman02

Craig Larman
Applying UML and Patterns: An introduction to Object-oriented analysis and Design and the Unified Process
Prentice Hall 2002
=HANDBOOK Object-oriented analysis design UML RUP PURPOSE QUALITITIES TECHNIQUES

Larman04

Craig Larman
Agile and iterative development: a manager's guide
Pearson Education Boston MA 2004 ISBN 0-13-111155-8 QA76.76.D47L39 2003
=SURVEY=HISTORY AGILE METHODS Evo Gilb Scrum XP RUP MANAGEMENT PROCESS
Best summary of AGILE METHODS to date.
Tackle riskiest non-functional requirement first!

Larman04b

Craig Larman
Applying UML and Patterns: An introduction to Object-oriented analysis and Design and the Unified Process (3 edn)
Prentice Hall 2004 ISBN 0-13-148906-2
=HANDBOOK Object-oriented analysis design RUP PURPOSE QUALITITIES TECHNIQUES UML2.0 GRASP responsibility
Previous edition [Larman02]

LarmanBasili03

Craig Larman & Victor R Basili
Iterative and Incremental development: A Brief History
IEEE Computer Magazine V36n6(Jun 2003)pp47-56 + correspondence V36n8(Aug 2003)pp5-6 from Rita Creel
=HISTORY AGILE METHODS IID evolution1950-2002 non-sequential processes
IID::="iterative and Incremental Development" -- projects that avoided a single-pass sequential document-driven gated-step approach.
Projects/People include 1950s:X-15, Mercury, Los Angeles MIS, IBM, Royce70 (!), Mills, IBM FSD, TRW, LAMPS, Gilb76, Trident, space shuttle, SDC, 1980s: weinberg, McCraken JacksonM, Swartout Balzer, Booch, Boehm Spiral, Brooks86, ParnasClements86, CCPDS-R, Cleanroom, DOD-Std-2167A(!), Gilb88, 1990s: Mil-Std-498 replaces 2167A, Scrum, Shashimi, RAD, DSDM, CAATS, RUP, XP, FDD, CHAOS, 2000: DoD 5000.2, Agile Alliance, ...
Much evidence that IID works better.
Creel corrects standards history.

Larsen99

Grant Larsen
Designing component-based frameworks using patterns in the UML
Commun ACM V42n10(Oct 1999)pp38-45 [Booch99]
=ADVERT 100% buzz-phrase compatible

LarsenFitzgeraldBrookes96

Peter Gorm Larsen & John Fitzgerald & Tom Brookes
Applying Formal Specification in Industry
IEEE Software Magazine V13N3(May 1996)pp48-56
=EXPERIMENT VDM-SL
EXPERIMENT with VDM-SL in British Aerospace Systems and Equipment Ltd. Both teams used top-down structured analysis and CASE
resulting code performed better and had fixed a bugs early. Over the whole cycle VDM-SL did not cost anything extra. Mathematical notation used in other FMs is an obstacle. Tools - simulators etc need for learning and experimenting. Training: 1 week(!) but needed 2 days specialized training for designers and for implementors

Larson09

Jim Larson
Erlang for Concurrent Programming
Commun ACM V52n3(Mar 2009)pp48-56 [ 1467247.1467263 ]
=ADVERT LANGUAGE Erlang NON-SEQUENTIAL FUNCTIONAL Ericsson OTP OPEN SOURCE AGENTS
A naturally concurrent language used at Ericsson and elsewhere.
Use pattern matching rather like Prolog! But also pattern matches incoming massages.
Has anonimous functions.
Typically a client makes a unique reference that it sends as part of a message to a parallel server. This identity is used by the server to call-back the client.
Note: The obligatory examples are also at [ Erlang_(programming_language) ] (Wikipedia)
See [ samples/languages.html#Erlang ] [Armstrong10] for more information.
OTP::="Open Telecom Platform".

LarusEtal04

James R Larus & Thomas Ba;; & Manuvir Da & Robert DeLine & Manuel Fahndrich & Jon Pinckus & Sriram K Rajaman & Ramanathan Venkatapathy
Righting Software
IEEE Software Magazine V21n3(May/Jun 2004)pp92-100
=EXAMPLE TOOLS ERROR CHECKING C MicroSoft PREfix PREfast API Slam FSMs
PREfix analyzes a complete C/C++ programs and finds patterns that are commonly errors.
PREfast is similar but faster and works on a function at a time.
Later tools target API usage and depend on being given descriptions of good and bad behavior.
Slam uses finite state machine descriptions of legal and illegal sequences of API calls.
ESP::=Error detection via scalable program analysis, less precise but handles more code and uses OPAL
OPAL::=Object Property Automaton Language, FSM and syntax patterns.
Vault::=a safe version of C allows checking across module boundaries
Also see [LarusHunt10]

LarusHunt10

James Larus & Galen Hunt (Microsoft)
The Singularity system
Commun ACM V53n8(Aug 2010)pp72-79 [ 1787234.1787253 ]
=DEMO MODULES SAFE OPERATING SYSTEM Boogie Bartok SELF-DESCRIBING CHANNELS ISOLATED PROCESSES MICROKERNEL Sing# MANIFESTS SPECIFICATIONS GARBAGE COLLECTION
Singularity::Operating_system= See http://www.cideplex.com/singularity. Designed to contain the consequences of bugs.
SIP::="software isolated processes", Can not share memory etc.
Channels have contracts. Contracts are light weight specifications that are tied to code.
Follows [LarusEtal04]

Latteier01

Amos Latteier
The Insider's Guide to Zope
Software Development Magazine V9n5(May 2001)pp31+33-36
=REVIEW TOOL OPENSOURCE WEB Object-Oriented DATABASE ORB PYTHON

Lattanze96

Anthony Lattanze
Under the Hood
Software Development Magazine V4n10(Oct 1996)pp53-54+56+58-59
=ADVERT INSPECTIONS SQA
inspect early and often

Lau07

Tessa Lau
Social Scripting for the web
IEEE Computer Magazine V40n6(Jun 2007)pp96-98
=TOOL OPEN SOURCE SCRIPTS PROCEDURES WWW/NET WIKI-like KOALA
Koala::= See http://www.research.ibm.com/koala
Koala records in peudo-natural language actions taken as user browses the web to generate scripts easily.
Scripts can pause for user interaction and fill in some values.
System will store and replay scripts.
Scripts can be published and so shared in Koalaescence.
Scripts can be edited.
Unclear if there is any form of conditional/selection/exception/extension/looping.
Scripts have a title but no other aparent documentation: e.g. no pre/post-conditions or safeness/liveness guarantees.

LauLawWiederhold05

Gloria T Lau & Kincho H Law & Gio Wiederhold
Analyzing government regulations using structural and domain information
IEEE Computer Magazine V38n12(Dec 2005)pp70-76
=ADVERT Regnet DOCUMENT STRUCTURE GOVERNMENT RULES DOMAIN ONTOLOGIES SIMILARITY METRIC ADAAG UFAS REQUIREMENTS SYSTEM

Regnet::= See http://eig.stanford.edu/regnet..Close

Lauesen03

Soren Lauesen
Task descriptions as Functional Requirements
IEEE Software Magazine V20n2(Feb/Mar 2003)pp58-65
=EXPERIENCE IDEA REQUIREMENTS support TASKS PURPOSES cf USER STORY USECASE
Tasks_and_Support::=Express requirements as the need to support tasks; repeat(split tasks up into subtasks(and variants) and review); attach the support provided by the computer systems to the subtasks.
Result: table with two columns: first tasks, second "support"s.
It worked to clarify and add traceability to requirements. Enabled suppliers to bid fairly. Can adjust costs,ambitions, and needs.
BUT needs data descriptions, quality specifications, suppliers don't know how to amend "supports", developers have to learn how to develop parts to support tasks by systematic HCI design, the CUSTOMER has to work harder (and faster)!
(dick)|-Why not UMLstyle activity diagrams for breaking down tasks?

LauesenHarning01

Soren Lauesen & Morten Borup Harning
Virtual windows: Linking user tasks, data models, and interface design
IEEE Software Magazine V18n4(July/Aug 2001)pp67-75+letter V18n5(Sep/Oct 2001)pp5-9(Rainer Schoenrank)
=EXPERIENCE USER DESIGN DATA PURPOSE
Pays to find smallest set of windows to present the data and then prepare storyboards with detailed example data. Show to users.

LauesenYounessi98

Soren Lauesen & Houman Younessi
Is Software Quality Visible in the Code?
IEEE Software magazine V15n4(Jul/Aug 1998)pp69-73
=EXPERIENCE =ANALYSIS TECHNICAL vs REQUIREMENTS
45% defects are not detectable from the code alone

Launchbury91

John Launchbury
Projection Factorisations in Partial Evaluation
Cambridge UP 1991 ISBN 0-521-41497-0
UK 1990 outstanding dissertation award

Lausen88

Georg Lausen
Modeling and Analysis of the Behavior of Information systems
IEEE Trans Soft Eng VSE-14n11(Nov 1988)pp1610-1620
=theory =demo dfds and petri-nets

LauWang07

Kung-Kiu Lau & Zheng Wang
Software Component Models
IEEE Trans Software Engineering V33n10(Oct 2007)pp709-724 CR 0812-1198
=SURVEY MODULES ARCHITECTURE EJB COM .NET CORBA PECOS UML2.0 SOFA ...

Laver65

F J M Laver
Introducing Computers
HMSO London England 1965
=HISTORY ADP SCIENTIFIC vs BUSINESS SYSTEMS ENGLISH-ELECTRIC ELLIOTT MARCONI LEO
ADP::acronym="Automatic Data Procesaing".
Quotation from Page 45

LawrenceJacksonD96

Brian Lawrence & Daniel Jackson
Point Counterpoint: Do You Really Need Formal Requirements? vs Requrements need Form and Maybe Formality
IEEE Software magazine V13n3(Mar 1996)pp20-22
=DEBATE FORMALISM REQUIREMENTS

LawrenceJohnson97

Brian Lawrence & Bob Johnson
The Project Scoping Gamble
IEEE Software magazine V14n3(May/Jun 1997)107-109

Lawson90

Harold W. Lawson
Philosophies for Engineering Computer-Based Systems
IEEE Computer V23n12(Dec 1990)pp52-63.
=ESSAY ETHICS PROFESSIONALISM

Lawton05

George Lawton
LAMP Lights Enterprise Development Efforts
IEEE Computer Magazine V38n9(Sep 2005)pp18-20
=ESSAY MicroSoft vs Sun Java vs Open Source
LAMP::=Platform(OS=Linux, Web_server=Apache, database=MySQL, scripting={Perl, PHP, Python})

Lawton08

George Lawton
New ways to build rich internet applications
=ADVERT RIA Ajax Google GWT Microsoft ASP.Net Silverlight Adobe Flash AIR Flex JavaFX
IEEE Computer Magazine V41n8(Aug 2008)pp10-12
RIA::="Rich Internet Applications".
Technology for more powerful clients in a client-server system -- mainly as plugin to a browser.
Several competing new systems.

Lawton09

George Lawton
the changing face of open source
IEEE computer magazine V42n5(May 2000)pp14-17
=HISTORY F/OSS ECONOMICS
open source is no longer a movement, but another development process option.

Lea94

Doug Lea(SUNY Oswego)
Cristopher Alexander: An Introduction for Object-Oriented Designers
ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)pp390-46 "A Pattern Language" by Alexanderetal77. [Anderson94] [Johnson94]

LeachFuller95

Ronal J Leach (rjl@scs.howard.edu) & Terrence L Fuller(tfuller@bnr.ca)
An Illustration of the Domain Analysis Process
ACM SIGSOFT Software Engineering Notes V20n5(Dec 1995)pp78-82
SYSTEM(Linux)->responsibillities: "To do action (A) to object (O) that resides on medium (M) is the responsibility of system (S)" + tables of AOMS words.

Leavens91

G T Leavens
Modular Specifications and Verification of Object-oriented programs
IEEE Software Magazine V8(July 1991)pp72-80

Leavitt51

H J Leavitt
Some effects of certain communication patterns on Group Performance
J Abnormal Social Psychol V46(??? 1951)pp38-50
=EXPERIMENT TEAM COMMUNICATION STRUCTURE PEOPLE
See [GoodeMachol57]

Leavitt04

Neal Leavitt
are web services finally ready to deliver.
IEEE Computer Magazine V37n11(Nov 2004)pp14-18
=ARTICLE Web/NET
WS-I::= "web services interoperability organisation".
OASIS::= "organisation for the advancement of structured information standards".

Leavitt10

Neal Leavitt
Will NoSQL databases live up to their promise?
IEEE Computer Magazine V43n2(Feb 2010)pp12-14
=ESSAY DATABASES RELATIONAL TABULAR vs key-value column-oriented document-based
Lists new tools and their issues.

LedererPrasad98

Albert L Lederer & Jayesh Prasad
A Causal Model for Software Cost Estimating Error
IEEE Trans Soft Eng V24n2(Feb 1998)pp137-148
=POLL =ANALYSIS PROCESS COST
why do algorithmic techniques fail to appear to increase accuracy

Ledgard01

Henry F Ledgard
The Emperor with No Clothes
Commun ACM V44n10(Oct 2001)pp126-128
=HISTORY PRODUCTIVITY TECHNOLOGY Object-Oriented
Some evidence that OOP may have decreased productivity -- but nobody is measuring the changes,

LedgardMarcotty75

H F Ledgard & M Marcotty
A Genealogy of Control Structures
Commun ACM v18n11(Nov 1975)pp629-639
=HARMFUL sequential Technical structures
Summarizes the controversy started by [BohmJacopini66]

Lee93

Geof Lee
Object-oriented GUI application development
Prentice Hall Englewood Cliffs NJ 1993 ISBN 0-13-363086-2 CR9411-0751
=MANUAL GRAPHIC USER GUI OBJECT-ORIETED OOA

Lee06

Edward A Lee
The Problem with Threads
IEEE Computer Magazine V39n5(May 2006)pp33-41
=HARMFUL THREADS =ADVERT Ptolemy
Replace threads by higher level abstractions.
Example of problems with the Observer pattern when multithreaded fixed by a higher level language expression.

LeeDeloneEspinosa06

Gwanhoo Lee & William Delone & J Alberto Espinosa
Ambidextrous coping strategies in global distributed software development projects
Commun ACM V49n10(Oct 2006)pp35-40
=POLL 22 MANAGERS GLOBAL DISTRIBUTED QUALITY ESTIMATION TIME BUDGET
Studied boundaries & barriers to communication & coordination that lower qualities.
Table 1 (page 36) classifies coping strategies by phase (initiation+execution) & focus (task+people+technology).
Coping strategies increase flexibility & rigor.
Example provide many communication technologies but let their usage evolve to fit needs.
More communication, work, documentation, diagrams, details, education, control, face-to-face workshops,...
Break down work into independent areas.
follow_the_sun::="24-hour operation by turning tasks over to sites in other time-zones".
Appoint a point of con tact for each location.

LeeXue99

Jonathon Lee & Nien-Lin Xue
Analyzing user requirements by use cases: a goal-driven approach
IEEE Software magazine V16n4(Jul/Aug 99)pp92-100 + letters V16n5(Sep/Oct 1999)pp14
=ADVERT PURPOSE USE-CASE GOALS
Letters: Constantine -> should give credit to Kaindl, Graham, Lockwood, etc.

Leech74

Geofrey Leech
Semantics
Penguin Books MD 1974-76
=TEXT LANGUAGES SEMANTICS

Leeper01

David G Leeper (intel)
A Long-term View of Short-Range Wireless
IEEE Computer Magazine V34n6(Jun 2001)pp39-44
=HISTORY =THEORY NET PAN LAN WAN
Wireless was at first importatn for long range (transatlantic) communication, now short range -- personal is found to be useful.
PAN:="Personal Area Network", 0..10.meter
Sample: passengers waiting for an aeroplane.
(Information theory)|- (Hartley_Shannon): C = B * log[2] (1 +(S/N) ) where C = channel capacity in bits/s, B= bandwidth in Hertz, S= signal power in watts, N = Noise power in watts.

LeeIyer95

Inhwan Lee & Ravishanka K Iyer
Software Dependability in the Tandem GUARDIAN System
IEEE Trans Software Engineering V21n5(May 1995)pp455-467
=EXPERIENCE RISKS RELIABILITY QUALITY

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

LeeSluizer91

Stanley Lee & Suzanne Sluizer
An Executable Language for Modeling Simple Behavior
IEEE Trans SE v17n6(Jun 1991)pp527-543
CR9211-0865
=CASE-STUDY REALITY MATHEMATICAL SXL
compare with JSD & STATEMATE

LeeSohn03

Jae Kyu Lee & Mye M Sohn
The eXtensible Rule Markup Language (XRML)
Commun ACM V46n5(May 2003)pp59-64
=IDEA LANGUAGE RULES XML HTML
XRML::= RIML+RSML+RTML.
RIML::="Rule identification language".
RSML::="Rule Structure Markup Language".
RTML::="Rule Triggering Markup Lange

Leeuwen90

Jan van Leeuwen(ed)
Handbook of Theoretical Computer Science -- Volume B. Formal models and Semantics
MIT Press Cambridge MA/Elsevier Science Pub Amsterdam The Netherlands CR9209-0659
=REFERENCE THEORY FORMAL SEMANTICS
Includes [Wirsing90]

LeeWei06

Wei Lee
Programming Sudoku
Apress Berkeley CA 2006 ISBN 1590596625 CR 0711-1092
=UNREAD EXAMPLE AI CONSTRAINT SUDOKU VISUAL BASIC

Lee11

Yee Lee (@yeeguy)
How Facebook Ships Code
Framethink (Jan 17 2011) [ http://framethink.wordpress.com/2011/01/17/how-facebook-ships-code/ ]
=BLOG = DISCUSSION PROCESS FACEBOOK ENGINEER
Boot Camp
Internal open source with all changes reviewed by another.
Monthly cross team meetings
Have to get people interested in a project to get help.
Build it and try it on 1% of users.
Engineers produce bug-free code so no QA dept.
Complicated release structure with a weekly cycle and authors online to fix.
(epriestley)|-There are some significant inaccuracies in this article [ c1d3b37 ]

LeeZachary95

Arthur H Lee & Joseph L Zachary
Reflections on Metaprogramming
IEEE Trans Soft Eng VSE21n10(Oct 1995)pp883-893
=THEORY metaprogramming promising but metaobject protocol a problem

LeffingwellWidrig00

Dean Leffingwell & Don Widrig
Managing software requirements: a unified approach
Addison-Wesley Boston MA 2000 ISBN 0-201-61593-2 CR0002-0056 QA76.76.D47 L44 1999
=EXPERIENCE METHOD USECASE SRS PEOPLE UML
Defines "Modern SRS"

Lehman78

Manny M Lehman(Imperial College London UK)
Laws of Program Evolution - Rules and Tools for Programming Managamnet
Proc Infotech State of the Art Conf "Why Software Projects Fail" (Apr 9-11 1978)pp11/1-25 UK
=EXPERIENCE RISKS EVOLUTION

Lehman95

Manny M Lehman(Imperial College London UK)
FEAST - Feedback, Evolution, And Software Technology
Software Process Newsletter n3(Spring 1995)pp3-6 IEEE CS TCSE Committee on Software Process
=THEORY EVOLUTION FEAST
FEAST::="Feedback, Evolution, And Software Technology".

Leinfuss93

Emily Leinfuss
Managing Class Libraries takes Discipline
IEEE Software Magazine(Jan 1993)pp15-21
=ESSAY OBJECT-ORIENTED LIBRARIES

Leite96

Julio Cesar Sampaio do Prado Leite<julio@inf.puc-rio.br>
Working Results on Software Re-Engineering
ACM SIGSOFT Software Eng Notes V21n2(Mar 1996)p39-44
=EXPERIENCES JSD SADT

LeiteEtal97

Julio C S P Leite & G Rossi & R M S Vicente & F Balaguer & V Maiorana & G Kaplan & G Hadad & A Oliveros
Enhancing a Requirements Baseline with Scenarios [RE'97] pp44-53
=DEMO ERD lexicon basic-model hypertext configuration views

LeiteFreeman91

Julio C S P Leite & Peter A. Freeman
Requirements Validation Through Viewpoint Resolution
IEEE Trans SE-17n12(Dec 1991)pp1253-1269 CR9301-0027
=DEMO REQUIREMENTS VIEWS
Used parsed trees to express and compare requirements
produces differences which help authors to understand the situation

LejkDeeks02

Mark Lejk & David Deeks
An Introduction to Systems Analysis Techniques (2nd edn.)
Addison Wesley USA & Pearson Edn Ltd Harlow Essex UK 2002 ISBN 0-201-79713-5
=TEXTBOOK SSADM Object-Oriented REALITY SYSTEM PURPOSE DFD SPECIFICATION ELHs PISO CRC Decision TABLES Management
PISO::="Process Improvement for Strategic Objectives".

LejterMeyersReiss92

Moises Lejter & Scott Meyers & Steven P Reiss
Support for Maintaining Object-Oriented Programs
IEEE Trans SE-v18n12(Dec 1992)pp1045-1052
=TOOL Maintenance XREFDB C++ Technical relational data base

LemahiueEtal05

Wilfried Lemahieu & Monique Snoeck & Frank Goethala &Manu De Backer & Raf Haesen & Jacques Vandenbulke & Guido Dedene
Coordinating COTS Applications via a Business Event Layer
IEEE Software Magazine V22n3(Jul/Aug 2005)pp28-35
=DEMO ARCHITECTURE BUSINESS PROCESS COTS COMPONENTS MODULES
Proposes coordinating components by using two layers on top of the components. One layer describes a business processing terms of business events. The second layer defines the different business events and notifies various subsets of application components in turn.
Compare with MVC and Larman

LemosSauudAnderson92

R de Lemos & A Sauud & T Anderson
A Train Set as a Case Study for the Requirements Analysis of Safety Critical Systems
Computer Journal V35n1(Feb 1992)pp30-40 CR9307-0516
=CASE-STUDY REQUIREMENTS Reality

Lenat95

Douglas B. Lenat(mailto:Lenat@MCC.COM & doug@cyc.com)
CYC: A Large-scale Investment in Knowledge Infrastructure
Commun ACM V38n11(Nov 1995)pp33-38 +pp45-48(critiques)
=EXPERIENCE CYC LOGIC ONTOLOGY

Lenatetal90

Douglas B. Lenat & R.V. Guha & Karen Pittman & Dexter Pratt & Mary Shephard
Cyc: Toward Programs with Common Sense
Commun ACM V233n6(Aug 1990)pp30-49
=EXPERIENCE CYC LOGIC ONTOLOGY

Leon04

Alexis Leon
Software Configuration Managment handbook (2nd Edn.)
Artech House Inc NorwordMA 2004 ISBN 1580538827 CR 0605-0???
=UNREAD =MANUAL SCM
Notes [click here if you can fill this hole]

LeonardDavis95

Corey A Leonard & J Steve Davis
Job-shop development Model: A Case Study
IEEE Software Magazine V12n2(Mar 1995)pp86-92
=CASE_STUDY STATISTICAL MODEL PROCESS

LepourasEtAl07

George Lepouras & Costas Vassilakis & Constantin Halatsis & Panagiotis Georgiadis
Domain Expert User Development: The SmartGov Approach
Commun ACM V50n9(Sep 2007)pp79-83
=EXPERIENCE DOMAIN USER ANALYSIS DESIGN e-forms TOOLS
Attempting to create electronic forms for Government.
Government systems have these types of stakeholders: end users (external), IT personnel, Managers, internal experts.
Issues tackled: Domain experts can have a limited view, Lost information, complexity of creating e-forms, providing helpful access(documentation, help,...) to end users.
Supsorting materials: /implicit knowledge, regulations, organizational practiceprinted forms, tacit.
Responsibilities split between domain experts, IT personel, and the Integrator Component.
IT experts: look and feel + connections to other/legacy systems.
Doamin experts: specify and design data, specify requirements, authoring knowledge units (documentation) about data, identify, retrieve, copy, edit existing data.
Software inhouse or open source LAMP, Based on JSP Java XML RDBMS JDBC

Leroy09

Xavier Leroy
Formal Verification of a realistic compiler
=DEMO PROGRAM PROVING COMPILER TOOLS CompCert Coq FORMAL SEMANTICS SEMANTIC PRESERVATION Mach Cminor
Commun ACM V52n7(Jul 2009)pp107-115
Shows that a useful subset of C can be compiled in real and efficient assembler code by a compiler that has been proven correct -- with the proofs checked by tools.

Lesiecki06

Nicholas Lesiecki
Applying AspectJ to J2EE Application Development
IEEE Software Magazine V23n1(Jan/Feb 2006)pp24-32
=EXPERIENCE ASPECTS GOOGLE AOP AspectJ
In [MurphySchwanninger06]

Lethbridge00

Timothy C Lethbridge
What knowledge is important to a software professional?
IEEE Computer Magazine V33n5(May 2000)pp45-50
=POLL DEVELOPERS EDUCATION vs PRACTICE
WWW Site: [ see.html ]
1998: 75 questions >< 4scales, 186 responses 24 countries
Education: 15%no bachelor, 48 bachelor, 37% postgrad. 60%in cs/se/is, 50%sci/eng degrees
topics that are taught but not used - chemistry, physics, calculus, differential equations, VLSI, robotics
topics needed more than taught - requirements, patterns, CM, negotiation, entrepreneurship, CMM/ISO9000

LethbridgeSingerForward03

Timothy C Lethbridge & Janice Singer & Andrew Forward
How Software engineers use documentation: The state of the Practice
IEEE Software Magazine V20n6(Nov/Dec 2003)pp35-39
=POLLS PRACTICES DOCUMENTATION Questionnaire [ main.html ]
In line comments help.
Documentation is
- helpful tends to be out of date too much
- poorly written
- takes more time than its worth
- not easy to retrieve
- untrustworthy
Only quality/test documentation is updated more than weekly.
Documentation doesn't need to be up to date to be worth doing. Software engineers tend to use simple and powerful documentation and ignore complex time-consuming documentation.
How to express more better simpler? Worth studying working developers.

LetierLamsweerde02

Emmanuel Letier & Axel van Lamsweerde
deriving Operational Software specifications from System Goals
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp119-128
=DEMO SYSTEM REQUIREMENTS GOAL REFINEMENT PATTERNS LOGIC AND/OR TEMPORAL RT-LTL REALITY ENTITY RELATIONSHIP OPERATION SPECIFICATION
An operation is a temporal proposition defined by the current truth of a set of preconditions and the truth in the next step of a set of postconditions.
goal_patterns::=achieve | maintain_avoid.
achieve::= unbounded_achieve | bounded_achieve | immediate_achieve.
unbounded_achieve: for always if C then sometime T.
maintain_avoid::= state_invariance | transition_invariance.
state_invariance::=global_invariance | after_invariance | in-between_invariance.

LetierLamsweerde04

Emmanuel Letier & Axel van Lamsweerde
Reasoning about partial goal satisfaction for requirements engineering.
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp53-62
=DEMO QUALITIES PROBABILITY GOALS PCTL

LeungEtAl00

Karl R P H Leung & Lucas C K Hui & S M Yiu & Ricky W M Tang
Modeling Web Navigation by Statechart
IEEE COMPSAC, p. 41, The Twenty-Fourth Annual International Computer Software and Applications Conference, 2000. [ CMPSAC.2000.884689 ]
=THEORY WEB DESIGN HAREL STATECHART
Note: treats frames by using parallel states.
Modifies notation with special transitiopns for hyperlinks.

Lev-AmiEtal00

Tal Lev-Ami & Thomas Reps & Mooly Sagiv & Reinhard Wilhelm
Putting Static Analysis to Work for Verification: A Case Study
Proc ISSTA 00 & ACM SIGSOFT Software Engineering Notes V25n5(Sep 2000)pp26-38
=DEMO TOOL PROOF POINTERS 3-valued LOGIC GRAPH

Leveson90

Nancy G Leveson (Guest Ed)
Formal Methods in Software Engineering
IEEE Trans Software Engineering SE-V16n9(Sep 1990)
=EDITORIAL

Leveson94

Nancy G Leveson<leveson@cs.washington.edu>
High-Pressure Steam Engines and Computer Software
IEEE Software Magazine V27n10(Oct 1994)pp65-73
=HISTORY RISKS SAFETY ENGINEERING

Leveson95

Nancy G Leveson
Safeware: system safety and computers
Addison-Wesley Redwood City CA 1995 ISBN 0-201-11972-2 QA76.76.R44L48
=MONOGRAPH RISK FAULT TREE

Leveson95a

Nancy G Leveson
Safety as a System Property
Commun ACM V38n11(Nov 1995)p146
=ADVERT RISK MONOGRAPH
[Leveson95(advert)]
accidents in complex systems happen when a bad interaction occurs between correctly operating parts
Safety is not a property of the parts but an "emergent" property of the whole system
safety does not survive reuse(Therac 25)
most accidence come from failure to apply well-known standard engineering practices

Leveson00

Nancy G Leveson
Intent Specifications: an approach to building human-centered specifications
IEEE Trans Software Eng V26n1(Jan 2000)pp15-35 CR0004-0268
=THEORY PEOPLE PURPOSE SPECIFICATION COGNITIVE HCI SYSTEM ENGINEERING METHOD NOTATION cognitive
designing a specification method to improve problem solving.
intent:=design rationale.
Levels why ->what->how: higher have emergent
TCAS II intent spec [ http://sunnyday.mit.edu ] does not fit sructure described in figure 2 p21
does include assumptions about environment, system constraints, operator and goals s description of system purpose.
means-ends abstraction is not traditional parallel/part-whole decomposition-- Rasmussen

LevesonEtal94

Nancy G Leveson & Mats Per Erik Heimdahl & Holly Hildreth & Jon Damon Reese
Requirements Specification for Process-Control Systems
IEEE Trans SE VSE-20n9(Sep 1994)pp684-707
=CASE-STUDY FORMAL STATECHART GRAPHICS REVERSE-ENGINEERING
[Heimdahl96]
1. RSML::=Requirements State Machine language TCAS II project While developing a formal model in a university the team was invited to do it for real. They joined the re-engineering team. Working out the requirements specifiction that should have been written - using a 15 year old modified pseudo-code specification and working with FAA employees, manufacturers, airline people, pilots etc. As a result they had to modify their notations to include graphics and tables. Briefly it worked.
  p684: "not only the computer" "a blackbox model separates the specification of requirements from design, simplifying the model and making the requirements model easier to construct, review, and formally analyse"
  FSM with superstates, substates, AND, arrays, connectives(C), plus encapsulated broadcast internal events plus directed communication (visible events), interface definitions, inputs+chart+output boxes, transition definitions, AND/OR tables, Macros and functions, transitions Busses, Xrefs and indentifiers (page refs on transitions), identity transitions, Timing, step semantics
  p704: Graphics and tables

LevesonEtal99

Nancy G Leveson & Mats P E Heimdahl & Jon Damon Reese
Designing Specification Languages for Process Control Systems; Lessons Learned and Steps to the Future
[NierstraszLemoine99] pp126-145
=EXPERIENCE RSML FAA TCAS SpecTRM SpecTRM-RL SPECIFICATION LANGUAGES METHOD FORMAL GRAPHIC TABULAR TOOLS
Errors from synchronizing parallel interdepent machines and startup, so eliminate internal events and use data dependencies to determine sequence of state changes.

LevesonEtal99b

Nancy Leveson & Mats Heimdahl & Jon D Reese
A CAD environment for safety-Critical Software
In [HincheyBowen99] pp139-156
=ADVERT PROTOTYPE FORMAL TOOL RISKS NASA RSM RSML TCAS FAA STATECHARTS FSM AND/OR SpecTRM-RL Safeware
Describes the plans for a tool to aid the specification of safe systems that contain software.
Importance of embedding software safety inside system safety.
Definitions of mishap, accident, hazard, risk.
Code generation is feasible but the result is 5-10 times slower and twice as large as human optimized code.
[LevesonEtal99]

LevesonTurner93

Nancy G Leveson & Clark S Turner
An Investigation of the Therac-25 Accidents
IEEE Computer Magazine V26n7(Jul 1993)pp18-41
=HISTORY RISKS Ignorant mistakes made at the process and coding levels.

LevesonWeiss04

Nancy G Leveson & Kathryn Anne Weiss
Making embedded software reuse practical and safe
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp171-
=EXAMPLES RISKS REUSE QUALITIES SAFETY EVOLUTION INTENT DOCUMENTATION DESIGN DECISIONS NASA MCO Ariane SOHO TOOL SpecTRM And/Or TABULAR SPHERES PAD FSA TCAS
Accidents caused when undocumented assumptions made by reused components ceased to be true.
Change happens and documentation helps to trace the changes to the components that are no longer safe to (re)use.
Generic libraries of intent specification for SPHERES project with a single experimental reuse...
Need to document the WHY at half-a-dozen levels.
Claims that OO requirements analysis can not produce safely reusable components because requirements are distributed across many object.
However OO design of components proved to meet documented requirements may be safe to reuse.

Lewietal92

Johan Lewi & Karel de Vlamink & Eric Steegmans
Software Development by LL(1) Syntax Description
John Wiley &Sons Inc Somerset NJ 1992
=TEXT SYNTAX

Lewin01

Roger Lewin
Complexity: Life at the edge of chaos
Univ Chicago Press 1992 1999 ISBN 0-226-47654-5
=IDEAs THEORY AUTOMATA BOOLEAN NETWORKS PHILOSOPHY BIOLOGY EVOLUTION EMERGENCE
Set of interviews. Chris Langton, Stu Kauffman, etc etc Santa Fe Institutes and beyond.
adaptive behavior emerges when many randomly connected arts have the right amount of connectivity. To much and the system is chaotic. To little and the system is static. On the edge the whole can move through chaos to a new island of stability. Niches and rugged "fitness landscapes".
Speculation on applications to psychology, sociology, business, and biology.

Lewis79

?Ted? Lewis
Software Engineering for Micros
Hayden Book Co USA
=TEST BNF Reality

LewisT94a

Ted G Lewis(<lewis@cs.nps.navy.mil>Naval Postgraduate School)
Where is Computing Headed
IEEE Computer Magazine V27n8(Aug 1994)pp59-63+ letters IEEE Computer magazine V28n11(Nov 1995)p5(Vinnie Ferrando)
=FUTURE

LewisT94b

Ted G Lewis(<lewis@cs.nps.navy.mil>Naval Postgraduate School)
The Dark side of Objects(Editorial)
IEEE Computer Magazine V27n12(Dec 1994)pp6-7
=ESSAY OBJECT-ORIENTATION

LewisT94c

Ted G Lewis(<lewis@cs.nps.navy.mil>Naval Postgraduate School)
The Big Software Chill
IEEE Computer Magazine V29N3(Mar 1996)pp12-14
=ESSAY ECONOMICS MARKET TECHNOLOGY

LewisT94d

Ted G Lewis(<lewis@cs.nps.navy.mil>Naval Postgraduate School)
The Next 10000[2] Years: Part II
IEEE Computer Magazine V29N5(May 1996)pp78-86
=ESSAY predictions DESIGN REUSE
1. networks will survive.
  Software as Steam for the future.
  Quotes Capers Jones on programmer productivity increasing 3-5% per year ($/fp).
  Shows comparison of power of languages.
  reates an oportunity for new ideas etc.
  Predicts large MIS will go for visual tools and object tools rather than languages. (compare Keuffel96? - the bubble sort effect). OT as a stepping stone, discarding functional decomposition and hiding if-then-else logic.
2. Errors of inheritance and polymorphism.
3. Things lacking and possible fixes:
  1. Requirements: continuous adaption
  2. defects: correct-by-construction
  3. Avoid big systems, make pieces
  4. Time: paint programs
  5. Cost: throwaway parts
  6. expertise: use tools with artistic skills needed
4. Frameworks with API, Components produced by experts.
5. Applets as event handlers with user in control using frameworks and components

Lewis98

Ted Lewis
Joe Sixpack, Larry Lemming, and Ralph Nader(Binary Critic)
IEEE Computer Magazine V31n7(Jul 1998)pp107-109
=EXPERIENCE USER MS RISKS
Windows 98 fixes 5K bugs in Windows95
Windows NT is certified C2 secure and has 104 vulnerabilities
Y2K problems in BIOS Access Excel Filemaker
Capers Jones formulae (one test/fix cycle gets remaining 30% of bugs) predict defectpotential for windows95 as 2.95M needing 18 test/fixcycles to get down to 5K or 42 to get down to one bug
Market and economics of testing can encourage release of damaged goods
consumer goods vs VAR market

Lewis00

Ted Lewis
The end of Research as we know it?
IEEE Computer Magazine V33n6(Jun 2000)pp112+110-111
=ESSAY SCIENCE
old_process:=government+basic; industry+(R&D; product predevt; product; manufacturing & sales & marketting).
new_process:=student_dissertation; venture_capital; starup+version 1; manufacturing & sales & marketting & customer feedback; investors
shallow science - imagination with no grad work.

LewisR11

Robert H Lewis
Mathematics: The most misunderstood Subject
Fordham University [ index.asp ] (Downloaded Jan 27th 2011) (Written 1993..2008)
=ESSAY MATHEMATICS
"The great misconception about mathematics -- and it stifles and thwarts more students than any other single thing -- is the notion that mathematics is about formulas and cranking out computations. It is the unconsciously held delusion that mathematics is a set of rules and formulas that have been worked out by God knows who for God knows why, and the student's duty is to memorize all this stuff. [...] Mathematics is not about answers, it's about processes. [...] The real "building" in the mathematics sense is the true mathematical understanding, the true ability to think, perceive, and analyze mathematically. "

Li91

Xiaofeng Li
What's so Bad about Rule-Based Programming
IEEE Software V8n5(Sept 1991)pp103-105
=DEMO LOGIC PROGRAMMING AI Technical Maintenance Reliability

Li04

Xiaotong Li
Informational Cascades in IT Adoption
Commun ACM V47n4(Apr 2004)pp15-19
=THEORY INFORMATION ECONOMICS EXTERNALITIES
If information on technology is shared then the best technology is likely to be adopted. If information is not shared and there are network externalities the early adopters can lead a herd of followers to a less perfect technology. It pays technology suppliers to get in first, hide information, and encourage creditable word of mouth from adopters to the rest. Cf.See [Botting97].

LiConradiEtAl09

Jinguin Li & Reidar Conradi & Odd Petter N Slyngstad & Christian Bunse & Marco Torchiano & Maurizio Morisio
Development with Off-the-shelf Components: 10 Facts
IEEE Software Magazine V26n2(Jan/Feb 2009)pp80-87
=POLL COTS OSS OFF-THE-SHELF COMPONENTS PROCESS ECONOMICS METHOD
Companies don't change their process because they are using OTS components... they just add special integration steps.
Components are selected informally.
Components are integrated into a system both early and late in the process.
Estimates are base on personal experience.
OTS components usually don't degrade system quality.
OSS and closed proprietary OTS components are used the same way -- no rewriting the open source parts.
Locating and debugging defects is substantial.
The supplier is involved in more than bug fixing during maintenance.
Clients are not usually involved in OTS selection.
Knowledge about non-fucntional properties of OTS components must be managed.

LiHarmanHierons07

Zheng Li & Mark Harman & Robert M Hierons
Search Algorithms for Regression Test Case Prioritization
IEEE Trans Software Engineering V33n4(Apr 2007)pp225-237
=EXPERIMENTS OPTIMIZATION GREEDY GENETIC HILL-CLIMBING
Test Case Prioritization:=following
Net
1. Tests::given.
2. PT:= 1..|Tests| --- Tests, permutations.
3. award : PT >-> Real = given.
4. T:PT = goal.
5. |-(optimal) : for all T':PT~{T}( award(T)>=award(T') ).
(End of Net)
Greedy worked quiet well in both small and large test sets.
Hill Climbing produced a wide range of local optima -- multimodality. Note: the hill climbing step was a single interchange of the first test in the order with another test.

Lichtenstein04

Yossi Lichtenstein
Puzzles in Software Development Contracting
Commun ACM V47n2(Feb 2004)pp61-65
=EXPERIENCE 17 contracts OUTSOURCING ECONOMICS
All fixed price contracts with 2..3 month milestones.
Doesn't fit economic agency or transaction cost theories.

LichtensteinPnueli00

Orna Lichtenstein and Amir Pnueli
Propositional Temporal Logics: Decidability and Completeness
Logic Journal of the IGPL V8n1(Jan 2000)pp55-85 [ #Lichtenstein ]
=THEORY FORMAL LOGIC TIME PTL
=HISTORY 20 years
axioms etc complete and sound relative model, decision procedure using semantic tableau.
time with a beginning. Basic modal operators: Next, Until, Weak_previous, Since. Defines half-a-dozen others. [ PTL in logic_9_Modalities ]

Lichteretal95

Horst Lichter & Matthias schneider-Hufschmidt & Heinz Zullighoven
Prototyping in Industrial software Projects - Bridging the Gap between Theory and Practice
IEEE Trans SE VSE-20n11(Nov 1994)pp825-831
=EXPERIENCE PROTOTYPING

LieSaarela

Hakon Wium Lie & Janne Saarela
Multipurpose Web Publishing: using HTML, XML, and CSS
Commun ACM V42n10(Oct 1999)pp95-101
=EXAMPLES WEB/NET Class AttributeA RDF SMIL HTML4.0 CSS2

LieberherrXiao93

Karl J Lieberherr & Cun Xiao
Object Oriented Software Evolution
IEEE Trans SE-V19n4(Apr 1993)pp313-343 See [LieberherrXiao94]
=ESSAY OBJECT-ORIENTATION

LieberherrXiao94

Karl J Lieberherr & Cun Xiao
Adaptive Object-Oriented Programming Using Graph-Based Customization
Comm ACM V37n5(May 1994)pp94-101
=ESSAY OBJECT-ORIENTATION

LiebermanFry01

Henry Lieberman & Christopher Fry
Will Software Ever Work
Commun ACM V44n3(Mar 2001)pp122-124 + Letters v44n8(aug 2001)pp12-13 + V44n8(Aug 2001)pp12-13
=ESSAY USER fixes BUGS
Bug removal and advoidance costs too much. Instead enable the user to figure out, work round, and fix bugs.

Lifschitz95

Vladimir Lifschitz
The Logic of Common Sense
ACM Computer Surveys V27n3(Sep 1995)pp343-345
=SURVEY AI Logic defaults inertia

Lilly99

Susan Lilly
Use-Case pitfalls: top 10 problems
IEEE CS TOOLS USA 99 (1999)
=EXPERIENCE USECASE SCENARIO REQUIREMENTS
fuzzy boundary, system's view, actor names inconsistent, too many, spiders web, scenario too long, confusing, actors entitled to too much, user doesn't understand, unfinished .See [Lilly00]

Lilly00

Susan Lilly
How to avoid Use-Case pitfalls
Software Development Magazine V8n1 (Jan 2000)pp40-44
=EXPERIENCE USECASE SCENARIO REQUIREMENTS
see [Lilly99]
clear boundary, templates, focus on goals, avoid CRUD & screens & design, reviews

Lim94

Wayne C Lim(HP)
Effects of Reuse on Quality & Productivity & Economics
IEEE Software Magazine V11n5(Sep 1994)pp23-30
=ESSAY REUSE QUALITY COSTS ECONOMICS

Limoncelli11

Thomas A Limoncelli
A plea from sysadmins to software vendors:10 do's and don'ts
Commun ACM V54n2(Feb 2011)pp50-51 [ 1897816.1897835 ]
=ADVICE SYSTEMS ADMINISTRATORS HCI API
A short, beautifully written list of dos and don'ts when programming the HCI for administrators.
Have a silent instal option.
Don't force the sysadmin to use a GUI.
Make an API so that it works remotely.
Configuration files should be in ASCII! Let them be under version control.
Include clear ways to restore every thing, restore one user, and one single item.
Instrument the system so we can diagnose problems.
Tell us about security problems first -- before the fix!
Use Existing logging frameworks and technology.
Be tidy: all binaries here, all configuration here, all data here.
Publish documentation/manuals on the web in HTML so it is linkable! And never ever delete them.

LiMukesh07

Huaizhi Li & Mukesh Singhal
Trust Management in Distributed Systems
IEEE Computer Magazine V40n2(Feb 2007)pp45-53
=SURVEY DISTRIBUTED TRUST CyberTrust P2P duckling TrustMe ecommerce ADHOC NET confidant eBay Amazon Sporas
When is trust transitive?
satisfaction, malice, selfishness
Evidence vs Recommendation
12 references, half-a-dozen systems described, half-a-dozen research issues.

Lin93

Huimin Lin(Beijing)
Procedural Implementation of Algebraic Specification
ACM Trans. Program Lang. Syst V15n5 (Nov 1993)pp876-895 CR 94090637
=THEORY SPECIFICATION ADT FUNCTIONS
1. f(g(h))) +-> h(a);g(a,b);f(b,c) Defines a set of observables that describe how free the algebraic spec,
  An implementation is correct if it satisfies the algebra and never make equivalent two observable results that can not be shown to be equal in the spec.
  shows that if observables are those generated by a subset of functions then proofs are finite

Lin06

Frank Lin
The concerns of innovation in organizations: a comparison of managerial and end-user perspectives and an Individual's Stages of concern
IDS Seminar, CBPA CSUSB (Jan 20 2006)
=EXPERIENCE CHINA PHARMACEUTICAL ERP
Senior manager see things differently.
China less positive than US.
Concern-Based Adoption Model,
CBAM::= awareness; informational; personal; management; consequence; collaboration; refocusing.

LindigSnelting97

Christian Lindig & Gregor Snelting
Assessing Modular Structure of Legacy Code Based on Mathematical Concept Analysis
[ICSE'97]
=EXPERIENCE FORMAL CONCEPT ANAYSIS LEGACY CODE
Analysis of retion between pieces of code and shared/global variables. new definition of module. works better on Modular than FORTRAN or COBOL legacy code. [Snelting96]

LindlandSundreSolvberg94

Odd Ivar Lindland & Guttorm Sundre & Arne Solvberg
Understanding Quality in Conceptual Modeling
IEEE Software magazine v11n2(Mar 1994)pp42-49
=ESSAY REQUIREMENTS QUALITY
1. hence definitions of quality in terms of the fit at the three interfaces" - whenever feasible
2. feasible: it is worth less to fix than it costs to fix
  "The goal is not to make the model easy to understand but to ensure that it is understood"
  "Always need some gut instinct" to judge feasibility.

Lindley08

David Lindley
The Limits of Computability
Commun ACM V51n11(Nov 2008)pp17-19 [ 1400214.1400219 ]
=SURVEY THEORY P=NP SUDOKU HARD Nash Equilibria Brains NEUROSCIENCE
Interesting problems have solutions that are easy to check, but not before you have found one.

Lindstrom93

David R Lindsrom
Five ways to Destroy a Development Project
IEEE Software Magazine V10n5(Sep 1993)pp55-58
=ANECDOTES RISKS
1. Inadequate front end work
2. Inadequate tracing, tracking and management
3. Improper sizing (performance)
4. Weak modularization
5. No metrics for management

Lindvall04

Mikael Lindvall & Dirk Muthig &Aldo Dagnino& Christina Wallin & Michael Stupperich & David Kiefer & John May & Tuomo Kahkonen
Agile Software Development in large organizations
IEEE Computer Magazine V37n12(Dec 2004)pp26-3
=POLL AGILE TECHNICAL PROCESS ONESIZE XP ABB DaimlerChrysler Motorola Nokia
Reports on meetings where several pilot XP projects were discussed
XP adopted in large organizations for the same business reasons as small ones: need to increase productivity without losing quality .
Problems with specifications becoming obsolete before project finished.
XP always needed customization.
It produced good or better software more quickly.
Changes were handled faster.
Morale was better.
But XP doesn't fit well with existing practices in large organizations and so has to be tailored.
Make it look like a CMM process.
Change control boards do not work well with refactoring, continuous integration, Problems when XP team is not in one place.
Problems with interfaces between XP team and Traditional team.
Architecture is important.
Clash between up-front top-down planning and XP planning game.
Requirements were already inaccurate when XP started and were not user stories.
Continuous testing vs an added round of acceptance tests done by a different team.
XP pairing vs formal reviews for SQA.
Management and QC want the old documentation and XP doesn't do documentation.
(dick)|-write a user story for each required piece of documentation and do the planning game on it. "That will take us 2 days work, ..."

LindvalRus00

Mikael Lindval & Ioana Rus
Process Diversity in Software Development
IEEE Software Magazine V17n3(Jul/Aug 2000)pp14-18
=SURVEY PROCESS BIBLIOGRAPHY
"A 'one size fits all' doesn't work".
Know sitution and the options.

Linger94

Richard C Linger
Cleanroom Process Model
IEEE Software magazine v11n2(Mar 1994)pp50-58
=ADVERT PROCESS INCREMENTAL SQA functional refinement
1. Quick and clean
2. errors found in tests down from 40/KLOC to 2.3/KLOC
3. errors left in are simple mistakes found by statistical testing
4. Pipeline of increments developed and certified by small independent teams... refinements predefined by previous increment... correctness verification... prototypes when in doubt of requirements
5. functional specification;plan increments;design and verify; certify quality vs statistical tests, feedback
6. top-down testing
7. Box structures: Black;State;Clear
8. Usage testing: all executions by users, high usage, lage number of tests
9. helps predict actual MTTF in the field
10. gives better MTTF than coverage testing

LingerTrammell99

Richard C Linger & Carmen J Trammell
Cleanroom Software Engineering:Theory & Practice
In [HincheyBowen99] pp351-372
=ADVERT Cleanroom CMM

LinnClancy92

Marcia C. Linn & Michael J Clancy
The Case for Case studies of Programming Problems
Commun ACM V35n3(Mar 1992)pp121-132
=EDUCATION PROGRAMMING
(p130) "Writing a computer program is less helpful than having an expert commentary for developping design skills"

LinialLondonRabinovich95

N Linial & E London & V Rabinovich
The Geometry of Graphs and some of its algorithmic applications
Combinatorics V15n2(1995) pp215-245, ref in Watts99 p39.
=UNREAD =THEORY GRAPH ALGORITHM multidimensional scaling
For G:Graph, i,j: G.nodes, G.d(i,j)::= length of the shortest path in G from i to j
For G:graph, c:distortion, embedding_dimension(G, c)::= least{n. for some f:G.nodes->Real^n, all i,j:G.nodes( G.d(i,j)/c <= distance(f(i)-f(j)) < G.d(i,j))}.
Any graph with N vertices can be embedded in Real^O(log N ) with distortion O(log N ).

Linton84

?? Linton
Implementing relational views of programs
ACM SIGSOFT notes v9 n3 & ACM SIGPLAN Notices v19 n5 (May 1984) pp132-140
=DEMO data

Lipkin99

Berenice S Lipkin
LaTeX for Linux: A Vade Mecum
Springer Z 253.4.L38L56 1999 ISBN 0-387-98708-8
=MANUAL LaTeX

Lippman99

Stanley Lippman
Essential C++ (C++ In-Depth Series)
Addison-Wesley1999 ISBN 0201485184 ; QA76.73.C153 L577
=TEXT C++

LippertEtal03

Martin Lippert & Petra Beck-Pechau & Jorn Koch & Andreas Kornstadt & Stefan Roock & Axel Schmolitzky & Henning Wolf & Heinz Zullighoven
developing complex Projects using XP with Extensions
IEEE Computer Magazine V36n6(Jun 2003)pp67-73
=EXPERIENCE AGILE XP one-size IT-workplace-solutions

LippertAnandarajan04

Susan K Lippert & Murugan Anandarajan
Academic vs. practitioner systems planning and analysis
Commun ACM V47n9(Sep 2004)pp91-94
=SURVEY INFORMATION SYSTEMS RESEARCH
Studied samples abstracts from 13 journals 1970..1990 & 1991..2002 read?writt en by practitioners or academics.
Practitioners tended to research about needed skills(32/264), methods(116/264), and tools(53/264). Academics tended research about planning(123/269).
Both shifted toward methods(30->145) and tools(21->60) in the later period. Academics increasedresearch on needed skills(9->18) and requirements(2->12) but practitioners did the reverse(28->4 and3->1).
Claims the gaps are causing problems.

LiShawHerbslebRaySanthnanam04

Paul Luo Li & Mary Shaw & Jim Herbsleb & Bonnie Ray & P Santhnanam
Empirical evaluation of Defect Projection models for widely-deployed production software systems
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp263-272
=EMPIRICAL STATISTICS DEFECTS COTS Tomcat OpenBSD Weibull
Gathered data about user reported defects in open and closed source code projects.
Rate of defects in each release vs time in release.
Found that Weibull work better than most models with Gamma a rival.
For Time t, defect_rate(t)::= N* α* β * t**(α-1) * exp(β * t**α).
Did not find a simple way to predict the parameters of each release.

LiSmidts03

Ming Li & Carol S Smidts
A Ranking of Software engineering measures based on expert opinion
IEEE Trans Software Engineering V29n9(Sep 2003)pp811-824
=POLL 10 EXPERTS RANKING 30 METRICS 7 QUALITIES PHASES
Note: More information is available when testing than any other phase.

Top_3_measures_per_phase::=following,
Table

Requirements	Design Implementation Testing.Row Fault density	Design defect density	Code defect density	Failure rat e.Row Requirements spec change rate Cyclomatic complexity Design defect densi ty code defect density
Error distribution Fault density	Cyclomatic complexity	Coverage factor

(Close Table)

LiskovGuttag86

B Liskov & J Guttag
Abstraction and Specification in Program Development
MIT Press Cambridge MA 1986
=THEORY non-sequential ADTs

LiskovWing94

Barbara H Liskov & Jeanette M Wing
A Behavioral notion of Subtyping
ACM Trans Prog Lang Sys V16n2(Nov 1994)pp1811-1841 CR9606-0432
=theory objects genericity

LiskovZilles75

Barbara Liskov & ?? Zilles
Specification techniques for data abstraction
IEEE trans on Software Eng SE-1 1 (Mar 1975) pp7-19
=THEORY ADTs

Little04

Todd Little
Value creation and capture: a model. of the software development process
IEEE Software Magazine V21n3(May/Jun 2004)pp48-53
=EXPERIENCE AGILE ECONOMICS ROI
Notes

Little05

Todd Little
Context-adaptive agility: managing complexity and uncertainty
IEEE Software Magazine V22n3(May/Jun 2005)pp28-35
=PRACTICE ONESIZE PROJECT -> PROCESS AGILE landmark
Classify projects as Skunks, Dogs, colts,Cows and Bulls.
Table
Project Simple Complex
Uncertain Colt Bull
Certain Skunk/Dog Cow

(Close Table)
A Skunk is typically a prototype but a Dog is a mature project.
Projects change state. 3 common trajectories. Skunk->Colt->Dog, Skunk->Colt-> Bull->Cow->Dog, Bull->Cow->Dog.
Fit the process to the animal. Core practices + adaptions.
Core Practice: product plan,prioritize requirements, quality targets, continuous integration, involve experts users, Project Dashboard.
Project_dashboard:=web-based project status updated weekly.
Colts benefit from short iterations, daily stand up meetings, and automated testing.
Cows need more rigorous management tools and procedures: CPM, subprojects, teams coordinated by Scrum, functional specs of interfaces,...
Bulls need BOTH Colt and Cow practices. They need the best experienced managers.
Has several process and project metrics.

Project	Simple	Complex
Uncertain	Colt	Bull
Certain	Skunk/Dog	Cow

LittleGibson03

Robert Grover Little Jr & Michael Lucas Gibson
Perceived influences on implementing data warehousing
IEEE Trans Software Engineering V29n4(Apr 2003)pp193-288
=POLL Data warehouse mining MANAGEMENT

Littlewood00

Bev Littlewood
The Use of Proof in Diversity Arguments
IEEE Trans Software Engineering V26n9(Sep 2000)pp921-1023
=THEORY RISKS PROBABILITY PROOF BAYES
Compare system with [PetersParnas00]
Multiple versions don't give increased reliability because of lack of independence between version.
However, if there is a primary system (A) and a simpler secondary system (B) that is likely to be perfect.
(above)|-P ( AB fails ) = P ( Afails and Bfails ) .
|-if not Bperfect then if Bfails then Afails,
|- (Littlewood00_1): P ( Afails ) = P ( Afails | not Bperfect )
|- (Littlewood00_2): if Bperfect then not ABfails.
(probability_theory)|-P ( ABfails ) = P ( ABfails | Bperfect ) * P ( Bperfect ) + P ( ABfails | not Bperfect ) * P ( not Bperfect ),
(Littlewood00_2)|-P ( AB fails ) = P ( ABfails | not Bperfect ) * P ( not Bperfect ),
(Littlewood00_1)|-P ( AB fails ) = P ( Afails ) * P ( not Bperfect ).

LittlewoodEtal00

Bev Littlewood & Peter T Popov & Lorenzo Strigini & Nick Shryane
Modeling the effects of combining diverse software fault detection techniques
IEEE Trans Software Engineering V26n12(Dec 2000)pp1157-1167
=THEORY MATHEMATCS PROBABILLITY ERROR TEST SQA CASESTUDY
Diversity is a good thing

LittlewoodStrigini92

Bev Littlewood & Lorenzo Strigini
The Risks of Software
Scientific American November 1992 pages 62-75
=REPORT RISKs Patriot Missile everyday Telephone services

LittlewoodWright97

Bev Littlewood & David Wright
Some Conservative Stopping Rules for the Operational Testing of Safety-Critical Software
IEEE Trans SE V23n11(Nov 1997)pp673-683
=THEORY SQA RISKS Baye's theorem gives stopping rule that allows for previous successes

LittlewoodWright07

Bev Littlewood & David Wright
The Use of Multilegged Arguments to increase confidence in safety claims for software-Based Systems: A Study based on a BBN Analysis of an idealized example
IEEE Trans Software Engineering V33n5(May 2007)pp347-365
=EXAMPLE THEORY RELIABILITY RISKS Arguments BAYES PROBABILITY BBN CAUSALITY SPECIFICATION CORRECTNESS TESTING
When should two different arguments for the safety of a system increase our belief that a system is safe?
Answer: when the arguments do not depend (too much) on a common source of defects.
Compare with the simpler [Littlewood00] example.
Example BBN:=following,
Net
1. Z: random_variable(Bit)= specification is correct
2. O: random_variable(Bit)= test oracle is correct
3. S: random_variable(Beta_distribution(0,1,...)) = probability of failure on demand.
4. T: random_variable(Bit)= probability of failure during testing.
5. V: random_variable(Bit)= formal verification proves correctness.
6. C: random_variable(Bit) = Claim that system is fit for use should be accepted.
  Dependencies:= (Z+>O | Z+>S | Z+>V | O+>T | S+> T | S+>V | T+>C | V+>C ).
  Example dependency: the correctness of the oracle O depends on the correctness of the specification (Z).
  Example dependency: the parameters of the distribution of S depend on whether the specification is correct(Z).
  In general, for each dependency XY+>W tabulate for each X&Y value the probability of each W value given the XY values. If W is a continuous random variable then tabulate the probability density functions. The table is called a conditional probability table. See paper for a large example.
7. A BBN implicitly defines a set of Conditional_independencies.
  Example Conditional_independencies:= following,
  Table
  Independent 0f Given
  O S V Z
  T Z V O S
  C O S Z V T
  
  (Close Table)
  So: if Z is given then O is independent of S and V.
8. CI::BBN=conditionally_independent, two events are independent under certain conditions.
9. conditionally_independent(A,B,C)::BBN= ( Pr(A B C) = Pr(A|C) Pr(B|C) Pr(C) ).
10. ...
11. Bayes's formula allows us to calculate the distribution of S and C given that T and V are true, see Bayes_theorem.
(End of Net)

Independent	0f	Given
O	S V	Z
T	Z V	O S
C	O S Z	V T

Liu02

Kechend Liu
Semiotics in Information Systems development
Cambridge UP 2000 ISBN 0-521-59335 2 QA76.9 S88 L58 2000 CR 0106-0203
=MONOGRAPH REQUIREMENTS SPECIFICATION SEMANTICS MEASUR NORMA LEGOL

LiuChanNosek08

Kim Man Lui & Keith C C Chan & John Teofil Nosek
The Effect of pairs in program design Tasks
IEEE Trans Software Engineering V34n2(Mar/Apr 2008)pp197-211
=EXPERIMENT PAIR PROGRAMMING vs LONE PROGRAMMING APTITUDE
Used aptitude tests to act as a surogate for programming and eliminate language skill effects.
Pairs substantially outperformed individuals in procedural/algorithmic design tasks.
Pairs substantially outperformed individuals in deductive problem solving.
Fewer errors. Faster time.

LiuEtAl12

Hui Liu & Zhiyi Ma & Weizhong Shao & Zhendong Niu
Schedule of Bad Smell Detection and Resolution: A new way to save effort
IEEE Trans on Software Eng VSE-38n1(Jan/Feb 2012)pp220-235
=THEORY REFACTORING TECHNICAL CODE IMPROVEMENT SMELLS METHOD
Proposes an efficient sequence for finding and fixing smelly code.
Sells::={duplicated_code, long_method, large_class, long_parameter_list, feature_envy, useless_field, useless_method, useless_class} | primitive_obsession,
primitive_obsession::={simple_primitive_obsession, simple_type_code, complex_type_code}.
sequence expressesd as "do _ before _".

Figure 8 as a table
Table

Do before	Do after
useless_class	useless_method
useless_method	duplicate_code, useless_field
duplicate_code	feature_envy, simple_primitive_obsession, complex_type_code, simple_type_code
feature_envy, simple_primitive_obsession, complex_type_code	long_method
long_method, simple_type_code	large class
large_class	long_parameter_list

(Close Table)

LiuFeketeGorton05

Yan Liu & Alan Fekete & Ian Gorton
Design-level Performance Prediction of Component-Base Applications
IEEE Trans Software Engineering V31n11(Nov 2005)pp928-941
=SIMULATION =THEORY QUEUE COMPONENTS PERFORMANCE EJB QNM
Derives a queuing theory performance model for various kinds of transactions.
Models calibrated by a very simple benchmark on two platforms.
Models combined with a sequence diagram model of an application to predict performance.
The predictions compares well with a simulation of the application.
The predictions allow the selection of the better of two possible designs.
No code is needed in to make the predictions.
(dick)|-SSADM Physical Design Control used quantified models of DBMSs and application designs to select a physical design that was likely to perform well in 1979.

LiuHorowitz89

Lung-Chun Liu & Ellis Horowitz
A Formal Model for Software Project Management
IEEE Trans Soft Eng vSE-15n10(Oct 1989)pp1280-1293
=THEORY PROCESS MODEL PETRIE NET AND/OR
process modeling: typed petrie nets+ AND/OR graphs

LiuOffuttEtal98

Shaoying Liu & A Jeff Offut & Chris Ho-Stuart & Yong Sun & Mitsuru Ohba
SOFL: A Formal Engineering Methodology for Industrial Application
IEEE Trans Soft Eng V24n1(Jan 1998)pp24-45
=DEMO PROCESS LANGUAGE INSPECTIONs
SOFL::="Structure Object-based Formal Language".
CDFD::="condition data flow diagram".
dynamic development

LiuStork00

Ziming Liu & David G Stork
Is Paperless Really More
Commun ACM V43n11(Nov 2000)pp94-97
=ESSAY TECHNOLOGY
Several refs to statistics and data.
Technology is only a part of a social-material complex.
New technology does not destroy the old. They stimulate a synergy between old and new.
Paper is easier to move, organize, read, annotate, and copy across platforms.
Documents have long lives so need paper.
Paper consumption is increasing, photocopying decreasing.

LiuWeiner73

L-Y Liu & Peter Weiner
An Infinite Hierarchy of Intersections of Context-Free Languages
J Math Systems Theory V7 n2 pp185-192
=THEORY language non-sequential

Lobur11

Julia M Lobur
The success of a COTS caseload management system in state government
IEEE Software Magazine V27n6(Mar/Apr 2011)pp10-14
=EXPERIENCE COMPONENT PEOPLE FEAR MANAGEMENT DISABILITY WORKFLOW
Project survives departure of manager.
IT team becomes part of the user group.
Focus groups think creatively about what the product can do, and what else it could do to fit the organization. The focus groups become advocates and trainers during roll out.
They had to overcome computer phobia and hatred. Some users retired rather than change.
Technically the project failed because it took 4 times the allocated time, but everybody felt it had succeeded because it made a big improvement.

LocascioDarpel93

Capt Charles J Locascio & 2Lt Mathew M darpel
Software Reengineering for the Future with Ada
IEEE Computer Society Reverse Engineering Newsletter n5&6(Dec 1993)pp4-5
=EXPERIENCE LEGACY COBOL JCL RENGINEERING Ada DFD REQUIREMENTS
1. Prelimnary Object Encyclopedia"
2. OOD
3. Advanced CASE Technology
4. Design Based Maintenance(DBM) : Design+Code is one thing.
5. Teamwork DSE(Design sensitive Editor)
6. Ada Structure Graphs(ASGs)
7. reuse: Booch components, 100s of generic packages, domain library
  Ada Helped.

LocascioDarpelMailley94

Capt Charles J Locascio & 1Lt Mathew M Darpel & 2Lt Jeffrey R Mailley(USAF)
Software Reengineering for the Future with Ada: Results and lessons learned
IEEE Computer Society Reverse Engineering Newsletter n7(Sep 1994)pp2-5
=EXPERIENCE RE-ENGINEERING EXPERIENCE Ada OO MAINTENANCE
IDCT::=iterative design-code-test phase. Payoff from objects and abstraction. maintaining so far so good.
1. Direct benefits to customer, Reduced Trainging time by using CASE etc tools, 60..70% reusability, can predict maintenance workload, Improved Maintainer morale
  LESSONS
2. The customers support and involvement, prepare before you get CASE, know what they say can't be done & research it until it can be done, management support is crucial, Discipline and Personal commitmment go a long way.

Lockwood00

Lucy Lockwood
Ugly GUI? Blame the Developers
Software Development Magazine V8n7(Jul 2000)pp80+78-79
=EXPERIENCES USER DESIGN
Manager must integrate usability (design..testing) into the whole development process.
One successful method is for a team that includes designers and programmers to develop the user interface as a team lead by an usability expert.

LogrippoRice83

?? Logrippo && ?? Rice
File Structures, Program Structures, and Attributed Grammars
IEEE Trans on Software Eng SE-9 3 (May 1983) pp260-266
=DEMO DDD DP

Loh10

Eugene Loh
The ideal HPC programming language
Commun ACM V53n6(Jun 2010)pp42-47 [ 1785414.1785434 ]
=EXPERIMENT PERFORMANCE READABILITY TECHNICAL CODE HPC FORTRAN
Ask people in high performance computing (HPC) to write algorithms and they write high=level FORTRAN.
Rewriting bench marks to be more readable and marking up the language leads to smaller FORTRAN code that is roughly twice as slow.

Lohr93

Concurrency Annotations for Reusable Software
Comm ACM V36n9(Sep 1993)pp81-89
=ADVERT LANGUAGE OBJECT-ORIENTED NONSEQUENTIAL
COOL::=Concurrent object-oriented language. Degrees of integration
1. 1. None
  2. Partial - synchronized, active,... objects. Not inheritted
  3. Full Integration. Inheritance hierarchies of active classes (POOL)

Lomet76

?? Lomet
Objects & values:The basis of a storage model for procedural languages
IBM J R & D V20 n2 (Mar 1976) pp157-167
=DEMO Technical

Long78

Chris Long
Logical
=LETTER ENGLISH LOGIC ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) (Mar 16 1978)p20
You can write English logically!

Long01

John Long <j1long@us.ibm.com>
Software Reuse Antipatterns
ACM SIGSOFT Software Engineering Notes V26n4(Jul 2001)pp68-76
=EXPERIENCE NEGATIVE ANTI-PATTERNS REUSE
reuse_antipatterns = { Field_of_Dreams, Garbage_Dump, Abracadabra, High_noon, Used_car_Fiasco, Hunter_Gatherer, One_size_fits_all, Domain_Analysis_Paralysis, Object_Explosion, Of_Course_its_Reusable, The_Cost_Cutter }.
(Dick)|-excellent descriptions
points to a set of good reuse patterns.
Notes problems with low quality and/or unable to find and/or unrewarded components.

LongDenning95

Jeffrey G. Long<jlong@seas.gwu.edu> & Dorothy E Denning <denning@cs.georgetown.edu>
Ultra-structure: A Design Theory for Complex Systems and Processes
Commun ACM V38n1(Jan 1995)pp103-120 CR9603-0204 H.2.1
=EXPERIENCE REALITY DATA TABULAR RULES ENGINES
reality data maintainability: tables are used to represent rules rather than objects/relations/procedures and Complex Operating Ruleform Engines animate the tables as an operating rule
[MittermeirOppitz87]

LongoMilstedSoloviev92

Giuseppe Long & Kathleen Milsted & Sergei Soloviev
The Genericity Theorem and the Notion of Parametricity in the Polymorphic λ-calculus
DEC Paris Research Lab TR21(Dec 1992)
=THEORY Lambda

Lopes12

Crista Videira Lopes
Research in Programming Languages
Tagide(Mar 2 2012) [ http://tagide.com/blog/2012/03/research-in-programming-languages/ ]
=BLOG =IDEA =DISCUSSION PROGRAMMING LANGUAGES TECHNICAL RESEARCH INVENTION EXPERIENCE
Observes that the research in programming languages has not produced new ideas for several decades, and that new languages (PHP, JavaScript, Python, Ruby, etc.) are not coming out of academe.
Also digresses to observe that STEM research (funded in the USA at the national level) excludes developing new software unless it is for some real Science, Engineering, or Mathematics research. Quote
2. there appears to be no correlation between the success of a programming language and its emergence in the form of someone�s doctoral or post-doctoral work.
quote
2. a reliable implementation of a language that addresses an important practical need is the key for the popularity of a programming language.
quote
2. In experimental design research, one can have hopes or expectations about the effects of the system, and those must be clearly articulated, but very few certainties will likely come out of such type of work.
Also see [ new-programming-languages-come-from-designers ] (SlashDot).

Lopez-GraoMerseguerCampos04

Juan Pablo Lopez-Grao & Jose Merseguer & Javier Campos
From UML Activity diagrams to stochastic Petri nets: application to software performance engineering
WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp25-36
=DEMO PERFORMANCE TOOL UML Petri LGSPN
LGSPN::="Labeled Generalized Stochastic Petri Net".

LorentzBenson83

?? Lorentz & ?? Benson
deterministic & nondeterministic flowchart interpretations
Jnl of Computer & Sys Science 27 3 (Dec 1983) pp400-433
=THEORY non-sequential Technical

Lorenz93

Mark Lorenz
Object Oriented Software Development: A Practical Guide
Prentice Hall Englewood Cliffs NJ 1993 Reviewed IEEE Software magazine v11n2(Mar 1994) CR9502-0058
=HOWTO OBJECT-ORIENTED

LorenzKidd9X

Mark Lorenz & Jeff Kidd
Object-oriented Software Metrics
Prentice Hall Englewood Cliffs NJ 199X ISBN 0-13-179292-X
=TEXT METRICS OBJECT-ORIENTED

Lott97

Christopher M Lott
Breathing New life into the Waterfall Model
IEEE Software Magazine V14n5(Sep 1997)pp103-105
=EXPERIENCE SEQUENTIAL with failure Process
staged contracts
analysis followed by design!

Loui08

Ronald P. Loui
A Modest Proposal for Annotating the Dialectical State of a Dispute
SCRIPTed V5n1(2008)#176 [ loui.asp ]
=ESSAY REBUTS Toulmin diagrams KISS RATIONALE
[ToulminRiekeJanik78]
Just list the data for a conclusion underneath the conclusion with the rebuttals etc ?(hidden) beside them.
Or use a simple tree diagram: children support parents and rebuttals have a heavy horizontal link to what they rebut.

LouridasLoucopolis00

Panagotis Louridas & Pericles Loucopolis
A Generic Model for Reflective Design
ACM TOSEM Trans Software Engineering & Methodology V9n2(Apr 2000)pp199-237
=MODEL DESIGN RATIONALE vs PROCESS

Louridas06

Panagiotis Louridas
Using Wikis in Software Development
IEEE Software Magazine V23n2(Mar/Apr 2006)pp88-91
=ADVERT TOOLS WIKIWIKIWEB COLLABORATION CASE HTML twiki confluence usemod moinmoin wikish mediawiki
Wiki webs are a simple tool that encourage communication and collaboration in a project -- end can handle time shifting and distributed teams.

Louridas06a

Pangiotis Louridas
SOAP and web services
IEEE Computer Magazine V39n10(Oct 2006)pp62-67
=DEMO SOAP WSDL XML Schema Stirling performance
Resources on page 63

Louridas08

Panagiotis Louridas
Orchestrating web services with BPEL
IEEE Software Magazine V25n2(Mar/Apr 2008)pp85-87
=ADVERT BPEL XML PROCESS WEB/NET SERVICES
BPEL::xml= "Business Process Execution Language"
36 line "Hello World".
p87: Lists resources.
process:=partner_links; variables; fault_handlers; sequence.
First understand the business requirements.

LouridasSpinellisVlachos08

Panagiotis Louridas & Diomedis Spinellis & Vasileos Vlachos
Power Laws in Software
ACM TOSEM Trans Software Eng & Methodology V18n1(Sep 2008)#2pp1-26 [ 1391984.1391986 ] published Sep 2008
=ANALYSIS CODE STATISTICS POWER LAWS MODULES CLASSES FUNCTIONS REFERENCES Java Ruby PERL TEX C++ Linux Fat Tail
One piece of code has a number of references to other pieces of code...
One piece of code is refered to or used by other pieces of code...
Suppose we tabulated how many refrences were made to or by a module to another then we get close to a simple rule.
In a power law
P( X = x) = c * x**(-k) for some constant c and k>0.
Or equivalently we have:
P(X >= x) = c * x **(-(k+1)).
Compare [ConcasEtAl07] (not mentioned).
As a rule the distribution on references to a module has a smaller k and a better correlation.
The distribution of the number of references made by a module to others do not fit as well and k is bigger.

Love78

C G Love
Lack of Support for Loglan
=ADVERT Esperanto
Computer Weekly (UK) n598 (Mar 30 1978)p16
States that Esperanto has many speakers and political support.

Lover08

Robert Lover
Elementary Logic: for software Development
Springer Publishing NY NY (2008) ISBN 1848000812 CR 1002-0125
=UNREAD =TEXT LOGIC
Notes [click here Lover08 if you can fill this hole]

Lovgren94

John Lovgren
How to choose good metaphors
IEEE Software magazine v11n1(Jan 1994)pp86-88
=HOWTO METAPHOR XP
1. metaphor:=a partial map between two concepts.
2. All computer interfaces are metaphoric
3. USER's sphere
4. talk to the users
5. interview and process recording
6. common metaphors
7. add a few good and useful power functions
  map System>->Reality

Lowell92

Arthur J Lowell
Rapid Evolutionary development: requirements, prototyping and software creation
John Wiley& Son NYNY 1992 ISBN 0-471-53633 CR9211-0860

LoweNewcomerSekine96

H Lowe & E Newcomer & J Sekine
STDL: A Route to productivity in Distributed Processing
ACM StandView V4n4(Dec 1996)pp198-204
=DEFINITION API TECHNICAL WWW/NET NONSEQUENTIAL
STDL::=Structured Transaction Definition Language
a common API for distributed TP(Transaction Processing)

LoyStapp93

Patrick Loy & Yvonne Stapp
DFD's vs. N^2 charts
ACM SIGSOFT Software Engineering Notes V18n3(Jul 1993)ppA16-17
=DEMO DFD GRAPHIC n-SQUARED

LubarsPottsRichter93

C Lubars & Colin Potts & C Richter
A Review of the State of the Practice in Requirements Modeling
Proc Int'l Requirements Eng. Symp. (IEEE CS Press Los Alimitos CA 1993) pp2-14
=POLL REQUIREMENTS MODEL
1. From Potts93 IEEE Software Magazine V10n5(Sep 1993)pp

Lucas00

Bruce Lucas
VoiceXML for web-based distributed conversational applications
Commun ACM V43n9(Sep 2000)pp53-57
=ADVERT XML JAVA JSGF GRAMMAR BNF

LuceEtal53

R D Luce & ??
Information flow in task oriented groups
MIT Lincoln Labs Tech Report #264(1953)
=EXPERIMENT TEAM COMMUNICATION STRUCTURE PEOPLE
See [GoodeMachol57]

LuckhamEtAl87

David C Luckham & Friedrich W von Henke & Bernd Krieg-Brukner & Alf Owe
Anna, a language for annotating Ada programs: Reference manual
Springer Verlag LNCS #260 1987 [ books?id=tybCNcTXmUkC ]
=LANGUAGE ADA PROOF ANNOTATION Floyd INVARIANT ASSERTION
"... applications include not only testing, debugging and formal verification of a finished program, but also specification of program parts during the earlier stages of requirements analysis and program design."

Luckhametal91

David Luckham & Sriram Sankar & Shuzo Takahashi
Two-Dimensional Pinpointing: Debugging with formal Specifications
IEEE Software v6n1(Jan 1991)pp74-75
=DEMO FORMAL DEBUG

Luckhametal95

David C Luckham & John J Kenney & Larry M Augustin & James Vera & Doug Bryan & Walter Mann
Specification and Analysis of System Architecture Using Rapide
IEEE Trans on Software Eng VSE-21n4(Apr 1995)pp336-355
=THEORY ARCHITECTURE NONSEQUENTIAL OBJECT-ORIENTED LANGUAGE Event-based POSETs MODULES DEMO

LuckhamVera95

David c Luckham & James Vera
An Event Architecture Definition Language
=THEORY Rapide ARCHITECTURE NONSEQUENTIAL OBJECT-ORIENTED LANGUAGE Event-based POSETs MODULES DEMO
IEEE Trans SE VSE-21n9(Sep 1995)pp

LuoDasBochman94

Gang Luo & Anindya Das & Gregor v. Bochman
Software Specification Testing Based on SDL Specifications with Save
IEEE Trans SE V20n1(Jan 1994)pp72-87
=DEMO TOOL TESTING SDL SPECIFICATIONS

LupuSloman99

Emil C Lupu & Morris Sloman
Conflicts in Policy-Based Distributed Systems Management
IEEE Trans Software Engineering V25n6(Nov/Dec 1999)pp82-867
=THEORY TOOL SYSADMIN MODAL LOGIC
distinguishes policies that permit actions(A+), forbid actions(A-), require actions(O+ on event), require non-action(O-), O:=Obligation, A:=Authorisation.

Luqi92

Luqi [Sic]
Computer-Aided Prototyping for a Command-and-Control System using CAPS
IEEE Software V8n1(Jan 1992)pp56-67
=DEMO PSDL formal hard realtime constraints

LuqiGoguen97

Luqi & Joseph A Gogguen
Formal Methods: Promises and Problems
IEEE Software Magazine V14n1(Jan/Feb 1997)pp73-85
=IDEAS hyperrequirements(p83) + social context + evolution + granularity of methods and tools + Generics
CAPS::=Computer Aided Protoyping System.

LuqiRoyce92

Luqi[sic] & Winston Royce
Status Report: Computer-aided Prototyping
IEEE Software magazine V9n6(Nov 1992)pp77-81
=EXPERIENCE PROTOTYPING
see Luqi92

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.

Lussier04

Stephane Lussier
New Tricks: How Open source changed the Way My Team works
IEEE Software Magazine V21n1(Jan/Feb 2004)pp68-72
=EXPERIENCE OPEN SOURCE WINE Linux CVS
Surprise 1: code was high quality.
Surprise 2: structure and process -- developer submit small patches to mailing list, reviewers comment, the committer decides if patch should be added. Monthly releases.
Surprise 3: Developers took time to review other's code. Our code had to improve.
Surprise 4: The Wine developers were also professionals.
Lesson 1: Code review produces better code + training.
Result: borrowed structure and process. It works.

Lustman94

Francois Lustman
Specifying Transaction-Based Information Systems with Regular Expressions
IEEE Trans SE V20n3(Mar 1994)pp207-217
=THEORY REGULAR SPECIFICATION
after Babinetal91

Lutz92

Mike Lutz
OO Meets the Real World at OOPSLA'91 (report on proceedings)
IEEE Software V8n1(Jan 1991)pp92-93
=NEWS OBJECT_ORIENTED EXPERIENCES
OOP+Formal works if given the chance

Lutz96

Michael J Lutz
Consumable Mathematics for Software Engineers
IEEE Computer Magazine V29N4(Apr 1996)pp27-28
=IDEA ENGINEERING MATHEMATICS
Engineers should not be mathematicians and so need charts, handbooks, equations, that capture in a compact form the phenomenom of interest without explicit ref to the underlying axioms and theorems.

LutzBagert06

Michael J Lutz & Donald Bagert (eds)
Software Engineering Curriculum Development (Focus of Issue)
IEEE Computer Magazine V39n10(Oct 2006)pp16-61
=COLLECTION CURRICULM SOFTWARE ENGINEERING SE2004 SEEK ACCREDITATION SWEBOK DISTANCE OU OPEN SOURCE ASPECT-ORIENTED

LutzMikulski04a

Robyn R Lutz & Ines Carmen Mikulski
Ongoing Requirements Discovery in High-Integrity Systems
IEEE Software Magazine V21n2(Mar/Apr 2004)pp19-25
=EXPERIENCE 7 NASA MISSIONS 199 ANOMALIES SYSTEMS ADMINISTRATION ERRORS RISKS REQUIREMENTS ODC
Requirements are discovered and clarified after release.
See [LutzMikulski04a].

LutzMikulski04b

Robyn R Lutz & Ines Carmen Mikulski
Empirical Analysis of Safety-Critical Anomalies During Operations
IEEE Trans Software Engineering V30n3(Mar 2004)pp172-180
=EMPIRICAL EXPERIENCE 7 NASA MISSIONS 199 ANOMALIES SYSTEMS ADMINISTRATION ERRORS RISKS REQUIREMENTS ODC
Compare [LutzMikulski04a].
ODC::="Orthogonal Defect Classification", (Activity, Trigger, Target(for fix), Type).
ISA::="Incident/Surprise/Anomaly", reported by operator.
Most anomalies reported during operations. But not during critical phases.
Many (69) were problems in finding/getting data -- files not in directories.
Many were fixed by changing procedures and fixing problems with uploading data.
Sometimes: the operator's manual was changed to stress that normally something surprising could happen.
Changing requirements is part of operations. Hardware decays in space. Hidden requirements discovered in use.
(dick)|-System administration is part of the software and needs care and attention. Admin procedures are programs too: precondition, postconditions, and invariants!

LutzWong92

Robyn R Lutz & Johnny S K Wong
Detecting unsafe Error Recovery schedules
IEEE Tran SE-V18 n8(Aug 1992)pp749-760
=THEORY concurrency formal SQA

LwgrenStolterman04

Jonas Lwgren & Erik Stolterman
Thoughtful interaction design: A design perspective on information technology
MIT Press Cambridge MA 2004 ISBN 0262122715 CR 0706-0554
=UNREAD USER DESIGN

LycettEtal03

Mark Lycett & Robert D Macredie & Chaitali Patel & Ray J Paul
Migrating Agile Methods to Standardized Development practice
IEEE Computer Magazine V36n6(Jun 2003)pp79-85
=EXPERIENCE AGILE embedded in SEQUENTIAL PLANNED PROCESS RUP in CMM PATTERNS one-size
disclaimer: authors from my Alma Mata.
Problems with embedding iterative RUP into a hierarchical planned organization pursuing CMM certification.
Proposed situational process model to evolve catalog of situation><practice patterns because CMM audit needs documented practices.
Used RUP UML process modeling.

LynchHorton01

Patric J Lynch & Sarah Horton
Web Style Guide
Yale UP 2002 ISBN 0-300-09682-8
=MANUAL VISUAL GRAPHIC STYLE TYPOGRAPHY LAYOUT WEB/NET

Lyon12

Doug Lyon
The Java Tree Withers
IEEE Computer Magazine V45n1(Jan 2012)pp-83-85
=ANECDOTE =ANALYSIS JAVA SOURCE CODE DEPRECATION OBSOLESCENCE FOSSIL FRAMEWORKS REUSE FAILURE JAVAFX ORACLE
The rate of depreciation of features in Java Frameworks and the lack of support by Oracle for some frameworks indicates a bad future for Java.

LyytinenYoo02

Kalle Lyytinen & Youngjin Yoo (eds)
Issues and challenges in Ubiquitous Computing
Commun ACM V45n12(Dec 2002)pp63-96
=REPORT =WORKSHOP UBIQUITOUS PERVASIVE MOBILE INVISIBLE PEOPLE SYSTEM
1. Introduction
2. Anytime/Anyplace Computing and the Future of Knowledge Work, Gordon P Davis
3. Group Dynamics and Ubiquitous computing, Jonathan Grudin
4. New frontiers of Applications Design, Daniel P Siewiorek
5. The Future of Business Services in the Age of Ubiquitous Computing, Andrew Fano & Anatole Gershman
6. The Relevance of Social Issues in Ubiquitous Computing, Leanard M Jessup & Daniel Robey
7. Software Infrastrcture and Design Challenges for Ubiquitous Computing Applications, Guruduth Banavar & Abrham Bernstein

MaarekBerryKaiser91

An Information Retrieval Approach For Automatically Constructing Software Libraries
IEEE Trans SE-17n8(Aug 1991)pp800-813
=DEMO REUSE

MacalaStuckeyGross96

Randall R Macala & Lyn D stuckey Jr and David C Gross
Managing Domain-Specific Product-line development
IEEE Software Magazine V13N3(May 1996)pp57-67
=EXPERIENCE REUSE ARCHITECTURE DOMAIN TOOLS PEOPLE
Document the current situation: SYSTEM!

Macauley96

Linda A Macauley(UMIST)
Requirements Engineering
Springer Verlag London UK 1996 $34.95 ISBN 3-540-76006-7
=SURVEY REQUIREMENTS METHODS
seven different customer-supplier relations with different RE processes

MacauleyMylopoulos96

Linda Macaulay & John Mylopoulos
Requirements Engineering: An Educational Dilemma
IEEE TCSE Committee on Software Engineering Education News n5(Wint 1995-96)pp EN-1..2
=EDUCATION REQUIREMENTS
Requirements not isolated, complete, fixed...

MacCormackKemererCusumanoCrandall03

Alan MacCormack & Chris F Kemerer & Michael Cusumano & Bill Crandall
Trade-offs between Productivity and Quality in Selecting Software Development Practices
IEEE Software Magazine V20n5(Sep/Oct 2003)pp78-85
=POLL HP PROJECTS 2000-2001 TECHNIQUES QUALITIES STATISTICS ONE-SIZE
Defect rate:= customer reported defects per LoC per month of use.
Productivity:= LoC per month of development
Significant Correlations:
Net
1. Systems projects had a larger defect rate.
2. Larger systems had a lower defect rate and higher productivity.
3. A complete functional specification increases productivity.
4. Customers using a more incomplete prototype decreased the defect rate and productivity.
5. Design reviews reduce defect rate.
(End of Net)
Best_fit models:
defect_rate= 16+15*system+0.5*prototype_completeness-12*regression testing-20*use_reviews.
productivity= 35-0..4*prototype_completeness+17*daily_builds.
Conclusion: one size does not fit all. Choose coherent set of practices to meet desired qualities.

MacDonellKitchenham10

Stephen MacDonnell & Barbara Kitchenham
How reliable are systematic reviews in empirical software engineering?
IEEE Trans Software Engineering V36n5(Sep/Oct 2010)pp676-687
=EXPERIMENT COMPARING SURVEYS
Compares the procedures and results of two independent teams trying to answer the same question by studying the published literature.
The differences in procedure did not lead to different conclusions.

MacKay99

Is Paper Safe? The Role of paper flight strips in air traffic control
ACM Trans Computer-Human Interact V6n4(Dec 1999)pp311-340 CR0006-0394
=EXPERIENCE RISK USER SYSTEM TECHNOLOGY
Studied existing 3 or 4 traffic control centers in europe
Don't remove a working technology from a human-computer system, augment it.

Mackey96

Karen Mackey
Why Bad Things Happen to Good Projects
IEEE Software Magazine V13N3(May 1996)pp27-33
=EXPERIENCE PROCESS ESTIMATION MURPHY
allow for murphy's law especially when doing a complex system right. Include performance and monitoring tools.

MackLewisCarroll83

Robert L. Mack & Clayton H. Lewis & John M. Carroll
Learning to Use Word Processors: Problems & Prospects
ACM TOIS V1n3(Jul 1983) pp254-271
=EXPERIENCE USER System PROTOTYPING

MacLeanetal95

Roy MacLean & Susan Stepney & Simon Smith & Nick Tordoff & David Gradwell & Tim Hoverd & Simon Katz
Analysing Systems: Determining Requirements for Object-oriented Development(ORCA)
Prentice Hall Int Herts UK 1994 (BCS series) ISBN 0-13-301433-9 CR9508-0547 reviewed IEEE Software magazine V13n3(Mar 1996)p119
=ADVERT OBJECT-ORIENTED METHODS
Diagnostic approach: Grampus:= Gurarntee/rely Approach to modeling PURPOSE in Systems + Beluga:= behaviorial

MacLennan79

B. J. MacLennan
Observations on the Differences Between Formulas and Sentences and their Application to Programming Language Design
SIGPLAN V14n7 (Jul 1979)p51-61
=DEMO logic languages graphic

MacLennan83

?? MacLennan
Principles of Programming Languages
NY NY Holt Rinehart & Winston 183
=SURVEY Smalltalk text survey

Maciaszek01

Leszek A Maciaszek
Requirements Analysis and System design: developing Information Systems with UML
Addison Wesley 2001 ISBN 0-201-70944-9
=TEXT UML DATA REQUIREMENTS DESIGN USE-CASE activity

MacLane71

Saunders Mac Lane
Categories for the Working Mathematician
Springer-Verlag NY NY 1971
=CLASSIC =TEXT MATH CATEGORY THEORY categories coproduct pushout pullback functor morphism
Also see my own [ math_25_Categories.html ]

Macri00

Julian Macri
State Patterns and C++
Dr. Dobbs Journal #313(Jun 2000)pp36-45
=DEMO C++ TECHNICAL state PATTERN
delegation vs checker
State vs context objects. state responsible for dynamics but who is reponsible for behavior.

MadanmohanDe'04

T R Madanmohan & Rahul De'
Open Source Reuse in Commercial Firms
IEEE Software Magazine V21n6(Nov /Dec 2004)pp62-69
=POLL 13 projects OPEN SOURCE REUSE COMPONENTS BSD Apache MySQL SSH
Selecting components is not easy.
The License rules play an important part in the selection process, as does the activity of the community that supports the source code.
Some components require other unusual components that make the package less appealing. Similarly, the documentation of interfaces lag behind implementations making some products less reusable.

MaddenRhone84

William F Madden & Kyle Y Rhone
Design & Development & Integration: Space Shuttle Primary Flight Software System
Commun ACM V27n9(Sep 1984)pp914-925
=CASESTUDY NASA shuttle software NON_SEQUENTIAL
One lesson learned: don't used shared memory to communicate between processes, use message passing.
Reason: message passing is more reliable than shared memory.
Seach for shuttle

Maddisonetal83

?? Maddison ...
Information Systems Methodologies
UK Wiley Hayden
=survey SAD SSADM DFD ERD PQRST

Maddux96

Roger D Maddux
Relation-algebraic semantics
Theor Comp Sci V160n1-2(Jun 1996)pp1-85
=SURVEY LOGIC SEMANTICS REGULAR-EXPRESSIONS
meaning of a statement is two elements in a relation algebra. One element defines what happens if the statement terminates and the other defines the states when the statement will not terminate. cf [Hoareetal87]

Madsenvanderplaats82

?? Madsen & ?? Van de Plaats
COPES - A FORTRAN control program for engineering design
Naval Postgraduate school Monterey CA NPS69-81-003
=TOOL engineering optimization Technical

MaedaEtal97

Chris Maeda & Arthur lee & Gail Murphy & Gregor Kiczales
Open Implementation Analysis and Design -- -- --(OIA/D)
In [Harandi97] pp44-52
=DEMO REUSE MODULES

Maginnis00

Terri Maginnis
Engineers Don't Build
IEEE Software Magazine V17n11(Jan/Feb 2000)pp34-39
=ESSAY STANDADS PROFESSION
Compares software development with the construction industry
-- we have no architects for a start
lists the life history of a proffessional engineer.

Magnusson90

Boris Magnusson
SCOOP-Europe report and introducing OOP Research at the University of Geneva
Journal of Object Oriented Programming V3n4(Nov/Dec 1990)p66-70.
=NEWS OBJECT-ORIENTED RESEARCH

Maguire94

Steve Maguire
Debugging the Development Process
Microsoft Press Redmond 1994
=ADVERT MICROSOFT MS-PROCESS
read Zachary93 as an antedote

MahalingamHuhns97

Kuhanandha Mahalingam(juha@sc.edu) & Michael N Huhns
A Tool for Organising Web Information
IEEE COmputer magazine V30n8(Jun 1997)pp80-83
=DEMO JAVA GRAPHIC ONTOLOGY TOOL Called JOE maps natural language query into SQL DATAbase
Ontology::=ERD

Mahmoud00

Qusay H Mahmoud
Writing Jini Services
Software Development Magazine V8n8(Aug 2000)pp57-58+60-62
=HOWTO TECHNICAL WWW/NET Jini CODE COMMANDS GUI TOOL

MahonyDong00

Brendan Mahony & Jin Song Dong
Timed Communicating Object Z
IEEE Trans Softw Eng V26n2(Feb 2000)pp150-177
=ADVERT LANGUAGE SPECIFICATION OBJECT-ORIENTED TIMING Z CSP TCOZ

MahoneyHayes92

Brendan P Mahoney & Ian J Hayes
A Case-Study in Timed Refinement: A Mine Pump
IEEE Trans SE-V18 n9 (Sep 1992)pp817-826
=DEMO Z continuous time units
Specification_statement::= variables":" "[" Assumptions "," Guaranteed"]".
FSM NOT!
p824, Conclusions: "The use of continuous observables, as opposed to the simple adoption of analog models, helps direct the the specifier away from detailed considerations of the method by which a system must evolve through time[...]leads to an algorithmic and evolutionary description of a system not always appropriate to the highest levels of the development process".

Maibaum97

T S E Maibaum <tsem@doc.ic.ac.uk>
What we teach Software Engineers in the University: Do we take Engineering Seriously?
[JazayeriSchauer97] pp40-50
=EDUCATION SCIENCE ENGINEERING NORMAL DESIGN COOKBOOK
normal_design::=improvement and fitting of the accepted under new or more stringent conditions.
micro-methods vs general theory
Later see [Maibaum09]

Maibaum09

Tom Maibaum
formal methods versus engineering
ACM Inroads & SIGCSE Bulletin V41n2(Jun 2009)pp6-12
=EDITORIAL ENGINEERING SCIENCE MATHEMATICS DESIGN HANDBOOKS EDUCATION METHODOLOGY COOKBOOK
Quotes Vincenti90 and MAJackson. Compare with [Maibaum97]
Engineers need standard cookbook methods and calculations suited to specific kinds of problems.
Fails to mention DDD(JSP, compilers, database, JSD, SSADM etc), Model checking ( SMV Alloy etc.)
Does not discuss the intractability and/or unsolvability of the problem of calculating consequences of requirements.
Implies that given pre/post conditions the code can be generated automatically -- but actually the engineer needs to supply internal invariants, structures, and non-functional requirements to determine the best design for code.
More on the scientific basis for software engineering [JuristoMoreno02] and compare with [HincheyEtAl08] on formal methods in software engineering.

Maiden05

Neil Maiden
What has requirements Research ever done for us?
IEEE Software Magazine V22n3(Jul/Aug 2005)pp104-105
=SURVEY requirements KAOS i* Tropos Use-case maps LTSA CREWS ART-SCENE
Sidebar has URLs.

Maiden06

Neil Maiden
Servicing your requirements
IEEE Software Magazine V23n5(Sep/Oct 2006)pp14-16
=CASE STUDY Requirements web uddi wsdl owl-s Woogle
Existing web services can be used to inspire new Requirements.
Existing web services are prototypes.
Woogle::= See http://haydn.cs.washington.edu:8080/won/wonServlet, server for finding web services.

Maiden06a

Neil Maiden
Improve your requirements: Quantify them
IEEE Computer Magazine V39n10(Oct 2006)pp68-69
=ADVOCACY QUANTIFY QUALITIES NONFUNCTIONAL REQUIREMENTS Volere Planguage Gilb
Volere::= See http://www.volere.co.uk/
Gilb::= See http://www.gilb.com/

Maiden07

Neil Maiden
My Requirements? Well, That depends
IEEE Software Magazine V24n1(Jan/Feb 2007)pp86-87
=ADVOCATES SCENARIOS for REQUIREMENTS in CONTEXT QUANITIFICATION USE CASES
Describe requirements by first writing scenarios describing specific ways a requirement may happen. Example: sending text message wearing gloves vs on a desk.

Maiden08

Neil Maiden
User Requirements and System Requirements
IEEE Software Magazine V25n2(MAr/Apr 2008)pp60-
= USER SYSTEM REQUIREMENTS
Distinguish user requirements from system requirements.
Need both, separately.
A user requirement comes from a user and describes a new property of the domain or business process. Goals.
A system requirement describes a desirable property of the new system. The system shall .... Use cases or other structured text.
Implementing system requirements should lead to satisfying user requirements -- Satisfaction arguments.
It is a design task to move from user to system requirements.

Maiden08a

Neil Maiden
Requirements 25 years on
IEEE Software Magazine V25n6(Nov/Dec 2008)pp26-28
=HISTORY 1983-2008 REQUIREMENTS
14 references
1970s: Requirements were monolithic and used natural language with "noise, silence, contradiction, ambiguity, and wishful thinking". VDM [Bekic70] and JSP [Jackson75]
available but not used. Pencil and Paper
1977: Ross [Ross77] developed SADT notation (IDEF) and method [Ross85] and story telling.
1978: [Jackson78] System maintains a model of reality. Leads to JSD in the 1980s
1979: DeMarco [DeMarco79] , Gane&Sarson [GaneSarson79] , Yourdon [Yourdon75] & Constantine. DFDs. Logical vs Physical. STDs. Functional decomposition. Informal diagrams. structured analysis and design. First CASE tools help draw informal graphics.
1980s: Greenspan. [BorgidaGreenspanMylopoulos85] [BorgidaGreenspanMylopoulos94] Semantic networks, logic, frames model knowledge about situation. RML: the model is collection of objects of different types. Ontology: entities, activities, assertions. Leads to TROPOS, i*, KAOS (Knowledge Acquisition in Automated Specification). Goals and Constraints. Expert systems.
1980s: Stakeholders have difficulties articulating requirements. So, repertory grids, card sorting, Laddering. [Maiden09]
1990s: Ethnography, HCI. Complexity of the working environment.
1998: Beyer & Holtzblatt [BeyerHoltzblatt94] [BeyerHoltzblatt95] : Contextual enquiry.
1999: Vicente: Cognitive work Analysis
2004: [MaidenGizikisRobertson04] : Inventing requirements.
Today: better at identifying stakeholders, use cases and scenarios, quality requirements, reasoning about natural language, multiply viewpoints, detecting and handling conflicts, social techniques, Tracing requirements, tailoring to different domains, training analysts.
Meanwhile: We are tackling larger and more complex systems.
Also see [Maiden05] on requirements research.

Maiden09

Neil Maiden
Card Sorts to Acquire Requirements
IEEE Computer Magazine V26n3(May/Jun 2009)p85-86
=EXPERIENCE MANUAL REQUIREMENTS TOOL CARDS SORTING
Compares advantages and disadvantages for using a very old technology to represent and manipulate requirements.
Compare the XP Planning Game.

Maiden09a

Neil Maiden
Oi, Analyst -- You're Barred
IEEE Computer Magazine V26n6(Nov/Dec 2009)pp13-14
=EDITORIAL vs CERTIFIED REQUIREMENTS ENGINEER
Requirements engineering: one size does not fit all.
Evidence that Domain Knowledge trumps RE skills [CurtisKrasnerIscoe88]
Rebuts [Paech08]

Maiden11

Neil Maiden
Requirements and Aesthetics
IEEE Software Magazine V28n3(May/Jun 2011)pp20-21
=ESSAY NONFUNCTIONAL REQUIREMENTS QUALITIES AESTHETICS generate PLEASURE EXCITEMENT PRIDE MEANING

Maiden11b

Neil Maiden
What time is it, Eccles
IEEE Software Magazine V28n4(Jul/Aug 2011)pp84-85
=JOKE GOONS Eccles Bluebottle clocks
Because current techniques appear to give the right answer there is a danger of not adopting newer and better techniques.
Compare with collecting scientific data on techniques... [[DiesteJuristo11]

Maiden11c

Neil Maiden
The Inhibited analyst
IEEE Software Magazine V28n6(Nov/Dec 2011)pp100-102
=ESSAY ANALYSTS ASK WHY
Like a three year old keep asking why!
And also "what happened before "
Ref to istar.

MaidenEtAl07

Neil Maiden & Omo Otojare & Norbert Seyff & Paul GrunBacher & Karl Mitteregger
Determining Stakeholder needs in the workplace: How Mobile Technologies can help
IEEE Software Magazine V24n2(Mar/Apr 2007)pp46-52
=EXPERIENCE MSP Mobile Scenario Presenter PDA MSWord Requirements Arena-M ART-Scene Web/Net
MSP::tool, presents and records scenarios + notes about them.
Mobile device should be used to collect requirements where they occur -- in the workplace. Can combine mobile technology with various methods of requirements elicitation.
Bespoke mobile requirements tools work better than generic tools.
Tools should work with different people: analysis have more complex needs than future users.
Usiability is important.
Plan carefully to develop an infrastructure that supports mobile RE tools.
Capture just enough information to enable completion of specifications later.
13 references.

MaidenGizikisRobertson04

Neil Maiden & Alexis Gizikis & Suzanne Robertson
Provoking Creativity: Imagine what your Requirements Could Be Like
IEEE Software Magazine V21n5(Sep /Oct 2004)pp68-75
=EXPERIENCE REQUIREMENTS WORKSHOP CREATIVITY CORA RESCUE Pre-USE CASE
Describes theoretical basis for creative thinking: Diverge; Converge. Prepare, incubate, illumination, verification. Cf. CORT TEC Target-Expand-Contract
RESCUE::="Requirements Engineering with Scenarios for User-centered Engineering".
CORA::="COnflict Resolution Assistant", for air-traffic Control. Cf. TCAS projects.
Used other domains and analogies to explore requirements. Analogy via a common abstraction.
Combine random stimuli(eg toy frog) and combinations of requirements.
Transform problems by relaxing constraints.
Helps to understand the difficulty of creativity.
Encourage playfulness.
Groups and plenary sessions. Ideas on cards.
Analogies need a step-by-step guidance.
It takes time to incubate analogical ideas,
Structure workshops about ideas rather than creative processes.
Record the rationale behind ideas.
Time to let off steam...
Plan plan and then plan alternatives.
Need a champion for workshops.
See Gottesdiener, DeBono, Wickelgreen, ...

MaidenJones10

Neil Maiden & Sara Jones
agile requirements -- can we have our cake and eat it to?
IEEE Software Magazine V27n3(May/Jun 2010)pp87-8
=ESSAY AGILE REQUIREMENTS HISTORY CARDS TOOLS CDs JISC CONVERSATION SPACE
Too much documentation is wasted effort.
Lack of documentation leads to predictable problems: Ignored nonfunctional requirements, inducting new members, evolving application, etc.
Alternatives to paper work: (1) Cards? (2) PDF requirements on CD was ignored. (3) Perhaps something like [Cook10] with digital tools?
JISC::="joint information systems committee".

MaidenNcubeMoore97

Neil A M Maiden & Cornelious Ncube & Andrew Moore
Lessons Learned During Requirements Acquisition for COTS Systems
Commun ACM V40n12(Dec 1997)pp21-25
=EXPERIENCES selecting TOOLS for REQUIREMENTS ACRE:=PORE [ welcome.html ]
1. + make them measurable
2. + use a prototype tool to develop tests
3. + usecase&scenarios match tests
4. + scope=core&other products
5. + stakeholders present at testing
6. + videotape tests and enter into rationales
7. + coffee
8. + have a common reference product
9. + use better weighting techniques than %
10. + beware the sales pitch and havea script of questions AHP::="Analytic Hierarchy Process [Saaty90].

MaidenNcube98

Neil A Maiden & Cornelious Ncube
Acquiring COTS Software Selection Requirements
IEEE Software Magazine V15n2(Mar/Apr 1998)pp46-56
=EXPERIENCES selecting TOOLS for REQUIREMENTS PORE [MaidenNcubeMoore97]
[AHP] problems with dependencies and large number of pairwise comparisons
PORE templates reduce possibles and increase requirements: supplier data; demo; hands-on use; ???

MaimonHorowitz99

Oded Z Maimon & Roni Horowitz
Sufficent conditions for inventive solutions
IEEE Trans Sys Man Cybernetics V29n3(Aug 1999)pp349-361
=EXPERIMENT POLL DESIGN
Theory: if qualitive change and closed world then inventive.

Maineetal85

Main & Milton & Mislove & Schmidt(Eds)
Mathematical Foundations of Program Semantics
Springer Verlag 1985 (Lect Notes in CS 298)
=theory mathematical semantics languages

MalhotraGalletta04

Yogesh Malhotra and Dennis F Galletta
Building Systems that Users want to use
Commun ACM V47n12(Dec 2004)pp89-
=EXPERIENCE =THEORY PEOPLE USERS SYSTEMS
If users are not committed and/or not motivated then they tend not to use systems that provided for them.
Improvement and value comes from systems being used not from the existence of the system.
Two classic anecdotes: the Pillsbury intranet for sharing information that nobody used for six months. The PriceWaterhouse Coopers institutional document repository was never used when an inferior mailing list became a primary channel for communication and collaboration.
Commitment: compliance..identification.. internalization.
Motivation: intrinsic and extrinsic.
(dick)|-ownership and involvement in development is a powerful motivator.

Makinson08

David Makinson
Sets, Logic, maths for computing
Springer NY NY 2008 ISBN 1846288444
=UNREAD DISCRETE MATHEMATICS
Notes [click here Makinson08 if you can fill this hole]

Malik11

Petra Malik
A retrospective on CZT
Software & Experience 41(2): 179-188, 2011.
=EXPERIENCE F/OSS OPEN SOURCE TOOL FORMAL Z Requirements specification verification tools LOGIC Set Theory UNICODE XML Circus
Community Z Tools on SourceForge. See [ Community_Z_Tools ] on the Wikipedia.

MalikZhang09

Sharad Malik & Lintao Zhang
Boolean Satisfiabiliy -- From Theoretical Hardness to Practical Success
Commun ACM V52n8(Aug 2009)pp76-82 [ 1536616.1536637 ]
=SURVEY THEORY BIGO EXAMPLE PRACTICE CNF DPLL ALGORITHMS PERFORMANCE BENCHMARKS NP COMPLEXITY PERFORMANCE
Theory calculates the worst case performance.
SAT solvers rely on the typical case (in a given domain) is not the worst case.
The Davis Putnam Logeman Loveland algorithm with optimizations gives a usable tool.
See [Fortnow09] for the theory.

MalkhiReiter00

Dahlia Malkhi & Michael K Reiter
Secure Execution of Java Applets Using a Remote Playground
IEEE Trans Software Engineering V26n12(Dec 2000)pp1197-1209
=DEMO SECURITY RISKS MOBILE WWW/NET JAVA1.1

Malone83

Thomas W. Malone
How do people organize their desks? Implications for the design of Office Information Systems
ACM Trans Off Inf Syss 1 1 (Jan 1983) pp99-112
=EXPERIENCE USER System Reality

Mamone94

Salvatore Mamone(Nynex)
The IEEE Standard for Software Maintenance
ACM SIGSOFT Software Eng Notes V19n1(Jan 1994)pp75-76
=STANDARD MAINTENTANCE IEEE
1. (problem|modification) identification & classification; analysis; design; implementation; system testing; acceptance testing; delivery
2. Guidelines....
3. Technology....

MamrakBarnesO'Connell93

Sandra A Mamrak<mamrak@cis.ohio-state.edu> & Julie Barnes & Conleth S O'Connell
Benefits of Automating Data Translation
IEEE Softare Magazine(July 1993)pp82-88
=ADVERT DDD Integrated Chameleon Architecture (ICA)

MancaSalibra92

Vincenzo Manca & Antonino Salibra
Soundness and completeness of the Birkhoff equational calculus for many-sorted algebras with possibly empty carrier sets
Theoretical Computer Sci V94n1(march 1992)pp101-124 CR9306-0387(F.3.2)
=THEORY DATA TYPES ADT

MandrioliMeyer91

D Mandrioloi & Bertrand Meyer
Advances in Object-Oriented Software Engineering
Prentice Hall Englewood Cliffs NJ 1991
=MONOGRAPH OOSE OBJECT-ORIENTED RESEARCH

Manes92

Ernest G Manes
Predicate Transformer Semantics
Tracts in Theoretcal Computer science V35 Cambridge U Press UK, Telegraphic Reveiw The American Math Monthly Oct 1993 pp817
=THEORY SEMANTICS CATEGORY
1. Partial Functions Pfn
2. Multi-valued fucntion Mfn
3. Cf Manes and Arbib?

ManesArbib86

Ernest G Manes & Michael A Arbib
Algebraic Approaches to Program Semantics
Springer Verlag Monograph 1986
=theory topology category

ManesMurphy93

Steve Manes & Tom Murphy
C++ Development
Unix Review V11n6(Jun 1993)pp83-88
=HISTORY C++ TOOLS objects Environments
7 integrated environments including C++ graphics and debuggers from DEC, HP, IBM & Sun.
MangerucaEtAl07
1. Leonardo Mangeruca & Massimo Baleani & Alberto Ferrari & Alberto Sangiovanni-Vincentelli
2. Semantic-Preserving Design of Embedded Control Software from Synchronous Models
3. IEEE Trans Software Engineering V33n8(Aug 2007)pp497-509
4. =THEORY EMBEDDED NONSEQUENTIAL DESIGN BUFFERED SYSTEM REAL-TIME PERFORMANCE SCHEDULING
5. How to map functional requirements into a buffered network that is guaranteed to meet performance requirements.

Mann02

Charles C Mann
Why Software is so Bad.
Technology Review MIT V105n6(Aug 2002)pp33-36+38
=ARTICLE RISKS ERRORS MICROSOFT CORRECTNESS Ada C++ CMS INSPECTIONS VISION USER

MannZ06

Zoltan Adam Mann
Three Public Enemies: Cut, Copy, and Paste
IEEE Computer Magazine V39n7(Jul 2006)pp31-39
=HARMFUL LOW-LEVEL CODE EDITING
Standard editting operations don't distinguish the half-a-dozen different purposes of using cut, copy and/or paste.
Paste does not record the possible link between old and new. Then a future change that should be done in several places is done once.
Worse it does not distinguish between "copy (and keep identical)" from "copy (and then change)".
Proposes introducing higher level operations (for complex dynamic artifacts). note
2. (DRY)|-Repetitive edits indicate the need for refactoring.

MannaPnueli91

Zohar Manna & Amir Pnueli
Completing the temporal Picture
Theor Comput Sci V83n1(Jun 1921)pp97-130 [CR] 9204-0235
=THEORY LOGIC SPECIFICATION MODAL TEMPORAL ASSERTIONAL
If a safety, response, or reactivity property can be proved in temporal logic then it can be proved in assertional logic

MannaPnueli92

Zohar Manna & Amir Pnueli
The Temporal Logic of Reactive and Concurent Systems: Systems
Springer Verlag NY NY 199?
=THEORY MODAL TEMPORAL LOGIC

MannaWaldinger85

Zohar Manna & Richard Waldinger
The Logical Basis for Computer Programming: Vol 1 Deductive reasoning
Addison Wesley series in C Sci 1985
=TEXT logic

MannaWaldinger92

Zohar Manna & Richard Waldinger
Fundamentals of Program Synthesis
IEEE Trans SE-18 n8(Aug 1992)pp674-704 CR9311-0864
=THEORY SYNTHESIS

MannionKeepence95

Mike Mannion<m.mannion@central.napier.ac.uk> & Barry Keepence
SMART Requirements
ACM SIGSOFT Software Engineering Notes V20n2(Apr 1995)pp42-47
=IDEA REQUIREMENTS
SMART::Requirements= Specific & Measurable & Attainable & Realizable & Traceable. [ MannionKeepence95.html ]

Mannuccietal89

S Manucci & B Mojana & MC Navazio & V Romano & MC Terzi & P Torrigiani
Graspin: A Structured Development Environment for Analysis & Design
IEEE SOftware v6 n6(Nov 1989)p35-43
=DEMO graphic tools

Mankin78

R Mankin
Loglan -- a more flexible language
=LETTER Esperanto vs Loglan Volapuk LOGIC ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) (Apr 13 1978)p16
Argues that an ITL must be artificial so that it does not grow, adapt, and develop dialects!
Rebuttal: Esperanto is used widely and yet has no dialects.

MantylaLassenius09

Mika V Mantyla & Casper Lassenius
What types of Defects are Really Discovered in Code Reviews
IEEE Trans Software Engineering V35n3(May/Jun 2009)pp430-448
=EMPIRICAL EXPERIMENT STUDENTS EXPERIENCE INDUSTRIAL INSPECTIONS SQA V&V DEFECT CLASSIFICATION EVOLUTION MAINTENANCE
Experiment done on students. Backed up with obsrvations of a company.
Inspections done after code has been run.
Most (60%) of discovered defects do not effect the functioning of software but might make the code harder to understand or change.

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.

MaoVredenburgSmithCarey05

Ji-Ye Mao & Karel Vredenburg & Paul W Smith & Tom Carey
The state of User-centered Design Practice
Commun ACM V48n3(Mar 2005)pp-
=POLL DESIGNERS USER ISO13407
UCD::="User Centered Design", multidisciplinary iterative (user; requirements; design; evaluation).
More than 10% of project budget.
Improves usefulness -- but measured how?
Techniques select by cost-benefit thinking. Many methods.
Notes

March83

?? March
Techniques for structuring database records
ACM Comp Surveys 15 1 (Mar 1983) pp43-79
=THEORY data optimization Technical

MarchandSamaan00

Herve Marchand & Mazen Samaan
Incremental Design of a power transformer station controller using a controller synthesis methodology
IEEE Trans Software Engineering V26n8(Aug 2000)pp729-741
=CASESTUDY why SIGALI SIGNAL control discrete event systems
PDS:= polynomial dynamical system.
PDS over {-1, 0, +1 } as Int modulo 3.
mapping signals to PDS value := (absent -> 0 | present and true -> +1 | present and false -> -1 ).
TDD:= ternary decision diagrams.
Physical model + objectives in SIGNAL compiled into PDS thence to SIGALI controller.
Manipulate systems of equations not sets of solutions.

Marciniak02

J. J. Marciniak, editor
Encyclopedia of Software Engineering
John Wiley & Sons, Inc., New York, NY 2002 2nd edn
=UNREAD =REFERENCE
Help [click here Marciniak02 if you can fill this hole]

Marcus03

Aaron Marcus
The 12 myths of Mobile Use
Software Development Magazine V11n4(Apr 2003)pp36-39+42
=ESSAY MOBILE HCI USER PURPOSE TECHNOLOGY vs MARKETING
1. USA tends to lag because of fragmented telecommunications.
2. Too many features is bad. KISS.
3. Mixing too many tools into one device leads to confusion manufacturers and consumers.
4. Consumers are not (in focus groups) good at predicting killer applications like SMS(short messaging service).
5. different locales have different cultures and so need different interfaces, functions, languages, character sets.
6. Classes of usage: self_enhancement, relationships, entertainment, commerce(THEY). With the user in the center...
7. The future mobile device is very hard to predict.
8. Don't expect a single user interface standard or OS.
9. Highly usable system are not a high priority, yet.
10. Expect commodity devices and conspicuous consumer devices.
11. How to grow and advance data service: start doing one useful thing well.
12. General mobile data services are not going to arrive soon. Vertical markets however are already happening.

MardenMunson99

Philip M Marden Jr & Ethan V Munson
Todays style sheet standards: The great vision blinded
IEEE Computer Magazine V32n11(Nov 1999)pp123-125 + Letters V33n3(Mar 2000)p8
=HARMFUL CSS XSL USER ADVERT PSL Proteus Thot P Constraint CSS

MargariaSteffen09

Tiziana Margaria & Bernhard Steffen
Continuous model-driven engineering
IEEE Computer Magazine V42n10(Oct 2009)pp106-100
=ADVERT OTA XMDD CMDE One-Thing MODEL USER STAKEHOLDER REQUIREMENTS EXECUTABLE FORMAL

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"

Margulies00

Benson Margulies
surviving performance fire drills
Software Development Magazine V8n8(Aug 2000)pp41-45
=EXPERIENCE PERFORMANCE METHOD is SCIENCE
scientific_method:=(problem; hypothesis; experiment; results) -> keep a notebook(spreadsheet)
inspect code. Missouri:="show me"

Margulies02

Benson I Margulies
Designing for debugging
Software Development Magazine V10n2(Feb 2002)pp-
=ARTICLE TECHNICAL CODE TESTABLE
Write code so that a normal debugger can see what is going on.
Also mentions other nasty roadblocks when fixing code.

Maring96

Blayne Maring
Object-Oriented Development of large Applications
IEEE Software Magazine V13N3(May 1996)pp33-40
=EXPERIENCE PROCESS OBJECT_ORIENTED FSM TABULAR TRAINING
JSD like state vectors? Six weeks training and only 10 to 20% made the switch. Stopped programmers from elaborating the class hierarchy because subclassing to model control flow makes the overall process difficult to see+debug+maintain. Separated table driven FSM for business rules. Give managers tools to modify tables/rules. Did not achieve desired productivity/time-to-market+quality etc expectations. Note: Clear evidence of a badly controlled process and weak OO methods.

Mark02

Gloria Mark
Extreme Collaboration
Commun ACM V45n6(Jun 2002)pp89-93
=EXPERIENCE TEAM PEOPLE DESIGN WORKPLACE JPL WAR-ROOM TEAM-X
Human network/teamwork is supported by networked spreadsheets, projectors, face-to-face.
Stressful but develops proposals quickly.

MarkCochrane92

Leo Mark & Roberta Cochrane
Grammars and Relations
IEEE Trans SE-V18 n9(Sep 1992)pp840-849 DDD
=IDEA ALGORITHM GeneRel GRAMMARS to RELATIONAL DATA SQL
TCFG:="Tagged " CFG.
compare with [Wile97]
1. !!EMail to leveson re omitted constraints on TCFGs to make the GeneRel algorithm work.
2. ??Variation might become DAD
3. !!Compare with GAMMA See Research/TODO/Prove DDD

Marketal93

William Mark & Sherman Tyler & James McGuire & Jon Schliossberg
Commitment-Based Software Development
IEEE Trans SE-V18n10(Oct 1992)pp870-885
=DEMO Comet LOOM AI DESIGN TOOL SEMANTIC

Markosianetal94

Lawrence Markosian & Philip Newcomb & Russel Brand & Scott Burson & Ted Kitzmiller
Using and Enabling Technology to Reengineer Legacy Systems
Comm ACM V37n5(May 1994)pp58-70
=ADVERT TOOLS LEGACY COBOL DATA EVOLUTION

Markus83

M Lynne Markus
Power, Politics, and MIS Implementation
Commun ACM V26n6(Jun 1983)pp430-444 & [MyersAvisson02] Chapter 3, pp19-48
=EXPERIENCE PEOPLE SYSTEMS RESISTANCE POLITICS ORGANIZATION MANAGEMENT FIS
In this case People resisted a new system not just because it wasn't good enough, or because they were not trained etc, but because the new Financial Information System was a ploy to change the organization.
New FIS system tended to move data and power toward a centralized system and away from divisional centers. Divisions fought the system.
Sometimes it is better to change the organization first and then change the technological systems in use.

MarloweKuBenham05

Thomas J Marlowe & Cyril S Ku & James W Benham
Design Patterns for Database Pedagogy - a proposal
ACM SIGCSE Tech Symp Proc (Feb 2005)pp48-54
=IDEA EDUCATION PATTERNS DATA GoF UML
Example. Views are database observer.

Marsaglia03

George Marsaglia
Seeds for Random Number Generator
Commun ACM V46n5(May 2003)pp90-93
=IDEA TECHNICAL RNG
RNG::="Random Number Generator".
|-A single seed RNG generates a (long?) but single cycle of numbers.
If x is followed by y, it always flowed by y.
(above)|-single seed RNGs can generate one out of many possible sequences.
|-Using such a RNG to generate a jury list is probably illegal!
Gives 8 examples (in C) of RNGs that use a buffered of seeds and generate more permutations and have a much longer cycle.
Suggests ways of getting the hundreds or thousands of random seeds.
Does not mention the use of a single seeded RNG to shuffle a buffer of previously generated numbers.

MarshallHermanMelancon01

M S Marshall & I Herman & G Melancon
An Object-Oriented design for Graph Visualization
Software - Practice & Experience V31n8(10 Jul 2001)pp739-756
=DEMO GRAPH GVF VISUALIZATON CLASS LIBRARY
Available at [ GVF ]

MartelliMontanari82

A Martelli & Ugo Montanari
An Efficient Unification Algorithm
ACM TOPLAS V4N2 Apr82 pp258-282
=IDEA ALGORITHM non-sequential optimization Reality

Martin73

James Martin
Design of Man-computer Dialogues
Prentice Hall NJ 1973
=TEXT USER

Martin85

James Martin
System Design from Provably Correct Constructs
Prentice-Hall Int(USA) 1985 QA76.9S88M37 1984, Dewey 001.64 ISBN 0-13-881483-X
=ADVERT HOS DATA Algebraic Specifications of AXES FORMAL METHODS FD
Net
1. Content:
2. data engineering ch10..14 +App iv,
3. HOS chapters 3..9,
4. WHY (ch00) Software Misengineering ch1,
5. HOS->DFDs ch15 (not vv),
6. New life cycles ch18,
7. Theory appendices I, II,
8. Intrinsic data types Appendices III,
9. TNF 3NF Third Normal Form Appendix IV,
(End of Net)
1. Claims these methods 10 times more productive p124 than informal structured methods.
2. Shows typical DFD and how it turns into two programs.
3. p265 " The shortcomings of DFDs as typically drawn[...]As a method of analysis they leave much to be desired. They help conceptualize entangled data flows of data between operations, but unless coupled to a more rigorous forms of analysis, they are often misleading or wrong. They are no substitute for formal data analysis and rigorous functional decomposition."
4. "Structured Analysis" as commonly practices gives inadequate front-end design(although it is better than unstructured text specifications), and consequently the programs created with it have many errors of specification which are expensive to corrrect"
5. (but no evidence given of claims)

Martin91

James Martin
Rapid Application Development
MacMillan Pub Co NY NY 1982 ISBN 0-02-376775-8 CR9206-0344
=ADVERT RAD function points normalization charts and diagrams timebox I-CASE

Martin93

James Martin
Principles of Object-Oriented Analysis and Design
Prentice Hall Englewood Cliffs NJ 1993
see [MartinOdell92]

Martin95

Robert C Martin
Designing object-oriented C++ Application: Using the Booch method
Prentice Halll Inc NJ 1995 ISBN 0-13-203837-4 CR9610-0770
=TEXT OBJECT-ORIENTED DESIGN patterns

Martin00

Robert C Martin
eXtreme Programming Development through Dialog
IEEE Software Magazine V17n3(Jul/Aug 2000)pp12-13
=ADVERT XP USER TECHNICAL FEEDBACK PROCESS QUALITY PEOPLE
PEOPLE not PAPER. [Beck00]
Conversational planning, customers set functions/tests & priorities. Programmerb estimate time & do one user story at a time. Limit trust to 2 weeks.
quality by pair programming, simplification, testing.
must create failing test before "fixing".

Martin02

Robert Martin
Crash Diet (part 2 of series)
Software Development Magazine V10n8(Aug 2002)pp47-49
=DEMO TECHNIQUE REFACTORING CODE COMMENTS Object-Oriented STRUCTURE
If a piece of code needs comments that explains how it works then rewrite it using (new) classes and methods that have self-explanatory names.
Retest every change.
(dick)|-you can not test a comment to see if it works, you can test self-documenting code.
(dick)|-Make documentation as executable as possible. Live code not dead trees.

Martin02b

Robert C Martin
A Test of Patience & Baby Steps
Software Development Magazine V10n10(Oct 2002)pp46+54,V10n10(Nov 2002)pp51-54
=DIALOGUE XP TESTFIRST REFACTOR PAIR-PROGRAMMING
Don't vest yourself in your code. Be ready to delete and start afresh using what you learned from the first version.
Example of how test first programming produces simple solutions.
First of a series [Martin03a] [Martin03b] Etc.

Martin03a

Robert C Martin
Mocket to me
Software Development Magazine V11n1(Jan 2003)pp45-46+48
=DIALOGUE XP Java Sockets testing Mock objects PAIR-PROGRAMMING
Part 7. [Martin02b]
Tests are also users!
Separating testing from code by introducing a class of mock objects into the test and into the production code tends to help develop the code for the user.

Martin03b

Robert C Martin
Testing in Synch
Software Development MagazineV11n2(Feb 2003)pp51-53
=DIALOGUE XP Java Sockets testing PAIR-PROGRAMMING
Part 8. [Martin03a]
Refactor-ed "DRY" tests are documentation that can be executed, tested, and even recycled into production code.
See also [Martin03c]

Martin03c

Robert C Martin
Dangerous Threads
Software Development Magazine V11n3(Mar 2003)pp51+53-54
=DIALOGUE NONSEQUENTIAL THREAD SAFETY Java PAIR-PROGRAMMING
Previous Episode: [Martin03b]
Next Episode: [Martin03d]

Martin03d

Robert C Martin
Iterations Unbound (episode 10)
Software Development Magazine V11n4(Apr 2003)pp48-50
=DIALOGUE TECHNICAL CODE ITERATORS RISKS JAVA THREADs PAIR-PROGRAMMING
Never add or remove something while you have an active iterator(or pointer).
If you are adding and deleting items in a container in threaded code: don't use iterators and synchronize access to the container or (better) use a synchronized version of the container.
Note. iterators for synchronized containers are not automatically synchronized.
Previous episode [Martin03c] and next [Martin03e]

Martin03e

Robert C Martin
Forget the Main()
Software Development Magazine V11n4(Apr 2003)pp50-51+55
=DIALOG USER CODE NET Java TESTING PAIR-PROGRAMMING
Write the main program last!
Handle each argument in a separate function and test separately.
Tests must create the files/data they use rather than rely on specially created data files.
Tests design the program for you.
Previous [Martin03d]
Next [Martin03f]

Martin03f

Robert C Martin
A Better Solution
Software Development Magazine V11n7(Jul 2003)pp53-55
=DIALOG OO CODE NET Java PEOPLE "Micah" PAIR-PROGRAMMING
Previous [Martin03e]
Don't send a sequence of strings. Package up a serializable object and send that!

Martin03

Robert C Martin (Uncle Bob)
Agile Software Development: Principles, Patterns, and Practices
Prentice Hall PTR UpperSaddle River NJ 2003 ISBN 01235974445 CR 0502-0167
=UNREAD =ADVERT AGILE PATTERN Object-Oriented UML TECHNICAL DESIGN CODE

Martin09

Robert C Martin
Clean Code: A Handbook of agile software craftsmanship
Pearson Education 2009 Boston MA ISBN 0-13-2350088-2 CR 0912-1114 and 1003-0222
=HOWTO CODE TECHNICAL QUALITY WRITING JAVA
Demands study but tends to change the way you look at code.
All examples are Java 6 but it changed my C++ standards.
Stresses the iterative and evolutionary nature of code -- enhancement and refactoring as the constant change.
90% is well known advice dating back 30 years.
Some of it is startling
1. Comments should be reduced in favor of more better named functions and variables.
2. Objects and data structures are different: Objects hide data and provide functions, but data structures give access to data and have no other function!
3. Writing tests is a good way to learn an API and pays for itself by proving documentation.
4. Refactoring an SQL class leads to a functional decomposition of classes into subclasses.
5. "Inversion of Control" and "Dependency Injection" -- dependencies are created at run time.
6. Use Domain Specific Languages at the systems level.
Good list of smells and heuristics in Chapter 17.
Notes and recommend an interesting property of Java 5 "enum"s -- can specify functions that return different values for each value in the enum. Better than "switch".

Martin06

Fred Martin
Toy projects considered Harmful
Commun ACM V49n6(Jun 2006)pp113-116
=HARMFUL PEDAGOGY PROJECTS CSCI372
Make projects real, safe, designed, prototyped, performed

MartinezMerinoSalmeronMalpartida09

Jesus Martinez & Pedro Merino & Alberto Salmeron & Francisco Malpartida
UML-based Model-Driven Development for HSDPA
IEEE Software Magazine V26n3(May/Jun 2009)p26-33
=EXPERIMENTS TELECOMMUNICATIONS ACE CODE UML MDD TOOL Rhapsody State-Charts
HSPDA::="High-Speed Downlink Packet Access".
Using executable and compilable models made it easier.

Martinig

Franco Martinig
Methods & Tools - a free PDF & HTML newsletter
See [ index.html ]
=NEWSLETTER METHODS TOOLS

MartinMcClure85

James Martin & Carma McClure
Diagrammatic Techniques for Analysts & Programmers
Prentice Hall Intl NJ 1985
=survey graphic DFD ERD STD DDD sequential

MartinMelnick08

Robert C Martin & Grigori Melnick
Tests and requirements, requirements and tests: a Mobius Strip
IEEE Software Magazine V25n1(Jan/Feb 2008)pp54-59
=ADVERT REQUIREMENTS TESTS FIT TABULAR SCENARIOS
FIT::tool= See http://fit.c2.com/. , Framework for Integrated Testing
.See ./samples/methods.html#Fit

MartinOdell92

James Martin & James Odell
Object-Oriented Analysis and Design
Prentice Hall Englewood Cliffs NJ 1992 ISBN 0-13-630245-9 CR9304-0194 IEEE Software Mar 1994 CR9404-0198
=ADVERT Reality data state-charts

MartinsVeloso85

?? Martins & ?? Veloso
Jackson's Method for Program Construction: Year Nine
Position paper pp155-158 Proc Third International Workshop on Software Specification & Design(IWSSD3) 1985 IEEE Cat No 85CH2138-6 Order No 638
=EXPERIENCE DDD sequential

MartinSwaran97

David H Martin & Agni Swaran
Designing for Performance: The ODBMS Impact on Design
Object Magazine (Feb 1997)pp45-50
=EXPERIENCE OBJECT-ORIENTED DATAbases two different projects with different lifecycles and domains
Optimizations similar to SSADM Physical Design Control
Time-to-market vs maintainability - [Botting97a]

MartinigEtAl

Martinig adn Associates
Methods and Tools
Web page [ http://www.methodsandtools.com/ ]
=MAGAZINE =ADVERTS METHODS TOOLS PROCESSES NEWS LINKS JOKES

MasieroGermano88

P Masiero & FSR Germano
JSD as an Object-Oriented Design Method
ACM SIGSOFT Software Engineering Notes v13n3 (Jul 1988)pp22-23
=IDEA DAD non-sequential

Mason03

John Mason
Comments Considered Harmful
ACM SIGCSE Bulletin V35n2(Jun 2003)pp120-122
=ESSAY COMMENTS STYLE TECHNICAL EDUCATION
(1) Parody of Dijkstra's letter written as student
(2) Anecdotal experience in industry.
(3) ideas used while teaching.
Proposes "reversed assignments": give larger program with bad style and asked to modify it.

MassonetLamsweerde97

Phillipe Massonet & Axel van Lamsweered
Analogical Reuse of Requirements Frameworks [RE'97]
=ADVERT KAOS SPECIFICATION LANGUAGE ontology temporal logic graphic tool

Mastro85

?? Mastros
Three Dimensional Design
ACM SIGSOFT Software Engineering Notes v10n5(Oct 1985)
=IDEA SAD DFD ERD sequential PURPOSE System Reality

MathewsMcGee90

Robert W Matthews & William C McGee
Data Modeling for Software Development
IBM Systems Journal V29n2(1990)pp228-235
=DEMO Conceptual vs Logical vs Physical
p233 orthogonal to Zachman

MathiassenNgwenyamaAaen05

Lars Mathiassen & Ojelanki K Ngwenyama & Ivan Aaen
Managing Change in process improvement
IEEE Software Magazine V22n5(Nov/Dec 2005)pp84- 91
=CASE STUDY 4 DANISH COMPANIES VARIED SPI IMPROVEMENT
All had limited success: software process was improved,none achieved as much as they wanted initially.
SPI is organizational change.
(above)|-need to use change management techniques.
- Understand context: source, organization structure,existing processes and needs.
- Create (and communicate) vision
- Manage commitment
- Plan
- Stay agile
- Monitor improvement
One size does not fit all. For example,
1. maintenance does not follow a development process.
2. Small and simple projects do not need all the procedures and data recording of a complex or large project.
In all 4 projects nobody expected that management would have to change!

Mathur87

Raghubir N Mathur
Methodology for Business System Development
IEEE Trans Soft Eng VSE-13n5(May 1987)pp593-601
=DEMO GRAPHIC STRUCTURE FORMS PDL
stimuus response paths and PDL layout forms

Matsson09

Anders Mattsson & Bjorn Lundell & Brian Lings & Brian Fitzgerald
Linking model-driven development and software architecture: A Case Study
IEEE Trans Software Engineering V35n1(Jan/Feb 2009)pp83-93
=EXPERIENCE MDD ARCHITECTURE RULES UML Rhapsody RUP EMBEDDED RISKY Combisoft Saab
The abscence of a formal ay to record architectural rules lead to extra effort being involved

Matsumoto95

Masoo J Matsumoto
Research to Shed Light on Software Shadows
IEEE Software Magazine V12n5(Sep 1995)p16(Insider)
=EXPERIENCE vs ACADEME LEGACY MAINTENANCE

MatsumuraMizutaniArai87

Kazuo Matsumura & Hiroyuki Mizutani & Masahiko Arai
An Application of Structural Modeling to Software Requirements Analysis and Design
IEEE Trans Soft Eng VSE-13n4(Apr 1987)pp461-471
=DEMO GRAPH CASE
structural_modeling::= extract functional terms;dataflows;control skeleton;...
USER requirements >< functions matrix QFD-like

MatsuuraEtal97

Saeko Matsuura & Hironobu Kutuma & Shinichi Honiden
EVA: A Flexible Programming Method for Evolving Systems
IEEE Trans Softw Eng VSE23n5(May 1997)pp296-313
=DEMO SPECIFICATION CODE REUSE
changes in SPECIFICATION lead to CODE changes...REUSE CODE+CODING process+Spec change process

MattoliniNesi01

Riccardo Mattolini & Paolo Nesi
An Interval Logic for real-Time system Specification
IEEE Trans Software Engineering V27n3(Mar 2001)pp208-227
=THEORY MATHEMATICAL LOGIC TEMPORAL SPECIFICATION LANGUAGE TILCO

MatosGrasser05

Victor Matos & Becky Grasser
SQL-based Discovery of exact and approximate functional dependencies
ACM SIGCSE Bulletin V36n4(Dec 2004)pp58-63
=DEMO SQL MATH

MattssonBoschFayad99

Michael Mattsson & Jan Bosch & Mohamed E Fayad
Framework Integration: Problems, Causes, Solutions
=EXAMPLES OBJECT-ORIENTED COMPONENTS ARCHITECTURE
Problem names: Inversion of control, integrating with existing tools and systems, gap between frameworks, overlapping frameworks, fucntionallity in two frameworks, architectural mismatches

Maurer00

Peter M Maurer
Components: What if they gave a revolution and nobody came
IEEE Computer Magazine V33n6(Jun 2000)pp28-34
=HISTORY MODULES COMPONENTS TOOLS MICROSOFT VisualBasic VBX OLE COM DCOM ActiveX CORBA EXAMPLE

Maurer04

Peter M Maurer
Metamorphic Programming: Unconventional High Performance
IEEE Computer Magazine V37n3(Mar 2004)pp30-38 Letter V37n5(May 2004)pp6-7
=DEMO POINTERS INDIRECT GOTOS PERFORMANCE STATES METAMORPHISM > POLYMORPHISM
Encode states by pointers. Transitions handled not by ifs but by using indirect (computed) goto.
Replace labels by functions in groups. Each one shares the stack frame of the others in the group.
Claims order of magnitude speedups.
Example of quicksort.
Does not mention GoF State Pattern.

Max89

N Max
Letter: Get Graphic
Commun ACM v32 n10(Oct 1989)pp1162-1163

MaxionOlszewski00

Roy A Maxion & Robert T Olszewski
Eliminating Exception handling errors with Dependability Cases: a comparative, empirical study
IEEE Trans Software Engineering V26n9(Sep 2000)pp888-906
=EXPERIMENT ERROR-HANDLING TESTS EXCEPTIONS
exceptional_children::mnemonic = { Computational, Hardware, I/O and files, Library functions, Data input, Returned value from function, External user/client, Null pointer and memory }
mnemonic+fishbone diagram; list hazards/exceptions; fault-tree; causal paths; defense .
compares dependabillity with safety and hazard analysis.
dependabillity cases better than collaboration better than individual better than N-version program

MaxwellForselius00

Kayrina D Maxwell & Pekka Forselius
Benchmarking Software Development Productivity
IEEE Software Magazine V17n11(Jan/Feb 2000)pp80-88
=EMPIRICAL STATISTICS 26 Companies in Finland - 42 variables
most variance from Company in Finland, 5 sectors(manufactring best), Each sector has different variables as most significant and different formulae(p 84)
uses the Experience 2.0 function-point measure of productivity

Mayhew99

Deborah J Mayhew
The usability engineering lifecycle: a practitioner's handbook for user interface design
Morgan Kaufman SF CA 1999 ISBN 1-55860-561-4
=HANDBOOK USER LIFECYCLE GUI

MayhewMGouHaaseHartemink12

Michael B Mayhew & Xin Guo & Steven B Haase & Alexander J Hartemink
Close encounters of the collaborative kind
IEEE Computer Magazine V45n3(Mar 2012)pp22-30
=ARTICLE ANALYSIS DESIGN ITERATION BIOLOGY YEAST DOMAIN LANGUAGE
Describes a collaborative development of software for modeling a biological process and answering biological questions about it.
Illustrates need to find and develop a common language for the stakeholder's domain.
Need to answer biological questions. In general: make sure you know what the user's want. Whu not use cases?
Process was iterative.

Mays94

R G Mays
Forging a silver bullet from the essence of software
IBM Systems Jnl V33n1(1994)pp20-45 CR9509-0690
=ESSAY THINKING ANAYLSIS DESIGN IMPLEMENT
1. |- (May94_1): content is conceptual
2. (above)|-malleable & changeable
3. |- (May94_2): Data, multiple subdomains
4. (above)|-complex
5. |- (May94_3): representations crystalize concept
6. (May94_2, May94_3)|- (May94_4): anticipate all possibilities
7. |- (May94_5): more conceptual than mathematical or graphical
8. (above)|-not visualizable
9. (May94_4, 5May94_)|- (May94_6): intense thinking
10. (May94_4, May94_5, May94_6)|- (May94_7): verification in the mind, formal in representation
11. (May94_3)|- (May94_8): programs are objects in the reaal world
12. (above)|-have to change
13. (above)|- (May94_9): software is an asset to be maintained & enhanced,
14. (above)|-develop thru incremental enhancements,
15. (above)|- (May94_10): first task of development is to re-enliven the conceptual construct in the developers thinking
  ----
  p33: support intellectual control: design reabstraction+formal verification
  p35-36:higher-order constructs: generic constructs& reuse+ doamin specific+ higherlevel languages
  p37: support development of concepts
16. :program understanding tools: incremental development
17. objects

MayTaylor03

Daniel May & Paul Taylor
Knowledge Management with Patterns Commun ACM V46n7(Jul 2003)pp94-99
=ANECDOTE ORGANIZATION PATTERNS WRITING SOCIAL
Patterns are a way to record/transmit/share/create organization's policies.
Not rules: rules in context!
PATTERN:=Net{name, context, problem, forces, solution, rationale, resulting_context, related_patterns}.
Process: incrementally and slowly make tacit knowledge explicit: identify; draft; relate to existing; editing(shepherd); workshop

Mazumbar02

Subhasish Mazumbar
Tackling the Software Crisis via Conceptual Modeling
[SCI2002] V1(Jul 2002)
=IDEA USER OPEN MODEL
Let the user of a software product see the schematics and conceptual design documents!

Mazzaetal9?

Mazza
Software Engineering Standards
Prentice Hall Upper Saddle River NJ 19?? ISBN 0-13-106568-8
=SURVEY STANDARDS Source

MaziniOsterman04

Mira Mazini & Klaus Osterman
Variability Management with Feature-Oriented Programming and Aspects
Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp127-136
=ADVERT Caesar TECHNICAL VARIABILITY FEATURES vs ASPECTS AspectJ FOA
Feature oriented programming allows the coding of refinements to existing base classes in layers. They may be mixed. This is implicitly hierarchical and the hierarchy may not fit other structures. They don't handle changes to the code that are cross-cutting concerns that impact many methods.
Aspects handle cross cutting concerns (by pointcut+advice) but can not form hierarchies.
Caesar::language=combines layers and aspects....
Will be applied in [ http://www.topprax.de/ ] the TOPPrax project.

McAllister11

Neil McAllister
The futility of developer productivity metrics
Infoworld (Nov 17 2011) [ the-futility-developer-productivity-metrics-179244?page=0,1 ]
=HARMFUL CODE METRICS IBM
Also see report [Bednarz11]

McBreen03

Pete McBreen
Questioning Extreme Programming
Addison-Wesley 2003
=ESSAY XP METHODS ONE-SIZE
Reviewed and praised in Glass03?

McBride07

Matthew R McBride
The software architect
Commun ACM V50n5(May 2007)pp75-81
=EXPERIENCE+SURVEY ARCHITECT PEOPLE ANALYSIS DESIGN MODULES QUALITIES ECONOMICS MANAGEMENT
Based on some classic readings and some experiences(positive and negative) as acting as chief architect.
Software Architects are responsible for the organization of the software -- the parts and how they work together.
Tasks
- Mitigate unbounded Complexity
  - Strategies: management, risk analysis, communication, educate stake holders in technology options and values
  - Tactics: requirements, layers, defined interfaces, iteration, increments
- Manage Functional Requirements
- Communicate Effectively. Developers, Senior management, project management, customers are different.
- Embrace leadership.
- Pay attention to nonfunctional requirements
- Bring a well stocked toolkit
  - Patterns and idioms
  - Frameworks
  - Best Practices
- Report results.

McCamantErnst03

Stephen McCamant & Michael D Ernst
Predicting Problems Caused by component upgrades
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp287-296
=DEMO MODULE TESTING LOGIC CONTRACT V&V EVOLUTION Daikon Simplify PERL
Before putting an upgraded component into an application, use the application+old component to generate a mathematical contract for the old component, then derive a similar contract for the new one. Only safe if the new contact is stronger than the old one.
contracts::=$ Net{ pre, post: @States}.
For contracts c1, c2, c1 is_stronger_than c2::= (c1.pre ==> c2.pre) and ((c1.pre&c2.post)==> c1.post).
Worked well on to PERL module upgrades!
Nice example of upgrading swap: will work in a bubble sort, but not in a particular selection sort.

McCannRoman98

Peter J McCann & Gruia-Catalin Roman
Compositional Programming Abstrations for Mobile computing
IEEE Trans Soft Eng V24n2(Feb 1998)pp97-110
=ADVERT non-sequential Net/Web LANGUAGES(UNITY) LOGIC PROOF

McCannRoman99

Peter J McCaqnn & Gruia-Catlin Roman
Modeling Mobile IP in Mobile UNITY
ACM TOSEM V8n2(Apr 1999)pp115-146
=CASESTUDY MOBILE UNITY LOGIC PROOF Protocol
[McCannRoman98]

McCarthy87

John McCarthy
Generality in Artificial Intelligences
Commun ACM V30n12(Dec 1987)pp1030-1035 based on 1971 Turing award talk
=ESSAY AI LOGIC LPC not PROLOG situation calculus frame problem nonmonotonicity.
Similar problems arrise in formal specifications: [Borgidaetal95]

McCarthyetal62

John McCarthy & Michael I Levin
Lisp 1.5 Programmers Manual: the Computation Center and Research Laboratory of Electronics, Massachusetts Institute of Technology
MIT press Cambridge MA 1962
=MANUAL LISP case-study formal
2d ed., 1965, reprinted 1975
The over-all design of the manual is based on McCarthy's paper "Recursive functions of symbolic expressions and their computation by machine", Communications of the ACM (Apr 1960)

McCarthyJ95

Jim McCarthy
The Dynamics of Software Development
Microsoft Press Redmond WA 1995 ISBN 1-55615-823-8 $24.95 CR9703-0182(Tse)"like marketting and escapist"
=EXPERIENCE PEOPLE MS-PROCESS

McCarthyJ95a

Jim McCarthy
Implementing Feature Teams
Software Development Magazine(Dec 1995)pp55-56+58+60-61
=ADVERT from McCarthyJ95

McCarthyMcCarthy02

Jim McCarthy & Michele McCarthy
Software for your Head
Addison-Wesley Reading MA 2002
=EXPERIENCE TEAM MEETINGS PATTERNS PEOPLE
The_Core::= { Check_in, Check_In, Pass, ... }.
Advertised in [DeMarco03]

McClintock97

Colleen McClintock
The Logic of Business Rules
Software Development magazine V5n11(Nov 1997)pp44-48+50
=DEMO DATA REALITY LOGIC CORBA IDL
DATA encodes REALITY LOGIC: repository to collect formulate store and maintain rules(Rochade/Microsoft/Platinum) hence models diagrams executable(CORBA IDL) rule servers

McConnell93

Steve McConnell
Code Complete: A Practical Handbook of Software Construction
MicroSoft Press Redmond WA 1993 ISBN 1-55615-484-4 BNB92-41059 QA76.6 D3 M39 1993
=HANDBOOK CODE MS-PROCESS

McConnell96

Steve McConnell
Missing in Action: Information Hiding
IEEE Software magazine V13n3(Mar 1996)pp128+127
=EDITORIAL INFORMATION HIDING
can be used at all levels and improves all methods. Value increases with evolutionary and incremental development

McConnell96a

Steve McConnell
Daily Build and Smoke Test
IEEE Software Magazine VSE13N4(Jul 1996)pp144+143
=EXPERIENCE MS-PROCESS TESTING

McConnell96b

Steve McConnell
Software Quality at Top Speed
Software Development Magazine (Aug 1996)pp39-42
=TEHORY QUALITY SQA vs DEVELOPMENT TIME MS-PROCESS RAD
QUALITY: relationship between SQA and development speed. Argues that removing 95% of defects before release gives the shortest development time.
Compares testing walkthrus reading and inspections. Part of book [McConnell96c]

McConnell96c

Steve McConnell(mailto:stevemcc@construx.com)
Rapid Development: Taming Wild Software Schedules
MicroSoft Press Redmond WA 1996
=EXPERIENCE MS-PROCESS RAD
[McConnell96b]

McConnell97a

Steve McConnell
Annualized Software Delivery
IEEE Software Magazine V14n1(Jan/Feb 1997)pp104+103
=IDEA MS-PROCESS EVOLUTION INCREMENTAL MAINTENANCE
deliver annual enhancements while simultaneously developing a new version:dropping bad legacies and looking for better concepts.

McConnell97b

Steve McConnell
Software's Ten Essentials
IEEE Software magazine V14n2(Mar/Apr 1997)144+1143
=ADVERT PROCESS
software_project_essentials::=product spec; detailed USER interface prototype; realistic schedule; explicit priorities; active risk management; SQA plan; detailed activity lists; [SCM;] software architecture; integration plan
Project_Breathalyzer::= See http://www.spmn.com/.

McConnell97c

Steve McConnell
Gauging Software Readiness with Defect Tracking
IEEE Software magazine V14n3(May/Jun 1997)136+135
=EXPERIENCE DEFECT QUALTITY SQA TIME-BOX
historical defects/KLoC guiding release time and testing + defect seeding and defect modeling

McConnell98

Steve McConnell
Problem Programmers
IEEE Software Magazine V15n2(Mar/Apr 1998)pp128+127+126
=ESSAY PEOPLE
experiments have shown 10:1 productivity but 10% never finish
typically: will hide ignorance + will be territorial + grumbles
early reviews will detect uncooperative people so all must take part in reviews or leave

McConnell98b

Steve McConnell
Feasibility Studies(Best Practices)
IEEE Software magazine V15n3(May/Jun 1998)pp120+119
=EXPERIENCES LIFECYCLE
study feasibility first

McConnell99

Steve McConnell
After the Gold Rush
IEEE Software Magazine V16n1(Jan/Feb 1999)pp6-8
=ESSAY SITUATIONS
New technology leads to rush of high risk entrepreneural small sized hackers,... and the good can survive

McConnel00

Steve McConnell(ed)
The Best Influences on Software Engineering
IEEE Software Magazine V17n11(Jan/Feb 2000)pp27-17
=INTERVIEW+POLL
Net
1. reviews and inspections [Fagan76]
2. informatin hiding [Parnas72b]
3. incremental development
4. user involvement
5. automatic revision control
6. development uing the Internet
7. programming languages hall of fame: FORTRAN,COBOL, Turbo Pascal, Visual Basic
8. capability maturity model for software
9. object-oriented progrmming
10. component-based development
11. metrics and measurement
(End of Net)

McConnell00b

Steve McConnell
what's in a name?
IEEE Software Magazine V17n5(Sep/Oct 2000)pp7-9
=MOTIVATION for STANDARD GLOSSARY
Terms like: requirement, specification, architecture, and prototype have many usages.
$?M court case consequence.
recommends IEEE glossary

McConnell00

Steve McConnell
Art, science, and Engineering
IEEE Software Magazine V18n2(Mar/Apr 2000)pp9-11
=ESSAY Art science Engineering
Reims Cathedral vs Sidney Opera House? Which you prefer is a matter of art but which can be built is a matter of engineering.
"Art without engineering can be impossible".
Commerce and craft precedes science and engineering.
Science consists of solved problems.

McConnell02

Steve McConnell
Real Quality for Real engineers
IEEE Software Magazine V19n2(Mar/Apr 2002)pp5-7
=EDITORIAL QUALITIES CRAFT VS ENGINEERING
maps different qualities of product and project and correlates them.
craftsman defines qualities in his/her own times.

McConnell02b

Steve McConnell
I know what I know
IEEE Software Magazine V19n3(May/Jun 2002)pp5-7
=EDITORIAL one-sise etc.

p7: Notes existence of clusters of practices that are best in certain situations.
Table

Situation	Practices
embedded systems	phased and gated with lots of upfront requirements and design
Software products	code focused with highly committed individuals working closely with management and marketing + extensive independent testing
in-house business	executive sponsorship+steady end-user involvement+ moderate requirements documentation + developer testing
Others?`How?

(Close Table)

McCormick01

Michael McCormick
Programming Extremism
Commun ACM V44n6(Jun 2001)pp109-111
=HISTORY EVOLUTION ITERATION XP CMM RUP OPEN PEOPLE CULTURES
XP is the latest manifestation of a long running religious conflict between programmers/hackers/scruffies and software engineers/computer scientists/tweedies.
Group_P_Beliefs::=
Net
1. |-code is easy to change.
2. |-verbal is good
3. |-the code is the design.
4. |-good design emerges from development.
5. |-Programmers colloborate.
6. |-Work with peers.
7. |-requirements should be informal.
8. |-RAD was good.
(End of Net)
Group_S_Beliefs::=
Net
1. |-code is expensive to change.
2. |-written is good
3. |-the code is a poor way to show design.
4. |-good design comes before code.
5. |-Programmers can not communicate
6. |-Review to find defects
7. |-Formal specifications and change control
8. |-"I told you RAD would fail".
(End of Net)
Compare [Sotirovski01] "fail fast" vs "right first time".
Both have succeeded and both have failed on different projects. One size does not fit all.
See Methodology_Space at [Humans_and_Technology].
Humans_and_Technology::= See http://members.aol.com/humansandt/.

McCracken99

Daniel D McCracken
An Inductive Approach to Teaching Object-Oriented Design
ACM SIGCSE Bulletin -- Inroads V31n1(Mar 1999)pp184-188
=EXPERIENCE Teaching sophomore 1.month team project
Feedback opinions on one page draft design with comments to class.

McCrayGallagher01

Alexa T McCray & Marie E Gallagher
Principles for Digital Library Development
Commun ACM V44n5(May 2001)pp49-54
=EXPERIENCE
Expect change, know your content, involve the right people, design usable systems, ensure open access, beware of data rights, automate whenever possible, adopt and adhere to standards, ensure quality, be concerned about persistence.

McCue78

Gerald M. McCue
IBM's Santa Teresa Laboratory: Architectural design for program development
The IBM System J. V17n1 (1978)pp 4-
=EXPERIENCE DESK PRODUCTIVITY
Influence of layout desk space etc on programmer productivity...

McDaniel98

Herman McDaniel
Computer Snafus
Chicora pub inc Myrtle Beach SC1998 ISBN0-9663993-0-7 CR9912-0909 QA76.9 F34 M37
=DATA RISKS ERRORS CYBERCRUD

McDermid89

John A McDermid(Ed)
The Theory and Practice of Refinement: Approaches to the Formal Development of Large-Scale Software Systems
Butterworths London UK 1989 QA7676 D47T48 1989 ISBN 0-408-03981 BNB 89-22172 Dewy 005.1
=WORKSHOP FORMAL TOP-DOWN Z VDM REQUIREMENTS
1. p136 specification is a mixture of formal text and natural language text Chapter 6, Z specification is a set of states, an initial state and some relations on the set of states [McDermid89]
  Contents
2. Forward: two obstacles: modularization and refinement
3. John A McDermid Intro pp1-12 Alan Dix & Michael Harrison pp12-26.p14 Design of editor determined by QT(screen vs line)
4. Cliff B Jones pp79-89. History of refinement in VDL, VDM ...Operation decomposition(pre,post), ADTs, Reification (MAJackson)
5. Steve King & Ib Holm Sorenson, pp90-121 Library: requirements,spec( abstract state, operations), design(states, invariants, operations, algorithm). proof oblgations. experienced designers "just know" how to implement a spec.
6. Ruaridh Macdonald & Chris Sennett pp122-133. security (and safety) properties require special refinement. Some functions can be partly incorrect and extra properties have to be proved.
7. Dave Neilson pp134..161. pp150 oo-refinement (finite approximation)
8. John B Wordsworth Program construction sort pp179-190. formal requires guidance by human and is pushed by nonfunctional pressures.
9. JCP Woodcock & B Dickinson pp191-217. Proof rules. Problems with editting(p207)

McDermid91

John A McDermid
Software Engineer's Reference Book
CRC Press Boca Raton Florida 1991 ISBN 0-8493-7766-8
=REFERENCE
Has section on Formal Development

McDonaldEdwards07

Sharron McDonald & Helen M Edwards
Who should test whom
Commun ACM V50n1(Jan 2007)pp67-71
=HARMFUL PROGRAMMER EXPERIMENTS PSYCHOLOGY TESTS

McDowellEtal06

Charlie McDowell & Linda Werner & Heather E Bullock & Julian Fernald
Pair programming improves Student Retention, confidence, and program quality
Commun ACM V49n8(Aug 2006)pp90-95 CR 0707-0729
=EXPERIMENT PEDAGOGY 554 UCSC STUDENTS PAIR-PROGRAMMING vs LONERS
Students who do pair programming do better in exams and in a later nonpairing class.

McFarland91

Michael C. McFarland (SJ)
Ethics and the Safety of Computer Systems
IEEE Computer V24n2(Feb 1991).
=ESSAY ETHICS RISKS

McGee95

W C NcGee
Comparative review of books on object-oriented databases
[CR] 9508-0576
=SURVEY object-oriented data TOOLS OODBMS vs RDBMS

McGillVolet95

Tanya McGill<mcgill@murdoch.edu.au> & Simone Volet
An Investigation of the Relationship between Student Algorithm Quality and Program Quality
ACM SIGCSE Bulletin V27n2 (Jun 1995)pp43-48
=EXPERIMENT PROCESS QUALITY
Observed how groups designed work and then compared the result programs. very similar rankings. small sample.

McGrawHarbison97

Karen McGraw & Karan Harbison
User-centered Requirements: The Scenario-based Engineering Process
Lawrence Erlbaum Associates Inc Hillsdale NJ 1997
=MANUAL USER SCENARIOS REQUIREMENTS METHODS(SEB)

McGregorDyer90

John D McGregor<johnmc@cs.clemson.edu> & Douglas M Dyer
A note on inheritance and state machines
ACM SIGSOFT Software Engineering Notes V18n4(Oct 1993) pp36-43
=IDEA OBJECT-ORIENTED STATECHARTS OBJECTCHARTS

McGregorKorson90

John D McGregor & Tim Korson(Guest Eds)
Object Oriented Design
Commun ACM V33n9(Sep 1990)pp38-159
=ADVERT OBJECT-ORIENTED DESIGN OOD

McGregorKorson94

John D McGregor & Tim Korson
Integrated Object Oriented Testing and Development Processes
Commun ACM V37n9(Sep 1994)pp59-77(in Binder94)
=ADVERT SASY method TDD? TESTING [Binder94]
1. SASY::=following,
  Net
  (End of Net)

McGregorMajor00

John D McGregor & Melissa L Major
Selecting Test Cases based on user priorties
Software Development Magazine V8n3(Nov/Dec 2000)pp26-28+31
=DEMO USECASE TESTING OBJECT-ORIENTED
profile each actor with frequecies for each usecase; assign criticallity to each case; combine; allocate test cases to usecases based on product.

McGregorSykes92

John D McGregor & David A Sykes
Object-Oriented Software Development: Engineering Software for Reuse
Van Nostrand Reinhold NY NY 1992 ISBN 0-442-00157-6 QA76.6.M416
=HOWTO REUSE OBJECT-ORIENTED ERA OMT STD inheritance tools persistence

McIlroy86

Doug McIlroy
Part of Programming Pearls Ed Jim Bentley
Commun ACM v29 n6 June 1986 (p481)
=ESSAY non-sequential pipes

McIlroy90

Doug McIlroy
Letter to the Commun ACM May 1990
=LETTER RISKS

McKeagMilligan80

?? McKeag & ?? Milligan
An Experiment in Parallel Program Design
Software Practice & Experience v10 pp687-696
=EXPERIENCE non-sequential Technical

McKee95

George McKee<mckee@neosoft.com>
A few (proposed) fundamental laws of computation
IEEE Computer V28n1(Jan 1995)pp120(Open Channel)
=IDEAS

McKenney96

Paul E McKenny
Selecting Locking Primitives for Parallel Programming
Comm ACM V39n10(Oct 1996)pp75-82
=IDEA 5 patterns ARCHITECTURE NONSEQUENTIAL

McKim96

James C McKim
Programming by Contract
IEEE Computer Magazine V29N3(Mar 1996)pp109-111
=ADVERT CONTRACT Eiffel
Eiffel "requires" and "ensures". Client responsible for the first
server will then be responsible for second. Rigorous documentation not executable code

McKensie11

Patrick McKenzie
Weapons of Mass Assignment
Commun ACM V54n5(May 2011)pp54-59 [ 1941487.1941503 ]
=DEMO CODE REVIEW SECURITY RUBY ON RAILS DIASPORA
Found
1. User's authority to access or change data is not checked.
2. Mass assignment insecure and the Rails default.
3. User's data is not checked but is substituted in data base commands.
Experimental release of software to naive users.

McKinney02

Dorothy McKinney
Six Translations between software-speak and Management-speak
IEEE Software Magazine V19n6(Nov/Dec2002)pp50-52
=ESSAY natural language engineer manager people
Compare with Yourdon9? keynote on engineering vs sales.
The managers needs to know if his/her promises to the client can be kept... even of the truth makes them angry.
What to offer customers when a schedule can not be met as promised: find things to omit or delay, or even hand over as is and offer a maintenance release.

McLaughlin03

Laurianne McLaughlin
Buggy Software: Can New Liability Rules Help Quality?
IEEE Software Magazine V20n5(Sep/Oct 2003)pp104-108
=ESSAY LEGAL QUALITIES DHS NIST UCITA
UCITA::="Uniform Compute Information Transactions Act", recommended to states but passed(2003) by only two: VI & MD, protects vendors from being sued if the software fails. Vendors can specify which state law will apply in their acceptance contract.
Kaner::= See http://www.badsoftware.com/.
Trustworthy computing and MS windows server 2003. Security Engineering Strategy.
Sustainable_computing_consortium::= See http://www.sustainablecomuting.org. Don't count defects.... predict failure intensity.
Licensing? no real SWEBOK.
California law: "Security Breach Information Act" July 2003. Businesses must promptly notify customers when reasonable suspicion f unencrypted personally identifiable data is accesses in bad faith----civil damage$$$

McLaughlin07

Laurianne McLaughlin
Universal Business Language: Checkup time for an XML Vision
IEEE Software Magazine V24n3(May/Jun 2007)pp113-116
=NEWS EDI BUSINESS DATA STANDARD UBL-1 UBL-2 ebXML xCBL XML OASIS vs SOA
UBL-1 defined the 8forms most often used between ordering and invoicing.
UBL-2 has 1,000 data elemnts and 23 trade documents for government procurement.
In use in Denmark and Sweden, not in USA.
Forum [ http://www.ebexmlforum.net/ ]
ebXML used for antiterroism, healthcare payments, B2B, ...
Developing an international set of data dictionaries.
Rivals: HL7, SOA, web services,
United Nations Centre for Trade Facilitation and Elkectronic Business [ http://www.unece.org/cefact/ ]

McLellanEtal98

Sam McLellan & Al Roesler & Zongming Fei & Savita Chandran & Clay Spinuzzi
Experience Using Web-Based Shotgun Measure for Large-System Characterization and Improvement
IEEE Trans Soft Eng V24n4(Apr 1998)pp268-277
=EXPERIENCE =TOOL DATA Mining in Software
Answering one query generates more new types of queries

McLellanEtal98b

Samuel G McLellan & Alvin W Roesler & Joseph T Tempest & Clay I Spinuzzi
Building more usable APIs
IEEE Software magazine V15n3(May/Jun 1998)pp78-86
=EXPERIMENT DOCUMENTATION and TECHNICAL DESIGN effects REUSE
Need Good examples also need prototype information and good interface design

McMahon82

A M McMahon
Behavior Modification in Programming (Forum)
Commun ACM V25N6(Jun 1982)pp400-401 [ 358523.358556 ]
=LETTER USER CRITIQUE BEHAVIORISM PEOPLE HCI BEHAVIOR MODIFICATION
Doubts the morality of behaviorism in HCI as expressed in [Dwyer81]
Barry Dwyer's Rebuttal:
But
1. Using behavioral psychology in HCI is like an automobile engineer using a jointed wooden dummy.
2. By using it people started to like my work.
3. "Systems that are aversive to users are destined to fail, even if they are technically perfect."
4. Common false assumptions: People are rational, Computer save work, users out to wreck the system, computer diagnostics spot the problem
(Close But )

McMenaminPalmer86

Stephen P McMenamin & John Palmer
Essential Systems Analysis
Yourdon Press 1986
=HANDBOOK ANALYSIS

McNameeOlsonn90

Carole McNamee & Ronald A Olson
Comments on "Critical Races in Ada Programs"(KaramSanczykBond89)
IEEE Trans SE-16 n12(Dec 1990)p1439
=CRITIQUE ADA NONSEQUENTIAL

McNurlin77

Barbara C McNurlin
Using Some New Programming Techniques
EDP Analyser V15n11 (Nov 1977) Canning Pubs Inc. CA.
=EXPERIENCE Case-study PURPOSE sequential IPT New York Times
IPT::="Improved Programming Techniques".

McNutt00

Bruce McNutt
The fractal structure of data reference: applications to the memory hierarchy
Kluwer Boston Ma 2000 (adv in data base systems) QA76.9 D3 M398 CR0102-0046
=Mathematics Mainframe DATA PERFORMANCE IBM
access to one item. inter-arrival time U. P[ U > δ ] = a*delta**(- θ).

McRae02

Eric McRae
Tracking Down Killer Bugs
Dr. Dobbs #335(Apr 2002)pp58+60-61+63-64
=EXPERIENCE EMBEDDED DEBUGGING TPU AUTOMOTIVE microcode ashware
finding an unpredictable hard/software bug close to the deadline in code controlling a motor.
Test platform for debugging cost $3500 -- real time simulators of environment and system + logic analyzer. +$700 for Linux compatible debugger.
Bug found by inspiration, data gathering, hardware simulation and monitoring, plus *explaining* the situation in detail.

McUmberCheng01

William E McUmber & Betty H C Cheng
A General Framework for Formalizing UML with Formal Languages
Proc 23rd ICSE 8(July 2001)pp433-442
=CASESTUDY Object-Oriented model UML TOOL FORMAL PROMELA SPIN

Mead04

Nancy R Mead
Who is liable for Insecure Systems?
IEEE Computer Magazine V37n7(Jul 2004)pp27-33
=ARTICLE SECURITY RISKS LEGAL UCITA NCCUSL COTS Microsoft
Map showing how 6 risks come from 5 technical flaws that came from 4 actors( vendor, service provider, web company, user)

MedvidovicEtal02

Nenad Medvidovic & David S Rosenblum & David F Redmiles & Jason E Robbins
Modeling Software Architectures in the Unified Modeling Language
ACM TOSEM Trans Software Engineering & Methodology V11n1(Jan 2002)pp2-57
=DEMO DESIGN ARCHITECTURE UML OCL ADLs C2 Rapide Wright CSP
Shows how UML+OCL can define stereotypes for encoding the concerns expresses in C2, Wright and Rapide.

MedvidovicOreizyTaylor97

Nenad Medvidovic & Peyman Oreizy & Richard N Taylor
Reuse of Off-the-Shelf Components in C2-Style Architecture
[Harandi97]
=DEMO KLAX components plus connector busses. components can encapsulate OTS software easily

MedvidivicTaylor00

Nenad Medvidivic & Richard N Taylor
A classification and comparison framework for software architecture Description languages
IEEE Trans Software Eng V26n1(Jan 2000)pp70-93
=SURVEY ARCHITECTURAL LANGUAGES ADLs
languages to describe highlevel structure not implementation of parts

Meijer11

Erik Meijer
The World According to LINQ
Commun ACM V54n10(Oct 2011)pp45-51 [ 2001269.2001285 ]
=DEMO DATA QUERY LANGUAGE MONADS COMPREHENSIONS APIs
Describes semantics and syntax/API for a general query language.
Includes a form of λ notation:
```
          variable => expression
```
Provides constants and operations on sets of data such as (corrected and translated) For S:Sets, LINQ_operations (S)
Net
1. For T:Sets.
2. empty::@S={}.
3. injection::S->@S=map[s]({s}).
4. union::(@S><@S)->@S=map[l,r](l|r).
5. projection::((S->T)><@S)->@T= map[f,A])({f(a) || a:A}).
6. selection::((S->@)><@S->@S = map[p,A]({a:A || p(a)}).
7. product::(@S><@T)->@(S><T)=map[A,B]({(a,b) || a:A, b:B}).
8. cross_apply::( (S->@T)><@S )-> @T= map[f,A](|{f(a) || a:A}).
(End of Net)
Operations like these are part of Codd's relational databases, Hadoop, and other systems/languages.
Also see [MeijerBierman11] and [MeijerBierman11a]

MeijerBierman11

Erik Meijer & Gavin Bierman(Microsoft)
A co-Relational Model of Data for Large Shared Data Banks
ACM Queue Online (March 18, 2011) [ detail.cfm?id=1961297 ]
=ESSAY CATEGORY THEORY RELATIONAL DATA BASES SQL NoSQL coSQL DUALITY MATHEMATICS
"Contrary to popular belief, SQL and noSQL are really just two sides of the same coin."
Developed into [MeijerBierman11a]

MeijerBierman11a

Erik Meijer & Gavin Bierman
A co-relational Model of Data for Large Shared Data Banks
Commun ACM V54n4(Apr 2011)pp49-58 [ 1924421.19244348 ]
=DEMO =THEORY DATA RELATIONAL CATEGORY THEORY DUALITY MONADS ECONOMICS MONPOLY OLIGOPOLY
Not noSQL but coSQL because pointers are dual to foreign+>prime key relations.
Neat arguments and abstruse theorems.
Developed from [MeijerBierman11]

MeijerSzyperski02

Erik Meijer & Clemens Szyperski
Overcoming Independent extensibility challenges
Commun ACM V45n10(Oct 2002)pp41-44
=ADVERT =EXAMPLE TECHNICAL COMPONENT MS.NET C# binding NAMES CLI
Component identifiers (strong name) need to include a name, version, culture, and a public key token, etc
Culture is identified by IETF RFC1766 + RFC3006: ge-CH

Mellor85

Mellor (Ed)
Mathematical Foundations of Program Semantics
Springer Verlag 1985 (Lect Notes in CS #239)
=theory language SEMANTICS

MellorBalcer02

Stephen J Mellor & Marc J Balcer
Executable UML: A Foundation for Model-driven Architecture (2nd Edition)
Addison Wesley 2002 ISBN 0-201-74804-5 [ 0201748045 ]
=HOWTO =ADVERT DAD DDD UML PROFILE xUML MDA DOMAIN BRIDGE USECASE NONSEQUENTIAL OBJECT_ORIENTED DAD LIFECYCLES TOOLS?
Updates the ShlaerMellor Methods to use the UML. [ShlaerMellor88] [ShlaerMellor89] [ShlaerMellor92] [ShlaerMellor97] to use the UML.
Comments wanted [click here if you can fill this hole]

MellorClarkFutagami03

Stephen J Mellor & Anthony N Clark & Takao Futagami
Model-Driven Development
IEEE Software Magazine V20n5(Sep/Oct 2003)pp14-18
=INTRODUCTION OMG UML MOF MDA PIM PSM MDD
sidebar p 16. Glossary
1. MOF::="Meta-Object Facility", OMG's standards for managing model data.
2. MDA::="Model Driven Architecture", OMG standard...
3. PIM::="Platform-Independent Model".
4. PSM::="Platform-specific Model", results from weaving a [PIM] with a platform.

MellorJohnson97

Stephen J Mellor & Ralph Johnson
Why Explore Object Methods, Patterns, and Architectures?
IEEE Software Magazine V14n1(Jan/Feb 1997)pp27-30
=ESSAY OBJECT-ORIENTED ARCHITECTURE PATTERNS GENERICS
introduction to special section attempting to synthesize OO ARCHITECTURE GENERICS
Why are certain assumptions so deeply embedded in each view?

MellorKendallUhlWeise04

Stephen J Mellor & Scott Kendall & Axel Uhl & Dirk Weise
MDA Distilled
Addison Wesley Longman Redwood City CA 2004 ISBN 0201788918 CR 0502-0174
=UNREAD MODEL ARCHITECTURE MDA OMG PIM PSM MOF UML
MDA="Model driven architecture".
? Can tools automatically translate business rules into code?
Notes

Mens02

Tom Mens
A State-of-the-Art Survey on Software Merging
IEEE Trans Software Engineering V28n5(May 2002)pp449-462
=HISTORY =SURVEY TOOL THEORY CONFIGURATION SCM

MendesAl-FakhriLuxton-Reilly06

Emilia Mendes & Lubna Al-Fakhri & Andrew Luxton-Reilly (New Zealand)
A Replicated Experiment of Pair-programming in a 2nd-year software development and design computer science class
ACM SIGCSE Bulletin V38n3(Sep 2006) & proc ITiCSE 2006 pp108-112
=EXPERIMENT REPLICATION SUEVEY PEDAGOGY PAIR-PROGRAMMING JAVA DATABASE PATTERNS
Repeats experiment reported in last ITiCSE 2005 by same authors.
Pair programming in ungraded labs.
Pair programming significantly linked to better examination scores, passing rate, and quality of independent (solo?) work.
10% students hated it, 50% liked it, 15% liked it a lot.
Literature survey of 20 items.

MensTourwe04

Tom Mens & Tom Tourwe
A Survey of Software Refactoring
IEEE Trans Software Engineering V30n2(Feb 2004)pp126-139
=SURVEY REFACTOR CORRECTNESS ARTIFACTS TOOLS PROCESS
Controlling complexity in evolving software by carrying out a series of small behavior preserving transformations of artifacts: code, documents, etc.
Example: refactoring, step-by-step, generates a visitor pattern.
111 refs.

MenziesCukic00

Tim Menzies & Bojan Cukic
When to test less
IEEE Software Magazine V17n5(Sep/Oct 2000)pp107-112
=THEORY ECONOMICS SIZE TESTING COST-BENEFIT
Argues that small projects do not benefit from extensive and expensive testing. Caveats: not safety-critical software. no distinction between unit, integration, product and regression testing. Full theory in [ 00issre.pdf ]
(Theory)|-White box testing over K partitions is no more than K times better than Black-box testing.
For x:probability=one test exposes a fault, N:Nat0=`number of tests, y: probability = 1 - ( 1 - x ) ** N, N tests expose fault.
Experience: small software has dozens or hundreds of manually chosen tests.
Small numbers of tests work better than expected on small projects because all the program pathways are often all easily covered.
Shape.
du_pathway = path from where a variable is defined to where it is used.. Example study indicate that usually nearly all du-pathways were covered by 400 test cases.
In C, edges in control flow graph grow linearly with number of statements.
Saturation effect. early tests find most faults.
defines the right shape: either fault hide in such complex paths that no testing will find them or so simple that random tests will enter all regions where faults may occur.
Explanation trees of faulty behavior. NAYO (No-and-yes-0r ) networks.
Recommend overnight testing with random valid inputs.

MenziesGreenwaldFrank07

Tim Menzies & Jeremy Greenwald & Art Frank
Data Mining Static Code Attributes to Learn Defect Predictors
IEEE Trans Software Engineering V33n1(Jan 2007)pp2-12 + discussion V33n9(Sep 2007)pp637-640
=EXPERIMENT DATA MINING NASA MODULES DEFECTS METRICS Halsted McCabe Lines of Code
Don't measure predictive power on the sample used to train the data mining formula. Instead train on a largesub sample and test on the rest -- the holdout subsample.
Brittleness: The best formula for some popular forms of data mining depends on the training subsample chosen.
A Bayesian learner is less brittle and can predict defective modules correcly 70% of the time and falsely predict defects in ok modules 25% of the time.
Discussion with Hongyu Zhang and Xiuzhen Zhang in V33n9.

MenziesHihn06

Tim Menzies & Jairus Hihn
Evidence-based cost-estimation for better-quality software
IEEE Software Magazine V23n4(Jul/Aug 2006)pp64-66
=EMPIRICAL COST ESTIMATION PRACTICES MANAGEMENT
Evaluated two known practices (local calibration and stratification) for improving estimates on three published data bases of project data.
They were as likely to improve the accuracy of the estimate as make it worse!

MenziesHu03

Tim Menzies & Ying Hu
Data Mining for Very Busy People
IEEE Computer Magazine V36n11(Nov 2003)pp22-28
=CASE-STUDY DATA RULE SIMPLIFICATION TAR2
TAR2::= See http://menzies.us/rx.html

MenziesOwenRichardson07

Tim Menzies & David Owen&Julian Richardson
The strangest Thing about Software
IEEE Computer Magazine V40n1(Jan 2007)pp54-60
=SURVEY COLLARS MASTER VARIABLES CLUMPS TESTING TAR3 LURCH SPIN
Page 54: "The strangest thing about software is that it works"
Claims that in complex systems (like software) on a small number of variables are important to the outcome, and only a small partt of the possible state space is ever visitted. [MenziesRichardson06]
Therefore proposes data mining to find the important variables ( they make the software work better/worse) and then random search on these "collars" to test the software.
(dick)|-"The ideas in this paper may account for why testing works better than it should". [MenziesCukic00]

MenziesRichardson06

Tim Menzies & Julian Richardson
Making Sense of Requirements, Sooner
IEEE Computer Magazine V39n10(Oct 2006)pp112-114
=DEMO SPECIFICATION SEARCH OPTIMAL REQUIREMENTS clumps collares TAR3
Can express the space of possible requirements/specifications using a Prolog like language:
solution(Parameters), score(Parameters, Score).
And search this space for the highest scores within the space of solutions.
Search is speeded up by using clumps, collars, and the TAR3 tool.
Clumps: Given indpendent parts the distribution of the whole tends to be lognormal -- clumped in just a few starts. From Druzdel's 1994 paper: [ uai94.pdf ]
Collars: Certain choices are critical vs the rest that make little difference. From Amarel's 1968 paper.
TAR3 does a stochastic search to spot collars and clumps and feed them into a better search.... From Hu's Master's thesis UBC 2003.

Mercuri02

Rebecca Mercuri
Florida 2002: sluggish systems, Vanished Votes
Commun ACM V45n11(Nov 2002)p136
=REPORT RISKS DEMOCRACY TESTING TRADE SECRETS Sequoia
Trade secret protection made it a felony for details of the specification or internals of a voting system to be revealed!
Pre-election testing did not test to see if votes were being recorded for any but the first candidate listed on the screen!

Mercuri04

Rebecca T Mercuri
The HIPAA-potamus in Health Care Data Security
Commun ACM V47n7(Jul 2004)pp25-28
=EXPERIENCE LEGAL Health data STANDARDS HIPAA TCSEC/ITSEC
HIPAA::= "Health insurance and Portability Act", USA 1996 [ http://cms.hhs.gov/hipaa/ ]
Aimed to reform insurance, lower costs by standardize health data, and protect privacy.
Consequences2004: costs up.
Notices of privacy practices.
Close relatives blocked from info about a patient.
So: Write a "grant permission to _ to receive my health care information on request" on notification.
Or get a lawyer to draft a "power of attorney".

ISO_common_criteria::= See http://www.common?criteria.org..Close

Mercurioetal90

V J Mercurio & B F Meyers & A M Nisbet & G Radin
AD/Cycle Strategy and Architecture
IBM Systems Journal V29n2(1990)pp170-188
=ADVERT METHODS AD/Cycle IBM
1. (Software Magazine field report September 1993)|-IBM abandons AD/Cycle as a main frame product.

Mercurius05

Neil Mercurius 'Scrubbing' data for D3M
THE Journal V33n3(Oct 2005)pp15-18 =HOWTO DATA QUALITY D3M
Clean data before entering it in a central data base!
D3M::jargon=data-driven decision-making.
Define & enforce formats & coding.

MeredithBjorg03

L G Meredith & Steve Bjorg (Microsoft)
Contracts and Types
Commun ACM V46n10(Oct 2003)pp41-47
=ARTICLE WEB/NET SPECIFICATION PROCESS ALGEBRA XML WSDL BEPL4WS WSCI Web services allow components to send each other specifications. Current standards define how to share interface and protocols. However the protocol languages are to complex. Process algebras with types provide a formal basis that is powerful and simple enough to be used.
Reduction rules for processes and process types.

MernicEtal99

Marjan Mernic & Viljem Zumer & Mitja Lenic & Enis Avdicausevic
Implementation of multiple attribute grammar inheritance in the tool LISA
SIGPLAN Notices V34n6(Jun 1999)pp68-75
=ADVERT LANGUAGE TOOL GRAMMAR INHERITANCE OBJECT-ORIENTED JAVA

Merlyn91

Vaughan Merlyn (CASE Research Corp)
Is RAD 'rad'?
Software Magazine (Feb 1991) p8
=ESSAY RAD

Merz01

Ulla Merz (ed Larry Constantine)
Small Teams Big Problems
Software Development Magazine V9n3(Mar 2001)pp70-72
=HOWTO WWW helps TEAM PROCESS MANAGEMENT
content Lists

MeservyFenstermacher05

Thomas O Meservy & Kurt D Fenstermacher
Transforming software development: the MDA Road map
IEEE Computer Magazine V38n9(Sep 2005)pp-58
=ADVERT MODELLING MDA CIM PIM PSM OptimalJ EJB IBM Rose
Defines of terms.
Uses maps as analogies and gives an incomplete demo.
Assumes that MDA starts with Computation Independent work-flow models -- activity diagrams.
Also see alternate views [Thomas04] [CaplatSourrouille05] [ArlowNeustadt03]

MesserschmittSzyperski03

David G Messerschmitt & Clemens Szyperski
Software Ecosystems: Understanding an indispensable Technology and Industry
MIT Press 2003
=UNREAD ECONOMICS MARKETED SOFTWARE
See [MesserschmittSzyperski04]

MesserschmittSzyperski04

David G Messerschmitt & Clemens Szyperski
Marketplace Issues in Software Planning and Design
IEEE Software Magazine V21n3(May/Jun 2004)pp62-70
=ESSAY MARKET ECONOMICS SUNK externalities ROI
Jargon ridden discussion of factors influencing the design of software. Compare [Botting97a]
Advert for [MesserschmittSzyperski03]

MetayerEtAl11

Daniel Le Metayer & Manuel Maarek & Eduardo Mazza & Marie-Laure Potet & Stephane Frience & Valerie Viet Triem Tong & Nicolas Craipeau & Ronan Hardouin
Liability Issues in Software Engineering: the use of formal methods to reduce legal uncertainties
Commun ACM V54n4(Apr 2011)pp99-106 [ 1924421.1924444 ]
=DEMO MASS MARKET SOFTWARE CONTRACTS LOGIC TOOLS CHECKING EULA
Shows how symbolic logic can be used to clarify who is responsible for various bad things happening.
formal model in terms of mappings time stamps ->@( {Send, Receive} >< (Components | Users )^2 >< Data).
Example: A document is only received if it has been sent:
For all documents d ( (Receive, Serv, SigApp, d) in T(θ) iff (Send, SigApp, IO, d) ).
Liability maps Claims><Traces><θ -> @(Parties).

Meyer82

B Meyer
Principles of Package Design
Commun ACM V25n7(Jul 1982)pp419-428
=THEORY modules

Meyer85

Bertrand Meyer
On Formalism in Specification
IEEE Software V2n1(Jan 1985)pp6-27
=DEMO formal logic non-sequential PURPOSE Reality

Meyer88

Bertrand Meyer
Object-oriented Software Construction
Prentice Hall International series in computer science - Prentice-Hall New York NY 1988
=HOWTO OBJECT-ORIENTED Eiffel

Meyer90

Bertrand Meyer
Tools for the New Culture: Lessons from the Design of the Eiffel Libraries
Commun ACM V33n9(Sep 1990)pp68-88.
=EXPERIENCE OBJECT-ORIENTED ADTS MODULAR
Need for uniform interface to ADTs - Table IV:"item, count, has, put, force, remove, wipe-out, empty, full"
Graphic notation

Meyer90a

Bertrand Meyer
Introduction to the Theory of Programming Languages
Prentice Hall Englewood Cliffs NJ 1990 Reviews: IEEE Software Nov 1992 pp119 & 122.
=ADVERT Eiffel

Meyer90b

Bertrand Meyer
The New Culture of Software Development
JOOP V3n4(Nov/Dec 1990)pp76-81
=HISTORY CULTURE OBJECT ORIENTED COMPONENTS CLUSTERS BOTTOM UP NONSEQUENTIAL PROCESS

Meyer91

Bertrand Meyer
Eiffel: The Language
Prentice Hall Englewood Cliffs NJ 1991 ISBN 0-13-247925-7 CR 9306-0353(D.3)
=MANUAL LANGUAGE LRM Eiffel
Road-signs in Text Margins

Meyer92

Bertrand Meyer
Applying "Design by Contract"
(Special Issue: Object-Oriented Computing) IEEE Computer Magazine V25n10(Oct 1992)pp40-53
=CASE-STUDY ADT OBJECT-ORIENTED CONTRACT

Meyer93

Bertrand Meyer<bertrand@eiffel.com>
Systematic Concurrent Object-Oriented Programming
Comm ACM V36n9(Sep 1993)pp56-80
=ESSAY nonsequential

Meyer94

Bertrand Meyer<bertrand@eiffel.com>
Reusable software: the BASE object-oriented component libraries(Eiffel)
Prentice Hall Englewood Cliffs NJ 1994 ISBN 0-13-245499-8 CR9509-0653
=LIBRARY COMPONENTS OBJECT_ORIENTED

Meyer96

Bertrand Meyer<ot-column@eiffel.com>
The Conceptual Perspective(Object Technology Dept)
IEEE Computer Magazine V29N1(Jan 1996)pp86-88
=ARTICLE OBJECT_ORIENTED TECHNOLOGY
1. dynamic_binding::=choosing the precise varian of an operation as late as possible depending on the operation's arget and yet still fulfilling the same general contract.
  classification: science is about order and pretends the messy world fits an artificial order -> inheritance hierarchies.
  Seamlessness: remove barriers and distinctions betweem analysis/design/implementation
  reversibility: to be able to accept belated wisdom, spec ideas discovered when coding etc.

Meyer96a

Bertrand Meyer<ot-column@eiffel.com>
The Reusabillity Challenge
IEEE Computer Magazine V29N2(Feb 1996)pp76-78
=ESSAY GENERICITY OBJECT-ORIENTED ARCHITECTURE/Patterns
claims patterns are pedagogical ideas not reusable code
1. (1) a higher level of abstraction
2. (2) structures that have holes in them: polymorphic, generic, patterns. Predesigned in generla form. Details supplied by client.
  Not Lego Block, but plug in parts to the power sockets.
  
  Obstacles:
3. (1)first you need good things to reuse.
4. (2) management is part of the problem

Meyer96b

Bertrand Meyer<ot-column@eiffel.com>
The Many faces of Inheritance: A Taxonomy of taxonomy
IEEE Computer Magazine V29N5(May 1996)pp105-108 [ http://www.eiffel.com/ ]
=IDEA INHERITANCE OBJECT-ORIENTED
1. subtype (parent abstract)
2. view(same as parent but different)(see web version)
3. restriction(those parents that satisfy a given constraint)
4. extension(features added to parent)
  2. TECHNICAL->Software
5. Reification( a partial or complete implementation)
6. Structure(children possess parental structures)
7. Implementation(parent supplies features to child)
8. Faciltiy(parent's PURPOSE is to define set of features for its children)
9. Constant(parent supplies constants)
10. Machine((parent supplies operations)
  3. GENERICTY->Variation
11. Functional variation(feature overridden in parent, no new features)
12. Type Variation(no new features, redfine types/signatures)
13. Uneffecting(converts featrues to deffered/abstract features)

Meyer96c

Bertrand Meyer(ed)
Gurus share insight on objects
IEEE Computer Magazine V29N5(May 1996)pp95-98
=INTERVIEWS UML
UML::=Unified Modeling Language
Grady Booch
Ivar Jacobsen & James Rumbaugh interviewed by Angea Burgess & Scott Hamilton at Sw Devt 1995
1. reify::=make something into an object, example, a rule reifies a particular process. maing behaviorial things into object that can be change at runtime. Architecture: patterns+protocols+interfaces capturing a system by use-cases
  Booch:"Companies that fail have a lot of time to write papers. companie that succeed are so busy doing what they do well that they don't have time to write"
  SDL was OO in 1976!
  metrics: revenues go up!
  What degree of "ceremony" do you need?
  Why standardize the process at all?
  Different companies->-different processes
  How are you getting on together? "We have to get Ivar to grow a beard"

Meyer96d

Bertrand Meyer
Reality: A Cousin twice removed
IEEE Computer Magazine V29n7(Jul 1996)p96-97
=ESSAY OBJECT-ORIENTED TECNOLOGY

Meyer96e

Bertrand Meyer
Teaching Object Technology
IEEE Computer Magazine V29n12(Dec 1996)p117
=EDUCATION OBJECT-ORIENTED
Hit them twice::=training course; experience;training course(same material); advanced training.

Meyer97

Bertrand Meyer
Practice to Perfect: The Quality First Model
IEEE Computer magazine V30n5(May 1997)pp102-103+105-106
=ADVERT QUALITY EVOLUTION INCREMENTS PURPOSE
First get highest QUALITY and then add PURPOSEs
always have a reliable robust maintainable product
not RAD but closer to MS smoke-test( [CusumanoSelby97)] plus using compiler to validate code
cf eXtreme Programming XP

Meyer98

Bertrand Meyer
The Role of Object-Oriented Metrics
IEEE Computer magazine V31n11(Nov 1998)pp123-125
=ESSAY METRICS
5 Rules: ned a goal, internal measure must imply result qualities, need a clear theory, need to calibrate, measurement has its own value anyway

Meyer99

Bertrand Meyer
The Significance of Components
=ESSAY MODULES OBJECT-ORIENTED
Need for uniform access to visible parts of components.
Need to avoid global variables and attributes that can be set.
Software Development Magazine V7n11(Nov 1999)pp56-57

Meyer00

Bertrand Meyer
Contracts for components
Software Development Magazine V8n7(Jul 2000)pp51-53
=ESSAY CORRECTNESS MODULES OBJECT-ORIENTED
IDLs omit contractual information

Meyer00b

Bertrand Meyer
The Significance of 'dot-NET'
Software Development Magazine V8n11(Nov 2000)pp51-52+54-55+58
=ADVERT LANGUAGES MODELS MS C# Eiffel# VOS CLR MSIL
VOS :Type_system= Virtual Object System.
CLR: virtual_machine = Common Language Runtime .
MSIL :language=Micosoft Intermediate Language. "JIT-ting the code".
JIT := just-in-time compilation, compile unit on first execution.

Meyer01

Bertrand Meyer
Software Engineering in the Academy
IEEE Computer Magazine V34n5(May 2001)pp28-35
=ESSAY CURRICULUM EDUCATION
Goals:= { principles, practices, applications, tools, mathematics}.
Side bar p30: principles:= {abstraction, spec vs implementation, recursion, information hiding, reuse, battling complexity, scaling up, design for change, classification, typing, contracts, exceptions, errors and debugging}.
inverted curriculum := introduces high level black box first and then goes under the hood. The wow effect.

Meyer01a

Bertrand Meyer
.NET Is Coming
IEEE Computer Magazine V34n8(Aug 2001)pp92-97
=ADVERT WWW/NET Microsoft ARCHITECTURE COMPONENTS XML ADO ASP SOAP WSDL CM selfdocumenting TECHNICAL

Meyer06

Bertrand Meyer
Testable, Reusable Units of Cognition
IEEE Computer Magazine V39n4(Apr 2006)pp20-24
=IDEA EDUCATIONAL MODULES Truc DIGRAPH
Truc::= Net{name, alternative_names, dependencies, summary, role, applicability, benefits, examples, common_confusions, pitfalls, tests_of_understanding}.
Dependency is acyclic, nontransitive, and irreflexive.
Includes "educational objectives".

Meyer08

Bertrand Meyer
Seven Principles of Software Testing
=ESSAY TESTING
IEEE Computer Magazine V41n8(Aug 2008)pp99-101
Principles
1. Testing means trying to make the software fail.
2. Tests are not a substitute for specifications.
3. Regression tests: Any failure must become permanent test...
4. Determining succes vs failure should be automatic -- use oracles. Base oracles on contracts.
5. Good testing has both manual and automatic tests.
6. Evaluate testing using objective and explicit criteria.
7. The most important property for a test is the number of faults uncovered as a function of time.

Meyer08a

Bertrand Meyer
Design and Code Reviews in the Age of the internet
Commun ACM V51n9(Sep 2008)pp67-71 [ 1378727.1378744 ]
=EXPERIENCE REVIEW SQA WWW/Net VoIP wiki Skype X-Lite Google Docs EiffelStudio
Design and code reviews can be carried out by an international team by using the web for text, chat, and voice communication in parallel.
Give access to documents when inviting people to take part. Invite them to contribute to a document of issues.
Web shared documents streamline the process. Reviewers post their issues and their comments on the issues into a shared document before the meeting. The authors responses are also posted. The meeting focusses on the interesting issues.
The meeting uses VoIP (Voice over Internet Protocol) and chat (text) as well as editting the shared issues.
Meetings are productive and not boring. Multimedia multitasking is common.
No need for a secretary the discussions, conclusions and responses are already on file!
Sample: [ 2008-02-sample.html ]

MeyerEtAl09

Bertrand Meyer & Arno Fiva & Ilinca Ciupa & Andreas Leitner & Yi Wei & Emanuel Stapf
Programs that test themselves
IEEE Computer Magazine V42n9(Sep 2009)pp46-55
=ADVERT CONTRACTS TESTING AutoTest
Contacts define unit tests...

MeyerMinginsSchmidt98

Bertrand Meyer & Christine Mingins & Heinz Schmidt
Proving Trusted Components to the Industry
IEEE Computer Magazine V31n5(May 1998)pp104-105
=IDEA SQA COMPONENTS
mathematical trust is based on subjective and social(who/how/where/...) as well as formal attributes
=ADVERT
[ http://www.trusted-components.org ]

MeyerS75

Stuart L Meyers
Data analysis for scientists and engineers
Wiley NY 1975 ISBN 0471599956
=UNREAD =TEXT STATISTICS EXPERIMENTS
Recommended by Dr. Karant.

Meyers01

Scott Meyers
Effective STL: 50 specific ways to improve your use of the standard Template Library
Addison Wesley 2001 QA76.73.C153.M49 ISBN 0-201-74962-9
=HOWTO C++ STL TECHNICAL CODE

Meyers04

Scott Meyers
The Most Important Design Guideline
IEEE Software Magazine V21n4(Jul/Aug 2004)pp14-16
=DEMO RISKS CODE GUI SAFER INTERFACES
"Make interfaces easy to use correctly and hard to use incorrectly".
Example: GUI date selector should not allow the selection of Feb 31st.
Example: giving the user of a class a resource that have to release when done.
Example: instead of constructor Date(int,int,int), declare int wrappers for Year and Day + a class with Months Jan, Feb, .... And a complete set of 6 explicit constructors: Date(Day, Month, Year), Date(Year, Day, Month), Date(Month, Day, Month), etc

MichalewiczFogel00

Zbigniew Michalewicz & David B Fogel
How to solve it: modern hehuristics
Springer Verlag NY 2000 ISBN 3-540-66061-5 CR0102-0057 I.2.8QA63.M53
=EXAMPLES MATHS ALGORITHMS TSP SAT OPTIMISATION
Real problems do not appear in chapters. You need to think.
How to mathc problems to algorithmic solutions and how to tune algorithms to specific problems.
Little computer science!
Dangerously addictive for some people.

MicrosoftResearch

Michael Barnett & Uwe Glaesser & Wolfgang Grieskamp & Yuri Gurevich & Lev Nachmanson & Wolfram Schulte & Nikolai Tillman & Margus Veanes
Foundations of Software Engineering
[ http://www.research.microsoft.com/foundations/ ]
=HOMEPAGE ASM TOOL AsmL
ASM:="Abstract State Machine".
AsmL:="Abstract State Machine Language".
Based on "Evolving Algebras".
See also [ http://www.eecs.umich.edu/gasm/ ]

MiddletonLeeIrani04

Peter Middleton & Ho Woo Lee & Shahruck A Irani
Why culling Software Colleagues is popular
IEEE Software Magazine V21n5(Sep /Oct 2004)pp28-32
=Simulation Process People
erratic performance has an intuitively bad effect on downstream work.
Many small consistently timed work products improved whole stream.
(dick)|-elementary queuing theory!

MikkonenPruuden01

Tomi Mikkonen & Peeter Pruuden
Flexibility as a Design Driver
IEEE Computer Magazine V34n11(Nov 2001)pp52-56
=EXPERIENCE REQUIREMENTS flexibility vs QUALITY in DESIGN
The unknown increases costs in many ways including schedule problems and unneeded complexity.
|-better to resolve an apparent unknown than accommodate it.

MIlesGrothMunroeMoreau11

Simon Miles & Paul Goth & Sreve Munroe & Luc Moreau
PrIMe: a methodology for developing provenance aware applications
ACM TOSEM Trans Software Eng & Methodology V20n3(Aug 2011)#8.1-42 [ 2000791.2000792 ]
=DEMO DATA PROVENANCE PROCESS XML METADATA
Provenance describes the sources of data sets.
Proposes and demonstrates a complex process for making applications track and use provenance

MiliAh-KiEtal97

Hafedh Mili & Estelle Ah-Ki & Robert Godin & Hamid Mcheick
Another nail in the coffin of faceted controlled-vocabulary component classification and retrieval
=EXPERIENCE LIBRARY REUSE RETRIEVAL
[Harandi97] pp89-98 REUSE retrieval techniques

Milicev02

Dragan Milicev
Automatic model transformations using extended UML Object diagrams in Modeling Environments
IEEE Trans Software Engineering V28n4(Apr 2002)pp413-431
=DEMO UML Object-Oriented MODEL CODE DOCUMENT GENERATION METAMODEL
Two stage process. Metamodel the source and target domains and then draw up the mapping between them.
compare recursive design and DDD.
PhD thesis tested with 3 student projects [ ~dmilicev ] Belgrade.
Mapping shown by diagrams of objects that are things in the UML model(class, operation, attribute)
package stereotypes: <<Foreach>>, <<SubStruct>>, <<sequence>>
conditional creation tag {Cond = ... }
object stereotypes: <<Ref>>
demos: state pattern->C++. OO->relational, ML->web/www. usecase->web

Milietal89

A Mili & N Boudriga & F Mili
Towards Structured Specifying: Theory Practice Application
Ellis Horwood Chichester UK 1989(USA Distribution John Wiley & Sons NY NY)
=HOWTO formal specification Reality PURPOSE
see [JaouaMilietal91]

MiliEtal99

Ali Mili & Sherif Yacoub & Edward Addy & Hafedh Mili
Toward an Engineering Discipline of Software Reuse
IEEE Software Magazine V16n5(Sep/Oct 1999)pp22-31
=ESSAY REUSE RESEARCH THEORY vs EMPIRICAL ECONOMICS ROI COTS
theory for insight,practice to be instantly useful

MiliFrappierEtal97

R Mili & J Desharnais & M Frappier & A Mili
A Calculus of programming Modification
[Harandi97]
THEORY relational demonic composition?

MiliMiliMili95

Hafedh Mili & Fatma Mili & Ali Mili
Reusing Software: Issues and Research Directions
IEEE Trans on Software Eng VSE-21n6(Jun 1995)pp528-562
=SURVEY REUSE

MiliMiliMittermeir97

Rym Mili & Ali Mili & Roland T Mittermeir
Storing and Retrieving Software Components: A Refinement Based System
IEEE Trans SE V23n7(Jul 1997)pp445-460
=THEORY REUSE RELATIONal SPECIFICATIONS =PROTOTYPE
R refines S::= ((R o L)&(S o L)&(R|S))=S where L=universal relation
partially ordered database of specifications and implementations

Milicev02

Dragan Milicev
Domain Mapping Using Extended UML Object Diagrams
IEEE Software Magazine V19n2(Mar/Apr 2002)pp90-97
=IDEA UML MODEL TRANSLATION DOMAIN to CODE FSM
Figure 1. UML Model of state machines
Meta-model has models of source, target AND the relations between them.
The meta-model generates the generators that convert source to intermediate to target code.
Adds a <<ForEach>> stereotype for packages to model translations.
Gives examples: FSM->Code, UML->RDBMS.
Used in class.

Milicev07

Dragan Milicev
On the Semantics of Associations and Association Ends in UML
IEEE Trans Software Engineering V33n4(Apr 2007)pp238-251
=THEORY SEMANTICS UML ASSOCIATION {unique} {nonunique} Z
Notes an ambiguity in the UML 2.0 standard metamodel of associations ("the restrictive") and proposes a fix("the intensional").
Very bdetailed and Precise using Z.

Miller93

Byron Miller
Object-oriented Design made easy
Impatiens Pubs minneapolis MN 1993 CR9508-0546: Apple W3 & Booch done badly
=IDEA Object-oriented Design

MillerFredricksenSo90

Barton P Miller & Lars Fredriksen & Bryan So
An Empirical Study of the Reliability of UNIX Utilities
Commun ACM V33n12(Dec 1990)pp32-44
=EMPIRICAL RISKS QUALITY UNIX

MillerJ02

Joaquin Miller (ed)
What UML should be
Commun ACM V45n11(Nov 2002)pp67-85
=COLLECTION ARTICLES UML PROPOSAL IDEAS OMG UML2 MOF2 MDA OPM U2P DSTC
Five proposals and discussions at the [ UML2.htm ] Wiki.
Selic etal argue for evolution.
Duddy argues for a family of languages -- mandatory extension requirements.
Mellor argues for a small well defined executable translatable kernel language to make tools easier.
Frank and Tyson argue for Clear clean Concise version of UML -- does UML specify systems or specifications of systems?
Dori argues that there is a need for a revolutionary change that will not happen. Suggests an Object Process diagram that integrates objects, states and processes and text relationships.

MillerR03

Roy Miller
Managing Software for Growth: without fear, control, and the manufacturing min dset
Addison-Wesley Longman, Boston MA 2003 ISBN 0321117433 CR 0409-1014
=UNREAD EVOLUTION ITERATION PROCESS AGILE COMPLEXITY
Software is not a product to be manufactured (predictable and repeated process
and end point)

MillerS01

Sandra Kay Miller
Aspect-Oriented Programming Takes Aim at Software Complexity
IEEE Computer Magazine V34n4(Apr 2001)pp18-21
=IDEA MODULES AOP [DRY]
tangling:=many modules tied together by a common concern.
crosscutting:= a concern that has to be placed in many code blocks.
aspect encapsulates the common concern and describes the modules into which it is woven.
join points:=places where an aspect is woven in, example: all public calls of printer methods.
pointcut
AspectJ::= See http://www.aspectj.org, tool that extends Java from Xerox PARC
MDSOC::="Multi-dimensional separation of concerns", uses hyperspaces. Hyper/J::=http://www.alphaworks.ibm.com/tech/hyperj.

MillerStrooper04

Tim Miller & Paul Strooper
A Framework and Tool Support for the Systematic Testing of Model-Based Specifications
ACM TOSEM Trans Software Eng & Methodology V12n4(Oct 2003)pp409-439
=CASESTUDIES TOOL MODEL CHECKING Z-like Sum SPECIFICATIONS Possum CONSTRAINT-SOLVING SETS RELATIONSHIPS MUTATION

MillingtonStapledon95

Don Millington & Jennifer Stapledon
Developing a RAD Standard(DSDM)
IEEE Software Magazine V12n5(Sep 1995)pp54-55
=ADVERT DSDM AGILE
1. DSDM::=Dynamic Systems Development Method.
  60 organisations including commerce and academe.
  DSDM Consortium Secretariat, The Coach House, Church Hill, Kingsworth, Ashford, KENT TN23 3EG, UK.
  Key success factors: easy access to users, stable nd skilled development team, a commercial appliation with clearly defined user group and flexible requirements.
  Also:
2. business requirements>quality
3. what not how
4. motivate team to business goals
5. integrate testing thru out
6. base estimates and risks assessment on functions of end product not development actions
7. Baseline high level requirements.
  Use time box scheduling: "Given this personnel-time, how much functionallity can be completed?"
  Three phases, each iterative

MillerWhalenCofer10

Steven P Miller & Michael W Whalen & Daren D Cofer
Software model checking takes off
Commun ACM V53n2(Feb 2010)pp58-64 [ 1646353.1646361 ] CR 1008-0811
=DEMO 3 CASESTUDIES TOOLS MODEL CHECKING PROOFS vs TESTING AVIATION SATISFIABILITY Simulink MATLAB Stateflow SCADE Reactis Safe State Machines Lustre NuSMV Prover ACL2 PVS C, Ada SAL
Case studies involve millions of states.
Need to take care in selecting the best tool to check the models.
Only takes a day to train people to use the tools.
Model checking found errors that testing missed, and cost lest.
Need better ways to handle floating point numbers and transcendental functions.

MillmanHarding91

Howard Millman & Elisabeth U. Harding
'Potential' Still Describes AI-Rooted Knowledge Tools
Software Magazine(Sept 1991)pp40-41+44+47+50-52
=EXPERIENCE TOOL KNOWLEDGE AI

Mills72

Harlan D Mills
Mathematical Foundations for Structured Programming
IBM Federal Systems Division (Report No. FSC 72-6012) Gettysburg MD Febuary 1972
=THEORY MATH sequential non-sequential formal structures
Later see CLEANROOM

Mills75

Harlan D Mills
The New Math of Computer Programming
Commun ACM V18n1(Jan 1975)pp43-48
=THEORY MATH LOGIC structured CLEANROOM
Also presented paper that year on getting programs right. International Conference on Reliable Software.(Berard)
Refed in Zelkowitz90, cites [BohmJaccopini66]

Mills86

Harlan D Mills
Structured Programming: Retrospect and Prospect
IEEE Software V3n6(Nov 1986)pp58-66
=HISTORY DIJKSTRA NYTIMES TOP-DOWN FUNCTIONAL AXIOMATIC ADTS CLEANRROM
p66: "An interactive debugger is an outstanding example of what is not needed - it encourages trial-and-error hacking rather than systematic design"
"and also hides marginal people barely qualified for precision programming"

Millsetal87

Harlan D Mills & Michael Dwyer & Richard C Linger
Cleanroom Software Engineering
IEEE Software V4n5(Sep 1987)pp19-25
=demo formal technical structured cleanroom

Millsetal89

Harlan D Mills & Victor R Basili & JD Gannon & RG Hamlet
Mathematical Principles for a First Course in Software Engineering
IEEE Trans Softw Eng V15n5(May 1989)pp550-559( CR9006-0527(K.3.2))
=essay formal CLEANROOM tables education

MillsGomma00

Kevin L Mills & Hassan Gomma
A Knowledge-Based Method for Inferring semantic concepts from Visual Models of System Behavior
ACM TOSEM Trans Software Engineering & Methodology V9n3(Jul 2000)pp306-337
=DEMO TOOL CODA DFD (COBRA ) to NONSEQUENTIAL ARCHITECTURE CLIPS SEMANTICS GAPHICS INFERENCE
Uses meta-model and inference to dd semantic tags and derive design. does 80% automatically

MillsLinger86

Harlan D Mills & Richard C Linger
Data Structured Programming: Program Design without Arrays & Pointers
in [BerglandZave86]
pp192-197
=DEMO ADTs Technical

MillsR92

Richard J Mills
When is a Picture a Program
(The Open Channel) IEEE Computer Magazine V25n10(Oct 1992)p128
=ESSAY VISUAL TECHNICAL

Milner80

Robin Milner
A Calculus of Communicating Systems
Springer Verlag 1980
=THEORY FORMAL non-sequential CCS timing
Time considered as a tree of possible communications.
Later algebra [Baetan90] ACP

Milner89

Robin Milner
Communication and concurrency
New York : Prentice Hall 1989. Series title: Prentice-Hall international series in computer science
=THEORY non-sequential communication timing

Milner93

Robin Milner
Elements of Interaction(Turing award lecture)
Comm ACM V36n1(Jan 1993)pp78-88
=LECTURE THEORY non-sequential communication timing CCS π-calculus Mobility

Millsap10a

Cary Millsap
Thinking clearly about performance, part 1
Commun ACM V53n9(Sep 2010)pp55-60 [ 1810891.1810902 ]
=EXPERIENCE oracle QUALITIES SPEED PERFORMANCE DIAGNOSIS AXIOMATIC
Trial and error << step by step improvements. Compare to doing algebra.
Response time is not related to throughput. Skew.
Users feel the variance not the mean. So do not express performance requirements as a mean value. Express performance requirements as
Task T takes R seconds or less P % or more of the executions.
Use sequence diagrams with timings. Profiles. Amdahl's law.
Improvements: how much vs how risky. Pick easy first to build trust.
Next Part [Millsap10b]

Millsap10b

Cary Millsap
Thinking clearly about performance, part 2
Commun ACM V53n10(Oct 2010)pp39-45 [ 1831407.1831422 ]
=EXPERIENCE QUALITIES SPEED PERFORMANCE DIAGNOSIS QUEUING THEORY KNEE COHERENCE
See [Millsap10a] part 1.
Risks include improving one part at the expense of other parts. Especially when going for a big global fix for a small local problem. Focus on what needs fixing.
Look for inefficiencies -- what can be eliminated and still get the same results?
Making any process more efficient and the load on the whole system decreases often improving overall performance.
Theory of M/M/m queues. m is number of service channels. Queueing delay as a function of load should have a long linear part before a "knee" and a curve going asymptotically up. Knee is where a line through the origin just touches the curve. When the load is above the knee a small extra load gives a big drop in performance. Variance is likely and will be noticed by users.
Coherency delays are a common cause of worse than the Queueing theory delay. They occur where processes interfere with each other. Where one process locks a shared resource typically.
Performance is a feature!

Minasi00

Mark Minasi <help@minasi.com>
The Software Conspiracy
Mcgraw-hill 2000 isbn0-07-134806-9 QA76.76 F34 M56 2000
=SURVEY RISKS ECONOMICS QUALITY ETHICS BUGS vs CMM Mass-Market Shrink-wrap PROCESS
Updates [ http://www.softwareconspiracy.com/ ]

Miner06

Andrew S Miner
Saturation for a general class of models
1st QEST & IEEE Trans Software Engineering V32n8(Aug 2006)pp559-570
=DEMO =MATHEMATICS MODEL CHECKING REACHABILITY MDD Kronecker MxD Markov

Minnick00

Chris Minnick
Visualizing Sticky Web Pages
Software Development Magazine V8n12(Dec 2000)pp29-31
=REVIEW TOOL GRAPHIC WWW PERFORMANCE USER WebFeedback1.2

Minsky67

Marvin Minsky
Computation - Finite & Infinite Machines
Prentice Hall Inc. Englewood Cliffs NJ
=THEORY language theory

MinskyY11

Yaron Minsky
OCaml for the masses
Commun ACM V54n11(Nov 2011)53-58 [ 2018396.2018413 ]
=ADVERT =EXPERIENCE FUNCTIONAL LANGUAGES OCaml Haskell ML F# Scala
OCaml:
- is Concise.
- performs almost as well as C/C++.
- has strong typing and a careful type design turns many bugs into compile errors.

Miranda01

Eduardo Mianda
Improving subjective estimates Using Paired Comparisons
IEEE Software Magazine V18n1(Jan/Feb 2000)pp87-91
=DEMO MATHEMATICS ESTIMATION
Use pairwise comparisons to form a judgment matrix. Review internal inconsistencies and then derive ratio scale. Use scale and known reference values to get better estimates.
Map verbal judgments to ratios: equal+>1 | bigger+>1.75 | smaller . 0.57 | slightly bigger +> 1.25 | slightly smaller +> 0.80 | much bigger +> 4.0 | much smaller +> 0.25 | extremely bigger > 7.00 | extremely smaller +> 0.13
judgment_matrix:= matrix(1..n><1..n -> ratio ).
geometric_mean[r] =v[r],
v[r] = a[r,*] **(1/n).
ratio[r] = v[r]/v[+].
inconsistency := sqrt(+[r] (+[c:r+1..n] (ln(a[r,c]) - ln(v[r]/v[c]) ))) /((n-1)*(n-2)/2).

Miranda02

Edwardo Miranda
Planning and Executing Time-Bound Projects
IEEE Computer Magazine V35n3(Mar 2002)pp73-79
=THEORY ESTIMATING TIME PLAN INCREMENTAL PROCESS QUALITY SPID
SPID::="Statistical Planned Incremental Deliveries",
no mention of alternatives: PERT XP
Monitors rate of progress and adjusts slack/buffers.
Uses triangular distribution with three parameters: best, most likely, worst times

MiriyalaHarandi91

Kanth Miriyala & Mehdi T. Harandi
Automatic Drerivation of Formal Software From Informal Descriptions
IEEE Trans SE-17n10(Oct 1991)pp1126-1142
=ESSAY TOOL
Informal<>natural
interactive edit of and searching for of algebraic specifications
incremental growth of dictionary of words and structures
onerous and time consuming
analogy
Program_spec::=${precondition, postcondition, required definitions}
precondition::={input:declarations, condition:proposition}...schema...analogy relation between concepts

Missaghi00

Moheb Missaghi
How many subscribers should share a modem
Dr. Dobbs #312(May 2000)pp119-121
=MATH SIMULATION QUALITY PERFORMANCE HARDWARE ISP
simulate users randomly online and offline

Mitchell90

John C Mitchell
Type systems for Programming Languages
Chapter 8( pp365-458) of Leeuwen90
=THEORY TYPE DATA
Type inference: Models of type systems. Models of assigning or infering the types of expressions.

Mitchell09

Melanie Mitchell
Complexity: a guided tour
Oxford UP UK 2009 CR 1101-0050
=POPULARISATION =HISTORY THEORIES SANTA FE INFORMATION COMPUTATION TURING EVOLUTION CHAOS GENETICS QUINE CELLULAR AUTOMATA AI NETWORKS FRACTALS SCALING POWER LAWS CYBERNETICS GENERAL SYSTEM THEORY
A personal, human, and pretty complete description of researches leading up to and associated with the Santa Fe Institute.
Includes a brief history of the rise and decline of cybernetics and of general systems theory.

MitchellMancoridis06

Brian S Mitchell & Spiros Mancoridis
On the Automatic Modularization of Software Systems using the Bunch tool
IEEE Trans Software Engineering V32n3(Mar 2006)pp193-208
=DEMO TOOL MODULE DIGRAPH MODULAR MDG BUNCH Acacia Chava
MQ:="module quality"
Partitions dependency digraph (small errors in definition on p194). Dependency is acyclic, nontransitive, and irreflexive.
Heuristic search for acceptable partition. Finding the Best is expensive.

MittermeirOppitz87

Roland T Mittermeir & Marcus Oppitz
Software Bases for the Flexible Composition of Application systems
IEEE Trans Soft Eng VSE-13n4(Apr 1987)pp440-460
=EXPERIENCE MAINTENANCE GENERIC CODE BNF USER
difficult! maintenance via generic code BNF rules matrices and structure supplied by administrator allowing laypeople to make safe changes to code
[LongDenning95]

Mitra00

Ananda Mitra
Internet, Pedagogy and Space (and power)
Proc SCI/ISAS2000 VXI pp7-11 [SCI00] [ ananda ]
=EXPERIENCE EDUCATION WWW/Net

MockusFieldingHerbsleb00

Audris Mockus & Roy T Fielding & James D Herbsleb
A Case Study of Open Source Software Development: The Apache Server
ICSE00 International Conf on Software Engineering 2000 pp263-272
=EMPiRICAL STATISTICS OPEN SOURCE TECHNICAL APACHE OSS EMAIL ARCHIVES vs commercial
Graphs and figures on debugging etc.
Open source differs from commercial development in coordination, selection, and assignment of work.
Small core of people make the changes, a larger group diagnose the problem, and a very large group people report problems.
High modularity and solid contractual interfaces help.
Open source proved to be faster, more productive and higher quality than normal commercial software.
Followup [MockusFieldingHerbsleb02]

MockusFieldingHerbsleb02

Audris Mockus & Roy T Fielding & James D Herbsleb
Two Case Studies of Open Source Software Development: Apache and Mozilla
ACM TOSEM Trans Software Eng & Methodology V11n3(Jun 2002)pp309-346
=EMPiRICAL STATISTICS OPEN SOURCE TECHNICAL APACHE MOZILLA OSS EMAIL ARCHIVES vs commercial
Many graphs and figures on debugging etc.
Open source differs from commercial development in coordination, selection, and assignment of work.
Small core of people make the changes, a larger group diagnose the problem, and a very large group people report problems.
High modularity and solid contractual interfaces help.
Open source proved to be faster, more productive and higher quality than normal commercial software.
Based on and replicates [MockusFieldingHerbsleb00]
Replicated on FreeBSD as [Dinh-TrongBieman05]

Modell92

Martin E Modell
Data analysis, Data modeling, and classification
McGraw-Hill Inc NY NY 1992 ISBN 0-07-042634-1 CR9306-0358(H.2.1)"decent summary"
=SURVEY DATA MODEL

ModerElmaghraby78

Joseph J Moder & Salah E Elmaghraby (Eds)
Handbook of Operations Research
NY NY Van Nostrand Reinhold 1978
=HANDBOOK OPTIMIZATION QUALITY TECHNICAL

ModugnoEtal97

Fracesmary Modugno & Nancy G Leveson & Jon D Reese & Kurt Partridge & Sean D Sandys
Integrated Safety Analysis of Requirements Specifications
RE'97 [RE'97] pp148-159
=CASESTUDY REQUIREMENTS RSML deviation analysis SQA RISKS TOOLS [ReeseLeveson97]
tools and mehods and human complement each other

Mody91

Rustam P Mody
C in education and Software Engineering
ACM SIGCSE BulletinV23n3(sep 1991)pp45..56
=EDUCATION C

Mody93

Rustam P Mody
Is Programming an Art
ACM SIGSOFT Software Engineering Notes V17n4 (Oct 1992)pp19..21
=ESSAY ART SCIENCE ENGINEERING

MoeDingsoyrDyba09

Nils Brede Moe & Torgeir Dingsoyr & Tore Dyba
Overcoming barriers to self-management in software teams
IEEE Software Magazine V26n6(Nov/Dec 2009)pp20-26
=EMPIRICAL 5 TEAMS PEOPLE AGILE Scrum PROCESS MANAGEMENT
Letting a team manage itself leads to efficiency ... But ...
Avoid specialisms, get generalists, encourage working together,and collocate the team.
Assign people to only one team at a time.
Build trust and commitment by avoiding unneeded control, under resourcing, etc.

Moen90

Sven Moen
Drawing Dynamic Trees
IEEE Software V7n4 (Jul 1990) p21-28
=DEMO graphic DYNAMICS

Moggridge06

Bill Moggridge
Designing Interactions
MIT Press Cambridge MA 2006 ISBN 0262134748 CR 0807-0653
=UNREAD =INTERVIEWS USER DESIGNERS
Reviewer: well designed book with DVD for designers developers and students [click here Moggridge06 if you can fill this hole]

MohaEtAl10

Naouel Moha & Yann-Gael Gueheneuc & Laurence Duchien & Ann-Francoise Le Meur
DECOR: A Method for the Specification and Detection of Code and Design Smells
IEEE Trans Software Engineering V36n1(Jan/Feb 2010)pp20-36
=DEMO TOOL DECOR DETEX CODE 15 SMELLS 4 ANTI-PATTERNS DOMAIN LANGUAGE METRICS
Anti_patterns := {Blob, Functional decomposition, Spaghetti code, Swiss Army Knife}.
Smells := {large class, low cohesion, data class, controller class, controller method, long method, no parameter, use global variable, no inheritance, no polymorphism, procedural names, one method in class, multiple interfaces, ...}.
Smells are symptoms of Anti-Patterns.
Shows how to express an informal description of an anti-pattern in terms of smells into a formal language called SMELLDL (a Domain Specific language for smells), and how to map smells into ranges of values for metrics. Hence how to spot antipatterns in code.
Tools based on theory detected many smells and antipatterns in open source code samples.
Problems with detecting smells expressed using natural language semantics of the identifiers in the code. Will try to use open ontologies.

MohaghehiIctConradi08

Parastoo Mohaghehi & Sintef Ict & Reidar Conradi
An Empirical Investigation of Software Reuse benefits in a large telecom Product
ACM TOSEM Trans Software Eng & Methodology V17n3(Apr 2008)#13pp1-31
=EXPERIENCE REUSE CODE QUALITY REWORK ARCHITECTURE
Significantly lower fault density in reused code.
Reused components are modified less the more they are reused.

MohanRamesh07

Kannan Mohan & Balasubramaniam Ramesh
Tracing variations in software families
Commun ACM V50n12(Dec 2007)68-73
=PROJECT KNOWLEDGE MANAGEMENT REQUIREMENTS DESIGNS PRODUCT LINES REUSE WHY
Analysis & Design of system to help manage product lines for 2 companies.
Do more than link requirements to designs .
Figure 1. UML. Variable requirements link to variation points in designs. Variation points linked to variants, mechanisms, and justifications. Interactions + conflicts + dependencies + constraints...
Provide integrated environment that can be used by whole organization: engineering, sales, marketing, etc.

Moitraetal88

Abha Moitra & S Sitharama Iyengar & Farokh B Bastani & I Ling Yen
Multilevel Data Structures: Models and Performance
IEEE Trans Soft Eng VSE-14n6(Jun 1988)pp858-867
=EXPERIENCE DATA PERFORMANCE

MollerSmolka95

Faron Moller & Scott A Smolka
On the Computational Complexity of Nisimulation
ACM Computing Surveys V37n2(Jun 1995)pp287-289

Molletal86

RN Moll & Michael A Arbib & AS Kfoury
An Introduction to Formal Language Theory
Springer Verlag monograph 1986
=THEORY LANGUAGE topology

Molokken-OstvoldMagne Jorgensen05

Kjetil Molokken-Ostvold & Magne Jorgensen
A Comparison of Software Project Overruns -- flexible versus sequential development Models
IEEE Trans Software Engineering V31n 9(Sep 2005)pp754-766 CR 0703-0266
=POLL INTERVIEWS 18 COMPANIES COST TIME ESTIMATION vs PROCESS AGILE SEQUENTIAL EVOLUTION ITERATION NORWAY
Effort. Sequential projects had bimodal estimates either accurate or 100% low. Flexible projects had estimates distributed about accurate.

MonarchiPuhr92

David E Monarchi & Gretchen I Puhr
A research topology for object-oriented Analysis and Design
Comm ACM V35n9(Sep 1992)pp35-47 CR9305-0301
=SURVEY OOAD OOA/D object-oriented Analysis and Design

Monin03

Jean-Francois Monin
Understanding Formal Methods Springer Verlag London UK 2003 ISBN 1-85233-247-6 QA76.6 M6513
=SURVEY FORMAL CTL Z B VDM LP HOL CCS CSP LCF LTL PVS TLA

Montagne10

Kevin Montagne
Tackling Architectural Complexity with modelling
Commun ACM V53n10(Oct 2010)pp46-52 [ 1831407.1831424 ]
=EXPERIENCE PERFORMANCE DEBUGGING PROTOTYPES
Using fake components that model behavior but not function.
Drivers fake the user activity and slaves mimic server systems.

Montgomery94

Susan Montgomery
Object-oriented information engineering: Analysis, design, and implementation
Academic Press Prof San Diego CA 1994 ISBN 0-12-505040-2 [CR] 9502-0058
=THEORY DAT OBJECT-ORIENTED ANALYSIS DESIGN HIDING

Moody09

Daniel L Moody
The "Physics" of Notations: Towards a scientific basis for constructing visual notations in Software Engineering
IEEE Trans Software Engineering V35n6(Nov/Dec 2009)pp756-779
=THEORY GRAPHICS DIAGRAMS EXAMPLES DFD UML ERD PEOPLE PSYCHOLOGY
Presents an exhaustive model of the possibilities for a diagram and there psychology.
Describes various pathologies.
Compares different notations.
Suggests new combinations. Example crowsfeet with multiplicities!
Notes that newer diagrams (UML) seem to be worse than the older ones
Applied in [MoodyHeymansMatulevivius10]

MoodyHeymansMatulevivius10

Daniel L Moody & Patrick Heymans & Raimundas Matulevicius
Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation
Requirements Engineering V15n2(2010)pp141-175 RE'09 Special Issue
=DEMO COGNITIVE GRAPHIC DESIGN i* istar SD SR INTENTIONS
Detailed and constructive criticism of i* notations.
Bsed on [Moody09]

Mooers66

Calvin N. Mooers, Rockford Research Inst
TRAC: A Procedure-Describing Language for the Reactive Typewriter
Commun ACM V9n3(Mar 1966)pp215-219
=DEMO LANGUAGE MACRO implementation USER
Also see [ 105.htm ] [ mooers.htm ] [ hw_trac.html ] [ lang_list.html ] and an implementation in Perl: //locke.ccil.org/pub/retro

Mookerjee05

Radha Mookerjee
Maintaining Enterprise Software Applications
Commun ACM V48n11(Nov 2005)pp75-79
=THEORY evolution maintenance multiple applications SYSTEMS COSTS
Argues that it pays to schedule joint maintenance when fixed costs are high, applications are coupled, and the rate of change is low.
Recommends separating implementation from interface and the use of wrappers, hubs, and web services.
Organization: recommends separating development from maintenance,

MoonYeomChae05

Mikyeong Moon & Keunhyuk Yeom & Heung Seol Chae
An Approach to Developing Domain Requirements as a Core Asset Based on Commonality and Variability Analysis in a Product Line
IEEE Trans Software Engineering V31n7(Jul 2005)pp551-569
=CASE STUDY ETRAVEL REQUIREMENTS VARIABILITY DOMAIN MODEL COMPONENTS CASE TOOL DREAM USECASE UML XML
Primitive Requirements: parts of use cases.
Matrix of primitive requirements vs products.
Stereotype use cases as<<common>>or <<optional>>

Moore90

Andrew P Moore
The Specification and Verified Decomposition of System Requirements Using CSP
IEEE Trans Software Engineering SE-V16n9(Sep 1990)

Moore95

James W Moore
Software Engineering Standards: A User's Road Map
IEEE Comp Soc 2000 ISBN o-8186-8008-3 QA76.758M66 2000
=SURVEY STANDARDs

Moore99

James W Moore
An integrated collection of Software Engineering Standards
IEEE Software Magazine V16n6(Nov/Dec 1999)pp51-64
=ADVERT SWEBOK PLAN ENGINEERING

MooreG91

George Moore
Crossing the Chasm
??
=ESSAY MARKET ECONOMICS USER

MooreG95

George Moore
Inside The Tornado
Harper-Business $25
=EXPERIENCE Netscape

MooreJRada96

James W Moore & Roy Rada
Organizational Badge Collecting
Comm ACM V39n8(Aug 1996)pp17-21
=HISTORY STANDARD LIFE-CYCLE PROCESS ISO 12207 mapped onto IEEE SESC standards

MooreKlinkerMihelcic99

Andrew P Moore & J eic Klinker & David M Mihelcic
How to Construct Formal Arguments that Persuade Certifiers
In [HincheyBowen99] pp285-314
=EXPERIENCE PROOF REFINEMENT SQA V&V SCR Statemate CSP EVES Verdi Ada VADS GSN SAM SESAME OzWeb TABULAR LITEATE SPECIFICATION SECURITY SED/SEC
GSN::graphic='Goal Structuring Notation', semantic net of Goals, assumptions, strategies, justifications, and choices. Used to develop assurance strategies.
(Fig13.1 assurance argument framework): 6 layers of specification each with tools and languages and kinds of proofs.
Higher levels of abstraction use process algebra and lower levels model based languages. Bottom level uses testing and test coverage on modules.
(Fig13.2 Flow of literate specification): lit. spec. is input to tangle and weave. weave generates hard copy and tangle drives analysis and testing tools generating hypertext evidence.

MoorselWolter06

Aad P A van Moorsel & Katinka Wolter
Analysis of restart mechanisms in software systems
1st QEST & IEEE Trans Software Engineering V32n8(Aug 2006)pp547-558
=MATHEMATICS PERFORMANCE SPEED OPTIMAL RESTART TIME-OUT STOCHASTIC BERNOULI
When the time to complete a task is randomly distributed with a heavy tail then it pays to restart after a delay.
It is better to have a longer delay before restarting.
If its worth restarting once then more restarts are better.
The mean time gets better but the variance gets worse with restarts.
Gives ways to compute best delays.

Morales00

Alexandra Weber Morales
Rapid Product Development Proven Practical
Software Development Magazine V8n3(Nov/Dec 2000)pp54
=EXPERIENCE RAD PROCESS Rolm
QRPD:= Quality Rapid Product Development,--Kopelman
vision and clearly limitted scope, obsessed leader of inspired team, frequent milestones and tests of prototyped
slow start - fast finish, buy wisely

Morales01

Alexandra weber Morales
Everyone's a Critic
Software Development Magazine V9n5(May 2001)p11 + letters in (Jun 2001)p13 on why
=REVIEW OPEN SOURCE EMPIRICAL PAPER PEOPLE
Quotes study (ICSE 2000) of apache development: 4 % of the community produced code. More critics/bug reports than new code. [MockusFieldingHerbsleb00]

Morales01a

Alexandra Weber Morales
Demonstrates that partial and under-defined functions can not be used consistently with normal axioms of λ calculus. Proposes remedies -- essentially limiting substitutions to particular proper values and functions.
disclaimer: page 700: "We Thank David Watt and Richard Botting for reviewing drafts of this article."
cf [Owreetal95] [Parnas93] [RushbyOwreShankar98]

Morrill09

Dan Morrill
Boom and Bust in the blogosphere: Case studies of the blogging Industry
BookSurge Publishing Charlestown SC, 2009, ISBN 1439216738
=BLOG BLOGGING
Help [click here Morrill09 if you can fill this hole]

MorrisBunkenburgTyrrell09

JOSEPH M. MORRIS & ALEXANDER BUNKENBURG & MALCOLM TYRRELL
Term Transformers: A New Approach to State
ACM Trans. Program. Lang. Syst. V31n4 (May 2009)a16:1-42 [ 1516507.1516511 ]
=IDEA TERM TRANSFORMERS PREDICATE wp LANGUAGES SEMANTICS LOGIC PROOF Lambda axiomatic denotation Dijkstra
phase::=command "|>" term.
In the text \righttriangle is used for my "|>" above.
Example:
x:=x+1 |> x^2 = (x+1)^2.
Uses a lambda calculus based language of commands and terms to establish mathematical bona vides.

MorrisLeeParkerBundellLam01

John Morris & Gareth Lee & Kris Parker & Gary A Bundell & Chiou Peng Lam
Software Component Certification
IEEE Computer Magazine V34n9(Sep 2001)pp30-36
=DEMO XML TEST SPECIFICATIONS MODULES

Morrison94

J Paul Morrison
Flow-based Programming: a new approach to application development
Van Nostrand R NY NY 1994 ISBN 4-442-1771-5 QA76.76A65M675
=HOWTO FLOW

MorrisonGeorge95

Joline Morrison & Joey F George
Exploring the Software Engineering Component in MIS Research
Commun ACM V38n7(Jul 1995)pp

=SURVEY SOFTWARE MIS Research COST ECONOMICS METHODS

Table

Name	Description	Bibliography terms
Formulative	involving development and refinement of theories, models or frameworks to support science and research	THEORY IDEA
Evaluative	scientific method working with hypothese and experiment	EXPERIMENT, CASE-STUDY, SURVEY
Descriptive	theories and models developed of what is as input into theory	EXPERIENCES, literature and product SURVEY, lighter. METAANALYSIS
Development	generating knowledge for explaining or solving problems	METHODS DEMO TOOL HOWTO

Morse95

Dave Morse(mailto:dmorse@raima.com)
OODBSs and the Marriage of Network and Relational Database Models
IEEE Computer Magazine V28n10(Oct 1995)pp66-67
=SURVEY DATA MODEL ACID OBJECTS NONSEQUENTIAL
1. ACID::principle="Atomic, Consistent, Isolated, and Durable".
2. missing in some OODBs
3. Extremes: map objects to RDBMS tuples..make table appear like a class of objects.

MorzentiSanPietro

Angelo Morzenti & Pierluigi San Pietro
Object-oriented logical specification of time-critical systems
TOSEM V3n1(Jan 1994)pp56-98 CR9503-0166
=THEORY OBJECT_ORIENTED LOGIC SPECIFICATION TIMING

MoserEtal97

L E Mose & Y S Ramakrishna & G Kutty & P M Melliar-Smith & Laura K Dillon
A Graphical Environment for the Design of Concurrent Real-Time Systems
ACM TOSEM V6n1(Jan 1997)pp1-30
=THEORY GRAPHIC LOGIC SPECIFICATION TIMING
RTGIL::=Real-time Graphical Interval Logic

Moss78

Chris Moss
The Value of Loglan as a useful tool in Machine translation
=ADVERT Loglan ITL UNIVERSAL LANGUAGES
Computer Weekly (UK) (Jun 15 1978)p4
Describes Loglan in more detail.

Moss92

J Elliot B Moss
Working with Persistent Objects: To Swizzle or Not to Swizzle
IEEE Trans SE-18 n8(Aug 1992)pp657-673
=THEORY DATA ADT
1. links persistent programming with database programming and finds a fuzzy boundary, also links to OODBMs and persistent object stores and servers.

Mosses90

Peter D Mosses
Denotational Semantics
Chapter 11(pages 575-631) of Leeuwen90
=THEORY LANGUAGE SEMANTICS

Mosses92

Peter D Mosses
Action Semantics
Tracts in Theor Comp Sci V26 Cambridge Univ Press 1992 ISBN 0-521-40347-2 Review p492 AMM May 1994
=THEORY LANGUAGE SEMANTICS

Mossinger10

Jurgen Mossinger
Software in automotive systems
IEEE Software Magazine V27n2(Mar/Apr 2010)pp92-94
=ESSAY AUTOMOBILE RELIABLE SAFE REAL-TIME RESOURCES ROBUST MECHATRONIC CLOSED LOOP CONTROL ASCET Mathlab/Simulink CMMI autosar RISKS
No reboots allowed!
1970s assembler..1990s C
Bosch CMMI level 3..5

Motoyama06

Tetsuro Motoyama
Improving software development through three stages
IEEE Software Magazine V23n5(Sep/Oct 2006)pp-
=EXPERIENCE IMPROVEMENT CMM
Put artifacts on web sites HTML + GIFs so that information is 3.sec/3.clicks away.
Read books.
Develop standards. And revise standards.
Separate designing from coding so that designs that are more than sketches.
Early writing of tests.
Public schedules and plans.
Manage risks.
First discuss an artifact then inspect for errors to stop problem solving.
Automation: Translate designs into template code.
All code available to all (online) is good.
Project postmortems help improvement.
Improvement happens only if you are willingn to identify errors and problems.

Mountain10

Gwaredd Mountain
Game Development in a Post-Agile world
Gwaredd Space (Feb 5 2010) [ game-development-in-post-agile-world.html ]
=POLEMIC ANTI-Scrum PEOPLE vs PROCESS GAMES
Game_production::= Pre_production; Production; Post_prod.
Pre_production:=Organic+creative+exploration; answers & technology.
Production:=make content & spend money
Post_prod:=alpha; beta.
alpha:=polish game play;
beta:=bug fixing;
"We can change our approach throughout a project lifecycle; we do not always have to stick to the same thing throughout."
Compare with the Rational Unified Process with its adjusting mix of disciplines and 4 phases.

Mowbray96

Tom Mowbray
Managing Complexity in OO Architectures
Object Magazine (Dec 1996)pp18+20
=SURVEY OBJECT-ORIENTED ARCHITECTURES
sweep it under the carpet(encapsulate)
hide it(repository)
ignore it(Horizontal arch)
slice it(Layered)
dice it(Vertical)

Mowbray97

Tom Mowbray
The Seven Deadly Sins of OO architecture
Object Magazine V7n1(Mar 1997)pp22+24
=ESSAY OBJECT-ORIENTED ARCHITECTURES
lack of abstraction and hasty decisions can make an architecture expensive. Lack of partitioning+configurationcontrol+lack of metadata+lack of architecture Mining(NIH)+Implementation dependency
[Mowbray96]

MowshowitzKumar09

Abbe Mowshowitz & Nanda Kumar
And Then THere were Three
IEEE Computer Magazine V42n2(Feb 2009)pp108+106-107
=ESSAY NETWORK SEARCH ENGINES MARKET ECONOMICS MONOPOLY KNOWLEDGE GATEKEEPER LEGAL ETHICS Google Yahoo AOL LLC Microsoft
Can Google be sued for not showing a relevant page to people looking for it?

Mrdalj90

Stevan Mrdalj<ori_mrdalj@emunix.emich.edu>
Bibliography of Object-Oriented System Development(OOSD)
ACM SIGSOFT SEN V15n6(Oct 1990)pp60-63
=Bibliography Object-Oriented System Development OOSD

Mubarak08

Hisham Mubarak
Developing Flexible Software using Agent-Oriented Software Engineering
IEEE Software Magazine V25n5(Sep/Oct 2008)pp12-15
=ADVERT AGENTS JADE Java
AOSE::= "Agent-Oriented Software Engineering".
Agents depend on a platform that lets them configure themselves to achieve their goals.
The platform includes agent management, directory services, a message transport system, and an agent communication language.
Article lists relevant websites.

MuckherjeeSiewiorek97

Arup Mukherjee & Daniel P Siewiorek
Measuring Software Dependability by Robustness Benchmarking
IEEE Trans Soft Eng V23n6(Jun 1997)pp366-378
=EXPERIENCE DEFECTS UNIX TESTING RISKS
5 UNIX (Mach) can be crashed by random programs within 1 minute
with random system calls 2 crash in 30 secs and 1 runs slowly and 2 survive

Mudawwar97

Muhammad F Mudawwar
Multicode: A Truly Multilingual Approach to Text Encoding
IEEE Computer Magazine V30n4(Apr 1997)pp37-43 + letter critizing
=IDEA CHARACTER CODE UNICODE ASCII MULTICODE
upto 256 different character sets. set 0 is default ASCII. 8 and 16.bit encoding. FF.hex+set number switches set. ??A different data type for each language and so strings can not mix different languages.??

Mugridge08

Rick Mugridge
Managing Agile project requirements with storytest-driven development
IEEE Software Magazine V25n1(Jan/Feb 2008)pp68-75
=DEMO REQUIREMENTS TESTS FIT TABULAR SCENARIOS
FitLibrary::= See http://sourceforge.net/projects/fitlibrary/.
FitNesse::= See http://www.fitness.org/.
Also see [ samples/methods.html#Fit ] [MartinMelnick08]

MugridgeCunningham05

Rick Mugridge & Ward Cunningham
Fit for developing Software: Framework for Integrated Tests
Pearson Education 2005 ISBN 0-321-269-34-9 $44.99
Review in ACM SIGSOFT Software Engineering Notes V31n3(May 2006)pp43-44 by Amr Elssamadisy
=UNREAD HOWTO TOOL DOMAIN RULES REQUIRMENTS SCENARIOS TABULAR TESTING
Describes methods and tools for using tables to connect user requirements to integration tests.
Refered to in [MartinMelnick08] [Mugridge08]

Muhanna91

Waleed A Muhanna
Composite Programs: Hierarchical Construction circularity and deadlocks
IEEE Trans SE-17n4(Apr 1991)pp320-333
=THEOY NON_SEQUENTIAL MODULES DEADLOCK

Mulhauseretal93

DOCASE: A Methodic Approach to Distributed Programming
Comm ACM V36n9(Sep 1993)pp127-138
=ADVERT METHOD WWW/NET objects
DOCASE::=Distribution and Objects in CASE

MullerKuhn93

Michael J Muller & Sarah Kuhn (Guest Editors)
Special Issue on participatory Design
Comm ACM V36n6(Jun 1993)pp24-103
=EDITORIAL JAD USER SYSTEM PD
PD:="Participatory Design".
Figure on page 27: card games, low-tech prototypes, storyboards, theatre, ... by Muller, Wildman and White

MullerPadberg03

Matthias M Muller & Frank Padberg
On the Economic Evaluation of XP Projects
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp168-177
=THEORY XP Economics pair test-driven velocity quality cost-benefit NPV
one-size does not fit all.

Mullins11

Justin Mullins
Move over, Einstein
New Scientist (19 Mar 2011)pp40-43
=ARTICLE EVOLUTIONARY ALGORITHM DATA INVARIANT FORMULAS SCIENCE MECHANICS BIOLOGY Eureqa OPEN SOURCE SYMBOLIC REGRESSION
Research by Michael Schmidt & Hod Lipson on evolutionary programming at Cornell.
Downloads, blogs, How to.... [ eureqa ]
Eureqa Algorithm evolves invariant formulas to fit scientific data.
But Eurequa doesn't explain why the formula is invariant.
Modelled double pendulum and Bacillus subtilis!
Like Roger Hartley (Ph. D. Brunel Cybernetics) in the 1970's but with more computer power and a better model of formulas.

MumfordWier79

?Enid? Mumford & ?? Wier
Computer Systems in Work Design - The Ethics Method
Associated Business Press 1979
=HANDBOOK PQRST USER System METHOD

MunakataJani94

Toshinori Munakata & Yashvant Jani
Fuzzy Systems: An Overview
Comm ACM V37n3(Mar 1994)(AI issue)pp69-76
=SURVEY =ADVERT FUZZY LOGIC MATHEMATICS

MunozDowekCarreno04

Cesar A Munoz & Gilles Dowek & Victor Carreno
Modeling and Verification of an Air Traffic Concept of Operations
Proc ISSTA 2004 & ACM SIGSOFT Software Engineering Notes V29n4(Jun 2004)pp175-182
=EXPERIENCE THEOREM PROVING PVS CONCEPT of OPERATIONS V&V REQUIREMENTS ATC Airport SATS-HVO
Concept_of_operations::="a collection of rules and procedures".
Uncovered 10 issues in proposed concept of operations that where accepted into a revised form.
The model also had to be revized...
Model checking could not handle the 213 boolean variables needed,
PVS allowed a more abstract expression of the concepts and the verification that it permitted only safe states.
Given no more than 4 planes at a time, depth first exploration discovered no more than 2811 reachable states. The algorithm (depth first) was written and proved using PVS. [ http:researcch.nianet.org/~munoz/Besc ]

MurugappanKeeni03

Mala Murugappan & Gargi Keeni
Blending CMM and Six Sigma to meet Business Goals
IEEE Software Magazine V20n2(Feb/Mar 2003)pp42-48
=EXPERIENCE BUSINESS QC STATISTICS PURPOSES QUALITIES QFD IMPROVEMENT SW-CMM PROCESS
7year process! Uncovered synergy.
Using z scores to quantify capability.
Roughly a 3σ process has 68 defective lines/KLoC but a 6σ process has only 3 per million LoC.

Murphy-HillParninBlack12

Emerson Murphy-Hill & Chris Parnin & Andrew P Blck
How we refactor, and how we know it
IEEE Trans on Software Eng VSE-38n1(Jan/Feb 2012)pp5-18
=SURVEY =POLL =ANALYSIS =INTERVIEWS REFACTORING ECLIPSE Mylyn
Tools seldom used. Tools are seldom configured. Tools underused. Tools used or not for different refactorings.
Toolsmiths refactor differently to normal programmers.
Refactoring can be done without noticing!
Distinguishes floss refactoring from root canal refectoring. Observes that flossing is common.
Many refectorings are medium and low level.
Refactoring is frequent.
Long list (pages 17-18) of refactoring steps: {rename, extract local variable, inline, extract method,....}

MurphyBalke89

John S Murphy & Karl G Balke
Software Diagramming: A New Design Paradigm
McGraw-Hill NY NY 1989 ISBN 0-07-044118-9 Lib Congress Card 89-83755 QA76.76 D47M95
=IDEA Graphic DFD+Control

MurphyKerstenFindlater06

Gail C Murphy & Mik Kersten & Leah Findlater
How are Java Software Developers Using the Eclipse IDE?
IEEE Software Magazine V23n4(Jul/Aug 2006)pp76-82
=EXPERIMENT 99 Developers Eclipse JDT Mylar Monitor plugin Java TOOLS refactoring
1 month activity compresses 95% to 1Mb.
Detailed stats on views, perspectives, commands, ...
Mylar::Eclipse_plugin= See http://www.eclipse.org/mylar

MurphyNotkin96

Gail C Murphy & David Notkin
Lightweight Lexical Source Model Extraction
ACM TOSEM V5n3(Jul 1996)pp626-292 CR9703-0194
=THEORY Regular Expressions LEXICAL DDD
LSME::= hierarchical Regular Expressions of Tokens with actions DDD

MurphyNotkin97

Gail C Murphy & David Notkin
Reengineering with Reflexion Models
IEEE Computer Magazine V30n8(Aug 1997)pp29-35
=ADVERT MAINTENANCE TOOLS for undocumented code by creating a model+ a map+refine parts to fit code
text used more than graphics
tools adapted by use

MurphyNotkinSullivan95

Gail C Murphy & David Notkin & Kevin Sullivan
Software Reflexion Models: Bridging the Gap between Source and High-level Models
[Kaiser95] pp18-28
=DEMO EXPERIENCES MODULE REVERSE ENGINEERING Z C/C++
understanding is an iterative process
engineer postulates model; maps source code names to model; sees structural differences

MurphyNotkinSullivan01

Gail C Murphy & David Notkin & Kevin J Sullivan
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Trans Software Engineering V27n4(Apr 2001)pp364-380
=FORMAL+EXPERIENCE MODEL TOOL TECHNICAL CODE Z
See [MurphyNotkinSullivan95]
[MurphyNotkin97]
[MurphyNotkin96]
gives formal Z model of a reflexion model and its computation from code.
Relates high level entities to source code entities. And high level relations to source code relations.
extract a reflexion model of the code and iteratively make them match via maps from model to code.
Tool looks for mismatches.
Experience includes MS Excel, > 1M LoC of C.

MurphyRomanVarghese02

Amy L Murphy & Gruia-Catalan Roman & George Varghese
Tracking Mobile Units for dependable message delivery
IEEE Trans Software Engineering V28n5(May 2002)pp433-448
=THEORY RELIABLE MOBILE COMMUNICATION
Treats mobile units as messages in the Dijkstra-Scholten diffusing computation algorithms.

MurphySchwanninger06

Gail Murphy & Christa Schwanninger
Aspect-oriented programming
IEEE Software Magazine V23n1(Jan/Feb 2006)pp20-23
=EXAMPLE ASPECTS AOP weaving
Introduces section with good examples, adverts, & discussion of AOP pp24-75

MurphyPiccoRoman06

Amy L Murphy & Gian Pietro Picco & Gruia-Catalin Roman
LIME: a coordination model and middleware supporting mobility of hosts and agents
ACM TOSEM Trans Software Eng & Methodology V15n3(Jul 2006)pp279-328
=DEMO Lynda MOBILE FORMAL UNITY DEVELOPMENT TUPLE-SPACE NONSEQUENTIAL OPEN SOURCE
Source [ http://lime.sourceforge.net ]
See [MurphyRomanVarghese02] for more

MurphyWalkerBaniassad99

Gail C Murphy & Robert J Walker & Elisa L ABaniassad
Evaluating emerging software development technologies: Lessons learned from assessing aspect-oriented programming
IEEE Trans Software Engineering V25n4(Jul 1999)pp438-455 CR9912-0921
=EMPIRICAL ASPECT AOP
Lessons learned from comparing technologies + obvious mistakes not recognized

MurruDeiasMugheddu03

Orlando Murru & Roberto Deias & Giampiero Mugheddu
Assessing XP at a European Internet Company
IEEE Software Magazine V20n3(May/Jun 2003)pp37-43
=EXPERIENCES Fst EURO PARTNER SECURE PORTALS RFCs JAVA RUP XP
Table (p38) shows 2 projects. 6/12 adoption, 2 9/12 adoption.
No planning means no control and coordination.
Planning: involve all, separate estimates from rewards and designs.
Metaphor? Felt need for architectural planning. (no stand up meetings?). Used posters and sketches instead.
refactoring and testing needs experience (didn't rotate?)
Sales and management had problems.
XP can imply ISO9001!

Musa93

John D Musa (AT&T Bell Labs)
Operational Profiles in Software-Reliability Engineering
IEEE Software Magazine V10n2 (Mar 1993)pp14-32
=ADVERT Cleanroom USER Reliability probability dynamics

MusaEhrlich96

John D Musa & Willa Ehlich
Advances in Software Reliability Engineering
Advances in Computers V42(1996)pp77-117
=EXPERIENCES RELIABILITY ENGINEERING

MusaIanninoOkumoto87

J D Musa & A Iannino & K Okumoto
Software Reliability: Measurement & Prediction & Application
McGraw-Hill 1987

MusserSaini96

David R Musser & Atui Saini
STL Tutorial & Reference Guide
Addisson Wesley Readsing MA 1996 Review IEEE Software Magazine Nov 1996 p122
=TUTORIAL LIBRARY generic C++ STL templates

MuthitacharoenSaeed09

Achita (Mi) Muthitacharoen & Khawaja A. Saeed
Examining User Involvement in Continuous Software Development ( A case of error reporting system) Commun ACM V52n9(Sep 2009)online [ 1562164.1562194 ]
=POLL USERS ERROR MESSAGE REPORTING

MyersAvisson02

Michael D Myers & David Avison
Qualitive Research in Information Systems: A Reader
SAGE Publications Thousand Oaks CA 2002 T58.64 Q35 ISBN 0-7619-6632-3
=READER PEOPLE SYSTEMS
Includes: [Markus83]

MyersBAetal97

Brad A Myers & Richard G McDaniel & Robert C Miller & Alan S Ferrency & Andrew Faulring & Bruce D Kyle & Andrew Mickish & Alex Klimovitski & Patrick Doane
The Amulet Environment: New Models for Effective User Interface Software Development
IEEE Trans Soft Eng V23n6(Jun 1997)pp347-365 [ amulet ]
=ADVERT USE HCI MODEL

MyersBANicholsWobbrockMiller04

Brad A Myers & Jeffrey Nichols & Jacob O Wobbrock & Robert C Miller
What
IEEE Computer Magazine V37n12(Dec 2004)pp36-43
=DEMO TOOLS HANDHELD PC INTEGRATION WIRELESS PDA CELL PHONE PalmOS
SlideShowCommander::tool.
PUC::protocol="Personal Universal Controller", allowing any device to be controlled from a handheld.
ShortCutter::tool="device independent design of controller interfaces"
People use both PC mouse and handheld together to do things.

MyersJP90

J. Paul Myers Jr.
The Central Role of Mathematical Logic in Computer Science
ACM SIGCSE V22n1(Feb 1990)pp22-26
=ESSAY logic formal

MyersW90a

Ware Myers (Cont Ed)
Interview of Mary Shaw(CMU SEI) : Seeking a foundation for Software Engineering
IEEE Software V7n2(Mar 1990) pp102
=handbook RISKS

MyersW90b

Ware Myers (Cont Ed)
Build defect-free software Fagan urges
IEEE Computer V23 n8(Aug 1990) pp112-113
=INTERVIEW SQA DEFECTS QUALITY

MyersW95

Ware Myers (Cont Ed)
Does Microsoft portend the future of Software Development (interview with Michael Cusumano)
IEEE Software Magazine(Nov 1995)pp110-111 [CusumanoSelby95]
=INTERVIEW MS-PROCESS ONE-SIZE
1. developers must know more than programming
2. organize feature teams
3. pioneer mass markets with early good-enough product
4. focus on features in current release and learn from users
5. daily biulds (but code checked in twice a week?)
6. still learning
7. make own products obsolete
  an incremental change company. example: adopted component reuse not full bloan object-orientation
  MS has been accumulating historical data to help scheduling and burnout
  feature eams lead to code bloat, Bill Gates pushes the development of standardized functions accross featrues and products. Hence OLE and DLL as tools and product. leads to interdependence.
  Predication: waterfall will decline further

MylopoulosChungLiaoWangYu01

John Mylopoulos& Lawrence Chung & Stephen Liao & Huaiqing Wang & Eric Yu
Exploring Alternatives during Requirements Analysis
IEEE Software Magazine V18n1(Jan/Feb 2000)pp92-96
=THEORY SOFTGOALS SIGs AND/OR GRAPHICS QUALITIES REALITIES SYSTEMS TECHNIQUES
for more [ChungNixonYuMylopoulos99]

MylopoulosChungNixon92

John Mylopoulos & Lawrence Chung & Brian Nixon
Representing and Using NonFunctional Requirements: A Process-Oriented Approach
IEEE Trans SE-18n6(Jun 1992)pp483-497 [CR] 9307-0467
=ESSAY Quality
ref to Herbert Simon

MylopoulosChungYu99

John Mylopolous & Lawrencce Chung & Eric Yu
From Object-oriented to Goal-oriented Requirements Analysis
Commun ACM V42n1(Jan 1999)pp31-37
=HISTORY QUALITY analysis before OOA/D
And/Or trees

MyrtveitStensrudOlsson01

Ingunn Myrtveit & Erik Stensrud & Ulf H Olsson
Analysing data sets with missing data: An empirical evaluation of imputation methods and likelihood-based methods
IEEE Trans Software Engineering V27n11(Nov 2001)pp999-1013
=STATISTICS ERP
Best depends on the pattern of missing data.
use Full Information Maximum Likelihood to impute missing data: less bias caused by biases in missing data

MyrtveitStensrudShepperd05

Ingun Myrtveit & Erik Stensrud & Martin Shepperd
Reliability and Validity in Comparative Studies of Software Prediction Models
IEEE Trans Software Engineering V31n5(May 2005)pp380-391
=SIMULATION =SURVEY RESEARCH EFFORT ESTIMATION COST PREDICTION
Shows that there is no consistent recommendation's in the literature for estimating cost/effort
Simulated the typical research procedure for evaluating and/or comparing ways of predicting the effort needed to produce software.
Shows that the particular measure of goodness of fit chosen determines the "best" model.
Shows that the particular sample of data also determines the "best" model.

Naftalinetal94

?? Naftalin (Ed)
FME '94: Industrial Benefits of Formal Methods (Second International Symposium of Formal Methods Europe, Barcelona, Spain, October 24 - 28, 1994. Proceedings)
Springer-Verlag 1994 ISBN 3-540-58555-9
=PROCEEDINGS FORMAL METHODS VDM REFINEMENT

Nagel56

E Nagel
A Formalization of Functionalism
Logic Without Metaphysics Free Press 1956 pp247-283, reprinted Emery69
=ESSAY FUNCTION SYSTEMS PURPOSES
p298. distinguishes mathematical function from purpose.
p311. functional analysis in social systems requires a standardized/patterned/repetitive items

NaikSarikaya92

Kshirasagar Naik & Behcet Sarikaya
Testing Communication Protocols
IEEE Software V9n1(Jan 1992)pp27-37
=ADVERT TESTING LOTOS formal

Najork95

Marc Najork
Visual Programming in 3d (the CUBE Language)
Dr. Dobbs Jnl n237(Dec 1995)pp18-24+28+31 [ cube.html ]
=ADVERT GRAPHIC CODE TECHNICAL VIRTUAL REALITY

NakajoKume91

Takeshi Nakajo & Hitoshi Kume
A Case History Analysis of Software Error Cause-effect Relationships
IEEE SE-V17n8(Aug 1991)pp830-838
=CASE-STUDY SAD reduced interface errors significantly

NakakojiYamamotoMatsubaraShirai12

Kumiyo Nakakoji & Yasuhiro Yamamoto & Nobutu Matsubara & Yshinari Shirai
Toward unweaving streams of thought for reflection in professional software design
IEEE Software Magazine V29n1(Jan/Feb 2012)pp34-38
=DEMO TOOL RECORDS DESIGN SESSION TAGS WHITEBOARD VIDEO AUDIO TEXT DPS ART019 TIMELINE COLLABORATION
Tools record whiteboard design sessions and correlate strokes audio video and text transcript.
Provides a searchable and browsable record.
Part of workshop [BakerHoekOssherPetre12]

Nakataetal91

Ikuo Nakata & Masataka Sassa
Programming with streams in a Pascal-Like Language
IEEE Trans SE-17 V17n1(Jan 1991)pp1-9
=THEORY NONSEQUENTAL DATA FLOW PASCAL producer-consumer
models next, eos, such that, while, blocked ....

NanardNanard95

Jocelyne Nanard & Marc Nanard
Hypertext Design Environments and the Hypertext Design Process
Commun ACM V38n8(Aug 1995)pp49-56
=SURVEY WRITING HYPERTEXT TOOLS
MacWeb
Tools based on "formal tools"
rigids methods vs need to experiment

NanHarter09

Ning Nan & Donald E Harter
impact of budget and schedule pressure on software development cycle time and effort
IEEE Trans Software Engineering V35n5(Sep/Oct 2009)pp623-637
=EMPIRICAL ESTIMATION COST SCHEDULE EFFORT
Budget pressure vs effort: u-shaped. Low and high pressure worse than medium.
sjimilarly buget in time to complete.

NapierMathiassenJohnson09

Nannette P Napier & Lars Mathiassen & Roy D Johnson
Combining Perceptions and Prescriptions in requirements engineering process assessment: an industrial case study
IEEE Trans Software Engineering V35n5(Sep/Oct 2009)pp593-606
=CASESTUDY PROCESS IMPROVEMENTS REQUIREMENTS STAKEHOLDER PERCEPTIONS TelSoft
In addition to prescribing improvements also analyse what people perceive about the process.
initiate carefully; #(engage stakeholders;collect data; analyse; debate findings); make recommendations.

NarayanaDharap90

K T Narayana & S Dharap
Formal Specification of a Look Manager
IEEE Trans Software Engineering SE-V16n9(Sep 1990)pp1089-1103
=DEMO Z FORMAL SPECIFICATION GRAPHIC USER INTERFACE GUI

Naur07

Peter Naur
Computing versus Human thinking
Commun ACM V50n1(Jan 2007)pp85-94 + letter V50n4(Apr 2007)pp7-8
=HISTORY REJECTING MODERN PSYCHOLOGY LOGIC TURING AI vs plastic neural nets CR 0801-0095
William James
Science as description not theorizing.

Nauretal64

Peter Naur(Ed.)
The Revised ALGOL 60 Report
Commun ACM 1965
=case-study BNF sequential LANGUAGE ALGOL CLASSIC
Authors
A rough transcription into MATHS/HTML: [ samples/algol60.syntax.html ]

NaumovichClarke00

Gleb Naumovich & Lori A Clarke
Classifying Properties: An alternative to the Safety-Liveness Classification
[FSE8] pp159-168
=IDEA TEMPORAL LOGIC SPECIFICATION ANALYSIS SAFETY LIVENESS
classifies properties in terms (1) that describe finite, infinite, or both kinds of sequences events, pus (2) that must be checked on finite, infinite, or both kinds of sequences of events.

NavedaSeidman05

J Fernando Naveda & Stephen B Seidman
Professional Certification of Software Engineers: The CSDP Program
IEEE Software Magazine V22n5(Sep/Oct 2005)pp73-77
=ADVERT IEEE CERTIFICATION PRACTICE BASED EXAMINATIONS URLs

Navathe92

Shamkant B Navathe
Evolution of Data Modeling for Databases
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp112-123
=HISTORY DATA MODEL

Navatheetal86

Shamkant B Navathe & R Elmastri & J Larson
Integrating User Views in Database Design
IEEE Computer V19n1(Jan 1986)pp50-62
=IDEA data USER Reality

NcubeEtal08

Cornelius Ncube & Patricioa Oberndorf & Anatol W Kark
Opportunistic Software Systems development: Making Systems from what is available
IEEE Software Magazine V25n6(Nov/Dec 2008)pp38-41
=EDITORIAL OSSD POSTMODERN MASHUPS LEGACY REUSE
OSSD::="Opportunistic Software Systems development".
Introduces a special section -- pages 42-83.
Comparison with "Junkyard wars"/"Scrapheap challenge".
Argues that the market forces the assembly of systems from components that where not intended for combination or even reuse.
Tends to require a different process: ad hoc, experimental prototyping, scavenging, attending to mismatches, smart engineering, creativity, innovation, imaginative gluing software pieces together.
Need to develop combinations and negotiate requirements later about gaps with stakeholders.
Architecture tends to evolve.
Risk of architectural mismatches (Boehm).
Mostly treat components as black boxes.
Testing "is the main disadvantage".
Need for fast release, collaboration, cooperation, and negotiation.
Good for startup companies.
Need a different curriculum -- closer to traditional engineering -- with more systems setup support(Obrenovic & Gasevic & Eliens).
(dick)|-in one sense nothing new here, but an acknowledgment of an existing process.
Also see [BoehmBhuta08] [Jansen08]

Nelson87

Greg Nelson
A Generalization of Dijkstra's Calculus
Digital Equipment Corpn Systems Research Center Report No. 16 Palo Alto CA USA
=THEORY non-sequential guarded-commands

NelsonArmstrongGhods02

H James Nelson & Deborah J Armstrong & Mehdi Ghods
Old Dogs and New Tricks
Commun ACM V45n10(Oct 2002)pp132-137
=EXPERIENCE PARADIGM SHIFT TRAINING Object-Oriented vs DOMAIN
Expert programmers tend to carry forward skills learned in a domain into a new paradigm and so avoid using it.
Instead a two day course can deconstruct the old paradigm and then help students to reconstruct their own version of the new paradigm.
old->abstraction->critique->new abstraction->new ideas.
The two day course resulted in preserving domain knowledge and better mastery of the new paradigm's way of doing things.

NelsonG89

Greg Nelson
A Generalization of Dijkstra's Calculus
ACM TOPLAS Oct 1989
=THEORY non-sequential guarded-commands

NelsonGOppen80

Greg Nelson & Derek C Oppen
Fast Decision procedures based on congruence closure
J ACM V27(Apr 1980)pp356-364
=ALGORITHM ALGEBRA LISP
1. f(f(a,b),b)=a:- f(a,b)=a, f(a)=a:-f(f(f(a)))=a=f(f(f(f(f(a))))).
2. LISP_AXIOMS::=
  Net{
  }=::LISP_AXIOMS.
3. LISP_PLUS::=
  Net{
  }=::LISP_PLUS.

NelsonT74

Ted(Theodor Holm) Nelson
Dream Machines/Computer Lib
Chicago Nelson 1974
=POLEMIC RISKS USER hypertext GRAPHIC CLASSIC XANADU

NelsonT95

Ted(Theodor Holm) Nelson
The Heart of Connection: Hypermedia Unified by Transclusion
Commun ACM V38n8(Aug 1995)pp31-33
=ADVERT hypertext WWW/NET

Nerson92

Jean-Marie Nerson
Applying Object-Oriented Analysis and Design
(Special Issue: Modeling) Comm ACM V35n9(Sep 1992)pp63-74
=SURVEY OBJECT-ORIENTED METHODS OOAD
1. ESPRIT project
2. ref to BeckCunningham89 re [CRC] cards, RubinGoldberg92 scenarios.
3. Ref to M Page-Jones & M Constantine & S Weiss, "Modeling object oriented systems: the uniform object notation", Comput Lang v7(Oct 1990)pp69-87
4. BON Better Object Notation (or Business Object Notstion?) (based on Meyer's work)
5. YAWN(Yet Another Whimsical Notation)
6. Uses Eiffel terminology without explanation
7. p63: "The bad news is that whenever inappropriate types of objects are selected, or whenever awkward structuring choice are made, the final architecture reflects these poor decisions"
8. p72: "Highlevel class abstractions usually do not come first to mind"
9. Car Rental Agency case study

NerurBalijepally07

Sridar Nerur & VenuGopal Balijepally
Theoretical Reflections on Agile Development Methodologies
Commun ACM V50n3(Mar 2007)pp79-83
=SURVEY Philosophies AGILE
Makes the case that agile mthods fit well with recent developments in architectural, cybernetic, and management thinking.

Nesdore83

?? Nesdore
Friendly to all or none
Comp World Oct 31 1983 In depth pp3-10
=IDEA USER
Designing an interface for everybody to use means nobody likes it much.

NetzerMiller92

Robert H Netzer & Barton P Miller
What are Race Conditions?: Some issues and formalizations
ACM Letters Programming Lang Syst V1n1(Mar 1992)pp74-88 CR9309-0683
=THEORY NONSEQUENTIAL RISKS

Neumann91

Peter G Neumann
Inside RISKS: Expecting the Unexpected - MAYDAY
Commun ACM V34n5(May 1991)p128
=EXPERIENCE RISKS

Neumann96

Peter G Neumann
Inside RISKS: Using Formal methods to Reduce Risks
Commun ACM V39n7(Jul 1996)p114
=EXPERIENCE RISKS vs MATHEMATICS
Small misunderstandings increase risk and may be reduced by using a formal perhaps mathematical language and techniques

Neumann97

Peter G Neumann
System Development Woes
Commun ACM V40n12(Dec 1997)p160
=EXPERIENCES RISKS

Neumann99

Peter G Neumann
Robust Open-Source Software
Commun ACM V42n2(Feb 1999)p128
=ESSAY many RISKS of secret source code compared to some successful Open-source projects
Open_source::= See http://www.opensource.org/.
RISKS::= See http://catless.ncl.ac.uk/Risks/.

Neumann05

Peter G Neumann
Anticipating Disasters
Commun ACM V48n3(Mar 2005)p128
=ESSAY RISKS PEOPLE ORGANIZATIONS
Problems preparing for disasters
1. plan responses based on the past disasters: after the horse has gone.
2. optimizing for the short term by ignoring long term consequences.
3. preparing for disaster feels bad.
4. crying wolf.
5. misreading the odds.

Neumann06

Peter G Neumann
The Foresight Saqa
Commun ACM V49n9(Sep 2006)p112
=HISTORY RISKS BACKUPS FAIL
Half a dozen recent situations where even having a back up system was not enough...
Moral: test your alternate backup systems as well the main system.

Neumann07

Pete J Neumann
Widespread Network Failures
Commun ACM V50n2(Feb 2007)p112
=HISTORY RISKS WEB/NET LOCAL event GLOBAL consequence
Gives examples 1980-2006 of nationwide networks collapsing due to a small local failure.
Not just cascades/propagation but feedback loops have to be calculated for.
quirks, hidden flaws, race hazards, deadlocks, ....
Need better architecture, analytical tools, planning, oversite, coordination...

Neumannetal91

Bernard de Neuman & Dan Simpson & Gil Slater(eds)
Mathematical Structures for Software Engineering
Inst of Math & its Applic Conf series no 27(Manchester poly UK July 1988)
Clarendon Press 1991 ISBN 0-19-853627-5 Review: Am Math Monthly telegraphic review V100n3(mar 1993)p315
=UNREAD

Neverman90

Gus Neverman (Wisconsin Public Service Corpn)
Fourth Generation Languages - The IS choice for survival
System Builder(Oct/Nov 1990)p22.
=ADVERT 4GL

Neville-Neil08

George V Neville-Neil
Kode Vicious: Beautiful code exists, if you know where to look
=COLUMN SOURCE CODE BSD BROOKES PROTOTYPING
Commun ACM V51n7(Jul 2008)pp23-25 [ 1364782.1364791 ]
First quotes a piece of "Good" code -- deep in the BSD Kernel.
Good code -- version numbers, named constants, objects in C, separate CPU dependent from CPU independent code.
Prototyping -- use it to find out where the difficult problems are not to give marketting something "pretty".

Neville-Neil08a

George Neville-Neil
Kode Vicious: Pride and Prejudice (The Vasa)
Commun ACM V51n9(Sep 2008)pp25-26 [ 1378727.1378737 ]
=HISTORY TECHNOLOGY RISK SAFETY MANAGEMENT
The history of the Vasa Galleon (1626) shows how a leader pushing technology too far, against the advice of technical experts, lead to a catestrophe.

Neville-Neil08b

George V Neville-Neil
Code Spelunking Redux
Commun ACM V51n10(Oct 2008)pp36-41 [ 1400181.1400194 ]
=DEMO TOOLS CODE Doxygen DTrace

Neville-Neal09

George V Neville-Neal (Kode Vicious)
System Changes and Side Effects
Commun ACM V52n4(Apr 2009)pp25-26 [ 1498765.1498777 ]
=EXPERIENCE TOOLS SYSTEMS CHANGE Make SCons Makefiles SConstruct debugging Python
Problems occur with build tools when there are many interlinked description/dependency files.
Debugging a collection of configuration/buildfiles/Makefiles is difficult.
Changes have unexpected consequence that ripple thru the system... and the description of the system.
Make changes because they give value.

Neville-Neil09a

George V Neville-Neil (Kode Vicious)
Kode reviews 101
Commun ACM V52n10(Oct 2009)pp28-29 [ 1562746.1562778 ]
=ESSAY CODE REVIEWS WHY HOWTO TEAM
How to learn about others code.
Must be prepared for. Piece of the code assigned to each for study.
Do not schedule after just lunch.
Provide coffee+food
Keep the focus. Do much more than nitpicking the spelling and syntax.
Take notes. And afterwards distribute.
Follow up.
Use a tool to track code reviews and followup work. Example Rietveld.

Neville-Neil10

George V Neville-Neil
Kode Vicious: Version Aversion
Commun ACM V53n10(Oct 2010)pp28-29 [ 1831407.1831420 ]
=ADVICE VERSION NUMBERS
ideal_version_number_syntax::=Major "." Minor "." bugFix.
Changes in the major version indicate loss of backward compatibility.
Minor versions changes typically should be enhancements.

Neville-Neil10a

George V Neville-Neil
Kode Vicious: literate coding
Commun ACM V53n12(Dec 2010)pp37-38 [ 1859204.1859219 ]
=ESSAYS TECHNICAL CODE STYLE TOOLS
Spelling and punctuation matter in code.
You don't have to use a debugger all the time!

Neville-Neil11

George V Neville-Neil
Kode Vicious: Coder's Block
Commun ACM V54n4(Apr 2011)pp34-35 [ 1924421.1924434 ]
=ANECDOTE PEOPLE PROGRAMMER THINKS and MANAGER FREAKS OUT

Neville-Neal11

George V Neville-Neal (Kode Vicious)
Storage Strife
Commun ACM V54n8(Aug 2011)pp34-35 [ 1978542.1978554 ]
=HOWTO STORE DATA SOURCE CODE CONTROL
Avoid archiving data in proprietary binary format.
Companies a binary formats go away.
Binary doesn't provide differencing to get deltas.

Neville-Neal11a

George V Neville-Neal (Kode Vicious)
File-system litter
Commun ACM V54n10(Oct 2011)pp25-26 [ 2001269.2001282 ]
=HOWTO DISK SPACE TEMPORARY FILES PEOPLE QUOTAS
If disk space is share all suffer if one person fills it with files.
Suggests ways to control problem
Avoiding recursive search and automatic deletion.

NevoWade07

Dorit Nevo & Michael R Wade
How toavood disapointment by design
Commun ACM V50n4(Apr 2007)pp43-48
=FOCUS EXPECTATIONS VoIP Project SATISFACTION EXPECTATIONS
Stakeholer satisfactiondepends on the system performing a little better than expected.

Ng05

Pan-Wei Ng
Effective business modeling with UML: describing business use cases and realizations
IBM/Rational/library, downloaded (Nov 2005) [ 905.htm ]
=DEMO MODELING BUSINESS PROCESSES UML profile USE CASE
Business modeling profile: business use case, actors, workers, and entities.
A business use case describes how an (outside) actor gets value from the business.
"the true value in business modeling lies in understanding how seemingly piecemeal work-flows relate to each other."
(dick)|-"Do DFDs do it better?"
Realizations model work processes, process automation, & information processes as interaction diagrams, class diagrams, and use case diagrams.
One must choose names for messages so that they describe the responsibility of the receiving object.
"the value of business use cases is to put use cases in context... how a group... deliver[s] business value."

NgSW98

Spencer W Ng
Advances in Disk Technology: Performance Issues
IEEE Computer Magazine V31n5(May 1998)pp75-81
=EXPERIENCE PERFORMANCE DATA DISK TIMING
overhead+seek+latency+transfer
seek time often one third of max seek!

NguyenRickenWong05

Dung "Zung" Nguyen & Mathias Ricken & Stephen Wong
Design Pattern for Parsing
ACM SIGCSE Tech Symp Proc (Feb 2005)pp477-481
=DEMO Object-Oriented LL(1) recursive descent PARSING PRDP PATTERNS composite visitor abstract factory Java .Lookup Schroedinger

NguyenWong02

Dung ("Zung") Nguyen & Stephen B Wong
Design Patterns
SIGCSE'02 Proceeding & ACM SIGCSE Bulletin V34n1(Mar 2002)pp121-125
=EXAMPLE PATTERNS GAME MVC State Visitor Strategy Command

Nicholls90

J E Nicholls(Ed)
Z users Workshop: Oxford 1989
British Computer Society/Springer VerlagWorkshops in Computing Series (WiCS) 1990 ZUM'89
=SURVEY FORMAL Z
List of 55 companies and universities using Z
ZUM'95 will be published in Springer-Verlag LNCS

NicholsK97

Kenneth Nichols
Inventing Software: The rise of Computer-related Patents
Quorum Books Westport Conn 1997 ISBN 1-56720-140-7 QA76.754N5
=ESSAY PATENTS PROPERTY LEGAL

Nichols99

Kenneth Nichols
The Age of Software Patents
IEEE Computer Magazine V32n4(Apr 1999)pp25-31 + letters V32n5(May 1999)pp4+6
=ESSAY LEGAL "Software is something new"

Nicolaisen96

Nancy Nicolaisen
Why Java is a Key Technology for the Internet
Object Magazine (Dec 1996)pp28-30+32-33
=ADVERT JAVA NONSEQUENTIAL: threads provide portable solutions to complex problems
But also see [Hartley99] and [BrinchHansen99]

NicolisPrigogine89

Gregoire Nicolis & Ilya Prigogine
Exploring Complexity: an introduction
Freeman NY NY 1989 Q175.N417 ISBN 0-7167-1859-6
=THEORY SYSTEMS COMPLEXITY CHAOS ENTROPY THERMODYNAMICS PHASES SELF-ORGANISING CYBERNETICS MATHEMATICS
Describes how many systems to transition from order to chaos through a complex phase as energy and/or connectivity increases.
Few proofs, many examples and formulas.

Nicollinetal92

Xavier Nicollin & Joseph Sifakis & Sergio Yovine
Compiling Real-Time Specifications into Extended Automata
IEEE Trans SE-V18 n9 (Sep 1992)pp794-804
=THEORY timeout watchdog gnerates event driven FSM from logical specification

NicolWilkesManola93

John R Nicol & Thomas Wilkes & Frank A Manola(GTE Labs)
Object Orientation in Heterogeneous Distributed Computing Systems
IEEE Computer Magazine V26n6(June 1993)pp57-67
=SURVEY Glossary

NeilLaplante03

Colin J Neil & Phillip A Laplante
Requirements Engineering: The State of the Practice
IEEE Software Magazine V20n6(Nov/Dec 2003)pp40-45
=POLL 194 GRADUATE ALUMNI REQUIREMENTS PRACTICES
- Waterfall is still the most popular life cycle (just)
- But prototyping is popular -- especially for user interfaces. Scenarios and use cases are the most popular requirements technique. Focus groups and informal modelling are popular. Then JAD and other "involve the user" technique s. Methodologies: "none" is most popular(32%), OO(30%), vs 40% structured: SADT(12%),
- SReM(10%), SSADM(8%), SERM(7%) and no JSD.
- Models: informal 51%, semiformal 27%, formal 7%. Success in 50% of projects. Tho' management felt 50% of the time the project was either over budget or late or both. Longer (> 2yrs) projects were less successful: over budget , late, less likely to be easy to use or to meet needs. Quality assurance: informal or formal walkthroughs plus some checklists and/or scenarios.

NeilMEtal98

Martin Neil & Gary Ostrolenk & Mary Tobin & Mark Southworth
Lessons from Using Z to Specify a Software Tool
IEEE Trans Soft Eng V24n1(Jan 1998)pp15-23
=EXPERIENCE Z SPECIFICATIONS caused problems
high productivity+low fault density inexplicable
(dick)|-wot no DDD!

NentwichEtal00

Christian Nentwich & Wolfgang Emmmerich & Anthony Finkelstein & Andrea Zisman
BOX: Browsing objects in XML
Software - Practice & Experience V30n15(Dec 2000)pp1661-1676
=DEMO WWW/NET UML XML XMI DOM VML Java DHTML JavaScript

NentwichEtAl03

Christian Nentwich & Wolfgang Emmerich & Anthony Finckelstein & Ernst Ellmer
Flexible Consistency Checking
ACM TOSEM Trans Software Eng & Methodology V12n1(Jan 2003)pp28-63
=DEMO WEB/NET DOCUMENTATION XML xlinkit webservice LOGIC CONSISTENCY MANAGEMENT DIFFERENCING TOOL UML Java EJB
Links are not placed in documents. Connect elements in other documents.
Four kinds of constraint: standard, extension, integration, custom.
xlinkit::webservice= See http://www.xlinkit.com.

NewkirkVorontsov02

James Newkirk & Alexei A Vorontsov
How .Net's Custom Attributes Affect Design
IEEE Software Magazine V19n5(Sep/Oct 2002)pp18-20
=DEMO TECHNICAL .NET vs JAVA metadata declarative code
Attributes are better than interfaces for indicating the capabilities of pieces of code.

NewmanBarabasiWatts06

Mark Newman & Albert Barabasi & Duncan J Watts
The Structure and Dynamics of Networks
Princeton UP Princeton NJ 2006 ISBN 0691113572 CR 0810-0946
=UNREAD =SURVEY RANDOM GRAPH THEORY SMALL WORLDS NET COMPLEXITY
Notes [click here if you can fill this hole]

NezhadEtal06

Hamid R Motahari Nezhad & Boualem Benatallah & Fabio Casati & Farouk Toumani
Web Services Interoperability Specifications
IEEE Computer Magazine V39n5(May 2006)pp24-32
=SURVEY STANDARDS WEB SERVICES SPECIFICATIONS METASPECIFICATION WS-* ebXML
MetaSpecifications define a language that is used to specify a property of a system -- e.g. security or QoS.

Nielsen92

Jacob Nielsen(Bellcore)
The Usabillity Engineering Life Cycle
IEEE Computer V25n3(Mar 1992)pp12-22 CR9302-0089 "We should not rush into design""do as much as possible before design is started" Hypertext(p17) Metamethod methods vs usage and impact(1..5)(p21)

Nielsen93

Jacob Nielsen(Bellcore)
Iterative User-Interface Design
IEEE Computer magazine v26n11(Nov 1993)pp32-41
=EXPERIENCE ITERATIVE USE HCI

Nielsen95

Jakob Nielsen(SunSoft)(mailto:jakob.nielsen@sun.com)
Applying Discount Usability Engineering
IEEE Software Magazine V12n1(Jan 1995)pp98-100
=EXPERIENCE CARDS USER COST PROTOTYPES
USER:Inexpensive ways to assess usability before programming. card sorting: words to icons. walkthroughs. iteration. cheap and quick but invaluable: some is better than none. Example evolution of an icon for a set of special applicationsfrom a toolchest to a toolstore to a toolchest.

Nielsen97

Jakob Nielsen
Let's Ask the Users
IEEE Software magazine V14n3(May/Jun 1997)110-111
=howto user questionaires

Nielsen99

Jakob Nielsen
User Interface Directions for the Web
Commun ACM V42n1(Jan 1999)pp65-72
=HISTORY USER WEB DESIGN
1. A download delay longer than one second breaks the flow.
2. With more than 200 pages you must have a search mechanism.
3. Create a sense of place: map+ "You are here".
4. Show all the options at one time. No scrolling on navigation pages.
5. Content is King.

NielsenFaber96

Jakob Nielsen(SunSoft) & Jan Maurits Faber
Improving System Usabillity Through Parallel Design
IEEE Computer Magazine V29N2(Feb 1996)pp29-35
=CASE-STUDY NONSEQUENTIAL PROCESS USER DESIGN
Need to try aout lots of user-interfaces
at least two but three are better. Can iterate. Can also develop look-and-feel designs rapidly and in parallel. The combine best features of best look-and-feel designs.

NielsenShumate87

Kjell W Nielsen & Ken Shumate
Designing Large Real-Time Systems with Ada
Commun ACM V30n8(Aug 1987)pp695-715
=EXPERIENCE Ada DESIGN DFDs RTS outside-in PDL. reviews DARTS Cherry/PAM/PAMELA Booch and Buhr
NONSEQUENTIAL: buffers+transporters+relays(ch01) [Gomaa84]

NielsonNielson92

Hanne Riis Nielson & Flemming Nielson
Semantics with Applications: A Formal Introduction
John Wiley & Sons Chichester W Sussex UK ISBN 0-471-92980-8
=TEXT LANGUAGE SEMANTICS FORMAL DENOTATIONAL AXIOMATIC OPERATIONAL
Used in first CSci620 class. Excellent. Out of Print.

NielsonNielson07

Hanne Riis Nielson & Flemming Nielson
Semantics with Applications: An Appetizer
Springer-Verlag NY Secaucus NJ 2007 ISBN 1846286913 CR 0811-1044 0902-0124 0905-0416
=UNREAD =TEXT LANGUAGE SEMANTICS FORMAL DENOTATIONAL AXIOMATIC OPERATIONAL
Sounds like an update of [NielsonNielson92] that I used in a graduate progrmming class 14 years ago. [click here if you can fill this hole]

NiemiJarvelin91

Prolog-Based Meta-Rules For Relational Database Representation and Manipulation
IEEE Trans SE-17 n8 (Aug 1991)pp762-788
=THEORY DATA Prolog RULES

NierstraszLemoine99

Oscar Nierstrasz & Michel Lemoine(eds)
7th European Software engineering conferencr + 7th ACM SIGSOFT Symposium on the Foundations of Software engineering
ACM SIGSOFT Software eng Notes V24n6(Nov 1999) & SpringerVerlag lect notes in comp sci V1687 ESEC/FSE'99
=PROCEEDINGS

NierstraszMeijler95

Oscar Nierstrasz & Theo Dirk Meijler
Research Directions in Software Composition
ACM Computing Surveys V27n2(June 1995)pp262-264
=THEORY REUSE ARCHITECTURE LANGUAGES

Nilsen98

Kelvin Nilsen
Adding Real-time Capabilities to Java
Commun ACM V41n6(Jun 1998)pp49-56
=ADVERT PERC is JAVA + TIMING
real time programming: tedious costly experimental
Java unpredicatable because of garbage collection algorithms and undefined scheduling rules
PERC::= See http://www.nemonics.com/.
Rate monotonic scheduling

NimmerErnst02

Jeremy W Nimmer & Michael D Ernst
Invariant Inference for Static Checking: An Empirical Evaluation
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp11-20
=EXPERIMENT V&V PROVING TOOLS INVARIANT ASSERTIONS ESC/Java Houdini Daikon
Unsound tests lets bugs get away.
ESC/Java is an unsound static checker that requires lots of assertions. Houdini adds likely assertions and remove those that fail to be true. Daikon runs tests and suggests invariants but is unsound.
All tools helped, but speed and transparency is valued more than accuracy.
ESC::= See http://research.compaq.com/SRC/esc/.
Daikon::= See http://pag.lcs.mit.edu/daikon.

Ningetal94

Jim Q Ning & Andre Engberts & W(Voytek) Kozacinski <*@andersen.com>
Automated Support for Legacy Code Understanding
Comm ACM V37n5(May 1994)pp50-57
=ADVERT TOOL EVOLUTION MAiNTENANCE CODE

Nishidaetal91

Fujio Nishida & Shinobu Takamatsu & Yoncharu Fujita & Tadaaki Tani
Semi-Automatic Program Construction Using Library Modules
IEEE Trans SE-17 n9 (Sep 1991)pp853-871 CR9302-0087
=THEORY re-use logic natural PURPOSE MAPS ≡ MATHS
refinement := unification and proof by refutation of horn clauses of structured specification with problem parts
library with specifications.

Nissanke99

Nimal Nissanke
Introductory Logic and Sets for Computer scientists
Addison Wesley Longman 1999 ISBN 0-201-17957-1 QA76.9 L63N57
=TEXT Z LOGIC DISCRETE MATH
for CSUSB csci556/656

Nissenbaum94

Helen Nissenbaum<helen@phoenix.princeton.edu
Computing and Accountability
Comm ACM V37n3(Jan 1994)pp73-80
=ARTICLE PROCESS PEOPLE
1. (1) many hands, (2) bugs, (3)computer scapegoat, (4) ownership without liability. Actions:
2. Distinguish accountability from liability,
3. Clarify and promote a substantive standard of care
4. simpler designs, modular approach, formal analysis,
5. QA, auditting, redundancy, excellent documentation.
6. Impose strict liability doctrine to software.

NIST4712

National Institute of Standards & ??
Questions and Answers on Quality
The [ISO9000] standard Series & Quality System Registration & Related Issues
Natl Center for Standards and Certification Information, NIST, TRF Bldg Room A163, Gaithersburg, MD 20899((301)-975-4040
=STANDARD QUALITY

Nissenbaum01

Helen Nissenbaum
How Computer Systems Embody Values
IEEE Computer Magazine V34n3(Mar 2001)pp120+118-119
=ESSAY ETHICS
control, transparency, balance, non-discrimination, enhance trust.

NiuAtleeDay02

Jianwei Niu & Joanne m Atlee & Nancy A Day
Composable Semantics for Model-Based Notations
SIGSOFT 2002/FSE 10 & ACM SIGSOFT Software Engineering Notes V27n6(Nov 2002)pp149-158
=ADVERT HTS includes statecharts RSML CSP CCS LOTOS etc
See [NiuAtleeDay03]

NiuAtleeDay03

Jianwei Niu & Joanne M Attlee & Nancy A Day
Template Semantics for Model-Based Notations
IEEE Trans Software Engineering V29n10(Oct 2003)pp866-882
=FORMAL SEMANTICS DYNAMIC MODELS CSP CCS LOTOS BTS SDL88 RSML STATECHARTS SCR Petri TOOLS OPERATIONAL microstep macrostep
See [NiuAtleeDay02]

NiuEasterbrook07

Nan Niu & Steve Easterbrook
So, You think you know others' goals? A Repertory Grid Study
IEEE Software Magazine V24n2(Mar/Apr 2007)pp-61
=EXPERIENCE KHP REQUIREMENTS GOALS RGT =SURVEY REPERTORY GRID PCT Kelly
RGT::="Repertory Grid Technique".
Grids discover the dimensions of the personal space for handling a set of objects.
PCT::="Personal Construct Theory", by George Kelly, all people construct their own models of the world using their own dimensions.
Grids are good for provoking discusion and eliciting hidden requirements/properties.
Need tools to support RGT.
Sidebars survey work and introduce RGT

NivatPerrin84

M Nivat & D Perrin
Automata on Infinite Words
Springer Verlag 1984 Lect Notes in CS #192
=THEORY topology theory language

Nixon00

Brian A Nixon
Management of Performance Requirements for information Systems
IEEE Trans Software Engineering V26n12(Dec 2000)pp1122-1146
=CASESTUDY Performance Requirements quality technical softgoals NFR graphic SIGs nonnumerical conflicts DATA
3 case studies of information systems
Chapter 9 of ChungNixonYuMylopoulos99 covers same techniques but without the case studies

Noble00

James Noble
arguments and Results
Computer Journal V43n6( 2000)pp439-450
=DEMO PATTERNS Object-Oriented DESIGN TECHNICAL SIMPLIFICATION Smalltalk
list of Pattern names: Argument Object, Selector Object, Curried Object, Result Object, Future Object, Lazy Object.
Future objects will give the answer in time meanwhile....
Lazy objects return info that may or may not be used by the client because it was easy to do it at the time but will be difficult later.

NobleBiddle02

James Noble & Robert Biddle
Notes on Postmodern Programming
Victoria U of Wellington NZ Tech Report CS-TR-02/9(Mar 2002) [ research ]
=IDEA POSTMODERN TECHNICAL

NoffsingerEtal98

W B Noffsinger & Robert Niedbalski & Michael Blanks & Niall Emmart
Legacy Object Modeling Speeds Software Integration
Commun ACM V41n12(Dec 1998)pp80-89
=EXPERIENCE three-tier architecture (mainframe+server+client) for CICS CORBA HTTP

Norman83

Donald A Norman
Design Rules Based on the Analysis of Human Error
Commun ACM 26 4 pp254-258 also [Norman90]
=EXPERIENCE USER engineering RISKS

Norman88

Donald A Norman
The Design of Everyday things
Basic Books 1988 ISBN 0-465-06710-7
=UNREAD =EXAMPLES ENGINEERING USER INTERFACE PEOPLE COGNITIVE
TBD [click here if you can fill this hole]

Norman90

Donald A Norman
Commentary: Human Error and the Design of Computer Systems
"Viewpoint" Commun ACM V33n1(Jan 1990)pp5-6 &7
=ESSAY USER engineering ERRORS
Compare [Norman83]

Norman98

Donald A Norman
The Invisible computer: Why good products can fail, the PC is so complex, and Information appliances are the solution
MIT Press Cambridge MA(1998) ISBN 0-465-06710-7
=HISTORY DESIGN ENGINEERING PROCESS FAILURE CHASM USER-CENTERED DISRUPTIVE
Life cycle: techie early adopters; real users.
Success
1. First to market is not enough.
2. Best technology is not enough.
3. Cheapest is not enough.
In the long run it is having users who enjoy and need the product.
Creeping featuritis.
1998 -- one machine switches between many functions and does none of them well.
Vision: many small, apparently simple, focussed, and communicating appliances.
Also see [Norman88] [NormanDraper86]

NormanDraper86

Donald A Norman & Stephen W Draper ( eds )
User Centered System Design, New Perspectives on Human-Computer Interaction
Lawrence Erlbaum Hillsdale NJ 1986 QA76.9 i58 u73 1986 ISBN 0-89859-781-1
=CONFERENCE USER UCSD DESIGN HCI MODEL metaphor cognitive engineering mimesis errors
We don't really want to use a computer. We want climb pyramids, sort thru our recipes, make a painting, ...

Notkin93

David Notkin(Editor)
SIGSOFT'93 Proc of the 1st ACM SIGSOFT Symposium on the Foundations of Software Engineering(7-10 Dec 1993)
SIGSOFT Software Engineering Notes V18n5(Dec 1993)
=PROCEEDINGS

NottegarPriamDegano01

Chiara Nottegar & Corrado Priam & Pierpaolo Degano
Performance Evaluation of Mobile Processes via Abstract Machines
IEEE Trans Software Engineering V27n10(Oct 2001)pp867-889
=FORMAL ALGEBRA MOBILE PERFORMANCE SEMANTICS HO_π calculus
HO_π::="Higher Order π calculus based on name passing", passing a name lets processes move from place to place.

Nov07

Oded Nov
What Motivates Wikipedians
Commun ACM V50n11(Nov 2007)pp60-64 CR 0812-1214
=SURVEY OPEN SOURCE KNOWLEDGE MOTIVATION
Looks like "fun" is the main reason for editting the Wikipedia

Novak95

Gordon S Novak
Creation of Views for Reuse of Software with Different Data Representations
IEEE Trans Softw Eng VSE21n12(Dec 1995)pp993-1005 [ novak ]
=ADVERT TOOL GUI GENERIC problems/solutions LISP C/C++

Novak97

Gordon S Novak Jr
Software Reuse by Specialization of Generic Procedures through View
IEEE Trans SE V23n7(Jul 1997)pp401-417
=THEORY GENERICITY OBJECTS REUSE EXAMPLES GLISP =TOOL
views::=concrete_type(0..1)-(0..1)abstract_type
also connecting clusters of types [ novak ]

NovakHillWanSayrs92

G Novak & F Hill & M Wan & B Sayrs
Negotiated interfaces for software reuse
IEEE Trans Softw Eng SE-V18n7(Jul 1988)pp??
=EXPERIENCE REUSE [Novak95]

NozekSchwartz88

John T Nosec & Ruth B schwartz
User Validation of Information System Requirements: Some Empirical Results
IEEE Trans Soft Eng VSE-14n9(Sep 1988)pp1372-1375
=EXPERIMENTS compare DFD HIPO Flowchart narative and Warnier. Result no real differences except: HIPO showed structure and DFDs showed boundaries

Norwalk09

Jeff Norwalk
Featured Case Study: Making the Move to AJAX
ACM Queue V7n1(Mar 2009) [ detail.cfm?id=1515744 ]
=CASE STUDY WEB/NET AJAX Javascript GWT DEBUGGING RIA SaaS SERIALIZATION PERFORMANCE QUALITY FITNESS
Beta release did not work well enough -- did not fit the user and underperformed.
Always try a full load test.
Always try a user interface test.
Also see [Christy09]

NunesCunha00

Nuno J Nunes & Joa'o F Cunha
Wisdom: A software Engineering Method for Small Software Development Companies
IEEE Software Magazine V17n5(Sep/Oct 2000)pp113-119
=ADVERT LITE-WEIGHT METHOD SIZE PROCESS UML MANAGEMENT CULTURE ITERATION MODEL USER
Chaos (Nike / just do it ) may make money but may fail and does not guarantee quality.
iteration := requirements..set goals; do it; evaulate results.
Parallel development and maintence.
Participative requirements for each iteration. requirements. estimating, risks, multiple prototype types.
Avoid early hi-fi prototypes!
In small projects analysis and design can be embedded in implementation.
Seven models(business/domain, use case, analysis, interaction, design, dialog, presentation ). 4 types of diagram {usecase, class, activity, statechart }. Initial model use stickies, then subset of UML
new UML stereotypes: browser, editor, task-class, interaction space, input element, output element, action, navigates contains.

Nuseibeh01

Bashar Nuseibeh <B.A.Nuseibeh@open.ac.uk> [ ban25 ]
Weaving Together Requirements and Architectures
IEEE Computer Magazine V34n3(Mar 2001)pp115-117
=ADVERT PROCESS REQUIREMENTS ARCHITECTURE Twin Peaks IKIWISI COTS XP
Two peaks: Requirements and architecture. Spiral down from one to the other and back again adding and subtracting detail.
Details: Goedicke & Nuseibeh 1996: The Process Road between Requirements and design, Proc 2nd World Conf integrated Design and Process Workshop SDPS Austin Texas.

Nuseibeh12

Bashar Nuseibeh
State of the Journal
IEEE Trans Software Eng V38n1(Jan/Feb 2012)pp1-2
=EDITORIAL CONFERENCES TRANSACTION ELECTRONIC PUBLICATION
Describes state of TSE and their plans for mainly electronic publication in the next year or so.
Already has accepted papers online through the IEEE portal before published on paper

Nuseibehetal94

Bashar Nuseibeh & Jeff Kramer & Anthony Finkelstein
A Framework for Expressing the Relationships between Multiple Views in Requirements Specification
IEEE Trans SE-V20n10(Oct 1994)pp760-773 [Finkelsteinetal94]
=ADVERT REQUIREMENTS SPECIFICATION METHODS CORE FUSION
Inconsistency management
p769:"The real world (the domain of requirements engineers) forces us to work with inconsistencies"
Compare with the way mathematicians handle inconsistencies in [Lakatos76].

NuseibehEasterbrookRusso00

Bashar Nuseibeh & Steve Easterbrook & Alessandra Russo
Leveraging inconsistency in Software Development
IEEE Computer Magazine V33n4(Apr 2000)pp24-29
=ESSAY
A foolish consistency is the hobgoblin of small minds

NuseibehRobertson97

Bashar Nuseibeh & Suzanne Robertson
Making Requirements Measurable
See [ICSE'97]
=ADVERT Tutorial

NuseibehHaleyFoster09

Bashar Nuseibeh & Charles B Haley & Craig Foster
Securing the Skies: In Requirements we Trust
IEEE Computer Magazine V42n9(Sep 2009)pp64-72
=EXPERIENCE ITERATIVE FORMAL SECURITY REQUIREMENTS ANALYSIS ATC TOULMIN ARGUMENT PROOF RISKS SYSTEM ARCHITECTURE STAKEHOLDERS EXPERTS
Advice: Exploit the experts. Exploit nonexperts. Scope the problems. Iterate to mitigate. Formalize but also argue informally.
Used [Jackson01] for architectural models. Used Toulmin to structure arguments and rebuttals.
Security requirements derived from protecting assets and challenging assumptions exposed by form proofs.
Outer arguments on cover hidden assumptions, inner arguments rebut assumptions and lead to mitigation strategies or revisions of requirements.

NuseibehZave10

Bashar Nuseibeh & Pamela Zave
Software Requirments and designs: the work of Michael Jackson
Good Friends Publishing Co, NJ 2010
=SURVEY REQUIREMENTS DESIGN JSD JSP
Help.... [click here NuseibehZave10 if you can fill this hole]

O'HareTroan94

A B O'Hare & E W Troan
RE-Analyzer: From source code to Structured Analysis
IBM Systems Jnl V33n1(1994)pp110-130
=ADVERT TOOL VIEWS SAD method CASE REVERSE ENGINEERING

O'Reilly99

Tim O'Reilly
Lesons from Open-Source Software Development
Commun ACM V41n4(Apr 1999)pp33-37
=EXPERIENCE PROCESS OPENSOURCE

Oakley90

Brian Oakley
The state of the use of Formal Methods
pp1-5 in [Nicholls90]
"It's like the early days of structural engineering[...]lacks the equivalent of Bowes diagrams, lacks component reuse, lacks tolerancing and quality approval processes, lacks proof[...]"

ObjectManagementGroup93a

Object Management Group
Object Management Architecture Guide 2nd Edn
QED Publishing Group Wellesley MA 1993
=STANDRAD OMG Object-oriented Architecture
OMG::="Object Management Group".

ObjectManagementGroup93b

Object Management Group & X/Open Co. Ltd.
The Common Object Request Broker: Architecture and Specification (Rev 1.1)
QED Publishing Group Wellesley MA 1993
=STANDARD SPECIFICATION CORBA NET Object-oriented

ObjectManagementGroup02

See [OMG020302]

OBrien94

Larry O'Brien
Bad Software: Meet your Party at Luggage Carousel Three(Editorial)
Software Development V2n1(Nov 1994)pp7-8
=EDITORIAL RISKS

OBrien95

Larry O'Brien
Guilty, Guilty, Guilty
Software Development Magazine(Dec 1995)pp7-8
=EXPERIENCE REQUIREMENTS users manual use cases
simple REQUIREMENTS capture by writing a users manual with tutorials(use-cases)
probable that many software organiastions are ignoring state of the art software engineering

OBrien96

Larry OBrien
The RAD Stuff
Software Development Magazine(Apr 1996)pp27+29+31+33
=SURVEY PROCESS SEQUENTIAL RAD HEROES
distinguishes waterfal from superteam(heroes) and RAD
RAD::="Rapid Application Development", iterative spiral+risk control
RAD=control without stifling creativity
spirals driven by risk control|release|quality
interface programming is now one of the easiest parts of programming

OBrien96a

Larry OBrien
More than a Notation
Software Development Magazine(Dec 1996)pp55-56+58+60+62
=INTERVIEW UML stereotypes patterns interfaces
Interview with Grady Booch+ James Rumbaugh + Ivar Jacobson about UML: a set of concepts like a programming language but for modeling with semantics and syntax
stereotypes patterns interfaces
on the Internet, search for The Object Technologies User's List

OBrien01

Larry O'Brien
The First Aspect-Oriented Compiler
Software Development Magazine V9n9(Sep 2001)pp23-25+
=REVIEW ASPECT JAVA TOOL AspectJ AOL Xerox PARC JDK
From George Kiczales, supported by DARPA, free from [ http://www.aspectj.org ]
Aspects supply advice to join points all thru a running program. Join points are calls/events/classes. Can add an interface to a class, and its implementation.
Clear application in debugging
Tool changes the paradigm but does not provide guidance.

OBrienEtal01

Larry O'Brien & Steve Adolph & Johanna Rothman & Scott Ambler & Scott Rosenberg & Laurie O'Conell
The Dot-Com Demise
Software Development Magazine V9n10(Oct 2001)pp38-42
=ANECDOTES ECONOMICS HISTORY CuCat WebVan
Failure from many sources including no business plan, no customer value, buggy software, paralysis by analysis and not able to adapt.
Consultants can fail if called into a company that does things right any way. Not process but communication and well defined roles><contracts.

OBrien02

Larry O'Brien
C# The Sweet Spot
Software Development Magazine V10n10(Oct 2002)pp36-39
=ADVERT C# delegates attributes webservices

OBrienTRaucher96

Timothy OBrien & Gary Raucher
UML Poised To Become OO Design Standard
Object Magazine (Nov 1996) pp16-17
=NEWS UML 1996
"A model of how a model should look" + a system of notation

OCallahanJackson97

Robert O'Callahan & Daniel Jackson
Lackwit: A Program Understanding Tool Based on Type Inference [ICSE'97]
=DEMO TOOL CODE ANALYSIS TYPES BUGS
signatures recover "real" types from "int" etc. Finds memory leaks and such.

OConnell02

Laurie O'Connell
Communications Gap
Software Development Magazine V10n5(May 2002)pp17
=REPORT SOFTWARE QUALITY
Reports on a 10 year DoD "National software quality Experiment" in the "Software Inspection Lab". No appreciable reduction in errors or improvements in process.
Main defects noted: 41% lack of traceability, 23% infringing standards. 7% logic errors. 7% functionality. 5% syntax. 5% initial values. 4% maintainability.
Software products are not "well connected" to their business requirements.

OConnellSaiedian00

Emilie O'Connell & Hossein Saiedian
Can You Trust Software Capability Evaluations?
IEEE Computer Magazine V33n7(Feb 2000)pp28-35
=EXPERIENCE PROCESS CMM DoD
SCE used to evaluate the abillity of a contractor to develop software.
Describes procedure and how it can fail to detect problems in contractors process.

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
1. Families of similar systems
2. product families
3. communication with enginners using reusable products
4. pilot
5. Domain::=Net{ narative: 2 pages, glossary:dictionary, commonality, variability:assumptions, decisions:models.}. ... Adaptable requirements components using wordperfect macros.
  Conclusions:
  1. Synthesis has immediate beefits....maturity
  2. management commitment at all levels
  3. payoff depends on a substantial commitment of effort
  4. adopting a discipline engineering process stimulates the adoption of disciplined engineering methods.

OMGEtAl10

Object Management Group
OMG Certified Systems Modeling Professional
Webs site (Sep 27 2010) [ http://www.omg.org/ocsmp/ ]
=EXAMINATIONS SysML UML SYSTEMS ENGINEERING UML REQUIREMENTS STRUCTURE PARAMETERS FORMULAS
SysML::="Systems Modeling Language", UML for Systems Engineers. [FriedenthalMooreSteiner08]

OMG020302

Object Management Group
UML Profile for Schedulability, Performance, and Time Specification
OMG [ 02-03-02.pdf ]
=STANDARD UML PERFORMANCE TIMING RT-UML PTC

ObrenovicStarcevic04

Zeljko Obrenovic & Dusan Starcevic
Modeling multi-modal human-computer interaction
IEEE Computer Magazine V37n9(Sep 2004)pp65-72
=IDEA MODEL HCI UML

Odell00

James Odell
Objects and Agents: How do they differ?
Journal of Object-Oriented Programming V13n6(Oct 2000)pp50-53
=IDEA AGENTS Object-Oriented
Agents are objects with added autonomy. They observe their environment. They can change their own state, environment, and interface.
Agents can say "No!" So not RMI but messages. So need ACL's?
ACL:=Agent Communication Language.

Odersky94

Martin Odersky
Defining context-dependent syntax without using contexts
ACM TOPLAS V15n3(Jul 1993)pp535-562 [CR] 9412-0876
=THEORY GRAMMARS SYNTAX CADET
1. CADET::="CAlculus on DErivation Trees", comparisons with others, needs a tool

OdlyzkoTilly05

Andrew Odlyzko & Benjamin Tilly
A refutation of Metcalfe's Law and a better estimate for the value of networks and network interconnections
Digital Technology Center, University of Minnesota 2005 [ metcalfe.pdf ]
=THEORY ECONOMICS NETWORK VALUE n*log(n)

Offut02

Jeff Offutt
Quality attributes of Web Software applications
IEEE Software Magazine V19n2(Mar/Apr 2002)pp25-32
=SURVEY QUALITIES WEB/NET USER diverse TECHNOLOGY ECONOMICS
Unlike mass-marketed software the first mover does not win. Customer easily and commonly switch to higher quality web sites. Quality is sticky.
Qualities:order=(Reliability, Usability, Security, Availability, Scalability, Maintainability, Time to market).
Describes evolution from simple client--http--server to n-tier architectures: client--server--application servers--databases
Educational opportunity..

OfuonyeEtAl08

Ejike Ofuonye & Patricia Beatty & Ian Reay & Scott Dick & James Miller
How do we build trust into E-commerce Web Sites
IEEE Software Magazine V25n5(Sep/Oct 2008)pp7-9
=SURVEY WWW cyberTRUST MODELS QUALITIES
Literature survey [ WebExtra.html ]
Conclusions
1. Trust is a complex quality depending on several linked factors:
  - Technology Acceptance Model (TAM),
    1. Which depends on the Usefulness and Ease-of-Use of the web-site.
    2. Ease-of-Use influences perceived Usefulness.
  - Benevolence-Competence-Integrity framework (BCI),
    1. Which depends on the perceived Risks and the site's Reputation.
2. Usefulness influences Competence and Integrity.
3. Risks influence Benevolence and Competence.
4. Reputation influences Competence.
5. All factors also directly effect Trust!

Ogdenetal94

William F Ogden & Murali Sitaraman & Bruce W Weide & Stuart H Zweben
The RESOLVE Framework and Discipline - A Research Synopsis
ACM SIGSOFT Software Engineering Notes V19n4(Oct 1994)pp23-28 See [Sitaraman94]
=ADVERT RESOLVE LANGUAGE Framework Discipline
1. Two kinds of components: abstract/specifications/concepts vs concrete realisations. concepts implemented by realizations, contexts
2. realisations use concepts (not other realizations)
3. realisations have two parts: additional concepts + body
4. highly parameterized/generic/templates -> instances
  Key Target: To be able to prove a generic implementation of a concept once and for all - once proved in general all valid instanciations will be correct.
(dick)|-Problem: Too damn complex(IMHO)

OhlsonAlberg07

Niclas Ohlson & Hans Alberg
Predicting Fault-prone software modules in telephone switches
IEEE Trans Software Engineering V22n12(Dec 1996)pp886-894
=EMPIRICAL METRICS FAULTY MODULES 130 Alberg diagrams Pareto Ericsson
Metrics can predict the 20% most fault prone modules.
Alberg diagram plots cumulatve %faults vs %modules with that # of faults.

OhstWelleKelter03

Dirk Ohst & Michael Welle & Udo Kelter
Differences between versions of UML Diagrams
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp227-236
=DEMO TOOL ALGORITHM SCM DIFFERENCE UML DIAGRAMS GRAPHICS COLOR PISET
tool uses color to show different and common parts of a UMLdiagram.
Based on XML/PCTE data.
Ignores layout (except in sequence diagrams)

OivoBasili93

Markku Oivo & Victor R Basili
Representing Software Engineering Models: The TAME Goal Oriented Approach
IEEE Trans SE-V18n10(Oct 1992)pp886-898
=DEMO PROCESS QUALITY PURPOSE OBJECT-ORIENTED EXPERT SYSTEM TOOL TAME
1. QIP::= "Quality Improvement Paradigm", loop with meta-system.
  Experience Factory(repository for stored and packaged experience) Software Engineering Models(SEMs), GoalQuestionMetric(GQM), using ERDs, is-a, instance-of, part-of, compatible, dynamic attribute link, counterpart, ES-TAME for Did Ward&Mellor, cf JSD SADT

Okhotin03

Alexander Okhotin Conjunctive Grammars
WWW [ http://www.cs.queensu.ca/home/okhotin/conjunctive/ ]
=ADVERT SURVEY Conjunctive Grammars
Also see [Okhotin04] Boolean Grammars.
Compare with [LiuWeiner73] [HehnerSilverberg83] [Hemendinger90] [Hopkins94]

Okhotin04b

Alexander Okhotin
Boolean Grammars
WWW [ http://www.cs.queensu.ca/home/okhotin/boolean/ ]
=ADVERT SURVEY Boolean Grammars
Also see [Okhotin03] Conjunctive Grammars

Okrent09

Arika Okrent
In the Land of Invented Languages: Esperanto Rock Stars, Klingon Poets, Loglan Lovers, and the Mad Dreamers Who Tried to Build A Perfect Language
Random House Publishing Group Pub. Date: May 2009 ISBN-13: 9780385527880 352pp
=SURVEY =HISTORY 900 ARTIFICIAL LANGUAGES Blissymbolics MATHEMATICS LOGIC Elvish Esperanto Gestuno Wilkins thesaurus Dalgarno Zamenhoff ONTOLOGY
Repeatedly somebody has had the same ideas for improving on natural "grown" languages -- using logic, setting up an ontology, using symbols, using numbers, using european languages, etc.
There is no natural ontology/symbology/adamic language.
Humans evolve the language that they use. Language inventors come into conflict with language users.
Bliss symbols for disabled children -- students needs vs Bliss's obsessions.
Loglan vs Lojban. Brown vs the Loglanists.
Writing Lojban is like programming. Speaking it seems to be impossible.
Learning a new language leads you to see the world differently.
Benjamin Whorf's Hypothesis?
Didn't mention e-prime or SLUNT...
You thoughts can go here: [click here if you can fill this hole]

OktabaEtAl07

Hanna Oktaba & Felix Garcia & Mario Piattini & Francisco Ruiz & Francisco J Pino & Claudia Alquicira
Software Process Improvement: the Competisoft Project
IEEE Computer Magazine V40n10(Oct 2007)pp21-28
=STANDARD IMPROVEMENT SOUTH AMERICAN SMALL ENTERPRISE CMMI VSE ISO MOPROSOFT
One size does not fit all: small enterprises need special software improvement methods.

OkunoMatsumotoAsai93

Hirotomo Okuno & Hideki Matsumoto & Hironobi Asai
TableSpec: Free Format Specification Table and Source Code Generation
Software - Practice & Experience V26n2(Feb 1996)pp213-235
=EXPERIENCE TABULAR TOOL SPECIFY code TESTS
Found that personel-days of specification about the same but gave a total reduction of 50% mainly in testing

OlaguEtAl07

Hector M Olague & Letha H Etzkorn & Sampson Gholston & Stephen Quattlebaum
Empirical validation of three software metrics suites to predict fault-proneness of Object-Oriented Classes developed using highly iterative or Agile Software Development Processes
IEEE Trans Software Engineering V33n6(Jun 2007)pp402-419
=EMPIRICAL OPEN-SOURCE AGILE BUGS METRICS CK Chidamber-Kemerer QMOOD MOOD Rhino Javascript
Showed that bad CK scores are associated with modules that need fixing.
Showed a slight tendency for metrics to be less useful in older projects.

OlearyStewart85

Data Flow Algorithms for Parallel Mathematical Computations
Commun ACM V28n8(Aug 1985)pp840-853
=DEMO DATA FLOW non-sequential MATHEMATICS

OlenderOsterweil90

Kurt M Olender and Leon J Osterweil
Cecil: A Sequencing Constraint Language for Automatic Static Analysis Generation
IEEE Trans SE-16n3pp268-280(Mar 1990)
=DEMO regular dynamic language

Olenfeldt85

Lars Olenfeldt
Object/Event Analysis
ACM SIGSOFT Software Engineering Notes v10n1 (Jan 1985) p52-57
=ADVERT DAD STD non-sequential graphic Reality

Olsen93

Neil C Olsen
The Software Rush Hour
IEEE Software Magazine V10n5(Sep 1993)pp29-37; correspondence Robert L Glass V11n1(Jan 1994)pp6&7
=THEORY PROCESS QUEUING DFD
1. change rate and service rate: like the function point model.
2. measuring the process: quality and overloading.
3. Control it: Change management.
  Glass: root problem is bad estimation.
4. "Maintenance is about enhancement not repair"

Olsen94

Neil C Olsen
Survival of the Fastest: ImprovingService Velocity
IEEE Software Magazine V12n5(Sep 1995)pp28-38
=MODEL PROCESS overloaded queueing model
Problems when incoming requirement changes faster than rate of service.
Benefits of shortening response time to change.

OlsenD93

David Olsen
Exploiting Chaos: Cashing in on the Realities of Software Development
Van Nostrand Reinhold NY NY LibCongress 76.76D47048 1992 ISBN 0-442-011124
=IDEAS Process Complexity chaos

OlsenK06

Kai A Olsen
Computer intelligence and formalization
IEEE Computer Magazine V39n8(Sep 2006)pp116+114-115
=ESSAY AI RISKS Context REALITY
Current intelligent features do the wrong thing because they don't have enough data on the context.
Automation requires data on the situation.
Need formal models of the context.

OlsenK08

Kai A Olsen
The $100,000 Keying error
IEEE Computer Magazine V41n4(Apr 2008)pp108+106-107 + Correspondence V41n6(Jun 2008)p7
=EXPERIMENT RISK USER INPUT ERROR Fossbakk
System accepted an extra digit in an account number and sent money to wrong account.
In experimental web-based simulation with "confirm" 124/1,778 transactions had errors.
29% of wrong number had extra digits in a sequence of repeated digits. Modulo 11 would find all but 3.
Always spot and highlight too many over-long input -- (Sanity check)
Confirmation does not catch common errors.
Need other checks of all user input. Example: modulo 11 CRC.
(Alan Quirt)|-typed comma for period and multiplied payment by 100 times.
(dick)|-give a picking list rather than expecting user to input digits.

Olsen11

Kai A Olsen
Programmed Politeness
IEEE Computer Magazine V44n7(Jul 2011)pp108+106-108
=ESSAY ANALOGIES USER INTERACTION DESIGN
Politeness as a protocol and a form of respect that makes systems popular.
Email sent needs a response, normally.
Warn up-front if a transaction is likely to fail with no backup.
Especially if it is an unlikely user input!
Speak the customers language consistently.
Avoid long user input -- system arrogance.
Don't silently reorganize the users life or system unlike Adobe Acrobat and Apple Quicktime.
Don't interrupt!
Remember people. Avoid reinputting previously input data.
Compare [Olsen08]

Olssenetal94

Anders Olssen & Ove Faergemand & Birger Moeller Pedersen & J R W Smith & Rick Reed
Systems Engineering using SDL-92
North Holland 1994 ISBN 0-444-89872-7
=HOWTO SYSTEMS ENGINEERNG SDL

OlverEtal10

F W Olver & D W Lozier & R F Boisvert & CW Clark (eds)
NIST Handbook of mathematical functions
Cambridge University Press NY NY (2010) ISBN 0521140633 CR 1104-0380
=HANDBOOK MATH FUNCTIONS FORMULAE STANDARD NOTATIONS
Update to [AbramowitzStegun6465]

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

OmanCook90a

Paul W Oman & Curtis R Cook
The Book Paradigm for Improved Maintenance
IEEE Software V7n1(Jan 1990)pp39-45
=ADVERT LANGUAGES READABILITY QUALITY TECHNICAL
[OmanCook90b]

OmanCook90b

Paul W Oman & Curtis R Cook
Typographic Style is More than Cosmetic
Commun ACM V33n5(May 1990)pp506-520
=EXPERIMENT LANGUAGES READABILITY QUALITY TECHNICAL

Ommering00

Rob van Ommering & Jeff Kramer & Jeff Magee
The Koala component model for consumer electronics software
IEEE Computer magazine V33n3(Mar 2000)pp78-85
=EXPERIENCE KOALA MODULAR ARCHITECTURE GRAPIC INTERFACES Phillips consumer electronics

Ommering05

Rob van Ommering
Software reuse in product populations
IEEE Trans Software Engineering V31n7(Jul 2005)pp537-550
=EXPERIENCE CONSUMER PHILLIPS REUSE COMPONENTS KOALA PROOF
cf [Ommering00]
Subsystems tend to be completely rewritten every 3.years or completely stable.
(Yawnoc's Law): Make the organization mirror structure of the system.

OnomaYamamura95

Akira K Onoma & Tsuneo Yamaura
Practical Steps Toward Quality Development
IEEE Software Magazine V12n5(Sep 1995)pp68-77
=EXPERIENCE HITACHI IMPROVEMENT PROCESS QUALITY TESTING

Oquendo06

Flavio Oquendo
Formally Modeling Software Architectures with the UML 2.0 Profile for p-ADL
ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)pp25-26(abstract) [ http://www.acm.org/sigsoft/SEN/ ] [ 1108768.1108773 ] (full text)
=PROPOSAL PROFILE UML2.0 FORMAL ARCHITECTURE pi-ADL

ORegan06

Gerard O'Regan
Mathematical Approaches to Software Quality
Springer-Verlag Secaucus NJ 2006 ISBN 184628242X CR 0710-0962
=UNREAD MATHEMATICS Z Vienna Hoare Dijkstra Parnas UML

OrfaliHarkeyEdwards97

Robert Orfali & Dan Harkey & Jeri Edwards
CORBA, Java, and the Object Web
Software Development V5n4(Apr 1997)pp31-34+36

Organick83

E Organick
A programmer's view of the intel 432 system
San Francisco McGrawHill 1983
=TEXT ADTs Technical Reality

Orman91

L Orman
Constraint Maintenance as a Data Model Design Criterion
Comput J V34n1(Feb 9) pp73-79(Special isssue on term rewriting)
CR9212-00943

Orr77

Ken Orr
Structured Systems Development
Yourdon Press NY
=HOWTO STRUCTURE SAD LCS

Orr88

Ken Orr
Methodologies bring Method to Madness
System Builder v1n1(Oct/Nov 1988)p36-39
=ADVERT LCS DAD

Orr04

Ken Orr
Agile Requirements: Opportunity or Oxymoron
IEEE Software Magazine V21n3(May/Jun 2004)pp71-73
=POLEMIC AGILE REQUIREMENTS PURPOSES
States that systems analysis has been underplayed recently but is still important.
Distinguishes primary outputs from "constraints". Ignores non-functional requirements.
Praises prototypes as a way to involve user.
Suggests that other engineering fields have developed tools that take rigorous requirements directly and cheaply to product.
(dick)|-Primary purpose: that purpose that if not met makes all other purposes valueless. For example: producing payroll payments is primary and producing W2s is secondary.

OrtinEtal04

Francisco Ortin & Benjamin Lopez &J Baltasar Garcia Perez-Schofield
Separating Adaptable Persistence Attributes through computational Reflection
IEEE Software Magazine V21n6(Nov /Dec 2004)pp41-49
=DEMO TOOL SEPARATE PERSISTENCE DATA vs BUSINESS LOGIC Nitr0 Java REFLECTION
Notes

Ortiz07

Sixto Ortiz Jr
Getting on ZBoard the Enterprise Service Bus
IEEE Computer Magazine V40n4(Apr 2007)pp15-17
=ADVERT ESB SERVICES ARCHITECTURE GLUE SOA INTEGRATION LEGACY EAI
EAI::="Enterprise Application Integration", hub and spoke. Adaptors. Brokers. Pipelines. Point-to-Point
SOA:="Service Oriented Architectures",XML defined WEB communication, SOAP HTTP UDDI ...
Hub and spoke can have performance problems.
ESB::="Enterprise Service Bus", analogy hardware bus, handles locating servers, adapting data, routing messages. JCA | SAP IDoc. Many protocols...
Does more work .... So larger servers.
Many rival products.

OShea07

Donald O'Shea
The Poincare Conjecture: In Search of the Shape of the Universe
Walker & Co NY NY 2007 ISBN 0-8027-1654-7
=POPULARIZATION MATHEMATICS TOPOLOGY GEOMETRY PROOFS REFUTATIONS
Compare to similar process noted by [Lakatos76]
Need for peer review of mathematical results.
Use of presentations.
Mathematics as a social process. [DeMilloLiptonPerlis79] [Lakatos76]
Rise of www.arXive.com.

OSullivan09

Bryan O'Sullivan
Making Sense of Revision-Control Systems
Commun ACM V52n9(Sep 2009)pp57-62 [ 1562164.1562183 ]
=OPINION CVS Subversion Git Mercurial
No simple answers in choosing between cntrlized and distributed RCS.

Osbourn11

Toby Osbourn
Getting the most out of the Web
IEEE Software Magazine V27n6(Jan/Feb 2011)pp96+95
=HOWTO TRICKS API DOCUMENTATION COMMUNITIES GOOGLE
Docs: Ctrl/F Ctrl/- Ctrl/+
Google -unwantedterm. [similar] ~term site:... Favorites
Stack Exchange [ http://stackexchange.com ] Q&A: search before you ask, ask in right place, don't spam, try to help, use good grammar
When you've got an answer, share it!

OshriNewellPan07

Han Oshri & Sue Newell & Shan L Pan
Implementing Component Reuse Strategy in complex environments
Commun ACM V50n12(Dec 2007)pp63-67
=CASESTUDY ENGINEERING REUSE PEOPLE MEETINGS DOCUMENTATION HARDWARE R&D RATIONAL
Engineers unhappy with reuse: exploration became exploitation + too many meetings.
The design of a component does not record its rationale.
Proposes that meetings to present new components should be held in laboratory with technical tools to demo ideas.
Problems with redesign feedback loops and time needed to reuse previous work.
(dick)|-management confused research with development.

Osterbye95

Kasper Osterbye
Literate Smalltalk ProgrammingUsing Hypertext
IEEE Trans on Software Eng VSE-21n2(Feb 1995)pp138-145
lost in hyperspace
switches from details to the interrelation of modules
no woven output....it is its own hypertext

Ostertagetal92

E Ostertag & J Hendler & R P Diaz & C Braun
Computing Similarity in a Reuse Library System: An AI-Based Approach
ACM Trans Softw Eng Methodol V1n3( Jul 1992 )pp 205-228
REUSE Lists of various ways components can be classified

Osterweil87

Leon J Osterweil
Software Processes are Software Too
Proc Int'l Conf on Software Engineering (ICSE) IEEE CS Press Los Alimitos CA 1987 pp2-13
Process Programming

Osterweil03

Leon J Osterweil
Understanding Process and the Quest for Deeper Questions in Software engineering Research
FSE-11 & ESEC 9 & ACM SIGSOFT Software Engineering Notes V28n5(Sep 2003)pp6-14
=HISTORY RESEARCH SOFTWARE PROCESS LANGUAGE MODEL dataflow workflow
Importance of having multiple languages modelling processes.
Many domains require the need of defined processes. software engineering is just one such domain.
Solving technical problems leads to new deeper questions. For example: what is software?
59 refs.

OsterweilClarke92

Leon J Osterweil & Lori A Clarke
A Proposed Testing and Analysis Research Initiative
IEEE Software Magazine V9n5(Sep 1992)pp89-96
RISKs and testing
OstrandWeyukerBell04
1. Thomas J Ostrand & Elaine J Weyuker & Robert M Bell
2. Where the bugs are
3. Proc ISSTA 2004 & ACM SIGSOFT Software Engineering Notes V29n4(Jun 2004)pp86-96
4. =