AutoMed Software Distributions

NB For help on use of JDBC and example databases, see Peter McBrien's home page.

Checking code into the repository

To use the AutoMed CVS repository as a developerof the repository code, you must have a CSG account, and be a member of the automed group. You may then acceess the repository on any CSG linux machine. You may also access the repository remotely. For remote access it is suggested that you use one of the compute servers cpu1.doc.ic.ac.uk, cpu2.doc.ic.ac.uk, or cpu3.doc.ic.ac.uk. You need to set the CVS environment variables appropriately; for example (replacing username with your login):

CVSROOT=":ext:username@shell2.doc.ic.ac.uk:/vol/automed/cvsroot/"
CVS_RSH="ssh"

For each update you wish to make to the repository, you should (assuming the you have you AutoMed code in ~automed):

Changing the machine used for your repository

You can check which machine is being used for your repository by executing the command from the root directory of the checked out code:

find . -name Root -type f -exec cat '{}' \;

To change the name of the machine, say from shell1 to cvsuser, you should execute:

find . -name Root -type f -exec sed -i 's/shell1/cvsuser/g' '{}' \; Note that users within DoC are recommended to use cvsuser as the name of the CVS repository machine.

LaTeX Resources

LaTeX Style Files

Most project reports and publications are prepared in LaTeX, and use standard packages. The following are those not found in a standard RedHat distribution of Linux, but are widely used LaTeX packages. The following macro packages also used are `home grown', and not `high quality' packages for general distribution, so use at your peril.
  • colours.sty: Define a number of colours to use in the LaTeX color package.
  • stdpjmmacros.sty: A large number of macros to assist the production of LaTeX documents, in particular in producing pictures in LaTeX documents. The macros use the epic and eepic standard LaTeX packages, and hence are in compatible to pdflatex.
  • stdpjm.sty: A small wrapper for stdpjmmacros.sty that also controls the format of the page (do not use this in conjuction with llncs or other publisher's style files).
  • hdm.sty: HDM schemes and transformations on those schemes, and IQL queries
  • xml.sty: XML data and DTD schemas
  • casetool.sty: ER and DFD diagrams
  • automed.sty: macros specific to the AutoMed project
  • pjmnotes.sty: overall style settings used by Peter McBrien in the production of notes and books (do not use this in conjuction with llncs or other publisher's style files). Wraps pjmnotesmacros.sty, which can be used alone with llncs and other styles.
  • ipexamples.sty: macros for producing IP protocol diagrams
  • psfig.sty: macros including PostScript diagrams
  • supertab.sty: macros to produce long tables
  • pjmnotesmacros.sty: macros used by Peter McBrien in the production of notes and books
LaTeX project reports make use of the following BiBTeX files:
  • database.bib: Database related publications
  • case.bib: Software Engineering and case tools related publications

Preparing Documents for Distribution

To prepare an AutoMed report for distribution, you need to prepare both a Postscript and a PDF version of the document according to the following instructions
  • To generate a postscript file for mydoc, use

    dvips -ta4 mydoc -o mydoc.ps

  • To generate a PDF file for mydoc, use

    dvips -ta4 -Ppdf mydoc -o mydoc_pdf.ps

    ps2pdf mydoc_pdf.ps mydoc.pdf

Then email both to pjm@doc.ic.ac.uk, and put in plain text in the email:
  • authors' names
  • title
  • abstract