Abram's BiBTeX Blog

Stoyan:acm:lfp:1984 Herbert Stoyan Early {LISP} History (1956--1959)
ID	Stoyan:acm:lfp:1984
Type	InProceedings
Author(s)	Herbert Stoyan
Title	Early {LISP} History (1956--1959)
Abstract	This paper describes the development of LISP from McCarthy's first research in the topic of programming languages for AI until the stage when the LISP1 implementation had developed into a serious program (May 1959). We show the steps that led to LISP and the various proposals for LISP interpreters (between November 1958 and May 1959). The paper contains some correcting details to our book~\cite{Stoyan:1980}.
source	dept. library
keywords	LISP history
refs	35
publisher	ACM month = aug,
Annotation	This was an interesting historical paper. It peaked into the development of the LISP language, the design decisions and what was happening at the time in the late 50s when McCarthy was working on LISP. It turns out that the rationale for running lisp in a interpretter that was itself really had to do with McCarthy making a function which could run LISP, this was to allow the 'apply' and 'eval' functions to evaluate and execute lisp code; the rationale was that if LISP could do that it was obviously turing complete since a turing machine could run a program which simulated itself. Also an undergrad did make a turing machine simulator in LISP. What I found interesting is what was and wasn't discovered at the time. It seems an if block with short circuit evaluation and conditional execution of either the positive or negative (else) blocks simply wasn't around. Supposedly McCarthy invented this. I was unaware how primitive FORTRAN was at the time. It was interesting that McCarthy added some List functionality to fortran. It was rather technical and there were some typing mistakes. Overall an enjoyable paper.
organization	ACM
note	Invited talk.
booktitle	Conference Record of the 1984 {ACM} Symposium on Lisp and Functional Programming
checked	19940322
year	1984
pages	299--310

Goetz:2002:MSPa Martin Goetz Memoirs of a Software Pioneer: Part {I}
ID	Goetz:2002:MSPa
Type	Article
Author(s)	Martin Goetz
Title	Memoirs of a Software Pioneer: Part {I}
URL	http://computer.org/annals/an2002/a1043abs.htm; http://dlib.computer.org/an/books/an2002/pdf/a1043.pdf
	acknowledgement = ack-nhfb,
ISSN	1058-6180
CODEN	IAHCEX
number	1
volume	24
Annotation	In Memoirs of software pioneer by M. Goetz, we learn initally software patents were used by the small companies to fight off the larger companies (IBM). Currently it seems muddled with corporations assuming more and more power and simply forming agreements they wont sue each other. I can't say I agree with Goetz's purpose in trying to get software patents recognized, it seems to me more like a company trying to compete using the legal system instead of a good product. Of course the problems at the time were related to IBM bundling software with their machinery and giving it away. Which in late 60s and 70s seemed like a really bad for business but now the world has changed. I remember Richard Stallman talking about how initally all the software was free and you traded it around, then suddenly corporations started coming in a trying to own everything and then suddenly software wasn't free. Goetz covers that time when IBM unbundled their software Interesting tid bits were how Goetz invented a kind of multiple tape merge sort where you had limited memory, sorted each tape and merged the tapes. Also covered is the first software patent (which he owns by the way). This was a historical paper that dealt with the inital software industry and it's first large hurdle the "IBM Monopoly". We now have a different monopoly doing similar things but in a less open manner.
bibdate	Fri Feb 22 12:42:03 MST 2002
year	2002
journal	IEEE Annals of the History of Computing
pages	43--56 month = jan # "--" # mar,

Hall01 Ethical Issues in Software Engineering Research: A Survey of Current Practice Ethical Issues in Software Engineering Research: A Survey Of Current Practice
ID	Hall01
Type	Article
Author(s)	Ethical Issues in Software Engineering Research: A Survey of Current Practice
Title	Ethical Issues in Software Engineering Research: A Survey Of Current Practice
country	Netherlands
number	6
email	t.hall@herts.ac.uk and fynv@sbu.ac.uk
publisher	Kluwer Academic Publishers
Annotation	A study of the opinions of academics in the UK regarding software engineering research and ethics. Areas such as ethics councils, funding and data protection legislation are discussed.
journal	Empirical Software Engineering

