Keynotes and General Session Presentations
Enterprise Architecture Tracks
Infrastructure Architecture Tracks
Software Architecture Tracks
Fundamentals of Architecture Tracks

*Topics and speakers are subject to change

Keynotes:

How to be a Successful IT Architect
Presented by Angela Yochem, IASA Fellow, SVP, Strategic Architecture Management Executive, Bank of America

The IT architect (software, infrastructure, business, or enterprise) is essential to the successful use of technology to support business objectives. IT architecture in this context is defined as THE expert in how to use technology to increase shareholder or business value. It is what defines us as a profession. However, becoming an architect and succeeding as an architect are seldom, if ever, discussed.

This presentation will describe a rigorous path to go from IT specialist (developer, pm, testing, etc) to architect and how to succeed and grow in that role. The author has taken her years in the trenches and in the board rooms and distilled a series of general guidelines and detailed specifications for success in this crucial role.

Large Scale Infrastructure Architecture
Presented by Michael Manos, Chief Architect, Microsoft MSN

The MSN infrastructure architecture is one of the most powerful in the world. With millions of subscribers, data centers with thousands of servers and one of the most powerful feature sets in the world, MSN has quite an architectural challenge to meet. Michael Manos is the master infrastructure architect bringing all of this strategy to life. This keynote will help your organization develop large scale infrastructure architectures basd on the real life case studies from the MSN experience.

Agile Strategies for Enterprise Architects
Presented by Scott Ambler, IASA Fellow, Practice Leader Agile Development with IBM Rational

Agile Strategies for Enterprise Architects Agile software development is quickly being adopted within organizations worldwide and will likely to be the norm by the end of the decade. Architecture is an important part of any agile software development project, contrary to popular belief. Just like a traditional team can benefit from enterprise architecture (EA) support, when it's done right, so can an agile project team. The secret is in doing EA right, and traditional approaches to EA simply aren't "right" for agile projects: the high failure rate with EA efforts tells us that traditional approaches likely aren't right for traditional teams either. This keynote describes effective strategies for EA which will enable enterprise architects to effectively support agile teams, strategies which are based on collaboration and working software instead of command-and-control and comprehensive documentation.

	Scott Ambler is the leading exponent of Agile Modeling (AM) methodologies. He is the author of many books on software architecture and process, and a columnist for Software Development magazine. His most recent book is "Agile Modeling: Effective Practices for Extreme Programming and the Unified Process."

Service Oriented Architecture: Making the Leap, Leveraging the Standards
Presented by Richard Soley, CEO, OMG

It seems that Service Oriented Architecture (SOA) is to be this year's hot buzzword, rather than a well-defined, meaningful and valuable part of the Enterprise Architecture landscape.  Before the term fades away completely, perhaps we should agree what's valuable about the move to SOA and how to make the leap, and make the leap valuable.  The SOA Consortium is making great strides in defining SOA to be a valuable business strategy for business agility, in the context of Enteprise Architecture, Business Process Management and other concepts; and the Object Management Group (OMG) is making headway on modeling standards for services (as opposed to yet another set of standards for moving bits around wires).  Dr. Soley will introduce the SOA Consortium and give some context for OMG's work in service modeling.

Enterprise Architecture Tracks

Evolution of the Enterprise Architecture practice from technology focus to impact on strategic business initiatives

Presented by Rawls Whittlesey, Chief Architect & Director, Enterprise Architecture, Delta Technology.

Enterprise Architecture came into being at Delta Air Lines in 2004 to provide an enterprise view of technology projects and to guide technology planning. Today the practice is seeing big wins in several business areas, and is playing a key role in the transformation of the Airline. This presentation discusses the evolution of the Enterprise Architecture practice from purely technology focused to its impact on strategic business initiatives. The journey continues and the Chief Architect will present the approach, several case studies and lessons learned along the way.

Cornerstone: 19 Core Beliefs about EA
Presented by Tim Westbrock, Managing Director, EAdirections

The fundamental objective of a business is to create value for stakeholders. 

Executive teams work hard to determine and validate a business’s value drivers and develop a business strategy.  They perform SWOT analyses, look for strategic inflection points, examine resource allocation and search for economies of scale while debating the merits of operational excellence versus customer intimacy. Business Process Owners look for value from large scale BPR efforts, business improvement through eliminating defects by embracing Six Sigma, or a continuous improvement approach such as kaizen.  Staff functions also work hard trying to create value – from improved cash management to talent acquisition.  All of these roles – executive leadership, business process owners and staff functions – are striving to create value.

