期刊名称：ACM TRANSACTIONS ON SOFTWARE ENGINEERING AND METHODOLOGY
|
ISSN： | 1049-331X
|
|
版本： | SCI-CDE
|
|
出版频率： | Quarterly
|
|
出版社： | ASSOC COMPUTING MACHINERY, 1515 BROADWAY, NEW YORK, NY, 10036
|
|
出版社网址： | http://www.acm.org/
|
|
期刊网址： | http://www.acm.org/tosem/
| |
影响因子： | 3.958(2008) |
| 主题范畴： | COMPUTER SCIENCE, SOFTWARE ENGINEERING |
 期刊简介(About the journal)
投稿须知(Instructions to Authors)
编辑部信息(Editorial Board)
About the journal
ACM Transactions on Software Engineering and Methodology (ACM TOSEM ) publishes original, significant, reproducible and archival results in all areas of software engineering research. The published articles, in general, provide substantial solutions to problems that make it difficult and costly to engineer complex and long-lived software systems with appropriate characteristics. The articles may also identify significant challenges for software engineering research based on thoughtful insights derived from practical experience.
Published ACM TOSEM articles present results that:
- are based on formal, experimental, or other scholarly approaches to problems in software engineering research, providing an evaluation of the research that is appropriate to and commensurate with the research claims;
- address any phase or phases in the software lifecycle, using models, languages, methods, analyses, tools, and other suitable approaches in the research; and
- consider the longer-term potential of the research (such as extensibility, scalability, and practical relevance).
As with other computing research areas, the characteristics of published ACM TOSEM papers evolve slowly over time. Recently published papers are usually characteristic of the style and topics that successfully complete the rigorous reviewing process.
Short contributions and technical correspondence about published papers may appear, as is customary in scientific journals.
David Notkin
Editor-in-Chief
Instructions to Authors
Information for Authors
Table of Contents
The ACM Transactions on Software Engineering and Methodology is a publication for original and significant results in all areas of software engineering research. The software systems of interest for this journal are charactered in most cases by a scale requiring development by teams, not individuals. They should be sufficiently complex and long-lived to justify investment in languages, methods, and tools that support specification, design, implementation, validation, documentation, maintenance, reengineering, and other related activities. Submitted papers should address important research topics; the results described must be reproducible, extensible, scalable, and have practical relevance.
Experience reports on the use of advanced software engineering techniques are also welcome. To be publishable, however, they must provide thoughtful insights about the development world or the application of a technology, that result in the identification of new important challenges for software engineering research.
The scope of TOSEM includes models, languages, methods, mechanisms, and tools for the elaboration, evaluation, and evolution of products and processes all along the software lifecycle, from requirements specification to software maintenance. Formal and experimental approaches are both in the scope of TOSEM. Examples of topics include:
- Requirements engineering: acquisition, modelling, specification, analysis, and prototyping;
- Design engineering: software architectures, specification, refinement, design methods, strategies, and styles; documentation of design rationales;
- Software testing, analysis and verification: algorithms, techniques and processes for assuring or assessing software with respect to functional or non-functional requirements;
- Configuration management: version control and system evolution;
- Software understanding and reengineering;
- Reuse: techniques for reusing components such as specifications, designs, or code, and for making such products reusable;
- Software process engineering: modeling, analysis, customization, enactment, evolution;
- Software engineering environments: organization, tool integration and interoperability; object management, language-directed tools, knowledge-based tools, dedicated tools; software visualization;
- Measurement, metrics, estimation methods, and empirical studies;
- Human-Software interaction;
- Collaborative software engineering;
- Special software engineering techniques for: distributed systems, real-time systems, safety-critical systems, secure systems, multimedia systems, and mobile computing;
- Adaptation of techniques from programming languages, artificial intelligence, or databases;
- Domain-specific software engineering techniques.
Papers submitted are judged primarily on originality, significance, technical soundness and quality of presentation. Contributions should conform to generally accepted practices for scientific papers with respect to organization, clarity and style.
Theoretical or methodological papers should clearly show how the results presented may contribute to software engineering practice. Papers on specific systems should concentrate on technical and architectural issues rather than providing feature-by-feature descriptions. Experimental papers should describe the experimental method used and interpret the results in terms of practice. All papers should clearly indicate what is new and significant about the work presented and how it compares with related work. Every claim must be substantiated through detailed arguments. Technical precision and conciseness are other important requirements.
It is the ACM policy to be the sole, original publisher of articles. Manuscripts that have been submitted simultaneously to other magazines, journals or to conferences, symposia, or workshops without the prior written consent of the Editor-in-Chief will be rejected outright and will not be reconsidered. Widely disseminated conference proceedings and newsletters are a form of publication, although they are usually only semi-archival and often not fully refereed. Publication of expanded versions of papers that have been disseminated via proceedings or newsletters is permitted only if the Editor-in-Chief judges that (a) the revision contains significant amplification or clarification of the original material or (b) there is a significant additional benefit to be gained from journal publication. In either case, any prior appearance should be noted on the title page of the paper. The differences between the submission and the original version should be made explicit both in the submission letter and in the paper. A conference chairperson can arrange with the Editor-in-Chief to publish selected papers from conferences, symposia, and workshops, after suitable reviewing. The papers must meet the editorial requirements for research articles. Acknowledgment of the originating conference will appear as a credit when the paper is published in TOSEM.
Extremely long submissions -- as a general rule, those that exceed approximately 11,000 words -- may be returned without review at the discretion of the editor-in-chief. If placed into the review process, such submissions are not guaranteed review or publication in a timely fashion.
Submissions are electronic and follow ACM guidelines.
Manuscripts intended for publication should be submitted by uploading an electronic version to http://mc.manuscriptcentral.com/tosem. Submission requires that the lead author creates an account with his/her full contact information and a statement that the material contained in the submitted paper has not been previously published and is not currently considered for publication elsewhere. If the submission is an expanded version of a conference or workshop paper the lead author should identify the conference or workshop and specify the differences between the submission and the conference version.
Papers will be refereed in the manner customary with scientific journals before being accepted for publication. The overall process is roughly as follows. (In the sequel the acronyms EIC and AE stand for Editor-in-Chief and Associate Editor, respectively.)
- Authors submit paper to EIC.
- EIC selects AE according to topic of paper, absence of conflict, fair distribution of load among AE's, etc.
- AE suggests 3-4 referees to EIC.
- EIC checks that referees suggested haven't been already solicited too much recently, have no conflict etc., THEN negotiates with referees an acceptable deadline for review, THEN emails or snail-mails paper to reviewer. Typically, 70% of reviewers commit to the proposed four weeks, 20% to 6 weeks, and 10% up to 10 weeks.
- AE and referees review paper.
- EIC tries to diplomatically pester reviewers when deadline is over.
- WHEN all reviews are available EIC sends them to AE and asks AE for an editorial decision together with some justification highlighting the main reviewers' concerns. The usual decisions are: accept, minor revision, major revision, reject. Minor revisions are usually rechecked by AE only; major revisions trigger a new round of reviewing by the original reviewers.
- EIC sends decision letter to authors together with referees' reports AND sends anonymous, verbatim copies and thanks to AE and reviewers.
- EIC sends accepted papers to ACM.
Steps (1)-(9) are carried out over the Internet whenever possible.
Authors are expected to keep the Editor-in-Chief informed of any change of address. Correspondence on editorial matters should be addressed to tosem at cs dot washington dot edu. Correspondence regarding accepted papers should be addressed to Jono Hardjowirogo (with a copy to tosem at cs dot washington dot edu), or on paper to:
Managing Editor, TOSEM, ACM, 1515 Broadway, New York, NY 10036
with a copy to the Editor-in-Chief.
Letters and notes of detailed technical content are considered for publication as Technical Correspondence. They are formally reviewed but are usually not refereed in the same way as short contributions or full articles.
If an author has concerns about how her or his paper was handled, that author should bring those concerns to the EIC. If the author feels that the concerns are not adequately addressed by the EIC, she or he may appeal to the Chair of the Publications Board, in accordance with ACM policy.
Once a manuscript is accepted, a final version must be submitted to the Editor-in-Chief for transmission to ACM for publication. Although this may be done on paper, electronic submission is again highly encouraged. ACM provides for a wide variety of formats for such electronic submissions. Please contact Jono Hardjowirogo for further details or refer to ACM's Guidelines for Submitting Accepted Articles for details.
Copyright. Authors who submit a paper will be sent a sample ACM copyright form for review. If the paper is acceptable after refereeing, each author will be asked to sign an actual ACM copyright form, either transferring copyright to ACM or declaring that the paper is part of government work. The return of the signed ACM form completes the acceptance process. Authors retain liberal rights to material published by ACM. Further information may be found in the ACM Interim Copyright Policies.
Use Agreement. Abstracting of material in ACM Transactions on Software Engineering and Methodology is permitted with credit to the source. Libraries are permitted to photocopy beyond the limits of U.S. copyright law for private use of patrons those articles in this volume that carry a code at the bottom of the first page, provided the per-copy fee indicated in the code is paid through the:
Copyright Clearance Center, P.O. Box 675, Schenectady, NY 12301.
Instructors are permitted to photocopy isolated articles for non-commercial classroom use without fee. For other copying, reprint, or republication permission, write to:
Director of Publications, ACM, 1515 Broadway, New York, NY 10036 USA.
All rights reserved.
Authors' institutions or corporations are requested to honour a page charge of $60.00 per printed page or part thereof to help defray the cost of publication. Page charges apply to all contributed papers, articles, algorithms, etc. Fifty reprints of each item are furnished free of charge. Payment of page charges is not a condition of publication; editorial acceptance of a paper is unaffected by payment or nonpayment.
Instructions to Authors
a1049-331X.pdf
Editorial Board
Editorial Charter
The purpose of the ACM Transactions on Software Engineering and Methodology (TOSEM) is to publish original and significant results in all areas of software engineering research. In general, the systems to which the results apply should be sufficiently complex and long-lived to justify investment in languages, methods, and tools that support specification, design, implementation, validation, documentation, maintenance, reengineering, and other related activities. Published articles will address important research topics; results will be reproducible, extensible, scalable, and have practical relevance. Experience reports on the use of advanced software engineering techniques are in principle excluded unless they provide thoughtful insights about the development world or the application of a technology, that result in the identification of new important challenges for software engineering research.
The scope of TOSEM includes models, languages, methods, mechanisms, and tools for the elaboration, evaluation, and evolution of products and processes all along the software lifecycle -- from requirements specification to software maintenance and reengineering. Formal and experimental approaches are both in the scope of TOSEM. Examples of topics include:
- Requirements engineering: acquisition, modeling, specification, analysis, and prototyping;
- Design engineering: software architectures, specification, refinement, design methods, strategies, and styles; documentation of design rationales;
- Software testing, analysis and verification: algorithms, techniques and processes for assuring or assessing software with respect to functional or non-functional requirements;
- Configuration management: version control and system evolution;
- Software understanding and reengineering;
- Reuse: techniques for reusing components such as specifications, designs, or code, or for making such products reusable;
- Software process engineering: modeling, analysis, customization, enactment, evolution;
- Software engineering environments: organization, tool integration and interoperability; object management, language-directed tools, knowledge-based tools, dedicated tools; software visualization;
- Measurement, metrics, estimation methods, and empirical studies;
- Human-Software interaction;
- Collaborative software engineering;
- Special software engineering techniques for: distributed systems, real-time systems, safety-critical systems, secure systems, multimedia systems, and mobile computing;
- Adaptation of techniques from programming languages, artificial intelligence, or databases;
- Domain-specific software engineering techniques.
Short contributions and technical correspondence about published papers may appear in appropriate sections as is customary in scientific journals.
TOSEM Policy on Original Publication: It is the policy of the TOSEM Editorial Board that ACM be the sole, original publisher of articles and commentary. Manuscripts that have been submitted simultaneously to other magazines, journals or to conferences, symposia, or workshops without the prior written consent of the Editor-in-Chief will be rejected outright and will not be reconsidered. Publication of expanded versions of papers that have been disseminated via proceedings or newsletters is permitted only if the Editor-in-Chief judges that there is significant additional benefit to be gained from journal publication. A conference chairperson can arrange with the Editor-in-Chief to publish selected papers from conferences, symposia, and workshops, after suitable reviewing. The papers must meet the editorial requirements for research articles. Acknowledgement of the originating conference will appear as a credit when the paper is published in TOSEM.
Publication of research results in an archival journal like TOSEM has several major benefits. From the author's perspective, the feedback from reviewers is usually much more substantial, deep and constructive than for conferences or workshops where a same reviewer may have to handle dozens of papers within a couple of weeks; the decision is not a binary one (accept/reject); the material can be presented in greater detail; the work being published is much less likely to be forgotten rapidly. From the reader's perspective, the material presented is more stable and better polished. The other side of the picture is that journal publication may tend to be not timely enough. The TOSEM Editorial Board has recently taken some drastic actions to fight against this (see submission and review processes).
On behalf of the Editorial Board, I wish to thank all readers, authors, and reviewers for their contribution in making TOSEM an exciting, premier scientific journal in the field of software engineering.
Editor-in-Chief
Carlo Ghezzi
|
|
Carlo Ghezzi e' Professore Ordinario di Ingegneria del Software e membro del Senato Accademico del Politecnico di Milano. E' Fellow dell'ACM (Association for Computing Machinery). E' Editor in Chief della rivista ACM Transactions on Software Engineering and Methodology e membro dello Steering Committee della International Conference on Software Engineering. Ha insegnato all'Universita' di Padova, all'Universita' della North Carolina (Chapel Hill), alla Escuela Superior Latino-Americana de Informatica (ESLAI, Argentina), alla Technische Universitaet di Vienna, all'Universita' di Klagenfurt, all'Universita' della Svizzera Italiana. Carlo Ghezzi e' membro di numerosi comitati scientifici a livello nazionale ed internazionale. Ha dato seminari e presentazioni di ricerca in molti paesi di tutti i continenti. La ricerca di Carlo Ghezzi si rivolge ai linguaggi di programmazione e all'ingegneria del software, con particolare riguardo ai fondamenti teorici, metodologici e tecnologici dello sviluppo delle applicazioni distribuite su rete.
Dipartimento di Elettronica e Informazione
Politecnico di Milano
Piazza Leonardo da Vinci, 32 - I 20133 Milano (Italy)
Phone: +39-022399-3529
Fax: +39-022399-3411
Carlo.Ghezzi@polimi.it
Information Director
Mattia Monga
Dipartimento di Informatica e Comunicazione
Università degli Studi di Milano
Via Comelico, 39/41 - I 20135 Milano (Italy)
Phone: +39-02503-16313
Fax: +39-02503-16253
mattia.monga@unimi.it
Editorial Assistant
Alessandra Viale
Dipartimento di Elettronica e Informazione
Politecnico di Milano
Piazza Leonardo da Vinci, 32 - I 20133 Milano (Italy)
Phone: +39-022399-3405
Fax: +39-022399-3411
Alessandra.Viale@elet.polimi.it
Editorial Board
Premkumar Devanbu
Dept. Of Computer Science
Engineering Unit II
University of California at Davis
Davis, CA 95616 USA
devanbu@cs.ucdavis.edu
Anthony Finkelstein
University College London
Dept. of Computer Science
Gower Street
London WC1E 6BT
United Kingdom
a.finkelstein@cs.ucl.ac.uk
Phyllis G. Frankl
Computer and Information Science
Polytechnic University
6 Metrotech Center
Brooklyn, NY 11201 USA
Phone: +1-718-260-3870
Fax: +1-718-260-3609
phyllis@morph.poly.edu
Alfonso Fuggetta
Dipartimento di Elettronica e Informazione
Politecnico di Milano
Piazza Leonardo da Vinci, 32 - 20133 Milano (Italy)
Phone: +39-022399-3540
Fax: +39-022399-3411
Alfonso.Fuggetta@polimi.it
David Garlan
School of Computer Science
Carnegie Mellon University
5000 Forbes Avenue
PITTSBURGH PA 15213 (USA)
Phone: +1 412 268 5056
Fax: +1 412 681 5739
garlan@cs.cmu.edu
Constance L. Heitmeyer
Center for High Assurance Computer Systems
Code 5546
Naval Research Laboratory
Washington, DC 20375
heitmeye@itd.nrl.navy.mil
Daniel Jackson
MIT Lab for Computer Science
545 Technology Square
Cambridge, MA 02139 (USA)
Fax: +1 617 258 8607
dnj@lcs.mit.edu
Adam Porter
Computer Science Department
University of Maryland
College Park, MD 20472 (USA)
Phone: +1-301-405-2702
Fax: +1-301-405-6707
aporter@cs.umd.edu
Gruia-Catalin Roman
Department of Computer Science
Washington University
Campus Box 1045
One Brookings Drive
Saint Louis, Missouri 63130
U.S.A.
roman@cs.wustl.edu
Kevin J. Sullivan
University of Virginia
Department of Computer Science
151 Engineer's Way, P.O. Box 400740
Charlottesville, Virginia, 22904-4740 U.S.A.
sullivan@virginia.edu
Alexander L. Wolf
Department of Computer Science
University of Colorado at Boulder
ECOT 7-7, Campus Box 430
BOULDER CO 80309-0430 (USA)
Phone: +1-303-492-5263
Fax: +1-303-492-2844
alw@cs.colorado.edu |
|
刊名字顺( Alphabetical List of Journals):
返回页首 