5th World Congress for Software Quality – Shanghai, China – November 2011

5WCSQ Word Template

5th World Congress for Software Quality – Shanghai, China – November 2011

1st Author

1st author's affiliation

Shanghai, China


2nd Author

2nd author's affiliation

Tokyo, Japan


3rd Author

3rd author's affiliation

Tokyo, Japan

5th World Congress for Software Quality – Shanghai, China – November 2011

Abstract

This document gives formatting instructions for authors preparing papers for World Congress for Software Quality. The authors are required to follow the guidelines given in the document for the papers to be submitted and published. You can use this document as both an instruction set and as a template into which you can type your own text.

1.  Introduction

The WCSQ proceedings are the records of the congress and give values to both the authors and all the participants of the WCSQ. The WCSQ Program Committee asks the authors follow the guidelines given in this document.

2.  Page Style

2.1  Layout

Your paper must use a page size corresponding to Letter size which is 215.9 mm (8.5 inch) wide and 279.4 mm (11 inch) long. The margins must be set to 25.4 mm for all four directions.

2.2  Font

Please use 10-point Helvetica or Arial font for the entire document including title and section headings. Title and section headings must be in bold.

2.3  Title and Author Details

Title and author details must be centered. For multiple authors, a multiple column function of Microsoft Word will be helpful like the author details of this document. Every word in a title must be capitalized except for short minor words such as “a”, “for”, “on”, “with”. The author details are recommended to include the name of the company, the names of the city and the country where the author is based, and the email address.

2.4  Section Headings

Every word in a section heading must be capitalized except for short minor words. A section and subsection should be numbered with a blank line above the section head. For a section head and a subsection head together (such as Section 2 and Subsection 2.1), use no blank line above the subsection head. No more than three levels of headings should be used.

2.5  Figures and Tables

Figures and tables should be centered. Please use adequate colors which contrast well when the paper is copied in a black-and-white hardcopy.

Figures and tables must have numbered captions in 10-point bold such as “Figure 1.” or “Table 1.”. Figure captions should be centered beneath the image or picture, and Table captions should be centered above the table body. Please see Figure 1 and Table 1 as references when you format your figures and tables.

Figure 1. A sample figure.

Table 1. A sample table.

WCSQ / Year / Place
1WCSQ / 1995 / San Francisco, USA
2WCSQ / 2000 / Yokohama, Japan
3WCSQ / 2005 / Munich, Germany
4WCSQ / 2008 / Bethesda Maryland, USA
5WCSQ / 2011 / Shanghai, China

2.6  References and Citations

A numbered list of the references is placed at the end of the article. The list should be ordered in either an alphabetical or a referred order in the article. The heading of the references must not be numbered. The references should be formatted in a consistent manner. See example references in this document.

When referring to a reference item in your article, please simply use the reference number, as in [1] for example. Multiple references are each numbered with separate brackets (e.g. [2], [3], [5-7]).

2.7  Headers and Footers

Please specify the title of your article in the footers except for the first page. You do not need to edit the other settings of headers and footers.

3.  Conclusions

This document provided the guidelines for WCSQ papers. The WCSQ Program Committee is waiting for valuable papers to discuss the excellence of software quality with you and all the participants of the WCSQ.

References

[1] Kan, S.H., Metrics and Models in Software Quality Engineering, Addison-Wesley, 2002.

[2] Basili, V.R., L.C. Briand, and W.L. Melo, A validation of object-oriented design metrics as quality indicators, IEEE Transactions on Software Engineering, 22(10), pp. 751-761, 1996.

[3] Boehm, B.W., Brown, A.W., Madachy, R. and Yang, Y., A Software Product Line Life Cycle Cost Estimation Model, Proc. 2004 International Symposium on Empirical Software Engineering (ISESE'04), pp. 156-164, 2004.

[4] Software engineering - Software measurement process, ISO/IEC 15939:2002, 2002.

[5] The IEEE website [Online], available at http://www.ieee.org/ (accessed on 2010/9/13).

Title of your article Page 2 of 2