Enterprise architecture efforts must also strive to create shareholder value if they are to gain the support of executive leadership, and be viewed as effective both inside and outside the IT organization.

This seminar will focus on the 19 core beliefs of EAdirections in helping EA teams create value, such as:

• When done correctly, Enterprise Architecture is a manifestation of an organization’s mission, and the IT strategy which enables that mission.
• A 'mediocre' Enterprise Architecture that is broadly understood and consistently implemented has much greater value and ‘hard ROI’ than a 'great' architecture with brilliant engineering which is neither understood nor embraced.
• The true measure of the effectiveness of an Enterprise Architecture is the extent to which it changes day-to-day behavior and decision making.
• Enterprise architecture is a 'process' not a 'project'; it must be on-going and organic, just as a healthy organization is always evaluating its strategies and tactics, measuring its performance and adapting as necessary.
• An EA framework is less important to success than EA leadership.

Making your systems smart (enough)
Presented by James Taylor, VP of Product Marketing/Management, FairIsaac 

The modern business climate requires smarter systems than most organizations have. Automating critical operational decisions with business rules, enhancing those rules with data-driven analytics and managing and adapting those decisions over time is what is needed: This approach, enterprise decision management, results in systems that are smart (enough) to be useful. In this session James will cover:

• Smart (enough) systems defined
• Focusing on decisions to make your systems smarter
• An architecture for automating decisions
• Decisions, SOA and BPM
• Getting there from here

	Vice President of Product Marketing/Management at Fair Isaac with 15 years designing, developing, releasing and marketing advanced enterprise software platforms and development tools. Across the board experience in software development, engineering and product management and product marketing.

Enterprise Business Architecture
Presented by Ralph Whittle, Strategic IT/Business Consultant

What is an Enterprise Business Architecture (EBA)?    This presentation will define and illustrate how the EBA is built and integrated with major strategic initiatives in order to deliver predictable results. 

To integrate and empirically derive all of the architectures of the enterprise, we need one base or foundational architecture; a central plexus between the strategy, its supporting architectures, and the expected results of the planned initiatives.  This is achieved with the Enterprise Business Architecture. 

The EBA provides a comprehensive view of the enterprise, and the insight necessary to achieve business/IT alignment, performance improvements and a competitive advantage.  

Enterprise Architecting Software + Services Applications
Presented by Fred Chong, Architect, Microsoft Architecture Strategy Team

Software plus services (S+S) is the new application paradigm for delivering the “best of” on-premise and software services to the application users. However, for the software vendors, delivering S+S involve solving new technical challenges in areas such as multi-tenancy, network-related user experience and application hosting and operation.

This session will highlight key architecture principles, approaches and tradeoffs for addressing customization, security and isolation concerns within a multi-tenant environment. In this session, Fred will use LitwareHR, a sample S+S application implemented with commercially available development tools and source code available from codeplex, to demonstrate the technologies and techniques for satisfying multi-tenant requirements and improving network user experience.

Enterprise Architecture Frameworks -- Enabling EA
Presented by Ramesh Yemeni, Turner Broadcasting

As we all know there is no Silver Bullet. However utilizing an existing EA framework can aid in the delivery of real value from the architectre teams without the cost of building it yourself.

There are numerous EA Frameworks available on the market today. TOGAF, Zachman, FEAF, Light EA, and many others. However there is little or no advice available on how to select, integrate and connect these frameworks within an organizations architecture practice. This talk will guide the architect practicioner through the selection and integration of an EA framework in an organization.

	Information coming soon

Pragmatic Approach to an EA Implementation
Presented by Mark Foster, Director of Professional Services, Troux Services

• “What are my assets and what do they support…TODAY”, says the CIO
• Aspects of Implementation
  • EA Planning
  • The ever-changing meta-model
  • Getting to the data
  • The Moment of Truth…the data
• Facts-to-Funding

Mark W. Foster is the Director of Professional Services at Troux Technologies and is responsible for the methodology for EA implementations as well as the overall success for customer implementation. Mark has worked closely with clients in the banking, entertainment, retail and technology industries with solutions for application rationalization, mergers and acquisitions, service portfolio management, standards and business impact analysis.

DoDAF - Not just for the Pentagon?
Presented by Daniel Brookshier, Chief Architect, NoMagic

