blob: 586ccfb9cf18ebff2a6a84c70a819e11726363d7 [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="img9.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img11.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="text10.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img10.png" alt="" style="float:left"/>
<p style="direction:ltr;">- It also contains <b>Model fragments</b>, defined with a generic textual syntax. These model fragments are what allow us to link the doc with concrete artifacts.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">This structure allows us to keep documentation close to the models it explains.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">Consequently, we can easily determine : </p>
<p style="direction:ltr;"> - for a given model element, which part of the doc explains it</p>
<p style="direction:ltr;"> - for a given requirement, which model elements have been designed to fulfill it</p>
<p style="direction:ltr;"></p>
</p>
</body>
</html>