Enterprise Architecture Openhouse 2009

It's often said that people want to buy fire insurance only after the house has burned down. This presentation will show how the artifacts and review processes of EA encourage a more proactive approach to system failure by looking at:

• Availability Engineering: What is the range of adverse events that we should consider? When is it a system failure?

• Risk Treatment: What options are there for dealing with identified failure risks?

• Focus of EA: What aspects of process and design do EA checkpoints focus on?

• Templates and artifacts: New advice and guidance to help you complete the relevant artifacts.

Peter Churchard
Security & Technology Architect
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Peter Churchard has 27 years of experience in IT, both in the private and public sectors. He joined the OPS in 1990 and has worked for the Ministry of Environment and for MBS/MGS at OCCSD and, most recently, OCCTO. For the last eight years he has worked in the Corporate Architecture Branch as a Security/Technology Architect. Prior to joining the OPS, he worked in the telecommunications industry for companies in the UK, Canada, and the US.

CYSSC has created an overarching project architecture development methodology and tool kit (labeled iPad) that greatly improves the timeliness, quality and efficiency of solution delivery. iPad provides step by step instructions for developing architecture on CYSSC I&IT projects. iPad also shows how well planned and executed project architecture integrates into the SDLC and OPS Unified Project Management methodologies that projects already use. iPad emphasizes how to plan for and do good architecture, as opposed to just producing artifacts (sometimes after the fact). iPad demonstrates, to Project Managers and Architects, how architecture improves solution timeliness and quality while reducing project risks. iPad is supported by tools that automate large parts of the process. They are used to create and maintain the various architecture artifacts—models in particular—from project start to project end. Deploying these tools and using iPad’s methodology as a practical guide results in reduced project risks and better, faster, cheaper and easier solution delivery. CYSSC and IMAB want to share their success and experience so that you can leverage it for your own endeavors.

• Learn best practices for architecture development at the project level
• Understand how architecture fits into the overall project life cycle: who is needed when, what are the internal and external dependencies
• Get tips for planning project architecture activities: optimizing project resources, deliverables, activities, and timelines
• Get the tools and understanding to explain project architecture to Project Managers and Project Sponsors
• Hear directly from architects who have worked on real-world projects
• Bonus – Live demo of iPad using a case tool to quickly automate an architecture design from end to end

Ling Chen
Application Architect
Information Management and Architecture Branch
Children, Youth and Social Services I&IT Cluster

Ling is an I&IT architect with over 17 years experience in Information Technologies, nine of which are with government. After joined CYSSC from City of Toronto, she has focused on Enterprise Architecture. She specializes in architecture methodology research and real-world solution delivery.

Richard is an I & IT architect with a Master’s degree in Computer Sciences and 20 years of experience in Information Technologies. During the last 14 years his achievements have been mainly focused on architecture. He specializes in defining and applying roadmaps that support a full development lifecycle.

This presentation will introduce innovative enterprise architecture concepts and practices emerging in the Land and Resources I&IT Cluster. Enterprise Maps are discussed, showing how to represent and describe complex Ministry-wide programs, services, and processes linked to I&IT capabilities, both current and out-years. Four Enterprise Map layers will be covered describing what they contain and how they can be analyzed to support planning, initiative identification and portfolio management. Also discussed will be the ability to effectively communicate the complex and numerous relationships between, independent and non redundant, business layer elements (e.g., goals, mandate, functions, programs, services, processes, locations, organizations), and the supporting information, application and technology layer elements (e.g., information groups, applications, data stores, components, technology infrastructure). Key relationships considered are;

• Business functions “supports” goals,
• Business functions “involves” information groups,
• Business functions “implemented” by applications,
• Business functions “responsibility of ” organizations.

The presentation will conclude with a description of how LRC plans to use PowerDesigner V15 to draw Ministry-wide Enterprise Blueprints and make them available for access and analysis.

Les Piotrowski
Manager, LRC Architecture Framework
Ministry of Natural Resources

Les G. Piotrowski is the Manager, Land and Resources I&IT Cluster – Architecture Frameworks, based out of Peterborough, Ontario. Les graduated from Lake Superior State University, Michigan, with a Bachelor’s degree in Mathematics and Computer Science.

Chris Baker has been a System Consultant for Sybase and working with Sybase products for 14 years and in the IT industry for almost 20 years.

Chris has a B.A.Sc from University of Toronto in Chemical Engineering and worked for several years in industry before jumping to Information Builders as a consultant in 1990.

