The role of an architect (Architectural Journal)

The debate of what an architect is, what he should do and how to become one seems to go on and on and on. Still some people I meet struggling with these questions have not learned about the Architectural Journal and the excellent issue about "The Role Of An Architect".

So, again, you can read all about this role here (English PDF Version).

================

Articles in This Issue
We Don't Need No Architects
by Joseph Hofstader
This article presents a defense of the practice of architecture in software development, and examines widely held perceptions of architects and some of the mistakes that they make that contribute to negative perceptions.

Becoming an Architect in a System Integrator
by Amit Unde
In this article, the author attempts to crystallize the wisdom that he has gathered from his work in a program in which he grooms aspiring architects into full-fledged architects.

Architecture Journal Profile: Paul Preiss
Paul Preiss is the founder of a nonprofit group called IASA (International Association of Software Architects). Read about the goal of the organization, as well as some of Paul's thoughts about the profession.

The Open Group's Architect Certification Programs
by Leonard Fehskens
How do you know if someone is really an architect? This article describes The Open Group Architecture Framework (TOGAF); the TOGAF certification program; and certification levels, programs, and process.

The Need for an Architectural Body of Knowledge
by Miha Kralj
This article covers why an Architectural Body of Knowledge (ArcBOK) is an important building block in professionalization of IT Architecture, and how the Microsoft Certified Architect community drives the creation of an ArcBOK through its Special Interest Group.

A Study of Architect Roles by IASA Sweden
by Daniel Akenine
In this article, we examine the need for IT architects, describe a study by IASA Sweden to better understand IT architecture, and discuss four architect roles that IASA Sweden recommends for a typical organization.

The Softer Side of the Architect
by Joe Shirey
This article outlines a framework that the author developed for defining "soft skills" and strategies for the architect, based on his experiences and interactions with architects that he admires.

An A-Z Guide to Being an Architect
by Mark Bloodworth and Marc Holmes
These days, an architect has a lot of diverse responsibilities. In this article, the authors provide a handy A-Z guide to being an architect, and wish that all your architectures be "n-tier".

Architecture? Who needs it!

I just read an blog-post that contained a knifesharp graphical summary that seemed all too familiair to me. I just had to share it.

Source: Nick Malik.

Full Skills Package For The IT architect (IASA)

De "International Association of Software Architects" (IASA) is bezig met het inventariseren van de kwaliteiten en kennis die een IT Architect zou moeten hebben.

Met deze lijst kun je vrij snel afvinken op welke onderdelen je sterk bent en aan welke onderdelen je eventueel nog zou kunnen werken: cursussen moet volgen en ervaring moet opdoen. Ook kan het uistekend dienen voor het vormgeven van je eigen (toekomstige) functie want veel bedrijven hebben de functie nog niet opgenomen in hun functiehuis is mijn ervaring.

Business-Technology Strategy
· Business and Technology Strategy Rationalization
· Business Capability Mapping
· Business Fundamentals
· Business Process Engineering and Business Process Management (BPE/BPM)
· Business Valuation
· Contracts
· Industry Analysis
· Intellectual Property
· Investment Prioritization and Planning
· Requirements and Constraints Analysis
· Technology Capability Projections and Planning

Design Skills
· Architectural Description
· Architecture Styles
· Architecture Viewpoint and Views
· Context
· Design Diagramming, Notation and Deliverables
· Design Methodologies
· Design Methodology Evaluation and Review Practices
· Domain-Specific Modeling Languages
· Optimization Techniques During Design
· Patterns and Best Practices
· Prototypes
· Reuse
· Synthesis and Problem Solving
· Traceability Throughout The Life Cycle

Human Dynamics
· Conflict Management
· Crisis Management
· Customer Relations
· Leadership
· Mentorship
· Negotiation Skills
· Peer Interaction
· Politics
· Presentation Skills
· Selling Skills
· Situational Awareness
· Team Building and Management

Infrastructure Architecture
· Access and Identity Management
· Capacity Planning
· Common Application Services
· Device Management and Provisioning
· Messaging Standards
· Network Design
· Support Processes and Tools
· System Tuning

IT Environment
· Capability Development, Training and Management
· Capability Mix Identification
· Compliance: Audits, Certification, Licensing and Regulation
· Cost Estimation and Tracking
· Dependency Identification and Management
· Engineering
· Governance
· Infrastructure Landscape
· Knowledge Management
· Maintenance and Support
· Operational Management
· Operations
· Organizational Dynamics
· Organizational Structure
· Outsourcing
· Resource Balancing and Management
· Stakeholder Definition
· Vendor Management
· Virus and Patch Management

Quality Attributes
· Implementing Quality Attributes
· Manageability, Maintainability and Supportability
· Monitoring Quality Attributes
· Performance, Extensibility, Flexibility
· Quality Attribute Auditing
· Reliability, Availability, Scalability
· Security
· Usability, Localization, Accessibility, Personalization/Customizability

Solution Architecture
· Application Layering
· Asset Management Systems
· Business Intelligence
· Change Control
· Customer Information and Relationship Management (CIM/CRM)
· Development and Build Environments
· End-to-End (E2E) Test Design and Implementation
· Implementing the User Experience
· Information Architecture
· Integrated Development Environments (IDEs) and Modeling Tools
· Localization
· Mainframe Development and Design
· Messaging Technology
· Mobile Platforms and Frameworks
· Personalization
· Programming Languages
· Proof of Concept Design
· Service Network
· Solution Architecture Design Methodologies
· Solution Architecture Design Patterns
· Solution Architecture Development Methodologies
· Solution Architecture Specialities
· Solution Architecture Tools
· Technology Frameworks
· Transactions
· User Experience
· Workflow

