Archive for Process
Why Just Enough Technology?
Posted by: | CommentsJust Enough Technology means providing the right technology to solve the right problem at the right cost. Not too much, not too little. The objectives of the business must be prioritized and kept in mind from concept to design to implementation to maintenance. Every decision made along the way must map to a business objective. Every software requirement must map to a business objective. This is the foundation of Just Enough Technology – clear and concise business objectives. Those objectives drive the requirements, and the requirements drive the design and implementation.
This is how I ended a short article about Just Enough Technology a while back. I’ve reproduced here for your reading pleasure. Differing opinions are invited 
Why Do We Need Software Architects?
Posted by: | CommentsAnother Blast From The Past Article – Originally Published in Sept. 2003
I am a software architect, but I’m not a “Blue Sky” thinker; I’m more of a practical thinker. I asked myself some questions about architects. What is a Software Architect and why do we need them? What do we expect from architects and why not just have a tech lead? Is there real benefit in an architect and are some projects too small for an architect? If so, what qualifies a project as needing an architect? Read More→
Risk Management in Requisite Pro
Posted by: | CommentsRisk Management is an important part of project success. Here is one way to help perform Risk Management using Rational Requisite Pro. Risks are a part of every project. Successful projects successfully manage risks. You can never completely eliminate risk, so it must be dealt with proactively.
Using Rational XDE with Visual Studio .Net
Posted by: | CommentsI have not been a great fan of reverse engineering tools in general. When I was creating applications in years ago, I held great hope for Visual Modeler. I do strongly believe in providing adequate documentation for an application and I most certainly value implementing an appropriate design phase during a project’s lifecycle. The tools available for accomplishing this have been sorely lacking in key areas, in my opinion.
What makes a documentation / design tool a good one? Well, seamless integration into the development process is one quality that is important to me. I detest having to input the same information more than once. That is one of the greatest strong points of automation. I’ve designed applications to automate workflow processes and share information between systems using tools that did not provide a solid way to do this with the development process. Read More→
A Programmer’s Bill of Rights?
Posted by: | CommentsHere’s a link to good post that talks about how companies can enhance developer productivity with some small investments in things like dual monitors. I just reread this article after finding it over a year ago. I am diligently trying to move our own department towards the things listed in the article, though some items, such as dual monitors, may be difficult for us given the current economic climate. We developers understand experientially how these things help our productivity, but is not always easy to communicate these truths to management. Read More→
