<metaname="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 "/>
<metaname="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 "/>
<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 <ahref="#PROGRAMMING-MF-MANIFESTO">[PROGRAMMING-MF-MANIFESTO]</a> which describes a natural approach to software engineering with a strong focus on the act of programming. The PM 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. </p>
<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>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>
<hrclass="noprint"/>
<h1class="np"id="rfc.toc"><ahref="#rfc.toc">Table of Contents</a></h1>
<pid="rfc.section.1.p.1">In 2011, Zed A. Shaw published a blog post which describes: </p>
<pid="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>
<pid="rfc.section.1.p.3">The programming methodology was published as a manifesto later <ahref="#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 <ahref="#THE-TAO-OF-PROGRAMMING">[THE-TAO-OF-PROGRAMMING]</a> describes similar methodologies which strongly focus on coding, scripting and programming. </p>
<h1id="rfc.section.1.1"><ahref="#rfc.section.1.1">1.1.</a><ahref="#management-and-pmf-methodology"id="management-and-pmf-methodology">Management and PMF methodology</a></h1>
<pid="rfc.section.1.1.p.1">A simple management process is a required 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. </p>
<h1id="rfc.section.1.2"><ahref="#rfc.section.1.2">1.2.</a><ahref="#conventions-and-terminology"id="conventions-and-terminology">Conventions and Terminology</a></h1>
<pid="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 <ahref="#RFC2119">[RFC2119]</a>. </p>
<pid="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>
<tdclass="top"><a>Bradner, S.</a>, "<ahref="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>
