mirror of
https://github.com/adulau/pmf.git
synced 2024-12-22 00:35:59 +00:00
Updated version
This commit is contained in:
parent
c93eea4be5
commit
ac45447ddf
GPG key ID:
09E2CD4944E6CBCD
3 changed files with 42 additions and 42 deletions
20
raw.md.html
20
raw.md.html
|
|
@ -428,7 +428,7 @@
|
|||
<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>
|
||||
<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 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>
|
||||
<h1 id="rfc.status">
|
||||
<a href="#rfc.status">Status of This Memo</a>
|
||||
</h1>
|
||||
|
|
@ -464,25 +464,25 @@
|
|||
<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 id="rfc.section.1.p.4">The overall concept of PMF methodology follows the following process: </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>
|
||||
<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>
|
||||
|
||||
<p> </p>
|
||||
<p id="rfc.section.1.p.6">This process is run in a while loop until the software is delivered. </p>
|
||||
<p id="rfc.section.1.p.6">Repeat the above process 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 id="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>
|
||||
<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>
|
||||
<li>Collect requirements of the users/customers.</li>
|
||||
<li>Provide programmers with the desired requirements.</li>
|
||||
<li>Review whether the software to be delivered matches the requirements.</li>
|
||||
</ul>
|
||||
|
||||
<p> </p>
|
||||
|
|
|
|||
38
raw.md.txt
38
raw.md.txt
|
|
@ -16,11 +16,11 @@ 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.
|
||||
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.
|
||||
|
||||
Status of This Memo
|
||||
|
||||
|
|
@ -92,17 +92,17 @@ Table of Contents
|
|||
[THE-TAO-OF-PROGRAMMING] describes similar methodologies which
|
||||
strongly focus on coding, scripting and programming.
|
||||
|
||||
The overall concept of PMF methodology follows this iteration:
|
||||
The overall concept of PMF methodology follows the following process:
|
||||
|
||||
o Write a list of things to be done and use an iterative programming
|
||||
process.
|
||||
o Compose a list of features to be implemented and use an iterative
|
||||
programming process.
|
||||
|
||||
o Do some of the things with additional programming.
|
||||
o Enhance said features using trial and error programming.
|
||||
|
||||
o Build testing and tests using programming.
|
||||
|
||||
This process is run in a while loop until the software is delivered.
|
||||
o Orchestrate your testing and integration processes using pragmatic
|
||||
programming.
|
||||
|
||||
Repeat the above process until the software is delivered.
|
||||
|
||||
|
||||
|
||||
|
|
@ -116,16 +116,16 @@ 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.
|
||||
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.
|
||||
|
||||
o Review requirements of the users/customers by asking them.
|
||||
o Collect requirements of the users/customers.
|
||||
|
||||
o Give the list of things to be done to the programmers.
|
||||
o Provide programmers with the desired requirements.
|
||||
|
||||
o Review the delivered software to see if it matches the
|
||||
o Review whether the software to be delivered matches the
|
||||
requirements.
|
||||
|
||||
1.2. Conventions and Terminology
|
||||
|
|
|
|||
26
raw.md.xml
26
raw.md.xml
|
|
@ -50,8 +50,8 @@
|
|||
|
||||
<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.
|
||||
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.
|
||||
</t>
|
||||
</abstract>
|
||||
|
||||
|
|
@ -67,28 +67,28 @@ into official engineering or project documents to describe one of the most used
|
|||
</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>The overall concept of PMF methodology follows the following process:
|
||||
</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>
|
||||
<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>This process is run in a while loop until the software is delivered.
|
||||
<t>Repeat the above process 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>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.
|
||||
</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>
|
||||
<t>Collect requirements of the users/customers.</t>
|
||||
<t>Provide programmers with the desired requirements.</t>
|
||||
<t>Review whether the software to be delivered matches the requirements.</t>
|
||||
</list>
|
||||
</t>
|
||||
</section>
|
||||
|
|
|
|||
Loading…
Reference in a new issue