Grace Hopper

Record year1957

summaryHe led or participated in the Univac automatic-programming team in delivering FLOW-MATIC, aimed at English-like business expression and forming the family of business-oriented programming languages after A-0.

M rationaleM5.2 is above A-0's M4.7 because FLOW-MATIC advanced from an automatic-programming prototype to a business-oriented problem language and team delivery; it belongs to the same reusable-method tier as Watt's condensing method M5.2, but does not include COBOL or later commercial computing.

attribution rationaleHopper for direction and team leadership 0.35; UNIVAC language and compiler implementation team 0.35; Sperry/Remington Rand institutions and product delivery 0.10; A-0, business computing, and language prior work 0.10; unknown 0.10.

overlap boundaryCredit only the FLOW-MATIC language, publicity materials, and locatable compiler-project artifacts directed at English-like business expression from 1957–1959. A-0 is a consumed precursor; COBOL is credited only for its new cross-institutional standardization. Exclude all commercial software, cross-machine computing, and the scale of COBOL operation.

Evidence gapsThe language manual has not been read in full. Specific syntax and compiler implementers have not been broken down.

Record year1958

summaryShe brought FLOW-MATIC experience into CODASYL and Univac's implementation of COBOL specifications, cross-institutional coordination, and promotion. The language was jointly formulated by a committee; Hopper's roles included technical adviser and specification implementation, while early implementations were completed by Remington Rand Univac and RCA teams.

M rationaleM5.8 is in the same tier as Watt's mature system: COBOL constituted an actual language-standard delivery with cross-institutional specifications, cross-vendor implementation, and continuing promotion. Its M is not Hopper's personal share; personal a is only 0.15, preventing reputation from swallowing the committee and implementation teams.

attribution rationaleHopper for Univac technical advice, specification implementation, and promotion 0.15; Mary Hawes, Cunningham, Jack Jones, and Al Ash for organizational leadership and requirements 0.25; Bemer and Baird for technical input 0.15; CODASYL committee 0.20; Remington Rand and RCA implementation 0.15; FLOW-MATIC precursor 0.05; unknown 0.05.

overlap boundaryCredit only the joint formulation of COBOL in CODASYL, specification implementation, cross-machine testing, early Remington Rand/RCA implementation, and Hopper's promotion from 1958 through the 1960s. FLOW-MATIC serves only as a precursor input; exclude the entire operational history of COBOL, all commercial computing, and every version of the standard.

Evidence gapsCODASYL meeting records and the 1960 specification text have not been read item by item. Named leaders' and internal committee shares are coarse-grained estimates.

Record year1951

summaryIn the UNIVAC I context, she designed the A-0 proto-compiler, organizing reusable program fragments and automatic generation of instructions as an independent tool; subsequent development was jointly completed by the automatic-programming team.

M rationaleM4.7 is close to ACE M5 but slightly lower: A-0 opened the direction of automatic-programming tools and has a prototype narrative, but lacks original manuals, running artifacts, and evidence of adoption scope. It is above the general-tool M3 because it changed how programs were constructed.

attribution rationaleHopper for tool design and the budget demonstration model 0.50; UNIVAC automatic-programming team 0.25; prior work in subroutines, assembly, and programming 0.15; institutional resources 0.05; unknown 0.05.

overlap boundaryCredit only the organization of reusable program fragments and instructions, from 1951–1952 in the UNIVAC I context, as an A-0 automatic-generation tool and an early demonstrable model. Do not claim an undisputed world's first compiler, or credit all subsequent compilers, assemblers, high-level languages, or FLOW-MATIC.

Evidence gapsOriginal A-0 manuals and running artifacts are lacking. CHM uses the terms proto-compiler/one of the first, so priority remains open.

Record year1960

summaryShe participated in computer-language standardization organizations and conducted sustained dissemination around standard languages, program portability, and training; validation services belonged to an institutional environment jointly constituted by the Navy, GSA, and committees.

M rationaleM4.2 reflects sustained institutional service over many years through committees, validation, and teaching, above the general-tool M3; because complete course sessions, validation projects, and adoption effects are insufficiently documented, it is below A-0 and the languages themselves.

attribution rationaleHopper's committee and promotional service 0.35; Norm Ream's standardization input 0.10; ANSI/CODASYL team 0.20; Navy/GSA validation institutions 0.15; teaching and dissemination support 0.10; prior work in standardization 0.05; unknown 0.05.

overlap boundaryCredit only Hopper's actual service in ANSI/CODASYL language standardization, the Navy/GSA validation system, and public teaching and dissemination from the 1960s to 1986. COBOL's initial formulation is credited by the preceding item; exclude every version of standards, military software, students' future outcomes, and all computing education.

Evidence gapsThe Navy biographical page in this round consists only of a search summary, and its full text has not been verified. Validation projects, courses, and audience scale are lacking.

Record year1944

summaryThrough Mark I operations and programming practice at the Harvard Computation Laboratory, she participated in producing an operating manual and joint technical documentation; the 1946 operating manual lists Hopper as an author and identifies her as managing editor.

M rationaleM3.5 is above general documentation or the general tool M3 because the manual delivered complex early-computer operational knowledge to subsequent operators; the collection proves only managing editorship and joint attribution, not chapter-by-chapter writing or adoption scale, so it is far below ACE architecture M5.

attribution rationaleHopper for managing editorship and program-documentation organization 0.35; Aiken's joint technical attribution 0.20; laboratory manual and programming team 0.25; Harvard, IBM, and Navy institutions and equipment conditions 0.10; unknown 0.10.

overlap boundaryCredit only the Harvard Computation Laboratory's organization of Mark I operation, programming, and technical knowledge into manuals for which Hopper was managing editor and technical documents jointly attributed with Aiken from 1944–1947. Exclude invention of Mark I hardware, the entire ballistics project, and military computing outcomes, and do not add M by chapter count.

Evidence gapsHopper's writing share has not been determined chapter by chapter. Evidence is lacking for the manual's user scale and specific operational effects.