Editorial Guidelines

Embedded Edge Online is a technical publication for development teams designing a wide range of systems incorporating DSP technology and products. It is published jointly by Texas Instruments, Inc. and CMP Media LLC. Access to the editorial sections is open to all TI DSP Third Party Network Members based on the space available.

Several editorial opportunities are available: news, product announcements, and technical articles. The news and product sections are staff-written, based on press releases sent to the editor or on private briefings. Technical articles are generally contributed but may be staff-written.

News and Product Announcements
Embedded Edge Online contains separate sections for news and new product announcements. These sections consist of brief staff-written items, based on press releases (or in some cases, interviews) from TI and Third Party Network Members. News consists of announcements of events, the creation of new business relationships, key technical or business employee announcements, and brief teasers about a new type of product (i.e., one that uses a new technology, approach, or architecture). Product announcements are typically single-paragraph write-ups with contact information. All press releases should be dated, and product releases should include price and availability. For both news and product announcements, please include a graphic-photo (electronic file, glossy, or slide), screen shot, or logo-whenever possible.

Submit news and product releases to the editor-in-chief, Mike Robinson, at mikerobinson255@earthlink.net. Send glossy photos or slides to him at CMP Media LLC, attn: Mike Robinson, 255 Cabrini Blvd, Suite 5A, New York, NY 10040.

Technical Articles
The magazine's primary purpose is to educate readers and give them practical information that they can use in their own applications or design environments. To do that, the magazine uses a "problem and solution" format, an editorial stance proven to generate high readership in a professional engineering audience. Consequently, the primary focus of Embedded Edge Online's technical articles should be on how to overcome problems encountered frequently during software design or application-for instance, how to develop algorithms more efficiently, how to get the best performance or code density, or how to better understand a software concept or use a software development tool more efficiently.

For example, technical articles might cover the pros and cons of assembly code versus C or C++; the role of data visualization in debugging; advances in algorithm development methodology; how to use TI's Code Composer Studio to design a plug-in application; ten things to avoid during algorithm development; getting the most out of your compilation tools; the role of standards in writing good C code; learning the ABCs of real-time trace; the challenges of real-time debugging; or a programmer's guide to advances in compiler technology. Also, software developers are always looking for tips or tricks. An article might offer tips centering on speeding up performance or using less memory, for example. The tips could come from gurus, wizards, or experienced users in the use of a tool, providing the article takes the reader well beyond the information available.

In addition, case histories might be good candidates for an article, but only if they highlight the technical aspects of one or more problems and their solution. Technical articles may also focus on the use of a particular product, providing the article takes the reader far beyond information published in the product's user manual and collateral material. Such articles should include a specific application as an example, and the solution can't be, in effect, "just use this product." Please keep in mind that articles should not contain marketing or promotional statements.

Finally, tutorials covering new standards or technologies are suitable subjects for articles, as well.

Technical articles are selected on technical merit and reader interest as judged by the chief editor, based on input from Embedded Edge Online's editorial board.

If you'd like to write an article for the magazine, please contact Mike Robinson, at mikerobinson255@earthlink.net, to discuss the topic and approach or to submit an abstract. The next step is to submit a detailed, very specific outline. The third step, if the proposal or abstract and outline are approved, is to write the article to the publication's specifications.

What to Avoid
Avoid blatant product pitches, rabbits out of the hat (add our new product and everything works like magic), success stories substantially lacking in technical content, and "dry labs" (unproven technical approaches or designs). Please do not submit articles to Embedded Edge Online that have already been published or submit articles to more than one publication at once.

Style Guidelines
Don't worry too much about style. Use a conversational tone and communicate one to one as though you were verbally explaining the subject while sitting across the table from the reader. Write simply: Embedded Edge Online's articles should not take an academic tone. Write succinctly: Readers are always pressed for time. Stay on topic and have a specific goal in mind for your article. You can even let the author's personality peek through.

The technical nature of the article topics in Embedded Edge Online makes the subject matter difficult without adding the complexity of pompous university thesisıstyle English. If in doubt, consult Strunk and White's excellent book on the subject, The Elements of Style (a mere 85 pages or so of clean, clear instruction). In the end, all technical articles will be edited for style and length by the editorial staff. If you would like help writing an article, please contact the editor.

Submission Guidelines
All articles should be submitted electronically to the editor either via e-mail or on a PC-compatible floppy or CD ROM (please, no Macintosh disks, TAR tapes, or other unusual magnetic media). Acceptable formats for text files include MS Word, ASCII text, or RTF files.

Generally, an article will contain about 2000 to 2500 words and include three or four graphic elements: figures (block diagrams, flowcharts, screen shots, etc.), stand-alone code listings, tables, and boxed text (sidebars). There's no need for camera-ready graphics, except for screen shots); we redraw all diagrams and charts and set all tables and listings.

Please do not embed graphics or tables in the middle of article submissions. Put graphics in one or more separate files; again we can handle a wide range of binary graphic image formats, such as JPEG or TIFF, but not PDF or BMP files; screen shots should be high-resolution. Put tables at the end of the text file.