In his IT experience, Chris has gained in-depth knowledge of all areas of IT from database and data warehousing to applications and architectures in many industry verticals and customers, with a particular focus on Financial, Government and Telco.

One of the most significant challenges for implementation of an EA is lack of a consistent approach to program and project governance to successfully manage change and enforce controls. Successful EA programs require effective estimation of application project costs, systematic controls on both project delivery and EA conformance, and integrated procedures for planning the on-boarding of new business services. It is also important for Business owners, Architecture groups, Development teams, Operations, Risk & Compliance, and Service Management to break out of their silos, and speak the same language and understand their respective responsibilities and interdependencies to enable successful EA implementation and operation.

This session addresses these issues by describing industry best practices for how the Application Development Lifecycle relates to the IT Service Lifecycle, and the key areas where these disciplines need to interact. Key metric areas and control points are identified at each of the critical lifecycle stages, from Architecture to Service Introduction through to Operational system and Optimization. Benchmarks and maturity models are used to discuss the most effective way to introduce an EA governance framework. Throughout the session, a number of worked examples are used to illustrate processes and tools to address these issues based on practical field experience.

Piers McMahon
VP & Principal Architect, Enterprise IT Management
CA

Piers McMahon is a Vice President and Principal Architect at Computer Associates International, Inc. (CA) with responsibilities for best practices in process and architecture across CA’s Enterprise IT Management solutions, and with a specific focus on CA’s security, service management and governance technologies. Piers led the worldwide rollout of CA’s solution architecture methodology, and also the development of Enterprise IT Management process best practices. Piers works with large clients on security, service management, and governance solutions, and he participates in standards committees of DMTF, OASIS and IEEE-ISTO, and is a member of CA’s Council for Technical Excellence. Formerly a strategist with ICL-Fujitsu Systems, Piers joined CA in 1999, and brings over nineteen years experience in distributed systems architecture and engineering.

Piers graduated in Computer Engineering from Trinity College Dublin, and he holds patents in identity, access, and systems management, and regularly presents at industry conferences.

Risk management is the process of identifying, assessing, and taking steps to reduce risk to an acceptable level. A useable and effective risk management program should be an integral part of a balanced organizational wide IT strategy with the end goal being to enable the business to meet its mission and achieve defined objectives by ensuring a stable and secure IT environment. As such, systems risk management should not be treated solely as purely a technical function to be addressed by IT experts, but rather an imperative program which must be embraced and sponsored at the most senior levels of an organization. During this presentation, Wes Gill will:

• outline a foundation for the development of an effective risk management program
• provide practical guidance on how an organization can design a program to assess and mitigate risk within IT systems
• illustrate that a well constructed IT risk management program will ultimately prove to be a sound investment and an integral part of responsible and effective organizational leadership

Wes Gill
Executive Lead, Enterprise Risk Management
SAS

Projects implement changes to business process and technology (business, information, and IT). They establish a new base line for business operations whether the project is a green field startup or an enhancement of existing business operations. Project success is measured by:

• Going live with Release 1 of the new business operation as elegantly as possible within architecture, time and budget constraints
• Establishing the ability to design, deliver and implement future releases within the architecture, time and budget constraints

Project Architecture identifies the as-is environment, requirements, constraints, desired end-state and migration strategy(releases) for end to end integration of business, application, information, technology, security and privacy. The purpose of Project Architecture is to help:

• Maximize the Good projects,
• Avoid the Bad projects, and
• Minimize the Ugly projects

Fred Nagy
President
Solutions In Context Inc.

Fred Nagy is a Certified Management Consultant (CMC) with over thirty years experience in designing and implementing online business information solutions. Fred is president of Solutions in Context which is a business, information and IT management consulting firm. He has worked with the public sector as an architect, project manager, and management consultant since 1983. His focus is helping clients define enterprise service requirements and designing information management solutions to meet those requirements. He has helped the Ontario Public Sector, particularly the Ontario Government, with designing and delivering large projects, defining business requirements and solution architecture, conducting TRAs and PIAs, establishing program management infrastructure, defining Project/Business/IT workflow, and defining architectures and reference artifacts (e.g. Ministry Technical Architecture, Business Architecture, Security Architecture, Information Architecture, Business Rules, Information Management and Flow, Technical Reference Architecture). Fred’s experience includes over twenty years managing information, technology and management consulting practices for (Solutions in Context, Xpedior, Deloitte/DRT Systems and Polaris) which provided architecture and implementation for enterprise information infrastructure and application solutions to the Ontario Public, Health, Financial, Retail and Manufacturing sectors.

