adulau/pmf
1
0
Fork 0
mirror of https://github.com/adulau/pmf.git synced 2024-12-22 00:35:59 +00:00
Code Issues Projects Releases Packages Wiki Activity

First version of the PMF document

Browse source
This commit is contained in:
Alexandre Dulaunoy 2017-09-27 09:52:58 +02:00
commit 9537370c86
Signed by: adulau
GPG key ID: 09E2CD4944E6CBCD
5 changed files with 1066 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
Makefile Normal file
View file

@ -0,0 +1,9 @@
MMARK:=/home/adulau/git/mmark/mmark/mmark -xml2 -page
docs = $(wildcard *.md)
all: $(docs)
$(MMARK) $< > $<.xml
xml2rfc --text $<.xml
xml2rfc --html $<.xml

117
raw.md Normal file
View file

@ -0,0 +1,117 @@
% Title = "Programming Methodology Framework aka PMF"
% abbrev = "PMF - Programming Methodology Framework"
% category = "info"
% docName = "draft-dulaunoy-programming-methodology-framework"
% ipr= "trust200902"
% area = "Security"
%
% date = 2017-09-27T00:00:00Z
%
% [[author]]
% initials="A."
% surname="Dulaunoy"
% fullname="Alexandre Dulaunoy"
% abbrev="CIRCL"
% organization = "Computer Incident Response Center Luxembourg"
% [author.address]
% email = "alexandre.dulaunoy@circl.lu"
% phone = "+352 247 88444"
% [author.address.postal]
% street = "16, bd d'Avranches"
% city = "Luxembourg"
% code = "L-1611"
% country = "Luxembourg"
% [[author]]
% initials="A."
% surname="Iklody"
% fullname="Andras Iklody"
% abbrev="CIRCL"
% organization = "Computer Incident Response Center Luxembourg"
% [author.address]
% email = "andras.iklody@circl.lu"
% phone = "+352 247 88444"
% [author.address.postal]
% street = " 16, bd d'Avranches"
% city = "Luxembourg"
% code = "L-1611"
% country = "Luxembourg"
.# Abstract
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 [@?PROGRAMMING-MF-MANIFESTO] which
describes a natural approach to software engineering especially on the strong focus towards the act of programming. The PM methodology uses a soft naming to allow a non-partisan reference
into official engineering or project documents to describe one of the most used software engineering methodology.
{mainmatter}
# Introduction
In 2011, Zed A. Shaw published a blog post which describes:
{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.
The programming methodology was published as a manifesto later [@?PROGRAMMING-MF-MANIFESTO]. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The [@?THE-TAO-OF-PROGRAMMING] describes similar methodologies which strongly focus on coding, scripting and programming.
The overall concept of PMF methodology follows this iteration:
- Write a list of things to be done and use an iterative programming process.
- Do some of the things with additional programming.
- Build testing and tests using programming.
This process is run in a while loop until the software is delivered.
## Management and PMF methodology
A simple management process is required in addition to the PMF methodology.
The management process is complementary to the PMF metholody and not interfering with
the programming aspect. The management process is there to support the PMF methodology.
- Review requirements of the users/customers by asking them.
- Give the list of things to be done to the programmers.
- Review the delivered software to see if it matches the requirements.
## Conventions and Terminology
The key words "**MUST**", "**MUST NOT**", "**REQUIRED**", "**SHALL**", "**SHALL NOT**",
"**SHOULD**", "**SHOULD NOT**", "**RECOMMENDED**", "**MAY**", and "**OPTIONAL**" in this
document are to be interpreted as described in RFC 2119 [@!RFC2119].
# Security Considerations
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.
# Acknowledgements
The authors wish to thank all the programmers who program.
<reference anchor='PROGRAMMING-MF-MANIFESTO' target='http://programming-motherfucker.com'>
<front>
<title>Programming Motherfucker, do you speak it?</title>
<author initials='' surname='Shaw' fullname='Zed A. Shaw'></author>
<date></date>
</front>
</reference>
<reference anchor='THE-TAO-OF-PROGRAMMING' target='http://www.mit.edu/~xela/tao.html'>
<front>
<title>The Tao of Programming</title>
<author initials='' surname='James' fullname='Geoffrey James'></author>
<date></date>
</front>
</reference>
<reference anchor='JSON-SCHEMA' target='https://tools.ietf.org/html/draft-wright-json-schema'>
<front>
<title>JSON Schema: A Media Type for Describing JSON Documents</title>
<author initials='' surname='' fullname='Austin Wright'></author>
<date year="2016"></date>
</front>
</reference>
{backmatter}

578
raw.md.html Normal file
View file

@ -0,0 +1,578 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>Programming Methodology Framework aka PMF</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents"/>
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction"/>
<link href="#rfc.section.1.1" rel="Chapter" title="1.1 Management and PMF methodology"/>
<link href="#rfc.section.1.2" rel="Chapter" title="1.2 Conventions and Terminology"/>
<link href="#rfc.section.2" rel="Chapter" title="2 Security Considerations"/>
<link href="#rfc.section.3" rel="Chapter" title="3 Acknowledgements"/>
<link href="#rfc.references" rel="Chapter" title="4 References"/>
<link href="#rfc.references.1" rel="Chapter" title="4.1 Normative References"/>
<link href="#rfc.references.2" rel="Chapter" title="4.2 Informative References"/>
<link href="#rfc.authors" rel="Chapter"/>
<meta name="generator" content="xml2rfc version 2.5.1 - http://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Dulaunoy, A. and A. Iklody" />
<meta name="dct.identifier" content="urn:ietf:id:draft-dulaunoy-programming-methodology-framework" />
<meta name="dct.issued" scheme="ISO8601" content="2017-9-27" />
<meta name="dct.abstract" 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 " />
<meta name="description" 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 " />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left">Network Working Group</td>
<td class="right">A. Dulaunoy</td>
</tr>
<tr>
<td class="left">Internet-Draft</td>
<td class="right">A. Iklody</td>
</tr>
<tr>
<td class="left">Intended status: Informational</td>
<td class="right">CIRCL</td>
</tr>
<tr>
<td class="left">Expires: March 31, 2018</td>
<td class="right">September 27, 2017</td>
</tr>
</tbody>
</table>
<p class="title">Programming Methodology Framework aka PMF<br />
<span class="filename">draft-dulaunoy-programming-methodology-framework</span></p>
<h1 id="rfc.abstract">
<a href="#rfc.abstract">Abstract</a>
</h1>
<p>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 <a href="#PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</a> which describes a natural approach to software engineering especially on the strong focus towards the act of programming. The PM methodology uses a soft naming to allow a non-partisan reference into official engineering or project documents to describe one of the most used software engineering methodology. </p>
<h1 id="rfc.status">
<a href="#rfc.status">Status of This Memo</a>
</h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on March 31, 2018.</p>
<h1 id="rfc.copyrightnotice">
<a href="#rfc.copyrightnotice">Copyright Notice</a>
</h1>
<p>Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this 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.</p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a></li>
<ul><li>1.1. <a href="#rfc.section.1.1">Management and PMF methodology</a></li>
<li>1.2. <a href="#rfc.section.1.2">Conventions and Terminology</a></li>
</ul><li>2. <a href="#rfc.section.2">Security Considerations</a></li>
<li>3. <a href="#rfc.section.3">Acknowledgements</a></li>
<li>4. <a href="#rfc.references">References</a></li>
<ul><li>4.1. <a href="#rfc.references.1">Normative References</a></li>
<li>4.2. <a href="#rfc.references.2">Informative References</a></li>
</ul><li><a href="#rfc.authors">Authors' Addresses</a></li>
</ul>
<h1 id="rfc.section.1"><a href="#rfc.section.1">1.</a> <a href="#introduction" id="introduction">Introduction</a></h1>
<p id="rfc.section.1.p.1">In 2011, Zed A. Shaw published a blog post which describes: </p>
<p id="rfc.section.1.p.2">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. </p>
<p id="rfc.section.1.p.3">The programming methodology was published as a manifesto later <a href="#PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</a>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <a href="#THE-TAO-OF-PROGRAMMING">[THE-TAO-OF-PROGRAMMING]</a> describes similar methodologies which strongly focus on coding, scripting and programming. </p>
<p id="rfc.section.1.p.4">The overall concept of PMF methodology follows this iteration: </p>
<p/>
<ul>
<li>Write a list of things to be done and use an iterative programming process.</li>
<li>Do some of the things with additional programming.</li>
<li>Build testing and tests using programming.</li>
</ul>
<p> </p>
<p id="rfc.section.1.p.6">This process is run in a while loop until the software is delivered. </p>
<h1 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1.</a> <a href="#management-and-pmf-methodology" id="management-and-pmf-methodology">Management and PMF methodology</a></h1>
<p id="rfc.section.1.1.p.1">A simple management process is required in addition to the PMF methodology. The management process is complementary to the PMF metholody and not interfering with the programming aspect. The management process is there to support the PMF methodology. </p>
<p/>
<ul>
<li>Review requirements of the users/customers by asking them.</li>
<li>Give the list of things to be done to the programmers.</li>
<li>Review the delivered software to see if it matches the requirements.</li>
</ul>
<p> </p>
<h1 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2.</a> <a href="#conventions-and-terminology" id="conventions-and-terminology">Conventions and Terminology</a></h1>
<p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 <a href="#RFC2119">[RFC2119]</a>. </p>
<h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a href="#security-considerations" id="security-considerations">Security Considerations</a></h1>
<p id="rfc.section.2.p.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. </p>
<h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a href="#acknowledgements" id="acknowledgements">Acknowledgements</a></h1>
<p id="rfc.section.3.p.1">The authors wish to thank all the programmers who program. </p>
<h1 id="rfc.references"><a href="#rfc.references">4.</a> References</h1>
<h1 id="rfc.references.1"><a href="#rfc.references.1">4.1.</a> Normative References</h1>
<table>
<tbody>
<tr>
<td class="reference">
<b id="RFC2119">[RFC2119]</b>
</td>
<td class="top"><a>Bradner, S.</a>, "<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.</td>
</tr>
</tbody>
</table>
<h1 id="rfc.references.2"><a href="#rfc.references.2">4.2.</a> Informative References</h1>
<table>
<tbody>
<tr>
<td class="reference">
<b id="PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</b>
</td>
<td class="top"><a>Shaw, </a>, "<a href="http://programming-motherfucker.com">Programming Motherfucker, do you speak it?</a>"</td>
</tr>
<tr>
<td class="reference">
<b id="THE-TAO-OF-PROGRAMMING">[THE-TAO-OF-PROGRAMMING]</b>
</td>
<td class="top"><a>James, </a>, "<a href="http://www.mit.edu/~xela/tao.html">The Tao of Programming</a>"</td>
</tr>
</tbody>
</table>
<h1 id="rfc.authors">
<a href="#rfc.authors">Authors' Addresses</a>
</h1>
<div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Alexandre Dulaunoy</span>
<span class="n hidden">
<span class="family-name">Dulaunoy</span>
</span>
</span>
<span class="org vcardline">Computer Incident Response Center Luxembourg</span>
<span class="adr">
<span class="vcardline">16, bd d'Avranches</span>
<span class="vcardline">
<span class="locality">Luxembourg</span>,
<span class="region"></span>
<span class="code">L-1611</span>
</span>
<span class="country-name vcardline">Luxembourg</span>
</span>
<span class="vcardline">Phone: +352 247 88444</span>
<span class="vcardline">EMail: <a href="mailto:alexandre.dulaunoy@circl.lu">alexandre.dulaunoy@circl.lu</a></span>
</address>
</div><div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Andras Iklody</span>
<span class="n hidden">
<span class="family-name">Iklody</span>
</span>
</span>
<span class="org vcardline">Computer Incident Response Center Luxembourg</span>
<span class="adr">
<span class="vcardline">16, bd d'Avranches</span>
<span class="vcardline">
<span class="locality">Luxembourg</span>,
<span class="region"></span>
<span class="code">L-1611</span>
</span>
<span class="country-name vcardline">Luxembourg</span>
</span>
<span class="vcardline">Phone: +352 247 88444</span>
<span class="vcardline">EMail: <a href="mailto:andras.iklody@circl.lu">andras.iklody@circl.lu</a></span>
</address>
</div>
</body>
</html>

224
raw.md.txt Normal file
View file

@ -0,0 +1,224 @@
Network Working Group A. Dulaunoy
Internet-Draft A. Iklody
Intended status: Informational CIRCL
Expires: March 31, 2018 September 27, 2017
Programming Methodology Framework aka PMF
draft-dulaunoy-programming-methodology-framework
Abstract
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 [PROGRAMMING-MF-MANIFESTO] which
describes a natural approach to software engineering especially on
the strong focus towards the act of programming. The PM methodology
uses a soft naming to allow a non-partisan reference into official
engineering or project documents to describe one of the most used
software engineering methodology.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 31, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Dulaunoy & Iklody Expires March 31, 2018 [Page 1]
Internet-Draft PMF - Programming Methodology Framework September 2017
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Management and PMF methodology . . . . . . . . . . . . . 3
1.2. Conventions and Terminology . . . . . . . . . . . . . . . 3
2. Security Considerations . . . . . . . . . . . . . . . . . . . 3
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Normative References . . . . . . . . . . . . . . . . . . 3
4.2. Informative References . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
In 2011, Zed A. Shaw published a blog post which describes:
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.
The programming methodology was published as a manifesto later
[PROGRAMMING-MF-MANIFESTO]. The manifesto clearly describes the
focus on programming to avoid the surrounding management overhead and
pivot towards the delivery of the software. The
[THE-TAO-OF-PROGRAMMING] describes similar methodologies which
strongly focus on coding, scripting and programming.
The overall concept of PMF methodology follows this iteration:
o Write a list of things to be done and use an iterative programming
process.
o Do some of the things with additional programming.
o Build testing and tests using programming.
This process is run in a while loop until the software is delivered.
Dulaunoy & Iklody Expires March 31, 2018 [Page 2]
Internet-Draft PMF - Programming Methodology Framework September 2017
1.1. Management and PMF methodology
A simple management process is required in addition to the PMF
methodology. The management process is complementary to the PMF
metholody and not interfering with the programming aspect. The
management process is there to support the PMF methodology.
o Review requirements of the users/customers by asking them.
o Give the list of things to be done to the programmers.
o Review the delivered software to see if it matches the
requirements.
1.2. Conventions and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Security Considerations
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.
3. Acknowledgements
The authors wish to thank all the programmers who program.
4. References
4.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>.
4.2. Informative References
[PROGRAMMING-MF-MANIFESTO]
Shaw, , "Programming Motherfucker, do you speak it?",
<http://programming-motherfucker.com>.
[THE-TAO-OF-PROGRAMMING]
James, , "The Tao of Programming",
<http://www.mit.edu/~xela/tao.html>.
Dulaunoy & Iklody Expires March 31, 2018 [Page 3]
Internet-Draft PMF - Programming Methodology Framework September 2017
Authors' Addresses
Alexandre Dulaunoy
Computer Incident Response Center Luxembourg
16, bd d'Avranches
Luxembourg L-1611
Luxembourg
Phone: +352 247 88444
Email: alexandre.dulaunoy@circl.lu
Andras Iklody
Computer Incident Response Center Luxembourg
16, bd d'Avranches
Luxembourg L-1611
Luxembourg
Phone: +352 247 88444
Email: andras.iklody@circl.lu
Dulaunoy & Iklody Expires March 31, 2018 [Page 4]

138
raw.md.xml Normal file
View file

@ -0,0 +1,138 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' []>
<rfc ipr="trust200902" category="info" docName="draft-dulaunoy-programming-methodology-framework">
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc private=""?>
<?rfc topblock="yes"?>
<?rfc comments="no"?>
<front>
<title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title>
<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>
<city>Luxembourg</city>
<code>L-1611</code>
<country>Luxembourg</country>
<region></region>
</postal>
<phone>+352 247 88444</phone>
<email>alexandre.dulaunoy@circl.lu</email>
<uri></uri>
</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>
<city>Luxembourg</city>
<code>L-1611</code>
<country>Luxembourg</country>
<region></region>
</postal>
<phone>+352 247 88444</phone>
<email>andras.iklody@circl.lu</email>
<uri></uri>
</address>
</author>
<date year="2017" month="September" day="27"/>
<area>Security</area>
<workgroup></workgroup>
<abstract>
<t>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 <xref target="PROGRAMMING-MF-MANIFESTO"/> which
describes a natural approach to software engineering especially on the strong focus towards the act of programming. The PM methodology uses a soft naming to allow a non-partisan reference
into official engineering or project documents to describe one of the most used software engineering methodology.
</t>
</abstract>
</front>
<middle>
<section anchor="introduction" title="Introduction">
<t>In 2011, Zed A. Shaw published a blog post which describes:
</t>
<t>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.
</t>
<t>The programming methodology was published as a manifesto later <xref target="PROGRAMMING-MF-MANIFESTO"/>. 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"/> describes similar methodologies which strongly focus on coding, scripting and programming.
</t>
<t>The overall concept of PMF methodology follows this iteration:
</t>
<t>
<list style="symbols">
<t>Write a list of things to be done and use an iterative programming process.</t>
<t>Do some of the things with additional programming.</t>
<t>Build testing and tests using programming.</t>
</list>
</t>
<t>This process is run in a while loop until the software is delivered.
</t>
<section anchor="management-and-pmf-methodology" title="Management and PMF methodology">
<t>A simple management process is required in addition to the PMF methodology.
The management process is complementary to the PMF metholody and not interfering with
the programming aspect. The management process is there to support the PMF methodology.
</t>
<t>
<list style="symbols">
<t>Review requirements of the users/customers by asking them.</t>
<t>Give the list of things to be done to the programmers.</t>
<t>Review the delivered software to see if it matches the requirements.</t>
</list>
</t>
</section>
<section anchor="conventions-and-terminology" title="Conventions and Terminology">
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
document are to be interpreted as described in RFC 2119 <xref target="RFC2119"/>.
</t>
</section>
</section>
<section anchor="security-considerations" title="Security Considerations">
<t>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.
</t>
</section>
<section anchor="acknowledgements" title="Acknowledgements">
<t>The authors wish to thank all the programmers who program.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
</references>
<references title="Informative References">
<reference anchor='PROGRAMMING-MF-MANIFESTO' target='http://programming-motherfucker.com'>
<front>
<title>Programming Motherfucker, do you speak it?</title>
<author initials='' surname='Shaw' fullname='Zed A. Shaw'></author>
<date></date>
</front>
</reference>
<reference anchor='THE-TAO-OF-PROGRAMMING' target='http://www.mit.edu/~xela/tao.html'>
<front>
<title>The Tao of Programming</title>
<author initials='' surname='James' fullname='Geoffrey James'></author>
<date></date>
</front>
</reference>
</references>
</back>
</rfc>