[Text Version] newbib Thu May 9 14:36:33 PDT 2013

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 C FORTRAN LANGUAGES
History of FORTRAN and C

Allman12

Eric Allman
Managing Technical Debt
Commun ACM V55n5(May 2012)pp50-55 CR 1211-1150 [ 2160718.2160733 ]
=SURVEY CODE TECHNICAL CHOICES ITERATION
Technical debt happens when you don't do it the best possible way.
It nearly always has to be paid off but typically by some one else.
The interest on the debt comes from working round or with the less than best system.
4 way trade off: quality, time, resources, & debt.

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.

ArcuriZohaibBrand12

Andrea Arcuri & Muhammad Zohaib & Lionel Brand
Random Testing: Theoretical results and practical implications
IEEE Trans Software Engineering V38n2(Mar/Apr 2012)pp258-277 & ISSTA 2010
=SURVEY PROBABILITY TESTING ORACLES SUT COUPON COLLECTOR RT
Good introduction to the topic. Covers the background and history well.
Proves several neat theorems.
Traditionally random testing is thought to be worse than partition testing.
This paper surveys experience papers and the theory to argue that it is not as bad as we thought.

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]

Armour12

Phillip G Armour
The business of software -- a measure of control
Commun ACM V55n6(Jun 2012)pp26-28 [ 2184319.2184329 ]
=ESSAY METRICS vs PROCESS KNOWLEDGE DOMAIN KNOWLEDGE
Chicken and egg.
Why measure something that is out of control -- unrepeatable.
Measurement can be used to enforce a process.
Core metrics: size, productivity, time, effort or cost, reliability or quality.
Size stands in for the knowlege content of the software.
Productivity as a proxy for the rate of learning.
Time: from when to when? Ramping up!
Effort may ignore overtime!
Quality - bad news is suppressed - bugs. But defects found show learning/progress.
Conclusion: much variability in measurement.

Armour13

Phillip G Armour
How we build things and why things are are 90% complete
Commun ACM V56n1(Jan 2013)pp32-33 [ 2398356.2398367 ]
=ESSAY ESTIMATION IGNORANCE SCHEDULE RISK Rayleigh PHASES
Work does not proceed in a linear fashion. The most work is done in the middle of the project and then there is a long tail.
For t:Time, distribution_of_total_effort_at_time(t)::= 2*K*a*t*exp(a*t^2) where K = total_effort and a=constant.
Cumulative_amount_complete::= K*(1-exp(a*t^2)).
Armour_Phases::Process= Preparation; Production; Proving.
It is not just that we don't know all the answers until the project is over. We don't know all the questions either.

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.

Berghel12

Hans Berghel
Breaking the fourth wall of electronic crime: blame it on the thespians
IEEE Computer Magazine V45n5(May 2012)pp86-88
=IDEA TRUST NET PEOPLE
Actors provide a recipe for cyber crime:
1. Create situation that looks plausible,
2. Target performance at particular audience.
3. Understand people and know how to exploit their frailties.
4. Focus on getting audience to willingly suspend disbelief.
5. Distract audience from the above items.

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, Kruchten, ...
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

BouwersVisserDeursen12

Eric Bouwers & Joost Visser & Arie Van Deursen
Getting what you measure
Commun ACM V55n7(Jul 2012)pp54-59 [ 2209249.2209266 ]
=EXPERIENCE HOW METRICS FAIL
Software Improvement Group
Metrics steer people. You get what you measure.
What does the metric mean? What is the goal?
Metric in a bubble. No interpretation. No context. What does it mean?
Treating the metric. Cosmetic changes. Find out the root cause and treat that!
One-track metric. Focus on just one measurement and ignoring the rest. Dig deeper.
Metrics galore. Too many metrics makes teams ignore all of them. Focus!

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 [ software ]
=ESSAY DESIGN METHODS
Real designers are oportunistic and modify the methods they are taught.

Budgen13

David Budgen
Design Patterns: Magic or Myth?
IEEE Software Magazine V30n2(Mar/Apr 2013)pp87-91 [ software ]
=EMPIRICAL =SURVEY =POLL GoF OO DESIGN PATTERNS
Evaluations of design patterns in [Gammaetal94] (GoF book).
Not much experimentation and few polls on the "Gang of Four" patterns. Only a few (8) have been evaluated.
Some evidence separating the best from the worst for 8 patterns.
list= (Observer, Composite, Abstract Factory, Facade, Factory Method, Iterator, Visitor).
More positive evidence for early items in list, and more negative for the end of the list.

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.

CalinescoGhezziKwiatowskaMirandola12

Radu Calinescu & Carlo Ghezzi & Marta Kwiatowska & Raffaela Mirandola
Self-adaptive Software needs Quantitative Verification at runtime
Commun ACM V55n9(Sep 2012)pp69-77 [ 2330667.2330686 ]
=THEORY ADAPTIVE PERFORMANCE MONITOR ADJUST DTMC PCTL SERVICE
Need to verify: If Specification and Domain then Requirement.
Non-standard activity diagrams look good...
Markovian model of the specification, Probalistic Computer Treel Logic requirements.
Domain data comes from monitoring service performance.
System can switch components if performance is bad.

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.

ChaudhuriGalwaniLublierman12

Swarat Chaudhuri & Sumit Gulwani & Roberto Lublierman
Continuity and Robustness of Programs
Commun ACM V55n8(Aug 2012)pp107-115 [ 2240236.2240262 ] , Letter David L Parnas V55n11(Nov 2012)p9 [ 2366316.2366318 ]
=THEORY COMPOSITIONAL PROOFS CONTINUITY
Programs define a map from initial values of a variable to a final value, if the variables have a metric, then the mapping is often a continuous function. This means that small changes in the initial state lead to small changes in the final output.
Gives classic eta-delta definition, rules for proving in a simple imperative language, and demonstrated continuity for several famous algorithms.
Key thought: conditions define boundaries where the two branches must match to get continuity.
Continuity::= See http://en.m.wikipedia.org/wiki/Continuous_function.
Parnas gives reasons for not trusting this approach.

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

Carlos Ivan Chesnevar & Ana Gabriela Maguitman & Ronald Prescott Loui
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

CimattiRoveriSusiTonetta12

