adulau/pmf
1
0
Fork 0
mirror of https://github.com/adulau/pmf.git synced 2024-11-07 12:06:32 +00:00
Code Issues Projects Releases Packages Wiki Activity

chg: [doc] updated

Browse source
This commit is contained in:
Alexandre Dulaunoy 2023-02-22 22:08:32 +01:00
parent 067048da10
commit a10d042319
Signed by: adulau
GPG key ID: 09E2CD4944E6CBCD
4 changed files with 475 additions and 233 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
raw.md
View file

@ -6,12 +6,12 @@ docName = "draft-dulaunoy-programming-methodology-framework"
ipr= "trust200902" ipr= "trust200902"
area = "Internet" area = "Internet"
keyword = ["software engineering", "engineering", "pmf", "programming"] keyword = ["software engineering", "engineering", "pmf", "programming"]
submissiontype = "independent"
date = 2023-02-22T00:00:00Z date = 2023-02-22T00:00:00Z
[seriesInfo] [seriesInfo]
name = "Internet-Draft" name = "Internet-Draft"
value = "draft-01" value = "draft-02"
stream = "independent" stream = "independent"
status = "informational" status = "informational"

628
raw.md.html
View file

@ -2,27 +2,65 @@
<html lang="en" class="Internet-Draft"> <html lang="en" class="Internet-Draft">
<head> <head>
<meta charset="utf-8"> <meta charset="utf-8">
<meta name="scripts" content="Common,Latin"> <meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>Programming Methodology Framework aka PMF</title> <title>Programming Methodology Framework aka PMF</title>
<meta name="author" content="Alexandre Dulaunoy"> <meta content="Alexandre Dulaunoy" name="author">
<meta name="author" content="Andras Iklody"> <meta content="Andras Iklody" name="author">
<meta name="description" content=" <meta content="
This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw which This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw which
describes a natural approach to software engineering with a strong focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference describes a natural approach to software engineering with a strong focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference
to official engineering or project documents describing one of the most used software engineering methodologies. to official engineering or project documents describing one of the most used software engineering methodologies.
"> " name="description">
<meta name="generator" content="xml2rfc 2.23.1"> <meta content="xml2rfc 3.12.1" name="generator">
<meta name="keyword" content="software engineering"> <meta content="software engineering" name="keyword">
<meta name="keyword" content="engineering"> <meta content="engineering" name="keyword">
<meta name="keyword" content="pmf"> <meta content="pmf" name="keyword">
<meta name="keyword" content="programming"> <meta content="programming" name="keyword">
<link rel="alternate" type="application/rfc+xml" href="raw.md.xml"> <meta content="draft-02" name="ietf.draft">
<link rel="license" href="#copyright"> <!-- Generator version information:
<style type="text/css">/* fonts */ xml2rfc 3.12.1
Python 3.8.10
appdirs 1.4.4
ConfigArgParse 1.5.3
google-i18n-address 2.5.0
html5lib 1.1
intervaltree 3.1.0
Jinja2 3.1.2
kitchen 1.2.6
lxml 4.9.1
pycairo 1.16.2
pycountry 22.3.5
pyflakes 2.4.0
PyYAML 6.0
requests 2.28.1
setuptools 65.4.0
six 1.16.0
-->
<link href="raw.md.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*
NOTE: Changes at the bottom of this file overrides some earlier settings.
Once the style has stabilized and has been adopted as an official RFC style,
this can be consolidated so that style settings occur only in one place, but
for now the contents of this file consists first of the initial CSS work as
provided to the RFC Formatter (xml2rfc) work, followed by itemized and
commented changes found necssary during the development of the v3
formatters.
*/
/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
@viewport {
zoom: 1.0;
width: extend-to-zoom;
}
@-ms-viewport { @-ms-viewport {
width: extend-to-zoom; width: extend-to-zoom;
zoom: 1.0; zoom: 1.0;
@ -167,6 +205,9 @@ ul.empty, .ulEmpty {
ul.empty li, .ulEmpty li { ul.empty li, .ulEmpty li {
margin-top: 0.5em; margin-top: 0.5em;
} }
ul.ulBare, li.ulBare {
margin-left: 0em !important;
}
ul.compact, .ulCompact, ul.compact, .ulCompact,
ol.compact, .olCompact { ol.compact, .olCompact {
line-height: 100%; line-height: 100%;
@ -180,11 +221,16 @@ dl > dt {
float: left; float: left;
margin-right: 1em; margin-right: 1em;
} }
/*
dl.nohang > dt {
float: none;
}
*/
dl > dd { dl > dd {
margin-bottom: .8em; margin-bottom: .8em;
min-height: 1.3em; min-height: 1.3em;
} }
dl.compact > dd, dlCompact > dd { dl.compact > dd, .dlCompact > dd {
margin-bottom: 0em; margin-bottom: 0em;
} }
dl > dd > dl { dl > dd > dl {
@ -195,10 +241,9 @@ dl > dd > dl {
/* links */ /* links */
a { a {
text-decoration: none; text-decoration: none;
z-index: 2;
} }
a[href] { a[href] {
color: #3E8EDE; color: #22e; /* Arlen: WCAG 2019 */
} }
a[href]:hover { a[href]:hover {
background-color: #f2f2f2; background-color: #f2f2f2;
@ -251,6 +296,7 @@ aside, blockquote {
} }
blockquote { blockquote {
background-color: #f9f9f9; background-color: #f9f9f9;
color: #111; /* Arlen: WCAG 2019 */
border: 1px solid #ddd; border: 1px solid #ddd;
border-radius: 3px; border-radius: 3px;
margin: 1em 0; margin: 1em 0;
@ -294,7 +340,7 @@ table p {
/* pilcrow */ /* pilcrow */
a.pilcrow { a.pilcrow {
color: #777; color: #666; /* Arlen: AHDJ 2019 */
text-decoration: none; text-decoration: none;
visibility: hidden; visibility: hidden;
user-select: none; user-select: none;
@ -345,6 +391,12 @@ hr {
float: left; float: left;
margin-bottom: 0; margin-bottom: 0;
} }
/* Fix PDF info block run off issue */
@media print {
#identifiers dd {
float: none;
}
}
#identifiers .authors .author { #identifiers .authors .author {
display: inline-block; display: inline-block;
margin-right: 1.5em; margin-right: 1.5em;
@ -355,7 +407,7 @@ hr {
/* The prepared/rendered info at the very bottom of the page */ /* The prepared/rendered info at the very bottom of the page */
.docInfo { .docInfo {
color: #999; color: #666; /* Arlen: WCAG 2019 */
font-size: 0.9em; font-size: 0.9em;
font-style: italic; font-style: italic;
margin-top: 2em; margin-top: 2em;
@ -469,17 +521,17 @@ hr.addr {
right: 0.2em; right: 0.2em;
padding: 0.2em; padding: 0.2em;
content: "The RFC Editor will remove this note"; content: "The RFC Editor will remove this note";
color: #b76427; color: #9e2a00; /* Arlen: WCAG 2019 */
background-color: rgba(249, 232, 105, 0.3); background-color: #ffd; /* Arlen: WCAG 2019 */
} }
.rfcEditorRemove { .rfcEditorRemove {
position: relative; position: relative;
padding-top: 1.8em; padding-top: 1.8em;
background-color: rgba(249, 232, 105, 0.3); background-color: #ffd; /* Arlen: WCAG 2019 */
border-radius: 3px; border-radius: 3px;
} }
.cref { .cref {
background-color: rgba(249, 232, 105, 0.3); background-color: #ffd; /* Arlen: WCAG 2019 */
padding: 2px 4px; padding: 2px 4px;
} }
.crefSource { .crefSource {
@ -628,6 +680,34 @@ hr.addr {
} }
} }
/* This is commented out here, as the string-set: doesn't
pass W3C validation currently */
/*
.ears thead .left {
string-set: ears-top-left content();
}
.ears thead .center {
string-set: ears-top-center content();
}
.ears thead .right {
string-set: ears-top-right content();
}
.ears tfoot .left {
string-set: ears-bottom-left content();
}
.ears tfoot .center {
string-set: ears-bottom-center content();
}
.ears tfoot .right {
string-set: ears-bottom-right content();
}
*/
@page :first { @page :first {
padding-top: 0; padding-top: 0;
@top-left { @top-left {
@ -648,10 +728,53 @@ hr.addr {
size: A4; size: A4;
margin-bottom: 45mm; margin-bottom: 45mm;
padding-top: 20px; padding-top: 20px;
/* The follwing is commented out here, but set appropriately by in code, as
the content depends on the document */
/*
@top-left {
content: 'Internet-Draft';
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-left {
content: string(ears-top-left);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-center {
content: string(ears-top-center);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-right {
content: string(ears-top-right);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@bottom-left {
content: string(ears-bottom-left);
vertical-align: top;
border-top: solid 1px #ccc;
}
@bottom-center {
content: string(ears-bottom-center);
vertical-align: top;
border-top: solid 1px #ccc;
}
@bottom-right {
content: '[Page ' counter(page) ']';
vertical-align: top;
border-top: solid 1px #ccc;
}
*/
} }
/* Changes introduced to fix issues found during implementation */ /* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
z-index: 2;
}
/* Separate body from document info even without intervening H1 */ /* Separate body from document info even without intervening H1 */
section { section {
clear: both; clear: both;
@ -710,10 +833,12 @@ tt, code, pre, code {
} }
/* Fix the height/width aspect for ascii art*/ /* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre { .art-text pre {
line-height: 1.12; line-height: 1.12;
} }
/* Add styling for a link in the ToC that points to the top of the document */ /* Add styling for a link in the ToC that points to the top of the document */
a.toplink { a.toplink {
float: right; float: right;
@ -774,7 +899,7 @@ caption {
script don't end up on the other side of the page. */ script don't end up on the other side of the page. */
address.vcard { address.vcard {
max-width: 20em; max-width: 30em;
margin-right: auto; margin-right: auto;
} }
@ -817,18 +942,11 @@ caption a[href] {
} }
/* Avoid page breaks inside dl and author address entries */ /* Avoid page breaks inside dl and author address entries */
dd {
page-break-before: avoid;
}
.vcard { .vcard {
page-break-inside: avoid; page-break-inside: avoid;
} }
} }
/* Avoid wrapping of URLs in references */
.references a {
white-space: nowrap;
}
/* Tweak the bcp14 keyword presentation */ /* Tweak the bcp14 keyword presentation */
.bcp14 { .bcp14 {
font-variant: small-caps; font-variant: small-caps;
@ -848,94 +966,255 @@ caption a[href] {
margin-top: -18px; /* provide offset for in-page anchors */ margin-top: -18px; /* provide offset for in-page anchors */
padding-top: 24px; padding-top: 24px;
} }
/* Float artwork pilcrow to the right */
@media screen {
.artwork a.pilcrow {
display: block;
line-height: 0.7;
margin-top: 0.15em;
}
}
/* Make pilcrows on dd visible */
@media screen {
dd:hover > a.pilcrow {
visibility: visible;
}
}
/* Make the placement of figcaption match that of a table's caption
by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
possibly even requiring a new line */
@media print {
a.pilcrow {
display: none;
}
}
/* Styling for the external metadata */
div#external-metadata {
background-color: #eee;
padding: 0.5em;
margin-bottom: 0.5em;
display: none;
}
div#internal-metadata {
padding: 0.5em; /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
clear: both;
margin: 0 0 -1em;
padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
margin-bottom: 0.25em;
min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
border-left: 1px solid #ddd;
margin: 1em 0 1em 2em;
padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
figcaption, table caption {
page-break-before: avoid;
}
}
/* Font size adjustments for print */
@media print {
body { font-size: 10pt; line-height: normal; max-width: 96%; }
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
h4 { font-size: 1em; padding-top: 1.5em; }
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
.artwork,
.sourcecode {
margin-bottom: 1em;
}
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
border: 1px solid #ddd;
}
td {
border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
#toc nav { display: none; }
#toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
break-after: avoid-page;
break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode {
break-before: auto;
break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
break-before: auto;
break-inside: auto;
}
dt {
break-before: auto;
break-after: avoid-page;
}
dd {
break-before: avoid-page;
break-after: auto;
orphans: 3;
widows: 3
}
span.break, dd.break {
margin-bottom: 0;
min-height: 0;
break-before: auto;
break-inside: auto;
break-after: auto;
}
/* Undo break-before ToC */
@media print {
#toc {
break-before: auto;
}
}
/* Text in compact lists should not get extra bottim margin space,
since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
margin-bottom: 1em; /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
backgrounds. Changed to something a bit more selective. */
tt, code {
background-color: transparent;
}
p tt, p code, li tt, li code {
background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
margin-bottom: 0;
}
</style> </style>
<link rel="stylesheet" href="rfc-local.css" type="text/css"> <link href="rfc-local.css" rel="stylesheet" type="text/css">
<script type="application/javascript">async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(let t=0;t<e.length;t++)if(/#identifiers/.exec(e[t].selectorText)){const a=e[t].cssText.replace("#identifiers","#external-updates");document.styleSheets[0].insertRule(a,document.styleSheets[0].cssRules.length)}}catch(e){console.log(e)}const e=document.getElementById("external-metadata");if(e)try{var t,a="",o=function(e){const t=document.getElementsByTagName("meta");for(let a=0;a<t.length;a++)if(t[a].getAttribute("name")===e)return t[a].getAttribute("content");return""}("rfc.number");if(o){t="https://www.rfc-editor.org/rfc/rfc"+o+".json";try{const e=await fetch(t);a=await e.json()}catch(e){t=document.URL.indexOf("html")>=0?document.URL.replace(/html$/,"json"):document.URL+".json";const o=await fetch(t);a=await o.json()}}if(!a)return;e.style.display="block";const s="",d="https://datatracker.ietf.org/doc",n="https://datatracker.ietf.org/ipr/search",c="https://www.rfc-editor.org/info",l=a.doc_id.toLowerCase(),i=a.doc_id.slice(0,3).toLowerCase(),f=a.doc_id.slice(3).replace(/^0+/,""),u={status:"Status",obsoletes:"Obsoletes",obsoleted_by:"Obsoleted By",updates:"Updates",updated_by:"Updated By",see_also:"See Also",errata_url:"Errata"};let h="<dl style='overflow:hidden' id='external-updates'>";["status","obsoletes","obsoleted_by","updates","updated_by","see_also","errata_url"].forEach(e=>{if("status"==e){a[e]=a[e].toLowerCase();var t=a[e].split(" "),o=t.length,w="",p=1;for(let e=0;e<o;e++)p<o?w=w+r(t[e])+" ":w+=r(t[e]),p++;a[e]=w}else if("obsoletes"==e||"obsoleted_by"==e||"updates"==e||"updated_by"==e){var g,m="",b=1;g=a[e].length;for(let t=0;t<g;t++)a[e][t]&&(a[e][t]=String(a[e][t]).toLowerCase(),m=b<g?m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>, ":m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>",b++);a[e]=m}else if("see_also"==e){var y,L="",C=1;y=a[e].length;for(let t=0;t<y;t++)if(a[e][t]){a[e][t]=String(a[e][t]);var _=a[e][t].slice(0,3),v=a[e][t].slice(3).replace(/^0+/,"");L=C<y?"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>, ":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>, ":"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>",C++}a[e]=L}else if("errata_url"==e){var R="";R=a[e]?R+"<a href='"+a[e]+"'>Errata exist</a> | <a href='"+d+"/"+l+"'>Datatracker</a>| <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>":"<a href='"+d+"/"+l+"'>Datatracker</a> | <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>",a[e]=R}""!=a[e]?"Errata"==u[e]?h+=`<dt>More info:</dt><dd>${a[e]}</dd>`:h+=`<dt>${u[e]}:</dt><dd>${a[e]}</dd>`:"Errata"==u[e]&&(h+=`<dt>More info:</dt><dd>${a[e]}</dd>`)}),h+="</dl>",e.innerHTML=h}catch(e){console.log(e)}else console.log("Could not locate metadata <div> element");function r(e){return e.charAt(0).toUpperCase()+e.slice(1)}}window.removeEventListener("load",addMetadata),window.addEventListener("load",addMetadata);</script>
</head> </head>
<body> <body>
<script> <script src="metadata.min.js"></script>
window.addEventListener('load',addMetadata);
async function addMetadata() {
// Copy all CSS rules for "#identifiers" to "#metadata"
try {
const cssRules = document.styleSheets[0].cssRules;
for (let i = 0; i < cssRules.length; i++) {
if (/#identifiers/.exec(cssRules[i].selectorText)) {
const rule = cssRules[i].cssText.
replace('#identifiers','#metadata');
document.styleSheets[0].
insertRule(rule, document.styleSheets[0].cssRules.length);
}
}
} catch (e) {
console.log(e);
}
// Retrieve the "metadata" element from the document
const div = document.getElementById('metadata');
if (!div) {
console.log("Could not locate metadata <div> element");
return;
}
div.style.background='#eee';
// Insert the metadata block
// [TODO: make this more sophisticated and linkify the values]
try {
const jsonFile = document.URL.replace(/html$/,'json');
const response = await fetch(jsonFile);
const metadata = (await response.json())[0];
const label = {
'STATUS': 'Status',
'OBSOLETES': 'Obsoletes',
'OBSOLETED-BY': 'Obsoleted By',
'UPDATES': 'Updates',
'UPDATED-BY': 'Updated By',
'SEE-ALSO': 'See Also',
'ERRATA-URL': 'Errata',
};
let metadataHTML = "<dl style='overflow:hidden'>";
['STATUS', 'OBSOLETES', 'OBSOLETED-BY', 'UPDATES',
'UPDATED-BY', 'SEE-ALSO', 'ERRATA-URL'].forEach(key => {
if (metadata[key]) {
metadataHTML += `<dt>${label[key]}:</dt><dd>${metadata[key]}</dd>`;
}
})
metadataHTML += "</dl>";
div.innerHTML = metadataHTML;
} catch (e) {
console.log(e);
}
}
</script>
<table class="ears"> <table class="ears">
<thead><tr> <thead><tr>
<td class="left">Internet-Draft</td> <td class="left">Internet-Draft</td>
<td class="center">PMF - Programming Methodology Framework</td> <td class="center">PMF - Programming Methodology Framework</td>
<td class="right">October 2021</td> <td class="right">February 2023</td>
</tr></thead> </tr></thead>
<tfoot><tr> <tfoot><tr>
<td class="left">Dulaunoy &amp; Iklody</td> <td class="left">Dulaunoy &amp; Iklody</td>
<td class="center">Expires 4 April 2022</td> <td class="center">Expires 26 August 2023</td>
<td class="right">[Page]</td> <td class="right">[Page]</td>
</tr></tfoot> </tr></tfoot>
</table> </table>
<div class="document-information"> <div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers"> <dl id="identifiers">
<dt class="label-workgroup">Workgroup:</dt>
<dd class="workgroup">Network Working Group</dd>
<dt class="label-internet-draft">Internet-Draft:</dt> <dt class="label-internet-draft">Internet-Draft:</dt>
<dd class="internet-draft">draft-01</dd> <dd class="internet-draft">draft-02</dd>
<dt class="label-published">Published:</dt> <dt class="label-published">Published:</dt>
<dd class="published"> <dd class="published">
<time datetime="2021-10-01" class="published">1 October 2021</time> <time datetime="2023-02-22" class="published">22 February 2023</time>
</dd> </dd>
<dt class="label-intended-status">Intended Status:</dt> <dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Informational</dd> <dd class="intended-status">Informational</dd>
<dt class="label-expires">Expires:</dt> <dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2022-04-04">4 April 2022</time></dd> <dd class="expires"><time datetime="2023-08-26">26 August 2023</time></dd>
<dt class="label-authors">Authors:</dt> <dt class="label-authors">Authors:</dt>
<dd class="authors"> <dd class="authors">
<div class="author"> <div class="author">
@ -975,7 +1254,7 @@ to official engineering or project documents describing one of the most used sof
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p> material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4"> <p id="section-boilerplate.1-4">
This Internet-Draft will expire on 4 April 2022.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p> This Internet-Draft will expire on 26 August 2023.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section> </section>
</div> </div>
<div id="copyright"> <div id="copyright">
@ -984,7 +1263,7 @@ to official engineering or project documents describing one of the most used sof
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
</h2> </h2>
<p id="section-boilerplate.2-1"> <p id="section-boilerplate.2-1">
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow"></a></p> document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow"></a></p>
<p id="section-boilerplate.2-2"> <p id="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
@ -992,43 +1271,40 @@ to official engineering or project documents describing one of the most used sof
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow"></a></p>
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow"></a></p>
</section> </section>
</div> </div>
<div id="toc"> <div id="toc">
<section id="section-boilerplate.3"> <section id="section-toc.1">
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
</h2> </h2>
<nav class="toc"><ul class="toc ulEmpty"> <nav class="toc"><ul class="compact toc ulBare ulEmpty">
<li class="toc ulEmpty" id="section-boilerplate.3-1.1"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
<p id="section-boilerplate.3-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-boilerplate.3-1.1.1" class="pilcrow"></a></p> <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
<ul class="toc ulEmpty"> <ul class="compact toc ulBare ulEmpty">
<li class="toc ulEmpty" id="section-boilerplate.3-1.1.2.1"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
<p id="section-boilerplate.3-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-management-and-pmf-methodol" class="xref">Management and PMF methodology</a><a href="#section-boilerplate.3-1.1.2.1.1" class="pilcrow"></a></p> <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-management-and-pmf-methodol" class="xref">Management and PMF methodology</a></p>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.1.2.2"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.2">
<p id="section-boilerplate.3-1.1.2.2.1"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-conventions-and-terminology" class="xref">Conventions and Terminology</a><a href="#section-boilerplate.3-1.1.2.2.1" class="pilcrow"></a></p> <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-conventions-and-terminology" class="xref">Conventions and Terminology</a></p>
</li> </li>
</ul> </ul>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.2"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
<p id="section-boilerplate.3-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-boilerplate.3-1.2.1" class="pilcrow"></a></p> <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.3"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
<p id="section-boilerplate.3-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-boilerplate.3-1.3.1" class="pilcrow"></a></p> <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.4"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
<p id="section-boilerplate.3-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-boilerplate.3-1.4.1" class="pilcrow"></a></p> <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.5"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
<p id="section-boilerplate.3-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-boilerplate.3-1.5.1" class="pilcrow"></a></p> <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li> </li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.6"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
<p id="section-boilerplate.3-1.6.1"><a href="#section-appendix.a" class="xref"></a>  <a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-boilerplate.3-1.6.1" class="pilcrow"></a></p> <p id="section-toc.1-1.6.1"><a href="#appendix-A" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li> </li>
</ul> </ul>
</nav> </nav>
@ -1037,24 +1313,24 @@ to official engineering or project documents describing one of the most used sof
<div id="introduction"> <div id="introduction">
<section id="section-1"> <section id="section-1">
<h2 id="name-introduction"> <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
</h2> </h2>
<p id="section-1-1">In 2011, Zed A. Shaw published a blog post which describes:<a href="#section-1-1" class="pilcrow"></a></p> <p id="section-1-1">In 2011, Zed A. Shaw published a blog post which describes:<a href="#section-1-1" class="pilcrow"></a></p>
<p id="section-1-2">{align="left"} I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology.<a href="#section-1-2" class="pilcrow"></a></p> <p id="section-1-2">{align="left"} I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology.<a href="#section-1-2" class="pilcrow"></a></p>
<p id="section-1-3">The PMF methodology was published as a manifesto later <span>[<a href="#PROGRAMMING-MF-MANIFESTO" class="xref">PROGRAMMING-MF-MANIFESTO</a>]</span>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <span>[<a href="#THE-TAO-OF-PROGRAMMING" class="xref">THE-TAO-OF-PROGRAMMING</a>]</span> describes similar methodologies which strongly focus on coding, scripting and programming.<a href="#section-1-3" class="pilcrow"></a></p> <p id="section-1-3">The PMF methodology was published as a manifesto later <span>[<a href="#PROGRAMMING-MF-MANIFESTO" class="xref">PROGRAMMING-MF-MANIFESTO</a>]</span>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <span>[<a href="#THE-TAO-OF-PROGRAMMING" class="xref">THE-TAO-OF-PROGRAMMING</a>]</span> describes similar methodologies which strongly focus on coding, scripting and programming.<a href="#section-1-3" class="pilcrow"></a></p>
<p id="section-1-4">The overall concept of PMF methodology follows the following process:<a href="#section-1-4" class="pilcrow"></a></p> <p id="section-1-4">The overall concept of PMF methodology follows the following process:<a href="#section-1-4" class="pilcrow"></a></p>
<ul> <ul class="compact">
<li id="section-1-5.1">Compose a list of features to be implemented and use an iterative programming process.<a href="#section-1-5.1" class="pilcrow"></a> <li class="compact" id="section-1-5.1">Compose a list of features to be implemented and use an iterative programming process.<a href="#section-1-5.1" class="pilcrow"></a>
</li> </li>
<li id="section-1-5.2">Enhance said features using trial and error programming.<a href="#section-1-5.2" class="pilcrow"></a> <li class="compact" id="section-1-5.2">Enhance said features using trial and error programming.<a href="#section-1-5.2" class="pilcrow"></a>
</li> </li>
<li id="section-1-5.3">Orchestrate your testing and integration processes using pragmatic programming.<a href="#section-1-5.3" class="pilcrow"></a> <li class="compact" id="section-1-5.3">Orchestrate your testing and integration processes using pragmatic programming.<a href="#section-1-5.3" class="pilcrow"></a>
</li> </li>
</ul> </ul>
<p id="section-1-6">Repeat the above process until the software is delivered.<a href="#section-1-6" class="pilcrow"></a></p> <p id="section-1-6">Repeat the above process until the software is delivered.<a href="#section-1-6" class="pilcrow"></a></p>
<p id="section-1-7">A simplified overview of the process can be described as follow:<a href="#section-1-7" class="pilcrow"></a></p> <p id="section-1-7">A simplified overview of the process can be described as follow:<a href="#section-1-7" class="pilcrow"></a></p>
<div id="section-1-8"> <div id="section-1-8">
<pre class="sourcecode lang-ascii-art">+----------+ <pre class="lang-ascii-art sourcecode">+----------+
| | | |
| idea &lt;------+ | idea &lt;------+
| | | | | |
@ -1079,17 +1355,17 @@ to official engineering or project documents describing one of the most used sof
<div id="management-and-pmf-methodology"> <div id="management-and-pmf-methodology">
<section id="section-1.1"> <section id="section-1.1">
<h3 id="name-management-and-pmf-methodol"> <h3 id="name-management-and-pmf-methodol">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-management-and-pmf-methodol" class="section-name selfRef">Management and PMF methodology</a> <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-management-and-pmf-methodol" class="section-name selfRef">Management and PMF methodology</a>
</h3> </h3>
<p id="section-1.1-1">A simple management process is a requirement of the PMF methodology. <p id="section-1.1-1">A simple management process is a requirement of the PMF methodology.
The management process is meant to be complementary instead of interfering with The management process is meant to be complementary instead of interfering with
the programming aspect and solely serves to support the PMF methodology.<a href="#section-1.1-1" class="pilcrow"></a></p> the programming aspect and solely serves to support the PMF methodology.<a href="#section-1.1-1" class="pilcrow"></a></p>
<ul> <ul class="compact">
<li id="section-1.1-2.1">Collect requirements of the users/customers.<a href="#section-1.1-2.1" class="pilcrow"></a> <li class="compact" id="section-1.1-2.1">Collect requirements of the users/customers.<a href="#section-1.1-2.1" class="pilcrow"></a>
</li> </li>
<li id="section-1.1-2.2">Provide programmers with the desired requirements.<a href="#section-1.1-2.2" class="pilcrow"></a> <li class="compact" id="section-1.1-2.2">Provide programmers with the desired requirements.<a href="#section-1.1-2.2" class="pilcrow"></a>
</li> </li>
<li id="section-1.1-2.3">Review whether the software to be delivered matches the requirements.<a href="#section-1.1-2.3" class="pilcrow"></a> <li class="compact" id="section-1.1-2.3">Review whether the software to be delivered matches the requirements.<a href="#section-1.1-2.3" class="pilcrow"></a>
</li> </li>
</ul> </ul>
</section> </section>
@ -1097,7 +1373,7 @@ the programming aspect and solely serves to support the PMF methodology.<a href=
<div id="conventions-and-terminology"> <div id="conventions-and-terminology">
<section id="section-1.2"> <section id="section-1.2">
<h3 id="name-conventions-and-terminology"> <h3 id="name-conventions-and-terminology">
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-conventions-and-terminology" class="section-name selfRef">Conventions and Terminology</a> <a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-conventions-and-terminology" class="section-name selfRef">Conventions and Terminology</a>
</h3> </h3>
<p id="section-1.2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", <p id="section-1.2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>",
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this
@ -1109,7 +1385,7 @@ document are to be interpreted as described in RFC 2119 <span>[<a href="#RFC2119
<div id="security-considerations"> <div id="security-considerations">
<section id="section-2"> <section id="section-2">
<h2 id="name-security-considerations"> <h2 id="name-security-considerations">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
</h2> </h2>
<p id="section-2-1">Secure and defensive programming can only come by practicing programming and this also <p id="section-2-1">Secure and defensive programming can only come by practicing programming and this also
includes the act of simplifying or removing code to reduce the attack surface.<a href="#section-2-1" class="pilcrow"></a></p> includes the act of simplifying or removing code to reduce the attack surface.<a href="#section-2-1" class="pilcrow"></a></p>
@ -1118,47 +1394,47 @@ includes the act of simplifying or removing code to reduce the attack surface.<a
<div id="acknowledgements"> <div id="acknowledgements">
<section id="section-3"> <section id="section-3">
<h2 id="name-acknowledgements"> <h2 id="name-acknowledgements">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
</h2> </h2>
<p id="section-3-1">The authors wish to thank all the programmers who program.<a href="#section-3-1" class="pilcrow"></a></p> <p id="section-3-1">The authors wish to thank all the programmers who program.<a href="#section-3-1" class="pilcrow"></a></p>
</section> </section>
</div> </div>
<section id="section-4"> <section id="section-4">
<h2 id="name-normative-references"> <h2 id="name-normative-references">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
</h2> </h2>
<dl class="references"> <dl class="references">
<dt id="RFC2119">[RFC2119]</dt> <dt id="RFC2119">[RFC2119]</dt>
<dd> <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03">March 1997</time> <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<span>, &lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd> <dd class="break"></dd>
</dl> </dl>
</section> </section>
<section id="section-5"> <section id="section-5">
<h2 id="name-informative-references"> <h2 id="name-informative-references">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
</h2> </h2>
<dl class="references"> <dl class="references">
<dt id="PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</dt> <dt id="PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</dt>
<dd> <dd>
<span class="refAuthor">Shaw, Z. A.</span>, <span class="refTitle">"Programming Motherfucker, do you speak it?"</span>, <span class="refContent"></span>, <time datetime="2021-10">October 2021</time> <span class="refAuthor">Shaw, Z. A.</span>, <span class="refTitle">"Programming Motherfucker, do you speak it?"</span>, <span>&lt;<a href="http://programming-motherfucker.com">http://programming-motherfucker.com</a>&gt;</span>. </dd>
<span>, &lt;<a href="http://programming-motherfucker.com">http://programming-motherfucker.com</a>&gt;</span>. </dd> <dd class="break"></dd>
<dt id="THE-TAO-OF-PROGRAMMING">[THE-TAO-OF-PROGRAMMING]</dt> <dt id="THE-TAO-OF-PROGRAMMING">[THE-TAO-OF-PROGRAMMING]</dt>
<dd> <dd>
<span class="refAuthor">James, G.</span>, <span class="refTitle">"The Tao of Programming"</span>, <span class="refContent"></span>, <time datetime="2021-10">October 2021</time> <span class="refAuthor">James, G.</span>, <span class="refTitle">"The Tao of Programming"</span>, <span>&lt;<a href="http://www.mit.edu/~xela/tao.html">http://www.mit.edu/~xela/tao.html</a>&gt;</span>. </dd>
<span>, &lt;<a href="http://www.mit.edu/~xela/tao.html">http://www.mit.edu/~xela/tao.html</a>&gt;</span>. </dd> <dd class="break"></dd>
</dl> </dl>
</section> </section>
<div id="authors-addresses"> <div id="authors-addresses">
<section id="section-appendix.a"> <section id="appendix-A">
<h2 id="name-authors-addresses"> <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
</h2> </h2>
<address class="vcard"> <address class="vcard">
<div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div> <div dir="auto" class="left"><span class="fn nameRole">Alexandre Dulaunoy</span></div>
<div dir="auto" class="left"><span class="fn nameRole">Alexandre Dulaunoy</span></div> <div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div>
<div dir="auto" class="left"><span class="street-address">16, bd d'Avranches</span></div> <div dir="auto" class="left"><span class="street-address">122, rue Adolphe Fischer</span></div>
<div dir="auto" class="left">L-<span class="postal-code">L-1160</span> <span class="locality">Luxembourg</span> <div dir="auto" class="left">L-<span class="postal-code">L-1521</span> <span class="locality">Luxembourg</span>
</div> </div>
<div dir="auto" class="left"><span class="country-name">Luxembourg</span></div> <div dir="auto" class="left"><span class="country-name">Luxembourg</span></div>
<div class="tel"> <div class="tel">
@ -1171,10 +1447,10 @@ includes the act of simplifying or removing code to reduce the attack surface.<a
</div> </div>
</address> </address>
<address class="vcard"> <address class="vcard">
<div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div> <div dir="auto" class="left"><span class="fn nameRole">Andras Iklody</span></div>
<div dir="auto" class="left"><span class="fn nameRole">Andras Iklody</span></div> <div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div>
<div dir="auto" class="left"><span class="street-address">16, bd d'Avranches</span></div> <div dir="auto" class="left"><span class="street-address">122, rue Adolphe Fischer</span></div>
<div dir="auto" class="left">L-<span class="postal-code">L-1160</span> <span class="locality">Luxembourg</span> <div dir="auto" class="left">L-<span class="postal-code">L-1521</span> <span class="locality">Luxembourg</span>
</div> </div>
<div dir="auto" class="left"><span class="country-name">Luxembourg</span></div> <div dir="auto" class="left"><span class="country-name">Luxembourg</span></div>
<div class="tel"> <div class="tel">
@ -1188,45 +1464,13 @@ includes the act of simplifying or removing code to reduce the attack surface.<a
</address> </address>
</section> </section>
</div> </div>
<script>var toc = document.getElementById("toc"); <script>const toc = document.getElementById("toc");
var tocToggle = toc.querySelector("h2"); toc.querySelector("h2").addEventListener("click", e => {
var tocNav = toc.querySelector("nav"); toc.classList.toggle("active");
});
// mobile menu toggle toc.querySelector("nav").addEventListener("click", e => {
tocToggle.onclick = function(event) { toc.classList.remove("active");
if (window.innerWidth < 1024) {
var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display;
if (tocNavDisplay == "none") {
tocNav.style.display = "block";
} else {
tocNav.style.display = "none";
}
}
}
// toc anchor scroll to anchor
tocNav.addEventListener("click", function (event) {
event.preventDefault();
if (event.target.nodeName == 'A') {
if (window.innerWidth < 1024) {
tocNav.style.display = "none";
}
var href = event.target.getAttribute("href");
var anchorId = href.substr(1);
var anchor = document.getElementById(anchorId);
anchor.scrollIntoView(true);
window.history.pushState("","",href);
}
}); });
// switch toc mode when window resized
window.onresize = function () {
if (window.innerWidth < 1024) {
tocNav.style.display = "none";
} else {
tocNav.style.display = "block";
}
}
</script> </script>
</body> </body>
</html> </html>

56
raw.md.txt
View file

@ -5,11 +5,11 @@
Network Working Group A. Dulaunoy Network Working Group A. Dulaunoy
Internet-Draft A. Iklody Internet-Draft A. Iklody
Intended status: Informational CIRCL Intended status: Informational CIRCL
Expires: 4 April 2022 1 October 2021 Expires: 26 August 2023 22 February 2023
Programming Methodology Framework aka PMF Programming Methodology Framework aka PMF
draft-01 draft-02
Abstract Abstract
@ -37,30 +37,27 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 4 April 2022. This Internet-Draft will expire on 26 August 2023.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document.
extracted from this document must include Simplified BSD License text
Dulaunoy & Iklody Expires 4 April 2022 [Page 1]
Dulaunoy & Iklody Expires 26 August 2023 [Page 1]
Internet-Draft PMF - Programming Methodology Framework October 2021 Internet-Draft PMF - Programming Methodology Framework February 2023
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
@ -94,9 +91,7 @@ Table of Contents
* Compose a list of features to be implemented and use an iterative * Compose a list of features to be implemented and use an iterative
programming process. programming process.
* Enhance said features using trial and error programming. * Enhance said features using trial and error programming.
* Orchestrate your testing and integration processes using pragmatic * Orchestrate your testing and integration processes using pragmatic
programming. programming.
@ -109,9 +104,14 @@ Table of Contents
Dulaunoy & Iklody Expires 4 April 2022 [Page 2]
Dulaunoy & Iklody Expires 26 August 2023 [Page 2]
Internet-Draft PMF - Programming Methodology Framework October 2021 Internet-Draft PMF - Programming Methodology Framework February 2023
+----------+ +----------+
@ -145,9 +145,7 @@ Internet-Draft PMF - Programming Methodology Framework October 2021
the PMF methodology. the PMF methodology.
* Collect requirements of the users/customers. * Collect requirements of the users/customers.
* Provide programmers with the desired requirements. * Provide programmers with the desired requirements.
* Review whether the software to be delivered matches the * Review whether the software to be delivered matches the
requirements. requirements.
@ -165,9 +163,11 @@ Internet-Draft PMF - Programming Methodology Framework October 2021
Dulaunoy & Iklody Expires 4 April 2022 [Page 3]
Dulaunoy & Iklody Expires 26 August 2023 [Page 3]
Internet-Draft PMF - Programming Methodology Framework October 2021 Internet-Draft PMF - Programming Methodology Framework February 2023
3. Acknowledgements 3. Acknowledgements
@ -185,28 +185,28 @@ Internet-Draft PMF - Programming Methodology Framework October 2021
[PROGRAMMING-MF-MANIFESTO] [PROGRAMMING-MF-MANIFESTO]
Shaw, Z. A., "Programming Motherfucker, do you speak it?", Shaw, Z. A., "Programming Motherfucker, do you speak it?",
, October 2021, <http://programming-motherfucker.com>. <http://programming-motherfucker.com>.
[THE-TAO-OF-PROGRAMMING] [THE-TAO-OF-PROGRAMMING]
James, G., "The Tao of Programming", , October 2021, James, G., "The Tao of Programming",
<http://www.mit.edu/~xela/tao.html>. <http://www.mit.edu/~xela/tao.html>.
Authors' Addresses Authors' Addresses
Computer Incident Response Center Luxembourg
Alexandre Dulaunoy Alexandre Dulaunoy
16, bd d'Avranches Computer Incident Response Center Luxembourg
L-L-1160 Luxembourg 122, rue Adolphe Fischer
L-L-1521 Luxembourg
Luxembourg Luxembourg
Phone: +352 247 88444 Phone: +352 247 88444
Email: alexandre.dulaunoy@circl.lu Email: alexandre.dulaunoy@circl.lu
Computer Incident Response Center Luxembourg
Andras Iklody Andras Iklody
16, bd d'Avranches Computer Incident Response Center Luxembourg
L-L-1160 Luxembourg 122, rue Adolphe Fischer
L-L-1521 Luxembourg
Luxembourg Luxembourg
Phone: +352 247 88444 Phone: +352 247 88444
@ -221,4 +221,4 @@ Authors' Addresses
Dulaunoy & Iklody Expires 4 April 2022 [Page 4] Dulaunoy & Iklody Expires 26 August 2023 [Page 4]

20
raw.md.xml
View file

@ -1,22 +1,22 @@
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" --> <!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-01" submissionType="IETF" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="false" consensus="true"> <rfc version="3" ipr="trust200902" docName="draft-02" submissionType="independent" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="true">
<front> <front>
<title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title><seriesInfo value="draft-01" stream="independent" status="informational" name="Internet-Draft"></seriesInfo> <title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title><seriesInfo value="draft-02" stream="independent" status="informational" name="Internet-Draft"></seriesInfo>
<author initials="A." surname="Dulaunoy" fullname="Alexandre Dulaunoy"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>16, bd d'Avranches</street> <author initials="A." surname="Dulaunoy" fullname="Alexandre Dulaunoy"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>122, rue Adolphe Fischer</street>
<city>Luxembourg</city> <city>Luxembourg</city>
<code>L-1160</code> <code>L-1521</code>
<country>Luxembourg</country> <country>Luxembourg</country>
</postal><phone>+352 247 88444</phone> </postal><phone>+352 247 88444</phone>
<email>alexandre.dulaunoy@circl.lu</email> <email>alexandre.dulaunoy@circl.lu</email>
</address></author><author initials="A." surname="Iklody" fullname="Andras Iklody"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>16, bd d'Avranches</street> </address></author><author initials="A." surname="Iklody" fullname="Andras Iklody"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>122, rue Adolphe Fischer</street>
<city>Luxembourg</city> <city>Luxembourg</city>
<code>L-1160</code> <code>L-1521</code>
<country>Luxembourg</country> <country>Luxembourg</country>
</postal><phone>+352 247 88444</phone> </postal><phone>+352 247 88444</phone>
<email>andras.iklody@circl.lu</email> <email>andras.iklody@circl.lu</email>
</address></author><date year="2021" month="October" day="1"></date> </address></author><date year="2023" month="February" day="22"></date>
<area>Internet</area> <area>Internet</area>
<workgroup></workgroup> <workgroup></workgroup>
<keyword>software engineering</keyword> <keyword>software engineering</keyword>
@ -40,7 +40,7 @@ to official engineering or project documents describing one of the most used sof
<t>The PMF methodology was published as a manifesto later <xref target="PROGRAMMING-MF-MANIFESTO"></xref>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <xref target="THE-TAO-OF-PROGRAMMING"></xref> describes similar methodologies which strongly focus on coding, scripting and programming.</t> <t>The PMF methodology was published as a manifesto later <xref target="PROGRAMMING-MF-MANIFESTO"></xref>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <xref target="THE-TAO-OF-PROGRAMMING"></xref> describes similar methodologies which strongly focus on coding, scripting and programming.</t>
<t>The overall concept of PMF methodology follows the following process:</t> <t>The overall concept of PMF methodology follows the following process:</t>
<ul> <ul spacing="compact">
<li>Compose a list of features to be implemented and use an iterative programming process.</li> <li>Compose a list of features to be implemented and use an iterative programming process.</li>
<li>Enhance said features using trial and error programming.</li> <li>Enhance said features using trial and error programming.</li>
<li>Orchestrate your testing and integration processes using pragmatic programming.</li> <li>Orchestrate your testing and integration processes using pragmatic programming.</li>
@ -75,7 +75,7 @@ to official engineering or project documents describing one of the most used sof
The management process is meant to be complementary instead of interfering with The management process is meant to be complementary instead of interfering with
the programming aspect and solely serves to support the PMF methodology.</t> the programming aspect and solely serves to support the PMF methodology.</t>
<ul> <ul spacing="compact">
<li>Collect requirements of the users/customers.</li> <li>Collect requirements of the users/customers.</li>
<li>Provide programmers with the desired requirements.</li> <li>Provide programmers with the desired requirements.</li>
<li>Review whether the software to be delivered matches the requirements.</li> <li>Review whether the software to be delivered matches the requirements.</li>
@ -111,7 +111,6 @@ includes the act of simplifying or removing code to reduce the attack surface.</
<author fullname="Zed A. Shaw" surname="Shaw"></author> <author fullname="Zed A. Shaw" surname="Shaw"></author>
<date></date> <date></date>
</front> </front>
<refcontent></refcontent>
</reference> </reference>
<reference anchor="THE-TAO-OF-PROGRAMMING" target="http://www.mit.edu/~xela/tao.html"> <reference anchor="THE-TAO-OF-PROGRAMMING" target="http://www.mit.edu/~xela/tao.html">
<front> <front>
@ -119,7 +118,6 @@ includes the act of simplifying or removing code to reduce the attack surface.</
<author fullname="Geoffrey James" surname="James"></author> <author fullname="Geoffrey James" surname="James"></author>
<date></date> <date></date>
</front> </front>
<refcontent></refcontent>
</reference> </reference>
</references> </references>