Architecture and Iasa Introduction
Upcoming SlideShare
Loading in...5
×
 

Architecture and Iasa Introduction

on

  • 468 views

This presentation leverages some content from others to give an overview of System and Software Architecture in general and an introduction into the fundamentals of the Iasa architecture model.

This presentation leverages some content from others to give an overview of System and Software Architecture in general and an introduction into the fundamentals of the Iasa architecture model.

Statistics

Views

Total Views
468
Views on SlideShare
461
Embed Views
7

Actions

Likes
3
Downloads
15
Comments
0

1 Embed 7

http://www.linkedin.com 7

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • These categories derived from information taken from a job task analysis used to define the IT Architect Body of Knowledge
  • All Specializations & Roles have the same foundational skills…How do these compare to Microsoft’s original 7 Architecture Competencies?The mapping shows how the original Microsoft Compentencies map directly to the IASA Pillars (as they should)The ISAS Pillars, however, add greater definition around the architectural disciplinesWorld-wide focus groups found EA to be a role, not a specializationEA’s are a cost in search of value with many organizations making them consultative groups (i.e., profit-centers) to re-coop costsUPS, BA take this role and apply it across their lines of business.Invite attendees to become part of the IASA BoE to continue the debate on these definitions.
  • An architect must not only know the financial calculations, but also when to use them to appropriately justify their architectural decisions.These strategy & innovation methodologies have been presented in TechEd’s past and are available for viewing on Channel 9 video in the reference section.It is important for architects to understand technology roadmaps not only of the products and stacks they use, but also of those in industry outside of their domain knowledge.
  • Skills in the functional and procedural aspects of technology organization to ascertain solution and organizational maturity.It’s how we run things (maintenance & support) and how we create new things (forward engineering).
  • Application DevelopmentInfrastructure Technical Project ManagementPlatforms and FrameworksChange ManagementAsset ManagementGovernanceTesting Methods, Tools, and Techniques
  • Industry trendsLeaders in the specific application space - and why they are leadersBenefits and limitations of various methodologies and technologiesMethodologies and technologies currently in use (and why)How to gage supportability, impacts on operations, etc. (TCO)It’s about Balance…
  • A quality attribute is a non-functional characteristic of a component or a system. It represents a cross-cutting architectural concern for a system or system of systems. IEEE 1061: The degree to which software possesses a desired combination of quality attributesISO/IEC 9126-1: Defined with six categories of characteristics: functionality, reliability, usability, efficiency, maintainability, and portability which are divided into sub-characteristics
  • The risk of ignoring quality attributes are many times greater than the cost of effectively managing from the start (e.g., some may cause potential lawsuit or death)
  • Only 21% of survey respondents thought QA monitoring & management is essential!!!
  • All Design decisions, elements, & artifacts should tie to a business requirementIf you cannot tie a given element of the architecture to a specific business requirement, then remove it – we create 10%-50% scope creep by our own admission of best-practices, standard template reference architectures, etc.
  • Peter Stasinopoulos, Michael H. Smith, Karlson 'Charlie' Hargroves, Cheryl Desha, Whole System Design: An Integrated Approach to Sustainable Engineering,Earthscan Publications Ltd. (January 2009) Whole System Design : Highlight that "whole system" applied means entire systems, how they interconnect, and exist in parallel with the whole environment are considered .Whole Design encompassesindustry perspectives – even those outside your in-house standards – as they may impact your architecture.
  • Human Dynamics encompasses the skills associated with managing and influencing people and their interrelationships in the context of an IT project or environment.
  • The first link is the repository home page.The second link is to the ITABoK download page.

