1 / 18

Information System Architectures and Services

Information System Architectures and Services. The architecture is the relationship of the components of the information system. One useful framework is the Model-View-Controller (MVC). Architectures.

asabi
Télécharger la présentation

Information System Architectures and Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information System Architectures and Services CC 2007, 2011 attribution - R.B. Allen

  2. The architecture is the relationship of the components of the information system. One useful framework is the Model-View-Controller (MVC) Architectures CC 2007, 2011 attribution - R.B. Allen

  3. There’s additional complexity when the components of the information system are distributed across several machines in a network. Some approaches for managing complexity: Layering Modularity Interoperability Managing Complexity withDistributed Systems CC 2007, 2011 attribution - R.B. Allen

  4. It’s helpful to define complex information systems in terms of the services they provide. We would like to work with architectures which make it easy to implement services. This turns out to fit well with systems analysis and object-oriented design In research environments, this is often implemented with java apache “tomcat” web server Repositories are content management systems which support services. Digital Libraries, Enterprise Content Management Systems, and Archives can all use repositories. Service Oriented Architectures (SOA) CC 2007, 2011 attribution - R.B. Allen

  5. Importance of information managementin society is shown by the fact that many societal institutions deal with the use of information Memory institutions, Cultural Institutions, Knowledge Institutions Libraries, Archives, Museums, Universities Trusted information professionals Librarians, Archivists, Journalists, Notaries To what extent can technology replace trusted humans? Information Institutions CC 2007, 2011 attribution - R.B. Allen

  6. A library needs to support collection management and content access. This functions (services) can be summarized with the acronym: Selection Deciding what should be included Organization Metadata A Access Easy to use. Also support reference and collaboration Persistence Continuity and Preservation Libraries CC 2007, 2011 attribution - R.B. Allen

  7. Archives typically collect material for which there’s only one copy: Manuscripts, letters, personal notes Archives emphasize persistence of content. The repository should be trusted. That is, we should have confidence that the contents of have not been tampered with. The Open Archival Information Systems (OAIS) Reference Model describes the generic components of an archive Archives CC 2007, 2011 attribution - R.B. Allen

  8. Unlike traditional media, digital media are ephemeral. Even if we it saving it is not easy: The ability to read the message format and character codes may change It may not be possible to access the storage media hardware. If the material is interactive, we need to save that interactivity. The best bet is to use standard formats. Digital Preservation CC 2007, 2011 attribution - R.B. Allen

  9. If there aren’t any copies, digital media is gone when it’s deleted It’s easy to make copies, but we have to keep track of them. Furthermore, the copies can tell whether somebody has tampered with the original. LOCKSS is a framework for ensuring managing this. LOCKSS:Lots of Copies Keeps Stuff Safe CC 2007, 2011 attribution - R.B. Allen

  10. What policies should we develop for managing the knowledge resources of an organization? For instance, What books, databases, and periodicals should be available? Use thesauri to organize content. Knowledge Management CC 2007, 2011 attribution - R.B. Allen

  11. The information is more important than the medium Records document transactions. Birth, marriage death, real estate, etc. Records management: Records need to be trusted. Not all materials (e.g., emails need to be saved) Some records can be deleted when they have outlived their lifespan. Electronic Records CC 2007, 2011 attribution - R.B. Allen

  12. Usually based on flow through an organization rather than hierarchical control. Rather than focus on hierarchical structure, focus on flow across the organization Organizations have social constraints Procedures can’t be over constrained Business Process Design CC 2007, 2011 attribution - R.B. Allen

  13. System analysis with UML (week 3) Stakeholders? Requirements. Information System Specification, Development, and Implementation CC 2007, 2011 attribution - R.B. Allen

  14. These are such complex systems that figuring out what is needed is not easy. Functional requirements Requirements Modeling Requirements CC 2007, 2011 attribution - R.B. Allen

  15. Can we specify all parameters in requirements Lots of testing Agile System Development CC 2007, 2011 attribution - R.B. Allen

  16. What makes an effective information system? Metrics System Management and Evaluation CC 2007, 2011 attribution - R.B. Allen

  17. There are many types of risk, how can we understand them and defend against them? What’s the chance that records could be lost? Attacked and corrupted? Risk Analysis andRisk Management CC 2007, 2011 attribution - R.B. Allen

  18. Analyzing risks to security Human elements vs technical issues. Encryption DES – Digital Encryption Standard Public Key Encryption Key Distribution Security and Encryption CC 2007, 2011 attribution - R.B. Allen

More Related