14 0,56,179,ReqDevProcEff,null,0,11,22,opt,0,0,0,Process effectiveness actions - How much emphasis does development management place on quality (as opposed to productivity)? For example, does development management ensure that review action items are tracked, and encourage extra analysis of suspected problems? Assessment of effectiveness of process problem reports (e.g., a formal mechanism to document, correct and publish 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. 1,372,330,ReqDevStaff,null,0,11,22,opt,0,0,0,Staff Ability - Overall ability level of the requirements development staff, in terms of size, development experience, domain experience and turnover with respect to the problem at hand. 2,42,355,ReqQual,null,0,11,22,opt,1,0,0,Requirements quality - Overall relative measure of requirements quality, and hence, probable relative defect density. 3,230,3,RRdPress,null,0,11,22,opt,1,0,0,Cost/schedule pressure - Similar to the cost and schedule pressure on requirements development. In some cases, the developer requirements inspection/checking process is more tightly constrained than requirements development. 4,29,117,RRdUserInvolve,null,0,11,22,opt,0,0,0,Stakeholder involvement - Degree to which users are involved in the requirements validation process. This is similar to but can be different from the user involvement for requirements development. 5,159,58,RRdFocus,or,0,11,22,opt,0,0,3,3,0,4,Defect Removal Effort/Focus - How much effort or focus does the developer apply to defect identification and removal during the requirements phase? Are users involved to make sure requirements are right, is there a rush to complete deliverables, is the defect removal process effective and adhered to? 6,311,18,RRdReviewQual,null,0,11,22,opt,0,0,0,Review quality - Quality of the embedded review process. For example, do the developers do formal, detailed requirements reviews? Do they use entry and exit criteria, track and board issues, etc? Do they hold walkthroughs with broad scope support? 7,550,25,RRdSim,null,0,11,22,opt,0,0,0,Simulation tool use - Degree to which the development organization uses simulation to understand and validate requirements. This does not refer to simulations to verify requirements but rather to simulations of the conceptual operation of the system or particular subsystems to assure the right requirements are being specified. This could be a model of the expected environment and the system/subsystem reaction to it at an abstract rather than implementation level. Completeness of those simulations. Coverage of novel or complex areas. 8,625,25,RRdReason,null,0,11,22,opt,0,0,0,Reasoning tool use - Degree of use of reasoning tools. By reasoning tools, we mean tools such as automation of formal methods, model checking, etc. 9,700,25,RRdUML,null,0,11,22,opt,1,0,0,Representation tool use - Degree to which the development organization uses representational tools to automate and support requirements validation. The best example of representation tools is UML. 10,447,167,RRdTools,or,0,11,22,opt,0,0,3,7,8,9,Tools effectiveness - Overall level and effectiveness of tool use in the requirements analysis process. 11,308,125,RRdTech,or,0,11,22,opt,0,0,3,5,6,10,Techniques Employed effectiveness - Overall level and effectiveness of defect removal techniques used by the developer. 12,269,227,DRRd,or,0,11,22,opt,0,0,2,11,1 13,179,281,FPRRRd,or,200,11,22,opt,0,1,2,2,12 Default,3,2,3,9,1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3,1,13,1,1,1,2,2,2,2,3,3,3 14 = Number of nodes in the network. This is used as an offset in the iteration of the input. 11,308,125,RRdTech,or,0,11,22,opt,0,0,3,5,6,10,Techniques Employed effectiveness - Overall level and effectiveness of defect removal techniques used by the developer. ^One single node. Broken down as follows: 11 = Index 308 = x position 125 = y position RRdTech = Name or = Operation 0 = Priority 11 = Minimum (left end of distribution) 22 = Maximum (right end of distribution) opt = DistributionLocked status (opt = mutable, fixed = locked) 0 = Binary flag "hasGivenDistribution" (0 = no, 1 = yes) 0 = Binary flag "hasGoalDistribution" (0 = no, 1 = yes) 3 = Number of children 5,6,10 = Indexes of children ,Techniques Employed... = Description text Default,3,2,3,9,1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3,1,13,1,1,1,2,2,2,2,3,3,3 ^One single view/user-profile. Broken down as follows: Default = Name 3 = Number of nodes with given distributions 2,3,9 = Index of nodes with given distributions 1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3,1,1,1,2,2,2,2,3,3,3 = Given distributions (10 numbers per distribution) 1 = Number of nodes with goal distributions 13 = Index of node with goal distribution 1,1,1,2,2,2,2,3,3,3 = Goal distribution