EDESuite Deliverables.xlsx

Deliverables

The following table lists the EDESuite and user documentation that the Contractor is required to develop and maintain. All system and user documentation shall comply with the LMM.

Pierce, Brian: Pierce, Brian:

Do we need to add the Serv. Pack docs?

Deliverable Type (Proj Mngt, Report, System, User) Deliverable Requires FSA Approval Frequency of

Introductions ‰ Opening Remarks The Mission - The Problem & Proposed Solution ‰ Identification of Key Stakeholders ‰ Project Organization ‰ The Implementation Plan ‰ Q & A / Next Steps Kickoff meeting minutes must capture all meeting attendees, discussions action items, risk and issues.

Project Management Project Management Plan Yes Annual Electronic Word Document DM 5 3 2 Must include: Goals, Objectives, Scope, Schedule, Resources, Risks Plan, Communications Plan, Organizational Chart, Transition Plan and Quality Plan

Project Management Risk Action Items and Issues Log No Per Release Electronic Word document X X X X See LMM Action log for criteria https://fsa.share.ed.gov/epms/ePMO/Shared%20Documents/Simple%20Project%20Toolkit/Executing/Output/Project_Issues_Log.docx Risk log should be specific and use complete sentences.

The area of impact must be identified.

Risks must be assessed to determine impact.

High impact risks must have a risk response identified along with a risk owner.

https://fsa.share.ed.gov/epms/ePMO/Shared%20Documents/Complex%20Project%20Toolkit/Planning/Schedule/1.3.6_Project%20Schedule%20Template.mpp Master Schedule Must provide a logical finish date of the project Includes Actual Start Dates, Actual Finish Dates, Actual Work, Actual Duration, % Complete, or % Work Complete of tasks Analyzes and manages project risks throughout both the development and maintenance phases High Level Schedule Must include major milestone dates for the life cycle of each product or service by release schedule Must provide a logical finish date of the project Status Report Provides weekly reports which may include weekly testing statistics, activities completed, notice of any continuing problems, status of on- going projects, and issues/questions awaiting resolution No Weekly Electronic Word document X X X X EDESuite Status Report Should include weekly testing statistics, software download statistics (from FSA Knowledge Center server site), activities completed, notice of any continuing problems, status of on-going projects, and issues/questions awaiting resolution

Must include monthly status of KPIs / SLAs.

Is a written description of the product in this contract in order to give the development team overall guidance to the architecture of the software project.

Must be consistent with requirements, Preliminary Design and Technology Standards.

Must be a feasible and workable design.

System User Acceptance Test Support Plan Yes Per Release Electronic Word document DS 10 5 5 User Acceptance Test Plans should detail the support and resources that will be provided to the FSA Acceptance Test team by contractor and their system testing subcontractor, as well as a listing of high-level responsibilities expected from each partner.

LMM Reference:

https://fsa.share.ed.gov/TOSL/PBLSH/Master_Test_Plan_Exemplar.pdf https://fsa.share.ed.gov/TOSL/PBLSH/User_Acceptance_Test_Plan_Exemplar.pdf System System Test Procedures/Test Cases Yes Per Release Electronic Word document DS 10 5 5 (See examples of existing System Test Procedures/Test Case documents.)

Should provide test procedures that outline the process and data needs to test each function in system Should provide detail test cases outlining the the data, steps, expected and actual results for each item that will be executed during system test.

System System Test Summary Report Yes Per Release Electronic Word document DM 5 3 2 The Test Summary Report Must summarize the system test phase of the project and include support materials related to version, deviations from the agreed upon System Test Plan.

Must perform an overall assessment of the product tested and status of incidents identified during system test activity.

System Business Impact Analysis (BIA) Yes Per Release Electronic Word document TBD TBD TBD TBD The BIA Must define all potential system vulnerabilities and related cost impacts, as well as describe the strategies for minimizing vulnerabilities and risks.

System Release Version Description Documents Yes Per Release Electronic Word document DS 10 5 5 Release Version Description Documents Should provide information regarding what changes are occurring in the application or its infrastructure, how the changes are to be installed in the application and/or its infrastructure.

Typically this is part of the Cover Letter and Electronic Announcement documents posted for the FSA partner community accompanying each release.

System Quality Assurance/Quality Control processes and procedures Yes Provided, upon request Electronic Word document or as available DM 5 3 2 Quality Assurance/Quality Control processes and procedures Should outline the steps taken to ensure that products and services meet the requirements Should include plans for improving results over time Should include elements of Quality Assurance (QA) and Quality Control (QC) for both software engineering and operational activities in both development and steady state Should cover all deliverables, processes, products, and phases of the project life cycle

Must include procedures and technical measures that enable the recovery of IT systems, operations, and data after a disruption.

Must include restoring IT operations at an alternate location Must include recovering IT operations using alternate equipment Must perform some or all of the affected business processes using non-IT (manual) means (typically acceptable for only short-term disruptions).

System System Security Plan Yes Annually, per product Electronic Word document TBD TBD TBD TBD The System Security Plan Must provide system security requirements and describe the management, operational and technical controls in place as well as responsibilities and expected behavior of those accessing the system.

Should describe general system information mapping to FIPS 199 categorization, the type of data processed, points of contact, system environment, applicable federal laws and guidelines and any sensitive information processed by the system.

Must be approved by the FSA CISO.