Daniel will introduce you to the DoD's Architectural framework. This will be a fast and complete introduction to the framework that is mandated for all DoD projects. This is a quick introduction into how DoDAF works and why, even though something out of the DoD might be suspected of being... huge and unmanageable, DoDAF is actually easy to use and powerful enough for the public sector.

Even if you have seen DoDAF in the past or its predecessor C4ISR in the past, you will be in for a surprise because the newest incarnation is based on an extension of UML called UPDM. UPDM, from the same group managing the UML standard, is a significant leap in your ability to create a verifiable architecture that can leverage code generation and other model-based technologies plus leverages your current tools and experience. It all adds up to a next generation framework for any domain. Is DoDAF something you just might need to learn? Daniel thinks so and will make the case that DoDAF is a very nice framework worthy of your consideration.

Daniel Brookshier has recently joined No Magic taking position of Chief Architect. He has been using UML in multiple international software development projects. Daniel has been MagicDraw UML user #14 since 1998. He has run multiple training courses covering UML modeling using MagicDraw. Daniel has impressive experience in Java development. He has been a consultant, speaker, author, and Java Geek since Java 1.0. Daniel is one of the core members at jxta.org and runs several open source projects. Daniel's latest book is JXTA: Java P2P Programming, but he also writes articles for java.sun.com and P2PJournal where he is an editor.

Infrastructure Architecture Tracks:

Perspective Based Architecture (The PBA Method)
Presented by Lewis Curtis, Strategic Infrastructure Architect Advisor for Microsoft Corporation

After nearly three years of field development with contributions, case studies from customers, international bodies and field teams, The PBA Method has matured into a viable structure promoting quality decisions with simplicity and ability to work with any process or methodology.

The PBA Method is a simple structure to promote higher quality decision making. This is accomplished through three stages containing structured focused questions. Step one is a series of questions capturing the perspective (what is your environment and where is it going). Step two examines the impact of alternatives or existing proposals on the captured perspective (from step one). Step three examines the impact of the final proposal on the captured perspective (from step one).

This simple structure works with all processes and methodologies, technologies and documentation standards. After two years of research and work with international bodies, customers and field teams, The PBA Method was developed to fill a missing element for the architecture community; drive better decisions by capturing better questions. Finally, The PBA Method represents a living architectural methodology. Questions and perspective structure can evolve over time that transcends current common patterns, methodologies, processes, technologies and operational structures. Customers, partners and international bodies have communicated a interest to participate in growing, promoting and capitalizing on The PBA Method.

Lewis Curtis is a Strategic Infrastructure Architecture Advisor for the Development and Platform Evangelism group. He focuses on next generation technologies and enterprise strategies for data center architecture. He has pioneered the work on the Perspective Based Architecture (www.perspectivebasedarchitecture.com) and published a PBA article for the Architecture Journal.   He is  on the Microsoft Certified Architect board of directors.

Infrastructure Thinking in the Business Domain
Presented by Chris Haddad, VP  Burton Group

While architects often believe that cutting-edge technology infrastructure provides the foundation for realizing business domain goals, business owners frequently take a pragmatic, ‘show me’ position. Demonstrating the value of infrastructure thinking in the business domain requires establishing business improvement goals, documenting the existing state, and performing disciplined collection of business and Information Technology (IT) metrics throughout projects.

In this presentation, Haddad will present how architects should position IT infrastructure projects in the context of strategy, standards, service models, process, and organizational realignment. He will outline a methodology to gauge and improve IT efficiency and productivity through the application of a maturity model, roadmap, and a transformation program.

Chris Haddad is Vice President and Service Director of Burton Group's Application Platform Strategies Service.  He leads the research team that focuses on infrastructure technologies used to design, develop, and deploy applications and services. His coverage areas include service oriented architecture, model driven development, business process management, opensource, and technology adoption strategies.   Chris has established software development processes, product direction, and integration strategy of several successful software companies. He was granted committer status on the Apache Axis project in 2002, and served as an advisor on conference editorial boards and chair of special interest groups. Author, editor, and contributor on numerous articles, technical publications, presentations, and podcasts. Frequent speaker at industry conferences including Enterprise Architecture Summit, Networld+Interop, SOA Web Services Edge, and SDWest.

Designing a Standard for Data Access in an SOA Environment
Presented by John Goodson, VP DataDirect

