01.02.2014 Views

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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 />

5987<br />

5988<br />

5989<br />

5990<br />

5991<br />

5992<br />

5993<br />

5994<br />

5995<br />

5996<br />

5997<br />

5998<br />

5999<br />

6000<br />

6001<br />

6002<br />

6003<br />

6004<br />

6005<br />

6006<br />

6007<br />

6008<br />

6009<br />

6010<br />

6011<br />

6012<br />

6013<br />

6014<br />

6015<br />

6016<br />

6017<br />

6018<br />

6019<br />

6020<br />

for COUNTY-specified Users to manage COUNTY’s caseload, over<br />

the term <strong>of</strong> the Agreement.<br />

5. The LRS Component shall support access via CONTRACTORprovided<br />

secure and confidential Internet connectivity to the LRS,<br />

including LRS Data input, updates, and queries, for COUNTYspecified<br />

Users, including applicants, participants, and the general<br />

public, over the term <strong>of</strong> the Agreement.<br />

6. The LRS Component shall support any growth in usage <strong>of</strong> the<br />

CONTRACTOR-provided secure and confidential Internet<br />

connectivity to the LRS, over the term <strong>of</strong> the Agreement.<br />

3.4 COMPONENT FRAMEWORK:<br />

Component Framework refers to the underlying s<strong>of</strong>tware foundation,<br />

technologies, standards, and specifications by which the LRS Application<br />

S<strong>of</strong>tware and its service components are built, exchanged, and deployed across<br />

the LRS SOA. The component framework is the “n-tier” environment within<br />

which the functional services provided by the LRS shall be implemented. The<br />

LRS Application S<strong>of</strong>tware design shall be split into distinct layers for<br />

presentation, business logic, and database management. Each layer shall be<br />

independent <strong>of</strong> the other and shall have defined interfaces for communication.<br />

This architecture shall facilitate change in the presentation, business logic, or<br />

database management layers without affecting the other layers.<br />

1. The LRS shall include guaranteed message delivery in order to enable “submit<br />

and forget” processing to improve LRS Application S<strong>of</strong>tware performance.<br />

2. The LRS s<strong>of</strong>tware applications shall be independent <strong>of</strong> the technical<br />

components (e.g., there shall be little effect on an application if a technical<br />

component, such as the TCP/IP stack, is changed or updated).<br />

3. The LRS shall be designed so that all major LRS Application S<strong>of</strong>tware<br />

processing occurs at the enterprise server level (i.e., Primary Central Site),<br />

with no resident or permanent processing occurring at the workstation or<br />

laptop level except for presentation layer activities.<br />

3.4.1 Security.<br />

The Security Layer shall ensure that the LRS includes appropriate security<br />

throughout the LRS that meets or exceeds all applicable federal, State, and<br />

local laws, rules, regulations, ordinances, guidelines, directives, policies,<br />

LRS RFP - Attachment B (SOR) Page 171 November 30, 2007

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!