Charles V. Weber

Learn More
This paper provides an overview of the latest version of the Capability Maturity Model for Software, CMM v1.1. Based on over six years of experience with software process improvement and the contributions of hundreds of reviewers, CMM v1.1 describes the software engineering and management practices that characterize organizations as they mature their(More)
The capability maturity model (CMM), developed to present sets of recommended practices in a number of key process areas that have been shown to enhance software-development and maintenance capability, is discussed. The CMM was designed to help developers select process-improvement strategies by determining their current process maturity and identifying the(More)
The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and " No Warranty " statements are included(More)
PURPOSE To compare the anatomic and visual results and complications of 25-gauge transconjunctival sutureless vitrectomy versus conventional 20-gauge vitrectomy for the management of primary rhegmatogenous retinal detachment. METHODS A retrospective comparative analysis of 125 consecutive eyes from 125 patients with a minimum of 3 months follow-up was(More)
Knowledge has received increased attention as the basis to explain differences in firm performance. Yet, the knowledge-based view of the firm in strategic management is still a contested and unmapped terrain with no unified clear-cut theories. This paper critiques existing contributions to knowledge-based views and highlights tensions in the field. We(More)
This chapter provides an overview of the Capability Maturity Model for Software (CMM VI.1). CMM Vl. l describes the software engineering and management practices that characterize organizations as their processes for developing and maintaining software mature. This chapter stresses the need for a process maturity framework to prioritize improvement actions;(More)
The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and " No Warranty " statements are included(More)