On Thursday December 5th
we have the inaugural meeting for the Atlantic Canada Association of IT Architects (ACAITA). We really are at the beginning of the formation of the group... so far I have been surprised by the response. We have five people committed to the first meeting at the Georgetown pub, and a whole lot of interest from Atlantic Canada. All counted over 10 people have contacted me expressing interest in and supporting the idea of Atlantic Canada Association of IT Architects (ACAITA). To get more details of the meeting look to the meetup invite
. The meeting agenda covers the following themes;
I hope we all take the time to introduce ourselves to each other. Reach out... enjoy the company of the others who are leaning toward IT architecture.
There are way more architecture frameworks than most people are aware of. The ISO Architecture group has put together an excellent list of frameworks which can be found here
. The two frameworks I find most useful, are;
- TOGAF - an Open Group Standard, is a proven Enterprise Architecture methodology and framework used by the world's leading organizations to improve business efficiency.
- Zachman - The Zachman Framework™ is a schema best understood by reading many of the artifacts made available by Zachman International.
There are a number of groups, professional associations, etc. involved with developing and forwarding the practice of IT architecture. The ones I see most important to developing an IT Architecture association are as follows; (I am open to discussing more than these five groups when it comes to how we align the association, everything that deepens architectural understanding is good for all of us).
Roles of the Architect
- IASA - An association for all IT Architects
- OpenGroup - Vendor neutral IT standards and certifications
- EAE - Association of Enterprise Architects
- EACOE - Enterprise Architecture Centre of Excellence
- FEAC - Training and Certification Institution for Enterprise Architects
- ISC - Vendor-neutral education products, career services, and Gold Standard credentials to professionals.
There are many roles for the IT Architect. And they all have a place in getting projects to finished... When you read over the different group sites (above) you will begin to get a sense there are a lot of definitions for architects. Listed below are how I see the collection of different architecture role definitions.
- Solution Architect - focused on the architecture for a particular solution built to meet a defined business need and / or business strategy.
- Enterprise Architect - aligning IT architecture with business strategy. More focused on governance.
- Application Architect - specifying the architecture for a particular software application. Differs from Solution Architect in that the application is for a specific business domain, where the solution architect is focused on a business need and evaluates many applications to fulfill the need.
- Component Architect - designs and architects complex and mission critical software components.
- Technical Architect - takes on the technically challenging aspects of engineering a software solution. Optimizes the design for reuse, performance, etc.
- Database Architect - specializes in architecting data storage solutions.
- Infrastructure Architect - focused on the server, networking and infrastructure architecture.
- Security Architect - focused upon all things security within IT.
- Information Architect - organizing and architecting information for usability.
- Business Architect - plays a key part in shaping and fostering continuous improvement, business transformation business innovation initiatives.
See everyone at the Georgetown Pub, 8:00 pm, Thursday December 5th...
- Growing the Community.
- Preparing for the Google Hangout.