Analyzing the System Proposal 1. There are a couple of requirements implied in the description of the current system. Please identify them. 2. There is at least one major risk (I would categorize it as a known-unknown) revealed in the system proposal. What is it? 3. What major tasks should the proposed system carry out? 4. List any business requirements in the system proposal. 5. List any user requirements in the system proposal. 6. List any functional requirements in the system proposal. 7. List any non-functional requirements in the system proposal. 8. List any system requirements in the system proposal.Automated Workflow System System Proposal This project will create and implement an Automated Workflow System (to be known as AWS). Current System When a customer contacts our business (known as "us") with a request, a work item is created. A work Item consists of a physical sheet of paper describing the request and the task(s) required to complete it. Work Items are distributed on a first-in, first-out basis. This does not always consider the relative importance of individual requests. This sometimes results in a delay in processing some items. Management of paper work items is challenging - paper takes up space, can sometimes be lost, and the handwritten notes added during the initial contact can be difficult to read. Proposal Related/Interdependent Project A separate project (Digital Work, or DW) is underway to automate the creation of work items based on customer contacts. The work item will become a digital artifact as the result of the DW project. The AWS proposal is dependent on the completion of the DW project and pre-supposes the existence of digital work items. The AWS System We propose to create an automated workflow system to manage, distribute, and track digital work Items. The new system will accept the digital work item ("Item", henceforth), determine the relative importance of the item with respect to the total workload, determine appropriate routing for the item, deliver the item to be worked, and allow the item to be "closed" when the required task(s) have been completed. Each item will be tracked from entry into the AWS throughout its life within the system. Such tracking information will be available to all employees requiring such access. Management will be able to monitor workload at the unit and individual employee levels throughout the work day and will be able to make some adjustments in workload distribution as needed. Proposed Budget & Timeline A preliminary budget covering the anticipated costs to design and deploy the AWS system is included under separate cover. A preliminary schedule for the early phases of analysis and design is likewise included under separate cover