leader replacement system - Department of Public Social Services ...
leader replacement system - Department of Public Social Services ...
leader replacement system - 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 />
136<br />
137<br />
138<br />
139<br />
140<br />
141<br />
142<br />
143<br />
144<br />
145<br />
146<br />
147<br />
148<br />
149<br />
150<br />
151<br />
152<br />
153<br />
154<br />
155<br />
156<br />
157<br />
158<br />
159<br />
160<br />
161<br />
162<br />
163<br />
164<br />
165<br />
166<br />
167<br />
168<br />
169<br />
170<br />
171<br />
172<br />
173<br />
174<br />
175<br />
176<br />
177<br />
178<br />
179<br />
180<br />
allows for the development <strong>of</strong> a <strong>system</strong>s architecture that is also modular and<br />
flexible for unanticipated changes in business requirements and technology.<br />
The SOA implementation shall be based on the following principles as<br />
defined under California Enterprise Architecture Program Service-Oriented<br />
Architecture (SOA) Master Guide:<br />
1. Design for Ease <strong>of</strong> Use<br />
2. Design Web services with appropriate granularity<br />
3. Reassemble before Rewrite<br />
4. Web services should be loosely coupled and extensible<br />
5. Web services must have well-defined interfaces<br />
6. Design stateless base Web services<br />
7. Implement business processes via orchestrating Web services into a<br />
process flow (BPEL standard)<br />
8. A governance structure must be created to manage Web service<br />
development and operational environments<br />
9. Implement Web service security and policy enforcement standards<br />
• Support Event-Based Processing. All new <strong>system</strong> design and<br />
development should be driven by business events. Event-based processing<br />
enables applications to adapt quickly to changes in business processes by<br />
only changing the application component related to the changed business<br />
event and strengthens linkage to the business by mirroring the actual<br />
business environment.<br />
• Support Workflow Processing. All new <strong>system</strong> design and development<br />
should incorporate workflow functionality. Workflow processing enables<br />
applications to incorporate functionality such as approvals within an<br />
application and change processing paths through the application without<br />
source code programming changes.<br />
• Support Data Warehousing. All new <strong>system</strong> acquisition and development<br />
should support the capability to develop online transaction processing (OLTP)<br />
and/or data warehousing applications. These two classes <strong>of</strong> applications<br />
require very different data models and make very different demands on<br />
database <strong>system</strong>s. Online transaction processing focuses on quick updates <strong>of</strong><br />
the data. Often, the speed <strong>of</strong> these updates can be dramatically slowed down<br />
by the processing generated by user queries. For this reason, it is best to<br />
separate the data warehouse from the OLTP. In so doing, we also provide for<br />
a more secure environment for both OLTP and data warehousing.<br />
• Partitioning and Modularization <strong>of</strong> Application Components. System<br />
solutions should be highly partitioned, modular in design, that are comprised<br />
<strong>of</strong> components that are maximally decoupled, and that use standards-based<br />
messaging protocols for communication between external and internal<br />
<strong>system</strong>s. This kind <strong>of</strong> modular implementation should allow for the upgrade,<br />
LRS RFP - Attachment H (Technical Exhibits) Page 11 November 30, 2007