Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

PP Two

394 views

Published on

  • Be the first to comment

  • Be the first to like this

PP Two

  1. 1. Service Oriented Architecture (SOA) Application in Justice Information Sharing
  2. 2. Enterprise Architecture Challenges <ul><li>How can I design a system which represents effectively the business process and at the same time is aligned with the key drivers of an organization? </li></ul><ul><li>How can I build an architecture that could respond to future changes without significant modifications? </li></ul>
  3. 3. How Alignment and Agility are Achieved? Application Layer Services Interface Layer Business Process Layer .NET J2EE Legacy Orchestration Service Layer Business Service Layer Application Service Layer
  4. 4. Alignment Makes a Difference Today <ul><li>SOA is a bridge that creates a symbiotic and synergistic relationship between the business and the technology world. </li></ul><ul><li>This relationship is more effective, powerful and valuable than anything experienced in the past. </li></ul><ul><li>The immediate result is achieving business process quality with the help of technology. </li></ul>
  5. 5. Agility is the Promise of the Future <ul><li>The resulting architecture will evolve effectively and efficiently as the underlying business processes change. </li></ul><ul><li>Estimated reduction of information technology expenses in the long term by as much as 20%. * </li></ul><ul><li>Savings become exponential over time as the library of business services expand and greater degree of reuse is achieved. </li></ul>* Based on Gartner’s estimate
  6. 6. Silos of Justice and Public Safety Information <ul><li>Existing systems are mostly custom built, use custom means for integration, and exemplify stand-alone “silos” of data which make it costly for sharing information. </li></ul>
  7. 7. The Interoperability Challenge <ul><ul><li>There are approximately 100,000 autonomous agencies that have a critical need to share information across their various information systems. </li></ul></ul><ul><ul><li>This variety creates multiple layers of interoperability problems because hardware, software, networks, and business rules for data exchange are different. </li></ul></ul>
  8. 8. An Approach to Resolution Data Model There are many existing ways to protect the data and to manage users and their access The existing systems store and interpret data in a variety of different ways The existing systems utilize different technologies Many business processes span multiple agencies and multiple systems Best Practices Privacy Security Architecture
  9. 9. Available Global Solutions There are many existing ways to protect the data and to manage users and their access The existing systems store and interpret data in a variety of different ways The existing systems utilize different technologies Many business processes span multiple agencies and multiple systems Global Best Practices Global Privacy Solutions Global Security Solutions JRA NIEM
  10. 10. The Role of Architecture <ul><ul><li>Minimize the dependencies between integrated information systems. </li></ul></ul><ul><ul><li>Favor technologies that leverage open industry standards . </li></ul></ul><ul><ul><li>Promote the treatment of integration interfaces as sharable and reusable enterprise assets . </li></ul></ul>
  11. 11. The Result is Effective and Efficient Information Sharing <ul><li>This approach provides inherent agility and scalability and can be utilized on multiple levels for federal, state, local and tribal sharing of justice and public safety information. </li></ul>
  12. 12. The Justice Reference Architecture (JRA) <ul><li>A Reference Architecture provides a proven template solution and a common vocabulary with which to discuss implementations, often with the aim to stress commonality. </li></ul><ul><li>The Justice Reference Architecture is: </li></ul><ul><ul><li>Developed specifically for the Justice domain and focuses on information sharing in a complex multi-jurisdictional environment. </li></ul></ul><ul><ul><li>Leverages the best practices of industry and specifically the OASIS Reference Model for SOA. </li></ul></ul><ul><ul><li>Continuous effort to maintain consistency with other architecture initiatives. </li></ul></ul>
  13. 13. Mission, Vision and Audience <ul><li>Mission: To enhance justice and public safety through a service-oriented approach to information sharing. </li></ul><ul><li>Vision: Global JRA and related documents will be the definitive source for justice and public safety agencies providing guidance on implementing a service-oriented approach to information sharing. </li></ul><ul><li>Target Audience: The target audience for the reference architecture and guidance is any group or set of justice partners that want to share information and agree to implement common business rules and infrastructure requirements. </li></ul>
  14. 14.
  15. 15. Architecture Principles <ul><li>Independence of Information Sharing Partners </li></ul><ul><li>Scalability to Allow Incremental Implementation </li></ul><ul><li>Diversity of Data Source Architectures </li></ul><ul><li>Long Term Agility </li></ul><ul><li>Reuse and Sharing of Assets </li></ul><ul><li>Alignment with Best Practices and Experience </li></ul>
  16. 16. The Two Main Use Cases <ul><li>Use Case One: To provide a starting point for local information sharing architectures </li></ul><ul><li>The architect of an information sharing enterprise will use the JRA as a basis or starting point for defining an information architecture for that enterprise.  The architect may also use JRA services as a starting point for describing the services to be offered within his/her enterprise. </li></ul><ul><li>Use Case Two: To provide a national architecture for information sharing services </li></ul><ul><li>This objective expands the existing national data model standards to provide a complete architecture for standardized national information sharing services. Part of this effort is defining a standard set of commonly used and mission critical services and their descriptions </li></ul>
  17. 17. Representative Projects <ul><li>Use Case One </li></ul><ul><ul><li>The Wyoming Criminal Justice Information System (WyCJIS) </li></ul></ul><ul><ul><li>The Pennsylvania Justice Network (JNET) </li></ul></ul><ul><ul><li>CONNECT </li></ul></ul><ul><li>Use Case Two </li></ul><ul><ul><li>Effort to perform business capabilities and process analysis and to develop service specifications for fusion centers </li></ul></ul>
  18. 18. Summary of Benefits <ul><li>Alignment with Business Drivers </li></ul><ul><li>Agility of the Information Sharing Environment </li></ul><ul><li>Cost Efficiency as Services are Being Reused </li></ul><ul><li>Reduced Risk Due to Incremental Implementation </li></ul><ul><li>Federal Funding Opportunities Associated with Conformance to Standards </li></ul>
  19. 19. Links to More Information <ul><li>The Global Justice Reference Architecture Site </li></ul><ul><li>http://it.ojp.gov/topic.jsp?topic_id=242 </li></ul><ul><li>The OASIS Reference Model for Service Oriented Architecture </li></ul><ul><li>http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf </li></ul><ul><li>The Service Oriented Architecture (SOA) Blog </li></ul><ul><li>http://it.toolbox.com/blogs/the-soa-blog/soa-benefits-challenges-and-risk-mitigation-8075 </li></ul><ul><li>Service Oriented Architecture, Thomas Erl </li></ul><ul><li>http://www.thomaserl.com/ </li></ul><ul><li>Defining SOA as an Architectural Style </li></ul><ul><li>http://www.ibm.com/developerworks/architecture/library/ar-soastyle/ </li></ul>
  20. 20. Thank You! <ul><li>Iveta Topalova </li></ul><ul><li>Analysts International </li></ul><ul><li>408-501-3705 </li></ul><ul><li>[email_address] </li></ul>

×