Information Technology Reference
In-Depth Information
algorithm. Some extra efforts were required during the compilation phase because
various parameters were required to parse while compiling a single module.
The implementation and integration with the main code was done, and a vehicle
test was conducted to verify the functionality of the vehicle, because it involved some
mechanical nuances to check and finalize the calibration values.
Time Recording Log, Defect Recording Log, and PSP Project Plan Summary were
used to determine Plan, Actual, To Date, and To Date% PSP process parameters during
this program. In this case, PSP processes for two persons were used and the combined
results related to time, defects injected, and defects removed are logged in Table 10.2,
which shows the Simple and Small-Size PSP Project Plan Summary. During the bench
test, software defects were injected to observe the proper functionality and response
to errors and its diagnostics. No operating issue with software was found during this
time. However, during the integration with the rest of the software modules at the
vehicle level, a mismatch in software variable name (typo) defect was found that
was caught as a result of an improper system response. The templates for Tables
10.2-10.7 were provided in a package downloaded from the SEI Web site “PSP-for-
Engineers-Public-Student-V4.1.zip” after the necessary registering procedure. For
Table 10.2 and Table 10.3 calculations, please refer to Appendix 10.A1, 10.A2, and
10.A3.
Although this example project is discussed here first, it was actually conducted
after the 'M&M' project. Also it was decided to apply FTA to understand fault modes
while designing the S&S project.
In conclusion, PSP processes provided a methodical and yet very lean approach to
practice software processes while working on the 'S&S' project. The deviation in the
achievement could be a result of a few constraints like newness of the process, the size
of software project, number of people involved, and finally taking into consideration
the individual software development person's personal software quality standard. The
final summary results for the S&S project are shown in Table 10.3.
10.4.2
Moderate and Medium-Size Project
In this case, an M&M software project in the range of 10 KLOCs was chosen to
understand the effectiveness of PSP and TSP while using the Spiral Model as shown
in Figure 10.6 (Shaout and Chhaya, 2008).
10.4.2.1 Deployment Example: Electrical Power Steering Subsystem
(Chhaya, 2008).
DFSS Identify Phase—
Discussions were held with the vehicle
system team and steering system team to identify the high-level requirements. Next,
the system requirements were interfaced to the vehicle, design guidelines, vehicle
standards (SAE and ISO), safety standards application implementation, and inte-
gration environment, and team interfaces were discussed and agreed to during this
phase. After jotting down the rough requirements, each of the requirements was
discussed thoroughly with internal and external interfaces. The following were the
requirements:
Search WWH ::
Custom Search