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 />
181<br />
182<br />
183<br />
184<br />
185<br />
186<br />
187<br />
188<br />
189<br />
190<br />
191<br />
192<br />
193<br />
194<br />
195<br />
196<br />
197<br />
198<br />
199<br />
200<br />
201<br />
202<br />
203<br />
204<br />
205<br />
206<br />
207<br />
208<br />
209<br />
210<br />
211<br />
212<br />
213<br />
214<br />
215<br />
216<br />
217<br />
218<br />
219<br />
220<br />
221<br />
222<br />
223<br />
224<br />
225<br />
exchange, and reuse <strong>of</strong> products with minimal retooling or disruption to the<br />
overall environment.<br />
• Application and/or Network Security. The County requests that<br />
departments implementing new applications contact Allen Brusewitz, Chief<br />
Information Security Officer for assistance in determining security<br />
requirements for the network, application and associated database. Mr.<br />
Brusewitz may be reached by telephone at (562) 940-3873 or by email at:<br />
ABrusewitz@cio.lacounty.gov.<br />
2. Development Standards<br />
The standards presented below are preferred technologies for products<br />
developed for the County. The County will consider alternate proposals that<br />
deviate from the standards if an acceptable business case is presented.<br />
• Unified Modeling Language. The use <strong>of</strong> the Unified Modeling Language<br />
(UML) for <strong>system</strong> specification and modeling is highly recommended for all<br />
enterprise level applications. UML is an open non-proprietary methodology<br />
used for business process and organizational structure modeling that<br />
promotes object-oriented s<strong>of</strong>tware development.<br />
• Database Management Systems (DBMS). The standard database<br />
management <strong>system</strong> (DBMS) for enterprise or affinity group applications is<br />
Oracle. Micros<strong>of</strong>t’s SQL Server DBMS is acceptable for department<br />
applications and may be <strong>of</strong>fered as an alternative for enterprise or affinity<br />
group applications, but must present an acceptable business case.<br />
• User Interface. All newly developed or acquired applications shall be<br />
accessible using a standard HTTP/HTTPS browser. To the extent possible<br />
and when cost-effective applications shall be browser neutral. <strong>Public</strong> Internet<br />
access shall be developed to be “browser neutral” and support the latest<br />
version <strong>of</strong> the browser and also be backward compatible by three (3) major<br />
releases.<br />
• Component Based Development Language. Enterprise or affinity group<br />
application should utilize Java2 Enterprise Edition (J2EE) to support an open,<br />
non-proprietary architecture. <strong>Department</strong> applications may utilize a .NET<br />
platform. New <strong>system</strong>s should use XML-based data architectures for<br />
increased standardization and data sharing, including industry specific XML<br />
dictionaries and schemas (e.g., Justice XML, etc.).<br />
• Open Architecture. All new <strong>system</strong>s should utilize an open architecture<br />
using industry standards such as Web <strong>Services</strong> and XML, WSDL, SOAP,<br />
UDDI, SAML, and OASIS. Also, functionality such as Transactional Integrity,<br />
Monitoring, Auditing, and Security must be supported natively by the product.<br />
LRS RFP - Attachment H (Technical Exhibits) Page 12 November 30, 2007
Change language