Program Engineering and System Development Lifecycle Management Engineering and Software Development Lifecycle Management standards ensure the context of the proposed solution meets identified business needs and requirements, is understood and communicated, and defines a standard development process that creates predictability and manageability. Technology Acquisition Planning—Individual Projects Standard Project Lifecycle COTS Project Lifecycle System Development Lifecycle Management Checklist Develop a Service Responsibility Matrix (SRM). The SRM identifies specific service areas and tasks by ownership. The SRM can be replaced with the detailed work breakdown structure (WBS) decomposed to the task level with resource allocations. Develop a System Requirements Traceability Matrix. The requirements traceability matrix is used to map the functional testability, WBS element allocation, budget line items, schedules, and organizational responsibility back to the designated requirement. All requirements are stated as discrete, single subject, testable, nonambiguous statements that include appropriate definitions, assumptions, and operational conditions associated via reference. All requirements are linked to the system design plan, detailed cost, and basis of estimate and test plan. Develop a System Engineering Plan. The system engineering plan specifies how a proposed program supports the District's Information Technology Strategic Plan. It specifies where the program fits within in the enterprise plan, and the deliverables that the program will produce. Develop a System Design Plan. The system design document includes descriptions of the schematic architecture, transaction flows, performance and capacity expectations (at the system and transactions levels), state diagrams, interface specifications and definitions, reliability and availability expectations, hardware/software architectures, and functional flows. Develop a Software Development/Acquisition Plan. The software development/acquisition plan describes the steps to be followed at each lifecycle phase; the risks and issues associated with each phase; the metrics to be collected, monitored, and reported; the schedules, milestones, and test plans for the software acquisition from inception to delivery. Page 1 of 3      1  2  3