Enterprise and Software Architecture
Public and Teleseminar Class Schedule
Prerequisites: Object Oriented Analysis and Design with UML
Duration: 5 days at a site, 10 weeks teleseminar series
Public class price: $2500.00 includes instructor, meeting space, all course materials, and lunch each day.
Public class size: 10 - 20 delegates
Teleseminar class price: $1750.00 includes 2 meetings a week with the instructor (one instructional, one Q&A) and all course materials. Homework is assigned, and delegates interact through a Facebook Fan page. Meetings are recorded and available for delegates to download after the meeting, making it possible for people to attend who have a schedule conflict at the meeting times.
Teleseminar minimum class size: 5 delegates
Description: This class provides fundamental training for a new project architect.
This course looks at Enterprise architectures and frameworks such as Zachman and TOGAF and large scale architectures
such as programs and lines-of-business. It covers the how the project architecture relates to the other architectures
and goes into a lot of detail about how to create and document project architectures. The course examines patterns
of project architectures such as layers, client/server, 3 tier, pipe and filter, and component based, and how to
document project architectures using frameworks such as 4+1 or Bredemeyer's Visual Architecting Process.
This class is designed for senior designer/developers who wish to move into a Project Architect role or perhaps
eventually an Enterprise Architect role. Delegates should have taken OOAD with UML or have significant experience
with Object Oriented programming and the UML notation.
Benefits of this Course:
- Know what an Enterprise Architecture is and how it affects the project architecture
- Understand common Enterprise Architecture patterns and frameworks
- Know what a large scale architecture is and how it is different from an Enterprise architecture or a project architecture
- Understand common project architecture patterns and how to apply them
- Know how to document a project architecture using a framework
- Understand the common design patterns and how they relate to your architecture
- Understand why common design issues have to be resolved in the architecture
- Know how to evaluate the strength or goodness of your architecture
Topics
- Introduction to Software Architecture
- What is architecture - building, complex, city
- What is software architecture - enterprise, large scale, project
- The importance of creating an architecture
- The importance of documenting an architecture
- The importance of maintaining an architecture
- Where we are today in applying software architecture
- Notation - UML, SysML, other
- Modeling Tools - Advantages and Disadvantages - Drawing Tools, Modeling Tools, Software Development Environments (SDE)
- Enterprise Architecture
- What is Enterprise Architecture
- Where it fits in the corporate structure
- Have we seen the benefits of Enterprise Architecture
- What are the elements of an Enterprise Architecture
- What are some common software architecture patterns for the Enterprise - event driven, agent based, service oriented, publish/subscribe, data centric
- The enterprise network - hardware and connections
- Locating databases and applications - centralized vs distributed
- Constraints at the enterprise level
- Maintaining the Enterprise Architecture
- Relationship of the Enterprise Architecture to the Project Architecture
- Documenting the Enterprise Architecture with Frameworks
- Zachman Framework for Enterprise Architecture
- The Open Group Architecture Framework (TOGAF) for Enterprise Architectures
- SOA
- Reasons for using this architecture
- The effect of a SOA architecture on the corporate structure
- Elements of a SOA Architecture
- Large Scale Architectures
- Program Architecture
- Reasons for using this architecture
- The effect of a Program architecture on the corporate structure
- Elements of a Program Architecture
- Line-of-Business Architecture
- Reasons for using this architecture
- The effect of a Line-of-Business architecture on the corporate structure
- Elements of a Line-of-Business Architecture
- Intro to Project Architectures
- The Architecture Lifecycle
- Analysis and Design Process for creating or updating an architecture
- Architecture and Agile projects - evolving the architecture
- Overview of Project Documentation
- Common UML Elements - Notes, Association, Dependency, Containment, Contents, Packages, Frame, Heading
- Analysis Model - Use Case, Activity, and Class Diagrams
- Architecture Model - Component, Sequence, Communication, and Deployment Diagrams
- Design Model - Class, Composite Structure, and State Machine Diagrams
- Technical Requirements Analysis
- Requirements Documentation - Use Cases, activity diagrams, domain model as class diagrams, shall requirements, supplemental requirements, business rules, UI and wireframes
- Analysis for New Development - Key abstractions, Basic Sequence Diagrams, relationship between activity and sequence diagrams
- Analysis for Updates to Existing Systems
- Analysis of the impact of Enterprise and Large Scale Architectures on the project
- Common Architectural Patterns
- Layered
- Client /server
- 3 tier
- Web
- Object Oriented or Component
- Reference Models
- Reference Architectures
- Mapping the Requirements to the Architecture
- New and existing systems
- Requirements from the Enterprise Architecture
- Architectural considerations and designing for change
- Components and Interfaces
- Requirements to component mapping - CRC cards, sequence diagrams
- Defining Interfaces to the Components
- Defining Architectural Constraints
- Project Level Architecture Frameworks
- Krutchen's 4+1 Architectural Views (from Rational Unified Process)
- Bredemeyer Visual Architecting Process
- Evaluating the Architecture
- Analyzing and comparing competing architectures
- Strength of the resulting architecture/design - coupling, cohesion, stability
- The case for refactoring
- Resolving System Design Issues
- Human / Machine Interface
- Multi-Process / Multi-Threaded and Parallel processing
- Distribution
- Persistance
- Error Handling
- Incorporating Legacy Systems - Applications, databases
- Introduction to Design Patterns
- Background and Usefulness
- Adapter
- Proxy
- Facade
- Command
- Bridge
- Emergent Architectures
- Dynamic Data and Relationships
- Dynamic User Interfaces
- Clouds
- Designing the Interfaces
- Component Design
- Test Harness Design
- State Machine Diagrams
- Identifying components with significant state-driven behavior
- Modeling state-driven behavior with State Machines
- The Architecture over Time
- Implementing the Architecture
- Maintaining the Architecture
- Techniques for "reverse-engineering" an architecture
- Resources for your continuing education
- Certifications
- Books
- Websites
Instructors: Geri Schneider Winters. Ms. Winters was first introduced to Object Oriented techniques in 1982. She has worked using OO Techniques in Booch, OMT, OOSE, and UML notations. Ms. Winters has taught OO, Architecture, and Design Patterns for many companies including Rational Software, IBM, Boeing, Safeway Inc., Intuit, Dental Dental of California, and University of California Santa Cruz Extension. She has been using UML since the 0.8 release in Austin, Texas in 1996.
Contact us to schedule an on-site class!
Recent News
Wyyzzk, Inc. courses have been delivered to major corporations such as Safeway Inc., IBM, Boeing, Intuit, and the US Air Force, as well as to the University of California Santa Cruz Extension and Carnegie Mellon University, Pittsburgh, Pennsylvania.
Comments
This course combines two shorter courses that were previously delivered for Carnegie Mellon University and Safeway Inc.
"Geri's Survey of System Architectures class was perfect for me. I've been interviewing for post-graduation jobs. This class gave me the knowledge to answer recruiter's questions about enterprise architecture. I felt I really impressed them, and felt good about having the answers!"
Jan P.
Pittsburgh,PA, USA
Comments refer to a course at Carnegie Mellon University for seniors in Information Systems