blob: c894f90250fc7fddedbf45092e94c280cf6b21b1 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/transitional.dtd">
<html>
<head>
<meta HTTP-EQUIV=CONTENT-TYPE CONTENT="text/html; charset=utf-8">
<title>Create Useful Documentation with Mylyn Intent : transcript</title>
<link rel="stylesheet" type="text/css" href="talk.css">
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#000080" vlink="#0000CC" alink="#000080">
<center>
<a href="img0.html"><img src="first.png" border=0 alt="Première page"></a> <a href="img19.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img21.html"><img src="right.png" border=0 alt="Suivant"></a> <a href="img29.html"><img src="last.png" border=0 alt="Dernière page"></a> <a href="Intent_ece2011.htm"><img src="home.png" border=0 alt="Résumé"></a> <a href="text20.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img20.png" alt="" style="float:left"/>
<p><p style="direction:ltr;">As a mater of fact, I'm sure that you already have high-level constraints on your software : your team shares the same dev guidelines, processes and
good practices. But most of the time these constraints are not explained formally : they are just textile files located somewhere.
</p>
<p>
Consequently, reviewing the code to check those is a very hard and painful job, and can lead you to endorse the bad role when you have to explain
to your developers that they do not code like you want them to. Moreover, as these constraints are not expressed formally you are never sure that you fulfilled all them.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">Intent provides tooling for <b>checking automatically</b> these constraints and guidelines.</p>
</p>
</body>
</html>