INSTRUCTIONS FORMAT!

Abstract
1. INTRODUCTION
2. METHODOLOGY
3. RESEARCH FRAMEWORK
4. EXPECTED OUTPUT
5. CONCLUSION
6. RECOMMENDATION
7. REFERENCES
NOTE: ALL THE TABLES ARE NOT (OPEN ENDED)
PLEASE LOOK THE FORMAT BELOW BUT
REMEMBER FOLLOW INSTRUCTIONS FORMAT!
OR YOU CAN SEARCH ACM FORMAT IN
GOOGLE. THANK YOU! GOODLUCK..
SIR. MARC P. LAURETA
TITLE
NAME OF RESEARCHERS
EMAIL
ABSTRACT
In this paper, we describe the formatting guidelines for ACM SIG
Proceedings.
Categories and Subject Descriptors
D.3.3 Programming Languages!" #anguage Constructs and
$eatures % abstract data types, polymorphism, control
structures. &his is 'ust an e(ample, please use the correct
categor) and sub'ect descriptors for )our submission. The ACM
Computing Classification Scheme:
http://www.acm.org/class/1998/
General Terms
*our general terms must be an) of the following +, designated
terms" Algorithms, Management, Measurement, Documentation,
Performance, Design, -conomics, .eliabilit), -(perimentation,
Securit), /uman $actors, Standardi0ation, #anguages, &heor),
#egal Aspects, 1erification.
Keywords
2e)words are )our own designated 3e)words.
! "#TR$D%CT"$#
&he proceedings are the records of the conference. ACM hopes to
gi4e these conference b)5products a single, high56ualit)
appearance. &o do this, we as3 that authors follow some simple
guidelines. In essence, we as3 )ou to ma3e )our paper loo3
e(actl) li3e this document. &he easiest wa) to do this is simpl)
to down5load a template from 7!, and replace the content with
)our own material.
&! PAG' S"('
All material on each page should fit within a rectangle of +8 9
73.: cm ;<= 9 >.7:=?, centered on the page, beginning +.> cm
;@.<:=? from the top of the page and ending with 7.:A cm ;+=?
from the bottom. &he right and left margins should be +.> cm
;.<:=?.
&he te(t should be in two 8.A: cm ;3.33=? columns with a .83 cm
;.33=? gutter.
)! T*P'S'T T'+T
)! #ormal or Body Te,t
Please use a >5point &imes .oman font, or other .oman font
with serifs, as close as possible in appearance to &imes .oman in
which these guidelines ha4e been set. &he goal is to ha4e a >5
point te(t, as )ou see here. Please use sans5serif or non5
proportional fonts onl) for special purposes, such as
distinguishing source code te(t. If &imes .oman is not a4ailable,
tr) the font named Computer Modern .oman. Bn a Macintosh,
use the font named &imes. .ight margins should be 'ustified,
not ragged.
)!& Title and Aut-ors
&he title ;/el4etica +85point bold?, authorsC names ;/el4etica +75
point? and affiliations ;/el4etica +@5point? run across the full
width of the page % one column wide. De also recommend phone
number ;/el4etica +@5point? and e5mail address ;/el4etica +75
point?. See the top of this page for three addresses. If onl) one
address is needed, center all address te(t. $or two addresses, use
two centered tabs, and so on. $or more than three authors, )ou
ma) ha4e to impro4ise.
+
)!) .irst Page Copyrig-t #otice
Please lea4e 3.8+ cm ;+.:=? of blan3 te(t bo( at the bottom of the
left column of the first page for the cop)right notice.
)!/ Subse0uent Pages
$or pages other than the first page, start at the top of the page,
and continue in double5column format. &he two columns on the
last page should be as close to e6ual length as possible.
Table ! Table captions s-ould be placed abo1e t-e table
Grap-ics Top "n2between Bottom
&ables -nd #ast $irst
$igures Good Similar 1er) well
)!3 Re4erences and Citations
$ootnotes should be &imes Eew .oman >5point, and 'ustified to
the full width of the column.
Fse the GACM .eference formatH for references % that is, a
numbered list at the end of the article, ordered alphabeticall) and
formatted accordingl). See e(amples of some t)pical reference
t)pes, in the new GACM .eference formatH, at the end of this
document. Dithin this template, use the st)le named references
for the te(t. Acceptable abbre4iations, for 'ournal names, can be
found here" http"IIlibrar).caltech.eduIreferenceIabbre4iationsI.
Dord ma) tr) to automaticall) JunderlineK hotlin3s in )our
references, the correct st)le is EB underlining.
&he references are also in > pt., but that section ;see Section <? is
ragged right. .eferences should be published materials
accessible to the public. Internal technical reports ma) be cited
onl) if the) are easil) accessible ;i.e. )ou can gi4e the address to
obtain the report within )our citation? and ma) be obtained b)
an) reader. Proprietar) information ma) not be cited. Pri4ate
communications should be ac3nowledged, not referenced ;e.g.,
G.obertson, personal communication!H?.
)!5 Page #umbering6 7eaders and .ooters
Do not include headers, footers or page numbers in )our
submission. &hese will be added when the publications are
assembled.
/! ."G%R'S8CAPT"$#S
Place &ablesI$iguresIImages in te(t as close to the reference as
possible ;see $igure +?. It ma) e(tend across both columns to a
ma(imum width of +<.<8 cm ;<H?.
+
If necessar), )ou ma) place some address information in a
footnote, or in a named section at the end of )our paper.
Conference10, Month +%7, 7@+@, Cit), State, Countr).
Cop)right 7@+@ ACM +5:8++35@@@5@I@@I@@+@ LM+:.@@.
Permission to ma3e digital or hard copies of all or part of this wor3 for
personal or classroom use is granted without fee pro4ided that copies are
not made or distributed for profit or commercial ad4antage and that copies
bear this notice and the full citation on the first page. &o cop) otherwise, or
republish, to post on ser4ers or to redistribute to lists, re6uires prior specific
permission andIor a fee.
Captions should be &imes Eew .oman >5point bold. &he)
should be numbered ;e.g., G&able +H or G$igure 7H?, please note
that the word for &able and $igure are spelled out. $igureKs
captions should be centered beneath the image or picture, and
&able captions should be centered abo4e the table bod).
3! S'CT"$#S
&he heading of a section should be in &imes Eew .oman +75
point bold in all5capitals flush left with an additional ,5points of
white space abo4e the section head. Sections and subse6uent
sub5 sections should be numbered and flush left. $or a section
head and a subsection head together ;such as Section 3 and
subsection 3.+?, use no additional space abo4e the subsection
head.
3! Subsections
&he heading of subsections should be in &imes Eew .oman +75
point bold with onl) the initial letters capitali0ed. ;Eote" $or
subsections and subsubsections, a word li3e the or a is not
capitali0ed unless it is the first word of the header.?
5.1.1 Subsubsections
&he heading for subsubsections should be in &imes Eew .oman
++5point italic with initial letters capitali0ed and ,5points of
white space abo4e the subsubsection head.
5.1.1.1 Subsubsections
&he heading for subsubsections should be in &imes Eew .oman
++5point italic with initial letters capitali0ed.
5.1.1.2 Subsubsections
&he heading for subsubsections should be in &imes Eew .oman
++5point italic with initial letters capitali0ed.
5! ACK#$9L'DG:'#TS
Bur than3s to ACM SIGC/I for allowing us to modif) templates
the) had de4eloped.
;! R'.'R'#C'S
+! Nowman, M., Debra), S. 2., and Peterson, #. #. +>>3.
.easoning about naming s)stems. ACM Trans. ro!ram.
"an!. Syst. +:, : ;Eo4. +>>3?, <>:587:. DBIO
http"IIdoi.acm.orgI+@.++A:I+,+A,8.+,+A<.
7! Ding, D. and Marchionini, G. +>><. A Study on #ideo
$ro%sin! Strate!ies. &echnical .eport. Fni4ersit) of
Mar)land at College Par3.
3! $rPhlich, N. and Plate, Q. 7@@@. &he cubic mouse" a new
de4ice for three5dimensional input. In roceedin!s of the
S&'C(& Conference on (uman )actors in Computin!
Systems ;&he /ague, &he Eetherlands, April @+ 5 @,, 7@@@?.
C/I C@@. ACM, Eew *or3, E*, :7,5:3+. DBIO
http"IIdoi.acm.orgI+@.++A:I337@A@.337A>+.
A! &a4el, P. 7@@<. Modelin! and Simulation *esi!n. A2
Peters #td., Eatic3, MA.
:! Sannella, M. Q. +>>A. Constraint Satisfaction and
*ebu!!in! for &nteracti+e ,ser &nterfaces. Doctoral &hesis.
FMI Brder Eumber" FMI Brder Eo. GAR>:5@>3>8.,
Fni4ersit) of Dashington.
,! $orman, G. 7@@3. An e(tensi4e empirical stud) of feature
selection metrics for te(t classification. -. Mach. "earn.
.es. 3 ;Mar. 7@@3?, +78>5+3@:.
<! Nrown, #. D., /ua, /., and Gao, C. 7@@3. A widget
framewor3 for augmented interaction in SCAP-. In
roceedin!s of the 1/th Annual ACM Symposium on ,ser
&nterface Soft%are and Technolo!y ;1ancou4er, Canada,
Eo4ember @7 5 @:, 7@@3?. FIS& C@3. ACM, Eew *or3, E*,
+5+@. DBIO http"IIdoi.acm.orgI+@.++A:I>,A,>,.>,A,><.
8! *u, *. &. and #au, M. $. 7@@,. A comparison of MCIDC,
MFMCF& and se4eral other co4erage criteria for logical
decisions. -. Syst. Soft%. <>, : ;Ma). 7@@,?, :<<5:>@. DBIO
http"IId(.doi.orgI+@.+@+,I'.'ss.7@@:.@:.@3@.
>! Spector, A. S. +>8>. Achie4ing application re6uirements. In
*istributed Systems, S. Mullender, -d. ACM Press $rontier
Series. ACM, Eew *or3, E*, +>533. DBIO
http"IIdoi.acm.orgI+@.++A:I>@A+<.>@<38.
Columns on Last Page Should Be Made As Close As
Possible to Equal Length
.igure ! "nsert caption to place caption below 4igure!
!