Some changes after the horrible problem of writing the same ch9 on all the html pages
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>
Chapter. Introduction
</title>
<link rel="stylesheet" href="/review/support/styles.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.74.3" />
<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png" />
<script type="text/javascript" src="/review/support/jquery-min.js">
</script>
<script type="text/javascript" src="/review/support/form.js">
</script>
<script type="text/javascript" src="/review/support/hsbook.js">
</script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="chapter" id="ch1Introduction">
<div class="titlepage">
</div>
<div class="toc">
<p>
<b>
Table of Contents
</b>
</p>
<dl>
<dt>
<span class="article">
<a href="#id2480917">
Introduction to the Course
</a>
</span>
</dt>
</dl>
</div>
<div class="article" title="Introduction to the Course">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a name="id2480917">
</a>
Introduction to the Course
</h2>
</div>
</div>
<hr />
</div>
<p id="ch1Introduction_1">
Engineering students use computers for a large number of curricular
tasks mostly computation centred. However, they do not see this as coding or programming tasks and usually are not even aware of the tools and
techniques that will help them to handle these tasks better. This results
in less than optimal use of their time and resources. This also causes
difficulties when it comes tocollaboration and building on other peoples
work. This course is intended to train such students in good software
practices and tools for producing code and documentation.
</p>
<p id="ch1Introduction_2">
After successfully completing the program, the participants will be able to:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" type="*">
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_3">
understand how software tools work together and how they can be used in tandem to carry out tasks,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_4">
use unix command line tools to carry out common (mostly text processing tasks,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_5">
to generate professional documents,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_6">
use version control effectively for both code and documents,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_7">
automate tasks by writing shell scripts and python scripts,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_8">
realise the impact of coding style and readbility on quality,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_9">
write mid-sized programs that carry out typical engineering / numerical computations such as those that involve (basic) manipulation of large arrays in an efficient manner,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_a">
generate 2D and simple 3D plots,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_b">
debug programs using a standardised approach,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_c">
understand the importance of tests and the philosophy of Test Driven Development,
</p>
</li>
<li class="listitem" style="list-style-type: *">
<p id="ch1Introduction_d">
write unit tests and improve the quality of code.
</p>
</li>
</ul>
</div>
</div>
</div>
</body>
</html>