Lethbridge01 Timothy C. LethbridgeJoan E. SieberJoan E. Sieber Mixing Software Engineering Resarch and Development -- What Needs Ethical Review and What Does Not?Protecting Research Subjects, Employees and Researchers: Implications for Software EngineeringNot Your Ordinary Research
ID	Lethbridge01
Type	Article
Author(s)	Timothy C. LethbridgeJoan E. SieberJoan E. Sieber
Title	Mixing Software Engineering Resarch and Development -- What Needs Ethical Review and What Does Not?Protecting Research Subjects, Employees and Researchers: Implications for Software EngineeringNot Your Ordinary Research
	@Article{Sieber01.1, @Article{Sieber01.2,
country	NetherlandsNetherlandsNetherlands
number	666
email	tcl@site.utottawa.cajsieber@csuhayward.edujsieber@csuhayward.edu
publisher	Kluwer Academic PublishersKluwer Academic PublishersKluwer Academic Publishers
Annotation	Suggests not all software engineering endevors such as those with real employees, etc. Warns against problems of using Students and Employees as subjects. Suggest avoiding situation where persons in authority can force people to volunteer. Covers basic kinds of risks, the classes of risks that software engineering research faces. Suggests not giving out more information about employees than is necessary for one could damage their career. Also covers areas such as IP and legal risks.A suggestion that data shouldn't be used administratively without consent of the givers. Paper gives instructions for elicting consent. Paper describes the ethical considerations involved in a academia / industry / research joint venture. Discusses IP, disgruntled employees, treatment of industry employees, confidentiality and sharing of IP.
journal	Empirical Software EngineeringEmpirical Software EngineeringEmpirical Software Engineering

Davis01 Michael Davis When is a Volunteer Not a Volunteer
ID	Davis01
Type	Article
Author(s)	Michael Davis
Title	When is a Volunteer Not a Volunteer
country	Netherlands
number	6
email	davism@iit.edu
publisher	Kluwer Academic Publishers
Annotation	Criticizes \cite{storey01} for suggesting that students volunteered. Pointed out that the large percentage of the students participated because they were virtually forced to. They weren't given a fair choice. A good analogy was "Your Money or your life".
journal	Empirical Software Engineering

Storey01 M. A. D. Storey and B. Phillips and M. Maczewski Is it Ethical to Evaluate Web-based Learning Tools using Students?
ID	Storey01
Type	Article
Author(s)	M. A. D. Storey and B. Phillips and M. Maczewski
Title	Is it Ethical to Evaluate Web-based Learning Tools using Students?
country	Netherlands
number	6
email	mstorey@uvic.ca
publisher	Kluwer Academic Publishers
Annotation	Paper discusses using students from an HCI class to research the usability of 2 web based learning tools, blackboard and web ct. Discussion of whether or not students were coercsed. Students withdrew from the study and hampered the marking for the class. There were issues of withdrawl, incentive and authority.
journal	Empirical Software Engineering

Gotterbarn01 Donald Gotterbarn Ethics in Qualitative Studies Of Commercial Software Enterprises Ethical Analysis
ID	Gotterbarn01
Type	Article
Author(s)	Donald Gotterbarn
Title	Ethics in Qualitative Studies Of Commercial Software Enterprises Ethical Analysis
country	Netherlands
number	6
email	gotterba@access.etsu.edu
publisher	Kluwer Academic Publishers
Annotation	Criticized \cite{seaman01} for saying anything about a 3rd party to the research subjects. Suggests that you have to treat the research subjects as subjects and be very careful not to say things to them that can alter your research. It was suggested that the entire study was compromised due to this situation of name dropping the other company.
journal	Empirical Software Engineering

BeckerKornstaedt01 Ulrike Becker-KornstaedtJanice Singer and Norman VinsonJanice Singer and Norman Vinson Descriptive Software Process Modeling - How to Deal with Sensitive Process InformationWhy and How Research Ethics Matters to You. Yes, You!} Getting to the Source of Ethical Issues
ID	BeckerKornstaedt01
Type	Article
Author(s)	Ulrike Becker-KornstaedtJanice Singer and Norman VinsonJanice Singer and Norman Vinson
Title	Descriptive Software Process Modeling - How to Deal with Sensitive Process InformationWhy and How Research Ethics Matters to You. Yes, You!} Getting to the Source of Ethical Issues
	@Article{SingerVinson01.2, @Article{SingerVinson01.3,
country	NetherlandsNetherlandsNetherlands
number	666
email	ulrike.becker-kornstaedt@iese.fhg.de{janice.singer,norm.vinson}@nrc.ca{janice.singer,norm.vinson}@nrc.ca
publisher	Kluwer Academic PublishersKluwer Academic PublishersKluwer Academic Publishers
Annotation	Discusses ways one can safely deal with sensitive information as not to harm employees. The author describes dangers, risks and steps taken to alleviate the risks to employees. Concerns arose over the easy identifiabilty of employees even when information was anonymized. An interesting concern arose when an employee admitted they didnt follow a process and then when the manager questioned the employee they denied that this actually happened. Essentially this was extracting process information from a company. The best point of this paper is it's discription how to cause minimal harm to participants. Discusses why software engineers should care about research ethics. Discusses funding and other organization. Discusses government agencies involved in the ethics regarding the research that involved humans and introduces the other papers in the volume. Metrics is not like art criticism. There is no real need to identify the projects used to gain these metrics. Metrics is about tools for analysis, not analysis of the actual projects therefore risk can be minimized through anonymization. Valuable for OSS ethics.
journal	Empirical Software EngineeringEmpirical Software EngineeringEmpirical Software Engineering

ElEmam01 Khaled El-Emam Ethics and Open Source
ID	ElEmam01
Type	Article
Author(s)	Khaled El-Emam
Title	Ethics and Open Source
country	Netherlands
number	6
email	khaled.el-emam@nrc.ca
publisher	Kluwer Academic Publishers
Annotation	Suggests scenarios about how source code was written and how authors often don't expect to be criticized or have metreics used on them. Examples of code intent are commercial software that is opensource. Paper asks questions, doesn't attempt to answer any.
journal	Empirical Software Engineering

seaman01 Carolyn B. Seaman Ethics in Qualitative Studies Of Commercial Software Enterprises: Case Description
ID	seaman01
Type	Article
Author(s)	Carolyn B. Seaman
Title	Ethics in Qualitative Studies Of Commercial Software Enterprises: Case Description
country	Netherlands
number	6
email	cseaman@umbc.edu
publisher	Kluwer Academic Publishers
Annotation	A problem is suggested where an author is studying commercial software development and the subjects ask questions about other research. Should the researcher mention other companies or not. Basically how name dropping damaged the author's research.
journal	Empirical Software Engineering