(Bron: http://www.iasahome.org/web/home/taxonomy)

Architectuur is de oplossing, maar wat was het probleem?

Als Architect kom je maar al te vaak in een situatie dat je moet uitleggen wat een Architect doet en wat de voordelen van Architectuur zijn.

Als je, net als ik, hiervoor een presentatie mag maken dan komt de volgende presentatie van het IMN (Informatie Management Nederland) je vast goed van pas!

De presentatie is in twee delen opgebouwd:
- Deel 1 geeft de algemene lijn van de IMN visie op architectuur-toepassing weer
- Deel 2 gaat concreet in op het gebruiken van de IMN-visie bij het toepassen van architectuur voor een specifieke probleemsituatie





Klik hier voor de PowerPoint.

Instructie video's van Microsoft

Hieronder een overzicht van instructievideo's van Microsoft gericht op de beginnende Software Architect.


Transitioning from a developer to an architect

http://msevents.microsoft.com/cui/eventdetail.aspx?EventID=1032338980&culture=en-CA

Are you a developer who would like to learn more about becoming an architect? Or how to get formally recognized as one (since you already wear the design and architecture hat along with the developer one)?. Join Mohammad Akif for the fourth and last part of the series focused on aspiring architects, during this session we will discuss how you can attain the skill set required to be an architect and sell yourself as an architect within your organization and industry. We will also provide a list of resources that you can use to continue the transition from a developer to an architect role.


Architecture 101

http://msevents.microsoft.com/cui/eventdetail.aspx?EventID=1032338971&culture=en-CA

Agenda

• Types of architects
• Role of an architect
• Why become an architect
• When not to become an architcet
• Attributes of an architect
• What an architect is expected to know
• How to ben an effective architect

Omschrijving

Architecture is the balance between art and engineering, it requires a certain mindset and approach to solving problems. Architects often function as a bridge between the business users and development groups and are increasingly being recognized as a critical community within organizations. Becoming an Architect can often translate in to an elevated status from a career stage perspective but it is hard to find prescriptive guidance around how to become an architect. Join Mohammad Akif for the first of a four part series focused on aspiring architects. During the Architecture 101 session we will discuss some key ideas around Architecture and define attributes of an architect.

Software development lifecycle and methodologies

http://msevents.microsoft.com/cui/eventdetail.aspx?EventID=1032338974&culture=en-CA


Over the years the various approaches teams have used to develop software have evolved. Join Dave Remmer in the second of a series focused on aspiring architects where we will discuss the various stages projects go through and sample some of the methodologies used by teams developing software. In this session we will compare and contrast the waterfall, agile, RUP, Scrum and MSF methodologies and how they are used within software projects.



Services orientation and other architectural paradigms

http://msevents.microsoft.com/cui/eventdetail.aspx?EventID=1032338978&culture=en-CA


One of the hottest topics in software architecture is the services oriented approach to building solutions and how this can provide agility, flexibility and reuse. Join Dave Remmer in the third of a series focused on aspiring architects where we will be looking at approaches to architecting software. This session will give an overall description of service orientation and how it differs from object oriented and component based architectures as well as a discussion of some of the organizational challenges teams experience when using a services oriented architecture.

Persoonlijke kenmerken van een architect

Wanneer men architecten in de praktijk vraagt naar de gewenste architectcompetenties, dan noemt hij of zij meestal persoonskenmerken. In de psychologie worden persoonlijkheidskenmerken in vijf groepen verdeeld, die bekend staan als de Big Five factorstructuur (Goldberg. “An Alternative "Description of Personality": The Big-Five Factor Structure”. Journal of Personality and Social Psychology 1990).

Classificeren we de meest genoemde persoonlijkheidskenmerken in deze big five, dan ontstaat het volgende beeld.

1. Extravertie.
• Communicatief
• Initatiefrijk

2. Aangenaamheid
• Teamplayer
• Empatisch (andermans standpunt kunnen invoelen)
• Luistervaardig

3. Betrouwbaarheid.
• Analytisch
• Georganiseerd, systematisch en ordelijk
• Besluitvaardig
• Resultaatgericht

4. Emotionele stabiliteit
• Zelfstandig

5. Intellect (reflectie).
• Creatief /innovatief
• Abstractievermogen
• Zichzelf blijven ontwikkelen

Deze lijst bevat alleen kenmerken die meerdere keren genoemd zijn. De volledige lijst is veel langer. Maar de lijst is al lang genoeg om ons af te vragen welke architect dat toch is die al deze eigenschappen heeft. Ik ken in elk geval niemand die ze allemaal heeft. Wel kan ik enkele herkenbare types architecten uit deze lijst afleiden. Twee contrasterende architecten die sommige, maar niet alle van deze persoonskenmerken hebben, zijn:

• De masculiene architect: resultaatgericht, besluitvaardig, met overtuigingskracht;
• De feminiene architect: een sensitieve teamplayer die goed luistert.

Twee andere types zijn die van de artiest versus de boekhouder:
• Artiest: Iemand die op hoog abstractieniveau creatieve oplossingen voorstelt;
• Analyticus: Iemand die nauwgezet en systematisch problemen analyseert en
oplossingen uitwerkt.

Bron: competenties van ict architecten (utwente)