Multi‐project software engineering analysis using systems thinking
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Abstract Software organizations often have multiple projects developed concurrently, the efficient and effective management of human resources in such a situation is essential if an organization is to prosper and flourish. The article argues that to analyze it systematically, we need to explore systems thinking and dynamics. The article then develops a number of systems dynamics models that model human resources and their associated productivity in such a multi‐project environment. However, systems thinking alone lacks the capability to construct a multi‐project scheduling network. Thus, this research also investigates the integration of systems thinking with a multi‐project network constructing method, called Critical Chain Project Management to provide a flexible scheduling mechanism. Furthermore, in order to portray unexpected situations, scenario planning is incorporated into the system to allow project managers to explore these situations and their impact on the production processes. This unique architecture allows the project manager to identify the restraining factors in various possible scenarios, to provide feasible managerial solutions and assist with optimal planning in this complex environment. Copyright © 2004 John Wiley & Sons, Ltd.
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.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.004 |
| 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 it