<p>HIGH-LEVEL BUSINESS REQUIREMENTS SUMMARY</p><p>Key Business Needs The following sections document the various PROPOSED business requirements of this project. Business case drivers, product definition documentation, legal/regulatory, and other stated requirements or needs that must be met by the final solution are described as Key Business Needs. They should be defined as much as possible for further exploration during detailed requirements definition. These Key Business needs will define the core application functionality. Business Need Summary Table</p><p># Need P Concerns Current Solution Proposed Solution n Workflow-based processing H Need to ensure the quality There is no system Use workflow ‘wizards’ to provide decision prompts, and completeness of managed workflow that launch when key date reminders, and other required documentation. processing or built-in QA. dates or decisions are automated triggering, activated stepping user tailored based on situation, through the business user, etc management process. 1</p><p>Desired Features Interviews, requirements gathering, and research have identified the following high-level Desired Features. These features will be matched to Business Needs, refined, expanded, prioritized, and/or modified during the requirements gathering process, and updated prior to final release as part of the sizing effort.</p><p>© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 6, 2018 Page 1 Features Summary Table</p><p># Feature P Usability Concerns n The [APPLICATION] workflow H A workflow-based system will support QA and ease of use requirements, but manager shall use wizard-like must be flexible to allow the user accountable to make judgment decisions prompts that are date and/or decision within a framework about the completion of the work. activated. n.a The [APPLICATION] shall provide an H As other departments and individuals are involved the business process Assignment feature to allow management, the handoff must be tracked and within certain defined electronic notification and tracking of guidelines, such as times to respond, standard expectations, and cross-department assignments and responsibility to complete the requested work must be communicated. responsibilities during the execution of the workflow activities. n.b The [APPLICATION] shall include a M Scheduling and notification of workflow upcoming workflow activities should Scheduling feature that will both be date range based (what is due in the next 30 days) as well as vendor calculate key processing events and based (what are all the pending activities and dates for vendor XYZ). allow a user defined date to provide a means to notify role-based users of the required event activity. 1</p><p>Critical Success Factors Key Success Indicator (if Action Steps to Assure Critical Success Factor applicable) Success To have standardized the workflow  Function called Work Flow  Complete Project Definition processing to the approved tools and Manager. Document, work plan, and integration systems within the [APPLICATION].  Audit log with time/date stamp and business requirements. user information by event.  Client Acceptance process.  Updateable business rules governing approval routing.</p><p>Key Assumptions</p><p>Assumption Description</p><p>© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 6, 2018 Page 2</p>