Description: Recommendations concerning Capability Maturity Model Integration; effective COTS integration requires a fundamental paradigm shift; a framework for the reliable evolution of software systems; a particular application of the IIDA process model described in Part I; how to improve the quality and efficiency of team-based projects; a method to use CMM practices on small projects; liability issues surrounding the software certification laboratories phenomenon; how to achieve a statistically correct sample for testing and evaluation; three lines of defense managers can use to guard against bad engineering.
Description:Description: The Air Force Y2K Program Management office is guiding the Air Force to year 2000 compliance; organizations may not properly grasp the magnitude of year 2000 reengineering; why year 2000 project changes should be concurrent with day-to-day project revisions; benefits of two time-shifting strategies: program encapsulation and data encapsulation; lessons learned from the DLA's year 2000 project; a compliance checklist to assess affected programs; ...
Description: Emergency help for projects at the ad/hoc level; a move beyond the clerical to the technical; new methods to manage software after deployment; the first of a three-part series explains the rationale behind the CMM, PSP, and how to employ PATs to your organization's advantage; the CMM was not intended to be a rating system or a box to check but an aid to improvement; a few simple metrics to determine overall product integrity.
Description: Those who survive their first ""dogfight"" with acquisition increase their oDs of continued success; how to make sure the learning pays off; bookmark automation using ""logobots"" increases efficiency in Internet learning; solid data on the effectiveness of the Personal Software Process; twenty-five tips on how to improve your Inspection process; a model to facilitate and control COTS evaluation, selection, and integration early in the development process; h...
Description: Recommendations concerning Capability Maturity Model Integration; effective COTS integration requires a fundamental paradigm shift; a framework for the reliable evolution of software systems; a particular application of the IIDA process model described in Part I; how to improve the quality and efficiency of team-based projects; a method to use CMM practices on small projects; liability issues surrounding the software certification laboratories phenomenon; ho...
Description: An Executive Order establishing a year 2000 conversion policy; support for the forthcoming CMMI; courses at the National Defense University arm students with software acquisition knowledge; how to get the most out of Software Capability Evaluations; recommended improvements to the SA-CMM that emphasize reuse; why data analysis saves more money and time than it takes; find a safe harbor for the year 2000 storm; big lessons learned from a small project; who kn...
Description: A low-cost, browser-based method to share information between an Air Force unit and its contractors; the next generation of markup languages expands the Web's functionality; the basics of Intranet purpose and structure; limitations in interconnection network resources can more negatively affect software than processor or memory constraints; an SOM can help acquisition managers and organizations ensure they acquire software that meets their needs; how to use ...
Description: Ten steps to better program management; people-oriented techniques to complement formal management procedures; a post-mortem analysis of ""deceased"" projects by experts in the field; why proper use of tool suites can make or break a project; this early-warning system can give management time to make course corrections before it is too late; steps to evaluate and coordinate your organization's year 2000 resolution efforts; workload, complexity, and cost diff...
Description: Why the year 2000 problem could seriously threaten our nation's security--but only if we let it; how to officially certify that your year 2000 fixes have been successful; real-world lessons on how metrics can help improve processes, communication, and teamwork; metrics to determine when software products should move to their next major phase; increase savings and quality by aDing statistical controls to automated test programs; the coupling dependency metric...
Description: A method to choose the most appropriate software model for your organization; a plan of attack when your organization encounters symptoms of these process improvement killers; a candid look at common misconceptions concerning process improvement; how software process improvement coaches differ from sponsors, champions, and change agents; a fresh look at the often misunderstood practice of process improvement; meaningful metrics collection with specific busin...
Description: Directions for the DoD in systems acquisition policy and practice; how to select a standard that best suits your project's needs; an overview of three process models; why human factors are vital to system design; a way to map SE-CMM process areas to the software CMM; an introduction to Odel, an easy-to-learn, ""executable"" system description language; this is a practitioner's discussion of the evolution of the current practice and application of RTCA/DO-178...
Description: Parametric models allow the inclusion of many variables that affect quality; how to understand the economic trade-offs involved in producing high-quality; three approaches to certifying the quality of software; the FAA-iCMM's architecture, domain, capability levels, maturity levels, and its appraisal method; current software development processes do not fully suit VLs and VPEs; an overview of the Testing Maturity Model Assessment Model.
Description: Which RE technologies are the most difficult to adopt and which approaches have worked; a case study comprising data from 40 software releases; an underrated method to improve requirements analysis; project data from NASA GoDard Space Flight Center demonstrates requirements definition, verification, and management; a method to analyze the impact new ideas will have on requirements and costs; findings from a National Research Council committee's review of Ada...
Description: A policy letter that details the reporting of mission-critical Y2K issues to the DoD Y2K database; the only way to improve software performance is to improve development processes; a guide to assess your critical network components for Y2K compliance; meaningful methods to help assess the true scope of your Y2K efforts; how to aDress 15 important testing concerns; ""Bullpen"" helps maintain realistic simulation behavior if one simulator malfunctions; technic...
Description: From the Ogden Air Logistics Center, the first results of using the Team Software Process on a software-intensive system project; a guide to making the transition from the older version to the newer; how to avoid three common documentation problems; how a practice common in manufacturing will enhance software development; An introduction to the concepts related to function points; not all the fallout from the year 2000 debacle will be negative.
Description: Basic principles that govern the formation of control boards; how to ""reverse configure"" for projects built without CM; what the future holds for configuration management tools and processes; the Cost/Schedule Control Systems Criteria technique can help projects achieve expected completion date and cost; how to understand logical events such as Y2K failures and create the most appropriate contingency plans.
Description: How to implement a defect-tracking process in your organization; quality software products begin with the requirements phase; lessons learned from one sponsor's experiences; the major principles and purposes of these important management tools; a method to bring insight into complex process behavior.
Description: An announcement of the Ogden Air Logistics Center, Software Engineering Division's Level 5 achievement; a quick refresher on key process areas and maturity levels; the answer to the question, ""How long does it take to reach Level 5?""; the return on both cost savings and employee satisfaction makes the initial investment well worth it; the QuEST for quality requires a dedicated, independent team; it is more important to improve software processes than to me...
Description: Poorly contrived measurements can make for poor decisions; a tool with the flexibility to support an effective, tailored measurement process; how people issues can cripple a measurement program or lead to its resounding success; implementing the necessary software process improvements required to achieve Level 2; an initial characterization of Department of Defense mission-critical software maintenance; putting out critical fires before they start; enhance d...
Description: An interview with the Deputy Under Secretary of Defense (Science and Technology); a look back at the 11th annual Department of Defense conference in Salt Lake City; once upon a time, a young man journeyed through project management; an overview of the Project Management Body of Knowledge model; developing an automated risk management tool; overcoming the barriers that impede standard data element use; using defined processes to produce quality software.
Description: The Deputy Under Secretary of Defense gives her thoughts on software acquisition; two methods used during source selection to evaluate a contractor's software development capability; reviewing project plans, requirements, and test plans for software acquisition success; results of two Department of Defense product line workshops; lowering program risks and producing a quality product with the Software Insight Tool.