Service Oriented Architectures (SOA) are rapidly becoming the standard for new application development in many organizations. Architects and development teams value SOA because it enables them to rapidly deploy new applications and functionality while utilizing existing assets to standardize common functionality.   In any SOA, standardization at the data access layer simplifies development, deployment, and increases overall flexibility. 

This session will lay out a strategy for designing a data access standard in the SOA context. We’ll look at the common challenges faced by architects as they attempt to utilize SOA as the integration architecture in their diverse, heterogeneous data environments. Next, we'll share an approach to designing a light-weight and flexible data services layer using standard components such as ODBC, JDBC, ADO.NET and XQuery. We will also discuss approaches for SOA-enablement of legacy assets, whether in the form of business logic, data or screen-based assets.  Finally we will examine current trends related to the use of XML for both messaging and data integration.

SOA, Everything You Know Is Wrong
Presented by Dave Edstrom, Technical Director, Sun Microsystems

Enterprise Identity Management Architecture
Presented by Sitaraman Lakshminarayanan, Enterprise Architecture and Security Consultant, Author

Organizations are looking to address the access management, single sign on, password management, on boarding or off boarding, Federated Identity Management, authentication in Web services, etc in all possible ways.

While different products can solve a particular issue, certain technolgies and solutions overlap and organizations should understand current and future technology trends in Industry to set the Enteprise Identity management Architecture. This presentation will discuss in detail the various components of Enteprise Identity Management Architecture such as Web access Management, SSO, Federated SSO, Virtual Directory, Meta-Directory, Security Token Service, Two Factor Authentication and how they interact with each other in an Enterprise.

	Sitaraman Lakshminarayan has over 10 years of IT experience and has co-authored the book on ASP.NET Security. He has worked on both .NET and java technologies and provides consulting in Enterprise Architecture and Security.

Master Data Management – where business meets IT
Presented by Roman Rytov, Product Director, SAP MDM NetWeaver

Master Data Management appeared on the map of an enterprise architecture just a few years ago but today all the major players have proposed their solutions. The presentation acquaints the audience with the problems and challenges that MDM comes to address, potential architectural options, the solution from SAP, and success stories of customer implementations. Target audience - enterprise architects, leads of IT, business analysts.

10 ways to fail in a data warehouse project
Presented by Jacob Pellock, Director of Software Architecture, ChoicePoint, Inc.

The presentation will review scenarios that can cause hardship and failure in data warehouse projects with the goal of learning from described anti-patterns.  The discussion will cover a broad number of points ranging from software architectural models, application and database scalability, hardware architecture, team relations, and requirements management.

Tension between convenience and security – finding the right balance
Presented by Jason Chambers, Lead Architect, nuBridges Inc.

Over the past decade or so the thirst for information has put tremendous pressure on the IT department to provide the business with access to any data any time from anywhere. In parallel with this, there has been a tremendous increase in data theft. The demand for information exposes the classic tension between convenience and security. The Architect has a big role to play in addressing the balance of convenience versus security.

This presentation will discuss the problem of Data Security from the viewpoint of the Solutions Architect. It will focus specifically on addressing the payment card industry (PCI) mandates which affects any business that deals with credit card information; however other types of sensitive information equally apply e.g. medical records, social security numbers etc.

Practical advice will be provided to those that may be facing this challenge in their current projects.

Software Architecture Tracks:

Twelve Timeless Tenets of Application Architecture
Presented by Rick Wagner, Software Architecture Consultant 

Experienced software architects carry a mental toolkit of patterns and best practices that allow them to quickly set direction and instantly increase a project's chance of success. This talk will introduce twelve such recurring patterns that have broad applicability and are sound enough to withstand years or even decades of change to the environment around them. Some deal with batch paradigms, some with online paradigms, and some with shared concerns, but all are relevant and of significant worth to the architect that recognizes the time to apply them.

Polygot Programming
Presented by Neal Ford, Sr Application Architect, ThoughtWorks

Java is dead; long live Java! The Java language is over a decade old, and it's starting to show its age, hampered by both backwards compatibility that it didn't need and the changing world. And I have examples! But the decline of the language is offset by the rise of the platform: the Java platform is as robust as ever. This presentation discusses the coming trends in software engineering, which I call "Polyglot Programming": special purpose, targeted languages running on current virtual machines. We already do this: every application today uses Java, SQL, and Ajax. In the coming years, we'll expand our horizons to start using JRuby, Groovy, Jaskell, and a host of other languages, all targeting the Java VM. This presentation also engages in a real conversation about "software engineering" and what that really means. And, it tells how we can get other engineers to stop making fun of us. Come see your future.