The OPS has identified significant risks related to applications across the government. These risks will impact service delivery to citizens and businesses in Ontario, and would prevent ministries from fulfilling their mandated purposes.

Over the past three years these risks have been identified and quantified, and plans were developed to address them. One mitigation strategy is to:

• simplify the application development environment
• reduce the number of supported products,
• reuse components and applications,
• develop common, reusable models and patterns that will lead to more consistency in the portfolio.

These strategies help achieve the goal of risk reduction, and offer other benefits as well: reduced time and effort in application development, and opportunities to achieve economies of scale in acquiring, implementing and supporting products. This session will focus on how common architecture reference models, patterns and standards are contributing to the overall goal of improving OPS service delivery through reduced risk.

Dave Harris
Manager
Major Application Portfolio Strategy
OCCTO

Dave’s IT career spans over 25 years in academic, private and public sectors. He joined the OPS in 1990, and held a number of positions in the Ministry of Culture, Community Services Cluster, Economics and Business Cluster, and most recently in the Office of the Corporate Chief Technology Officer.

Dave has been involved in the OPS architecture practice since its inception in the late 1990s. Working with the Ministry of Education, he helped lead one of the first ministry-wide change initiatives. He worked as Lead Security Architect at EBC, and acted as manager of consulting architecture in OCCTO.

For the past two years, Dave has been working on the Major Application Portfolio Strategy, assessing the portfolio of applications across the government, and advancing remediation plans for the highest-risk of them.

Joe Fernandes is the Enterprise Application Architect, Corporate Architecture Branch, Office of the Corporate Chief Technology Officer, Ministry of Government Services. Joe provides architectural guidance/directions/recommendations for implementing effective enterprise application architectures, and related policies, procedures and technologies for the I&IT environments within the OPS. He has been an IT professional for over 20 years and his work experience covers the full range of IT domains including architecture, application development, network/infrastructure design and project management. For the past few years, Joe is a strong proponent of Enterprise Architecture and has been instrumental in promoting the merit and value of enterprise reusable services/components.

Dean has accumulated a wealth of knowledge over the last 20+ years as an IT professional. He has successfully developed and implemented projects ranging from distributed client server applications to centralized corporate systems. He currently leads and/or guides project teams in the development of business architecture. He has been involved in the development of enterprise architecture methodologies since the OPS Enterprise Architecture program's inception in 1998. He ensures that the creation of contextual and conceptual models comply with the Government of Ontario Enterprise Architecture Process & Methods Handbook.

To meet the needs of its clients, Statistics Canada conducts about 350 surveys annually. The collection of survey information is conducted through a number of regions and a variety of modes. Facing a number of issues in data collection, Statistics Canada used an Enterprise Architecture (EA) approach to reorganize the people, processes and technology that support the Collection function.

In this session, you will learn how Statistics Canada used EA to:

• address challenges in data collection service levels, including consistency, timeliness, response rates, data quality and service efficiency;
• improve management of the overall collection processes both within and across surveys;
• reduce transformation risk by articulating a target design and developing a roadmap to bridge the gap between the current and planned organization

Jeff Smith
Partner
KPMG

Jeff started with Chartwell in 1995. His business and relationship development background, as well as his natural leadership ability and drive, has been a strong complement to Chartwell’s senior team.

Jeff not only brings a tireless attitude to developing relationships and corporate reputation, he was very focused on community development and Chartwell’s leadership in corporate social responsibility. For the past eight years, Jeff has committed to bringing non-profit, government and business leaders together for the resolution of Toronto’s homeless issue.

Jeff led the Chartwell management team in planning and implementation of business strategies, as well as the realization of Chartwell’s vision as a leading business design, IT strategy and implementation management firm, known nationally and abroad.

Jeff will continue to provide leadership to the Chartwell team, under our new umbrella as KPMG’s first EA Practice, assisting in setting best practice in Canada and abroad.

IT Platforms are what we build solutions on and the evolution of those platforms continues: from mainframe to PC to client / server to web based solutions. The latest one we are starting to hear a lot about is Cloud Computing – and despite many of us Enterprise Architect’s nagging suspicions that there is a lot more hype than reality this platform is already starting to affect how our organizations collaborate, communicate, and provide services to our stakeholders.

