Course Description. Course Audience. Course Outline. Course Page - Page 1 of 14

Similar documents
Sparx Systems Enterprise Architect for Team Players

SOMA, RUP and RMC: the right combination for Service Oriented Architecture

Sparx Enterprise Architect for Business Analysts

What is a life cycle model?

Chap 1. Introduction to Software Architecture

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK

California Enterprise Architecture Framework

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

Appendix 2-A. Application and System Development Requirements

Architecture. Reda Bendraou

Developing SOA solutions using IBM SOA Foundation

Software Design Document (SDD) Template

A Comparison of SOA Methodologies Analysis & Design Phases

Applying 4+1 View Architecture with UML 2. White Paper

SOA + BPM = Agile Integrated Tax Systems. Hemant Sharma CTO, State and Local Government

The Role of the Software Architect

Software Development in the Large!

Federal Enterprise Architecture and Service-Oriented Architecture

Object-Oriented Systems Analysis and Design

Aerospace Software Engineering

Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions

Service Oriented Architecture (SOA) Architecture, Governance, Standards and Technologies

Karunya University Dept. of Information Technology

Requirements Management Practice Description

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led

Requirements engineering

Engineering Design. Software. Theory and Practice. Carlos E. Otero. CRC Press. Taylor & Francis Croup. Taylor St Francis Croup, an Informa business

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED BUSINESS INTEGRATION MODEL LANGUAGE SPECIFICATIONS

Requirements engineering and quality attributes

Software Architecture. New wine in old bottles? (i.e., software architecture global design?, architect designer)

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS

Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture

A UML Introduction Tutorial

Definition: Software Architecture

SOA and BPO SOA orchestration with flow. Jason Huggins Subject Matter Expert - Uniface

A Software Development Platform for SOA

Business-Driven Software Engineering Lecture 3 Foundations of Processes

Service Oriented Architecture

In this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?

White Paper What Solutions Architects Should Know About The TOGAF ADM

Enhanced Funding Requirements: Seven Conditions and Standards

Service Oriented Architecture and the DBA Kathy Komer Aetna Inc. New England DB2 Users Group. Tuesday June 12 1:00-2:15

SOA: The missing link between Enterprise Architecture and Solution Architecture

Service Oriented Architecture 1 COMPILED BY BJ

Module F13 The TOGAF Certification for People Program

Web Application Architectures

ArchiMate and TOGAF. What is the added value?

ITIL Service Lifecycles and the Project Manager

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal

Software Architecture Professional Certificate

Software Engineering Question Bank

Government's Adoption of SOA and SOA Examples

Applying Business Architecture to the Cloud

Advancing Your Business Analysis Career Intermediate and Senior Role Descriptions

Enterprise Architecture Glossary by Set

Developing Business Architecture with TOGAF

Protect Your Organization With the Certification That Maps to a Master s-level Education in Software Assurance

Approach to Service Management

Cloud Computing for Architects

RUP Design. Purpose of Analysis & Design. Analysis & Design Workflow. Define Candidate Architecture. Create Initial Architecture Sketch

VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur

The Rap on RUP : An Introduction to the Rational Unified Process

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED DISCOVERY AND ANALYSIS MODEL LANGUAGE SPECIFICATIONS

Plan-Driven Methodologies

(BA122) Software Engineer s Workshop (SEW)

Logical Data Models for Cloud Computing Architectures

Design Specification for IEEE Std 1471 Recommended Practice for Architectural Description IEEE Architecture Working Group 0 Motivation

Development of Enterprise Architecture of PPDR Organisations W. Müller, F. Reinert

Enterprise Test Management Standards

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED CONCEPTUALIZATION MODEL LANGUAGE SPECIFICATIONS

Data Modeling Basics

SOA Adoption Challenges

Guiding Principles for Modeling and Designing Reusable Services

Chapter 15. Web services development lifecycle

Service Oriented Architecture

Reaching CMM Levels 2 and 3 with the Rational Unified Process

How To Understand The Software Development Lifecycle

Designing an Enterprise Application Framework for Service-Oriented Architecture 1

Business Process Modeling with Structured Scenarios

3SL. Requirements Definition and Management Using Cradle

