1. Story Board: Disclaimer: The Graphical User Interface (GUI) designs and business flows included in this document are intended as a rough-draft proof of concept, and do not represent final application designs. Their intention is to allow readers to envision many of the known requirements in the context of GUI mocks or an application prototype, enabling meaningful discourse with the customer about the application vision. As these GUIs are reviewed with groups of actual users during iterative feedback sessions, the designs and contents will change. Month DD, YYYY

2. Solution Approach/Overview 2

3. Solution Users 3 There are a number of users of the proposed USACE application. Primary Users: The primary users of the system include: User Role 1 User Role 2 User Role 3 Secondary Users: There are other users who interact with the system, but are not part of the primary organization. This include: User Role 4 User Role 5 User Role N

4. Story Board Parameters 4 The purpose for laying out Story Boards is to present a prototype of solution elements visually to significantly improve the speed and effectiveness of Solution Design – so the Story Board is intended to result in modifications. The User Experience Architecture is focused on creating the underlying virtual architecture (automated forms/case file organization, inboxes and ad-hoc routing capabilities), rather than hard-coding complex business routing rules that are likely to change or require some flexibility. This is a best-practices approach, especially for a first phase of any solution. The GUIs presented herein are early mocks, considered “Concept Mocks” as the main goal is to identify the right conceptual functionality of the GUI. Final GUI designs will require multiple SME interaction sessions. The GUI mocks do not address every process and sub-process that needs to occur within the proposed solution, they provide a “style guide” against which more detailed and robust functionality can be expanded in a conventional manner.

5. Replace with actual SDD for solution… 5 Example GUI Mock… preferably with watermark disclaimer about it being a concept mock…

6. Replace with actual SDD for solution… 6 Example GUI Mock… preferably with watermark disclaimer about it being a concept mock…

7. Replace with actual SDD for solution… 7 Example GUI Mock… preferably with watermark disclaimer about it being a concept mock… Example Form A…

8. Replace with actual SDD for solution… 8 Example GUI Mock… preferably with watermark disclaimer about it being a concept mock…

9. . Questions:

10. Document Acceptance (may not be needed) 10 The following identifies the minimum list of individuals required to provide acceptance of this document. The top-level customer requirements as stated in this document are hereby acknowledged, approved and accepted as delivering and satisfying the concept of a Storyboard and UI Mock Ups document for the project. RoleName of Acceptor, Acceptance Date and Method Project ManagerName Project ManagerName EIM Project ManagerName