Total online: 1
|« May 2020 »|
| || || || || ||1||2|
|A HEARTY WELCOME TO MA VISITORS 4R ENTERIN MA BLOG
THNX 4R VISITIN MA BLOG||
|Welcome Guest | RSS|
Main | Registration | Login
Main » LATEST TECHNICAL IMPORTANT NEWS
Writing a Technical white paper is an art. You need to follow certain rules, maintain certain dos and don’ts when writing a Technical white paper for presentation.
Give a catchy title
Innovations are being made everyday, and thousands of Technical white papers are published. If you want your Technical white paper to be considered better than others, you have to make it appealing to the reviewers/judges.
Title, is something that lures prospective reviewers/judges into opening your white paper. Hence, it is imperative to give a suitable and eye catching title.
Make the title self explanatory, so the reader knows what to expect in the paper. Your title should also be effective, in separating your ideas from the rest.
Engage your Audience
Always remember; you are writing the Technical white paper for a certain audience. You, have to first know who these audiences are, and what they are expecting.
You have to engage all your readers equally, by making your white paper empathetic. Make a brief description of the problems faced and how it can be easily resolved using your ideas. Then, proceed to give the technical details.
You can also detail some parts of the technical aspects in points. This makes the Technical white paper look short, but complete. You would have all the readers read the white paper, till the end.
A Technical white paper, written in such a manner is successful in proving three points to the readers.
1. You understand the customers’ problems.
2. A good description of your technology.
3. Gives enough explanation, as to how your product is the best.
Your content has to be short and brief. A brief, but targeted description would suffice and be read completely.
Organize your content neatly, making clear subdivisions and paragraphs so that one paragraph opens into the next.
You may follow the traditional formula to tell your readers what they are going to read and, explaining the product, and repeat what you have already explained.
There are standard formats to write Technical white papers. You have to follow these to make your white paper more effective and readable by scholars and other academicians, who may have influence in the propagation.
Introduction – this has to be a concise and not more than one or two paragraph. You have to briefly explain about your product or technology. Remember, there are people who would just read the introduction to know about the entire contents.
The problem faced – Give an overview of the problem faced.
How your product solves it – explain what your product does to solve their problem.
Show off your product - give the technological explanations here.
Conclusion – briefly, repeat all that you have already explained.
Use Real Examples
Make your examples speak on their own, by presenting how companies and people can be benefited from your technology. Your product would sound more real and worthy, when projected in this manner.
Use Charts and Graphs
Break the monotony of your Technical white paper by including charts and graphs wherever necessary.
Writing a good Technical white paper is not an easy task, but can be learnt and excelled with practice. You need to have a deep understanding of the product and its technology so that you can convince the readers.
This is a new post. it is unique from the other post of this blog because it is not that technical post or a paper presentation, book link or a engineering stuff. It is more like a soft skill development lesson. Yes! yes! yes! i know what you think. No time for these articles!?
Engineering is a study were we focus our minds for hours. we are more into concepts and ideas for most of our times. So, I just wanted share this small piece of tip for my readers.
When ever you see a new and interesting titled article, you start reading it with much interest and willingness but as you gradually start understanding the content you think you are done and start feeling bored. Then suddenly your facebook wall seems more interesting to you and you convince yourself that you've understood the article (This happens a lot for me :p), we tend to stop reading that and assume we understood what the poor author tries to convey. Yes! you'd have actually understood it but this causes some huge set backs for our parameters.
Well then why do i want you continue reading that article??
- An increasing number of experts think skimming through a article make us more stupider and say it's time to slow down.
- The interpretation of different writers might be different, towards various issues and concepts. feeling bored and getting lost can happen sometimes but still holding the patience can provide you fruitful results.
- Reading an article completely can give you enormous amount of courage and confidence to share the topic in your group at colleges or work places.
- When you develop the habit of reading the articles completely, you can be a thought
Read more »
|Guidelines for 8.5x11-inch Proceedings Manuscripts
The abstract is to be in fully-justified italicized text, at the top of the left-hand column as it is here, below the author information. Use the word "Abstract” as the title, in 12-point Times, boldface type, centered relative to the column, initially capitalized. The abstract is to be in 10-point, single-spaced type, and may be up to 3 in. (7.62 cm) long. Leave two blank lines after the abstract, then begin the main text. All manuscripts must be in English.
These guidelines include complete descriptions of the fonts, spacing, and related information for producing your proceedings manuscripts.
A zip-file of this sample manuscript is also available (http://mecha.ee.boun.edu.tr/word2.zip), which you can use as a template to prepare your paper.
Please note that your paper should normally be limited to six pages. A maximum of two additional pages can be used subject to a charge of $100/page.
2. Formatting your paper
All printed material, including text, illustrations, and charts, must be kept within a print area of 6-7/8 inches (17.5 cm) wide by 8-7/8 inches (22.54 cm) high. Do not write or print anything outside the print area. All text must be in a two-column format. Columns are to be 3-1/4 inches (8.25 cm) wide, with a 5/16 inch (0.8 cm) space between them. Text must be fully justified.
3. Main title
The main title (on the first page) should begin 1-3/8 inches (3.49 cm) from the top edge of the page, centered, and in Times 14-point, boldface type. Capitalize the first letter of nouns, pronouns, verbs, adjectives, and adverbs; do not capitalize articles, coordinate conjunctions, or prepositions (unless the title begins with such a word). Leave two blank lines after the title.
4. Author name(s) and affiliation(s)
Author names and affiliations are to be centered beneath the title and printed in Times 12-point, non-boldface type. Multiple authors may be shown in a two- or three-column format, with their affiliations below their respective names. Affiliations are centered below each author name, italicized, not bold. Include e-mail addresses if possible. Follow the author information by two blank lines before main text.
5. Second and following pages
The second and following pages should begin 1.0 inch (2.54 cm) from the top edge. On all pages, the bottom margin should be 1-1/8 inches (2.86 cm) from the bottom edge of the page for 8.5 x 11-inch paper; for A4 paper, approximately 1-5/8 inches (4.13 cm) from the bottom edge of the page.
6. Type-style and fonts
Wherever Times is specified, Times Roman, or New Times Roman may be used. If neither is available on your word processor, please use the font closest in appearance to Times that you have access to. Please avoid using bit-mapped fonts if possible. True-Type 1 fonts are preferred.
7. Main text
Type your main text in 10-point Times, single-spaced. Do not use double-spacing. All paragraphs should be indented 1 pica (approximately 1/6- or 0.17-inch or 0.422 cm). Be sure your text is fully justified—that is, flush left and flush right. Please do not place any additional blank lines between paragraphs.
Figure and table captions should be 10-point Helvetica (or a similar sans-serif font), boldface. Callouts should be 9-point Helvetica, non-boldface. Initially capitalize only the first word of each figure caption and table title. Figures and tables must be numbered separately. For example: "Figure 1. Database contexts”, "Table 1. Input data”. Figure captions are to be below the figures. Table titles are to be centered above the tables.
8. First-order headings
For example, "1. Introduction”, should be Times 12-point boldface, initially capitalized, flush left, with one blank line before, and one blank line after. Use a period (".”) after the heading number, not a colon.
8.1. Second-order headings
As in this heading, they should be Times 11-point boldface, initially capitalized, flush left, with one blank line before, and one after.
8.1.1. Third-order headings. Third-order headings, as in this paragraph, are discouraged. However, if you must use them, use 10-point Times, boldface, initially capitalized, flush left, preceded by one blank line, followed by a period and your text on the same line.
9. Printing your paper
Print your properly-formatted text on high-quality, 8.5 x 11-inch white printer paper. A4 paper is also acceptable, but please leave the extra 0.5 inch (1.27 cm) at the BOTTOM of the page. If the
Read more »
Java Courses full tutorial
I found this tutorial videos to be annoying
for most of the impatient engineering students out there, from the feed back i received. But still i strongly recommend you guys to download
this stuff, as soon as possible because i found it to be extremely useful for the beginners and amateurs to built some strong base in the booming technology.
English | H264 729kbps | 1280×720 25fps | MP3 117kbps | 2.83 GB
Genre: Video Training
This videos includes:
- Java basics
- Java Intermediate
- Java game development
DOWNLOAD THIS :
Are you feeling bad that you are not good in JAVA and ORACLE?
No problem! says the future of Information technology. Yes, you believe it? your highschool
and college syllabus
C, C++ are going to get their driving seats sooner. There once was a period in which the languages
(C,C++) seemed to die slowly and get replaced by languages like JAVA, RUBY and JAVA SCRIPT. But now the future of these languages looks brighter than any time in the past.
When i read this article in one my favorite blogs, i was soo glad and enthused about the reasons quoted.
- The support for lambdas and closures in the newest C++ standard.
- The uncertainty surrounding Java following Oracle's acquisition of Sun, and the uncertainty around .NET as Microsoft seems to be de-prioritizing it inWindows 8.
- We can't see Microsoft deprecating C# anytime soon, but the Visual C++ team is hard at work and C++ is clearly going to be central to Microsoft's developer strategy in the future.
Read more »
Only the most hardcore puzzle-solvers ever go beyond the standard 3x3x3 Rubik's cube, attempting much larger ones such as those pictured on the right. Now an algorithm has been developed that can solve a Rubik's cube of any size. It might offer clues to humans trying to deal with these tricky beasts.
Rubik's cube science got a boost last year when a team led by programmer Tomas Rokicki of Palo Alto, California, showed that even the most scrambled standard Rubik's cube can be solved in 20 moves or less. That feat was a big deal: the figure has been dubbed "God's number", the assumption being that the Almighty couldn't solve it faster. But that result didn't shed light on the monster cubes.
So Erik Demaine, a computer scientist at the Massachusetts Institute of Technology, set out to find a general algorithm for solving a cube with any side-length – of n squares.
The new approach differs from that of Rokicki's. The latter used a "brute force" method, relying on computers borrowed from Google to check all 43 quintillion possible solutions, but Demaine says doing the same for larger cubes would be impossible. "You can't solve all values of n with computational search," he explains.
Instead, Demaine's team started by looking at a method Rubik's cube enthusiasts commonly use to quickly solve the puzzle. Essentially, you try to move a single square, or "cubie", into the desired position while leaving the rest of the cube as unchanged as possible. Because it's not possible to move a single cubie without disturbing others, this method is time-consuming, requiring a number of moves that is proportional to n2.
Demaine and his colleagues found a short-cut. Each cubie has a particular path that will place it in the correct position. His algorithm looks for cubies that all need to go in the same direction, then moves them at the same time. "We found that instead of solving one cubie at a time, you can parallelise that process and solve several," Demaine says.
Grouping cubies with similar paths reduces the number of moves required by a factor of around log n. This means that the maximum number of moves that will ever be required for a cube of side n is proportional to n
Read more »
The genetic code common to all life is not set in stone. We can change it at its most fundamental level for our own purposes. Genetic engineers have invented a new way to quickly, precisely and thoroughly rewrite the genome of living bacteria.
The technique could make drug-producing bacteria immune to viruses, prevent laboratory engineered organisms from genetically contaminating wildlife and enable scientists to construct proteins that do not exist in nature.
Farren Isaacs of Yale University led the team that this week proves it is possible to make numerous and very precise changes in the genome of living cells. "In the process we are recoding organisms that could have completely new functionality."
"I think it's a tour de force, one of the top 10 papers of the year," saysFrederick Blattner of the University of Wisconsin-Madison, who was not involved in the study. "Even though the genes are essential, they can be altered."
Ultimately, the study paves the way for re-coding the universal genetic code.
Stop sign swap
Isaacs and his colleagues systematically replaced one three-letter sequence in the genome of Escherichia coli with another.
Three-letter genetic sequences are known as codons, and they can either code for an amino acid – the building blocks of proteins – or act as stop signals. A cell's internal machinery reads copies of the genome, and as it goes along it links the corresponding amino acids together into protein strings until it reaches a stop codon.
The researchers sifted through the E. coli genome and identified all 314 TAG stop codons. They then designed fragments of single-stranded DNA that, with the assistance of viral enzymes, would replace the TAG stop codons with TAA, another stop codon.
Isaacs submerged a billion E. coli cells in pools of water brimming with the bits of DNA and viral enzymes, and zapped the mixture with electricity, opening pores in the bacteria's cell membranes for the DNA to pass through. The process is known as multiplex automated genome engineering, or MAGE.
Isaacs then isolated 32 strains from the mixture, each of which had around 10 TAA codons instead of TAG codons at different points in the genome. The next challenge was to combine these partially rewritten genomes into a single genome with 314 TAA stop codons and no TAG codons. How did they do it? Think promiscuous pizzas.
Read more »