Posts Tagged Visio
This taxonomy is very much a work in progress. I can guarantee that this taxonomy will evolve and change. The taxonomy will grow as the classes of tools classified expands to meet all of the “niches” which the development software environment contains.
Why Produce a Taxonomy of Software Development Tools
This represents one of the starting steps in the development of Software Architecture for area I’m working in. My view on a Software Architecture is that encompasses the tools, as well as the architecture of the solutions within the architecture.
What does the Tools Taxonomy lead towards, in the development of an architecture? There are number of elements of software architecture which flow from having a Tools Taxonomy. These elements of a software architecture which include:
- Some degree of control over the tools used in the group.
- The taxonomy allows for the identification of the toolset which is preferred for development. A degree of control over the toolset used can be important in any the software development group. There are number of direct benefits which can flow from having a good understanding of the tools portfolio of a development group which include:
- minimising of the costs of team members moving between project teams, by using the same set of tools is projects is an important goal.
- Rationalising the number of tools used in the group, and hence the licence costs for tools. This can only be realised when you have the luxury of being able to rationalise the toolset being used.
- The Tools Taxonomy is needed if you wish to map systems which the teams develops, or maintains, to the tools which are used in the construction of those systems. This is import if you ever need to do an impact analysis of removing, or upgrading, a tool.
The following is an image of the taxonomy (a Visio Organisation Chart – produced using the Organisation Chart Wizard – see the previous posts: Display Hierarchical Data With Visio and Excel). The taxonomy is heavily focused on the Software Development process and tools.
The Excel source for this can be found here (Software Development Tools Taxonomy).
This is very much a work in progress.
This taxonomy could provide a starting point for the development of a tools taxonomy which is specific to your requirements.
This is a post on how to display any hierarchal data in Visio. It is one of those post which shows the benefit of using the Microsoft Office suite, when you know how to make them “dance to your tune”.
This shows how to “bend” the “Organization Chart Wizard” (the US spelling on the screen) to display an arbitrary set of hierarchical data. In this case I have been using it go generate a presentation of a “Taxonomy of Software”, or a “Software Portfolio Taxonomy” (if you prefer – I’m not exactly what title to give it yet). I’ll blog about the taxonomy, and some of the design decisions, I’ve built in a subsequent blog post.
The data which is “presented” by Visio, is a Excel Table in an Excel Work Book. The columns I am using are shown beside. This is the top of the taxonomy, “Software Portfolio” is the one top element, which has a couple of children shown. You can probably go to any depth (number of levels down from the top), or width (I’ve only tried one top element, but I’ve only tried one top thus far), I’ve not found where the limits are in this approach.
One Tip For Creating the Data
The hierarchical relation “hangs together” on the basis of the strings in the “Parent” and “Name” columns. To make sure that these are going to link together correctly, use Excel’s copy and paste functions to duplicate the strings between the columns. Being a lazy typist, I always do this.
You do need to have you wits about you when you are setting up the data. Visio is doing all the hard work drawing the hierarchical tree, any mistakes (things not linking up the way you wanted) and you just go back fix the data, and run the wizard again.
I’ll show the individual steps here, so that you should be able to follow.
This is under the Business Templates in the “Create New” part of Visio. This is the starting point for the process.
Here select the “Information that’s already stored in a file or database”.
Tip: Make sure you have saved and closed the Excel workbook which has the data you about to use. If you don’t you’ll get an error from one of the following wizard screens.
This is where we start down the data from Excel path.
I have not tried any other data source, but I’m certain that those should also work.
Just select the Excel Workbook which you have set up with the data to be presented in the hierarchical structure.
This is the point where using an Excel Table in the Workbook brings a benefit. The system knows how to get the names form the columns of the table.
Step 6 – Selecting The Field which is Displayed
This is where we are setting the field which is “put in the boxes” which Visio is going to draw is defined.
If you other data columns you would like to have attached into each of the object created by this process, this where you specify them.
I’ve not used this option, but it should work. If you are using people, then phone numbers and locations could be extra data which you would attach.
I have found that what I’ve wanted is all of the hierarchy on the one Visio page. I do some shuffling around to get it to “fit”, but that’s simple stuff to do.
This is the end wizard screens. Visio will next “whir it’s cogs”, and present you with a hierarchal display of the data you have fed into it.
The opposite is a screen grab from Visio. All of the text and lines are generated by the wizard. A bit of quick shuffling and I get it all onto one page.
Applying a Theme and Effects takes the simple monochrome present into something which the “boss” or “client” will like.
I hope this saves you some time when next confronted with lots of data which you need to build a presentation from.
This approach saves a lot of work in Visio, and the sort of work which I dislike doing. I really hate drawing boxes, adding text to them and drawing lines between them, especially when there is a smarter way to achieve the result.
I’ve been drawing a few UML Sequence diagrams with Visio (at work). This is the first time I’ve tried to draw such a diagram with Visio. Today, I struck a foible of Visio working with this diagram type. Also, I think I’ve found the “right” way of getting Visio to draw this diagram type, which I’ll share in the following.
When I started working with this diagram type I ended up with Lifelines which needed to be extended after an Activation Block. The problem was that the “extra Lifeline” object would not join on the center of the Activation Block. The graphic to the left shows what I ended up with. This was not a satisfactory solution. My sense of aesthetics was offended by the outcome.
Just extend the Lifeline to the full length of the diagram and then drop the Activation segment on the Lifeline. The left shows the before, the right shows the after. I could not be simpler, but it had me going for a while trying to the get the “extra Lifeline Object” to work for me.
I’m starting to wonder what the purpose of the extra segment object is really for. Extending the Lifeline to the full length works so well, why would you need an extra bit. If nothing else it’s confusing to have one. But, there are probably versions of the UML Sequence diagram, which utilises the extra segment. I’ve yet to see an example of one yet, but they could be our there.
I hope this reduces the WTF count in the universe. See TheDailyWTF for example of WTF’s.