A Survey of Service Oriented Development Methodologies

How To Develop An Enterprise Architecture

Software Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: (Computer Programming 2).

Independent Insight for Service Oriented Practice. An SOA Roadmap. John C. Butler Chief Architect. A CBDI Partner Company.

ITS Projects Systems Engineering Process Compliance Checklist

US Department of Education Federal Student Aid Integration Leadership Support Contractor January 25, 2007

Program Lifecycle Methodology Version 1.7

Agile Modeling and Design of Service-Oriented Component Architecture

Designing Real-Time and Embedded Systems with the COMET/UML method

TOGAF usage in outsourcing of software development

Microsoft SOA Roadmap

Platform Autonomous Custom Scalable Service using Service Oriented Cloud Computing Architecture

11 Tips to make the requirements definition process more effective and results more usable

QUality Assessment of System ARchitectures (QUASAR)

Architecture Centric Development in Software Product Lines

Software Requirements, Third Edition

A Quick Chat about SOMF Capabilities Page1 Service-Oriented Modeling Framework (SOMF) Building Attribution Models

Frank Tsui. Orlando Karam. Barbara Bernal. State. University. Polytechnic. Ail of Southern JONES & BARTLETT LEARNING

VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0

Transcription:

Course Page - Page 1 of 14 Solution Architecture Training: SA Practitioner's Guide (Extended) BSP-2325 Length: 4 days Price: $ 2,995.00 Course Description The course covers stakeholder identification, including identifying the stakeholder viewpoints. It covers the concept of architecturally significant that drives the architecture artifacts, including system process models, system use cases, change cases, and architecture requirements. The course material and techniques are based on industry best practices such as 4+1 architecture, business-driven architecture, and requirements-driven architecture. The course includes handson labs related to core architecture skills such as developing non-functional requirements, developing architecture views, using architecture patterns, and performing architecture reviews. Course Audience Solution Architects new to SA. Course Outline CHAPTER 1 - INTRODUCTION Introductions Course Outline Handouts & Appendices Practical Application: Building Skills Practical Application: Filling Your Toolbox Course Evaluation & Questions Course Delivery Overview CHAPTER 2 - SOLUTION A RCHITECTURE OVERVIEW Why is Solution Architecture Important? Communications Vehicle Among Stakeholders The Project is Organized Around Architectural Elements

Course Page - Page 2 of 14 What is a System? Why Focus on Structure? Solution Architecture Context Solution Architecture & Domains SA Spans All Domains Relationship to EA Architecture Development Process Solution Architecture Example: Solution Architecture Stakeholders Solution Architecture Deliverables EA Involvement in SA Architecturally Significant Group Discussion: Architecture Resource: Software Engineering Institute (SEI) Resource: SWEBOK Resource: OpenUp Resource: Microsoft Library Group Discussion: Methodologies CHAPTER 3 - CORE SOLUTION ARCHITECTURE METHODS Shared Vision Example Shared Vision Draw the Boundary Well-defined Interface Example: Context Diagram Identify the External Interfaces Subsystems Subsystem Context Diagram Layers Example: Subsystems with Layers Components Decomposing the System Partitioning Patterns Example Partitioning Based on Patterns Example: Healthcare SOA Framework Requirements Allocation Group Discussion: Requirements Allocation Configuration Management Implications Release Management Implications Testing Implications Work Pattern & Skill Set Implications Work & Build Dependencies Increment/Sprint Planning Sizing Implications More Than Executable Architecture

Course Page - Page 3 of 14 Development Architecture Operations Architecture Group Discussion: Integrating Operations Architecture CHAPTER 4 - REFERENCE ARCHITECTURE Reference Architecture Reference Architecture Components Reference Architecture Summarized Reference Architecture Context Architecture Principles Components of Principles Qualities of a Good Set of Principles Templates: Principle & Principle Catalog Example: Architecture Principles Sample: Architecture Principles Group Discussion: Principles Applying Architecture Principles Policies Template: Policy Example: Governance Policies Example: SOA Policy Example: Policies Reference Models Example: Reference Model Example: Architecture Use Cases Example: SOA Reference Architecture Practices: Standards & Guidelines Example: Interoperability Standards Resource: Financial Industry Organizations Resource: Health Industry Organizations Resource: Retail Industry Organizations Resource: Technical Organizations Industry Organizations Insurance Industry Standards ROI Requirements Example: Mobile Security Reference Architecture Example: MSRA Requirements Architecture Building Blocks: Reusable Requirement Sets Resource: NIST Security Requirements Example: COTS Standard Requirements Set CHAPTER 5 - STAKEHOLDER MANAGEMENT

