Information management


Published on

Example of combining methodologies to architect a complex IT solution.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Information management

  1. 1. We are all trying to do this
  2. 2. Information Management AIIM has a nice layman’s definition  Capture  Store  Manage  Preserve  Deliver This happens when we are talking and listening or when we are trying to manage Petabytes There is a lot more behind the next slide
  3. 3. Cloud Platform (thank you Gartner) Turnkey Service (sounds like SOA) Elastic (scalable) Shared Environment (multi-tenant) Pay for what you use (have to track usage stats) Use standard protocols (HTTP/HTTPS) Like an electric utility, just use it and pay the bill
  4. 4. 3 Levels of Cloud Service IAAS  Bare-bones VM capacity PAAS  Software development tools to create and run applications SAAS  Out-of-the-box software solutions accessed through a front-end portal
  5. 5. Cloud Types Public cloud  Resource dynamically provisioned on a self-serve basis via the web from an off-site 3rd party provider who shares resources and bills clients Private cloud  Installations that emulate many aspects of public cloud computing but do so on a completely secure private network Hybrid cloud  Some resource in-house and others managed externally
  6. 6. IBM View Example
  7. 7. IBM Smart Analytics Cloud
  8. 8. Enterprise Services “Enterprise services architecture emphasizes abstraction and componentization, which provides a mechanism for employing both the required internal and external business standards. The main goal of enterprise services architecture is to create an IT environment in which standardized components can aggregate and work together to reduce complexity. To create reusable and useful components, it is equally important to build an infrastructure allowing components to conform to the changing needs of the environment.” - Techopedia In other words, “loosely coupled” services that perform specific tasks, can be easily inserted, updated or replaced  The services may be “course-grained” or “fine-grained”. Course-grained is what the business sees, fine-grained can be reused by the course-grained.
  9. 9. Enterprise ArchitectureMaturity Model 4 stages  Application silo  Standardized Technology  Rationalized Data  Modular From MIT Sloan School of Management Center for Information Systems Research
  10. 10. From MIT Sloan School of ManagementCenter for Information Systems Research
  11. 11. Business Operating Models From MIT Sloan School of Management Center for Information Systems Research
  12. 12. SOA Governance Example
  13. 13. Implementing Enterprise Services Implementing enterprise services starts not with technology but with the business requirements. What enterprise services does the business need?  Reporting  Analytics  Process management  Predictive analytics  Messaging and routing  Data translation
  14. 14. Example Hadoop + Analytics
  15. 15. Defining Architectures Network Server Application Data Transformation Security Event and event handling ESB and adapters
  16. 16. Business and Ops Support Plan for support of multi-tenant environment  Tools to capture usage statistics Plan for proactive operational support  Tools for monitoring all aspects of the solution
  17. 17. Methodology Two Paths in Parallel  Business  Gather high-level requirements  Functional  Non functional  Technical  Identify technology platforms and components  Design architectures  Design end-to-end proof-of-concept Crawl, walk, run
  18. 18. Methodology Architectural blueprinting  Work in progress through project phases Define a multi-phase project management strategy  Look for small wins first
  19. 19. Architecture Blueprints Graphical representation of the business view of data, functions, technology, people and the relationship and/or interactions between them Set the context Set ground rules for modeling Determine modeling levels of detail
  20. 20. Architecture Blueprints –Set the context Who is the audience? What level of detail do they need to see? What will the content include?  Data, functions, technology, people?  Communications layers?  Sequence, flow? What planning horizon will be used? What part of IT does the architecture need to describe?
  21. 21. Architecture Blueprints –Ground Rules Agree on a set of standard components Use a standard representation scheme Set a scope Determine the level of detail  Level 0 – conceptual, one page  Level 1 – More detailed, specific  Level N – Most detailed, form the bridge from architecture to development Define the state to be modeled (current, target) Define the environment (prod, dev, ops)
  22. 22. Project Summary Capture data from many sources in many formats Route data to data warehouse using ESB Utilize Analytics and/or BI platform on data