public marks

PUBLIC MARKS from tadanderson with tags technology & rup

2012

Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies Book Review

This is one of those books that should be read by every person with a relationship to IT. Testers, CIOs, CFOs, developers, architects, project managers, and agilists will benefit from this book. I highly recommend reading it. You will come out the back end of it with a complete new perspective on Software Engineering.

.NET Architecture and Development Book Recommendations for 2012

Another year has gone by. Happy New Year everyone. It is time to update my book recommendation blog. There have been a ton of books come out this year both good and bad.

2007

Cool Links III- .NET 3.0, 3.5, Acropolis, TFS, AJAX, Visual Studio 2008, CAB, WPF, Silverlight, WCF, SQL Server 2008

I posted a few sets of links a few months ago. Here is another list. There has been a ton of new info to keep up with. Topics - .NET 3.0, 3.5, Acropolis, TFS, AJAX, Visual Studio 2008, CAB, WPF, Silverlight, SQL Server 2008, Architecture, WCF, LINQ, MVP, Repository Factory, etc...

if(Money == RUP || $$$ == IBM || RMC == Cash){Your Golden}else{Go OpenUP};

Wow... IBM's pricing for using the Rational Unified Process and the Rational Method Composer stinks. If you can see it, you got to pay for it.

When will Microsoft Sew their Nose Back On???

A few years ago Microsoft decided to cut off its nose to spite its face. The war on UML started with the DSL movement. Although Microsoft still claimed to see UML as an essential tool, they stopped trying to compete with the rest of the market and tried to lead us down a new path that did not include UML.

Thinking Software Development Process Implementation is Free means the Blind are Leading the Blind, but there are Ruby Slippers that may Help.

What makes people think a Software Development Process can be implemented in an organization at no upfront cost (including time and money)? Of course the number one culprit is lack of experience. The inexperienced have no understanding of what is involved in process engineering, and they usually have the belief that process is a luxurious overhead that is only to be thought about when there is complete downtime or during hours above billable hours.