.png){kind=icon}
Return
Anchoring the software process
.png){kind=icon}
PRE
AI
DOI：10.1109/52.526834.png)
.png){kind=icon}
Original request for help.png){kind=icon}
Share.png){kind=icon}
Save
Abstract
En 中文
For a few golden moments in the mid-'70s, it appeared that the software field had found ii sequence of milestones around which people could plan, organize, monitor, and control their projects. These were the milestones in the waterfall model. They typically included the completion of system requirements, software requirements, preliminary design, detailed design, code, unit test, software acceptance test, and system acceptance test. Unfortunately, just as the waterfall model was becoming fully elaborated, people were finding that its milestones did not fit an increasing number of project situations. The risk-driven content of the three milestones proposed in this article let you tailor them to specific software situations, and at the same time they remain general enough to apply to most software projects.
Journal
IF:
3
Papers:
3.2K
Citations:
3.6K
Organization
No organization information available
Cited Papers
ShareSaveShareSaveAssessment of eight nucleic acid amplification technologies for potential use to detect infectious agents in low-resource settings.png)
PLOS ONE
OAAI
PLOS ONEIF0
OAAIShareSaveShareSaveShareSaveMicroorganisms of the upper atmosphere I. Instrumentation for isokinetic air sampling at altitude
OAAI
IF0
OAAIShareSaveShareSave no more
no more