The Latest

Applying the Unified Modeling Language (UML) is now easier, thanks to GD Pro 3.1. The visual modeling tool offered by Advanced Software Technologies supports software design, development, redesign, and maintenance for small and large teams alike.

This paper presents experiences in testing critical software that supports flight systems developed by Lockheed Martin Astronautics in Denver, Colorado. This approach has not been proven in an academic sense, but has been demonstrated over the years to result in software that successfully performs missions. It is based on teams comprised of the correct skill balance in software and systems engineering, as well as using a defined process.

This paper examines the successful application of tolerances on process metrics used in management activities of an ongoing test project. The result was a more stable system during the "crunch" at the end of the test cycle.

This article is a basic introduction to the concepts of Software Risk Management. It includes discussions of: Identifying the Risks, Analyzing the Risks, Building the Risk Management Plan, Tracking and Controlling to the Plan and Learning from Experiences.

This paper discusses the fundamental approaches to establishing a test strategy and the varying levels of the test plan.

These are generic entry and exit criteria used on Inspections at ISS based on the work done by Gilb & Graham. Some of them were waived initially in order to get the process accepted, although we accept that this is far from ideal.

Launching a new product line is a difficult and time-consuming task under the best circumstances. While working on a new project can be refreshing, difficulties arise in allocating sufficient resources to create and tune the new product development processes. Modifying the processes or Best-Known Methods (BKMs) of the past is one technique employed to allocate time and resources more effectively. Transferring BKMs from an earlier product line into the current one can bring about its own set of challenges which include: defining the BKMs, producing repeatable BKMs to be deployed in varied environments, implementing techniques to log the BKMs, and placing the BKMs in a central location. This paper discusses one approach to transfer software BKMs between generational product lines. The topics addressed include: defining the project's mission and goals; creating definitions and processes to support the BKM transference; encountering and solving issues while implementing the processes.