blob: 40f651411f15ec2168acf9372dc308ba350a6022 [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="img18.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img20.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_AgileALMConnect2012.htm"><img src="home.png" border=0 alt="Résumé"></a> <a href="text19.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img19.png" alt="" style="float:left"/>
<p><p style="direction:ltr;">Ok, so now you've understood that Intent allows you to make your documentation react to changes and keep it synchronized with your code.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">But Intent is much more than a synchronization tool : as it is a bridge between technical artifacts and high-level concerns,
it is a perfect way to provide <b>tooling for checking high-level constraints</b> on your software.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;"><font color="#FF0000"></font></p>
</p>
</body>
</html>