TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Los Angeles COUNTY<br />
<strong>Department</strong> <strong>of</strong> <strong>Public</strong> <strong>Social</strong> <strong>Services</strong><br />
LEADER Replacement System (LRS)<br />
6561<br />
6562<br />
6563<br />
6564<br />
6565<br />
6566<br />
6567<br />
6568<br />
6569<br />
6570<br />
6571<br />
6572<br />
6573<br />
6574<br />
6575<br />
6576<br />
6577<br />
6578<br />
6579<br />
6580<br />
6581<br />
6582<br />
6583<br />
6584<br />
6585<br />
6586<br />
6587<br />
6588<br />
6589<br />
6590<br />
6591<br />
6592<br />
6593<br />
6594<br />
6595<br />
6596<br />
6597<br />
6598<br />
17. The LRS shall display a screen name and screen ID on all screens.<br />
a. The LRS shall place the Web page (s) in a consistent location<br />
throughout the LRS Application S<strong>of</strong>tware and at a place that is<br />
visually easy to locate; and<br />
b. The LRS shall clearly distinguish sub-pages as unique from a<br />
“parent” Web page as well as from the other sub-pages derived<br />
from the “parent” Web page.<br />
18. The LRS shall provide the User with an easily viewed navigation<br />
structure that allows him to know where he is at all times and can<br />
easily return him to a desired starting point, including the LRS “home”<br />
logout Web page with a single action from anywhere within the LRS<br />
navigation structure.<br />
19. The LRS shall immediately transfer LRS Data values from “pop-ups”<br />
to the appropriate field when selected and proceed to the next LRS<br />
Data entry field.<br />
20. The LRS shall allow default values to be designated for specific<br />
actions or LRS Data fields.<br />
21. The LRS shall adjust required LRS Data based upon answers to<br />
previous questions.<br />
22. The LRS shall allow the use <strong>of</strong> data-driven branching logic to develop<br />
the LRS screen-based workflows. This shall enable the design <strong>of</strong> an<br />
interactive workflow wherein the LRS User interface shall branch to<br />
the appropriate next question based on previous sets <strong>of</strong> responses and<br />
other existing LRS Data.<br />
23. The LRS shall include tools to design and automate the screen-based<br />
workflow that facilitate an underlying business process or sub-process.<br />
These tools shall allow for the design and testing <strong>of</strong> the workflow<br />
without the need for programming (e.g., the tools would include a<br />
graphical editing and simulation tool for defining and verifying screenbased<br />
workflows).<br />
24. The LRS workflow tools shall allow for the development <strong>of</strong> screen and<br />
Web page flows that progress logically with no break in functionality<br />
(e.g., returning to the LRS home page unnecessarily). The screen flow<br />
shall return the User to a default starting point that follows logically<br />
from his completion <strong>of</strong> the previous task.<br />
25. The LRS shall ensure that any LRS Data entered propagates to all<br />
affected pages, screens, tables, and indexes based on the needs <strong>of</strong> the<br />
underlying business processes and/or sub-processes.<br />
LRS RFP - Attachment B (SOR) Page 187 November 30, 2007
Change language