Programming-in-the-Large Versus Programming-in-the-Small
IEEE Transactions on Software Engineering
Structured Analysis for Requirements Definition
IEEE Transactions on Software Engineering
A Requirements Engineering Methodology for Real-Time Processing Requirements
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
Over the past decade numerous methodologies were introduced to guide and ease the project manager's burden over the entire life cycle of system/software development. Additionally, various software tools were developed to support specific methodologies. In fact, the collection of methodologies and support tools grew so rapidly that a project manager was left with a confusing array of choices. Some method was needed for comparing project requirements against the methodology capabilities in order to find the best fit. The Air Force awarded a contract to Boeing Aerospace Company to address the problem. The stated objective of the Specification Technology Guidelines contract was to organize existing information on requirements and design technologies into a Guidebook that could be used by USAF technical managers in selecting appropriate methodologies for future projects. We will describe an approach that integrates such concepts as project significance level, software categorization, and life-cycle requirements, and implements them by means of a table-driven procedure that could easily be computerized. Using this approach, the technical manager measures project significance and requirements against the functions available in various methodologies; selects candidate methodologies best fitting a project; and, finally, assigns a score to the candidates in order to make a final methodology selection.