Wayback Public Library (WPL) is the library that time forgot. They have not modernized their systems for managing books since 1983 when they got the new microfiche machine. They’re pretty sure that th

Project Wayback Public Library Information System Wayback Pu blic Library ( WPL ) is the library that time forgot . They have not modernized t heir systems for managing books since 198 3 when they got the new m icrofiche machine. They ’re pretty sure that th ey can get some govern ment funding to modernize t heir processes, but they ’re not sure what to do, how to do it, or how to justify it. You r Mom works for WPL and knows that you ’ve recently take n a course on systems analysis and de sign. She also knows you work cheap , and that ’s good because there isn ’t any bu dget allocated yet. You and your te am decide to take on this project as a contribution to your community and to gain val uable experience . You need to help WP L analyze t heir existin g processes and propose changes. This needs to be pack aged in a format that can be sent as a proposal to obtain impleme ntation fun ding . The proposal must be s ent in as one or more electronic documents . At minimum, your proposal needs to contain: 1. Activity diagrams: a. Check -in current state b. Check -out current state c. Check -in future state d. Check -out fu ture state 2. Domain model . 3. Epic /user stories (with MoSCo W priorities ). 4. Full y dressed use case narrative for check -in epic . 5. Wir efr ame model for UI with navigation . 6. Rele ase sch edule for development . 7. Estimate of costs and benefits for this project . 8. Describe who will be doing the software development. 9. Document any additional di scovery that needs to be performed and how you will obt ain that information. Note : If you make any assumptions during t hese processes, document what they are. You have been provided with the following documentation : • WplDescription.pdf - A document that describes existing processes and prop osed improvements. • Wpl UserStoriesTemplate.pdf – A template document example that you can use to build a document that identifies epics, their related user stories , and MoSCo W priorities .