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