OpenUP/OpenUP_baseline_EN/library/openup_basic/guidances/concepts/coding_standard.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-vlYpfwIYlF_ZCk5s4Dsqdg" name="new_concept,_0lnRMMqOEduwrYVlQ9zp3w" guid="-vlYpfwIYlF_ZCk5s4Dsqdg" changeDate="2007-03-04T15:29:08.886-0500">
  <mainDescription>&lt;p&gt;
    Using a coding standard is a software development practice that has been widely accepted in the industry. The need for
    this practice takes on added importance in&amp;nbsp;a highly collaborative environment. The team should have a standard way
    of naming and formatting things so they can understand the code quickly and know where to look at all times.
&lt;/p&gt;
&lt;p&gt;
    Ideally, the coding standard should be the result of team consensus. In some cases, decisions will be arbitrary (like
    how much to indent). Each item in the standard should support one or more goals, improved communication being one of
    the most critical goals. Once the team agrees on a standard, all members of the teams are expected to follow it. With
    time, the team will use and modify the standard to develop a style that is well adapted to their environment.
&lt;/p&gt;
&lt;p&gt;
    Benefits
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        Improved communication: increases the ability to read each other's code.
    &lt;/li&gt;
    &lt;li&gt;
        Refactoring support: provides consistently shaped code.
    &lt;/li&gt;
&lt;/ul&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>