Alessandro Cimatti & Marco Roveri & Angelo Susi & Stefano Tonetta
Validation of Requirements for Hibrid Systems: A Formal Approach
ACM TOSEM Trans Software Eng & Methodology V21n4(Nov 2012)#22:1-34 [ 2377656.2377657 ]
=CASE STUDY UML OTHELLO ETCS LTL LINEAR TIME LOGIC TRAINS TOOLS ROSE SMT WORD Requisite Pro
UML used to describe domain, a natural language form of LTL.
Requirements classified: Glossary, Relationship, Action, Configuration, Behavior, Scenario, Property, Annotation.
Formalized as UML class diagram plus LTL logic constraints.
Tools check for consistency and completeness of requirements.
Discover unexpected scenarios and cases where unwanted behaviors are allowed by the requirements.
Example constraint
for all t in trains (
1. in the future t.front.end != t.MA.EOA.location and (
  1. in the future t.front.end = t.MA.EOA.location
  )
)
Experts learned to use the tools and method and liked them.

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 techniques.
- 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)
1. 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.
2. Also variations on free software: free razor + paid_for_blades, free software + paid_for_services, free software + advertizing.
Cusmano07c
1. Michael A Cusumano
2. Extreme Programming compared with Microsoft-Style Iterative Development
3. Commun ACM V50n10(Oct 2007)pp15-18
4. =ESSAY XP Microsoft ITERATION HP WATERFALL
5. Useful comparison
Cusumano08
1. Michael Cusumano
2. Technology Strategy & Managment: The Puzzle of Apple
3. Commun ACM V51n9(Sep 2008)pp- [ 1378727.1378736 ]
4. =ESSAY ECONOMICS PRODUCTS vs PLATFORMS
5. MS tends to create platforms that encourage other businesses to get involved.
6. Apple prefers a closed but higher quality (and higher priced) product.
7. Comparison with Betamax vs VHS.
CusumanoMaccormackKemererCrandall03
1. Michael Cusumano & Alan Maccormack & Chris F Kemerer & Bill Crandall
2. Software Development worldwide: The State of the practice.
3. IEEE Software Magazine V20n6(Nov/Dec 2003)pp28-34
4. =POLL 104 PROJECTS INTERNATIONAL PRACTICES ONESIZE
5. LOC productivity about the same as 10 years ago. lowest = India <US < Europe etc < Japan = most.
6. Defect rates have improved. worst US > India > Europe etc > Japan.
7. Certain clusters of practices work better than others: for example, iterative development with beta testing works as well as waterfall with complete specification.
8. See [CusumanoMaccormackKemererCrandall03]
CusumanoMaccormackKemererCrandall09
1. Michael A Cusumano & Alan MacCormack & Chris F Kemerer & William Crandall
2. Critical Decisions in Software Development: Updating the State of the Practice
3. IEEE Software Magazine V25n5(Sep/Oct 2000)pp84-87
4. =SURVEY PROCESS MANAGEMENT waterfall vs agile ONESIZE QUALITIES
5. Revisits [CusumanoMaccormackKemererCrandall03] showing a wide range of processes and qualities.
6. One size does not fit all.
7. Must choose a process to fit the situation.
8. Distributed development gives rise to a more modular structure and needs special learning to pay off.
9. A rigid process can give higher quality but at risk of loosing innovative products.
CusumanoSelby95
1. Michael Cusumano & Rick Selby
2. Microsoft's Secrets: How the world's most powerful software company creates technology& shapes markets & and manages people
3. Simon & Schuster September 1995
4. =REPORT MICROSOFT PROCESS PEOPLE MS-PROCESS AGILE
5. See also [Keuffel95b] , [Bond95] , [MyersW95] , and an extract in [CusumanoSelby97]
6. For a view of the later Microsoft proceesses, see [ Cusumano06 ]
7. 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
8. Also Warren Keuffel's notes [ notes/Keuffel95b.html ] on Cusmano's talk at ICSE 1995.
CusumanoSelby97
1. Michael A Cusumano & Richard W Shelby
2. How Microsoft Builds Software
3. Commun ACM V40n6(Jun 1997)pp53-61 CR9711-0916
4. =ADVERT [CusumanoSelby95]
CusumanoYoffie98
1. Michael A Cusumano & David B Yoffie
2. Competing on Internet Time
3. Free Press (Simon & Shuster) NY NY 1998 ISBN0-684-85319-1 HD9696.65.U64N473
4. =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
1. Mark R Cutkosky & Jay M Tenenbaum & Jay Glicksman
2. Madefast: Collaborative Engineering over the Internet
3. Commun ACM V39n9(Sep 1996)pp78-87
4. =TOOL DISTANCE ENGINEERING
5. Engineering Web: problems to solve security+standards+interactivity+organising site+people [ ACM_paper.html ]
6. ENGINEERING documents are a mixture of formal and informal information
Cutts88
1. Geof Cutts
2. Structured Systems Analysis and Design Methodology
3. Van Nostrand Reinhold NY NY 1988
4. =TEXT SAD ERD(cow format) DFD DAD(using std not ELH) SSADM PQRST
CybulskiReed92
1. Jacob L Cybulski & Karl Reed
2. A Hypertext Based Software Engineering Environment
3. IEEE Software V9n2(Mar 1992)pp62-68
4. =ADVERT HyperCASE
CysneirosLeite04
1. Luiz Marcio Cysneiros & Julio Cesar Sampaio do Prado Leite
2. Nonfunctional Requirements: from elicitation to Conceptual models
3. IEEE Trans Software Engineering V30n5(May 2004)pp328-350
4. =CASESTUDY operational QUALITIES REQUIREMENTS NFR UML LEL CR 0504-0459
5. NFR::="Nonfunctional Requirement".
6. LEL::= "Language Extended Lexicon", project glossary.
7. NFR_graph::lattice, mapped to class diagrams etc..
8. Figures have spelling mistakes & they ignore UML stereotypes & tags.
9. Can not handle Qs like maintainability that "do not demand actions to be performed by the system".
D'Souza93
1. Desmond F D'Souza
2. A Comparison of Object-Oriented Analysis and Design Methods and Application Domains
3. OOPSLA 1993 Tutorial Notes # 2 ACM PRESS
4. =SURVEY METHODS OBJECT-ORIENTED
D'Souza98
1. Desmond D'Souza
2. Interface-Centric Design
3. Software Development Magazine V6n6(Jun 1998)pp43-44+46-47
4. =ADVERT for UML book [D'SouzaWills98]
5. type models describe vocabulary
6. collaborations via interfaces
7. patterns
D'SouzaWills98
1. Desmond D'Souza & Alan Willis
2. Objects, Components, and Frameworks with UML: the CATALYSIS approach
3. AddisonWesleyLongman Reading MA 1999 ISBN 0-201-31012-0 CR9903-0146
4. =EXAMPLES OOA/D UML CATALYSIS
DAmbrosLanzaLungu09
1. Marc D'Ambrose & Michele Lanza & Mircea Lungu
2. Visualizing co-change information with the evolution radar
3. IEEE Trans Software Engineering V35n5(Sep/Oct 2009)pp720-735
4. =TOOL GRAPHIC EVOLUTION MODULE CHANGE CVS Java PACKAGES FILES
5. The image shows a central module and all the other modules surrounding it.
6. A Module is a slice of the pie and contains files.
7. The files are shown as circles with size proportional to the degree of change.
8. Their angle of a file is determined by their name with in each module.
9. Their distance depends on the degree that they are changed at the same time as the central module.
10. Relies on a revision /configuration control system that records all changes in time.
11. Tested on one maintenance project.
DaCapo08
1. 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
2. Wake Up and Smell the Coffee: Evaluation methodology for the 21st century
3. =ADVERT JAVA BENCHMARKs PERFORMANCE METRICS
4. Commun ACM V51n8(Aug 2008)pp83-89 [ 1378704.1378723 ]
5. Developing a useful benchmark is time consuming.
6. Using them needs understanding of relevant workloads, good experimental design, and rigorous analysis.
7. Benchmark research is underfunded.
DagRegnellGervasiBrinkkemper05
1. Johan Natt och Dag & Bjorn Regnell & Vincenzo Gervasi & Sjaak Brinkkemper
2. A Linguistic-Engineering Approach to Large-scale requirements Management
3. IEEE Software Magazine V22n1(Jan /Feb 2005)pp32-39
4. =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)
5. Applied to matching market requirements to business requirements.
DahlbomMathiassen97
1. Bo Dahlbom & Lars Mathiassen
2. The Future of Our Profession
3. Commun ACM V40n6(Jun 1997)pp80-89
4. =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
1. O Dahl & E W Dijkstra & C A R Hoare
2. Structured Programming
3. Ac Press NY NY 1972
4. =TEXT sequential non-sequential PURPOSE Technical
5. Once called "The Old Testament".
DaiXieLongNg07
1. Yuan-Shun Dai & Min Xie & Quan Long & Szu-Hui Ng
2. Uncertainty Analysis in Software Reliability modelling by Bayesian Approach with Maximum-Entropy Principle
3. IEEE Trans Software Engineering V33n11(Nov 2007)pp781-795
4. =THEORY PROBABILITY RELIABILITY PREDICTION
5. Problems: few tests fail, inorporating prior information, allowing uncertainty in modelling to reduce reliability.
6. MEP::= "Maximum-Entropy Principle", choose an a prior distribution to maximize the entropy given the known data.
7. For distribution p, entropy(p):= E(-ln(p(_))).
8. Use Bayesian a postiori formula to encorporate data from tests.
9. Use simulation and analysis to predict relibilities of whole system.
10. Gives examples.
11. Refers to texts for calculations of MEP.
DalaKamathKolarikSivaraman04
1. Nikuni P Dala & Manjunath Kamath & WilliamJ Kolarik & Eswar Sivaraman
2. Toward an Integrated Framework for Modeling Enterprise Process
3. Commun ACM V47n3(Mar 2004)pp83-86
4. =ADVERT BUSINESS PROCESS MODELLING IMPROVEMENT ERP EPML XML Petri Analysis TED
5. Need to model/implement distributed.
6. Need for process semantics.
7. Need to link business and enginering.
8. Graphic front-end(EPML) <->XML<-> formal Back-end. Analise back end.
9. NSF Scalable Enterprise Systems Initiative.
10. EPML::="Enterprise Process Modelling Language".
11. Graphic showing: activities (Human, Computer, Machine), logic and decision logic, data icons, control flows , (input, output)><( material, data), timing triggers.
12. TED::="Task Execution Diagram". Analysis petri nets: design (termination, deadlock, safety) + performance (resource assignment, simulation, timing, success vs time statistics)
DalalMcIntosh94
1. Siddhartha R Dalal & Allen A McIntosh
2. When to stop Testing for Large Software Systems with Changing Code
3. IEEE Trans SE-30n4(Apr 1994)pp318-323
4. =THEORY ECONOMIC TEST MAINTENANCE
DamasLambeauDupontLamsweerde05
1. Christophe Damas & Bernard Lambeau & Pierre Dupont & Axel van Lamsweerde
2. Generating Annotate Behavior Models from End-User Scenarios
3. IEEE Trans Software Engineering V31n12(Dec 2005)pp1056-1073
4. =DEMO INTERACTIVE TOOL SCENARIOS MODEL MSC LTS FLUENTS use-cases
5. Given positive and negtive scenarios (sequence charts) the system asks questions in the form of scenarios.
6. 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.
7. Fluents have a name, start and end events, and an initial value. Booleans. Example: doorOpen. [GiannakopoulouMagee03]
DamianChesan06
1. Daniela Damian & James Chesan
2. An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management
3. IEEE Trans Software Engineering V32n7(Jul 2006)pp433-453
4. =EXPERIENCE REQUIREMENTS PROCESS IMPROVEMENT ACUS
5. Evidence that collaborative and iterative analysis and negotiation of requirements into testable scenarios improves estimates and quality.
6. Evidence that change management reduces requirements creep.
7. Important contributions from forming cross-functional teams, group-analysis, traceability, and decomposition.
DamianEberleinShawGaines00
1. Daniela E Herlea Damian & Armin Eberlein & Mildred L G Shaw & Brian R Gaines
2. Using different communications media in requirements negotiation
3. IEEE Software Magazine V17n3(May/Jun 2000)pp28-36
4. =EXPERIMENT REQUIREMENTS PEOPLE ORGANISATION
5. 2 conflicting customers + 1 systems analyst + 1facilitator
6. face to face is not the best!
7. don't put all your customers in one room.
DamianiEtal06
1. Ernesto Damiani & Brian Fitzgerald & Walt Scacchi & Marco Scotto & GianCarlo Succi
2. 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)
3. Springer-Verlag New York, Inc., Secaucus, NJ, 2006.
4. =PROCEEDINGS HISTORY OPEN SOURCE F/OSS PROCESS PSYCHOLOGY ECONOMICS SOCIOLOGY USAGE CR 0802-0110
5. Academic.
6. 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.
7. Outer layers of a project are transient debugging groups that stay together as they move from project to project.
8. Prestige comes from sharing information like in scientific research.
DamianiFuginiBelletini99
1. E Damiani & M G Fugini & C Belletini
2. A Hierarchy-Aware Approach to Faceted Classification of Object-Oriented Components
3. ACM TOSEM V8n3(Jul 1999)pp215-262 + Corrigenda V8n4(Oct 1999)pp425-472
4. =TOOL REUSE COMPONENT FRAMEWORK OBJECT-ORIENTED Isa MFC C++ Borland Delphi Facetted descriptors
DamonJacksonJha96
1. Craig A Damon & Daniel Jackson & Somesh Jha
2. Checking Relational Specifications With Binary Descision Diagrams
3. Proc 4th ACM SIGSOFT 96 Symp on the Foundns of Software Eng: ACM SIGSEN V21n6(Nov 1996)pp70-80
4. =DEMO MODEL CHECKING BDDs
5. Z-like specs checked via testrolog-type diagrams
6. BDDs::=Binary Decision Diagrams
Daneva04
1. Maya Daneva
2. ERP Requirements Engineering Practice: Lessons Learned
3. IEEE Software Magazine V21n2(Mar/Apr 2004)pp26-33 +CR 0705-0527
4. =EXPERIENCE REQUIREMENTS reuse ASAP ERP
5. 13 lessons learned mainly reinforcing known results!
6. cooperation win-win team communication learning are good
7. reuse needs management: query assumptions, analyze risks, plan, do, measure...
8. need data modeling
9. lookout for unofficial requirements leaking into project.
DanforthTomlinson88
1. S Danforth & C Tomlinson
2. Type Theories and Object Oriented Programming
3. Comp Surveys V20n1 (pp29-72)Mar 1988
4. =THEORY object-oriented logic Reality
DangleLarsenShawZelkowitz05
1. Kathleen Coleman Dangle & Patricia Larsen & Michele Shaw & Marvin V Zelkowitz
2. Software Process Improvement in Small Organizations: A Case Study
3. IEEE Software Magazine V22n5(Nov/Dec 2005)pp68-75
4. =CASE STUDY DSCS CMM
5. (dick)|-when does software process improvement merge into business process reengineering?
6. (dick)|-Rediscovers some trad systems analysis and design ideas.
7. 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
1. John Daniels
2. Modeling with a sense of Purpose
3. IEEE Software Magazine V19n1(Jan/Feb 2002)pp8-10
4. =ESSAY MODELs REALITY SPECIFICATION TECHNICAL UML
5. Three types of model: World/conceptual, Specification, Implementation
6. Maps UML notations to types of model (eg UseCase-> spec)
7. Proposes using three UML stereotypes: <<concept>>, <<type>>, <<class>>
DanoBriandBarbier97
1. Benedicte Dano & Henri Briand & Frank Barbier
2. An Approach Based on the Concept of Use Case to Produce Dynamic Object-Oriented Specifications [RE'97] p54-64
3. petri-nets
DarcyKemerer05
1. David P Darcy & Chris F Kemerer
2. OO metrics in Practice
3. IEEE Software Magazine V22n5(Nov/Dec 2005)pp17-19
4. =ADVERT =SURVEY CK METRICS Object-Oriented
Dasgupta89
1. Subrata Dasgupta
2. The Structure of Design Processes
3. pp1-62 of Yovitz(ed)89
4. =THEORY ENGINEERING lifecycle=scientific discovery
Darwiche10
1. Adnan Darwiche
2. Bayesian Networks
3. Commun ACM V53n12(Dec 2010)pp80-90 [ 1859204.1859227 ]
4. =ADVERT BAYES PROBABILITY NETWORK CAUSALITY BBN HMM HIDDEN MARKOV
5. Good description of the theory, practice, and possibilities of Bayesian models.
6. Source [Pearl88]
Dasgupta91
1. Subrata Dasgupta
2. Design Theory and Computer Science: Processes and Methodology of Computer Systems Design
3. Cambridge U Press NY NY 1991(Tracts in theoretical Comp Sci)
4. =THEORY ENGINEERING methodology
5. Reviews: CR9207-0475
6. Am Math Monthly V100n4(Apr 1993) page 423
  1. plausibility::={undetermined, assumed, validates, refuted}.
Dashboard08
1. Project Dashboard Initiative
2. Project Dashboard
3. Sourceforge [ http://processdash.sourceforge.net/ ]
4. =UNTESTED =TOOL PSP TSP GRAPHIC MANAGEMENT DEFECTS QUALITITES ESTIMATION
5. Notes [click here if you can fill this hole]
Date00
1. Christopher J Date
2. What not how: the business rules approach to application development
3. Addison-Wesley Longman Boston MA 2000 pp131 $24.95 ISBN 0-201-70850-7 CR0011-0557 H.2.0 qa76.76 a65 d375 2000
4. =ADVERT RULES SQL LOGIC LPC TABLES
DateDarwen06
1. Christopher J Date & Hugh Darwen
2. Databases, Types, and the Relational model
3. Addison Wesley Longman Publishing Co, Inc., Redwood City, CA, 2007
4. =THEORY DATA Rejects SQL. Back to Codd.
DateFagin92
1. C J Date & Ronald Fagin
2. Simple conditions for guaranteeing higher normal forms in relational databases
3. ACM Trans Database Systems V17n3(Sept 1992)pp465-476
4. =THEORY DATA NORMALIZATION 5NF 4NF PJ/NF(Projection-join)
DatteroGallup04
1. Ronald Dattero & Stuart D Gallup
2. Programing Language and Gender
3. Commun ACM V47n1(Jan 2004)pp99-102
4. =POLL 37398 PEOPLE LANGUAGES GENDER COBOL Java C++ SQL HTML
5. Roughly 80/20 male/female split.
6. Experience:= distribution (..1.yr +> 11%, 1..2.yr+>16%, 3..5+>33%, 6..10+>20%, 11..14+>8%, 15.yr.. +>12%)
7. 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%, ...).
8. Most have 2 languages.
DavanbuStubblebine02
1. Premkumar T Davanbu & Stuart G Stubblebine
2. Stack and Queue Integrity on a Hostile Platforms
3. IEEE Trans Software Engineering V28n1(Jan 2002)pp100-108
4. =THEORY ADTs without trust
Davidson88
1. Colin M Davidson
2. Quicksort Revisited
3. IEEE Trans Soft Eng VSE-14n10(Oct 1988)pp1480-1481
4. =DEMO METHOD new Quicksort with no recursion [MillsLinger86]
5. inspired new way to derive quicksort: put unsorted segments into a set and so no stack and no recursion.
DaviesDavies97
1. Byron Davies & Victoria Bryan Davies
2. Patching onto the Web: Common LISP Hypermedia for the Intranet
3. Comm ACM V40n5(May 1995)pp66-69
4. ADVERT LISP WEB/NET CL-HTTP
5. CL-HTTP to put large factory database onto the WWW
DaviesJ94
1. Jim Davies
2. Specification and proof in real-time CSP
3. Cambridge Univ Press NY NY ISBN 0-521-45055-1(distinguished dissertation) CR9407-0395 AMM Review: timed denotational semantics
4. =THEORY SEMANTICS TIMING SPECIFICATION PROOF
DavisA90
1. Alan M. Davis
2. Software Requirements: Analysis and Specification
3. Prentice Hall Englewood Cliffs NJ 1990 ISBN 0-13-824673-4 BNB89-16392 QA76.76 D47 D38 1990
4. =TEXT SADT DFD DATA Coad bibliography
5. Reviews: IEEE Software magazine v11n2(Mar 1994) CR9112-0915.
6. Revised as DavisA93a
DavisA92
1. Alan M. Davis
2. Operational Prototyping: A New Development Approach
3. IEEE Software Magazine V9n5(Sep 1992)pp70-78
4. 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
1. Alan M Davis
2. Software requirements: objects & functions and states
3. Prentice Hall Englewood Cliffs NJ 1993
4. =TEXT SADT DFD DATA Coad bibliography
DavisA93b
1. Alan M. Davis
2. Software Lemmingineering
3. IEEE Software Magazine V10n5(Sep 1993)pp79-81&84;correspondence V11n1 (Jan 1994) pp10+V11n4(Jul 1994)pp110-111+QV DavisA94a&b.
4. =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
1. Alan M. Davis
2. Counterpoint: There are no bad guys and no one has the "Truth"(Side bar in Glass94a)
3. IEEE Software magazine v11n3(May 1994)pp92
4. =DEBATE
DavisA94b
1. Alan M. Davis
2. Rewards of Taking the Path Less Traveled
3. IEEE Software magazine v11n4(Jul 1994)pp100-101+102
4. =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
1. Alan M. Davis(ed)
2. Fifteen Principles of Software Engineering
3. IEEE Software Magazine V11n6(Nov 1994)pp94-96&101
4. =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
1. Alan M Davis
2. 201 Principles of Software Engineering
3. McGrawHill NY NY 1995 $24.95 ISBN 0-07-015840-1 CR9512-0926(Praise by Tom DeMarco)
4. =HANDBOOK [DavisA94c]
DavisA95a
1. Alan M Davis
2. Software Prototyping
3. Advances in Computers V40(1995)pp39-63
4. =EXPERIENCES PROTOTYPING COST QUALITY
5. Is not instantly cheaper! Choose throwaway or evolutionary.
6. Evolution demands good QUALITY from the beginning and maintained for ever.
DavisA00
1. Alan M Davis
2. The Software Company Machine
3. IEEE Software Magazine V17n2(Mar/Apr 2000)pp14-15
4. =THEORY ORGANISATION
5. (R&D + Financial + Marketting& Sales) engines
DavisA03
1. Alan M Davis
2. The Art of Requirements Triage
3. IEEE Computer Magazine V36n3(Mar 2003)pp42-49
4. =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.
5. Partition requirements into (must have + must not have + may or may not have) in this release. Use priorities to schedule the third group.
6. Use schedule probability graphs: map dates>->probability of completion by that date.
7. When there 100s of requirements group them into features/"super-requirements" capable of unified implementation and sale.
8. Refers to A Davis03? "Just enough Requirements Management", Prentice Hall Int 2003.
Davis03a
1. Alan M Davis
2. System Phenotypes
3. IEEE Software Magazine V20n4(Jul/Aug 2003)pp54-56
4. =IDEA REQUIREMENTS PHENOTYPE vs DESIGN CODE GENOTYPE
5. The difference between requirements and design is not a matter of detail or refinement.
6. Examining a fly in detail under a microscope shows you the phenotype not the genetic. Genetics is not always expressed. Phenotype is observable.
7. Requirements are observable even if highly detailed. They constrain the internal structure (genotype).
8. Requirements expressed(spoken, drawn,..) in the customers language not technical jargon.
Davis05
1. Alan M Davis
2. Just enough Requirments management: where software development meets marketting
3. Dorset House NY NY 2005, 240 pages, ISBN 0932633641 CR 0712-1159
4. =UNREAD EXPERIENCES REQUIREMENTS ELICITATION TRIAGE SPECIFICATION
5. May also have been published in 2003. See [DavisA03] above
Davisetal88
1. Alan M. Davis & Edward H Bersoff & Edward R Comer
2. A Strategy for Comparing Alternative software Development Life Cycle Models
3. IEEE Trans Soft Eng VSE-14n10(Oct 1988)pp1453-1461
4. =THEORY METHODS PROCESS USER vs TIME
5. plot USER needs and functionallity supplied against time
Davisetal91
1. Alan M. Davis & Peter A Freeman
2. Requirements Engineering (Guest Editors Introduction)
3. IEEE Trans SE-17 n3(Mar 1991)pp210-211
4. =EDITORIAL REQUIREMENTS RESEARCH
Davisetal94
1. Alan M. Davis & Pradip Sitaram
2. A Concurrent Process Model of Software Development
3. ACM SIGSOFT Software Eng Notes V19n2(Apr 1994)pp38-51
4. =THEORY non-sequential process statechart ...
DavisM11
1. Michael Davis
2. Computer ethics: will software engineering ever be engineering?
3. Commun ACM V54n11(Nov 2011)pp32-34 [ 2018396.2018407 ] Rebuttal GM Samaras V55n1(Jan 2012)p6 [ 2063176.2063168 ]
4. =ESSAY ENGINEERING KNOWLEDGE
5. SWEBOK omits knowledge (eg chemistry) found in engineering. Also misdefines engineering.
6. Software engineering has its own methods.
7. But engineering is starting to look like software engineering!
DavisMorgan93
1. John Davis<74155.416@compuserve.com> & Tom Morgan
2. Object-Oriented Development at Brooklyn Union Gas
3. Special Theme "Making OO Work" IEEE Software V10n1(Jan 1993)pp67-74
4. =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
1. Mathew S Davis
2. an object-oriented approach to constructing recursive descent parsers
3. ACM SIGPLAN notices V35n2(Feb 2000)pp46-51
4. =DEMO TECHNICAL SMALLTALK DDD
DavisR07
1. Randall Davis
2. Magic Paper: Sketch-understanding Research
3. IEEE Computer Magazine V40n9(Sep 2007)pp34-41
4. =DEMO TABLET SKETCH GRAPHICS CASE Rose USER
5. Tantalysing glimpse of a tool that front-ends Rational Rose to turn a rough sketch of a class diagram into Java Code.
6. Discusses issues in recognizing and parsing roughly hand drawn graphics.
DavisRetal96
1. Randall Davis & Pamela Samuelson & Mitchell Kapor & Jerome Reichman
2. A new View of Intellectual Property and Software
3. Commun ACM V39n3(Mar 1996)pp21-30
4. =IDEA ETHICS PROPERTY
DavisTE00
1. Thomas E Davis
2. Object-Oriented Design in Procedural Environments
3. Dr. Dobbs Journal #313(Jun 2000)pp68+70-72
4. =DEMO
5. Reinvents techniques used in FORTRAN and C!
Dean96
1. Neville Dean
2. The Essence of Discrete Mathematics
3. Prentice Hall Hemel Hempstead UK 1996
4. =TEXT DISCRETE MATHEMATICS
5. part of the "Essence of Computing" series 1996. See DeanHinchey95
DeanCordy95
1. Thomas R Dean & James R Cordy
2. A Syntactic Theory of Software Architecture
3. IEEE Trans on Software Eng VSE-21n4(Apr 1995)pp301-314 CR9602-0119 D.2.0
4. =THEORY ARCHITECTURE DFDs GRAMMAR
DeanGhemawat08
1. Jeffrey Dean & Sanjay Ghemawat
2. MapReduce: Simplified Data Processing on Large Clusters
3. Commun ACM V51n1(Jan 2008)pp107-113
4. =EXPERIENCE FUNCTIONAL PROGRAMMING Google DATA C++ LIBRARY FP NONSEQUENTIAL PIPE
5. Very large numbers of problems have been programmed to run on large clusters. Each is written as two (2) functions:
6. map: Key><Value><Data -> List(Key>< Value),
7. reduce: (Key->List(Value)) ->List( Value).
8. Also, implicitly the system has a sort function:
9. sort: List(Key><Value) -> (Key->List(Value).
10. System applies map to some data, sorts data by key and passes it to reduce.
11. map; sort; reduce
12. All the concurrency, distribution, fault tolerance etc. is provided by the system not the programmer.
13. 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.
14. For an attempt to express this in Haskell see [Lammel08]
DeanGhemawat10
1. Jeffrey Dean & Sanjay Ghemawat
2. MapReduce: A Flexible Data Processing Tool
3. Commun ACM V53n1(Jan 2010)pp72-77 [ 1629175.1629197 ]
4. =ADVERT =EXPERIENCE GOOGLE TOOLS MapReduce Hadoop FORMATS Protocol Buffer
5. Reply to [StonebrakerEtAl10]
6. Has some conclusions (p77) for speeding up MapReduce processes.
DeanHinchey95
1. Neville Dean & Michael G Hinchey
2. Introducing Formal Methods Through Role-playing
3. Papers of the 26th SIGCSE Technical Symposium on Computer science Education: ACM SIGCSE Bulletin V27n1(Mar 1995)pp302-36
4. =EDUCATION FORMAL Z
DeAntonellisZonta90
1. Valeria De De Antonellis & Bruta Zonta
2. A Disciplined Approach to Office Analysis
3. IEEE Trans SE-16n8(Aug 1990)pp822-828
4. =DEMO System Reality
DeBakker75
1. J W de Bakker
2. Flow of Control in the Proof of Sequential Programs
3. Proc 16th Ann Symposium on the Fundamentals of Computer Science Berkeley California(pp29-33) IEEE Computer Society 1975
4. =THEORY regular logic
DeBakker96
1. Jaco de Bakker
2. Control Flow Semantics
3. MIT Press Cambridge MA 1996 ISBN0-262-04154 $50 CR9709-0654(F.3.2)
4. =MATHEMATICAL 27 LANGUAGES MATHEMATICS TOPOLOGY Complete Metric spaces
Deck01
1. Michael Deck
2. Managing Process Diversity while Improving your Practice
3. IEEE Software Magazine V18n3(May/June 2001)pp21-27
4. =EXPERIENCE IMPROVEMENT EVOLUTION CLEANROOM PEOPLE RISKS INCREMENTS ONE-SIZE CMM
5. 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.
6. People -- especially new ones -- are a prime risk factor.
7. Diversity plan distinguishes three levels for each part of a process: Foundation, standard and advanced.
8. A practice can be required, recommended, or optional.
DedekeLiberman06
1. Adenekan (Nick) Dedeke & Benjamin Liberman
2. Qualifying Use Case Diagram Associations
3. IEEE Computer Magazine V39n6(Jun 2006)pp23-29
4. =DEMO UML USE CASE DOMAIN MODEL DATA FLOWS DFDs
5. Analyzing data needed for a use case and linking it to a conceptual domain model leads to better use cases.
6. Extension to UML2.0 use case diagrams.
7. (dick)|-why not use a DFD? [ papers/rjb04bDFDs/ ]
DedeneSnoeck94
1. G Dedene & M Snoeck<fdbaa30@cc1.kuleuven.ac.be>
2. MERODE: A Model-Driven Entity-Relationship Object-oriented DEvelopment method
3. ACM SIGSOFT Software Engineering Notes V19n3(Jul 1994)pp51-61
4. =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
5. For an improved method see [SnoeckDedene98]
DeekMcHugh07
1. Fadi P Deek & James A M McHugh
2. Open source: technology and policy
3. Cambridge UP NY NY 2008 ISBN 0-521-88L03-X
4. =TEXT Open source
DeGraceStahl90
1. Peter DeGrace & Leslie H Stahl
2. Wicked Problems and Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms
3. Yourdon Press NY NY 1990 QA76.758.D44 1990 CR9208-0538
4. =POLEMIC METHODS vs PROBLEMS
5. many DFDs of methods.
6. 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].
7. handcuffs and hacking.
8. (dick)|-possible confusions: COBOL=DP. top-down=waterfall. [Cardetal87]
DeGraceStahl93
1. Peter DeGrace & Leslie H Stahl
2. The Olduvai imperative: CASE and the state of software engineering practice
3. Yourdon Press NY NY 1993 ISBN 0-13-161100-3 CR9401-0006
4. =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
1. Pierpaolo Degano & Rocco De Nicola & Jose Meseguer (eds)
2. Concurrency, Graphs and Models: Essays dedicated to Ugo Montanari on his 65th Birthday
3. LNCS 5065 Springer Verlag Berlin Heidelberg (2008) CR 0909-0812
4. =FESTSHRIFT MATHEMATICS GRAPH THEORY CONCURRENCY NON-SEQUENTIAL CATEGORIES SEMIRINGS TOOLS HISTORY
5. Includes [AstesianoReggioRicca08] UML BUSINESS ... [Baetan08] ALGEBRA EQUATIONS AUTOMATA ... [BeauxisPalamidessiValencia08] NONSEQUENTIAL BAGS... [HermenegildoEtAl08] LANGUAGE Ciao ... [Quaglia08] BIOLOGICAL CELLULAR SYSTEMS...
deJong07
1. Jennifer deJong
2. It's Lean, But Is It Agile? Iterative methods are closely aligned
3. SD Times (15 Jun 2007) [ story-20070615-04.html ]
4. =ARTICLE AGILE = LEAN XP Crystal Beck Cockburn
deGuzman0jedaValverdes95
1. I P de Guzman & M Ojeda & A Valverdes
2. A formal identifiaction between tuples and lists with application to list-arithmetic categories
3. Acta Inf V32n1(1995)pp61-78 CR9602-0125 D.3.1
4. =THEORY DATA STRUCTURES
DelamaroMaldonadoMathur01
1. Macio E Delamaro & Jose c Maldonado & Aditya P Mathur
2. Interface Mutation: An Approach for Integration Testing
3. IEEE Trans Software Engineering V27n3(Mar 2001)pp228-247
4. =DEMO TESTING MODULES
Delany76
1. Samuel R Delany
2. Triton: Some Informal Remarks Toward the Modular Calculus Part One
3. Corgi Edn. 1977 Transworld London UK
4. =FICTION =SEMINAR language SEMANTICS theory structure
DelatteHeitzMuller93
1. B Delatte & M Heitz & J F Muller
2. HOOD: Reference Manual 3.1
3. Prentice Hall International(UK) Mason Paris France 1993 ISBN 0-13-396243-1 CR9411-0756
4. =HANDBOOK Object-oriented method
DelenDalaBenjamin05
1. Dursun Delen & Nikunj P Dala & Perakath C Benjamin
2. Integrated Modeling: The key to Holistic understanding of the enterprise
3. Commun ACM V48n4(Apr 2005)pp107-112
4. =ADVERT ERP MODELING TOOL PROCESS FUNCTION DATA COST ONTOLOGY PQRST GERAM IDEF CPM MODELMOSAIC REPOSITORY
5. GERAM::= See http://www.cit.gu.edu.au/~bernus/taskforce/
Delgrande98
1. James P Delgrande(Simon Fraser U, Burnaby, BC, Canada)<jim@cs.sfu.ca>
2. On first-order conditional logics
3. Artif Intell V105n1-2(Oct 1998)pp105-137 CR9903-0211
4. =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
1. Robert DeLine
2. Avoiding Packaging Mismatch with Flexible Packaging
3. IEEE Trans Software Engineering V27n2(Feb 2001)pp124-143 in ICSE'99 + Correction IEEE Trans Software Engineering V27n6(Jun 2001)p576
4. =DEMO MODULE ARCHITECTURE ware+packager NONSEQUENTIAL
5. Allows one piece of logic to be mapped into spreadsheet, CGI, yacc, ....
6. Stresses use of coroutines as more flexible than procedural code.
DeLineVenoliaRowan10
1. Robert DeLine & Gina Venolia & Kael Rowan (Microsoft Research)
2. Software Development with Code Maps
3. ACM Queue(Jul 4 2010) [ detail.cfm?id=1831329 ] & Commun ACM V53n8(Aug 2010)pp48-62 (Better pictures) [ 1787234.1787250 ]
4. =ADVERT TOOL GRAPHIC TECHNICAL CODE VISUALIZATION HCI CODE MAP VISUAL STUDIO CODE CANVAS
5. Another tool that generate graphic zoomable and editable images of code. But a tool based on what programmers already did!
6. A rare example of applying systems analysis to software engineering.
DeLineZelesnikShaw97
1. Robert DeLine & Gregory Zelesnik & Mary Shaw
2. Lessons on Converting Batch Systems to Support Interactions [ICSE'97]
3. =Experience architecture evolution
4. 8 rules on page 203
5. no ref to Jackson's work in 1975.
DelisleGarlan90
1. Norman Delisle & David Garlan
2. A Formal Specification of an Oscilloscope
3. IEEE Software V7n5(sep 1990)
4. =DEMO FORMAL SPECIFICATION HARDWARE
DeLoachHartrum00
1. Scott A DeLoach & Thomas C Hartrum
2. A Theory-based representation for object-oriented domaon models
3. IEEE Trans Software Engineering V26n6(Jun 2000)pp500-517
4. =DEMO CATEGORY THEORY fits OMT O-SLANG
5. classes events sorts atttributes axioms
DeMarco79
1. Tom De Marco
2. Structured Analysis & Systems Specification
3. Prentice Hall 1979
4. =TEXT SAD DFD PURPOSE System
DeMarco80
1. Tom De Marco
2. Structured Analysis & System Specification
3. Yourdon Press NY NY
4. =HANDBOOK SAD DFD ERD PURPOSE System Reality
DeMarco88
1. Tom de Marco
2. Interview
3. IEEE Software v6n2(Mar 1988)pp92-93
4. =INTERVIEW object-oriented non-sequential
DeMarco95
1. Tom DeMarco
2. Why Does Software Cost So Much? And Other Puzzles of the Information Age
3. Dorset house 1995 CR9702-0104 rev IEEE Software Magazine VSE13N4(Jul 1996)pp134-135(Alan M Davis)
4. =ESSAYs PEOPLE COST
DeMarco03
1. Tom DeMarco
2. The McCarthy Protocols
3. Commun ACM V46n6(Jun 2003)pp24-25
4. =ADVERT TEAM PEOPLE MEETING CEREMONY PATTERN
5. Describes Jim and Michele's patterns for meetings, see
6. TeamorX::= See http://www.mccarthytech.com, and [McCarthyMcCarthy02]
DeMarco09
1. Tom DeMarco
2. software engineering: an idea whose time has come and gone
3. IEEE Software Magazine V26n4(Jul/Aug 2009)pp96+95 =ESSAY PROCESS CONTROL METRIC ESTMATING PLANNING
4. 1982 book tried to control too much.
5. Only marginal projects need tight control.
6. Better to ask for incremental growth to better and better systems until time runs out.
DeMarco11
1. Tom DeMarco
2. All late projects are the same
3. IEEE Software Magazine V28n6(Nov/Dec 2011)pp104+103 [ lateprojects ] with discussion V29n1(Jan/Feb 2012)pp8-11
4. =ESSAY ESTIMATION COST LATE PROJECTS
5. Late projects start too late.
6. Either trying to catch a competitor, or to save money, or discovered need too late!
7. Discussions look at other possible reasons for failure.
DeMarcoBoehm02
1. Tom DeMarco & Barry Boehm
2. The Agile Methods Fray
3. IEEE Computer Magazine V35n6(Jun 2002)pp90-92
4. =DEBATE AGILE METHODS
5. Previous [Boehm02]
6. Individual skills or organizational rules?
7. Also see "Duking it out" in Software Development Magazine V10n7(Jul 2002)pp53-55
DeMarcoHruschkaEtAl08
1. Tom Demarco & Peter Hruschka & Tim Lister & Suzanne Robertson & James Robertson & McManamin
2. Adrenaline Junkies and Template Zombies: Understanding patterns of project behavior
3. Dorset House, NY NY 2008 pp248 ISBN 0932633676
4. =UNREAD PEOPLE PATTERNS PROJECTS PROCESSES
5. Contributions needed -- [click here DeMarcoHruschkaEtAl08 if you can fill this hole]
DeMarcoLister87
1. Tom DeMarco & T Lister
2. Peopleware: Productive Projects and Teams
3. Dorset House NYNY 1987
4. =TEXT PROCESS PEOPLE TEAM
5. from [Brooks95]
DeMarcoLister03
1. Tom DeMarco & Tim Lister
2. Risk Management during Requirements
3. IEEE Software Magazine V20n5(Sep/Oct 2003)pp99-101
4. =EXPERIENCE RISKS REQUIREMENTS PEOPLE POLITICS
5. Continuous public identification of risks to a project.
6. examples: arbitrary schedule, stakeholder conflict, scope creep, personnel loss, productivity variation.
7. 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)
8. Diagnose non-agreement/politics by precisely documenting data flows in and out of system.
DeMelo06
1. Darrion DeMelo
2. ReMoTe: A Complete tool to support software process management
3. CSUSB MS Presentation (Feb 24 2006)
4. =DEMO TOOL MANAGEMENT PROCESS RMT CHAT MESSAGES GANT BAR CVS BUGZILLA
DeMilloLiptonPerlis79
1. Richard DeMillo & Richard Lipton & Alan Perlis
2. Social processes and Proofs of Theorems and Programs
3. Commun ACM V22n5(May 1979) pp271-280, letters V22n11pp621-630
4. =ESSAY EXAMPLES MATHEMATICS PROOF LOGIC
5. p272: "There is simply no way to describe the history of mathematical ideas without describing the successive social processes at work on proofs."
6. See [Lakatos76] [Bauer92]
7. (DeMilloLiptonPerlis79)|-rigorous software development will also depend on social processes
DeMouraBjorner11
1. Leonardo de Moura & Nikolaj BjC8rner
2. Satisfiability modulo theories: introduction and applications
3. Commun ACM V54n9(Sep 2011)pp69-77 [ 1995376.1995394 ]
4. =ADVERT LOGIC FORMAL MATHEMATICS PROBLEM SOLVING TOOLS SMT SAT
5. SMT solve problems within specialized mathematical theories.
6. Example theory: difference arithmetic where every formula has form x-y<=c where x & y are variables and c is a constant.
7. SMT work with SAT solvers.
8. Several solvers for different theories can be combined.
9. Many problems about programs can be expressed in the theories with tractable solvers.
Demers81
1. Richard A. Demers
2. System Design for Usability
3. Commun ACM V24n8 (Aug 1981) pp494-501
4. =DEMO USER IBM System/38
DemirersGencel09
1. Onur Demirors & Cigdem Gencel
2. Conceptual Association of Functional Size Measurement Methods
3. IEEE Software Magazine V26n3(May/Jun 2009)pp71-78
4. =CASESTUDIES ESTIMATION FPA FSM UM
DempseyWeissJoneGreenberg02
1. Bert J Dempsey & Debra Weiss & Paul Jone & Jane Greenberg
2. Who is an Open Source Software developer
3. Commun ACM V45n2(Feb 2002)pp67-72
4. =HISTORY OPEN SOURCE LINUX ARCHIVE 4k contributions MetaLab LSM ibiblio.org
5. more European than US, more com than edu, more single submissions than many, some maintenance, mix of apps+utilities+games+system+etc
6. LSM::="Linux Software Map", defines data about a contribution, Net{ Title, Version, Entered=date, description, Primary-site: fields, ...}.
7. Archive at [ http://www.ibiblio.org ]
DemskyRinard06
1. Brian Demsky & Martin C Rinard
2. Goal-Directed Reasoning for specification-based Data Structure Repair
3. ICSE'05 & IEEE Computer Magazine V39n12(Dec 2006)pp931-951
4. =DEMO DATA SPECIFICATION SETS RELATIONS ABSTRACTION INVARIANTS CONSTRAINTS REPAIR FAULT AbiWorld CTAS Freeciv File System
5. In some cases it is better to repair a broken data structure incorrectly and continue running rather than crash and stop running.
6. Data structures can be repaired by using formal abstract specification in terms of Sets and Relationships.
7. Comparison with bespoke/domain specific fsck and chkdsk.
8. Fix each broken constraint in turn and use a Repair Dependence Graph to avoid infinite loops of repairs.
9. Lists actions to repair data structure.
10. Focuses on internal consistency rather than "REALITY" and as a consequence the whole application may work incorrectly.
11. Compare [KuncakLamZeeRinard06] that uses a similar abstraction/specification but includes domain constraints to model bot internal data structure consistency and external domain constraints.
DeneckerBruynooghe02
1. Marc Denecker & Maurice Bruynooghe
2. Logic Programming Revisited: Logic Programs as Inductive Definitions
3. ACM Trans Computational Logic V2n4(Oct 2001)pp623-654
4. =THEORY LOGIC Prolog INDUCTION
DenneCleland-Huang04
1. Mark Denne & Jane Cleland-Huang
2. The incremental funding method: Data-driven Software Development
3. IEEE Software Magazine V21n3(May/Jun 2004)pp39-47
4. =EXAMPLES ECONOMICS ROI COST-BENEFIT INCREMENTAL
5. Include value of each delivered increment as benefit with costs.
Denning90
1. Peter Denning
2. Human Error and the Search for Blame(editorial)
3. Commun ACM V33n1(Jan 1990)pp6-7
4. =EDITORIAL RISKS
Denning93
1. Peter J Denning
2. Educating a New Engineer
3. Comm ACM V35n12(Dec 1992)pp83-97
4. =EDUCATION ENGINEER
Denning94
1. Peter J Denning
2. Designing a Discipline of Software Design
3. 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
4. =IDEA REALITY ONTOLOGY [WandWeber90] cf [WiederholdWegnerCeri93] cf
5. ?? S-->RPQ->T (ontological mapping)
Denning02
1. Peter J Denning
2. Flatlined
3. Commun ACM V45n6(Jun 2002)pp15-19
4. =ESSAY THINKING GRIDs 2dimensional GRAPH TABLE Science
5. 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.
6. Example: science: understanding >< utility.
7. Example: software industry: technical excellence >< customer satisfaction.
8. Example: professions: technical skills >< value skills
Dennning03
1. Peter J Denning
2. Accomplishment
3. Commun ACM V46n7(Jul 2003)pp19-23
4. =ADVERT Language-action PHILOSOPHY PEOPLE SYSTEMS COORDINATION USER AI
5. People use language to make more or less explicit contracts for action. Trust comes from a promised action satisfying expectations.
6. action_loop::=#( a.request; b.promise; b.deliver; a.accept).
7. Watch out for miscommunication. Exposed by action.
8. Loss of market can come from lack of satisfaction in above loop between producer and consumer.
9. Used as a basis for Email client.
10. Management depends on handling action_loops.
11. There are protocols for inventing possibilities.
12. disclosure: Implicit awareness of signals about other's thoughts & feelings (but distorted). Need to consciously listen; react; adjust interpretation. [DenningDunham03]
Denning04
1. Peter J Denning
2. The Social Life of Innovation
3. Commun ACM V47n4(Apr 2004)pp15-19
4. =SURVEY INNOVATION ENGINEERING WEB
5. |-invention != innovation.
6. 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
1. Peter J Denning
2. The Field of Programmers Myth
3. Commun ACM V47n7(Jul 2004)pp1-20
4. =HISTORY EDUCATION programming vs computer science
5. (public)|- (myth_cs_is_p): computer science = programming != science.
6. Separate and link programming practice with algorithmic thinking/abstraction. "ladder of competence".
7. Teach error detection and correction
Denning04c
1. Peter J Denning
2. Network Laws
3. Commun ACM V47n11(Nov 2004)pp15-20
4. =SURVEY MATHEMATICS NETWORKS RANDOM GRAPHS POWER LAWS SMALL WORLDS
5. Clique: highly connected subset with few connections outside the clique.
6. Hubs: nodes with many links.
7. Broker: the only connection between a pair of cliques.
8. Bridge: connected to several cliques In many real networks the Pr[k links at a node] = (1/k)**p, "power law".
9. Accounted for by new nodes being created at random and connecting to nodes wit h larger numbers of links.
10. Hubs are key for securing and using a network.
11. Command a network by communicating intent and delegating decision making.
Denning05
1. Peter J Denning
2. Is Computer Science Science?
3. Commun ACM V48n4(Apr 2005)pp27-31
4. =HISTORY =SURVEY SCIENCE ENGINEERING TECHNOLOGY ART
5. Simulated dialog with a skeptic.
6. 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
1. Peter J Denning
2. The Locality Principle
3. Commun ACM V48n7(Jul 2005)pp19-24
4. =SURVEY =HISTORY LOCALITY
Denning07
1. Peter J Denning
2. Mastering the Mess
3. Commun ACM V50n4(Apr 2007)pp31-25
4. =ESSAY PROBLEMS INNOVATION THINKING
5. mess: disorder, no problem statement, controversy, doubtful causality, fixes don't work, ... "Normal"...
6. 4 levels of mess and actions.
7. 6 stratagems: declare, learn, question, many views, lead, disguise
Denning07a
1. Peter J Denning
2. Computing is a natural science
3. Commun ACM V50n7(Jul 2007)pp13-18
4. =ESSAY COMPUTING SCIENCE ARTIFICIAL
5. Refutes Herbert Simon's claim the that we study the "Science of the Artificial". [Simon69]
6. 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
1. Peter J Denning
2. The Choice Uncertainty Principle
3. Commun ACM V50n11(Nov 2007)pp9-14
4. =ESSAY RACE HAZARDS ARBITRATION SYNCHONISATION NON-SEQUENTIAL METASTABLE STATE flipflop Buridan
5. CUP::= "No choice between near-simultaneous events can be made unambiguously within a preset deadline".
6. 9 refs. Many examples: hardware, software, and mundane.
Denning11
1. Peter J Denning
2. The profession of IT: The Grounding Practice
3. Commun ACM V54n12(Dec 2011)pp36-40 [ 2043174.2043188 ]
4. =IDEA CLAIMS EVIDENCE ARGUMENTS DATA cf TOULMIN
5. Grounded_claim::=a claim accompanied by sufficient relevant supporting evidence.
6. Objective vs subjective evidence.
7. Also: plausibility, balance, commitment.
8. Need to provide more than objective evidence when an innovation may change the culture.
9. Some claims depend on community opinions. But beware truthiness.
10. p40: Table describes the anatomy of a grounded claim.
11. Get into the habit of noticing what kind of grounds are presented when people present claims.
DenningDunham03
1. Peter J Denning & Robert Dunham
2. The Missing Customer
3. Commun ACM V46n3(Mar 2003)pp19-23
4. =FLAME CUSTOMER USER VALUE SATISFACTION TRUST ACADEMIC EDUCATION
5. argues that IT professionals, academics, and companies can focus on technical excellence rather than the impressions that a customer gets of the profession/company.
6. 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
1. Peter J Denning & Robert Dunham
2. Innovation as Language Action
3. Commun ACM V49n5(May 2006)pp47-52
4. =ADVERT INVENTION INNOVATION PEOPLE
5. Based on the Language-Action Perspective [Dennning03]
6. Innovation is more than invention: innovation changes what people do.
7. Most innovation is a normal process.
8. Some innovations are bad and are|should be abandoned.
9. Innovation size is measured by the number of people involved: 4..4M
10. Innovation takes time.
11. Most Innovations are incremental not radical.
12. (dick)|-Viral innovation is effortless.
13. Stresses the need to observe what is going on and listen to criticism during development.
14. Claims there are seven skill areas or practices that can be learned that are needed: Sensing, Envisioning, Offering, Executing, Adopting, Sustaining + Leadership.
15. Non-verbal communication ( body language, tone of voice, ...) are the most important part of these skills.
16. Gives examples, tables, and references.
17. (dick)|-the 7 practices fit perfectly into the classic SDLC(Software Development Life Cycle).
18. Does not mention subversive innovations as in "The Inventors Dilemma".
19. Used in my CSCI372 course 2006
Denningetal89a
1. P J Denning & D E Comer & D Gries & M C Mulder & A Tucker & A J Turner & P R Young
2. Computing as a Discipline
3. Commun ACM V32n1(Jan 1989)pp9-23
4. =CURRICULUM education science ENGINEERING
Denningetal89b
1. Peter Denning (ed)
2. A Debate on Teaching Computing Science
3. Commun ACM V32n12 pp1397-1414(Dec 1989)
4. =DEBATE education
5. Dijkstra89 plus replies by 7 others also letters V33n3p264-271(Mar 1990) and V33n6pp628-630&633(Jun 1990)
DenningEtAl08
1. Peter J. Denning & Chris Gunderson & Rick Hayes-Roth
2. The Profesion of IT: Evolutionary System Development
3. Commun ACM V51n12(Dec 2008)pp- [ 1490360.1409371 ]
4. =REPORT EVOLUTION PROCESS AGILE USA GOVERNMENT LTEs RISKS FITNESS
5. Important to understand how fast a situation is changing and make sure that software is developed and delivered before the requirements change.
6. USA procurement rules allow LTE -- Limited Procurement Experiments -- that don't follow the BDUF waterfall.
7. 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
1. Peter J Denning & Fernando Flores & Peter Luzmore
2. The Profession of IT -- Orchestrating Coordination in Pluralistic Networks
3. Commun ACM V53n3(Mar 2010)pp30-32 + Correspondence V53n6(Jun 2010)p6 + letter Ronnie Ward V53n2(Jun 2010)p6
4. =ANECDOTE WoW SIMULATE TRAINING TEAMS CULTURES PEOPLE
5. Claims that there is a need for effective multicultural distributed teams.
6. Claims that certain values/activities help and can be learned in multiplayer style game environment like World of Warcraft.
7. 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.
8. Ronnie ward states the obvious that Email does not do enough to inspire teamwork.
DenningFreeman09
1. Peter J Denning & Peter A Freeman
2. The Profesion of IT: computing's paradigm
3. Commun ACM V52n12(Dec 2009)pp28-30 [ 1610252.1610256 ] +Letters V53n4(Apr 2010)pp6-7 [ Fulltext in citation ]
4. =ESSAY SCIENCE MATHEMATICS ENGINEERING COMPUTING
5. shared_paradigm::=initiation; conceptualization; realization; evaluation; action.
6. (dick)|-Ignores analysis, maintenance, iterations, updating, and social processes.
DenningHorning0202
1. Peter J Denning & James J Horning
2. Inside RISKS: Risks of Linear Thinking
3. Commun ACM V45n2(Mar 2002)p120
4. =ESSAY USER vs TECHNIQUE
5. 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).
6. Argues that software development is similar: focus on the user and focus on the technical aspects.
DenningRiehle09
1. Peter J Denning & Richard D Riehle
2. The Profession of IT: Is Software Engineering Engineering
3. Commun ACM V52n3(Mar 2009)pp24-26 [ 1467247.1467257 ]
4. =POLEMIC ENGINEERS
5. 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
6. Roles (one person plays many roles in a team) --
7. software { architect, engineer, programmer, manager } | O(systems engineer).
8. Need for Systems Thinking: From the hardware.... to the user environment.
9. Need for better tools, education, adoption of effective practices.
DenningYaholkovsky08
1. Peter J Denning & Peter Yaholkovsky
2. Getting to "We"
3. Commun ACM V51n4(Apr 2008)pp19-24
4. =ESSAY TOOLS PEOPLE TEAM WICKED PROBLEMS SYNERGY DESIGN Charettes
5. Collaboration is when people create synergistic solutions|strategies
6. Notes that tools support communication, coordination and cooperation rather than collaboration.
Dent96
1. Alan Dent(dent@highway1.com.au)
2. Solo Software Engineering
3. Software Development Magazine(Apr 1996)pp41+42+44-45
4. =EXPERIENCE SOLO
5. interuptions mean need for documentation
6. recommends diarys: project diary+random thoughts diady+design decisions diary+code change diary
7. User testing via self-hypnosis
8. Version control system [ adsoftware ]
Dern11
1. Daniel P. Dern
2. Lost programming skills: What today's coders don't know and why it matters
3. ITWorld(Aug 5 2011) [ lost-programming-skills ]
4. =POLL MANAGERS TECHNICAL LOST CODING
DershowitzJouannaud90
1. Nachum Dershowitz & Jean-Pierre Jouannaud
2. Rewrite Systems
3. Chapter 6 (pp243-320) of Leeuwen90.
4. =THEORY STRINGS GRAMMARS
DesaiEtal05
1. Nirmit Desai & Ashok U Mallya & Amit K Chopra & Munindar P Singh
2. Interaction protocols as design abstractions for business processes
3. IEEE Trans Software Engineering V31n12(Dec 2005)pp1015-1027
4. =THEORY MODEL BUSINESS PROCESS COMMITMENTS SCENARIOS OWL-P AGENTS ROLES π-CALCULUS
5. Proposes a logic of commitments between agents.
6. Uses sequence charts containing commitments to describe protocols.
7. Implies that activity diagrams are a bad way to describe business processes. Entangles the internal logic of different agents with each other. So unstable.
8. (dick)|-take home message: don't use control flows to model work flow.
DesaiChopraSingh09
1. Nirmilt Desai & Amit K Chopra & Munindar P Singh
2. Amoeba: A methodology for modeling and evolving cross-organizational business processes
3. ACM Transactions on Software Engineering and Methodology V19n2(Oct 2009)pp6.1-45
4. =ADVERT 2 CASE STUDIES Amoeba REQUIREMENTS METHOD LOGIC COMMITMENTS SCENARIOS SEQUENCE CHARTS AXIOMS EVOLUTION AGENTS SERVICES ORCHESTRATION CHOREOGRAPHY
5. Amoeba::Method= iterate( roles and interactions; contractual relationships -> Commitments; message meanings->create and manipulate commitments; Constraints; compose protocols -> process model).
6. 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.
7. Theory [DesaiEtal05]
DeselEtAl04
1. Jorg Desel & Wolfgang Reisig & Grzegorz Rozenberg (Eds)
2. Lectures on Concurrency and Petri nets: Advances in Petri Nets (LectureNotes in CSci 3098)
3. SpringerVerlag NY NY 2004 ISBN 3540222618 CR 0511-1194
4. =UNREAD =PAPERS NONSEQUENTIAL MODELS Petri TIMED AUTOMATA algebra TCP
Desfray94
1. Phillippe Desfray(SOFTEAM)
2. Object Engineering: the Fourth Dimension
3. Addison-Wesley Redwood City CA 1994 $36.95 ISBN 0-201-42288-3 CR9511-0834
4. =TEXT OBJECT-ORIENTED [Desfray96]
Desfray94
1. Phillippe Desfray(SOFTEAM)
2. title
3. IEEE Computer Magazine V29N2(Feb 1996)pp62-66
4. =CASE-STUDY Hypergenericity client-server
5. see [Desfray94] for details
  1. Adds a method with processing etc to an existing class.
  2. "for each attribute..."
DesharnaisEtal98
1. Jules Desharnais & Marc frappier & Ridha Khedri & Ali Mili
2. Integration of Sequential Scenarios
3. IEEE Trans SE V24n9(Sep 1998)pp695-678 CR9906-0431
4. =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)).
5. Scenario as a digraph labelled by two kinds of relations: those describing environment actions and those defining system actions.
6. Integration defined by union of environment actions and demonic meet of system actions.
7. "the simple fact of formalizing a specification or a scenario is a step towards a better understanding of the system under consideration"
Desilets08
1. Alain Desilets
2. Tell Me a Story
3. IEEE Software Magazine V25n2(MAr/Apr 2008)pp14-15
4. =EXPERIENCE USER REQUIREMENTS STORIES
5. Express user goals as simple, specific, and concrete stories about particular people getting valuable things.
Desouza03
1. Kevin C Desouza
2. Barriers to effective use of Knowledge Management systems in software engineering
3. Commun ACM V46n1(Jan 2003)pp99-100
4. =SURVEY REPOSITORY KNOWLEDGE EXPERTISE PEOPLE
5. Software engineers do not like being categorized as experts since it may type-cast them.
6. Knowledge about software is hard to capture and categorize on a computer data base.
7. Alternative (Human) systems may work better.
8. Measure communication not just use of repository use.
Desouza03b
1. Kevin C Desouza
2. Facilitating Tacit Knowledge exchange
3. Commun ACM V46n6(Jun 2003)pp85-88
4. =EXPERIENCE TEAM KNOWLEDGE
5. People needed encouraging to use a game room on company time.
6. Managers expected job-related knowledge to be shared in the room.
7. Lotus notes was used fro sharing knowledge later and both game room and project oriented knowledge started to be posted.
DesouzaAwazuTiwana06
1. Kevin C Desouza & Yukika Awazu & Amrit Tiwana
2. Four Dynamics for bringing use back into software reuse
3. Commun ACM V49n1(Jan 2006)pp97-100
4. =POLL 100 REUSE PEOPLE
5. Traditional reuse of published artifacts works better among novice and transient developers.
6. Uncovered evidence of three "knowledge spaces": private, public, and quasi-private.
7. A knowledge space is a collection of artifacts that may be more or less reusable. Examples repositories, code libraries, ..., and CASE tools.
8. Developers prefer to reuse stuff in their private space rather than the public space,
9. Expert: if it isn't in my private space, it probably doesn't exist.
10. Experts understand the interconnections better than novices and so tend to work with them rather than refactor into modules.
11. Novices and rookies are risk averse and don't have a wide knowledge space so they tend to reuse public artifacts.
12. Modularity encourages reuse.
13. Reuse tends to occur within groups rather than across team boundaries. The teams have tacit shared knowledge that makes reuse more valuable.
14. 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.
15. Notes application of theories to open source projects.
DetlefsNelsonSax05
1. David Detlefs & Greg Nelson & James B Sax
2. Simplify: A theorem prover for program checking
3. J ACM V52n3(May 2005)pp365-473 CR 0605-0494
4. =UNREAD =DEMO TOOL PROGRAM PROVING V&V Simplify [click here if you can fill this hole]
Deursen01
1. Arie van Deursen
2. Customer Involvement in Extreme Programming -- XP2001 Workshop Report
3. ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp70-73 & [ http://www.cwi.nk/~arie/wci2001/ ]
4. =CONFERENCE XP USER CUSTOMER SQA
5. 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.
6. Ask customers to add a "...so that..." clause to their User Stories that refers to the higher level goal.
DeursenKlintVisser00
1. Arie van Deursen & Paul Klint & Joost Visser
2. Domain-Specific Languages: An Annotated Bibliography
3. ACM SIGPLAN notices V35n6(Jun 2000)pp26-36
4. =BIBLIOGRAPHY DOMAIN LANGUAGES DSL
5. Project [ dsl ]
DeursenKuipers99
1. Arie van Deursen & Tobias Kuipers
2. Identifying Objects using Cluster and Concept Analysis
3. ICSE'99, Proceeedings of the 21st International Conference on Software Engineering (May 1999)pp246-255
4. =EXPERIMENT Concept analysis beats cluster analysis [Snelting??]
Deville90
1. Yves Deville
2. Logic Programming: Systematic Program Development
3. Addison Wesley 1990 QA76.63.D48 CR9204-0201 & CR9102-0042
4. =TEXT LOGIC PROGRAMMING
Devlin01
1. Keith Devlin
2. The Real Reason why Software Engineers need Math
3. Commun ACM V44n10(Oct 2001)pp21-22
4. =ADVERT MATH
5. Learning of specific mathematical skills is not important -- they may never be used in practice.
6. Software practice demands abstract thinking.
7. Repetitive practice in mathematics makes thinking about abstractions a familiar and so easier process.
8. Evidence of rigorous algebra improving all scores!
DevlinEtal03
1. Keith Devlin (ed)
2. Why Universities require computer science students to take math (special section)
3. Commun ACM V46n9(Sep 2003)pp37-55
4. =ESSAYS MATH
5. 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.
6. Henderson argues for math in software engineering because need precise abstract th inking.
7. 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
1. Keith Devlin & Duska Rosenberg(Brunel)
2. Language at Work: analyzing communication breakdown in the workplace to inform systems design
3. CSLI/Stanford Standford CA 1996 ISBN 1-57586-05101
4. =EXPERIENCE SYSTEM MATHEMATICS: Situation theory
5. LFZ::="Layered formalism and zooming".
Dewan05
1. Presan Dewan
2. Teaching inter-object design patterns to freshman
3. ACM SIGCSE Tech Symp Proc (Feb 2005)pp482-486
4. =DEMO small Object-Oriented PATTERNS iterator MVC observer facade composite factory Java
DewanRiedl93
1. Prasun Dewan & John Riedl
2. Toward Computer-Supported Concurrent Software Engineering
3. IEEE Computer Magazine V26n1(Jan 1993)pp17-28
4. =DEMO Flecse TECHNICAL TOOLS Concepts LIFECYCLE integration sharing NONSEQUENTIAL
DharJarke88
1. Dependency Directed Reasoning and learning in Systems Maintenance Support
2. IEEE Trans Soft Eng VSE-14n2(Feb 1988)pp211-227
3. =EXPERIENCE OBJECT-ORIENTED MAINTAINCE AI ONTOLOGY WHY
4. 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
1. Jared Diamond
2. Guns, Germs, and Steel: The Fates of Human Societies
3. Norton NY NY(2003) ISBN 0-393-31755-2
4. =HISTORY PEOPLE CONNECTIONS COMPLEXITY INNOVATION GEOGRAPHY MIME TICS
5. The differences between societies -- and who conquers who -- appear to depend on geography not genetics.
6. Innovation happens most when there are large numbers of communicating and competing parts.
7. The technologies of farming flow east-west more than North-South.
8. Catalogs crops and domesticated animals by geography.
9. The 2003 edition relates the theories to software development at Microsoft vs IBM etc.
Diaz-Herrera93
1. Jorge L Diaz-Herrera(SEI-CMU)
2. The Importance of Static Structures in Software Construction
3. IEEE Software Magazine(May 1993)pp75-87
4. =IDEA GRAPHIC MODULAR HMD
5. Hierarchical Modular Diagrams(HMD) GRAPHIC
DiazSligo97
1. Michael Diaz & Joseph Sligo
2. How Software Process Improvement Helped Motorola
3. IEEE Software Magazine V14n5(Sep 1997)pp75-81
4. =EXPERIENCE IMPROVEMENT CMM
5. increased quality and lowered cycle time
6. process defined by task leaders and preactitioners
7. CMM lower levels pay off in higher levels
DisneyJohnson98
1. Anne M Disney & Phillip M Johnson
2. Investigating Data QUALITY Problems in the PSP
3. ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp143-152 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
4. =ANALYSIS CASE-STUDY 10 students...
  [JohnsonDisney98]
DistefanoScarpaPuliafito11
1. Salvatore Distefano & Marco Scarpa & Antonio Puliafito
2. From UML to Petrie Nets: the PCM-based Methodology
3. IEEE Trans Software Engineering V37n1(Jan/Feb 2011)pp65-79
4. =DEMO METHOD ESTIMATE PERFORMANCE UML NON-MARKOVIAN PETRIE NETS PCM
Dichter93
1. Carl Dichter
2. Software Audits
3. UNIX Review V11n10(Oct 1993)pp43-49
4. =NEWS STANDARDS SQA QUALITY ISO SEI MATURITY
  1. ISO9000
  2. SEI CMM
Dick05
1. Jeremy Dick
2. Design traceability
3. IEEE Software Magazine V22n5(Nov/Dec 2005)pp14-16
4. =ESSAY traceability REQUIREMENTS DESIGN
5. Value in knowing why something is needed or how a need is met.
6. Defines implicit traceability and rich traceability.
7. Review. Sufficient design? Necessary design?
DickKrauseCozens90
1. A J J Dick & P J Krause & J Cozens
2. Computer Aided Transformations of Z into Prolog
3. pp71-85 in Nicholls90
4. =DEMO TOOL Z SPECIFICATION PROLOG PROTOTYPE
5. prototype
6. animation tool
7. finds unintended non-determinism in Z specification
Diehl07
1. Stephan Diehl
2. Software Visualization: Visualizing the structure, behavior, and evolution of sofware
3. Springer Verlag NY NY 2007 ISBN 3540465049 CR 0809-0828 & 0810-0932
4. =UNREAD =TEXT GRAPHIC CODE TECHNICAL [click here if you can fill this hole]
DiesteJuristo11
1. Oscar Dieste & Natalia Juristo
2. Systematic review and aggregation of empirical studies on elucidating techniques
3. IEEE Trans Software Engineering V37n2(Mar/Apr 2011)pp283-304
4. =SURVEY 30 EMPIRICAL REQUIREMENTS ELICITATION
5. Covers until 2005.
6. 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
1. Oscar Dieste & Natalie Juristo & Forrest Shull
2. Understanding the customer: What do we know about Requirements Elicitation
3. IEEE Software Magazine V25n2(MAr/Apr 2008)pp11-13
4. =SURVEY USER REQUIREMENTS ELICITATION
5. Many techniques and results, see [ s2voe.html ]
6. Summary:
7. Plan interviews in advance! Plan a Structure.
8. Include general question when new to a domain.
9. Introspective techniques are less useful.
10. Sorting techniques not as useful as interviews but sometimes quicker.
Dietz06
1. Jan L G Dietz
2. The deep Structure of Business Processes
3. Commun ACM V49n5(May 2006)pp59-64
4. =EXPERIENCE INTERACTION DESIGN LANGUAGE-ACTION PEOPLE REALITIES SYSTEMS
5. Used the language action perspective to analyze and design interactions.
6. Sample diagrams and jargon not well defined.
7. Distinguishes language acts from performing acts.
8. Mentions communication facts and performance facts... but not defined.
9. Goal to extract the essential map of a process as a basis for discovering opportunities and designs.
Digre98
1. Tom Digre<tomd@dataaccess.com>
2. Business Object Component Architecture
3. IEEE Software Magazine V18n5(Sep/Oct 1998)pp60-69
4. =THEORY DOMAIN ARCHITECTURE
5. Boca::="Business Object Component Architecture", pseudoC.
Dijkstra68a
1. Edsger W Dijkstra
2. Co-operating Sequential Processes
3. "Programming Languages" Academic Press 1968
4. =DEMO TECHNICAL non-sequential
Dijkstra68b
1. Edsger W Dijkstra
2. GOTO statement considered harmful
3. Letter Commun ACM 11 3 pp147-148 (Mar 1968)
4. =EXPERIENCE =HARMFUL sequential
Dijkstra68c
1. Edsger W Dijkstra
2. The structure of the "THE"-Multiprogramming System
3. Commun ACM 11 5 pp341-346 (May 1968)
4. =DEMO non-sequential formal analysis virtual machine
Dijkstra72
1. Edsger W Dijkstra
2. The Humble Programmer - ACM Turing Award Lecture 1972
3. see ACM86
4. =HISTORY science
Dijkstra74
1. Edsger W Dijkstra
2. Self-Stabilising systems in spite of distributed control
3. Comm ACM V17n11(Nov 1974)pp643-644
4. =THEORY TECHNICAL NONSEQUENTIAL
5. Ref by letter from Xavier A Bebest(Hochhheim Germany) Comm ACM V38n2(Feb 1995)pp115-117
Dijkstra76
1. Edsger W Dijkstra
2. A Discipline of Programming
3. Prentice Hall Inc Englewood Cliffs NJ
4. =TEXT guarded-commands sequential non-sequential formal logic structures
Dijkstra89
1. Edsger W Dijkstra
2. On the Cruelty of Really Teaching Computer Science
3. Talk at ACM Computer Science Conference Louisville Feb 1989(See [Denning89b] )
4. =TALK formal logic education
Dijkstra90
1. Edsger W Dijkstra(Editor)
2. Formal Development: programs and proofs
3. Addison-Wesley 1990(U Texas Year of Programming Series)
4. =MONOGRAPH FORMAL PROOFS
Dijkstra01
1. Edsgar W Dijkstra
2. The End of Computing science?
3. Commun ACM V44n3(Mar 2001)p92
4. =IDEA COMPLEXITY SCIENCE
5. |-Research is about what we don't know how to do.
6. (above)|-we need to study intricacy and simplicity.
7. "The average customer [...] expects his system to crash all the time."
DilligDilligAiken10
1. Isil Dillig & Thomas Dillig & Alex Aiken
2. Reasoning about the unknown in static analysis
3. Commun ACM V53n8(Aug 2010)pp116-123 [ 1787234.1787259 ]
4. =DEMO LOGIC MATHEMATICS MODEL CHECKING C Linux may/must SOUNDNESS
Dillon90
1. Laura K Dillon
2. Verifying General Safety Properties of Ada Tasking Programs
3. IEEE Trans SE-16n1pp51-63(Jan 1990)
4. =EXPERIENCE formal QUALITY non-sequential
Dillonetal86
1. Laura K Dillon & G S Avrunin & J C Wileden
2. Constrained Expressions: Toward Broad Applicability of Analysis Methods for Distributed Software Systems
3. COINS Tech Report 86-15 Univ of Amherst MA
4. =THEORY PREDICTING regular DAD formal
Dillonetal94
1. Laura K Dillon & G Kutty & L E Moser & P M Melliar-Smith && Y S Ramakrishna
2. A Graphical Interval Logic for Specifying Concurrent Systems
3. 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 ]
4. =ADVERT NOTATION MODAL TEMPORAL LOGIC FORMAL GIL TOOL GILED
5. GIL::="Graphic Interval Logic".
6. Later see [RTGIL] -- real time GIL
DillRushby96
1. David L Dill(Stanford) & John Rushby(SRI International)
2. Acceptance of Formal methods: Lessona from Hardware Design
3. IEEE Computer Magazine V29N4(Apr 1996)pp23-24
4. =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
1. Ania Dimaghani & Jim Dibble (Oracle Corp)
2. Strategies for Early-Stage Collaborative Design
3. IEEE Software Magazine V29n1(Jan/Feb 2012)pp39-45
4. =ADVERT EXPERIENCE COLLABORATION DESIGN SUCCESS VISEO RECORD
5. 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.
6. Part of workshop [BakerHoekOssherPetre12]
DimitrovSchietendorfDumke02
1. Evgeni Dimitrov & Andreas Schietendorf & Reiner Dumke
2. UML-based Performance Engineering Possibilities and Techniques
3. IEEE Software Magazine V19n1(Jan/Feb 2002)pp74-83
4. =ESSAY UML QUALITY PERFORMANCE OCL CONSTRAINTS STEREOTYPES TAGGEDVALUES STATECHARTS
DingMateti90
1. Chen Ding & Prabhaker Mateti
2. A Framework for the Automated Drawing of Data Structure Diagrams
3. IEEE Trans SE-V16 n5 pp543-557(May 1990) CR9207-0512
4. =THEORY graphic ERD
DingelGarlanJhaNotkin98
1. J Dingel & D Garlan & S Jha & DNotkin
2. Reasoning about Implicit Invocation
3. ACM SIGSOFT Software Engineering Notes V23n6(Nov 1998)pp209-221 & Proc 6th Int Symp on the Foundations of Software Engineering(Nov 1998)
4. =DEMO =THEORY PROOF ARCHITECTURE MODULARITY
DingelLiang04
1. Juergen Dingel & Hongzhi Liang
2. Automating comprehensive safety analysis of concurrent programs using VeriSoft and TXL
3. Proc SIGSOFT'04/FSE-12& ACM SIGSOFT Software Engineering Notes V29n6(Nov 2004)pp13-22
4. =DEMO SQA AUTOMATED MODEL CHECKING TOOL ViP TXL plLTL Verisoft
Dinh-TrongBieman05
1. Trung T Dinh-Trong & James M Bieman
2. The FreeBSD Project: A Replication Case Study of Open Source Development
3. IEEE Trans Software Engineering V31n6(Jun 2005)pp481-494
4. =POLL OPEN SOURCE PROCESS FreeBSD GNATS
5. Replicates [MockusFieldingHerbsled02]
6. FreeBSD has been developing for 10 years.
7. A small group of up to 15 developers controlled the code base.
8. No more than 50 top developers contributed most of the functionality.
9. Some ceremony was needed to coordinate work but it is neither imposed nor veri fied.
10. A larger group repairs defects fed by an even larger group of developers who r eport problems,
11. A mechanism for separating stable from unstable code means that stable code will have a lower defect density than commercial feature tested code.
12. The developers were users.
dick
1. Richard J Botting
2. Comments on Item in this bibliography
3. Various item in this bibliography [ newbib.html ] source code [ newbib.mth ]
4. =METAINFORMATION
5. I use the MATHS assertion syntax to add my annotations to items:
```
 		(dick)|-comment
```
6. Direct quotations from original items are in double-quoted strings like this
```
 		page-number:"..."
```
diSessaAbelson86
1. Andrea diSessa & Harold Abelson
2. Boxer: A Reconstructable Computational Medium
3. Commun ACM V29n9(Sep 1986)pp859-868
4. =ADVERT graphic nested boxes/text + sprites as objects+LOGO-like
DittoMunakata95
1. William Ditto & Toshinori Munakata
2. Principles and Applications of Chaotic Systems
3. Commun ACM V38n11(Nov 1995)pp96-107
4. =THEORY CHAOS COMPLEXITY
DittrichVaucouleurGiff09
1. Yvonne Dittrich & Sebastien Vaucouleur & Stephen Giff
2. ERP customization as software engineering: knowledge sharing and cooperation
3. IEEE Software Magazine V26n6(Nov/Dec 2009)pp41-47
4. =EMPIRICAL VIDEOS DEVELOPERS INTERVIEWS DOCUMENTATION ADDON ENHANCE COMPLEX CODE
5. Understanding the ERP is the main challenge. Communication. Apprenticeship. Studying code.
6. Need more than user documentation to customize ERP.
7. Separate new code from old code.
8. A feature can effect tables , forms, code, etc. Crosscutting:.aspects?! Multilevel.
9. (dick)|-more like maintenance than green field development.
Dixmier84
1. Jacques Dixmier
2. General Topology
3. Springer Verlag Undergraduate Texts in Maths 1984
4. =MATHEMATICS
DjuricDevedzic10
1. Dragan Djuric & Vladan Devedzic
2. Magic Potion: incorporating new development paradigms through metaprogramming
3. IEEE Software Magazine V27n5(Sep/Oct 2010)pp38-44
4. =ADVERT JAVA LISP JVM Modeling Spaces XML RDF/OWL DSL DOMAIN MODEL LOGIC ONTOLOGY UML MDA
5. Clojure::= See http://clojure.org, Dialect of LISP that runs in the Java Virtual Machine.
DladodHarmanOteroHu03
1. J J Dladod & M Harman & M C Otero & L Hu
2. An Empirical investigation of the influence of a s type of side effects on program comprehension
3. IEEE Trans Software Engineering V29n7(Jul 2003)pp665-670
4. =EXPERIMENT CODE TECHNICAL SIDEEFEECTS UNDERSTANDING C
5. Compared answers of students to questions about C code with and without side effects (x++).
6. Side effects make code harder to read.
DobingParsons06
1. Brian Dobing & Jeffrey Parsons
2. How UML is Used
3. Commun ACM V49n5(May 2006)pp109-113 + letterV49n8(Aug 2006)pp11-13 + CR 0705-0477
4. =POLL GRAPHIC UML PRACTICE
5. Frequency of diagrams/narratives use varies a lot between teams/projects.
6. At least Half the projects are not use case driven --- more class diagram usage.
7. Clients are involved in most diagram types.
8. Use case narratives are used >70% by analysts and programmers.
9. Use case naratives do not capture all requirements.
10. UML is complex and could be understood better.
DobricaNiemela02
1. Liliana Dobrica & Eila Niemela
2. A Survey on Software Architecture Analysis Methods
3. IEEE Trans Software Engineering V28n7(Jul 2002)pp638-653
4. =SURVEY 8 METHODS Architecture Qualities SAAM SAAMCS ESAAMI SAAMER ATAM SBAR ALPSM SAEM scenarios metrics
Doernhoefer00
1. Mark Doernhoefer(ed)
2. Large vs Small. More on Programming in Small Teams
3. ACM SIGSOFT Software Engineering notes V25n4(Jul 2000)pp13-18
4. =DISCUSSION ONE-SIZE PROCESS
5. What to do when you are successful small project engineer faced by a manager who expects lsrge scale processes.
6. Methods and processes for small teams.
Doernhoefer01
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Free Software
3. ACM SIGSOFT Software Engineering Notes V26n6(Nov 2001)pp19-28
4. =ADVERT OPEN SOURCE WWW/NET GNU Linux FreeBSD Apache PHP MySQL OSDN Slashdot SourceForge OpenSource.org W3C
Doernhoefer03a
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: GUI Building
3. ACM SIGSOFT Software Engineering Notes V28n3(May 2003)pp13-21 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 773126.773134 ]
4. =SURVEY GRAPHIC USER GUI
5. Dozen good WWW sites
Doernhoefer03b
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Database Design
3. ACM SIGSOFT Software Engineering Notes V28n4(Jul 2003)pp11-20 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ ??? ]
4. =SURVEY DATA DESIGN KNOWLEDGE
5. 17 good WWW sites
Doernhoefer04
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: XML
3. ACM SIGSOFT Software Engineering Notes V29n3(May 2004)pp15-24 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 986710.986718 ]
4. =SURVEY XML MARKUP LANGUAGES
5. Dozen or more good WWW sites related to the eXtensible Markup Language.
Doernhoefer05
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: service oriented architecture
3. ACM SIGSOFT Software Engineering Notes V30n6(Nov 2005)pp5-13 [ http://www.acm.org/sigsoft/SEN/ ] ACM DL subscribers: [ 1102107.1102116 ]
4. =SURVEY WEB SERVICES SOA XML Sun BEA IBM ESB .NET CBD OASIS TOGAF ADM OWASP WS-I W3C Notes.Close
5. Another excellent collection of web sites on a new topic/hype-fest.
Doernhoefer06
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Software Process Improvement
3. ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)pp5-13 [ http://www.acm.org/sigsoft/SEN/ ] [ 1108768.1108783 ]
4. =SURVEY PROCESS IMPROVEMENT CMM-I SEI SPICE PSP SWPI SEPO USNAVY SWEBOK
Doernhoefer06a
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Requirements Management
3. ACM SIGSOFT Software Engineering Notes V31n2(Mar 2006)pp17-25 [ 1118537.1118553 ]
4. =SURVEY NET REQUIREMENTS
5. 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
1. Mark Doernhoefer
2. Surfing the net for software engineering notes: The semantic Web
3. ACM SIGSOFT Software Engineering Notes V31n3(May 2006)pp8-16
4. =SURVEY SEMANTIC WEB ONTOLOGY URI OWL RDF DAML SPARQL Jena pOWL Protege SWOOP
5. 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
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Database Technology
3. ACM SIGSOFT Software Engineering notes V32n4(Jul 2007)pp10-19 [ surfing.html ]
4. =REVIEW WEB/NET DATA
Doernhoefer07a
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: User Interface Design
3. ACM SIGSOFT Software Engineering notes V32n5(Sep 2007)pp7-16 [ surfing.html ]
4. =REVIEW WEB/NET USER SIGCHI HCI MVC FOX Webby Suck
Doernhoefer08
1. Mark Doernhoefer
2. Surfing the Net for Software Engineering Notes: Requirements
3. =REVIEW WEB/NET REQUIREMENTS
4. ACM SIGSOFT Software Engineering Notes V33n3(May 2008)pp7-16 [ 1360602.1360606 ]
5. 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
1. Mark Doernhoefer
2. Surfing the net for software engineering notes: Computer People
3. ACM SIGSOFT SEN V33n4(Jul 2008)p7-16 [ 1384139.1384149 ]
4. =SURVEY WEB BIOGRAPHIES PEOPLE
5. 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
1. Mark Doernhoefer
2. Surfing the net for software engineering notes: Tool Time
3. ACM SIGSOFT SEN V34n1(Jan 2009)pp7-16 [ 1457516.1457519 ]
4. =SURVEY TOOLS Eclipse NetBeans MySQL PostGresSQL Apache Tomcat JBoss Caucho Resin ArgoUML C# .Net Subversion CVS FindBugs PMD Pentaho W3C VALIDATION LINK CHECKER
Doernhoefer09a
1. Mark Doernhoefer
2. Surfing the net for software Engineering notes -- Software and System Reliability
3. ACM SIGSOFT Software Engineering Notes V34n3(May 209)pp6-15 [ 1527202.1527204 ] (PDF)
4. =SURVEY =LINKS RELIABILITY
5. Handbook [ http://www.cse.cuhk.edu.hk/~lyu/book/reliability/ ]
6. The Reliability Information Analysis Center [ http://www.theriac.org/ ]
7. The Data and Analysis Center for Software [ https://www.thedacs.com/databases/url/key/2/ ]
8. Relex Reliability Dictionary [ ReliabilityDictionary.asp ]
9. Weibull.com [ http://www.weibull.com/ ]
10. NASA Software Assurance Technology Center [ http://satc.gsfc.nasa.gov ]
11. IEEE Reliability Society [ index.jsp?&pName=relsoc_home ]
12. City University Centre for Software Reliability [ http://www.csr.city.ac.uk ]
13. Reliability Engineering Tools [ tools.htm ]
14. ...
15. IEEE Transactions on Software Engineering(1993) [ toc.cfm?id=173802&type=issue&coll=GUIDE&dl=GUIDE&CFID=29760540&CFTOKEN=27889279 ]
16. Dependable Embedded Systems [ http://www.ece.cmu.edu/~koopman/des_s99/sw_reliability/ ]
17. ...
18. Reliability Calculators [ AvailabilityTranslator.htm ] [ reliability_calculator ]
Doernhoefer09b
1. Mark Doernhoefer
2. Surfing the net for software Engineering notes -- Empirical Software Engineering
3. ACM SIGSOFT Software Engineering Notes V34n3(Jul 2009)pp4-16 [ 1543405.1543409 ] (PDF)
4. =SURVEY =LINKS EMPIRICAL EXPERIMENTAL EXPERIENCE POLLS SURVEYS
5. LInks to Journals, Groups, Courses, Conferences all concerned with gathering data and fitting theories to software development.
Doernhoefer09c
1. Mark Doernhoefer
2. Surfing the net for software engineering notes: computer science
3. ACM SIGSOFT SEN V34n5(Sep 2009)pp8-17 [ 1598732.1598752 ]
4. =SURVEY SWEBOK SigACT ALGORITHMS CALGO NUMERICAL NIST GAMS DATA STRUCTURES THEORY HARDWARE TM OS IMBOK FUZZY LOGIC PROGRAMMING LANGUAGES
Dolado00
1. Jose Javier Dolado
2. A Validation of the Component-Based Method for Software Size Estimation
3. IEEE Trans Software Engineering V26n9(Sep 2000)pp1006-1021
4. =EXPERIMENT 46 SIMULATED BUSINESS Informix-4GL ESTIMATE LOC CBM FPs
5. component := menu | input | report_and_enquiry.
6. stats: regression, neural nets, genetic programming.
7. NOC::= number of components.
8. example: LOC = 116 + 75 *inputs + 73 *menus + 68 * reports.
9. NOC increases with LOC. NOC/LOC decreases with LOC from 0.03 to 0.005. Type of components matter.
  [VernerTate92]
Dolev00
1. Shlomi Dolev
2. Self-Stabilization
3. MIT press 2000 $40 ISBN 0-262-04178-2 CR0006-0360
4. =MONOGRAPH THEORY NONSEQUENTIAL RELIABILITY
DongYangZhang07
1. Jing Dong & Sheng Yang & Kang Zhang
2. Visualizing Design Patterns in Their Applications and Compositions
3. IEEE Trans Software Engineering V33n7(Jul 2007)pp433-453
4. =DEMO TOOL VisDP UML PROFILE PATTERNS GRAPHICS WEB SERVICE XMI J2EE java.awt
5. Need to show how one object/class plays many roles depending on the patterns.
6. Defines an UML profile to show how classes/attributes/operations take part in design patterns.
7. Demonstartes the clutter that appears with different ways of displaying this information.
8. Demonstrates a tool that will make design paterns visible as requested by the user.
DonnellanEtal05
1. Brian Donnellan & Brian Fitzgerald & Brian Lake & John Sturdy
2. Implementing an Open Source Knowledge Base
3. IEEE Software Magazine V22n5(Nov/Dec 2005)pp92-95
4. =COMPARISON TOOLS KB OPEN SOURCE COSPA MetaData DSpace LAMP Data Centric KMS Lotus Notes
5. KB::="Knowledge Base", part of an expert system, the body of knowledge available for the inference engine to use.
6. Dublin_Core::standard= See http://dublincore.org.
  (Open archives initiative Protocol for Metadata Harvesting): framework [ http://www.openarchives.org ]
7. Only works well when it evolves with the needs of the users.
Donnelly00
1. Daniel Donnelly
2. In your Face Too!
3. Rockport Pubs Inc., Gloucester MA, 2000 ISBN 156496-677-1
4. =EXAMPLES interactive interfaces CD-ROM DVD web/net kiosks user HCI
Donzelli 06
1. Paulo Donzelli
2. A Decision Support System for Software Project Management
3. IEEE Software Magazine V23n4(Jul/Aug 2006)pp67-75
4. =DEMO SIMULATION QUEUING NONSEQUENTIAL PROCESS ESTIMATION STAFFING + COCOMO REQUIREMENTS QNAP2 NASA SEL
5. Two level model: artifacts circulate around workstations, work station parameters determined by COCOMO.
6. Predicts staffing requirements -- completely ignoring Brooke's Law.
7. Changing requirements add more work later in the project and extend time to complete by about 30%
8. Comparable with staffing profile from SEL project with high instability.
9. For a survey of other process models see [AcunaJuristo05].
Doolan92
1. E P Doolan
2. Experience with Fagan's Inspection Method
3. Software - Practice & Experience V22n2(Feb 1992)pp173-182
4. =EXPERIENCE QUALITY V&V INSPECTIONS REQUIREMENTS
5. Each personel-hour of inspection saved cost of 30 personel-hours of fixing
DoppkeEtal98
1. John C Doppke & Dennis Heimbigner & Alexander L Wolf
2. Software Process Modeling and execution within Virtual Environments
3. ACM ToSEM V7n1(Jan 1998)pp1-40
4. =DEMO PROCESS can be described game(MUD/MOO) using lambdaMOO
Dorfman99
1. Merlin Dorfman
2. Commercial vs Aerospace Worlds: comparing software engineering cultures
3. IEEE Software Magazine V16n6(Nov/Dec 1999)pp97-100
4. =ESSAY EXPERIENCE
5. one size does not fit all
6. comercial: - smaller projects +Time to market -new methods - new tools - funding + hope - time accounting - costing - estimating
Dori08
1. Dov Dori
2. Words from Pictures for Dual-Channel Processing
3. =DEMO TOOL GRAPHIC NATURAL LANGUAGE SYSTEM DESIGN MODELLING OPM OPD OPL OPCAT FSM
4. Commun ACM V51n5(May 2008)#7pp47-52
5. Claims that automatically linking diagrams to text makes process more intuitive. [MillerJ02]
Doublait97
1. Stephane Doublait
2. Standard Reuse Practices: Many Myths vs a Reality
3. ACM StandView V5n5(Sep 1997)pp84-91
4. =EXPERIENCES at Sodalia(ISO9001& CMM=2)
Douglass99
1. Bruce Powel Douglass
2. Components: Logical, Physical Models
3. Software Development Magazine V7n12(Dec 1999)pp52-54
4. =ADVERT OBJECT-ORIENTED METHOD UML ROPES COMPONENTS
5. Components are runtime plugin Binaries not objects .Note UML components include data files, web pages, source code, etc etc.
Douglass99b
1. Bruce Powel Douglass
2. Doing Hard Time: developing real-time systems with UML, Objects frameworks, and patterns
3. Addison Wesley, Longman 1999 ISBN 0-201-49837-5 QA46.6 D655 1999 includes CDROM
4. =TEXTBOOK ADVERT UML Rhapsody TMING NONSEQUENTIAL ROPES Object-Oriented
5. special stereotypes pp48-52
6. 5 safety patterns pp116-124
7. Mechanistic design
8. 12 state-behavioral-patterns, table pp 590-591.
9. Many patterns recur in different parts.
10. RMA:: theory = Rate Monotonic Algorithm, requires sum [i : 1..n](worst [i ] / period [i ] ) < n*( 2**(1/ n )-1).
11. 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
1. Bruce Powell Douglass
2. Real Time UML (3rd edn): Advances in the UML for Real-Time Systems
3. Pearson Education Boston MA 2004 ISBN 0-321-16076-2 (Addison-Wesley Object Technology Series)
4. =TEXT QUALITIES PURPOSE PERFORMANCE TIMING RELIABILITY UML ROPES PATTERNS
5. No mention of OCL and some diagrams have non-standard UML notations.
6. Introduction to and examples of PTS profile and RT-UML [OMG020302].
7. ROPES::="Rapid Object-Oriented Process for Embedded Systems".
8. Quotes (misquotes?) the Rate Monotone Analysis bound.
9. Older and subtly different [Douglass99b].
DowdyFoster82
1. Comparative Models of the File Assignment Problem
2. ACM Comp Surveys V14 n2 (Jun 1982) pp287-313 see also V15 n1 pp87-89
3. data optimization Technical
DownsA00
1. Andrew Downs
2. From Engineer to Technical Lead
3. Software Development Magazine V8n4(Apr 2000)pp72-74
4. =EXPERIENCE PEOPLE code reviews
DownsClareCoe8792
1. Ed Downs & Peter Clare & Ian Coe
2. Structured Systems Analysis and Design Method
3. Prentice Hall International (UK) Herts UK 1988(1st edn) & 1992(2nd Edn) CR9305-0292
4. =TEXT SSADM management COMPACT
5. COMPACT for Office systems
6. 2nd Edn has Combined viewpoint diagrams(CCTA 1990) : two parts control+Process
Dowson86
1. M Dowson(ed)
2. Iteration in the Software Process
3. Proc of the 3rd Int Software Process Workshop (Nov 1986)
4. =PROCEEDINGS non-sequential lifecycle PROCESS ITERATION AGILE
Drake96
1. Thomas Drake
2. Measuring Software Quality: A Case Study
3. IEEE Computer Magazine V29n11(Nov 1996)pp78-87
4. NSA SEATC(Software Engineering Applied Technology Center)
5. =EXPERIENCE TECHNICAL QUALITY
6. 25MLoC benefits Kiviat Diagrams profile many Qualities of code
Dribin96
1. Lawrence S Driben
2. Defining Design Terminology(letter)
3. IEEE Software Magazine V13N3(May 1996)p8
4. external design vs internal design: which is the true architecture?
DrobkaNoftzRaghu04
1. Jerry Drobka & David Noftz & Rekha Raghu
2. Piloting XP on four mission-critical projects
3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp70-75
4. =EXPERIENCE XP AGILE 4 Motorola Projects
5. 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)
6. High morale and confidence, training easier.
7. Challenges: fitting with non-XP projects and managers. Need thorough training and coaching.
8. Did an initial "blitz" software architecture rather like Unified Process.
Dromey88
1. RG Dromey
2. Systematic Program Development
3. IEEE Trans Soft Eng SE-V14n1(Jan 1988)pp12-29
4. formal
Dromey90
1. Geof Dromey
2. Program derivation: the development of programs from specifications
3. Addison-Wesley Reading MA 1990 TEXT FORMAL METHOD
DromeyChorvat90
1. RG Dromey & TA Chorvat
2. Structure clashes -- an alternative to program inversion
3. Comput J V33n2(Apr 1990)pp126-132
4. JSP
Drucker85
1. Peter Drucker
2. Innovation and Entrepreneurship
3. Harper Business 1993, Harper Perennial 1985
4. =EXPERIENCES INNOVATIONS ENGINEERING BUSINESS ANALYSIS
5. 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
1. J Du J & S Jing & J Liu
2. Creating shared design thinking process for collaborative design
3. Journal of Network and Computer Applications V35n1(2012)pp111-120
4. =DEMO ENGINEERING RATIONALE TOOL TEAMTHINK S-DTPM cf COMPENDIUM IBIS TOULMIN
5. Ideas about designs are issues, options, solutions, rules, criteria, and annotations.
6. There are operations for sharing perspectives: Argument, evolution, association, fusion.
7. Very weak evidence: one demo/case-study with 2 people.
DubocRosenblumLetier10
1. Leticia Duboc & David S Rosenblum & Emmanuel Letier
2. Death, Taxes, & Scalability
3. IEEE Software Magazine V27n4(Jul/Aug 2010)pp20-21
4. =ADVERT REQUIREMENTS KAOS QUALITY REALITY SCALABILITY LAS HMRC
5. Scalability is not just about performance but impacts other qualities and even functionality.
6. Scalability is not defined well in most projects. Examples: LAS (London Ambulance System) & HMRC (UK Revenue and Customs).
7. 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.
8. Scalability is always relative to the reality and the system surrounding the software. These must be defined as assumptions. They must then be challenged.
9. Analyzing how a system will fail to scale leads to better systems -- for example adding emergency procedures and back up processing power.
DucasseLanza05
1. Stephane Ducasse & Michele Lanza
2. The Class Blueprint: visually supporting the understanding of classes
3. IEEE Trans Software Engineering V31n1(Jan 2005)pp79-90
4. =EXPERIMENTAL GRAPHIC Object-Oriented code metrics structure smalltalk
5. Classifies attributes and methods into layers: initialization, interface, internal implementation, accessors, attributes.
6. Attributes and methods shown as boxes. Metrics mapped to height and width. Type to color.
7. Caller-callee link goes from bottom of caller box to top of called.
8. Tested on real code. and by a dozen students (all found it helpful).
DueckCormack90
1. G D P Dueck & G V Cormack
2. Modular Attribute Grammars
3. Computer Jnl V33n2(Feb 1992)pp164-173
DuenasEtAl07
1. Juan C Duenas & Hugo A Prada G & Felix Cuado & Manuel Santillan & Jose L Ruiz
2. Apache and Eclipse: Comparing open source project incubators
3. IEEE Software Magazine V24n6(Nov/Dec 2007)pp90-98
4. =EMPIRICAL COMPARISON 2 F/OSS PROCESSES PROJECT INITIATION LIFE CYCLE ANALYSIS
5. Incubation is the process of developing and defining new project/subprojects to be further developed and integrated into a the current (evolving) system.
6. Apache and Eclipse have well defined processes and share many features (Table 1 page 97)
DugganByrneLyons04
1. Jim Duggan & Jason Byrne & Gerard J Lyons
2. A task allocation optimizer for Software Construction
3. IEEE Software Magazine V21n3(May/Jun 2004)pp76-82
4. =DEMO PEOPLE PROCESS PLAN ALGORITHM MOEA
5. Allocating people to tasks has many objectives: time & defects.
6. Multiobjective optimizer computes Pareto-optimal set using elitist genetic algorithm.
7. Human picks one.
8. dominates::@(solution, solution), x dominates y iff for all f:objectives(f(x)better_than f(y).
9. Pareto_optimal_set::@(solution)= {x. for no y(y dominates x)}.
DumasParsons95
1. Joseph Dumas & Paige Parsons
2. Discovering the Way Programmers Think about New Programming Environments
3. Commun ACM V38n6(Jun 1995)pp45-56
4. Dylan USER PROTOTYPE
5. 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.
  DybaSharp12
  1. Tore Dyba & Helen Sharp
  2. What's the evidence for Lean
  3. IEEE Software Magazine V29n5(Sep/Oct 2012)pp19-21 [ software ]
  4. =SURVEY EVIDENCE LEAN MANUFACTURING TOYOTA IMVP OVERTIME
  5. Evidence for Lean Manufacturing has been challenged -- it ignored overtime...
  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.
  EastawayWyndham98
  1. Rob Eastaway & Jeremy Wyndham
  2. Why do busses come in threes: the hidden mathematics of everyday life
  3. Wiley 1998 + Barnes & Noble 2002
  4. =FUN MATHEMATICS BOOK
  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
  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 [Fagan99] (23 years later).
  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] (23 years earlier).
  6. A precisely defined and proven method of examining code to find out the defects within it.
  Fairbairn87
  1. ?? Fairbairn
  2. Making Form follow Function: An Experiment in Functional Programming Style
  3. Software - Practice and Experience V17n6(Jun 1987)pp379-386
  4. =EXAMPLE 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 REQUIREME

Usage	% of time
Required	83%
Sketch	78%
Blueprint	76%
Language	38%