• Like
  • Save
PP Two
Upcoming SlideShare
Loading in...5
×
 

PP Two

on

  • 395 views

 

Statistics

Views

Total Views
395
Views on SlideShare
395
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 2008 National Forum on Criminal Justice & Public Safety
  • To resolve the first challenge we need better alignment between business and technology To resolve the second challenge we need to design an architecture in which modifications in one component would not require modification of the integrated components - agility 2008 National Forum on Criminal Justice & Public Safety
  • Silos of Capabilities – biometric identification of an individual or creating a case Unlocking the business capabilities The applications are the existing RMS, CMS, CAD system The approach leverages the existing investments in these existing applications and allows for incremental deployment Services become composable capabilities 2008 National Forum on Criminal Justice & Public Safety
  • Since the services on which SOA relies are based on the business capabilities of an organization the alignment between business and technology is mutually beneficial and empowering. 2008 National Forum on Criminal Justice & Public Safety
  • There is a large number of justice agencies which have to share information in order to prevent or respond to crime and/or hazards These agencies have a large number variety of systems and applications The systems and applications have their own way of storing and interpreting data and thus speak different languages The systems and applications use a variety of ways of protecting the data and thus have different user groups and authentication and authorization mechanisms. As a result it is a challenge to establish exchange of information (you can think of it as conversation). The systems and applications are developed using a variety of technologies and as a result there is additional development required to enable the exchange of information.  As a result if there is no standardization each exchange is different and developed as an one off.
  • There is a large number of justice agencies which have to share information in order to prevent or respond to crime and/or hazards These agencies have a large number variety of systems and applications The systems and applications have their own way of storing and interpreting data and thus speak different languages The systems and applications use a variety of ways of protecting the data and thus have different user groups and authentication and authorization mechanisms. As a result it is a challenge to establish exchange of information (you can think of it as conversation). The systems and applications are developed using a variety of technologies and as a result there is additional development required to enable the exchange of information.  As a result if there is no standardization each exchange is different and developed as an one off.
  • 2008 National Forum on Criminal Justice & Public Safety
  • The JNET has accepted and continues to migrate towards a service oriented approach.  In doing so, JNET has implemented technology consistent with this philosophy.  Just as importantly JNET’s governance model, while not documented, has proceeded with considerable discipline.   The JRA material is very familiar to JNET.  JNET coincidently has moved in a manner similar to that outlined in Guideline for Identifying and Designing Services. We define services similarly.  Many of the traits of the service design principles are illustrated in the JNET methodology:  reuse, composable, autonomous, cohesiveness and discoverable.   The JRA “Service Identification Methodology” is very similar to the process employed here at JNET.  There are strong similarities in the process in outlining the inventory of services candidates (JNET has currently has 44 services outlined using this methodology).  The identification of services as discussed in the Guideline is very consistent to the actual live process followed by JNET.    The drivers and business considerations were reasons these services made the inventory list but they were also instrumental in deriving our list of 12 services priorities.  To help management with the prioritization process we spend a considerable amount of time on a process that contained all or most of the elements in the JRA cycle including: interdependency analysis, interdependency resolution, business value and architectural validation.   All in all, JNET has applied good business sense in their best practices.  The use of Global materials is a key in these best practices 2008 National Forum on Criminal Justice & Public Safety

PP Two PP Two Presentation Transcript

  • Service Oriented Architecture (SOA) Application in Justice Information Sharing
  • Enterprise Architecture Challenges
    • 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?
    • How can I build an architecture that could respond to future changes without significant modifications?
  • 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
  • Alignment Makes a Difference Today
    • SOA is a bridge that creates a symbiotic and synergistic relationship between the business and the technology world.
    • This relationship is more effective, powerful and valuable than anything experienced in the past.
    • The immediate result is achieving business process quality with the help of technology.
  • Agility is the Promise of the Future
    • The resulting architecture will evolve effectively and efficiently as the underlying business processes change.
    • Estimated reduction of information technology expenses in the long term by as much as 20%. *
    • Savings become exponential over time as the library of business services expand and greater degree of reuse is achieved.
    * Based on Gartner’s estimate
  • Silos of Justice and Public Safety Information
    • 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.
  • The Interoperability Challenge
      • There are approximately 100,000 autonomous agencies that have a critical need to share information across their various information systems.
      • This variety creates multiple layers of interoperability problems because hardware, software, networks, and business rules for data exchange are different.
  • 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
  • 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
  • The Role of Architecture
      • Minimize the dependencies between integrated information systems.
      • Favor technologies that leverage open industry standards .
      • Promote the treatment of integration interfaces as sharable and reusable enterprise assets .
  • The Result is Effective and Efficient Information Sharing
    • 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.
  • The Justice Reference Architecture (JRA)
    • A Reference Architecture provides a proven template solution and a common vocabulary with which to discuss implementations, often with the aim to stress commonality.
    • The Justice Reference Architecture is:
      • Developed specifically for the Justice domain and focuses on information sharing in a complex multi-jurisdictional environment.
      • Leverages the best practices of industry and specifically the OASIS Reference Model for SOA.
      • Continuous effort to maintain consistency with other architecture initiatives.
  • Mission, Vision and Audience
    • Mission: To enhance justice and public safety through a service-oriented approach to information sharing.
    • 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.
    • 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.
  • Architecture Principles
    • Independence of Information Sharing Partners
    • Scalability to Allow Incremental Implementation
    • Diversity of Data Source Architectures
    • Long Term Agility
    • Reuse and Sharing of Assets
    • Alignment with Best Practices and Experience
  • The Two Main Use Cases
    • Use Case One: To provide a starting point for local information sharing architectures
    • 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.
    • Use Case Two: To provide a national architecture for information sharing services
    • 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
  • Representative Projects
    • Use Case One
      • The Wyoming Criminal Justice Information System (WyCJIS)
      • The Pennsylvania Justice Network (JNET)
      • CONNECT
    • Use Case Two
      • Effort to perform business capabilities and process analysis and to develop service specifications for fusion centers
  • Summary of Benefits
    • Alignment with Business Drivers
    • Agility of the Information Sharing Environment
    • Cost Efficiency as Services are Being Reused
    • Reduced Risk Due to Incremental Implementation
    • Federal Funding Opportunities Associated with Conformance to Standards
  • Links to More Information
    • The Global Justice Reference Architecture Site
    • http://it.ojp.gov/topic.jsp?topic_id=242
    • The OASIS Reference Model for Service Oriented Architecture
    • http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf
    • The Service Oriented Architecture (SOA) Blog
    • http://it.toolbox.com/blogs/the-soa-blog/soa-benefits-challenges-and-risk-mitigation-8075
    • Service Oriented Architecture, Thomas Erl
    • http://www.thomaserl.com/
    • Defining SOA as an Architectural Style
    • http://www.ibm.com/developerworks/architecture/library/ar-soastyle/
  • Thank You!
    • Iveta Topalova
    • Analysts International
    • 408-501-3705
    • [email_address]