pages/transcripts/2012_AgileALMConnect/img6.html - gerrit/www.eclipse.org/intent - Git at Google

 <!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="img5.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img7.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="text6.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
 <img src="img6.png" alt="" style="float:left"/>

 <p><p style="direction:ltr;">So we can see that if documentation is often discarded in Agile methods, it is because of its maintenance, which is both expensive and painful.
 That is exactly why the main purpose of Intent is to provide tooling for easily keeping your doc synchronized with your technical artifacts.</p>
 <p>
 I don't know if you're familiar with the <a href="http://www.charlesweir.com/papers/teamwork.pdf">Ad-hoc Corrections</a> pattern defined by Charles Weir, which tries to answer
 to the same problematic with a team best practice.<br/>
 All the team shares a master copy of the documentation on paper.
 Any time a developer makes a change on the software that deviate from design (and hence requires a documentation update),
 he must write a correction in the margin of the master copy, indicating the documentation parts that have to be updated.
 </p><p>
 That's exactly what Intent synchronization mechanism is about : when you make a change in code that impacts the documentation,
 Intent will detect that a change occurred, find out all the documentation parts related to this change and place synchronization error markers on it.
 </p>

 </p>
 </body>
 </html>
	<!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="img5.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img7.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="text6.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
	<img src="img6.png" alt="" style="float:left"/>

	<p><p style="direction:ltr;">So we can see that if documentation is often discarded in Agile methods, it is because of its maintenance, which is both expensive and painful.
	That is exactly why the main purpose of Intent is to provide tooling for easily keeping your doc synchronized with your technical artifacts.</p>
	<p>
	I don't know if you're familiar with the <a href="http://www.charlesweir.com/papers/teamwork.pdf">Ad-hoc Corrections</a> pattern defined by Charles Weir, which tries to answer
	to the same problematic with a team best practice.<br/>
	All the team shares a master copy of the documentation on paper.
	Any time a developer makes a change on the software that deviate from design (and hence requires a documentation update),
	he must write a correction in the margin of the master copy, indicating the documentation parts that have to be updated.
	</p><p>
	That's exactly what Intent synchronization mechanism is about : when you make a change in code that impacts the documentation,
	Intent will detect that a change occurred, find out all the documentation parts related to this change and place synchronization error markers on it.
	</p>

	</p>
	</body>
	</html>