While it’s impossible to truly see into the future we can begin to make educated guesses about how Cloud Computing will start to affect our organizations and ourselves as EA’s. In particular, we as a discipline need to start looking at this new platform type and begin to consider how it helps the business drive architecture, how it will change internal communication and collaboration, and how we as EA’s will need to evolve over the next 10 years and beyond in order to leverage capabilities that will become essential to our organization’s health.

At the end of the discussion attendees should:

• Have a better idea of the context in which Cloud Computing is being offered today and likely ways it will be offered in the future
• How organizations are already taking advantage of Cloud Computing today and the likely ways this will evolve how IT departments offer services in the future
• Issues that we EA’s need to anticipate as Cloud Computing evolves in the present and in the future

Dave Remmer
Architect Advisor
Microsoft Canada

An industry veteran, Dave Remmer has architected solutions in the financial, multi-media, security, manufacturing, services and health care industries. He specializes in leveraging SOA, security, and standards development to realize ongoing business value within organizations. Dave focuses on current issues in architecting enterprise solutions and how to leverage the Microsoft platform to support client’s project’s architectural success. He has achieved the Sun Certified Java Programmer and Sun Certified Java Architect as well as the Microsoft Certified Solution Developer designation.

This presentation provides an introduction and demonstration of OCCTO’s Enterprise Architecture self-service tool. The tool is placed in the context of the other sources of architecture related information offered by OCCTO. It outlines the purposes of the tool, and demonstrates how it may be used to view architecture from three perspectives:

• Why - An overview of architecture;
• What - Requirements for passing each checkpoint;
• How - Insights on selecting and completing the architecture documents required at each checkpoint.

Dale Hunter
Methodology Specialist
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Dale Hunter is the Methodology Specialist in Corporate Architecture Branch, Office of the Chief Corporate Technology Officer. Dale is a graduate of McGill University and has been a member of a number of professional associations. Prior to joining MGS in 2002 he held a variety of business and I&IT positions with the Ministry of Health and Long-Term Care and with the Human Services Cluster.

Description: GSDC has over the past 9 months launched a series of service delivery innovation initiatives to support the objectives of MTI 3:3:4 and the upcoming Guelph Data Center Transition. This workshop will focus on the cluster's Quality Management initiative , developed in support of the cluster's 10 managed client IT Portfolios, that was designed in alignment with OPS I&IT Policy and Directives. The session will include a review of the following:

• GSDC Gateway Review Committee (GGRC), an Integrated Quality Assurance team and process with membership across all cluster branches
• GSDC Quality Assurance (QA) Checklist for Project Managers
• GSDC Project Development Lifecycle Model
• GSDC IT Portfolio/Program Management Governance and Technical Knowledge Management

Brad Cowls
Manager, I&IT Enterprise Planning
IT Service Management
Ministry of Government Services

Brad has a Master's Degree in Canadian Political History and 23 years of service to Ontario taxpayers within the Ontario Public Service completing public policy and planning activities. Most recent work has been in the GSDC Enterprise Strategy and Planning Practice in implementing the GSDC quality assurance initiative, I&IT project gating methods and governance, and managed all I&IT planning activities within the cluster.

Master Certified Architect and IBM Distinguished Engineer. 20 years working within the public sector on strategy, design, planning, implementation and support of I+IT Solutions. Most recent work with GSDC Enterprise Strategy and Planning Practice, OCCTO, OCIPO and ITPC on the development of the GSDC Quality Assurance, Information Management and Architecture Practices and supporting process models, governance teams and guidelines.

Business areas must manage risk appropriately in order to deliver secure and available services to the Ontario public. This presentation will introduce the participants to the basic concepts of the threat risk assessment process. You will learn when a risk assessment is required, how it fits into the SDLC and project gating processes. Most importantly, you will understand how a risk assessment can benefit your project by providing strategies to reduce risk, prioritizing actions and cost justifying security expenditures. We will show how to leverage the recommendations from a Threat Risk Assessment to proactively reduce risk to your service. Finally, the role of Threat Risk Assessments in the broader risk management toolkit will be examined.

Mano Pancharatnam
Security Design
Corporate Security Branch, Office of the Corporate Chief Information Officer
Ministry of Government Services

Mano joined the Ministry of Government Services Corporate Security Branch in 2002. As an acting coordinator for the security design team, Mano is responsible for reviewing IT solutions, assessing security risks and providing advice to various projects on security standards compliance. Mano has been working in the IT security field for the past 10 years. He ensures the provision of timely and authoritative advice and support to cluster security and OPS client ministries in securing their information systems are secure.

