期刊名称：IEEE SOFTWARE
 期刊简介(About the journal)
投稿须知(Instructions to Authors)
编辑部信息(Editorial Board)
About the journal
IEEE Software 's mission is to build the community of leading and future software practitioners. The magazine delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change. The authority on translating software theory into practice, the magazine positions itself between pure research and pure practice, transferring ideas, methods, and experiences among researchers and engineers. Peer-reviewed articles, topical interviews, and columns by seasoned practitioners illuminate all aspects of the industry, including process improvement, project management, development tools, software maintenance, Web applications and opportunities, testing, usability, and much more.
Instructions to Authors
Mission and Scope
IEEE Software's mission is to Build the Community of Leading and Future Software Practitioners. The magazine delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change. The authority on translating software theory into practice, the magazine positions itself between pure research and pure practice, transferring ideas, methods, and experiences among researchers and engineers. Peer-reviewed articles, topical interviews, and columns by seasoned practitioners illuminate all aspects of the industry, including requirements and design, process improvement, project management, development tools, software maintenance, Web applications and opportunities, testing, usability, and much more.
In addition to full-length, peer-reviewed articles, IEEE Software has departments that cover news analysis, requirements, design, software construction, quality, management, and book reviews.
Please consult our Editorial Calendar for more information on special issues and submission deadlines. To propose a special-issue topic, see our special-issue proposal instructions or contact software@computer.org. If you have further questions, contact us at software@computer.org.
Originality
All manuscripts submitted must be original. Articles published (completely or in significant part) in other magazines or journals will not be considered for publication in IEEE Software. We will consider papers published in conference proceedings if they contain important or interesting new results, but they will be refereed again by the magazine's reviewers, independent of the conference's reviewing process. If a manuscript has been published or is being considered for publication elsewhere, the author must include that information in the submission cover letter. If such an article is accepted for publication in IEEE Software, the author is responsible for securing permission from the copyright holder.
Content and Presentation
IEEE Software is a magazine, not a journal. Articles should be understandable to a broad range of developers who want information they can apply in their daily work. Writing should be down-to-earth, practical, original, and comprehensible to all readers, regardless of their specialty. Do not assume that your audience has specialized experience in any particular subfield. Explain terms and concepts, and avoid jargon.
Use active instead of passive voice ("We discovered ..." rather than "It was discovered ...") and straightforward declarative sentences. In an introduction of 2 to 3 paragraphs, tell what the article is about and why your subject is significant in the field of software development. Avoid repetition of results and signposting (indications of what will follow or references to previous or subsequent sections). If acronyms must be used, define each one on its first appearance. When a person is mentioned in the text, include the full name on first reference and only the last name subsequently. Conclusions should not summarize, but instead outline future goals or lessons learned.
Article text should be in a text-accessible form such as MSWord (.doc) or ASCII (.txt) and a printable format such as PDF (.pdf) or Postscript (.ps). Pages should be sized at 8.5 by 11 inches and numbered at the bottom, and margins should be set at 1 inch all around.
Length
Articles should not exceed 5,400 words, including all text, the abstract, keywords, bibliography, biographies, and table text. Each figure and table counts as 200 words (to account for white space needed). Any article that exceeds this word count may be rejected automatically. Articles should have no more than 15 references. Reasonable exceptions are possible for surveys and tutorials.
Department items are usually about 1,400 to 2,500 words. Contact the specific department editor listed in the magazine to see if he or she is accepting submissions and what the particular guidelines are.
Specific Article Genres
Besides the topics listed below and our scheduled theme topics (see Editorial Calendar), we seek articles that fit particular genres, such as industry experience reports, tool reports, essays, and so on.
Biographical Sketch
Articles should be accompanied by a short biographical sketch. It should contain, in the following order, your current position and technical interests, prior applicable professional experience, education, professional affiliations, and address.
References
Please number your references in the order in which they appear. On average, an article should have no more than 15 references, sometimes more in well-justified situations such as survey or tutorial pieces. Cite only published or scheduled-for-publication material that the public can easily access. Avoid listing multiple references for standards or methodologies that are well known to the community and Software's readership.
Citations must include full publication information--for articles, this means listing all authors, the article name, the publication's full name, the volume, issue number, month, and year of publication, and the pages cited. For conference proceedings, we need all authors' names, the title of the article and the proceedings, the name of the proceedings publisher (not the conference's location), the year of publication, and the pages cited (see http://computer.org/author/style/refer.htm for examples).
Illustrations
We strongly encourage the use of visual presentation of your ideas.
Please provide high-quality, high-resolution files for best results. All illustrations must be cited in the text, numbered, and have descriptive captions. Submitted drawings should be clear and complete. We often redraw line art to conform with other figures in the magazine. See our graphics guidelines for full details on submitting high-resolution images to IEEE Software.
Submission
The IEEE Computer Society now employs a secure, Web-based manuscript submission and peer-review tracking system called Manuscript Central for all article submissions to IEEE Software. The site itself provides detailed instructions on usage. This tool significantly reduces the time required for the peer review process.
First-time users must create a new account. Authors must submit a word-processed (.doc or .txt) or print (.ps or .pdf) version; we prefer to have both word-processed and print files. On the first page of the manuscript, include the title, "Version #...," all author names and affiliations, the date of submission, an abstract, and keywords. In the cover letter, include all authors' mailing addresses, daytime telephones, email addresses, and fax numbers. For articles with more than one author, state who will act as the primary contact with the magazine. For more information, please see our submission guidelines and requirements located in the Author Center.
Peer Review
We solicit peer reviews from at least three individuals both inside and outside the manuscript's specialty. Reviews are used as the basis for acceptance and content revisions. The editor in chief makes the final decision regarding publication. Only about 25% of all article submissions are accepted.
Editing
Once an article is accepted for publication, IEEE Software staff editors will work with you to prepare the article to meet our style requirements, editing it according to our requirements regarding length, presentation, grammar, and style (see our Editing Philosophy). Editing includes copy editing (grammar, punctuation, and capitalization), style editing (conformance to the Computer Society magazines' house style), and content editing (flow, meaning, clarity, directness, and organization). We are happy to correct any errors inadvertently introduced during the editing process but must adhere to our style guidelines for consistency throughout the magazine. The editing process begins four to ten weeks before publication and takes two to three weeks.
Copyright Form and Clearances
We assume that articles submitted to us are for our exclusive use and will be published under the IEEE copyright. At least one author must sign a release form transferring copyright to the IEEE (excepting certain key rights retained by authors) before we can publish an article. The author must secure all necessary copyright clearances. For more information and an online copy of the form, see http://computer.org/copyright.htm.
Topics of Interest
We're looking for articles on the following topics:
Management
* Tailoring processes for organizational goals
* Assessing the impact of CMMI: does it work, what's the payoff?
* Comparison of CMM v. CMMI v. ISO9001:2000 v. SPICE
* Internationalization -- culture, text, space, colors, localization, national differences
* $100 million failures
* Lessons learned from the first Internet boom
* Post-project analysis
* Case studies of CMM level 3 companies
* Test information management
* Small company/start-up business issues
Software Construction
* Practitioners' good-practice guides on topic X
* Impact of introducing agile methods; is "agile" fragile?
* New user interfaces
* Comparison of CMM v. CMMI v. ISO9001:2000 v. SPICE
* Practitioners' good-practice guides on topic X
* Impact of introducing agile methods; is "agile" fragile?
* Geographically distributed development teams
* Web-based software development
* The software engineering of Internet software
* Ubiquitous computing (security, deployment, and embedded issues)
* Middleware
* COTS
* Electronic warfare
Design and Architecture
* Architectures as corporate assets
* Designing distributed systems
* Product line explosion
* Scaling software engineering
* Software architecture as a profession
Standards
* Professional standards, personal liability
* What can an individual do with a standard?
* Roadmap for how organizations can apply standards
Quality
* Cost of product quality
* Pervasive/mobile/personalized ways we interact with systems
* Management by data: what are the implications?
* What statistics applications are appropriate?
* Statistics vs. metrics, what's the difference?
* Collaborative quality assurance
* Just enough -- quality ramifications
* Economics of software quality
* Practice in inspections and estimation
Education and Training
* The learning organization
* SE education: should the teaching of programming be banned?
* Education -- skill sets needed for the future; certifications; licensing
These topics are merely the ones we know we are interested in. If you think we should be interested in some other topic, by all means tell us!
Contact Information
IEEE Software
IEEE Computer Society Publications Office
10662 Los Vaqueros Circle
Los Alamitos, CA 90720-1314 USA
phone: +1.714.821.8380
fax: +1.714.821.4010
Magazine Assistant (submissions)
Pauline Hosillos
software@computer.org
Senior Lead Editor (staff contact)
Dale Strok
dstrok@computer.org
Editor in Chief (volunteer)
Warren Harrison
phone: +1.503.725.3108
fax: +1.503.725.3211
warren@cs.pdx.edu
Group Managing Editor (staff)
Crystal Shif
cshif@computer.org
Editorial Board
Editor in Chief
Warren Harrison, warren.harrison@computer.org.
Staff
Dale Strok, Senior Lead Editor, dstrok@computer.org
Crystal Shif, Group Managing Editor, cshif@computer.org
Dennis Taylor, Associate Editor, dtaylor@computer.org
Shani Murray, Associate Editor, smurray@computer.org
Rebecca Deuel, Assistant Editor, rdeuel@computer.org
Denise Kano, Assistant Editor, dkano@computer.org
Joan Hong, Editorial Assistant, jhong@computer.org
Pauline Hosillos, Magazine Assistant, software@computer.org
Angela Burgess, Publisher, aburgess@computer.org
Dick Price, Assistant Publisher, dprice@computer.org
Design Director: Toni Van Buskirk
Production Artist: Carmen Flores-Garvey
Cover Art: Dirk Hagner
Technical Illustration: Alex Torres
Business Development Manager: Sandy Brown, sbrown@computer.org
Assistant Advertising Coordinator: Debbie Sims, dsims@computer.org
Membership/Circulation Promotions Manager: Georgann Carter, gcarter@computer.org
|
刊名字顺( Alphabetical List of Journals):
返回页首 