10 Ways to Improve Your Code
Presented by Neal Ford, Sr Application Architect, ThoughtWorks

Last year, I did a talk called Clean Up Your Code: 10 Coding Tricks, Techniques, and Philosophies. The concept behind that talk was to point out common mistakes and treacherous paths that Java sometimes exhibits. This talk is essentially the sequel to that one, discussing code hygeine from a more advanced level. This talk discusses a wide swath of topics, including good citizenship, appropriate messaging between objects, canonicality, reflection & code generation, improving your abstractions via domain specific languages, sacred cows, code generation, common code smells, and anti-objects. The goal is to make you think differently about the code you write every day. No one writes perfect code, and every developer eventually falls into a slump where they just crank out the same code day after day. This talk helps identify your pitfalls and how to avoid them.

Session Topics:

• Good citizenship
• Sacred cows
• Methods &messaging
• Canonicality
• Mixins
• Reflection
• Code generation
• Abstraction upgrade via DSLs
• Common code smells
• Anti-objects

Architecting Office Business Applications
Presented by Bill Zack, IASA NYC Chapter President, Microsoft Architect Evangelist, Author

APIs: The other User Interface
Presented by Burkhardt Hufnagel, Sr Software Architect, ChoicePoint, Inc. 

A well designed API is critical to the success of libraries and frameworks, but the methods and techniques to do so are rarely taught - or even thought about. This talk centers on the importance of good API design and shows how User Interface and User Experience design principles and techniques can help you craft APIs that are effective, efficient, and elegant.

Agile EAI, Agile SOA
Presented by Richard Green, Enterprise Architect, DTE Energy 

The purpose of this session is to explain a few simple concepts and methods that facilitate agility in the context of enterprise integration and service-oriented architecture. The session is a short tutorial. However, attendees should be familiar with basic OOA and OOD concepts and practices to fully understand the concepts and put the methods into practice.

The epiphany comes when you realize that enterprise integration is all about improving the way that business processes talk to each other. Business processes talk to each other by sending messages. Hence, in enterprise integration, the message is the feature. This presentation outlines how to reduce this simple idea to a simple practice by applying the fundamental concepts of OOA, OOD, TDD, concurrent engineering, and agile project management.

Corrective IT Architecture: Maintenance in the Large
Presented by Mark Grand, Software Architect Consultant and Author

Corrective IT architecture is about fixing broken projects and dysfunctional infrastructure.  This talk will explain how to recognize when business as usual will not lead to the success of a project or overcoming a dysfunctional infrastructure. It will also describe techniques to fix projects and improve infrastructure it while allowing applications depending on it to continue operating.

Adding Concreteness to the Business Value of Architectural Choices
Presented by Cliff Berg, IASA Capital Area Chapter President, Consultant and Author

Business is calling for a greater participation in IT decisions, yet IT suffers from a credibility gap and will be at a disadvantage in integrated decision-making unless it finally learns to explain the value of its technical architecture strategies in business terms. Prior approaches that resort to intangible risk and value scales are inadequate because they do not provide a means of performing tradeoffs between different business priorities. The only answer is to tackle the hard problem: what is an IT architecture strategy worth?

Fundamentals of Architecture Tracks:

Empower developers using Feature Driven Development
Presented by Don Browning, Principle Architect, Turner Broadcasting Systems

Developers are always getting dumped on. Project managers blow estimates; developers pay the price. Business Analysts generate bad requirements; developers pay the price. Management sets unrealistic expectations and delivery dates; developers pay the price. So how can we as Architects help to fix this problem? We fix it by empowering developers to take a more active role in the tactical execution of development projects. Two primary forces are at play to enable this: 1) the developer toolset, in our case Visual Studio Team System, and 2) the project methodology, Feature Driven Development (or FDD).

This session will begin with an overview of FDD. FDD is an agile methodology is and is based on timeboxed iterations no longer than 3 weeks in duration. A project using FDD is based on five phases, 3 for planning and 2 for construction. In this talk we’ll start by discussing the planning phases, how to model the problem domain, and how to work with analysts, users, and project managers to gather requirements (features) and estimate them. Then we will dive into the construction phases and discuss specific strategies for designing and building code so that you may track the progress of the project based on code checked into the source repository.