With over 23 years in IT Security Pat Antliff has been with what is now Corporate Security Branch, MGS, since its inception. As the Coordinator for IT Risk Management Services, Pat is responsible for delivery of Threat Risk Assessments and Business Impact Assessments to all clusters across the OPS. During the past year she has been working on transforming the TRA process to better meet business needs. She views Threat Risk Assessments as an integral piece to the SDLC enabling effective and secure program delivery to Ontario citizens through proactive risk management.

The Integrated Financial Information System (IFIS) is an enterprise approach to transforming Financial Management within the OPS, including associated policies, processes, systems, skills and organization. IFIS is the Ontario government’s single, authoritative source for financial management information and reporting, as well as for revenue, expenditure, asset and liability management processing. The Enterprise Financial System Business Architecture project used business architecture as the basis to:

• Document the systems and components required to deliver the Financial Management Strategy as the foundation for an as-is and to be technology blueprint/reference architecture which will refresh the IFIS IT Architecture (2000 and 2003)
• Support and extend IFIS as the recognized IT solution for enterprise financial management as defined within the project scope;

Russ Whitehead
Head, Applied Architecture
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Information Management (IM) is a strategic priority, a transformation enabler and risk-reduction area for the Ontario Government. IM is increasingly important to institutions as is evidenced in current industry reports. In the Ontario Government Enterprise Architecture (EA) has the mandate, maturity, governance and practice standards and methods in place as well as the Information Architecture based skill set critical to enabling IM. In turn, IM brings recorded information/records management understanding that benefits EA in areas such as EA repository work, yet is still new-on-the-scene in terms of strategic priorities. The experts (Gartner, Burton, etc.) are telling us IM needs to build on and become part of EA (and not just on the IA side). This presentation will discuss:

• How has that been done successfully?
• Where is it working this marriage of IM and EA?
• What are the risks if we don't dovetail EA and IM practices and priorities?
• How does EA/IM partnership work elsewhere and where/how can we do it in the OPS?
• What are the benefits to Ontario residents and Ontario Government workers?

Brady Thompson
Policy Advisor
Office of the Chief Information and Privacy Officer

Brady Thompson has over 25 years experience in information technology, public policy and economics, information management and standards and IT security and privacy in the public and private sectors in the UK and Canada. His experience includes identity policy lead for the Office of the Corporate Chief Strategist, Lead for Security Architecture, Planning and Architecture for the Community Services I&IT Cluster, and economic policy lead for immigration for the ministry of Citizenship. In spring 2009, along with colleagues from the Ontario Government, he will deliver a course on Information Management Governance at the University of Toronto.

Are the discussions on the benefits of Open Source Software (OSS) shifting from decreasing cost to architectural values such as flexibility, performance, reliability? What are the architectural impacts of using OSS, especially in the area of integration?

Rizwan Akhtar
Manager, Breakthrough Technologies Unit, Technology Adoption Branch, OCCTO
Ministry of Government Services

Eion Gomes
Head - Technology Adoption Branch, OCCTO
Ministry of Government Services
Office of the Corporate Chief Technology Officer

Security architecture has, as its focus, the production of the authoritative set of artefacts used to manage complexity in system design enterprise wide. The extent to which these artifacts influence design-related considerations is a function of their usefulness to expose security-related anomalies in conceptual, logical and physical design phases of a project.

State modeling is one such technique. The presentation will look at information security and security architecture as complementary disciplines, state modeling fundamentals, notation, methodological considerations and, through example, underscore the value proposition delivered to the business in managing security risk. It will be of particular relevance to security architects and business management alike.

Murray Rosenthal
Senior Policy Analyst
City of Toronto

Murray Rosenthal, CISA, is a well-regarded information security practitioner with 20 years of experience in the information security profession. He is known for his thought leadership in the areas of information security strategic planning and information security management systems, as well as state modeling and breach vector identification across the domain architectures of business, information, application, technology, security and privacy. Murray is also responsible for leading-edge thinking on security-related aspects of the Zachman Framework, described by John Zachman as “especially innovative”.

The presentation will describe the OPS environment for Enterprise Architecture (EA) Security Architecture, why we do Security Architecture, the challenges, it’s value, and benefits. The presentation also describes the context of Security Architecture domain in the EA process, Framework, modeling, and Gating. As well, the presentation will discuss in detail Security Principles, Standards, Practices, measures and metrics, and provide an OPS initiative example.

