TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
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 />
5044<br />
5045<br />
5046<br />
5047<br />
5048<br />
5049<br />
5050<br />
5051<br />
5052<br />
5053<br />
5054<br />
5055<br />
5056<br />
5057<br />
5058<br />
5059<br />
5060<br />
5061<br />
5062<br />
5063<br />
5064<br />
5065<br />
5066<br />
5067<br />
5068<br />
5069<br />
5070<br />
5071<br />
5072<br />
5073<br />
5074<br />
5075<br />
5076<br />
5077<br />
5078<br />
5079<br />
5080<br />
5081<br />
5082<br />
5083<br />
5084<br />
3. TECHNICAL REQUIREMENTS:<br />
3.1 GENERAL TECHNICAL REQUIREMENTS:<br />
1. The LRS shall be based on a service-oriented architecture (SOA) using Webservices<br />
standards and technologies, as described in Exhibit 3 (COUNTY’s<br />
Chief Information Office (CIO) Guiding Principles) and Exhibit 4 (California<br />
Enterprise Architecture Program: Service-Oriented Architecture (SOA)<br />
Master Guide) <strong>of</strong> Attachment H (Technical Exhibits).<br />
2. The LRS shall include independent Web services, including clearance,<br />
eligibility determination, benefit calculation, benefit issuance, and client<br />
correspondence, which shall be accessible by COUNTY-specified entities<br />
(e.g., other California SAWS systems) via LAnet/EN and the Internet.<br />
3. The LRS shall support access to and use <strong>of</strong> external Web services provided by<br />
COUNTY-specified entities.<br />
4. The LRS shall support flexible workflow using Business Process Execution<br />
Language (BPEL), including the ability to bypass internal LRS services and<br />
access to and use <strong>of</strong> external Web services, as specified by COUNTY.<br />
5. The LRS shall employ Web services, which are platform-independent,<br />
standards based Web applications that interact with other applications for the<br />
purposes <strong>of</strong> exchanging data via standardized messaging, e.g., Extensible<br />
Markup Language (XML). LRS shall also be capable <strong>of</strong> Web services based<br />
integration with external applications and services. Such Web services must<br />
comply with the following standards:<br />
a. Extensible Markup Language (XML) schema current version;<br />
b. Web services Definition Language (WSDL) current version;<br />
c. Universal Description, Discovery and Integration (UDDI) current version;<br />
d. Simple Object Access Protocol (SOAP) current version;<br />
e. Web services-reliability standard i.e. a SOAP protocol for guaranteed<br />
delivery <strong>of</strong> SOAP messages without duplicates;<br />
f. Security standards:<br />
i. WS-Security from Organization for the Advancement <strong>of</strong> Structured<br />
Information Standards (OASIS), which defines the mechanism for<br />
including integrity, confidentiality, and single message authentication<br />
features within a SOAP message;<br />
ii. Security Assertion Markup Language (SAML) from OASIS, which<br />
provides a means for partner applications to share user authentication<br />
and authorization information;<br />
iii. Standards defined by the Worldwide Web Consortium (W3C), and the<br />
Open Web Application Security Project (OWASP);<br />
g. National Institute <strong>of</strong> Standards and Technology (NIST) Federal<br />
Information Processing Standards (FIPS) <strong>Public</strong>ation 140-2 “Security<br />
LRS RFP - Attachment B (SOR) Page 145 November 30, 2007