We're calling on Fabio Castiglioni, an Executive IT Architect with IBM Sales and Distribution and an instructor of Component Modeling classes for IBM architects. His latest article, Enterprise architecture in the age of cloud services, was born from one of his latest client situations.
What inspired you to write an article on this specific topic?
I have a client who wants to move to a Cloud SaaS Service Provider role, so I put myself in the shoes of my client's end users to work through the situation.
How do you gather requirements for a project?
I trust objective inputs - such as an analysis of the domain (business, process and functional), the client's strategic direction, and the technical environment - more than subjective information, such as interviews with single stakeholders.
What communities, forums or user groups do you turn to for help or technical insight?
I rely on my own network of technical leaders. For methodology-related advice I turn to Pete Cripps (the author of IBM Component Modeling methodology) and Philippe Spaas (the author of IBM Operational Modeling methodology, and of the SDS Modeling Standard)
What is the one action you have taken that has accounted for most of your success?
More of a course of action, I received good advice from my first manager: To always look for activities that are challenging but that I will enjoy doing.
How do you handle obstacles and roadblocks?
I'm usually very outspoken, but I make any effort to listen and find the good in opposing ideas.
Fabio is inspired by foundations learned in The Process of Software Architecting by Peter Eeles & Peter Cripps. In his spare time, he enjoys History, especially the late Roman Empire-Early Middle Ages.
Many of the courses and past articles from Fabio are about nonfunctional requirements. How do you gather requirements for a project? Let Fabio know in the comments.