Journal of Software: Evolution and Process
© John Wiley & Sons Ltd
Edited By: Gerardo Canfora, Darren Dalcher and David Raffo
Impact Factor: 0.729
ISI Journal Citation Reports © Ranking: 2015: 69/106 (Computer Science Software Engineering)
Online ISSN: 2047-7481
Associated Title(s): Concurrency and Computation: Practice and Experience, Software Focus, Software Process: Improvement and Practice, Software Testing, Verification and Reliability, Software: Practice and Experience
NIH Public Access Mandate
For those interested in the Wiley-Blackwell policy on the NIH Public Access Mandate, please visit our policy statement
For additional tools visit Author Resources - an enhanced suite of online tools for Wiley Online Library journal authors, featuring Article Tracking, E-mail Publication Alerts and Customized Research Tools.
The Journal of Software: Evolution and Process operates an online submission and peer review system that allows authors to submit articles online and track their progress via a web interface. Please read the remainder of these instructions to authors and then visit http://mc.manuscriptcentral.com/jsme and navigate to the Journal of Software: Evolution and Process online submission site. IMPORTANT: Please check whether you already have an account in the system before trying to create a new one. If you have reviewed or authored for the journal in the past year it is likely that you will have had an account created.
All papers must be submitted via the online system.
File types. Preferred formats for the text and tables of your manuscript are .doc, .rtf, .ppt, .xls. LaTeX files may be submitted provided that an .eps or .pdf file is provided in addition to the source files. Figures may be provided in .tiff or .eps format.
Non-LaTeX users. Upload your manuscript files. At this stage, further source files do not need to be uploaded.
LaTeX users. For reviewing purposes you should upload a single .pdf that you have generated from your source files. You must use the File Designation "Main Document" from the dropdown box.
Non-LaTeX users. Editable source files must be uploaded at this stage. Tables must be on separate pages after the reference list, and not be incorporated into the main text. Figures should be uploaded as separate figure files.
LaTeX users. When submitting your revision you must still upload a single .pdf that you have generated from your revised source files. You must use the File Designation "Main Document" from the dropdown box. In addition you must upload your TeX source files. For all your source files you must use the File Designation "Supplemental Material not for review". Previous versions of uploaded documents must be deleted. If your manuscript is accepted for publication we will use the files you upload to typeset your article within a totally digital workflow.
COPYRIGHT AND PERMISSIONS
If your paper is accepted, the author identified as the formal corresponding author for the paper will receive an email prompting them to login into Author Services; where via the Wiley Author Licensing Service (WALS) they will be able to complete the license agreement on behalf of all authors on the paper.
For authors signing the copyright transfer agreement
If the OnlineOpen option is not selected the corresponding author will be presented with the copyright transfer agreement (CTA) to sign. The terms and conditions of the CTA can be previewed in the samples associated with the Copyright FAQs below:
CTA Terms and Conditions http://authorservices.wiley.com/bauthor/faqs_copyright.asp
For authors choosing OnlineOpen
If the OnlineOpen option is selected the corresponding author will have a choice of the following Creative Commons License Open Access Agreements (OAA):
Creative Commons Attribution License OAA
Creative Commons Attribution Non-Commercial License OAA
Creative Commons Attribution Non-Commercial -NoDerivs License OAA
To preview the terms and conditions of these open access agreements please visit the Copyright FAQs hosted on Wiley Author Services http://authorservices.wiley.com/bauthor/faqs_copyright.asp and visit http://www.wileyopenaccess.com/details/content/12f25db4c87/Copyright--License.html.
If you select the OnlineOpen option and your research is funded by certain funders [e.g. The Wellcome Trust and members of the Research Councils UK (RCUK) or the Austrian Science Fund (FWF)] you will be given the opportunity to publish your article under a CC-BY license supporting you in complying with your Funder requirements. For more information on this policy and the Journal’s compliant self-archiving policy please visit:http://www.wiley.com/go/funderstatement.
Submission of a manuscript will be held to imply that it contains original unpublished work and is not being submitted for publication elsewhere at the same time.
At the time of submission, authors should select one of the following manuscript types to describe their paper:
- Analytical: A paper in which the main contribution relies on new algorithms or mathematical theory. Examples include new bug prediction techniques, model transformations, algorithms for dynamic and static analysis, and reliability analysis. Such a contribution must be evaluated with a convincing analysis of the algorithmic details, whether through a proof, complexity analysis, or run-time analysis, among others and depending on the objectives.
- Empirical: A paper in which the main contribution is the empirical study of a software engineering technology or phenomenon. This includes controlled experiments, case studies, and surveys of professionals reporting qualitative or quantitative data and analysis results. Such a contribution will be judged on its study design, appropriateness and correctness of its analysis, and threats to validity. Replications are welcome.
- Technological: A paper in which the main contribution is of a technical nature. This includes novel tools, modeling languages, infrastructures, and other technologies. Such a contribution does not necessarily need to be evaluated with humans. However, clear arguments, backed up by evidence as appropriate, must show how and why the technology is beneficial, whether it is in automating or supporting some user task, refining our modeling capabilities, improving some key system property, etc.
- Methodological: A paper in which the main contribution is a coherent system of broad principles and practices to interpret or solve a problem. This includes novel requirements elicitation methods, process models, design methods, development approaches, programming paradigms, and other methodologies. The authors should provide convincing arguments, with commensurate experiences, why a new method is needed and what the benefits of the proposed method are.
- Practice: A paper presented as a practitioner paper or an experience report. Examples include reports on experimentation with new technologies or performance improvement approaches within a specific organisation, sector, country or region. Such a contribution is evaluated in terms of the value offered to practitioners and researchers looking for specific insights into the issues faced by practice. To the extent possible, these papers should present the costs and benefits associated with adopting the new technology or performance improvement approaches. Quantitative assessments of impact are one of the important factors that is considered when reviewing this type of paper.
- Standards: A paper reporting new developments, updates or changes to standards. Examples include the papers reporting changes to maturity models, evaluation schemes and ISO standards. Such a contribution will be evaluated to determine the value to both practitioners and researchers in terms of the extent/novelty of the changes and the impact to industry.
- Perspective: A paper in which the main contribution is a novel perspective on the field as a whole, or part thereof. This includes assessments of the current state of the art and achievements, systematic literature reviews, framing of an important problem, forward-looking thought pieces, connections to other disciplines, and historical perspectives. Such a contribution must, in a highly convincing manner, clearly articulate the vision, novelty, and potential impact.
The language of the journal is English. 12-point type in one of the standard fonts: Times, Helvetica, or Courier is preferred. It is not necessary to double-line space your manuscript. Tables must be on separate pages after the reference list, and not be incorporated into the main text. Figures should be uploaded as separate figure files.
Manuscript length. The recommended length for regular papers can vary, usually not more than 20 pages, fully formatted. Letter size submissions should not exceed the length of six pages, including figures and tables. A maximum of four figures is suggested.During the submission process you must enter the full title, short title of up to 70 characters and names and affiliations of all authors. Give the full address, including email, telephone and fax, of the author who is to check the proofs.
- Include the name(s) of any sponsor(s) of the research contained in the paper, along with grant number(s) .
- Enter an abstract of up to 200 words for all articles. An abstract is a concise summary of the whole paper, not just the conclusions, and is understandable without reference to the rest of the paper. It should contain no citation to other published work.
- Include up to six keywords that describe your paper for indexing purposes.
- Table of contents entries. Journal of Software: Evolution and Process publishes Graphical Table of Contents (GTOC) from 2009. Authors must submit an abstract figure (diagram or illustration selected from the manuscript or an additional "eye-catching" figure) and accompanying text for this abstract with the original manuscript. The GTOC entry should include the paper title, the authors’ names (with the corresponding author indicated by an asterisk) together with the figure and no more than 80 words or 3 sentences of text summarizing the key findings presented in the paper.
- Program material should be supplied as originals on plain paper, and will be reproduced photographically to avoid errors. The Editors and Publishers do not accept responsibility for the correctness of published programs.
- A section of 'Letters to the Editor' (each limited to 500 words) will provide a forum for discussion of recent problems.
- Alonso P, Badía JM, Vidal AM. Solving the block-Toeplitz least-squares problem in parallel. Concurrency and Computation: Practice and Experience 2005; 17 (1): 49-67. DOI: 10.1002/cpe.883.
- Reismann H. Elastic Plates: Theory and Application . Wiley: New York, 1988;1-10.
- PARAllel Total Energy Code. http://www.nersc.gov/projects/paratec [6 November 2004].
*The Digital Object Identifier (DOI) is an identification system for intellectual property in the digital environment. Developed by the International DOI Foundation on behalf of the publishing industry, its goals are to provide a framework for managing intellectual content, link customers with publishers, facilitate electronic commerce, and enable automated copyright management.
Illustrations. Upload each figure as a separate file in either .tiff or .eps format, with the lead author's name, the figure number and the top of the figure indicated. Compound figures e.g. 1a, b, c should be uploaded as one figure. Tints are not acceptable. Lettering must be of a reasonable size that would still be clearly legible upon reduction, and consistent within each figure and set of figures. Where a key to symbols is required, please include this in the artwork itself, not in the figure legend. All illustrations must be supplied at the correct resolution:
- Black and white and colour photos - 300 dpi
- Graphs, drawings, etc - 800 dpi preferred; 600 dpi minimum
- Combinations of photos and drawings (black and white and colour) - 500 dpi
We accept supporting information in many formats: Please provide as much information as you can about the file types, and aim for standard formats that will be viewable on many platforms (PC, Mac, UNIX, Linux). Irregular file types should be provided in a Zip archive.
Preferred: GIF, JPEG, PDF, SVG, MPEG, AVI, MOV, MP3, plain text, RTF, Zip.
Avoid: EPS, application specific files
Further information. For accepted manuscripts the publisher will supply proofs to the corresponding author prior to publication. This stage is to be used only to correct errors that may have been introduced during the production process. Prompt return of the corrected proofs, preferably within two days of receipt, will minimise the risk of the paper being held over to a later issue. Once your article is published online no further amendments can be made. Free access to the final PDF offprint of your article will be available via Author Services only. Please therefore sign up for Author Services if you would like to access your article PDF offprint and enjoy the many other benefits the service offers. Additional copies of the journal may be ordered. There is no page charge to authors.
Author Resources. Manuscript now accepted for publication?
If so, visit our suite of tools and services for authors and sign up for:
- Article Tracking
- E-mail Publication Alerts
- Personalization Tools
Cite EarlyView articles. To link to an article from the author’s homepage, take the DOI (digital object identifier) and append it to "http://dx.doi.org/" as per following example:
DOI 10.1002/hep.20941, becomes http://dx.doi.org/10.1002/hep.20941.
News and Diary. News and Diary on forthcoming meetings, publications, legislation and new products are invited and should be sent to the Editor-in-Chief.
This journal now uses eLocators. For more information, please visit the Author Services eLocator page here.