Home
> Uncategorized > Empirical Software Engineering using R: first draft available for download
Empirical Software Engineering using R: first draft available for download
A draft of my book Empirical Software Engineering using R is now available for download.
The book essentially comes in two parts:
- statistical techniques that are useful for analyzing software engineering data. This draft release contains most of the techniques I plan to cover. I am interested in hearing about any techniques you think ought to be covered, but I only cover techniques when real data is available to use in an example,
- six chapters covering what I consider to be the primary aspects of software engineering. This draft release includes the Human Cognitive Characteristics chapter and I am hoping to release one each of the remaining chapters every few months (Economics is next).
There is a page for making suggestions and problem reports.
All the code+data is available and I am claiming to have a copy of all the important, publicly available, software engineering data. If you know of any I don’t have, please let me know.
I am looking for a publisher. The only publisher I have had serious discussions with decided not to go ahead because of my insistence of releasing a free copy of the pdf. Self-publishing is a last resort.
Comparing distributions via student t-test, wilcoxon and other methods used in empirical software engineering needs to be clearly described in my opinion.
It is true that student t-test, wilcoxon and other methods are currently used in analysis of software engineering data (as well as analysis of all kinds of data). I don’t discuss these for the reasons cited, i.e., better methods (the bootstrap) are available (my reasons may need to be more clearly stated or made more prominent).
Hi!
Would it be possible to create an ebook reader friendly format besides pdf? It would be nice to be able to read it on a mobile device. Have you tried Leanpub as a publisher?
The production pipeline is:
Asciidoc
Docbook
Home grown scripts
LuaTex
So in theory another format is possible. The home grown scripts handle various features not supported by Asciidoc (AsciiDoctor does not yet have good enough LaTeX support) and invoke various LaTeX packages; so all this will need to be redone to support a new output format. At the moment the effort is going into the text.
An ebook format is a possibility once a complete draft is available.