adulau/pmf
1
0
Fork 0
mirror of https://github.com/adulau/pmf.git synced 2024-10-05 22:01:49 +00:00
Code Issues Projects Releases Packages Wiki Activity

update: [PMF] clarify that PMF is applicable for open source but also

Browse source 
proprietary software
This commit is contained in:
Alexandre Dulaunoy 2021-10-01 10:41:51 +02:00
parent a756bac046
commit f94580f3e9
Signed by: adulau
GPG key ID: 09E2CD4944E6CBCD
5 changed files with 1364 additions and 764 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Makefile
View file

@ -1,4 +1,4 @@
MMARK:=/home/adulau/git/mmark/mmark/mmark -xml2 -page MMARK:=mmark
docs = $(wildcard raw.md) docs = $(wildcard raw.md)

87
raw.md
View file

@ -1,41 +1,49 @@
% Title = "Programming Methodology Framework aka PMF" %%%
% abbrev = "PMF - Programming Methodology Framework" Title = "Programming Methodology Framework aka PMF"
% category = "info" abbrev = "PMF - Programming Methodology Framework"
% docName = "draft-dulaunoy-programming-methodology-framework" category = "info"
% ipr= "trust200902" docName = "draft-dulaunoy-programming-methodology-framework"
% area = "Internet" ipr= "trust200902"
% keyword = ["software engineering", "engineering", "pmf", "programming"] area = "Internet"
% keyword = ["software engineering", "engineering", "pmf", "programming"]
% date = 2019-04-11T00:00:00Z
% date = 2021-10-01T00:00:00Z
% [[author]]
% initials="A." [seriesInfo]
% surname="Dulaunoy" name = "Internet-Draft"
% fullname="Alexandre Dulaunoy" value = "draft-01"
% abbrev="CIRCL" stream = "independent"
% organization = "Computer Incident Response Center Luxembourg" status = "informational"
% [author.address]
% email = "alexandre.dulaunoy@circl.lu" [[author]]
% phone = "+352 247 88444" initials="A."
% [author.address.postal] surname="Dulaunoy"
% street = "16, bd d'Avranches" fullname="Alexandre Dulaunoy"
% city = "Luxembourg" abbrev="CIRCL"
% code = "L-1160" organization = "Computer Incident Response Center Luxembourg"
% country = "Luxembourg" [author.address]
% [[author]] email = "alexandre.dulaunoy@circl.lu"
% initials="A." phone = "+352 247 88444"
% surname="Iklody" [author.address.postal]
% fullname="Andras Iklody" street = "16, bd d'Avranches"
% abbrev="CIRCL" city = "Luxembourg"
% organization = "Computer Incident Response Center Luxembourg" code = "L-1160"
% [author.address] country = "Luxembourg"
% email = "andras.iklody@circl.lu" [[author]]
% phone = "+352 247 88444" initials="A."
% [author.address.postal] surname="Iklody"
% street = "16, bd d'Avranches" fullname="Andras Iklody"
% city = "Luxembourg" abbrev="CIRCL"
% code = "L-1160" organization = "Computer Incident Response Center Luxembourg"
% country = "Luxembourg" [author.address]
email = "andras.iklody@circl.lu"
phone = "+352 247 88444"
[author.address.postal]
street = "16, bd d'Avranches"
city = "Luxembourg"
code = "L-1160"
country = "Luxembourg"
%%%
.# Abstract .# Abstract
@ -85,6 +93,9 @@ A simplified overview of the process can be described as follow:
+----------+ +----------+
~~~~~ ~~~~~
The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both.
## Management and PMF methodology ## Management and PMF methodology
A simple management process is a requirement of the PMF methodology. A simple management process is a requirement of the PMF methodology.

1721
raw.md.html
View file

File diff suppressed because it is too large Load diff

