| Risks |
| The project team does not have access to a process management tool. |
| The project team has little access to design and analysis tools. |
| Popular design and analysis tools are not appropriate |
| for development of the PPF. |
| Compatibility between the KCC and egcs compilers may be problematic. |
| Cross platform compatibility may prove problematic. |
| The project members have no experience debugging threads |
| on the sp2 or Digital Unix platform. |
| Thread debuggers for all platforms may not be available. |
| Mitigation |
| Process management can be accomplished by use of programs |
| such as Microsoft Project run on a separate machine than that used |
| for the project. |
| The PPF project does not warrant any special tools for design |
| or development, design should be rather straightforward as the library |
| has relatively few use cases. |
| Again the nature of the PPF project does not require |
| the use of extravagant design and development tools. |
| All code for the PPF must follow the C++ standard. |
| Continuous builds on all target platforms will ensure |
| compatibility at every step of the development process. |
| Project members must research debugging methods for threads |
| on the sp2 and Digital Unix platform. |
| In the case that an adequate debugger is not found, the |
| threads can be debugged separately from the running code using a traditional |
| debugger. |