Chapter 24: Architecture Competence

Slides:



Advertisements
Similar presentations
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Advertisements

Knowledge Strategy & Leadership Intellectual Capital Management Organizational Culture and Communicaiton Collaboration and Community Building Knowledge.
Software Architecture in Practice
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
The Many Contexts of Software Architecture
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
Human Resources Management
S/W Project Management
Copyright Course Technology 1999
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Software Project Management Introduction to Project Management.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
Ways for Improvement of Validity of Qualifications PHARE TVET RO2006/ Training and Advice for Further Development of the TVET.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Lecture 7: Requirements Engineering
Georgia Institute of Technology CS 4320 Fall 2003.
Formulating a Simulation Project Proposal Chapter3.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
BSBPMG506A Manage Project Human Resources Manage Project Human Resources Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
33 3. IS Planning Issues Scope of IS planning Barriers in IS planning Overview of IS planning Inputs to IS planning Process of IS planning Outputs from.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Software Engineering Lecture 10: System Engineering.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Building a SW Architecture Group Tomer Peretz Chief Software Architect.
Building a BA Center of Excellence Gain Momentum...Produce Results!
Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
Chapter 12: Other Quality Attributes
Project Management What is Project Management?
Chapter 7: Modifiability
Quality Attribute Modeling and Analysis
Software Quality Control and Quality Assurance: Introduction
Chapter 3: The Many Contexts of Software Architecture
Project Management (x470)
Chapter 17: Designing an Architecture
Lecture 17 ATAM Team Expertise
Project Integration Management
Chapter 11: Usability © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
TechStambha PMP Certification Training
Chapter 19: Architecture, Implementation, and Testing
IEEE Std 1074: Standard for Software Lifecycle
Epilog © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
Chapter 22: Management and Governance
Chapter 25: Architecture and Product Lines
CMMI – Staged Representation
Software Engineering (CSI 321)
ITSM Governance is Imperative to Succeed
Software Project Management
EOSCpilot Skills Landscape & Framework
Chapter 1 (pages 4-9); Overview of SDLC
Project Management Process Groups
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
Chapter 1 INTRODUCTION TO MANAGEMENT AND ORGANIZATIONS
Management and organization
Software Reviews.
Project Management and the Organization
Systems Architecture and Engineering
Bridging the ITSM Information Gap
Bridging the ITSM Information Gap
Presentation transcript:

Chapter 24: Architecture Competence © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Chapter Outline Competence of Individuals: Duties, Skills, and Knowledge of Architects Competence of a Software Architecture Organization Summary © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Competence of Individuals Skills Knowledge Duties © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Technical Duties of an Architect General Duty Specific Duties Architecting Creating an architecture Evaluating and analyzing an architecture Documenting an architecture Working with and transforming other systems Performing other architecting duties Other life cycle activities Managing the requirements Implementing the product Testing the product Evaluation future technologies Selecting tools and technology © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Non-Technical Duties of an Architect General Duty Specific Duties Management Managing the project Managing the people Supporting the management Organization and business related duties Supporting the organization Supporting the business Leadership and team building Providing technical leadership Building a team © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Skills of an Architect General Skill Area Specific Skills Communication skills Outward Inward Interpersonal skills Within team With other people Work skills Leadership Workload management Skills to excel in corporate environment Skills for handling information Skills for handling unexpected © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Knowledge of an Architect General Knowledge Area Specific Knowledge Computer Science knowledge Architecture Software Engineering Design knowledge Programming knowledge Technology and Platforms Specific knowledge General knowledge Organization context and management Domain knowledge Industry knowledge Enterprise knowledge Leadership and management techniques © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Organizational Competence It is not enough for the architect to be competent The organizational setting is usually outside the control of individual architects. The architect must operate in an environment that understands how to create/nurture/reward architects. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Some Examples of Activities by a Competent Organization Establish a career track for architects. Establish a clear statement of responsibilities and authority for architects. Establish a mentoring program for architects. Establish an architecture training/education program. Include architecture milestones in project plans. Have architects provide input into product definition. Have architects advise on development team structure. Give architects influence throughout the entire project life cycle. Reward or penalize architects based on project success or failure. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Assessing an Organization There are three practice areas that can be used to assess an organization's competence. Software Engineering Technical Management Organizational Management © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Software Engineering Organizations should have defined practices for Quality Attribute Elicitation Tools and Technology Selection Modeling and Prototyping Architecture Design Architecture Description Architecture Evaluation System Implementation Software Design (design conforms to architecture) Software Coding (code conforms to design and architecture) Software Verification Proving Properties of the Software Software Testing © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Technical Management Organizations should have defined practices for Business or Mission Goals Setting goals Setting functional requirements Allocating Resources Setting architect’s workload and schedule Funding stakeholder involvement Project plan structure aligned with architecture structure. Adequate time planned for architecture evaluation. Establish organization-wide architecture practices Process monitoring and improvement Reuse Collaboration with manager © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Organizational Management Organizations should have defined practices for Career track for Architects Leadership roles for architects Succession planning Ongoing training Creating and sustaining an internal community of architects Supporting participation in external communities Organizational Planning Technology Planning and Forecasting © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Questions within Competence Categories Within each competence category one can have questions to evaluate how well an organization measures against particular criteria. E.g. How do you ensure that the architecture is aligned with the business goals? What is the input into the architecture creation process? What inputs are provided to the architect? How does the architect validate the information provided? What does the architect do in case the input is insufficient or inadequate? © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Assessment in Practice Based on these kinds of questions, skilled evaluators can assess the organization’s competence The output is a list of strengths and weaknesses. The weaknesses can lead to an improvement plan. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Summary Individuals need to have particular knowledge and skills as architects. These lead to duties. Organizations need to provide an environment that supports architects, creates new architects, and evaluates and rewards successful architects. All of this can be evaluated, to help guide an organization to improve its organizational competence. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License