Colin Easton
Security & Technology Architect
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Colin joined the OPS six years ago in the Corporate Architecture Branch of OCCTO within MGS, as a Security and Technology Architect providing expertise in Technology and Security architecture as it pertains to Information and Information Technology (I&IT). He’s previously held the chair of the government ACT Security Architecture Domain Working Group. Colin has over 16 years experience in IT in public and private enterprises. He’s worked for the Bank of Montreal, Roger’s Communications and Netcom. He also is certified as an Information Technology Security Auditor.

This presentation is focused on highlighting the value of business architecture, not only for IT solution development but as a valuable business asset for planning and knowledge management. You will be able to understand the real meaning of terms like ‘re-usability traceability’, ‘transformation’ and ‘baseline brought to life’. You will also see how a complex business can be fully and precisely described with a concise set of models that are clear and easy to understand. Join John Lynch and Richard Pelletier as they:

• Illustrate traceability and alignment between business processes, rules, and data, roles and accountabilities as well as the dimensions of time and location,
• Reinforce the importance and value of a re-usable enterprise baseline, i.e. a documented business architecture that can be re-used for future projects in this program area, which would reduce the work effort required to meet architecture guidelines and allow for quicker development of more cost effective solutions,
• Demonstrate the power of case tools to support the efficient and effective use of Enterprise Architecture.

Richard Pelletier
Information Architect
Information Management and Architecture Branch
Children, Youth and Social Services I&IT Cluster

Richard is an I & IT architect with a Master’s degree in Computer Sciences and 20 years of experience in Information Technologies. During the last 14 years his achievements have been mainly focused on architecture. He specializes in defining and applying roadmaps that support a full development lifecycle.

John Lynch has over 30 years experience in the OPS, mainly with the Ministry of Transportation, and has led numerous business architecture initiatives for MTO and in conjunction with ServiceOntario, MOHLTC, and the Ministry of Labour over the past 5 years.

The presentation gives an overview of the changes made in the past year to our architecture practice. EA Methodology and the five architecture domains have contributed to significant improvements and efficiency gains at both the corporate and project levels. The presentation seeks to explain the rationale for those changes and to advise project architecture teams how to capitalize on the timesaving features of those updates.

Dale Hunter
Methodology Specialist
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Dale Hunter is the Methodology Specialist in Corporate Architecture Branch, Office of the Chief Corporate Technology Officer. Dale is a graduate of McGill University and has been a member of a number of professional associations. Prior to joining MGS in 2002 he held a variety of business and I&IT positions with the Ministry of Health and Long-Term Care and with the Human Services Cluster.

Joe Fernandes is the Enterprise Application Architect, Corporate Architecture Branch, Office of the Corporate Chief Technology Officer, Ministry of Government Services. Joe provides architectural guidance/directions/recommendations for implementing effective enterprise application architectures, and related policies, procedures and technologies for the I&IT environments within the OPS. He has been an IT professional for over 20 years and his work experience covers the full range of IT domains including architecture, application development, network/infrastructure design and project management. For the past few years, Joe is a strong proponent of Enterprise Architecture and has been instrumental in promoting the merit and value of enterprise reusable services/components.

This presentation will focus on the use of Quality Factors in system definition. We will discuss how they can be used to clarify general system requirements and surface some of the associated risks. This then leads to a better specification of a system's characteristics and improved understanding between business and IT. This presentation will focus on:

• Basic purpose and intent: What are the benefits?
• Definition and types of Quality Factors: A tour of all the "-elites"
• Recent streamlining of Quality Factors in EA artifact templates: Improvements that have been made to some artifact templates
• Quality Level Metrics and Examples: How to measure and quantify Quality Factors
• Common misunderstandings and omissions: What are some of the nuances and pitfalls?

Peter Churchard
Security & Technology Architect
Office of the Corporate Chief Technology Officer
Ministry of Government Services

Peter Churchard has 27 years of experience in IT, both in the private and public sectors. He joined the OPS in 1990 and has worked for the Ministry of Environment and for MBS/MGS at OCCSD and, most recently, OCCTO. For the last eight years he has worked in the Corporate Architecture Branch as a Security/Technology Architect. Prior to joining the OPS, he worked in the telecommunications industry for companies in the UK, Canada, and the US.