zachman

I still believe that most practitioners will find Zachman to be a handy analysis reference during their work.

Amid the swarm of overlapping methodologies, these stand apart as three pillars of modern information systems architecture.

For example, it would be questionable to use Zachman in a development environment by virtue of its inherent unsuitability.

The Zachman Framework incorporates neither a notation nor a process, nor does it impose limitations on their selection.

Simpler realizations can replicate Zachman structure using file system folders.

Applying RUP to Zachman or vice versa makes for a better overall learning experience.

Since both RUP and Zachman can depend on UML, the latter is the preferred methodology of the three to introduce first.

With its rigid structure, Zachman may be just the right source of information to answer questions like these. 10

Application 8: Use RUP with Zachman to help bridge the gap between enterprise and project architecture

Application 4: Learning RUP alongside Zachman (and vice versa) may be easier

Application 5: Zachman as an aid during RUP tailoring

Figure 9: Meta-analysis of Zachman during RUP planning

Application 7: When planning a RUP project, look at the Zachman structure

Figure 7: Distribution of artifacts according to the Zachman layout