Course Page - Page 4 of 14 Stakeholders Stakeholder Management When to Focus on Stakeholder Management Steps in the Stakeholder Management Process Identifying Stakeholders Points to Consider Example Stakeholders & Concerns Classifying Their Positions: The Stakeholder Matrix Determining the Stakeholder Management Approach and Tailoring the Deliverables: The Stakeholder Map Example: Stakeholder Map Template: Stakeholder Map Matrix Template CHAPTER 6 - ARCHITECTURE REQUIREMENTS Architecture Quality Attributes Quality of Service Requirement Categories Checklist: Quality Attribute (QA) Categories Trade-off Analysis Group Discussion: Trade-offs Technique: Requirement Patterns Tool: Non-Functional Requirement Patterns Checklist: Requirement Statement Best Practices Technique: Architecture Change Cases Template: Elements of a Change Case Example: Change Case Eliciting Change Cases Group Discussion: Change Case CHAPTER 7 - QUALITY OF SERVICE (QOS) REQUIREMENTS Qualities of Service and Design Performance: Requirements Performance: Response Time Pattern Performance: Transaction Time Patterns Performance: Throughput Pattern Scalability Scalability: Capacity Patterns Reliability & Availability Mean Time Between Failures (MTBF) Availability: Pattern Extensibility Maintainability Manageability

Course Page - Page 5 of 14 Security Cultural Adaptability Portability Testability Usability Upgradeability Recoverability Recovery Time Objective (RTO) Recovery Point Objective (RPO) Prioritizing Quality of Service Requirements Inspecting QoS Requirements for Trade-off Opportunities Quality of Service Testing CHAPTER 8 - ARCHITECTURE TACTICS Tactics Availability Tactics Modifiability Tactics Performance Tactics Security Tactics Testability Tactics Usability Tactics Approach for Describing Tactics Group Discussion: Tactics Pipes & Filters: Tactics Service-Oriented Architecture (SOA): Tactics Architectural Patterns and Corresponding Tactics for Modifiability CHAPTER 9 - PATTERNS What are Patterns? Elements of a Pattern Pattern Levels Pattern Types How to Start Using Patterns? Common Architectural Patterns Layers Pattern Example: Retail Layered Architecture Object-Oriented Design Patterns OO Design Patterns Structural Design Pattern: Facade Pattern Example Enterprise Integration Patterns Messaging Systems: Overview Example Pattern: Pipes and Filters Example: Monitoring Credit Bureau

Course Page - Page 6 of 14 EAA Patterns Model-View-Controller (MVC) Pattern SOA Patterns Example: Saga Pattern Business Process Patterns Example: Synchronizing Merge Pattern Configuration Management Patterns New Patterns Continue to Emerge Group Discussion: Patterns CHAPTER 10 - SOLUTION ARCHITECTURE STYLES Message Oriented Middleware (MOM) MOM Messaging MOM Qualities Publish/Subscribe Messaging Point-to-Point Messaging (P2P) MOM Related Standards MOM Example Service Oriented Architecture (SOA) Enterprise Model SOA Interaction Model SOA Characteristics Enterprise Service Bus (ESB) Web Services SOA Standards Organizations SOA Example SOA Example: Illustrated CHAPTER 11 - ARCHITECTURE REQUIREMENT TECHNIQUES Requirements Management Requirements Management Activities Best Practices Baselining Requirements Desirable RM Repository Characteristics Example: Behavior Driven Development Why Traceability? Identifying Candidate Tactics, Patterns and Styles Requirements-Tactics-Patterns-Styles Making Architectural Decisions Architectural Measurement Implementing Architectural Measurement Example Metrics

