期刊名称：SOFTWARE-PRACTICE & EXPERIENCE
 期刊简介(About the journal)
投稿须知(Instructions to Authors)
编辑部信息(Editorial Board)
About the journal
|
Software - Practice and Experience is an internationally respected and rigorously refereed vehicle for the dissemination and discussion of practical experience with new and established software for both systems and applications. Contributions regularly:
Describe detailed accounts of completed software-system projects
which can serve as 'how-to-do-it' models for future work in the same field;
Present short reports on programming techniques that can be used in a wide variety of areas;
Document new techniques and tools that aid in solving software construction problems;
Explain methods/techniques that cope with the special demands of large scale software projects.
|
|
The journal also features timely Short Communications on rapidly developing new topics.
The editors actively encourage papers which result from practical experience with tools and methods developed and used in both academic and industrial environments. The aim is to encourage practitioners to share their experiences with design, implementation and evaluation of techniques and tools for software and software systems.
Papers cover software design and implementation, case studies describing the evolution of system and the thinking behind them, and critical appraisals of software systems. The journal has always welcomed tutorial articles describing well-timed techniques not previously documented in computing literature. The emphasis is on practical experience; articles with theoretical or mathematical content are included only in cases where an understanding of the theory will lead to better practical systems.
Articles range in length from a Short Communication (half to two pages) to the length required to give full treatment to a substantial piece of software (40 or more pages)
Readership
Software engineers and designers ¡¤ systems programmers and analysts ¡¤ computer science educators and students
Keywords
software, practical, computer
Instructions to Authors
The keynotes are contained in the title - practice and experience. You should aim to convey the practical aspect of your work in a form that will enable others to reproduce your techniques in their own system and to benefit from your experience (whether successful or disastrous). Theory can be included, but only where it illuminates the point under discussion. Do not be frightened of including techniques that you feel are not original; they may need repeating to make your article clear. Worse still, they may not be written down anywhere in the available literature, in which case you will be doing a service to the computing community by putting them on paper. It is difficult to advise exactly what aspects of your work you should emphasize: it might help to record the things you were unclear about but would have found useful when you started your project. Avoid the temptation to dress up your work as a significant piece of pure research or highbrow mathematics.
Notes for Contributors
1. Initial submission: Manuscripts should be submitted electronically in PDF to:
Professor A.J. Wellings
Department of Computer Science
University of York
Heslington, York YO10 5DD
(e-mail: andy@cs.york.ac.uk)
or to
Professor D.E. Comer
Computer Science Department
Purdue University
West Lafayette, IN 47907
USA
(e-mail: spe@cs.purdue.edu) Authors must also supply:
o an electronic copy of the final version (see section below),
o a Copyright Transfer Agreement with original signature(s) - without this we are unable to accept the submission, and
o permission grants - if the manuscript contains extracts, including illustrations, from other copyright works (including material from on-line or intranet sources) it is the author's responsibility to obtain written permission from the owners of the publishing rights to reproduce such extracts using the Wiley Permission Request Form. Permission grants should be submitted with the manuscript.
Submitted manuscripts should not have been previously published and should not be submitted for publication elsewhere while they are under consideration by Wiley. Submitted material will not be returned to the author unless specifically requested.
2. Publisher's Note on electronic submission of accepted papers: If the text of your paper is available electronically it would be helpful to the Publisher if, together with the hard copy, you were to supply two disks containing the final version of your paper. Alternatively you may email your files to prd-spe@wiley.co.uk. The disks should be clearly labelled with the author's name, the date, the hardware and software packages used and the names of the files on the disk. We suggest that the following file naming conventions are used: the article file should have a six-letter name, the first three of which identify the journal (e.g. SPE for Software - Practice and Experience), the remaining three being the author's initials (use an X for the middle initial if you only have two initials). Separate files containing Figures should then be identified with the same six letters followed by a one-or two-character identifier for the Figure, e.g. 1, 2a, etc. The preferred medium is a 3.5 or 5.25 inch disk for PC (MS-DOS or Windows) or Macintosh. We are able to deal with most standard software packages currently available, although our preference is for WordPerfect, Word or TeX (and/or one of its derivatives). We are also able to accept line artwork/graphics on disk. For guidelines on the preparation of illustrations, see note 10. The disks must be accompanied by a hard copy printout. If the disk and the paper copy differ, the paper copy will be treated as the definitive version.
3. Only original papers will be accepted, and copyright in published papers will be vested in the Publisher.
4. The language of the journal is English.
5. Twenty-five offprints of each paper will be provided free of charge. Additional copies may be purchased on an offprint order form which will accompany the proofs. Offprints and correspondence will be sent to the first-named author unless otherwise stated.
6. Manuscripts should be typed double-spaced with wide margins, on one side of the paper only, and submitted in triplicate. Authors should write concisely.
7. The title should be brief, typed on a separate sheet and the author's name should be typed on the line below the title; the affiliation and address should follow on the next line. In the case of co-authors, respective addresses should be clearly indicated. Correspondence and proofs for corrections will be sent to the first-named author, unless otherwise indicated. In order to enable the publisher to do everything to ensure prompt publication, the full postal address should be given for the author who will check proofs, along with telephone, fax and email numbers where possible.
8. The body of the manuscript should be preceded by a Summary (maximum length 200 words) which should be a summary of the entire paper, not of the conclusions alone. This should be followed by not more than 6 key words.
9. The paper should be reasonably sub-divided into sections and, if necessary, subsections. Numbering of these should be avoided wherever possible.
10. Illustrations. In your initial submission illustrations may be embedded in the text. However, for submission of the accepted paper the Publisher prefers the illustrations to be submitted on separate sheets, each accompanied by a separate list of captions. Drawings should be supplied at the same size as the intended printed version (so no enlargement or reduction is required), maximum dimensions 140mm by 200mm. Lettering on the artwork should be set in 8pt type. The amount of lettering on a drawing should be reduced as far as possible by transferring it to the caption. Tints are to be avoided; hatching should be used instead. Boxes should not be used to enclose diagrams unless the box is an integral part of the illustration.
If you are submitting the final version of the paper electronically, and illustrations are available in electronic form, they should be supplied together with the text file. Each illustration should be supplied in a separate file. Illustrations should preferably be created in a dedicated drawing package, such as Adobe Illustrator/Corel Draw/Macromedia Freehand not presentation, spreadsheet or database packages, and both the source file and an Encapsulated PostScript file should be supplied, along with a hardcopy printout of each figure, clearly identified. The caption should not form part of the illustration, but be supplied as part of the text file.
Artwork not available electronically should be supplied as originals on plain paper for photographic reproduction. A distinct black image must be supplied. Computer-generated artwork must be submitted as laser printed output at a resolution of 600 dots per inch on high quality paper. Dot matrix printer output is unacceptable. Drawn artwork should be carefully lettered and drawn in black ink. Provide copies as well as the originals.
11. Photographic illustrations are to be restricted in number to the minimum necessary. Sharp glossy black and white prints (not photocopies or previously printed material) should accompany the manuscript, and should not be attached to manuscript pages. Laser output photographs are to be avoided. If words or numbers are to appear on a photograph, two prints should be sent, the lettering being clearly indicated on one print only.
12. Colour illustrations will be accepted only if the costs are borne by the author.
13. All printed items of artwork or illustrative material should be clearly identified on the back in pencil with the author's name and the Figure number.
14. Program material. To avoid errors in reproducing program material, authors should supply displayed program examples either as artwork, in which case the guidelines for illustrations should be followed, or electronically. The preferred electronic format is as ASCII text with a maximum of 70 characters per line, with indentations generated by space characters rather than tabs. Programs, and program material in running text, will normally be set in a typewriter font (Courier). If your programs require non-ASCII characters or mixed fonts please indicate this clearly on the final manuscript.
15. It is the author's responsibility to obtain written permission to quote material which has appeared in another publication.
16. Tables should be numbered consecutively and titled. All table columns should have an explanatory heading. Tables should not repeat data which is available elsewhere in the paper, e.g., in a line diagram.
17. References to published literature should be quoted in the text by superior numbers and grouped together at the end of the paper in numerical order and arranged thus:
1. R. Fletcher and M.J.D. Powell, 'A rapidly convergent descent method for minimization', Comput. J., 6, 163-168 (1963)
2. H. Carslaw and J.G. Jaeger, Operational Methods in Applied Mathematics, 2nd edn., Oxford University Press, London, 1953.
18. A section of 'Letters to the Editor' (each limited to 500 words) will provide a forum for discussion of recent problems.
19. No manuscripts or figures will be returned to authors following publication.
20. The Publisher will do everything possible to ensure prompt publication. It will therefore be appreciated if manuscripts and illustrations conform from the outset to the style of the journal.
21. The Editors and Publishers do not accept responsibility for the correctness of published programs.
22. If the software discussed in your paper is available from a Web site or an FTP site, you should give the URL, either as a footnote to the text or as part of your reference list. Authors are responsible for verifying the accuracy of all citations, including URLs or other references to items available on the Internet.
*NOTE: Because of recent changes in copyright law the transfer of copyright from author to publisher, previously implicit in the submission of a manuscript, must now be explicitly transferred to enable the Publisher to ensure maximum dissemination of the author's work. A copy of the Copyright Transfer Agreement to be used for Software - Practice and Experience is reproduced in each volume. Additional copies are available from the journal editors or from the Publisher; or contributors may photocopy the agreement from this journal or print a copy from this Web site. A copy of the agreement, signed by the author, must accompany every article submitted for publication.
Editorial Board
|
EDITORS |
|
Professor D.E. Comer
Computer Science Department
Purdue University, West Lafayette
IN 47907, USA |
Professor A.J. Wellings
Department of Computer Science
University of York
Heslington, York YO10 5DD, UK |
|
ADVISORY EDITORIAL BOARD |
|
|
|
|
|
Professor D.W. Barron
Department of Electronics and
Computer Science
University of Southampton
Southampton SO9 5NH, UK |
Professor Per Brinch Hansen
School of Computer and Information Science
4-116 CST, Syracuse University
Syracuse, New York 13210, USA |
|
Professor P.J. Brown
Department of Computer Science
University of Exeter
Exeter EX4 4PT, UK |
Professor F.J. Corbato
Electrical Engineering Department
Massachusetts Institute of Technology
545 Technology Square,
Cambridge, MA 02139, USA |
|
Dr Christopher W. Fraser
Microsoft Research
1 Microsoft Way
Redmond, WA 98052, USA |
Professor D.R. Hanson
Microsoft Research
1 Microsoft Way
Redmond, WA 98052, USA |
|
Professor J. Katzenelson
Faculty of Electrical Engineering
Technion-Israel Institute of Technology
Haifa, Israel |
Dr B.W. Kernighan
Bell Laboratories
Lucent Technologies
600 Mountain Avenue
Murray Hill, NJ 07974, USA |
|
Professor D.E. Knuth
Department of Computer Science
Stanford University,
Stanford, CA 94305, USA |
Dr B.W. Lampson
180 Lake View Ave.,
Cambridge
MA 02138, USA |
|
Dr C.A. Lang
Three-Space Ltd
Park House
Castle Park
Cambridge CB3 0DU, UK |
Professor B. Randell
Computing Laboratory
University of Newcastle-upon-Tyne
Claremont Tower, Claremont Road
Newcastle-upon-Tyne NE1 7RU, UK |
|
Professor J.S. Rohl
Department of Computer Science
The University of Western Australia
Nedlands, Western Australia 6009 |
Dr D.T. Ross
33 Dawes Road, Lexington
MA 02421, USA |
B.H. Shearing
The Software Factory
28 Padbrook, Limpsfield
Oxted, Surrey RH8 0DW, UK
|
