Simple Solutions to Complex Problems
  • Simple Solutions
    • Documents Live Once
    • Good JIgs
    • Polya and Friends
  • Long Term Relations
    • Customers & Projects >
      • APU OverView >
        • APU Early Years
        • APU Middle Years
        • APU Late Years
      • AQMD >
        • DataGeneral v Hewlett Packard
      • Big Lots
      • The Federate Group >
        • Stabilizing the System
        • The Cash Register System
        • Later Projects
      • Munson Management Systems
      • National Electronics
      • Richey Electronics
      • Sierra Pacific Investments
      • Other Customers
  • Diagonal Method
    • D2-M2 >
      • Diagonal differs from Agile
      • Maintenance Projects
      • Manufacturing Projects
      • Research Projects
    • Data Structures >
      • Data Levels
      • Data Logging
      • Data Merging
      • Data Input Buffers
      • Data Sorting
      • Data Deltas
    • Readable Source Code >
      • Readable Code Modifications
      • Readable Paradigms
      • Readable Style
    • Critical Path Method >
      • CPM Data Tasks
      • CPM Menu and Security
      • CPM External Tasks
      • CPM: Early Calculations
      • CMP Stem to Stern >
        • Work Units
    • Semi-Interpretive Mindset >
      • Simple Semi-Interpretive Case Study 1
      • Semi-Interpretive Case Study 1 -- Semesters 2 and 3
      • More Thorough and Efficient
      • Software Research Northwest
    • Semi-Interpretive Methods
    • Concepts and Practices >
      • Data Changes
      • Data Stacks
      • Data Tokens and Loose Linking
    • Diagrams & Examples >
      • Venn Diagrams
      • Music Score as a Diagram
      • Cause & Effect Diagrams
    • Dictionary and Lexicon
  • Programmers
    • Tools and Languages >
      • python considerations
      • program names, like sa5comm
    • Perspectives of a Manager
    • ToDo
    • HTML testing
    • Private Thoughts
    • Leads
  • Contact Pilgrim
    • Land of the Free
    • Pilgrim Legal Status
    • Index to Pages
  • New Page
  • Stonehenge Simply Done

Critical Path Method (CPM):  Very Important Technique

For small projects, like a new screen, the manager probably has memorized steps that lead to successful implementations.  A screen should only take a few days, so there is not much to optimize.  However, when there are many screens, or many steps, in a project, the critical path method becomes very useful.  The building of the list of tasks and the building of the charts force the manager towards realistic estimates and solutions. 
The manager repeats the following steps until a complete diagram takes shape

  1. Makes a list all of the steps that seem required. The list becomes the basis for calculations.
  2. Sketch a chart that shows the sequence and connection of the steps; the chart becomes the visual representation
  3. Untangle the lines on the chart, which often makes more boxes
  4. Expand boxes like DB into its components
  5. Programs, when developed in stages or by functions, spawn multiple boxes

When two tasks depend on two or more of the same parent tasks, the chart becomes messy.  This chart has only two programs; a dozen would be very messy. To unsnarl some of the mess, connectors come into the picture, and the number of pages or frames increases.

Sometimes, the definition of the parent is flawed. 
The chart on the right decomposes several ways.  The DB box represents a data base; likely there are multiple tables. 

Likewise the data might go into the DB thru a load process or into the programs via a keyboard. 

In some cases, shorthand simplifies the chart.  If the Menu mechanism already exists, the Menu becomes a candidate for shorthand.
 
Picture
Picture
The DB box probably has many embedded boxes or tasks.  Extracting the boxes gives more detail and hopefully better estimates.  The DB Creation and the DB admin probably becomes a box at the beginning of the project. 

The PRGM table probably needs a record for each program, which might be a short task.

Later, a general DB box and a few data tables become prerequisites to each program.

The Menu Box usually has a simpler decomposition.
See CPM2
PCC 1982 - 2014