Course Page - Page 7 of 14 CHAPTER 12 - VIEWS & VIEWPOINTS Views and Viewpoints Views Example View: Claim Handling from a Process Viewpoint Example View: Claim Handling from a Data Viewpoint Example View: Claim Handling Project from a Financial Viewpoint Contents of Views and Viewpoints Example Formal Viewpoint: Security Software Architecture Viewpoints: 4+1 Group Discussion: Viewpoints CHAPTER 13 - ARCHITECTURE CONCEPTS Fundamental Architecture Concepts Abstraction Coupling Cohesion Decomposition & Modularization Encapsulation & Information Hiding Separation of Interface & Implementation CHAPTER 14 - ARCHITECTURE DELIVERABLES Documentation Best Practices Architecture Requirements Document Template: Requirements Specification IEEE Architectural Description Document Template: Architectural Description Document TOGAF Architecture Definition Document Templates: Architectural Definition Document Group Discussion: Architecture Definition Documents Interface Specifications Interface Specification Best Practices Interface Design Document Template: Interface Design Document Database Design Document Template: Database Design Document Platform Design Document Template: Platform Design Document Architecture Decision Document Template: Architecture Decision Document

Course Page - Page 8 of 14 ATAM: Scenario-based Architecture Review Example: Utility Tree Presentation Best Practices: ICEPAC Verbal Supports: CREST Group Discussion: Presentations CHAPTER 15 - BUSINESS ARCHITECTURE Business Architecture Models & Diagrams Business Process Concepts Example: Medicaid Business Process Model Example: Medicaid Business Process Definition Business Function Concepts Example: HL7 EHR Functional Model Example: Process Flow Diagram Resource: Business Analysis Book of Knowledge (BABOK) Resource: Business Architecture Body of Knowledge (BIZBOK ) CHAPTER 16 - DATA ARCHITECTURE Data Modeling Conceptual Data Model Example: Conceptual Data Model Example: Property & Casualty Conceptual Data Model Example: Data Entities Logical Data Model Normalization Abstraction Example: Logical Data Model Physical Data Model Example: Physical Data Model Data Modeling Notation Entity Relationship Diagram (ERD) Cardinality Annotated Relationships Subtype Relationship Resource: DAMA DMBOK CHAPTER 17 - APPLICATION ARCHITECTURE The 4+1 Views Approach Take a Multiple View Approach UML: Unified Modeling Language

Course Page - Page 9 of 14 UML Notation Examples Use Case View Logical View Process Views Implementation View Deployment View CHAPTER 18 - TECHNICAL ARCHITECTURE What is Technical Architecture? Two Components of Technical Architecture Software Architecture What a Technical Architecture is Not Architectural Views Rational Unified Process (RUP) 4 + 1 Views The Implementation View The Deployment View Technology Modeling The Essential Project: Technology Modeling overview Layers of the Enterprise Architecture Relationship with Other Architectures Relationship between Business Architecture and TA Relationship between EA, SA and TA SA vs TA Technical Architecture's Scope The Technical Architect's Areas of Expertise The Technical Architect's Tasks Target System Elements Identification Technical Architecture Governance System Capacity Planning CHAPTER 19 - PACKAGED SOFTWARE AND SAAS Alternatives to Custom Development and Hosting Open Source Software Frameworks Cloud Computing Integration of Mixed Solutions Implications for Architecture Packaged Software Advantages & Disadvantages SaaS Advantages and Disadvantages Open Source Advantages and Disadvantages Integration Strategies The API Economy

Course Page - Page 10 of 14 COTS Implication: Accept Design Influence COTS Implication: Plan for Stability COTS Implication: Sustain Competency COTS Implication: Vendor Lock-In COTS Implication: Balance Business Needs & Architecture COTS Inherent Risks COTS Risk Management Strategy #1 COTS Risk Management Strategy #2 COTS Risk Management Strategy #3 Group Discussion: COTS Typical COTS Architecture CHAPTER 20 - USE CASES Use Cases Architecture Use Cases Use Case Diagram Notation Example: Use Case Diagram Template: Use Case Use Case Patterns:Team Composition Use an Iterative Approach When Is A Use Case Done? Use Case Patterns: Use Case Set The Single-minded Use Case Use Case Patterns: Scenarios & Steps Use Case Patterns: Relationships CHAPTER 21 - ARCHITECTURE DECISION DOCUMENTS Architectural Decision-making Architecture Decision Documents Sample 1: Work Queues Sample 1 Continued Sample 2: Business Rules Sample 2 Continued CHAPTER 22 - SDLC SUPPORT Architecture is Only as Good as the Implementation Solution Architect and Project Manager Project vs Product Lifecycle Collaboration Important Quality Requirements

