BUSCA

Links Patrocinados



Buscar por Título
   A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z


Write An Abstract Today Ii
(CGS)

Publicidade
Write an Abstract Today II
(Draft 10/26/05)
[CGS] C.G.Subramaniam, Hyd ? AP / India


Checklist: Parts of an Abstract



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?

Don't miss to check
Write an Abstract Today III & IV...Have a Blessed day....CGS...



Resumos Relacionados


- Write An Abstract Today...i

- Write An Abstract Today...

- Write An Abstract Today - Iii

- How To Write A Good Abstract

- Win Money - How Write Abstracts



Passei.com.br | Biografias

FACEBOOK


PUBLICIDADE




encyclopedia