Submission

Submission for Vissoft 2005 is now closed.

Information for the preparationof the camera ready versions of the papers

The position papers for the proceedings should be no longer than 6 pages and should conform to the IEEE style guidelines.
The tool demos for the proceedings should be no longer than 2 pages and should conform to the IEEE style guidelines.

Deadline:
July 29th, 2005

Formatting your Paper:
Your final papers must be formatted to IEEE Computer Society Proceedings Manuscript Formatting Guidelines.

Formatting Instructions
8.5" x 11" (DOC, PDF, PS)
LaTex Formatting Macros

We can accept only documents in PDF form.
For PDF generation, follow the rules:
- Optimized,
- Acrobat 4.0 compatibility,
- ALL graphics at least 300 dpi resolution, (higher if preferred)
- ALL fonts MUST be embedded and subset,
- Postscript settings DO NOT override distiller settings,
- Page size is 612.0 x 792.0 points (8.5" x 11").

Submitting the camera ready version of your paper:
Send the camera ready version of your paper by July 29th, 2005 to vissoft_submission@sdml.info


For this year's workshop we accept two types of submissions.

Position paper:
We solicit thought-provoking position style papers that will be presented and used for discussion during the workshop. Criteria for selection will be based on the clarity of the paper and the appropriateness of the topic for a group discussion. Note we strongly encourage tool users to submit papers that discuss what they would like to see the tool designers deliver in their tools, as well as position papers from tool designers. Position papers will be available in advance of the workshop and attendees will be encouraged to browse them beforehand to improve the discussion. Position papers should have a maximum of 6 pages in IEEE proceedings format.

Tool demonstrations :
Interested tool designers should submit a description of their tool and how it can be used to enhance understanding. Submissions should have a maximum of 2 pages with additional 2 pages with the description of the demonstration and screen captures if needed). The number of tools demonstrated will be limited
(by the size of the room). Criteria for selection will be on the maturity of the tool (for example, can the participants try it), innovative aspects and the quality of the description of the tool and the tasks it supports. We are particularly interested in software visualization tools that assist in understanding the static and dynamic aspects of the software during software maintenance and development.


Sponsored by IEEE-CS