Course Page - Page 11 of 14 Requirements Traceability Testing Test Cycles Group Discussion: Test Types CHAPTER 23 - THE ARCHITECTURE TOOLBOX The Architecture Toolbox The Toolbox What Goes in A Toolbox Solution Architecture Practitioner Toolbox Items Reference Library Group Discussion: Toolbox Items CHAPTER 24 - LESSONS LEARNED Process Recommendations Structural Recommendations Anti-Patterns Anti-Pattern: Bleeding Edge Anti-Pattern: Goldplatting Anti-Pattern: Strive for Perfection Anti-Pattern: Stuck in the Weeds Anti-Pattern: Technology Above All Group Discussion HANDOUT 1 - SAMPLE PRINCIPLES Business Principles Data Principles Application Principles Technology Principles Governance Principles SOA Governance Principles HANDOUT 2 - REQUIREMENT STATEMENT CHECKLIST Introduction Requirement Statement Review Checklist HANDOUT 3 - REQUIREMENT PATTERNS HANDOUT 4 - QUALITY ATTRIBUTE (QA)/QUALITY OF SERVICE (QOS) CATEGORIES

Course Page - Page 12 of 14 Introduction Quality Attributes HANDOUT 5 - BUSINESS USE CASE RUBRIC HANDOUT 6 - MOBILE APPLICATION ARCHITECTURE The Model View Controller (MVC) Pattern Advantages of MVC The Model Layer Controller Responsibilities Controller in Android View Layer in Android Model Layer Issues in Mobile Applications Controller Layer Issues View Layer Issues Cross Cutting Issues Mobile Architecture and Pattern Resources APPENDIX A - REFERENCE LIBRARY Overview Industry Organizations References & Further Reading APPENDIX B - ARCHITECTURE GLOSSARY ABC DEF GHI MNO PQR STU VWXYZ APPENDIX C - PATTERN LIST APPENDIX D - SOLUTION ARCHITECTURE STYLES Web 2.0 The WOA Difference Web 2.0 Technologies REST: Constraints REST: Uniform Interface REST Example Plain-Old-XML (POX) Example JavaScript Object Notation (JSON) Really Simple Syndication (RSS) & Atom

Course Page - Page 13 of 14 Syndication Example Business Process Management Further Qualifying BPM BPM Architecture BPM Architecture Model BPM Standards Master Data Management (MDM) Understanding Master Data Qualities of Master Data MDM Implementation Styles MDM Example APPENDIX E - BUSINESS PROCESS MODELING BPMN Event Symbols and Definitions Activities, Gateways, and Objects Flow Connectors APPENDIX F - UML REFERENCE UML Class UML Interface UML Associations UML Association Class UML Aggregation & Composition UML Generalization APPENDIX G - CLASS DIAGRAMS Package Diagram Package Diagram Illustrated Class Diagram Example: Annotated Class Diagram Example: Application Framework Class Diagram Example: Architectural Solution Diagram Class Diagram Notation Multiplicity Aggregation Composition APPENDIX H - INTERACTION DIAGRAMS Subsystem Interaction Diagrams Pattern Interaction Diagrams

Powered by TCPDF (www.tcpdf.org) Course Page - Page 14 of 14 Interaction Diagrams Sequence Diagram Illustrated Sequence Diagram Sequence Diagram Notation Annotated Sequence Diagram Message Notation Annotated Message Notation Example: Sequence Diagram APPENDIX I - DEPLOYMENT DIAGRAMS Deployment Diagram Notation: Nodes Stereotypes Associations Example: Deployment Diagram APPENDIX J - DEVELOP CLASS DIAGRAM APPENDIX K - THE SOLUTION ARCHITECTURE TOOLBOX SUMMARY What Goes in A Toolbox Practitioner Toolbox Items Available Dates 03/13/2017 10:00 am - 03/16/2017 6:00 pm