Enterprise Implementation With Sa And Tau


Published on

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
  • Enterprise Implementation With Sa And Tau

    1. 1. Enterprise Implementation System Architect and Tau working together
    2. 2. The Workflow Driven Environment Develop enterprise architecture Analyze & optimize business strategies Deploy & maintain Design services & applications Business requirements User requirements System requirements Trace and analyze relationships
    3. 3. Defense Workflow Develop defense architecture Analyze & optimize operations strategies Deploy & maintain Design services & applications Program requirements Project requirements System requirements Trace and analyze relationships
    4. 4. The IBM Solution Develop enterprise architecture Analyze & optimize business strategies Deploy & maintain Design services & applications Business requirements User requirements System requirements Trace and analyze relationships System Architect Tau DOORS Common Repository
    5. 5. Telelogic Tau ® - Model-Driven Development for Complex IT <ul><li>Capabilities </li></ul><ul><li>Develop systems and applications using UML 2.1, SysML, MDA, SOA, and DoDAF </li></ul><ul><li>Prove systems design by simulating and testing as you develop </li></ul><ul><li>Provide requirements-driven round-trip code support for Java, C++, C#, C </li></ul><ul><li>Benefits </li></ul><ul><li>Deliver on time and on budget by finding design errors as they occur </li></ul><ul><li>Satisfy regulatory requirements by maintaining complete audit and development trails </li></ul><ul><li>Keep large, diverse teams in sync with powerful collaboration features </li></ul>“ Tau enables our architects, systems engineers, and software developers to improve the development process. We can use a single tool for analysis, design, and auto code generation . ” - Nigel Bartlett, Director of Wireless Communications Software, Hughes Network Systems
    6. 6. Tau Vision <ul><li>Model-Driven SOA </li></ul><ul><ul><li>Leverage global resources </li></ul></ul><ul><ul><li>Streamline infrastructure </li></ul></ul><ul><li>Large, complex, and distributed systems </li></ul><ul><ul><li>Developed by large, distributed teams </li></ul></ul><ul><li>Application design and development </li></ul><ul><ul><li>Information systems and software </li></ul></ul><ul><ul><li>Loosely-coupled and real-time </li></ul></ul>
    7. 7. Tau for Model-Driven SOA <ul><li>Satisfy business requirements </li></ul><ul><ul><li>Design applications that directly tie to the business plan </li></ul></ul><ul><li>Tame complexity </li></ul><ul><ul><li>Visually analyse, design and assemble service architectures </li></ul></ul><ul><ul><li>Provide a single SOA repository </li></ul></ul><ul><li>Gain understanding </li></ul><ul><ul><li>Visualize and import code, WSDL, XSD… </li></ul></ul><ul><li>Adapt legacy services </li></ul><ul><ul><li>Apply round-trip engineering </li></ul></ul><ul><ul><li>Generate WSDL and XSD </li></ul></ul><ul><li>Ensure correctness </li></ul><ul><ul><li>Simulate and test your logic before any code is written!! </li></ul></ul><ul><li>Enable reuse </li></ul><ul><ul><li>Keep designs abstract to extend their life </li></ul></ul>
    8. 8. Enterprise Architecture through Implementation System Architect  Tau <ul><li>Bi-directional modeling link between business and IT </li></ul><ul><ul><li>Common UML 2.1 support across both products </li></ul></ul><ul><ul><li>Shared repository enables Tau and System Architect users to read/write/visualize from either environment with no data loss </li></ul></ul><ul><ul><li>Predefined mappings automate the conversion of models, frameworks and formats between different users </li></ul></ul><ul><li>Seamless workflow : </li></ul><ul><ul><li>Enterprise architecture  business process analysis  application modeling and development </li></ul></ul><ul><ul><li>Defense architecture  operations planning  systems and software modeling and development </li></ul></ul><ul><li>Share models and data across the organization without forced expertise in other modeling domains </li></ul><ul><li>Maintain complete traceability through full DOORS integration </li></ul>
    9. 9. Enterprise Workflow
    10. 10. <ul><li>Model the key domains and their relationships: </li></ul><ul><ul><li>Business, Strategy, Applications, Infrastructure, Data </li></ul></ul><ul><li>Relate to the overall service infrastructure and its elements </li></ul>Modeling the Enterprise Architecture Network Concept Diagram Application Architecture Business Process Diagram Enterprise Direction Diagram Service Collaboration Diagram
    11. 11. Business Analysis & Planning <ul><li>Map business objectives and goals </li></ul><ul><ul><li>establish scope </li></ul></ul><ul><li>Understand the existing business in terms of: </li></ul><ul><ul><li>people </li></ul></ul><ul><ul><li>processes </li></ul></ul><ul><ul><li>applications </li></ul></ul><ul><ul><li>information </li></ul></ul><ul><ul><li>services </li></ul></ul><ul><li>Plan changes in line with objectives and goals </li></ul><ul><ul><li>roadmaps </li></ul></ul><ul><li>Develop and maintain business architecture </li></ul>Business Services Deployment Platform Enterprise Architecture guidance accountability Design services Implement services Integrate services Test services Scope business Analyze organization Identify services Plan roadmaps
    12. 12. Deployment Analysis <ul><li>Provide the enterprise view of the project </li></ul><ul><ul><li>Show how business operates today </li></ul></ul><ul><ul><li>Explore how new services are going to fit into the organization </li></ul></ul><ul><ul><li>Perform impact analysis on removal or change of existing services </li></ul></ul><ul><li>Business and IT can see the service plan for any implementation </li></ul><ul><ul><li>Identify candidates for reuse </li></ul></ul><ul><ul><li>Perform analysis to determine characteristics of desired future state architectures </li></ul></ul>
    13. 13. Project Architecture Analysis and Design <ul><li>Start from the business needs from System Architect </li></ul><ul><ul><li>Capture understanding of the overall purpose for development </li></ul></ul><ul><li>Visualize the significant participants and their use cases </li></ul><ul><li>Determine what is involved in meeting their needs </li></ul><ul><li>Simulate and test as a whole </li></ul><ul><li>Maintain full traceability </li></ul>
    14. 14. Systems & Application Development <ul><li>Analyze the model to determine overall impact </li></ul><ul><li>Split the project up into manageable components </li></ul><ul><ul><li>Treat each component as a standalone model </li></ul></ul><ul><li>Simulate and test to verify that each component is correct </li></ul><ul><li>Recombine components in real-time </li></ul><ul><li>Extract documents and reports from the model </li></ul><ul><ul><li>Can be updated automatically by extracting the information again </li></ul></ul>
    15. 15. Software Development <ul><li>Analyze to determine missing application components </li></ul><ul><ul><li>Buy or make? </li></ul></ul><ul><li>Extract design data to define component architecture </li></ul><ul><li>Add platform details for deployment </li></ul><ul><li>Round-trip engineer deployable software </li></ul><ul><ul><li>Integrate with Eclipse and Visual Studio IDEs </li></ul></ul><ul><ul><li>Java, C# or C++ source code </li></ul></ul><ul><ul><li>WSDL and XSD interfaces </li></ul></ul><ul><ul><li>J2EE, Java EE 5, Java SE 6, .NET platforms </li></ul></ul>
    16. 16. Encouraging Reuse <ul><li>Reuse brings major advantages </li></ul><ul><ul><li>Reduces effort </li></ul></ul><ul><ul><li>Reduces risk – zero impact on quality </li></ul></ul><ul><ul><li>Speeds delivery </li></ul></ul><ul><li>Re-use existing information in the IT landscape </li></ul><ul><ul><li>Import existing services (WSDL, XSD, source code) </li></ul></ul><ul><ul><li>Import other data (XML, XMI, CSV, libraries,…) </li></ul></ul><ul><li>Reuse within the service Architecture </li></ul><ul><ul><li>Search for existing services (harvesting) </li></ul></ul><ul><ul><li>Design new services with reuse in mind </li></ul></ul>
    17. 17. Collaboration <ul><li>Divide and govern large projects </li></ul><ul><ul><li>Logically separate project models </li></ul></ul><ul><ul><li>Develop and deliver specifications and interface information (WSDL, XSD, XML…) </li></ul></ul><ul><ul><li>Powerful compare/merge </li></ul></ul><ul><li>Speak the same language </li></ul><ul><ul><li>Common basis for specifying and enforcing compliance </li></ul></ul><ul><ul><li>Gain acceptance at each stage through shared models </li></ul></ul><ul><li>Keep teams fully accountable </li></ul><ul><ul><li>Traceability ensures accurate reporting </li></ul></ul><ul><ul><li>Prove designs against the original requirements </li></ul></ul>
    18. 18. Round Trip Traceability - The Audit Trail business requirements user requirements system requirements business processes service design
    19. 19. Summary <ul><li>System Architect and Tau enable you to Implement your Enterprise Architecture </li></ul><ul><ul><li>Visually analyse, design and assemble service architectures as part of an enterprise strategy </li></ul></ul><ul><ul><li>Provide a single SOA repository </li></ul></ul><ul><ul><li>Simulate and test your logic before any code is written!! </li></ul></ul><ul><ul><li>Promote reuse </li></ul></ul><ul><ul><li>Ensure correctness </li></ul></ul><ul><ul><li>Extend design life by keeping it abstract </li></ul></ul><ul><ul><li>Visualize, import and generate WSDL and XSD </li></ul></ul><ul><ul><li>Adapt legacy services </li></ul></ul><ul><ul><li>Design new services as needed </li></ul></ul>
    20. 20. Thank You & Questions