From f94580f3e914dc4e74a510a63ff7b3ab54a402a8 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Fri, 1 Oct 2021 10:41:51 +0200 Subject: [PATCH] update: [PMF] clarify that PMF is applicable for open source but also proprietary software --- Makefile | 2 +- raw.md | 87 +-- raw.md.html | 1751 ++++++++++++++++++++++++++++++++++----------------- raw.md.txt | 132 ++-- raw.md.xml | 156 ++--- 5 files changed, 1364 insertions(+), 764 deletions(-) diff --git a/Makefile b/Makefile index 5998158..aee2e8c 100644 --- a/Makefile +++ b/Makefile @@ -1,4 +1,4 @@ -MMARK:=/home/adulau/git/mmark/mmark/mmark -xml2 -page +MMARK:=mmark docs = $(wildcard raw.md) diff --git a/raw.md b/raw.md index 1d0c199..9b10fbe 100644 --- a/raw.md +++ b/raw.md @@ -1,41 +1,49 @@ -% Title = "Programming Methodology Framework aka PMF" -% abbrev = "PMF - Programming Methodology Framework" -% category = "info" -% docName = "draft-dulaunoy-programming-methodology-framework" -% ipr= "trust200902" -% area = "Internet" -% keyword = ["software engineering", "engineering", "pmf", "programming"] -% -% date = 2019-04-11T00: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-1160" -% 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-1160" -% country = "Luxembourg" +%%% +Title = "Programming Methodology Framework aka PMF" +abbrev = "PMF - Programming Methodology Framework" +category = "info" +docName = "draft-dulaunoy-programming-methodology-framework" +ipr= "trust200902" +area = "Internet" +keyword = ["software engineering", "engineering", "pmf", "programming"] + +date = 2021-10-01T00:00:00Z + +[seriesInfo] +name = "Internet-Draft" +value = "draft-01" +stream = "independent" +status = "informational" + +[[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-1160" + 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-1160" + country = "Luxembourg" +%%% .# 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 A simple management process is a requirement of the PMF methodology. diff --git a/raw.md.html b/raw.md.html index a4c5502..33ac9ab 100644 --- a/raw.md.html +++ b/raw.md.html @@ -1,488 +1,1060 @@ - + + + + + +Programming Methodology Framework aka PMF + + + + + + + + + + + +/* lists */ +ol, ul { + padding: 0; + margin: 0 0 1em 2em; +} +ol ol, ul ul, ol ul, ul ol { + margin-left: 1em; +} +li { + margin: 0 0 0.25em 0; +} +.ulCompact li { + margin: 0; +} +ul.empty, .ulEmpty { + list-style-type: none; +} +ul.empty li, .ulEmpty li { + margin-top: 0.5em; +} +ul.compact, .ulCompact, +ol.compact, .olCompact { + line-height: 100%; + margin: 0 0 0 2em; +} - - - - - - - - - - +/* definition lists */ +dl { +} +dl > dt { + float: left; + margin-right: 1em; +} +dl > dd { + margin-bottom: .8em; + min-height: 1.3em; +} +dl.compact > dd, dlCompact > dd { + margin-bottom: 0em; +} +dl > dd > dl { + margin-top: 0.5em; + margin-bottom: 0em; +} + +/* links */ +a { + text-decoration: none; + z-index: 2; +} +a[href] { + color: #3E8EDE; +} +a[href]:hover { + background-color: #f2f2f2; +} +figcaption a[href], +a[href].selfRef { + color: #222; +} +/* XXX probably not this: +a.selfRef:hover { + background-color: transparent; + cursor: default; +} */ + +/* Figures */ +tt, code, pre, code { + background-color: #f9f9f9; + font-family: 'Roboto Mono', monospace; +} +pre { + border: 1px solid #eee; + margin: 0; + padding: 1em; +} +img { + max-width: 100%; +} +figure { + margin: 0; +} +figure blockquote { + margin: 0.8em 0.4em 0.4em; +} +figcaption { + font-style: italic; + margin: 0 0 1em 0; +} +@media screen { + pre { + overflow-x: auto; + max-width: 100%; + max-width: calc(100% - 22px); + } +} + +/* aside, blockquote */ +aside, blockquote { + margin-left: 0; + padding: 1.2em 2em; +} +blockquote { + background-color: #f9f9f9; + border: 1px solid #ddd; + border-radius: 3px; + margin: 1em 0; +} +cite { + display: block; + text-align: right; + font-style: italic; +} + +/* tables */ +table { + width: 100%; + margin: 0 0 1em; + border-collapse: collapse; + border: 1px solid #eee; +} +th, td { + text-align: left; + vertical-align: top; + padding: 0.5em 0.75em; +} +th { + text-align: left; + background-color: #e9e9e9; +} +tr:nth-child(2n+1) > td { + background-color: #f5f5f5; +} +table caption { + font-style: italic; + margin: 0; + padding: 0; + text-align: left; +} +table p { + /* XXX to avoid bottom margin on table row signifiers. If paragraphs should + be allowed within tables more generally, it would be far better to select on a class. */ + margin: 0; +} + +/* pilcrow */ +a.pilcrow { + color: #777; + text-decoration: none; + visibility: hidden; + user-select: none; + -ms-user-select: none; + -o-user-select:none; + -moz-user-select: none; + -khtml-user-select: none; + -webkit-user-select: none; + -webkit-touch-callout: none; +} +@media screen { + aside:hover > a.pilcrow, + p:hover > a.pilcrow, + blockquote:hover > a.pilcrow, + div:hover > a.pilcrow, + li:hover > a.pilcrow, + pre:hover > a.pilcrow { + visibility: visible; + } + a.pilcrow:hover { + background-color: transparent; + } +} + +/* misc */ +hr { + border: 0; + border-top: 1px solid #eee; +} +.bcp14 { + font-variant: small-caps; +} + +.role { + font-variant: all-small-caps; +} + +/* info block */ +#identifiers { + margin: 0; + font-size: 0.9em; +} +#identifiers dt { + width: 3em; + clear: left; +} +#identifiers dd { + float: left; + margin-bottom: 0; +} +#identifiers .authors .author { + display: inline-block; + margin-right: 1.5em; +} +#identifiers .authors .org { + font-style: italic; +} + +/* The prepared/rendered info at the very bottom of the page */ +.docInfo { + color: #999; + font-size: 0.9em; + font-style: italic; + margin-top: 2em; +} +.docInfo .prepared { + float: left; +} +.docInfo .prepared { + float: right; +} + +/* table of contents */ +#toc { + padding: 0.75em 0 2em 0; + margin-bottom: 1em; +} +nav.toc ul { + margin: 0 0.5em 0 0; + padding: 0; + list-style: none; +} +nav.toc li { + line-height: 1.3em; + margin: 0.75em 0; + padding-left: 1.2em; + text-indent: -1.2em; +} +/* references */ +.references dt { + text-align: right; + font-weight: bold; + min-width: 7em; +} +.references dd { + margin-left: 8em; + overflow: auto; +} + +.refInstance { + margin-bottom: 1.25em; +} + +.references .ascii { + margin-bottom: 0.25em; +} + +/* index */ +.index ul { + margin: 0 0 0 1em; + padding: 0; + list-style: none; +} +.index ul ul { + margin: 0; +} +.index li { + margin: 0; + text-indent: -2em; + padding-left: 2em; + padding-bottom: 5px; +} +.indexIndex { + margin: 0.5em 0 1em; +} +.index a { + font-weight: 700; +} +/* make the index two-column on all but the smallest screens */ +@media (min-width: 600px) { + .index ul { + -moz-column-count: 2; + -moz-column-gap: 20px; + } + .index ul ul { + -moz-column-count: 1; + -moz-column-gap: 0; + } +} + +/* authors */ +address.vcard { + font-style: normal; + margin: 1em 0; +} + +address.vcard .nameRole { + font-weight: 700; + margin-left: 0; +} +address.vcard .label { + font-family: "Noto Sans",Arial,Helvetica,sans-serif; + margin: 0.5em 0; +} +address.vcard .type { + display: none; +} +.alternative-contact { + margin: 1.5em 0 1em; +} +hr.addr { + border-top: 1px dashed; + margin: 0; + color: #ddd; + max-width: calc(100% - 16px); +} + +/* temporary notes */ +.rfcEditorRemove::before { + position: absolute; + top: 0.2em; + right: 0.2em; + padding: 0.2em; + content: "The RFC Editor will remove this note"; + color: #b76427; + background-color: rgba(249, 232, 105, 0.3); +} +.rfcEditorRemove { + position: relative; + padding-top: 1.8em; + background-color: rgba(249, 232, 105, 0.3); + border-radius: 3px; +} +.cref { + background-color: rgba(249, 232, 105, 0.3); + padding: 2px 4px; +} +.crefSource { + font-style: italic; +} +/* alternative layout for smaller screens */ +@media screen and (max-width: 1023px) { + body { + padding-top: 2em; + } + #title { + padding: 1em 0; + } + h1 { + font-size: 24px; + } + h2 { + font-size: 20px; + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 38px; + } + #identifiers dd { + max-width: 60%; + } + #toc { + position: fixed; + z-index: 2; + top: 0; + right: 0; + padding: 0; + margin: 0; + background-color: inherit; + border-bottom: 1px solid #ccc; + } + #toc h2 { + margin: -1px 0 0 0; + padding: 4px 0 4px 6px; + padding-right: 1em; + min-width: 190px; + font-size: 1.1em; + text-align: right; + background-color: #444; + color: white; + cursor: pointer; + } + #toc h2::before { /* css hamburger */ + float: right; + position: relative; + width: 1em; + height: 1px; + left: -164px; + margin: 6px 0 0 0; + background: white none repeat scroll 0 0; + box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; + content: ""; + } + #toc nav { + display: none; + padding: 0.5em 1em 1em; + overflow: auto; + height: calc(100vh - 48px); + border-left: 1px solid #ddd; + } +} + +/* alternative layout for wide screens */ +@media screen and (min-width: 1024px) { + body { + max-width: 724px; + margin: 42px auto; + padding-left: 1.5em; + padding-right: 29em; + } + #toc { + position: fixed; + top: 42px; + right: 42px; + width: 25%; + margin: 0; + padding: 0 1em; + z-index: 1; + } + #toc h2 { + border-top: none; + border-bottom: 1px solid #ddd; + font-size: 1em; + font-weight: normal; + margin: 0; + padding: 0.25em 1em 1em 0; + } + #toc nav { + display: block; + height: calc(90vh - 84px); + bottom: 0; + padding: 0.5em 0 0; + overflow: auto; + } + img { /* future proofing */ + max-width: 100%; + height: auto; + } +} + +/* pagination */ +@media print { + body { + + width: 100%; + } + p { + orphans: 3; + widows: 3; + } + #n-copyright-notice { + border-bottom: none; + } + #toc, #n-introduction { + page-break-before: always; + } + #toc { + border-top: none; + padding-top: 0; + } + figure, pre { + page-break-inside: avoid; + } + figure { + overflow: scroll; + } + h1, h2, h3, h4, h5, h6 { + page-break-after: avoid; + } + h2+*, h3+*, h4+*, h5+*, h6+* { + page-break-before: avoid; + } + pre { + white-space: pre-wrap; + word-wrap: break-word; + font-size: 10pt; + } + table { + border: 1px solid #ddd; + } + td { + border-top: 1px solid #ddd; + } +} + +@page :first { + padding-top: 0; + @top-left { + content: normal; + border: none; + } + @top-center { + content: normal; + border: none; + } + @top-right { + content: normal; + border: none; + } +} + +@page { + size: A4; + margin-bottom: 45mm; + padding-top: 20px; +} + +/* Changes introduced to fix issues found during implementation */ + +/* Separate body from document info even without intervening H1 */ +section { + clear: both; +} - - +/* Top align author divs, to avoid names without organization dropping level with org names */ +.author { + vertical-align: top; +} - - - - - +/* Leave room in document info to show Internet-Draft on one line */ +#identifiers dt { + width: 8em; +} +/* Don't waste quite as much whitespace between label and value in doc info */ +#identifiers dd { + margin-left: 1em; +} + +/* Give floating toc a background color (needed when it's a div inside section */ +#toc { + background-color: white; +} + +/* Make the collapsed ToC header render white on gray also when it's a link */ +@media screen and (max-width: 1023px) { + #toc h2 a, + #toc h2 a:link, + #toc h2 a:focus, + #toc h2 a:hover, + #toc a.toplink, + #toc a.toplink:hover { + color: white; + background-color: #444; + text-decoration: none; + } +} + +/* Give the bottom of the ToC some whitespace */ +@media screen and (min-width: 1024px) { + #toc { + padding: 0 0 1em 1em; + } +} + +/* Style section numbers with more space between number and title */ +.section-number { + padding-right: 0.5em; +} + +/* prevent monospace from becoming overly large */ +tt, code, pre, code { + font-size: 95%; +} + +/* Fix the height/width aspect for ascii art*/ +.art-text pre { + line-height: 1.12; +} + +/* Add styling for a link in the ToC that points to the top of the document */ +a.toplink { + float: right; + margin-right: 0.5em; +} + +/* Fix the dl styling to match the RFC 7992 attributes */ +dl > dt, +dl.dlParallel > dt { + float: left; + margin-right: 1em; +} +dl.dlNewline > dt { + float: none; +} + +/* Provide styling for table cell text alignment */ +table td.text-left, +table th.text-left { + text-align: left; +} +table td.text-center, +table th.text-center { + text-align: center; +} +table td.text-right, +table th.text-right { + text-align: right; +} + +/* Make the alternative author contact informatio look less like just another + author, and group it closer with the primary author contact information */ +.alternative-contact { + margin: 0.5em 0 0.25em 0; +} +address .non-ascii { + margin: 0 0 0 2em; +} + +/* With it being possible to set tables with alignment + left, center, and right, { width: 100%; } does not make sense */ +table { + width: auto; +} + +/* Avoid reference text that sits in a block with very wide left margin, + because of a long floating dt label.*/ +.references dd { + overflow: visible; +} + +/* Control caption placement */ +caption { + caption-side: bottom; +} + +/* Limit the width of the author address vcard, so names in right-to-left + script don't end up on the other side of the page. */ + +address.vcard { + max-width: 20em; + margin-right: auto; +} + +/* For address alignment dependent on LTR or RTL scripts */ +address div.left { + text-align: left; +} +address div.right { + text-align: right; +} + +/* Provide table alignment support. We can't use the alignX classes above + since they do unwanted things with caption and other styling. */ +table.right { + margin-left: auto; + margin-right: 0; +} +table.center { + margin-left: auto; + margin-right: auto; +} +table.left { + margin-left: 0; + margin-right: auto; +} + +/* Give the table caption label the same styling as the figcaption */ +caption a[href] { + color: #222; +} + +@media print { + .toplink { + display: none; + } + + /* avoid overwriting the top border line with the ToC header */ + #toc { + padding-top: 1px; + } + + /* Avoid page breaks inside dl and author address entries */ + dd { + page-break-before: avoid; + } + .vcard { + page-break-inside: avoid; + } + +} +/* Avoid wrapping of URLs in references */ +.references a { + white-space: nowrap; +} +/* Tweak the bcp14 keyword presentation */ +.bcp14 { + font-variant: small-caps; + font-weight: bold; + font-size: 0.9em; +} +/* Tweak the invisible space above H* in order not to overlay links in text above */ + h2 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 31px; + } + h3 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 24px; + } + h4 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 24px; + } + + - + + + - - - - - - - - - - - - - -
Internet-DraftA. Iklody
Intended status: InformationalCIRCL
Expires: October 13, 2019April 11, 2019
- -

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 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.

-

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 https://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 October 13, 2019.

-

Copyright Notice

-

Copyright (c) 2019 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 (https://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.

- - -
-

Table of Contents

- + + + +
+
+

+1. 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 PMF 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 the following process:

    -
  • Compose a list of features to be implemented and use an iterative programming process.
    • -
  • Enhance said features using trial and error programming.
    • -
  • Orchestrate your testing and integration processes using pragmatic programming.
    • -
- -

-

Repeat the above process until the software is delivered.

-

A simplified overview of the process can be described as follow:

-
-+----------+
+
  • Compose a list of features to be implemented and use an iterative programming process.
+
    • 
+        
  • Enhance said features using trial and error programming.
+
    • 
+        
  • Orchestrate your testing and integration processes using pragmatic programming.
+
    • 
+      
+
    Repeat the above process until the software is delivered.
    
+
    A simplified overview of the process can be described as follow:
    
+
    
+
    +----------+
 |          |
 |   idea   <------+
 |          |      |
@@ -501,105 +1073,160 @@
 |  release +------+
 |          |
 +----------+
-
    
-
    
-1.1. Management and PMF methodology
-
    
-
    A simple management process is a requirement of the PMF methodology.  The management process is meant to be complementary instead of interfering with the programming aspect and solely serves to support the PMF methodology.  
    
-
    
-
-
      
-
    • Collect requirements of the users/customers.
      • 
-
    • Provide programmers with the desired requirements.
      • 
-
    • Review whether the software to be delivered 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.
    
-
    
-4.2. Informative References
    
-
-
-
-
-
-
-
-
-
-
    [PROGRAMMING-MF-MANIFESTO]
-Shaw, "Programming Motherfucker, do you speak it?"
    [THE-TAO-OF-PROGRAMMING]
-James, "The Tao of Programming"
    
-
    Authors' Addresses
    
-
    
-  
    
-	
-	  Alexandre Dulaunoy 
-	  
-	
-	Computer Incident Response Center Luxembourg
-	
-	  16, bd d'Avranches
-
-	  
-		Luxembourg,  
-		
-		L-1160
-	  
-	  Luxembourg
-	
-	Phone: +352 247 88444
-
-EMail: alexandre.dulaunoy@circl.lu
-
-  
    
-
    
-  
    
-	
-	  Andras Iklody 
-	  
-	
-	Computer Incident Response Center Luxembourg
-	
-	  16, bd d'Avranches
-
-	  
-		Luxembourg,  
-		
-		L-1160
-	  
-	  Luxembourg
-	
-	Phone: +352 247 88444
-
-EMail: andras.iklody@circl.lu
-
-  
    
+
    +

    The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both.

    +
    +
    +

    +1.1. Management and PMF methodology +

    +

    A simple management process is a requirement of the PMF methodology. +The management process is meant to be complementary instead of interfering with +the programming aspect and solely serves to support the PMF methodology.

    +
      +
    • Collect requirements of the users/customers. +
      • +
    • Provide programmers with the desired requirements. +
      • +
    • Review whether the software to be delivered 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. Normative References +

    +
    +
    [RFC2119]
    +
    +Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, + , <https://www.rfc-editor.org/info/rfc2119>.
    +
    +
    +
    +

    +5. Informative References +

    +
    +
    [PROGRAMMING-MF-MANIFESTO]
    +
    +Shaw, Z. A., "Programming Motherfucker, do you speak it?", , + , <http://programming-motherfucker.com>.
    +
    [THE-TAO-OF-PROGRAMMING]
    +
    +James, G., "The Tao of Programming", , + , <http://www.mit.edu/~xela/tao.html>.
    +
    +
    +
    +
    +

    +Authors' Addresses +

    +
    +
    Computer Incident Response Center Luxembourg
    +
    Alexandre Dulaunoy
    +
    16, bd d'Avranches
    +
    L-L-1160 Luxembourg +
    +
    Luxembourg
    +
    +Phone: ++352 247 88444 +
    + +
    +
    +
    Computer Incident Response Center Luxembourg
    +
    Andras Iklody
    +
    16, bd d'Avranches
    +
    L-L-1160 Luxembourg +
    +
    Luxembourg
    +
    +Phone: ++352 247 88444 +
    + +
    +
    +
    + diff --git a/raw.md.txt b/raw.md.txt index 3a7af64..8e4481b 100644 --- a/raw.md.txt +++ b/raw.md.txt @@ -5,11 +5,11 @@ Network Working Group A. Dulaunoy Internet-Draft A. Iklody Intended status: Informational CIRCL -Expires: October 13, 2019 April 11, 2019 +Expires: 4 April 2022 1 October 2021 Programming Methodology Framework aka PMF - draft-dulaunoy-programming-methodology-framework + draft-01 Abstract @@ -37,30 +37,29 @@ Status of This Memo 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 October 13, 2019. + This Internet-Draft will expire on 4 April 2022. 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. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents - (https://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 + Provisions Relating to IETF Documents (https://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 -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 - the Trust Legal Provisions and are provided without warranty as - described in the Simplified BSD License. + 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 @@ -69,20 +68,19 @@ Table of Contents 1.2. Conventions and Terminology . . . . . . . . . . . . . . . 3 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 - 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 4.1. Normative References . . . . . . . . . . . . . . . . . . 4 - 4.2. Informative References . . . . . . . . . . . . . . . . . 4 + 4. Normative References . . . . . . . . . . . . . . . . . . . . 4 + 5. Informative References . . . . . . . . . . . . . . . . . . . 4 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 + {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 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: - 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. - 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. 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 <------+ - | | | - +----+-----+ | - | | - | | - +----v-----+ | - | | | it doesn't work - | code | | - | | | - +----+-----+ | - | | - | | - +----v-----+ | - | | | - | release +------+ - | | - +----------+ + +----------+ + | | + | idea <------+ + | | | + +----+-----+ | + | | + | | + +----v-----+ | + | | | it doesn't work + | code | | + | | | + +----+-----+ | + | | + | | + +----v-----+ | + | | | + | 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 @@ -141,11 +144,11 @@ Internet-Draft PMF - Programming Methodology Framework April 2019 interfering with the programming aspect and solely serves to support 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. 1.2. Conventions and Terminology @@ -162,53 +165,48 @@ Internet-Draft PMF - Programming Methodology Framework April 2019 - - - -Dulaunoy & Iklody Expires October 13, 2019 [Page 3] +Dulaunoy & Iklody Expires 4 April 2022 [Page 3] -Internet-Draft PMF - Programming Methodology Framework April 2019 +Internet-Draft PMF - Programming Methodology Framework October 2021 3. Acknowledgements The authors wish to thank all the programmers who program. -4. References - -4.1. Normative References +4. 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, . -4.2. Informative References +5. Informative References [PROGRAMMING-MF-MANIFESTO] - Shaw, "Programming Motherfucker, do you speak it?", - . + Shaw, Z. A., "Programming Motherfucker, do you speak it?", + , October 2021, . [THE-TAO-OF-PROGRAMMING] - James, "The Tao of Programming", + James, G., "The Tao of Programming", , October 2021, . Authors' Addresses - Alexandre Dulaunoy Computer Incident Response Center Luxembourg + Alexandre Dulaunoy 16, bd d'Avranches - Luxembourg L-1160 + L-L-1160 Luxembourg Luxembourg Phone: +352 247 88444 Email: alexandre.dulaunoy@circl.lu - Andras Iklody Computer Incident Response Center Luxembourg + Andras Iklody 16, bd d'Avranches - Luxembourg L-1160 + L-L-1160 Luxembourg Luxembourg 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] diff --git a/raw.md.xml b/raw.md.xml index f057dca..879f24c 100644 --- a/raw.md.xml +++ b/raw.md.xml @@ -1,49 +1,22 @@ - - - - - - - - - - - + + + + -Programming Methodology Framework aka PMF - - -Computer Incident Response Center Luxembourg -
    - -16, bd d'Avranches +Programming Methodology Framework aka PMF +Computer Incident Response Center Luxembourg
    16, bd d'Avranches Luxembourg L-1160 Luxembourg - - -+352 247 88444 ++352 247 88444 alexandre.dulaunoy@circl.lu - -
    -     - -Computer Incident Response Center Luxembourg -
    - -16, bd d'Avranches +
    Computer Incident Response Center Luxembourg
    16, bd d'Avranches Luxembourg L-1160 Luxembourg - - -+352 247 88444 ++352 247 88444 andras.iklody@circl.lu - -
    -     - - +
     Internet software engineering @@ -51,42 +24,31 @@ pmf programming - -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 -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. -     -
    -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 PMF methodology was published as a manifesto later . The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The describes similar methodologies which strongly focus on coding, scripting and programming. - -The overall concept of PMF methodology follows the following process: - - - -Compose a list of features to be implemented and use an iterative programming process. -Enhance said features using trial and error programming. -Orchestrate your testing and integration processes using pragmatic programming. - - -Repeat the above process until the software is delivered. - -A simplified overview of the process can be described as follow: - +
    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 PMF methodology was published as a manifesto later . The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The describes similar methodologies which strongly focus on coding, scripting and programming. +The overall concept of PMF methodology follows the following process: -
    -+----------+ +
      +
    • Compose a list of features to be implemented and use an iterative programming process.
      • +
    • Enhance said features using trial and error programming.
      • +
    • Orchestrate your testing and integration processes using pragmatic programming.
      • +
    +Repeat the above process until the software is delivered. +A simplified overview of the process can be described as follow: + ++----------+ | | | idea <------+ | | | @@ -105,62 +67,62 @@ to official engineering or project documents describing one of the most used sof | release +------+ | | +----------+ -
    + +The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both. -
    +
    Management and PMF methodology A simple management process is a requirement of the PMF methodology. The management process is meant to be complementary instead of interfering with -the programming aspect and solely serves to support the PMF methodology. - - - -Collect requirements of the users/customers. -Provide programmers with the desired requirements. -Review whether the software to be delivered matches the requirements. - - +the programming aspect and solely serves to support the PMF methodology. + +
      +
    • Collect requirements of the users/customers.
      • +
    • Provide programmers with the desired requirements.
      • +
    • Review whether the software to be delivered matches the requirements.
      • +
    -
    -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 . - +
    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 .
    -
    +
    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. - +includes the act of simplifying or removing code to reduce the attack surface.
    -
    -The authors wish to thank all the programmers who program. - +
    Acknowledgements +The authors wish to thank all the programmers who program.
    + - - +Normative References + - - +Informative References + - Programming Motherfucker, do you speak it? - - + Programming Motherfucker, do you speak it? + + + - + - The Tao of Programming - - + The Tao of Programming + + + +