132
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: October 13, 2019 April 11, 2019 Expires: 4 April 2022 1 October 2021
Programming Methodology Framework aka PMF Programming Methodology Framework aka PMF
draft-dulaunoy-programming-methodology-framework draft-01
Abstract Abstract
@ -37,30 +37,29 @@ 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 October 13, 2019. This Internet-Draft will expire on 4 April 2022.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2021 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 Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
Dulaunoy & Iklody Expires October 13, 2019 [Page 1] Dulaunoy & Iklody Expires 4 April 2022 [Page 1]
Internet-Draft PMF - Programming Methodology Framework April 2019 Internet-Draft PMF - Programming Methodology Framework October 2021
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Simplified BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
@ -69,20 +68,19 @@ Table of Contents
1.2. Conventions and Terminology . . . . . . . . . . . . . . . 3 1.2. Conventions and Terminology . . . . . . . . . . . . . . . 3
2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Normative References . . . . . . . . . . . . . . . . . . . . 4
4.1. Normative References . . . . . . . . . . . . . . . . . . 4 5. Informative References . . . . . . . . . . . . . . . . . . . 4
4.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
In 2011, Zed A. Shaw published a blog post which describes: In 2011, Zed A. Shaw published a blog post which describes:
I think I'm going to create the ultimate software development {align="left"} I think I'm going to create the ultimate software
methodology. It'll be revolutionary compared to others because it development methodology. It'll be revolutionary compared to others
will focus on the one thing that gets software done. Its entire because it will focus on the one thing that gets software done. Its
focus will be this one, glorious, completely useful activity for entire focus will be this one, glorious, completely useful activity
writing software. It's name even embodies the perfection of this for writing software. It's name even embodies the perfection of this
programming methodology. programming methodology.
The PMF methodology was published as a manifesto later The PMF methodology was published as a manifesto later
@ -94,12 +92,12 @@ Table of Contents
The overall concept of PMF methodology follows the following process: The overall concept of PMF methodology follows the following process:
o 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.
o Enhance said features using trial and error programming. * Enhance said features using trial and error programming.
o Orchestrate your testing and integration processes using pragmatic * Orchestrate your testing and integration processes using pragmatic
programming. programming.
Repeat the above process until the software is delivered. Repeat the above process until the software is delivered.
@ -109,30 +107,35 @@ Table of Contents
Dulaunoy & Iklody Expires October 13, 2019 [Page 2]
Dulaunoy & Iklody Expires 4 April 2022 [Page 2]
Internet-Draft PMF - Programming Methodology Framework April 2019 Internet-Draft PMF - Programming Methodology Framework October 2021
+----------+ +----------+
| | | |
| idea <------+ | idea <------+
| | | | | |
+----+-----+ | +----+-----+ |
| | | |
| | | |
+----v-----+ | +----v-----+ |
| | | it doesn't work | | | it doesn't work
| code | | | code | |
| | | | | |
+----+-----+ | +----+-----+ |
| | | |
| | | |
+----v-----+ | +----v-----+ |
| | | | | |
| release +------+ | release +------+
| | | |
+----------+ +----------+
The PMF methodology covers open source software along with
proprietary software and can be used interchangeably in both.
1.1. Management and PMF methodology 1.1. Management and PMF methodology
@ -141,11 +144,11 @@ Internet-Draft PMF - Programming Methodology Framework April 2019
interfering with the programming aspect and solely serves to support interfering with the programming aspect and solely serves to support
the PMF methodology. the PMF methodology.
o Collect requirements of the users/customers. * Collect requirements of the users/customers.
o Provide programmers with the desired requirements. * Provide programmers with the desired requirements.
o Review whether the software to be delivered matches the * Review whether the software to be delivered matches the
requirements. requirements.
1.2. Conventions and Terminology 1.2. Conventions and Terminology
@ -162,53 +165,48 @@ Internet-Draft PMF - Programming Methodology Framework April 2019
Dulaunoy & Iklody Expires 4 April 2022 [Page 3]
Dulaunoy & Iklody Expires October 13, 2019 [Page 3]
Internet-Draft PMF - Programming Methodology Framework April 2019 Internet-Draft PMF - Programming Methodology Framework October 2021
3. Acknowledgements 3. Acknowledgements
The authors wish to thank all the programmers who program. The authors wish to thank all the programmers who program.
4. References 4. Normative References
4.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
4.2. Informative References 5. Informative References
[PROGRAMMING-MF-MANIFESTO] [PROGRAMMING-MF-MANIFESTO]
Shaw, "Programming Motherfucker, do you speak it?", Shaw, Z. A., "Programming Motherfucker, do you speak it?",
<http://programming-motherfucker.com>. , October 2021, <http://programming-motherfucker.com>.
[THE-TAO-OF-PROGRAMMING] [THE-TAO-OF-PROGRAMMING]
James, "The Tao of Programming", James, G., "The Tao of Programming", , October 2021,
<http://www.mit.edu/~xela/tao.html>. <http://www.mit.edu/~xela/tao.html>.
Authors' Addresses Authors' Addresses
Alexandre Dulaunoy
Computer Incident Response Center Luxembourg Computer Incident Response Center Luxembourg
Alexandre Dulaunoy
16, bd d'Avranches 16, bd d'Avranches
Luxembourg L-1160 L-L-1160 Luxembourg
Luxembourg Luxembourg
Phone: +352 247 88444 Phone: +352 247 88444
Email: alexandre.dulaunoy@circl.lu Email: alexandre.dulaunoy@circl.lu
Andras Iklody
Computer Incident Response Center Luxembourg Computer Incident Response Center Luxembourg
Andras Iklody
16, bd d'Avranches 16, bd d'Avranches
Luxembourg L-1160 L-L-1160 Luxembourg
Luxembourg Luxembourg
Phone: +352 247 88444 Phone: +352 247 88444
@ -221,4 +219,6 @@ Authors' Addresses
Dulaunoy & Iklody Expires October 13, 2019 [Page 4]
Dulaunoy & Iklody Expires 4 April 2022 [Page 4]

