Professional Documents
Culture Documents
General Guidelines
• Before proceeding to subject
guidelines, let’s do a quick revision!
HOW TO CREATE • Hit the dash button three times “---”, and then click ENTER
once.
• Never italicize units • Follow the same notations of the textbook for
variables/symbols.
✘ M = 25 kg
✓ M = 25 kg
• Italicize variables everywhere
• Always insert a space
before the units. • Use “and” instead of ampersands (“&”).
✘ PQ = 5cm
✓ PQ = 5 cm • Avoid using shortforms like “L.H.S.”, “RHS”,
“w.r.t.”, ∴ , ∵ and others.
• Do not use “dot”
where you have to
Instead, write out the complete term.
use “mid-dot”.
✓ N · m,
✘ N.m
4
• Make the Debit items appear clear and distinct from the Credit items
• Give a brief narration of the transactions. This narration could be in Italics (depending upon the
textbook style)
• Make a clear mention about transactions that need only Memorandum entries
• Always follow the “Balance column account” format for T-Accounts or the format specific to a textbook.
• Always use the Multiple Step format until and unless a specific format is mentioned in the problem.
10
11
12
14
15
16
• Explain the related concepts / • Use “ChemDraw” for drawing • Use MS Excel to draw
equations wherever necessary. chemical graphs/Tables.
structures/mechanisms.
• If there are multiple approaches • Embed the final graph or table
to solve a problem, state the • Use “Serif Draw Plus” or in your solutions in JPEG/PNG
reason for using the approach equivalent graphic software for format only.
you choose. diagrams.
17
• All chemical formulas, • Write the name of the compound • Always indicate a lone pair
chemical symbols, and units below the structure. of electrons on the respective
should be written using atom in a Lewis structure / in
MathType or Microsoft an organic reaction
Equation 3.0 mechanism. Draw the lone
pairs so that the electrons are
• While drawing structure of clearly visible.
chemical molecules using
ChemDraw, correctly connect
the bonds and atoms
19
20
• Notations or variables used must be the same as those used in the textbook for uniformity.
• Standard constant values (acceleration due to gravity, specific gravity, density), must be taken
from the respective textbook as the values might vary slightly.
• The representation of sigma, dash symbol and degree symbol that are frequently used in the
expressions
21
• While calculation of values in tables, the first value must be calculated with all detailed
calculations, then the other values can be tabulated directly.
C) GRAPHS
• While taking any constant values from the textbook graphs, the graph name should be specified.
Note: Technology
• For representing equations in your solutions, use MathType or Microsoft Equation 3.0
22
• In the case of shear force and bending • While drawing the shear diagram and the
moment diagrams, their widths should match moment diagram, the width of the diagram
the width of the beam. The diagrams should should be the same as the given Load diagram.
also be aligned with the beam. Also, the diagrams should be aligned vertically.
23
24
While authoring solutions related to programming, there are multiple logical parts, with each part
having one or more Chegg steps.
• First part (needed only in special cases): If the situation given is complex or involve
mathematics or topics from other subjects; then the analysis of the situation/problem
should be explained in this part.
• Second part: Give explanation briefly, how the program will be implemented and how it works
under the heading “Program Plan:”.
• Third part (needed only in special cases): When designing forms in “.net” environment (or
any equivalent environment), the steps involved in placing the controls, naming etc. should be
explained.
25
a) In the beginning of the program use comment block. In that block, write description (in one or two
lines) of what the program does.
b) If any specific header files or import packages are used (other than usual), then write details about
the functions or methods used from those header files or packages.
d) Write necessary comments to understand the statements and the logical flow of the program.
e) Write comments for every statement in the function, method, and definitions.
f) Use a delimiter to separate functions (C Language) and different classes (OO Languages).
g) Write the program using the topics/concepts covered so far in the textbook.
h) The program should be indented properly. The indenting should follow “Allman Style”.
26
a) If the program requires any special execution method (example: command line arguments in C or
C++), the procedure of execution should be explained.
b) If the program needs to work with database, give step-by-step procedure to run the program.
• Sixth part: The output is given under the heading “Sample Output:”. Present the output as follows:
b) If the program is console-based, then the output should be in text form directly copied from the console
(using Clipboard pasting).
c) If the program is GUI based, then the output should contain screenshots.
• Seventh part (needed only in special cases): Include this part if the output needs to be explained.
Note: Use specified Integrated Development Environments (IDEs) for compiling, debugging, and running
the programs. Present the code in colors as per the default colors of the IDE.
27
• Write the function/method in the user specified language, within the scope of the concepts, and
functionality specifications.
• Write the method with the parameters and return values as specified.
• Try to demonstrate the functionality of the function/method using a simple driver program (If
the function/method is independent and can be called directly).
28
• Identify the location in the program where the statement or method needs to be added.
• Don’t write complete program given in the textbook. Instead give reference to the location in
the textbook where the code is available. Use Figure No., Table No., Listing No., as
references. Avoid using page numbers as references.
• Highlight the code that is added/modified using “Text Highlighter” in grey colour. It helps the
user to identify the additions/modifications easily.
29
• Read and understand the question carefully and identify the statements with errors.
• Fix all the errors in the program/code/statement and make the code executable if possible.
• If program is given to rectify errors, then highlight the code that is rectified using “Text
Highlighter” in grey colour. It helps the user to identify the rectifications easily and give the
code (skeleton).
• Use a table to give the differences, and give as many (at least 5) differences as possible.
• If the question asked to compare and contrast, give the comparisons first and differences next
(don’t mix).
30
• Identify the correct matching terms and give the appropriate matching using a table.
7. Theoretical questions:
31
• If formula is required in a step; write it, give description of the formula, and its significance in
the step.
• Read and understand the question carefully and identify all the requirements.
• Follow the instructions given in the question and present the pseudo code, flowchart in the
same order. Pseudo code style should match the style given in the textbook.
• Use Serif Draw Plus, Microsoft Paint, Microsoft Visio (or any other equivalent software)
to draw flow-charts. Flow-chart symbols should be aligned neatly.
32
• Author the solution such that the ideas/suggestions/context discussed in the case study
should reflect in the solution.
• Solution should be within the context of the given case study and if required within the
context of the respective chapter.
33
34
Note: Technology
• Equations: Use MathType or Microsoft Equation 3.0 available in MS Office 2007/2010 to type
any equation.
• Tables: Use Excel tables for creating tables and paste them into your Microsoft Word file in an
image format.
C) EXPLANATION / APPROACH
Let’s have a look at some types of questions you will find & how to approach them:
Example
36
37
c. Solve step-wise.
Example
38
39
40
• The conclusion statement should reflect the question. Any inferences from the solution can be
mentioned in the conclusion section.
B) EQUATIONS
41
Note: Technology
42
• In truth tables and Karnaugh maps, all cells should have their entries
center-aligned. The titles should be in bold.
Note: Technology
43
44
45
46
47
48
49
50
1. For theory as well as numerical problems, introductory part of the solution should contain
relevant concept or context discussed in the question. The main idea behind the introduction
part is to give the student an understanding of the underlying concept.
2. For assumption/opinion-based questions, expert should avoid writing the solution using first
person or second person pronouns like I/we/us/me/you, etc. Instead of this, expert is
advised to write the solution from an individual’s perspective.
51
4. For business law questions, expert can also quote the actual law/definition using proper
citations.
52
53
54
Every case law should be properly Full text of a provision is not recommended.
cited with full citation. However, a summarized and brief version of the
provision should be included.
For example, the correct way for
citing a case law is: Example:
Here,
55
56
57
59
60
61
• If the problem involves interpolation, then the calculation part of the interpolation should be
explained clearly instead of writing direct values.
B) EQUATIONS
• The representation of sigma symbol and degree symbol that are frequently used in the expressions:
62
63
5. In the case of shear force and bending moment diagrams, their widths
should match the width of the beam.
6. While drawing the shear diagram and the moment diagram, the width of
the diagram should be the same as the given Load diagram. Also, all the
three diagrams should be aligned vertically.
• While taking any constant values from the textbook tables / graphs, the
table / graph name should be specified. Do not use their number.
64
65
66
67
The variables labelled in diagrams The scale chosen for the graph must
should be in italics. be indicated at its top right side corner.
68
69
70
71
72
73
75
76