What about Software Architecture?
All I have seen so far in VSTS 2005 is new tools for the System Architect, Developer, Tester, and Project manager. I'd like to hear what Microsoft is planning for the Software Architect.
In my Blog on DSL tools ( http://realworldsa.dotnetdevelopersjournal.com/dsl.htm ) I summarize my thoughts on how much of a mess I think they are going to create in the industry.
I would like to hear some thoughts on what MS is planning to do for the Software Architect (NOT System Architect) besides making us turn to third party vendors for the tools we need to do our jobs.
Answers
- It is really important, especially with Visual Studio, to not see the tool as a completed thing, but something that is continually evolving. That means that as good as VS 2005 is, it is just a step along the way. With that in mind, I would suggest that you are right by expecting 'people in the know' to influence Microsoft, but that doesn't stop you doing it too. You can find the Microsoft people through msdn.microsoft.com/architecture.
I have been pinged a few times about why I marked the second response as the answer. It reminded me that I have always had to depend on other tools for Software Architecting and Development. For architecture, the past few years I have used Rational's XDE (may they R.I.P.). Before that I used Rose. For development before Visual Studio 2002 I used Borland and ColdFusion Studio. So he is right in that MS has made progress, but I will need to rely on other tools for Architecting.
I was just hoping that this year I could spend less on software than I do on my cars.
BTW, DSL tools are the only fault I am finding with the new MS tools. Here is where we are with our evaluation of them.
As far ice cream goes in the other post, I do believe most people are capable of eating it with many different processes, but making it is a different story. Try convincing these guys process is not needed in the making of ice cream http://www.creamery.psu.edu/creamery.html
Yes skills are needed and in one-off development shops (big or small), skills and sweat carry the load for the lack of process (see
), but if you have every been in a successful shop, executing processes successfully makes a world of difference. There is a big difference between Development and Engineering (see
), and engineering is my current concern.
- I have posted a reply on my blog (http://blogs.msdn.com/jackgr/archive/2006/01/06/510162.aspx).
All Replies
The taxonomy Microsoft is using (at least for the certifications) is "Solutions Architect" so I suppose that's what you would call "software architect".
That said, as far as your blog entry, Microsoft can hardly control what random yahoos do with their tools - the alternative being no tools are released and we trudge on with what we have today?
And in any case, the methodology/process one happens to like is really like one's favorite ice cream. Everybody has one. I've seen shops completely butcher UP; Amercan Express' Method/1 sucks rocks but they get things done (mostly). It's really the people who implement the solution rather than the methodology they use.
- It is really important, especially with Visual Studio, to not see the tool as a completed thing, but something that is continually evolving. That means that as good as VS 2005 is, it is just a step along the way. With that in mind, I would suggest that you are right by expecting 'people in the know' to influence Microsoft, but that doesn't stop you doing it too. You can find the Microsoft people through msdn.microsoft.com/architecture.
I have been pinged a few times about why I marked the second response as the answer. It reminded me that I have always had to depend on other tools for Software Architecting and Development. For architecture, the past few years I have used Rational's XDE (may they R.I.P.). Before that I used Rose. For development before Visual Studio 2002 I used Borland and ColdFusion Studio. So he is right in that MS has made progress, but I will need to rely on other tools for Architecting.
I was just hoping that this year I could spend less on software than I do on my cars.
BTW, DSL tools are the only fault I am finding with the new MS tools. Here is where we are with our evaluation of them.
As far ice cream goes in the other post, I do believe most people are capable of eating it with many different processes, but making it is a different story. Try convincing these guys process is not needed in the making of ice cream http://www.creamery.psu.edu/creamery.html
Yes skills are needed and in one-off development shops (big or small), skills and sweat carry the load for the lack of process (see
), but if you have every been in a successful shop, executing processes successfully makes a world of difference. There is a big difference between Development and Engineering (see
), and engineering is my current concern.
- I have posted a reply on my blog (http://blogs.msdn.com/jackgr/archive/2006/01/06/510162.aspx).
Thanks for reponding...
I have tried to clarify my frustrations @
http://realworldsa.dotnetdevelopersjournal.com/dsl.htm
My hopes are that DSL's are used in the context you described and do not get abused.
