Bibliographic record
Abstract
Abstract Downsizing, and consolidation of previously independent companies, has produced a clash of cultures in many companies. The problem is exacerbated by “home‐grown” product development cultures that have been around for decades and often fail to adequately integrate new disciplines such as software engineering and systems engineering. Over the years, the pace and complexity of technological development has increased. Mergers have brought together more companies with differing processes. New standards like the Software‐Capability Maturity Model® (SW‐CMM®) and Capability Maturity Model Integration® (CMMI®) have been introduced. All these changes have increased the need for developing and instituting new, integrated, and more repeatable engineering processes. Methods of introducing, and gaining acceptance of, these new processes are becoming very important to the continued competitiveness of many companies. At issue is how best to get a diverse workforce to work together to achieve extraordinary goals. Lockheed Martin Missiles and Fire Control (LMMFC), faced with integrating two former competitors, embarked in 1999 on a course to develop a common product development culture. A primary forcing function was the use of Carnegie Mellon University's Capability Maturity Model‐Integration (CMMI®) standard. The resulting new processes are enabling employees to achieve higher goals – by increasing productivity, maximizing use of information, using proven simplified processes, increasing re‐use, and decreasing re‐work. Results to date indicate a “One Company, One Team” mentality is rapidly becoming the norm at LMMFC.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".