RESEARCH PAPER #1 CHECKLIST: Here's a checklist that you should use in the writing of your first Research Paper for the USC SAE 574 Class. This is what I use in grading papers. This isn't meant to indicate a strict FORMAT or an OUTLINE-- it's just a checklist. Please refer to the class website and lecture notes for detailed instructions on formatting your paper. ( ) Title Page? ( ) Abstract (with a brief biography)? ( ) Introduction or Background or History? ( ) A general description of the system? ( ) Analysis using Lectures 1 through 5b? ( ) A summary or conclusion? ( ) References or bibliography or footnotes? Analysis to be performed from Lecture #1: ( ) What benefits does the system provide to its users, due to its net-centric design? (At least one paragraph) Analysis to be performed from Lecture #2: ( ) What is the fundamental organization of the network? E.g. Fixed users of a Fixed network? Mobile users of a Mobile Network? A MANet? (At least one paragraph, and at least one top-level figure) ( ) HOW does the system support user collaboration? (At least one paragraph) Analysis to be performed from Lecture #3 & 4: ( ) What is the architecture of at least ONE sample node in the system, in terms of the OSI 7-layer or TCP/IP 4-layer (or other) reference models? (At least one paragraph and at least one top-level figure for at least one major node) Analysis to be performed from Lecture #4: ( ) What capability has been provided in the system's architecture to handle growth, or unexpected ways of using the system, or ability to evolve to meet user needs? (At least one paragraph) Analysis to be provided from Lecture #5a: ( ) What assured availability steps have been included in the system's design? E.g. fault tolerance, redundant/backup items, diagnostics/testability, maintainability, etc.? (At least one paragraph and at least one top-level figure) ( ) What are the failure modes and effects with criticality analysis and mitigation recommendations for at least one major component (hardware or software) in the system? (At least one paragraph with a top-level FMECA diagram in a format similar to that in Lecture 5a-- at least one hardware or software or system component, with at least six rows sorted into order of descending risk, and at least ONE risk item "below the line") ( ) What SYSTEM integrity steps have been (or should be) included in the system's design, such as "trusted" hardware, software, processes (e.g. ISO 9001), people (e.g. background checks), etc.? (At least one paragraph, and you may have to recommend integrity steps if the system doesn't already have them) Analysis to be provided from Lecture #5b: ( ) What DATA integrity steps have been (or should be) included in the system's design, such as checksums or CRC in data storage or transmission? (At least one paragraph and at least one top-level figure) ( ) What authentication measures have been (or should be) included in the system's design to ensure that only authorized people or systems can use the system? (At least one paragraph and at least one top-level figure) ( ) What confidentiality measures have been (or should be) included in the system's design to ensure that unauthorized people or systems cannot access or modify critical data used in the system? (At least one paragraph and at least one top-level figure) ( ) What non-repudiation measures have been (or should be) included in the system's design to ensure that at least an audit trail is kept of access to (or modification of) critical data used in the system? (At least one paragraph) ( ) What is the security management method provided by the system's design (e.g. Enclave Security vs. Defense-In-Depth) in terms of the acceptable level of RISK of not achieving the Information Assurance steps described in all of the above? (At least one paragraph) What if you can’t find information about one or more of the above items on the checklist? DO NOT SKIP THAT ANALYSIS, and assume that it is not applicable! Such omission will significantly impact your grade. You may need to recommend what should be (or could be) added to the system, and then analyze that recommendation. My intent in providing you with this list is to HELP you in accomplishing a comprehensive analysis of your chosen topic, and to provide some insight into the kind of technical "meat" that I'm looking for in considering your paper's grade. N.B. very few papers are worthy of an “A” grade in this class unless they EXCEED most of the requirements given in the Research Paper Checklist (i.e. have more that the minimum required). The checklist descriptions represent the minimum requirements for a passing grade (“B”) in the class. And to deserve an “A+” grade, a paper would have to be of sufficient quality and depth of analysis that it could be used as a Guest Lecture for this class. One of the metrics used to grade papers is the volume of analysis, which should be at least 15 pages of analysis in terms of 12 point text in Times New Roman font, single spaced, with 1" top and bottom margins and 1-1/4" left and right margins (and figures deleted unless they specifically contribute to, or are part of the analysis). HINTS! Common mistakes that students make include: * No title page. Believe it or not, this happens! In many of the USC Distance Education Network (DEN) classes (but not this one), students are required to submit their papers via e-mail or a fax to the DEN, rather than online via DEN Assignments. In such cases students may be used to filling out a DEN submittal form. The DEN submittal form is not a title page! * No abstract, or missing a biography in the abstract. Yes, you have to both provide an abstract for approval AND place that abstract on the second page of your paper. If you have adjusted your abstract after obtaining approval of your chosen topic, then the ADJUSTED abstract should be used in the paper. * No clear linkage of analysis to the checklist. * Confusing SYSTEM vs. DATA Integrity. * Describing “User Support” rather than “User Collaboration”. * FMECA missing columns, or missing at last one low-risk item "below the line", or table not sorted in order of descending risk. * Missing one (or more) of the other items on the checklist. * Analysis text provided, but without a required diagram (see checklist above for required diagrams). * Figures(s) without a detailed explanation of content. You should not succumb to the temptation of filling in blank space or attempting to increase the length of your paper with meaningless figures (including diagrams, graphics, artwork, and tables). All figures should have a reference in your text (a figure number, a table number, etc.). And your text should include at least one paragraph that explains the figure in terms of the analysis that you’re providing. In short, everything in your paper should be relevant. * Limited depth of analysis (paper too short: less than 20 pages in total or less than 15 pages of detailed analyses). For example, a 50 page paper filled with detailed technical descriptions and fancy color figures/pictures of the system (but only 5 pages of net-centric analysis via the checklist above) will not receive a good grade. * No (or improper) references, footnotes, or bibliography. Surely you must have used something as a reference in the development of your paper, even if you are a “world expert” on your chosen topic! And please remember to properly cite the SAE 574 class lectures if you use material from those lectures in your paper. Remember also that too many references to uncontrolled Internet sites may detract from your paper’s grade. * Improper citations for quoted text or copied artwork. Yes, you can “borrow” artwork or a figure or table from another source, but you must properly cite that source! And yes, you can include direct verbiage from another source, but you must properly designate those words in quotations and properly cite that source! (This includes the case where you are the author of the “other source”!) Failure to properly reference copied text will be treated as a violation of academic integrity! * Excessive amount of quoted text. This includes large amounts of text quoted from papers that you wrote for a different class! * Speling errorz. Please remember to do a “Spell Check” before submitting your paper. If a quoted source includes a spelling error, simple place the designation (sic) after that word to show that you weren’t the one that made the error. Also remember that most spell-checkers are not a substitute for good editing (for example, deciding whether “threw” or “through” is the correct word in a given context). Ken Cureton cureton@usc.edu