ACoLC WSCPL2018: Annual Community of Learning Conference 2018 PDC Hall Mombasa, Kenya, June 13-20, 2018 |
Submission link | https://easychair.org/conferences/?conf=acolcwscpl2018 |
Abstract registration deadline | June 4, 2018 |
Submission deadline | June 4, 2018 |
Full Paper | June 11, 2018 |
Presentation | June 11, 2018 |
The conference is aimed to allow faculty to share their learning outcomes during the continuous professional learning sessions face to face after three weeks supported by weekly programme and school level meeting where they were investigating on inquiry-based learning models. The faculty worked in teams and inquired in 10 different focus areas namely, Assessment, Conceptual Understanding, Differentiation, Implementation, Inquiry Models, Linkages, Mentorship, Resources, Roles, and Questions and Concepts. A total of 25 presentations will be made in the sub areas under the focused areas.
Submission Guidelines
All papers must be original and not simultaneously submitted to another journal or conference. The following paper categories are welcome:
1. Abstract-
Because on-line search databases typically contain only abstracts, it is vital to write a complete but concise description of your work to entice potential readers into obtaining a copy of the full paper. This article describes how to write a good computer architecture abstract for both conference and journal papers. Writers should follow a checklist consisting of: motivation, problem statement, approach, results, and conclusions. Following this checklist should increase the chance of people taking the time to obtain and read your complete paper.
Introduction
Now that the use of on-line publication databases is prevalent, writing a really good abstract has become even more important than it was a decade ago. Abstracts have always served the function of "selling" your work. But now, instead of merely convincing the reader to keep reading the rest of the attached paper, an abstract must convince the reader to leave the comfort of an office and go hunt down a copy of the article from a library (or worse, obtain one after a long wait through inter-library loan). In a business context, an "executive summary" is often the only piece of a report read by the people who matter; and it should be similar in content if not tone to a journal paper abstract.
Checklist: Parts of an Abstract
Despite the fact that an abstract is quite brief, it must do almost as much work as the multi-page paper that follows it. In a computer architecture paper, this means that it should in most cases include the following sections. Each section is typically a single sentence, although there is room for creativity. In particular, the parts may be merged or spread among a set of sentences. Use the following as a checklist for your next abstract:
-
Motivation:
Why do we care about the problem and the results? If the problem isn't obviously "interesting" it might be better to put motivation first; but if your work is incremental progress on a problem that is widely recognized as important, then it is probably better to put the problem statement first to indicate which piece of the larger problem you are breaking off to work on. This section should include the importance of your work, the difficulty of the area, and the impact it might have if successful. -
Problem statement:
What problem are you trying to solve? What is the scope of your work (a generalized approach, or for a specific situation)? Be careful not to use too much jargon. In some cases it is appropriate to put the problem statement before the motivation, but usually this only works if most readers already understand why the problem is important. -
Approach:
How did you go about solving or making progress on the problem? Did you use simulation, analytic models, prototype construction, or analysis of field data for an actual product? What was the extent of your work (did you look at one application program or a hundred programs in twenty different programming languages?) What important variables did you control, ignore, or measure? -
Results:
What's the answer? Specifically, most good computer architecture papers conclude that something is so many percent faster, cheaper, smaller, or otherwise better than something else. Put the result there, in numbers. Avoid vague, hand-waving results such as "very", "small", or "significant." If you must be vague, you are only given license to do so when you can talk about orders-of-magnitude improvement. There is a tension here in that you should not provide numbers that can be easily misinterpreted, but on the other hand you don't have room for all the caveats. -
Conclusions:
What are the implications of your answer? Is it going to change the world (unlikely), be a significant "win", be a nice hack, or simply serve as a road sign indicating that this path is a waste of time (all of the previous results are useful). Are your results general, potentially generalizable, or specific to a particular case? -
Other Considerations
An abstract must be a fully self-contained, capsule description of the paper. It can't assume (or attempt to provoke) the reader into flipping through looking for an explanation of what is meant by some vague statement. It must make sense all by itself. Some points to consider include:
-
Meet the word count limitation. If your abstract runs too long, either it will be rejected or someone will take a chainsaw to it to get it down to size. Your purposes will be better served by doing the difficult task of cutting yourself, rather than leaving it to someone else who might be more interested in meeting size restrictions than in representing your efforts in the best possible manner. An abstract word limit of 150 to 200 words is common.
-
Any major restrictions or limitations on the results should be stated, if only by using "weasel-words" such as "might", "could", "may", and "seem".
-
Think of a half-dozen search phrases and keywords that people looking for your work might use. Be sure that those exact phrases appear in your abstract, so that they will turn up at the top of a search result listing.
-
Usually the context of a paper is set by the publication it appears in (for example, IEEE Computer magazine's articles are generally about computer technology). But, if your paper appears in a somewhat un-traditional venue, be sure to include in the problem statement the domain or topic area that it is really applicable to.
-
Some publications request "keywords". These have two purposes. They are used to facilitate keyword index searches, which are greatly reduced in importance now that on-line abstract text searching is commonly used. However, they are also used to assign papers to review committees or editors, which can be extremely important to your fate. So make sure that the keywords you pick make assigning your paper to a review category obvious (for example, if there is a list of conference topics, use your chosen topic area as one of the keyword tuples).
-
Conclusion
Writing an efficient abstract is hard work, but will repay you with increased impact on the world by enticing people to read your publications. Make sure that all the components of a good abstract are included in the next one you write.
2. Full papers (Optional)
-
Main paper title
Paper sub-title
Author name
-
Affiliation, Institution, Country, Email
Abstract. No more than 300 words.
Keywords. No more than 5.
1 Title section one
First paragraph.
Second paragraph.
Make sure references are shown as numbers in the text in this form [1].
2 Title section two
First paragraph.
Second paragraph.
2.1 Sub-heading
First paragraph.
Second paragraph.
3 Title section three
First paragraph.
Second paragraph.
-
4 Title section four
-
First paragraph.
Second paragraph.
Table 1. Font sizes of headings. Table captions should always be positioned above the tables.
5 Title section five
First paragraph.
Second paragraph.
6 Title section six
First paragraph.
Second paragraph.
7 Title section seven
First paragraph.
Second paragraph.
Acknowledgments. The author would like to thank xxx.
References
-
Raffe, D.: Young People Not in Education, Employment or Training. Centre for Educational Sociology, University of Edinburgh (2003)
-
Commission of the European Communities: Commission Staff Working Paper: Progress towards the Lisbon Objectives in Education and Training. Commission of the European Communities, Brussels (2005)
-
Passey, D.: First no choice, then some choice, and finally overload: A reasonable data management evolution? In Tatnall, A., Visscher, A., Finegan, A., O’Mahoney, C. (eds.) Evolution of Information Technology in Educational Management. Springer, New York, NY (2009)
-
Kelder, S.H., Perry, C.L., Klepp, K.-I, Lytle, L.L.: Longitudinal tracking of adolescent smoking, physical activity, and food choice behaviors. American Journal of Public Health. 84(7), 1121-1126 (1994)
3. Posters (Optional)
What is a Research Poster?
Posters are widely used in the academic community, and most conferences include poster presentations in their program. Research posters summarize information or research concisely and attractively to help publicize it and generate discussion.
The poster is usually a mixture of a brief text mixed with tables, graphs, pictures, and other presentation formats. At a conference, the researcher stands by the poster display while other participants can come and view the presentation and interact with the author.
What makes a good poster?
-
Important information should be readable from about 10 feet away
-
Title is short and draws interest
-
Word count of about 300 to 800 words
-
Text is clear and to the point
-
Use of bullets, numbering, and headlines make it easy to read
-
Effective use of graphics, color and fonts
-
Consistent and clean layout
-
Includes acknowledgments, your name and institutional affiliation
Where do I begin?
Answer these three questions:
-
What is the most important/interesting/astounding finding from my research project?
-
How can I visually share my research with conference attendees? Should I use charts, graphs, photos, images?
-
What kind of information can I convey during my talk that will complement my poster?
What software can I use to make a poster?
PowerPoint: A popular, easy-to-use option. It is part of Microsoft Office package and is available on the library computers in rooms LC337 and LC336. (Advice for creating a poster with PowerPoint).
Adobe Illustrator, Photoshop and InDesign: Feature-rich professional software that is good for posters including lots of high-resolution images, but they are more complex and expensive.
Open Source Alternatives: OpenOffice in the free alternative to MS Office (Impress is its PowerPoint alternative). Inkscape and Gimp are alternatives to Adobe products. For charts and diagrams try Gliffy or Lovely Charts. A complete list of free graphics software.
A sample of a poorly designed poster
Committees
Program Committee
-
PDC Team
Orgnising committee
-
Academic Commitee
Contact
All questions about submissions should be emailed to gioko@agakhanacademies.org