#ARCHITECTURAL DIAGRAMS PROGRAMMING DATABASE HOW TO#
This was a liberating experience as it freed us from the extremely limited "Models" provided in TOGAF itself and showed us how to create high quality materials using nothing more sophisticated than Visio. He provided real world examples (with names redacted but otherwise complete) of the collateral produced by his company on the understanding that we as students could not take copies but could look. When I did a TOGAF course prior to my certification exams the trainer explained that the Models provided with the TOGAF materials were a compromise between all of the participants (Look at the list of members from pages xxv - xxx in the 9.1 edition of the book and imagine getting all of them to agree on anything - CA, CSC, HP, IBM.) and as such were pretty much useless. In the above example, you'd want to include or hide technical details for certain audiences but both diagrams would be appropriate for one level of detail so don't stress over the colour or shape of the boxes so long as the information is accessible and comprehensible.Įdit following the changes to the question Decide what viewpoints you need to create and ensure that each viewpoint has a clear targeted diagram that tells your stakeholders what they need to know. TOGAF advocates having a number of "viewpoints" of the architecture targeting different stakeholder groups concerns and different levels of detail. Use the most appropriate representation that works for your audience. This question makes about as much sense to TOGAF Certified individual as the question "How to represent and application and database in PRINCE2" would to a PRINCE2 qualified individual. There's no magical template for TOGAF - TOGAF is a methodology for describing existing architectures, future architecture states and the road maps to get from one to another.
0 kommentar(er)