Architecture and Iasa Introduction Architecture and Iasa Introduction Presentation Transcript

  • Utah IT Architects Association Iasa Salt Lake City Chapter Architecture and IASA Introduction Tom Creighton CTO/Lead Architect FamilySearch tc@familysearch.org January 2014
  • What is Architecture? • Many definitions proposed • CMU SEI: > 30 definitions of Software Architecture – – – – – http://www.sei.cmu.edu/architecture/start/glossary/?location=tertiary-nav&source=217160 Bibliographic Software Architecture Definitions Community Software Architecture Definitions Modern Software Architecture Definitions Published Software Architecture Definitions
  • ISO/IEC/IEEE 42010 • fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution • Note the distinction between architecture and artifacts.
  • Open Group • A formal description of a system, or a detailed plan of the system at component level, to guide its implementaition. (source ISO/IEC 42010:2007) • The structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time.
  • IASA
  • IASA’s Skills Matrix Role Specializations Enterprise Architecture Software Architecture Infrastructure Architecture Foundation Body of Knowledge Business Technology Strategy IT Environment Foundation (5-Pillars) Quality Attributes Design Human Dynamics Information Architecture Business Architecture
  • Business Technology Strategy It’s the financials… TCO, CBA, ROI, Payback Period, NPV, Valuation, etc. It’s business strategy innovation & validation It’s industry concerns, trends, conformance to standards, and compliance
  • IT Environment Skills in the functional and procedural aspects of technology organization to ascertain solution and organizational maturity. It’s how we run things (maintenance & support) and how we create new things (forward engineering).
  • IT Environment Determine Goals, Alternatives, and Constraints Evaluate Alternatives and Risks Establish Requirements Application Development Infrastructure Technical Project Management Platforms and Frameworks Change Management Asset Management Governance Testing Methods, Tools, and Techniques Design Creation Budget 4 Budget 3 Budget 2 Budget 1 Prototype 1 Prototype 2 Prototype 3 Prototype 4 Program Implementation System Test Release to Customer Plan Develop and Test Plan Voice of the Customer Testing Scenarios New User Inputs Bugs New Version System Metaphor Architectural Spike Release Planning Uncertain Estimates Process Iteration Acceptance Testing Confident Estimates Next Iteration Spike Next Release
  • IT Environment Best if you are familiar with: Buy • Industry trends • Leaders in the specific application space - and why they are leaders Build Waterfall • Benefits and limitations of various methodologies and technologies Agile • Methodologies and technologies currently in use (and why) • How to gage supportability, impacts on operations, etc. (TCO) Interoperab ility Stand alone
  • Quality Attributes A quality attribute is a non-functional characteristic of a component or a system. It represents a cross-cutting architectural concern for a system or system of systems.
  • Quality Attributes IASA Groupings: • Quality attributes cut across all IT architectural concerns • Also called systemic qualities, *ilities • Time, cost, requirement, & resources constraints can become a trade off in applying quality attributes Usage: Development: • • • • • • • • • • Usability Localization Accessibility Personalization Customizability Manageability Maintainability Supportability Extensibility Flexibility Operation: • • • • Performance Reliability Availability Scalability Security
  • Quality Attributes Must be measurable, monitored… Number of 9’s Yearly Downtime 3 Nines (99.9%) ~9 hours 4 Nines (99.99%) ~1 hour 5 Nines (99.999%) ~ 5 minutes 6 Nines (999.999%) ~31 seconds 24/7 0
  • Quality Attributes QA Interactions… Flexibility Personalization Localization Maintainability Extensibility Reliability Customizability Availability Accessibility Performance Scalability Security Deployability Observability Supportability Key + P P + + + P P P P P P P P P P P - P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P - - + P P P P P P + P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P lic ab le Operations he l ps hu rts ne ut ra No l ta pp Ü imapcts Ú Usability Fle Pe xibil rso ity na liz ati Lo on ca liz ati M ain on t Ex a ina ten bil it s Re ibili y ty lia b Cu ility sto Av miza a il bi l a it Ac bilit y y ce ssi bil Pe rfo ity r Sc man ala c bil e i Se c u ty rit De y plo Ob yabi li se rva ty Su pp bility or tab ilit y Development P P P P P P P P P P P P P P - P
  • Design Design skills are an architect’s primary tool in delivering architecture strategy and product to the business. Good design is justifications, reasons, and trade off considerations… it encompasses capturing the decisions made.
  • Design Design implies: Knowledge of methodologies and techniques Knowledge of tools for design Knowledge of design artifacts such as patterns, styles, views, and viewpoints All Design decisions, elements, & artifacts should tie to a business requirement
  • Design Whole System Design : The "whole system" of interconnected elements that participate in, impact, and influence the design process, including the nature and rich tradition of design theory and practice, relevancy of understanding design as a discipline. The systems sciences, systems theory, and systems thinking; developing “whole systems” perspective and its importance to architects, including recognizing and addressing complex systemic problems and architecture praxis. Design judgment and the construction of meaning, including work redesign, industry perspectives, and the increasing importance of architectural influence on design.
  • Human Dynamics Human Dynamics encompasses the skills associated with managing and influencing people and their interrelationships in the context of an IT project or environment.
  • Human Dynamics Attribute Managing the Culture Customer Relations What does this really mean? Politics – understanding of the impact of human culture executing as a culture change agent. Understanding the psychological dynamics & managing stakeholder & consumer expectations against the business strategy. Leadership and Management Mentoring and guiding those who can benefit from your skills, knowledge, and experience. Peer Interaction Playing well with others by being responsive to their needs by understanding the psychology of interpersonal human interactions. Collaboration and Negotiation More Politics – the psychology of human collaboration & networking as well as strategies & methods for working together to reach agreement. Presentation Skills Understanding your audience and presenting/communicating to them appropriately. Writing Skills Quality over quantity in techniques & methods for formal & informal compositions, especially with regard to technical documentation.
  • Are You An Architect? • Do you care? • Do you want to become one? • Why should it matter?
  • Your Call to Action… Download & fill out the IASA Skills Matrix Foundation 1 Awareness Associate 2 Basic Information Demonstration 3 Individualized Knowledge 4 Practice 5 Delivery 6 Connectivity of Ideas 7 Enterprise Level Leadership 8 Industry Mentorship 9 Research 10 Industry Leadership Professional Master
  • Learn More • Visit iasaglobal.net • Join IASA – – – – Corporate membership Full membership Basic Free Membership Iasaglobal.org/iasa/membership_levels.asp • Browse/download repository items – http://www.iasaglobal.org/iasa/Resources.asp – http://www.iasaglobal.org/Document.asp?MODE=VIEW&DocID=554 • Parts of this presentation used materials from Jim Wilt’s IASA5Pillars presentation: – http://www.iasaglobal.org/Document.asp?MODE=VIEW&DocID=541 – http://www.youtube.com/watch?v=DV09cysHu7k
  • DISCUSSION