Home Search Contact Us SEER National Cancer Institute SEER
skip top navigation
National Cancer Institute   U.S. National Institutes of Healthwww.cancer.gov
National Cancer Institute - SEER Data Management System SEER DMS
Project Definition:
  Home
  Stakeholders
  Intentions
  Values:
    Holistic List
    Conflicting Values
  Focus Statement:
    Breadth
    Perspectives
    Depth
    Universality
    Scope of Integration
  Context:
    Latitudes
    Uncertainties
    Understandings
  Project Approach
  Project Organization
  History

Ranking of Likely Conflicting Values

Extracting/synthesizing values from the Holistic List of values and considering other possible values, the project has attempted to specify key values in relative order of desirability. This Ranking of Likely Conflicting Values will help when trade-offs and judgments have to be made.


No. Name Explanation
1 Cost of Production
  • Production = Operations, data entry, support after implementation, …
  • Low Cost of Production implies that reducing the ongoing cost is the driving concern and that other variables might be adjusted to reduce this cost.
  • If there is a high value on lowering the cost of production, typically the cost of development will rise.
2 Time/Speed
  • Meets product delivery deadline.
  • The rate at which the solution is delivered without regard to the quality of the solution.
  • High speed implies that other variables will be sacrificed in order to achieve quick deliverables.
3 Quality
  • Consistency without error.
  • The raw goodness of the final results in terms of usability, reliability, fitness for a purpose, etc. How suitable is the end result for a purpose.
  • High quality implies that there will be added quality assurance activities, and that fitness for an intended purpose will not be abridged to make deadlines and cost targets.
4 Functionality
  • Solution performs according to full range of specifications.
  • High functionality means that the breadth of coverage of the solution (in terms of goals, functionality, or features) will not be compromised to make deadlines or cost targets.
  • Note: We assumed that if we compromised functionality we would still provide a meaningful solution.
  • Given that we will seek an incremental development strategy, parts of the functionality would be delivered at different times. This timing does NOT imply compromising or cutting the functionality.
5 Reusability
  • The extent to which the effort will utilize AND create reusable components (analysis, design or actual product components).
  • High reusability implies that there are formal activities to locate and attempt to use existing reusable components and that there are formal activities to identify, develop and certify new reusable components.
6 Cost of Development
  • This is an inverse relationship with the cost of production. Low cost of development implies that reducing cost and producing the results at a low cost is the driving concern and that the other variables might be adjusted to reduce the cost.
  • For example, it is cheaper to "hard code". However, the resulting cost to make changes or support flexibility will raise the Cost of Production.
7 Fit for the Registries
  • The degree to which the solution meets the Registries' needs. For example:
    • The solution has a "core", but with flexibility for extensions to meet Registry specific needs. Thus, all Registries could be served fully.
    • The solution is a traditional application that meets 80% of their needs without any real means to extend the solution per Registry.
SRP logo Surveillance Research Program
DCCPS
National Cancer Institute
DCCPS logo Division of Cancer Control &
Population Sciences

National Cancer Institute
Comments or Questions
Accessibility: Feedback Form
Privacy Policy & Disclaimers
National Cancer Institute    Department of Health and Human Services     National Institutes of Health    USA.gov