EA Workshop 1

2,888
-1

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,888
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
309
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The Architecture Development Method (ADM) The basic structure of the ADM consists of a number of phases, labelled A to H, that are iteratively cycled in a step-by-step process. This iterative process is important, not only repeating around the full cycle, but also between phases and within phases. As phases are undertaken and completed there is a strong emphasis on frequent validation of results against the original expectations and requirements. At the start of each full cycle of the ADM an institution should make careful decisions about the scope of the architectural work, the level of detail to be considered and the time horizons that are being taken into account. In this way, a process of architectural refnement can be implemented by repeated cycles of the phases A to H.
  • EA Workshop 1

    1. 1. Bracken Project Enterprise Architecture Workshop Sam Rowley Learning Development Manager Staffordshire University [email_address]
    2. 2. Agenda
    3. 3. What is Enterprise Architecture? <ul><li>Enterprise: </li></ul><ul><ul><li>collection of organizations with a common set of goals </li></ul></ul><ul><ul><li>e.g. </li></ul></ul><ul><ul><ul><li>cross-cutting aspect such as student records or identity management </li></ul></ul></ul><ul><ul><ul><li>department </li></ul></ul></ul><ul><ul><ul><li>faculty </li></ul></ul></ul><ul><ul><ul><li>college </li></ul></ul></ul><ul><ul><ul><li>network of institutions </li></ul></ul></ul>
    4. 4. What is Enterprise Architecture? <ul><li>Architecture: </li></ul><ul><ul><li>description of the functional aspects of an organisation </li></ul></ul><ul><ul><ul><li>people </li></ul></ul></ul><ul><ul><ul><li>processes </li></ul></ul></ul><ul><ul><ul><li>tools </li></ul></ul></ul><ul><ul><ul><li>data </li></ul></ul></ul><ul><ul><ul><li>information </li></ul></ul></ul><ul><ul><li>not IT-focussed </li></ul></ul><ul><ul><ul><li>not to be confused with IT architecture </li></ul></ul></ul>
    5. 5. What Is Enterprise Architecture? <ul><li>Enterprise Architecture </li></ul><ul><ul><li>high-level, strategic technique </li></ul></ul><ul><ul><li>designed to help senior managers achieve business and organisational change </li></ul></ul><ul><ul><li>achieving desired future change through design </li></ul></ul><ul><li>Approach </li></ul><ul><ul><li>Describe current state (‘as is’ or ‘baseline’ ) </li></ul></ul><ul><ul><li>Describe vision of intended state (‘to be’ or ‘target’) </li></ul></ul><ul><ul><ul><li>target created to satisfy business goals </li></ul></ul></ul><ul><ul><li>Use these descriptions as roadmap to guide organisational change </li></ul></ul>
    6. 6. EA Journey
    7. 7. Typical EA Lifecycle
    8. 8. Principles of EA <ul><li>EA is both </li></ul><ul><ul><li>process </li></ul></ul><ul><ul><ul><li>transition between the current state of an organisation and its future </li></ul></ul></ul><ul><ul><li>product </li></ul></ul><ul><ul><ul><li>the documented representation of the architecture </li></ul></ul></ul><ul><li>EA is as much about process as product </li></ul><ul><ul><li>‘ the journey is its own reward’ </li></ul></ul>
    9. 9. Coordination with other management frameworks
    10. 10. Benefits of EA <ul><li>Enables high level alignment between an organisation’s business processes and the underlying ICT systems </li></ul><ul><li>Facilitates clear communication between different groups of people </li></ul><ul><li>Provides a roadmap for translating business goals into changes to the business processes, day-to-day operations and ICT systems of an organisation </li></ul><ul><li>Promotes better understanding of how the business operates </li></ul><ul><li>Helps promote an ‘enterprise mindset’ </li></ul><ul><li>Enables comparison of different strategic visions for the organisation </li></ul><ul><li>Creating an EA highlights all sorts of architectural, governance and decision-making issues that need to be addressed for the betterment of the business regardless of whether EA is adopted or not </li></ul>
    11. 11. <ul><li>The Open Group Architecture Framework </li></ul><ul><li>The de facto standard EA framework </li></ul><ul><ul><li>a tool for developing a broad range of different architectures </li></ul></ul><ul><li>Provides a method for EA development </li></ul><ul><li>Best practice approach </li></ul><ul><ul><li>refined over 15 years </li></ul></ul><ul><li>Vendor and technology neutral </li></ul>
    12. 12. TOGAF
    13. 13. TOGAF Architecture Development Method (ADM)
    14. 14. ADM Phases
    15. 15. ADM Phases Getting the organisation committed and involved
    16. 16. ADM Phases Getting the architecture right
    17. 17. ADM Phases Making the architecture work
    18. 18. ADM Phases Keeping the process running
    19. 19. EA Modelling <ul><li>Capture stakeholder concerns </li></ul><ul><li>Address concerns by identifying and refining requirements </li></ul><ul><li>Create EA models </li></ul><ul><li>Create views of the model for stakeholders </li></ul><ul><ul><li>show how concerns and requirements will be addressed </li></ul></ul><ul><ul><li>show trade-offs arising from conflicting concerns </li></ul></ul>
    20. 20. <ul><li>Modelling language </li></ul><ul><li>Intuitive notation </li></ul><ul><li>Designed for high-level modelling </li></ul><ul><ul><li>‘ the big picture’ </li></ul></ul><ul><ul><li>relationships and dependencies </li></ul></ul><ul><li>Designed to bridge different domains </li></ul><ul><ul><li>UML in software development </li></ul></ul><ul><ul><li>BPMN/BPML in business process modelling </li></ul></ul><ul><li>Fits well with TOGAF </li></ul>
    21. 21. Archimate Elements
    22. 22. Element Types
    23. 23. Archimate layers
    24. 24. Business Layer
    25. 25. Application Layer
    26. 26. Technology Layer
    27. 27. Archimate Relationships
    28. 28. Putting it all together
    29. 29. Archimate vs Business Process Modelling <ul><li>Archimate higher level </li></ul><ul><ul><li>Focuses on interconnections and relations </li></ul></ul><ul><li>Link to business process maps for the process details </li></ul>
    30. 30. How to use Archimate <ul><li>Start with business layer </li></ul><ul><ul><li>process steps first </li></ul></ul><ul><ul><li>add actors and roles </li></ul></ul><ul><ul><li>add business objects </li></ul></ul><ul><li>Application layer </li></ul><ul><li>Technology layer </li></ul><ul><li>Create views from the model to fit stakeholder concerns </li></ul>
    31. 31. Real World models
    32. 32. The Archi Modelling Tool <ul><li>Open source, cross-platform tool to create  ArchiMate  models </li></ul><ul><li>Development funded by  JISC </li></ul><ul><li>Rapidly becoming the  de facto  ArchiMate modelling tool </li></ul><ul><li>...and it’s free! </li></ul>
    33. 33. Archi Demonstration
    34. 34. EA in Practice <ul><li>Small scope example - external examiners </li></ul><ul><ul><li>business process duplication </li></ul></ul><ul><li>Followed tailored TOGAF process </li></ul><ul><ul><li>only relevant scope and steps </li></ul></ul><ul><li>Process: </li></ul><ul><ul><li>Identify Stakeholders </li></ul></ul><ul><ul><li>Gather information, concerns and requirements </li></ul></ul><ul><ul><li>Create models – baseline and target </li></ul></ul><ul><ul><li>Implement solution </li></ul></ul>
    35. 35. Gathering information <ul><li>Gathering Information </li></ul><ul><ul><li>interviews </li></ul></ul><ul><ul><li>existing process maps </li></ul></ul><ul><ul><li>process descriptions </li></ul></ul><ul><ul><ul><li>e.g. quality process guidance from the Web site </li></ul></ul></ul><ul><li>Modelling sessions </li></ul><ul><ul><li>with ‘friendly’ stakeholders </li></ul></ul><ul><ul><li>avoid a blank slate </li></ul></ul><ul><ul><ul><li>come armed with a model to refine </li></ul></ul></ul><ul><ul><li>good response to Archimate </li></ul></ul><ul><ul><ul><li>stakeholders understand the meaning </li></ul></ul></ul>
    36. 36. Baseline Model - Processes
    37. 37. Actors and Roles
    38. 38. Representations
    39. 39. Business Objects
    40. 40. Other stakeholders
    41. 41. Other stakeholders
    42. 42. Other stakeholders
    43. 43. Other stakeholders
    44. 44. Baseline Model
    45. 45. Target Model
    46. 46. Gap Analysis Model
    47. 47. Summary <ul><li>Enterprise Architecture </li></ul><ul><ul><li>for understanding ‘the big picture’ </li></ul></ul><ul><ul><li>roadmap for organisational change </li></ul></ul><ul><li>TOGAF </li></ul><ul><ul><li>the method </li></ul></ul><ul><ul><li>useful toolkit/checklist </li></ul></ul><ul><li>Archimate </li></ul><ul><ul><li>the modelling language </li></ul></ul><ul><li>Archi </li></ul><ul><ul><li>the free modelling tool </li></ul></ul>
    48. 48. Getting started <ul><li>Focus on Archimate modelling first </li></ul><ul><ul><li>get into TOGAF later if required </li></ul></ul><ul><li>Download and install Archi </li></ul><ul><li>Try some modelling on a business problem </li></ul><ul><ul><li>Use other models as a guide </li></ul></ul><ul><ul><li>Read introductory Archimate documentation </li></ul></ul><ul><li>Start with business architecture layer then move down the layers (if necessary) </li></ul><ul><li>Talk with domain experts to get input into the models and gain better understanding </li></ul><ul><li>Create ‘as is’ before trying ‘to be’ </li></ul>
    49. 49. Links to further resources <ul><li>Enterprise Architecture </li></ul><ul><ul><li>JISC InfoNet Enterprise Architecture: http://www.jiscinfonet.ac.uk/flexible-service-delivery/ea </li></ul></ul><ul><ul><li>Doing EA (JISC EA Pilot case studies): www.jisc.ac.uk/media/documents/techwatch/jisc_ea_pilot_study.pdf </li></ul></ul><ul><li>TOGAF </li></ul><ul><ul><li>http://www.opengroup.org/togaf/ </li></ul></ul><ul><ul><li>TOGAF 'book': http://pubs.opengroup.org/architecture/togaf9-doc/arch/ </li></ul></ul><ul><li>Archimate </li></ul><ul><ul><li>http://www.opengroup.org/archimate </li></ul></ul><ul><ul><li>Specification: http://www.opengroup.org/archimate/doc/ts_archimate/ </li></ul></ul><ul><ul><li>Introduction: https://doc.novay.nl/dsweb/Get/Document-43839/ArchiMate_Language_Primer.pdf </li></ul></ul><ul><ul><li>Web site: http://www.archimate.org/ </li></ul></ul><ul><ul><li>Quick reference: https://doc.novay.nl/dsweb/Get/Document-52048/ </li></ul></ul><ul><ul><li>Guides: https://doc.novay.nl/dsweb/View/Collection-4766 </li></ul></ul><ul><li>Archi </li></ul><ul><ul><li>http://archi.cetis.ac.uk </li></ul></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×