| Risks |
| Addition of extraneous code not directly pertinent to a project. |
| Limited number of users may limit PPF's benefits. |
| The library may unnecessarily complicate the project using it. |
| Attempts to save a problems progress in the advent of failure may |
| use large amounts of system resources including drive space. |
| The PPF may add a disproportionate amount of overhead to small |
| problems. |
| MITIGATION |
| Development efforts should focus on limiting the code for |
| PPF to only handle particle passing and mesh decomposition |
| which is common to all projects. |
| During requirements capture, PPF's usefulness should be |
| evaluated in light of the number of foreseeable clients. |
| Efforts should be made during development to make the library |
| linkage and interface as simple as possible. |
| PPF should only do large data dumps to hard disk if explicitly |
| sanctioned by the user. |
| It should be agreed by developers to use PPF only if the problems |
| they run are large enough to warrant it. |