BBPRASanth


SUBMITTED BY: BBPrasanth123

DATE: June 13, 2016, 10:31 a.m.

FORMAT: Text only

SIZE: 4.2 kB

HITS: 4747

  1. bhavani M. J. 1994. Constraint Satisfaction and Debugging for Interactive User Interfaces. Doctoral Thesis. UMI Order Number: UMI Order No. GAX95-09398., University of Washington.
  2. Forman, G. 2003. An extensive empirical study of feature selection metrics for text classification. J. Mach. Learn. Res. 3 (Mar. 2003), 1289-1305.
  3. Brown, L. D., Hua, H., and Gao, C. 2003. A widget framework for augmented interaction in SCAPE. In Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology (Vancouver, Canada, November 02 - 05, 2003). UIST '03. ACM, New York, NY, 1-10. DOI=  HYPERLINK "http://doi.acm.org/10.1145/964696.964697" http://doi.acm.org/10.1145/964696.964697.
  4. Yu, Y. T. and Lau, M. F. 2006. A comparison of MC/DC, MUMCUT and several other coverage criteria for logical decisions. J. Syst. Softw. 79, 5 (May. 2006), 577-590. DOI=  HYPERLINK "http://dx.doi.org/10.1016/j.jss.2005.05.030" http://dx.doi.org/10.1016/j.jss.2005.05.030.
  5. Spector, A. Z. 1989. Achieving application requirements. In Distributed Systems, S. Mullender, Ed. ACM Press Frontier Series. ACM, New York, NY, 19-33. DOI=  HYPERLINK "http://doi.acm.org/10.1145/90417.90738" http://doi.acm.org/10.1145/90417.90738.
  6. Columns on Last Page Should Be Made As Close As Possible to Equal Length
  7. 1st Author
  8. 1st author's affiliation 1st line of address 2nd line of address Telephone number, incl. country code
  9. 1st author's email address
  10. 2nd Author
  11. 2nd author's affiliation 1st line of address 2nd line of address Telephone number, incl. country code
  12. 2nd E-mail
  13. 3rd Author
  14. 3rd author's affiliation 1st line of address 2nd line of address Telephone number, incl. country code
  15. 3rd E-mail
  16. ABSTRACT
  17. In this paper, we describe the formatting guidelines for ACM SIG Proceedings.
  18. Categories and Subject Descriptors
  19. D.3.3 [Programming Languages]: Language Contructs and Features – abstract data types, polymorphism, control structures. This is just an example, please use the correct category and subject descriptors for your submission. The ACM Computing Classification Scheme:  HYPERLINK "http://www.acm.org/class/1998/" http://www.acm.org/class/1998/
  20. General Terms
  21. Your general terms must be any of the following 16 designated terms: Algorithms, Management, Measurement, Documentation, Performance, Design, Economics, Reliability, Experimentation, Security, Human Factors, Standardization, Languages, Theory, Legal Aspects, Verification.
  22. Keywords
  23. Keywords are your own designated keywords.
  24. INTRODUCTION
  25. The proceedings are the records of the conference. ACM hopes to give these conference by-products a single, high-quality appearance. To do this, we ask that authors follow some simple guidelines. In essence, we ask you to make your paper look exactly like this document. The easiest way to do this is simply to down-load a template from [2], and replace the content with your own material.
  26. PAGE SIZE
  27. All material on each page should fit within a rectangle of 18 x 23.5 cm (7" x 9.25"), centered on the page, beginning 1.9 cm (0.75") from the top of the page and ending with 2.54 cm (1") from the bottom. The right and left margins should be 1.9 cm (.75”). The text should be in two 8.45 cm (3.33") columns with a .83 cm (.33") gutter.
  28. TYPESET TEXT
  29. Normal or Body Text
  30. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.
  31. Conference’10, Month 1–2, 2010, City, State, Country.
  32. Copyright 2010 ACM 1-58113-000-0/00/0010…$10.00.
  33. Please use a 9-point Times Roman font, or other Roman font with serifs, as close as possible in appearance to Times Roman in which these guidelines have been set. The goal is to have a 9-point text, as you see here. Please use sans-serif or non-proportional fonts only for special purposes, such as distinguishing source code text. I

comments powered by Disqus