mirror of
https://github.com/adulau/pmf.git
synced 2024-09-18 04:16:21 +00:00
140 lines
4.8 KiB
Markdown
140 lines
4.8 KiB
Markdown
%%%
|
|
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
|
|
|
|
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.
|
|
|
|
{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 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:
|
|
|
|
~~~~~ ascii-art
|
|
+----------+
|
|
| |
|
|
| 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.
|
|
|
|
## 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.
|
|
|
|
## 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>
|
|
|
|
{backmatter}
|