Mario Cardinal

Software Architect

The real voyage of discovery consists, not in seeking new landscapes, but in having new eyes

This paper presents the full spectrum of roles that software architects must fulfill when building enterprise applications.

IT shops must fulfill two roles: to "build" and to "run" software. Each role requires a different set of skills. The gap between "build" and "run" is almost always clearly visible in the organization chart. At the architecture level, on one side, there are the application architects involved in software development (build), and, on the other side, the infrastructure architects involved in software operation (run). Being an application architect, I believe that both teams should learn from each other's best practices. One best practice that the infrastructure team should learn from the software-development team is to express architecture decisions using test scripts.

The reasons why I think TFS is a "first-class" citizen in regard with agility.

This paper classify team attributes express in Ray Immelman book Great Boss, Dead Boss according to Maslow’s hierarchy of human needs. I have identified how these team attributes can easily be reinforced using agile software development process. I conclude this paper by proposing to supplement agile software development process with improvement in order to encourage these team attributes to emerge.

This paper discuss the benefits and the challenge of the OMG's Model Driven Architecture initiative in terms of ROI rergarding UML and software development tools.