1. Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” MarkITS Enterprise A rchitecture Tenets for Improved PARTS 4 th Quarter 2005

2. 2October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Agenda Enterprise Architecture Services in a Nutshell “WHAT” Are Architecture Tenets “WHEN” Are Tenets Applied “HOW” an Architecture Tenet is Defined

3. 3October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Architecture Tenets in a Nutshell Convergence Checklist Mission and Benefits: 1.Lead convergence via a checklist of design practices; 2.Extend the useful life of system components; 3.Consistent usage of best practices “appropriate” for the size and complexity of each project; 4.Increase quality of data; 5.Increase reliability and availability of applications; 6.Improve agility of processing systems.

4. 4October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Agenda Enterprise Architecture Services in a Nutshell “WHAT” Are Architecture Tenets “WHEN” Are Tenets Applied “HOW” an Architecture Tenet is Defined

5. 5October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” “What” Are Architecture Tenets A checklist of recommendations that: 1.Guide the specification, design and implementation of solutions in context of “Architecture Views”; 2.Defines quality attributes and details specific best practices; 3.Facilitate the realization of improved IT “PARTS”:  Performance;  Availability;  Reliability;  Testability;  Scalability

6. 6October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Agenda Enterprise Architecture Services in a Nutshell “WHAT” Are Architecture Tenets “WHEN” Are Tenets Applied “HOW” an Architecture Tenet is Defined

7. 7October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” “WHEN” Are Tenets Applied Used during early requirements through implementation. Begin during project proposal assessment  Map business and IT needs to potential inventory of existing solutions or TBD’s EAS listens to key business requirements discussions to concurrently identify technical requirements and facilitate adoption of Tenets. EAS helps structure the requirements as they are being identified:  Business Requirements – inclusion in key Business-IT discussions;  Functional Requirements – testable details of business requirements;  Non-functional Requirements – supplemental needs (PARTS);  Data – persistence needs;  Technical – integration, sizing, hardware, environments, tools, COTS. EAS assists analysis to ID logical packages and raw components. EAS provides patterns mentoring during high level and detail design. EAS provides architecture & design services to business application teams

8. 8October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Typical EAS life-cycle activities in terms of 5 popular industry methods and SDLC 1 SEI 1 SEI 1) Quality Attribute Workshop, 2) Attribute-Driven Design 3) Arch. Tradeoff Analysis Method, 4) Cost-Benefit Analysis Method, 5) Active Reviews for Intermediate Designs “WHEN” Are Tenets Applied Zeal for time boxing forces delivery teams to skip critical analysis, arch, design. Once new dev. project is in implementation, arch. is largely decided (or missing). Industry shows need to focus on architecture artifacts earlier in a project’s lifetime. Exception - CBAM applies post-release activities to affect the architecture.

9. 9October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Agenda Enterprise Architecture Services in a Nutshell “WHAT” Are Architecture Tenets “WHEN” Are Tenets Applied “HOW” an Architecture Tenet is Defined

10. 10October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Best practices across four architecture views  1) Applications, 2) Data, 3) Technical, 4) Business  Speed is the need – streamline and accelerate work products  Assessment – empower self review by roles and delivery teams  Continuous improvement Empowers repeatable process for architecture and design reviews Streamline execution of tactical deliveries with less rework Spreadsheet based “roadmap” leading to “ convergence” Architecture Tenet Quality / Best Practice Work Product / Sub-product SortNum - SDLC SDLC Milestone PARTS Addressed Role Descriptor of the best practice action step Describes some of the key goals the tenet addresses Identify SDLC work product and sub set of artifacts that would satisfy the tenet Sort order and phase within the overall SDLC workflow PAP, Requirements, Specification, Development, Test Performance, Availability, Adaptability, Reliability, Reusability, Testability, Traceability, Scalability, Supportability List one or more roles accountable for ensuring the tenet is incorporated into the solution or explicitly waived “WHAT” is the Footprint of an Architecture Tenet

11. 11October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” The Application Architecture View involves detailed understanding of core applications: It describes how our organization automates business processes, both internally and externally; it describes the interactions and dependencies among processes, systems, and components; and it provides a mechanism for developing new applications and extending existing applications. If the applications identified in the Application Architecture View do not significantly contribute to meeting, or exceeding, stated organizational business objectives, the validity of the application should be questioned. Tenets applied must include Performance, Availability, Reliability, Traceability, Testability, Security, Scalability, and Supportability. The Data Architecture View reveals critical information necessary to effectively operate: The primary focus of the Data Architecture View is data. It delineates the data models of your enterprise; it defines the procedures, processes, and policies that govern your data management activities; it provides you with a greater understanding of your data recovery, backup, and usage patterns; and it provides greater understanding of the relationships and interdependencies among the data documents within your organization. The Data Architecture View is about capturing, defining, and understanding data as it relates to organizational business processes, workflows, and data repositories. Tenets applied must include Performance, Availability, Reliability, Security, Scalability, and Supportability. The Technical Architecture View enumerates the state of the technical infrastructure: It identifies desktop and server hardware; it identifies the operating systems and network infrastructure; it identifies any network components such as printers, modems, and faxes; and it provides a common set of standards and best practices for supporting the business mission of your organization. The Technical Architecture View may also include an inventory of internal and external vendors, an evaluation of current technology staffing preparedness, and the Information Technology Expenditures Budget. Tenets include Performance, Availability, Security, Scalability, and Supportability. The Business Architecture View should be foundational to all EA planning: It describes how our enterprise is structured, both internally and externally; it describes the business strategies and decisions that keep our organization focused on growth, profit and goals; it flushes out the internal operating structure of business units and the interlocking relationships between business them; and it exposes the overall objectives and goals of our enterprise. At a minimum, the Business Architecture View should enumerate our organization's values, goals, vision, and mission from an operations perspective for the next 24 months. The Business Architecture View may also contain our organizational structure, management philosophy, marketing goals, and our business plan. “How” to Maintain Convergence Heading Enterprise Architecture Plan

12. 12October 12, 2014 Slide Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” Discussion – Q & A Thank You For Your Support and Participation! Contacts and Information http://www.MarkITS.us Mark@MarkITS.us