\begin{figure*}
{\scriptsize
\small
\begin{tabular}{|l|l|p{5.35in}|}\hline

base?&name&notes\\\hline\hline
y&devCMM &This is an overall assessment of the effectiveness of the development process related to development of requirements.  The assessment should include methods for requirements elicitation, coordination, documentation, and validation. It should correlate fairly well with CMM level, but includes an assessment of what is really happening in addition to what is documented.\\
\hline
y&novel&Relative novelty (to the developer or user) of the application/mission or the solution approach. For example, entry GN\&C for a new vehicle where all algorithms are adapted from Shuttle would be low novelty (10) (provided the new mission is very similar to the Shuttle mission), completely new algorithms or new application would be high novelty (1).\\
\hline
y&reqCplx &Qualitative estimate of overall system/problem complexity.  Related to technical difficulty, required interfaces (developer and system), and unity of users.  Not correlated with code complexity metrics. Simple (10) to complex (1)\\
\hline
y&reqDevBudget &How tight is the development budget?  Assessment of flexibility in cost growth.\\
\hline
y&reqDevDomain &Average experience of development staff in the specific application domain (e.g., laser guidance system, space telescope, crew rescue, etc).  Consider all individual domains within the system (e.g., space telescope will require GN\&C, optics, propulsion, system management, telemetry, etc).\\
\hline
y&reqDevExpr&Average experience level of development staff, not specific to the problem domain, but overall experience in software development for the domain type (e.g., real-time embedded flight, financial, ground, manned , etc).\\

\hline
y&reqDevProcEff &How much emphasis does development management place on quality (as opposed to productivity)? For example, does development management participate in reviews, ensure that action items are tracked, and encourage extra analysis of suspected problems?  Assessment of effectiveness of process problem reports (like our CPAR to document discrepancies in following the process), process improvement actions, activity of a board to assess effectiveness of process, etc.  An assessment of the 'aliveness' of the developer process and attention to making it work to produce better products.\\
\hline
y&reqDevQualOrg &How effective is the embedded quality organization?  This measure includes consideration of size, breadth and depth of capability, and level of authority granted to quality organization applied to this project.\\
\hline
n&reqDevResAvail & Resource availability\newline
reqDevResAvail   = reqDevTrnOvr     + reqDevStfLev.\\\hline

y&reqDevSched &How much margin is in the development schedule?  Assessment of flexibility in end date.\\
\hline
n&reqDevStaff & Staff ability\newline
reqDevStaff      = reqDevExpr       + reqDevDomain  + reqDevResAvail.\\\hline
y&reqDevStfLev &Assessment of whether the quantity and distribution of staff is sufficient for the problem space\\
\hline
n&reqExtCstr& External constraint pressure\newline
reqExtCstr       = reqDevSched      + reqDevBudget.\\\hline
n& reqProcAdhere & Process adherence\newline
reqProcAdhere    = reqExtCstr       + reqDevProcEff + reqDevQualOrg.\\\hline
n & reqProcRigor & Process rigor\newline
reqProcRigor     = devCMM           + reqProcAdhere + reqDevTool. \\\hline
n& reqProdSpc & Problem space\newline
reqProbSpc      = reqStab          + sysDocQual    + reqCplx.\\\hline
n& reqStab& Requirements stability\newline
reqStab          = reqQualUserInput + novel.\\\hline
n & reqQual & Requirements quality\newline
 reqQual          = reqProbSpc       + reqDevStaff   + reqProcRigor.\\\hline
y&reqDevTool &Degree to which the developer uses tools in developing and analyzing requirements. Tools here include requirements management tools (DOORs, for example), traceability tools, simulations, process support, etc.\\\hline
y& reqDevTrnOvr&Experienced or historical rate of change of staff involved with requirements development\\
\hline
n&reqQualUserInput& Quality of user input.\newline
					reqQualUserInput = userExper        + userInvolve.\\\hline
y&sysDocQual&Qualitative estimate of the quality (completeness, correctness, and consistency) of system documentation from which software requirements may be derived.\\
\hline
y&userExperR&Experience level of system users with similar (or the same) systems or solution approach.  Maturity level of users in understanding technical aspects of system to be implemented and the scenarios in which it will be used.\\\hline
y&userInvolveR&Degree to which the system users are involved in the requirements definition process and the timeliness of that involvement.  Note that a high score here requires involvement or representation of all key system users, not just system operators.\\
\hline
\end{tabular}
}
\caption[Some definitions]{Some definitions of nodes in  the Dabney model. Scored 1 to 10.}\label{fig:dabnet}
\end{figure*}
