of Defense for Acquisition and Sustainment or a Senior Acquisition Executive. (B) Requirements The guidance required by subsection (a) shall provide the following with respect to requirements: (i) Requirements for covered acquisitions are developed on an iterative basis through engagement with the user community, and the use of user feedback in order to regularly define and set priorities for software requirements and evaluate the software capabilities acquired. (ii) The requirements process begins with the identification of the warfighter or user need, including the rationale for how these software capabilities will support increased lethality and efficiency, and the identification of a relevant user community. (iii) Initial contract requirements are stated in the form of a summary-level list of problems and shortcomings in existing software systems and desired features or capabilities of new or upgraded software systems. (iv) Contract requirements are continuously refined and set in priority order in an evolutionary process through discussions with users that may continue throughout the development and implementation period. (v) Issues related to lifecycle costs and systems interoperability are continuously considered. (vi) Issues of logistics support in cases where the software developer may stop supporting the software system are addressed. (vii) Rapid contracting procedures, to include timeframes for award, contract types, teaming, and options. (viii) Execution processes, including supporting development and test infrastructure, automation and tools, data collection and sharing, the role of developmental and operational testing activities, and key decisionmaking and oversight events, and supporting processes and activities such as independent costing activity, operational demonstration, and performance metrics. (ix) Administrative procedures, including procedures related to the roles and responsibilities of the implementing project or product teams and supporting activities, team selection and staffing