156
raw.md.xml
View file

@ -1,49 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' []> <!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc ipr="trust200902" category="info" docName="draft-dulaunoy-programming-methodology-framework"> <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 toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc private=""?>
<?rfc topblock="yes"?>
<?rfc comments="no"?>
<front> <front>
<title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title> <title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title><seriesInfo value="draft-01" 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>16, bd d'Avranches</street>
<city>Luxembourg</city> <city>Luxembourg</city>
<code>L-1160</code> <code>L-1160</code>
<country>Luxembourg</country> <country>Luxembourg</country>
<region></region> </postal><phone>+352 247 88444</phone>
</postal>
<phone>+352 247 88444</phone>
<email>alexandre.dulaunoy@circl.lu</email> <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>
</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> <city>Luxembourg</city>
<code>L-1160</code> <code>L-1160</code>
<country>Luxembourg</country> <country>Luxembourg</country>
<region></region> </postal><phone>+352 247 88444</phone>
</postal>
<phone>+352 247 88444</phone>
<email>andras.iklody@circl.lu</email> <email>andras.iklody@circl.lu</email>
<uri></uri> </address></author><date year="2021" month="October" day="1"></date>
</address>
</author>
<date year="2019" month="April" day="11"/>
<area>Internet</area> <area>Internet</area>
<workgroup></workgroup> <workgroup></workgroup>
<keyword>software engineering</keyword> <keyword>software engineering</keyword>
@ -51,42 +24,31 @@
<keyword>pmf</keyword> <keyword>pmf</keyword>
<keyword>programming</keyword> <keyword>programming</keyword>
<abstract> <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 <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"></xref> 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.</t>
</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction" title="Introduction"> <section anchor="introduction"><name>Introduction</name>
<t>In 2011, Zed A. Shaw published a blog post which describes: <t>In 2011, Zed A. Shaw published a blog post which describes:</t>
</t> <t>{align=&quot;left&quot;} 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>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>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> <t>The overall concept of PMF methodology follows the following process:</t>
<t>The PMF 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 the following process:
</t>
<t>
<list style="symbols">
<t>Compose a list of features to be implemented and use an iterative programming process.</t>
<t>Enhance said features using trial and error programming.</t>
<t>Orchestrate your testing and integration processes using pragmatic programming.</t>
</list>
</t>
<t>Repeat the above process until the software is delivered.
</t>
<t>A simplified overview of the process can be described as follow:
</t>
<figure align="center"><artwork align="center" type="ascii-art"> <ul>
+----------+ <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>Orchestrate your testing and integration processes using pragmatic programming.</li>
</ul>
<t>Repeat the above process until the software is delivered.</t>
<t>A simplified overview of the process can be described as follow:</t>
<sourcecode type="ascii-art">+----------+
| | | |
| idea &lt;------+ | idea &lt;------+
| | | | | |
@ -105,62 +67,62 @@ to official engineering or project documents describing one of the most used sof
| release +------+ | release +------+
| | | |
+----------+ +----------+
</artwork></figure> </sourcecode>
<t>The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both.</t>
<section anchor="management-and-pmf-methodology" title="Management and PMF methodology"> <section anchor="management-and-pmf-methodology"><name>Management and PMF methodology</name>
<t>A simple management process is a requirement of the PMF methodology. <t>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. the programming aspect and solely serves to support the PMF methodology.</t>
</t>
<t> <ul>
<list style="symbols"> <li>Collect requirements of the users/customers.</li>
<t>Collect requirements of the users/customers.</t> <li>Provide programmers with the desired requirements.</li>
<t>Provide programmers with the desired requirements.</t> <li>Review whether the software to be delivered matches the requirements.</li>
<t>Review whether the software to be delivered matches the requirements.</t> </ul>
</list>
</t>
</section> </section>
<section anchor="conventions-and-terminology" title="Conventions and Terminology"> <section anchor="conventions-and-terminology"><name>Conventions and Terminology</name>
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, <t>The key words &quot;<bcp14>MUST</bcp14>&quot;, &quot;<bcp14>MUST NOT</bcp14>&quot;, &quot;<bcp14>REQUIRED</bcp14>&quot;, &quot;<bcp14>SHALL</bcp14>&quot;, &quot;<bcp14>SHALL NOT</bcp14>&quot;,
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this &quot;<bcp14>SHOULD</bcp14>&quot;, &quot;<bcp14>SHOULD NOT</bcp14>&quot;, &quot;<bcp14>RECOMMENDED</bcp14>&quot;, &quot;<bcp14>MAY</bcp14>&quot;, and &quot;<bcp14>OPTIONAL</bcp14>&quot; in this
document are to be interpreted as described in RFC 2119 <xref target="RFC2119"/>. document are to be interpreted as described in RFC 2119 <xref target="RFC2119"></xref>.</t>
</t>
</section> </section>
</section> </section>
<section anchor="security-considerations" title="Security Considerations"> <section anchor="security-considerations"><name>Security Considerations</name>
<t>Secure and defensive programming can only come by practicing programming and this also <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. includes the act of simplifying or removing code to reduce the attack surface.</t>
</t>
</section> </section>
<section anchor="acknowledgements" title="Acknowledgements"> <section anchor="acknowledgements"><name>Acknowledgements</name>
<t>The authors wish to thank all the programmers who program. <t>The authors wish to thank all the programmers who program.</t>
</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references><name>Normative References</name>
<?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
</references> </references>
<references title="Informative References"> <references><name>Informative References</name>
<reference anchor='PROGRAMMING-MF-MANIFESTO' target='http://programming-motherfucker.com'> <reference anchor="PROGRAMMING-MF-MANIFESTO" target="http://programming-motherfucker.com">
<front> <front>
<title>Programming Motherfucker, do you speak it?</title> <title>Programming Motherfucker, do you speak it?</title>
<author initials='' surname='Shaw' fullname='Zed A. 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>
<title>The Tao of Programming</title> <title>The Tao of Programming</title>
<author initials='' surname='James' fullname='Geoffrey James'></author> <author fullname="Geoffrey James" surname="James"></author>
<date></date> <date></date>
</front> </front>
<refcontent></refcontent>
</reference> </reference>
</references> </references>
</back> </back>
</rfc> </rfc>