:-j
On Oct 15, 1:56 am, Brian K Seitz
> I agree. The old adage still applies. A fool with a tool is still a fool. Tools, especially I.T. tools are good for storing and calculations, but very poor at thinking.
> I started out with simple set of diagrams and a spreadsheet, when nature of the data and the problem became more than a whiteboard could contain I switched to building my own EA Portfolio management database out of MS Access and the office suite. While not as fancy as a shrinkwrap, it gets the job done fast and efficently. The nice part about using a database is the ability to create links as needed. The bad part is creating links as done as opposed to as desired. Like anything measure twice cut once :-)
> Brian K Seitz
> -----Original Message-----
> >From: Joseph George
> >Sent: Oct 14, 2008 10:54 AM
> >To: The Enterprise Architecture Network
> >Subject: Re: Architecture Consolidation
> >Benjamin,
> >Just to make it clear, my post in no way was a recommendation for any
> >particular tool. My personal opinion is that tools are very useful
> >when your "requirement becomes complex". But, tools are no good, if
> >you don't know how to do it otherwise. Tools are no good, if you don't
> >know how to use the various power features offered by your tool.
> >Just a simple example: If all I want to do is write a letter and print
> >it, do I really need MS Word (and I am not advocating this tool
> >either)? Only when my requirement becomes complex enough, that I might
> >want to use a tool. If I didn't know how to fully use MS Word, how
> >useful and advantageous might this be to me in publishing a set of
> >huge master documents, sub-linked to various other documents? I might
> >as well do it in WordPad and not do anything different, if I only
> >needed to do it once. Far simpler and cheaper!
> >I also find that overtime, many EA tools have matured significantly.
> >Having said that, I still personally prefer to use the whiteboard, and/
> >or paper & pencil for all initial work, and then transfer them online.
> >You don't need to use a sledge-hammer every time, even if you have one
> >ready and available.
> >I think the second part of your question deserves to be in its own
> >thread. I'm sure many others might be eager to contribute too.
> >Best regards,
> >Joseph
> >On Oct 03, 06:22 pm, Benjamin
> >> Joseph,
> >> Nice to see that you are using Casewise as a tool. But don't you think
> >> that tools as such when requirement becomes complex are unable to
> >> handle. I did scantily used casewise long time back - but eventually
> >> it turned out to be diagram mess.
> >> Which all framework have you used for Business, Enterprise & Data
> >> Architecture.
> >> Thanks;
> >> Benjamin
> Thank You
> Brian K Seitz
No comments:
Post a Comment