| No. |
Project Approaches |
| 1 |
We will be using a registry-operations-driven approach |
| 2 |
Registry directors and IT personnel will determine the system requirements of this effort. NCI will facilitate the process. |
| 3 |
Joint Development Approach (JDA) will be used to allow authorized SEER Registry participants to specify the operational requirements of the system. |
| 4 |
Visual modeling tools will be used to capture registry operation requirements - for example, Unified Modeling Language (UML) and Rational Rose, that are understandable by non-technical people |
| 5 |
This project is part of a multi-phase effort and will be developed incrementally. |
| 6 |
The project feasibility will be ascertained before moving into (development?). Feasibility will be determined by committee of the whole. To be determined no later than February 2001. |
| 7 |
Design methods and considerations will include near-cutting edge technology, portability, multiple platforms, longevity, and rapid application development. |
| 8 |
Continuous verification and feedback to ensure conformance to real requirements. For example: model testing, design testing, test sites. At each stage determine who should be involved and how. For example: involve authorized SEER Registry participants intensely during analysis to specify the requirements and then periodically, in a review role, during design to ensure that the requirements are being met. |
| 9 |
To achieve consensus on common functionality and to allow registries to implement their unique functional needs. |
| 10 |
Recognizing the need for broad contribution as well as the limited time available to contribute we will attempt the following:
- to select subgroups to develop straw models. They might meet as a whole or communicate remotely
- to be innovative in ways to collect expertise from people unable to participate in a subgroup
- to assemble as large a group as possible for final verifications
|