Robert L. Glass

According to our database1, Robert L. Glass authored at least 290 papers between 1969 and 2020.

Collaborative distances:

Awards

ACM Fellow

ACM Fellow 1999, "For distinguished contributions to practical software engineering through writing and speaking in language and action bridging the interests of academia and industry.".

Timeline

Legend:

Book 
In proceedings 
Article 
PhD thesis 
Dataset
Other 

Links

Online presence:

On csauthors.net:

Bibliography

2020
In Praise of Software Practice.
ACM SIGSOFT Softw. Eng. Notes, 2020

2019
Don't ignore the cost of 'embedded energy'.
Commun. ACM, 2019

2018
Errors in Computing History.
ACM SIGSOFT Softw. Eng. Notes, 2018

2014
Goodbye.
Inf. Syst. Manag., 2014

Whatever Happened to Young What's His Name?
Inf. Syst. Manag., 2014

2013
Tinkerings I Have Done.
Inf. Syst. Manag., 2013

Who Pays for IT Publications? The Reader (that's the tradition) or the Author (that's what's new).
Inf. Syst. Manag., 2013

Give Me An Act of God, Please.
Inf. Syst. Manag., 2013

The Queensland Health Payroll Debacle.
Inf. Syst. Manag., 2013

2012
The Gender Gap: Is It a Computing Problem or Simply a Computer Science Problem?
IEEE Softw., 2012

Managing projects in trouble: achieving turnaround and success by Ralph L. Kliem.
ACM SIGSOFT Softw. Eng. Notes, 2012

A Study About Software Maintenance.
Inf. Syst. Manag., 2012

What Is IS?
Inf. Syst. Manag., 2012

All About Julian Assange.
Inf. Syst. Manag., 2012

The Gender Gap: Does It Include Information Systems?
Inf. Syst. Manag., 2012

2011
Naïveté Squared: In Search of Two Taxonomies and a Mapping between Them.
IEEE Softw., 2011

An assessment of systems and software engineering scholars and institutions (2003-2007 and 2004-2008).
J. Syst. Softw., 2011

Software - The Technology that "Don't Get No Respect".
Inf. Syst. Manag., 2011

On the Aging of Software.
Inf. Syst. Manag., 2011

Déjà Vu All Over Again: Is Software Engineering REALLY an Idea Whose Time Has Come and Gone?
Inf. Syst. Manag., 2011

2010
Test-First Approaches: Are They Harmful?
Inf. Syst. Manag., 2010

A Quibble About "Computation".
Inf. Syst. Manag., 2010

A Current-Day Problem and a Future-Day Disaster-in-the-Making.
Inf. Syst. Manag., 2010

Three Obscure Things in Our Field that I Actually SUPPORT!!
Inf. Syst. Manag., 2010

2009
Doubt and Software Standards.
IEEE Softw., 2009

Making Research More Relevant While Not Diminishing Its Rigor.
IEEE Softw., 2009

A Classification System for Testing, Part 2.
IEEE Softw., 2009

An assessment of systems and software engineering scholars and institutions (2002-2006).
J. Syst. Softw., 2009

Divided by a Common Language, Version 2.
Inf. Syst. Manag., 2009

Google Emissions Study Borders on the Absurd.
Inf. Syst. Manag., 2009

Frivolous Research.
Inf. Syst. Manag., 2009

Creativity vs. the Law.
Inf. Syst. Manag., 2009

RESRES: The story behind the paper "Research in software engineering: An analysis of the literature".
Inf. Softw. Technol., 2009

The impact of subversive stakeholders on software projects.
Commun. ACM, 2009

2008
Lying on Software Projects.
IEEE Softw., 2008

Negative Productivity and What to Do about It.
IEEE Softw., 2008

Two Mistakes and Error-Free Software: A Confession.
IEEE Softw., 2008

Software: Hero or Zero?
IEEE Softw., 2008

On the Impurity of the English Language.
IEEE Softw., 2008

Intuition's Role in Decision Making.
IEEE Softw., 2008

An assessment of systems and software engineering scholars and institutions (2001-2005).
J. Syst. Softw., 2008

Experience May Not be the Best Teacher After All.
Inf. Syst. Manag., 2008

The Notion of an Information System Apgar Score.
Inf. Syst. Manag., 2008

Divided by a Common Language: The Story of Requirements Triage.
Inf. Syst. Manag., 2008

The EU - Pouring Trouble on Oiled Waters.
Inf. Syst. Manag., 2008

Software design and the monkey's brain.
Commun. ACM, 2008

Managing for innovation.
Commun. ACM, 2008

2007
What's with This Blog Thing?
IEEE Softw., 2007

Is Software Engineering Fun? Part 2.
IEEE Softw., 2007

Is Software Engineering Fun?
IEEE Softw., 2007

Through a Glass, Darkly : IS: Doom and Gloom Forecasts?
Inf. Syst. Manag., 2007

Through a Glass, Darkly : .
Inf. Syst. Manag., 2007

A research project with important practitioner-oriented findings.
Commun. ACM, 2007

A deja-vu look at software engineering researchers who care about practice.
Commun. ACM, 2007

One man's quest for the state of software engineering's practice.
Commun. ACM, 2007

2006
Software Testing and Industry Needs.
IEEE Softw., 2006

Greece vs. Rome: Two Very Different Software Cultures.
IEEE Softw., 2006

How Much of the Software Engineering Old Still Remains New?
IEEE Softw., 2006

Of Health, Trust, Money ... and Integrity.
IEEE Softw., 2006

Review of "COBOL Programmers Swing With Java by E. Reed Doke, Bill C. Hardgrave and Richard A. Johnson", Cambridge University Press, 2005.
ACM SIGSOFT Softw. Eng. Notes, 2006

An assessment of systems and software engineering scholars and institutions (2000-2004).
J. Syst. Softw., 2006

Looking into the challenges of complex IT projects.
Commun. ACM, 2006

The Standish report: does it really describe a software crisis?
Commun. ACM, 2006

Is the crouching tiger a threat?
Commun. ACM, 2006

2005
A Follow-the-Leader Story with a Strange Ending.
IEEE Softw., 2005

Never the CS and IS Twain Shall Meet?
IEEE Softw., 2005

A Sad SAC Story about the State of the Practice.
IEEE Softw., 2005

IT Failure Rates--70% or 10-15%?
IEEE Softw., 2005

Viruses Are Beginning to Get to Me!
IEEE Softw., 2005

An assessment of systems and software engineering scholars and institutions (1999-2003).
J. Syst. Softw., 2005

A unified classification system for research in the computing disciplines.
Inf. Softw. Technol., 2005

The plot to deskill software engineering.
Commun. ACM, 2005

"Silver bullet" milestones in software history.
Commun. ACM, 2005

The first business application: a significant milestone in software history.
Commun. ACM, 2005

2004
Anarchy and the Effects of Schedule Pressure.
IEEE Softw., 2004

Some Heresy Regarding Software Engineering.
IEEE Softw., 2004

Learning to Distinguish a Solution from a Problem.
IEEE Softw., 2004

On Modeling and Discomfort.
IEEE Softw., 2004

Sources for Software Development: A Mugwumpish View.
IEEE Softw., 2004

Research in computer science: an empirical study.
J. Syst. Softw., 2004

An analysis of research in computing disciplines.
Commun. ACM, 2004

Is this a revolutionary idea, or not?
Commun. ACM, 2004

The mystery of formal methods disuse.
Commun. ACM, 2004

Matching methodology to problem domain.
Commun. ACM, 2004

A look at the economics of open source.
Commun. ACM, 2004

2003
Guest Editor's Introduction: The State of the Practice of Software Engineering.
IEEE Softw., 2003

A Big Problem in Academic Software Engineering and a Potential Outside-the-Box Solution.
IEEE Softw., 2003

Questioning the Software Engineering Unquestionables.
IEEE Softw., 2003

Error-Free Software Remains Extremely Elusive.
IEEE Softw., 2003

An assessment of systems and software engineering scholars and institutions (1998-2002).
J. Syst. Softw., 2003

A sociopolitical look at open source.
Commun. ACM, 2003

A mugwump's-eye view of Web work.
Commun. ACM, 2003

One giant step backward.
Commun. ACM, 2003

2002
Predicting Future Maintenance Cost, and How We're Doing It Wrong.
IEEE Softw., 2002

Project Retrospectives, and Why They Never Happen.
IEEE Softw., 2002

In Search of Meaning (A Tale of Two Words).
IEEE Softw., 2002

The Naturalness of Object Orientation: Beating a Dead Horse?
IEEE Softw., 2002

Failure Is Looking More like Success These Days.
IEEE Softw., 2002

An assessment of systems and software engineering scholars and institutions (1997-2001).
J. Syst. Softw., 2002

A Final Good-bye.
J. Syst. Softw., 2002

Research in Information Systems: An Empirical Study of Diversity in the Discipline and Its Journals.
J. Manag. Inf. Syst., 2002

Research in software engineering: an analysis of the literature.
Inf. Softw. Technol., 2002

How to handle real project risks, while filing gaps in the risk theory literature.
Data Base, 2002

Sorting out software complexity.
Commun. ACM, 2002

The proof of correctness wars.
Commun. ACM, 2002

Searching for the holy grail of software engineering.
Commun. ACM, 2002

Stodgy by design, and the notion of 'dumbing up'.
Commun. ACM, 2002

2001
Extreme Programming: The Good, the Bad, and the Bottom Line.
IEEE Softw., 2001

A Story about the Creativity Involved in Software Work.
IEEE Softw., 2001

Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering.
IEEE Softw., 2001

An assessment of Systems and Software Engineering scholars and institutions (1996-2000).
J. Syst. Softw., 2001

Little Red Riding Hood meets critical social theory.
Data Base, 2001

What can we learn from the dot-com debacle?
Data Base, 2001

Rigor vs. Relevance: A Practitioner's Eye View of an Explosion of IS Opinions.
Commun. Assoc. Inf. Syst., 2001

Of Model Changeovers, Style, and Fatware.
Commun. ACM, 2001

Practical programmer: academics, and the scarlet letter "A".
Commun. ACM, 2001

An embarrassing, yet rewarding, ending to a previous column.
Commun. ACM, 2001

2000
Loyal Opposition - Y2K and Other Software Noncrises.
IEEE Softw., 2000

Loyal Opposition - The Sociology of Open Source: Of Cults and Cultures.
IEEE Softw., 2000

Loyal Opposition - Process Diversity and a Computing Old Wives'/Husbands' Tale.
IEEE Softw., 2000

Loyal Opposition - New Answer to "How Important Is Mathematics to the Software Practitioner?".
IEEE Softw., 2000

Loyal Opposition - The Generalization of an Application Domain.
IEEE Softw., 2000

Corrigendum to: An assessment of systems and software engineering scholars and institutions (1994-1998) [The Journal of Systems and Software 49 (1) (1999) 81-86].
J. Syst. Softw., 2000

Y2K, and believing in software practice.
J. Syst. Softw., 2000

Discussion.
J. Syst. Softw., 2000

Software maintenance, Y2K and other software non-crises.
J. Syst. Softw., 2000

An assessment of systems and software engineering scholars and institutions (1995-1999).
J. Syst. Softw., 2000

A letter from the frustrated author of a journal paper.
J. Syst. Softw., 2000

The End of the "Outsourcing Era".
J. Syst. Softw., 2000

On design.
J. Syst. Softw., 2000

Academics, and the scarlet letter 'A'.
J. Syst. Softw., 2000

Software requirements success predictors - behavioral factors beat technical ones.
J. Syst. Softw., 2000

The "software-first" revolution in computer hardware design.
J. Syst. Softw., 2000

The "maintenance-first" software era.
J. Syst. Softw., 2000

Y2K behind us: smooth sailing and blue skies?
J. Syst. Softw., 2000

A good-bye of sorts.
J. Syst. Softw., 2000

Talk About a Software Crisis - Not!
J. Syst. Softw., 2000

A delicate issue: what to do when the state of the practice leads the state of the art.
Data Base, 2000

On personal technical obsolescence.
Commun. ACM, 2000

1999
Cobol: A Historic Past, A Vital Future?
IEEE Softw., 1999

Loyal Opposition - A Snapshot of Systems Development Practice.
IEEE Softw., 1999

Loyal Opposition - On Design.
IEEE Softw., 1999

Loyal Opposition - Of Open Source, Linux...and Hype.
IEEE Softw., 1999

Examining the effects of the "Application Revolution".
J. Syst. Softw., 1999

Of counting schemes and end-of-century partying.
J. Syst. Softw., 1999

An assessment of systems and software engineering scholars and institutions (1994-1998).
J. Syst. Softw., 1999

COBOL: Is It Dying - or Thriving?
Data Base, 1999

Evolving a New Theory of Project Success.
Commun. ACM, 1999

Buzzwordism and the Epic $150 Million Software Debacle.
Commun. ACM, 1999

Is Criticism of Computing Academe Inevitably Divisive?
Commun. ACM, 1999

Inspections - Some Surprising Findings.
Commun. ACM, 1999

The Realities of Software Payoffs.
Commun. ACM, 1999

1998
Maintenance: Less Is Not More.
IEEE Softw., 1998

Defining Quality Intuitively.
IEEE Softw., 1998

Reuse: What's Wrong with This Picture?
IEEE Softw., 1998

Loyal Opposition: Is There Really a Software Crisis?
IEEE Softw., 1998

In Praise of Practice.
IEEE Softw., 1998

Editor's corner: How long do information systems last?
J. Syst. Softw., 1998

Editor's corner yet another date crisis -- Y2k is only the beginning.
J. Syst. Softw., 1998

Editor's Corner: Software runaways - Some surprising findings.
J. Syst. Softw., 1998

An assessment of systems and software engineering scholars and institutions (1993-1997).
J. Syst. Softw., 1998

Issue Management.
Data Base, 1998

Controlling Software Diseases.
Data Base, 1998

Enterprise Resource Planning - Breakthrough and/or Term Problem?
Data Base, 1998

A Tongue-in-Cheek Look at Fun and/or Games.
Data Base, 1998

Success? Failure? Or Both?
Computer, 1998

Strong Vs. Weak Approaches to Systems Development.
Commun. ACM, 1998

How Not To Prepare for a Consulting Assignment, and Other Ugly Consultancy Truths.
Commun. ACM, 1998

Short-Term and Long-term Remedies for Runaway Projects.
Commun. ACM, 1998

Everything Old Is New Again.
Commun. ACM, 1998

Focusing on the Application Domain: Everyone Agrees It's Vital, but Who's Doing Anything about It?
Proceedings of the Thirty-First Annual Hawaii International Conference on System Sciences, 1998

1997
Soapbox: Telling Good Numbers from Bad Ones.
IEEE Softw., 1997

Editor's corner some brainstorming thoughts about the date crisis problem.
J. Syst. Softw., 1997

Editor's corner computer science Ph.D. production - more institutions, fewer degrees, more students (!).
J. Syst. Softw., 1997

An assessment of systems and software engineering scholars and institutions (1993-1996).
J. Syst. Softw., 1997

Editor's corner Top scholars and institutions study reaching maturity: A lesson re-learned.
J. Syst. Softw., 1997

Editor's corner Is there anything "time-honored" in the field of software?
J. Syst. Softw., 1997

Editor's corner "good enough" software - A unique American advantage.
J. Syst. Softw., 1997

Software Reflections - A Pioneer's View of the History of the Field.
J. Syst. Softw., 1997

Pilot Studies: What, Why, and How.
J. Syst. Softw., 1997

Editor's Corner - Client/Server: Boom or Bust?
J. Syst. Softw., 1997

Systems Development: a dying Discipline?
Inf. Syst. Manag., 1997

Software Runaways - Some Surprising Findings.
Data Base, 1997

A Word of Warning About Reuse.
Data Base, 1997

How Best to Provide the Services IS Programmers Need.
Commun. ACM, 1997

Cobol - A Contradiction and an Enigma.
Commun. ACM, 1997

Revisiting the Industry/Academe Communication Chasm.
Commun. ACM, 1997

The Ups and Downs of Programmer Stress.
Commun. ACM, 1997

The Next Date Crisis and the Ones After That.
Commun. ACM, 1997

In the beginning - personal recollections of software pioneers.
IEEE, ISBN: 978-0-8186-7999-5, 1997

1996
Study supports existence of software crisis; Management issues appear to be prime cause.
J. Syst. Softw., 1996

Editor's corner mathematics and the computer scientist.
J. Syst. Softw., 1996

Editor's corner computer support for creativity.
J. Syst. Softw., 1996

Editor's corner About software engineering hype.
J. Syst. Softw., 1996

Editor's corner object-orientation claims: Naturalness, seamlessness seem doubtful.
J. Syst. Softw., 1996

The Non-Goal-Oriented Committee Meeting.
J. Syst. Softw., 1996

An Assessment of Systems and Software Engineering Scholars and Institutions (1993-1995).
J. Syst. Softw., 1996

The Strange Case of the Proofreader's Pencil.
J. Syst. Softw., 1996

Who Cares? Technologies in Practice.
Data Base, 1996

Is There Anything "Time-Honored" in the Field of Software?
Data Base, 1996

Some Thoughts on Automatic Code Generation.
Data Base, 1996

Methodologies: Bend to Fit?
Data Base, 1996

An Invitation to Formal Methods.
Computer, 1996

The Relationship Between Theory and Practice in Software Engineering.
Commun. ACM, 1996

1995
Contemporary Application-Domain Taxonomies.
IEEE Softw., 1995

Editor's corner a theory about software's practice.
J. Syst. Softw., 1995

Editor's corner a close escape from greatness.
J. Syst. Softw., 1995

A structure-based critique of contemporary computing research.
J. Syst. Softw., 1995

Turning the corner...to the same old street: A fundamental nonchange in JSS policy.
J. Syst. Softw., 1995

Editor's corner Beyond formal methods.
J. Syst. Softw., 1995

Readers' corner: An exchange with an anonymous reader, and a call for help from either researchers or librarians.
J. Syst. Softw., 1995

Software automation: Fact or fraud?
J. Syst. Softw., 1995

Editor's corner Plenty of pitfalls: There are numbers and then there are numbers.
J. Syst. Softw., 1995

Editor's corner an assessment of systems and software engineering scholars and institutions, 1993 and 1994.
J. Syst. Softw., 1995

Editor's corner in search of an obvious yet radical idea.
J. Syst. Softw., 1995

In Search of Self-Belief: The "BOP" Phenomenen.
Computer, 1995

1994
The Software-Research Crisis.
IEEE Softw., 1994

From Wonderland to the Real Problem.
IEEE Softw., 1994

Science and Substance: A Challenge to Software Engineers.
IEEE Softw., 1994

Editor's corner object-orientation: Theory and Practice (II).
J. Syst. Softw., 1994

Editor's corner : User satisfaction.
J. Syst. Softw., 1994

Editor's corner A tabulation of topics where software practice leads software theory.
J. Syst. Softw., 1994

Editor's corner theory + practice: A disturbing example.
J. Syst. Softw., 1994

Editor's corner discipline and creativity: An odd couple.
J. Syst. Softw., 1994

Editor's corner The faking of software design.
J. Syst. Softw., 1994

Editor's corner My readers write: Some thoughts on formal methods.
J. Syst. Softw., 1994

An assessment of systems and software engineering scholars and institutions.
J. Syst. Softw., 1994

Editor's corner Discipline is a dirty word: A story about the software life cycle.
J. Syst. Softw., 1994

Software Tasks: Intellectual, Clerical or Creative?.
Proceedings of the 27th Annual Hawaii International Conference on System Sciences (HICSS-27), 1994

1993
Object-oriented programming: The promise and the reality.
J. Syst. Softw., 1993

Editor's corner : The many flavors of testing.
J. Syst. Softw., 1993

Editor's corner: Object-orientation: Theory and practice.
J. Syst. Softw., 1993

Editor's corner : Of understanding, acceptance, ... and formal methods.
J. Syst. Softw., 1993

Editor's corner can english majors write maintenance documentation?
J. Syst. Softw., 1993

Editor's corner in defense of adhocracy.
J. Syst. Softw., 1993

Editor's corner the gold we've failed to mine.
J. Syst. Softw., 1993

Error detection: Which is better, reviews or testing?
J. Syst. Softw., 1993

Editor's corner Which do you think? Modern methods will lead to less software maintenance, or more?
J. Syst. Softw., 1993

Editor's corner software estimation is not a rational process.
J. Syst. Softw., 1993

1992
Toward a taxonomy of software application domains: History.
J. Syst. Softw., 1992

A comparative analysis of the topic areas of computer science, software engineering, and information systems.
J. Syst. Softw., 1992

Editor's corner: Finally - someone who understands where software quality fits in.
J. Syst. Softw., 1992

Editor's corner The link between software quality and software maintenance.
J. Syst. Softw., 1992

Editor's corner : The importance of the application domain cluster.
J. Syst. Softw., 1992

Editor's Corner we have lost our way.
J. Syst. Softw., 1992

Editor's corner on becoming obsolete.
J. Syst. Softw., 1992

Editor's corner : The importance of software quality in the 1990s.
J. Syst. Softw., 1992

Editor's corner The best and worst of software in the 1980s.
J. Syst. Softw., 1992

Software tasks: Intellectual or clerical?
Inf. Manag., 1992

1991
Editor's corner software productivity: What is management's role?
J. Syst. Softw., 1991

Editor's corner : Quality software: What is management's role?
J. Syst. Softw., 1991

Editor's corner: Structured research? (A partly tongue-in-cheek look).
J. Syst. Softw., 1991

Editor's corner : The (solved, unsolved) problem of literature searches.
J. Syst. Softw., 1991

Formal methods vs. heuristics: Clarifying a controversy.
J. Syst. Softw., 1991

Editor's corner : The computing communication chasm: Some new insight into why it is there, and what can be done about it.
J. Syst. Softw., 1991

4GLs and CASE: What's the payoff?
J. Syst. Softw., 1991

Editor's corner: Software maintenance: It's time to educate the educators.
J. Syst. Softw., 1991

Editor's corner: A report from the best and brightest.
J. Syst. Softw., 1991

1990
Editor's corner : Mikhail Gorbachev and software productivity (!?).
J. Syst. Softw., 1990

Editor's corner : Automatic programming - A cocktail party myth?
J. Syst. Softw., 1990

Editor's Corner: At last - some measured results of the "structured revolution".
J. Syst. Softw., 1990

Editor's Corner: Theory versus practice - revisited.
J. Syst. Softw., 1990

Editor's corner: The mystery of the little Chinese boy and his computer.
J. Syst. Softw., 1990

Editor's corner: Some pros and cons on (of all things!) references.
J. Syst. Softw., 1990

Editor's corner: Software design: Is there madness in a method?
J. Syst. Softw., 1990

1989
Editor's corner: Should a journal publish a virus?
J. Syst. Softw., 1989

Software metrics: of lightning rods and built-up tension.
J. Syst. Softw., 1989

Editor's corner : How can computer science truly become a science, and software engineering truly become engineering?
J. Syst. Softw., 1989

The temporal relationship between theory and practice.
J. Syst. Softw., 1989

Editor's corner: The legend of the bad software project.
J. Syst. Softw., 1989

Editor's corner : Some thoughts on software errors.
J. Syst. Softw., 1989

Editor's corner: How about next year? A look at a study of technology maturation.
J. Syst. Softw., 1989

Editor's corner: My trivial/brilliant concept called "problem solving".
J. Syst. Softw., 1989

Editor's corner.
J. Syst. Softw., 1989

1988
Editor's corner Robert L. Glass : Software Technology Transfer: A Multiflawed Process (The Road to Productivity Is Full of Potholes).
J. Syst. Softw., 1988

Editor's corner : A mythology of technology transfer.
J. Syst. Softw., 1988

Editor's corner : Software productivity improvement: Who's doing what?
J. Syst. Softw., 1988

1986
Editor's corner : "Dangerous and misleading": A look at software research via the parnas papers.
J. Syst. Softw., 1986

1985
Special Feature: Software Theft.
IEEE Softw., 1985

1982
Real-time Checkout: The 'Source Error First'.
Softw. Pract. Exp., 1982

Recommended: a Minimum Standard Software Toolset.
ACM SIGSOFT Softw. Eng. Notes, 1982

1981
Persistent Software Errors.
IEEE Trans. Software Eng., 1981

Letter from Robert L. Glass.
ACM SIGSOFT Softw. Eng. Notes, 1981

1980
The importance of the individual.
ACM SIGSOFT Softw. Eng. Notes, 1980

A benefit analysis of some software reliability methodologies.
ACM SIGSOFT Softw. Eng. Notes, 1980

The "project which failed" which succeeded.
ACM SIGPLAN Notices, 1980

Real-Time: The "Lost World" Of Software Debugging and Testing.
Commun. ACM, 1980

1978
Patching is alive and, lamentably, thriving in the real-time world.
ACM SIGPLAN Notices, 1978

Computing failure: A learning experience.
SIGMETRICS Perform. Evaluation Rev., 1978

1969
An Elementary Discussion of Compiler/Interpreter Writing.
ACM Comput. Surv., 1969


  Loading...