blob: 832c44abfec9a320f2e9736b03a1b72fbdea8650 [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="img6.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img8.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="text7.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img7.png" alt="" style="float:left"/>
<p><p style="direction:ltr;">In order to achieve that goal, we defined the <b>Literate Modeling</b> approach. </p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">It's based on Donald Knuth's <b>Literate Programming</b> theory.
The main idea of this work is to mix explanations in natural language along with code in a same document.
With this structure, it is way easier to explain a part of code you have above your eyes, and to retrieve the doc related to a code part.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">For the Literate Modeling approach, we have decided to use <b>model fragments</b> instead of code, as models are way more generic than code. </p>
</p>
</body>
</html>