Summary: Minimum development life cycle documentation is required for varying life cycle tracks. Please include these documents in your project to ensure you have identified all needs of your project. Additional information related to the development life cycle tracks is available at UCOP’s standards website.

Topic Detail Software/Tool Evaluations (usually low cost) Requirements Document – supplied by project stakeholder or technical staff. Categorize requirements into mandatory, desirable and optional categories. Features Comparison Form – after identifying and evaluating tools from various vendors, complete the Features Comparison Matrix containing each vendor product, cost, support, and requirements ratings. Document selection results – conclusion or summary of comparison findings. New Project Development or Major System Enhancement Requirements Document – supplied by user or technical staff. Capacity plans – developed within technical requirements. Data Model – develop data model, scheduled reviews by DBA Object Model – review by object librarians for redundancy Project Plan – required for all major or visible projects. See Project Plan Content Guidelines template and use JIRA or Enterprise PM Test Plan – supplied by user/technical staff. User Help/Instructions – incorporate in the application. Training materials – supplied by functional offices/users Production turnover – refer to change management procedures Purchased Applications Requirements Document – supplied by project stakeholder or technical staff. Request for Proposal Document (RFP) — including an overview of the organization users of the system, operating environment of the system, schedule of key events for the proposal process (deadline for proposals), response terms and conditions (contacts, date and delivery of proposal, approval process and notification procedures), technical requirements and other restrictions.   New Project Buy vs Build Analysis Requirements Document – supplied by project stakeholder or technical staff. Categorize requirements into mandatory, desirable and optional categories. Document product list – identify products and vendor/developer in order to schedule product demos, site visits, Features Comparison Form – after identifying and evaluating tools from various vendors, complete the Features Comparison Matrix containing each vendor product, cost, support, and requirements ratings. Document selection results – conclusion or summary of comparison findings. Documents for Purchased Applications track or New Project Development track

Need an expert? Please contact the Systems Development team.

Notice: University policies, procedures and applicable collective bargaining agreements shall supersede information in this document or elsewhere on this site.

Author: N/A		Last published: N/A