Once we’ve laid the foundation with the process, we’ll dive into Visual Studio Team System. There are specific features of VSTS that enable this type of development. VSTS is much more than a fancy source code repository (though it does that very well), it provides a mechanism for creating and tracking development tasks and scenarios, it enables parallel development with complex (yet easy to use) branching and merging capabilities, code inspection, project tracking with Excel and Project integration, bug tracking, unit testing, automated builds and a data warehouse to surface rich information about the state and health of the project. Most importantly though, it puts developers in the center of the development process. The supporting roles (PM, BA, QA, CM) surround it and use VSTS to enable them to get the information they need to keep the project rolling.

Designing a Highly Available Environment for the Masses
Presented by Marvin Vinson, Sales Consultant, Oracle

Critical applications must be highly available.  Brokerage sites, internet stores, support centers, retail systems and other crucial applications cannot handle extended outages due to unplanned and planned downtime.  This could lead to reduced revenue, lower margins, lost customers or bankruptcy.  This session will explain necessary hardware and software components, as well as best practices to design a highly available infrastructure.  These concepts can be applied to Small and Medium Sized Businesses (SMB) as well as business with revenues that exceed one billion dollars.

Persistence Architectures
Presented by Carol Shepherd, Instructor & Principal, Zo-Be Enterprises

This session will focus on the new JPA standard and how it fits into your application’s architecture.  We’ll start by setting the stage with a discussion of data persistence and the most common implementation, ORM ( Object Relational Mapping).   We’ll then move on to discuss the frameworks and application servers  that many of you are using right now and how they fit into this new JPA world.   Next, we look at the moving parts of JPA from a visual thinker’s perspective ( that is me!).  Finally we’ll dig into some real code examples with a few digressions into the new Java 5 annotations.  And at some point in the hour I’m sure we’ll have some rousing discussion on the de rigueur of annotations vs. XML.

Introduction to Architectural and Design Patterns
Presented by Mark Grand, Software Architect Consultant and Author

This is an introduction to architectural and design patterns. It will explain the benefits of using patterns for improved communications and organization of software architecture and design. Examples of different types or patterns (fundamental, micro-architectural and architectural patterns) will be presented.

Beyond Web 2.0 - An Architect's Toolkit for a "Network of Things".
Presented by Mike Sweeney,  Open-source and Community Evangelist, Sun Microsystems

As more and more "things" are connecting to the network, Architects face accelerated change, and a proliferation of nebulous stakeholder requirements.

Today's RSS data feeds will be supplemented with new protocols and telemetry data from "things" such as, commercial and residential-based electronic sensors (modern SCADA networks - electric, gas, and water pipeline operations), air and ground-based engine monitors, intelligent power usage meters, and a profusion of multi-purpose phones, smart cards, and GPS units.

This talk will include methodologies and tools to manage the data explosion, and capture changing requirements, It will also include sharing communication skills vital for interacting with demanding stakeholders.

The Profession of IT Architecture
Presented by Paul Preiss, President and Founder, IASA

This presentation focuses on the skill-set taxonomy and the goals of IASA including education, certification, and training.  Join Paul to discover what IASA is doing for the IT Architecture profession and how the organization plans to turn good architects into great architects.

Architecting Right Quality Attributes
Presented by Max Poliashenko, VP Strategic Architecture Management, Bank of America 

Architecting your solution to meet the functional requirements is not sufficient to assure its success. Your customers probably have quite specific expectations about how your solution should perform, also known as non-functional requirements. Besides that, you may have to think about cost of maintaining and evolving your application or product in the future, as well as of costs of supporting it in operations. If you plan for it or not, but your IT system always has Quality Attributes that affect all these aspects and areas. It is much better when you get requirements for them, plan, architect measure and manage them rather than letting it happen by chance. Each Quality Attribute has unique set of considerations and sometimes, they compete. It is important for you as an Architect to understand what architectural decisions may affect these attributes, how to measure such impacts, and what to be guided by when dealing with trade-off points.

World-class Architecture Documentation
Presented by Brian Sondergaard, Director of Product Development, CheckFree Corporation

Good architecture descriptions are explosive! Like C4, the architecture description can shake things up, remove roadblocks, and create opportunities where none existed before. In order to have this impact, the architecture description - the Software Architecture Document (SAD) - must be Correct, Clear, Concise, and Comprehensive. It must be C4!