System System Test Plan and Acceptance Criteria Yes Annually Electronic Word document DS 10 5 5 The System Test Plan Shall provide a comprehensive plan for testing of all system functions until the system is retired from production.

Should define the development of a comprehensive System Test package to simulate operation of the entire system and to serve as the basis for accepting or rejecting the system.

Should have the purpose to: judge the adequacy of the testing and explain the tools used to measure the progress being made with a mechanism for understanding of project test plans sequence of events leading to system acceptance (timetable) system fulfills the agreed-to customer requirements LMM Reference: https://fsa.share.ed.gov/TOSL/PBL SH/System_Test_Plan_Exemplar.pdf

System Project Test Plans (each major release) No Per Release Electronic Word document X X X X LMM Reference:

https://fsa.share.ed.gov/TOSL/PBLSH/Master_Test_Plan_Exemplar.pdf System Requirements Traceability Matrix No Per Release Electronic Excel document X X X X The Requirements Traceability Matrix Must associate requirements with portions of the build designed to satisfy them.

Must tie testing cases and procedures to the requirements on which they are based to ensure that the build meets all requirements.

Shall accurately document the interface between two systems or subsystems.

System Configuration Management Plan Yes Annually Electronic Word Document DS 10 5 5 The Configuration Management (CM) Plan Must provide an overview of the organization, activities, overall tasks, and objectives of CM for an initiative.

Must addresses: baseline work products, describes the mechanism to track and control changes/change requests, and the mechanism to establish and maintain baseline integrity.

LMM Reference:

https://fsa.share.ed.gov/TOSL/PBLSH/Enterprise_Configuration_Management_Plan_Template.docx User Packaging Technical Reference Yes Per Release (as needed) Electronic PDF document DS 10 5 5 The Packaging Technical Reference Should provide instructions and record layouts for integrating your school’s mainframe or third-party software with the EDExpress for Windows Packaging module.

Should include instruction for how schools can use the EDExpress Packaging module to:

o Update the Packaging database table with an external import function.

o Enable users to add or modify records in the Packaging module of EDExpress by importing External Add, External Change, and Add Funds records from an external system.

o Enable users to export packaging data in custom file formats.

o Enable users to export the packaging data from EDExpress to your school’s system.

o Must be 508-compliant User COD Technical Reference (Combo System Volume TOC and Sections 1-4, DL Tools Volume TOC and Sections 1-4) Yes Annually and as needed Electronic Word document DS 10 5 5 COD Tech Ref Volume 3: Combo Systems:

Should contain a general overview of information and guidance for schools and other agencies who use EDExpress in combination with third-party software or in-house systems to exchange Federal Pell Grant, Teacher Education Assistance for College and Higher Education (TEACH) Grant, and William D. Ford Direct Loan program data with the COD System.

Must be 508-compliant

COD Tech Ref Volume 4: DL Tools:

Should contain a general overview of information and guidance for schools and other agencies who use Direct Loan (DL) Tools Release 14.0 in combination with the three most recent cycle versions of EDExpress, third-party software and/or other in-house systems to track, analyze, reconcile, and rebuild William D. Ford Federal Direct Loan data processed by the COD System.

Must be 508-compliant

Should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the document should reflect all updates for the next release(s) that users need to be aware of.

Must be 508-compliant User EDExpress for Windows Installation Guide Yes Per Release Electronic PDF document DS 10 5 5 EDExpress for Windows Installation Guide Should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the document should reflect all updates for the next release(s) that users need to be aware of.

Must be 508-compliant.

should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the document should reflect any updates for the next release(s) that users need to be aware of Must be 508-compliant User DL Tools Cover Letter Yes Per Release Electronic PDF document DS 10 5 5 DL Tools Cover Letter Should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the document should reflect all updates for the next release that users need to be aware of.

Must be 508-compliant.

User DL Tools Installation Guide Yes Per Release Electronic PDF document DS 10 5 5 DL Tools Installation Guide Should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the document should reflect all updates for the next release that users need to be aware of.

Must be 508-compliant.

User EDExpress for Windows Help Text Yes Per Release RoboHelp files released as component of EDExpress DE 15 7 7 EDExpress for Windows Help Text Must be 508-compliant. The document should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the help text should reflect all updates for the next release(s) that users need to be aware of.

User DL Tools Help Text Yes Per Release RoboHelp files released as component of DL Tools DE 15 7 7 DL Tools Help Text Must be 508-compliant. The document should be clearly written, factually accurate, free from grammatical errors, and information presented should be at a level of detail appropriate to the audience using it. Information in the help text should reflect all updates for the next release(s) that users need to be aware of.

User Electronic Announcements Yes As needed for Annual Releases Electronic Word document DS 10 5 5 Electronic Announcement Shall accurately describe the release/issue and associated user documentation, if appropriate. The Electronic Announcement will follow all FSA communication standards and style guidelines.

Must be 508 compliant.

System Incident Response Plan Yes Annual Electronic Word Document TBD TBD TBD TBD Must use FSA provided document template -Must adhere to applicable agency handbooks and standrards -document is provided on time, according to the approved and established government schedule.

-document accurately documents the incident reponse and reporting processes and procedures.

System System Authorization Boundary Document Yes Annual Electronic Word Document TBD TBD TBD TBD Must use FSA provided document template -Must adhere to applicable agency handbooks and standrards -Document is provided on time, according to the approved and established government schedule.

-Document accurately documents system components in the major application system boundary.